
From daedulus@btconnect.com  Thu Mar  1 02:45:50 2012
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 799D121F864E for <ietf@ietfa.amsl.com>; Thu,  1 Mar 2012 02:45:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.732
X-Spam-Level: 
X-Spam-Status: No, score=-0.732 tagged_above=-999 required=5 tests=[AWL=-1.333, BAYES_50=0.001, J_CHICKENPOX_102=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LUILpB22dnMc for <ietf@ietfa.amsl.com>; Thu,  1 Mar 2012 02:45:49 -0800 (PST)
Received: from mail.btconnect.com (c2bthomr09.btconnect.com [213.123.20.127]) by ietfa.amsl.com (Postfix) with ESMTP id A7BC421F863E for <ietf@ietf.org>; Thu,  1 Mar 2012 02:45:47 -0800 (PST)
Received: from host86-163-139-217.range86-163.btcentralplus.com (HELO pc6) ([86.163.139.217]) by c2bthomr09.btconnect.com with SMTP id GOF25199; Thu, 01 Mar 2012 10:45:44 +0000 (GMT)
Message-ID: <003501ccf790$009c5b20$4001a8c0@gateway.2wire.net>
From: "t.petch" <daedulus@btconnect.com>
To: "Murray S. Kucherawy" <msk@cloudmark.com>, <ietf@ietf.org>
References: <20120301004219.15266.76505.idtracker@ietfa.amsl.com> <9452079D1A51524AA5749AD23E00392806E6F5@exch-mbx901.corp.cloudmark.com>
Subject: Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple MailTransfer Protocol extension for Message Transfer Priorities)to	Proposed Standard
Date: Thu, 1 Mar 2012 10:45:09 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Mirapoint-IP-Reputation: reputation=Fair-1, source=Queried, refid=tid=0001.0A0B0303.4F4F5357.0076, actions=tag
X-Junkmail-Premium-Raw: score=7/50, refid=2.7.2:2012.3.1.101215:17:7.944, ip=86.163.139.217, rules=__HAS_MSGID, __OUTLOOK_MSGID_1, __SANE_MSGID, __TO_MALFORMED_2, __BOUNCE_CHALLENGE_SUBJ, __BOUNCE_NDR_SUBJ_EXEMPT, __MIME_VERSION, __CT, CT_TP_8859_1, __CT_TEXT_PLAIN, __CTE, __HAS_X_PRIORITY, __HAS_MSMAIL_PRI, __HAS_X_MAILER, USER_AGENT_OE, __OUTLOOK_MUA_1, __USER_AGENT_MS_GENERIC, __ANY_URI, __URI_NO_WWW, __URI_NO_PATH, __CP_NOT_1, BODYTEXTP_SIZE_3000_LESS, BODY_SIZE_800_899, __MIME_TEXT_ONLY, RDNS_GENERIC_POOLED, HTML_00_01, HTML_00_10, BODY_SIZE_5000_LESS, RDNS_SUSP_GENERIC, __OUTLOOK_MUA, BODY_SIZE_1000_LESS, RDNS_SUSP, BODY_SIZE_2000_LESS, BODY_SIZE_7000_LESS
X-Junkmail-Status: score=10/50, host=c2bthomr09.btconnect.com
X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A0B020C.4F4F5358.00AD,ss=1,re=0.000,fgs=0, ip=0.0.0.0, so=2011-07-25 19:15:43, dmn=2011-05-27 18:58:46, mode=multiengine
X-Junkmail-IWF: false
Cc: alexey.melnikov@isode.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Mar 2012 10:45:50 -0000

----- Original Message -----
From: "Murray S. Kucherawy" <msk@cloudmark.com>
To: <ietf@ietf.org>
Cc: <alexey.melnikov@isode.com>
Sent: Thursday, March 01, 2012 5:43 AM
> - Appendix D: "This appendix and its subsections are informative."  I think
that (a) any appendix is informative, because normative text doesn't belong in
an appendix; and (b) the normative stuff uses RFC2119 language and this doesn't.
Thus, I think this sentence should be removed.  (I know I've lost this argument
before, but I'll make another stand here anyway.)
>
I hope that you lose again:-)  I am always confused, since I see a substantial
number of normative appendices and so want it clearly spelt out, is it
informative, what happens when the body clashes with the appendices etc etc.

Tom Petch

> -MSK


From barryleiba.mailing.lists@gmail.com  Thu Mar  1 06:10:10 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 ECCD521E829A for <ietf@ietfa.amsl.com>; Thu,  1 Mar 2012 06:10:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.987
X-Spam-Level: 
X-Spam-Status: No, score=-102.987 tagged_above=-999 required=5 tests=[AWL=-0.010, 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 LYIIUFzJsxEv for <ietf@ietfa.amsl.com>; Thu,  1 Mar 2012 06:10:09 -0800 (PST)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id A59F421E87D1 for <ietf@ietf.org>; Thu,  1 Mar 2012 06:09:49 -0800 (PST)
Received: by yhpp34 with SMTP id p34so239305yhp.31 for <ietf@ietf.org>; Thu, 01 Mar 2012 06:09:49 -0800 (PST)
Received-SPF: pass (google.com: domain of barryleiba.mailing.lists@gmail.com designates 10.236.37.132 as permitted sender) client-ip=10.236.37.132; 
Authentication-Results: mr.google.com; spf=pass (google.com: domain of barryleiba.mailing.lists@gmail.com designates 10.236.37.132 as permitted sender) smtp.mail=barryleiba.mailing.lists@gmail.com; dkim=pass header.i=barryleiba.mailing.lists@gmail.com
Received: from mr.google.com ([10.236.37.132]) by 10.236.37.132 with SMTP id y4mr7391322yha.10.1330610989242 (num_hops = 1); Thu, 01 Mar 2012 06:09:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=cbKo0B2TYnh3x+SiEJPaL+ngH9c5LpV0qgZub22533c=; b=Q+YY0Y1RHWoJP+wCI6/NQ+7+OFpY17pn4rmYrdufL33fmv5WBWTeSebFmSV6fqiTb8 6rje/2JvRPrOeRVo6KeijrUWFdawLSkbh8jmwVsX+AzQ5htK+FW0f7xNRnNkGnhUPWNd th8wSfyWyIILNc8Lid8ex47/rBcHjKtmkXB50=
MIME-Version: 1.0
Received: by 10.236.37.132 with SMTP id y4mr5751454yha.10.1330610989192; Thu, 01 Mar 2012 06:09:49 -0800 (PST)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.147.106.16 with HTTP; Thu, 1 Mar 2012 06:09:49 -0800 (PST)
In-Reply-To: <6.2.5.6.2.20120229181328.0a95a9f8@resistor.net>
References: <20120301004643.17274.83943.idtracker@ietfa.amsl.com> <6.2.5.6.2.20120229181328.0a95a9f8@resistor.net>
Date: Thu, 1 Mar 2012 09:09:49 -0500
X-Google-Sender-Auth: _G9wUa_Wm2XX7bX4QPDw-UaOye8
Message-ID: <CAC4RtVDUmcLZh4J2SvV32kNxaQcPYr1+9S9q59Kd50F4hqWaOQ@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-marf-spf-reporting-08.txt> (SPF Authentication Failure Reporting using the Abuse Report Format) to Proposed Standard
From: Barry Leiba <barryleiba@computer.org>
To: SM <sm@resistor.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Mar 2012 14:10:10 -0000

> The MARF charter [1] does not contain any mention of "SPF Authentication
> Failure Reporting using the Abuse Report Format" as a deliverable. =A0The=
re is
> no mention of SPF in the charter.

Keep in mind that the charter has these two items:

 2) The group will produce an informational document detailing
 guidelines for deploying and using ARF, including descriptions
 of current practices and their rationales.

 3) The group will specify the integration of ARF into DKIM-aware
 environments, with draft-kucherawy-dkim-reporting-06 as its input.
 It contains extensions to DKIM that are related to ARF as a means
 of reporting DKIM-related failures which include phishing
 ("fraud") and as such are relevant to the ARF effort. The group
 will produce Proposed Standard track specification for these
 ARF and DKIM extensions.

Then note this:
1. The reporting document originally included the SPF information,
since there's a lot of common aspects, and it makes sense to talk
about both.  The WG decided to split the document into four pieces,
for organizational purposes, with authfailure-report, redaction, dkim,
and spf as separate pieces.

2. SPF is widely deployed in the real world.  Information about
deploying and using ARF (item 2 in the charter) in such an environment
is absolutely part of the charter.

It's important to get this information out there in parallel with the
DKIM information.  If the output of the spfbis working group results
in a need for a revision to this document, such revision can be taken
up then.

Barry

From scott@kitterman.com  Thu Mar  1 06:22:25 2012
Return-Path: <scott@kitterman.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7EA9C21E82D1 for <ietf@ietfa.amsl.com>; Thu,  1 Mar 2012 06:22:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Gp9x1H+TLHtf for <ietf@ietfa.amsl.com>; Thu,  1 Mar 2012 06:22:24 -0800 (PST)
Received: from mailout02.controlledmail.com (mailout02.controlledmail.com [72.81.252.18]) by ietfa.amsl.com (Postfix) with ESMTP id 7331621E8276 for <ietf@ietf.org>; Thu,  1 Mar 2012 06:22:24 -0800 (PST)
Received: from mailout02.controlledmail.com (localhost [127.0.0.1]) by mailout02.controlledmail.com (Postfix) with ESMTP id C04B620E40DA; Thu,  1 Mar 2012 09:22:23 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=2007-00; t=1330611743; bh=akvEt92GrcOvLJdoBBC34UEw2IX1VuBa9pMvu9ds+30=; h=From:To:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version:Content-Transfer-Encoding:Content-Type; b=KxFuFv5zecW60R4dJSWSDdWkFUkilir9G6kVqaS6rseqhY5AclDkliA4g0aYMgq/T niCgM/WipZ5pIjrF4xyqpJAZqR0X8lN2GH/80xtpxHmmwRtJM5kZILSmgT2IoJpLnC /dXPq/L6uqEw3DmK/YsFDltA3k59K6rDmwWGPzoM=
Received: from scott-latitude-e6320.localnet (170.sub-97-10-249.myvzw.com [97.10.249.170]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailout02.controlledmail.com (Postfix) with ESMTPSA id 6C14C20E408F;  Thu,  1 Mar 2012 09:22:23 -0500 (EST)
From: Scott Kitterman <scott@kitterman.com>
To: ietf@ietf.org
Subject: Re: Last Call: <draft-ietf-marf-spf-reporting-08.txt> (SPF Authentication Failure Reporting using the Abuse Report Format) to Proposed Standard
Date: Thu, 01 Mar 2012 09:22:22 -0500
Message-ID: <8066871.IkNuLJFsLQ@scott-latitude-e6320>
User-Agent: KMail/4.7.3 (Linux/3.0.0-16-generic-pae; KDE/4.7.4; i686; ; )
In-Reply-To: <6.2.5.6.2.20120229181328.0a95a9f8@resistor.net>
References: <20120301004643.17274.83943.idtracker@ietfa.amsl.com> <6.2.5.6.2.20120229181328.0a95a9f8@resistor.net>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
X-AV-Checked: ClamAV using ClamSMTP
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Mar 2012 14:22:25 -0000

On Wednesday, February 29, 2012 10:26:41 PM SM wrote:
> At 16:46 29-02-2012, The IESG wrote:
> >The IESG has received a request from the Messaging Abuse Reporting Format
> >WG (marf) to consider the following document:
> >- 'SPF Authentication Failure Reporting using the Abuse Report Format'
> >
> >   <draft-ietf-marf-spf-reporting-08.txt> as a 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-03-14. Exceptionally, comments may be
> 
> [snip]
> 
> >Note that this document has a downward normative reference: This
> >document makes a normative reference to SPF (RFC4408), which is
> >Experimental.
> The MARF charter [1] does not contain any mention of "SPF
> Authentication Failure Reporting using the Abuse Report Format" as a
> deliverable.  There is no mention of SPF in the charter.
> 
> According to the Abstract Section of this document:
> 
>    "This memo presents extensions to the Abuse Reporting Format (ARF),
>     and Sender Policy Framework (SPF) specifications to allow for
>     detailed reporting of message authentication failures in an on-demand
>     fashion."
> 
> This extends a specification on which there hasn't been any
> conclusion yet.  I note that there is a downward normative reference
> to RFC 4408.  During discussions about RFC 4408, on which I don't
> have any opinion up to now, there have been comments about:
> 
>   (i)   The specification not being sufficiently clear.
> 
>   (ii)  A compelling case that there is, indeed, an error in RFC4408.
> 
>   (iii) Interoperability problems in the protocol due to DNS
> "incompatibility".
> 
> I suggest that the IETF waits for a migration or co-existence
> document which discusses about the non-standards track protocol on
> which there is a downward reference.

I'll limit my response to these aspects of your comment, since they are the 
most important to resolve.

I'll leave it to the MARF chairs to explain their view of how this is related 
to the charter.  This draft is, however, related to draft-ietf-marf-
authfailure-report, which is already through last call and approved by the 
IESG.  It includes SPF specifics (although it doesn't require a normative 
reference to RFC 4408, so there's no downref issue with it), so I think that 
in the context of authentication failure reporting this is already established 
to be in scope.  All the current draft does is provide an optional mechanism 
to make the desire for such reports discoverable.

This draft does not depend on any elements of RFC 4408 that are under review 
in SPFbis (in fact, it's not possible in the current scope of the SPFbis 
charter to change any of them), so the risk that the ongoing work in SPFbis 
will affect this body of work is nil.

I don't think it's efficient at all to put this draft on hold and revive it 
later for non-technical reasons.

Scott K

From hongk@cisco.com  Thu Mar  1 07:14:04 2012
Return-Path: <hongk@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 276BB21F8B85 for <ietf@ietfa.amsl.com>; Thu,  1 Mar 2012 07:14:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wTt98a3XjkrV for <ietf@ietfa.amsl.com>; Thu,  1 Mar 2012 07:14:03 -0800 (PST)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) by ietfa.amsl.com (Postfix) with ESMTP id 2489F21F8B4A for <ietf@ietf.org>; Thu,  1 Mar 2012 07:14:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=hongk@cisco.com; l=2451; q=dns/txt; s=iport; t=1330614843; x=1331824443; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to; bh=DQ62t31LFPzDgqESQZxsM2X+F89Iq3z+Aj51L/C4qSI=; b=EYR/sGkR9JQIzBkABf3WnUK8mTV72hi4IcCxNcTQkFjChQvGA/H7bc0I XuHDH1Dli1qazBo7hELr/m14QdqyWWgLwd75a7f4j44vynLRT4/6/1iMD Oq4Wd6/Qe5yp//jiCefqP/vaaOXnKR9uwbXbRSJ+NLsTWshcfJ/lK5Qun E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EACWRT0+tJXG9/2dsb2JhbABDtAWBB4F9AQEBBAEBAQ8BHQo0FwQCAQgRBAEBCwYTBAEGASYfCQgCBBMIEweHZAuaBQGfAY0IDgsNAwI9GAkChRoCBAIFAQECAgELCgENBwQGGg6CP2MEiE+ffQ
X-IronPort-AV: E=Sophos;i="4.73,511,1325462400"; d="scan'208";a="63018667"
Received: from rcdn-core2-2.cisco.com ([173.37.113.189]) by rcdn-iport-7.cisco.com with ESMTP; 01 Mar 2012 15:14:02 +0000
Received: from xbh-rcd-202.cisco.com (xbh-rcd-202.cisco.com [72.163.62.201]) by rcdn-core2-2.cisco.com (8.14.3/8.14.3) with ESMTP id q21FE2ws007184 for <ietf@ietf.org>; Thu, 1 Mar 2012 15:14:02 GMT
Received: from xmb-rcd-103.cisco.com ([72.163.62.145]) by xbh-rcd-202.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 1 Mar 2012 09:14:02 -0600
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-betts-itu-oam-ach-code-point-03.txt> (Allocation of an Associated Channel Code Point for Use by ITU-T Ethernet based OAM) to Informational RFC
Date: Thu, 1 Mar 2012 09:14:01 -0600
Message-ID: <515703B08A3A064C9CC8C09ACCC710DC0631679E@XMB-RCD-103.cisco.com>
In-Reply-To: <03a301ccf174$ff953290$febf97b0$@olddog.co.uk>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt> (Allocation of an Associated Channel Code Point for Use by ITU-T Ethernet based OAM) to Informational RFC
thread-index: AQGdS0dQFbRu6GyAeWPtVTnp+xX6JJaoUwDwgAyPnwA=
References: <20120222151252.32262.82157.idtracker@ietfa.amsl.com> <03a301ccf174$ff953290$febf97b0$@olddog.co.uk>
From: "Kyung-Yeop Hong (hongk)" <hongk@cisco.com>
To: <ietf@ietf.org>
X-OriginalArrivalTime: 01 Mar 2012 15:14:02.0666 (UTC) FILETIME=[EF8B38A0:01CCF7BD]
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Mar 2012 15:14:04 -0000

No/do not support.

One of the issues with G.8113.1 in LS370 is its stability and maturity.
That was one of the reasons why it was not approved.=20

The Ethernet based OAM protocol documented in the LS370 version is
intended to be deployed for MPLS networks. I think the IETF has a duty
to ensure that a solution is stable and works for MPLS networks before
the code point allocation. A number of concerns with the deployment of
this proposed protocol raised in
draft-spercher-mpls-tp-oam-considerations are critical to the Internet
and must be taken into consideration in this Last Call.=20

KY


> -----Original Message-----
> From: ietf-announce-bounces@ietf.org [mailto:ietf-announce-
> bounces@ietf.org] On Behalf Of The IESG
> Sent: 22 February 2012 15:13
> To: IETF-Announce
> Subject: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt>
(Allocation of
an
> Associated Channel Code Point for Use by ITU-T Ethernet based OAM) to
> Informational RFC
>=20
>=20
> The IESG has received a request from an individual submitter to
consider
> the following document:
> - 'Allocation of an Associated Channel Code Point for Use by ITU-T
>    Ethernet based OAM'
>   <draft-betts-itu-oam-ach-code-point-03.txt> as an Informational RFC
>=20
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2012-03-21. Exceptionally, comments may
be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
>=20
> Abstract
>=20
>    This document assigns an Associated Channel Type code point for
>    carrying Ethernet based Operations, Administration, and Management
>    messages in the MPLS Generic Associated Channel (G-ACh).
>=20
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-betts-itu-oam-ach-code-point/
>=20
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-betts-itu-oam-ach-code-point/
>=20
>=20
> No IPR declarations have been submitted directly on this I-D.
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-announce

_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls

From nurit.sprecher@nsn.com  Thu Mar  1 07:15:32 2012
Return-Path: <nurit.sprecher@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 7CB2521E816C for <ietf@ietfa.amsl.com>; Thu,  1 Mar 2012 07:15:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.537
X-Spam-Level: 
X-Spam-Status: No, score=-6.537 tagged_above=-999 required=5 tests=[AWL=0.062,  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 mKZi9uU85osu for <ietf@ietfa.amsl.com>; Thu,  1 Mar 2012 07:15:31 -0800 (PST)
Received: from demumfd002.nsn-inter.net (demumfd002.nsn-inter.net [93.183.12.31]) by ietfa.amsl.com (Postfix) with ESMTP id 8EC4C21E803E for <ietf@ietf.org>; Thu,  1 Mar 2012 07:15:31 -0800 (PST)
Received: from demuprx016.emea.nsn-intra.net ([10.150.129.55]) by demumfd002.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id q21FFRgx004483 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 1 Mar 2012 16:15:27 +0100
Received: from demuexc022.nsn-intra.net (demuexc022.nsn-intra.net [10.150.128.35]) by demuprx016.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id q21FFNt0001924; Thu, 1 Mar 2012 16:15:27 +0100
Received: from DEMUEXC013.nsn-intra.net ([10.150.128.24]) by demuexc022.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 1 Mar 2012 16:15:00 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt>(Allocation of an Associated Channel Code Point for Use byITU-T Ethernet based OAM) to Informational RFC
Date: Thu, 1 Mar 2012 16:14:59 +0100
Message-ID: <E4873516F3FC7547BCFE792C7D94039C015D117D@DEMUEXC013.nsn-intra.net>
In-Reply-To: <515703B08A3A064C9CC8C09ACCC710DC0631679E@XMB-RCD-103.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt>(Allocation of an Associated Channel Code Point for Use byITU-T Ethernet based OAM) to Informational RFC
Thread-Index: AQGdS0dQFbRu6GyAeWPtVTnp+xX6JJaoUwDwgAyPnwCAAALukA==
References: <20120222151252.32262.82157.idtracker@ietfa.amsl.com><03a301ccf174$ff953290$febf97b0$@olddog.co.uk> <515703B08A3A064C9CC8C09ACCC710DC0631679E@XMB-RCD-103.cisco.com>
From: "Sprecher, Nurit (NSN - IL/Hod HaSharon)" <nurit.sprecher@nsn.com>
To: "ext Kyung-Yeop Hong (hongk)" <hongk@cisco.com>, <ietf@ietf.org>
X-OriginalArrivalTime: 01 Mar 2012 15:15:00.0980 (UTC) FILETIME=[124D3B40:01CCF7BE]
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: 2955
X-purgate-ID: 151667::1330614927-000015E0-D70A19C4/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: Thu, 01 Mar 2012 15:15:32 -0000

Great!

-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
ext Kyung-Yeop Hong (hongk)
Sent: Thursday, March 01, 2012 5:14 PM
To: ietf@ietf.org
Subject: Re: Last Call:
<draft-betts-itu-oam-ach-code-point-03.txt>(Allocation of an Associated
Channel Code Point for Use byITU-T Ethernet based OAM) to Informational
RFC

No/do not support.

One of the issues with G.8113.1 in LS370 is its stability and maturity.
That was one of the reasons why it was not approved.=20

The Ethernet based OAM protocol documented in the LS370 version is
intended to be deployed for MPLS networks. I think the IETF has a duty
to ensure that a solution is stable and works for MPLS networks before
the code point allocation. A number of concerns with the deployment of
this proposed protocol raised in
draft-spercher-mpls-tp-oam-considerations are critical to the Internet
and must be taken into consideration in this Last Call.=20

KY


> -----Original Message-----
> From: ietf-announce-bounces@ietf.org [mailto:ietf-announce-
> bounces@ietf.org] On Behalf Of The IESG
> Sent: 22 February 2012 15:13
> To: IETF-Announce
> Subject: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt>
(Allocation of
an
> Associated Channel Code Point for Use by ITU-T Ethernet based OAM) to
> Informational RFC
>=20
>=20
> The IESG has received a request from an individual submitter to
consider
> the following document:
> - 'Allocation of an Associated Channel Code Point for Use by ITU-T
>    Ethernet based OAM'
>   <draft-betts-itu-oam-ach-code-point-03.txt> as an Informational RFC
>=20
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2012-03-21. Exceptionally, comments may
be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
>=20
> Abstract
>=20
>    This document assigns an Associated Channel Type code point for
>    carrying Ethernet based Operations, Administration, and Management
>    messages in the MPLS Generic Associated Channel (G-ACh).
>=20
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-betts-itu-oam-ach-code-point/
>=20
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-betts-itu-oam-ach-code-point/
>=20
>=20
> No IPR declarations have been submitted directly on this I-D.
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-announce

_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls
_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf

From nurit.sprecher@nsn.com  Thu Mar  1 07:20:44 2012
Return-Path: <nurit.sprecher@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 7F09D21E81C2 for <ietf@ietfa.amsl.com>; Thu,  1 Mar 2012 07:20:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.538
X-Spam-Level: 
X-Spam-Status: No, score=-6.538 tagged_above=-999 required=5 tests=[AWL=0.060,  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 DHA3sJf6F5xH for <ietf@ietfa.amsl.com>; Thu,  1 Mar 2012 07:20:41 -0800 (PST)
Received: from demumfd002.nsn-inter.net (demumfd002.nsn-inter.net [93.183.12.31]) by ietfa.amsl.com (Postfix) with ESMTP id 02DF821E81BF for <ietf@ietf.org>; Thu,  1 Mar 2012 07:20:40 -0800 (PST)
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 q21FKdt1016528 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for <ietf@ietf.org>; Thu, 1 Mar 2012 16:20:39 +0100
Received: from DEMUEXC048.nsn-intra.net ([10.159.32.94]) by demuprx017.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id q21FKXHv001361 for <ietf@ietf.org>; Thu, 1 Mar 2012 16:20:39 +0100
Received: from DEMUEXC013.nsn-intra.net ([10.150.128.24]) by DEMUEXC048.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 1 Mar 2012 16:20:35 +0100
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_01CCF7BE.D98DEA4C"
Subject: RE: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt>(Allocationof an Associated Channel Code Point for Use byITU-T Ethernetbased OAM) to Informational RFC
Date: Thu, 1 Mar 2012 16:20:34 +0100
Message-ID: <E4873516F3FC7547BCFE792C7D94039C015D118B@DEMUEXC013.nsn-intra.net>
In-Reply-To: <E4873516F3FC7547BCFE792C7D94039C015D117D@DEMUEXC013.nsn-intra.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt>(Allocationof an Associated Channel Code Point for Use byITU-T Ethernetbased OAM) to Informational RFC
Thread-Index: AQGdS0dQFbRu6GyAeWPtVTnp+xX6JJaoUwDwgAyPnwCAAALukIAAAQFg
References: <20120222151252.32262.82157.idtracker@ietfa.amsl.com><03a301ccf174$ff953290$febf97b0$@olddog.co.uk><515703B08A3A064C9CC8C09ACCC710DC0631679E@XMB-RCD-103.cisco.com> <E4873516F3FC7547BCFE792C7D94039C015D117D@DEMUEXC013.nsn-intra.net>
From: "Sprecher, Nurit (NSN - IL/Hod HaSharon)" <nurit.sprecher@nsn.com>
To: <ietf@ietf.org>
X-OriginalArrivalTime: 01 Mar 2012 15:20:35.0082 (UTC) FILETIME=[D97126A0:01CCF7BE]
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: 19543
X-purgate-ID: 151667::1330615239-000015E0-B7F0038B/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: Thu, 01 Mar 2012 15:20:44 -0000

This is a multi-part message in MIME format.

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

Hi,

=20

I cannot support the publication of the document in its current version.

=20

I have the following concerns:

=20

*        It is indicated that the channel is intended to be used to
carry Ethernet based OAM messages. It is not clear why there is a need
for ACH. PWs can be used to transmit Ethernet OAM.=20

If the intention is to use the channel for OAM messages for operating
MPLS-TP based networks, the IETF *already* defined a solution for
MPLS-TP OAM and I expect to see first a technical *justification* why a
second solution is needed. In addition, I would expect to see
*references to the arguments* raised in
draft-sprecher-mpls-tp-oam-considerations.=20

=20

*        It is not clear what the maturity status of G.8113.1 is. It
seems that the document was not approved by SG15 and the discussion was
deferred to WTSA. This indicates that there is *no consensus* for the
approval of G.8113.1. A code point should not be allocated before a
consensus/decision is reached in the ITU-T and before the document is
mature and approved. I do not think it is appropriate to allocate a code
point and try to force a resolution in the ITU-T.=20

=20

*        I find a contradiction in the draft. In one place it is
mentioned: "These Ethernet based OAM messages and procedures, address
the OAM functional requirements defined in [RFC5860]. Other message
types should not be carried behind this code point." In another place it
is mentioned: "all ITU-T Recommendations are subject to revision.
Therefore, the code point allocated by this document may be used for
future versions of [G.8113.1].". The last statement opens the door for
the definition of additional messages in G.8113.1 in the following
versions, for example, for APS (supporting linear or ring protection
mechanisms) and by this creates two solutions for other mechanisms as
well.=20

=20

The use of the code point can go much beyond its original purpose and it
will hide other messages....a code point should not be allocated at this
point at all, but specifically not for unknown usage that may be defined
in future versions of G.8113.1.=20

=20

Best regards,

Nurit

=20

=20

=20

> -----Original Message-----

> From: ietf-announce-bounces@ietf.org
<mailto:ietf-announce-bounces@ietf.org>  [mailto:ietf-announce-

> bounces@ietf.org <mailto:bounces@ietf.org> ] On Behalf Of The IESG

> Sent: 22 February 2012 15:13

> To: IETF-Announce

> Subject: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt>

(Allocation of

an

> Associated Channel Code Point for Use by ITU-T Ethernet based OAM) to

> Informational RFC

>=20

>=20

> The IESG has received a request from an individual submitter to

consider

> the following document:

> - 'Allocation of an Associated Channel Code Point for Use by ITU-T

>    Ethernet based OAM'

>   <draft-betts-itu-oam-ach-code-point-03.txt> as an Informational RFC

>=20

> The IESG plans to make a decision in the next few weeks, and solicits

> final comments on this action. Please send substantive comments to the

> ietf@ietf.org <mailto:ietf@ietf.org>  mailing lists by 2012-03-21.
Exceptionally, comments may

be

> sent to iesg@ietf.org <mailto:iesg@ietf.org>  instead. In either case,
please retain the

> beginning of the Subject line to allow automated sorting.

>=20

> Abstract

>=20

>    This document assigns an Associated Channel Type code point for

>    carrying Ethernet based Operations, Administration, and Management

>    messages in the MPLS Generic Associated Channel (G-ACh).

>=20

> The file can be obtained via

> http://datatracker.ietf.org/doc/draft-betts-itu-oam-ach-code-point/
<http://datatracker.ietf.org/doc/draft-betts-itu-oam-ach-code-point/>=20

>=20

> IESG discussion can be tracked via

> http://datatracker.ietf.org/doc/draft-betts-itu-oam-ach-code-point/
<http://datatracker.ietf.org/doc/draft-betts-itu-oam-ach-code-point/>=20

>=20

>=20

> No IPR declarations have been submitted directly on this I-D.

> _______________________________________________

> IETF-Announce mailing list

> IETF-Announce@ietf.org <mailto:IETF-Announce@ietf.org>=20

> https://www.ietf.org/mailman/listinfo/ietf-announce
<https://www.ietf.org/mailman/listinfo/ietf-announce>=20

=20

_______________________________________________

mpls mailing list

mpls@ietf.org <mailto:mpls@ietf.org>=20

https://www.ietf.org/mailman/listinfo/mpls
<https://www.ietf.org/mailman/listinfo/mpls>=20

_______________________________________________

Ietf mailing list

Ietf@ietf.org <mailto:Ietf@ietf.org>=20

https://www.ietf.org/mailman/listinfo/ietf
<https://www.ietf.org/mailman/listinfo/ietf>=20

_______________________________________________

Ietf mailing list

Ietf@ietf.org <mailto:Ietf@ietf.org>=20

https://www.ietf.org/mailman/listinfo/ietf
<https://www.ietf.org/mailman/listinfo/ietf>=20


------_=_NextPart_001_01CCF7BE.D98DEA4C
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:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 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: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;}
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;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
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:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1724795371;
	mso-list-type:hybrid;
	mso-list-template-ids:1827805576 1604772236 67698691 67698693 67698689 =
67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-start-at:0;
	mso-level-number-format:bullet;
	mso-level-text:\2022;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.5in;
	font-family:Consolas;
	mso-fareast-font-family:Calibri;}
@list l1
	{mso-list-id:2119984890;
	mso-list-type:hybrid;
	mso-list-template-ids:-1705461598 67698689 67698691 67698693 67698689 =
67698691 67698693 67698689 67698691 67698693;}
@list l1:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
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=3DMsoPlainText>Hi,<o:p></o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p class=3DMsoPlainText><span =
style=3D'color:black'>I cannot support the publication of the document =
in its current version.<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'color:black'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'color:black'>I have the following =
concerns:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'color:black'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.5in;mso-list:l0 level1 =
lfo2'><![if !supportLists]><span style=3D'color:black'><span =
style=3D'mso-list:Ignore'>&#8226;<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span dir=3DLTR></span><span =
style=3D'color:black'>It is indicated that the channel is intended to be =
used to carry Ethernet based OAM messages. It is not clear why there is =
a need for ACH. PWs can be used to transmit Ethernet OAM. =
<o:p></o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in'><span style=3D'color:black'>If the intention =
is to use the channel for OAM messages for operating MPLS-TP based =
networks, the IETF *already* defined a solution for MPLS-TP OAM and I =
expect to see first a technical *justification* why a second solution is =
needed. In addition, I would expect to see *references to the arguments* =
raised in draft-sprecher-mpls-tp-oam-considerations. =
<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'color:black'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.5in;mso-list:l0 level1 =
lfo2'><![if !supportLists]><span style=3D'color:black'><span =
style=3D'mso-list:Ignore'>&#8226;<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span dir=3DLTR></span><span =
style=3D'color:black'>It is not clear what the maturity status of =
G.8113.1 is. It seems that the document was not approved by SG15 and the =
discussion was deferred to WTSA. This indicates that there is *no =
consensus* for the approval of G.8113.1. A code point should not be =
allocated before a consensus/decision is reached in the ITU-T and before =
the document is mature and approved. I do not think it is appropriate to =
allocate a code point and try to force a resolution in the ITU-T. =
<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'color:black'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.5in;mso-list:l0 level1 =
lfo2'><![if !supportLists]><span style=3D'color:black'><span =
style=3D'mso-list:Ignore'>&#8226;<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span dir=3DLTR></span><span =
style=3D'color:black'>I find a contradiction in the draft. In one place =
it is mentioned: &quot;These Ethernet based OAM messages and procedures, =
address the OAM functional requirements defined in [RFC5860]. Other =
message types should not be carried behind this code point.&quot; In =
another place it is mentioned: &quot;all ITU-T Recommendations are =
subject to revision. Therefore, the code point allocated by this =
document may be used for future versions of [G.8113.1].&quot;. The last =
statement opens the door for the definition of additional messages in =
G.8113.1 in the following versions, for example, for APS (supporting =
linear or ring protection mechanisms) and by this creates two solutions =
for other mechanisms as well. <o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'color:black'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText style=3D'margin-left:.5in'><span =
style=3D'color:black'>The use of the code point can go much beyond its =
original purpose and it will hide other messages....a code point should =
not be allocated at this point at all, but specifically not for unknown =
usage that may be defined in future versions of G.8113.1. =
<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'color:black'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoPlainText><span style=3D'color:black'>Best =
regards,<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'color:black'>Nurit<o:p></o:p></span></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p class=3DMsoPlainText>&gt; =
-----Original Message-----<o:p></o:p></p><p class=3DMsoPlainText>&gt; =
From: <a href=3D"mailto:ietf-announce-bounces@ietf.org"><span =
style=3D'color:windowtext;text-decoration:none'>ietf-announce-bounces@iet=
f.org</span></a> [mailto:ietf-announce-<o:p></o:p></p><p =
class=3DMsoPlainText>&gt; <a href=3D"mailto:bounces@ietf.org"><span =
style=3D'color:windowtext;text-decoration:none'>bounces@ietf.org</span></=
a>] On Behalf Of The IESG<o:p></o:p></p><p class=3DMsoPlainText>&gt; =
Sent: 22 February 2012 15:13<o:p></o:p></p><p class=3DMsoPlainText>&gt; =
To: IETF-Announce<o:p></o:p></p><p class=3DMsoPlainText>&gt; Subject: =
Last Call: =
&lt;draft-betts-itu-oam-ach-code-point-03.txt&gt;<o:p></o:p></p><p =
class=3DMsoPlainText>(Allocation of<o:p></o:p></p><p =
class=3DMsoPlainText>an<o:p></o:p></p><p class=3DMsoPlainText>&gt; =
Associated Channel Code Point for Use by ITU-T Ethernet based OAM) =
to<o:p></o:p></p><p class=3DMsoPlainText>&gt; Informational =
RFC<o:p></o:p></p><p class=3DMsoPlainText>&gt; <o:p></o:p></p><p =
class=3DMsoPlainText>&gt; <o:p></o:p></p><p class=3DMsoPlainText>&gt; =
The IESG has received a request from an individual submitter =
to<o:p></o:p></p><p class=3DMsoPlainText>consider<o:p></o:p></p><p =
class=3DMsoPlainText>&gt; the following document:<o:p></o:p></p><p =
class=3DMsoPlainText>&gt; - 'Allocation of an Associated Channel Code =
Point for Use by ITU-T<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&nbsp;&nbsp;&nbsp; Ethernet based =
OAM'<o:p></o:p></p><p class=3DMsoPlainText>&gt;&nbsp;&nbsp; =
&lt;draft-betts-itu-oam-ach-code-point-03.txt&gt; as an Informational =
RFC<o:p></o:p></p><p class=3DMsoPlainText>&gt; <o:p></o:p></p><p =
class=3DMsoPlainText>&gt; The IESG plans to make a decision in the next =
few weeks, and solicits<o:p></o:p></p><p class=3DMsoPlainText>&gt; final =
comments on this action. Please send substantive comments to =
the<o:p></o:p></p><p class=3DMsoPlainText>&gt; <a =
href=3D"mailto:ietf@ietf.org"><span =
style=3D'color:windowtext;text-decoration:none'>ietf@ietf.org</span></a> =
mailing lists by 2012-03-21. Exceptionally, comments =
may<o:p></o:p></p><p class=3DMsoPlainText>be<o:p></o:p></p><p =
class=3DMsoPlainText>&gt; sent to <a href=3D"mailto:iesg@ietf.org"><span =
style=3D'color:windowtext;text-decoration:none'>iesg@ietf.org</span></a> =
instead. In either case, please retain the<o:p></o:p></p><p =
class=3DMsoPlainText>&gt; beginning of the Subject line to allow =
automated sorting.<o:p></o:p></p><p class=3DMsoPlainText>&gt; =
<o:p></o:p></p><p class=3DMsoPlainText>&gt; Abstract<o:p></o:p></p><p =
class=3DMsoPlainText>&gt; <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&nbsp;&nbsp;&nbsp; This document assigns an =
Associated Channel Type code point for<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&nbsp;&nbsp;&nbsp; carrying Ethernet based =
Operations, Administration, and Management<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&nbsp;&nbsp;&nbsp; messages in the MPLS Generic =
Associated Channel (G-ACh).<o:p></o:p></p><p class=3DMsoPlainText>&gt; =
<o:p></o:p></p><p class=3DMsoPlainText>&gt; The file can be obtained =
via<o:p></o:p></p><p class=3DMsoPlainText>&gt; <a =
href=3D"http://datatracker.ietf.org/doc/draft-betts-itu-oam-ach-code-poin=
t/"><span =
style=3D'color:windowtext;text-decoration:none'>http://datatracker.ietf.o=
rg/doc/draft-betts-itu-oam-ach-code-point/</span></a><o:p></o:p></p><p =
class=3DMsoPlainText>&gt; <o:p></o:p></p><p class=3DMsoPlainText>&gt; =
IESG discussion can be tracked via<o:p></o:p></p><p =
class=3DMsoPlainText>&gt; <a =
href=3D"http://datatracker.ietf.org/doc/draft-betts-itu-oam-ach-code-poin=
t/"><span =
style=3D'color:windowtext;text-decoration:none'>http://datatracker.ietf.o=
rg/doc/draft-betts-itu-oam-ach-code-point/</span></a><o:p></o:p></p><p =
class=3DMsoPlainText>&gt; <o:p></o:p></p><p class=3DMsoPlainText>&gt; =
<o:p></o:p></p><p class=3DMsoPlainText>&gt; No IPR declarations have =
been submitted directly on this I-D.<o:p></o:p></p><p =
class=3DMsoPlainText>&gt; =
_______________________________________________<o:p></o:p></p><p =
class=3DMsoPlainText>&gt; IETF-Announce mailing list<o:p></o:p></p><p =
class=3DMsoPlainText>&gt; <a =
href=3D"mailto:IETF-Announce@ietf.org"><span =
style=3D'color:windowtext;text-decoration:none'>IETF-Announce@ietf.org</s=
pan></a><o:p></o:p></p><p class=3DMsoPlainText>&gt; <a =
href=3D"https://www.ietf.org/mailman/listinfo/ietf-announce"><span =
style=3D'color:windowtext;text-decoration:none'>https://www.ietf.org/mail=
man/listinfo/ietf-announce</span></a><o:p></o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>_______________________________________________<o:p>=
</o:p></p><p class=3DMsoPlainText>mpls mailing list<o:p></o:p></p><p =
class=3DMsoPlainText><a href=3D"mailto:mpls@ietf.org"><span =
style=3D'color:windowtext;text-decoration:none'>mpls@ietf.org</span></a><=
o:p></o:p></p><p class=3DMsoPlainText><a =
href=3D"https://www.ietf.org/mailman/listinfo/mpls"><span =
style=3D'color:windowtext;text-decoration:none'>https://www.ietf.org/mail=
man/listinfo/mpls</span></a><o:p></o:p></p><p =
class=3DMsoPlainText>_______________________________________________<o:p>=
</o:p></p><p class=3DMsoPlainText>Ietf mailing list<o:p></o:p></p><p =
class=3DMsoPlainText><a href=3D"mailto:Ietf@ietf.org"><span =
style=3D'color:windowtext;text-decoration:none'>Ietf@ietf.org</span></a><=
o:p></o:p></p><p class=3DMsoPlainText><a =
href=3D"https://www.ietf.org/mailman/listinfo/ietf"><span =
style=3D'color:windowtext;text-decoration:none'>https://www.ietf.org/mail=
man/listinfo/ietf</span></a><o:p></o:p></p><p =
class=3DMsoPlainText>_______________________________________________<o:p>=
</o:p></p><p class=3DMsoPlainText>Ietf mailing list<o:p></o:p></p><p =
class=3DMsoPlainText><a href=3D"mailto:Ietf@ietf.org"><span =
style=3D'color:windowtext;text-decoration:none'>Ietf@ietf.org</span></a><=
o:p></o:p></p><p class=3DMsoPlainText><a =
href=3D"https://www.ietf.org/mailman/listinfo/ietf"><span =
style=3D'color:windowtext;text-decoration:none'>https://www.ietf.org/mail=
man/listinfo/ietf</span></a><o:p></o:p></p></div></body></html>
------_=_NextPart_001_01CCF7BE.D98DEA4C--

From housley@vigilsec.com  Thu Mar  1 08:06:11 2012
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8792321E80B1 for <ietf@ietfa.amsl.com>; Thu,  1 Mar 2012 08:06:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.551
X-Spam-Level: 
X-Spam-Status: No, score=-102.551 tagged_above=-999 required=5 tests=[AWL=0.048, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DL-UycSZua7i for <ietf@ietfa.amsl.com>; Thu,  1 Mar 2012 08:06:05 -0800 (PST)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id 8E88521E805B for <ietf@ietf.org>; Thu,  1 Mar 2012 08:06:03 -0800 (PST)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 99B5B9A472B; Thu,  1 Mar 2012 11:06:24 -0500 (EST)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([208.254.26.82]) by localhost (ronin.smetech.net [208.254.26.81]) (amavisd-new, port 10024) with ESMTP id LUnVb3cVfhUs; Thu,  1 Mar 2012 11:05:30 -0500 (EST)
Received: from [192.168.2.104] (pool-96-241-165-215.washdc.fios.verizon.net [96.241.165.215]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 029FE9A471B; Thu,  1 Mar 2012 11:06:22 -0500 (EST)
Subject: Re: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt> (Allocation of an Associated Channel Code Point for Use by ITU-T Ethernet based OAM) to Informational RFC
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/signed; boundary=Apple-Mail-10-123442766; protocol="application/pkcs7-signature"; micalg=sha1
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <515703B08A3A064C9CC8C09ACCC710DC0631679E@XMB-RCD-103.cisco.com>
Date: Thu, 1 Mar 2012 11:06:00 -0500
Message-Id: <C71DA9B1-A61F-4C5D-8DCE-3702271CBB6D@vigilsec.com>
References: <20120222151252.32262.82157.idtracker@ietfa.amsl.com> <03a301ccf174$ff953290$febf97b0$@olddog.co.uk> <515703B08A3A064C9CC8C09ACCC710DC0631679E@XMB-RCD-103.cisco.com>
To: Kyung-Yeop Hong (hongk) <hongk@cisco.com>
X-Mailer: Apple Mail (2.1084)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Mar 2012 16:06:11 -0000

--Apple-Mail-10-123442766
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

KY:

Would you support the assignment to an approved G.8113.1?  That is, if =
the document contained a normative reference to the approved G.8113.1, =
then the document that makes the code point allocations would sit in the =
RFC Editor queue until the ITU-T reaches consensus and approves =
G.8113.1.

Russ


On Mar 1, 2012, at 10:14 AM, Kyung-Yeop Hong (hongk) wrote:

> No/do not support.
>=20
> One of the issues with G.8113.1 in LS370 is its stability and =
maturity.
> That was one of the reasons why it was not approved.=20
>=20
> The Ethernet based OAM protocol documented in the LS370 version is
> intended to be deployed for MPLS networks. I think the IETF has a duty
> to ensure that a solution is stable and works for MPLS networks before
> the code point allocation. A number of concerns with the deployment of
> this proposed protocol raised in
> draft-spercher-mpls-tp-oam-considerations are critical to the Internet
> and must be taken into consideration in this Last Call.=20
>=20
> KY
>=20
>=20
>> -----Original Message-----
>> From: ietf-announce-bounces@ietf.org [mailto:ietf-announce-
>> bounces@ietf.org] On Behalf Of The IESG
>> Sent: 22 February 2012 15:13
>> To: IETF-Announce
>> Subject: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt>
> (Allocation of
> an
>> Associated Channel Code Point for Use by ITU-T Ethernet based OAM) to
>> Informational RFC
>>=20
>>=20
>> The IESG has received a request from an individual submitter to
> consider
>> the following document:
>> - 'Allocation of an Associated Channel Code Point for Use by ITU-T
>>   Ethernet based OAM'
>>  <draft-betts-itu-oam-ach-code-point-03.txt> as an Informational RFC
>>=20
>> The IESG plans to make a decision in the next few weeks, and solicits
>> final comments on this action. Please send substantive comments to =
the
>> ietf@ietf.org mailing lists by 2012-03-21. Exceptionally, comments =
may
> be
>> sent to iesg@ietf.org instead. In either case, please retain the
>> beginning of the Subject line to allow automated sorting.
>>=20
>> Abstract
>>=20
>>   This document assigns an Associated Channel Type code point for
>>   carrying Ethernet based Operations, Administration, and Management
>>   messages in the MPLS Generic Associated Channel (G-ACh).
>>=20
>> The file can be obtained via
>> http://datatracker.ietf.org/doc/draft-betts-itu-oam-ach-code-point/
>>=20
>> IESG discussion can be tracked via
>> http://datatracker.ietf.org/doc/draft-betts-itu-oam-ach-code-point/
>>=20
>>=20
>> No IPR declarations have been submitted directly on this I-D.
>> _______________________________________________
>> IETF-Announce mailing list
>> IETF-Announce@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf-announce
>=20
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


--Apple-Mail-10-123442766
Content-Disposition: attachment;
	filename=smime.p7s
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIKqTCCBSow
ggQSoAMCAQICEQCWQVO8Se/ELTDvfzPfbE7PMA0GCSqGSIb3DQEBBQUAMIGTMQswCQYDVQQGEwJH
QjEbMBkGA1UECBMSR3JlYXRlciBNYW5jaGVzdGVyMRAwDgYDVQQHEwdTYWxmb3JkMRowGAYDVQQK
ExFDT01PRE8gQ0EgTGltaXRlZDE5MDcGA1UEAxMwQ09NT0RPIENsaWVudCBBdXRoZW50aWNhdGlv
biBhbmQgU2VjdXJlIEVtYWlsIENBMB4XDTEyMDMwMTAwMDAwMFoXDTEzMDMwMTIzNTk1OVowJTEj
MCEGCSqGSIb3DQEJARYUaG91c2xleUB2aWdpbHNlYy5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IB
DwAwggEKAoIBAQDf+ZqfVh9j1/uT+utUViLKlpZAA9aLSKUcj8NOg8eiofsmSrgv9WhqLZqd3zgW
UXlCMv8X25RJ1JvAP8ZuRMs5nYhalLhSIBt4fnyYQ3XSdD21V/cfXb6OYngaVbFz2QR/3/kNXwBh
PttzTQm2Caen/xtcyqiguNmVHCx1jh0mjq0XwYCBc6xg8c/GM26t9RGaZG0zB0kdfAj61sussqYQ
080u9WjL9/oguapIjDQ4aO6LY+m0qL+2Vavk44wFPeDtFHA9hujoPcc63E0l/U5PRYpGAmHp1UEC
1jBU7uYd/iewV2EDEkDX55WLIpGZfoBF+uKx1VoPmEZltPqljg8hAgMBAAGjggHkMIIB4DAfBgNV
HSMEGDAWgBR6E04AdFvGeGNkJ8Ev4qBbvHnFezAdBgNVHQ4EFgQU9jGbv3XM7fKm9udp1jtSoF5Y
4HQwDgYDVR0PAQH/BAQDAgWgMAwGA1UdEwEB/wQCMAAwIAYDVR0lBBkwFwYIKwYBBQUHAwQGCysG
AQQBsjEBAwUCMBEGCWCGSAGG+EIBAQQEAwIFIDBGBgNVHSAEPzA9MDsGDCsGAQQBsjEBAgEBATAr
MCkGCCsGAQUFBwIBFh1odHRwczovL3NlY3VyZS5jb21vZG8ubmV0L0NQUzBXBgNVHR8EUDBOMEyg
SqBIhkZodHRwOi8vY3JsLmNvbW9kb2NhLmNvbS9DT01PRE9DbGllbnRBdXRoZW50aWNhdGlvbmFu
ZFNlY3VyZUVtYWlsQ0EuY3JsMIGIBggrBgEFBQcBAQR8MHowUgYIKwYBBQUHMAKGRmh0dHA6Ly9j
cnQuY29tb2RvY2EuY29tL0NPTU9ET0NsaWVudEF1dGhlbnRpY2F0aW9uYW5kU2VjdXJlRW1haWxD
QS5jcnQwJAYIKwYBBQUHMAGGGGh0dHA6Ly9vY3NwLmNvbW9kb2NhLmNvbTAfBgNVHREEGDAWgRRo
b3VzbGV5QHZpZ2lsc2VjLmNvbTANBgkqhkiG9w0BAQUFAAOCAQEAgSXPb1o6jO+b+6FUddXr55XJ
wQ2QdnXMq9vZjvrMT9QsWT9w9M24/qKcQAIy7DKoPbWYdks6XwSAG3lYfxUyCEDcq8nIbegFO9Ov
B7KlNg/3W0JkpUeBNqFywnXtQh4WR/dCXfoxxiKgvR2BGyMXrkfSfb5NU3wUZC0bHeMczwzFReMF
QjaY08y2V1rReTVxL4wSag9cMUtOzSLVbBWhiNAOxLiA7yu3EqfpsW935htmCXVLk2JQj4mbGEPm
wx2JJRIKjfZKfdAnaI/TVbO2tUgc60Fgx+C+der2gFaqvC1pKRSM/mOqP7KFfSMoCnoV8EpxcUK6
JcjZfvD5SQJJlDCCBXcwggRfoAMCAQICEQC/HkHRL9TErrj9ADkdlht/MA0GCSqGSIb3DQEBBQUA
MIGuMQswCQYDVQQGEwJVUzELMAkGA1UECBMCVVQxFzAVBgNVBAcTDlNhbHQgTGFrZSBDaXR5MR4w
HAYDVQQKExVUaGUgVVNFUlRSVVNUIE5ldHdvcmsxITAfBgNVBAsTGGh0dHA6Ly93d3cudXNlcnRy
dXN0LmNvbTE2MDQGA1UEAxMtVVROLVVTRVJGaXJzdC1DbGllbnQgQXV0aGVudGljYXRpb24gYW5k
IEVtYWlsMB4XDTExMDIyMzAwMDAwMFoXDTEyMDIyMzIzNTk1OVowJTEjMCEGCSqGSIb3DQEJARYU
aG91c2xleUB2aWdpbHNlYy5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCw0MgZ
J40HVA6CN9jGwA0pudBn0OQT8816EBgpVzV5X3DTnf8roF3vTPNTfZyuyuaDcZADMhmuZ7blVxN2
lVlaHmY+WTJZkcvkFwGUFX2X8lAyBc4I1+J7oSpupF2X8nHW6W7/QvYHD6lxMNssB0/ma/z+5QuE
+ypnCEJdbeDbGcipdjXlwXCBYbIRTQmEzec5VuPZAxVtpMehL+dNyG2xc5q9viXm0eYKdlLmegcF
pPTa0CwWUpnMhXjAUUl41k4GJnyX4INEL7JJnCkhHPJYKbOsoMwtV4/8D8nIJSz7R4VcRQo0Sq+0
ENMrwLZai7LIBflq691QfONyCvWvjg3fAgMBAAGjggIWMIICEjAfBgNVHSMEGDAWgBSJgmd9xJ0m
cABLtFBIfN49rgRufTAdBgNVHQ4EFgQUaZfWeIVDGMaHXO9NcMRXavC7TLIwDgYDVR0PAQH/BAQD
AgWgMAwGA1UdEwEB/wQCMAAwIAYDVR0lBBkwFwYIKwYBBQUHAwQGCysGAQQBsjEBAwUCMBEGCWCG
SAGG+EIBAQQEAwIFIDBGBgNVHSAEPzA9MDsGDCsGAQQBsjEBAgEBATArMCkGCCsGAQUFBwIBFh1o
dHRwczovL3NlY3VyZS5jb21vZG8ubmV0L0NQUzCBpQYDVR0fBIGdMIGaMEygSqBIhkZodHRwOi8v
Y3JsLmNvbW9kb2NhLmNvbS9VVE4tVVNFUkZpcnN0LUNsaWVudEF1dGhlbnRpY2F0aW9uYW5kRW1h
aWwuY3JsMEqgSKBGhkRodHRwOi8vY3JsLmNvbW9kby5uZXQvVVROLVVTRVJGaXJzdC1DbGllbnRB
dXRoZW50aWNhdGlvbmFuZEVtYWlsLmNybDBsBggrBgEFBQcBAQRgMF4wNgYIKwYBBQUHMAKGKmh0
dHA6Ly9jcnQuY29tb2RvY2EuY29tL1VUTkFBQUNsaWVudENBLmNydDAkBggrBgEFBQcwAYYYaHR0
cDovL29jc3AuY29tb2RvY2EuY29tMB8GA1UdEQQYMBaBFGhvdXNsZXlAdmlnaWxzZWMuY29tMA0G
CSqGSIb3DQEBBQUAA4IBAQAakko5qXz1U0VWMkiuo+bNCY3QEsM55vIqJujM+c3romvLuBVnDk+Z
Q/MjyCrrJ8acR3bFCQGnr+9+rV/cxLcZCxFUDuUhucaSxlu82N3/75fi1JFe/ZByJJW80U/oY6xn
mNUX8S5tQ/+tmr/JpysOh68BU/qKagXUvDlMVHwSrumBzbG84+/SBMYx4ZB4KgtiL0EaqzKiqLMt
jQrGLeSe02A0OoIwRoeYCzGojMjPHjv9GfvBGNUDXDhB+GiiDK+zT9O65KulkuDHB9A14nYQtXih
caAE9bXRPBjDy1zEZ7kfXolnnBjx/eokmW7aXnfL/h+a3pLwvu2Hf7xqbTmBMYIDyTCCA8UCAQEw
gcQwga4xCzAJBgNVBAYTAlVTMQswCQYDVQQIEwJVVDEXMBUGA1UEBxMOU2FsdCBMYWtlIENpdHkx
HjAcBgNVBAoTFVRoZSBVU0VSVFJVU1QgTmV0d29yazEhMB8GA1UECxMYaHR0cDovL3d3dy51c2Vy
dHJ1c3QuY29tMTYwNAYDVQQDEy1VVE4tVVNFUkZpcnN0LUNsaWVudCBBdXRoZW50aWNhdGlvbiBh
bmQgRW1haWwCEQC/HkHRL9TErrj9ADkdlht/MAkGBSsOAwIaBQCgggHZMBgGCSqGSIb3DQEJAzEL
BgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTEyMDMwMTE2MDYwMVowIwYJKoZIhvcNAQkEMRYE
FGsDRnf8knJjF6kNxhccYwuW8L/gMIG6BgkrBgEEAYI3EAQxgawwgakwgZMxCzAJBgNVBAYTAkdC
MRswGQYDVQQIExJHcmVhdGVyIE1hbmNoZXN0ZXIxEDAOBgNVBAcTB1NhbGZvcmQxGjAYBgNVBAoT
EUNPTU9ETyBDQSBMaW1pdGVkMTkwNwYDVQQDEzBDT01PRE8gQ2xpZW50IEF1dGhlbnRpY2F0aW9u
IGFuZCBTZWN1cmUgRW1haWwgQ0ECEQCWQVO8Se/ELTDvfzPfbE7PMIG8BgsqhkiG9w0BCRACCzGB
rKCBqTCBkzELMAkGA1UEBhMCR0IxGzAZBgNVBAgTEkdyZWF0ZXIgTWFuY2hlc3RlcjEQMA4GA1UE
BxMHU2FsZm9yZDEaMBgGA1UEChMRQ09NT0RPIENBIExpbWl0ZWQxOTA3BgNVBAMTMENPTU9ETyBD
bGllbnQgQXV0aGVudGljYXRpb24gYW5kIFNlY3VyZSBFbWFpbCBDQQIRAJZBU7xJ78QtMO9/M99s
Ts8wDQYJKoZIhvcNAQEBBQAEggEAb+B2kdwxFNt+nJ5bOkQ9GFh4+z7YsX//sAVx8sMwU45REFR2
KC+NB9AB5pDyzAafOBflMi44ekOo/H4phNamjURFH9yNsHJVkN79iupTwutjUoXHwR8ZG3VafQYO
dfz1yIN1vKR9y5aW6ZDNQfozdKyz48abK0ZiItfd1rVg+1LoqYqJFJ5XN3z1nwE/yaQrg2eM8UEL
Kqjq3QSGHsiqHpjtRA7xctiQiD0DPNGbB256Qk1hgZzDK1PCUi+srzD8PgrG8n3li8STlUW/9q7G
9sdYVZZDMg4xl4lfjZslBb5bk0xOVfV3Id07Z7/flOdu/j06Nk5Ys12ZF/gMy6UPswAAAAAAAA==

--Apple-Mail-10-123442766--

From sm@resistor.net  Thu Mar  1 08:14:09 2012
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E4E9621E8220 for <ietf@ietfa.amsl.com>; Thu,  1 Mar 2012 08:14:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.648
X-Spam-Level: 
X-Spam-Status: No, score=-102.648 tagged_above=-999 required=5 tests=[AWL=-0.049, 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 aHCS5QKSiTcO for <ietf@ietfa.amsl.com>; Thu,  1 Mar 2012 08:14:08 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id BB12721E8172 for <ietf@ietf.org>; Thu,  1 Mar 2012 08:14:08 -0800 (PST)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id q21GE3Fr001158 for <ietf@ietf.org>; Thu, 1 Mar 2012 08:14:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1330618448; i=@resistor.net; bh=hsUwcp9uitosgd52Px66i+obPASyNyaTsZGDct9b3fM=; h=Message-Id:Date:To:From:Subject:In-Reply-To:References: Mime-Version:Content-Type:Cc; b=peozGkr/lDufA2OKmIY+eKI7StmqFVFWeyCorewOYO+VRZSnWZYLaiWPmCA49DIDB qgTVgER/p4cp3Ya2pq+l7jnKRr1b7S9iQSfbzElmXrK7CzxvVRa1psqHjFHIAVp69W VNr50LTgNcYIaiA/AK1LBCdssasa/syfU0ZpytFk=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1330618448; i=@resistor.net; bh=hsUwcp9uitosgd52Px66i+obPASyNyaTsZGDct9b3fM=; h=Message-Id:Date:To:From:Subject:In-Reply-To:References: Mime-Version:Content-Type:Cc; b=u+oRFDmYdfIQJDhUYVvcjKFX1FwAkvVgNBShdtOxch2o4dINE+RdCJiwTscYCxMUO sP7+Y0QuBulkbzEQU9jYIg+qyqbrTe2z0SYf9rhQFD5LcBjC9bh+KUtRbbvOCgv23J a4NL8c8ork5Sxu3Wzew1+bPqE9TtrVboM9M+u47I=
Message-Id: <6.2.5.6.2.20120301064114.0a80f078@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 01 Mar 2012 07:53:48 -0800
To: ietf@ietf.org
From: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-ietf-marf-spf-reporting-08.txt> (SPF Authentication Failure Reporting using the Abuse Report Format) to Proposed Standard
In-Reply-To: <CAC4RtVDUmcLZh4J2SvV32kNxaQcPYr1+9S9q59Kd50F4hqWaOQ@mail.g mail.com>
References: <20120301004643.17274.83943.idtracker@ietfa.amsl.com> <6.2.5.6.2.20120229181328.0a95a9f8@resistor.net> <CAC4RtVDUmcLZh4J2SvV32kNxaQcPYr1+9S9q59Kd50F4hqWaOQ@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Mar 2012 16:14:10 -0000

At 06:09 01-03-2012, Barry Leiba wrote:
>Keep in mind that the charter has these two items:

Ok.

>2. SPF is widely deployed in the real world.  Information about

Is a protocol considered by the IETF to be widely deployed based on 
deployment of implementations?  For example, an IPv6 survey ( 
http://dns.measurement-factory.com/surveys/2011/IPv6/ ) used a a 
DNS-centric perspective to measure some basic statistics on IPv6 
deployment.  Are such statistics acceptable to the IETF to determine 
wide deployment of RFC 2460?

Quoting a report from 2010 about DNSSEC:

   "2010 has been a significant year for DNSSEC. On July 15th, the root zone
    was signed, removing one of the most significant barriers to broad DNSSEC
    deployment. However other obstacles remain:

    - The .com and .net zones are not yet signed.
    - Few registrars support DNSSEC.
    - Few resolvers have DNSSEC validation enabled.
    - The tools for managing signed zones are basic and typically entail a
      steep learning curve.

  Consequently DNSSEC deployment is still extremely limited."

The above mentions some of the factors that affects DNSSEC 
deployment.  If DNSSEC records are published in DNS but few resolvers 
have DNSSEC validation enabled, does that constitute wide deployment?

According to BCP 97:

   "In the IETF, it is a basic assumption that implementors must have a
    clear understanding of what they need to implement in order to be
    fully compliant with a standard and to be able to interoperate with
    other implementations of that standard".

Is the interoperability assessment based on implementations of a 
specification or are other ways to determine interoperability 
acceptable to the IETF?

At 06:22 01-03-2012, Scott Kitterman wrote:
>IESG.  It includes SPF specifics (although it doesn't require a normative
>reference to RFC 4408, so there's no downref issue with it), so I think that
>in the context of authentication failure reporting this is already 
>established
>to be in scope.  All the current draft does is provide an optional mechanism

In the Last Call message issued by the IESG, it is mentioned that:

   "Note that this document has a downward normative reference: This document
    makes a normative reference to SPF (RFC4408), which is Experimental."

Is the downward normative reference in the draft incorrect?

Regards,
-sm 


From adrien@qbik.com  Wed Feb 29 12:10:03 2012
Return-Path: <adrien@qbik.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 653E821E805C; Wed, 29 Feb 2012 12:10:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.48
X-Spam-Level: 
X-Spam-Status: No, score=-3.48 tagged_above=-999 required=5 tests=[AWL=-1.181,  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 u62c4JRTBUwq; Wed, 29 Feb 2012 12:10:02 -0800 (PST)
Received: from smtp.qbik.com (smtp.qbik.com [210.55.214.35]) by ietfa.amsl.com (Postfix) with ESMTP id 883A821E8032; Wed, 29 Feb 2012 12:10:00 -0800 (PST)
Received: From [192.168.1.10] (unverified [125.237.241.8]) by SMTP Server [210.55.214.35] (WinGate SMTP Receiver v7.1.0 (Build 3388)) with SMTP id <0018891738@smtp.qbik.com>; Thu, 01 Mar 2012 09:09:56 +1300
Message-ID: <4F4E8614.90901@qbik.com>
Date: Thu, 01 Mar 2012 09:09:56 +1300
From: Adrien de Croy <adrien@qbik.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:11.0) Gecko/20120216 Thunderbird/11.0
MIME-Version: 1.0
To: =?UTF-8?B?SGVucmlrIE5vcmRzdHLDtm0=?= <henrik@henriknordstrom.net>
Subject: Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
References: <20120221181006.43AB121F87BF@ietfa.amsl.com> <4F43E1D3.4070201@cs.tcd.ie> <4F43E364.4040706@gmx.de> <4F43E458.6030705@cs.tcd.ie> <4F43E75C.2010309@gmx.de> <1330543172.24673.7.camel@home.hno.se>
In-Reply-To: <1330543172.24673.7.camel@home.hno.se>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Mailman-Approved-At: Thu, 01 Mar 2012 08:18:30 -0800
Cc: IETF-Discussion <ietf@ietf.org>, Julian Reschke <julian.reschke@gmx.de>, mnot@mnot.net, iesg@ietf.org, ietf-http-wg@w3.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Feb 2012 20:10:03 -0000

There is one other thing I would add to auth:

Ability for a challenger to identify itself, and for a response to 
target a challenger.

Currently with chained proxies, it's not possible to reliably pass 
challenges and creds back to the client.  A proxy looking at a request 
would need to maintain state to know if it challenged the client or not.

Adding a parameter to the challenge and response which identifies the 
challenger would allow for this.

In fact it would then allow proxy and server auth to use the same 
mechanism and headers.

Adrien



On 1/03/2012 8:19 a.m., Henrik Nordström wrote:
> tis 2012-02-21 klockan 19:50 +0100 skrev Julian Reschke:
>> Well, we have an existing authentication framework. It would be
>> interesting to find out what's missing from it.
> My take is better secure authentication schemes (not plaintext password
> based) which is cleanly specified to a level that implementations
> actually interop properly, and the ability for site owners (and proxies)
> to influence how the login process is presented to users in a safe
> manner that do not collide with preceived https security or makes a mess
> for matchine<->machine communication not involving humans.
>
> The existing HTTP auth framework works in general very well for
> machine<->machine.
>
> This said I have used HTTP Digest authentication quite successfully (but
> with a number of interop workarounds) with non-tech users using the
> default login box, only providing a good error response message seen if
> the user cacels of fails the login.
>
> Regards
> Henrik
>
>

-- 
Adrien de Croy - WinGate Proxy Server - http://www.wingate.com


From henrik@henriknordstrom.net  Wed Feb 29 11:19:42 2012
Return-Path: <henrik@henriknordstrom.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D286D21F85C4; Wed, 29 Feb 2012 11:19:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[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 qu9CkSNjAtdk; Wed, 29 Feb 2012 11:19:42 -0800 (PST)
Received: from vps1.henriknordstrom.net (vps1.henriknordstrom.net [IPv6:2a02:750:7::d0a]) by ietfa.amsl.com (Postfix) with ESMTP id 2ABF421F85BE; Wed, 29 Feb 2012 11:19:41 -0800 (PST)
Received: from home.hno.se (home.hno.se [IPv6:2001:470:df90::1]) (authenticated bits=128) by vps1.henriknordstrom.net (8.14.2/8.14.2/Debian-2build1) with ESMTP id q1TJJYUW022139; Wed, 29 Feb 2012 19:19:35 GMT
Received: from [127.0.0.1] (localhost.localdomain [127.0.0.1]) by home.hno.se (8.14.5/8.14.5) with ESMTP id q1TJJWsm026387; Wed, 29 Feb 2012 20:19:32 +0100
Message-ID: <1330543172.24673.7.camel@home.hno.se>
Subject: Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
From: Henrik =?ISO-8859-1?Q?Nordstr=F6m?= <henrik@henriknordstrom.net>
To: Julian Reschke <julian.reschke@gmx.de>
Date: Wed, 29 Feb 2012 20:19:32 +0100
In-Reply-To: <4F43E75C.2010309@gmx.de>
References: <20120221181006.43AB121F87BF@ietfa.amsl.com> <4F43E1D3.4070201@cs.tcd.ie> <4F43E364.4040706@gmx.de> <4F43E458.6030705@cs.tcd.ie> <4F43E75C.2010309@gmx.de>
Content-Type: text/plain; charset="UTF-8"
X-Mailer: Evolution 3.2.3 (3.2.3-1.fc16) 
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0
X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-3.0 (vps1.henriknordstrom.net [IPv6:2a02:750:7::d0a]); Wed, 29 Feb 2012 19:19:36 +0000 (UTC)
X-Mailman-Approved-At: Thu, 01 Mar 2012 08:18:30 -0800
Cc: mnot@mnot.net, IETF-Discussion <ietf@ietf.org>, iesg@ietf.org, ietf-http-wg@w3.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Feb 2012 22:34:50 -0000

tis 2012-02-21 klockan 19:50 +0100 skrev Julian Reschke:
> Well, we have an existing authentication framework. It would be 
> interesting to find out what's missing from it.

My take is better secure authentication schemes (not plaintext password
based) which is cleanly specified to a level that implementations
actually interop properly, and the ability for site owners (and proxies)
to influence how the login process is presented to users in a safe
manner that do not collide with preceived https security or makes a mess
for matchine<->machine communication not involving humans.

The existing HTTP auth framework works in general very well for
machine<->machine. 

This said I have used HTTP Digest authentication quite successfully (but
with a number of interop workarounds) with non-tech users using the
default login box, only providing a good error response message seen if
the user cacels of fails the login.

Regards
Henrik


From henrik@henriknordstrom.net  Wed Feb 29 11:55:35 2012
Return-Path: <henrik@henriknordstrom.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E485B21F879E; Wed, 29 Feb 2012 11:55:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[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 B6q+0HSQLoaS; Wed, 29 Feb 2012 11:55:35 -0800 (PST)
Received: from vps1.henriknordstrom.net (vps1.henriknordstrom.net [IPv6:2a02:750:7::d0a]) by ietfa.amsl.com (Postfix) with ESMTP id 2B39321F8783; Wed, 29 Feb 2012 11:55:35 -0800 (PST)
Received: from home.hno.se (home.hno.se [IPv6:2001:470:df90::1]) (authenticated bits=128) by vps1.henriknordstrom.net (8.14.2/8.14.2/Debian-2build1) with ESMTP id q1TJtRQw019815; Wed, 29 Feb 2012 19:55:28 GMT
Received: from [127.0.0.1] (localhost.localdomain [127.0.0.1]) by home.hno.se (8.14.5/8.14.5) with ESMTP id q1TJtOvl028932; Wed, 29 Feb 2012 20:55:24 +0100
Message-ID: <1330545324.24673.22.camel@home.hno.se>
Subject: Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
From: Henrik =?ISO-8859-1?Q?Nordstr=F6m?= <henrik@henriknordstrom.net>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Date: Wed, 29 Feb 2012 20:55:24 +0100
In-Reply-To: <4F48EC87.4040302@cs.tcd.ie>
References: <CB6A507F.13D92%ietfdbh@comcast.net> <DDD5CAD5-AB39-4DEE-BD4B-46AB4138AF05@vpnc.org> <4F452842.3050905@stpeter.im> <F4187EC0-40EA-4DAA-B232-D28C7A43288B@gbiv.com> <CAHBU6ivfNaAXsh-x5kqzUnzRfoPpr00COHz3oi2tWRcxgPZfxQ@mail.gmail.com> <C761AFCD-BCD7-45EE-9D89-FB568ABEE53A@gbiv.com> <4F478872.8020103@cs.tcd.ie> <8B377788-1995-4F38-88A8-E33C2FBFD2E5@mnot.net> <4F48E62C.5020902@cs.tcd.ie> <4F48EA4B.6050500@gmx.de> <4F48EC87.4040302@cs.tcd.ie>
Content-Type: text/plain; charset="UTF-8"
X-Mailer: Evolution 3.2.3 (3.2.3-1.fc16) 
Content-Transfer-Encoding: 8bit
Mime-Version: 1.0
X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-3.0 (vps1.henriknordstrom.net [IPv6:2a02:750:7::d0a]); Wed, 29 Feb 2012 19:55:29 +0000 (UTC)
X-Mailman-Approved-At: Thu, 01 Mar 2012 08:18:30 -0800
Cc: IETF-Discussion <ietf@ietf.org>, Julian Reschke <julian.reschke@gmx.de>, "Roy T. Fielding" <fielding@gbiv.com>, Paul Hoffman <paul.hoffman@vpnc.org>, Mark Nottingham <mnot@mnot.net>, Tim Bray <tbray@textuality.com>, The IESG <iesg@ietf.org>, ietf-http-wg@w3.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Feb 2012 22:35:47 -0000

lör 2012-02-25 klockan 14:13 +0000 skrev Stephen Farrell:

> I don't agree with you there - the perceived low probability that
> something will be deployed is a real disincentive here. We have had
> people wanting to do work on this and have been told there's no point
> because it won't get adopted.

I do not agree that getting new auth schemes deployed if they do make
sense is such big problem in the longer scope.

We have already had two new auth schemes deployed within HTTP/1.1 during
the lifetime of HTTP/1.1 and which is in wide scale use today across
numerous different implementations. And these doesn't even followin HTTP
semantics...

A beauty of HTTP auth model here is that it can downgrade nicely,
allowing old clients to continue working only not gaining the benefits
of the new auth model. But that obviously have security implications as
well if newer user-agents can be fooled into downgrading.

Regards
Henrik


From henrik@henriknordstrom.net  Wed Feb 29 11:57:39 2012
Return-Path: <henrik@henriknordstrom.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6B6D821E802A; Wed, 29 Feb 2012 11:57:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[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 z02JtmmciKiu; Wed, 29 Feb 2012 11:57:39 -0800 (PST)
Received: from vps1.henriknordstrom.net (vps1.henriknordstrom.net [IPv6:2a02:750:7::d0a]) by ietfa.amsl.com (Postfix) with ESMTP id A520D21F87FF; Wed, 29 Feb 2012 11:57:38 -0800 (PST)
Received: from home.hno.se (home.hno.se [IPv6:2001:470:df90::1]) (authenticated bits=128) by vps1.henriknordstrom.net (8.14.2/8.14.2/Debian-2build1) with ESMTP id q1TJvXAS029844; Wed, 29 Feb 2012 19:57:34 GMT
Received: from [127.0.0.1] (localhost.localdomain [127.0.0.1]) by home.hno.se (8.14.5/8.14.5) with ESMTP id q1TJvVgM029142; Wed, 29 Feb 2012 20:57:31 +0100
Message-ID: <1330545451.24673.24.camel@home.hno.se>
Subject: Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
From: Henrik =?ISO-8859-1?Q?Nordstr=F6m?= <henrik@henriknordstrom.net>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Date: Wed, 29 Feb 2012 20:57:31 +0100
In-Reply-To: <4F491E02.9020207@cs.tcd.ie>
References: <CB6A507F.13D92%ietfdbh@comcast.net> <DDD5CAD5-AB39-4DEE-BD4B-46AB4138AF05@vpnc.org> <4F452842.3050905@stpeter.im> <F4187EC0-40EA-4DAA-B232-D28C7A43288B@gbiv.com> <CAHBU6ivfNaAXsh-x5kqzUnzRfoPpr00COHz3oi2tWRcxgPZfxQ@mail.gmail.com> <C761AFCD-BCD7-45EE-9D89-FB568ABEE53A@gbiv.com> <4F478872.8020103@cs.tcd.ie> <8B377788-1995-4F38-88A8-E33C2FBFD2E5@mnot.net> <4F48E62C.5020902@cs.tcd.ie> <4F48EA4B.6050500@gmx.de> <4F48EC87.4040302@cs.tcd.ie> <4F48EE34.3020504@gmx.de> <4F491E02.9020207@cs.tcd.ie>
Content-Type: text/plain; charset="UTF-8"
X-Mailer: Evolution 3.2.3 (3.2.3-1.fc16) 
Content-Transfer-Encoding: 8bit
Mime-Version: 1.0
X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-3.0 (vps1.henriknordstrom.net [IPv6:2a02:750:7::d0a]); Wed, 29 Feb 2012 19:57:34 +0000 (UTC)
X-Mailman-Approved-At: Thu, 01 Mar 2012 08:18:30 -0800
Cc: IETF-Discussion <ietf@ietf.org>, Julian Reschke <julian.reschke@gmx.de>, "Roy T. Fielding" <fielding@gbiv.com>, Paul Hoffman <paul.hoffman@vpnc.org>, Mark Nottingham <mnot@mnot.net>, Tim Bray <tbray@textuality.com>, The IESG <iesg@ietf.org>, ietf-http-wg@w3.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Feb 2012 22:36:07 -0000

lör 2012-02-25 klockan 17:44 +0000 skrev Stephen Farrell:

> I don't think fixing or changing the framework will give us better
> auth schemes by itself. (Better auth schemes may or may not require
> changes to the framework, I dunno.)

Obviously not. Fixing the framework giving better use of auth schemes
may triggering interest in finding a better auth scheme however.

Regards
Henrik


From henrik@henriknordstrom.net  Wed Feb 29 12:11:08 2012
Return-Path: <henrik@henriknordstrom.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 37B8521F85F9; Wed, 29 Feb 2012 12:11:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[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 mo68nGQ93WoC; Wed, 29 Feb 2012 12:11:07 -0800 (PST)
Received: from vps1.henriknordstrom.net (vps1.henriknordstrom.net [IPv6:2a02:750:7::d0a]) by ietfa.amsl.com (Postfix) with ESMTP id 733A421E8032; Wed, 29 Feb 2012 12:11:07 -0800 (PST)
Received: from home.hno.se (home.hno.se [IPv6:2001:470:df90::1]) (authenticated bits=128) by vps1.henriknordstrom.net (8.14.2/8.14.2/Debian-2build1) with ESMTP id q1TKB2l2005434; Wed, 29 Feb 2012 20:11:03 GMT
Received: from [127.0.0.1] (localhost.localdomain [127.0.0.1]) by home.hno.se (8.14.5/8.14.5) with ESMTP id q1TKB0pK030112; Wed, 29 Feb 2012 21:11:00 +0100
Message-ID: <1330546260.24673.37.camel@home.hno.se>
Subject: Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
From: Henrik =?ISO-8859-1?Q?Nordstr=F6m?= <henrik@henriknordstrom.net>
To: Julian Reschke <julian.reschke@gmx.de>
Date: Wed, 29 Feb 2012 21:11:00 +0100
In-Reply-To: <4F49271C.5030509@gmx.de>
References: <CB6A507F.13D92%ietfdbh@comcast.net> <DDD5CAD5-AB39-4DEE-BD4B-46AB4138AF05@vpnc.org> <4F452842.3050905@stpeter.im> <F4187EC0-40EA-4DAA-B232-D28C7A43288B@gbiv.com> <CAHBU6ivfNaAXsh-x5kqzUnzRfoPpr00COHz3oi2tWRcxgPZfxQ@mail.gmail.com> <C761AFCD-BCD7-45EE-9D89-FB568ABEE53A@gbiv.com> <4F478872.8020103@cs.tcd.ie> <8B377788-1995-4F38-88A8-E33C2FBFD2E5@mnot.net> <4F48E62C.5020902@cs.tcd.ie> <4F48EA4B.6050500@gmx.de> <4F48EC87.4040302@cs.tcd.ie> <4F48EE34.3020504@gmx.de> <4F491E02.9020207@cs.tcd.ie> <4F49271C.5030509@gmx.de>
Content-Type: text/plain; charset="UTF-8"
X-Mailer: Evolution 3.2.3 (3.2.3-1.fc16) 
Content-Transfer-Encoding: 8bit
Mime-Version: 1.0
X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-3.0 (vps1.henriknordstrom.net [IPv6:2a02:750:7::d0a]); Wed, 29 Feb 2012 20:11:03 +0000 (UTC)
X-Mailman-Approved-At: Thu, 01 Mar 2012 08:18:30 -0800
Cc: IETF-Discussion <ietf@ietf.org>, "Roy T. Fielding" <fielding@gbiv.com>, Paul Hoffman <paul.hoffman@vpnc.org>, Mark Nottingham <mnot@mnot.net>, Tim Bray <tbray@textuality.com>, The IESG <iesg@ietf.org>, ietf-http-wg@w3.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Feb 2012 22:37:01 -0000

lör 2012-02-25 klockan 19:23 +0100 skrev Julian Reschke:
> Well, I'm one of the editors of the authentication framework spec, so if 
> there's something wrong with it, I'd like to know.

Only the thing said earluer

- Define how servers may influence the visible appearance of the login
action

- Perhaps some way of triggering a logout.

> So if we collectively think that the framework probably is ok, and that 
> we *do* need a new authentication scheme, what's stopping us to start 
> that activity *right now*?

Nothing.

A cleaned up http digest with less fancy bells no one implements
correctly and stronger methods would do nicely at improving the raw
security side of things.

But at the same time it alone does solve the reasons why HTTP Digest is
not widely used today which is or any of the newer use cases with auth
delegation via trusted third parties.

A very interesting thought is to look into how for example Kerberos
could be implemented as a first class HTTP Auth citizen without
violating HTTP messaging semantics. Is there anything needed at the
framework side for making that work right?

Regards
Henrik


From loa@pi.nu  Thu Mar  1 08:42:59 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 4606D21E8266 for <ietf@ietfa.amsl.com>; Thu,  1 Mar 2012 08:42:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.583
X-Spam-Level: 
X-Spam-Status: No, score=-102.583 tagged_above=-999 required=5 tests=[AWL=0.016, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yE-leM2wH4rX for <ietf@ietfa.amsl.com>; Thu,  1 Mar 2012 08:42:58 -0800 (PST)
Received: from mail.pi.nu (mail.pi.nu [194.71.127.148]) by ietfa.amsl.com (Postfix) with ESMTP id 2AE1221E822A for <ietf@ietf.org>; Thu,  1 Mar 2012 08:42:57 -0800 (PST)
Received: from [192.168.1.64] (81-236-221-144-no93.tbcn.telia.com [81.236.221.144]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: loa@pi.nu) by mail.pi.nu (Postfix) with ESMTPSA id A3ADE514002; Thu,  1 Mar 2012 17:42:53 +0100 (CET)
Message-ID: <4F4FA70B.2030906@pi.nu>
Date: Thu, 01 Mar 2012 17:42:51 +0100
From: Loa Andersson <loa@pi.nu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: Russ Housley <housley@vigilsec.com>
Subject: Re: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt> (Allocation of an Associated Channel Code Point for Use by ITU-T Ethernet based OAM) to Informational RFC
References: <20120222151252.32262.82157.idtracker@ietfa.amsl.com> <03a301ccf174$ff953290$febf97b0$@olddog.co.uk> <515703B08A3A064C9CC8C09ACCC710DC0631679E@XMB-RCD-103.cisco.com> <C71DA9B1-A61F-4C5D-8DCE-3702271CBB6D@vigilsec.com>
In-Reply-To: <C71DA9B1-A61F-4C5D-8DCE-3702271CBB6D@vigilsec.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Mar 2012 16:42:59 -0000

Russ,

I'm not KY, but I feel that your question is a bit loaded.

Certainly if the document is reviewed and approved by the IETF/IESG
it would be no problem to support the assignment of a ACh Type.

But I can't see that approval by some other instance actually carry
the same merit - so exactly what do u mean by "approved G.8113.1"?

/Loa

On 2012-03-01 17:06, Russ Housley wrote:
> KY:
>
> Would you support the assignment to an approved G.8113.1?  That is, if the document contained a normative reference to the approved G.8113.1, then the document that makes the code point allocations would sit in the RFC Editor queue until the ITU-T reaches consensus and approves G.8113.1.
>
> Russ
>
>
> On Mar 1, 2012, at 10:14 AM, Kyung-Yeop Hong (hongk) wrote:
>
>> No/do not support.
>>
>> One of the issues with G.8113.1 in LS370 is its stability and maturity.
>> That was one of the reasons why it was not approved.
>>
>> The Ethernet based OAM protocol documented in the LS370 version is
>> intended to be deployed for MPLS networks. I think the IETF has a duty
>> to ensure that a solution is stable and works for MPLS networks before
>> the code point allocation. A number of concerns with the deployment of
>> this proposed protocol raised in
>> draft-spercher-mpls-tp-oam-considerations are critical to the Internet
>> and must be taken into consideration in this Last Call.
>>
>> KY
>>
>>
>>> -----Original Message-----
>>> From: ietf-announce-bounces@ietf.org [mailto:ietf-announce-
>>> bounces@ietf.org] On Behalf Of The IESG
>>> Sent: 22 February 2012 15:13
>>> To: IETF-Announce
>>> Subject: Last Call:<draft-betts-itu-oam-ach-code-point-03.txt>
>> (Allocation of
>> an
>>> Associated Channel Code Point for Use by ITU-T Ethernet based OAM) to
>>> Informational RFC
>>>
>>>
>>> The IESG has received a request from an individual submitter to
>> consider
>>> the following document:
>>> - 'Allocation of an Associated Channel Code Point for Use by ITU-T
>>>    Ethernet based OAM'
>>>   <draft-betts-itu-oam-ach-code-point-03.txt>  as an 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-03-21. 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 assigns an Associated Channel Type code point for
>>>    carrying Ethernet based Operations, Administration, and Management
>>>    messages in the MPLS Generic Associated Channel (G-ACh).
>>>
>>> The file can be obtained via
>>> http://datatracker.ietf.org/doc/draft-betts-itu-oam-ach-code-point/
>>>
>>> IESG discussion can be tracked via
>>> http://datatracker.ietf.org/doc/draft-betts-itu-oam-ach-code-point/
>>>
>>>
>>> No IPR declarations have been submitted directly on this I-D.
>>> _______________________________________________
>>> IETF-Announce mailing list
>>> IETF-Announce@ietf.org
>>> https://www.ietf.org/mailman/listinfo/ietf-announce
>>
>> _______________________________________________
>> mpls mailing list
>> mpls@ietf.org
>> https://www.ietf.org/mailman/listinfo/mpls
>> _______________________________________________
>> Ietf mailing list
>> Ietf@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf
>
>
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf

-- 


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 scott@kitterman.com  Thu Mar  1 08:54:53 2012
Return-Path: <scott@kitterman.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CBB0521E8363 for <ietf@ietfa.amsl.com>; Thu,  1 Mar 2012 08:54:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.578
X-Spam-Level: 
X-Spam-Status: No, score=-2.578 tagged_above=-999 required=5 tests=[AWL=0.021,  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 6kQHOIHVp50X for <ietf@ietfa.amsl.com>; Thu,  1 Mar 2012 08:54:53 -0800 (PST)
Received: from mailout02.controlledmail.com (mailout02.controlledmail.com [72.81.252.18]) by ietfa.amsl.com (Postfix) with ESMTP id 0005821E8299 for <ietf@ietf.org>; Thu,  1 Mar 2012 08:53:36 -0800 (PST)
Received: from mailout02.controlledmail.com (localhost [127.0.0.1]) by mailout02.controlledmail.com (Postfix) with ESMTP id 0EAB320E40DA; Thu,  1 Mar 2012 11:53:36 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=2007-00; t=1330620816; bh=2CoEKXnrkWZNggGChx3MWh69IOGCjyvhRFozxgfCxgc=; h=From:To:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version:Content-Transfer-Encoding:Content-Type; b=Czrk01q6hkVgedDts/Iwqzfa0e2FOHp/Lk7za9QrkuvrpAcu3NTUAecO5JmWsSEMv KVgHOgAh4NxTJEcBZBYlw9NLZOMQL5XiSeacTHvLkS0mY09p7+63DN7gu+jptt5unQ NqIAVFc3kMYhZleG9XkBKTCh2UTkG6DdZToiXrRY=
Received: from scott-latitude-e6320.localnet (static-72-81-252-21.bltmmd.fios.verizon.net [72.81.252.21]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailout02.controlledmail.com (Postfix) with ESMTPSA id E0CED20E408F;  Thu,  1 Mar 2012 11:53:35 -0500 (EST)
From: Scott Kitterman <scott@kitterman.com>
To: ietf@ietf.org
Subject: Re: Last Call: <draft-ietf-marf-spf-reporting-08.txt> (SPF Authentication Failure Reporting using the Abuse Report Format) to Proposed Standard
Date: Thu, 01 Mar 2012 11:53:35 -0500
Message-ID: <42925810.AtQu7N28Qf@scott-latitude-e6320>
User-Agent: KMail/4.7.3 (Linux/3.0.0-16-generic-pae; KDE/4.7.4; i686; ; )
In-Reply-To: <6.2.5.6.2.20120301064114.0a80f078@resistor.net>
References: <20120301004643.17274.83943.idtracker@ietfa.amsl.com> <CAC4RtVDUmcLZh4J2SvV32kNxaQcPYr1+9S9q59Kd50F4hqWaOQ@mail.gmail.com> <6.2.5.6.2.20120301064114.0a80f078@resistor.net>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
X-AV-Checked: ClamAV using ClamSMTP
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Mar 2012 16:54:54 -0000

On Thursday, March 01, 2012 07:53:48 AM SM wrote:
...
> At 06:22 01-03-2012, Scott Kitterman wrote:
> >IESG.  It includes SPF specifics (although it doesn't require a normative
> >reference to RFC 4408, so there's no downref issue with it), so I think
> >that in the context of authentication failure reporting this is already
> >established
> >to be in scope.  All the current draft does is provide an optional
> >mechanism
> In the Last Call message issued by the IESG, it is mentioned that:
> 
>    "Note that this document has a downward normative reference: This
> document makes a normative reference to SPF (RFC4408), which is
> Experimental."
> 
> Is the downward normative reference in the draft incorrect?

No.  The downref is correct.  Downrefs are allowed, but have to be reviewed 
(AIUI).  I was saying that I think the downref is safe and appropriate in this 
instance because the parts of RFC 4408 that are relevant to this draft are 
stable and it would be very, very, very unlikely for them to change in SPFbis.

The "no downref issue" was related to draft-ietf-marf-authfailure-report-10, 
not this one.

Scott K

From nurit.sprecher@nsn.com  Thu Mar  1 09:23:00 2012
Return-Path: <nurit.sprecher@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 69E5521E806F for <ietf@ietfa.amsl.com>; Thu,  1 Mar 2012 09:23:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.54
X-Spam-Level: 
X-Spam-Status: No, score=-6.54 tagged_above=-999 required=5 tests=[AWL=0.059,  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 AUXdAcC+i52V for <ietf@ietfa.amsl.com>; Thu,  1 Mar 2012 09:22:59 -0800 (PST)
Received: from demumfd002.nsn-inter.net (demumfd002.nsn-inter.net [93.183.12.31]) by ietfa.amsl.com (Postfix) with ESMTP id F0C6121E804B for <ietf@ietf.org>; Thu,  1 Mar 2012 09:22:58 -0800 (PST)
Received: from demuprx016.emea.nsn-intra.net ([10.150.129.55]) by demumfd002.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id q21HMrp5021360 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 1 Mar 2012 18:22:55 +0100
Received: from demuexc023.nsn-intra.net (demuexc023.nsn-intra.net [10.150.128.36]) by demuprx016.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id q21HMplX006787; Thu, 1 Mar 2012 18:22:52 +0100
Received: from DEMUEXC013.nsn-intra.net ([10.150.128.24]) by demuexc023.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 1 Mar 2012 18:22:44 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt>(Allocation of an Associated Channel Code Point for Use byITU-T Ethernet based OAM) to Informational RFC
Date: Thu, 1 Mar 2012 18:22:42 +0100
Message-ID: <E4873516F3FC7547BCFE792C7D94039C015D1227@DEMUEXC013.nsn-intra.net>
In-Reply-To: <C71DA9B1-A61F-4C5D-8DCE-3702271CBB6D@vigilsec.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt>(Allocation of an Associated Channel Code Point for Use byITU-T Ethernet based OAM) to Informational RFC
Thread-Index: Acz3xUUOahjW7090RKyBaFlAtulJ6AACiBDA
References: <20120222151252.32262.82157.idtracker@ietfa.amsl.com><03a301ccf174$ff953290$febf97b0$@olddog.co.uk><515703B08A3A064C9CC8C09ACCC710DC0631679E@XMB-RCD-103.cisco.com> <C71DA9B1-A61F-4C5D-8DCE-3702271CBB6D@vigilsec.com>
From: "Sprecher, Nurit (NSN - IL/Hod HaSharon)" <nurit.sprecher@nsn.com>
To: "ext Russ Housley" <housley@vigilsec.com>, "Kyung-Yeop Hong (hongk)" <hongk@cisco.com>
X-OriginalArrivalTime: 01 Mar 2012 17:22:44.0262 (UTC) FILETIME=[E9F94460:01CCF7CF]
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: 3925
X-purgate-ID: 151667::1330622575-000033AC-4CCB56CF/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, 01 Mar 2012 17:23:00 -0000

Hi Russ,
I am not K.Y., but to me it seems at the moment as a very theoretical
question.
If the document is stable and approved, we can re-issue an IETF LC for a
better version of draft-betts that resolves my and others' comments that
I sent earlier today and the IETF can make the decision then.=20
At the moment, I cannot support the publication of draft-bett, for the
reasons please see my mail that was sent earlier today to the IETF list.
Best regards,
Nurit

-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
ext Russ Housley
Sent: Thursday, March 01, 2012 6:06 PM
To: Kyung-Yeop Hong (hongk)
Cc: ietf@ietf.org
Subject: Re: Last Call:
<draft-betts-itu-oam-ach-code-point-03.txt>(Allocation of an Associated
Channel Code Point for Use byITU-T Ethernet based OAM) to Informational
RFC

KY:

Would you support the assignment to an approved G.8113.1?  That is, if
the document contained a normative reference to the approved G.8113.1,
then the document that makes the code point allocations would sit in the
RFC Editor queue until the ITU-T reaches consensus and approves
G.8113.1.

Russ


On Mar 1, 2012, at 10:14 AM, Kyung-Yeop Hong (hongk) wrote:

> No/do not support.
>=20
> One of the issues with G.8113.1 in LS370 is its stability and
maturity.
> That was one of the reasons why it was not approved.=20
>=20
> The Ethernet based OAM protocol documented in the LS370 version is
> intended to be deployed for MPLS networks. I think the IETF has a duty
> to ensure that a solution is stable and works for MPLS networks before
> the code point allocation. A number of concerns with the deployment of
> this proposed protocol raised in
> draft-spercher-mpls-tp-oam-considerations are critical to the Internet
> and must be taken into consideration in this Last Call.=20
>=20
> KY
>=20
>=20
>> -----Original Message-----
>> From: ietf-announce-bounces@ietf.org [mailto:ietf-announce-
>> bounces@ietf.org] On Behalf Of The IESG
>> Sent: 22 February 2012 15:13
>> To: IETF-Announce
>> Subject: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt>
> (Allocation of
> an
>> Associated Channel Code Point for Use by ITU-T Ethernet based OAM) to
>> Informational RFC
>>=20
>>=20
>> The IESG has received a request from an individual submitter to
> consider
>> the following document:
>> - 'Allocation of an Associated Channel Code Point for Use by ITU-T
>>   Ethernet based OAM'
>>  <draft-betts-itu-oam-ach-code-point-03.txt> as an Informational RFC
>>=20
>> The IESG plans to make a decision in the next few weeks, and solicits
>> final comments on this action. Please send substantive comments to
the
>> ietf@ietf.org mailing lists by 2012-03-21. Exceptionally, comments
may
> be
>> sent to iesg@ietf.org instead. In either case, please retain the
>> beginning of the Subject line to allow automated sorting.
>>=20
>> Abstract
>>=20
>>   This document assigns an Associated Channel Type code point for
>>   carrying Ethernet based Operations, Administration, and Management
>>   messages in the MPLS Generic Associated Channel (G-ACh).
>>=20
>> The file can be obtained via
>> http://datatracker.ietf.org/doc/draft-betts-itu-oam-ach-code-point/
>>=20
>> IESG discussion can be tracked via
>> http://datatracker.ietf.org/doc/draft-betts-itu-oam-ach-code-point/
>>=20
>>=20
>> No IPR declarations have been submitted directly on this I-D.
>> _______________________________________________
>> IETF-Announce mailing list
>> IETF-Announce@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf-announce
>=20
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From nurit.sprecher@nsn.com  Thu Mar  1 09:26:03 2012
Return-Path: <nurit.sprecher@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 0EEDD21E8094 for <ietf@ietfa.amsl.com>; Thu,  1 Mar 2012 09:26:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.541
X-Spam-Level: 
X-Spam-Status: No, score=-6.541 tagged_above=-999 required=5 tests=[AWL=0.058,  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 IAj2+jh5MvZW for <ietf@ietfa.amsl.com>; Thu,  1 Mar 2012 09:26:02 -0800 (PST)
Received: from demumfd001.nsn-inter.net (demumfd001.nsn-inter.net [93.183.12.32]) by ietfa.amsl.com (Postfix) with ESMTP id D945421E808B for <ietf@ietf.org>; Thu,  1 Mar 2012 09:26:01 -0800 (PST)
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 q21HPw5i018924 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 1 Mar 2012 18:25:58 +0100
Received: from demuexc023.nsn-intra.net (demuexc023.nsn-intra.net [10.150.128.36]) by demuprx016.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id q21HPr6t020615; Thu, 1 Mar 2012 18:25:58 +0100
Received: from DEMUEXC013.nsn-intra.net ([10.150.128.24]) by demuexc023.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 1 Mar 2012 18:25:28 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt>(Allocationof an Associated Channel Code Point for Use byITU-T Ethernetbased OAM) to Informational RFC
Date: Thu, 1 Mar 2012 18:25:27 +0100
Message-ID: <E4873516F3FC7547BCFE792C7D94039C015D122B@DEMUEXC013.nsn-intra.net>
In-Reply-To: <E4873516F3FC7547BCFE792C7D94039C015D1227@DEMUEXC013.nsn-intra.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt>(Allocationof an Associated Channel Code Point for Use byITU-T Ethernetbased OAM) to Informational RFC
Thread-Index: Acz3xUUOahjW7090RKyBaFlAtulJ6AACiBDAAAAzWHA=
References: <20120222151252.32262.82157.idtracker@ietfa.amsl.com><03a301ccf174$ff953290$febf97b0$@olddog.co.uk><515703B08A3A064C9CC8C09ACCC710DC0631679E@XMB-RCD-103.cisco.com><C71DA9B1-A61F-4C5D-8DCE-3702271CBB6D@vigilsec.com> <E4873516F3FC7547BCFE792C7D94039C015D1227@DEMUEXC013.nsn-intra.net>
From: "Sprecher, Nurit (NSN - IL/Hod HaSharon)" <nurit.sprecher@nsn.com>
To: "Sprecher, Nurit (NSN - IL/Hod HaSharon)" <nurit.sprecher@nsn.com>, "ext Russ Housley" <housley@vigilsec.com>, "Kyung-Yeop Hong (hongk)" <hongk@cisco.com>
X-OriginalArrivalTime: 01 Mar 2012 17:25:28.0560 (UTC) FILETIME=[4BE72700:01CCF7D0]
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: 4064
X-purgate-ID: 151667::1330622758-000044A2-86593107/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, 01 Mar 2012 17:26:03 -0000

Hi Russ,
I am not K.Y., but to me it seems at the moment as a very theoretical
question.
If the G.8113.1 document is stable and approved, we can re-issue an IETF
LC for a
better version of draft-betts that resolves my and others' comments that
I sent earlier today and the IETF can make the decision then.=20
At the moment, I cannot support the publication of draft-bett, for the
reasons please see my mail that was sent earlier today to the IETF list.
Best regards,
Nurit

-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
ext Russ Housley
Sent: Thursday, March 01, 2012 6:06 PM
To: Kyung-Yeop Hong (hongk)
Cc: ietf@ietf.org
Subject: Re: Last Call:
<draft-betts-itu-oam-ach-code-point-03.txt>(Allocation of an Associated
Channel Code Point for Use byITU-T Ethernet based OAM) to Informational
RFC

KY:

Would you support the assignment to an approved G.8113.1?  That is, if
the document contained a normative reference to the approved G.8113.1,
then the document that makes the code point allocations would sit in the
RFC Editor queue until the ITU-T reaches consensus and approves
G.8113.1.

Russ


On Mar 1, 2012, at 10:14 AM, Kyung-Yeop Hong (hongk) wrote:

> No/do not support.
>=20
> One of the issues with G.8113.1 in LS370 is its stability and
maturity.
> That was one of the reasons why it was not approved.=20
>=20
> The Ethernet based OAM protocol documented in the LS370 version is
> intended to be deployed for MPLS networks. I think the IETF has a duty
> to ensure that a solution is stable and works for MPLS networks before
> the code point allocation. A number of concerns with the deployment of
> this proposed protocol raised in
> draft-spercher-mpls-tp-oam-considerations are critical to the Internet
> and must be taken into consideration in this Last Call.=20
>=20
> KY
>=20
>=20
>> -----Original Message-----
>> From: ietf-announce-bounces@ietf.org [mailto:ietf-announce-
>> bounces@ietf.org] On Behalf Of The IESG
>> Sent: 22 February 2012 15:13
>> To: IETF-Announce
>> Subject: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt>
> (Allocation of
> an
>> Associated Channel Code Point for Use by ITU-T Ethernet based OAM) to
>> Informational RFC
>>=20
>>=20
>> The IESG has received a request from an individual submitter to
> consider
>> the following document:
>> - 'Allocation of an Associated Channel Code Point for Use by ITU-T
>>   Ethernet based OAM'
>>  <draft-betts-itu-oam-ach-code-point-03.txt> as an Informational RFC
>>=20
>> The IESG plans to make a decision in the next few weeks, and solicits
>> final comments on this action. Please send substantive comments to
the
>> ietf@ietf.org mailing lists by 2012-03-21. Exceptionally, comments
may
> be
>> sent to iesg@ietf.org instead. In either case, please retain the
>> beginning of the Subject line to allow automated sorting.
>>=20
>> Abstract
>>=20
>>   This document assigns an Associated Channel Type code point for
>>   carrying Ethernet based Operations, Administration, and Management
>>   messages in the MPLS Generic Associated Channel (G-ACh).
>>=20
>> The file can be obtained via
>> http://datatracker.ietf.org/doc/draft-betts-itu-oam-ach-code-point/
>>=20
>> IESG discussion can be tracked via
>> http://datatracker.ietf.org/doc/draft-betts-itu-oam-ach-code-point/
>>=20
>>=20
>> No IPR declarations have been submitted directly on this I-D.
>> _______________________________________________
>> IETF-Announce mailing list
>> IETF-Announce@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf-announce
>=20
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf

From stpeter@stpeter.im  Thu Mar  1 09:50:40 2012
Return-Path: <stpeter@stpeter.im>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C024621E80BF; Thu,  1 Mar 2012 09:50:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.658
X-Spam-Level: 
X-Spam-Status: No, score=-102.658 tagged_above=-999 required=5 tests=[AWL=-0.059, 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 8+zrb0SF0318; Thu,  1 Mar 2012 09:50:39 -0800 (PST)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id C28C421E80BC; Thu,  1 Mar 2012 09:50:35 -0800 (PST)
Received: from squire.local (unknown [64.101.72.114]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 45FDF4005B; Thu,  1 Mar 2012 11:02:15 -0700 (MST)
Message-ID: <4F4FB6E9.6020201@stpeter.im>
Date: Thu, 01 Mar 2012 10:50:33 -0700
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.5; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: iesg@ietf.org
Subject: Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
References: <20120221181006.43AB121F87BF@ietfa.amsl.com>
In-Reply-To: <20120221181006.43AB121F87BF@ietfa.amsl.com>
X-Enigmail-Version: 1.3.5
OpenPGP: url=https://stpeter.im/stpeter.asc
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: mnot@mnot.net, ietf-http-wg@w3.org, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Mar 2012 17:50:41 -0000

<hat type='AD'/>

On 2/21/12 11:10 AM, IESG Secretary wrote:
> A modified charter has been submitted for the Hypertext Transfer 
> Protocol Bis (httpbis) working group in the Applications Area of the 
> IETF.  The IESG has not made any determination as yet.  The modified 
> charter is provided below for informational purposes only.  Please send 
> your comments to the IESG mailing list (iesg@ietf.org) by Tuesday, 
> February 28, 2012.

Clearly this rechartering request has triggered a lengthy discussion
about web authentication. However, the only comment on the charter
itself Stephen Farrell's noting that this bullet is a bit vague
(specifically that it does not mention authentication):

> * Reflecting modern security requirements and practices

Stephen and I just had a chat about this matter. He and I came up with a
proposed paragraph to add after that list of bullet points:

   In the initial phase of work on HTTP/2.0, new proposals
   for authentication schemes can be made.  The WG will
   select zero or more of those with a goal of choosing
   at least one scheme that is better than those available
   for HTTP/1.x.  Non-selected schemes might be discussed
   with the IETF Security Area for further work there.

Your comments are welcome.

Peter

-- 
Peter Saint-Andre
https://stpeter.im/



From tbray@textuality.com  Thu Mar  1 09:57:41 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 B296021E80EE for <ietf@ietfa.amsl.com>; Thu,  1 Mar 2012 09:57:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.866
X-Spam-Level: 
X-Spam-Status: No, score=-3.866 tagged_above=-999 required=5 tests=[AWL=-0.889, 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 33V-OrYGYvBf for <ietf@ietfa.amsl.com>; Thu,  1 Mar 2012 09:57:40 -0800 (PST)
Received: from mail-tul01m020-f172.google.com (mail-tul01m020-f172.google.com [209.85.214.172]) by ietfa.amsl.com (Postfix) with ESMTP id CF88121E80DA for <ietf@ietf.org>; Thu,  1 Mar 2012 09:57:40 -0800 (PST)
Received: by obbeh20 with SMTP id eh20so1206093obb.31 for <ietf@ietf.org>; Thu, 01 Mar 2012 09:57:40 -0800 (PST)
Received-SPF: pass (google.com: domain of tbray@textuality.com designates 10.182.48.36 as permitted sender) client-ip=10.182.48.36; 
Authentication-Results: mr.google.com; spf=pass (google.com: domain of tbray@textuality.com designates 10.182.48.36 as permitted sender) smtp.mail=tbray@textuality.com
Received: from mr.google.com ([10.182.48.36]) by 10.182.48.36 with SMTP id i4mr2261689obn.72.1330624660567 (num_hops = 1); Thu, 01 Mar 2012 09:57:40 -0800 (PST)
MIME-Version: 1.0
Received: by 10.182.48.36 with SMTP id i4mr1964760obn.72.1330624660396; Thu, 01 Mar 2012 09:57:40 -0800 (PST)
Received: by 10.182.137.69 with HTTP; Thu, 1 Mar 2012 09:57:39 -0800 (PST)
X-Originating-IP: [24.84.235.32]
In-Reply-To: <4F4FB6E9.6020201@stpeter.im>
References: <20120221181006.43AB121F87BF@ietfa.amsl.com> <4F4FB6E9.6020201@stpeter.im>
Date: Thu, 1 Mar 2012 09:57:39 -0800
Message-ID: <CAHBU6ivBtYxy0_eDZu1YMNfq9+aCz3jGaLTS48+=b4WZGT8OpQ@mail.gmail.com>
Subject: Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
From: Tim Bray <tbray@textuality.com>
To: Peter Saint-Andre <stpeter@stpeter.im>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Gm-Message-State: ALoCoQklBmEx8R76uU7PwG+JITg9Skq1uYhRfXfX1qr/OfZhCvfWVa29UeUhmLG04wkMSNVfCEka
Cc: mnot@mnot.net, IETF discussion list <ietf@ietf.org>, iesg@ietf.org, ietf-http-wg@w3.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Mar 2012 17:57:41 -0000

+1

On Thu, Mar 1, 2012 at 9:50 AM, Peter Saint-Andre <stpeter@stpeter.im> wrot=
e:
> <hat type=3D'AD'/>
>
> On 2/21/12 11:10 AM, IESG Secretary wrote:
>> A modified charter has been submitted for the Hypertext Transfer
>> Protocol Bis (httpbis) working group in the Applications Area of the
>> IETF. =A0The IESG has not made any determination as yet. =A0The modified
>> charter is provided below for informational purposes only. =A0Please sen=
d
>> your comments to the IESG mailing list (iesg@ietf.org) by Tuesday,
>> February 28, 2012.
>
> Clearly this rechartering request has triggered a lengthy discussion
> about web authentication. However, the only comment on the charter
> itself Stephen Farrell's noting that this bullet is a bit vague
> (specifically that it does not mention authentication):
>
>> * Reflecting modern security requirements and practices
>
> Stephen and I just had a chat about this matter. He and I came up with a
> proposed paragraph to add after that list of bullet points:
>
> =A0 In the initial phase of work on HTTP/2.0, new proposals
> =A0 for authentication schemes can be made. =A0The WG will
> =A0 select zero or more of those with a goal of choosing
> =A0 at least one scheme that is better than those available
> =A0 for HTTP/1.x. =A0Non-selected schemes might be discussed
> =A0 with the IETF Security Area for further work there.
>
> Your comments are welcome.
>
> Peter
>
> --
> Peter Saint-Andre
> https://stpeter.im/
>
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf

From nick@inex.ie  Thu Mar  1 10:01:42 2012
Return-Path: <nick@inex.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 913BF21E80A5; Thu,  1 Mar 2012 10:01:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.562
X-Spam-Level: 
X-Spam-Status: No, score=-2.562 tagged_above=-999 required=5 tests=[AWL=0.037,  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 nQTL5j3gCKCF; Thu,  1 Mar 2012 10:01:42 -0800 (PST)
Received: from mail.acquirer.com (mail.acquirer.com [IPv6:2a03:8900:0:100::5]) by ietfa.amsl.com (Postfix) with ESMTP id BB7E321E8081; Thu,  1 Mar 2012 10:01:40 -0800 (PST)
X-Envelope-To: ietf@ietf.org
Received: from crumpet.foobar.org (twinkie.foobar.org [87.192.56.84]) (authenticated bits=0) by mail.acquirer.com (8.14.4/8.14.4) with ESMTP id q21I272l092005 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Thu, 1 Mar 2012 18:02:13 GMT (envelope-from nick@inex.ie)
Message-ID: <4F4FB97C.2080600@inex.ie>
Date: Thu, 01 Mar 2012 18:01:32 +0000
From: Nick Hilliard <nick@inex.ie>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: Peter Saint-Andre <stpeter@stpeter.im>
Subject: Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
References: <20120221181006.43AB121F87BF@ietfa.amsl.com> <4F4FB6E9.6020201@stpeter.im>
In-Reply-To: <4F4FB6E9.6020201@stpeter.im>
X-Enigmail-Version: 1.3.5
X-Company-Info-1: Internet Neutral Exchange Association Limited. Registered in Ireland No. 253804
X-Company-Info-2: Registered Offices: 1-2, Marino Mart, Fairview, Dublin 3
X-Company-Info-3: Internet Neutral Exchange Association Limited is limited by guarantee
X-Company-Info-4: Offices: 4027 Kingswood Road, Citywest, Dublin 24.
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: mnot@mnot.net, IETF discussion list <ietf@ietf.org>, iesg@ietf.org, ietf-http-wg@w3.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Mar 2012 18:01:42 -0000

On 01/03/2012 17:50, Peter Saint-Andre wrote:
> Stephen and I just had a chat about this matter. He and I came up with a
> proposed paragraph to add after that list of bullet points:
> 
>    In the initial phase of work on HTTP/2.0, new proposals
>    for authentication schemes can be made.  The WG will
>    select zero or more of those with a goal of choosing
>    at least one scheme that is better than those available
>    for HTTP/1.x.  Non-selected schemes might be discussed
>    with the IETF Security Area for further work there.
> 
> Your comments are welcome.

Can I suggest you also include authorization capabilities as a core
component of this. It's not much use to have people able to authenticate
themselves to a system if that system doesn't also provide a framework for
allowing the server-side application decide what they can or cannot do.

Nick

From housley@vigilsec.com  Thu Mar  1 10:02: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 6CD2E21E80E5 for <ietf@ietfa.amsl.com>; Thu,  1 Mar 2012 10:02:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.552
X-Spam-Level: 
X-Spam-Status: No, score=-102.552 tagged_above=-999 required=5 tests=[AWL=0.047, 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 1+p6TZ3BYamr for <ietf@ietfa.amsl.com>; Thu,  1 Mar 2012 10:02:05 -0800 (PST)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id 83ECB21E80B5 for <ietf@ietf.org>; Thu,  1 Mar 2012 10:02:05 -0800 (PST)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 3238A9A471B; Thu,  1 Mar 2012 13:02:24 -0500 (EST)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([208.254.26.82]) by localhost (ronin.smetech.net [208.254.26.81]) (amavisd-new, port 10024) with ESMTP id NMmNDJJJJx3U; Thu,  1 Mar 2012 13:01:42 -0500 (EST)
Received: from [192.168.2.104] (pool-96-241-165-215.washdc.fios.verizon.net [96.241.165.215]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 9A8719A470F; Thu,  1 Mar 2012 13:02:22 -0500 (EST)
Subject: Re: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt> (Allocation of an Associated Channel Code Point for Use by ITU-T Ethernet based OAM) to Informational RFC
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <4F4FA70B.2030906@pi.nu>
Date: Thu, 1 Mar 2012 13:02:02 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <D0F60388-D852-4815-917A-B14BF40C64FB@vigilsec.com>
References: <20120222151252.32262.82157.idtracker@ietfa.amsl.com> <03a301ccf174$ff953290$febf97b0$@olddog.co.uk> <515703B08A3A064C9CC8C09ACCC710DC0631679E@XMB-RCD-103.cisco.com> <C71DA9B1-A61F-4C5D-8DCE-3702271CBB6D@vigilsec.com> <4F4FA70B.2030906@pi.nu>
To: Loa Andersson <loa@pi.nu>
X-Mailer: Apple Mail (2.1084)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Mar 2012 18:02:06 -0000

Loa:

Right now, there is no ITU-T approved document to reference.   I am =
certainly not an expert on ITU-T process, but my understanding is that =
earliest that we could see an approved G.8113.1 is December 2012.  My =
point is that we don't want to assign a code point until the ITU-T =
approves their document.  However, if we are willing to assign a code =
point to G.8113.1 once it is approved, then this would be an approach =
where the code point assignment would block on the approval of the =
normative reference.

I like this approach from the political point of view.  With this =
approach the IETF tells the ITU-T that if and only if they are able to =
achieve consensus on G.8113.1, then a code point will be assigned.

Russ


On Mar 1, 2012, at 11:42 AM, Loa Andersson wrote:

> Russ,
>=20
> I'm not KY, but I feel that your question is a bit loaded.
>=20
> Certainly if the document is reviewed and approved by the IETF/IESG
> it would be no problem to support the assignment of a ACh Type.
>=20
> But I can't see that approval by some other instance actually carry
> the same merit - so exactly what do u mean by "approved G.8113.1"?
>=20
> /Loa
>=20
> On 2012-03-01 17:06, Russ Housley wrote:
>> KY:
>>=20
>> Would you support the assignment to an approved G.8113.1?  That is, =
if the document contained a normative reference to the approved =
G.8113.1, then the document that makes the code point allocations would =
sit in the RFC Editor queue until the ITU-T reaches consensus and =
approves G.8113.1.
>>=20
>> Russ
>>=20
>>=20
>> On Mar 1, 2012, at 10:14 AM, Kyung-Yeop Hong (hongk) wrote:
>>=20
>>> No/do not support.
>>>=20
>>> One of the issues with G.8113.1 in LS370 is its stability and =
maturity.
>>> That was one of the reasons why it was not approved.
>>>=20
>>> The Ethernet based OAM protocol documented in the LS370 version is
>>> intended to be deployed for MPLS networks. I think the IETF has a =
duty
>>> to ensure that a solution is stable and works for MPLS networks =
before
>>> the code point allocation. A number of concerns with the deployment =
of
>>> this proposed protocol raised in
>>> draft-spercher-mpls-tp-oam-considerations are critical to the =
Internet
>>> and must be taken into consideration in this Last Call.
>>>=20
>>> KY
>>>=20
>>>=20
>>>> -----Original Message-----
>>>> From: ietf-announce-bounces@ietf.org [mailto:ietf-announce-
>>>> bounces@ietf.org] On Behalf Of The IESG
>>>> Sent: 22 February 2012 15:13
>>>> To: IETF-Announce
>>>> Subject: Last Call:<draft-betts-itu-oam-ach-code-point-03.txt>
>>> (Allocation of
>>> an
>>>> Associated Channel Code Point for Use by ITU-T Ethernet based OAM) =
to
>>>> Informational RFC
>>>>=20
>>>>=20
>>>> The IESG has received a request from an individual submitter to
>>> consider
>>>> the following document:
>>>> - 'Allocation of an Associated Channel Code Point for Use by ITU-T
>>>>   Ethernet based OAM'
>>>>  <draft-betts-itu-oam-ach-code-point-03.txt>  as an Informational =
RFC
>>>>=20
>>>> The IESG plans to make a decision in the next few weeks, and =
solicits
>>>> final comments on this action. Please send substantive comments to =
the
>>>> ietf@ietf.org mailing lists by 2012-03-21. Exceptionally, comments =
may
>>> be
>>>> sent to iesg@ietf.org instead. In either case, please retain the
>>>> beginning of the Subject line to allow automated sorting.
>>>>=20
>>>> Abstract
>>>>=20
>>>>   This document assigns an Associated Channel Type code point for
>>>>   carrying Ethernet based Operations, Administration, and =
Management
>>>>   messages in the MPLS Generic Associated Channel (G-ACh).
>>>>=20
>>>> The file can be obtained via
>>>> http://datatracker.ietf.org/doc/draft-betts-itu-oam-ach-code-point/
>>>>=20
>>>> IESG discussion can be tracked via
>>>> http://datatracker.ietf.org/doc/draft-betts-itu-oam-ach-code-point/
>>>>=20
>>>>=20
>>>> No IPR declarations have been submitted directly on this I-D.
>>>> _______________________________________________
>>>> IETF-Announce mailing list
>>>> IETF-Announce@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/ietf-announce
>>>=20
>>> _______________________________________________
>>> mpls mailing list
>>> mpls@ietf.org
>>> https://www.ietf.org/mailman/listinfo/mpls
>>> _______________________________________________
>>> Ietf mailing list
>>> Ietf@ietf.org
>>> https://www.ietf.org/mailman/listinfo/ietf
>>=20
>>=20
>>=20
>> _______________________________________________
>> Ietf mailing list
>> Ietf@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf
>=20
> --=20
>=20
>=20
> 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 nurit.sprecher@nsn.com  Thu Mar  1 10:07:08 2012
Return-Path: <nurit.sprecher@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 8384121E80C8 for <ietf@ietfa.amsl.com>; Thu,  1 Mar 2012 10:07:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.543
X-Spam-Level: 
X-Spam-Status: No, score=-6.543 tagged_above=-999 required=5 tests=[AWL=0.056,  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 eFHOE5AMR0nK for <ietf@ietfa.amsl.com>; Thu,  1 Mar 2012 10:07:06 -0800 (PST)
Received: from demumfd001.nsn-inter.net (demumfd001.nsn-inter.net [93.183.12.32]) by ietfa.amsl.com (Postfix) with ESMTP id CE8EE21E80CC for <ietf@ietf.org>; Thu,  1 Mar 2012 10:07:04 -0800 (PST)
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 q21I73lB017643 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 1 Mar 2012 19:07:03 +0100
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 q21I6w7Y014209; Thu, 1 Mar 2012 19:07:02 +0100
Received: from DEMUEXC013.nsn-intra.net ([10.150.128.24]) by DEMUEXC048.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 1 Mar 2012 19:07:02 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt>(Allocation of an Associated Channel Code Point for Use byITU-T Ethernet based OAM) to Informational RFC
Date: Thu, 1 Mar 2012 19:06:59 +0100
Message-ID: <E4873516F3FC7547BCFE792C7D94039C015D1238@DEMUEXC013.nsn-intra.net>
In-Reply-To: <D0F60388-D852-4815-917A-B14BF40C64FB@vigilsec.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt>(Allocation of an Associated Channel Code Point for Use byITU-T Ethernet based OAM) to Informational RFC
Thread-Index: Acz31X24pPa5eT3ZQTy+0WoRj780FgAAGwUw
References: <20120222151252.32262.82157.idtracker@ietfa.amsl.com><03a301ccf174$ff953290$febf97b0$@olddog.co.uk><515703B08A3A064C9CC8C09ACCC710DC0631679E@XMB-RCD-103.cisco.com><C71DA9B1-A61F-4C5D-8DCE-3702271CBB6D@vigilsec.com><4F4FA70B.2030906@pi.nu> <D0F60388-D852-4815-917A-B14BF40C64FB@vigilsec.com>
From: "Sprecher, Nurit (NSN - IL/Hod HaSharon)" <nurit.sprecher@nsn.com>
To: "ext Russ Housley" <housley@vigilsec.com>, "Loa Andersson" <loa@pi.nu>
X-OriginalArrivalTime: 01 Mar 2012 18:07:02.0724 (UTC) FILETIME=[1A8A6040:01CCF7D6]
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: 5638
X-purgate-ID: 151667::1330625223-000044A2-11E8EDD8/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, 01 Mar 2012 18:07:09 -0000

Russ,
Independently of that point, draft-betts in its current version has many
issues....
Many clarifications are needed before it can be considered....please see
my mail for the details.
Best regards,
Nurit


-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
ext Russ Housley
Sent: Thursday, March 01, 2012 8:02 PM
To: Loa Andersson
Cc: ietf@ietf.org
Subject: Re: Last Call:
<draft-betts-itu-oam-ach-code-point-03.txt>(Allocation of an Associated
Channel Code Point for Use byITU-T Ethernet based OAM) to Informational
RFC

Loa:

Right now, there is no ITU-T approved document to reference.   I am
certainly not an expert on ITU-T process, but my understanding is that
earliest that we could see an approved G.8113.1 is December 2012.  My
point is that we don't want to assign a code point until the ITU-T
approves their document.  However, if we are willing to assign a code
point to G.8113.1 once it is approved, then this would be an approach
where the code point assignment would block on the approval of the
normative reference.

I like this approach from the political point of view.  With this
approach the IETF tells the ITU-T that if and only if they are able to
achieve consensus on G.8113.1, then a code point will be assigned.

Russ


On Mar 1, 2012, at 11:42 AM, Loa Andersson wrote:

> Russ,
>=20
> I'm not KY, but I feel that your question is a bit loaded.
>=20
> Certainly if the document is reviewed and approved by the IETF/IESG
> it would be no problem to support the assignment of a ACh Type.
>=20
> But I can't see that approval by some other instance actually carry
> the same merit - so exactly what do u mean by "approved G.8113.1"?
>=20
> /Loa
>=20
> On 2012-03-01 17:06, Russ Housley wrote:
>> KY:
>>=20
>> Would you support the assignment to an approved G.8113.1?  That is,
if the document contained a normative reference to the approved
G.8113.1, then the document that makes the code point allocations would
sit in the RFC Editor queue until the ITU-T reaches consensus and
approves G.8113.1.
>>=20
>> Russ
>>=20
>>=20
>> On Mar 1, 2012, at 10:14 AM, Kyung-Yeop Hong (hongk) wrote:
>>=20
>>> No/do not support.
>>>=20
>>> One of the issues with G.8113.1 in LS370 is its stability and
maturity.
>>> That was one of the reasons why it was not approved.
>>>=20
>>> The Ethernet based OAM protocol documented in the LS370 version is
>>> intended to be deployed for MPLS networks. I think the IETF has a
duty
>>> to ensure that a solution is stable and works for MPLS networks
before
>>> the code point allocation. A number of concerns with the deployment
of
>>> this proposed protocol raised in
>>> draft-spercher-mpls-tp-oam-considerations are critical to the
Internet
>>> and must be taken into consideration in this Last Call.
>>>=20
>>> KY
>>>=20
>>>=20
>>>> -----Original Message-----
>>>> From: ietf-announce-bounces@ietf.org [mailto:ietf-announce-
>>>> bounces@ietf.org] On Behalf Of The IESG
>>>> Sent: 22 February 2012 15:13
>>>> To: IETF-Announce
>>>> Subject: Last Call:<draft-betts-itu-oam-ach-code-point-03.txt>
>>> (Allocation of
>>> an
>>>> Associated Channel Code Point for Use by ITU-T Ethernet based OAM)
to
>>>> Informational RFC
>>>>=20
>>>>=20
>>>> The IESG has received a request from an individual submitter to
>>> consider
>>>> the following document:
>>>> - 'Allocation of an Associated Channel Code Point for Use by ITU-T
>>>>   Ethernet based OAM'
>>>>  <draft-betts-itu-oam-ach-code-point-03.txt>  as an Informational
RFC
>>>>=20
>>>> The IESG plans to make a decision in the next few weeks, and
solicits
>>>> final comments on this action. Please send substantive comments to
the
>>>> ietf@ietf.org mailing lists by 2012-03-21. Exceptionally, comments
may
>>> be
>>>> sent to iesg@ietf.org instead. In either case, please retain the
>>>> beginning of the Subject line to allow automated sorting.
>>>>=20
>>>> Abstract
>>>>=20
>>>>   This document assigns an Associated Channel Type code point for
>>>>   carrying Ethernet based Operations, Administration, and
Management
>>>>   messages in the MPLS Generic Associated Channel (G-ACh).
>>>>=20
>>>> The file can be obtained via
>>>> http://datatracker.ietf.org/doc/draft-betts-itu-oam-ach-code-point/
>>>>=20
>>>> IESG discussion can be tracked via
>>>> http://datatracker.ietf.org/doc/draft-betts-itu-oam-ach-code-point/
>>>>=20
>>>>=20
>>>> No IPR declarations have been submitted directly on this I-D.
>>>> _______________________________________________
>>>> IETF-Announce mailing list
>>>> IETF-Announce@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/ietf-announce
>>>=20
>>> _______________________________________________
>>> mpls mailing list
>>> mpls@ietf.org
>>> https://www.ietf.org/mailman/listinfo/mpls
>>> _______________________________________________
>>> Ietf mailing list
>>> Ietf@ietf.org
>>> https://www.ietf.org/mailman/listinfo/ietf
>>=20
>>=20
>>=20
>> _______________________________________________
>> Ietf mailing list
>> Ietf@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf
>=20
> --=20
>=20
>=20
> 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

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf

From sm@resistor.net  Thu Mar  1 10:07:19 2012
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D032321E80D1 for <ietf@ietfa.amsl.com>; Thu,  1 Mar 2012 10:07:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.647
X-Spam-Level: 
X-Spam-Status: No, score=-102.647 tagged_above=-999 required=5 tests=[AWL=-0.048, 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 IQAaHckgb-Qu for <ietf@ietfa.amsl.com>; Thu,  1 Mar 2012 10:07:15 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id AE36A21E80C8 for <ietf@ietf.org>; Thu,  1 Mar 2012 10:07:11 -0800 (PST)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id q21I76Ae003907 for <ietf@ietf.org>; Thu, 1 Mar 2012 10:07:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1330625231; i=@resistor.net; bh=n4YMEoIC2F+2ljIR3SJ6Q52p3uqY64mvchWtkMZYP+k=; h=Message-Id:Date:To:From:Subject:In-Reply-To:References: Mime-Version:Content-Type:Cc; b=bU3hKkrH0Xb42ZnAIaWoOdPILjTPk1hlULoFvsNkZfC2Qv4Idk9FID+E71NCdCr4j A0yAJeNbX7TELsRidLyfD/vsYBH3yCcTiZA8tdNrEyA7TAgbkyuX69OcTJpkBKYy2j EDJonvtPzKBrp81fJmOMoc5ILxMc+WUiyf/YMlr0=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1330625231; i=@resistor.net; bh=n4YMEoIC2F+2ljIR3SJ6Q52p3uqY64mvchWtkMZYP+k=; h=Message-Id:Date:To:From:Subject:In-Reply-To:References: Mime-Version:Content-Type:Cc; b=1GzLpLsisEKo+FO3l/+sQWeJnB1C0C1Yb9F2wqjjXweJmmzkfkZAM73KZck19ORgx dQg+bGc7WHjtsRXBo//dwx/TU8Qa6rZZfLjraT6itEP+l80OiD23WpvkKs/Bk8X+vK sDmKc/zpekU5sh9qOc1kwuhZHE9jzTw8zUyQaqDQ=
Message-Id: <6.2.5.6.2.20120301091406.0a655e48@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 01 Mar 2012 10:00:56 -0800
To: ietf@ietf.org
From: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-ietf-marf-spf-reporting-08.txt> (SPF Authentication Failure Reporting using the Abuse Report Format) to Proposed Standard
In-Reply-To: <42925810.AtQu7N28Qf@scott-latitude-e6320>
References: <20120301004643.17274.83943.idtracker@ietfa.amsl.com> <CAC4RtVDUmcLZh4J2SvV32kNxaQcPYr1+9S9q59Kd50F4hqWaOQ@mail.gmail.com> <6.2.5.6.2.20120301064114.0a80f078@resistor.net> <42925810.AtQu7N28Qf@scott-latitude-e6320>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Mar 2012 18:07:19 -0000

At 08:53 01-03-2012, Scott Kitterman wrote:
>No.  The downref is correct.  Downrefs are allowed, but have to be reviewed
>(AIUI).  I was saying that I think the downref is safe and appropriate in this

The question would be whether the downward reference is in accordance 
with BCP 97.  It is up to the IESG to consider whether a 
non-standards track protocol which has not received full IETF review 
is in line with BCP 97.

Regards,
-sm 


From sm@resistor.net  Thu Mar  1 10:07:19 2012
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 141E821E80F0 for <ietf@ietfa.amsl.com>; Thu,  1 Mar 2012 10:07:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.647
X-Spam-Level: 
X-Spam-Status: No, score=-102.647 tagged_above=-999 required=5 tests=[AWL=-0.048, 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 wOBLrgFz9Sxd for <ietf@ietfa.amsl.com>; Thu,  1 Mar 2012 10:07:18 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 4DDD021E80CC for <ietf@ietf.org>; Thu,  1 Mar 2012 10:07:17 -0800 (PST)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id q21I76Ag003907; Thu, 1 Mar 2012 10:07:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1330625236; i=@resistor.net; bh=vlQ3LCPPFj6EsZnj85697Mbsv4BWlAAovzpJd0jHwPw=; h=Message-Id:Date:To:From:Subject:Cc:In-Reply-To:References: Mime-Version:Content-Type; b=YGaArG4JaQShp85DRFxITsLaR3zxkvBa3vRmEgmiMj1ylflUGQOHCEz2U+r6G6q5c tAF4648+GoDu7Qfa5/F58IGqn6FzeBz8/QS7/m2fMH0NF/tqq8RPYbeR6It5oQ89Fn udXFFYvnqY0Epneapm6mMA4rzYQEd8Dcufsyd0a0=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1330625236; i=@resistor.net; bh=vlQ3LCPPFj6EsZnj85697Mbsv4BWlAAovzpJd0jHwPw=; h=Message-Id:Date:To:From:Subject:Cc:In-Reply-To:References: Mime-Version:Content-Type; b=TqAVQmDkkU5IsY4pjyL8K4W9FKkAfVmvS9q191Kj2snliYPG+l0Yz718d5RwotGeF nx7wP7T2a50HLfcMn9BT2VTXbYNr75uhHtpiqVwerXcxYp9qSiGsEICNR4mkr0xDVQ 7vMoiK3rP6zsrhY3mjG1pYiB1Al4brnU3QyjF5X0=
Message-Id: <6.2.5.6.2.20120301100242.0a6565f8@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 01 Mar 2012 10:05:19 -0800
To: IETF discussion list <ietf@ietf.org>
From: SM <sm@resistor.net>
Subject: Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
In-Reply-To: <4F4FB6E9.6020201@stpeter.im>
References: <20120221181006.43AB121F87BF@ietfa.amsl.com> <4F4FB6E9.6020201@stpeter.im>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: mnot@mnot.net, ietf-http-wg@w3.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Mar 2012 18:07:19 -0000

At 09:50 01-03-2012, Peter Saint-Andre wrote:
>Stephen and I just had a chat about this matter. He and I came up with a
>proposed paragraph to add after that list of bullet points:
>
>    In the initial phase of work on HTTP/2.0, new proposals
>    for authentication schemes can be made.  The WG will
>    select zero or more of those with a goal of choosing
>    at least one scheme that is better than those available
>    for HTTP/1.x.  Non-selected schemes might be discussed
>    with the IETF Security Area for further work there.

If the WG selects zero, how can it meet the goal of choosing at least 
one scheme?

Regards,
-sm 


From dhc@dcrocker.net  Thu Mar  1 10:18:57 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 9E17C21F8A29 for <ietf@ietfa.amsl.com>; Thu,  1 Mar 2012 10:18:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.608
X-Spam-Level: 
X-Spam-Status: No, score=-6.608 tagged_above=-999 required=5 tests=[AWL=-0.009, 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 0u-FqkJGopAE for <ietf@ietfa.amsl.com>; Thu,  1 Mar 2012 10:18:57 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 1CCDA21F8A10 for <ietf@ietf.org>; Thu,  1 Mar 2012 10:18:57 -0800 (PST)
Received: from [192.168.1.11] (adsl-67-127-58-62.dsl.pltn13.pacbell.net [67.127.58.62]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q21IIpbu027933 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Thu, 1 Mar 2012 10:18:56 -0800
Message-ID: <4F4FBD88.4000006@dcrocker.net>
Date: Thu, 01 Mar 2012 10:18:48 -0800
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Last Call: <draft-ietf-marf-spf-reporting-08.txt> (SPF Authentication Failure Reporting using the Abuse Report Format) to Proposed Standard
References: <20120301004643.17274.83943.idtracker@ietfa.amsl.com> <6.2.5.6.2.20120229181328.0a95a9f8@resistor.net> <8066871.IkNuLJFsLQ@scott-latitude-e6320>
In-Reply-To: <8066871.IkNuLJFsLQ@scott-latitude-e6320>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Thu, 01 Mar 2012 10:18:57 -0800 (PST)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Mar 2012 18:18:57 -0000

On 3/1/2012 6:22 AM, Scott Kitterman wrote:
> I don't think it's efficient at all to put this draft on hold and revive it
> later for non-technical reasons.


+1

d/
-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From john-ietf@jck.com  Thu Mar  1 10:29:01 2012
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0E7D021E8116 for <ietf@ietfa.amsl.com>; Thu,  1 Mar 2012 10:29:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.861
X-Spam-Level: 
X-Spam-Status: No, score=-102.861 tagged_above=-999 required=5 tests=[AWL=-0.262, 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 aVVO9WOEUl-Y for <ietf@ietfa.amsl.com>; Thu,  1 Mar 2012 10:29:00 -0800 (PST)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 9E0DD21E815A for <ietf@ietf.org>; Thu,  1 Mar 2012 10:28:56 -0800 (PST)
Received: from [198.252.137.7] (helo=PST.JCK.COM) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1S3Afv-000MVG-L2; Thu, 01 Mar 2012 13:24:23 -0500
Date: Thu, 01 Mar 2012 13:28:44 -0500
From: John C Klensin <john-ietf@jck.com>
To: Russ Housley <housley@vigilsec.com>, Loa Andersson <loa@pi.nu>
Subject: Re: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt>	(Allocation of an Associated Channel Code Point for Use by	ITU-T Ethernet based OAM) to Informational RFC
Message-ID: <BD60EA38ED03AF5A21868DF1@PST.JCK.COM>
In-Reply-To: <D0F60388-D852-4815-917A-B14BF40C64FB@vigilsec.com>
References: <20120222151252.32262.82157.idtracker@ietfa.amsl.com> <03a301ccf174$ff953290$febf97b0$@olddog.co.uk> <515703B08A3A064C9CC8C09ACCC710DC0631679E@XMB-RCD-103.cisco.com> <C71DA9B1-A61F-4C5D-8DCE-3702271CBB6D@vigilsec.com> <4F4FA70B.2030906@pi.nu> <D0F60388-D852-4815-917A-B14BF40C64FB@vigilsec.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Mar 2012 18:29:02 -0000

--On Thursday, March 01, 2012 13:02 -0500 Russ Housley
<housley@vigilsec.com> wrote:

> Loa:
> 
> Right now, there is no ITU-T approved document to reference.
> I am certainly not an expert on ITU-T process, but my
> understanding is that earliest that we could see an approved
> G.8113.1 is December 2012.  My point is that we don't want to
> assign a code point until the ITU-T approves their document.
> However, if we are willing to assign a code point to G.8113.1
> once it is approved, then this would be an approach where the
> code point assignment would block on the approval of the
> normative reference.
> 
> I like this approach from the political point of view.  With
> this approach the IETF tells the ITU-T that if and only if
> they are able to achieve consensus on G.8113.1, then a code
> point will be assigned.

FWIW, this seems entirely appropriate to me.  If we do it this
way, I think it is important to note --for the benefit of those
more historically involved with the ITU and others-- that we
routinely block our own documents on normative references to
work that is still in progress and, usually, do not do related
code point allocations until the blocking referenced documents
are ready.  Once the present I-D is judged to be sufficiently
ready, this approach would therefore be IETF approval and a
formal guarantee to the ITU that a code point will be allocated
if an when G.8113.1 is approved and published, but not
assignment of that code point until the referenced base document
is finished.  

Completely normal procedurally.
 
   john





From nurit.sprecher@nsn.com  Thu Mar  1 10:34:16 2012
Return-Path: <nurit.sprecher@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 4F27621F8AEB for <ietf@ietfa.amsl.com>; Thu,  1 Mar 2012 10:34:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.544
X-Spam-Level: 
X-Spam-Status: No, score=-6.544 tagged_above=-999 required=5 tests=[AWL=0.055,  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 TD4Qa4hDUW61 for <ietf@ietfa.amsl.com>; Thu,  1 Mar 2012 10:34:15 -0800 (PST)
Received: from demumfd002.nsn-inter.net (demumfd002.nsn-inter.net [93.183.12.31]) by ietfa.amsl.com (Postfix) with ESMTP id 6B1E321F8AE7 for <ietf@ietf.org>; Thu,  1 Mar 2012 10:34:06 -0800 (PST)
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 q21IY5Wn027089 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 1 Mar 2012 19:34:05 +0100
Received: from DEMUEXC048.nsn-intra.net ([10.159.32.94]) by demuprx017.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id q21IY4Vi019794; Thu, 1 Mar 2012 19:34:05 +0100
Received: from DEMUEXC013.nsn-intra.net ([10.150.128.24]) by DEMUEXC048.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 1 Mar 2012 19:34:03 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt>(Allocationof an Associated Channel Code Point for Use byITU-T Ethernetbased OAM) to Informational RFC
Date: Thu, 1 Mar 2012 19:34:01 +0100
Message-ID: <E4873516F3FC7547BCFE792C7D94039C015D1241@DEMUEXC013.nsn-intra.net>
In-Reply-To: <E4873516F3FC7547BCFE792C7D94039C015D1238@DEMUEXC013.nsn-intra.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt>(Allocationof an Associated Channel Code Point for Use byITU-T Ethernetbased OAM) to Informational RFC
Thread-Index: Acz31X24pPa5eT3ZQTy+0WoRj780FgAAGwUwAADuAOA=
References: <20120222151252.32262.82157.idtracker@ietfa.amsl.com><03a301ccf174$ff953290$febf97b0$@olddog.co.uk><515703B08A3A064C9CC8C09ACCC710DC0631679E@XMB-RCD-103.cisco.com><C71DA9B1-A61F-4C5D-8DCE-3702271CBB6D@vigilsec.com><4F4FA70B.2030906@pi.nu><D0F60388-D852-4815-917A-B14BF40C64FB@vigilsec.com> <E4873516F3FC7547BCFE792C7D94039C015D1238@DEMUEXC013.nsn-intra.net>
From: "Sprecher, Nurit (NSN - IL/Hod HaSharon)" <nurit.sprecher@nsn.com>
To: "Sprecher, Nurit (NSN - IL/Hod HaSharon)" <nurit.sprecher@nsn.com>, "ext Russ Housley" <housley@vigilsec.com>, "Loa Andersson" <loa@pi.nu>
X-OriginalArrivalTime: 01 Mar 2012 18:34:03.0422 (UTC) FILETIME=[E08D43E0:01CCF7D9]
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: 8388
X-purgate-ID: 151667::1330626845-000033AC-9836D2AE/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, 01 Mar 2012 18:34:16 -0000

To make sure that my concerns are not missed, I attach them:

--
Hi,

I cannot support the publication of the document in its current version.

I have the following concerns:

*	It is indicated that the channel is intended to be used to carry
Ethernet based OAM messages. It is not clear why there is a need for
ACH. PWs can be used to transmit Ethernet OAM.=20
If the intention is to use the channel for OAM messages for operating
MPLS-TP based networks, the IETF *already* defined a solution for
MPLS-TP OAM and I expect to see first a technical *justification* why a
second solution is needed. In addition, I would expect to see
*references to the arguments* raised in
draft-sprecher-mpls-tp-oam-considerations.=20

*	It is not clear what the maturity status of G.8113.1 is. It
seems that the document was not approved by SG15 and the discussion was
deferred to WTSA. This indicates that there is *no consensus* for the
approval of G.8113.1. A code point should not be allocated before a
consensus/decision is reached in the ITU-T and before the document is
mature and approved. I do not think it is appropriate to allocate a code
point and try to force a resolution in the ITU-T.=20

*	I find a contradiction in the draft. In one place it is
mentioned: "These Ethernet based OAM messages and procedures, address
the OAM functional requirements defined in [RFC5860]. Other message
types should not be carried behind this code point." In another place it
is mentioned: "all ITU-T Recommendations are subject to revision.
Therefore, the code point allocated by this document may be used for
future versions of [G.8113.1].". The last statement opens the door for
the definition of additional messages in G.8113.1 in the following
versions, for example, for APS (supporting linear or ring protection
mechanisms) and by this creates two solutions for other mechanisms as
well.=20

The use of the code point can go much beyond its original purpose and it
will hide other messages....a code point should not be allocated at this
point at all, but specifically not for unknown usage that may be defined
in future versions of G.8113.1.=20

Best regards,
Nurit
---


-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
Sprecher, Nurit (NSN - IL/Hod HaSharon)
Sent: Thursday, March 01, 2012 8:07 PM
To: ext Russ Housley; Loa Andersson
Cc: ietf@ietf.org
Subject: RE: Last Call:
<draft-betts-itu-oam-ach-code-point-03.txt>(Allocationof an Associated
Channel Code Point for Use byITU-T Ethernetbased OAM) to Informational
RFC

Russ,
Independently of that point, draft-betts in its current version has many
issues....
Many clarifications are needed before it can be considered....please see
my mail for the details.
Best regards,
Nurit


-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
ext Russ Housley
Sent: Thursday, March 01, 2012 8:02 PM
To: Loa Andersson
Cc: ietf@ietf.org
Subject: Re: Last Call:
<draft-betts-itu-oam-ach-code-point-03.txt>(Allocation of an Associated
Channel Code Point for Use byITU-T Ethernet based OAM) to Informational
RFC

Loa:

Right now, there is no ITU-T approved document to reference.   I am
certainly not an expert on ITU-T process, but my understanding is that
earliest that we could see an approved G.8113.1 is December 2012.  My
point is that we don't want to assign a code point until the ITU-T
approves their document.  However, if we are willing to assign a code
point to G.8113.1 once it is approved, then this would be an approach
where the code point assignment would block on the approval of the
normative reference.

I like this approach from the political point of view.  With this
approach the IETF tells the ITU-T that if and only if they are able to
achieve consensus on G.8113.1, then a code point will be assigned.

Russ


On Mar 1, 2012, at 11:42 AM, Loa Andersson wrote:

> Russ,
>=20
> I'm not KY, but I feel that your question is a bit loaded.
>=20
> Certainly if the document is reviewed and approved by the IETF/IESG
> it would be no problem to support the assignment of a ACh Type.
>=20
> But I can't see that approval by some other instance actually carry
> the same merit - so exactly what do u mean by "approved G.8113.1"?
>=20
> /Loa
>=20
> On 2012-03-01 17:06, Russ Housley wrote:
>> KY:
>>=20
>> Would you support the assignment to an approved G.8113.1?  That is,
if the document contained a normative reference to the approved
G.8113.1, then the document that makes the code point allocations would
sit in the RFC Editor queue until the ITU-T reaches consensus and
approves G.8113.1.
>>=20
>> Russ
>>=20
>>=20
>> On Mar 1, 2012, at 10:14 AM, Kyung-Yeop Hong (hongk) wrote:
>>=20
>>> No/do not support.
>>>=20
>>> One of the issues with G.8113.1 in LS370 is its stability and
maturity.
>>> That was one of the reasons why it was not approved.
>>>=20
>>> The Ethernet based OAM protocol documented in the LS370 version is
>>> intended to be deployed for MPLS networks. I think the IETF has a
duty
>>> to ensure that a solution is stable and works for MPLS networks
before
>>> the code point allocation. A number of concerns with the deployment
of
>>> this proposed protocol raised in
>>> draft-spercher-mpls-tp-oam-considerations are critical to the
Internet
>>> and must be taken into consideration in this Last Call.
>>>=20
>>> KY
>>>=20
>>>=20
>>>> -----Original Message-----
>>>> From: ietf-announce-bounces@ietf.org [mailto:ietf-announce-
>>>> bounces@ietf.org] On Behalf Of The IESG
>>>> Sent: 22 February 2012 15:13
>>>> To: IETF-Announce
>>>> Subject: Last Call:<draft-betts-itu-oam-ach-code-point-03.txt>
>>> (Allocation of
>>> an
>>>> Associated Channel Code Point for Use by ITU-T Ethernet based OAM)
to
>>>> Informational RFC
>>>>=20
>>>>=20
>>>> The IESG has received a request from an individual submitter to
>>> consider
>>>> the following document:
>>>> - 'Allocation of an Associated Channel Code Point for Use by ITU-T
>>>>   Ethernet based OAM'
>>>>  <draft-betts-itu-oam-ach-code-point-03.txt>  as an Informational
RFC
>>>>=20
>>>> The IESG plans to make a decision in the next few weeks, and
solicits
>>>> final comments on this action. Please send substantive comments to
the
>>>> ietf@ietf.org mailing lists by 2012-03-21. Exceptionally, comments
may
>>> be
>>>> sent to iesg@ietf.org instead. In either case, please retain the
>>>> beginning of the Subject line to allow automated sorting.
>>>>=20
>>>> Abstract
>>>>=20
>>>>   This document assigns an Associated Channel Type code point for
>>>>   carrying Ethernet based Operations, Administration, and
Management
>>>>   messages in the MPLS Generic Associated Channel (G-ACh).
>>>>=20
>>>> The file can be obtained via
>>>> http://datatracker.ietf.org/doc/draft-betts-itu-oam-ach-code-point/
>>>>=20
>>>> IESG discussion can be tracked via
>>>> http://datatracker.ietf.org/doc/draft-betts-itu-oam-ach-code-point/
>>>>=20
>>>>=20
>>>> No IPR declarations have been submitted directly on this I-D.
>>>> _______________________________________________
>>>> IETF-Announce mailing list
>>>> IETF-Announce@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/ietf-announce
>>>=20
>>> _______________________________________________
>>> mpls mailing list
>>> mpls@ietf.org
>>> https://www.ietf.org/mailman/listinfo/mpls
>>> _______________________________________________
>>> Ietf mailing list
>>> Ietf@ietf.org
>>> https://www.ietf.org/mailman/listinfo/ietf
>>=20
>>=20
>>=20
>> _______________________________________________
>> Ietf mailing list
>> Ietf@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf
>=20
> --=20
>=20
>=20
> 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

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf
_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf

From msk@cloudmark.com  Thu Mar  1 10:35:14 2012
Return-Path: <msk@cloudmark.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 46CC321F87E8 for <ietf@ietfa.amsl.com>; Thu,  1 Mar 2012 10:35:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.604
X-Spam-Level: 
X-Spam-Status: No, score=-102.604 tagged_above=-999 required=5 tests=[AWL=-0.005, 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 XxMvnA1ELCy1 for <ietf@ietfa.amsl.com>; Thu,  1 Mar 2012 10:35:13 -0800 (PST)
Received: from ht1-outbound.cloudmark.com (ht1-outbound.cloudmark.com [72.5.239.25]) by ietfa.amsl.com (Postfix) with ESMTP id 7DAF821E81A9 for <ietf@ietf.org>; Thu,  1 Mar 2012 10:34:47 -0800 (PST)
Received: from EXCH-MBX901.corp.cloudmark.com ([fe80::addf:849a:f71c:4a82]) by EXCH-HTCAS901.corp.cloudmark.com ([fe80::2966:6846:8d89:4681%12]) with mapi id 14.01.0355.002; Thu, 1 Mar 2012 10:34:46 -0800
From: "Murray S. Kucherawy" <msk@cloudmark.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: Last Call: <draft-ietf-marf-spf-reporting-08.txt> (SPF Authentication Failure Reporting using the Abuse Report Format) to	Proposed Standard
Thread-Topic: Last Call: <draft-ietf-marf-spf-reporting-08.txt> (SPF Authentication Failure Reporting using the Abuse Report Format) to	Proposed Standard
Thread-Index: AQHM99Y+lvZJpgPRRE2+OZ8SlMVN2pZVvoWQ
Date: Thu, 1 Mar 2012 18:34:46 +0000
Message-ID: <9452079D1A51524AA5749AD23E00392806F808@exch-mbx901.corp.cloudmark.com>
References: <20120301004643.17274.83943.idtracker@ietfa.amsl.com> <CAC4RtVDUmcLZh4J2SvV32kNxaQcPYr1+9S9q59Kd50F4hqWaOQ@mail.gmail.com> <6.2.5.6.2.20120301064114.0a80f078@resistor.net> <42925810.AtQu7N28Qf@scott-latitude-e6320> <6.2.5.6.2.20120301091406.0a655e48@resistor.net>
In-Reply-To: <6.2.5.6.2.20120301091406.0a655e48@resistor.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.20.2.121]
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, 01 Mar 2012 18:35:14 -0000

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of S=
M
> Sent: Thursday, March 01, 2012 10:01 AM
> To: ietf@ietf.org
> Subject: Re: Last Call: <draft-ietf-marf-spf-reporting-08.txt> (SPF
> Authentication Failure Reporting using the Abuse Report Format) to
> Proposed Standard
>=20
> At 08:53 01-03-2012, Scott Kitterman wrote:
> >No.  The downref is correct.  Downrefs are allowed, but have to be
> >reviewed (AIUI).  I was saying that I think the downref is safe and
> >appropriate in this
>=20
> The question would be whether the downward reference is in accordance
> with BCP 97.  It is up to the IESG to consider whether a non-standards
> track protocol which has not received full IETF review is in line with
> BCP 97.

The citation you made from BCP 97 says that the standard needs to be clear =
and interoperable.  In this case, BCP 97 applies to the document under eval=
uation, not to RFC4408, as the latter is Experimental.

The specification contained in RFC4408 has flaws that have long been acknow=
ledged and some new ones that have recently come to light, but despite thes=
e it is operationally stable and its output is deterministic, resulting in =
widespread deployment and numerous interoperating implementations.  Given t=
hat, I don't believe the proposed standard under consideration fails to mee=
t the requirements of BCP 97.

If and when the spfbis working group produces an update that fixes RFC4408,=
 and/or new versions of SPF come out that actually alter the output of SPF,=
 an update to this document that accommodates those changes could be made t=
o keep them aligned, as Barry has already pointed out.

-MSK


From nurit.sprecher@nsn.com  Thu Mar  1 10:39:08 2012
Return-Path: <nurit.sprecher@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 00F1E21E8192 for <ietf@ietfa.amsl.com>; Thu,  1 Mar 2012 10:39:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.545
X-Spam-Level: 
X-Spam-Status: No, score=-6.545 tagged_above=-999 required=5 tests=[AWL=0.054,  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 FlrGoH+3PSzS for <ietf@ietfa.amsl.com>; Thu,  1 Mar 2012 10:39:07 -0800 (PST)
Received: from demumfd001.nsn-inter.net (demumfd001.nsn-inter.net [93.183.12.32]) by ietfa.amsl.com (Postfix) with ESMTP id E58D821F8A3C for <ietf@ietf.org>; Thu,  1 Mar 2012 10:39:06 -0800 (PST)
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 q21Id1nZ031872 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 1 Mar 2012 19:39:01 +0100
Received: from DEMUEXC048.nsn-intra.net ([10.159.32.94]) by demuprx017.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id q21Id0US029282; Thu, 1 Mar 2012 19:39:01 +0100
Received: from DEMUEXC013.nsn-intra.net ([10.150.128.24]) by DEMUEXC048.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 1 Mar 2012 19:38:59 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Last Call:<draft-betts-itu-oam-ach-code-point-03.txt>	(Allocation of anAssociated Channel Code Point for Use by	ITU-T Ethernet basedOAM) to Informational RFC
Date: Thu, 1 Mar 2012 19:38:58 +0100
Message-ID: <E4873516F3FC7547BCFE792C7D94039C015D1244@DEMUEXC013.nsn-intra.net>
In-Reply-To: <BD60EA38ED03AF5A21868DF1@PST.JCK.COM>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Last Call:<draft-betts-itu-oam-ach-code-point-03.txt>	(Allocation of anAssociated Channel Code Point for Use by	ITU-T Ethernet basedOAM) to Informational RFC
Thread-Index: Acz32UJhst7Xa8MMSJKgKc/dXohXDgAALeow
References: <20120222151252.32262.82157.idtracker@ietfa.amsl.com><03a301ccf174$ff953290$febf97b0$@olddog.co.uk><515703B08A3A064C9CC8C09ACCC710DC0631679E@XMB-RCD-103.cisco.com><C71DA9B1-A61F-4C5D-8DCE-3702271CBB6D@vigilsec.com><4F4FA70B.2030906@pi.nu><D0F60388-D852-4815-917A-B14BF40C64FB@vigilsec.com> <BD60EA38ED03AF5A21868DF1@PST.JCK.COM>
From: "Sprecher, Nurit (NSN - IL/Hod HaSharon)" <nurit.sprecher@nsn.com>
To: "ext John C Klensin" <john-ietf@jck.com>, "Russ Housley" <housley@vigilsec.com>, "Loa Andersson" <loa@pi.nu>
X-OriginalArrivalTime: 01 Mar 2012 18:38:59.0642 (UTC) FILETIME=[911CD9A0:01CCF7DA]
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: 2607
X-purgate-ID: 151667::1330627141-000044A2-C0A71C64/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, 01 Mar 2012 18:39:08 -0000

Draft-betts asks a code point for a document which is not mature and not
agreed yet. Usually we do not issue last call for a document in such a
condition!
And in addition, draft-betts has many issues that must be resolved
first.=20
For example it must be clear for what the code point is requested.
Draft-betts indicates that G.8113.1 is subjected to revisions...they may
add more messages to G.8113.1 that will be hidden behind the code point,
etc. =20

-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
ext John C Klensin
Sent: Thursday, March 01, 2012 8:29 PM
To: Russ Housley; Loa Andersson
Cc: ietf@ietf.org
Subject: Re: Last Call:<draft-betts-itu-oam-ach-code-point-03.txt>
(Allocation of anAssociated Channel Code Point for Use by ITU-T Ethernet
basedOAM) to Informational RFC



--On Thursday, March 01, 2012 13:02 -0500 Russ Housley
<housley@vigilsec.com> wrote:

> Loa:
>=20
> Right now, there is no ITU-T approved document to reference.
> I am certainly not an expert on ITU-T process, but my
> understanding is that earliest that we could see an approved
> G.8113.1 is December 2012.  My point is that we don't want to
> assign a code point until the ITU-T approves their document.
> However, if we are willing to assign a code point to G.8113.1
> once it is approved, then this would be an approach where the
> code point assignment would block on the approval of the
> normative reference.
>=20
> I like this approach from the political point of view.  With
> this approach the IETF tells the ITU-T that if and only if
> they are able to achieve consensus on G.8113.1, then a code
> point will be assigned.

FWIW, this seems entirely appropriate to me.  If we do it this
way, I think it is important to note --for the benefit of those
more historically involved with the ITU and others-- that we
routinely block our own documents on normative references to
work that is still in progress and, usually, do not do related
code point allocations until the blocking referenced documents
are ready.  Once the present I-D is judged to be sufficiently
ready, this approach would therefore be IETF approval and a
formal guarantee to the ITU that a code point will be allocated
if an when G.8113.1 is approved and published, but not
assignment of that code point until the referenced base document
is finished. =20

Completely normal procedurally.
=20
   john




_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf

From stbryant@cisco.com  Thu Mar  1 10:39:18 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 0611A21E819C for <ietf@ietfa.amsl.com>; Thu,  1 Mar 2012 10:39:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.577
X-Spam-Level: 
X-Spam-Status: No, score=-110.577 tagged_above=-999 required=5 tests=[AWL=0.022, 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 3LpWFet8e8sP for <ietf@ietfa.amsl.com>; Thu,  1 Mar 2012 10:39:17 -0800 (PST)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by ietfa.amsl.com (Postfix) with ESMTP id 318B921E81B6 for <ietf@ietf.org>; Thu,  1 Mar 2012 10:39:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=stbryant@cisco.com; l=2041; q=dns/txt; s=iport; t=1330627157; x=1331836757; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=kqfCys3cxHf48/ZZSzTN/g1A1ti9QdCw9GkZ+D7fEj0=; b=ckeyfiosRNx7HiFLssaGs0vWWsIjJ2KGHFi45E0gviaRW/uqFZakJNXa 2zyOGGicsGY961KnJ+Xf1hTTDDHuTbJinGiq+l37NbMQcEpQ/NzmuZlo/ DXbeao7okorADm1PhGeXySYz2lXAzJZWFYgpQBMp2Nc5MiGLGKKkzx1il Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAP3BT0+Q/khL/2dsb2JhbABDtAKBB4F9AQEBBBIBAgEiMw0BEAsYCRYECwkDAgECAUUGDQEFAgEBEA6HZJlVAYMxDwGbKo0hBgsCAgcGBAMEAwgECgcPAQoJAoUCDwcBAQYCBQEBBAELCw4Vg0UEkV2DXpJy
X-IronPort-AV: E=Sophos;i="4.73,512,1325462400"; d="scan'208";a="131095752"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by ams-iport-1.cisco.com with ESMTP; 01 Mar 2012 18:39:16 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by ams-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id q21IdGtn018451; Thu, 1 Mar 2012 18:39:16 GMT
Received: from dhcp-bdlk10-data-vlan300-64-103-107-132.cisco.com (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id q21IdEpc015788; Thu, 1 Mar 2012 18:39:15 GMT
Message-ID: <4F4FC252.9010001@cisco.com>
Date: Thu, 01 Mar 2012 18:39:14 +0000
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
Subject: Re: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt>	(Allocation of an Associated Channel Code Point for Use by	ITU-T Ethernet based OAM) to Informational RFC
References: <20120222151252.32262.82157.idtracker@ietfa.amsl.com> <03a301ccf174$ff953290$febf97b0$@olddog.co.uk> <515703B08A3A064C9CC8C09ACCC710DC0631679E@XMB-RCD-103.cisco.com> <C71DA9B1-A61F-4C5D-8DCE-3702271CBB6D@vigilsec.com> <4F4FA70B.2030906@pi.nu> <D0F60388-D852-4815-917A-B14BF40C64FB@vigilsec.com> <BD60EA38ED03AF5A21868DF1@PST.JCK.COM>
In-Reply-To: <BD60EA38ED03AF5A21868DF1@PST.JCK.COM>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Mar 2012 18:39:18 -0000

On 01/03/2012 18:28, John C Klensin wrote:
>
> --On Thursday, March 01, 2012 13:02 -0500 Russ Housley
> <housley@vigilsec.com>  wrote:
>
>> Loa:
>>
>> Right now, there is no ITU-T approved document to reference.
>> I am certainly not an expert on ITU-T process, but my
>> understanding is that earliest that we could see an approved
>> G.8113.1 is December 2012.  My point is that we don't want to
>> assign a code point until the ITU-T approves their document.
>> However, if we are willing to assign a code point to G.8113.1
>> once it is approved, then this would be an approach where the
>> code point assignment would block on the approval of the
>> normative reference.
>>
>> I like this approach from the political point of view.  With
>> this approach the IETF tells the ITU-T that if and only if
>> they are able to achieve consensus on G.8113.1, then a code
>> point will be assigned.
> FWIW, this seems entirely appropriate to me.  If we do it this
> way, I think it is important to note --for the benefit of those
> more historically involved with the ITU and others-- that we
> routinely block our own documents on normative references to
> work that is still in progress and, usually, do not do related
> code point allocations until the blocking referenced documents
> are ready.  Once the present I-D is judged to be sufficiently
> ready, this approach would therefore be IETF approval and a
> formal guarantee to the ITU that a code point will be allocated
> if an when G.8113.1 is approved and published, but not
> assignment of that code point until the referenced base document
> is finished.
>
> Completely normal procedurally.
>
>     john
>
>
To be clear John our normal requirement would be that the
technical community achieved consensus that the base document
was ready. I have never seen ITU-T consensus on the contents
of G.8113.1 at any meeting that I have observed. What in your
view is the criteria for determining that  G.8113.1 has achieved
consensus?

Stewart



From stpeter@stpeter.im  Thu Mar  1 10:40:59 2012
Return-Path: <stpeter@stpeter.im>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8DD6C21E813B for <ietf@ietfa.amsl.com>; Thu,  1 Mar 2012 10:40:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.699
X-Spam-Level: 
X-Spam-Status: No, score=-102.699 tagged_above=-999 required=5 tests=[AWL=-0.100, 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 wKk3yyV6Jdwl for <ietf@ietfa.amsl.com>; Thu,  1 Mar 2012 10:40:58 -0800 (PST)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 9DB6421F8A2A for <ietf@ietf.org>; Thu,  1 Mar 2012 10:40:58 -0800 (PST)
Received: from squire.local (unknown [64.101.72.114]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id F0F204009B; Thu,  1 Mar 2012 11:52:38 -0700 (MST)
Message-ID: <4F4FC2B9.7030304@stpeter.im>
Date: Thu, 01 Mar 2012 11:40:57 -0700
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.5; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: SM <sm@resistor.net>
Subject: Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
References: <20120221181006.43AB121F87BF@ietfa.amsl.com> <4F4FB6E9.6020201@stpeter.im> <6.2.5.6.2.20120301100242.0a6565f8@resistor.net>
In-Reply-To: <6.2.5.6.2.20120301100242.0a6565f8@resistor.net>
X-Enigmail-Version: 1.3.5
OpenPGP: url=https://stpeter.im/stpeter.asc
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: mnot@mnot.net, IETF discussion list <ietf@ietf.org>, ietf-http-wg@w3.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Mar 2012 18:40:59 -0000

On 3/1/12 11:05 AM, SM wrote:
> At 09:50 01-03-2012, Peter Saint-Andre wrote:
>> Stephen and I just had a chat about this matter. He and I came up with a
>> proposed paragraph to add after that list of bullet points:
>>
>>    In the initial phase of work on HTTP/2.0, new proposals
>>    for authentication schemes can be made.  The WG will
>>    select zero or more of those with a goal of choosing
>>    at least one scheme that is better than those available
>>    for HTTP/1.x.  Non-selected schemes might be discussed
>>    with the IETF Security Area for further work there.
> 
> If the WG selects zero, how can it meet the goal of choosing at least
> one scheme?

One can have a goal of choosing a scheme that's better, but if no one
proposes any or none of the selected schemes are deemed better, then we
will not achieve the goal. Perhaps that thought could be worded more
clearly.

Peter

-- 
Peter Saint-Andre
https://stpeter.im/



From msk@cloudmark.com  Thu Mar  1 10:41:45 2012
Return-Path: <msk@cloudmark.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A5A2D21E81D1 for <ietf@ietfa.amsl.com>; Thu,  1 Mar 2012 10:41:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.604
X-Spam-Level: 
X-Spam-Status: No, score=-102.604 tagged_above=-999 required=5 tests=[AWL=-0.005, 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 z8Q8dn3F3sNH for <ietf@ietfa.amsl.com>; Thu,  1 Mar 2012 10:41:45 -0800 (PST)
Received: from ht1-outbound.cloudmark.com (ht1-outbound.cloudmark.com [72.5.239.25]) by ietfa.amsl.com (Postfix) with ESMTP id 42C6A21F8A2A for <ietf@ietf.org>; Thu,  1 Mar 2012 10:41:45 -0800 (PST)
Received: from EXCH-MBX901.corp.cloudmark.com ([fe80::addf:849a:f71c:4a82]) by EXCH-HTCAS901.corp.cloudmark.com ([fe80::2966:6846:8d89:4681%12]) with mapi id 14.01.0355.002; Thu, 1 Mar 2012 10:41:44 -0800
From: "Murray S. Kucherawy" <msk@cloudmark.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: Last Call: <draft-ietf-marf-spf-reporting-08.txt> (SPF Authentication Failure Reporting using the Abuse Report Format)	to Proposed Standard
Thread-Topic: Last Call: <draft-ietf-marf-spf-reporting-08.txt> (SPF Authentication Failure Reporting using the Abuse Report Format)	to Proposed Standard
Thread-Index: AQHM97a/9M4Lu1B6hUu7l1FIO6oAmZZVxllA
Date: Thu, 1 Mar 2012 18:41:44 +0000
Message-ID: <9452079D1A51524AA5749AD23E00392806F83F@exch-mbx901.corp.cloudmark.com>
References: <20120301004643.17274.83943.idtracker@ietfa.amsl.com> <6.2.5.6.2.20120229181328.0a95a9f8@resistor.net> <8066871.IkNuLJFsLQ@scott-latitude-e6320>
In-Reply-To: <8066871.IkNuLJFsLQ@scott-latitude-e6320>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.20.2.121]
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, 01 Mar 2012 18:41:45 -0000

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of S=
cott Kitterman
> Sent: Thursday, March 01, 2012 6:22 AM
> To: ietf@ietf.org
> Subject: Re: Last Call: <draft-ietf-marf-spf-reporting-08.txt> (SPF
> Authentication Failure Reporting using the Abuse Report Format) to
> Proposed Standard
>=20
> I don't think it's efficient at all to put this draft on hold and
> revive it later for non-technical reasons.

+1.

-MSK



From stpeter@stpeter.im  Thu Mar  1 10:43:49 2012
Return-Path: <stpeter@stpeter.im>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E0BA21E81E6; Thu,  1 Mar 2012 10:43:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.739
X-Spam-Level: 
X-Spam-Status: No, score=-102.739 tagged_above=-999 required=5 tests=[AWL=-0.140, 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 mAW9HZ8-ktOq; Thu,  1 Mar 2012 10:43:48 -0800 (PST)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id C091521F8A2A; Thu,  1 Mar 2012 10:43:48 -0800 (PST)
Received: from squire.local (unknown [64.101.72.114]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 1090D4009B; Thu,  1 Mar 2012 11:55:28 -0700 (MST)
Message-ID: <4F4FC363.4030802@stpeter.im>
Date: Thu, 01 Mar 2012 11:43:47 -0700
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.5; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: Nick Hilliard <nick@inex.ie>
Subject: Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
References: <20120221181006.43AB121F87BF@ietfa.amsl.com> <4F4FB6E9.6020201@stpeter.im> <4F4FB97C.2080600@inex.ie>
In-Reply-To: <4F4FB97C.2080600@inex.ie>
X-Enigmail-Version: 1.3.5
OpenPGP: url=https://stpeter.im/stpeter.asc
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: mnot@mnot.net, IETF discussion list <ietf@ietf.org>, iesg@ietf.org, ietf-http-wg@w3.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Mar 2012 18:43:49 -0000

[ no hat ]

On 3/1/12 11:01 AM, Nick Hilliard wrote:
> On 01/03/2012 17:50, Peter Saint-Andre wrote:
>> Stephen and I just had a chat about this matter. He and I came up with a
>> proposed paragraph to add after that list of bullet points:
>>
>>    In the initial phase of work on HTTP/2.0, new proposals
>>    for authentication schemes can be made.  The WG will
>>    select zero or more of those with a goal of choosing
>>    at least one scheme that is better than those available
>>    for HTTP/1.x.  Non-selected schemes might be discussed
>>    with the IETF Security Area for further work there.
>>
>> Your comments are welcome.
> 
> Can I suggest you also include authorization capabilities as a core
> component of this. It's not much use to have people able to authenticate
> themselves to a system if that system doesn't also provide a framework for
> allowing the server-side application decide what they can or cannot do.

Feel free to include that in your proposal. :)

Peter

-- 
Peter Saint-Andre
https://stpeter.im/



From hongk@cisco.com  Thu Mar  1 10:47:32 2012
Return-Path: <hongk@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 A06F621E820A for <ietf@ietfa.amsl.com>; Thu,  1 Mar 2012 10:47:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oAT2WuDIZC29 for <ietf@ietfa.amsl.com>; Thu,  1 Mar 2012 10:47:31 -0800 (PST)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) by ietfa.amsl.com (Postfix) with ESMTP id ACA6D21E8202 for <ietf@ietf.org>; Thu,  1 Mar 2012 10:47:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=hongk@cisco.com; l=3947; q=dns/txt; s=iport; t=1330627651; x=1331837251; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=WluPtiYmjqEsa3VWi5LTGvaSYYSzXRA+4PGWkT0BgJI=; b=GDhGJXbe17P93iCKBG7dLBJ8zjXkrXDmyLsF0Hh9z4YSZg5pN8gLSyEb Q1yXrYt3uJyN76lIEi8PBPmUDBaK9Fn+hzViA/EY9oRSdnadedL5uduGV f2L2/ihVT5ufkCAJJVK1c4JnSq4MbFSQ7YeujAxERhI15RB0IRvwWL3k/ U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAFAKTDT0+tJV2b/2dsb2JhbABDtAKBB4F9AQEBAwEBAQEPAR0KNAsFBwQCAQgRBAEBCwYTBAEGASYfCQgBAQQTCBMHh18FC5lQAZ5pjQEDBAIMCw0DAj0YC4UaAgQCBQEBAgIBCwoBDQEGBAYagk1jBIhPn30
X-IronPort-AV: E=Sophos;i="4.73,512,1325462400"; d="scan'208";a="63086650"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by rcdn-iport-7.cisco.com with ESMTP; 01 Mar 2012 18:47:26 +0000
Received: from xbh-rcd-302.cisco.com (xbh-rcd-302.cisco.com [72.163.63.9]) by rcdn-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id q21IlQma018464;  Thu, 1 Mar 2012 18:47:26 GMT
Received: from xmb-rcd-103.cisco.com ([72.163.62.145]) by xbh-rcd-302.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 1 Mar 2012 12:47:26 -0600
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-betts-itu-oam-ach-code-point-03.txt> (Allocation of an Associated Channel Code Point for Use by ITU-T Ethernet based OAM) to Informational RFC
Date: Thu, 1 Mar 2012 12:47:25 -0600
Message-ID: <515703B08A3A064C9CC8C09ACCC710DC063168E1@XMB-RCD-103.cisco.com>
In-Reply-To: <C71DA9B1-A61F-4C5D-8DCE-3702271CBB6D@vigilsec.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt> (Allocation of an Associated Channel Code Point for Use by ITU-T Ethernet based OAM) to Informational RFC
thread-index: Acz3xTqkgc6TtJ4UTAuoF/sFGNEYdAAFahIw
References: <20120222151252.32262.82157.idtracker@ietfa.amsl.com> <03a301ccf174$ff953290$febf97b0$@olddog.co.uk> <515703B08A3A064C9CC8C09ACCC710DC0631679E@XMB-RCD-103.cisco.com> <C71DA9B1-A61F-4C5D-8DCE-3702271CBB6D@vigilsec.com>
From: "Kyung-Yeop Hong (hongk)" <hongk@cisco.com>
To: "Russ Housley" <housley@vigilsec.com>
X-OriginalArrivalTime: 01 Mar 2012 18:47:26.0676 (UTC) FILETIME=[BF541940:01CCF7DB]
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Mar 2012 18:47:32 -0000

Russ,

The LS370 version of G.8113.1 has been sent to the ITU-T Nov 2012
meeting (a.k.a. WTSA) for further discussion. At this point, no one can
tell if it will be approved. As the level of stability and maturity of
G.8113.1 will not be changed between now and Nov, the opinions made by
ITU-T members at the last meeting concerning its stability would not be
changed. So the concerns expressed in this Last Call relating to the
LS370 version will remain even if G.8113.1 is approved at the ITU-T Nov
meeting.

Thanks,
KY

-----Original Message-----
From: Russ Housley [mailto:housley@vigilsec.com]=20
Sent: Thursday, March 01, 2012 11:06 AM
To: Kyung-Yeop Hong (hongk)
Cc: ietf@ietf.org
Subject: Re: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt>
(Allocation of an Associated Channel Code Point for Use by ITU-T
Ethernet based OAM) to Informational RFC

KY:

Would you support the assignment to an approved G.8113.1?  That is, if
the document contained a normative reference to the approved G.8113.1,
then the document that makes the code point allocations would sit in the
RFC Editor queue until the ITU-T reaches consensus and approves
G.8113.1.

Russ


On Mar 1, 2012, at 10:14 AM, Kyung-Yeop Hong (hongk) wrote:

> No/do not support.
>=20
> One of the issues with G.8113.1 in LS370 is its stability and
maturity.
> That was one of the reasons why it was not approved.=20
>=20
> The Ethernet based OAM protocol documented in the LS370 version is
> intended to be deployed for MPLS networks. I think the IETF has a duty
> to ensure that a solution is stable and works for MPLS networks before
> the code point allocation. A number of concerns with the deployment of
> this proposed protocol raised in
> draft-spercher-mpls-tp-oam-considerations are critical to the Internet
> and must be taken into consideration in this Last Call.=20
>=20
> KY
>=20
>=20
>> -----Original Message-----
>> From: ietf-announce-bounces@ietf.org [mailto:ietf-announce-
>> bounces@ietf.org] On Behalf Of The IESG
>> Sent: 22 February 2012 15:13
>> To: IETF-Announce
>> Subject: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt>
> (Allocation of
> an
>> Associated Channel Code Point for Use by ITU-T Ethernet based OAM) to
>> Informational RFC
>>=20
>>=20
>> The IESG has received a request from an individual submitter to
> consider
>> the following document:
>> - 'Allocation of an Associated Channel Code Point for Use by ITU-T
>>   Ethernet based OAM'
>>  <draft-betts-itu-oam-ach-code-point-03.txt> as an Informational RFC
>>=20
>> The IESG plans to make a decision in the next few weeks, and solicits
>> final comments on this action. Please send substantive comments to
the
>> ietf@ietf.org mailing lists by 2012-03-21. Exceptionally, comments
may
> be
>> sent to iesg@ietf.org instead. In either case, please retain the
>> beginning of the Subject line to allow automated sorting.
>>=20
>> Abstract
>>=20
>>   This document assigns an Associated Channel Type code point for
>>   carrying Ethernet based Operations, Administration, and Management
>>   messages in the MPLS Generic Associated Channel (G-ACh).
>>=20
>> The file can be obtained via
>> http://datatracker.ietf.org/doc/draft-betts-itu-oam-ach-code-point/
>>=20
>> IESG discussion can be tracked via
>> http://datatracker.ietf.org/doc/draft-betts-itu-oam-ach-code-point/
>>=20
>>=20
>> No IPR declarations have been submitted directly on this I-D.
>> _______________________________________________
>> IETF-Announce mailing list
>> IETF-Announce@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf-announce
>=20
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From scott@kitterman.com  Thu Mar  1 11:00:48 2012
Return-Path: <scott@kitterman.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8047521E8093 for <ietf@ietfa.amsl.com>; Thu,  1 Mar 2012 11:00:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.579
X-Spam-Level: 
X-Spam-Status: No, score=-2.579 tagged_above=-999 required=5 tests=[AWL=0.020,  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 wlr1z6XUKBkj for <ietf@ietfa.amsl.com>; Thu,  1 Mar 2012 11:00:47 -0800 (PST)
Received: from mailout02.controlledmail.com (mailout02.controlledmail.com [72.81.252.18]) by ietfa.amsl.com (Postfix) with ESMTP id B3E1221E81C2 for <ietf@ietf.org>; Thu,  1 Mar 2012 11:00:47 -0800 (PST)
Received: from mailout02.controlledmail.com (localhost [127.0.0.1]) by mailout02.controlledmail.com (Postfix) with ESMTP id 32A1A20E40DA; Thu,  1 Mar 2012 14:00:47 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=2007-00; t=1330628447; bh=KNa9iCuGl2+o33Pe9PPJYNLVgQ/SGEz3/uQSkcqMGCw=; h=From:To:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version:Content-Transfer-Encoding:Content-Type; b=WlSUhM1ldQJX28bxkH81foSqzqnSXTVgkg3Poxue0VUQOSV9SCkgmAIb0ioYDk6lJ GUYk9ZjJ/zYXUxjcXSXkwXWszaom6OQFJxebcgfM3qgOxH3JWVGqU6SStJJUGUU2Pl 4ABsVaX0L3idmRbrL/xYv8/eLaUFI9P27f96RIxw=
Received: from scott-latitude-e6320.localnet (static-72-81-252-21.bltmmd.fios.verizon.net [72.81.252.21]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailout02.controlledmail.com (Postfix) with ESMTPSA id 1950120E408F;  Thu,  1 Mar 2012 14:00:46 -0500 (EST)
From: Scott Kitterman <scott@kitterman.com>
To: ietf@ietf.org
Subject: Re: Last Call: <draft-ietf-appsawg-xdash-03.txt> (Deprecating Use of the "X-" Prefix in Application Protocols) to Best Current Practice
Date: Thu, 01 Mar 2012 14:00:46 -0500
Message-ID: <2328831.zKV7qZlmPL@scott-latitude-e6320>
User-Agent: KMail/4.7.3 (Linux/3.0.0-16-generic-pae; KDE/4.7.4; i686; ; )
In-Reply-To: <20120301184750.21152.93044.idtracker@ietfa.amsl.com>
References: <20120301184750.21152.93044.idtracker@ietfa.amsl.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
X-AV-Checked: ClamAV using ClamSMTP
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Mar 2012 19:00:48 -0000

On Thursday, March 01, 2012 10:47:50 AM The IESG wrote:
> The IESG has received a request from the Applications Area Working Group
> WG (appsawg) to consider the following document:
> - 'Deprecating Use of the "X-" Prefix in Application Protocols'
>   <draft-ietf-appsawg-xdash-03.txt> as a 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-03-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
> 
> 
>    Historically, designers and implementers of application protocols
>    have often distinguished between "standard" and "non-standard"
>    parameters by prefixing the latter with the string "X-" or similar
>    constructions.  In practice, this convention causes more problems
>    than it solves.  Therefore, this document deprecates the "X-"
>    convention for textual parameters in application protocols.
...

2.  Recommendations for Implementers of Application Protocols

   Implementers of application protocols MUST NOT treat the general
   categories of "standard" and "non-standard" parameters in
   programatically different ways within their applications.

Shouldn't this restrict itself to the naming of parameters?  Perhaps:

2.  Recommendations for Implementers of Application Protocols

   Implementers of application protocols MUST NOT treat the general
   naming of parameters in programmatically different ways within
   their applications depending on if they are "standard" or "non-standard".

Other than that nit, I think it looks good.

Scott K

From paul.hoffman@vpnc.org  Thu Mar  1 11:08:03 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 BAC9521F8A7F; Thu,  1 Mar 2012 11:08:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.669
X-Spam-Level: 
X-Spam-Status: No, score=-102.669 tagged_above=-999 required=5 tests=[AWL=-0.070, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GzA1HsxO43KM; Thu,  1 Mar 2012 11:08:03 -0800 (PST)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id 4C54221F8604; Thu,  1 Mar 2012 11:08:03 -0800 (PST)
Received: from [10.20.30.100] (50-0-66-4.dsl.dynamic.fusionbroadband.com [50.0.66.4]) (authenticated bits=0) by hoffman.proper.com (8.14.5/8.14.3) with ESMTP id q21J81n9017899 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 1 Mar 2012 12:08:02 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Subject: Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=us-ascii
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <4F4FB97C.2080600@inex.ie>
Date: Thu, 1 Mar 2012 11:08:01 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <174F6C5C-731A-43AA-A8C0-B51F857B8C99@vpnc.org>
References: <20120221181006.43AB121F87BF@ietfa.amsl.com> <4F4FB6E9.6020201@stpeter.im> <4F4FB97C.2080600@inex.ie>
To: Nick Hilliard <nick@inex.ie>
X-Mailer: Apple Mail (2.1257)
Cc: ietf-http-wg@w3.org, mnot@mnot.net, IETF discussion list <ietf@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, 01 Mar 2012 19:08:03 -0000

On Mar 1, 2012, at 10:01 AM, Nick Hilliard wrote:

> Can I suggest you also include authorization capabilities as a core
> component of this. It's not much use to have people able to =
authenticate
> themselves to a system if that system doesn't also provide a framework =
for
> allowing the server-side application decide what they can or cannot =
do.


This is a request for an HTTP capability that is significantly different =
than what has been proposed before, and has not been one of the items =
that caused problems in HTTP 1.x. I suggest that this not be part of the =
charter for httpbis until it can be shown to be a significant need, not =
just a new idea.

--Paul Hoffman


From paul.hoffman@vpnc.org  Thu Mar  1 11:09:17 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 88D6D21E8164 for <ietf@ietfa.amsl.com>; Thu,  1 Mar 2012 11:09:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.669
X-Spam-Level: 
X-Spam-Status: No, score=-102.669 tagged_above=-999 required=5 tests=[AWL=-0.070, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S0Y82ocvJCIL for <ietf@ietfa.amsl.com>; Thu,  1 Mar 2012 11:09:17 -0800 (PST)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id 1879121E80CC for <ietf@ietf.org>; Thu,  1 Mar 2012 11:09:17 -0800 (PST)
Received: from [10.20.30.100] (50-0-66-4.dsl.dynamic.fusionbroadband.com [50.0.66.4]) (authenticated bits=0) by hoffman.proper.com (8.14.5/8.14.3) with ESMTP id q21J9GCV017958 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 1 Mar 2012 12:09:16 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Subject: Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=us-ascii
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <6.2.5.6.2.20120301100242.0a6565f8@resistor.net>
Date: Thu, 1 Mar 2012 11:09:15 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <A5973A46-EBF7-4333-9AF2-95B11FD1F1AE@vpnc.org>
References: <20120221181006.43AB121F87BF@ietfa.amsl.com> <4F4FB6E9.6020201@stpeter.im> <6.2.5.6.2.20120301100242.0a6565f8@resistor.net>
To: SM <sm@resistor.net>
X-Mailer: Apple Mail (2.1257)
Cc: mnot@mnot.net, IETF discussion list <ietf@ietf.org>, ietf-http-wg@w3.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Mar 2012 19:09:17 -0000

On Mar 1, 2012, at 10:05 AM, SM wrote:

> At 09:50 01-03-2012, Peter Saint-Andre wrote:
>> Stephen and I just had a chat about this matter. He and I came up =
with a
>> proposed paragraph to add after that list of bullet points:
>>=20
>>   In the initial phase of work on HTTP/2.0, new proposals
>>   for authentication schemes can be made.  The WG will
>>   select zero or more of those with a goal of choosing
>>   at least one scheme that is better than those available
>>   for HTTP/1.x.  Non-selected schemes might be discussed
>>   with the IETF Security Area for further work there.
>=20
> If the WG selects zero, how can it meet the goal of choosing at least =
one scheme?


It doesn't, of course. If the WG doesn't meet that goal, it will be =
clear at the time, and the WG can ask to recharter for that limited =
purpose.

--Paul Hoffman


From housley@vigilsec.com  Thu Mar  1 11:11:51 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 C01DB21E80B1 for <ietf@ietfa.amsl.com>; Thu,  1 Mar 2012 11:11:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.552
X-Spam-Level: 
X-Spam-Status: No, score=-102.552 tagged_above=-999 required=5 tests=[AWL=0.047, 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 6RX83YLFRZkf for <ietf@ietfa.amsl.com>; Thu,  1 Mar 2012 11:11:51 -0800 (PST)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id 33DC821E8069 for <ietf@ietf.org>; Thu,  1 Mar 2012 11:11:51 -0800 (PST)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 4F7A59A471B for <ietf@ietf.org>; Thu,  1 Mar 2012 14:11:51 -0500 (EST)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([208.254.26.82]) by localhost (ronin.smetech.net [208.254.26.81]) (amavisd-new, port 10024) with ESMTP id dNmb7cJGfXZG for <ietf@ietf.org>; Thu,  1 Mar 2012 14:11:50 -0500 (EST)
Received: from [192.168.2.104] (pool-96-241-165-215.washdc.fios.verizon.net [96.241.165.215]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 6D8299A470F for <ietf@ietf.org>; Thu,  1 Mar 2012 14:11:50 -0500 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1084)
Subject: Re: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt>	(Allocation of an Associated Channel Code Point for Use by	ITU-T Ethernet based OAM) to Informational RFC
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <4F4FC252.9010001@cisco.com>
Date: Thu, 1 Mar 2012 14:11:49 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <444F9B86-84CD-4A21-BD02-067877052A0A@vigilsec.com>
References: <20120222151252.32262.82157.idtracker@ietfa.amsl.com> <03a301ccf174$ff953290$febf97b0$@olddog.co.uk> <515703B08A3A064C9CC8C09ACCC710DC0631679E@XMB-RCD-103.cisco.com> <C71DA9B1-A61F-4C5D-8DCE-3702271CBB6D@vigilsec.com> <4F4FA70B.2030906@pi.nu> <D0F60388-D852-4815-917A-B14BF40C64FB@vigilsec.com> <BD60EA38ED03AF5A21868DF1@PST.JCK.COM> <4F4FC252.9010001@cisco.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: Thu, 01 Mar 2012 19:11:52 -0000

>>> Right now, there is no ITU-T approved document to reference.
>>> I am certainly not an expert on ITU-T process, but my
>>> understanding is that earliest that we could see an approved
>>> G.8113.1 is December 2012.  My point is that we don't want to
>>> assign a code point until the ITU-T approves their document.
>>> However, if we are willing to assign a code point to G.8113.1
>>> once it is approved, then this would be an approach where the
>>> code point assignment would block on the approval of the
>>> normative reference.
>>>=20
>>> I like this approach from the political point of view.  With
>>> this approach the IETF tells the ITU-T that if and only if
>>> they are able to achieve consensus on G.8113.1, then a code
>>> point will be assigned.
>> FWIW, this seems entirely appropriate to me.  If we do it this
>> way, I think it is important to note --for the benefit of those
>> more historically involved with the ITU and others-- that we
>> routinely block our own documents on normative references to
>> work that is still in progress and, usually, do not do related
>> code point allocations until the blocking referenced documents
>> are ready.  Once the present I-D is judged to be sufficiently
>> ready, this approach would therefore be IETF approval and a
>> formal guarantee to the ITU that a code point will be allocated
>> if an when G.8113.1 is approved and published, but not
>> assignment of that code point until the referenced base document
>> is finished.
>>=20
>> Completely normal procedurally.
>>=20
> To be clear John our normal requirement would be that the
> technical community achieved consensus that the base document
> was ready. I have never seen ITU-T consensus on the contents
> of G.8113.1 at any meeting that I have observed. What in your
> view is the criteria for determining that  G.8113.1 has achieved
> consensus?


This is not an IETF problem, and I do not think that the IETF ought to =
be discussing the internal workings of the ITU-T process.  The point is =
to come up with a mechanism that allows the code point to be assigned if =
and only if the ITU-T does come to a consensus by whatever means is =
allowed by their own process.

Russ=

From msk@cloudmark.com  Thu Mar  1 11:14:25 2012
Return-Path: <msk@cloudmark.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7AE3F21F86F1; Thu,  1 Mar 2012 11:14:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.604
X-Spam-Level: 
X-Spam-Status: No, score=-102.604 tagged_above=-999 required=5 tests=[AWL=-0.005, 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 b0csDrubgM8Y; Thu,  1 Mar 2012 11:14:24 -0800 (PST)
Received: from ht1-outbound.cloudmark.com (ht1-outbound.cloudmark.com [72.5.239.25]) by ietfa.amsl.com (Postfix) with ESMTP id 988FD21E824D; Thu,  1 Mar 2012 11:14:21 -0800 (PST)
Received: from EXCH-MBX901.corp.cloudmark.com ([fe80::addf:849a:f71c:4a82]) by EXCH-HTCAS901.corp.cloudmark.com ([fe80::2966:6846:8d89:4681%12]) with mapi id 14.01.0355.002; Thu, 1 Mar 2012 11:14:21 -0800
From: "Murray S. Kucherawy" <msk@cloudmark.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: Last Call: <draft-ietf-marf-spf-reporting-08.txt> (SPF Authentication Failure Reporting using the Abuse Report Format) to	Proposed Standard
Thread-Topic: Last Call: <draft-ietf-marf-spf-reporting-08.txt> (SPF Authentication Failure Reporting using the Abuse Report Format) to	Proposed Standard
Thread-Index: AQHM93WQJGLXlQlAakuMTOLw/EOUTZZVzRBQ
Date: Thu, 1 Mar 2012 19:14:20 +0000
Message-ID: <9452079D1A51524AA5749AD23E00392806F917@exch-mbx901.corp.cloudmark.com>
References: <20120301004643.17274.83943.idtracker@ietfa.amsl.com> <6.2.5.6.2.20120229181328.0a95a9f8@resistor.net>
In-Reply-To: <6.2.5.6.2.20120229181328.0a95a9f8@resistor.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.20.2.121]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "marf@ietf.org" <marf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Mar 2012 19:14:25 -0000

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of S=
M
> Sent: Wednesday, February 29, 2012 10:27 PM
> To: ietf@ietf.org
> Subject: Re: Last Call: <draft-ietf-marf-spf-reporting-08.txt> (SPF
> Authentication Failure Reporting using the Abuse Report Format) to
> Proposed Standard

As for your non-procedural concerns:

> I'll avoid commenting on the technical angle.  Here are some editorial
> comments:
>=20
> In Section 3:
>=20
>    "There exist cases in which a domain name owner employing [SPF] for
>     announcing sending practices may want to know when messages are
>     received via unauthorized routing."
>=20
> I suggest not using the term "domain name owner" to side-step the
> question of domain "ownership".

Would "ADMD" and an informative reference to RFC5598 be more appropriate?

>    "particular because a message arrived via an unauthorized route.
>     To generate a complete address to which the report is sent, the
>     verifier simply appends to this value an "@" followed by the
>     SPF domain per paragraph 4.1 of [SPF]."
>=20
> RFC 4408 uses the term "SPF-compliant domain".

That's fine with us.

> In Section 5.1:
>=20
>    "New registrations or updates MUST be published in accordance with the
>     "Specification Required" guidelines as described in
>     [IANA-CONSIDERATIONS].  New registrations and updates MUST contain
>     the following information:"
>=20
> I suggest not using RFC 2119 key words in the IANA Considerations
> section unless there are interoperability issues with IANA.

We'll change "MUST" to "are to be".

>    "current:  The field is in current use
>=20
>     deprecated:  The field is in current use but its use is
>        discouraged"
>=20
> The difference in "current use" can end up being problematic for the
> designated expert.

A number of registries are using this wording already and there's been no o=
bjection to date.  Do you have a better suggestion?

> In Section 6:
>=20
>   "Security issues with respect to these reports are similar to those
>    found in [DSN]."
>=20
> The reference to DSN could be normative.

Security Considerations are never normative, so I'm not sure I agree that t=
his should be.

>    "The HELO/EHLO command SHOULD also be selected so that it
>     will pass [SPF] HELO checks."
>=20
> I could not understand what to do about the above recommendation.
> FWIW, the command is specified in RFC 5321.  That specification is not
> referenced by this draft.

Yes, that needs to be clarified, the reference added, and the typo in the s=
ection title needs correction.

Thanks,
-MSK

From nurit.sprecher@nsn.com  Thu Mar  1 11:34:05 2012
Return-Path: <nurit.sprecher@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 4A88D21E829C for <ietf@ietfa.amsl.com>; Thu,  1 Mar 2012 11:34:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.546
X-Spam-Level: 
X-Spam-Status: No, score=-6.546 tagged_above=-999 required=5 tests=[AWL=0.053,  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 r0aL0yAfu48p for <ietf@ietfa.amsl.com>; Thu,  1 Mar 2012 11:34:04 -0800 (PST)
Received: from demumfd001.nsn-inter.net (demumfd001.nsn-inter.net [93.183.12.32]) by ietfa.amsl.com (Postfix) with ESMTP id 5829621E8069 for <ietf@ietf.org>; Thu,  1 Mar 2012 11:34:04 -0800 (PST)
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 q21JY0QK008903 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 1 Mar 2012 20:34:00 +0100
Received: from DEMUEXC048.nsn-intra.net ([10.159.32.94]) by demuprx017.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id q21JXvlF012821; Thu, 1 Mar 2012 20:34:00 +0100
Received: from DEMUEXC013.nsn-intra.net ([10.150.128.24]) by DEMUEXC048.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 1 Mar 2012 20:33:50 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Last Call:<draft-betts-itu-oam-ach-code-point-03.txt>	(Allocation of anAssociated Channel Code Point for Use by	ITU-T Ethernet basedOAM) to Informational RFC
Date: Thu, 1 Mar 2012 20:33:49 +0100
Message-ID: <E4873516F3FC7547BCFE792C7D94039C015D125D@DEMUEXC013.nsn-intra.net>
In-Reply-To: <444F9B86-84CD-4A21-BD02-067877052A0A@vigilsec.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Last Call:<draft-betts-itu-oam-ach-code-point-03.txt>	(Allocation of anAssociated Channel Code Point for Use by	ITU-T Ethernet basedOAM) to Informational RFC
Thread-Index: Acz33zUrwoW7GfLCRMG9/dOiSxMekgAApblA
References: <20120222151252.32262.82157.idtracker@ietfa.amsl.com><03a301ccf174$ff953290$febf97b0$@olddog.co.uk><515703B08A3A064C9CC8C09ACCC710DC0631679E@XMB-RCD-103.cisco.com><C71DA9B1-A61F-4C5D-8DCE-3702271CBB6D@vigilsec.com><4F4FA70B.2030906@pi.nu><D0F60388-D852-4815-917A-B14BF40C64FB@vigilsec.com><BD60EA38ED03AF5A21868DF1@PST.JCK.COM> <4F4FC252.9010001@cisco.com> <444F9B86-84CD-4A21-BD02-067877052A0A@vigilsec.com>
From: "Sprecher, Nurit (NSN - IL/Hod HaSharon)" <nurit.sprecher@nsn.com>
To: "ext Russ Housley" <housley@vigilsec.com>, "IETF" <ietf@ietf.org>
X-OriginalArrivalTime: 01 Mar 2012 19:33:50.0835 (UTC) FILETIME=[3AD10C30:01CCF7E2]
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: 2830
X-purgate-ID: 151667::1330630440-000044A2-D277017C/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: Thu, 01 Mar 2012 19:34:05 -0000

Russ,=20
I propose to simply re-discuss it when and IFF G.8113.1 is mature and
approved...
Best regards,
Nurit


-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
ext Russ Housley
Sent: Thursday, March 01, 2012 9:12 PM
To: IETF
Subject: Re: Last Call:<draft-betts-itu-oam-ach-code-point-03.txt>
(Allocation of anAssociated Channel Code Point for Use by ITU-T Ethernet
basedOAM) to Informational RFC

>>> Right now, there is no ITU-T approved document to reference.
>>> I am certainly not an expert on ITU-T process, but my
>>> understanding is that earliest that we could see an approved
>>> G.8113.1 is December 2012.  My point is that we don't want to
>>> assign a code point until the ITU-T approves their document.
>>> However, if we are willing to assign a code point to G.8113.1
>>> once it is approved, then this would be an approach where the
>>> code point assignment would block on the approval of the
>>> normative reference.
>>>=20
>>> I like this approach from the political point of view.  With
>>> this approach the IETF tells the ITU-T that if and only if
>>> they are able to achieve consensus on G.8113.1, then a code
>>> point will be assigned.
>> FWIW, this seems entirely appropriate to me.  If we do it this
>> way, I think it is important to note --for the benefit of those
>> more historically involved with the ITU and others-- that we
>> routinely block our own documents on normative references to
>> work that is still in progress and, usually, do not do related
>> code point allocations until the blocking referenced documents
>> are ready.  Once the present I-D is judged to be sufficiently
>> ready, this approach would therefore be IETF approval and a
>> formal guarantee to the ITU that a code point will be allocated
>> if an when G.8113.1 is approved and published, but not
>> assignment of that code point until the referenced base document
>> is finished.
>>=20
>> Completely normal procedurally.
>>=20
> To be clear John our normal requirement would be that the
> technical community achieved consensus that the base document
> was ready. I have never seen ITU-T consensus on the contents
> of G.8113.1 at any meeting that I have observed. What in your
> view is the criteria for determining that  G.8113.1 has achieved
> consensus?


This is not an IETF problem, and I do not think that the IETF ought to
be discussing the internal workings of the ITU-T process.  The point is
to come up with a mechanism that allows the code point to be assigned if
and only if the ITU-T does come to a consensus by whatever means is
allowed by their own process.

Russ
_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf

From barryleiba.mailing.lists@gmail.com  Thu Mar  1 12:49:45 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 4E16B21F88EE for <ietf@ietfa.amsl.com>; Thu,  1 Mar 2012 12:49:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.987
X-Spam-Level: 
X-Spam-Status: No, score=-102.987 tagged_above=-999 required=5 tests=[AWL=-0.010, 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 V4JM4isHS2bp for <ietf@ietfa.amsl.com>; Thu,  1 Mar 2012 12:49:44 -0800 (PST)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id 407CD21F8A39 for <ietf@ietf.org>; Thu,  1 Mar 2012 12:49:40 -0800 (PST)
Received: by yhpp34 with SMTP id p34so564387yhp.31 for <ietf@ietf.org>; Thu, 01 Mar 2012 12:49:39 -0800 (PST)
Received-SPF: pass (google.com: domain of barryleiba.mailing.lists@gmail.com designates 10.236.37.132 as permitted sender) client-ip=10.236.37.132; 
Authentication-Results: mr.google.com; spf=pass (google.com: domain of barryleiba.mailing.lists@gmail.com designates 10.236.37.132 as permitted sender) smtp.mail=barryleiba.mailing.lists@gmail.com; dkim=pass header.i=barryleiba.mailing.lists@gmail.com
Received: from mr.google.com ([10.236.37.132]) by 10.236.37.132 with SMTP id y4mr9881034yha.10.1330634979966 (num_hops = 1); Thu, 01 Mar 2012 12:49:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=NVBBjAEGdEvCWfh7CN16xM7wa53o0JGHtDJra8J0d3c=; b=c9z3FvhRGOmahd00nmHISGQnL6lTZHyXHo9rGMlro/ggnw4dBGNPytxoV1IQ9wS1Tb 6XRWDzVTaqoF7nJ5PRcTONhfdobcjJSgXebABcZ94lT3BqtBmI8o3s3exw50IgOPVG8H aHOjYAYa0CJyNiqMkHBHiww1IcafKNdrmufcXepAPCqwYJbjT4s+twoPK370l/Y8wWjM bGlzUYx6AuOZNdLyB329nb0cJ8dCYdqy31dH+cqXoacv9XoDOgVpogd/nB3aWyX3HJv/ 040YjLFWP5EA/O9/N48nT5P5XsCPYIx2G+4TChFXwhF/5oIgobrvp6v531MnuaEzieTy EoSg==
MIME-Version: 1.0
Received: by 10.236.37.132 with SMTP id y4mr7800008yha.10.1330634979899; Thu, 01 Mar 2012 12:49:39 -0800 (PST)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.147.106.16 with HTTP; Thu, 1 Mar 2012 12:49:39 -0800 (PST)
In-Reply-To: <20120301004219.15266.76505.idtracker@ietfa.amsl.com>
References: <20120301004219.15266.76505.idtracker@ietfa.amsl.com>
Date: Thu, 1 Mar 2012 15:49:39 -0500
X-Google-Sender-Auth: gijKgpXcZUk1EDYN7nNVyCQf1pY
Message-ID: <CAC4RtVDeXwCLh9R_bNmLwEC5g_4Dv9HadOpXMwbSz5RT2m+jUg@mail.gmail.com>
Subject: Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard
From: Barry Leiba <barryleiba@computer.org>
To: ietf@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Cc: Pete Resnick <presnick@qualcomm.com>, Alexey Melnikov <Alexey.Melnikov@isode.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Mar 2012 20:49:45 -0000

I had expected that we'd deal with my shepherd review before doing the
last call on the document.  Because that didn't happen, I'll re-post
my review here, as public last-call comments.  Maybe that will prevent
people from raising the same things I've already raised.

First, two additional points:

1. As to Murray's comment about explicitly declaring text to be
informative, I'm with Tom on this: I think it's at worst harmless, and
possibly very useful as a clarification, to explicitly say "this
[paragraph, section, whatever] is not normative."  It might be
unnecessary, but where's the harm?

2. I, too, noticed all the lower-case "should" and "may" words.  I
suggest that the best way to handle this is to make the following
change to the RFC 2119 citation text at the beginning of section 2:

NEW
   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC2119] when they appear
   in ALL CAPS.  These words also appear in this document in lower case as plain
   English words, absent their normative meanings.

My review, which was already sent to Alexey and Pete:

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

Section 4.1
  1.  A conforming SMTP server SHOULD NOT refuse a MAIL command based
      on the absence of the PRIORITY parameter.

I agree with Pete's MUST NOT -- also because at this point, the server
has no idea whether the message is coming from a non-supporting
server, and whether or not there's an MT-Priority header field in the
message.  This really needs to be MUST NOT.

-----
Section 4.4
  1.  A PRIORITY parameter MUST NOT appear in the MAIL command issued
      when relaying the message.

  2.  The relaying MTA MUST first remove any and all existing MT-
      Priority header fields from the message, and then add its own MT-
      Priority header field with the value determined by the procedure
      in Section 4.2.  One exception to this rule is that a message
      which didn't contain any MT-Priority header field and which
      didn't have the PRIORITY MAIL FROM parameter specified doesn't
      need to be updated to contain the "MT-Priority: 0" header field.
      Syntax of the MT-Priority header field is specified in Section 7.

Because of the exception, I think there's a slight unclear point here
(and I also don't like the passive voice in bullet 1).  Let me re-work
this thus:

NEW
  1.  The relaying MTA MUST NOT use the PRIORITY parameter in the
      MAIL command issued when relaying the message.

  2.  The relaying MTA MUST first remove any and all existing MT-
      Priority header fields from the message.

  3.  If the message had a PRIORITY specified in the MAIL FROM
      parameter *or* there was an MT-Priority header field
      removed in step 2, then the relaying MTA MUST add its own
      MT-Priority header field with the value determined by the
      procedure in Section 4.2.

      The syntax of the MT-Priority header field is specified in
      Section 7.

-----
Section 5.
  A message priority is a decimal integer in the range from -9 to 9
  (inclusive).  SMTP servers compliant with this specification are not
  required to support all 19 distinct priority levels (i.e. to treat
  each priority value as a separate priority), but they MUST implement
  at least the following 6 distinct priority levels: -4, -2, 0, 2, 4,
  9.  I.e. an implementation that only supports the 6 priority levels
  will internally treat all syntactically valid priority values below
  and including -4 as priority -4, priorities -3 and -2 as priority -2,
  priorities -1 and 0 as priority 0, etc., with all priorities starting
  from 5 are treated as priority 9.  An SMTP server MAY support more
  than 6 different priority levels.  Decision about which levels to
  support in addition to the 6 mentioned above is a local matter.

There's a lot of stuff after the "I.e.", much of which can be changed
to just say that a syntatically valid level that isn't supported gets
raised to the next higher supported number.  Say that, and it all
looks clearer and easier.

-----
Editorial:
OLD
  Note: 19 possible priority levels are defined by this specification
  for extensibility, for example if a particular implementation or
  deployment environment needs to provide fine grainer control over
  message transfer priorities, for example a server implementation may
  need to have an extra high priority level to the 6 levels defined
  above.

NEW
  Note: 19 possible priority levels are defined by this specification
  for extensibility. For example, a particular implementation or
  deployment environment might need to provide finer-grained control
  over message transfer priorities.  In such a case, a server
  implementation might need an extra priority level beyond the 6 levels
  defined above.

-----
Editorial:
OLD
Such actions usually need user confirmation.
NEW
Such actions usually require user interaction.

-----
Section 5.1
  As a default policy, emails with higher priority waiting to be sent
  by a client SHOULD NOT initiate transactions for emails with lower
  priorites.  If two or more emails with the same priority are ready to
  be sent at the same time, the MTA should use its regular algorithm
  (the algorithm used in absence of this SMTP extension) for deciding
  how to send them out.

I have no idea what the first sentence means.  For the second
sentence, I would say it like this: "Within a priority level, the MTA
uses its normal ordering for the messages."

-----
Section 5.2
Editorial:
OLD
  An important constraint (usually associated with higher priority
  levels) is, that messages with that priority have to reach its
  destination within a defined period of time.  In some cases, higher
  priorities mean shorter maximum allowed time of delivery.
NEW
  An important constraint (usually associated with higher priority
  levels) is that messages with high priority have some delivery
  time constraints.  In some cases, higher priorities mean a shorter
  maximum time allowed for delivery.

And I would add to the second paragraph, "But note that use of the
DELIVERBY extension alone does not guarantee any priority processing."

-----
Section 6
I would switch sections 6 and 7, to avoid the forward reference in the
current section 6.

-----
Section 8. Example
I'd like to see an example that includes multiple hops, and that
includes transit across an MTA that doesn't support this.  Perhaps a
life-cycle example: MUA -> MSA -> MTA1 -> MTA2 -> MTA3 -> MDA, where
MTA2 does not support the priority extension.  Maybe:
MSA is mail.alertservice.example
MTA1 is outbound.alertservice.example
MTA2 is relay.backbone.example (doesn't support)
MTA3 is mx1.isp.example
MDA is mailbox5.isp.example

The one simple example doesn't convey much that's useful about how the
various bits work, and especially how the parameter tunneling works.
(You'll also need to provide message headers in the DATA section in
order to show that.)  I think it makes for a bulky Examples section,
but I think it's important.

I think I would do this as separate subsections:
8. Example
8.1 Message Submission
8.2 Relay to Internet Edge MTA
8.3 Relay through Internet Backbone
8.4 Relay to ISP's Edge MTA
8.5 Delivery to ISP User's Mailbox

-----
Section 10
I think the SMTP parameters should match the header field, and all be
MT-PRIORITY.  I'm not going to fight about it, though.

-----
Section 12.1
I am concerned that we're somewhat overloading DKIM here, by asking an
MTA to DKIM-sign a message *solely* to protect the value of one
specific header field.  That's a bit of a stretch, and causes some
level of problem in some cases.  Consider the example above, and
suppose that MSA DKIM-signs the message, with no MT-Priority header
field.  Now MTA1 has to add MT-Priority in order to relay to MTA2, and
it DKIM-signs it again... but perhaps only covering the "from" and
"mt-priority" fields.  None of that is a *huge* deal, but it just
strikes me as an odd use of DKIM, which goes beyond the semantics we
put on it.

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

Barry, document shepherd

From barryleiba.mailing.lists@gmail.com  Thu Mar  1 13:01:24 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 63A8421E80D8; Thu,  1 Mar 2012 13:01:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.987
X-Spam-Level: 
X-Spam-Status: No, score=-102.987 tagged_above=-999 required=5 tests=[AWL=-0.010, 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 pl1pXPv4yr94; Thu,  1 Mar 2012 13:01:22 -0800 (PST)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id B5A4721E8021; Thu,  1 Mar 2012 13:01:20 -0800 (PST)
Received: by yhpp34 with SMTP id p34so571533yhp.31 for <multiple recipients>; Thu, 01 Mar 2012 13:01:20 -0800 (PST)
Received-SPF: pass (google.com: domain of barryleiba.mailing.lists@gmail.com designates 10.236.136.4 as permitted sender) client-ip=10.236.136.4; 
Authentication-Results: mr.google.com; spf=pass (google.com: domain of barryleiba.mailing.lists@gmail.com designates 10.236.136.4 as permitted sender) smtp.mail=barryleiba.mailing.lists@gmail.com; dkim=pass header.i=barryleiba.mailing.lists@gmail.com
Received: from mr.google.com ([10.236.136.4]) by 10.236.136.4 with SMTP id v4mr9586826yhi.44.1330635680442 (num_hops = 1); Thu, 01 Mar 2012 13:01:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=ebeGm97z6fj7BgEk+H0OPLw+L+qqZhveOK1UHxIkH4M=; b=IpOnn7k0K3WE7CAuqwiseJGXPxZYLPKI4aTKW37VEiAKafbcwV76tx7+S6mVa0nDoJ bqjbagf/0TC9WUY1Io0c1ubvQ6cCN0UdoZgZ1SWFRVl5NMYI97N468XwMLuzlVyB+vTy FuHPFmXiWHVYKChtoEbH3GVWSjtmzAP3p3SWx6vhkxhTJPnhVzKamyC4Y/XPZNsMwUs9 6xr2JGv9UDiwHkohr7mPemYMfbM4ZRXHMWaN36XSH4dB3nkZ8j11Ul+DkUDoi6GG/l/D Kx4r2bcviVSN8L/tbhfHvKG8Kmu+YmJ4bopdkGpSyEREpbia3DBpBpGJ2dcA4wSHtvlr gwRA==
MIME-Version: 1.0
Received: by 10.236.136.4 with SMTP id v4mr7596775yhi.44.1330635680385; Thu, 01 Mar 2012 13:01:20 -0800 (PST)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.147.106.16 with HTTP; Thu, 1 Mar 2012 13:01:20 -0800 (PST)
In-Reply-To: <9452079D1A51524AA5749AD23E00392806F917@exch-mbx901.corp.cloudmark.com>
References: <20120301004643.17274.83943.idtracker@ietfa.amsl.com> <6.2.5.6.2.20120229181328.0a95a9f8@resistor.net> <9452079D1A51524AA5749AD23E00392806F917@exch-mbx901.corp.cloudmark.com>
Date: Thu, 1 Mar 2012 16:01:20 -0500
X-Google-Sender-Auth: 4jP_NmemvtpoU2eLI5--Q5qC0U8
Message-ID: <CAC4RtVC5e4O3e1cUSDfj+fi-4StvqS14p5BJ89+QANC30hmfYA@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-marf-spf-reporting-08.txt> (SPF Authentication Failure Reporting using the Abuse Report Format) to Proposed Standard
From: Barry Leiba <barryleiba@computer.org>
To: "Murray S. Kucherawy" <msk@cloudmark.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "ietf@ietf.org" <ietf@ietf.org>, "marf@ietf.org" <marf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Mar 2012 21:01:24 -0000

>> =A0 =A0"current: =A0The field is in current use
>>
>> =A0 =A0 deprecated: =A0The field is in current use but its use is
>> =A0 =A0 =A0 =A0discouraged"
>>
>> The difference in "current use" can end up being problematic for the
>> designated expert.
>
> A number of registries are using this wording already and there's been no
> objection to date. =A0Do you have a better suggestion?

I suggest, "The field might still be in use, but its use is discouraged."

>> In Section 6:
>>
>> =A0 "Security issues with respect to these reports are similar to those
>> =A0 =A0found in [DSN]."
>>
>> The reference to DSN could be normative.
>
> Security Considerations are never normative, so I'm not sure I agree that=
 this should be.

It should.  Just because the Security Considerations section doesn't
usually use normative language doesn't mean that it's not normative.
People reading the document and implementing the protocol certainly
have to read and understand the Security Considerations section, along
with any transitive sections in other documents.

Barry, MARF co-chair

From scott@kitterman.com  Thu Mar  1 13:15:07 2012
Return-Path: <scott@kitterman.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BA13A21E8085 for <ietf@ietfa.amsl.com>; Thu,  1 Mar 2012 13:15:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.58
X-Spam-Level: 
X-Spam-Status: No, score=-2.58 tagged_above=-999 required=5 tests=[AWL=0.019,  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 Zxs2zRmo6tLC for <ietf@ietfa.amsl.com>; Thu,  1 Mar 2012 13:15:07 -0800 (PST)
Received: from mailout02.controlledmail.com (mailout02.controlledmail.com [72.81.252.18]) by ietfa.amsl.com (Postfix) with ESMTP id 07AE521E803E for <ietf@ietf.org>; Thu,  1 Mar 2012 13:15:07 -0800 (PST)
Received: from mailout02.controlledmail.com (localhost [127.0.0.1]) by mailout02.controlledmail.com (Postfix) with ESMTP id 6F2BF20E40DA; Thu,  1 Mar 2012 16:15:06 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=2007-00; t=1330636506; bh=2/XyTspylgJ2tBZoHxOppyXJgo3vDmVLp0aaFuXdzvI=; h=From:To:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version:Content-Transfer-Encoding:Content-Type; b=N7juTG50jzRbDgj3o/LLEa363BOnJOEl8wu0KYnPbXVVc5WkJG2XxRxCvoul2Kztt C84K8PSnlzTYamqbxDnkfezFba+qe9my862GO/puGL3w9vft53KRC2ePtzKeizlmUH fOVFvjVxcyOs22lrA64S+c+nc8q8/Qhgs/HX2mWE=
Received: from scott-latitude-e6320.localnet (static-72-81-252-21.bltmmd.fios.verizon.net [72.81.252.21]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailout02.controlledmail.com (Postfix) with ESMTPSA id 554DA20E408F;  Thu,  1 Mar 2012 16:15:06 -0500 (EST)
From: Scott Kitterman <scott@kitterman.com>
To: ietf@ietf.org
Subject: Re: Last Call: <draft-ietf-marf-spf-reporting-08.txt> (SPF Authentication Failure Reporting using the Abuse Report Format) to Proposed Standard
Date: Thu, 01 Mar 2012 16:15:05 -0500
Message-ID: <1637246.LVMrVQYPHS@scott-latitude-e6320>
User-Agent: KMail/4.7.3 (Linux/3.0.0-16-generic-pae; KDE/4.7.4; i686; ; )
In-Reply-To: <CAC4RtVC5e4O3e1cUSDfj+fi-4StvqS14p5BJ89+QANC30hmfYA@mail.gmail.com>
References: <20120301004643.17274.83943.idtracker@ietfa.amsl.com> <9452079D1A51524AA5749AD23E00392806F917@exch-mbx901.corp.cloudmark.com> <CAC4RtVC5e4O3e1cUSDfj+fi-4StvqS14p5BJ89+QANC30hmfYA@mail.gmail.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
X-AV-Checked: ClamAV using ClamSMTP
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Mar 2012 21:15:07 -0000

On Thursday, March 01, 2012 04:01:20 PM Barry Leiba wrote:
...
> >> In Section 6:
> >> 
> >>   "Security issues with respect to these reports are similar to those
> >>    found in [DSN]."
> >> 
> >> The reference to DSN could be normative.
> > 
> > Security Considerations are never normative, so I'm not sure I agree
> > that this should be.
> It should.  Just because the Security Considerations section doesn't
> usually use normative language doesn't mean that it's not normative.
> People reading the document and implementing the protocol certainly
> have to read and understand the Security Considerations section, along
> with any transitive sections in other documents.

The reason I didn't make it normative when I drafted that section is because 
this isn't a DSN, it's an ARF, thus the similar to.  If people think it should 
be normative, I think it's fine to change it.

Scott K

From sm@resistor.net  Thu Mar  1 13:37:07 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 CA40A21E8217 for <ietf@ietfa.amsl.com>; Thu,  1 Mar 2012 13:37:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.646
X-Spam-Level: 
X-Spam-Status: No, score=-102.646 tagged_above=-999 required=5 tests=[AWL=-0.047, 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 Q8VyBqXWyS69 for <ietf@ietfa.amsl.com>; Thu,  1 Mar 2012 13:37:07 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id BCB3821E8279 for <ietf@ietf.org>; Thu,  1 Mar 2012 13:37:06 -0800 (PST)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id q21LaxrB024828; Thu, 1 Mar 2012 13:37:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1330637824; i=@resistor.net; bh=k2bCk2GxLAbS9w8N+Ji4SJ7mlgyoWRaaOIsGtUvcAlw=; h=Message-Id:Date:To:From:Subject:Cc:In-Reply-To:References: Mime-Version:Content-Type; b=NuoW4ueRv1r7P4sbk6gKNAGziyNq3gfaMXKYyglNcnfKxEjO40pWNEZ9b34/3VX5s Mtndl/pRfXHQaTwuAPFhazKtNqOLAmcsctgdsI+O34DGcrK4reF3O/jSBQ0HlqwMPG GSlCYa0K3ZWrxThPKkz+hIz0I9TXbP173MouEGOU=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1330637824; i=@resistor.net; bh=k2bCk2GxLAbS9w8N+Ji4SJ7mlgyoWRaaOIsGtUvcAlw=; h=Message-Id:Date:To:From:Subject:Cc:In-Reply-To:References: Mime-Version:Content-Type; b=FmPWuj1NkraOTkEwVF9BHqUppPkj3sy/7d3+EZSeRkTH+4Z7TEaokBaBHe9JYbVYl Dts+wsH/IUD4VfVWUnTFBe5ii2kj7q5f6Q6lQwPxwMMMQwiZdFy/0ImjgzBrwFKFg4 Tn7S6xf36WB+StQeVALPGA/MbrIykSwWd3GVqbcU=
Message-Id: <6.2.5.6.2.20120301120015.0940b2c0@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 01 Mar 2012 13:36:09 -0800
To: ietf@ietf.org
From: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard
In-Reply-To: <20120301004219.15266.76505.idtracker@ietfa.amsl.com>
References: <20120301004219.15266.76505.idtracker@ietfa.amsl.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: Alexey Melnikov <Alexey.Melnikov@isode.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Mar 2012 21:37:07 -0000

At 16:42 29-02-2012, The IESG wrote:
>The IESG has received a request from an individual submitter to consider
>the following document:
>- 'Simple Mail Transfer Protocol extension for Message Transfer
>    Priorities'
>   <draft-melnikov-smtp-priority-07.txt> as a 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-03-28. Exceptionally, comments may be

This draft specifies a SMTP extension.  The IANA Considerations does 
not mention registration in the the SMTP Service Extensions 
registry.  There should also be an indication about the extension 
being valid for the submit port.  The issue of referencing STANAG 
4406 was resolved by the IESG last year (see RFC 6477).

This draft also defines the MT-Priority header field.  It is quite 
unusual for a SMTP extension specification to define a mail header 
field.  If I had an reservations about this draft, it would be on 
architectural grounds.  The draft tries really hard to transfer 
priority information over the Internet and in a foreign 
environment.  Although the draft is well-written and can be 
implemented, I have doubts about whether it will achieve its 
objective.  I unfortunately cannot support the publication of this 
draft as a Proposed Standard.

Regards,
-sm 


From barryleiba.mailing.lists@gmail.com  Thu Mar  1 13:47:47 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 0E46521E8171 for <ietf@ietfa.amsl.com>; Thu,  1 Mar 2012 13:47:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.987
X-Spam-Level: 
X-Spam-Status: No, score=-102.987 tagged_above=-999 required=5 tests=[AWL=-0.010, 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 hkFHz+UI48PO for <ietf@ietfa.amsl.com>; Thu,  1 Mar 2012 13:47:46 -0800 (PST)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id F160F21E8134 for <ietf@ietf.org>; Thu,  1 Mar 2012 13:47:43 -0800 (PST)
Received: by yhpp34 with SMTP id p34so598688yhp.31 for <ietf@ietf.org>; Thu, 01 Mar 2012 13:47:43 -0800 (PST)
Received-SPF: pass (google.com: domain of barryleiba.mailing.lists@gmail.com designates 10.236.145.230 as permitted sender) client-ip=10.236.145.230; 
Authentication-Results: mr.google.com; spf=pass (google.com: domain of barryleiba.mailing.lists@gmail.com designates 10.236.145.230 as permitted sender) smtp.mail=barryleiba.mailing.lists@gmail.com; dkim=pass header.i=barryleiba.mailing.lists@gmail.com
Received: from mr.google.com ([10.236.145.230]) by 10.236.145.230 with SMTP id p66mr9834478yhj.27.1330638463669 (num_hops = 1); Thu, 01 Mar 2012 13:47:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=1eYbVHBs2SQ7HQ65D6rpKPV4bLXxHF1RbDRyKcWJXfg=; b=qUIo2fPxQM7VwYpDlp6+32iZRqm3r493pkOJdn+ZEMwNAHCvKXhq3oq28ezRH30w4l E4HRs5FnXJByiSwY/Gqi64zkV61WgTPCuwgJTGSGDUMXMo4zQv/11+grkXu1NHn359Ab 6DcOl86qtJCxNiWy1Q1R1gztok9gAo6nSQvjsmkJ2JxnjrIGT8SPc8l64eikFr9po9rg TNQfi/dFA5h9xZld6jPFDM/xDGLsQg5cveVvQXI0eAjDHdt6UFrb1+bhoRmeossKM7J7 YVcRRd8AR33uBjbaIHQkZs42P53BbBXe9UKt1FpYdGUoF0R0wG6avTK8oqv8TKya6Qed e44w==
MIME-Version: 1.0
Received: by 10.236.145.230 with SMTP id p66mr7794088yhj.27.1330638463611; Thu, 01 Mar 2012 13:47:43 -0800 (PST)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.147.106.16 with HTTP; Thu, 1 Mar 2012 13:47:43 -0800 (PST)
In-Reply-To: <1637246.LVMrVQYPHS@scott-latitude-e6320>
References: <20120301004643.17274.83943.idtracker@ietfa.amsl.com> <9452079D1A51524AA5749AD23E00392806F917@exch-mbx901.corp.cloudmark.com> <CAC4RtVC5e4O3e1cUSDfj+fi-4StvqS14p5BJ89+QANC30hmfYA@mail.gmail.com> <1637246.LVMrVQYPHS@scott-latitude-e6320>
Date: Thu, 1 Mar 2012 16:47:43 -0500
X-Google-Sender-Auth: XaoYtO-XiLf5iJrzll3M8-U-e1I
Message-ID: <CAC4RtVCSNcdiwcYR5fMcPvMSxCAVFNrWg+7-AOyM4G22u7vu9Q@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-marf-spf-reporting-08.txt> (SPF Authentication Failure Reporting using the Abuse Report Format) to Proposed Standard
From: Barry Leiba <barryleiba@computer.org>
To: Scott Kitterman <scott@kitterman.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Mar 2012 21:47:47 -0000

>> >> =A0 "Security issues with respect to these reports are similar to tho=
se
>> >> =A0 =A0found in [DSN]."
>> >>
>> >> The reference to DSN could be normative.
>> >
>> > Security Considerations are never normative, so I'm not sure I agree
>> > that this should be.
>>
>> It should. =A0Just because the Security Considerations section doesn't
>> usually use normative language doesn't mean that it's not normative.
>> People reading the document and implementing the protocol certainly
>> have to read and understand the Security Considerations section, along
>> with any transitive sections in other documents.
>
> The reason I didn't make it normative when I drafted that section is beca=
use
> this isn't a DSN, it's an ARF, thus the similar to. =A0If people think it=
 should
> be normative, I think it's fine to change it.

Yes, but think about the difference between these two statements:

1. Security issues with respect to these reports are similar to those
found in [DSN].

2. Security issues with respect to these reports are similar to those
found in [DSN].  Specifically, X and Y.  Also Z, when that situation
is applicable.

In the second case, you can understand the security issues here
without going and reading [DSN].  It really is just saying that these
are similar to those, so the reference is informative.  In the first
case, how can you know *anything* about the security issues without
reading the referenced document?

If sections 6.1 and 6.2 really do say everything that needs to be
said, and the sentence in 6. could be removed without loss of
important information, then leave it as an informative reference.  If
one really has to go to [DSN] to see what some of the issues are, make
it normative.  That's the test.

Barry

From barryleiba.mailing.lists@gmail.com  Thu Mar  1 13:53:31 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 1338E21E824A for <ietf@ietfa.amsl.com>; Thu,  1 Mar 2012 13:53:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.987
X-Spam-Level: 
X-Spam-Status: No, score=-102.987 tagged_above=-999 required=5 tests=[AWL=-0.010, 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 PBEya3LvAToU for <ietf@ietfa.amsl.com>; Thu,  1 Mar 2012 13:53:30 -0800 (PST)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id 617E721E8230 for <ietf@ietf.org>; Thu,  1 Mar 2012 13:53:30 -0800 (PST)
Received: by ggmi1 with SMTP id i1so603775ggm.31 for <ietf@ietf.org>; Thu, 01 Mar 2012 13:53:30 -0800 (PST)
Received-SPF: pass (google.com: domain of barryleiba.mailing.lists@gmail.com designates 10.100.252.14 as permitted sender) client-ip=10.100.252.14; 
Authentication-Results: mr.google.com; spf=pass (google.com: domain of barryleiba.mailing.lists@gmail.com designates 10.100.252.14 as permitted sender) smtp.mail=barryleiba.mailing.lists@gmail.com; dkim=pass header.i=barryleiba.mailing.lists@gmail.com
Received: from mr.google.com ([10.100.252.14]) by 10.100.252.14 with SMTP id z14mr3013237anh.88.1330638810084 (num_hops = 1); Thu, 01 Mar 2012 13:53:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=y1ZigbIKtPR9zeDwXnPVJbd2VXm7Asiq0efPNn8HCPM=; b=KkIAluzOmDcr5OXcPGmIpuR7z4KevD7S1rul23oYu+Er5E7U1D1/ZtGAuB+T4q1dVG hTzgFBP7caedhhLTVpcjVMHrfdx/b+6xNn4cfPxaBGuC2tlnaNAHLnCH3dMadQJICExU p7ADNCWsPVRpNeHuMaEApKcxZoODslsQH4DDZVtz2/Q3tHLM6Dtk/BQo+a1evNM0Bay8 6am81ncbSw/2p5Z+oEFvvmQZV1hzovRzF1Eo1l5apXt7xt3DkxyLA27fNnWS4ptgLTWc XImEkHlGykSUHT7ZR3Lstr8gBIfjH/vkhMmhMZ0eNB9+yt3ZiBPHjvWjrg0pXMRhue0V ODtQ==
MIME-Version: 1.0
Received: by 10.100.252.14 with SMTP id z14mr2388161anh.88.1330638809989; Thu, 01 Mar 2012 13:53:29 -0800 (PST)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.147.106.16 with HTTP; Thu, 1 Mar 2012 13:53:29 -0800 (PST)
In-Reply-To: <6.2.5.6.2.20120301120015.0940b2c0@resistor.net>
References: <20120301004219.15266.76505.idtracker@ietfa.amsl.com> <6.2.5.6.2.20120301120015.0940b2c0@resistor.net>
Date: Thu, 1 Mar 2012 16:53:29 -0500
X-Google-Sender-Auth: E5Yf3UOL4faTQ7KSyLh90RDSHIo
Message-ID: <CAC4RtVA3F8gsBWY65W5KNDE+408EvtP+hp5GTzLg4FMgC1bdcQ@mail.gmail.com>
Subject: Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard
From: Barry Leiba <barryleiba@computer.org>
To: SM <sm@resistor.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: Alexey Melnikov <Alexey.Melnikov@isode.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Mar 2012 21:53:31 -0000

> This draft specifies a SMTP extension. =A0The IANA Considerations does no=
t
> mention registration in the the SMTP Service Extensions registry.

It certainly does, in the first paragraph:

   This specification requests IANA to add the PRIORITY SMTP extension
   to the "SMTP Service Extensions" registry (in
   http://www.iana.org/assignments/mail-parameters).

>=A0There
> should also be an indication about the extension being valid for the subm=
it
> port.

Section 3:
   7.  The PRIORITY extension is valid for the submission service
       [RFC6409] and LTMP [RFC2033].

(Murray has already commented on the misspelling of "LMTP" here.)

> This draft also defines the MT-Priority header field. =A0It is quite unus=
ual
> for a SMTP extension specification to define a mail header field. =A0If I=
 had
> an reservations about this draft, it would be on architectural grounds. =
=A0The
> draft tries really hard to transfer priority information over the Interne=
t
> and in a foreign environment.

This is my major concern about this protocol as well, as I note in the
PROTO writeup (which, unfortunately, can't be seen publicly because of
a limitation in the datatracker; perhaps I should post it here).  I'm
interested in hearing whether others share this concern, and what the
community consensus is about it.

Barry, document shepherd

From barryleiba.mailing.lists@gmail.com  Thu Mar  1 13:55:28 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 8B99521E8275 for <ietf@ietfa.amsl.com>; Thu,  1 Mar 2012 13:55:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.987
X-Spam-Level: 
X-Spam-Status: No, score=-102.987 tagged_above=-999 required=5 tests=[AWL=-0.010, 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 2KYd41Q0xnOA for <ietf@ietfa.amsl.com>; Thu,  1 Mar 2012 13:55:26 -0800 (PST)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by ietfa.amsl.com (Postfix) with ESMTP id A2AF421E8262 for <ietf@ietf.org>; Thu,  1 Mar 2012 13:55:25 -0800 (PST)
Received: by yenm5 with SMTP id m5so598818yen.31 for <ietf@ietf.org>; Thu, 01 Mar 2012 13:55:25 -0800 (PST)
Received-SPF: pass (google.com: domain of barryleiba.mailing.lists@gmail.com designates 10.236.79.202 as permitted sender) client-ip=10.236.79.202; 
Authentication-Results: mr.google.com; spf=pass (google.com: domain of barryleiba.mailing.lists@gmail.com designates 10.236.79.202 as permitted sender) smtp.mail=barryleiba.mailing.lists@gmail.com; dkim=pass header.i=barryleiba.mailing.lists@gmail.com
Received: from mr.google.com ([10.236.79.202]) by 10.236.79.202 with SMTP id i50mr10003869yhe.61.1330638925353 (num_hops = 1); Thu, 01 Mar 2012 13:55:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=q2lq8+67+5nfRr0Edn6v0EmW9tief0R7OYjIwAoXRcs=; b=EaniTzK/atarEbHU5C+mV9m81aInc3dz2sI0+Ibuiafyi04wawYkaES5amzcXG9/gl UUgR7mDlKGb/v661Vr6Vnib22w+q7If9PZM/xRWnmtgFKKzyTWqAO1xEZZyJEp4DdgT3 1TFV2XnEX6oh306x8MVzQa+wGhotph74vFEcUx7QduXzVpT3ie0gQbBWwLpgdoq1mE6p pfuEhLw1H0nFvBJiaSsYA4oycFAQEsqJWveL81sc03T/B/14l815+6GAykVye0K/RxN5 XdvrlVuVbJFTu3SmGVquTa3ckuzYtZ9mkAbGQG3CoOdh0R7Af/QLVBAHx4Y54dyTwoJ1 o4hQ==
MIME-Version: 1.0
Received: by 10.236.79.202 with SMTP id i50mr7903688yhe.61.1330638925271; Thu, 01 Mar 2012 13:55:25 -0800 (PST)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.147.106.16 with HTTP; Thu, 1 Mar 2012 13:55:25 -0800 (PST)
In-Reply-To: <CAC4RtVDeXwCLh9R_bNmLwEC5g_4Dv9HadOpXMwbSz5RT2m+jUg@mail.gmail.com>
References: <20120301004219.15266.76505.idtracker@ietfa.amsl.com> <CAC4RtVDeXwCLh9R_bNmLwEC5g_4Dv9HadOpXMwbSz5RT2m+jUg@mail.gmail.com>
Date: Thu, 1 Mar 2012 16:55:25 -0500
X-Google-Sender-Auth: hC0LXIA6LLOTM1L9f_kMw1goKTw
Message-ID: <CAC4RtVB1G_HjYNug0Fvq7LPSnzqG2KxH-PY6nv=nBZKv-uXTLA@mail.gmail.com>
Subject: Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard
From: Barry Leiba <barryleiba@computer.org>
To: ietf@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Cc: Pete Resnick <presnick@qualcomm.com>, Alexey Melnikov <Alexey.Melnikov@isode.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Mar 2012 21:55:28 -0000

Also, because it's not publicly visible, here's my PROTO writeup for
this document:

The publication of draft-melnikov-smtp-priority as a Proposed Standard
is requested by an individual contributor.

(1) What type of RFC is being requested (BCP, Proposed Standard,
Internet Standard, Informational, Experimental, or Historic)?  Why
is this the proper type of RFC?  Is this type of RFC indicated in the
title page header?

This document proposes a standard protocol extension to SMTP.  It is
possible for the proposal to go through as Experimental, but the
shepherd and the participants in the discussion of the document
believe that Proposed Standard is correct.  The strongest argument for
Experimental is probably the new mechanism of tunneling the SMTP
parameters through servers that don't support them by using reserved
message header fields (see more below).

(2) The IESG approval announcement includes a Document Announcement
Write-Up. Please provide such a Document Announcement Write-Up. Recent
examples can be found in the "Action" announcements for approved
documents. The approval announcement contains the following sections:

 Technical Summary

  Relevant content can frequently be found in the abstract
  and/or introduction of the document. If not, this may be
  an indication that there are deficiencies in the abstract
  or introduction.

This defines an extension to SMTP whereby messages are sent with a
"priority", enabling the receiving Message Transfer Agent to take the
priority into account for onward processing.  The goal is to process
and/or transfer higher priority messages first.

 Working Group Summary

  Was the document considered in any WG, and if so, why was
  it not adopted as a work item there? Was there controversy
  about particular points that caused the WG to not adopt the
  document?

There are currently no appropriate email-related working groups.  The
ADs and AppsAWG chairs considered the document for the Apps Area WG,
but decided that it would be done best as an individual submission,
and did not need the attention of the working group.

 Document Quality

  Are there existing implementations of the protocol? Have a
  significant number of vendors indicated their plan to
  implement the specification? Are there any reviewers that
  merit special mention as having done a thorough review,
  e.g., one that resulted in important changes or a
  conclusion that the document had no substantive issues? If
  there was a MIB Doctor, Media Type or other expert review,
  what was its course (briefly)? In the case of a Media Type
  review, on what date was the request posted?

There is at least one prototype implementation, and plans for at least
one other after publication.  This is largely being done for a
particular use case, and the proponents are aware of some of the
tradeoffs they've made.  The shepherd has some concern about the
broader applicability of this as a standard, given those trade-offs.
That said, some of them had to be made, and there is value in
implementing features from proprietary email systems in standardized
ways on the open Internet.  The shepherd supports that general effort.

 Personnel

  Who is the Document Shepherd? Who is the Responsible Area
  Director?

Barry Leiba is the document shepherd; Pete Resnick is the Responsible AD.

(3) Briefly describe the review of this document that was performed by
the Document Shepherd.  If this version of the document is not ready
for publication, please explain why the document is being forwarded to
the IESG.

I have reviewed several versions of the document as it has progressed
through the stages of discussion and modification, and I think this
version is ready to go forward.  I would like IETF community input on
some of the trade-offs, particularly those created by the parameter
tunneling and those involving the trust model (see below).

(4) Does the document Shepherd have any concerns about the depth or
breadth of the reviews that have been performed?

The document has had sufficient review from the email community, on
the ietf-smtp list and through individual reviews.  I have no concerns
about the level of review.

(5) Do portions of the document need review from a particular or from
broader perspective, e.g., security, operational complexity, AAA, DNS,
DHCP, XML, or internationalization? If so, describe the review that
took place.

I would like to see SecDir and OpsDir reviews during the last-call process.

(6) Describe any specific concerns or issues that the Document Shepherd
has with this document that the Responsible Area Director and/or the
IESG should be aware of? For example, perhaps he or she is uncomfortable
with certain parts of the document, or has concerns whether there really
is a need for it. In any event, if the interested community has
discussed those issues and has indicated that it still wishes to advance
the document, detail those concerns here.

The most significant item that needs to be called out is the issue of
tunneling the PRIORITY value through non-conforming MTAs by turning it
into a message header field (MT-Priority) and then back again.  This
is a problematic technique, but is an important capability for those
who need and intend to implement this extension.  It creates a trust
issue, wherein a message containing MT-Priority can be originated with
a Message Submission Agent that does not know about this extension,
and when the message hits a Message Transfer Agent that does support
this, the header field will be turned back into a valid PRIORITY
value, on the unwarranted assumption that it was authorized.
Intermediate MTAs have no way to distinguish this situation from one
where the field was tunneled legitimately.

The counter-argument is that the use case for this specification
involves out-of-band trust relationships, and that such situations
will be known and dealt with.  I believe that limits the usability of
those features on the open Internet, with other use cases.

(7) Has each author confirmed that any and all appropriate IPR
disclosures required for full conformance with the provisions of BCP 78
and BCP 79 have already been filed. If not, explain why.

Yes.

(8) Has an IPR disclosure been filed that references this document?
If so, summarize any discussion and conclusion regarding the IPR
disclosures.

No, and there are no known IPR issues with this document.

(9) How solid is the consensus of the interested community behind this
document? Does it represent the strong concurrence of a few individuals,
with others being silent, or does the interested community as a whole
understand and agree with it?

The consensus for this is solid, but relatively small.  A number of
participants/reviewers have expressed interest in the concept, though
it's not clear how much implementation is planned.

(10) Has anyone threatened an appeal or otherwise indicated extreme
discontent? If so, please summarise the areas of conflict in separate
email messages to the Responsible Area Director. (It should be in a
separate email because this questionnaire is publicly available.)

No.

(11) Identify any ID nits the Document Shepherd has found in this
document. (See http://www.ietf.org/tools/idnits/ and the Internet-Drafts
Checklist). Boilerplate checks are not enough; this check needs to be
thorough.

The document refers to iana.org URLs at the shepherd's request, to
make it clear which registries are being referenced.  These URLs will
be removed before RFC publication.

(12) Describe how the document meets any required formal review
criteria, such as the MIB Doctor, media type, and URI type reviews.

No formal reviews are needed.

(13) Have all references within this document been identified as
either normative or informative?

Yes.

(14) Are there normative references to documents that are not ready for
advancement or are otherwise in an unclear state? If such normative
references exist, what is the plan for their completion?

No.

(15) Are there downward normative references references (see RFC 3967)?
If so, list these downward references to support the Area Director in
the Last Call procedure.

There is a normative reference to RFC 2033 (LMTP), which is
Informational.  This needs to be called out in the last-call note.

(16) Will publication of this document change the status of any existing
RFCs? Are those RFCs listed on the title page header, listed in the
abstract, and discussed in the introduction? If the RFCs are not listed
in the Abstract and Introduction, explain why, and point to the part of
the document where the relationship of this document to the other RFCs
is discussed. If this information is not in the document, explain why
the interested community considers it unnecessary.

No documents are modified by this one.

(17) Describe the Document Shepherd's review of the IANA considerations
section, especially with regard to its consistency with the body of the
document. Confirm that all protocol extensions that the document makes
are associated with the appropriate reservations in IANA registries.
Confirm that any referenced IANA registries have been clearly
identified. Confirm that newly created IANA registries include a
detailed specification of the initial contents for the registry, that
allocations procedures for future registrations are defined, and a
reasonable name for the new registry has been suggested (see RFC 5226).

The document contains several IANA actions, which are all clearly
specified and correct.  No new registries are created.

(18) List any new IANA registries that require Expert Review for future
allocations. Provide any public guidance that the IESG would find
useful in selecting the IANA Experts for these new registries.

None.

(19) Describe reviews and automated checks performed by to validate
sections of the document written in a formal language, such as XML code,
BNF rules, MIB definitions, etc.

I have run the usual idnits and ABNF checks, and all is OK.

From mnot@mnot.net  Thu Mar  1 14:09:37 2012
Return-Path: <mnot@mnot.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2251821E830B; Thu,  1 Mar 2012 14:09:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.721
X-Spam-Level: 
X-Spam-Status: No, score=-104.721 tagged_above=-999 required=5 tests=[AWL=-2.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 sILTHX-J4WBy; Thu,  1 Mar 2012 14:09:36 -0800 (PST)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) by ietfa.amsl.com (Postfix) with ESMTP id C49F321E8310; Thu,  1 Mar 2012 14:09:35 -0800 (PST)
Received: from mnot-mini.mnot.net (unknown [118.209.126.24]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 7117722E260; Thu,  1 Mar 2012 17:09:24 -0500 (EST)
Subject: Re: WG Review: Recharter of Hypertext Transfer Protocol Bis (httpbis)
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=us-ascii
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <4F4FB6E9.6020201@stpeter.im>
Date: Fri, 2 Mar 2012 09:09:20 +1100
Content-Transfer-Encoding: 7bit
Message-Id: <D8D647B3-B2FF-49BA-B98A-FF7CF03EB955@mnot.net>
References: <20120221181006.43AB121F87BF@ietfa.amsl.com> <4F4FB6E9.6020201@stpeter.im>
To: Peter Saint-Andre <stpeter@stpeter.im>
X-Mailer: Apple Mail (2.1257)
Cc: IETF discussion list <ietf@ietf.org>, iesg@ietf.org, ietf-http-wg@w3.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Mar 2012 22:09:37 -0000

WFM. Thanks, Peter.

On 02/03/2012, at 4:50 AM, Peter Saint-Andre wrote:

> <hat type='AD'/>
> 
> On 2/21/12 11:10 AM, IESG Secretary wrote:
>> A modified charter has been submitted for the Hypertext Transfer 
>> Protocol Bis (httpbis) working group in the Applications Area of the 
>> IETF.  The IESG has not made any determination as yet.  The modified 
>> charter is provided below for informational purposes only.  Please send 
>> your comments to the IESG mailing list (iesg@ietf.org) by Tuesday, 
>> February 28, 2012.
> 
> Clearly this rechartering request has triggered a lengthy discussion
> about web authentication. However, the only comment on the charter
> itself Stephen Farrell's noting that this bullet is a bit vague
> (specifically that it does not mention authentication):
> 
>> * Reflecting modern security requirements and practices
> 
> Stephen and I just had a chat about this matter. He and I came up with a
> proposed paragraph to add after that list of bullet points:
> 
>   In the initial phase of work on HTTP/2.0, new proposals
>   for authentication schemes can be made.  The WG will
>   select zero or more of those with a goal of choosing
>   at least one scheme that is better than those available
>   for HTTP/1.x.  Non-selected schemes might be discussed
>   with the IETF Security Area for further work there.
> 
> Your comments are welcome.
> 
> Peter
> 
> -- 
> Peter Saint-Andre
> https://stpeter.im/
> 
> 

--
Mark Nottingham   http://www.mnot.net/




From sm@resistor.net  Thu Mar  1 14:10:23 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 3986B21E82BA for <ietf@ietfa.amsl.com>; Thu,  1 Mar 2012 14:10:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.646
X-Spam-Level: 
X-Spam-Status: No, score=-102.646 tagged_above=-999 required=5 tests=[AWL=-0.047, 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 UT2PIogPwHKQ for <ietf@ietfa.amsl.com>; Thu,  1 Mar 2012 14:10:22 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 863FF21E8308 for <ietf@ietf.org>; Thu,  1 Mar 2012 14:10:22 -0800 (PST)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id q21MAERi008250; Thu, 1 Mar 2012 14:10:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1330639819; i=@resistor.net; bh=7mg0AI3EvVN/KS8giu9aTXW83ju+oDeZcsq52+xsnQM=; h=Message-Id:Date:To:From:Subject:Cc:In-Reply-To:References: Mime-Version:Content-Type; b=Fnlcd7iZ75lkdzYMSLQ6TiFCH2O8z20auVT0CHeFizZHk2M9j6KQdbXjKeVJqU0fV 8bFFN22at6o8pdKIQceJVOul0F3en33GYgh4U6hBVvWF2WKer2oU07oPWZ3zCmL3Oe hef+kyyBrTANvybSOoUo+0jtjiEXmpBzIClOJ/0w=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1330639819; i=@resistor.net; bh=7mg0AI3EvVN/KS8giu9aTXW83ju+oDeZcsq52+xsnQM=; h=Message-Id:Date:To:From:Subject:Cc:In-Reply-To:References: Mime-Version:Content-Type; b=TWNeKaHcbiPVIaP/JrB/CTN9MbWmgZlJTKi51bFQ0H9vs3W0hZzi4/z5whSpJXqjs gCHhZTG3RhDw6JemzRrqmMHJHGoQSr9XzYy7AjgrF14mgVcojiaAlbz8Ir3k21Ht43 CiWCi6oc2CYgw1s6s5KTEuwdlRdGiLC7xNPR884U=
Message-Id: <6.2.5.6.2.20120301140000.09711f20@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 01 Mar 2012 14:08:33 -0800
To: Barry Leiba <barryleiba@computer.org>
From: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard
In-Reply-To: <CAC4RtVA3F8gsBWY65W5KNDE+408EvtP+hp5GTzLg4FMgC1bdcQ@mail.g mail.com>
References: <20120301004219.15266.76505.idtracker@ietfa.amsl.com> <6.2.5.6.2.20120301120015.0940b2c0@resistor.net> <CAC4RtVA3F8gsBWY65W5KNDE+408EvtP+hp5GTzLg4FMgC1bdcQ@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: Alexey Melnikov <Alexey.Melnikov@isode.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Mar 2012 22:10:23 -0000

Hi Barry,
At 13:53 01-03-2012, Barry Leiba wrote:
>It certainly does, in the first paragraph:

I missed that.

>Section 3:
>    7.  The PRIORITY extension is valid for the submission service
>        [RFC6409] and LTMP [RFC2033].

And that one.

>This is my major concern about this protocol as well, as I note in the
>PROTO writeup (which, unfortunately, can't be seen publicly because of
>a limitation in the datatracker; perhaps I should post it here).  I'm
>interested in hearing whether others share this concern, and what the
>community consensus is about it.

I read the PROTO writeup.  The other problem may be a bug.  I did not 
report it.

Regards,
-sm 


From msk@cloudmark.com  Thu Mar  1 14:16:04 2012
Return-Path: <msk@cloudmark.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 552E921E830D for <ietf@ietfa.amsl.com>; Thu,  1 Mar 2012 14:16:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.604
X-Spam-Level: 
X-Spam-Status: No, score=-102.604 tagged_above=-999 required=5 tests=[AWL=-0.005, 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 4eKLgHZbzLzm for <ietf@ietfa.amsl.com>; Thu,  1 Mar 2012 14:16:03 -0800 (PST)
Received: from ht2-outbound.cloudmark.com (ht2-outbound.cloudmark.com [72.5.239.26]) by ietfa.amsl.com (Postfix) with ESMTP id B739221E8024 for <ietf@ietf.org>; Thu,  1 Mar 2012 14:16:03 -0800 (PST)
Received: from EXCH-MBX901.corp.cloudmark.com ([fe80::addf:849a:f71c:4a82]) by exch-htcas902.corp.cloudmark.com ([fe80::e82a:4f80:7f44:eaf7%12]) with mapi id 14.01.0355.002; Thu, 1 Mar 2012 14:16:03 -0800
From: "Murray S. Kucherawy" <msk@cloudmark.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard
Thread-Topic: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard
Thread-Index: AQHM9/jjCHx8F3+wt0yyf3qeIuiGkA==
Date: Thu, 1 Mar 2012 22:16:03 +0000
Message-ID: <9452079D1A51524AA5749AD23E00392806FE0C@exch-mbx901.corp.cloudmark.com>
References: <20120301004219.15266.76505.idtracker@ietfa.amsl.com> <6.2.5.6.2.20120301120015.0940b2c0@resistor.net>
In-Reply-To: <6.2.5.6.2.20120301120015.0940b2c0@resistor.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.20.2.121]
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, 01 Mar 2012 22:16:04 -0000

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of S=
M
> Sent: Thursday, March 01, 2012 1:36 PM
> To: ietf@ietf.org
> Cc: Alexey Melnikov
> Subject: Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple
> Mail Transfer Protocol extension for Message Transfer Priorities) to
> Proposed Standard
>=20
> This draft also defines the MT-Priority header field.  It is quite
> unusual for a SMTP extension specification to define a mail header
> field.  If I had an reservations about this draft, it would be on
> architectural grounds.  The draft tries really hard to transfer
> priority information over the Internet and in a foreign environment.
> Although the draft is well-written and can be implemented, I have
> doubts about whether it will achieve its objective.  I unfortunately
> cannot support the publication of this draft as a Proposed Standard.

It's certainly true that this could be done as a pair of clustered drafts, =
but since they are clearly meant to be used together, and indeed have to be=
 when tunneling priority information through non-participating environments=
, their coupling into a single draft makes sense to me.

Doubling the work of the IESG and the RFC Editor doesn't seem reasonable he=
re.

-MSK

From stpeter@stpeter.im  Thu Mar  1 14:43:04 2012
Return-Path: <stpeter@stpeter.im>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0D0DD21E83B0 for <ietf@ietfa.amsl.com>; Thu,  1 Mar 2012 14:43:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.771
X-Spam-Level: 
X-Spam-Status: No, score=-102.771 tagged_above=-999 required=5 tests=[AWL=-0.172, 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 Jlk5RDTIg8hd for <ietf@ietfa.amsl.com>; Thu,  1 Mar 2012 14:43:03 -0800 (PST)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 71C8F21E8357 for <ietf@ietf.org>; Thu,  1 Mar 2012 14:43:03 -0800 (PST)
Received: from squire.local (unknown [64.101.72.114]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 411A74005A; Thu,  1 Mar 2012 15:54:44 -0700 (MST)
Message-ID: <4F4FFB75.5080303@stpeter.im>
Date: Thu, 01 Mar 2012 15:43:01 -0700
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.5; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: Scott Kitterman <scott@kitterman.com>
Subject: Re: Last Call: <draft-ietf-appsawg-xdash-03.txt> (Deprecating Use of the "X-" Prefix in Application Protocols) to Best Current Practice
References: <20120301184750.21152.93044.idtracker@ietfa.amsl.com> <2328831.zKV7qZlmPL@scott-latitude-e6320>
In-Reply-To: <2328831.zKV7qZlmPL@scott-latitude-e6320>
X-Enigmail-Version: 1.3.5
OpenPGP: url=https://stpeter.im/stpeter.asc
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Mar 2012 22:43:04 -0000

On 3/1/12 12:00 PM, Scott Kitterman wrote:
> On Thursday, March 01, 2012 10:47:50 AM The IESG wrote:
>> The IESG has received a request from the Applications Area Working Group
>> WG (appsawg) to consider the following document:
>> - 'Deprecating Use of the "X-" Prefix in Application Protocols'
>>   <draft-ietf-appsawg-xdash-03.txt> as a 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-03-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
>>
>>
>>    Historically, designers and implementers of application protocols
>>    have often distinguished between "standard" and "non-standard"
>>    parameters by prefixing the latter with the string "X-" or similar
>>    constructions.  In practice, this convention causes more problems
>>    than it solves.  Therefore, this document deprecates the "X-"
>>    convention for textual parameters in application protocols.
> ...
> 
> 2.  Recommendations for Implementers of Application Protocols
> 
>    Implementers of application protocols MUST NOT treat the general
>    categories of "standard" and "non-standard" parameters in
>    programatically different ways within their applications.
> 
> Shouldn't this restrict itself to the naming of parameters?  Perhaps:
> 
> 2.  Recommendations for Implementers of Application Protocols
> 
>    Implementers of application protocols MUST NOT treat the general
>    naming of parameters in programmatically different ways within
>    their applications depending on if they are "standard" or "non-standard".

How about this?

   Implementations of application protocols MUST NOT programatically
   discriminate between "standard" and "non-standard" parameters based
   solely on the names of such parameters.

> Other than that nit, I think it looks good.

Thanks!

Peter

-- 
Peter Saint-Andre
https://stpeter.im/



From barryleiba.mailing.lists@gmail.com  Thu Mar  1 15:00:52 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 647E921E8217 for <ietf@ietfa.amsl.com>; Thu,  1 Mar 2012 15:00:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.986
X-Spam-Level: 
X-Spam-Status: No, score=-102.986 tagged_above=-999 required=5 tests=[AWL=-0.010, 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 enWL0PeIUCWj for <ietf@ietfa.amsl.com>; Thu,  1 Mar 2012 15:00:51 -0800 (PST)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id 880F721E819C for <ietf@ietf.org>; Thu,  1 Mar 2012 15:00:51 -0800 (PST)
Received: by ggmi1 with SMTP id i1so633249ggm.31 for <ietf@ietf.org>; Thu, 01 Mar 2012 15:00:51 -0800 (PST)
Received-SPF: pass (google.com: domain of barryleiba.mailing.lists@gmail.com designates 10.236.37.132 as permitted sender) client-ip=10.236.37.132; 
Authentication-Results: mr.google.com; spf=pass (google.com: domain of barryleiba.mailing.lists@gmail.com designates 10.236.37.132 as permitted sender) smtp.mail=barryleiba.mailing.lists@gmail.com; dkim=pass header.i=barryleiba.mailing.lists@gmail.com
Received: from mr.google.com ([10.236.37.132]) by 10.236.37.132 with SMTP id y4mr10467586yha.10.1330642851251 (num_hops = 1); Thu, 01 Mar 2012 15:00:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=sjwjfmvbJEk/pyiVDuAeYw2TT/NA7lMCuDjDC+/CqT0=; b=DYY6GAdbHBqKaWadJRr8GB7L0EA26tHcI0CjgJ13ADo1OF6aNYjR6HWoKDZeQLmKR1 H5ZqhY5IjLI+aw4xn2glNJytrinJAGM+9+J/OenXzzS/viMI9knGyDiuvPjvKkdi+HsZ BjHAdYHcaeRRfRQli9I7+CBpC74ixY13c4eK62VADVrbelbfYw4iN5OYicISowc0t4Mk 1wYvb26Bb/kLaPxXc255WXfXdGZuJ41U1rei+6SF/GClJm938lMrTcFijih+z4sHT48l 4i1qfi+Fz4t+crCKf3q218FRkmK0s3dAKoP2Vp2JM6p4Nhnlqnalez6/A/OEI52191eY Fbow==
MIME-Version: 1.0
Received: by 10.236.37.132 with SMTP id y4mr8261913yha.10.1330642851186; Thu, 01 Mar 2012 15:00:51 -0800 (PST)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.147.106.16 with HTTP; Thu, 1 Mar 2012 15:00:51 -0800 (PST)
In-Reply-To: <9452079D1A51524AA5749AD23E00392806FE0C@exch-mbx901.corp.cloudmark.com>
References: <20120301004219.15266.76505.idtracker@ietfa.amsl.com> <6.2.5.6.2.20120301120015.0940b2c0@resistor.net> <9452079D1A51524AA5749AD23E00392806FE0C@exch-mbx901.corp.cloudmark.com>
Date: Thu, 1 Mar 2012 18:00:51 -0500
X-Google-Sender-Auth: G0VyAHTQ0xHCmsDN7y31HiIVFEI
Message-ID: <CAC4RtVCm_=VkfHiP_93_AKbo-X3NZc=NEt2pX_cEg6LYHtHSEQ@mail.gmail.com>
Subject: Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard
From: Barry Leiba <barryleiba@computer.org>
To: "Murray S. Kucherawy" <msk@cloudmark.com>
Content-Type: multipart/alternative; boundary=20cf302d488277c96104ba366eac
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Mar 2012 23:00:52 -0000

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

Oh, it's absolutely true that if one is to define this sort of thing as a
combination of SMTP protocol and message header fields, that should be done
in a single specification.  What I'm interested in community input on is
whether the mechanism of transferring the information back and forth
between the two, and having SMTP protocol get involved in inspecting and
altering header fields is a good thing.

Barry, document shepherd

On Thursday, March 1, 2012, Murray S. Kucherawy wrote:

> > -----Original Message-----
> > From: ietf-bounces@ietf.org <javascript:;> [mailto:ietf-bounces@ietf.org<javascript:;>]
> On Behalf Of SM
> > Sent: Thursday, March 01, 2012 1:36 PM
> > To: ietf@ietf.org <javascript:;>
> > Cc: Alexey Melnikov
> > Subject: Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple
> > Mail Transfer Protocol extension for Message Transfer Priorities) to
> > Proposed Standard
> >
> > This draft also defines the MT-Priority header field.  It is quite
> > unusual for a SMTP extension specification to define a mail header
> > field.  If I had an reservations about this draft, it would be on
> > architectural grounds.  The draft tries really hard to transfer
> > priority information over the Internet and in a foreign environment.
> > Although the draft is well-written and can be implemented, I have
> > doubts about whether it will achieve its objective.  I unfortunately
> > cannot support the publication of this draft as a Proposed Standard.
>
> It's certainly true that this could be done as a pair of clustered drafts,
> but since they are clearly meant to be used together, and indeed have to be
> when tunneling priority information through non-participating environments,
> their coupling into a single draft makes sense to me.
>
> Doubling the work of the IESG and the RFC Editor doesn't seem reasonable
> here.
>
> -MSK
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org <javascript:;>
> https://www.ietf.org/mailman/listinfo/ietf
>

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

Oh, it&#39;s absolutely true that if one is to define this sort of thing as=
 a combination of SMTP protocol and message header fields, that should be d=
one in a single specification. =A0What I&#39;m interested in community inpu=
t on is whether the mechanism of transferring the information back and fort=
h between the two, and having SMTP protocol get involved in inspecting and =
altering header fields is a good thing.<div>
<br></div><div>Barry, document shepherd<br><br>On Thursday, March 1, 2012, =
Murray S. Kucherawy  wrote:<br><blockquote class=3D"gmail_quote" style=3D"m=
argin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">&gt; -----Ori=
ginal Message-----<br>

&gt; From: <a href=3D"javascript:;" onclick=3D"_e(event, &#39;cvml&#39;, &#=
39;ietf-bounces@ietf.org&#39;)">ietf-bounces@ietf.org</a> [mailto:<a href=
=3D"javascript:;" onclick=3D"_e(event, &#39;cvml&#39;, &#39;ietf-bounces@ie=
tf.org&#39;)">ietf-bounces@ietf.org</a>] On Behalf Of SM<br>

&gt; Sent: Thursday, March 01, 2012 1:36 PM<br>
&gt; To: <a href=3D"javascript:;" onclick=3D"_e(event, &#39;cvml&#39;, &#39=
;ietf@ietf.org&#39;)">ietf@ietf.org</a><br>
&gt; Cc: Alexey Melnikov<br>
&gt; Subject: Re: Last Call: &lt;draft-melnikov-smtp-priority-07.txt&gt; (S=
imple<br>
&gt; Mail Transfer Protocol extension for Message Transfer Priorities) to<b=
r>
&gt; Proposed Standard<br>
&gt;<br>
&gt; This draft also defines the MT-Priority header field. =A0It is quite<b=
r>
&gt; unusual for a SMTP extension specification to define a mail header<br>
&gt; field. =A0If I had an reservations about this draft, it would be on<br=
>
&gt; architectural grounds. =A0The draft tries really hard to transfer<br>
&gt; priority information over the Internet and in a foreign environment.<b=
r>
&gt; Although the draft is well-written and can be implemented, I have<br>
&gt; doubts about whether it will achieve its objective. =A0I unfortunately=
<br>
&gt; cannot support the publication of this draft as a Proposed Standard.<b=
r>
<br>
It&#39;s certainly true that this could be done as a pair of clustered draf=
ts, but since they are clearly meant to be used together, and indeed have t=
o be when tunneling priority information through non-participating environm=
ents, their coupling into a single draft makes sense to me.<br>

<br>
Doubling the work of the IESG and the RFC Editor doesn&#39;t seem reasonabl=
e here.<br>
<br>
-MSK<br>
_______________________________________________<br>
Ietf mailing list<br>
<a href=3D"javascript:;" onclick=3D"_e(event, &#39;cvml&#39;, &#39;Ietf@iet=
f.org&#39;)">Ietf@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/ietf" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/ietf</a><br>
</blockquote></div>

--20cf302d488277c96104ba366eac--

From john-ietf@jck.com  Thu Mar  1 15:05:20 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 5F80D21E8248 for <ietf@ietfa.amsl.com>; Thu,  1 Mar 2012 15:05:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.854
X-Spam-Level: 
X-Spam-Status: No, score=-102.854 tagged_above=-999 required=5 tests=[AWL=-0.255, 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 euUpvJ8RyO6j for <ietf@ietfa.amsl.com>; Thu,  1 Mar 2012 15:05:19 -0800 (PST)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id EAFD221E824F for <ietf@ietf.org>; Thu,  1 Mar 2012 15:05:11 -0800 (PST)
Received: from [198.252.137.7] (helo=PST.JCK.COM) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1S3EzE-000N80-Ka; Thu, 01 Mar 2012 18:00:36 -0500
Date: Thu, 01 Mar 2012 18:04:58 -0500
From: John C Klensin <john-ietf@jck.com>
To: stbryant@cisco.com
Subject: Re: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt>	(Allocation of an Associated Channel Code Point for Use by	ITU-T Ethernet based OAM) to Informational RFC
Message-ID: <C3E581FB44D46BF4128A2229@PST.JCK.COM>
In-Reply-To: <4F4FC252.9010001@cisco.com>
References: <20120222151252.32262.82157.idtracker@ietfa.amsl.com> <03a301ccf174$ff953290$febf97b0$@olddog.co.uk> <515703B08A3A064C9CC8C09ACCC710DC0631679E@XMB-RCD-103.cisco.com> <C71DA9B1-A61F-4C5D-8DCE-3702271CBB6D@vigilsec.com> <4F4FA70B.2030906@pi.nu> <D0F60388-D852-4815-917A-B14BF40C64FB@vigilsec.com> <BD60EA38ED03AF5A21868DF1@PST.JCK.COM> <4F4FC252.9010001@cisco.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Mar 2012 23:05:20 -0000

--On Thursday, March 01, 2012 18:39 +0000 Stewart Bryant
<stbryant@cisco.com> wrote:

>...
>> FWIW, this seems entirely appropriate to me.  If we do it this
>> way, I think it is important to note --for the benefit of
>> those more historically involved with the ITU and others--
>> that we routinely block our own documents on normative
>> references to work that is still in progress and, usually, do
>> not do related code point allocations until the blocking
>> referenced documents are ready.  Once the present I-D is
>> judged to be sufficiently ready, this approach would
>> therefore be IETF approval and a formal guarantee to the ITU
>> that a code point will be allocated if an when G.8113.1 is
>> approved and published, but not assignment of that code point
>> until the referenced base document is finished.
>> 
>> Completely normal procedurally.
>...
> To be clear John our normal requirement would be that the
> technical community achieved consensus that the base document
> was ready. I have never seen ITU-T consensus on the contents
> of G.8113.1 at any meeting that I have observed. What in your
> view is the criteria for determining that  G.8113.1 has
> achieved consensus?

Stewart, 

I don't think so.  

Let me suggest that there are two entirely separate issues here
and that talking about "technical community consensus" obscures
both of them.

(1) Whether, given the JWT and other agreements, the ITU has any
business developing G.8113.x at all, or whether they should be
simply submitting ideas to the IETF for consideration.  Many of
us think that, under that agreement, the G.8113 activity is
inappropriate.  But the ITU has obviously decided otherwise and
we have no enforcement capability to prevent them from doing so
(whether we should or should not is pretty much irrelevant at
this point, at least IMO).  Whether the "technical community"
has achieved consensus is not relevant either, the only thing
that matters is whether G.8113.1 is, or will be, fully approved
by the ITU under ITU procedures.

(2) Whether it is reasonable or appropriate for the IETF to use
our responsibility for code point assignments and consequent
relationship with IANA to try to keep protocols that are not
consistent with our design judgment and aesthetics --no matter
how grounded in experience and good engineering-- off the
Internet.  That is the "Internet gatekeeper" function about
which, as you know, I've expressed concern in other contexts.  I
think the answer has got to be "we can, should, and always will
exercise quality control on stable specifications and normative
references but, unless we can justify being sure of our own
infallibility, we cannot and should not try to prevent another
body from deploying a specification on the Internet by using our
control of the registration model".   Telling people why we
think their ideas are sub-optimal is fine, as is identifying any
risks we see in appropriate and visible places, but telling
another group what they can't do because the IETF doesn't like
the idea isn't.

And I think that distinction is entirely consistent with Russ's
suggestion.

best,
   john





From sm@resistor.net  Thu Mar  1 15:24: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 EA74F21F8755 for <ietf@ietfa.amsl.com>; Thu,  1 Mar 2012 15:24:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.646
X-Spam-Level: 
X-Spam-Status: No, score=-102.646 tagged_above=-999 required=5 tests=[AWL=-0.047, 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 QQ5WApU2LcdC for <ietf@ietfa.amsl.com>; Thu,  1 Mar 2012 15:24:38 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id D107721F8753 for <ietf@ietf.org>; Thu,  1 Mar 2012 15:24:38 -0800 (PST)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id q21NOYci008791 for <ietf@ietf.org>; Thu, 1 Mar 2012 15:24:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1330644278; i=@resistor.net; bh=ae3hbNnz9Z+DcNJA6U6VCIq32fB5am/T49r0/XRyaNA=; h=Message-Id:Date:To:From:Subject:In-Reply-To:References: Mime-Version:Content-Type:Cc; b=SoxZMlLRJr59c3PwGRUEA4ruxjdD31z810LooenCYIRY+KC6CfjJpiK+niOme1Yv0 WV3HbtQ10jwXl15kSj3J4MTEj5EfFi0GIG9QIle+lPhCarXX75L6tXpX81ubhWHm3v EJ8iGHT35eSXArYqqDMJOPQKOtBM+Ku6UEUJPFww=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1330644278; i=@resistor.net; bh=ae3hbNnz9Z+DcNJA6U6VCIq32fB5am/T49r0/XRyaNA=; h=Message-Id:Date:To:From:Subject:In-Reply-To:References: Mime-Version:Content-Type:Cc; b=IQWS5Kaxwxl+rxFiH9ITIoeeKA0hekbFaZ/fypc1oK3GSrY+oqNBu6QLLTNltiOqZ tEjWbHW0PiKlfIYDvqTGpdyhVh9hNK3wx2ZPQHDQ2KfsQdvWNOAgv8jPRcVwDCJez+ fr8FOhSVfpsVcxOZ5EPYNkWdP47jwDJCUYeXKRq0=
Message-Id: <6.2.5.6.2.20120301141041.09b6b9e0@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 01 Mar 2012 14:31:40 -0800
To: ietf@ietf.org
From: SM <sm@resistor.net>
Subject: Re: [marf] Last Call: <draft-ietf-marf-spf-reporting-08.txt> (SPF	Authentication Failure Reporting using the Abuse Report Format) to	Proposed Standard
In-Reply-To: <9452079D1A51524AA5749AD23E00392806F917@exch-mbx901.corp.cl oudmark.com>
References: <20120301004643.17274.83943.idtracker@ietfa.amsl.com> <6.2.5.6.2.20120229181328.0a95a9f8@resistor.net> <9452079D1A51524AA5749AD23E00392806F917@exch-mbx901.corp.cloudmark.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Mar 2012 23:24:40 -0000

At 11:14 01-03-2012, Murray S. Kucherawy wrote:
>Would "ADMD" and an informative reference to RFC5598 be more appropriate?

   There exist cases in which the administrator of domain name employing
  [SPF] for announcing sending practices may want to know when messages are
   received via unauthorized routing.

>A number of registries are using this wording already and there's 
>been no objection to date.  Do you have a better suggestion?

It's not an objection.  The comments were labelled as editorial.

draft-nottingham-appsawg-happiana-00 contains some suggestions.

Regards,
-sm  


From msk@cloudmark.com  Thu Mar  1 15:38:24 2012
Return-Path: <msk@cloudmark.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 52B0121E83CD for <ietf@ietfa.amsl.com>; Thu,  1 Mar 2012 15:38:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.604
X-Spam-Level: 
X-Spam-Status: No, score=-102.604 tagged_above=-999 required=5 tests=[AWL=-0.005, 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 eyTSEwpg0Pxp for <ietf@ietfa.amsl.com>; Thu,  1 Mar 2012 15:38:23 -0800 (PST)
Received: from ht2-outbound.cloudmark.com (ht2-outbound.cloudmark.com [72.5.239.26]) by ietfa.amsl.com (Postfix) with ESMTP id 73C3621E8035 for <ietf@ietf.org>; Thu,  1 Mar 2012 15:38:23 -0800 (PST)
Received: from EXCH-MBX901.corp.cloudmark.com ([fe80::addf:849a:f71c:4a82]) by exch-htcas902.corp.cloudmark.com ([fe80::e82a:4f80:7f44:eaf7%12]) with mapi id 14.01.0355.002; Thu, 1 Mar 2012 15:38:22 -0800
From: "Murray S. Kucherawy" <msk@cloudmark.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard
Thread-Topic: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard
Thread-Index: AQHM9/jjCHx8F3+wt0yyf3qeIuiGkJZWlHaA//+CvcA=
Date: Thu, 1 Mar 2012 23:38:22 +0000
Message-ID: <9452079D1A51524AA5749AD23E00392807024F@exch-mbx901.corp.cloudmark.com>
References: <20120301004219.15266.76505.idtracker@ietfa.amsl.com> <6.2.5.6.2.20120301120015.0940b2c0@resistor.net> <9452079D1A51524AA5749AD23E00392806FE0C@exch-mbx901.corp.cloudmark.com> <CAC4RtVCm_=VkfHiP_93_AKbo-X3NZc=NEt2pX_cEg6LYHtHSEQ@mail.gmail.com>
In-Reply-To: <CAC4RtVCm_=VkfHiP_93_AKbo-X3NZc=NEt2pX_cEg6LYHtHSEQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.20.2.121]
Content-Type: text/plain; charset="iso-8859-1"
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, 01 Mar 2012 23:38:24 -0000

> From: barryleiba.mailing.lists@gmail.com [mailto:barryleiba.mailing.lists=
@gmail.com] On Behalf Of Barry Leiba
> Sent: Thursday, March 01, 2012 3:01 PM
> To: Murray S. Kucherawy
> Cc: ietf@ietf.org
> Subject: Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mai=
l Transfer Protocol extension for Message Transfer Priorities) to Proposed =
Standard
>=20
> Oh, it's absolutely true that if one is to define this sort of thing as a=
 combination of SMTP protocol and
> message header fields, that should be done in a single specification. =A0=
What I'm interested in community input
> on is whether the mechanism of transferring the information back and fort=
h between the two, and having SMTP
> protocol get involved in inspecting and altering header fields is a good =
thing.

It took me a bit of reading of older SMTP extension documents to realize th=
at this was something new.  I had thought things like DELIVERBY did this, b=
ut I see now that's not the case.

To borrow some language from recent conversations that considered questions=
 like this, it is only a /proposed/ standard we're talking about.

That said, are there any existing implementations of this that can speak to=
 the question of unintended side effects?

-MSK

From housley@vigilsec.com  Thu Mar  1 15:52:09 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 0750221E801F for <ietf@ietfa.amsl.com>; Thu,  1 Mar 2012 15:52:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.553
X-Spam-Level: 
X-Spam-Status: No, score=-102.553 tagged_above=-999 required=5 tests=[AWL=0.046, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jMxz2Gz+8Pv8 for <ietf@ietfa.amsl.com>; Thu,  1 Mar 2012 15:52:08 -0800 (PST)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id 979AD21E8052 for <ietf@ietf.org>; Thu,  1 Mar 2012 15:52:06 -0800 (PST)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 80B0E9A4726; Thu,  1 Mar 2012 18:52:19 -0500 (EST)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([208.254.26.82]) by localhost (ronin.smetech.net [208.254.26.81]) (amavisd-new, port 10024) with ESMTP id X-tJ-QnkM-Wj; Thu,  1 Mar 2012 18:52:00 -0500 (EST)
Received: from [192.168.2.104] (pool-96-241-165-215.washdc.fios.verizon.net [96.241.165.215]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 76C4D9A470F; Thu,  1 Mar 2012 18:52:18 -0500 (EST)
Subject: Re: Last Call:<draft-betts-itu-oam-ach-code-point-03.txt>	(Allocation of anAssociated Channel Code Point for Use by	ITU-T Ethernet basedOAM) to Informational RFC
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <E4873516F3FC7547BCFE792C7D94039C015D125D@DEMUEXC013.nsn-intra.net>
Date: Thu, 1 Mar 2012 18:52:04 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <28D09181-4EAF-4770-963F-A57073D77AE7@vigilsec.com>
References: <20120222151252.32262.82157.idtracker@ietfa.amsl.com><03a301ccf174$ff953290$febf97b0$@olddog.co.uk><515703B08A3A064C9CC8C09ACCC710DC0631679E@XMB-RCD-103.cisco.com><C71DA9B1-A61F-4C5D-8DCE-3702271CBB6D@vigilsec.com><4F4FA70B.2030906@pi.nu><D0F60388-D852-4815-917A-B14BF40C64FB@vigilsec.com><BD60EA38ED03AF5A21868DF1@PST.JCK.COM> <4F4FC252.9010001@cisco.com> <444F9B86-84CD-4A21-BD02-067877052A0A@vigilsec.com> <E4873516F3FC7547BCFE792C7D94039C015D125D@DEMUEXC013.nsn-intra.net>
To: "Sprecher, Nurit (NSN - IL/Hod HaSharon)" <nurit.sprecher@nsn.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: Thu, 01 Mar 2012 23:52:09 -0000

Nurit:

Some people are using the lack of a code point as the reason that the =
cannot support the ITU-T document.  My approach tells the ITU-T that a =
code point is available to them IFF they are able to reach consensus.  =
The removes IETF from the discussion.  This creates a situation where =
G.8113.1 succeeded or fails based on the ITU-T members actions, with no =
finger pointing at the IETF.  This is completely a Layer 9 =
consideration, and it has noting to do with the technical content of the =
document.

Russ


On Mar 1, 2012, at 2:33 PM, Sprecher, Nurit (NSN - IL/Hod HaSharon) =
wrote:

> Russ,=20
> I propose to simply re-discuss it when and IFF G.8113.1 is mature and
> approved...
> Best regards,
> Nurit
>=20
>=20
> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf =
Of
> ext Russ Housley
> Sent: Thursday, March 01, 2012 9:12 PM
> To: IETF
> Subject: Re: Last Call:<draft-betts-itu-oam-ach-code-point-03.txt>
> (Allocation of anAssociated Channel Code Point for Use by ITU-T =
Ethernet
> basedOAM) to Informational RFC
>=20
>>>> Right now, there is no ITU-T approved document to reference.
>>>> I am certainly not an expert on ITU-T process, but my
>>>> understanding is that earliest that we could see an approved
>>>> G.8113.1 is December 2012.  My point is that we don't want to
>>>> assign a code point until the ITU-T approves their document.
>>>> However, if we are willing to assign a code point to G.8113.1
>>>> once it is approved, then this would be an approach where the
>>>> code point assignment would block on the approval of the
>>>> normative reference.
>>>>=20
>>>> I like this approach from the political point of view.  With
>>>> this approach the IETF tells the ITU-T that if and only if
>>>> they are able to achieve consensus on G.8113.1, then a code
>>>> point will be assigned.
>>> FWIW, this seems entirely appropriate to me.  If we do it this
>>> way, I think it is important to note --for the benefit of those
>>> more historically involved with the ITU and others-- that we
>>> routinely block our own documents on normative references to
>>> work that is still in progress and, usually, do not do related
>>> code point allocations until the blocking referenced documents
>>> are ready.  Once the present I-D is judged to be sufficiently
>>> ready, this approach would therefore be IETF approval and a
>>> formal guarantee to the ITU that a code point will be allocated
>>> if an when G.8113.1 is approved and published, but not
>>> assignment of that code point until the referenced base document
>>> is finished.
>>>=20
>>> Completely normal procedurally.
>>>=20
>> To be clear John our normal requirement would be that the
>> technical community achieved consensus that the base document
>> was ready. I have never seen ITU-T consensus on the contents
>> of G.8113.1 at any meeting that I have observed. What in your
>> view is the criteria for determining that  G.8113.1 has achieved
>> consensus?
>=20
>=20
> This is not an IETF problem, and I do not think that the IETF ought to
> be discussing the internal workings of the ITU-T process.  The point =
is
> to come up with a mechanism that allows the code point to be assigned =
if
> and only if the ITU-T does come to a consensus by whatever means is
> allowed by their own process.
>=20
> Russ
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From john@jlc.net  Thu Mar  1 15:54:20 2012
Return-Path: <john@jlc.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4A2E821E8132 for <ietf@ietfa.amsl.com>; Thu,  1 Mar 2012 15:54:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.329
X-Spam-Level: 
X-Spam-Status: No, score=-106.329 tagged_above=-999 required=5 tests=[AWL=0.270, 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 xg4vuTx-325p for <ietf@ietfa.amsl.com>; Thu,  1 Mar 2012 15:54:19 -0800 (PST)
Received: from mailhost.jlc.net (mailhost.jlc.net [199.201.159.4]) by ietfa.amsl.com (Postfix) with ESMTP id A68C821E8108 for <ietf@ietf.org>; Thu,  1 Mar 2012 15:54:19 -0800 (PST)
Received: by mailhost.jlc.net (Postfix, from userid 104) id E4CF233C99; Thu,  1 Mar 2012 18:54:19 -0500 (EST)
Date: Thu, 1 Mar 2012 18:54:19 -0500
From: John Leslie <john@jlc.net>
To: Barry Leiba <barryleiba@computer.org>
Subject: Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard
Message-ID: <20120301235419.GN27716@verdi>
References: <20120301004219.15266.76505.idtracker@ietfa.amsl.com> <6.2.5.6.2.20120301120015.0940b2c0@resistor.net> <9452079D1A51524AA5749AD23E00392806FE0C@exch-mbx901.corp.cloudmark.com> <CAC4RtVCm_=VkfHiP_93_AKbo-X3NZc=NEt2pX_cEg6LYHtHSEQ@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAC4RtVCm_=VkfHiP_93_AKbo-X3NZc=NEt2pX_cEg6LYHtHSEQ@mail.gmail.com>
User-Agent: Mutt/1.4.1i
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Mar 2012 23:54:20 -0000

Barry Leiba <barryleiba@computer.org> wrote:
> 
> Oh, it's absolutely true that if one is to define this sort of thing as a
> combination of SMTP protocol and message header fields, that should be done
> in a single specification.  What I'm interested in community input on is
> whether the mechanism of transferring the information back and forth
> between the two, and having SMTP protocol get involved in inspecting and
> altering header fields is a good thing.

   Heck, I owe Barry an honest reply...

draft-melnikov-smtp-priority-07 states:
] 
] This document allows a message priority to be tunneled through MTAs
] which don't support the PRIORITY SMTP extension by specifying how it
] can be represented in the message itself (using the MT-Priority
] header field).  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.

   ROTFL. It could come from literally anywhere, including MTAs you
wouldn't think are on-path.

   However, the draft continues:
] 
] Such trust can be realized, for example, by using DKIM Section 12.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) .

   This at least attempts to make the MT-Priority trustworthy.

   Myself, I don't think it's worth the trouble. DKIM positively invites
replay; I must be missing how S/MIME protects a header field; and lists
of trusted senders go out-of-date awfully quickly.

   I think tunneling like this is clever, but asking for trouble: and
I've seen too many instances of getting the trouble -- even without a
intentionally-bad actor.

   As to whether having SMTP protocol get involved in inspecting and
altering header fields is a good thing, that horse has left the barn;
nonetheless, it's error-prone and very vulnerable to bad-analysis in
the presence of known-bad actors.

   I believe I'd opt-out of paying any attention to MT-Priority.
Priority is fine along an unbroken path of trust, but IMHO should stop
at the first weak link.

   (Sorry, Alexey...)

--
John Leslie <john@jlc.net>

From scott@kitterman.com  Thu Mar  1 16:14:33 2012
Return-Path: <scott@kitterman.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BA5F521E81F5 for <ietf@ietfa.amsl.com>; Thu,  1 Mar 2012 16:14:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eFmhNUrqzMe1 for <ietf@ietfa.amsl.com>; Thu,  1 Mar 2012 16:14:33 -0800 (PST)
Received: from mailout03.controlledmail.com (mailout03.controlledmail.com [208.43.65.50]) by ietfa.amsl.com (Postfix) with ESMTP id E86A021E81E8 for <ietf@ietf.org>; Thu,  1 Mar 2012 16:14:32 -0800 (PST)
Received: from mailout03.controlledmail.com (localhost [127.0.0.1]) by mailout03.controlledmail.com (Postfix) with ESMTP id E5B47D04083; Thu,  1 Mar 2012 18:14:31 -0600 (CST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=2007-00; t=1330647272; bh=V87BQzp85kY3eECVPPyK9Fc337lefOou0M3o4Fqq8y4=; h=References:In-Reply-To:MIME-Version:Content-Type: Content-Transfer-Encoding:Subject:From:Date:To:Message-ID; b=E/oKyAtjpGBT9z890qMG2keTmZMx70qJUwRKI9olKyHa9qXPxy8gQMMSwB39Do9Os x3FTlNcoeZfsJFFG0GZ8uKGa2X83v2OSrGtjUwPgiSaFCpktDIyGl7ZH9U/SmQq3mQ SDYnMNzRNLE0z+X5WwYgcO5sJdQxhMjFCtpNSWIE=
Received: from 98.sub-97-11-68.myvzw.com (98.sub-97-11-68.myvzw.com [97.11.68.98]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailout03.controlledmail.com (Postfix) with ESMTPSA id 55BB7D0400C;  Thu,  1 Mar 2012 18:14:31 -0600 (CST)
References: <20120301184750.21152.93044.idtracker@ietfa.amsl.com> <2328831.zKV7qZlmPL@scott-latitude-e6320> <4F4FFB75.5080303@stpeter.im>
User-Agent: K-9 Mail for Android
In-Reply-To: <4F4FFB75.5080303@stpeter.im>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Subject: Re: Last Call: <draft-ietf-appsawg-xdash-03.txt> (Deprecating Use of the "X-" Prefix in Application Protocols) to Best Current Practice
From: Scott Kitterman <scott@kitterman.com>
Date: Thu, 01 Mar 2012 19:14:41 -0500
To: ietf@ietf.org
Message-ID: <61623076-6684-46d9-94bc-eefb2b1de6b9@email.android.com>
X-AV-Checked: ClamAV using ClamSMTP
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Mar 2012 00:14:33 -0000

Peter Saint-Andre <stpeter@stpeter.im> wrote:

>On 3/1/12 12:00 PM, Scott Kitterman wrote:
>> On Thursday, March 01, 2012 10:47:50 AM The IESG wrote:
>>> The IESG has received a request from the Applications Area Working
>Group
>>> WG (appsawg) to consider the following document:
>>> - 'Deprecating Use of the "X-" Prefix in Application Protocols'
>>>   <draft-ietf-appsawg-xdash-03.txt> as a 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-03-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
>>>
>>>
>>>    Historically, designers and implementers of application protocols
>>>    have often distinguished between "standard" and "non-standard"
>>>    parameters by prefixing the latter with the string "X-" or
>similar
>>>    constructions.  In practice, this convention causes more problems
>>>    than it solves.  Therefore, this document deprecates the "X-"
>>>    convention for textual parameters in application protocols.
>> ...
>> 
>> 2.  Recommendations for Implementers of Application Protocols
>> 
>>    Implementers of application protocols MUST NOT treat the general
>>    categories of "standard" and "non-standard" parameters in
>>    programatically different ways within their applications.
>> 
>> Shouldn't this restrict itself to the naming of parameters?  Perhaps:
>> 
>> 2.  Recommendations for Implementers of Application Protocols
>> 
>>    Implementers of application protocols MUST NOT treat the general
>>    naming of parameters in programmatically different ways within
>>    their applications depending on if they are "standard" or
>"non-standard".
>
>How about this?
>
>   Implementations of application protocols MUST NOT programatically
>   discriminate between "standard" and "non-standard" parameters based
>   solely on the names of such parameters.

I'm not quite sure.

Is this supposed to be about how one selects names or how one uses them. I'd thought it meant the former, but your revised text sounds like the latter to me.

Scott K


From john-ietf@jck.com  Thu Mar  1 16:14:41 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 BF59421E8235 for <ietf@ietfa.amsl.com>; Thu,  1 Mar 2012 16:14:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.846
X-Spam-Level: 
X-Spam-Status: No, score=-102.846 tagged_above=-999 required=5 tests=[AWL=-0.247, 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 zpJityrpzcLv for <ietf@ietfa.amsl.com>; Thu,  1 Mar 2012 16:14:41 -0800 (PST)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id DF06821E8011 for <ietf@ietf.org>; Thu,  1 Mar 2012 16:14:40 -0800 (PST)
Received: from [198.252.137.7] (helo=PST.JCK.COM) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1S3G4T-000ND2-5M; Thu, 01 Mar 2012 19:10:05 -0500
Date: Thu, 01 Mar 2012 19:14:26 -0500
From: John C Klensin <john-ietf@jck.com>
To: "Sprecher, Nurit (NSN - IL/Hod HaSharon)" <nurit.sprecher@nsn.com>, Russ Housley <housley@vigilsec.com>, Loa Andersson <loa@pi.nu>
Subject: RE: Last Call:<draft-betts-itu-oam-ach-code-point-03.txt>	(Allocation of anAssociated Channel Code Point for Use by	ITU-T Ethernet basedOAM) to Informational RFC
Message-ID: <8B5AE089F0643EE8C5867DBC@PST.JCK.COM>
In-Reply-To: <E4873516F3FC7547BCFE792C7D94039C015D1244@DEMUEXC013.nsn-intra.net>
References: <20120222151252.32262.82157.idtracker@ietfa.amsl.com> <03a301ccf174$ff953290$febf97b0$@olddog.co.uk> <515703B08A3A064C9CC8C09ACCC710DC0631679E@XMB-RCD-103.cisco.com> <C71DA9B1-A61F-4C5D-8DCE-3702271CBB6D@vigilsec.com> <4F4FA70B.2030906@pi.nu> <D0F60388-D852-4815-917A-B14BF40C64FB@vigilsec.com> <BD60EA38ED03AF5A21868DF1@PST.JCK.COM> <E4873516F3FC7547BCFE792C7D94039C015D1244@DEMUEXC013.nsn-intra.net>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Mar 2012 00:14:41 -0000

--On Thursday, March 01, 2012 19:38 +0100 "Sprecher, Nurit (NSN
- IL/Hod HaSharon)" <nurit.sprecher@nsn.com> wrote:

> Draft-betts asks a code point for a document which is not
> mature and not agreed yet. Usually we do not issue last call
> for a document in such a condition!

Actually, we do that fairly regularly.   Have a look at the RFC
Editor queue, see how many documents have a status that includes
"MISSREF", and you will get an idea of how many recent ones
there are.   Of course, for that analogy to hold, draft-betts
itself must be complete and competent.  But a forward normative
reference is not a problem: it just goes into the RFC Editor
queue and, normally, IANA doesn't start doing any assignments on
the basis of such documents until the problems/ references are
resolved and the RFC Editor is editing.

> And in addition, draft-betts has many issues that must be
> resolved first. 
> For example it must be clear for what the code point is
> requested. Draft-betts indicates that G.8113.1 is subjected to
> revisions...they may add more messages to G.8113.1 that will
> be hidden behind the code point, etc.  

IMO, that should not be part of the IETF's problem.  It is part
of the forward reference.  As far as I can tell, Russ is not
suggesting actually allocating a code point until (and unless)
G.8113.1 is formally approved and hence complete and "hiding"
nothing.

     john



From randy@psg.com  Thu Mar  1 18:27:46 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 9610121E8098 for <ietf@ietfa.amsl.com>; Thu,  1 Mar 2012 18:27:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.496
X-Spam-Level: 
X-Spam-Status: No, score=-2.496 tagged_above=-999 required=5 tests=[AWL=0.103,  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 p88PX9rgiT9w for <ietf@ietfa.amsl.com>; Thu,  1 Mar 2012 18:27:46 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 38FD221E804F for <ietf@ietf.org>; Thu,  1 Mar 2012 18:27:46 -0800 (PST)
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 1S3IDg-0004YE-Nh; Fri, 02 Mar 2012 02:27:45 +0000
Date: Fri, 02 Mar 2012 11:27:43 +0900
Message-ID: <m24nu7zqhs.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Barry Leiba <barryleiba@computer.org>
Subject: Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail	Transfer Protocol extension for Message Transfer Priorities) to	Proposed Standard
In-Reply-To: <CAC4RtVCm_=VkfHiP_93_AKbo-X3NZc=NEt2pX_cEg6LYHtHSEQ@mail.gmail.com>
References: <20120301004219.15266.76505.idtracker@ietfa.amsl.com> <6.2.5.6.2.20120301120015.0940b2c0@resistor.net> <9452079D1A51524AA5749AD23E00392806FE0C@exch-mbx901.corp.cloudmark.com> <CAC4RtVCm_=VkfHiP_93_AKbo-X3NZc=NEt2pX_cEg6LYHtHSEQ@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>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Mar 2012 02:27:46 -0000

> What I'm interested in community input on is whether the mechanism of
> transferring the information back and forth between the two, and
> having SMTP protocol get involved in inspecting and altering header
> fields is a good thing.

you're kidding, right?  talk about primrose path.  did you not notice
the three headed dog?  sheesh!

MTA should not muck with headers.

randy

From narten@us.ibm.com  Thu Mar  1 21:53:54 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 B9FE221F8A7F for <ietf@ietfa.amsl.com>; Thu,  1 Mar 2012 21:53:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.569
X-Spam-Level: 
X-Spam-Status: No, score=-109.569 tagged_above=-999 required=5 tests=[AWL=1.030, 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 gllNqr1l2isa for <ietf@ietfa.amsl.com>; Thu,  1 Mar 2012 21:53:54 -0800 (PST)
Received: from e1.ny.us.ibm.com (e1.ny.us.ibm.com [32.97.182.141]) by ietfa.amsl.com (Postfix) with ESMTP id D263E21F8A7B for <ietf@ietf.org>; Thu,  1 Mar 2012 21:53:53 -0800 (PST)
Received: from /spool/local by e1.ny.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <ietf@ietf.org> from <narten@us.ibm.com>; Fri, 2 Mar 2012 00:53:52 -0500
Received: from d01dlp02.pok.ibm.com (9.56.224.85) by e1.ny.us.ibm.com (192.168.1.101) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Fri, 2 Mar 2012 00:53:05 -0500
Received: from d01relay07.pok.ibm.com (d01relay07.pok.ibm.com [9.56.227.147]) by d01dlp02.pok.ibm.com (Postfix) with ESMTP id 99EC06E8049 for <ietf@ietf.org>; Fri,  2 Mar 2012 00:53:04 -0500 (EST)
Received: from d01av04.pok.ibm.com (d01av04.pok.ibm.com [9.56.224.64]) by d01relay07.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id q225r4ZX3645658 for <ietf@ietf.org>; Fri, 2 Mar 2012 00:53:04 -0500
Received: from d01av04.pok.ibm.com (loopback [127.0.0.1]) by d01av04.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id q225r40B026444 for <ietf@ietf.org>; Fri, 2 Mar 2012 00:53:04 -0500
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.27.192.143]) by d01av04.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id q225r3ak026424 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Fri, 2 Mar 2012 00:53:03 -0500
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [127.0.0.1]) by rotala.raleigh.ibm.com (8.14.4/8.12.5) with ESMTP id q225r2UK027857 for <ietf@ietf.org>; Fri, 2 Mar 2012 00:53:03 -0500
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.4/8.14.4/Submit) id q225r2V4027834 for ietf@ietf.org; Fri, 2 Mar 2012 00:53:02 -0500
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201203020553.q225r2V4027834@rotala.raleigh.ibm.com>
Date: Fri, 02 Mar 2012 00:53:02 -0500
To: ietf@ietf.org
Subject: Weekly posting summary for ietf@ietf.org
User-Agent: Heirloom mailx 12.5 7/5/10
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 12030205-6078-0000-0000-000008A16EB0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Mar 2012 05:53:54 -0000

Total of 183 messages in the last 7 days.
 
script run at: Fri Mar  2 00:53:02 EST 2012
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
  8.20% |   15 |  7.44% |   110386 | scott@kitterman.com
  6.56% |   12 |  6.44% |    95538 | sant9442@gmail.com
  4.37% |    8 |  6.65% |    98699 | nurit.sprecher@nsn.com
  5.46% |   10 |  4.50% |    66772 | msk@cloudmark.com
  4.37% |    8 |  5.13% |    76119 | stephen.farrell@cs.tcd.ie
  4.92% |    9 |  4.44% |    65967 | marka@isc.org
  3.83% |    7 |  4.94% |    73298 | barryleiba@computer.org
  4.37% |    8 |  3.81% |    56519 | sm@resistor.net
  2.73% |    5 |  4.21% |    62540 | touch@isi.edu
  3.83% |    7 |  2.69% |    39966 | johnl@iecc.com
  2.73% |    5 |  2.78% |    41292 | julian.reschke@gmx.de
  2.73% |    5 |  2.78% |    41258 | mnot@mnot.net
  2.73% |    5 |  2.54% |    37671 | john-ietf@jck.com
  2.19% |    4 |  2.78% |    41235 | housley@vigilsec.com
  2.73% |    5 |  2.10% |    31127 | paul.hoffman@vpnc.org
  2.19% |    4 |  2.38% |    35375 | stbryant@cisco.com
  2.19% |    4 |  1.84% |    27384 | paf@frobbit.se
  2.19% |    4 |  1.76% |    26079 | henrik@henriknordstrom.net
  2.19% |    4 |  1.66% |    24712 | stpeter@stpeter.im
  1.09% |    2 |  2.57% |    38088 | kkinnear@cisco.com
  1.64% |    3 |  1.72% |    25608 | loa@pi.nu
  1.64% |    3 |  1.40% |    20733 | vesely@tana.it
  1.64% |    3 |  1.34% |    19962 | w@1wt.eu
  1.64% |    3 |  1.33% |    19754 | dougb@dougbarton.us
  1.64% |    3 |  1.23% |    18253 | ajs@anvilwalrusden.com
  1.09% |    2 |  1.27% |    18787 | hongk@cisco.com
  1.09% |    2 |  1.02% |    15136 | adrien@qbik.com
  1.09% |    2 |  1.01% |    15066 | daedulus@btconnect.com
  1.09% |    2 |  1.01% |    14944 | stewe@stewe.org
  1.09% |    2 |  0.97% |    14344 | ynir@checkpoint.com
  1.09% |    2 |  0.81% |    12018 | john@jlc.net
  0.55% |    1 |  0.86% |    12757 | hsantos@santronics.com
  0.55% |    1 |  0.79% |    11726 | vincent.roca@inria.fr
  0.55% |    1 |  0.74% |    10999 | jouni.korhonen@nsn.com
  0.55% |    1 |  0.70% |    10348 | tevfik.sahin@turktelekom.com.tr
  0.55% |    1 |  0.66% |     9775 | narten@us.ibm.com
  0.55% |    1 |  0.66% |     9747 | presnick@qualcomm.com
  0.55% |    1 |  0.63% |     9339 | ben@nostrum.com
  0.55% |    1 |  0.60% |     8912 | ted.lemon@nominum.com
  0.55% |    1 |  0.59% |     8828 | dwing@cisco.com
  0.55% |    1 |  0.57% |     8414 | feng.f.huang@alcatel-sbell.com.cn
  0.55% |    1 |  0.56% |     8304 | tnadeau@lucidvision.com
  0.55% |    1 |  0.54% |     7962 | hallam@gmail.com
  0.55% |    1 |  0.50% |     7436 | ned+ietf@mauve.mrochek.com
  0.55% |    1 |  0.48% |     7152 | tbray@textuality.com
  0.55% |    1 |  0.48% |     7118 | david.black@emc.com
  0.55% |    1 |  0.46% |     6831 | patrik@frobbit.se
  0.55% |    1 |  0.44% |     6507 | bschlies@cisco.com
  0.55% |    1 |  0.43% |     6448 | ed.lewis@neustar.biz
  0.55% |    1 |  0.43% |     6368 | conte@isoc.org
  0.55% |    1 |  0.43% |     6353 | mohta@necom830.hpcl.titech.ac.jp
  0.55% |    1 |  0.42% |     6207 | tglassey@certichron.com
  0.55% |    1 |  0.41% |     6079 | nick@inex.ie
  0.55% |    1 |  0.37% |     5562 | iesg@ietf.org
  0.55% |    1 |  0.37% |     5428 | dhc@dcrocker.net
  0.55% |    1 |  0.36% |     5382 | randy@psg.com
--------+------+--------+----------+------------------------
100.00% |  183 |100.00% |  1484612 | Total


From ned+ietf@mauve.mrochek.com  Thu Mar  1 22:32:39 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 B515821E8078 for <ietf@ietfa.amsl.com>; Thu,  1 Mar 2012 22:32:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4KSFQVr0XKU4 for <ietf@ietfa.amsl.com>; Thu,  1 Mar 2012 22:32:39 -0800 (PST)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id 27A7A21E802B for <ietf@ietf.org>; Thu,  1 Mar 2012 22:32:39 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OCM8WH3WCG006Z2T@mauve.mrochek.com> for ietf@ietf.org; Thu, 1 Mar 2012 22:32:34 -0800 (PST)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OCI1CWJADS00ZUIL@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Thu, 1 Mar 2012 22:32:28 -0800 (PST)
From: ned+ietf@mauve.mrochek.com
Message-id: <01OCM8WDJZKI00ZUIL@mauve.mrochek.com>
Date: Thu, 01 Mar 2012 22:12:05 -0800 (PST)
Subject: Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to	Proposed Standard
In-reply-to: "Your message dated Thu, 01 Mar 2012 16:55:25 -0500" <CAC4RtVB1G_HjYNug0Fvq7LPSnzqG2KxH-PY6nv=nBZKv-uXTLA@mail.gmail.com>
MIME-version: 1.0
Content-type: TEXT/PLAIN
References: <20120301004219.15266.76505.idtracker@ietfa.amsl.com> <CAC4RtVDeXwCLh9R_bNmLwEC5g_4Dv9HadOpXMwbSz5RT2m+jUg@mail.gmail.com> <CAC4RtVB1G_HjYNug0Fvq7LPSnzqG2KxH-PY6nv=nBZKv-uXTLA@mail.gmail.com>
To: Barry Leiba <barryleiba@computer.org>
Cc: Pete Resnick <presnick@qualcomm.com>, Alexey Melnikov <Alexey.Melnikov@isode.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Mar 2012 06:32:39 -0000

> The most significant item that needs to be called out is the issue of
> tunneling the PRIORITY value through non-conforming MTAs by turning it
> into a message header field (MT-Priority) and then back again.  This
> is a problematic technique, but is an important capability for those
> who need and intend to implement this extension.  It creates a trust
> issue, wherein a message containing MT-Priority can be originated with
> a Message Submission Agent that does not know about this extension,
> and when the message hits a Message Transfer Agent that does support
> this, the header field will be turned back into a valid PRIORITY
> value, on the unwarranted assumption that it was authorized.
> Intermediate MTAs have no way to distinguish this situation from one
> where the field was tunneled legitimately.

There may not be substantial experience with doing this sort of thing in SMTP
relays, but there's plenty of experience doing it in gateways to other mail
environments, e.g., X.400 and many of the old LAN email systems. In fact one of
the more common fields that has been mapped this way is message transfer
priority, so there is considerably experience with fields having more or less
the same semantics as what is being proposed here.

I am unaware of any cases where this was abused, probably because increased
transfer priority doesn't buy you all that much in most cases. Related
but more user-visible features, e.g., importance (in the X.400 sense)
have been known to be abused, however.

That said, I think an important omission in this document is that it 
only allows MSA's to change message priorities to conform to site policy.
MTAs should also be allowed to do this.

Another issue is the silly prohibition against using Priority: and other header
fields to set priority levels. What if is existing site policy is in fact to
use those fields to determine message priority?

> The counter-argument is that the use case for this specification
> involves out-of-band trust relationships, and that such situations
> will be known and dealt with.  I believe that limits the usability of
> those features on the open Internet, with other use cases.

Not if MTAs aren't also allowed to enforce site policy.

				Ned

From paf@frobbit.se  Thu Mar  1 23:07:59 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 80AEB21F8B9C for <ietf@ietfa.amsl.com>; Thu,  1 Mar 2012 23:07:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.298
X-Spam-Level: 
X-Spam-Status: No, score=-2.298 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 ajSsRK3KKzeT for <ietf@ietfa.amsl.com>; Thu,  1 Mar 2012 23:07:59 -0800 (PST)
Received: from srv01.frobbit.se (srv01.frobbit.se [IPv6:2a02:80:3ffe::39]) by ietfa.amsl.com (Postfix) with ESMTP id C023021F8B52 for <ietf@ietf.org>; Thu,  1 Mar 2012 23:07:58 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by srv01.frobbit.se (Postfix) with ESMTP id EB2B11335C695; Fri,  2 Mar 2012 08:07:55 +0100 (CET)
X-Virus-Scanned: amavisd-new at frobbit.se
Received: from srv01.frobbit.se ([127.0.0.1]) by localhost (srv01.frobbit.se [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tVmZ+Yuba3pv; Fri,  2 Mar 2012 08:07:55 +0100 (CET)
Received: from [IPv6:2a02:80:3ffc::14] (unknown [IPv6:2a02:80:3ffc::14]) (Authenticated sender: paf01) by srv01.frobbit.se (Postfix) with ESMTP id B0A611335C688; Fri,  2 Mar 2012 08:07:55 +0100 (CET)
Subject: Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: multipart/alternative; boundary="Apple-Mail=_3DDB3869-97F2-4E04-BF36-BEBDB6AA493A"
From: =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
In-Reply-To: <CAC4RtVCm_=VkfHiP_93_AKbo-X3NZc=NEt2pX_cEg6LYHtHSEQ@mail.gmail.com>
Date: Fri, 2 Mar 2012 08:07:55 +0100
Message-Id: <0AC3C8D8-C895-4B04-B7C4-7AB47E81BAB2@frobbit.se>
References: <20120301004219.15266.76505.idtracker@ietfa.amsl.com> <6.2.5.6.2.20120301120015.0940b2c0@resistor.net> <9452079D1A51524AA5749AD23E00392806FE0C@exch-mbx901.corp.cloudmark.com> <CAC4RtVCm_=VkfHiP_93_AKbo-X3NZc=NEt2pX_cEg6LYHtHSEQ@mail.gmail.com>
To: Barry Leiba <barryleiba@computer.org>
X-Mailer: Apple Mail (2.1257)
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Mar 2012 07:07:59 -0000

--Apple-Mail=_3DDB3869-97F2-4E04-BF36-BEBDB6AA493A
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1


On 2 mar 2012, at 00:00, Barry Leiba wrote:

>  What I'm interested in community input on is whether the mechanism of =
transferring the information back and forth between the two, and having =
SMTP protocol get involved in inspecting and altering header fields is a =
good thing.

No, not change header fields.

  Patrik


--Apple-Mail=_3DDB3869-97F2-4E04-BF36-BEBDB6AA493A
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=iso-8859-1

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><br><div><div>On 2 mar 2012, at 00:00, Barry Leiba wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
font-family: 'Lucida Sans Typewriter'; 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; ">&nbsp;What =
I'm interested in community input on is whether the mechanism of =
transferring the information back and forth between the two, and having =
SMTP protocol get involved in inspecting and altering header fields is a =
good thing.</span></blockquote></div><br><div>No, not change header =
fields.</div><div><br></div><div>&nbsp; =
Patrik</div><div><br></div></body></html>=

--Apple-Mail=_3DDB3869-97F2-4E04-BF36-BEBDB6AA493A--

From dougb@dougbarton.us  Fri Mar  2 01:32:21 2012
Return-Path: <dougb@dougbarton.us>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2429921F8ADF for <ietf@ietfa.amsl.com>; Fri,  2 Mar 2012 01:32:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.94
X-Spam-Level: 
X-Spam-Status: No, score=-2.94 tagged_above=-999 required=5 tests=[AWL=-0.830,  BAYES_05=-1.11, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XqCYR+tyVsYr for <ietf@ietfa.amsl.com>; Fri,  2 Mar 2012 01:32:20 -0800 (PST)
Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by ietfa.amsl.com (Postfix) with ESMTP id 5D0E021F879A for <ietf@ietf.org>; Fri,  2 Mar 2012 01:32:19 -0800 (PST)
Received: (qmail 22611 invoked by uid 399); 2 Mar 2012 09:32:13 -0000
Received: from unknown (HELO 172-17-197-151.globalsuite.net) (dougb@dougbarton.us@12.207.105.210) by mail2.fluidhosting.com with ESMTPAM; 2 Mar 2012 09:32:13 -0000
X-Originating-IP: 12.207.105.210
X-Sender: dougb@dougbarton.us
Message-ID: <4F50939C.4020608@dougbarton.us>
Date: Fri, 02 Mar 2012 01:32:12 -0800
From: Doug Barton <dougb@dougbarton.us>
Organization: http://SupersetSolutions.com/
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:10.0.2) Gecko/20120224 Thunderbird/10.0.2
MIME-Version: 1.0
To: "John R. Levine" <johnl@iecc.com>
Subject: Re: DNS RRTYPEs, the difficulty with
References: <20120228015606.2227.qmail@joyce.lan> <4F4D53E2.5080803@dougbarton.us> <alpine.BSF.2.00.1202281745310.7969@joyce.lan>
In-Reply-To: <alpine.BSF.2.00.1202281745310.7969@joyce.lan>
X-Enigmail-Version: 1.3.5
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Mar 2012 09:32:21 -0000

On 02/28/2012 15:06, John R. Levine wrote:
> In your little dialog, the boss was entirely reasonable -- the practical
> benefit from implementing SPF records would be zip.
> 
>> Or, put more simply, your conclusion seems to be that we can never add
>> new RRs. Given that adding new RRs is crucial to the growth of the
>> Internet, I reject that conclusion completely.
> 
> No, I'm saying that it would be a lot more productive to help people
> improve their provisioning systems, rather than say how stupid they are
> for not doing what we want. 

Um, who called anyone stupid? As you pointed out above, the lack of
movement from SPF{TXT} to SPF{SPF} was entirely rational.

My point was that *we* need to learn from our experiences with SPF, and
not do the same things again.

> By the way, what's your opinion of draft-levine-dnsextlang-02?

It isn't clear to me what problem you're trying to solve. For resolving
name servers 3597 should be enough. For authoritative name servers your
idea is sort of interesting, but generally upgrading the software to
pick up support for new RRtypes is a good idea, since you'll also pick
up new security fixes, etc.


Doug

-- 
    If you're never wrong, you're not trying hard enough

From sant9442@gmail.com  Fri Mar  2 03:47:23 2012
Return-Path: <sant9442@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2BE3721F8B79 for <ietf@ietfa.amsl.com>; Fri,  2 Mar 2012 03:47:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[AWL=-0.294, BAYES_00=-2.599, MISSING_HEADERS=1.292, 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 MrfWYdYfoLPa for <ietf@ietfa.amsl.com>; Fri,  2 Mar 2012 03:47:22 -0800 (PST)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id A807521F8B78 for <ietf@ietf.org>; Fri,  2 Mar 2012 03:47:22 -0800 (PST)
Received: by ggmi1 with SMTP id i1so797332ggm.31 for <ietf@ietf.org>; Fri, 02 Mar 2012 03:47:22 -0800 (PST)
Received-SPF: pass (google.com: domain of sant9442@gmail.com designates 10.236.186.1 as permitted sender) client-ip=10.236.186.1; 
Authentication-Results: mr.google.com; spf=pass (google.com: domain of sant9442@gmail.com designates 10.236.186.1 as permitted sender) smtp.mail=sant9442@gmail.com; dkim=pass header.i=sant9442@gmail.com
Received: from mr.google.com ([10.236.186.1]) by 10.236.186.1 with SMTP id v1mr13343283yhm.4.1330688842341 (num_hops = 1); Fri, 02 Mar 2012 03:47:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=2M0wikOB58GrvNrZUDx9MZnVlk105bK/OPN35kwAx1A=; b=VZ5u9TtTXh0hi5+QiDB43ylheGGE8ZCiVj4AZaG/L0towXzIArFHOPBUaMWhK5bt7p m/LzEMhhkc99zH+NpsPtlcxOuloHRYi/nwieUp2eQQ5p03yYqA36wrdctbU+AoPGQSeq +KFYMG9oThWyDuPwtFNZCZjR07JZNiw0/yffUiBCIHhZ6Ux8qdV7G+3lxntFBhYezSLW cNHcrWBnyGgSzFvLFicZdu9eoTnbAiYwnlSYjX/kT161YXQPEA6bE6iO9Iv7l34c9kkb QXkSgNyxtyva6+nIsXo2L/IgdZaH/751FfCq8UWJbdIYx0nbSFOrsKAHjXzIP/XRt20L Gb5A==
Received: by 10.236.186.1 with SMTP id v1mr10554812yhm.4.1330688842293; Fri, 02 Mar 2012 03:47:22 -0800 (PST)
Received: from adsl-215-50-126.mia.bellsouth.net (99-3-147-93.lightspeed.miamfl.sbcglobal.net. [99.3.147.93]) by mx.google.com with ESMTPS id 32sm8360710anu.14.2012.03.02.03.47.19 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 02 Mar 2012 03:47:20 -0800 (PST)
Message-ID: <4F50B339.2030003@gmail.com>
Date: Fri, 02 Mar 2012 06:47:05 -0500
From: Hector <sant9442@gmail.com>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
CC: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to	Proposed Standard
References: <20120301004219.15266.76505.idtracker@ietfa.amsl.com>	<6.2.5.6.2.20120301120015.0940b2c0@resistor.net>	<9452079D1A51524AA5749AD23E00392806FE0C@exch-mbx901.corp.cloudmark.com> <CAC4RtVCm_=VkfHiP_93_AKbo-X3NZc=NEt2pX_cEg6LYHtHSEQ@mail.gmail.com>
In-Reply-To: <CAC4RtVCm_=VkfHiP_93_AKbo-X3NZc=NEt2pX_cEg6LYHtHSEQ@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Mar 2012 11:47:23 -0000

Barry Leiba wrote:

> What I'm interested in community input on is
> whether the mechanism of transferring the information back and forth
> between the two, and having SMTP protocol get involved in inspecting and
> altering header fields is a good thing.

I may be too old school, but I still believe "thou shall not tamper 
with mail" in principle, especially passthru.

Only with Network related control lines/headers that the transports 
deal with. If this header is one of these, I don't see an issue.

Also, in regards of the transport even processing the headers (which 
suggest analyzing the payload at DATA before the EOD response is 
issued), past concerns included the "delay factor", the scalability 
question, the dupe potentials, the current 10 min "timeout" too long 
and not always supported by clients, including ideas of using a "Keep 
Alive" for DATA shims that take too long.

If I understand where you going with this, IMV, I don't think it is a 
good thing SMTP systems should be expected will be processing the 
payload or its headers before the EOD is issued.

--
HLS


From barryleiba.mailing.lists@gmail.com  Fri Mar  2 06:26:49 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 A6AD821F85E1 for <ietf@ietfa.amsl.com>; Fri,  2 Mar 2012 06:26:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.986
X-Spam-Level: 
X-Spam-Status: No, score=-102.986 tagged_above=-999 required=5 tests=[AWL=-0.009, 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 8QNNEklBYS2f for <ietf@ietfa.amsl.com>; Fri,  2 Mar 2012 06:26:49 -0800 (PST)
Received: from mail-gy0-f172.google.com (mail-gy0-f172.google.com [209.85.160.172]) by ietfa.amsl.com (Postfix) with ESMTP id 0E1D221F85D9 for <ietf@ietf.org>; Fri,  2 Mar 2012 06:26:48 -0800 (PST)
Received: by ghbg16 with SMTP id g16so872918ghb.31 for <ietf@ietf.org>; Fri, 02 Mar 2012 06:26:48 -0800 (PST)
Received-SPF: pass (google.com: domain of barryleiba.mailing.lists@gmail.com designates 10.236.145.230 as permitted sender) client-ip=10.236.145.230; 
Authentication-Results: mr.google.com; spf=pass (google.com: domain of barryleiba.mailing.lists@gmail.com designates 10.236.145.230 as permitted sender) smtp.mail=barryleiba.mailing.lists@gmail.com; dkim=pass header.i=barryleiba.mailing.lists@gmail.com
Received: from mr.google.com ([10.236.145.230]) by 10.236.145.230 with SMTP id p66mr13755877yhj.27.1330698408681 (num_hops = 1); Fri, 02 Mar 2012 06:26:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=yXgbRygp2Yli/1dvXNcEKSvMftfVMbAMhW4RkW/I3dw=; b=g4cjPsvQSj5sqWhkiTSg9rdVSDW9q1ltD2sgATCZeeDY//+jkOy5NYddlsVFsKL/iv Th5o0RCGx04nROILR9uUuphg2thOfFsdD655uGI1yn04Ycqx/oTXtpcYoaK0FCz6eb9j bEEPPuep9vi/kAGvYkeBSVpKPievYoHzBAm8S5Hx4LRUpBJuLDsVkXRUr//xHUJ1SjA2 NyA1w3wpclgOxPTk7FFwackXu7OPeOKG6ITJWCDJIJ3IDOSkBzYcCgiEjOOfqqsEqsJ8 4V4qzo3XKfgsbroNJhmRK7Wb4k2/SYybb9EPpeSRh+RYap1L7O2mHxFv4QOKZ5+8xo4k jeXQ==
MIME-Version: 1.0
Received: by 10.236.145.230 with SMTP id p66mr10891622yhj.27.1330698408616; Fri, 02 Mar 2012 06:26:48 -0800 (PST)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.147.106.16 with HTTP; Fri, 2 Mar 2012 06:26:48 -0800 (PST)
In-Reply-To: <4F50B339.2030003@gmail.com>
References: <20120301004219.15266.76505.idtracker@ietfa.amsl.com> <6.2.5.6.2.20120301120015.0940b2c0@resistor.net> <9452079D1A51524AA5749AD23E00392806FE0C@exch-mbx901.corp.cloudmark.com> <CAC4RtVCm_=VkfHiP_93_AKbo-X3NZc=NEt2pX_cEg6LYHtHSEQ@mail.gmail.com> <4F50B339.2030003@gmail.com>
Date: Fri, 2 Mar 2012 09:26:48 -0500
X-Google-Sender-Auth: 9Z_xsrqFGHGFJNl0QOyVapriD0g
Message-ID: <CAC4RtVA_fBAVgsDbDDXEGBCfBqUke-8dA41h_NmjHAraay+0Tw@mail.gmail.com>
Subject: Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard
From: Barry Leiba <barryleiba@computer.org>
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, 02 Mar 2012 14:26:49 -0000

On Fri, Mar 2, 2012 at 6:47 AM, Hector <sant9442@gmail.com> wrote:
> If I understand where you going with this, IMV, I don't think it is a good
> thing SMTP systems should be expected will be processing the payload or its
> headers before the EOD is issued.

This document doesn't specify anything that needs header processing
*during* the SMTP transaction.[1]  The specified manipulation would
happen after the MTA had accepted the message, and before it relayed
it to the next hop, so I don't think there's any timeout-sensitive
issue here.

[1] It's possible that if an MTA should receive a high-priority
message that came through a non-supporting MTA immediately prior, AND
it wanted to reject the message based on the priority ("message too
big for the specified priority," or some such), then it would have to
find and parse the MT-Priority header field before giving the OK after
DATA.  That seems minimal, but perhaps it could be a problem.


Unrelated to Hector's note:
Does anyone's answer change if I point out that we already have at
least two protocols that have an MTA alter message header fields in
between message receipt and message relay?

An MTA that supports DKIM [RFC6376] might, under some conditions,
remove an existing signature and add its own.

An MTA that implements the Authentication-Results header field
[RFC5451] might remove an existing header and add its own.

Arguments can be made that the former is more of a gateway function
than a relay function (and Ned has already pointed out that we're
pretty sanguine about this sort of manipulation in gateways), and that
the latter is behaving more or less as a trace field, which we also
allow some flexibility with.  Also, those specifications aren't
directly part of an SMTP extension, so they're things that are
performed by a server that supports SMTP *and also* something else.
Whereas this manipulation is built directly into the SMTP extension,
as part of the protocol.

No opinions given here as a participant -- I'm trying to tease out the
issues for this document.

Barry, still shepherding

From scott@kitterman.com  Fri Mar  2 07:23:00 2012
Return-Path: <scott@kitterman.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0FE7121F8652 for <ietf@ietfa.amsl.com>; Fri,  2 Mar 2012 07:23:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.581
X-Spam-Level: 
X-Spam-Status: No, score=-2.581 tagged_above=-999 required=5 tests=[AWL=0.018,  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 GvcLvK5I-WKH for <ietf@ietfa.amsl.com>; Fri,  2 Mar 2012 07:22:59 -0800 (PST)
Received: from mailout02.controlledmail.com (mailout02.controlledmail.com [72.81.252.18]) by ietfa.amsl.com (Postfix) with ESMTP id 0A66921F8636 for <ietf@ietf.org>; Fri,  2 Mar 2012 07:22:59 -0800 (PST)
Received: from mailout02.controlledmail.com (localhost [127.0.0.1]) by mailout02.controlledmail.com (Postfix) with ESMTP id 06B8D20E40DA; Fri,  2 Mar 2012 10:22:58 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=2007-00; t=1330701778; bh=cPFYIn9UbQ0tiTx/A1gfz1G4IFRIDtHD0Cz5jMQ2vfA=; h=From:To:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version:Content-Transfer-Encoding:Content-Type; b=KtL/pPazVuBd2xdc9beXK+x+RLnxf6tyirUin4QszU7W0ZUQPZUTH8yiM5BC1vdkm DMftl1ahYSkMDr5CWSnKRqbrWhrgdemaAD0bKIc6nsTM6j9FeVgUgVlKkBU4eonkzc H7c2c4vC4FDVzYjRzGMxpi1iq369TFaZTK9hsKMI=
Received: from scott-latitude-e6320.localnet (static-72-81-252-21.bltmmd.fios.verizon.net [72.81.252.21]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailout02.controlledmail.com (Postfix) with ESMTPSA id DB28020E408E;  Fri,  2 Mar 2012 10:22:57 -0500 (EST)
From: Scott Kitterman <scott@kitterman.com>
To: ietf@ietf.org
Subject: Re: Last Call: <draft-ietf-marf-spf-reporting-08.txt> (SPF Authentication Failure Reporting using the Abuse Report Format) to Proposed Standard
Date: Fri, 02 Mar 2012 10:22:57 -0500
Message-ID: <1349422.baAQMnczus@scott-latitude-e6320>
User-Agent: KMail/4.7.3 (Linux/3.0.0-16-generic-pae; KDE/4.7.4; i686; ; )
In-Reply-To: <CAC4RtVCSNcdiwcYR5fMcPvMSxCAVFNrWg+7-AOyM4G22u7vu9Q@mail.gmail.com>
References: <20120301004643.17274.83943.idtracker@ietfa.amsl.com> <1637246.LVMrVQYPHS@scott-latitude-e6320> <CAC4RtVCSNcdiwcYR5fMcPvMSxCAVFNrWg+7-AOyM4G22u7vu9Q@mail.gmail.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
X-AV-Checked: ClamAV using ClamSMTP
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Mar 2012 15:23:00 -0000

On Thursday, March 01, 2012 04:47:43 PM Barry Leiba wrote:
> >> >>   "Security issues with respect to these reports are similar to
> >> >> those
> >> >>    found in [DSN]."
> >> >> 
> >> >> The reference to DSN could be normative.
> >> > 
> >> > Security Considerations are never normative, so I'm not sure I
> >> > agree
> >> > that this should be.
> >> 
> >> It should.  Just because the Security Considerations section doesn't
> >> usually use normative language doesn't mean that it's not normative.
> >> People reading the document and implementing the protocol certainly
> >> have to read and understand the Security Considerations section, along
> >> with any transitive sections in other documents.
> > 
> > The reason I didn't make it normative when I drafted that section is
> > because this isn't a DSN, it's an ARF, thus the similar to.  If people
> > think it should be normative, I think it's fine to change it.
> 
> Yes, but think about the difference between these two statements:
> 
> 1. Security issues with respect to these reports are similar to those
> found in [DSN].
> 
> 2. Security issues with respect to these reports are similar to those
> found in [DSN].  Specifically, X and Y.  Also Z, when that situation
> is applicable.
> 
> In the second case, you can understand the security issues here
> without going and reading [DSN].  It really is just saying that these
> are similar to those, so the reference is informative.  In the first
> case, how can you know *anything* about the security issues without
> reading the referenced document?
> 
> If sections 6.1 and 6.2 really do say everything that needs to be
> said, and the sentence in 6. could be removed without loss of
> important information, then leave it as an informative reference.  If
> one really has to go to [DSN] to see what some of the issues are, make
> it normative.  That's the test.

Makes sense.  Thanks for the clarification.

Today I reviewed RFC 3464 again.  It has the following security 
considerations:

4.1 Forgery
4.2 Confidentiality
4.3 Non-Repudiation

Of these, I think that only forgery is relevant to this draft.  The non-
repudiation issue is not applicable to authentication failure reporting.  The 
confidentiality issue should be addressed in the document that discusses 
creation and formatting of these reports.

draft-ietf-marf-authfailure-report-10 (which is already a normative reference 
and listed for included security considerations) covers forgeries in great 
detail, so to the extent the advice in 6.2 of this draft doesn't address it, I 
think it's addressed there.

Based on that, I think that the sentence in paragraph 6 could be lost without 
losing anything important, so I think it should stay as it is.

This discussion also caused me to re-read draft-ietf-marf-authfailure-
report-10 again since that's where report generations is described.  It is (I 
believe) silent on confidentiality, except to say:

6.  Security Considerations

   Security issues with respect to these reports are similar to those
   found in [DSN].

(the exact same text that caused comment in this draft)

It might be worth someone looking at draft-ietf-marf-authfailure-report-10 
again to see if that's really appropriate.

Scott K

From johnl@iecc.com  Fri Mar  2 09:00:27 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 EF44321F85D8 for <ietf@ietfa.amsl.com>; Fri,  2 Mar 2012 09:00:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.377
X-Spam-Level: 
X-Spam-Status: No, score=-102.377 tagged_above=-999 required=5 tests=[AWL=0.223, 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 uLz0Fxjz1mVy for <ietf@ietfa.amsl.com>; Fri,  2 Mar 2012 09:00:25 -0800 (PST)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id A821721F86AD for <ietf@ietf.org>; Fri,  2 Mar 2012 09:00:25 -0800 (PST)
Received: (qmail 55879 invoked from network); 2 Mar 2012 17:00:23 -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=da41.4f50fca7.k1203; bh=g0WDDwXSN+4MD0M/Wwsu5xflIPBqW0ly22a+idGaHVI=; b=CjMi62+/0VkyeJRbJd5gLbxB6uuv8CFcznspCoC6nvqxt2GhOvobKH7lgLQ75gKa+BMS8Twunyq1DWR71/lX1QHxmf3NEM5T+LJ1lD9QSJRraq3NJ1Iyn9sPABxz78b5BW33EndOwRnbExj34hS5GAH5FXO8F9F2mKkj/bZaChk=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Received: (ofmipd 127.0.0.1) with (DHE-RSA-AES256-SHA encrypted) SMTP; 2 Mar 2012 17:00:01 -0000
Date: 2 Mar 2012 12:00:22 -0500
Message-ID: <alpine.BSF.2.00.1203020941360.37874@joyce.lan>
From: "John R. Levine" <johnl@iecc.com>
To: "Doug Barton" <dougb@dougbarton.us>
Subject: Re: provisioning software, was DNS RRTYPEs, the difficulty with
In-Reply-To: <4F50939C.4020608@dougbarton.us>
References: <20120228015606.2227.qmail@joyce.lan> <4F4D53E2.5080803@dougbarton.us> <alpine.BSF.2.00.1202281745310.7969@joyce.lan> <4F50939C.4020608@dougbarton.us>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
Cleverness: None detected
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Mar 2012 17:00:27 -0000

>> By the way, what's your opinion of draft-levine-dnsextlang-02?
>
> It isn't clear to me what problem you're trying to solve. For resolving
> name servers 3597 should be enough. For authoritative name servers your
> idea is sort of interesting, but generally upgrading the software to
> pick up support for new RRtypes is a good idea, since you'll also pick
> up new security fixes, etc.

Oh, wow.  Now I see the problem: people here are totally unaware of what 
using DNS software is like if you're not a DNS weenie.

If you think that it's reasonable to require a new version of your DNS 
software every time there's a new RR, you've conceded total defeat.  On 
most servers I know, software upgrades are risky and infrequent.  It could 
easily take a year for a new version of BIND to percolate out of the lab, 
into the various distribution channels, and to be installed on people's 
servers, by which time everyone has built their applications with TXT 
records and it's too late.

Moreover, the servers aren't the hard part, it's the provisioning systems. 
You and I may edit our zone files with emacs, but civilians use web based 
things with pulldown menus and checkboxes.  If they can't enter an RR into 
one of them it doesn't matter whether the name server supports it or not. 
This latest round of teeth gnashing was provoked by discussions in the 
spfbis WG, where we're wondering whether to deprecate the type 99 SPF 
record.  Among the reasons it's unused in practice is that nobody's 
provisioning system lets you create SPF records.

The point of my draft is that it's an extension language that both name 
servers and provisioning systems can read on the fly.  Add a new stanza to 
/etc/rrtypes and you're done, no software upgrades needed.  The risk is 
much lower since the worst that will happen if the new stanza is broken is 
that the provisioning software and name servers will ignore it, not 
that the whole thing will crash.

Sure, there are some RRs with complex semantics that can't be done without 
new code (DNSSEC being the major example), but most RRs are syntactically 
and semantically trivial, just a bunch of fields that the server doesn't 
even interpret once it's parsed the master records or their equivalent.

Until the DNS crowd admits that provisioning systems are a major 
bottleneck, and telling people to hand-code more types into them isn't 
going to happen, there's no chance of getting more RRs deployed.

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

From scott@kitterman.com  Fri Mar  2 09:02:11 2012
Return-Path: <scott@kitterman.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CF49521F869E for <ietf@ietfa.amsl.com>; Fri,  2 Mar 2012 09:02:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.582
X-Spam-Level: 
X-Spam-Status: No, score=-2.582 tagged_above=-999 required=5 tests=[AWL=0.017,  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 ass8XoBJ5Ew9 for <ietf@ietfa.amsl.com>; Fri,  2 Mar 2012 09:02:10 -0800 (PST)
Received: from mailout02.controlledmail.com (mailout02.controlledmail.com [72.81.252.18]) by ietfa.amsl.com (Postfix) with ESMTP id C753F21F85DD for <ietf@ietf.org>; Fri,  2 Mar 2012 09:02:10 -0800 (PST)
Received: from mailout02.controlledmail.com (localhost [127.0.0.1]) by mailout02.controlledmail.com (Postfix) with ESMTP id 02D1F20E40DA; Fri,  2 Mar 2012 12:02:07 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=2007-00; t=1330707727; bh=DbOxTatA8DWjsh7dNsNbAH222NJ5RxHM0xVFZWCHZyM=; h=From:To:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version:Content-Transfer-Encoding:Content-Type; b=n+kBATmSVxj/B2NUlQKj+FUJVV0yS2TdpNoJ+VRc64TAWASnRI0GvZm7+nilM0/RR hQOqdb2bEYnvD3uqcR/dihmkcgNS4hizNT+dwrRz4XjaYZFKLMgom6Pm/6/LsLJg2P baUI75OhGcmA69yRFfF6BaDwv0VfO0EU1SAwhXuU=
Received: from scott-latitude-e6320.localnet (static-72-81-252-21.bltmmd.fios.verizon.net [72.81.252.21]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailout02.controlledmail.com (Postfix) with ESMTPSA id D9AA620E408E;  Fri,  2 Mar 2012 12:02:06 -0500 (EST)
From: Scott Kitterman <scott@kitterman.com>
To: ietf@ietf.org
Subject: Re: Last Call: <draft-ietf-marf-spf-reporting-08.txt> (SPF Authentication Failure Reporting using the Abuse Report Format) to	Proposed Standard
Date: Fri, 02 Mar 2012 12:02:06 -0500
Message-ID: <2261824.fY9co50BPG@scott-latitude-e6320>
User-Agent: KMail/4.7.3 (Linux/3.0.0-16-generic-pae; KDE/4.7.4; i686; ; )
In-Reply-To: <9452079D1A51524AA5749AD23E00392806F917@exch-mbx901.corp.cloudmark.com>
References: <20120301004643.17274.83943.idtracker@ietfa.amsl.com> <6.2.5.6.2.20120229181328.0a95a9f8@resistor.net> <9452079D1A51524AA5749AD23E00392806F917@exch-mbx901.corp.cloudmark.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
X-AV-Checked: ClamAV using ClamSMTP
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Mar 2012 17:02:11 -0000

On Thursday, March 01, 2012 07:14:20 PM Murray S. Kucherawy wrote:
> > In Section 3:
> > 
> >    "There exist cases in which a domain name owner employing [SPF] for
> >     announcing sending practices may want to know when messages are
> >     received via unauthorized routing."
> > 
> >
> > I suggest not using the term "domain name owner" to side-step the
> > question of domain "ownership".
> 
> Would "ADMD" and an informative reference to RFC5598 be more appropriate?

I think it wouldn't.  As I read 5598, ADMD is the provider of services.  If 
you look at the examples in 5598, paragraph 2.3, only one of those, Enterprise 
Service Providers, is also the owner of the domain (and the one that controls 
policy).  For many small domains they use the services of ISPs or ESPs (the 
other two examples), but in no way should ISPs or ESPs be determining what 
goes into a domain's SPF record for domains they don't own (this has been 
tried, BTW, and it was a disaster).

Domain owners is the term used in RFC 4408 (see paragraph 1, introduction).  
I'm not sure what question of domain ownership we're trying to side step, but 
the term seems to me to be both literally correct and the same terminology 
already in use in related documents (also, I might add) a term no one has 
suggested should be changed in SPFbis).

Scott K

From scott@kitterman.com  Fri Mar  2 09:19:12 2012
Return-Path: <scott@kitterman.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3038B21F86AB for <ietf@ietfa.amsl.com>; Fri,  2 Mar 2012 09:19:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.583
X-Spam-Level: 
X-Spam-Status: No, score=-2.583 tagged_above=-999 required=5 tests=[AWL=0.016,  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 2f8cfVjQDTYy for <ietf@ietfa.amsl.com>; Fri,  2 Mar 2012 09:19:11 -0800 (PST)
Received: from mailout02.controlledmail.com (mailout02.controlledmail.com [72.81.252.18]) by ietfa.amsl.com (Postfix) with ESMTP id 36EF221F868A for <ietf@ietf.org>; Fri,  2 Mar 2012 09:19:11 -0800 (PST)
Received: from mailout02.controlledmail.com (localhost [127.0.0.1]) by mailout02.controlledmail.com (Postfix) with ESMTP id C13DE20E40DA; Fri,  2 Mar 2012 12:19:10 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=2007-00; t=1330708750; bh=FVEytQ/TTV5uybrlp8MFylfJwXuYb6wF3fKcOcR0OEg=; h=From:To:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version:Content-Transfer-Encoding:Content-Type; b=F/suXTQgxe51wmD0XZFE/tYj+fJZLM3T26WTCSKp1F5LsPXrdEG33xM4f5Wd3n/BI WqI2MxGbFEtTXWO617aD+TTcNG+IpCbEp79qgnJKLnW9xbuRz361EYN2JsHrhkCPIL gPwpPtg0f0eblULe1yBvU5xFUENHOex+ewK/kpLg=
Received: from scott-latitude-e6320.localnet (static-72-81-252-21.bltmmd.fios.verizon.net [72.81.252.21]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailout02.controlledmail.com (Postfix) with ESMTPSA id 9031320E408E;  Fri,  2 Mar 2012 12:19:10 -0500 (EST)
From: Scott Kitterman <scott@kitterman.com>
To: ietf@ietf.org
Subject: Re: Last Call: <draft-ietf-marf-spf-reporting-08.txt> (SPF Authentication Failure Reporting using the Abuse Report Format) to	Proposed Standard
Date: Fri, 02 Mar 2012 12:19:09 -0500
Message-ID: <18744934.WPNuXzvee6@scott-latitude-e6320>
User-Agent: KMail/4.7.3 (Linux/3.0.0-16-generic-pae; KDE/4.7.4; i686; ; )
In-Reply-To: <9452079D1A51524AA5749AD23E00392806F917@exch-mbx901.corp.cloudmark.com>
References: <20120301004643.17274.83943.idtracker@ietfa.amsl.com> <6.2.5.6.2.20120229181328.0a95a9f8@resistor.net> <9452079D1A51524AA5749AD23E00392806F917@exch-mbx901.corp.cloudmark.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
X-AV-Checked: ClamAV using ClamSMTP
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Mar 2012 17:19:12 -0000

On Thursday, March 01, 2012 07:14:20 PM Murray S. Kucherawy wrote:
> > -----Original Message-----
> > From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
> > SM Sent: Wednesday, February 29, 2012 10:27 PM
> > To: ietf@ietf.org
> > Subject: Re: Last Call: <draft-ietf-marf-spf-reporting-08.txt> (SPF
> > Authentication Failure Reporting using the Abuse Report Format) to
> > Proposed Standard
> 
> As for your non-procedural concerns:
> > I'll avoid commenting on the technical angle.  Here are some editorial
> > comments:
> > 
> > In Section 3:
> >    "There exist cases in which a domain name owner employing [SPF]
> >    for
> >    
> >     announcing sending practices may want to know when messages are
> >     received via unauthorized routing."
> > 
> > I suggest not using the term "domain name owner" to side-step the
> > question of domain "ownership".
> 
> Would "ADMD" and an informative reference to RFC5598 be more appropriate?

Replied seprately.  I think it should stay as it is.

> >    "particular because a message arrived via an unauthorized route.
> >    
> >     To generate a complete address to which the report is sent, the
> >     verifier simply appends to this value an "@" followed by the
> >     SPF domain per paragraph 4.1 of [SPF]."
> > 
> > RFC 4408 uses the term "SPF-compliant domain".
> 
> That's fine with us.

Done in my local copy

> > In Section 5.1:
> >    "New registrations or updates MUST be published in accordance with
> >    the
> >    
> >     "Specification Required" guidelines as described in
> >     [IANA-CONSIDERATIONS].  New registrations and updates MUST
> >     contain
> >     the following information:"
> > 
> > I suggest not using RFC 2119 key words in the IANA Considerations
> > section unless there are interoperability issues with IANA.
> 
> We'll change "MUST" to "are to be".

Done in my local copy

> >    "current:  The field is in current use
> >    
> >     deprecated:  The field is in current use but its use is
> >     
> >        discouraged"
> > 
> > The difference in "current use" can end up being problematic for the
> > designated expert.

Done in my local copy.

> A number of registries are using this wording already and there's been no
> objection to date.  Do you have a better suggestion?
> > In Section 6:
> >   "Security issues with respect to these reports are similar to those
> >   
> >    found in [DSN]."
> > 
> > The reference to DSN could be normative.

Replied separately.  I think it should stay the way it is.

> Security Considerations are never normative, so I'm not sure I agree that
> this should be.
> >    "The HELO/EHLO command SHOULD also be selected so that it
> >    
> >     will pass [SPF] HELO checks."
> > 
> > I could not understand what to do about the above recommendation.
> > FWIW, the command is specified in RFC 5321.  That specification is not
> > referenced by this draft.
> 
> Yes, that needs to be clarified, the reference added, and the typo in the
> section title needs correction.

I agree I should add the reference to 5321.  Is informative sufficient (I don't 
think any detailed understand of Mail From or EHLO/HELO is necessary to 
implement this spec).

I can see the construction is awkward, but I'm not sure how to make it better.  
I'd appreciate suggestions.

On Thursday, March 01, 2012 04:01:20 PM Barry Leiba wrote:
> >>    "current:  The field is in current use
> >> 
> >>     deprecated:  The field is in current use but its use is
> >>        discouraged"
> >> 
> >> The difference in "current use" can end up being problematic for the
> >> designated expert.
> > 
> > A number of registries are using this wording already and there's been
> > no
> > objection to date.  Do you have a better suggestion?
> 
> I suggest, "The field might still be in use, but its use is discouraged."

Done in my local copy.

Scott K

From julien.meuric@orange.com  Fri Mar  2 09:21:20 2012
Return-Path: <julien.meuric@orange.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DA1B421F8644 for <ietf@ietfa.amsl.com>; Fri,  2 Mar 2012 09:21:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.936
X-Spam-Level: 
X-Spam-Status: No, score=-5.936 tagged_above=-999 required=5 tests=[AWL=0.313,  BAYES_00=-2.599, HELO_EQ_FR=0.35, 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 vKcQr+oKEluh for <ietf@ietfa.amsl.com>; Fri,  2 Mar 2012 09:21:20 -0800 (PST)
Received: from p-mail2.rd.francetelecom.com (p-mail2.rd.francetelecom.com [195.101.245.16]) by ietfa.amsl.com (Postfix) with ESMTP id 8629721F8699 for <ietf@ietf.org>; Fri,  2 Mar 2012 09:21:19 -0800 (PST)
Received: from p-mail2.rd.francetelecom.com (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id BDD721074002 for <ietf@ietf.org>; Fri,  2 Mar 2012 18:22:21 +0100 (CET)
Received: from ftrdsmtp2.rd.francetelecom.fr (unknown [10.192.128.47]) by p-mail2.rd.francetelecom.com (Postfix) with ESMTP id B2861E302B6 for <ietf@ietf.org>; Fri,  2 Mar 2012 18:22:21 +0100 (CET)
Received: from ftrdmel10.rd.francetelecom.fr ([10.192.128.44]) by ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.4675);  Fri, 2 Mar 2012 18:21:18 +0100
Received: from [10.193.71.161] ([10.193.71.161]) by ftrdmel10.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.4675);  Fri, 2 Mar 2012 18:21:17 +0100
Message-ID: <4F51018D.2080105@orange.com>
Date: Fri, 02 Mar 2012 18:21:17 +0100
From: Julien Meuric <julien.meuric@orange.com>
Organization: France Telecom
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.27) Gecko/20120216 Lightning/1.0b2 Thunderbird/3.1.19
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: RE: Last Call:<draft-betts-itu-oam-ach-code-point-03.txt>	(Allocation of an Associated Channel Code Point for Use by ITU-T Ethernet based OAM) to Informational RFC
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-OriginalArrivalTime: 02 Mar 2012 17:21:17.0593 (UTC) FILETIME=[E0BA6090:01CCF898]
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Mar 2012 17:21:21 -0000

Hi.

It looks like the candidate process is clear: the IETF and the IANA are 
capable of holding a document and the associated allocation until 
normative references are published.

I would like to come back to the original topic: the aforementioned I-D 
and the last call in progress. I have a few issues to add to the list.
1/ The I-D asks for a code point named "Ethernet based OAM" (starting 
form the title itself). That phrase may suit to Y.1731, targeted at 
Ethernet networks, but the I-D is clearly scoped within the MPLS 
context; so is the title of G.8113.1. This lack of clarity for such a 
controversial topic tends to make me think that the I-D is not mature 
and that the associated speech requires more exactness at this stage.
2/ The I-D has an explicit reference to 
draft-sprecher-mpls-tp-oam-considerations: acknowledging, inside the 
document, the existence of opposition does not solve the corresponding 
issues.
3/ It looks like that the I-D falls into the scope of RFC 4775 and RFC 
4929. Both could be quoted largely. Do they still have precedence in the 
current context?

Regards,

Julien


Le -10/01/-28163 20:59, John C Klensin a écrit :
>  --On Thursday, March 01, 2012 19:38 +0100 "Sprecher, Nurit (NSN -
>  IL/Hod HaSharon)" <nurit.sprecher@nsn.com> wrote:
>
> > Draft-betts asks a code point for a document which is not mature
> > and not agreed yet. Usually we do not issue last call for a
> > document in such a condition!
>
>  Actually, we do that fairly regularly. Have a look at the RFC
>  Editor queue, see how many documents have a status that includes
>  "MISSREF", and you will get an idea of how many recent ones there
>  are. Of course, for that analogy to hold, draft-betts itself must
>  be complete and competent. But a forward normative reference is not
>  a problem: it just goes into the RFC Editor queue and, normally, IANA
>  doesn't start doing any assignments on the basis of such documents
>  until the problems/ references are resolved and the RFC Editor is
>  editing.
>
> > And in addition, draft-betts has many issues that must be resolved
> > first. For example it must be clear for what the code point is
> > requested. Draft-betts indicates that G.8113.1 is subjected to
> > revisions...they may add more messages to G.8113.1 that will be
> > hidden behind the code point, etc.
>
>  IMO, that should not be part of the IETF's problem. It is part of
>  the forward reference. As far as I can tell, Russ is not suggesting
>  actually allocating a code point until (and unless) G.8113.1 is
>  formally approved and hence complete and "hiding" nothing.
>
>  john
>


From sob@sobco.com  Thu Mar  1 15:15: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 B46B921E838D for <ietf@ietfa.amsl.com>; Thu,  1 Mar 2012 15:15:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.495
X-Spam-Level: 
X-Spam-Status: No, score=-0.495 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lN8d8-lQBLbj for <ietf@ietfa.amsl.com>; Thu,  1 Mar 2012 15:15:51 -0800 (PST)
Received: from sobco.sobco.com (unknown [136.248.127.164]) by ietfa.amsl.com (Postfix) with ESMTP id D772821E82D8 for <ietf@ietf.org>; Thu,  1 Mar 2012 15:15:50 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by sobco.sobco.com (Postfix) with ESMTP id 42DE826DDDE5 for <ietf@ietf.org>; Thu,  1 Mar 2012 18:15:49 -0500 (EST)
X-Virus-Scanned: amavisd-new at sobco.com
Received: from sobco.sobco.com ([127.0.0.1]) by localhost (sobco.sobco.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IbZGzIuPJ3Ou for <ietf@ietf.org>; Thu,  1 Mar 2012 18:15:47 -0500 (EST)
Received: from [10.0.1.3] (unknown [173.166.5.69]) by sobco.sobco.com (Postfix) with ESMTPSA id 8DA8726DDDD3 for <ietf@ietf.org>; Thu,  1 Mar 2012 18:15:47 -0500 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1257)
Subject: Re: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt>	(Allocation of an Associated Channel Code Point for Use by	ITU-T Ethernet based OAM) to Informational RFC
From: "Scott O. Bradner" <sob@sobco.com>
In-Reply-To: <C3E581FB44D46BF4128A2229@PST.JCK.COM>
Date: Thu, 1 Mar 2012 18:15:59 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <A101B91C-CBB3-42FF-9AD0-E531E002AE36@sobco.com>
References: <20120222151252.32262.82157.idtracker@ietfa.amsl.com> <03a301ccf174$ff953290$febf97b0$@olddog.co.uk> <515703B08A3A064C9CC8C09ACCC710DC0631679E@XMB-RCD-103.cisco.com> <C71DA9B1-A61F-4C5D-8DCE-3702271CBB6D@vigilsec.com> <4F4FA70B.2030906@pi.nu> <D0F60388-D852-4815-917A-B14BF40C64FB@vigilsec.com> <BD60EA38ED03AF5A21868DF1@PST.JCK.COM> <4F4FC252.9010001@cisco.com> <C3E581FB44D46BF4128A2229@PST.JCK.COM>
To: IETF-Discussion list discussion <ietf@ietf.org>
X-Mailer: Apple Mail (2.1257)
X-Mailman-Approved-At: Fri, 02 Mar 2012 09:37:30 -0800
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Mar 2012 23:15:51 -0000

what John said with one caveat - ITU-T consensus to modify an IETF =
protocol rather than
bringing requirements to the IETF should not escape the gatekeeper =
function

Scott

On Mar 1, 2012, at 6:04 PM, John C Klensin wrote:

>=20
>=20
> --On Thursday, March 01, 2012 18:39 +0000 Stewart Bryant
> <stbryant@cisco.com> wrote:
>=20
>> ...
>>> FWIW, this seems entirely appropriate to me.  If we do it this
>>> way, I think it is important to note --for the benefit of
>>> those more historically involved with the ITU and others--
>>> that we routinely block our own documents on normative
>>> references to work that is still in progress and, usually, do
>>> not do related code point allocations until the blocking
>>> referenced documents are ready.  Once the present I-D is
>>> judged to be sufficiently ready, this approach would
>>> therefore be IETF approval and a formal guarantee to the ITU
>>> that a code point will be allocated if an when G.8113.1 is
>>> approved and published, but not assignment of that code point
>>> until the referenced base document is finished.
>>>=20
>>> Completely normal procedurally.
>> ...
>> To be clear John our normal requirement would be that the
>> technical community achieved consensus that the base document
>> was ready. I have never seen ITU-T consensus on the contents
>> of G.8113.1 at any meeting that I have observed. What in your
>> view is the criteria for determining that  G.8113.1 has
>> achieved consensus?
>=20
> Stewart,=20
>=20
> I don't think so. =20
>=20
> Let me suggest that there are two entirely separate issues here
> and that talking about "technical community consensus" obscures
> both of them.
>=20
> (1) Whether, given the JWT and other agreements, the ITU has any
> business developing G.8113.x at all, or whether they should be
> simply submitting ideas to the IETF for consideration.  Many of
> us think that, under that agreement, the G.8113 activity is
> inappropriate.  But the ITU has obviously decided otherwise and
> we have no enforcement capability to prevent them from doing so
> (whether we should or should not is pretty much irrelevant at
> this point, at least IMO).  Whether the "technical community"
> has achieved consensus is not relevant either, the only thing
> that matters is whether G.8113.1 is, or will be, fully approved
> by the ITU under ITU procedures.
>=20
> (2) Whether it is reasonable or appropriate for the IETF to use
> our responsibility for code point assignments and consequent
> relationship with IANA to try to keep protocols that are not
> consistent with our design judgment and aesthetics --no matter
> how grounded in experience and good engineering-- off the
> Internet.  That is the "Internet gatekeeper" function about
> which, as you know, I've expressed concern in other contexts.  I
> think the answer has got to be "we can, should, and always will
> exercise quality control on stable specifications and normative
> references but, unless we can justify being sure of our own
> infallibility, we cannot and should not try to prevent another
> body from deploying a specification on the Internet by using our
> control of the registration model".   Telling people why we
> think their ideas are sub-optimal is fine, as is identifying any
> risks we see in appropriate and visible places, but telling
> another group what they can't do because the IETF doesn't like
> the idea isn't.
>=20
> And I think that distinction is entirely consistent with Russ's
> suggestion.
>=20
> best,
>   john
>=20
>=20
>=20
>=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From msk@cloudmark.com  Fri Mar  2 09:59:53 2012
Return-Path: <msk@cloudmark.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ECB4C21F854E for <ietf@ietfa.amsl.com>; Fri,  2 Mar 2012 09:59:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.604
X-Spam-Level: 
X-Spam-Status: No, score=-102.604 tagged_above=-999 required=5 tests=[AWL=-0.005, 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 Gb3GH0euQfU8 for <ietf@ietfa.amsl.com>; Fri,  2 Mar 2012 09:59:49 -0800 (PST)
Received: from ht1-outbound.cloudmark.com (ht1-outbound.cloudmark.com [72.5.239.25]) by ietfa.amsl.com (Postfix) with ESMTP id 7A08621F8584 for <ietf@ietf.org>; Fri,  2 Mar 2012 09:59:49 -0800 (PST)
Received: from EXCH-MBX901.corp.cloudmark.com ([fe80::addf:849a:f71c:4a82]) by EXCH-HTCAS901.corp.cloudmark.com ([fe80::2966:6846:8d89:4681%12]) with mapi id 14.01.0355.002; Fri, 2 Mar 2012 09:59:46 -0800
From: "Murray S. Kucherawy" <msk@cloudmark.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to	Proposed Standard
Thread-Topic: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to	Proposed Standard
Thread-Index: AQHM+ICHWiFRfLLC70OQhgZhp6mVzpZXSk+w
Date: Fri, 2 Mar 2012 17:59:45 +0000
Message-ID: <9452079D1A51524AA5749AD23E003928072F34@exch-mbx901.corp.cloudmark.com>
References: <20120301004219.15266.76505.idtracker@ietfa.amsl.com> <6.2.5.6.2.20120301120015.0940b2c0@resistor.net> <9452079D1A51524AA5749AD23E00392806FE0C@exch-mbx901.corp.cloudmark.com> <CAC4RtVCm_=VkfHiP_93_AKbo-X3NZc=NEt2pX_cEg6LYHtHSEQ@mail.gmail.com> <4F50B339.2030003@gmail.com> <CAC4RtVA_fBAVgsDbDDXEGBCfBqUke-8dA41h_NmjHAraay+0Tw@mail.gmail.com>
In-Reply-To: <CAC4RtVA_fBAVgsDbDDXEGBCfBqUke-8dA41h_NmjHAraay+0Tw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.20.2.121]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Mar 2012 17:59:54 -0000

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of B=
arry Leiba
> Sent: Friday, March 02, 2012 6:27 AM
> To: ietf@ietf.org
> Subject: Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple
> Mail Transfer Protocol extension for Message Transfer Priorities) to
> Proposed Standard
>=20
> Does anyone's answer change if I point out that we already have at
> least two protocols that have an MTA alter message header fields in
> between message receipt and message relay?
>=20
> An MTA that supports DKIM [RFC6376] might, under some conditions,
> remove an existing signature and add its own.

That's a good example.

> An MTA that implements the Authentication-Results header field
> [RFC5451] might remove an existing header and add its own.

Unfortunately I don't think this one is, because the header changes it enco=
urages take place strictly within an ADMD (specifically, the receiving one)=
, not as a mechanism for tunneling transport metadata through non-participa=
ting environments.

> Arguments can be made that the former is more of a gateway function
> than a relay function (and Ned has already pointed out that we're
> pretty sanguine about this sort of manipulation in gateways), and that
> the latter is behaving more or less as a trace field, which we also
> allow some flexibility with.

RFC6376 also asks for trace header field treatment for DKIM-Signature.

That said, this does show that we've dabbled in this area of mushy boundari=
es, and the results haven't exactly been disastrous.

-MSK

From dougb@dougbarton.us  Fri Mar  2 10:09:56 2012
Return-Path: <dougb@dougbarton.us>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8D35021F85E0 for <ietf@ietfa.amsl.com>; Fri,  2 Mar 2012 10:09:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.663
X-Spam-Level: 
X-Spam-Status: No, score=-3.663 tagged_above=-999 required=5 tests=[AWL=-0.064, 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 fEPDMTGolj7p for <ietf@ietfa.amsl.com>; Fri,  2 Mar 2012 10:09:55 -0800 (PST)
Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by ietfa.amsl.com (Postfix) with ESMTP id 5FFFE21F85D4 for <ietf@ietf.org>; Fri,  2 Mar 2012 10:09:55 -0800 (PST)
Received: (qmail 6564 invoked by uid 399); 2 Mar 2012 18:09:49 -0000
Received: from unknown (HELO opti.dougb.net) (dougb@dougbarton.us@12.207.105.210) by mail2.fluidhosting.com with ESMTPAM; 2 Mar 2012 18:09:49 -0000
X-Originating-IP: 12.207.105.210
X-Sender: dougb@dougbarton.us
Message-ID: <4F510CEB.4040208@dougbarton.us>
Date: Fri, 02 Mar 2012 10:09:47 -0800
From: Doug Barton <dougb@dougbarton.us>
Organization: http://SupersetSolutions.com/
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:10.0.2) Gecko/20120224 Thunderbird/10.0.2
MIME-Version: 1.0
To: "John R. Levine" <johnl@iecc.com>
Subject: Re: provisioning software, was DNS RRTYPEs, the difficulty with
References: <20120228015606.2227.qmail@joyce.lan> <4F4D53E2.5080803@dougbarton.us> <alpine.BSF.2.00.1202281745310.7969@joyce.lan> <4F50939C.4020608@dougbarton.us> <alpine.BSF.2.00.1203020941360.37874@joyce.lan>
In-Reply-To: <alpine.BSF.2.00.1203020941360.37874@joyce.lan>
X-Enigmail-Version: 1.3.5
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Mar 2012 18:09:56 -0000

On 03/02/2012 09:00, John R. Levine wrote:
>>> By the way, what's your opinion of draft-levine-dnsextlang-02?
>>
>> It isn't clear to me what problem you're trying to solve. For resolving
>> name servers 3597 should be enough. For authoritative name servers your
>> idea is sort of interesting, but generally upgrading the software to
>> pick up support for new RRtypes is a good idea, since you'll also pick
>> up new security fixes, etc.
> 
> Oh, wow.  Now I see the problem: people here are totally unaware of what
> using DNS software is like if you're not a DNS weenie.

Assuming you're the only one with the True WisdomTM is almost always a
bad idea. I stated earlier in the thread that I've done the kinds of
provisioning systems you describe. And I'm not going to throw my resume
at you, but I'm also intimately familiar with DNS at the large
enterprise level.

> If you think that it's reasonable to require a new version of your DNS
> software every time there's a new RR, you've conceded total defeat.  On
> most servers I know, software upgrades are risky and infrequent.  It
> could easily take a year for a new version of BIND to percolate out of
> the lab, into the various distribution channels, and to be installed on
> people's servers, by which time everyone has built their applications
> with TXT records and it's too late.

I understand what you're saying, and I've seen this kind of
institutional lethargy in action. My point is that just because this is
a very common situation doesn't make it correct, or even defensible.

We have a longstanding culture of DNS being a set-and-forget service. Us
"DNS weenies" have been the worst offenders in enabling this bad
behavior by trying to be backwards-backwards-backwards compatible with
every new change. Those days are over. And just because properly
updating your software can be difficult doesn't make it the wrong answer.

> Moreover, the servers aren't the hard part, it's the provisioning
> systems. You and I may edit our zone files with emacs, but civilians use
> web based things with pulldown menus and checkboxes.  If they can't
> enter an RR into one of them it doesn't matter whether the name server
> supports it or not.

Yes, I get that bit too.

> The point of my draft is that it's an extension language that both name
> servers and provisioning systems can read on the fly.  Add a new stanza
> to /etc/rrtypes and you're done, no software upgrades needed.  The risk
> is much lower since the worst that will happen if the new stanza is
> broken is that the provisioning software and name servers will ignore
> it, not that the whole thing will crash.

So it seems to me that what you're proposing would also cause the need
for changes to be made to the provisioning systems. Or are you
suggesting that the same users who cannot handle anything other than
point and click are suddenly going to be able to enter specially
formatted text strings that they don't understand? And/or that the
people who operate those provisioning systems are going to allow end
users to "Add a new stanza to /etc/rrtypes"?

> Until the DNS crowd admits that provisioning systems are a major
> bottleneck, and telling people to hand-code more types into them isn't
> going to happen, there's no chance of getting more RRs deployed.

The rest of this discussion is almost certainly more suitable for dnsop,
but I'll say one more time that I disagree with you on this point.
Provisioning systems *are* a bottleneck, no one is disputing that. But
our experience with new TLDs, IPv6 and DNSSEC shows that when there is
user demand for these changes, they get made.

I'll also add one more point based on my experience with DNS
provisioning system UI design, most of what you are trying to accomplish
with your draft on the UI side can be handled with a simple text field
in an HTML form that allows the user to enter free-form stuff that is
then checked for syntax errors and loaded if the name server software
supports the record. I realize that we disagree on right solution for
the name server support side of the equation, but my point is that most
of what you claim to be trying to achieve is already easily accomplished.


Doug (emacs!?! vi or die, baby)

-- 
    If you're never wrong, you're not trying hard enough

From msk@cloudmark.com  Fri Mar  2 10:16:48 2012
Return-Path: <msk@cloudmark.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C235A21F869F for <ietf@ietfa.amsl.com>; Fri,  2 Mar 2012 10:16:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.604
X-Spam-Level: 
X-Spam-Status: No, score=-102.604 tagged_above=-999 required=5 tests=[AWL=-0.005, 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 Iq-IBPxrHT+1 for <ietf@ietfa.amsl.com>; Fri,  2 Mar 2012 10:16:48 -0800 (PST)
Received: from ht2-outbound.cloudmark.com (ht2-outbound.cloudmark.com [72.5.239.26]) by ietfa.amsl.com (Postfix) with ESMTP id 0793221F8693 for <ietf@ietf.org>; Fri,  2 Mar 2012 10:16:48 -0800 (PST)
Received: from EXCH-MBX901.corp.cloudmark.com ([fe80::addf:849a:f71c:4a82]) by exch-htcas902.corp.cloudmark.com ([fe80::e82a:4f80:7f44:eaf7%12]) with mapi id 14.01.0355.002; Fri, 2 Mar 2012 10:16:47 -0800
From: "Murray S. Kucherawy" <msk@cloudmark.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: Last Call: <draft-ietf-marf-spf-reporting-08.txt> (SPF Authentication Failure Reporting using the Abuse Report Format)	to	Proposed Standard
Thread-Topic: Last Call: <draft-ietf-marf-spf-reporting-08.txt> (SPF Authentication Failure Reporting using the Abuse Report Format)	to	Proposed Standard
Thread-Index: AQHM+JZB+ZaJUDtfWUuQSqFrXGTIT5ZXTfHQ
Date: Fri, 2 Mar 2012 18:16:47 +0000
Message-ID: <9452079D1A51524AA5749AD23E00392807301F@exch-mbx901.corp.cloudmark.com>
References: <20120301004643.17274.83943.idtracker@ietfa.amsl.com> <6.2.5.6.2.20120229181328.0a95a9f8@resistor.net> <9452079D1A51524AA5749AD23E00392806F917@exch-mbx901.corp.cloudmark.com> <2261824.fY9co50BPG@scott-latitude-e6320>
In-Reply-To: <2261824.fY9co50BPG@scott-latitude-e6320>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.20.2.121]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Mar 2012 18:16:48 -0000

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of S=
cott Kitterman
> Sent: Friday, March 02, 2012 9:02 AM
> To: ietf@ietf.org
> Subject: Re: Last Call: <draft-ietf-marf-spf-reporting-08.txt> (SPF
> Authentication Failure Reporting using the Abuse Report Format) to
> Proposed Standard
>=20
> On Thursday, March 01, 2012 07:14:20 PM Murray S. Kucherawy wrote:
> > > In Section 3:
> > >
> > >    "There exist cases in which a domain name owner employing [SPF] fo=
r
> > >     announcing sending practices may want to know when messages are
> > >     received via unauthorized routing."
> > >
> > > I suggest not using the term "domain name owner" to side-step the
> > > question of domain "ownership".
> >
> > Would "ADMD" and an informative reference to RFC5598 be more
> > appropriate?
>=20
> I think it wouldn't.  As I read 5598, ADMD is the provider of services.

It's an MTA operator (RFC5598, 2.2.1), but basically the term is used to in=
dicate a separate organization that might own one or more domains.  Google,=
 for example, owns gmail.com and google.com (and googlers.com now), but tha=
t's all one ADMD.  This is how the term is used in several other documents.=
  It's obvious that this is the ADMD that will be the one setting SPF (or a=
ny) policy for mail use with respect to those domains, regardless of who ac=
tually handles the mail.

> Domain owners is the term used in RFC 4408 (see paragraph 1, introduction=
).
> I'm not sure what question of domain ownership we're trying to side
> step, but the term seems to me to be both literally correct and the
> same terminology already in use in related documents (also, I might
> add) a term no one has suggested should be changed in SPFbis).

I don't feel strongly about changing to ADMD except inasmuch as I suspect i=
t might resolve the comment and is a more commonly used term.  I'm actually=
 fine with "domain owner" because that's also an implicit property of the A=
DMD.

-MSK

From msk@cloudmark.com  Fri Mar  2 10:28:35 2012
Return-Path: <msk@cloudmark.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 531A921E802D for <ietf@ietfa.amsl.com>; Fri,  2 Mar 2012 10:28:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.604
X-Spam-Level: 
X-Spam-Status: No, score=-102.604 tagged_above=-999 required=5 tests=[AWL=-0.005, 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 lDsIP7VdPY-z for <ietf@ietfa.amsl.com>; Fri,  2 Mar 2012 10:28:34 -0800 (PST)
Received: from ht2-outbound.cloudmark.com (ht2-outbound.cloudmark.com [72.5.239.26]) by ietfa.amsl.com (Postfix) with ESMTP id D0E5321E8019 for <ietf@ietf.org>; Fri,  2 Mar 2012 10:28:34 -0800 (PST)
Received: from EXCH-MBX901.corp.cloudmark.com ([fe80::addf:849a:f71c:4a82]) by exch-htcas902.corp.cloudmark.com ([fe80::e82a:4f80:7f44:eaf7%12]) with mapi id 14.01.0355.002; Fri, 2 Mar 2012 10:28:34 -0800
From: "Murray S. Kucherawy" <msk@cloudmark.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: Last Call: <draft-ietf-marf-spf-reporting-08.txt> (SPF Authentication Failure Reporting using the Abuse Report Format)	to	Proposed Standard
Thread-Topic: Last Call: <draft-ietf-marf-spf-reporting-08.txt> (SPF Authentication Failure Reporting using the Abuse Report Format)	to	Proposed Standard
Thread-Index: AQHM+Jib3Bzch9sZ9kukAY/PhG+WsZZXUCsQ
Date: Fri, 2 Mar 2012 18:28:32 +0000
Message-ID: <9452079D1A51524AA5749AD23E003928073049@exch-mbx901.corp.cloudmark.com>
References: <20120301004643.17274.83943.idtracker@ietfa.amsl.com> <6.2.5.6.2.20120229181328.0a95a9f8@resistor.net> <9452079D1A51524AA5749AD23E00392806F917@exch-mbx901.corp.cloudmark.com> <18744934.WPNuXzvee6@scott-latitude-e6320>
In-Reply-To: <18744934.WPNuXzvee6@scott-latitude-e6320>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.20.2.121]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Mar 2012 18:28:35 -0000

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of S=
cott Kitterman
> Sent: Friday, March 02, 2012 9:19 AM
> To: ietf@ietf.org
> Subject: Re: Last Call: <draft-ietf-marf-spf-reporting-08.txt> (SPF
> Authentication Failure Reporting using the Abuse Report Format) to
> Proposed Standard
>=20
> > >    "The HELO/EHLO command SHOULD also be selected so that it
> > >     will pass [SPF] HELO checks."
> > >
> > > I could not understand what to do about the above recommendation.
> > > FWIW, the command is specified in RFC 5321.  That specification is
> > > not referenced by this draft.
> >
> > Yes, that needs to be clarified, the reference added, and the typo in
> > the section title needs correction.
>=20
> I agree I should add the reference to 5321.  Is informative sufficient
> (I don't think any detailed understand of Mail From or EHLO/HELO is
> necessary to implement this spec).
>=20
> I can see the construction is awkward, but I'm not sure how to make it be=
tter.
> I'd appreciate suggestions.

I suggest:

OLD:
   In addition to the advice in security considerations of
   [I-D.IETF-MARF-AS] the additional consderations apply to [SPF] auth
   failure reports.  If the MAIL FROM command is not the NULL return
   address, i.e., "MAIL FROM:<>", then the selected MAIL FROM address
   MUST pass [SPF] MAIL FROM checks on receipt.  The HELO/EHLO command
   SHOULD also be selected so that it will pass [SPF] HELO checks.

NEW:
	In addition to the advice in the Security Considerations section of
	[I-D.IETF-MARF-AS], these additional considerations apply to
	generation of [SPF] authentication failure reports:

	o If the return address to be used will not be the NULL return
	  address, i.e., "MAIL FROM:<>", then the selected return address
	  MUST be selected such that it will pass [SPF] MAIL FROM checks
	  upon initial receipt.

	o If the report is passed to the Mail Submission Agent (MSA)
	  using [SMTP], the HELO/EHLO command parameter SHOULD also be
	  selected so that it will pass [SPF] HELO checks.

If needed, MSA is defined in RFC5598, so maybe this is another argument for=
 adding it as an informative reference and changing to use ADMD as discusse=
d in the other thread.

-MSK

From paul.hoffman@vpnc.org  Fri Mar  2 10:34:11 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 CD13821E8037 for <ietf@ietfa.amsl.com>; Fri,  2 Mar 2012 10:34:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.705
X-Spam-Level: 
X-Spam-Status: No, score=-102.705 tagged_above=-999 required=5 tests=[AWL=-0.106, 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 GlkrJ-BS7Yhr for <ietf@ietfa.amsl.com>; Fri,  2 Mar 2012 10:34:11 -0800 (PST)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id 217EF21E8034 for <ietf@ietf.org>; Fri,  2 Mar 2012 10:34:11 -0800 (PST)
Received: from [10.20.30.100] (50-0-66-4.dsl.dynamic.fusionbroadband.com [50.0.66.4]) (authenticated bits=0) by hoffman.proper.com (8.14.5/8.14.3) with ESMTP id q22IY21q086097 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 2 Mar 2012 11:34:03 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Subject: Re: provisioning software, was DNS RRTYPEs, the difficulty with
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=us-ascii
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <4F510CEB.4040208@dougbarton.us>
Date: Fri, 2 Mar 2012 10:34:02 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <C85B37B7-49DA-4E99-BA71-C99CCB08C016@vpnc.org>
References: <20120228015606.2227.qmail@joyce.lan> <4F4D53E2.5080803@dougbarton.us> <alpine.BSF.2.00.1202281745310.7969@joyce.lan> <4F50939C.4020608@dougbarton.us> <alpine.BSF.2.00.1203020941360.37874@joyce.lan> <4F510CEB.4040208@dougbarton.us>
To: Doug Barton <dougb@dougbarton.us>
X-Mailer: Apple Mail (2.1257)
Cc: "John R. Levine" <johnl@iecc.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Mar 2012 18:34:11 -0000

On Mar 2, 2012, at 10:09 AM, Doug Barton wrote:

>> The point of my draft is that it's an extension language that both =
name
>> servers and provisioning systems can read on the fly.  Add a new =
stanza
>> to /etc/rrtypes and you're done, no software upgrades needed.  The =
risk
>> is much lower since the worst that will happen if the new stanza is
>> broken is that the provisioning software and name servers will ignore
>> it, not that the whole thing will crash.
>=20
> So it seems to me that what you're proposing would also cause the need
> for changes to be made to the provisioning systems. Or are you
> suggesting that the same users who cannot handle anything other than
> point and click are suddenly going to be able to enter specially
> formatted text strings that they don't understand?

Yes, that's exactly the point. If they can copy-and-paste from a tool =
that created the text string, this will be of huge benefit.

> And/or that the
> people who operate those provisioning systems are going to allow end
> users to "Add a new stanza to /etc/rrtypes"?

No, that's not what is proposed. What is proposed is that if the =
operator has added the stanza, the user can add the RRtypes.

>> Until the DNS crowd admits that provisioning systems are a major
>> bottleneck, and telling people to hand-code more types into them =
isn't
>> going to happen, there's no chance of getting more RRs deployed.
>=20
> The rest of this discussion is almost certainly more suitable for =
dnsop,
> but I'll say one more time that I disagree with you on this point.
> Provisioning systems *are* a bottleneck, no one is disputing that. But
> our experience with new TLDs, IPv6 and DNSSEC shows that when there is
> user demand for these changes, they get made.

The purpose of the proposal is to allow protocols with less press oomph =
than "new TLDs, IPv6 and DNSSEC" to be deployed. Maybe you don't want =
that, but many of us do.

> I'll also add one more point based on my experience with DNS
> provisioning system UI design, most of what you are trying to =
accomplish
> with your draft on the UI side can be handled with a simple text field
> in an HTML form that allows the user to enter free-form stuff that is
> then checked for syntax errors and loaded if the name server software
> supports the record. I realize that we disagree on right solution for
> the name server support side of the equation, but my point is that =
most
> of what you claim to be trying to achieve is already easily =
accomplished.


Here, I agree with you more than I agree with John, but history has =
shown that HTML forms are not sufficient. I'm not sure why.

--Paul Hoffman


From msk@cloudmark.com  Fri Mar  2 10:43:50 2012
Return-Path: <msk@cloudmark.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3150221E803C for <ietf@ietfa.amsl.com>; Fri,  2 Mar 2012 10:43:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.604
X-Spam-Level: 
X-Spam-Status: No, score=-102.604 tagged_above=-999 required=5 tests=[AWL=-0.005, 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 85OKsh635U2S for <ietf@ietfa.amsl.com>; Fri,  2 Mar 2012 10:43:49 -0800 (PST)
Received: from ht1-outbound.cloudmark.com (ht1-outbound.cloudmark.com [72.5.239.25]) by ietfa.amsl.com (Postfix) with ESMTP id 4197721E8049 for <ietf@ietf.org>; Fri,  2 Mar 2012 10:43:33 -0800 (PST)
Received: from EXCH-MBX901.corp.cloudmark.com ([fe80::addf:849a:f71c:4a82]) by EXCH-HTCAS901.corp.cloudmark.com ([fe80::2966:6846:8d89:4681%12]) with mapi id 14.01.0355.002; Fri, 2 Mar 2012 10:43:33 -0800
From: "Murray S. Kucherawy" <msk@cloudmark.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: Last Call: <draft-ietf-marf-spf-reporting-08.txt> (SPF Authentication Failure Reporting using the Abuse Report Format)	to Proposed Standard
Thread-Topic: Last Call: <draft-ietf-marf-spf-reporting-08.txt> (SPF Authentication Failure Reporting using the Abuse Report Format)	to Proposed Standard
Thread-Index: AQHM+IhjGfsh27xNzEaq9uOELx7h+ZZXVOtg
Date: Fri, 2 Mar 2012 18:43:32 +0000
Message-ID: <9452079D1A51524AA5749AD23E00392807309D@exch-mbx901.corp.cloudmark.com>
References: <20120301004643.17274.83943.idtracker@ietfa.amsl.com> <1637246.LVMrVQYPHS@scott-latitude-e6320> <CAC4RtVCSNcdiwcYR5fMcPvMSxCAVFNrWg+7-AOyM4G22u7vu9Q@mail.gmail.com> <1349422.baAQMnczus@scott-latitude-e6320>
In-Reply-To: <1349422.baAQMnczus@scott-latitude-e6320>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.20.2.121]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Mar 2012 18:43:50 -0000

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of S=
cott Kitterman
> Sent: Friday, March 02, 2012 7:23 AM
> To: ietf@ietf.org
> Subject: Re: Last Call: <draft-ietf-marf-spf-reporting-08.txt> (SPF
> Authentication Failure Reporting using the Abuse Report Format) to
> Proposed Standard
>=20
> Based on that, I think that the sentence in paragraph 6 could be lost
> without losing anything important, so I think it should stay as it is.

Yes, I suggest that the sentence that comprises Section 6 proper can be dro=
pped.  The text currently in 6.1 can be moved up to 6, and the current 6.1 =
thus removed.

> It might be worth someone looking at draft-ietf-marf-authfailure-report-1=
0
> again to see if that's really appropriate.

I'll take a second look.

-MSK, MARF co-chair

From dougb@dougbarton.us  Fri Mar  2 10:46:58 2012
Return-Path: <dougb@dougbarton.us>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0CCD021E803C for <ietf@ietfa.amsl.com>; Fri,  2 Mar 2012 10:46:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.661
X-Spam-Level: 
X-Spam-Status: No, score=-3.661 tagged_above=-999 required=5 tests=[AWL=-0.062, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id G1f9ojtDNNV5 for <ietf@ietfa.amsl.com>; Fri,  2 Mar 2012 10:46:57 -0800 (PST)
Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by ietfa.amsl.com (Postfix) with ESMTP id 3A5C421E8019 for <ietf@ietf.org>; Fri,  2 Mar 2012 10:46:57 -0800 (PST)
Received: (qmail 21352 invoked by uid 399); 2 Mar 2012 18:46:54 -0000
Received: from unknown (HELO opti.dougb.net) (dougb@dougbarton.us@12.207.105.210) by mail2.fluidhosting.com with ESMTPAM; 2 Mar 2012 18:46:54 -0000
X-Originating-IP: 12.207.105.210
X-Sender: dougb@dougbarton.us
Message-ID: <4F51159D.3010603@dougbarton.us>
Date: Fri, 02 Mar 2012 10:46:53 -0800
From: Doug Barton <dougb@dougbarton.us>
Organization: http://SupersetSolutions.com/
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:10.0.2) Gecko/20120224 Thunderbird/10.0.2
MIME-Version: 1.0
To: Paul Hoffman <paul.hoffman@vpnc.org>
Subject: Re: provisioning software, was DNS RRTYPEs, the difficulty with
References: <20120228015606.2227.qmail@joyce.lan> <4F4D53E2.5080803@dougbarton.us> <alpine.BSF.2.00.1202281745310.7969@joyce.lan> <4F50939C.4020608@dougbarton.us> <alpine.BSF.2.00.1203020941360.37874@joyce.lan> <4F510CEB.4040208@dougbarton.us> <C85B37B7-49DA-4E99-BA71-C99CCB08C016@vpnc.org>
In-Reply-To: <C85B37B7-49DA-4E99-BA71-C99CCB08C016@vpnc.org>
X-Enigmail-Version: 1.3.5
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "John R. Levine" <johnl@iecc.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Mar 2012 18:46:58 -0000

On 03/02/2012 10:34, Paul Hoffman wrote:
> On Mar 2, 2012, at 10:09 AM, Doug Barton wrote:
> 
>>> The point of my draft is that it's an extension language that
>>> both name servers and provisioning systems can read on the fly.
>>> Add a new stanza to /etc/rrtypes and you're done, no software
>>> upgrades needed.  The risk is much lower since the worst that
>>> will happen if the new stanza is broken is that the provisioning
>>> software and name servers will ignore it, not that the whole
>>> thing will crash.
>> 
>> So it seems to me that what you're proposing would also cause the
>> need for changes to be made to the provisioning systems. Or are
>> you suggesting that the same users who cannot handle anything other
>> than point and click are suddenly going to be able to enter
>> specially formatted text strings that they don't understand?
> 
> Yes, that's exactly the point. If they can copy-and-paste from a tool
> that created the text string, this will be of huge benefit.

So new tools still have to be created for new RRtypes, right? This
sounds like an "elephants all the way down" situation to me.

>> And/or that the people who operate those provisioning systems are
>> going to allow end users to "Add a new stanza to /etc/rrtypes"?
> 
> No, that's not what is proposed. What is proposed is that if the
> operator has added the stanza, the user can add the RRtypes.

So less difficult than a full-fledged change to the provisioning system,
but still requires operator intervention, and now you have operators
*and* users with chances to make fatal errors.

>>> Until the DNS crowd admits that provisioning systems are a major 
>>> bottleneck, and telling people to hand-code more types into them
>>> isn't going to happen, there's no chance of getting more RRs
>>> deployed.
>> 
>> The rest of this discussion is almost certainly more suitable for
>> dnsop, but I'll say one more time that I disagree with you on this
>> point. Provisioning systems *are* a bottleneck, no one is disputing
>> that. But our experience with new TLDs, IPv6 and DNSSEC shows that
>> when there is user demand for these changes, they get made.
> 
> The purpose of the proposal is to allow protocols with less press
> oomph than "new TLDs, IPv6 and DNSSEC" to be deployed. Maybe you
> don't want that, but many of us do.

Please don't use that kind of ad-hominem-adjacent line of argument with
me. I'm already on record numerous times, including in this thread,
saying that I believe the ability to deploy new RRtypes is crucial to
the ongoing health of the Internet.

>> I'll also add one more point based on my experience with DNS 
>> provisioning system UI design, most of what you are trying to
>> accomplish with your draft on the UI side can be handled with a
>> simple text field in an HTML form that allows the user to enter
>> free-form stuff that is then checked for syntax errors and loaded
>> if the name server software supports the record. I realize that we
>> disagree on right solution for the name server support side of the
>> equation, but my point is that most of what you claim to be trying
>> to achieve is already easily accomplished.
> 
> 
> Here, I agree with you more than I agree with John, but history has
> shown that HTML forms are not sufficient. I'm not sure why.

IME this has been because of the lack of a validation step in between
user entry and (attempted) deployment. My (simplified) work flow for
these kinds of systems has been:

User input
    |
Sanity checks based on internal policy
    |
named-checkzone (or equivalent)
    |
Deploy to name server
    |
Validate that the new zone loaded correctly

Skipping steps 2, 3, or 5 *will* cause tears, at some point.


Doug

-- 
    If you're never wrong, you're not trying hard enough

From johnl@iecc.com  Fri Mar  2 10:48:06 2012
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6BC8821E8049 for <ietf@ietfa.amsl.com>; Fri,  2 Mar 2012 10:48:06 -0800 (PST)
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.217, 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 kBHSEyL4J2nZ for <ietf@ietfa.amsl.com>; Fri,  2 Mar 2012 10:48:05 -0800 (PST)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 32F7B21E8019 for <ietf@ietf.org>; Fri,  2 Mar 2012 10:48:04 -0800 (PST)
Received: (qmail 88363 invoked from network); 2 Mar 2012 18:48:03 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:vbr-info:user-agent:cleverness; s=15929.4f5115e3.k1203; bh=+QBiQe3mEc1PpDgbW5y0+FSqg367ZFWtaUv8psrkFQA=; b=SD++eLUqVc2FLM35dJ94RqaSmG7fr6QhR6+ZVMeCuFM7bOmI3GAHXXbr5reHvEPewK6wDK5WPZDDflQnHLYL/yUqBa1zylKDiwfCfHX7EZFxSQ2e8iUoS4OC3ZN/TfRadDFveQ/NnIACggI73AqYJ0OqURugEAFxFWi9u7dlJZs=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Received: (ofmipd 127.0.0.1) with (DHE-RSA-AES256-SHA encrypted) SMTP; 2 Mar 2012 18:47:40 -0000
Date: 2 Mar 2012 13:48:01 -0500
Message-ID: <alpine.BSF.2.00.1203021337280.48208@joyce.lan>
From: "John R. Levine" <johnl@iecc.com>
To: "Paul Hoffman" <paul.hoffman@vpnc.org>
Subject: Re: provisioning software, was DNS RRTYPEs, the difficulty with
In-Reply-To: <C85B37B7-49DA-4E99-BA71-C99CCB08C016@vpnc.org>
References: <20120228015606.2227.qmail@joyce.lan> <4F4D53E2.5080803@dougbarton.us> <alpine.BSF.2.00.1202281745310.7969@joyce.lan> <4F50939C.4020608@dougbarton.us> <alpine.BSF.2.00.1203020941360.37874@joyce.lan> <4F510CEB.4040208@dougbarton.us> <C85B37B7-49DA-4E99-BA71-C99CCB08C016@vpnc.org>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
Cleverness: None detected
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Mar 2012 18:48:06 -0000

Skipping over all the parts I agree with, and noting that two decades of 
telling people to upgrade their DNS servers frequently hasn't worked, we 
get to ...

>> I'll also add one more point based on my experience with DNS
>> provisioning system UI design, most of what you are trying to accomplish
>> with your draft on the UI side can be handled with a simple text field
>> in an HTML form that allows the user to enter free-form stuff that is
>> then checked for syntax errors

Checked for syntax errors?  By what?

The whole point of the extension language is to describe the syntax of new 
RRs as data that provisioning software and nams servers can read at 
runtime, so you don't have to patch your software for every new RR.

It also can be translated into an HTML form for the RR that the user can 
fill in, the provisioning software can syntax check by field, so you don't 
have to build an entire BIND master file parser into your PHP web scripts.

And, of course, your DNS server uses the same data to parse new RRs 
without being patched.

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

From ned+ietf@mauve.mrochek.com  Fri Mar  2 10:49:26 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 16EFA21F8587 for <ietf@ietfa.amsl.com>; Fri,  2 Mar 2012 10:49:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 pUJRY2j45yUZ for <ietf@ietfa.amsl.com>; Fri,  2 Mar 2012 10:49:25 -0800 (PST)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id 6817421F85C2 for <ietf@ietf.org>; Fri,  2 Mar 2012 10:49:25 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OCMYMZVINK014V1G@mauve.mrochek.com> for ietf@ietf.org; Fri, 2 Mar 2012 10:49:23 -0800 (PST)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OCI1CWJADS00ZUIL@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Fri, 2 Mar 2012 10:49:19 -0800 (PST)
From: ned+ietf@mauve.mrochek.com
Message-id: <01OCMYMXVKGA00ZUIL@mauve.mrochek.com>
Date: Fri, 02 Mar 2012 10:48:13 -0800 (PST)
Subject: Re: provisioning software, was DNS RRTYPEs, the difficulty with
In-reply-to: "Your message dated Fri, 02 Mar 2012 12:00:22 -0500" <alpine.BSF.2.00.1203020941360.37874@joyce.lan>
MIME-version: 1.0
Content-type: TEXT/PLAIN; Format=flowed
References: <20120228015606.2227.qmail@joyce.lan> <4F4D53E2.5080803@dougbarton.us> <alpine.BSF.2.00.1202281745310.7969@joyce.lan> <4F50939C.4020608@dougbarton.us> <alpine.BSF.2.00.1203020941360.37874@joyce.lan>
To: "John R. Levine" <johnl@iecc.com>
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Mar 2012 18:49:26 -0000

I've rarely read a message on this list that I agreed with more.

+1000 to everything said below.

				Ned

> >> By the way, what's your opinion of draft-levine-dnsextlang-02?
> >
> > It isn't clear to me what problem you're trying to solve. For resolving
> > name servers 3597 should be enough. For authoritative name servers your
> > idea is sort of interesting, but generally upgrading the software to
> > pick up support for new RRtypes is a good idea, since you'll also pick
> > up new security fixes, etc.

> Oh, wow.  Now I see the problem: people here are totally unaware of what
> using DNS software is like if you're not a DNS weenie.

> If you think that it's reasonable to require a new version of your DNS
> software every time there's a new RR, you've conceded total defeat.  On
> most servers I know, software upgrades are risky and infrequent.  It could
> easily take a year for a new version of BIND to percolate out of the lab,
> into the various distribution channels, and to be installed on people's
> servers, by which time everyone has built their applications with TXT
> records and it's too late.

> Moreover, the servers aren't the hard part, it's the provisioning systems.
> You and I may edit our zone files with emacs, but civilians use web based
> things with pulldown menus and checkboxes.  If they can't enter an RR into
> one of them it doesn't matter whether the name server supports it or not.
> This latest round of teeth gnashing was provoked by discussions in the
> spfbis WG, where we're wondering whether to deprecate the type 99 SPF
> record.  Among the reasons it's unused in practice is that nobody's
> provisioning system lets you create SPF records.

> The point of my draft is that it's an extension language that both name
> servers and provisioning systems can read on the fly.  Add a new stanza to
> /etc/rrtypes and you're done, no software upgrades needed.  The risk is
> much lower since the worst that will happen if the new stanza is broken is
> that the provisioning software and name servers will ignore it, not
> that the whole thing will crash.

> Sure, there are some RRs with complex semantics that can't be done without
> new code (DNSSEC being the major example), but most RRs are syntactically
> and semantically trivial, just a bunch of fields that the server doesn't
> even interpret once it's parsed the master records or their equivalent.

> Until the DNS crowd admits that provisioning systems are a major
> bottleneck, and telling people to hand-code more types into them isn't
> going to happen, there's no chance of getting more RRs deployed.

> Regards,
> John Levine, johnl@iecc.com, Primary Perpetrator of "The Internet for Dummies",
> Please consider the environment before reading this e-mail. http://jl.ly
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf

From dougb@dougbarton.us  Fri Mar  2 11:09:14 2012
Return-Path: <dougb@dougbarton.us>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1D68721E8038 for <ietf@ietfa.amsl.com>; Fri,  2 Mar 2012 11:09:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.66
X-Spam-Level: 
X-Spam-Status: No, score=-3.66 tagged_above=-999 required=5 tests=[AWL=-0.061,  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 m0FynFns715o for <ietf@ietfa.amsl.com>; Fri,  2 Mar 2012 11:09:13 -0800 (PST)
Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by ietfa.amsl.com (Postfix) with ESMTP id 475D521E8019 for <ietf@ietf.org>; Fri,  2 Mar 2012 11:09:13 -0800 (PST)
Received: (qmail 16491 invoked by uid 399); 2 Mar 2012 19:09:08 -0000
Received: from unknown (HELO opti.dougb.net) (dougb@dougbarton.us@12.207.105.210) by mail2.fluidhosting.com with ESMTPAM; 2 Mar 2012 19:09:08 -0000
X-Originating-IP: 12.207.105.210
X-Sender: dougb@dougbarton.us
Message-ID: <4F511AD3.6020903@dougbarton.us>
Date: Fri, 02 Mar 2012 11:09:07 -0800
From: Doug Barton <dougb@dougbarton.us>
Organization: http://SupersetSolutions.com/
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:10.0.2) Gecko/20120224 Thunderbird/10.0.2
MIME-Version: 1.0
To: "John R. Levine" <johnl@iecc.com>
Subject: Re: provisioning software, was DNS RRTYPEs, the difficulty with
References: <20120228015606.2227.qmail@joyce.lan> <4F4D53E2.5080803@dougbarton.us> <alpine.BSF.2.00.1202281745310.7969@joyce.lan> <4F50939C.4020608@dougbarton.us> <alpine.BSF.2.00.1203020941360.37874@joyce.lan> <4F510CEB.4040208@dougbarton.us> <C85B37B7-49DA-4E99-BA71-C99CCB08C016@vpnc.org> <alpine.BSF.2.00.1203021337280.48208@joyce.lan>
In-Reply-To: <alpine.BSF.2.00.1203021337280.48208@joyce.lan>
X-Enigmail-Version: 1.3.5
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: Paul Hoffman <paul.hoffman@vpnc.org>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Mar 2012 19:09:14 -0000

On 03/02/2012 10:48, John R. Levine wrote:
> Skipping over all the parts I agree with, and noting that two decades of
> telling people to upgrade their DNS servers frequently hasn't worked, we
> get to ...
> 
>>> I'll also add one more point based on my experience with DNS
>>> provisioning system UI design, most of what you are trying to accomplish
>>> with your draft on the UI side can be handled with a simple text field
>>> in an HTML form that allows the user to enter free-form stuff that is
>>> then checked for syntax errors
> 
> Checked for syntax errors?  By what?

Didn't you answer your own question further down in your own post? :)

But seriously folks, I really do understand what you're saying, but my
experience as both a DNS protocol weenie and as a designer/builder of
provisioning systems designed for non-DNS-protocol-weenie end users
tells me that your proposed solution is not likely to work in the (IMO
overly optimistic) manner in which you describe, and even if it did it's
the wrong solution to the problem.

If you want to discuss it further, dnsop is probably where that
discussion should take place, I've already repeated myself enough times
here.


Doug

-- 
    If you're never wrong, you're not trying hard enough

From adrian@olddog.co.uk  Fri Mar  2 13:44:29 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 75AFB21F849C for <ietf@ietfa.amsl.com>; Fri,  2 Mar 2012 13:44:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.224
X-Spam-Level: 
X-Spam-Status: No, score=-2.224 tagged_above=-999 required=5 tests=[AWL=0.376,  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 e56KaxAyItvX for <ietf@ietfa.amsl.com>; Fri,  2 Mar 2012 13:44:29 -0800 (PST)
Received: from asmtp3.iomartmail.com (asmtp3.iomartmail.com [62.128.201.159]) by ietfa.amsl.com (Postfix) with ESMTP id B36E321F8498 for <ietf@ietf.org>; Fri,  2 Mar 2012 13:44:28 -0800 (PST)
Received: from asmtp3.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id q22LiQ20003789;  Fri, 2 Mar 2012 21:44:26 GMT
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id q22LiPxn003773 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 2 Mar 2012 21:44:26 GMT
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <ietf@ietf.org>
Subject: Updates to draft-farrresnickel-ipr-sanctions
Date: Fri, 2 Mar 2012 21:44:27 -0000
Message-ID: <048501ccf8bd$a51c3b60$ef54b220$@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: Acz4vYrUlGjihk/0R9usevGyDMXrRw==
Content-Language: en-gb
Cc: Pete Resnick <presnick@qualcomm.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Mar 2012 21:44:29 -0000

Hi,

Just a couple of very minor changes in this revision.

s/authored/invented/ wrt IPR

Added note about using datatracker to record movement of names on a document.

We would really welcome more opinions and discussion.

Thanks,
Adrian
per pro Pete

> -----Original Message-----
> From: i-d-announce-bounces@ietf.org [mailto:i-d-announce-bounces@ietf.org]
> On Behalf Of internet-drafts@ietf.org
> Sent: 02 March 2012 21:36
> To: i-d-announce@ietf.org
> Subject: I-D Action: draft-farrresnickel-ipr-sanctions-01.txt
> 
> A New Internet-Draft is available from the on-line Internet-Drafts
directories.
> 
>Title     : Sanctions Available for Application to Violators of IETF IPR Policy
> Author(s)       : Adrian Farrel
>                           Pete Resnick
> Filename        : draft-farrresnickel-ipr-sanctions-01.txt
> Pages           : 10
> Date            : 2012-03-02
> 
>    The IETF has developed and documented policies that govern the
>    behavior of all IETF participants with respect to intellectual
>    property about which they might reasonably be aware.
> 
>    The IETF takes conformance to these IPR policies very seriously.
>    However, there has been some ambiguity as to what the appropriate
>    sanctions are for the violation of these policies, and how and by
>    whom those sanctions are to be applied.
> 
>    This document discusses these issues and provides a suite of
>    potential actions that may be taken within the IETF community.
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-farrresnickel-ipr-sanctions-01.txt


From marka@isc.org  Fri Mar  2 14:48:39 2012
Return-Path: <marka@isc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6336D21E8083 for <ietf@ietfa.amsl.com>; Fri,  2 Mar 2012 14:48:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 7odMBs2moEIH for <ietf@ietfa.amsl.com>; Fri,  2 Mar 2012 14:48:38 -0800 (PST)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [IPv6:2001:500:60::65]) by ietfa.amsl.com (Postfix) with ESMTP id 5AD4221E803C for <ietf@ietf.org>; Fri,  2 Mar 2012 14:48:38 -0800 (PST)
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mail.isc.org", Issuer "RapidSSL CA" (not verified)) by mx.ams1.isc.org (Postfix) with ESMTPS id F25FA5F984C; Fri,  2 Mar 2012 22:48:26 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (unknown [IPv6:2001:470:1f00:820:9892:9f19:d063:bddd]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by bikeshed.isc.org (Postfix) with ESMTPSA id 7B0CF216C36; Fri,  2 Mar 2012 22:48:24 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (Postfix) with ESMTP id E2B111E02C9D; Sat,  3 Mar 2012 09:48:16 +1100 (EST)
To: "John R. Levine" <johnl@iecc.com>
From: Mark Andrews <marka@isc.org>
References: <20120228015606.2227.qmail@joyce.lan> <4F4D53E2.5080803@dougbarton.us> <alpine.BSF.2.00.1202281745310.7969@joyce.lan> <4F50939C.4020608@dougbarton.us> <alpine.BSF.2.00.1203020941360.37874@joyce.lan>
Subject: Re: provisioning software, was DNS RRTYPEs, the difficulty with
In-reply-to: Your message of "02 Mar 2012 12:00:22 CDT." <alpine.BSF.2.00.1203020941360.37874@joyce.lan>
Date: Sat, 03 Mar 2012 09:48:16 +1100
Message-Id: <20120302224816.E2B111E02C9D@drugs.dv.isc.org>
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Mar 2012 22:48:39 -0000

In message <alpine.BSF.2.00.1203020941360.37874@joyce.lan>, "John R. Levine" wr
ites:
> >> By the way, what's your opinion of draft-levine-dnsextlang-02?
> >
> > It isn't clear to me what problem you're trying to solve. For resolving
> > name servers 3597 should be enough. For authoritative name servers your
> > idea is sort of interesting, but generally upgrading the software to
> > pick up support for new RRtypes is a good idea, since you'll also pick
> > up new security fixes, etc.
> 
> Oh, wow.  Now I see the problem: people here are totally unaware of what 
> using DNS software is like if you're not a DNS weenie.
> 
> If you think that it's reasonable to require a new version of your DNS 
> software every time there's a new RR, you've conceded total defeat.  On 
> most servers I know, software upgrades are risky and infrequent.  It could 
> easily take a year for a new version of BIND to percolate out of the lab, 
> into the various distribution channels, and to be installed on people's 
> servers, by which time everyone has built their applications with TXT 
> records and it's too late.

Well for BIND it's add a new file that defines the type's methods
and recompile.  That isn't a whole new version.

> Moreover, the servers aren't the hard part, it's the provisioning systems. 
> You and I may edit our zone files with emacs, but civilians use web based 
> things with pulldown menus and checkboxes.  If they can't enter an RR into 
> one of them it doesn't matter whether the name server supports it or not. 
> This latest round of teeth gnashing was provoked by discussions in the 
> spfbis WG, where we're wondering whether to deprecate the type 99 SPF 
> record.  Among the reasons it's unused in practice is that nobody's 
> provisioning system lets you create SPF records.

Which is why there is a format for unknown types.  You can cut and
paste them as easily as known types.  Unfortunately the provision
systems often do a subset of RFC 1035 types let alone anything
newer.  Basically they are often just plain garbage.

> The point of my draft is that it's an extension language that both name 
> servers and provisioning systems can read on the fly.  Add a new stanza to 
> /etc/rrtypes and you're done, no software upgrades needed.  The risk is 
> much lower since the worst that will happen if the new stanza is broken is 
> that the provisioning software and name servers will ignore it, not 
> that the whole thing will crash.
>
> Sure, there are some RRs with complex semantics that can't be done without 
> new code (DNSSEC being the major example), but most RRs are syntactically 
> and semantically trivial, just a bunch of fields that the server doesn't 
> even interpret once it's parsed the master records or their equivalent.
> 
> Until the DNS crowd admits that provisioning systems are a major 
> bottleneck, and telling people to hand-code more types into them isn't 
> going to happen, there's no chance of getting more RRs deployed.

Until provisoning systems accept UNKNOWN record types they will
always be a bottle neck.  Without that you will have to wait for
the change request to be processed.  Given the history just getting
AAAA records added to most of these system it will be forever.

All the tools we ship support UNKNOWN record types and classes.

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

From johnl@iecc.com  Fri Mar  2 15:13:25 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 9AA3F21E8029 for <ietf@ietfa.amsl.com>; Fri,  2 Mar 2012 15:13:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.39
X-Spam-Level: 
X-Spam-Status: No, score=-102.39 tagged_above=-999 required=5 tests=[AWL=0.210, 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 J2PpAwC8qFqZ for <ietf@ietfa.amsl.com>; Fri,  2 Mar 2012 15:13:24 -0800 (PST)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id B2E5C21E8010 for <ietf@ietf.org>; Fri,  2 Mar 2012 15:13:24 -0800 (PST)
Received: (qmail 57553 invoked from network); 2 Mar 2012 23:13:23 -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=e0d0.4f515413.k1203; bh=ctHhp+bhTwPTYae4oU9LJ3zb25ErvNXpqk97zlqtfps=; b=UPQTXUhAMsDPkDq9TZzpx7orCpTY/bEBTmZsJ8P41QAO6OSvjekOnKKtJWwowZp0MM2oQ3+rmZa+lJaHMWFzV1aC8pjGqzDPDy7Ou9U5+8KBst4bCMhdTqFLRqr8QMcMebUCiOM4feqt/DfUqLIeWWpxwD9NTSy5dYNhN8fsT9U=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Received: (ofmipd 127.0.0.1) with (DHE-RSA-AES256-SHA encrypted) SMTP; 2 Mar 2012 23:13:01 -0000
Date: 2 Mar 2012 18:13:23 -0500
Message-ID: <alpine.BSF.2.00.1203021755270.76484@joyce.lan>
From: "John R. Levine" <johnl@iecc.com>
To: "Mark Andrews" <marka@isc.org>
Subject: Re: provisioning software, was DNS RRTYPEs, the difficulty with
In-Reply-To: <20120302224816.E2B111E02C9D@drugs.dv.isc.org>
References: <20120228015606.2227.qmail@joyce.lan> <4F4D53E2.5080803@dougbarton.us> <alpine.BSF.2.00.1202281745310.7969@joyce.lan> <4F50939C.4020608@dougbarton.us> <alpine.BSF.2.00.1203020941360.37874@joyce.lan> <20120302224816.E2B111E02C9D@drugs.dv.isc.org>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
Cleverness: None detected
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Mar 2012 23:13:25 -0000

> Well for BIND it's add a new file that defines the type's methods
> and recompile.  That isn't a whole new version.

Recompile -> new version.  These days, most server systems are built from 
precompiled packages.  Check your local Linux box for an example.

> Which is why there is a format for unknown types.  You can cut and
> paste them as easily as known types.  Unfortunately the provision
> systems often do a subset of RFC 1035 types let alone anything
> newer.  Basically they are often just plain garbage.

Well, yes.  Wouldn't it be nice to have provisioning systems that could be 
configured to support the RR types you want to use?  If so, you might want 
to look at my draft.

> Until provisoning systems accept UNKNOWN record types they will
> always be a bottle neck.  Without that you will have to wait for
> the change request to be processed.  Given the history just getting
> AAAA records added to most of these system it will be forever.

AAAA was unusually painful, since it requires adding a parser for IPv6 
addresses.  (Having hacked it into my provisioning system, I speak from 
experience.)  Most new RR types are just strings, numbers, names, and the 
occasional bit field.

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

From bernard_aboba@hotmail.com  Fri Mar  2 16:32:28 2012
Return-Path: <bernard_aboba@hotmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0A0FA21E8037 for <ietf@ietfa.amsl.com>; Fri,  2 Mar 2012 16:32:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.625
X-Spam-Level: 
X-Spam-Status: No, score=-100.625 tagged_above=-999 required=5 tests=[AWL=-0.627, BAYES_50=0.001, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9ap6LJUm0L1m for <ietf@ietfa.amsl.com>; Fri,  2 Mar 2012 16:32:27 -0800 (PST)
Received: from blu0-omc2-s36.blu0.hotmail.com (blu0-omc2-s36.blu0.hotmail.com [65.55.111.111]) by ietfa.amsl.com (Postfix) with ESMTP id 6D34D21E8082 for <ietf@ietf.org>; Fri,  2 Mar 2012 16:32:27 -0800 (PST)
Received: from BLU152-W4 ([65.55.111.71]) by blu0-omc2-s36.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675);  Fri, 2 Mar 2012 16:32:26 -0800
Message-ID: <BLU152-W454679C371D8155B1743693520@phx.gbl>
Content-Type: multipart/alternative; boundary="_85fbb775-936c-4669-9c56-539ad3fe1df0_"
X-Originating-IP: [131.107.0.125]
From: Bernard Aboba <bernard_aboba@hotmail.com>
To: <ietf@ietf.org>
Subject: Re: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt> (Allocation of an Associated Channel Code Point for Use by ITU-T Ethernet based OAM)
Date: Fri, 2 Mar 2012 16:32:26 -0800
Importance: Normal
MIME-Version: 1.0
X-OriginalArrivalTime: 03 Mar 2012 00:32:26.0764 (UTC) FILETIME=[1BF49CC0:01CCF8D5]
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 03 Mar 2012 00:32:28 -0000

--_85fbb775-936c-4669-9c56-539ad3fe1df0_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


Russ Housley said:

"This is not an IETF problem=2C and I do not think that the IETF ought to=20
be discussing the internal workings of the ITU-T process.  The point is=20
to come up with a mechanism that allows the code point to be assigned if
 and only if the ITU-T does come to a consensus by whatever means is=20
allowed by their own process. "

[BA] Indeed=2C as a procedural matter=2C it should be clear that this is an=
 IETF last call on draft-betts-itu-oam-ach-code-point=2C not an IETF last c=
all on G.8113.1.  As Russ has noted=2C draft-betts-itu-oam-ach-code-point c=
an be approved for publication=2C holding issuance of an RFC and assignment=
 of a code point until G.8113.1 is approved by the ITU-T.  This guarantees =
that upon publication of draft-betts-itu-oam-ach-code-point as an RFC=2C th=
e reference will be to a stable=2C ITU-T approved version of G.8113.1. =20
 		 	   		  =

--_85fbb775-936c-4669-9c56-539ad3fe1df0_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<style><!--
.hmmessage P
{
margin:0px=3B
padding:0px
}
body.hmmessage
{
font-size: 10pt=3B
font-family:Tahoma
}
--></style></head>
<body class=3D'hmmessage'><div dir=3D'ltr'>
Russ Housley said:<br><br>"This is not an IETF problem=2C and I do not thin=
k that the IETF ought to=20
be discussing the internal workings of the ITU-T process.  The point is=20
to come up with a mechanism that allows the code point to be assigned if
 and only if the ITU-T does come to a consensus by whatever means is=20
allowed by their own process. "<br><br>[BA] Indeed=2C as a procedural matte=
r=2C it should be clear that this is an IETF last call on draft-betts-itu-o=
am-ach-code-point=2C not an IETF last call on G.8113.1.&nbsp=3B As Russ has=
 noted=2C draft-betts-itu-oam-ach-code-point can be approved for publicatio=
n=2C holding issuance of an RFC and assignment of a code point until G.8113=
.1 is approved by the ITU-T.&nbsp=3B This guarantees that upon publication =
of draft-betts-itu-oam-ach-code-point as an RFC=2C the reference will be to=
 a stable=2C ITU-T approved version of G.8113.1.&nbsp=3B <br> 		 	   		  </=
div></body>
</html>=

--_85fbb775-936c-4669-9c56-539ad3fe1df0_--

From randy@qualcomm.com  Fri Mar  2 16:48:43 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 8FDDC21E8037 for <ietf@ietfa.amsl.com>; Fri,  2 Mar 2012 16:48:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.928
X-Spam-Level: 
X-Spam-Status: No, score=-105.928 tagged_above=-999 required=5 tests=[AWL=0.671, 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 uRPwNfpp83xM for <ietf@ietfa.amsl.com>; Fri,  2 Mar 2012 16:48:42 -0800 (PST)
Received: from wolverine01.qualcomm.com (wolverine01.qualcomm.com [199.106.114.254]) by ietfa.amsl.com (Postfix) with ESMTP id DBEE721E8082 for <ietf@ietf.org>; Fri,  2 Mar 2012 16:48:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=randy@qualcomm.com; q=dns/txt; s=qcdkim; t=1330735722; x=1362271722; h=message-id:x-mailer:date:to:from:subject:cc:mime-version: content-type:x-random-sig-tag:x-originating-ip; z=Message-ID:=20<p06240605cb7713381b6a@loud.pensive.org> |X-Mailer:=20Eudora=20for=20Mac=20OS=20X|Date:=20Fri,=202 =20Mar=202012=2016:48:22=20-0800|To:=20<ietf@ietf.org> |From:=20Randall=20Gellens=20<randy@qualcomm.com> |Subject:=20Re:=20Last=20Call:=20<draft-ietf-appsawg-xdas h-03.txt>|CC:=20Peter=20Saint-Andre=20<stpeter@stpeter.im >,=20Dave=20Crocker=20<dcrocker@bbiw.net>|MIME-Version: =201.0|Content-Type:=20text/plain=3B=20charset=3D"us-asci i"=3B=20format=3Dflowed|X-Random-Sig-Tag:=201.0b28 |X-Originating-IP:=20[172.30.39.5]; bh=lJ1WRW1sz9xmnpR+jYRnj6HGOhBzNDpMYm2Mdhvx+70=; b=MQpcHBKlqY3jfNoXQErh9+2PznieMtoElTZcgV+0SszWIfoqusDbtWn8 rWXx2MRxKTVKiuLXQFdSZtqf6jtm3PmPioEgkjbhZZ4zkOp9b9KZbvVn6 O6sB7Vp3SkExbWImN3cYhmsVY7fGDq698K8P+TE3HbX4ZzxSYwenxi+Cq 4=;
X-IronPort-AV: E=McAfee;i="5400,1158,6637"; a="168774205"
Received: from ironmsg03-r.qualcomm.com ([172.30.46.17]) by wolverine01.qualcomm.com with ESMTP; 02 Mar 2012 16:48:26 -0800
X-IronPort-AV: E=Sophos;i="4.73,518,1325491200"; d="scan'208";a="209359516"
Received: from nasanexhc07.na.qualcomm.com ([172.30.39.190]) by Ironmsg03-R.qualcomm.com with ESMTP/TLS/AES128-SHA; 02 Mar 2012 16:48:26 -0800
Received: from loud.pensive.org (172.30.39.5) by qcmail1.qualcomm.com (172.30.39.190) with Microsoft SMTP Server (TLS) id 14.1.339.1; Fri, 2 Mar 2012 16:48:26 -0800
Message-ID: <p06240605cb7713381b6a@loud.pensive.org>
X-Mailer: Eudora for Mac OS X
Date: Fri, 2 Mar 2012 16:48:22 -0800
To: <ietf@ietf.org>
From: Randall Gellens <randy@qualcomm.com>
Subject: Re: Last Call: <draft-ietf-appsawg-xdash-03.txt>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Random-Sig-Tag: 1.0b28
X-Originating-IP: [172.30.39.5]
Cc: Dave Crocker <dcrocker@bbiw.net>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 03 Mar 2012 00:48:43 -0000

Hi all,

Three suggestions for edits:

First: I suggest adding a brief note to this text in Appendix B:

    2.  When parameter names might have significant meaning.  However,
        this case too is rare, since implementers can almost always find
        a synonym for an existing term (e.g., "urgency" instead of
        "priority") or simply invent a more creative name (e.g., "get-it-
        there-fast").

At the end, I suggest adding an additional sentence:

     The existence of multiple similarly-named paramaters can
     be confusing, but this is true regardless if there is an
     attempt to segregate standard and non-standard (e.g.,
     "X-Priority" can be confused with "Urgency").


Second, consider this the text in Appendix B:

    Furthermore, often standardization of a non-standard parameter or
    protocol element leads to subtly different behavior (e.g., the
    standard version might have different security properties as a result
    of security review provided during the standardization process).  If
    implementers treat the old, non-standard parameter and the new,
    standard parameter as equivalent, interoperability and security
    problems can ensue.

This is of course true, but I think it is somewhat misleading:  If a 
parameter starts out as non-standard, gets some deployment, then as 
part of an effort to standardize it, flaws are discovered which 
require different behavior, I think we want the new, standardized 
parameter to have a different name so it can be distinguished and the 
new, more desirable behavior mandated.  This is the same regardless 
if the old and new parameters are, say, "x-priority" and "priority", 
or "priority" and "urgency".  In either case, implementers shouldn't 
treat the old parameter as identical to the new, standardized one.

Further, I think it's a good thing when an old, non-standard 
parameter is standardized and flaws are corrected.  We should 
encourage, not discourage this.

It would be good to have at least a little text along these lines. 
Specifically, I suggest adding new text at the end:

     Analysis of non-standard parameters and protocol elements
     to detect and correct flaws is in general a good thing and
     is not intended to be discouraged by the lack of
     distinction in element names.  Whenever an originally
     non-standard parameter or protocol element is standardized
     and the new form has differences which affect
     interoperability or security properties, implementations
     MUST NOT treat the old form as identical to the new form.

Further in the appendix, justification 1 is over-drawn.  I suggest 
toning it down slightly, from:

    1.  Implementers are easily confused and can't be expected to know
        that a parameter is non-standard unless it contains the "X-"
        prefix.  However, implementers already are quite flexible about
        using both prefixed and non-prefixed names based on what works in
        the field, so the distinction between de facto names (e.g.,
        "X-foo") and de jure names (e.g., "foo") is without force.

To:

    1.  Implementers may confuse parameters that have similar
    names; a rigid distinction such as an "X-" prefix can make
    this clear.  However, in practice implementers are forced
    to blur the distinction (e.g., by treating "X-foo" as a de
    facto standard) and so it inevitably becomes meaningless.

-- 
Randall Gellens
Opinions are personal;    facts are suspect;    I speak for myself only
-------------- Randomly selected tag: ---------------
There is only one thing in the world worse than being talked about, and
that is not being talked about.     --Oscar Wilde

From scott@kitterman.com  Fri Mar  2 16:54:19 2012
Return-Path: <scott@kitterman.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D6E3D21E808F for <ietf@ietfa.amsl.com>; Fri,  2 Mar 2012 16:54:19 -0800 (PST)
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.015,  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 JuCXZyiIDsdM for <ietf@ietfa.amsl.com>; Fri,  2 Mar 2012 16:54:19 -0800 (PST)
Received: from mailout02.controlledmail.com (mailout02.controlledmail.com [72.81.252.18]) by ietfa.amsl.com (Postfix) with ESMTP id 1182F21E808B for <ietf@ietf.org>; Fri,  2 Mar 2012 16:54:19 -0800 (PST)
Received: from mailout02.controlledmail.com (localhost [127.0.0.1]) by mailout02.controlledmail.com (Postfix) with ESMTP id 82C1E20E40DA; Fri,  2 Mar 2012 19:54:18 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=2007-00; t=1330736058; bh=pK0qycmmNmKG5xXeZOsarPmgeFohsrvCgcCvQZKxLwk=; h=From:To:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version:Content-Transfer-Encoding:Content-Type; b=QxJclQ5jn/VEB4gJpBhKiVQikaD9pmU6OHJZsEVfmRAjYhkw9sbK/j8NAdPXz5YTj 4rR4NlwaHw9khWRubdgnngQmBqxnJVHRraJxQt/tq9wWheUzqChxPwFSgww8Pb/Xlj VIvRjIR927ltJEx1oh/CviQXMDmoO42WMayhSFXw=
Received: from scott-latitude-e6320.localnet (static-72-81-252-21.bltmmd.fios.verizon.net [72.81.252.21]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailout02.controlledmail.com (Postfix) with ESMTPSA id 6566C20E408E;  Fri,  2 Mar 2012 19:54:18 -0500 (EST)
From: Scott Kitterman <scott@kitterman.com>
To: ietf@ietf.org
Subject: Re: Last Call: <draft-ietf-marf-spf-reporting-08.txt> (SPF Authentication Failure Reporting using the Abuse Report Format)	to Proposed Standard
Date: Fri, 02 Mar 2012 19:27:35 -0500
Message-ID: <8216968.xi76SI5ueq@scott-latitude-e6320>
User-Agent: KMail/4.7.3 (Linux/3.0.0-16-generic-pae; KDE/4.7.4; i686; ; )
In-Reply-To: <9452079D1A51524AA5749AD23E00392807309D@exch-mbx901.corp.cloudmark.com>
References: <20120301004643.17274.83943.idtracker@ietfa.amsl.com> <1349422.baAQMnczus@scott-latitude-e6320> <9452079D1A51524AA5749AD23E00392807309D@exch-mbx901.corp.cloudmark.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
X-AV-Checked: ClamAV using ClamSMTP
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 03 Mar 2012 00:54:19 -0000

On Friday, March 02, 2012 06:43:32 PM Murray S. Kucherawy wrote:
> > -----Original Message-----
> > From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
> > Scott Kitterman Sent: Friday, March 02, 2012 7:23 AM
> > To: ietf@ietf.org
> > Subject: Re: Last Call: <draft-ietf-marf-spf-reporting-08.txt> (SPF
> > Authentication Failure Reporting using the Abuse Report Format) to
> > Proposed Standard
> > 
> > Based on that, I think that the sentence in paragraph 6 could be lost
> > without losing anything important, so I think it should stay as it is.
> 
> Yes, I suggest that the sentence that comprises Section 6 proper can be
> dropped.  The text currently in 6.1 can be moved up to 6, and the current
> 6.1 thus removed.

Done in my local copy.

> > It might be worth someone looking at
> > draft-ietf-marf-authfailure-report-10 again to see if that's really
> > appropriate.
> 
> I'll take a second look.

Thanks.

Scott K

From scott@kitterman.com  Fri Mar  2 16:54:41 2012
Return-Path: <scott@kitterman.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B741521E8097 for <ietf@ietfa.amsl.com>; Fri,  2 Mar 2012 16:54:41 -0800 (PST)
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.014,  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 Yih0LdXXQfiB for <ietf@ietfa.amsl.com>; Fri,  2 Mar 2012 16:54:41 -0800 (PST)
Received: from mailout02.controlledmail.com (mailout02.controlledmail.com [72.81.252.18]) by ietfa.amsl.com (Postfix) with ESMTP id F29A021E808B for <ietf@ietf.org>; Fri,  2 Mar 2012 16:54:40 -0800 (PST)
Received: from mailout02.controlledmail.com (localhost [127.0.0.1]) by mailout02.controlledmail.com (Postfix) with ESMTP id 8486620E40DA; Fri,  2 Mar 2012 19:54:40 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=2007-00; t=1330736080; bh=WN7Rk1G7Fl8rSqux/Xrq0+63rPwWEAjAfizu4AHjY3w=; h=From:To:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version:Content-Transfer-Encoding:Content-Type; b=W4cdMWAf8jOUjU2HvgDVYaOjETb+ntpRFLkKtqCEUTQ/XkF04hlO3WeSHm5P8gO5f GLivbmZHo6CyIebMj3T/xzFdt7Jve+vxfGJP1MP4EujGJo/gU5nxm/GuSqnqdr14HM /QbIncC8TqIWCGME9Vm4ontpOUvCBhidNAzn+0GI=
Received: from scott-latitude-e6320.localnet (static-72-81-252-21.bltmmd.fios.verizon.net [72.81.252.21]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailout02.controlledmail.com (Postfix) with ESMTPSA id 77A9720E408E;  Fri,  2 Mar 2012 19:54:40 -0500 (EST)
From: Scott Kitterman <scott@kitterman.com>
To: ietf@ietf.org
Subject: Re: Last Call: <draft-ietf-marf-spf-reporting-08.txt> (SPF Authentication Failure Reporting using the Abuse Report Format)	to	Proposed Standard
Date: Fri, 02 Mar 2012 19:54:40 -0500
Message-ID: <1562623.FH7htBXOsi@scott-latitude-e6320>
User-Agent: KMail/4.7.3 (Linux/3.0.0-16-generic-pae; KDE/4.7.4; i686; ; )
In-Reply-To: <9452079D1A51524AA5749AD23E003928073049@exch-mbx901.corp.cloudmark.com>
References: <20120301004643.17274.83943.idtracker@ietfa.amsl.com> <18744934.WPNuXzvee6@scott-latitude-e6320> <9452079D1A51524AA5749AD23E003928073049@exch-mbx901.corp.cloudmark.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
X-AV-Checked: ClamAV using ClamSMTP
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 03 Mar 2012 00:54:41 -0000

On Friday, March 02, 2012 06:28:32 PM Murray S. Kucherawy wrote:
> > -----Original Message-----
> > From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
> > Scott Kitterman Sent: Friday, March 02, 2012 9:19 AM
> > To: ietf@ietf.org
> > Subject: Re: Last Call: <draft-ietf-marf-spf-reporting-08.txt> (SPF
> > Authentication Failure Reporting using the Abuse Report Format) to
> > Proposed Standard
> > 
> > > >    "The HELO/EHLO command SHOULD also be selected so that it
> > > >    
> > > >     will pass [SPF] HELO checks."
> > > > 
> > > > I could not understand what to do about the above
> > > > recommendation.
> > > > FWIW, the command is specified in RFC 5321.  That specification
> > > > is
> > > > not referenced by this draft.
> > > 
> > > Yes, that needs to be clarified, the reference added, and the typo
> > > in
> > > the section title needs correction.
> > 
> > I agree I should add the reference to 5321.  Is informative sufficient
> > (I don't think any detailed understand of Mail From or EHLO/HELO is
> > necessary to implement this spec).
> > 
> > I can see the construction is awkward, but I'm not sure how to make it
> > better. I'd appreciate suggestions.
> 
> I suggest:
> 
> OLD:
>    In addition to the advice in security considerations of
>    [I-D.IETF-MARF-AS] the additional consderations apply to [SPF] auth
>    failure reports.  If the MAIL FROM command is not the NULL return
>    address, i.e., "MAIL FROM:<>", then the selected MAIL FROM address
>    MUST pass [SPF] MAIL FROM checks on receipt.  The HELO/EHLO command
>    SHOULD also be selected so that it will pass [SPF] HELO checks.
> 
> NEW:
> 	In addition to the advice in the Security Considerations section of
> 	[I-D.IETF-MARF-AS], these additional considerations apply to
> 	generation of [SPF] authentication failure reports:
> 
> 	o If the return address to be used will not be the NULL return
> 	  address, i.e., "MAIL FROM:<>", then the selected return address
> 	  MUST be selected such that it will pass [SPF] MAIL FROM checks
> 	  upon initial receipt.
> 
> 	o If the report is passed to the Mail Submission Agent (MSA)
> 	  using [SMTP], the HELO/EHLO command parameter SHOULD also be
> 	  selected so that it will pass [SPF] HELO checks.
> 
> If needed, MSA is defined in RFC5598, so maybe this is another argument for
> adding it as an informative reference and changing to use ADMD as discussed
> in the other thread.

Thanks.  Done (including replacing domain owner) in my local copy.

Scott K

From sant9442@gmail.com  Fri Mar  2 19:16:47 2012
Return-Path: <sant9442@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4570721F85AD for <ietf@ietfa.amsl.com>; Fri,  2 Mar 2012 19:16:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.232
X-Spam-Level: 
X-Spam-Status: No, score=-3.232 tagged_above=-999 required=5 tests=[AWL=0.367,  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 bXXI02r46Gma for <ietf@ietfa.amsl.com>; Fri,  2 Mar 2012 19:16:46 -0800 (PST)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id 7F5AC21F85AA for <ietf@ietf.org>; Fri,  2 Mar 2012 19:16:46 -0800 (PST)
Received: by ggmi1 with SMTP id i1so1228220ggm.31 for <ietf@ietf.org>; Fri, 02 Mar 2012 19:16:46 -0800 (PST)
Received-SPF: pass (google.com: domain of sant9442@gmail.com designates 10.101.175.2 as permitted sender) client-ip=10.101.175.2; 
Authentication-Results: mr.google.com; spf=pass (google.com: domain of sant9442@gmail.com designates 10.101.175.2 as permitted sender) smtp.mail=sant9442@gmail.com; dkim=pass header.i=sant9442@gmail.com
Received: from mr.google.com ([10.101.175.2]) by 10.101.175.2 with SMTP id c2mr5305760anp.73.1330744606188 (num_hops = 1); Fri, 02 Mar 2012 19:16:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=/VGQZmBH9fB9ezfL2IVH9WBLQTAIbpqTbDeZbm8pZlA=; b=zvApxW3EsaDvYsAiI0yV0uSiZnRzZxFqy/9xTCPKDaPUDqWtnZ88fhZP1QMpQGu2pU Sevm0hQnhQZErBtR58+ShLn3DotaFW79q/AEUUGAoTih+OKsDd7EeMGoM+Bu7vYUiuaS 7BnHB3R1MFJBf/MaPF9uI4/1/jJ6FvhGXyBWocoz/yInkmTkNSSCNxPxECu5OCBFeX9A r89twuBRUJHYX4Wq6kwMvqXgKrU6nQnHsjz5JI5ya0WDwV289bU8oZBqfp+sqHyXPiJj a3b/+Ds5u4hIuO4kKQR+3MnSEHP28OWJrv7cWLfcqs1edJFlBD89Hbj53GKRB8aV+lhO YDQQ==
Received: by 10.101.175.2 with SMTP id c2mr4205536anp.73.1330744606128; Fri, 02 Mar 2012 19:16:46 -0800 (PST)
Received: from adsl-215-50-126.mia.bellsouth.net (99-3-147-93.lightspeed.miamfl.sbcglobal.net. [99.3.147.93]) by mx.google.com with ESMTPS id x13sm12334468ang.21.2012.03.02.19.16.43 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 02 Mar 2012 19:16:44 -0800 (PST)
Message-ID: <4F518D15.1020901@gmail.com>
Date: Fri, 02 Mar 2012 22:16:37 -0500
From: Hector <sant9442@gmail.com>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to	Proposed Standard
References: <20120301004219.15266.76505.idtracker@ietfa.amsl.com>	<6.2.5.6.2.20120301120015.0940b2c0@resistor.net>	<9452079D1A51524AA5749AD23E00392806FE0C@exch-mbx901.corp.cloudmark.com>	<CAC4RtVCm_=VkfHiP_93_AKbo-X3NZc=NEt2pX_cEg6LYHtHSEQ@mail.gmail.com>	<4F50B339.2030003@gmail.com> <CAC4RtVA_fBAVgsDbDDXEGBCfBqUke-8dA41h_NmjHAraay+0Tw@mail.gmail.com>
In-Reply-To: <CAC4RtVA_fBAVgsDbDDXEGBCfBqUke-8dA41h_NmjHAraay+0Tw@mail.gmail.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, 03 Mar 2012 03:16:47 -0000

Barry Leiba wrote:
> On Fri, Mar 2, 2012 at 6:47 AM, Hector <sant9442@gmail.com> wrote:
>> If I understand where you going with this, IMV, I don't think it is a good
>> thing SMTP systems should be expected will be processing the payload or its
>> headers before the EOD is issued.
> 
> This document doesn't specify anything that needs header processing
> *during* the SMTP transaction.[1]  The specified manipulation would
> happen after the MTA had accepted the message, and before it relayed
> it to the next hop, so I don't think there's any timeout-sensitive
> issue here.

Thanks Barry for your follow up.

I was provided input relative to the generality of your question 
regarding an "SMTP system" which you now provided a better specific 
example(s) to what I was referring to, case in point.

> Unrelated to Hector's note:
> Does anyone's answer change if I point out that we already have at
> least two protocols that have an MTA alter message header fields in
> between message receipt and message relay?
> 
> An MTA that supports DKIM [RFC6376] might, under some conditions,
> remove an existing signature and add its own.

My question is "when" or does it matter?

Is its done during the SMTP session (DATA before the EOD response) or 
is it done after the mail is accepted?

I believe if done at DATA, then we are still talking the SMTP 
protocol. If it is done after the SMTP session, then its not really 
something we can say is still part of the SMTP protocol.

It also depends on the augmented protocol itself.

Example, as an DKIM implementator, the verification is only done at 
the SMTP DATA, no resigning or anything related to "CHANGE" is done 
here.  Anything close to that is completely outside of SMTP. But.....

> An MTA that implements the Authentication-Results header field
> [RFC5451] might remove an existing header and add its own.

This is closer to a higher potential for SMTP systems to consider 
because of the nature and intent of new receiver message validations 
now using a AUTH-RES header to provide receiver processing "state" 
information to be either appended (a change) and/or additional 
AUTH-RES header added.

But there also the idea that you won't do (change) because AUTH-RES 
also provides the machine identity that did the checking and added the 
information.  So if there are now new state information to add, I 
would think you will see want to have some persistency and trace 
history of the different hops, machines that did the AUTH-RES state 
checks.

I was purely thinking in general terms of how/where an email augmented 
protocol would be expected to be implemented for quick plug and play 
operations.

To me, AUTH-RES "change" would fits better for your question when all 
done in the same ADMD. It is what might be expected and happen in 
adding new processing state information   DKIM verification and 
changes related to stripping/replacement (a already controversial 
subjective tampering idea) I would not expect to be "normally" done in 
a SMTP receiver.

Of course, its just one person opinion and one input only.

Thanks

--
HLS

From johnl@iecc.com  Fri Mar  2 20:12:18 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 8B71621E8058 for <ietf@ietfa.amsl.com>; Fri,  2 Mar 2012 20:12:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.584
X-Spam-Level: 
X-Spam-Status: No, score=-110.584 tagged_above=-999 required=5 tests=[AWL=0.615, 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 H1RzL5PLFx3a for <ietf@ietfa.amsl.com>; Fri,  2 Mar 2012 20:12:17 -0800 (PST)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 9D03F21E8037 for <ietf@ietf.org>; Fri,  2 Mar 2012 20:12:17 -0800 (PST)
Received: (qmail 22121 invoked from network); 3 Mar 2012 04:12:15 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 3 Mar 2012 04:12:15 -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=4f519a1f.xn--i8sz2z.k1203; i=johnl@user.iecc.com; bh=R7hfYP1WmVF3S8vtUzVGrdpys9Oby8y08evR39nUHj0=; b=ujlztABt0CG+n4Mf3qIlWfsGj/4nnDVspvAgvT6KdibIZvblS9Nq8dsShJyPt6jsBbuo+oZp0adaGKDwpY9O/HUeOtukWv23ttYacM3TokegDF1giq/E+pRG/XmZsIZijRf8mLb10ZYwFEwOEjBLyMCfI6n/TMkqabA2dtsOKyk=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 3 Mar 2012 04:11:53 -0000
Message-ID: <20120303041153.23749.qmail@joyce.lan>
From: "John Levine" <johnl@iecc.com>
To: ietf@ietf.org
Subject: Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard
In-Reply-To: <CAC4RtVA3F8gsBWY65W5KNDE+408EvtP+hp5GTzLg4FMgC1bdcQ@mail.gmail.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
Cc: barryleiba@computer.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 03 Mar 2012 04:12:18 -0000

>> This draft also defines the MT-Priority header field.  It is quite unusual
>> for a SMTP extension specification to define a mail header field. ...

>This is my major concern about this protocol as well, as I note in the
>PROTO writeup (which, unfortunately, can't be seen publicly because of
>a limitation in the datatracker; perhaps I should post it here).  I'm
>interested in hearing whether others share this concern, and what the
>community consensus is about it.

I have no problem logging stuff from the SMTP session into a message
header, we've been doing that since forever.  But I have a lot of
problem turning a header back into SMTP for a subsequent relay, for
two reasons.

One is just that it's ugly.  There were good reasons to separate the
envelope from the body back in the 1970s, and I think those reasons
are just as good now.  Over in the EAI group, there was a valiant
effort to tunnel EAI messages through non-EAI SMTP servers via
downgrades, and we eventually gave up.  Now, if you want to send an
EAI message, there has to be an EAI path all the way from the sender
to the recipient.  This isn't exactly analogous, but it's instructive.

The other reason is that I think it's too ill-specified to
interoperate.  The theory seems to be that the relay server notices an
MT-Priority: header, and (vigorous waving of hands) somehow decides if
the message has sufficient virtue to promote the header back into the
SMTP session.  The hand-waving is not persuasive; the suggestion of
S/MIME, which obviously won't work, is not encouraging.

If you want to brave the ugliness and standardize this, the spec needs
to explain how the server decides whether to believe an MT-Priority
header.  If it doesn't, it's too vague to interoperate.

So I have two suggestions.  One is to leave it as is, and make it
experimental. If it turns out the tunnels all work the same way, you
can come back and add the spec about how they work and rev it as
standards track.  The other is to take out the tunnel bit and make it
standards track now, so a compliant implementation needs
priority-aware MTAs from end to end.  Even if you take out the tunnel
stuff in the spec, you can still tunnel in your implementations, using
whatever non-standard ad hoc kludges you want.  Since the current spec
has gaps that would need to be filled by non-standard ad hoc kludges
anyway, you haven't lost anything.

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

From sant9442@gmail.com  Fri Mar  2 21:54:03 2012
Return-Path: <sant9442@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B50EB21F853B for <ietf@ietfa.amsl.com>; Fri,  2 Mar 2012 21:54:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.25
X-Spam-Level: 
X-Spam-Status: No, score=-3.25 tagged_above=-999 required=5 tests=[AWL=0.349,  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 XPt+Me6KaqaH for <ietf@ietfa.amsl.com>; Fri,  2 Mar 2012 21:54:03 -0800 (PST)
Received: from mail-gy0-f172.google.com (mail-gy0-f172.google.com [209.85.160.172]) by ietfa.amsl.com (Postfix) with ESMTP id EA09D21F853A for <ietf@ietf.org>; Fri,  2 Mar 2012 21:54:02 -0800 (PST)
Received: by ghbg16 with SMTP id g16so1248853ghb.31 for <ietf@ietf.org>; Fri, 02 Mar 2012 21:54:02 -0800 (PST)
Received-SPF: pass (google.com: domain of sant9442@gmail.com designates 10.236.72.195 as permitted sender) client-ip=10.236.72.195; 
Authentication-Results: mr.google.com; spf=pass (google.com: domain of sant9442@gmail.com designates 10.236.72.195 as permitted sender) smtp.mail=sant9442@gmail.com; dkim=pass header.i=sant9442@gmail.com
Received: from mr.google.com ([10.236.72.195]) by 10.236.72.195 with SMTP id t43mr17228128yhd.126.1330754042589 (num_hops = 1); Fri, 02 Mar 2012 21:54:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=MCQYXjrG58k/ltcLz1N+ahID6HhwnLmDh0+viXDhHgA=; b=hmWzwQw1Nj1DcsgL+3apn84ABsG5KFrpK/L0y/BS+HBEeEFVbsb0r/fWj5WkeCf/9d CtI/ksSeEpPLXuNDVLcrwKsWoiHHg6RzSNs4+IrLbYkU94naVtPFlJctVypTwb/GjsgR KqLLPv7uicFDNHfPh8iYDrdERoLPCk08ETPr+nc8HKCWrwK/8y3+OX/ZFpBgW/mJOhek K/Jkz2NMWxmMB2s04eW7/2Nl5F0InRWHcG87mqDudWzGs+1NxfRYMnr+NxjAH0njhdW5 dkrjuUAEih4+H3cpFEHABn65ziw0Et/r2GFUWGL2wHOueejJWF3wGBC7nn3zkpQ912WQ W4dw==
Received: by 10.236.72.195 with SMTP id t43mr13655679yhd.126.1330754042531; Fri, 02 Mar 2012 21:54:02 -0800 (PST)
Received: from adsl-215-50-126.mia.bellsouth.net (99-3-147-93.lightspeed.miamfl.sbcglobal.net. [99.3.147.93]) by mx.google.com with ESMTPS id b73sm19970393yhj.22.2012.03.02.21.54.00 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 02 Mar 2012 21:54:01 -0800 (PST)
Message-ID: <4F51B1F3.3020404@gmail.com>
Date: Sat, 03 Mar 2012 00:53:55 -0500
From: Hector <sant9442@gmail.com>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: Last Call: <draft-ietf-marf-spf-reporting-08.txt> (SPF	Authentication Failure Reporting using the Abuse Report	Format)	to	Proposed Standard
References: <20120301004643.17274.83943.idtracker@ietfa.amsl.com>	<6.2.5.6.2.20120229181328.0a95a9f8@resistor.net>	<9452079D1A51524AA5749AD23E00392806F917@exch-mbx901.corp.cloudmark.com>	<18744934.WPNuXzvee6@scott-latitude-e6320> <9452079D1A51524AA5749AD23E003928073049@exch-mbx901.corp.cloudmark.com>
In-Reply-To: <9452079D1A51524AA5749AD23E003928073049@exch-mbx901.corp.cloudmark.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, 03 Mar 2012 05:54:03 -0000

Murray S. Kucherawy wrote:
> I suggest:
> 
> OLD:
>    In addition to the advice in security considerations of
>    [I-D.IETF-MARF-AS] the additional consderations apply to [SPF] auth
>    failure reports.  If the MAIL FROM command is not the NULL return
>    address, i.e., "MAIL FROM:<>", then the selected MAIL FROM address
>    MUST pass [SPF] MAIL FROM checks on receipt.  The HELO/EHLO command
>    SHOULD also be selected so that it will pass [SPF] HELO checks.
> 
> NEW:
> 	In addition to the advice in the Security Considerations section of
> 	[I-D.IETF-MARF-AS], these additional considerations apply to
> 	generation of [SPF] authentication failure reports:
> 
> 	o If the return address to be used will not be the NULL return
> 	  address, i.e., "MAIL FROM:<>", then the selected return address
> 	  MUST be selected such that it will pass [SPF] MAIL FROM checks
> 	  upon initial receipt.
> 
> 	o If the report is passed to the Mail Submission Agent (MSA)
> 	  using [SMTP], the HELO/EHLO command parameter SHOULD also be
> 	  selected so that it will pass [SPF] HELO checks.
> 
> If needed, MSA is defined in RFC5598, so maybe this is another argument 
> for adding it as an informative reference and changing to use ADMD as 
> discussed in the other thread.

If applicable, I would like to provide the following implementation note:

MSA - what kind?

The PORT 587 kind or a Port 25 kind with a user using ESMTP AUTH?

Why?

Since use RFC6409 (formerly 4409) has a PORT 587 and ESMTP AUTH 
requirement which the public SMTP port does not, it was as a indicator 
and method to skip the strong EHLO checking requirement.

In practice this became necessary with the growth of the SOHO and home 
use NAT market with now Mommy and Daddy had their PCs on the home 
network and the MUA they used exposed the private side IP literal and 
the Connection IP was that of the NAT.

It was a problem for the SUBMISSION protocol with strong EHLO checking 
requirements.

The solution was to get the MUA (in this case Thunderbird) to offer 
flexibility in its MTA setting for the EHLO command and in the mean 
time, relaxed a port 587 connection to delay or skip any initial EHLO 
checking until the required ESMTP AUTH was completed.

With a public port SMTP session, the ESMTP AUTH (MSA like behavior) is 
not required so any EHLO checking can apply when first presented.

Thanks

--
HLS

From vesely@tana.it  Sat Mar  3 03:19:36 2012
Return-Path: <vesely@tana.it>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 07C3321F8584 for <ietf@ietfa.amsl.com>; Sat,  3 Mar 2012 03:19:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.649
X-Spam-Level: 
X-Spam-Status: No, score=-4.649 tagged_above=-999 required=5 tests=[AWL=0.070,  BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KsSnA3b7bDqx for <ietf@ietfa.amsl.com>; Sat,  3 Mar 2012 03:19:35 -0800 (PST)
Received: from wmail.tana.it (wmail.tana.it [62.94.243.226]) by ietfa.amsl.com (Postfix) with ESMTP id 2F38E21F857A for <ietf@ietf.org>; Sat,  3 Mar 2012 03:19:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=test; t=1330773571; bh=rFHpx5Bbxt0+JUz7f4thBJghQQEv66QVJxHS082CvLw=; l=980; h=Message-ID:Date:From:MIME-Version:To:References:In-Reply-To: Content-Transfer-Encoding; b=egtUgmJb+Si43gsNkew1+WJ+0xevAnHVEkmnODcX5hF1zcu+DnsG9O5b5mxVMIQ7j 7+iLhIRKt+1eKBMpx7pZGNC/lfXsp1LdzbT6bnvpknxoF1VZbp2tWm/dgWYHAhs4Mw MT8sB9B+yf6d0+FMHc+bLDoaoegkFHXFqemfP26o=
Received: from [172.25.197.158] (pcale.tana [172.25.197.158]) (AUTH: CRAM-MD5 515, TLS: TLS1.0,256bits,RSA_AES_256_CBC_SHA1) by wmail.tana.it with ESMTPSA; Sat, 03 Mar 2012 12:19:31 +0100 id 00000000005DC039.000000004F51FE43.000047DB
Message-ID: <4F51FE43.5010402@tana.it>
Date: Sat, 03 Mar 2012 12:19:31 +0100
From: Alessandro Vesely <vesely@tana.it>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: provisioning software, was DNS RRTYPEs, the difficulty with
References: <20120228015606.2227.qmail@joyce.lan> <4F4D53E2.5080803@dougbarton.us> <alpine.BSF.2.00.1202281745310.7969@joyce.lan> <4F50939C.4020608@dougbarton.us> <alpine.BSF.2.00.1203020941360.37874@joyce.lan> <20120302224816.E2B111E02C9D@drugs.dv.isc.org> <alpine.BSF.2.00.1203021755270.76484@joyce.lan>
In-Reply-To: <alpine.BSF.2.00.1203021755270.76484@joyce.lan>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 03 Mar 2012 11:19:36 -0000

On 03/Mar/12 00:13, John R. Levine wrote:
> 
>> Until provisoning systems accept UNKNOWN record types they will
>> always be a bottle neck.  Without that you will have to wait for
>> the change request to be processed.  Given the history just getting
>> AAAA records added to most of these system it will be forever.
> 
> AAAA was unusually painful, since it requires adding a parser for IPv6
> addresses.  (Having hacked it into my provisioning system, I speak
> from experience.)  Most new RR types are just strings, numbers, names,
> and the occasional bit field.

Yeah, and if ISPs already had troubles with ho-de-ho-de-ho-de-ho, how
will they join in on skee-bop-de-google-eet-skee-bop-de-goat?

Given that, designers of new RR types will want to stick to string
formats just to spare ISPs some parsing, at the cost of losing a half
of the advantages that RFC 5507 talks about, along with syntactic
validations aimed at preventing some permerror/permfail cases.

From ned+ietf@mauve.mrochek.com  Sat Mar  3 08:01:41 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 93D8321F866D for <ietf@ietfa.amsl.com>; Sat,  3 Mar 2012 08:01:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vtYOqbc0oxKo for <ietf@ietfa.amsl.com>; Sat,  3 Mar 2012 08:01:41 -0800 (PST)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id 7A52B21F8659 for <ietf@ietf.org>; Sat,  3 Mar 2012 08:01:40 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OCO727AQ0G005ZU5@mauve.mrochek.com> for ietf@ietf.org; Sat, 3 Mar 2012 08:01:30 -0800 (PST)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OCI1CWJADS00ZUIL@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Sat, 3 Mar 2012 08:01:25 -0800 (PST)
From: ned+ietf@mauve.mrochek.com
Message-id: <01OCO724C8RI00ZUIL@mauve.mrochek.com>
Date: Sat, 03 Mar 2012 07:56:45 -0800 (PST)
Subject: Re: provisioning software, was DNS RRTYPEs, the difficulty with
In-reply-to: "Your message dated Sat, 03 Mar 2012 12:19:31 +0100" <4F51FE43.5010402@tana.it>
MIME-version: 1.0
Content-type: TEXT/PLAIN
References: <20120228015606.2227.qmail@joyce.lan> <4F4D53E2.5080803@dougbarton.us> <alpine.BSF.2.00.1202281745310.7969@joyce.lan> <4F50939C.4020608@dougbarton.us> <alpine.BSF.2.00.1203020941360.37874@joyce.lan> <20120302224816.E2B111E02C9D@drugs.dv.isc.org> <alpine.BSF.2.00.1203021755270.76484@joyce.lan> <4F51FE43.5010402@tana.it>
To: Alessandro Vesely <vesely@tana.it>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mrochek.com; s=mauve; t=1330790494; i=@mrochek.com; bh=6SB6LxFpcd6ctaGLO0HeAJfZ7tBm8T63ICzVCLuaWyo=;  h=From:Cc:Message-id:Date:Subject:In-reply-to:MIME-version: Content-type:References:To; b=RGG0tBlx+Fd/qT1oMN+msEddFEAJZE4YHjkj6lNIQ08rOl6xiTf7AzU2GNXT/bHp4 opg77VnmndkXVGLHP+uib5GU9sKAsc/7LWoPFEL/6gVyOp+l1wm8huV5RvOWC007pT 4L/yqB+Qje9yPwcpYdEsOGSsDsdWio8Wg+XMmhkk=
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 03 Mar 2012 16:01:41 -0000

> On 03/Mar/12 00:13, John R. Levine wrote:
> >
> >> Until provisoning systems accept UNKNOWN record types they will
> >> always be a bottle neck.  Without that you will have to wait for
> >> the change request to be processed.  Given the history just getting
> >> AAAA records added to most of these system it will be forever.
> >
> > AAAA was unusually painful, since it requires adding a parser for IPv6
> > addresses.  (Having hacked it into my provisioning system, I speak
> > from experience.)  Most new RR types are just strings, numbers, names,
> > and the occasional bit field.

> Yeah, and if ISPs already had troubles with ho-de-ho-de-ho-de-ho, how
> will they join in on skee-bop-de-google-eet-skee-bop-de-goat?

> Given that, designers of new RR types will want to stick to string
> formats just to spare ISPs some parsing, at the cost of losing a half
> of the advantages that RFC 5507 talks about, along with syntactic
> validations aimed at preventing some permerror/permfail cases.

Doubtful. If a record needs to have, say, a priority field, or a port number,
given the existence of MX, SRV, and various other RRs it's going to be very
difficult for the designers of said field to argue that that should be done as
ASCII text that has to be parsed out to use.

More generally, this is trying to have things both ways. We can't
simultaneously assert that deploying simple new RRs is a breeze, making this
unnnecessary, and that it's so difficult that everything should be crammed into
TXT Format no matter the actual structure is.

				NNed

From paf@frobbit.se  Sat Mar  3 08:05:11 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 D352A21F86A0 for <ietf@ietfa.amsl.com>; Sat,  3 Mar 2012 08:05:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[AWL=0.000,  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 uiwDY8aMB2DB for <ietf@ietfa.amsl.com>; Sat,  3 Mar 2012 08:05:11 -0800 (PST)
Received: from srv01.frobbit.se (srv01.frobbit.se [IPv6:2a02:80:3ffe::39]) by ietfa.amsl.com (Postfix) with ESMTP id 201DE21F858E for <ietf@ietf.org>; Sat,  3 Mar 2012 08:05:11 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by srv01.frobbit.se (Postfix) with ESMTP id BD5CE1338055B; Sat,  3 Mar 2012 17:05:08 +0100 (CET)
X-Virus-Scanned: amavisd-new at frobbit.se
Received: from srv01.frobbit.se ([127.0.0.1]) by localhost (srv01.frobbit.se [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lUEtp96jgigh; Sat,  3 Mar 2012 17:05:08 +0100 (CET)
Received: from [IPv6:2a02:80:3ffc::14] (unknown [IPv6:2a02:80:3ffc::14]) (Authenticated sender: paf01) by srv01.frobbit.se (Postfix) with ESMTP id 9653C13380554; Sat,  3 Mar 2012 17:05:08 +0100 (CET)
Subject: Re: provisioning software, was DNS RRTYPEs, the difficulty with
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=us-ascii
From: =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
In-Reply-To: <01OCO724C8RI00ZUIL@mauve.mrochek.com>
Date: Sat, 3 Mar 2012 17:05:08 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <4BFFCC4E-BDF2-40D1-A452-F37DE2A43FD5@frobbit.se>
References: <20120228015606.2227.qmail@joyce.lan> <4F4D53E2.5080803@dougbarton.us> <alpine.BSF.2.00.1202281745310.7969@joyce.lan> <4F50939C.4020608@dougbarton.us> <alpine.BSF.2.00.1203020941360.37874@joyce.lan> <20120302224816.E2B111E02C9D@drugs.dv.isc.org> <alpine.BSF.2.00.1203021755270.76484@joyce.lan> <4F51FE43.5010402@tana.it> <01OCO724C8RI00ZUIL@mauve.mrochek.com>
To: ned+ietf@mauve.mrochek.com
X-Mailer: Apple Mail (2.1257)
Cc: ietf@ietf.org, Alessandro Vesely <vesely@tana.it>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 03 Mar 2012 16:05:11 -0000

On 3 mar 2012, at 16:56, ned+ietf@mauve.mrochek.com wrote:

> Doubtful. If a record needs to have, say, a priority field, or a port =
number,
> given the existence of MX, SRV, and various other RRs it's going to be =
very
> difficult for the designers of said field to argue that that should be =
done as
> ASCII text that has to be parsed out to use.

Agree with you but too many people today "just" program in perl och =
python where the parsing is just a cast or similar, and they do not =
understand this argument of yours -- which I once again completely stand =
behind myself.

   Patrik


From sant9442@gmail.com  Sat Mar  3 08:23:09 2012
Return-Path: <sant9442@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E265B21F8681 for <ietf@ietfa.amsl.com>; Sat,  3 Mar 2012 08:23:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.621
X-Spam-Level: 
X-Spam-Status: No, score=-2.621 tagged_above=-999 required=5 tests=[AWL=-0.314, BAYES_00=-2.599, MISSING_HEADERS=1.292, 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 ha8jieShYEHH for <ietf@ietfa.amsl.com>; Sat,  3 Mar 2012 08:23:09 -0800 (PST)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by ietfa.amsl.com (Postfix) with ESMTP id 3BDE121F85C0 for <ietf@ietf.org>; Sat,  3 Mar 2012 08:23:09 -0800 (PST)
Received: by yenm5 with SMTP id m5so1336492yen.31 for <ietf@ietf.org>; Sat, 03 Mar 2012 08:23:08 -0800 (PST)
Received-SPF: pass (google.com: domain of sant9442@gmail.com designates 10.236.173.195 as permitted sender) client-ip=10.236.173.195; 
Authentication-Results: mr.google.com; spf=pass (google.com: domain of sant9442@gmail.com designates 10.236.173.195 as permitted sender) smtp.mail=sant9442@gmail.com; dkim=pass header.i=sant9442@gmail.com
Received: from mr.google.com ([10.236.173.195]) by 10.236.173.195 with SMTP id v43mr19881869yhl.40.1330791788925 (num_hops = 1); Sat, 03 Mar 2012 08:23:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=iDXhx8v1KqEu3TDpYQO/ym7E4H++TsjksqpwSn3eriI=; b=v68S9PFLb1Ok1umlXKLtzba/rzZMcTiI6fn43PudUHUIBSwlceqI7ljEIx79m5gPUp 80e27Rr6B87+FX1AyLzC8wRzcc3LRMpfdM3A4+3zR4fqQoCYEqTa4VYkF+5k/gnBj1D2 y8z41G0P00v8O/NOStkrmaoHWs1FWfG8vm+IHHMiLUmXk1hBJt9A9LUdrMEhm027Mexi GckYItE5yj/YESd8KZy+N/7dnCsqto4fYgt1qv6IRYDIYYNCv0qDcXDkpBTkX777CdkJ Y14d79KENk949NLYbo82nyi6mhe83mk4FZOtgXrfhRYcIWg9sjPEv/ZdM56YJPgzSzTD Zr0g==
Received: by 10.236.173.195 with SMTP id v43mr15767044yhl.40.1330791788875; Sat, 03 Mar 2012 08:23:08 -0800 (PST)
Received: from adsl-215-50-126.mia.bellsouth.net (99-3-147-93.lightspeed.miamfl.sbcglobal.net. [99.3.147.93]) by mx.google.com with ESMTPS id p41sm23735503yhj.14.2012.03.03.08.23.06 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 03 Mar 2012 08:23:07 -0800 (PST)
Message-ID: <4F524582.2070900@gmail.com>
Date: Sat, 03 Mar 2012 11:23:30 -0500
From: Hector <sant9442@gmail.com>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
CC: ietf@ietf.org
Subject: Re: provisioning software, was DNS RRTYPEs, the difficulty with
References: <20120228015606.2227.qmail@joyce.lan>	<4F4D53E2.5080803@dougbarton.us>	<alpine.BSF.2.00.1202281745310.7969@joyce.lan>	<4F50939C.4020608@dougbarton.us>	<alpine.BSF.2.00.1203020941360.37874@joyce.lan>	<20120302224816.E2B111E02C9D@drugs.dv.isc.org>	<alpine.BSF.2.00.1203021755270.76484@joyce.lan>	<4F51FE43.5010402@tana.it> <01OCO724C8RI00ZUIL@mauve.mrochek.com>
In-Reply-To: <01OCO724C8RI00ZUIL@mauve.mrochek.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, 03 Mar 2012 16:23:10 -0000

ned+ietf@mauve.mrochek.com wrote:

>> Given that, designers of new RR types will want to stick to string
>> formats just to spare ISPs some parsing, at the cost of losing a half
>> of the advantages that RFC 5507 talks about, along with syntactic
>> validations aimed at preventing some permerror/permfail cases.
> 
> Doubtful. If a record needs to have, say, a priority field, or a port number,
> given the existence of MX, SRV, and various other RRs it's going to be very
> difficult for the designers of said field to argue that that should be done as
> ASCII text that has to be parsed out to use.
> 
> More generally, this is trying to have things both ways. We can't
> simultaneously assert that deploying simple new RRs is a breeze, making this
> unnnecessary, and that it's so difficult that everything should be crammed into
> TXT Format no matter the actual structure is.

Whats missing from all this is whether a TXT based protocol 
application can successfully pass all IETF/IESG and DNS community 
reveals, full endorsement and move to Internet Status.  Sounds like 
isn't an issue any more with the aggressive push with protocols like 
DKIM and other TXT only proposed standard protocols.

That was what I was trying to get out of all this.  What is the new 
developer going to think when he invents the next DNS application? 
Which approach does he use for greater endorsement?

--
HLS

From scott@kitterman.com  Sat Mar  3 08:29:13 2012
Return-Path: <scott@kitterman.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 518B521F86C1 for <ietf@ietfa.amsl.com>; Sat,  3 Mar 2012 08:29:13 -0800 (PST)
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.014,  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 l6ll2W32WQBU for <ietf@ietfa.amsl.com>; Sat,  3 Mar 2012 08:29:12 -0800 (PST)
Received: from mailout02.controlledmail.com (mailout02.controlledmail.com [72.81.252.18]) by ietfa.amsl.com (Postfix) with ESMTP id 457CF21F86AD for <ietf@ietf.org>; Sat,  3 Mar 2012 08:29:12 -0800 (PST)
Received: from mailout02.controlledmail.com (localhost [127.0.0.1]) by mailout02.controlledmail.com (Postfix) with ESMTP id 7708020E40DA; Sat,  3 Mar 2012 11:29:11 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=2007-00; t=1330792151; bh=JE8nO3cSlv+GuMMFh3em3SG1pRKCsCNKrPDAwITjlgw=; h=From:To:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version:Content-Transfer-Encoding:Content-Type; b=MYYV3WXVlLo9EgHYbDexIV20sW9vSNMRaMVWnQA0B8XDG+IXwVz1ZYc1qrs0qspDM sheQI5YekM7pBPbC9X+zObNp7YxHxb0yiElmKsCXqCCPqJl5bbWiPBtADjsuR0vVky I2FU0vTyvziNK0QaKGfXJJ70Y7BJJHRCQHqrnjPc=
Received: from scott-latitude-e6320.localnet (static-72-81-252-21.bltmmd.fios.verizon.net [72.81.252.21]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailout02.controlledmail.com (Postfix) with ESMTPSA id 58BDA20E40BB;  Sat,  3 Mar 2012 11:29:11 -0500 (EST)
From: Scott Kitterman <scott@kitterman.com>
To: ietf@ietf.org
Subject: Re: provisioning software, was DNS RRTYPEs, the difficulty with
Date: Sat, 03 Mar 2012 11:29:10 -0500
Message-ID: <28932822.UOiERLMsQ1@scott-latitude-e6320>
User-Agent: KMail/4.7.3 (Linux/3.0.0-16-generic-pae; KDE/4.7.4; i686; ; )
In-Reply-To: <4BFFCC4E-BDF2-40D1-A452-F37DE2A43FD5@frobbit.se>
References: <20120228015606.2227.qmail@joyce.lan> <01OCO724C8RI00ZUIL@mauve.mrochek.com> <4BFFCC4E-BDF2-40D1-A452-F37DE2A43FD5@frobbit.se>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"
X-AV-Checked: ClamAV using ClamSMTP
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 03 Mar 2012 16:29:13 -0000

On Saturday, March 03, 2012 05:05:08 PM Patrik F=E4ltstr=F6m wrote:
> On 3 mar 2012, at 16:56, ned+ietf@mauve.mrochek.com wrote:
> > Doubtful. If a record needs to have, say, a priority field, or a po=
rt
> > number, given the existence of MX, SRV, and various other RRs it's
> > going to be very difficult for the designers of said field to argue=

> > that that should be done as ASCII text that has to be parsed out to=

> > use.
>=20
> Agree with you but too many people today "just" program in perl och p=
ython
> where the parsing is just a cast or similar, and they do not understa=
nd
> this argument of yours -- which I once again completely stand behind
> myself.

There's a design trade off here that one should not over generalize abo=
ut. =20
Sometimes an ASCII text record will be fine, in other cases, it probabl=
y won't. =20
Making the 'easy' case really easy so that new RRTypes get traction is =
a=20
worthwhile goal.  It certainly won't apply to all new RRTypes and so cl=
aims=20
that it's not a universal solution don't mean it's not useful.

Scott K

From sant9442@gmail.com  Sat Mar  3 08:39:20 2012
Return-Path: <sant9442@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6032521F8653 for <ietf@ietfa.amsl.com>; Sat,  3 Mar 2012 08:39:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.606
X-Spam-Level: 
X-Spam-Status: No, score=-2.606 tagged_above=-999 required=5 tests=[AWL=-0.299, BAYES_00=-2.599, MISSING_HEADERS=1.292, 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 gZk9TyK9B-+0 for <ietf@ietfa.amsl.com>; Sat,  3 Mar 2012 08:39:19 -0800 (PST)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id A141121F864F for <ietf@ietf.org>; Sat,  3 Mar 2012 08:39:19 -0800 (PST)
Received: by yhpp34 with SMTP id p34so1347142yhp.31 for <ietf@ietf.org>; Sat, 03 Mar 2012 08:39:19 -0800 (PST)
Received-SPF: pass (google.com: domain of sant9442@gmail.com designates 10.236.116.195 as permitted sender) client-ip=10.236.116.195; 
Authentication-Results: mr.google.com; spf=pass (google.com: domain of sant9442@gmail.com designates 10.236.116.195 as permitted sender) smtp.mail=sant9442@gmail.com; dkim=pass header.i=sant9442@gmail.com
Received: from mr.google.com ([10.236.116.195]) by 10.236.116.195 with SMTP id g43mr19494639yhh.26.1330792759332 (num_hops = 1); Sat, 03 Mar 2012 08:39:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=7wQ9v3n7qU4MNJLULlb4fhX6uibHJvIo1gPRF4twyKQ=; b=Yy4LPw2YoMi666aCLbjV/n5M7APEvIwfvMfxPwTqGO1HY5RF2sP3aqbuc5iYhgQK1G DCv1BMxO5IXjeKTVBxywd/FCvqJ+XhzRoATMfICYmeIOZeagDQarIbCiQ1u2GSeSQYqx ezV3TtUyGHEoKxOTsRW+SAlTTG1HEZTl6WIwX9S2xrT2juFKvI7Auq6i2TYTrXWTNwfO +rV16uBZ4d4bSZnd23Aj3/PMbPdkndX1rChazDPc1m1ygBvYVUQfC2MsQplA9Qy+lCDQ 6p3nW2urAlCV6BFxA4rGFTQsH7NYFF8J1oX+dTduHyRJtZiaPvnPVzEvykbeEifudiTT T2vA==
Received: by 10.236.116.195 with SMTP id g43mr15458637yhh.26.1330792759226; Sat, 03 Mar 2012 08:39:19 -0800 (PST)
Received: from adsl-215-50-126.mia.bellsouth.net (99-3-147-93.lightspeed.miamfl.sbcglobal.net. [99.3.147.93]) by mx.google.com with ESMTPS id n35sm23814163yhh.19.2012.03.03.08.39.17 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 03 Mar 2012 08:39:18 -0800 (PST)
Message-ID: <4F52494D.10005@gmail.com>
Date: Sat, 03 Mar 2012 11:39:41 -0500
From: Hector <sant9442@gmail.com>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
CC: ietf@ietf.org
Subject: Re: provisioning software, was DNS RRTYPEs, the difficulty with
References: <20120228015606.2227.qmail@joyce.lan>	<4F4D53E2.5080803@dougbarton.us>	<alpine.BSF.2.00.1202281745310.7969@joyce.lan>	<4F50939C.4020608@dougbarton.us>	<alpine.BSF.2.00.1203020941360.37874@joyce.lan>	<20120302224816.E2B111E02C9D@drugs.dv.isc.org>	<alpine.BSF.2.00.1203021755270.76484@joyce.lan>	<4F51FE43.5010402@tana.it> <01OCO724C8RI00ZUIL@mauve.mrochek.com> <4BFFCC4E-BDF2-40D1-A452-F37DE2A43FD5@frobbit.se>
In-Reply-To: <4BFFCC4E-BDF2-40D1-A452-F37DE2A43FD5@frobbit.se>
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: Sat, 03 Mar 2012 16:39:20 -0000

� wrote:
> On 3 mar 2012, at 16:56, ned+ietf@mauve.mrochek.com wrote:
> 
>> Doubtful. If a record needs to have, say, a priority field, or a port number,
>> given the existence of MX, SRV, and various other RRs it's going to be very
>> difficult for the designers of said field to argue that that should be done as
>> ASCII text that has to be parsed out to use.
> 
> Agree with you but too many people today "just" program in perl och python 
> where the parsing is just a cast or similar, and they do not understand 
> this argument of yours -- which I once again completely stand behind myself.

The original version of Sender-ID (Caller ID Policy) was an XML 
version of SPF. In fact, the experimental record still exist:

    nslookup -query=txt _ep.hotmail.com

    "<ep xmlns='http://ms.net/1' testing='true'>
     <out><m><indirect>list1._ep.hotmail.com</indirect>
     <indirect>list2._ep.hotmail.com</indirect>
     <indirect>list3._ep.hotmail.com</indirect></m></out></ep>"

It was introductions like this that raised eyebrows and the need to 
include a new RR type with the simpler language SPF TXT fallback for 
SPF and SENDER-ID.

If TXT becomes the acceptable norm, than perhaps the XML format cane 
easily be reconsidered for a DNS TXT storage with a common XML I/O 
construct. :(

--
HLS

From ned+ietf@mauve.mrochek.com  Sat Mar  3 08:42:25 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 C6A1621F869F for <ietf@ietfa.amsl.com>; Sat,  3 Mar 2012 08:42:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level: 
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, 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 U-XNYnTetggX for <ietf@ietfa.amsl.com>; Sat,  3 Mar 2012 08:42:25 -0800 (PST)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id 258F521F8661 for <ietf@ietf.org>; Sat,  3 Mar 2012 08:42:25 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OCO8HUUNNK00KP03@mauve.mrochek.com> for ietf@ietf.org; Sat, 3 Mar 2012 08:42:22 -0800 (PST)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OCI1CWJADS00ZUIL@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Sat, 3 Mar 2012 08:42:18 -0800 (PST)
From: ned+ietf@mauve.mrochek.com
Message-id: <01OCO8HSX2DM00ZUIL@mauve.mrochek.com>
Date: Sat, 03 Mar 2012 08:38:16 -0800 (PST)
Subject: Re: provisioning software, was DNS RRTYPEs, the difficulty with
In-reply-to: "Your message dated Sat, 03 Mar 2012 17:05:08 +0100" <4BFFCC4E-BDF2-40D1-A452-F37DE2A43FD5@frobbit.se>
MIME-version: 1.0
Content-type: TEXT/PLAIN
References: <20120228015606.2227.qmail@joyce.lan> <4F4D53E2.5080803@dougbarton.us> <alpine.BSF.2.00.1202281745310.7969@joyce.lan> <4F50939C.4020608@dougbarton.us> <alpine.BSF.2.00.1203020941360.37874@joyce.lan> <20120302224816.E2B111E02C9D@drugs.dv.isc.org> <alpine.BSF.2.00.1203021755270.76484@joyce.lan> <4F51FE43.5010402@tana.it> <01OCO724C8RI00ZUIL@mauve.mrochek.com> <4BFFCC4E-BDF2-40D1-A452-F37DE2A43FD5@frobbit.se>
To: =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mrochek.com; s=mauve; t=1330792946; i=@mrochek.com; bh=pwT0ipXApEhFd/mOQO8/TadSWdiLtvpwt3rgzfwQo/E=;  h=From:Cc:Message-id:Date:Subject:In-reply-to:MIME-version: Content-type:References:To; b=sJT3/nqDS0NPXMZAldPj03G+ORcPH8+N30LPt5dvLg6585LFqPykX2HXC8w6pTcOj dHtSlHp3xBzoLii3ULVoSQOR6HqQ3gMJMm0kjV8UGHR4yYtiJfPNZ6bIVIyZyh0SYe X1Q468FJHoz6K31CoTMvfGpe78ASc3bFKzuM6jtw=
Cc: ned+ietf@mauve.mrochek.com, ietf@ietf.org, Alessandro Vesely <vesely@tana.it>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 03 Mar 2012 16:42:25 -0000

> On 3 mar 2012, at 16:56, ned+ietf@mauve.mrochek.com wrote:

> > Doubtful. If a record needs to have, say, a priority field, or a port number,
> > given the existence of MX, SRV, and various other RRs it's going to be very
> > difficult for the designers of said field to argue that that should be done as
> > ASCII text that has to be parsed out to use.

> Agree with you but too many people today "just" program in perl och python where the parsing is just a cast or similar, and they do not understand this argument of yours -- which I once again completely stand behind myself.

Regardless of the language you program in, you still have to get your proposal
approved. For that to happen the folks who review these things would in effect
be conceding that there is in fact a major deployment problem out there.

That's the point I was trying to make, not that people wouldn't argue for this
approach.

I am unaware of any counterexamples that have actually made it through the
process, but if they exist feel free to point them out.


				Ned

From johnl@iecc.com  Sat Mar  3 09:43:52 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 4A51B21F8684 for <ietf@ietfa.amsl.com>; Sat,  3 Mar 2012 09:43:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.298
X-Spam-Level: 
X-Spam-Status: No, score=-106.298 tagged_above=-999 required=5 tests=[AWL=-3.699, 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 gQTowIkfjrv7 for <ietf@ietfa.amsl.com>; Sat,  3 Mar 2012 09:43:51 -0800 (PST)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 5A37D21F8681 for <ietf@ietf.org>; Sat,  3 Mar 2012 09:43:50 -0800 (PST)
Received: (qmail 16761 invoked from network); 3 Mar 2012 17:43:48 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 3 Mar 2012 17:43:48 -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=4f525854.xn--yuvv84g.k1203; i=johnl@user.iecc.com; bh=/ZT6LHQJXVvnnhslTPdhSRd724O/NysE7lfS+B1fXQ8=; b=UIduXHYY5PjwD6VEC3m2mi6QpJIpUYl40WZmjlTuG9POHhOQ6cs5q5GwPApXOTPthGNVwWzoWt32v7EHAQkIaN5EP6TPrJT1mKrpIZsoD7mswdQYc/BQeBWm6PGtEfqV+yHCs7gAgXfMzibibxzzEPFi7bFlWyIZrsteGZ9TqXw=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 3 Mar 2012 17:43:26 -0000
Message-ID: <20120303174326.53036.qmail@joyce.lan>
From: "John Levine" <johnl@iecc.com>
To: ietf@ietf.org
Subject: Re: field types, was provisioning software, was DNS RRTYPEs, the difficulty with
In-Reply-To: <4BFFCC4E-BDF2-40D1-A452-F37DE2A43FD5@frobbit.se>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
Cc: paf@frobbit.se
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 03 Mar 2012 17:43:52 -0000

>> Doubtful. If a record needs to have, say, a priority field, or a port number,
>> given the existence of MX, SRV, and various other RRs it's going to be very
>> difficult for the designers of said field to argue that that should be done as
>> ASCII text that has to be parsed out to use.
>
>Agree with you but too many people today "just" program in perl och python where the parsing is just a cast or similar, and they do not
>understand this argument of yours -- which I once again completely stand behind myself.

Honestly, if new RR types were all text to be parsed by clients, a la
SPF and DKIM, that wouldn't be the worst thing in the world.  The main
advantage of a new RR type is that clients can ask for it specifically
and know that any they answer they get is that kind of data, as opposed
to overloaded TXT where you get what you get.

If the DNS records have binary fields, the parsing happens in the DNS
server.  If they're text, the parsing happens in the client.  Back
when the DNS was young, the suggestion that clients would have to
parse the records would have seemed nuts.  Now mail clients parse
multiple SPF and DKIM records on every mail transaction and nobody
cares.  An advantage of parsing in the server is that you catch syntax
records earlier, but that's still no guarantee that the data are
valid.  (For example, see the MX data for international.com, which
caused a mail loop I fixed yesterday.)  An advantage of parsing in the
client is that the parser is in code managed by people who care about
it, rather than managed by some distant DNS operator.

I suppose that unparsed records mean that the server can't add
additional section records, but based on yesterday's discussion, it
sounds like nobody's using them any more, so who cares?




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

From jdrake@juniper.net  Sat Mar  3 10:04:06 2012
Return-Path: <jdrake@juniper.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 285A321F869A for <ietf@ietfa.amsl.com>; Sat,  3 Mar 2012 10:04:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.016
X-Spam-Level: 
X-Spam-Status: No, score=-5.016 tagged_above=-999 required=5 tests=[AWL=1.583,  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 f70f2L-6mvry for <ietf@ietfa.amsl.com>; Sat,  3 Mar 2012 10:04:05 -0800 (PST)
Received: from exprod7og115.obsmtp.com (exprod7og115.obsmtp.com [64.18.2.217]) by ietfa.amsl.com (Postfix) with ESMTP id 3852B21F8698 for <ietf@ietf.org>; Sat,  3 Mar 2012 10:04:02 -0800 (PST)
Received: from P-EMHUB01-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob115.postini.com ([64.18.6.12]) with SMTP ID DSNKT1Jc+kFGsG8KURic/wgk+hgtmO5QuTGN@postini.com; Sat, 03 Mar 2012 10:04:05 PST
Received: from EMBX01-HQ.jnpr.net ([fe80::c821:7c81:f21f:8bc7]) by P-EMHUB01-HQ.jnpr.net ([fe80::fc92:eb1:759:2c72%11]) with mapi; Sat, 3 Mar 2012 09:58:08 -0800
From: John E Drake <jdrake@juniper.net>
To: Russ Housley <housley@vigilsec.com>, "Sprecher, Nurit (NSN - IL/Hod HaSharon)" <nurit.sprecher@nsn.com>
Date: Sat, 3 Mar 2012 09:58:06 -0800
Subject: RE: Last Call:<draft-betts-itu-oam-ach-code-point-03.txt> (Allocation of an Associated Channel Code Point for Use by ITU-T Ethernet basedOAM) to Informational RFC
Thread-Topic: Last Call:<draft-betts-itu-oam-ach-code-point-03.txt> (Allocation of an Associated Channel Code Point for Use by ITU-T Ethernet basedOAM) to Informational RFC
Thread-Index: Acz4BlSZ7Mu/Ctc3SmyvqS2H/99kdABYB6Vw
Message-ID: <5E893DB832F57341992548CDBB333163A55D435980@EMBX01-HQ.jnpr.net>
References: <20120222151252.32262.82157.idtracker@ietfa.amsl.com><03a301ccf174$ff953290$febf97b0$@olddog.co.uk><515703B08A3A064C9CC8C09ACCC710DC0631679E@XMB-RCD-103.cisco.com><C71DA9B1-A61F-4C5D-8DCE-3702271CBB6D@vigilsec.com><4F4FA70B.2030906@pi.nu><D0F60388-D852-4815-917A-B14BF40C64FB@vigilsec.com><BD60EA38ED03AF5A21868DF1@PST.JCK.COM> <4F4FC252.9010001@cisco.com> <444F9B86-84CD-4A21-BD02-067877052A0A@vigilsec.com> <E4873516F3FC7547BCFE792C7D94039C015D125D@DEMUEXC013.nsn-intra.net> <28D09181-4EAF-4770-963F-A57073D77AE7@vigilsec.com>
In-Reply-To: <28D09181-4EAF-4770-963F-A57073D77AE7@vigilsec.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
x-exclaimer-md-config: e4081efb-6d29-443c-8708-750833aec629
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 03 Mar 2012 18:04:06 -0000

Hi,

I agree with the proposal that Russ Housley made, below, but before even pr=
ovisionally granting G.8113.1 a code point by placing draft-betts in the RF=
C editor's queue until G.8113.1 is approved, I would like to understand whe=
ther there is a reasonable chance for it to be approved at WTSA next fall.

Draft-betts was already in the IETF approval process at the time that G.811=
3.1 was disapproved, so I don't see why lack of a code point was given as a=
 reason for its disapproval.

It is my understanding that it is very unusual to send a document to WTSA f=
or approval, so would the authors please indicate the other issues causing =
G.8113.1 to be disapproved and the plan by which the ITU will address these=
 issues?

Thanks,

John=20

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
> Russ Housley
> Sent: Thursday, March 01, 2012 3:52 PM
> To: Sprecher, Nurit (NSN - IL/Hod HaSharon)
> Cc: IETF
> Subject: Re: Last Call:<draft-betts-itu-oam-ach-code-point-03.txt>
> (Allocation of anAssociated Channel Code Point for Use by ITU-T
> Ethernet basedOAM) to Informational RFC
>=20
> Nurit:
>=20
> Some people are using the lack of a code point as the reason that the
> cannot support the ITU-T document.  My approach tells the ITU-T that a
> code point is available to them IFF they are able to reach consensus.
> The removes IETF from the discussion.  This creates a situation where
> G.8113.1 succeeded or fails based on the ITU-T members actions, with no
> finger pointing at the IETF.  This is completely a Layer 9
> consideration, and it has noting to do with the technical content of
> the document.
>=20
> Russ
>=20
>=20
> On Mar 1, 2012, at 2:33 PM, Sprecher, Nurit (NSN - IL/Hod HaSharon)
> wrote:
>=20
> > Russ,
> > I propose to simply re-discuss it when and IFF G.8113.1 is mature and
> > approved...
> > Best regards,
> > Nurit
> >
> >
> > -----Original Message-----
> > From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf
> Of
> > ext Russ Housley
> > Sent: Thursday, March 01, 2012 9:12 PM
> > To: IETF
> > Subject: Re: Last Call:<draft-betts-itu-oam-ach-code-point-03.txt>
> > (Allocation of anAssociated Channel Code Point for Use by ITU-T
> Ethernet
> > basedOAM) to Informational RFC
> >
> >>>> Right now, there is no ITU-T approved document to reference.
> >>>> I am certainly not an expert on ITU-T process, but my
> >>>> understanding is that earliest that we could see an approved
> >>>> G.8113.1 is December 2012.  My point is that we don't want to
> >>>> assign a code point until the ITU-T approves their document.
> >>>> However, if we are willing to assign a code point to G.8113.1
> >>>> once it is approved, then this would be an approach where the
> >>>> code point assignment would block on the approval of the
> >>>> normative reference.
> >>>>
> >>>> I like this approach from the political point of view.  With
> >>>> this approach the IETF tells the ITU-T that if and only if
> >>>> they are able to achieve consensus on G.8113.1, then a code
> >>>> point will be assigned.
> >>> FWIW, this seems entirely appropriate to me.  If we do it this
> >>> way, I think it is important to note --for the benefit of those
> >>> more historically involved with the ITU and others-- that we
> >>> routinely block our own documents on normative references to
> >>> work that is still in progress and, usually, do not do related
> >>> code point allocations until the blocking referenced documents
> >>> are ready.  Once the present I-D is judged to be sufficiently
> >>> ready, this approach would therefore be IETF approval and a
> >>> formal guarantee to the ITU that a code point will be allocated
> >>> if an when G.8113.1 is approved and published, but not
> >>> assignment of that code point until the referenced base document
> >>> is finished.
> >>>
> >>> Completely normal procedurally.
> >>>
> >> To be clear John our normal requirement would be that the
> >> technical community achieved consensus that the base document
> >> was ready. I have never seen ITU-T consensus on the contents
> >> of G.8113.1 at any meeting that I have observed. What in your
> >> view is the criteria for determining that  G.8113.1 has achieved
> >> consensus?
> >
> >
> > This is not an IETF problem, and I do not think that the IETF ought
> to
> > be discussing the internal workings of the ITU-T process.  The point
> is
> > to come up with a mechanism that allows the code point to be assigned
> if
> > and only if the ITU-T does come to a consensus by whatever means is
> > allowed by their own process.
> >
> > Russ
> > _______________________________________________
> > Ietf mailing list
> > Ietf@ietf.org
> > https://www.ietf.org/mailman/listinfo/ietf
>=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf

From housley@vigilsec.com  Sat Mar  3 10:11:29 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 6A04821F85A7 for <ietf@ietfa.amsl.com>; Sat,  3 Mar 2012 10:11:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.547
X-Spam-Level: 
X-Spam-Status: No, score=-102.547 tagged_above=-999 required=5 tests=[AWL=0.052, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i-CsowKlT0kH for <ietf@ietfa.amsl.com>; Sat,  3 Mar 2012 10:11:28 -0800 (PST)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id 9136421F84E0 for <ietf@ietf.org>; Sat,  3 Mar 2012 10:11:28 -0800 (PST)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 4DDC6F24025; Sat,  3 Mar 2012 13:11:28 -0500 (EST)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([208.254.26.82]) by localhost (ronin.smetech.net [208.254.26.81]) (amavisd-new, port 10024) with ESMTP id PSX2ZVlZhkC0; Sat,  3 Mar 2012 13:11:27 -0500 (EST)
Received: from [192.168.2.104] (pool-96-241-165-215.washdc.fios.verizon.net [96.241.165.215]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 5094AF24013; Sat,  3 Mar 2012 13:11:27 -0500 (EST)
Subject: Re: Last Call:<draft-betts-itu-oam-ach-code-point-03.txt> (Allocation of an Associated Channel Code Point for Use by ITU-T Ethernet basedOAM) to Informational RFC
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <5E893DB832F57341992548CDBB333163A55D435980@EMBX01-HQ.jnpr.net>
Date: Sat, 3 Mar 2012 13:11:26 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <E56CC29B-7FBD-40D6-B331-F7787A49B66E@vigilsec.com>
References: <20120222151252.32262.82157.idtracker@ietfa.amsl.com><03a301ccf174$ff953290$febf97b0$@olddog.co.uk><515703B08A3A064C9CC8C09ACCC710DC0631679E@XMB-RCD-103.cisco.com><C71DA9B1-A61F-4C5D-8DCE-3702271CBB6D@vigilsec.com><4F4FA70B.2030906@pi.nu><D0F60388-D852-4815-917A-B14BF40C64FB@vigilsec.com><BD60EA38ED03AF5A21868DF1@PST.JCK.COM> <4F4FC252.9010001@cisco.com> <444F9B86-84CD-4A21-BD02-067877052A0A@vigilsec.com> <E4873516F3FC7547BCFE792C7D94039C015D125D@DEMUEXC013.nsn-intra.net> <28D09181-4EAF-4770-963F-A57073D77AE7@vigilsec.com> <5E893DB832F57341992548CDBB333163A55D435980@EMBX01-HQ.jnpr.net>
To: John E Drake <jdrake@juniper.net>
X-Mailer: Apple Mail (2.1084)
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 03 Mar 2012 18:11:29 -0000

John:

If G.8113.1 never gets approved, then draft-betts- will sit in the RFC =
Editor queue until someone acknowledges this situation.

I do not want anyone to use the IETF as a reason for or against =
achieving consensus in the ITU-T.  Such consensus is left completely to =
ITU-T member states and sector members.

Russ


On Mar 3, 2012, at 12:58 PM, John E Drake wrote:

> Hi,
>=20
> I agree with the proposal that Russ Housley made, below, but before =
even provisionally granting G.8113.1 a code point by placing draft-betts =
in the RFC editor's queue until G.8113.1 is approved, I would like to =
understand whether there is a reasonable chance for it to be approved at =
WTSA next fall.
>=20
> Draft-betts was already in the IETF approval process at the time that =
G.8113.1 was disapproved, so I don't see why lack of a code point was =
given as a reason for its disapproval.
>=20
> It is my understanding that it is very unusual to send a document to =
WTSA for approval, so would the authors please indicate the other issues =
causing G.8113.1 to be disapproved and the plan by which the ITU will =
address these issues?
>=20
> Thanks,
>=20
> John=20
>=20
>> -----Original Message-----
>> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf =
Of
>> Russ Housley
>> Sent: Thursday, March 01, 2012 3:52 PM
>> To: Sprecher, Nurit (NSN - IL/Hod HaSharon)
>> Cc: IETF
>> Subject: Re: Last Call:<draft-betts-itu-oam-ach-code-point-03.txt>
>> (Allocation of anAssociated Channel Code Point for Use by ITU-T
>> Ethernet basedOAM) to Informational RFC
>>=20
>> Nurit:
>>=20
>> Some people are using the lack of a code point as the reason that the
>> cannot support the ITU-T document.  My approach tells the ITU-T that =
a
>> code point is available to them IFF they are able to reach consensus.
>> The removes IETF from the discussion.  This creates a situation where
>> G.8113.1 succeeded or fails based on the ITU-T members actions, with =
no
>> finger pointing at the IETF.  This is completely a Layer 9
>> consideration, and it has noting to do with the technical content of
>> the document.
>>=20
>> Russ
>>=20
>>=20
>> On Mar 1, 2012, at 2:33 PM, Sprecher, Nurit (NSN - IL/Hod HaSharon)
>> wrote:
>>=20
>>> Russ,
>>> I propose to simply re-discuss it when and IFF G.8113.1 is mature =
and
>>> approved...
>>> Best regards,
>>> Nurit
>>>=20
>>>=20
>>> -----Original Message-----
>>> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf
>> Of
>>> ext Russ Housley
>>> Sent: Thursday, March 01, 2012 9:12 PM
>>> To: IETF
>>> Subject: Re: Last Call:<draft-betts-itu-oam-ach-code-point-03.txt>
>>> (Allocation of anAssociated Channel Code Point for Use by ITU-T
>> Ethernet
>>> basedOAM) to Informational RFC
>>>=20
>>>>>> Right now, there is no ITU-T approved document to reference.
>>>>>> I am certainly not an expert on ITU-T process, but my
>>>>>> understanding is that earliest that we could see an approved
>>>>>> G.8113.1 is December 2012.  My point is that we don't want to
>>>>>> assign a code point until the ITU-T approves their document.
>>>>>> However, if we are willing to assign a code point to G.8113.1
>>>>>> once it is approved, then this would be an approach where the
>>>>>> code point assignment would block on the approval of the
>>>>>> normative reference.
>>>>>>=20
>>>>>> I like this approach from the political point of view.  With
>>>>>> this approach the IETF tells the ITU-T that if and only if
>>>>>> they are able to achieve consensus on G.8113.1, then a code
>>>>>> point will be assigned.
>>>>> FWIW, this seems entirely appropriate to me.  If we do it this
>>>>> way, I think it is important to note --for the benefit of those
>>>>> more historically involved with the ITU and others-- that we
>>>>> routinely block our own documents on normative references to
>>>>> work that is still in progress and, usually, do not do related
>>>>> code point allocations until the blocking referenced documents
>>>>> are ready.  Once the present I-D is judged to be sufficiently
>>>>> ready, this approach would therefore be IETF approval and a
>>>>> formal guarantee to the ITU that a code point will be allocated
>>>>> if an when G.8113.1 is approved and published, but not
>>>>> assignment of that code point until the referenced base document
>>>>> is finished.
>>>>>=20
>>>>> Completely normal procedurally.
>>>>>=20
>>>> To be clear John our normal requirement would be that the
>>>> technical community achieved consensus that the base document
>>>> was ready. I have never seen ITU-T consensus on the contents
>>>> of G.8113.1 at any meeting that I have observed. What in your
>>>> view is the criteria for determining that  G.8113.1 has achieved
>>>> consensus?
>>>=20
>>>=20
>>> This is not an IETF problem, and I do not think that the IETF ought
>> to
>>> be discussing the internal workings of the ITU-T process.  The point
>> is
>>> to come up with a mechanism that allows the code point to be =
assigned
>> if
>>> and only if the ITU-T does come to a consensus by whatever means is
>>> allowed by their own process.
>>>=20
>>> Russ
>>> _______________________________________________
>>> Ietf mailing list
>>> Ietf@ietf.org
>>> https://www.ietf.org/mailman/listinfo/ietf
>>=20
>> _______________________________________________
>> Ietf mailing list
>> Ietf@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf


From sant9442@gmail.com  Sat Mar  3 10:22:09 2012
Return-Path: <sant9442@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2567821F86A2 for <ietf@ietfa.amsl.com>; Sat,  3 Mar 2012 10:22:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.593
X-Spam-Level: 
X-Spam-Status: No, score=-2.593 tagged_above=-999 required=5 tests=[AWL=-0.286, BAYES_00=-2.599, MISSING_HEADERS=1.292, 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 N4Sv6OxWsuOQ for <ietf@ietfa.amsl.com>; Sat,  3 Mar 2012 10:22:08 -0800 (PST)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id 9013321F85F6 for <ietf@ietf.org>; Sat,  3 Mar 2012 10:22:08 -0800 (PST)
Received: by ggmi1 with SMTP id i1so1366609ggm.31 for <ietf@ietf.org>; Sat, 03 Mar 2012 10:22:08 -0800 (PST)
Received-SPF: pass (google.com: domain of sant9442@gmail.com designates 10.236.173.132 as permitted sender) client-ip=10.236.173.132; 
Authentication-Results: mr.google.com; spf=pass (google.com: domain of sant9442@gmail.com designates 10.236.173.132 as permitted sender) smtp.mail=sant9442@gmail.com; dkim=pass header.i=sant9442@gmail.com
Received: from mr.google.com ([10.236.173.132]) by 10.236.173.132 with SMTP id v4mr19606602yhl.78.1330798928175 (num_hops = 1); Sat, 03 Mar 2012 10:22:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=bWn0oLsBIfBVOKgmi3rcPS1gm/F5QV7j3x6D3v5qb6M=; b=ktGqDEqH4pC0PHG7KdLRPAni3/wj0MPhhfIhjOxpMJswRXGYm31ArfenutkY9QPj7P VIjw7g/ofEAnltMUT+zvZRwe34AlTpYu9iDzM6o0rHj+hDYmavFTApaFz8y+1FUfFrUv dVGELLeIb87gdz8gXUe4sWPv/qWA3X0er+bESnyPWzlfWcOlwYlLeaBowVpSH41bjmrf ShLQkp5b3xVemz01sq1+lenCEXiiXOPI0RMjc9oZ1oXQhGjM0q7ivnbajIUve9jRQZ5P kj1bVkU6q4L+tIPtqMUNuQagAtUro2ju5V6xWEaLtgAaXZ1RlxbhEYrrzkHTOOLTpcBH ieFA==
Received: by 10.236.173.132 with SMTP id v4mr15542435yhl.78.1330798928135; Sat, 03 Mar 2012 10:22:08 -0800 (PST)
Received: from adsl-215-50-126.mia.bellsouth.net (99-3-147-93.lightspeed.miamfl.sbcglobal.net. [99.3.147.93]) by mx.google.com with ESMTPS id b6sm15478291anc.3.2012.03.03.10.22.06 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 03 Mar 2012 10:22:07 -0800 (PST)
Message-ID: <4F526132.9050009@gmail.com>
Date: Sat, 03 Mar 2012 13:21:38 -0500
From: Hector <sant9442@gmail.com>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
CC: ietf@ietf.org
Subject: Re: field types, was provisioning software, was DNS RRTYPEs,	the difficulty with
References: <20120303174326.53036.qmail@joyce.lan>
In-Reply-To: <20120303174326.53036.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: Sat, 03 Mar 2012 18:22:09 -0000

John Levine wrote:

> Now mail clients parse
> multiple SPF and DKIM records on every mail transaction and nobody
> cares.  

Well....., its not like anyone really had a choice.

SPF is still maturing with its RR type, DKIM didn't bother, and now 
also have VBR, ADSP and now ATPS and then DMARC (all by the same group 
of people), where for the total coverage aware integrator is a major 
overhead, 4-5 calls with a very low yield.  I care about it. Its ugly. 
But no choice.

> I suppose that unparsed records mean that the server can't add
> additional section records, but based on yesterday's discussion, it
> sounds like nobody's using them any more, so who cares?

Do you think a TXT only based DNS application can today pass the 
IETF/IESG DNS community endorsement to IS?

I think another part of the problem is that many of these TXT bases 
protocols currently on the radar are all related in some form or 
fashion.  A solution to merge all or just some where applicable, to 
reduce multiple calls and redundancy, can help alleviate some of the 
concerns.


From ned+ietf@mauve.mrochek.com  Sat Mar  3 10:23:34 2012
Return-Path: <ned+ietf@mauve.mrochek.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B940421F86E2 for <ietf@ietfa.amsl.com>; Sat,  3 Mar 2012 10:23:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.587
X-Spam-Level: 
X-Spam-Status: No, score=-2.587 tagged_above=-999 required=5 tests=[AWL=0.012,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6x2xl-6-WLjj for <ietf@ietfa.amsl.com>; Sat,  3 Mar 2012 10:23:33 -0800 (PST)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id CE41121F859B for <ietf@ietf.org>; Sat,  3 Mar 2012 10:23:33 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OCOC19ZM1C01782W@mauve.mrochek.com> for ietf@ietf.org; Sat, 3 Mar 2012 10:23:32 -0800 (PST)
MIME-version: 1.0
Content-type: text/plain; charset=utf-8
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OCI1CWJADS00ZUIL@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Sat, 3 Mar 2012 10:23:28 -0800 (PST)
From: ned+ietf@mauve.mrochek.com
Message-id: <01OCOC18E6PI00ZUIL@mauve.mrochek.com>
Date: Sat, 03 Mar 2012 10:07:37 -0800 (PST)
Subject: Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to	Proposed Standard
In-reply-to: "Your message dated Sat, 03 Mar 2012 04:11:53 +0000" <20120303041153.23749.qmail@joyce.lan>
References: <CAC4RtVA3F8gsBWY65W5KNDE+408EvtP+hp5GTzLg4FMgC1bdcQ@mail.gmail.com> <20120303041153.23749.qmail@joyce.lan>
To: John Levine <johnl@iecc.com>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mrochek.com; s=mauve; t=1330799016; i=@mrochek.com; bh=kjmsrE2avN6T5AxNfKQpF7aqIoReUitqfsMLdiMYnYI=;  h=MIME-version:Content-type:From:Cc:Message-id:Date:Subject: In-reply-to:References:To; b=Mw561J5ZKMQawt6oFiy25sIVKp7RySwvXXzBjaFUkQMXammWopWnJSKO345TNAhMx WQkvtm6GR2ev9HjFdv3A71iESFv4WwPJvvOpFoXFgA72MnKJ+DCP4ZnLhEd9CDEviF NivcFjUk4eKj3iApwG3UvIDy9jPcz37dVKOegZqk=
Cc: 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: Sat, 03 Mar 2012 18:23:34 -0000

> >> This draft also defines the MT-Priority header field.  It is quite unusual
> >> for a SMTP extension specification to define a mail header field. ...

> >This is my major concern about this protocol as well, as I note in the
> >PROTO writeup (which, unfortunately, can't be seen publicly because of
> >a limitation in the datatracker; perhaps I should post it here).  I'm
> >interested in hearing whether others share this concern, and what the
> >community consensus is about it.

> I have no problem logging stuff from the SMTP session into a message
> header, we've been doing that since forever.  But I have a lot of
> problem turning a header back into SMTP for a subsequent relay, for
> two reasons.

> One is just that it's ugly.  There were good reasons to separate the
> envelope from the body back in the 1970s, and I think those reasons
> are just as good now.  Over in the EAI group, there was a valiant
> effort to tunnel EAI messages through non-EAI SMTP servers via
> downgrades, and we eventually gave up.  Now, if you want to send an
> EAI message, there has to be an EAI path all the way from the sender
> to the recipient.  This isn't exactly analogous, but it's instructive.

> The other reason is that I think it's too ill-specified to
> interoperate.  The theory seems to be that the relay server notices an
> MT-Priority: header, and (vigorous waving of hands) somehow decides if
> the message has sufficient virtue to promote the header back into the
> SMTP session.  The hand-waving is not persuasive; the suggestion of
> S/MIME, which obviously won't work, is not encouraging.

Both good points. While I personally am indifferent to header modification
being an issue - I believe we've long since crossed that bridge - I will also
note that simply changing this proposal to always insert the MT-Priority: field
at submission time and leave it unchanged throughout message transit would
leave most of the functionality intact and eliminate the header modification
issue entirely.

But the upleveling of header to envelope would remain. John is quite correct in
his assertion that these are mostly uncharted waters: The only remotely
comparable case I can think of is the mapping of some X.400 fields to the
NOTARY extension, but in that case the mapping was from X.400 envelope material
to SMTP envelope material. Additionally, the mapping was precisly specified
with no wiggle room for "site policy". 

I think this will likely lead to interoperability problems. Now, in the case
of message processing priority the chance of such problems causing significant
trouble seem pretty slim, but "it doesn't work well but it also doesn't
matter much" is not a justification I feel comfortable embracing.

> If you want to brave the ugliness and standardize this, the spec needs
> to explain how the server decides whether to believe an MT-Priority
> header.  If it doesn't, it's too vague to interoperate.

> So I have two suggestions.  One is to leave it as is, and make it
> experimental. If it turns out the tunnels all work the same way, you
> can come back and add the spec about how they work and rev it as
> standards track.  The other is to take out the tunnel bit and make it
> standards track now, so a compliant implementation needs
> priority-aware MTAs from end to end.  Even if you take out the tunnel
> stuff in the spec, you can still tunnel in your implementations, using
> whatever non-standard ad hoc kludges you want.  Since the current spec
> has gaps that would need to be filled by non-standard ad hoc kludges
> anyway, you haven't lost anything.

I have to say I strongly prefer the latter, especially if it also includes
eliminating the prohibition on using other sources of priority information to
set the envelope priority level on submission. In fact given that prohibition
I see little point in implementing this, at least not in a fashion
that conforms to the specification.

				Ned

From nurit.sprecher@nsn.com  Sat Mar  3 10:50:26 2012
Return-Path: <nurit.sprecher@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 A425621F86B5 for <ietf@ietfa.amsl.com>; Sat,  3 Mar 2012 10:50:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.547
X-Spam-Level: 
X-Spam-Status: No, score=-6.547 tagged_above=-999 required=5 tests=[AWL=0.052,  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 5PVerUOssPsv for <ietf@ietfa.amsl.com>; Sat,  3 Mar 2012 10:50:25 -0800 (PST)
Received: from demumfd001.nsn-inter.net (demumfd001.nsn-inter.net [93.183.12.32]) by ietfa.amsl.com (Postfix) with ESMTP id 308E621F8687 for <ietf@ietf.org>; Sat,  3 Mar 2012 10:50:25 -0800 (PST)
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 q23IoLGt022178 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sat, 3 Mar 2012 19:50:21 +0100
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 q23IoJha004078; Sat, 3 Mar 2012 19:50:19 +0100
Received: from DEMUEXC013.nsn-intra.net ([10.150.128.24]) by DEMUEXC048.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.4675);  Sat, 3 Mar 2012 19:50:19 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Last Call:<draft-betts-itu-oam-ach-code-point-03.txt> (Allocationof an Associated Channel Code Point for Use by ITU-T EthernetbasedOAM) to Informational RFC
Date: Sat, 3 Mar 2012 19:50:16 +0100
Message-ID: <E4873516F3FC7547BCFE792C7D94039C015D17EC@DEMUEXC013.nsn-intra.net>
In-Reply-To: <E56CC29B-7FBD-40D6-B331-F7787A49B66E@vigilsec.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Last Call:<draft-betts-itu-oam-ach-code-point-03.txt> (Allocationof an Associated Channel Code Point for Use by ITU-T EthernetbasedOAM) to Informational RFC
Thread-Index: Acz5aRmMVP+n8xITRtyguI7LCfCGCgAAZlrw
References: <20120222151252.32262.82157.idtracker@ietfa.amsl.com><03a301ccf174$ff953290$febf97b0$@olddog.co.uk><515703B08A3A064C9CC8C09ACCC710DC0631679E@XMB-RCD-103.cisco.com><C71DA9B1-A61F-4C5D-8DCE-3702271CBB6D@vigilsec.com><4F4FA70B.2030906@pi.nu><D0F60388-D852-4815-917A-B14BF40C64FB@vigilsec.com><BD60EA38ED03AF5A21868DF1@PST.JCK.COM><4F4FC252.9010001@cisco.com><444F9B86-84CD-4A21-BD02-067877052A0A@vigilsec.com><E4873516F3FC7547BCFE792C7D94039C015D125D@DEMUEXC013.nsn-intra.net><28D09181-4EAF-4770-963F-A57073D77AE7@vigilsec.com><5E893DB832F57341992548CDBB333163A55D435980@EMBX01-HQ.jnpr.net> <E56CC29B-7FBD-40D6-B331-F7787A49B66E@vigilsec.com>
From: "Sprecher, Nurit (NSN - IL/Hod HaSharon)" <nurit.sprecher@nsn.com>
To: "ext Russ Housley" <housley@vigilsec.com>, "John E Drake" <jdrake@juniper.net>
X-OriginalArrivalTime: 03 Mar 2012 18:50:19.0026 (UTC) FILETIME=[7AE21F20:01CCF96E]
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: 6872
X-purgate-ID: 151667::1330800621-000044A2-4A713356/0-0/0-0
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 03 Mar 2012 18:50:26 -0000

Russ hi,
I think many concerns were raised on draft-betts itself, so I think we
should first look at these comments....
Concerning G.8113.1, as mentioned before as it was disapproved, it is
clear that there was no consensus. It will be good to understand what
are the issues...the code point was not the main issue, as indicated by
John.
Best regards,
Nurit
=20
P.S. Concerning the chances of the document to be approved in WTSA,
please note that I do not think the members of WTSA have the technical
expertise to discuss the technical aspects of the document, and I
believe they would like to encourage SG15 to stick with the ITU's
culture of negotiation and consensus-building and have technical
standards developed by the industry members based on consensus. The
logical step would be to send the document back to SG15 to resolve the
issues and get consensus.=20


-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
ext Russ Housley
Sent: Saturday, March 03, 2012 8:11 PM
To: John E Drake
Cc: IETF
Subject: Re: Last Call:<draft-betts-itu-oam-ach-code-point-03.txt>
(Allocationof an Associated Channel Code Point for Use by ITU-T
EthernetbasedOAM) to Informational RFC

John:

If G.8113.1 never gets approved, then draft-betts- will sit in the RFC
Editor queue until someone acknowledges this situation.

I do not want anyone to use the IETF as a reason for or against
achieving consensus in the ITU-T.  Such consensus is left completely to
ITU-T member states and sector members.

Russ


On Mar 3, 2012, at 12:58 PM, John E Drake wrote:

> Hi,
>=20
> I agree with the proposal that Russ Housley made, below, but before
even provisionally granting G.8113.1 a code point by placing draft-betts
in the RFC editor's queue until G.8113.1 is approved, I would like to
understand whether there is a reasonable chance for it to be approved at
WTSA next fall.
>=20
> Draft-betts was already in the IETF approval process at the time that
G.8113.1 was disapproved, so I don't see why lack of a code point was
given as a reason for its disapproval.
>=20
> It is my understanding that it is very unusual to send a document to
WTSA for approval, so would the authors please indicate the other issues
causing G.8113.1 to be disapproved and the plan by which the ITU will
address these issues?
>=20
> Thanks,
>=20
> John=20
>=20
>> -----Original Message-----
>> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf
Of
>> Russ Housley
>> Sent: Thursday, March 01, 2012 3:52 PM
>> To: Sprecher, Nurit (NSN - IL/Hod HaSharon)
>> Cc: IETF
>> Subject: Re: Last Call:<draft-betts-itu-oam-ach-code-point-03.txt>
>> (Allocation of anAssociated Channel Code Point for Use by ITU-T
>> Ethernet basedOAM) to Informational RFC
>>=20
>> Nurit:
>>=20
>> Some people are using the lack of a code point as the reason that the
>> cannot support the ITU-T document.  My approach tells the ITU-T that
a
>> code point is available to them IFF they are able to reach consensus.
>> The removes IETF from the discussion.  This creates a situation where
>> G.8113.1 succeeded or fails based on the ITU-T members actions, with
no
>> finger pointing at the IETF.  This is completely a Layer 9
>> consideration, and it has noting to do with the technical content of
>> the document.
>>=20
>> Russ
>>=20
>>=20
>> On Mar 1, 2012, at 2:33 PM, Sprecher, Nurit (NSN - IL/Hod HaSharon)
>> wrote:
>>=20
>>> Russ,
>>> I propose to simply re-discuss it when and IFF G.8113.1 is mature
and
>>> approved...
>>> Best regards,
>>> Nurit
>>>=20
>>>=20
>>> -----Original Message-----
>>> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf
>> Of
>>> ext Russ Housley
>>> Sent: Thursday, March 01, 2012 9:12 PM
>>> To: IETF
>>> Subject: Re: Last Call:<draft-betts-itu-oam-ach-code-point-03.txt>
>>> (Allocation of anAssociated Channel Code Point for Use by ITU-T
>> Ethernet
>>> basedOAM) to Informational RFC
>>>=20
>>>>>> Right now, there is no ITU-T approved document to reference.
>>>>>> I am certainly not an expert on ITU-T process, but my
>>>>>> understanding is that earliest that we could see an approved
>>>>>> G.8113.1 is December 2012.  My point is that we don't want to
>>>>>> assign a code point until the ITU-T approves their document.
>>>>>> However, if we are willing to assign a code point to G.8113.1
>>>>>> once it is approved, then this would be an approach where the
>>>>>> code point assignment would block on the approval of the
>>>>>> normative reference.
>>>>>>=20
>>>>>> I like this approach from the political point of view.  With
>>>>>> this approach the IETF tells the ITU-T that if and only if
>>>>>> they are able to achieve consensus on G.8113.1, then a code
>>>>>> point will be assigned.
>>>>> FWIW, this seems entirely appropriate to me.  If we do it this
>>>>> way, I think it is important to note --for the benefit of those
>>>>> more historically involved with the ITU and others-- that we
>>>>> routinely block our own documents on normative references to
>>>>> work that is still in progress and, usually, do not do related
>>>>> code point allocations until the blocking referenced documents
>>>>> are ready.  Once the present I-D is judged to be sufficiently
>>>>> ready, this approach would therefore be IETF approval and a
>>>>> formal guarantee to the ITU that a code point will be allocated
>>>>> if an when G.8113.1 is approved and published, but not
>>>>> assignment of that code point until the referenced base document
>>>>> is finished.
>>>>>=20
>>>>> Completely normal procedurally.
>>>>>=20
>>>> To be clear John our normal requirement would be that the
>>>> technical community achieved consensus that the base document
>>>> was ready. I have never seen ITU-T consensus on the contents
>>>> of G.8113.1 at any meeting that I have observed. What in your
>>>> view is the criteria for determining that  G.8113.1 has achieved
>>>> consensus?
>>>=20
>>>=20
>>> This is not an IETF problem, and I do not think that the IETF ought
>> to
>>> be discussing the internal workings of the ITU-T process.  The point
>> is
>>> to come up with a mechanism that allows the code point to be
assigned
>> if
>>> and only if the ITU-T does come to a consensus by whatever means is
>>> allowed by their own process.
>>>=20
>>> Russ
>>> _______________________________________________
>>> Ietf mailing list
>>> Ietf@ietf.org
>>> https://www.ietf.org/mailman/listinfo/ietf
>>=20
>> _______________________________________________
>> Ietf mailing list
>> Ietf@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf

From vesely@tana.it  Sun Mar  4 04:47:04 2012
Return-Path: <vesely@tana.it>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 29A8221F85CD for <ietf@ietfa.amsl.com>; Sun,  4 Mar 2012 04:47:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.649
X-Spam-Level: 
X-Spam-Status: No, score=-4.649 tagged_above=-999 required=5 tests=[AWL=0.070,  BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hZ7xT5ix-Zk6 for <ietf@ietfa.amsl.com>; Sun,  4 Mar 2012 04:47:03 -0800 (PST)
Received: from wmail.tana.it (mail.tana.it [62.94.243.226]) by ietfa.amsl.com (Postfix) with ESMTP id 438FE21F85B7 for <ietf@ietf.org>; Sun,  4 Mar 2012 04:47:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=test; t=1330865219; bh=WskZWmS49Hnaqsz4c3feEwN2AX4KvKUheoW8m+zJNiw=; l=2062; h=Message-ID:Date:From:MIME-Version:To:References:In-Reply-To: Content-Transfer-Encoding; b=iQTmEwwrES29dV/yCsp9grzBOzGx0ZujdK8f2vutI1UX3s8Cgixb1D0rjLD+li2cU 1XgVcAMe/lZeumdHSImieAeBpo6MvMmvn5+HFxcRK2x2HjOKXaf+UIB4WlyEgIPavA 0wJlVyxzb3fC2a2bJHqPMbLkUHXmLLa5TAU/BW3o=
Received: from [172.25.197.158] (pcale.tana [172.25.197.158]) (AUTH: CRAM-MD5 515, TLS: TLS1.0,256bits,RSA_AES_256_CBC_SHA1) by wmail.tana.it with ESMTPSA; Sun, 04 Mar 2012 13:46:59 +0100 id 00000000005DC039.000000004F536443.00001C36
Message-ID: <4F536443.9040708@tana.it>
Date: Sun, 04 Mar 2012 13:46:59 +0100
From: Alessandro Vesely <vesely@tana.it>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: field types, was provisioning software, was DNS RRTYPEs, the difficulty with
References: <20120303174326.53036.qmail@joyce.lan>
In-Reply-To: <20120303174326.53036.qmail@joyce.lan>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 04 Mar 2012 12:47:04 -0000

On 03/Mar/12 18:43, John Levine wrote:
> 
> Honestly, if new RR types were all text to be parsed by clients, a la
> SPF and DKIM, that wouldn't be the worst thing in the world.

Well, since that's what is currently being done, it must obviously be
feasible.  However, there is no reason to stick to it if a better
choice is available.

> The main advantage of a new RR type is that clients can ask for it
> specifically and know that any they answer they get is that kind of
> data, as opposed to overloaded TXT where you get what you get.

Yes, possibly better than using _prefixes.

> An advantage of parsing in the server is that you catch syntax 
> records earlier, but that's still no guarantee that the data are 
> valid.

Allowing a binary form is also an advantage, although I agree that the
hype on performance is a relic.

> An advantage of parsing in the client is that the parser is in code
> managed by people who care about it, rather than managed by some
> distant DNS operator.

I see a tendency to stick to good parsing models, both by referencing
their specs in newer specs and by reusing library function.  Except
for possible bugs, whose patches could be promptly broadcasted as
security fixes, we gathered enough experience with those formats that
I think we're likely to get a generic spec right on the first attempt.

Public keys, IP addresses, flags, are all candidates for binary field
formats.  The binary version of "tag=value" could look much like DER,
except that tag enumerations could be drawn from the relevant protocol
registry.  I guess there's plenty of possibilities better than XML.

> I suppose that unparsed records mean that the server can't add
> additional section records, but based on yesterday's discussion, it
> sounds like nobody's using them any more, so who cares?

You mean that a response to a query for, say, DKIM could come with a
few byte worth of ADSP added as a bonus, if it fits within the
response size?  This feature is also missing from
draft-levine-dnsextlang-02.

From d3e3e3@gmail.com  Sun Mar  4 20:33:40 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 88EB721F86D8 for <ietf@ietfa.amsl.com>; Sun,  4 Mar 2012 20:33:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.394
X-Spam-Level: 
X-Spam-Status: No, score=-104.394 tagged_above=-999 required=5 tests=[AWL=-0.795, 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 UZsPmZbXToYd for <ietf@ietfa.amsl.com>; Sun,  4 Mar 2012 20:33:39 -0800 (PST)
Received: from mail-lpp01m010-f44.google.com (mail-lpp01m010-f44.google.com [209.85.215.44]) by ietfa.amsl.com (Postfix) with ESMTP id 5CD9921F86D5 for <ietf@ietf.org>; Sun,  4 Mar 2012 20:33:39 -0800 (PST)
Received: by lagj5 with SMTP id j5so5104787lag.31 for <ietf@ietf.org>; Sun, 04 Mar 2012 20:33:38 -0800 (PST)
Received-SPF: pass (google.com: domain of d3e3e3@gmail.com designates 10.112.48.74 as permitted sender) client-ip=10.112.48.74; 
Authentication-Results: mr.google.com; spf=pass (google.com: domain of d3e3e3@gmail.com designates 10.112.48.74 as permitted sender) smtp.mail=d3e3e3@gmail.com; dkim=pass header.i=d3e3e3@gmail.com
Received: from mr.google.com ([10.112.48.74]) by 10.112.48.74 with SMTP id j10mr8462247lbn.106.1330922018428 (num_hops = 1); Sun, 04 Mar 2012 20:33:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type:content-transfer-encoding; bh=EMX47OxhhQIkMM5ZYsJAEQjO0ftaCe8X7nZNjheEdjw=; b=EAs3AySr3Uqu/bjdTtWOlH5ZC7DvpTRDpamQOMXvIKnHc8c68Txiv8nOqdeNdtk0GH l7T7jiCjOnbkGSWNaOHc7NRKpspkGjfZOyu6AP4Hea0YH6ryJrq1zcs1Sq4WWX6GLOoP v9qACqF5F8EKNNW0FNIUa8l/FzOTCgwaTxZI6MrUE+kgiHDCA0SVLMKioMlmd6EbwM6F 53hHVgFnBvjTREofjkeX9GDExWfjkEnxiC1ciiq2HBqp1O3IVTJMJ3qx6hkUCG1hsenW BBht2068SFqrbbvWIgQU+nKDktwfaHqHzTuhqXyMabftNvPT7drzF5Tba7oqBBcdOufF EvQQ==
Received: by 10.112.48.74 with SMTP id j10mr7004096lbn.106.1330922018305; Sun, 04 Mar 2012 20:33:38 -0800 (PST)
MIME-Version: 1.0
Received: by 10.112.130.167 with HTTP; Sun, 4 Mar 2012 20:33:18 -0800 (PST)
In-Reply-To: <4F52494D.10005@gmail.com>
References: <20120228015606.2227.qmail@joyce.lan> <4F4D53E2.5080803@dougbarton.us> <alpine.BSF.2.00.1202281745310.7969@joyce.lan> <4F50939C.4020608@dougbarton.us> <alpine.BSF.2.00.1203020941360.37874@joyce.lan> <20120302224816.E2B111E02C9D@drugs.dv.isc.org> <alpine.BSF.2.00.1203021755270.76484@joyce.lan> <4F51FE43.5010402@tana.it> <01OCO724C8RI00ZUIL@mauve.mrochek.com> <4BFFCC4E-BDF2-40D1-A452-F37DE2A43FD5@frobbit.se> <4F52494D.10005@gmail.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Sun, 4 Mar 2012 23:33:18 -0500
Message-ID: <CAF4+nEFpkVzArC_8n3u01SiRa6QGSOjPDr5O8FfDWQVVM=b6Bg@mail.gmail.com>
Subject: Re: provisioning software, was DNS RRTYPEs, the difficulty with
To: ietf@ietf.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Mar 2012 04:33:40 -0000

Hey, if people don't like the restrictions of the TXT RR, have I got
an answer for you!
See http://tools.ietf.org/html/draft-ietf-dnsind-kitchen-sink-02
A little out of data but gives you a wide variety of formats :-)

Thanks,
Donald
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D
=C2=A0Donald E. Eastlake 3rd=C2=A0=C2=A0 +1-508-333-2270 (cell)
=C2=A0155 Beaver Street,=C2=A0Milford, MA 01757 USA
=C2=A0d3e3e3@gmail.com



On Sat, Mar 3, 2012 at 11:39 AM, Hector <sant9442@gmail.com> wrote:
> =EF=BF=BD wrote:
>>
>> On 3 mar 2012, at 16:56, ned+ietf@mauve.mrochek.com wrote:
>>
>>> Doubtful. If a record needs to have, say, a priority field, or a port
>>> number,
>>> given the existence of MX, SRV, and various other RRs it's going to be
>>> very
>>> difficult for the designers of said field to argue that that should be
>>> done as
>>> ASCII text that has to be parsed out to use.
>>
>>
>> Agree with you but too many people today "just" program in perl och pyth=
on
>> where the parsing is just a cast or similar, and they do not understand =
this
>> argument of yours -- which I once again completely stand behind myself.
>
>
> The original version of Sender-ID (Caller ID Policy) was an XML version o=
f
> SPF. In fact, the experimental record still exist:
>
> =C2=A0 nslookup -query=3Dtxt _ep.hotmail.com
>
> =C2=A0 "<ep xmlns=3D'http://ms.net/1' testing=3D'true'>
> =C2=A0 =C2=A0<out><m><indirect>list1._ep.hotmail.com</indirect>
> =C2=A0 =C2=A0<indirect>list2._ep.hotmail.com</indirect>
> =C2=A0 =C2=A0<indirect>list3._ep.hotmail.com</indirect></m></out></ep>"
>
> It was introductions like this that raised eyebrows and the need to inclu=
de
> a new RR type with the simpler language SPF TXT fallback for SPF and
> SENDER-ID.
>
> If TXT becomes the acceptable norm, than perhaps the XML format cane easi=
ly
> be reconsidered for a DNS TXT storage with a common XML I/O construct. :(
>
> --
> HLS
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf

From alexey.melnikov@isode.com  Mon Mar  5 03:12:31 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 36F2B21F857D for <ietf@ietfa.amsl.com>; Mon,  5 Mar 2012 03:12:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.259
X-Spam-Level: 
X-Spam-Status: No, score=-102.259 tagged_above=-999 required=5 tests=[AWL=0.340, 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 YzeomxQLjRD1 for <ietf@ietfa.amsl.com>; Mon,  5 Mar 2012 03:12:30 -0800 (PST)
Received: from rufus.isode.com (cl-125.lon-03.gb.sixxs.net [IPv6:2a00:14f0:e000:7c::2]) by ietfa.amsl.com (Postfix) with ESMTP id CB8E921F855B for <ietf@ietf.org>; Mon,  5 Mar 2012 03:12:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1330945948; d=isode.com; s=selector; i=@isode.com; bh=sqXZH4ITAqEyBTtbXEG5mYdpBzbp4oZzYh+fOhcTFOA=; 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=mnHISoDDs7Ltfmyk1GQLDX1049cdD7NwNPCIfyXoCQw2oTnXxySF0TGUpTrLFNO64Odrvi /zlMom4tNCsfv+1i7VO72rd2trZgnz+dvDBmDszk5wrNG70gmMwR8w7qsQiW+ONCxXIZCO E0aQJsyV6PjR1dYHvP74al5soAmsPHM=;
Received: from [172.16.1.29] (shiny.isode.com [62.3.217.250])  by rufus.isode.com (submission channel) via TCP with ESMTPSA  id <T1SfmwBhulRQ@rufus.isode.com>; Mon, 5 Mar 2012 11:12:28 +0000
Message-ID: <4F549FC0.1060609@isode.com>
Date: Mon, 05 Mar 2012 11:13:04 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:9.0) Gecko/20111222 Thunderbird/9.0.1
To: Barry Leiba <barryleiba@computer.org>
Subject: Re: Last Call: <draft-melnikov-smtp-priority-07.txt>  (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard
References: <20120301004219.15266.76505.idtracker@ietfa.amsl.com> <CAC4RtVDeXwCLh9R_bNmLwEC5g_4Dv9HadOpXMwbSz5RT2m+jUg@mail.gmail.com>
In-Reply-To: <CAC4RtVDeXwCLh9R_bNmLwEC5g_4Dv9HadOpXMwbSz5RT2m+jUg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Pete Resnick <presnick@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: Mon, 05 Mar 2012 11:12:31 -0000

On 01/03/2012 20:49, Barry Leiba wrote:
> I had expected that we'd deal with my shepherd review before doing the
> last call on the document.  Because that didn't happen, I'll re-post
> my review here, as public last-call comments.  Maybe that will prevent
> people from raising the same things I've already raised.
>
> First, two additional points:
>
> 1. As to Murray's comment about explicitly declaring text to be
> informative, I'm with Tom on this: I think it's at worst harmless, and
> possibly very useful as a clarification, to explicitly say "this
> [paragraph, section, whatever] is not normative."  It might be
> unnecessary, but where's the harm?
Agreed.
> 2. I, too, noticed all the lower-case "should" and "may" words.  I
> suggest that the best way to handle this is to make the following
> change to the RFC 2119 citation text at the beginning of section 2:
>
> NEW
>     The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
>     "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
>     document are to be interpreted as described in [RFC2119] when they appear
>     in ALL CAPS.  These words also appear in this document in lower case as plain
>     English words, absent their normative meanings.
I don't mind changing that, but ID-nits gives a warning when the text 
about keywords is changed and *everybody* likes to complain about that. 
Please talk to IESG about whether using a variant of the standard text 
is acceptable.
> My review, which was already sent to Alexey and Pete:
>
> ----------------------------------------------------------------
>
> Section 4.1
>    1.  A conforming SMTP server SHOULD NOT refuse a MAIL command based
>        on the absence of the PRIORITY parameter.
>
> I agree with Pete's MUST NOT -- also because at this point, the server
> has no idea whether the message is coming from a non-supporting
> server, and whether or not there's an MT-Priority header field in the
> message.  This really needs to be MUST NOT.
Agreed.
> -----
> Section 4.4
>    1.  A PRIORITY parameter MUST NOT appear in the MAIL command issued
>        when relaying the message.
>
>    2.  The relaying MTA MUST first remove any and all existing MT-
>        Priority header fields from the message, and then add its own MT-
>        Priority header field with the value determined by the procedure
>        in Section 4.2.  One exception to this rule is that a message
>        which didn't contain any MT-Priority header field and which
>        didn't have the PRIORITY MAIL FROM parameter specified doesn't
>        need to be updated to contain the "MT-Priority: 0" header field.
>        Syntax of the MT-Priority header field is specified in Section 7.
>
> Because of the exception, I think there's a slight unclear point here
> (and I also don't like the passive voice in bullet 1).  Let me re-work
> this thus:
>
> NEW
>    1.  The relaying MTA MUST NOT use the PRIORITY parameter in the
>        MAIL command issued when relaying the message.
>
>    2.  The relaying MTA MUST first remove any and all existing MT-
>        Priority header fields from the message.
>
>    3.  If the message had a PRIORITY specified in the MAIL FROM
>        parameter *or* there was an MT-Priority header field
>        removed in step 2, then the relaying MTA MUST add its own
>        MT-Priority header field with the value determined by the
>        procedure in Section 4.2.
>
>        The syntax of the MT-Priority header field is specified in
>        Section 7.
Thanks, I've used your text.
> -----
> Section 5.
>    A message priority is a decimal integer in the range from -9 to 9
>    (inclusive).  SMTP servers compliant with this specification are not
>    required to support all 19 distinct priority levels (i.e. to treat
>    each priority value as a separate priority), but they MUST implement
>    at least the following 6 distinct priority levels: -4, -2, 0, 2, 4,
>    9.  I.e. an implementation that only supports the 6 priority levels
>    will internally treat all syntactically valid priority values below
>    and including -4 as priority -4, priorities -3 and -2 as priority -2,
>    priorities -1 and 0 as priority 0, etc., with all priorities starting
>    from 5 are treated as priority 9.  An SMTP server MAY support more
>    than 6 different priority levels.  Decision about which levels to
>    support in addition to the 6 mentioned above is a local matter.
>
> There's a lot of stuff after the "I.e.", much of which can be changed
> to just say that a syntatically valid level that isn't supported gets
> raised to the next higher supported number.  Say that, and it all
> looks clearer and easier.
Ok, I will try to use your suggestion.
> -----
> Editorial:
> OLD
>    Note: 19 possible priority levels are defined by this specification
>    for extensibility, for example if a particular implementation or
>    deployment environment needs to provide fine grainer control over
>    message transfer priorities, for example a server implementation may
>    need to have an extra high priority level to the 6 levels defined
>    above.
>
> NEW
>    Note: 19 possible priority levels are defined by this specification
>    for extensibility. For example, a particular implementation or
>    deployment environment might need to provide finer-grained control
>    over message transfer priorities.  In such a case, a server
>    implementation might need an extra priority level beyond the 6 levels
>    defined above.
Changed, thanks.
> -----
> Editorial:
> OLD
> Such actions usually need user confirmation.
> NEW
> Such actions usually require user interaction.
Ok.
> -----
> Section 5.1
>    As a default policy, emails with higher priority waiting to be sent
>    by a client SHOULD NOT initiate transactions for emails with lower
>    priorites.
Removed as per reply to Pete.
> If two or more emails with the same priority are ready to
>    be sent at the same time, the MTA should use its regular algorithm
>    (the algorithm used in absence of this SMTP extension) for deciding
>    how to send them out.
>
> I have no idea what the first sentence means.  For the second
> sentence, I would say it like this: "Within a priority level, the MTA
> uses its normal ordering for the messages."
Ok.
> -----
> Section 5.2
> Editorial:
> OLD
>    An important constraint (usually associated with higher priority
>    levels) is, that messages with that priority have to reach its
>    destination within a defined period of time.  In some cases, higher
>    priorities mean shorter maximum allowed time of delivery.
> NEW
>    An important constraint (usually associated with higher priority
>    levels) is that messages with high priority have some delivery
>    time constraints.  In some cases, higher priorities mean a shorter
>    maximum time allowed for delivery.
Ok.
> And I would add to the second paragraph, "But note that use of the
> DELIVERBY extension alone does not guarantee any priority processing."
Added.
>
> -----
> Section 6
> I would switch sections 6 and 7, to avoid the forward reference in the
> current section 6.
Ok.

  [snip]

Thank you,
Alexey


From alexey.melnikov@isode.com  Mon Mar  5 03:59:18 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 0AEDE21F8730 for <ietf@ietfa.amsl.com>; Mon,  5 Mar 2012 03:59:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.27
X-Spam-Level: 
X-Spam-Status: No, score=-102.27 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 kvXW56fYYQ1s for <ietf@ietfa.amsl.com>; Mon,  5 Mar 2012 03:59:16 -0800 (PST)
Received: from rufus.isode.com (cl-125.lon-03.gb.sixxs.net [IPv6:2a00:14f0:e000:7c::2]) by ietfa.amsl.com (Postfix) with ESMTP id 6A12621F8532 for <ietf@ietf.org>; Mon,  5 Mar 2012 03:59:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1330948755; d=isode.com; s=selector; i=@isode.com; bh=ajb8dinvyuYTYWBJp3QjWp75DbHIp0btw7khde7O7lE=; 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=HgedGuS7DmTvHcrbxwm/fM737Z72vk9sJFNci3KuA1LxI26Yg46LxN5cfmaDHHgQWCDy72 rJTDlGHo7sf4qzm0mn5COg6qoT+AYp7g/9rsGhXYjji5ayJGQWTXojwbSz8pbrJQ8FanHR l1l/o8pNgvWyp8oz81eEWGgrfm5u1yo=;
Received: from [172.16.1.29] (shiny.isode.com [62.3.217.250])  by rufus.isode.com (submission channel) via TCP with ESMTPSA  id <T1SqkgBhuppy@rufus.isode.com>; Mon, 5 Mar 2012 11:59:15 +0000
Message-ID: <4F54AAB7.5000703@isode.com>
Date: Mon, 05 Mar 2012 11:59:51 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:9.0) Gecko/20111222 Thunderbird/9.0.1
To: "Murray S. Kucherawy" <msk@cloudmark.com>
Subject: Re: Last Call: <draft-melnikov-smtp-priority-07.txt>  (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard
References: <20120301004219.15266.76505.idtracker@ietfa.amsl.com> <9452079D1A51524AA5749AD23E00392806E6F5@exch-mbx901.corp.cloudmark.com>
In-Reply-To: <9452079D1A51524AA5749AD23E00392806E6F5@exch-mbx901.corp.cloudmark.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Mar 2012 11:59:18 -0000

Hi Murray,
Thank you for the comments. Some answers below.

On 01/03/2012 04:43, Murray S. Kucherawy wrote:
> I have several comments on this draft.  But first, this is a big improvement since the last version I reviewed, so kudos to the authors.
>
> A couple of these refer to issues in the document that need to be resolved before it can move forward, but you probably already know what they are.  The rest are not showstoppers.  It could also use a quick editorial pass, which I'm happy to do for you separately if you like.
>
> - Section 3, bullet 7: LTMP ->  LMTP
Fixed.
> - Section 4.1 contains a reference to "esmtp-values" which looks like an ABNF terminal, but it's not explained.  Did you mean an ABNF terminal,
Yes, as defined in Section 4.1.2 of RFC 5321. Clarified.
> or did you mean something about ESMTP parameters?
>
> - Section 4.2, bullet 2: "Section 6" should probably be in parentheses, probably preceded by "see"
Fixed.
> - There's a bunch of TBDs that still need to be resolved before this document moves forward (X.7.TBD3 as an enhanced status code, for example)
No, these are assigned by IANA before publication. RFC Editor will fix 
these.
> - Section 4.2 makes reference to "the Minimize condition" but the document doesn't otherwise define it
Yes, I will explain.
> - Section 4.3 says "For example, once an MTA accepts a message, the MTA MUST NOT change a (syntactically valid) priority value if the MTA doesn't support it."  There seems to be a chicken-and-egg going on here: If the MTA doesn't support the extension, how can it know not to change the priority outbound?
I meant "supports the extension, but doesn't support a particular value 
as distinct priority level". Suggestions on how to make this clear would 
be appreciated.
> - There are lots of SHOULDs in here that might benefit from example situations in which one might deviate from the normative statement containing the SHOULD.
I will review. I had some discussion with SM about some of these and 
argued that not all of them should be explained. But I agree that some 
of them need explanation.
> - Section 5 and Section 5.1 use "not required", "should", and "may" where RFC2119 is cited earlier.  Should they be in all-caps, or should other language be selected?
Lowercased versions are not used in normative sense. Maybe a note 
suggested by Barry would help with this.
> - Section 5: "Irrespectively on" ->  "Irrespective of"
Changed.
> - Section 5: "fine grainer control" ->  "finer-grained control"
Changed.
> - Section 5.1 makes reference to "the work-in-progress effort extension to RSVP that prioritizes reservations."  This should include a citation even if it references an I-D that's not published yet.
Ok, I will ask my co-editor about this.
> - Section 9: "it is advised that all or none of them SHOULD support the PRIORITY extension" sounds awfully mushy.  I suggest dropping the SHOULD, and rather say something like "it is advised that either all of them support the PRIORITY extension, or none do".
Ok.
> - Section 10 should be resolved before the document advances.
>
> - Section 11: Why use "PRI" and not "priority"?  The existing set of Received clause names are lowercase words, so it seems strange to deviate.
I don't mind to switching to "PRIORITY". But section 4.4 of RFC 5321 
uses uppercase variants (and yes, I know they are case insensitive).
> - Appendix A: Can STANAG 4406 be listed in the Informative References?
Sure.
> - Appendix D: "This appendix and its subsections are informative."  I think that (a) any appendix is informative, because normative text doesn't belong in an appendix; and (b) the normative stuff uses RFC2119 language and this doesn't.  Thus, I think this sentence should be removed.  (I know I've lost this argument before, but I'll make another stand here anyway.)
I think other people already commented on this :-)


From alexey.melnikov@isode.com  Mon Mar  5 06:11:29 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 890C121F8639 for <ietf@ietfa.amsl.com>; Mon,  5 Mar 2012 06:11:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.28
X-Spam-Level: 
X-Spam-Status: No, score=-102.28 tagged_above=-999 required=5 tests=[AWL=0.319, 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 zYntF8bON8DW for <ietf@ietfa.amsl.com>; Mon,  5 Mar 2012 06:11:28 -0800 (PST)
Received: from rufus.isode.com (cl-125.lon-03.gb.sixxs.net [IPv6:2a00:14f0:e000:7c::2]) by ietfa.amsl.com (Postfix) with ESMTP id 76AEB21F8630 for <ietf@ietf.org>; Mon,  5 Mar 2012 06:11:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1330956687; d=isode.com; s=selector; i=@isode.com; bh=8JU3b4SSGZy/5XG5j2zKR2oK/MWlJOJThudQkV/y9Wk=; 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=A78Xp1Jt+Xur/thg3f4gkrMVmowEpJo4GY3fi/Tk7UrqoWRUSNCmVdTcJwBQacxL+NLF7y 0b9bgYnfnrz0HM04mloVfR2la7ipG8rjF42OyEdf687UxZPslq95MpwG6q1qILT8R4H19/ vmltS6Qr1IXGneDxWb66emsfFRx9rCc=;
Received: from [172.16.1.29] (shiny.isode.com [62.3.217.250])  by rufus.isode.com (submission channel) via TCP with ESMTPSA  id <T1TJjgBhuoFd@rufus.isode.com>; Mon, 5 Mar 2012 14:11:27 +0000
Message-ID: <4F54C9B1.4010100@isode.com>
Date: Mon, 05 Mar 2012 14:12:01 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:9.0) Gecko/20111222 Thunderbird/9.0.1
To: Ned Freed <ned.freed@mrochek.com>
Subject: Re: Last Call: <draft-melnikov-smtp-priority-07.txt>  (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard
References: <20120301004219.15266.76505.idtracker@ietfa.amsl.com> <CAC4RtVDeXwCLh9R_bNmLwEC5g_4Dv9HadOpXMwbSz5RT2m+jUg@mail.gmail.com> <CAC4RtVB1G_HjYNug0Fvq7LPSnzqG2KxH-PY6nv=nBZKv-uXTLA@mail.gmail.com> <01OCM8WDJZKI00ZUIL@mauve.mrochek.com>
In-Reply-To: <01OCM8WDJZKI00ZUIL@mauve.mrochek.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Pete Resnick <presnick@qualcomm.com>, 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: Mon, 05 Mar 2012 14:11:29 -0000

Hi Ned,

On 02/03/2012 06:12, Ned Freed wrote:
>> The most significant item that needs to be called out is the issue of
>> tunneling the PRIORITY value through non-conforming MTAs by turning it
>> into a message header field (MT-Priority) and then back again.  This
>> is a problematic technique, but is an important capability for those
>> who need and intend to implement this extension.  It creates a trust
>> issue, wherein a message containing MT-Priority can be originated with
>> a Message Submission Agent that does not know about this extension,
>> and when the message hits a Message Transfer Agent that does support
>> this, the header field will be turned back into a valid PRIORITY
>> value, on the unwarranted assumption that it was authorized.
>> Intermediate MTAs have no way to distinguish this situation from one
>> where the field was tunneled legitimately.
> There may not be substantial experience with doing this sort of thing in SMTP
> relays, but there's plenty of experience doing it in gateways to other mail
> environments, e.g., X.400 and many of the old LAN email systems. In fact one of
> the more common fields that has been mapped this way is message transfer
> priority, so there is considerably experience with fields having more or less
> the same semantics as what is being proposed here.
Exactly.
> I am unaware of any cases where this was abused, probably because increased
> transfer priority doesn't buy you all that much in most cases. Related
> but more user-visible features, e.g., importance (in the X.400 sense)
> have been known to be abused, however.
>
> That said, I think an important omission in this document is that it
> only allows MSA's to change message priorities to conform to site policy.
> MTAs should also be allowed to do this.
Can you elaborate a bit more on possible use cases? Would such an MTA 
only lower the priority or do you think it might also raise it?
> Another issue is the silly prohibition against using Priority: and other header
> fields to set priority levels. What if is existing site policy is in fact to
> use those fields to determine message priority?
(Ignoring the question of whether use of MT-Priority header field is a 
good thing or not for a moment.)

I actually don't have a strong feeling against usage of other existing header fields.
Some of the existing header fields don't have the exact semantics desired here. Others (like the MIXER's Priority) have the right semantics but don't support sufficient number of priorities required by MMHS (6 levels). That is why a new header field was introduced.

But anyway, I am happy for this restriction to be removed/relaxed. Can you recommend some specific text?



From alexey.melnikov@isode.com  Mon Mar  5 06:45:12 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 391A221F85E4 for <ietf@ietfa.amsl.com>; Mon,  5 Mar 2012 06:45:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.29
X-Spam-Level: 
X-Spam-Status: No, score=-102.29 tagged_above=-999 required=5 tests=[AWL=0.309, 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 c6xJ75nEMvJ6 for <ietf@ietfa.amsl.com>; Mon,  5 Mar 2012 06:45:11 -0800 (PST)
Received: from rufus.isode.com (cl-125.lon-03.gb.sixxs.net [IPv6:2a00:14f0:e000:7c::2]) by ietfa.amsl.com (Postfix) with ESMTP id 2804F21F85E5 for <ietf@ietf.org>; Mon,  5 Mar 2012 06:45:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1330958710; d=isode.com; s=selector; i=@isode.com; bh=khkBPao1pILGfqckaqXfqJ8lQHe3sQs/s+GkObQlKTA=; 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=nQb7hwNNCncpjUEjUKXBVwtlg+Gv6XB1iLmc2NHHnn1JnU5jCGjKWUxc21BBo/EPZugiX8 WTsRzqDs0DGIV1XJUiZMXfTxsaZ1LcAGu+FVQ2d2ou4UQ9cOkK+MhbcFTvICTVGSz91//y g+uFzHyTPXrZ4UD+O7gI1pMLC4u3ydE=;
Received: from [172.16.1.29] (shiny.isode.com [62.3.217.250])  by rufus.isode.com (submission channel) via TCP with ESMTPSA  id <T1TRdQBhugVG@rufus.isode.com>; Mon, 5 Mar 2012 14:45:10 +0000
Message-ID: <4F54D198.3000607@isode.com>
Date: Mon, 05 Mar 2012 14:45:44 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:9.0) Gecko/20111222 Thunderbird/9.0.1
To: ned+ietf@mauve.mrochek.com
Subject: Re: Last Call: <draft-melnikov-smtp-priority-07.txt>  (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard
References: <CAC4RtVA3F8gsBWY65W5KNDE+408EvtP+hp5GTzLg4FMgC1bdcQ@mail.gmail.com> <20120303041153.23749.qmail@joyce.lan> <01OCOC18E6PI00ZUIL@mauve.mrochek.com>
In-Reply-To: <01OCOC18E6PI00ZUIL@mauve.mrochek.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: John Levine <johnl@iecc.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Mar 2012 14:45:12 -0000

On 03/03/2012 18:07, ned+ietf@mauve.mrochek.com wrote:
  [...]
>> So I have two suggestions.  One is to leave it as is, and make it
>> experimental. If it turns out the tunnels all work the same way, you
>> can come back and add the spec about how they work and rev it as
>> standards track.  The other is to take out the tunnel bit and make it
>> standards track now, so a compliant implementation needs
>> priority-aware MTAs from end to end.  Even if you take out the tunnel
>> stuff in the spec, you can still tunnel in your implementations, using
>> whatever non-standard ad hoc kludges you want.  Since the current spec
>> has gaps that would need to be filled by non-standard ad hoc kludges
>> anyway, you haven't lost anything.
> I have to say I strongly prefer the latter, especially if it also includes
> eliminating the prohibition on using other sources of priority information to
> set the envelope priority level on submission. In fact given that prohibition
> I see little point in implementing this, at least not in a fashion
> that conforms to the specification.
I do prefer the latter as well (and yes, happy to remove the restriction), but I don't feel very comfortable pretending that tunneling wouldn't happen. See my other reply about this (to be written later today).



From barryleiba@gmail.com  Mon Mar  5 07:15:33 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 D823A21F8776 for <ietf@ietfa.amsl.com>; Mon,  5 Mar 2012 07:15:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.986
X-Spam-Level: 
X-Spam-Status: No, score=-102.986 tagged_above=-999 required=5 tests=[AWL=-0.009, 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 nG7aqKXRn045 for <ietf@ietfa.amsl.com>; Mon,  5 Mar 2012 07:15:33 -0800 (PST)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id 4792A21F8770 for <ietf@ietf.org>; Mon,  5 Mar 2012 07:15:33 -0800 (PST)
Received: by ggmi1 with SMTP id i1so1876280ggm.31 for <ietf@ietf.org>; Mon, 05 Mar 2012 07:15:32 -0800 (PST)
Received-SPF: pass (google.com: domain of barryleiba@gmail.com designates 10.60.7.70 as permitted sender) client-ip=10.60.7.70; 
Authentication-Results: mr.google.com; spf=pass (google.com: domain of barryleiba@gmail.com designates 10.60.7.70 as permitted sender) smtp.mail=barryleiba@gmail.com; dkim=pass header.i=barryleiba@gmail.com
Received: from mr.google.com ([10.60.7.70]) by 10.60.7.70 with SMTP id h6mr7676270oea.44.1330960532903 (num_hops = 1); Mon, 05 Mar 2012 07:15:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=sqRlOL3F2FnPz3k1FLOYv/YhuRANzKzEvfRl3azfkVY=; b=OcG+mhNWDzYUib3t13JmwFgX+i3A+byO2rawbaFipydPecEO5UsE/QOo4YB2EMNBGW sZ6f0Bq4im8Djaumodob8hIn5akG0xfSFpR/dxygzj49bWvbiXxup2/UHJsVzmWgGHv1 mU5yP4j2mEyltQlGnXC3UNKhbr3Bmm38WWeoPxEjlbRKA3uWHLqJhVRbf2znaQJffRRm /k21ooNf2bz24wgrOitsBZNfmOR9EknskRqYvvJVeE1JQmTmozBtc2ZvUvGA3zVnDLqq I2HIrcrXRRYhozn83xlWreRFPc+ZYUZu6dTx8ht72Ah0F+WUDp6KF3vT0OBZFHN0LoTt OSdQ==
MIME-Version: 1.0
Received: by 10.60.7.70 with SMTP id h6mr6789670oea.44.1330960532853; Mon, 05 Mar 2012 07:15:32 -0800 (PST)
Sender: barryleiba@gmail.com
Received: by 10.60.125.37 with HTTP; Mon, 5 Mar 2012 07:15:32 -0800 (PST)
In-Reply-To: <4F54C9B1.4010100@isode.com>
References: <20120301004219.15266.76505.idtracker@ietfa.amsl.com> <CAC4RtVDeXwCLh9R_bNmLwEC5g_4Dv9HadOpXMwbSz5RT2m+jUg@mail.gmail.com> <CAC4RtVB1G_HjYNug0Fvq7LPSnzqG2KxH-PY6nv=nBZKv-uXTLA@mail.gmail.com> <01OCM8WDJZKI00ZUIL@mauve.mrochek.com> <4F54C9B1.4010100@isode.com>
Date: Mon, 5 Mar 2012 10:15:32 -0500
X-Google-Sender-Auth: VCPB8injnyJ8iPUNsG2VB8ZbUyI
Message-ID: <CALaySJJUE02R7NP08HB-Si7vOZHRg28vtKqLF9Y45=6d43QHdA@mail.gmail.com>
Subject: Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard
From: Barry Leiba <barryleiba@computer.org>
To: Alexey Melnikov <alexey.melnikov@isode.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: Pete Resnick <presnick@qualcomm.com>, Ned Freed <ned.freed@mrochek.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Mar 2012 15:15:34 -0000

Ned:
>> Another issue is the silly prohibition against using Priority: and other
>> header fields to set priority levels. What if is existing site policy is in fact
>> to use those fields to determine message priority?

Alexey:
> I actually don't have a strong feeling against usage of other existing
> header fields.
> Some of the existing header fields don't have the exact semantics desired
> here. Others (like the MIXER's Priority) have the right semantics but don't
> support sufficient number of priorities required by MMHS (6 levels). That is
> why a new header field was introduced.

Right, this is the issue I have with Ned's desire to allow use of
other fields: those fields have inconsistent semantics, and
inconsistent and non-standard usage.  They're often used to indicate
visual importance of the message to the MUA, rather than anything
related to transmission priority.

That said, I'd have no problem with some sort of MAY-level permission
to *MSAs* to use these fields.  I'd feel very uncomfortable allowing
*MTAs* to do it.  Ned, would it be adequate to your needs to handle it
that way?  Something like this:

OLD
   Other message header fields, such as Importance [RFC2156], Priority
   [RFC2156] and X-Priority, MUST NOT be used for determining the
   priority under this "Priority Message Handling" SMTP extension.

NEW
   Other message header fields, such as Importance [RFC2156], Priority
   [RFC2156] and X-Priority, are used inconsistently and often with
   different semantics from MT-Priority.  Message Submission Agents
   [RFC6409] MAY use such fields to assign an initial priority in the
   absence of an SMTP PRIORITY parameter.  Otherwise, such fields
   MUST NOT be used for determining the priority under this "Priority
   Message Handling" SMTP extension.

Barry

From johnl@iecc.com  Mon Mar  5 07:42:00 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 5713D21F87B4 for <ietf@ietfa.amsl.com>; Mon,  5 Mar 2012 07:42:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.366
X-Spam-Level: 
X-Spam-Status: No, score=-102.366 tagged_above=-999 required=5 tests=[AWL=0.234, 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 iSJ5poccuzkV for <ietf@ietfa.amsl.com>; Mon,  5 Mar 2012 07:41:59 -0800 (PST)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 57FD621F8683 for <ietf@ietf.org>; Mon,  5 Mar 2012 07:41:59 -0800 (PST)
Received: (qmail 91166 invoked from network); 5 Mar 2012 15:41: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:references:mime-version:content-type:vbr-info:user-agent:cleverness; s=1641d.4f54dec5.k1203; bh=KHkne4MlKFYuugqO4FhuIhD36xIz26GnnGNK6JaBSms=; b=enYrMYJnRgAeVAbW+tP/Pm24EX+BlJ8BgTiaZHYYvPFiEToJWoan0Jpzt6GQ2A5rSSFC4c+WsjWIy+GUCHVJuZtZdB1ftI7QOphEqSQDbdVR34n24CMyq6PCjiEgVIXWzDuJDN2qOUZEK3WZk6nli2o9DVotj5I73D3rRzpPOmo=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Received: (ofmipd 127.0.0.1); 5 Mar 2012 15:41:35 -0000
Date: 5 Mar 2012 10:41:56 -0500
Message-ID: <alpine.BSF.2.00.1203051040260.47190@joyce.lan>
From: "John R. Levine" <johnl@iecc.com>
To: "Alexey Melnikov" <alexey.melnikov@isode.com>
Subject: Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard
In-Reply-To: <4F54D198.3000607@isode.com>
References: <CAC4RtVA3F8gsBWY65W5KNDE+408EvtP+hp5GTzLg4FMgC1bdcQ@mail.gmail.com> <20120303041153.23749.qmail@joyce.lan> <01OCOC18E6PI00ZUIL@mauve.mrochek.com> <4F54D198.3000607@isode.com>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
Cleverness: None detected
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Mar 2012 15:42:00 -0000

> I do prefer the latter as well (and yes, happy to remove the restriction), 
> but I don't feel very comfortable pretending that tunneling wouldn't happen.

Of course people will tunnel stuff.  But will they all tunnel it the same 
way, in which case a standard could be useful, or will they each have 
their own hacks?  Given the vagueness about how you can tell that 
something should come out of the tunnel back into the envelope, it sounds 
more like the latter.

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

From ned+ietf@mauve.mrochek.com  Mon Mar  5 07:46:40 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 E7E4F21F87C1 for <ietf@ietfa.amsl.com>; Mon,  5 Mar 2012 07:46:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.587
X-Spam-Level: 
X-Spam-Status: No, score=-2.587 tagged_above=-999 required=5 tests=[AWL=0.012,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id d2AOMwFzRuM7 for <ietf@ietfa.amsl.com>; Mon,  5 Mar 2012 07:46:40 -0800 (PST)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id 1818721F87C4 for <ietf@ietf.org>; Mon,  5 Mar 2012 07:46:40 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OCQZ46TBHC0160HU@mauve.mrochek.com> for ietf@ietf.org; Mon, 5 Mar 2012 07:46:26 -0800 (PST)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OCPMUVDUMO00ZUIL@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Mon, 5 Mar 2012 07:46:21 -0800 (PST)
From: ned+ietf@mauve.mrochek.com
Message-id: <01OCQZ44DUX800ZUIL@mauve.mrochek.com>
Date: Mon, 05 Mar 2012 07:34:30 -0800 (PST)
Subject: Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard
In-reply-to: "Your message dated Mon, 05 Mar 2012 14:12:01 +0000" <4F54C9B1.4010100@isode.com>
MIME-version: 1.0
Content-type: TEXT/PLAIN; format=flowed
References: <20120301004219.15266.76505.idtracker@ietfa.amsl.com> <CAC4RtVDeXwCLh9R_bNmLwEC5g_4Dv9HadOpXMwbSz5RT2m+jUg@mail.gmail.com> <CAC4RtVB1G_HjYNug0Fvq7LPSnzqG2KxH-PY6nv=nBZKv-uXTLA@mail.gmail.com> <01OCM8WDJZKI00ZUIL@mauve.mrochek.com> <4F54C9B1.4010100@isode.com>
To: Alexey Melnikov <alexey.melnikov@isode.com>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mrochek.com; s=mauve; t=1330962393; i=@mrochek.com; bh=MNaXNe7gy8QAQ8KFjasHERILqJhGadG210lAtlhl3ok=;  h=From:Cc:Message-id:Date:Subject:In-reply-to:MIME-version: Content-type:References:To; b=fD9YQz8FCCFtgKUfHlIfeNYvBq3eQZNzCLLLVTDBOPY+judSGDJjx7BUO2RQgG3YQ ngD9FczeJe1GnTnAeT9tjeI3oukRfqv5w/aQ7tVxFtyk4qzxvca6NFnU7rCXcb9m20 DkCxopDbda3lD0ZW3mwH2pP4Jg1BuNfW3Qf3j2cQ=
Cc: Pete Resnick <presnick@qualcomm.com>, Barry Leiba <barryleiba@computer.org>, Ned Freed <ned.freed@mrochek.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Mar 2012 15:46:41 -0000

> > That said, I think an important omission in this document is that it
> > only allows MSA's to change message priorities to conform to site policy.
> > MTAs should also be allowed to do this.

> Can you elaborate a bit more on possible use cases?

Nobody is going to simply allow priorities to be set willy-nilly on mail coming
from random sources outside their administrative domain. That's absurd.
However, they may be will to make bilateral arrangements with selected
partners, identified by IP address or whatever, that would allow such a
setting, perhaps within a restricted range of allowed values.

> Would such an MTA
> only lower the priority or do you think it might also raise it?

I don't see any reason to limit it to lowering it.

> > Another issue is the silly prohibition against using Priority: and other header
> > fields to set priority levels. What if is existing site policy is in fact to
> > use those fields to determine message priority?

> (Ignoring the question of whether use of MT-Priority header field is a
> good thing or not for a moment.)

> I actually don't have a strong feeling against usage of other existing
> header fields.  Some of the existing header fields don't have the exact
> semantics desired here.

Well, sure. You most definitely don't want to mix in Importance or other
MUA level priority fields.

> Others (like the MIXER's Priority) have the right semantics but don't support
> sufficient number of priorities required by MMHS (6 levels).

I think you're going to have to accept the fact that the overwhelming majority
of people out there running email systems have never even heard of MMHS and
even if they have don't give a damn about faithfully retaining it's
semantics. But they do care that new mechanism be made compatible with
whatever ad-hoc scheme they are currently using, even if said scheme
doesn't have the full range of values.

For example, I can easily see a site wanting to map this to and from the field
used by Microsoft Exchange (sorry, I forget the exact name) even though if
memory serves that field only accepts three values. And either this is going to
happen no matter what the specification says, or the specification simply won't
deploy in any meaningful way.

> That is why a new header field was introduced.

> But anyway, I am happy for this restriction to be removed/relaxed. Can you
> recommend some specific text?

I'll try to do so later this week.

				Ned

From ned+ietf@mauve.mrochek.com  Mon Mar  5 07:56:03 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 EA4BD21F87DC for <ietf@ietfa.amsl.com>; Mon,  5 Mar 2012 07:56:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.588
X-Spam-Level: 
X-Spam-Status: No, score=-2.588 tagged_above=-999 required=5 tests=[AWL=0.011,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Abx7RRhyD3Vd for <ietf@ietfa.amsl.com>; Mon,  5 Mar 2012 07:56:03 -0800 (PST)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id 1818021F87DD for <ietf@ietf.org>; Mon,  5 Mar 2012 07:56:03 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OCQZG1FVCG017HRC@mauve.mrochek.com> for ietf@ietf.org; Mon, 5 Mar 2012 07:55:59 -0800 (PST)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OCPMUVDUMO00ZUIL@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Mon, 5 Mar 2012 07:55:53 -0800 (PST)
From: ned+ietf@mauve.mrochek.com
Message-id: <01OCQZFYBOQA00ZUIL@mauve.mrochek.com>
Date: Mon, 05 Mar 2012 07:47:24 -0800 (PST)
Subject: Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard
In-reply-to: "Your message dated Mon, 05 Mar 2012 10:15:32 -0500" <CALaySJJUE02R7NP08HB-Si7vOZHRg28vtKqLF9Y45=6d43QHdA@mail.gmail.com>
MIME-version: 1.0
Content-type: TEXT/PLAIN
References: <20120301004219.15266.76505.idtracker@ietfa.amsl.com> <CAC4RtVDeXwCLh9R_bNmLwEC5g_4Dv9HadOpXMwbSz5RT2m+jUg@mail.gmail.com> <CAC4RtVB1G_HjYNug0Fvq7LPSnzqG2KxH-PY6nv=nBZKv-uXTLA@mail.gmail.com> <01OCM8WDJZKI00ZUIL@mauve.mrochek.com> <4F54C9B1.4010100@isode.com> <CALaySJJUE02R7NP08HB-Si7vOZHRg28vtKqLF9Y45=6d43QHdA@mail.gmail.com>
To: Barry Leiba <barryleiba@computer.org>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mrochek.com; s=mauve; t=1330962966; i=@mrochek.com; bh=SYKBR4nDat9kIGTpXNTZRBfMoVHG4cjhDlpkXN9X0Iw=;  h=From:Cc:Message-id:Date:Subject:In-reply-to:MIME-version: Content-type:References:To; b=A2rWRjfoQ/Zt7rxPD7FAKDurpn/pafRx8bfe/keVKWUAnuNWqjDL3igXAHOroCxiP jln9wAfB5RsfEFT/fXkYobFojHf2dIXm1zvE4Pag3Jw+vlEXcyAl7xVQZsm+aTTNJG Idjl84AGPjelWJyUYPKERzy7edi2mtgzLbJM4cCU=
Cc: Pete Resnick <presnick@qualcomm.com>, Alexey Melnikov <alexey.melnikov@isode.com>, Ned Freed <ned.freed@mrochek.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Mar 2012 15:56:04 -0000

> Ned:
> >> Another issue is the silly prohibition against using Priority: and other
> >> header fields to set priority levels. What if is existing site policy is in fact
> >> to use those fields to determine message priority?

> Alexey:
> > I actually don't have a strong feeling against usage of other existing
> > header fields.
> > Some of the existing header fields don't have the exact semantics desired
> > here. Others (like the MIXER's Priority) have the right semantics but don't
> > support sufficient number of priorities required by MMHS (6 levels). That is
> > why a new header field was introduced.

> Right, this is the issue I have with Ned's desire to allow use of
> other fields: those fields have inconsistent semantics, and
> inconsistent and non-standard usage.  They're often used to indicate
> visual importance of the message to the MUA, rather than anything
> related to transmission priority.

I'm sorry, but that's simply a strawman. AFAICT nobody pushing back on this is
suggesting mapping MTA priority to or from a field with totally different
semantics. But there are plenty of fields in common use that are used to
control MTA priority. Those are the fields I'm talking about.

And yes, people will make mistakes. They always do. But as I commented
in a previous discussion, if we let that stop us we'd never standarize
anything.

> That said, I'd have no problem with some sort of MAY-level permission
> to *MSAs* to use these fields.  I'd feel very uncomfortable allowing
> *MTAs* to do it.  Ned, would it be adequate to your needs to handle it
> that way?

No. Like it or not, if you expect this to gain any traction at all, you're
going to have to accept the fact that people are going to want to tunnel it
through fields with the same general semantics but restricted as to possible
values.

  Something like this:

> OLD
>    Other message header fields, such as Importance [RFC2156], Priority
>    [RFC2156] and X-Priority, MUST NOT be used for determining the
>    priority under this "Priority Message Handling" SMTP extension.

I hadn't noticed importance listed as a possible source of MTA priority
information. That's actually committing the error of mapping a field with
entirely different semantics into MTA priority and at a minimum needs to be
removed - we should NOT be encouraging that.

> NEW
>    Other message header fields, such as Importance [RFC2156], Priority
>    [RFC2156] and X-Priority, are used inconsistently and often with
>    different semantics from MT-Priority.  Message Submission Agents
>    [RFC6409] MAY use such fields to assign an initial priority in the
>    absence of an SMTP PRIORITY parameter.  Otherwise, such fields
>    MUST NOT be used for determining the priority under this "Priority
>    Message Handling" SMTP extension.

It seems you're complaining about other people doing something they never
wanted to do while actually making that error yourself.

				Ned

From barryleiba@gmail.com  Mon Mar  5 08:07: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 C259121F8813 for <ietf@ietfa.amsl.com>; Mon,  5 Mar 2012 08:07:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.986
X-Spam-Level: 
X-Spam-Status: No, score=-102.986 tagged_above=-999 required=5 tests=[AWL=-0.009, 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 6Ewv3-90LtyL for <ietf@ietfa.amsl.com>; Mon,  5 Mar 2012 08:07:17 -0800 (PST)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by ietfa.amsl.com (Postfix) with ESMTP id 13D1521F8812 for <ietf@ietf.org>; Mon,  5 Mar 2012 08:07:17 -0800 (PST)
Received: by yenm5 with SMTP id m5so1914399yen.31 for <ietf@ietf.org>; Mon, 05 Mar 2012 08:07:16 -0800 (PST)
Received-SPF: pass (google.com: domain of barryleiba@gmail.com designates 10.60.18.163 as permitted sender) client-ip=10.60.18.163; 
Authentication-Results: mr.google.com; spf=pass (google.com: domain of barryleiba@gmail.com designates 10.60.18.163 as permitted sender) smtp.mail=barryleiba@gmail.com; dkim=pass header.i=barryleiba@gmail.com
Received: from mr.google.com ([10.60.18.163]) by 10.60.18.163 with SMTP id x3mr4607385oed.64.1330963636449 (num_hops = 1); Mon, 05 Mar 2012 08:07:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=fRdn5AOAqHo5d7QeUADJktMmopVip3M5JV44vti4vT4=; b=ImZPP4QIVAyPLM1cqiRT8f7TBZkaO1BRyAT8OQOVIsbdApUMFHE+qBr9Zm8GGjo5i6 u6fcPzXAKMdCg9DM6N9VWupIfMSuUZN9wXgjV1A+l5T22iB4DbFG82sDl7kb2nIHOg6x fccwClwjr0poX++smpygSOpCBcSp+EMHIDdgeiMZAA/O6NvEmn7YGchK3kJ52+yPE1ve P85TqWh52kwMM4SCq8fsupxjcVAqrpYyS1AoCV6qPdpz6j0inUacCRkjwMNh1tVHjb0o VOa5Xh9r/X8MFslfh1fKXyUmZsAWl0TdwXN95UHqZt4tisi+GOFcdGb+pwjnF6O6dhk8 2ezw==
MIME-Version: 1.0
Received: by 10.60.18.163 with SMTP id x3mr4118346oed.64.1330963636404; Mon, 05 Mar 2012 08:07:16 -0800 (PST)
Sender: barryleiba@gmail.com
Received: by 10.60.125.37 with HTTP; Mon, 5 Mar 2012 08:07:16 -0800 (PST)
In-Reply-To: <01OCQZFYBOQA00ZUIL@mauve.mrochek.com>
References: <20120301004219.15266.76505.idtracker@ietfa.amsl.com> <CAC4RtVDeXwCLh9R_bNmLwEC5g_4Dv9HadOpXMwbSz5RT2m+jUg@mail.gmail.com> <CAC4RtVB1G_HjYNug0Fvq7LPSnzqG2KxH-PY6nv=nBZKv-uXTLA@mail.gmail.com> <01OCM8WDJZKI00ZUIL@mauve.mrochek.com> <4F54C9B1.4010100@isode.com> <CALaySJJUE02R7NP08HB-Si7vOZHRg28vtKqLF9Y45=6d43QHdA@mail.gmail.com> <01OCQZFYBOQA00ZUIL@mauve.mrochek.com>
Date: Mon, 5 Mar 2012 11:07:16 -0500
X-Google-Sender-Auth: rjqpTCqVnCJVCnwriYUlBxmecPE
Message-ID: <CALaySJJ1CJSPFEh3MfdGCP=FeuiM7Gvzf9MU0F_83qtbWcazew@mail.gmail.com>
Subject: Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard
From: Barry Leiba <barryleiba@computer.org>
To: Ned Freed <ned.freed@mrochek.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: Pete Resnick <presnick@qualcomm.com>, Alexey Melnikov <alexey.melnikov@isode.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Mar 2012 16:07:17 -0000

>> =A0 =A0Other message header fields, such as Importance [RFC2156], Priori=
ty
>> =A0 =A0[RFC2156] and X-Priority, are used inconsistently and often with
>> =A0 =A0different semantics from MT-Priority. =A0Message Submission Agent=
s
>> =A0 =A0[RFC6409] MAY use such fields to assign an initial priority in th=
e
>> =A0 =A0absence of an SMTP PRIORITY parameter. =A0Otherwise, such fields
>> =A0 =A0MUST NOT be used for determining the priority under this "Priorit=
y
>> =A0 =A0Message Handling" SMTP extension.
>
> It seems you're complaining about other people doing something they never
> wanted to do while actually making that error yourself.

I have no idea what you mean, so perhaps you can be more specific
about what it is that you want to do.

Barry

From sm@resistor.net  Mon Mar  5 08:30:07 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 D3E1D21F87E3 for <ietf@ietfa.amsl.com>; Mon,  5 Mar 2012 08:30:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.645
X-Spam-Level: 
X-Spam-Status: No, score=-102.645 tagged_above=-999 required=5 tests=[AWL=-0.046, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i-8-YcYwpcFY for <ietf@ietfa.amsl.com>; Mon,  5 Mar 2012 08:30:05 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id B1A8621F87DD for <ietf@ietf.org>; Mon,  5 Mar 2012 08:30:05 -0800 (PST)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id q25GU0TK019929; Mon, 5 Mar 2012 08:30:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1330965005; i=@resistor.net; bh=q5OQgRSPnUw/WOZ+DmUmRGdn12/0+lm8owjPgKkUQrA=; h=Message-Id:Date:To:From:Subject:Cc:In-Reply-To:References: Mime-Version:Content-Type; b=kMJp+5+pPKf18ZCxYM0O2lvoOhyOrg9oK08l1zywhh1rH+CdpkEAE6c20EM/6p6PS ySJSVkZisszBB3G2c8a2CdxT1ZXC5OOOCrswPzNVBUbTV6D6IX/P7RTzJLdL5Ti94j 7t/BxhQhMvEk1F/i1c05JIZjeIKQANUhQpNmqA8U=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1330965005; i=@resistor.net; bh=q5OQgRSPnUw/WOZ+DmUmRGdn12/0+lm8owjPgKkUQrA=; h=Message-Id:Date:To:From:Subject:Cc:In-Reply-To:References: Mime-Version:Content-Type; b=LOKQy96Ac2rUzxmZdBZmX4XwR203ADESp0LD3n5poeSgRcEZbag1W4jyVm8mIhNUb scTXcfaMGFCcEf6Jy4Uwf/gMyFFU3RtGhTGonsHs0al9K49keCRlRpWxvuicORtrDo 9ZR98ppM2L158lLSnUpxeb5r/yo8Yq6hSoD3Nnuw=
Message-Id: <6.2.5.6.2.20120305073616.0b531000@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 05 Mar 2012 08:30:00 -0800
To: ietf@ietf.org
From: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard
In-Reply-To: <20120303041153.23749.qmail@joyce.lan>
References: <CAC4RtVA3F8gsBWY65W5KNDE+408EvtP+hp5GTzLg4FMgC1bdcQ@mail.gmail.com> <20120303041153.23749.qmail@joyce.lan>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: Alexey Melnikov <alexey.melnikov@isode.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Mar 2012 16:30:07 -0000

At 20:11 02-03-2012, John Levine wrote:
>So I have two suggestions.  One is to leave it as is, and make it
>experimental. If it turns out the tunnels all work the same way, you
>can come back and add the spec about how they work and rev it as
>standards track.  The other is to take out the tunnel bit and make it
>standards track now, so a compliant implementation needs
>priority-aware MTAs from end to end.  Even if you take out the tunnel
>stuff in the spec, you can still tunnel in your implementations, using
>whatever non-standard ad hoc kludges you want.  Since the current spec
>has gaps that would need to be filled by non-standard ad hoc kludges
>anyway, you haven't lost anything.

Here's the other side of the coin.

A careful review of the draft would show that the authors thought 
about the idea very carefully and they have good specification and 
implementation experience.  The easy path would be to make this Experimental.

As John Levine mentioned above, there is an alternative to get this 
on the standards track.  The specification could be in three parts, 
one for the SMTP extension, the second for the header field, and the 
last one is about how the technologies are applied.  I didn't think 
about the alternative when I went through -04.

Most of the text from Section 12 would go into the third part.   I 
wouldn't go too much into trust; it may be easier to make use of 
local policy or "use cases".  If I am not mistaken, the old version 
of the proposal used that approach.  Bullets 2 and 3 of Section 4.2 
and bullet 2 of Section 4.4 could be moved to the third part, 
together with the note in bullet 1 of Section 4.3.   The header 
restriction for a MSA is permitted through compliance with site 
policy (Section 12).  Getting into S/MIME entails having to deal with 
outer and inner headers.  It's easier not to get into that.

Regards,
-sm  


From patrik@frobbit.se  Sat Mar  3 15:23:19 2012
Return-Path: <patrik@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 600D021F8631 for <ietf@ietfa.amsl.com>; Sat,  3 Mar 2012 15:23:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.301
X-Spam-Level: 
X-Spam-Status: No, score=-101.301 tagged_above=-999 required=5 tests=[AWL=-0.398, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, MIME_QP_LONG_LINE=1.396, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YAzl+Bj8kkCM for <ietf@ietfa.amsl.com>; Sat,  3 Mar 2012 15:23:00 -0800 (PST)
Received: from srv01.frobbit.se (srv01.frobbit.se [IPv6:2a02:80:3ffe::39]) by ietfa.amsl.com (Postfix) with ESMTP id 6B7C421F8627 for <ietf@ietf.org>; Sat,  3 Mar 2012 15:23:00 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by srv01.frobbit.se (Postfix) with ESMTP id 34628133856A2; Sun,  4 Mar 2012 00:22:58 +0100 (CET)
X-Virus-Scanned: amavisd-new at frobbit.se
Received: from srv01.frobbit.se ([127.0.0.1]) by localhost (srv01.frobbit.se [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wVpRwnPI3GZK; Sun,  4 Mar 2012 00:22:57 +0100 (CET)
Received: from [192.168.1.2] (unknown [128.127.186.196]) (Authenticated sender: paf01) by srv01.frobbit.se (Postfix) with ESMTP id 68D411338569B; Sun,  4 Mar 2012 00:22:57 +0100 (CET)
References: <20120228015606.2227.qmail@joyce.lan> <01OCO724C8RI00ZUIL@mauve.mrochek.com> <4BFFCC4E-BDF2-40D1-A452-F37DE2A43FD5@frobbit.se> <28932822.UOiERLMsQ1@scott-latitude-e6320>
In-Reply-To: <28932822.UOiERLMsQ1@scott-latitude-e6320>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=us-ascii
Message-Id: <13872505-949E-4C98-A945-28510E344201@frobbit.se>
X-Mailer: iPhone Mail (9A405)
From: =?utf-8?Q?Patrik_F=C3=A4ltstr=C3=B6m?= <patrik@frobbit.se>
Subject: Re: provisioning software, was DNS RRTYPEs, the difficulty with
Date: Sun, 4 Mar 2012 00:22:05 +0100
To: Scott Kitterman <scott@kitterman.com>
X-Mailman-Approved-At: Mon, 05 Mar 2012 08:59:35 -0800
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, 03 Mar 2012 23:23:19 -0000

On 3 mar 2012, at 17:29, Scott Kitterman <scott@kitterman.com> wrote:

> Sometimes an ASCII text record will be fine, in other cases, it probably w=
on't.

My point is as we move again towards multiple text representations of "the d=
igit five" for example, both encoding and parsing is easier and more secure i=
f that digit is really for example eight bits and not "text" that someone ha=
s to parse.

   Patrik=

From johnl@iecc.com  Mon Mar  5 09:10:09 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 9C96221F882D for <ietf@ietfa.amsl.com>; Mon,  5 Mar 2012 09:10:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.514
X-Spam-Level: 
X-Spam-Status: No, score=-110.514 tagged_above=-999 required=5 tests=[AWL=0.685, 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 FRWfTjVgxCZx for <ietf@ietfa.amsl.com>; Mon,  5 Mar 2012 09:10:08 -0800 (PST)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 8F35421F8803 for <ietf@ietf.org>; Mon,  5 Mar 2012 09:10:01 -0800 (PST)
Received: (qmail 15915 invoked from network); 5 Mar 2012 17:10:00 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 5 Mar 2012 17:10:00 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=4f54f368.xn--30v786c.k1203; i=johnl@user.iecc.com; bh=3+PXfGpZ+QdZ77AJ0wk0cZjPHCXDoVLT8jQcv/YFb5g=; b=JeRdae9Of/0zR88Rd7IbkOd7JXhTmbdD3jmCLBaaAo8gtfzZM2tscqb7uQzQKeVgN1sdWQAdKbfxp88aKPPS69Zu+qcy0TPmpA5SEAzj5bNC+f6WLPtDhk9Dz0jv/QRpkUjtpsr/OPaW2RRZaUKnAJt7DGv2y5VWjh5ZjJMnpw8=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 5 Mar 2012 17:09:38 -0000
Message-ID: <20120305170938.57919.qmail@joyce.lan>
From: "John Levine" <johnl@iecc.com>
To: ietf@ietf.org
Subject: Re: provisioning software, was DNS RRTYPEs, the difficulty with
In-Reply-To: <13872505-949E-4C98-A945-28510E344201@frobbit.se>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
Cc: patrik@frobbit.se
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Mar 2012 17:10:10 -0000

>> Sometimes an ASCII text record will be fine, in other cases, it probably won't.
>
>My point is as we move again towards multiple text representations of "the digit five" for example,
>both encoding and parsing is easier and more secure if that digit is really for example eight bits
>and not "text" that someone has to parse.

Unless you provision your DNS zones with a hex debugger, the digit
will always start out as text that someone has to parse.  The question
is who does the parsing, the DNS server or the application.  As I said
in a previous message, I can see plausible reasons to put the parser into
the application.

Would you really want to build an SPF or DKIM parser into every DNS
server?  That's a lot of code that the DNS manager doesn't care about,
but the mail manager does.

R's,
John

PS: For anyone who didn't read my previous message, I am NOT saying
that it's fine to overload everything into TXT.  I am saying that new
RRTYPEs that are text blobs interpreted by client software wouldn't
necessarily be bad.



From msk@cloudmark.com  Mon Mar  5 10:00:16 2012
Return-Path: <msk@cloudmark.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 408D221F87D6 for <ietf@ietfa.amsl.com>; Mon,  5 Mar 2012 10:00:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.604
X-Spam-Level: 
X-Spam-Status: No, score=-102.604 tagged_above=-999 required=5 tests=[AWL=-0.005, 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 5aR4hTAmg75g for <ietf@ietfa.amsl.com>; Mon,  5 Mar 2012 10:00:14 -0800 (PST)
Received: from ht1-outbound.cloudmark.com (ht1-outbound.cloudmark.com [72.5.239.25]) by ietfa.amsl.com (Postfix) with ESMTP id 3BB1621F87D4 for <ietf@ietf.org>; Mon,  5 Mar 2012 10:00:14 -0800 (PST)
Received: from EXCH-MBX901.corp.cloudmark.com ([fe80::addf:849a:f71c:4a82]) by EXCH-HTCAS901.corp.cloudmark.com ([fe80::2966:6846:8d89:4681%12]) with mapi id 14.01.0355.002; Mon, 5 Mar 2012 10:00:12 -0800
From: "Murray S. Kucherawy" <msk@cloudmark.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities)         to Proposed Standard
Thread-Topic: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities)         to Proposed Standard
Thread-Index: AQHM+sdxXMzPJQgaA0uPAlCVYyU+45Zb/ODQ
Date: Mon, 5 Mar 2012 18:00:12 +0000
Message-ID: <9452079D1A51524AA5749AD23E00392807ABA1@exch-mbx901.corp.cloudmark.com>
References: <20120301004219.15266.76505.idtracker@ietfa.amsl.com> <9452079D1A51524AA5749AD23E00392806E6F5@exch-mbx901.corp.cloudmark.com> <4F54AAB7.5000703@isode.com>
In-Reply-To: <4F54AAB7.5000703@isode.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.20.2.121]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Mar 2012 18:00:16 -0000

> -----Original Message-----
> From: Alexey Melnikov [mailto:alexey.melnikov@isode.com]
> Sent: Monday, March 05, 2012 4:00 AM
> To: Murray S. Kucherawy
> Cc: ietf@ietf.org
> Subject: Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple
> Mail Transfer Protocol extension for Message Transfer Priorities) to
> Proposed Standard
>=20
> > - There's a bunch of TBDs that still need to be resolved before this
> > document moves forward (X.7.TBD3 as an enhanced status code, for
> > example)
>=20
> No, these are assigned by IANA before publication. RFC Editor will fix
> these.

OK, I've just never seen that approach taken before.

> > - Section 4.3 says "For example, once an MTA accepts a message, the
> MTA MUST NOT change a (syntactically valid) priority value if the MTA
> doesn't support it."  There seems to be a chicken-and-egg going on
> here: If the MTA doesn't support the extension, how can it know not to
> change the priority outbound?
>=20
> I meant "supports the extension, but doesn't support a particular value
> as distinct priority level". Suggestions on how to make this clear
> would be appreciated.

Suggest:

For example, once an MTA accepts a message, the MTA MUST not change a (synt=
actically valid) priority value if that value is not supported by the MTA's=
 implementation of this extension.

> > - There are lots of SHOULDs in here that might benefit from example
> > situations in which one might deviate from the normative statement
> > containing the SHOULD.
>
> I will review. I had some discussion with SM about some of these and
> argued that not all of them should be explained. But I agree that some
> of them need explanation.

There are some that are in more need of this than others, and I know lately=
 that I've been thanked by ADs during IESG evaluation for providing this ki=
nd of text, so it can only help where it's possible to provide it.

> > - Section 5 and Section 5.1 use "not required", "should", and "may"
> > where RFC2119 is cited earlier.  Should they be in all-caps, or should
> > other language be selected?
>=20
> Lowercased versions are not used in normative sense. Maybe a note
> suggested by Barry would help with this.

Sure, and I sympathize with your reply that it triggers an ID nit.  I wonde=
r if the IESG could agree on some text like what Barry suggested and add it=
 to the ID nit checker as a valid exception.  Maybe 2119 should also be upd=
ated accordingly.

> > - Section 11: Why use "PRI" and not "priority"?  The existing set of
> > Received clause names are lowercase words, so it seems strange to
> > deviate.
>=20
> I don't mind to switching to "PRIORITY". But section 4.4 of RFC 5321
> uses uppercase variants (and yes, I know they are case insensitive).

I don't think I've ever seen them in the wild, which is why it caught my at=
tention.

> > - Appendix D: "This appendix and its subsections are informative."  I
> > think that (a) any appendix is informative, because normative text
> > doesn't belong in an appendix; and (b) the normative stuff uses
> > RFC2119 language and this doesn't.  Thus, I think this sentence
> > should be removed.  (I know I've lost this argument before, but I'll ma=
ke
> > another stand here anyway.)
>=20
> I think other people already commented on this :-)

Those people are also no longer on my Christmas list.  :-)

Thanks,
-MSK


From vesely@tana.it  Mon Mar  5 11:01:59 2012
Return-Path: <vesely@tana.it>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4670B21F88B1 for <ietf@ietfa.amsl.com>; Mon,  5 Mar 2012 11:01:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.651
X-Spam-Level: 
X-Spam-Status: No, score=-4.651 tagged_above=-999 required=5 tests=[AWL=0.068,  BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tv1X8FkWuuty for <ietf@ietfa.amsl.com>; Mon,  5 Mar 2012 11:01:58 -0800 (PST)
Received: from wmail.tana.it (www.tana.it [62.94.243.226]) by ietfa.amsl.com (Postfix) with ESMTP id 5737B21F88AE for <ietf@ietf.org>; Mon,  5 Mar 2012 11:01:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=test; t=1330974113; bh=GizgJuUPM1wWoN+737Efbjrg6BcIrnPiqbW6xPaQDwk=; l=1737; h=Message-ID:Date:From:MIME-Version:To:References:In-Reply-To: Content-Transfer-Encoding; b=DPyxQfZwkUBk/8xylALhzNLfcz4BZY2PmvaI0uH1NykSvO4RPZ9RgysafRIlrWsV9 72xGSEoOvnba6JzkZ4a9vEuEtakKzQ3lVPVKmIWmuwD0olk41rCibmeg3UaX0OxIsU VUjNVd/IYsEpjJLKfb56tqUU2nEjPvZAnPIzvxnA=
Received: from [172.25.197.158] (pcale.tana [172.25.197.158]) (AUTH: CRAM-MD5 515, TLS: TLS1.0,256bits,RSA_AES_256_CBC_SHA1) by wmail.tana.it with ESMTPSA; Mon, 05 Mar 2012 20:01:53 +0100 id 00000000005DC039.000000004F550DA1.00004298
Message-ID: <4F550DA1.8060304@tana.it>
Date: Mon, 05 Mar 2012 20:01:53 +0100
From: Alessandro Vesely <vesely@tana.it>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: provisioning software, was DNS RRTYPEs, the difficulty with
References: <20120305170938.57919.qmail@joyce.lan>
In-Reply-To: <20120305170938.57919.qmail@joyce.lan>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Mar 2012 19:01:59 -0000

On 05/Mar/12 18:09, John Levine wrote:
>>> Sometimes an ASCII text record will be fine, in other cases, it probably won't.
>>
>>My point is as we move again towards multiple text representations of "the digit five" for example,
>>both encoding and parsing is easier and more secure if that digit is really for example eight bits
>>and not "text" that someone has to parse.
> 
> Unless you provision your DNS zones with a hex debugger, the digit
> will always start out as text that someone has to parse.  The question
> is who does the parsing, the DNS server or the application.  As I said
> in a previous message, I can see plausible reasons to put the parser into
> the application.
> 
> Would you really want to build an SPF or DKIM parser into every DNS
> server?  That's a lot of code that the DNS manager doesn't care about,
> but the mail manager does.

But it would be the same code, most likely by the same author(s).  It
may be generic for a kind of syntax or specific for a RR type,
according to its author's convenience.  On a system that allows new RR
types without recompiling, the code would come as some sort of plugin
in both cases.

Why is it important what the DNS manager cares about?  Parsers,
including null parsers, would come with the same sub-package that
enables the new RR type definition.  Their complexity would only
matter to the people who read/maintain their sources.

> PS: For anyone who didn't read my previous message, I am NOT saying
> that it's fine to overload everything into TXT.  I am saying that new
> RRTYPEs that are text blobs interpreted by client software wouldn't
> necessarily be bad.

Agreed.  That doesn't preclude syntax checking on loading the zone,
though.

From hsantos@isdg.net  Mon Mar  5 11:19:34 2012
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0244221F87AD for <ietf@ietfa.amsl.com>; Mon,  5 Mar 2012 11:19:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.147
X-Spam-Level: 
X-Spam-Status: No, score=-2.147 tagged_above=-999 required=5 tests=[AWL=0.452,  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 U073bGbXgxuJ for <ietf@ietfa.amsl.com>; Mon,  5 Mar 2012 11:19:33 -0800 (PST)
Received: from news.winserver.com (news.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id ED93421F858E for <ietf@ietf.org>; Mon,  5 Mar 2012 11:19:32 -0800 (PST)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=1824; t=1330975166; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:Subject:To: List-ID; bh=zgYbe0mBTztwARi4uB8w0BQHsBs=; b=DFS4bjiAIQYKQrJzLl9c tdU/tnyyM51F6UsQ84saluQq/FPZK2bZjAAOgOQIxwdEp8gdOXeqzMvGWEgiLTuF m0CB/5p4gUqeSwUXggAmmp6sigUbSrSgfrPBci+QEDscdKN8SeXyQ7gRfrYwZKFt evr/d9OmRZ+Ptdm85kaA7a4=
Received: by winserver.com (Wildcat! SMTP Router v6.4.454.1) for ietf@ietf.org; Mon, 05 Mar 2012 14:19:26 -0500
Authentication-Results: dkim.winserver.com; dkim=pass header.d=beta.winserver.com header.s=tms1 header.i=beta.winserver.com;  adsp=pass policy=all author.d=isdg.net asl.d=beta.winserver.com;
Received: from opensite.winserver.com ([208.247.131.23]) by winserver.com (Wildcat! SMTP v6.4.454.1) with ESMTP id 4176998517.4276.3440; Mon, 05 Mar 2012 14:19:25 -0500
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=1824; t=1330974907; h=Received:Received: Message-ID:Date:From:Organization:Subject:To:List-ID; bh=1S0GjDj 3k1C3zkS+DKzZbl2BJ5JnkRNzdSJRhwSK59Q=; b=kNedKE9CaxD058WFSEIrcA3 ItjGHs1rdbY8udPS+2ryEF82J7LTZuXcxkz1BIXxqmtANHEaurJ9TH5pq01NWdyG aFVtvjIQCS5RdX8z58vpYjuNbIntZRW/0vnSTIJdV6H0Y+CSmK4BXkOvw9u7hRVx nBpQzYglpEXjwgt3yls0=
Received: by beta.winserver.com (Wildcat! SMTP Router v6.4.454.1) for ietf@ietf.org; Mon, 05 Mar 2012 14:15:07 -0500
Received: from [192.168.1.101] ([99.3.147.93]) by beta.winserver.com (Wildcat! SMTP v6.4.454.1) with ESMTP id 480962158.24835.364; Mon, 05 Mar 2012 14:15:06 -0500
Message-ID: <4F5511BC.7010800@isdg.net>
Date: Mon, 05 Mar 2012 14:19:24 -0500
From: Hector Santos <hsantos@isdg.net>
Organization: Santronics Software, Inc.
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
CC: ietf@ietf.org
Subject: Re: provisioning software, was DNS RRTYPEs, the difficulty with
References: <20120305170938.57919.qmail@joyce.lan> <4F550DA1.8060304@tana.it>
In-Reply-To: <4F550DA1.8060304@tana.it>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Comment: Missing recipient address appended by wcSMTP router.
To: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Mar 2012 19:19:34 -0000

Alessandro Vesely wrote:

> Why is it important what the DNS manager cares about?  Parsers,
> including null parsers, would come with the same sub-package that
> enables the new RR type definition.  Their complexity would only
> matter to the people who read/maintain their sources.

+1

>> PS: For anyone who didn't read my previous message, I am NOT saying
>> that it's fine to overload everything into TXT.  I am saying that new
>> RRTYPEs that are text blobs interpreted by client software wouldn't
>> necessarily be bad.
> 
> Agreed.  That doesn't preclude syntax checking on loading the zone,
> though.

As a Windows shop, there is no hiding of the long product development 
battles between the *nix weenies world and the WinDoze world.  At a 
general level, the WinDoze world is not one that is use to and relies 
on text based "editors" configuration, they need the GUI.  I even 
recourse getting a private message suggesting my customers must be 
"stupid."

Nonetheless, to reach critical mass, it is important the GUI is 
developed for this stuff. I can't rely on customers becoming text 
editor people if that is the only way to make this work.  They only 
way I could even begin to offer DKIM, ADSP and even now ATPS is to 
provide a GUI, like this public version we have here for ADSP and ATPS

        http://www.winserver.com/public/wcadsp

Just consider that ATPS has SHA1, BASE32 functions to produce the 
records.  That adds complexity for any DNS server manager (Windows or 
Bind) to consider. Its just not a plug and play consideration.  Its 
probably easier for the ISP Web-based managers since its more of an 
add-on to there current DNS software, using command line tools to act 
on GUI posted information.


-- 
Hector Santos, CTO
http://www.santronics.com
http://santronics.blogspot.com



From barryleiba.mailing.lists@gmail.com  Mon Mar  5 11:41:00 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 7D76021F8927 for <ietf@ietfa.amsl.com>; Mon,  5 Mar 2012 11:41:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.986
X-Spam-Level: 
X-Spam-Status: No, score=-102.986 tagged_above=-999 required=5 tests=[AWL=-0.009, 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 J1nLKGTqnbNq for <ietf@ietfa.amsl.com>; Mon,  5 Mar 2012 11:40:59 -0800 (PST)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by ietfa.amsl.com (Postfix) with ESMTP id BF05C21F891A for <ietf@ietf.org>; Mon,  5 Mar 2012 11:40:57 -0800 (PST)
Received: by yenm5 with SMTP id m5so2088631yen.31 for <ietf@ietf.org>; Mon, 05 Mar 2012 11:40:57 -0800 (PST)
Received-SPF: pass (google.com: domain of barryleiba.mailing.lists@gmail.com designates 10.101.142.4 as permitted sender) client-ip=10.101.142.4; 
Authentication-Results: mr.google.com; spf=pass (google.com: domain of barryleiba.mailing.lists@gmail.com designates 10.101.142.4 as permitted sender) smtp.mail=barryleiba.mailing.lists@gmail.com; dkim=pass header.i=barryleiba.mailing.lists@gmail.com
Received: from mr.google.com ([10.101.142.4]) by 10.101.142.4 with SMTP id u4mr8842776ann.60.1330976457492 (num_hops = 1); Mon, 05 Mar 2012 11:40:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=78JqNhM7n445Elom5Zi97G/GcCCkPPl+UWeitr5SzNk=; b=KLpqsjwUqjcnbSBFEJZAtJxoHr0meRvHRHq3BnuyQkdxpvflC9JFekvPgugqaUgJB8 6zVzeVoFZa4mND0hg4l9jWDefq27TYjXZdOqA3EH2xjig5FlSXXetmfkle7N4nR9TDdo 2RHysXHbgvOhJzOFa/V03VWxx/zYv4p/BRXsmIzos4ZF0iGktZefQmss7whVV7+fRZbK jLibRozEeuHgaZ8tbiBAvAw3cGqq4Q5O09GXVAkqNTAAlQ2i3vZBecsDPVAn+z5rs9U7 idhvXXkE7Mzs2kFeAiFgyWGVSTlWX8qG8ghPDIpvt6DGNp1YRuvlMH7xB4jj5dg7gNbM tWDA==
MIME-Version: 1.0
Received: by 10.101.142.4 with SMTP id u4mr6968194ann.60.1330976457429; Mon, 05 Mar 2012 11:40:57 -0800 (PST)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.147.106.16 with HTTP; Mon, 5 Mar 2012 11:40:57 -0800 (PST)
In-Reply-To: <4F549FC0.1060609@isode.com>
References: <20120301004219.15266.76505.idtracker@ietfa.amsl.com> <CAC4RtVDeXwCLh9R_bNmLwEC5g_4Dv9HadOpXMwbSz5RT2m+jUg@mail.gmail.com> <4F549FC0.1060609@isode.com>
Date: Mon, 5 Mar 2012 14:40:57 -0500
X-Google-Sender-Auth: 9posJXoQOe4PdDx41A_mW6KTG0o
Message-ID: <CAC4RtVDzvaY0uF6oEVaK_HK_DuS8YyaJbUni25M6TG5uudSLuA@mail.gmail.com>
Subject: Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard
From: Barry Leiba <barryleiba@computer.org>
To: Alexey Melnikov <alexey.melnikov@isode.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: Pete Resnick <presnick@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: Mon, 05 Mar 2012 19:41:00 -0000

>> 2. I, too, noticed all the lower-case "should" and "may" words. =A0I
>> suggest that the best way to handle this is to make the following
>> change to the RFC 2119 citation text at the beginning of section 2:
>>
>> NEW
>> =A0 =A0The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT=
",
>> =A0 =A0"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in t=
his
>> =A0 =A0document are to be interpreted as described in [RFC2119] when the=
y
>> appear
>> =A0 =A0in ALL CAPS. =A0These words also appear in this document in lower=
 case as
>> plain
>> =A0 =A0English words, absent their normative meanings.
>
> I don't mind changing that, but ID-nits gives a warning when the text abo=
ut
> keywords is changed and *everybody* likes to complain about that. Please
> talk to IESG about whether using a variant of the standard text is
> acceptable.

I've used text like this before, and the IESG has never objected to
it.  One advantage with this formulation, which uses the standard 2119
text and *appends* to it, is that idnits likes it and doesn't generate
a warning.

Barry

From agmalis@gmail.com  Mon Mar  5 15:54:29 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 62E2421E8068 for <ietf@ietfa.amsl.com>; Mon,  5 Mar 2012 15:54:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.513
X-Spam-Level: 
X-Spam-Status: No, score=-3.513 tagged_above=-999 required=5 tests=[AWL=0.086,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AwXZXjwlkOzt for <ietf@ietfa.amsl.com>; Mon,  5 Mar 2012 15:54:28 -0800 (PST)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id D72EF21E804A for <ietf@ietf.org>; Mon,  5 Mar 2012 15:54:26 -0800 (PST)
Received: by iazz13 with SMTP id z13so7269526iaz.31 for <ietf@ietf.org>; Mon, 05 Mar 2012 15:54:25 -0800 (PST)
Received-SPF: pass (google.com: domain of agmalis@gmail.com designates 10.42.145.72 as permitted sender) client-ip=10.42.145.72; 
Authentication-Results: mr.google.com; spf=pass (google.com: domain of agmalis@gmail.com designates 10.42.145.72 as permitted sender) smtp.mail=agmalis@gmail.com; dkim=pass header.i=agmalis@gmail.com
Received: from mr.google.com ([10.42.145.72]) by 10.42.145.72 with SMTP id e8mr2216393icv.0.1330991665251 (num_hops = 1); Mon, 05 Mar 2012 15:54:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=MaAMQ2fegs/zm1M3OyFr927jwRvNLNDokrJAcf3G+TY=; b=VcVgyWz7haj4j98TQho95oIepMR+j4WAvblUy1nuA7LO9ktvJYAu89vb1id01CVV1U YscSJBU6ML9yivEzyAqqfDd4fu/nYt4XZgNYjFFuMmwtD9ghDzw1DhFkUbMKruL4Gswz jN3oMHgJdrHPXoUdME2CTFUK9ld3cU2A+3fyhX/cvU5TuvBqOHvShXR/+6ywtWZGuStB THKWqAbdBoKhLJYPSweqeatDWp/+tI4hb/Y3/Xki0Ex5d647GX8ZF3woNqqMbkGNlXXs b7w8DKA+0DNFLAgEI0O0xOh3YZ8oIeeJG2/k+N1UkwIy9St6FusnVu1XWNzy565rrj8K nGFg==
Received: by 10.42.145.72 with SMTP id e8mr1829951icv.0.1330991665133; Mon, 05 Mar 2012 15:54:25 -0800 (PST)
MIME-Version: 1.0
Received: by 10.50.222.136 with HTTP; Mon, 5 Mar 2012 15:54:05 -0800 (PST)
In-Reply-To: <E4873516F3FC7547BCFE792C7D94039C015D118B@DEMUEXC013.nsn-intra.net>
References: <20120222151252.32262.82157.idtracker@ietfa.amsl.com> <03a301ccf174$ff953290$febf97b0$@olddog.co.uk> <515703B08A3A064C9CC8C09ACCC710DC0631679E@XMB-RCD-103.cisco.com> <E4873516F3FC7547BCFE792C7D94039C015D117D@DEMUEXC013.nsn-intra.net> <E4873516F3FC7547BCFE792C7D94039C015D118B@DEMUEXC013.nsn-intra.net>
From: "Andrew G. Malis" <agmalis@gmail.com>
Date: Mon, 5 Mar 2012 15:54:05 -0800
Message-ID: <CAA=duU21qzU3s4xPhPH-0_V7buteVXPo5Kx5m2iu5+7F8qu28A@mail.gmail.com>
Subject: Re: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt>(Allocationof an Associated Channel Code Point for Use byITU-T Ethernetbased OAM) to Informational RFC
To: "Sprecher, Nurit (NSN - IL/Hod HaSharon)" <nurit.sprecher@nsn.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Mar 2012 23:54:29 -0000

I would like to support Nurit's comments below. In particular, in the
past the ITU-T has expanded upon or changed the usage of IETF
codepoint allocations, in some cases incompatibly with its original
usage or definition. In the future, all codepoint allocations to the
ITU-T should be tied to one specific, dated revision of their
specification only. This is similar to the ITU-T's own processes, such
as section 2.2.1 of Rec. A.5, which requires a version number and/or
date for referenced outside documents in ITU-T recommendations.

Cheers,
Andy

On Thu, Mar 1, 2012 at 7:20 AM, Sprecher, Nurit (NSN - IL/Hod
HaSharon) <nurit.sprecher@nsn.com> wrote:
> Hi,
>
>
>
> I cannot support the publication of the document in its current version.
>
>
>
> I have the following concerns:
>
>
>
> =95=A0=A0=A0=A0=A0=A0=A0 It is indicated that the channel is intended to =
be used to carry
> Ethernet based OAM messages. It is not clear why there is a need for ACH.
> PWs can be used to transmit Ethernet OAM.
>
> If the intention is to use the channel for OAM messages for operating
> MPLS-TP based networks, the IETF *already* defined a solution for MPLS-TP
> OAM and I expect to see first a technical *justification* why a second
> solution is needed. In addition, I would expect to see *references to the
> arguments* raised in draft-sprecher-mpls-tp-oam-considerations.
>
>
>
> =95=A0=A0=A0=A0=A0=A0=A0 It is not clear what the maturity status of G.81=
13.1 is. It seems
> that the document was not approved by SG15 and the discussion was deferre=
d
> to WTSA. This indicates that there is *no consensus* for the approval of
> G.8113.1. A code point should not be allocated before a consensus/decisio=
n
> is reached in the ITU-T and before the document is mature and approved. I=
 do
> not think it is appropriate to allocate a code point and try to force a
> resolution in the ITU-T.
>
>
>
> =95=A0=A0=A0=A0=A0=A0=A0 I find a contradiction in the draft. In one plac=
e it is mentioned:
> "These Ethernet based OAM messages and procedures, address the OAM
> functional requirements defined in [RFC5860]. Other message types should =
not
> be carried behind this code point." In another place it is mentioned: "al=
l
> ITU-T Recommendations are subject to revision. Therefore, the code point
> allocated by this document may be used for future versions of [G.8113.1].=
".
> The last statement opens the door for the definition of additional messag=
es
> in G.8113.1 in the following versions, for example, for APS (supporting
> linear or ring protection mechanisms) and by this creates two solutions f=
or
> other mechanisms as well.
>
>
>
> The use of the code point can go much beyond its original purpose and it
> will hide other messages....a code point should not be allocated at this
> point at all, but specifically not for unknown usage that may be defined =
in
> future versions of G.8113.1.
>
>
>
> Best regards,
>
> Nurit
>
>
>
>
>
>
>
>> -----Original Message-----
>
>> From: ietf-announce-bounces@ietf.org [mailto:ietf-announce-
>
>> bounces@ietf.org] On Behalf Of The IESG
>
>> Sent: 22 February 2012 15:13
>
>> To: IETF-Announce
>
>> Subject: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt>
>
> (Allocation of
>
> an
>
>> Associated Channel Code Point for Use by ITU-T Ethernet based OAM) to
>
>> Informational RFC
>
>>
>
>>
>
>> The IESG has received a request from an individual submitter to
>
> consider
>
>> the following document:
>
>> - 'Allocation of an Associated Channel Code Point for Use by ITU-T
>
>>=A0=A0=A0 Ethernet based OAM'
>
>>=A0=A0 <draft-betts-itu-oam-ach-code-point-03.txt> as an Informational RF=
C
>
>>
>
>> 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-03-21. 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
>
>>
>
>>=A0=A0=A0 This document assigns an Associated Channel Type code point for
>
>>=A0=A0=A0 carrying Ethernet based Operations, Administration, and Managem=
ent
>
>>=A0=A0=A0 messages in the MPLS Generic Associated Channel (G-ACh).
>
>>
>
>> The file can be obtained via
>
>> http://datatracker.ietf.org/doc/draft-betts-itu-oam-ach-code-point/
>
>>
>
>> IESG discussion can be tracked via
>
>> http://datatracker.ietf.org/doc/draft-betts-itu-oam-ach-code-point/
>
>>
>
>>
>
>> No IPR declarations have been submitted directly on this I-D.
>
>> _______________________________________________
>
>> IETF-Announce mailing list
>
>> IETF-Announce@ietf.org
>
>> https://www.ietf.org/mailman/listinfo/ietf-announce
>
>
>
> _______________________________________________
>
> mpls mailing list
>
> mpls@ietf.org
>
> https://www.ietf.org/mailman/listinfo/mpls
>
> _______________________________________________
>
> Ietf mailing list
>
> Ietf@ietf.org
>
> https://www.ietf.org/mailman/listinfo/ietf
>
> _______________________________________________
>
> Ietf mailing list
>
> Ietf@ietf.org
>
> https://www.ietf.org/mailman/listinfo/ietf
>
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>

From ned+ietf@mauve.mrochek.com  Mon Mar  5 18:24:52 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 3DA1521F855B for <ietf@ietfa.amsl.com>; Mon,  5 Mar 2012 18:24:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.589
X-Spam-Level: 
X-Spam-Status: No, score=-2.589 tagged_above=-999 required=5 tests=[AWL=0.010,  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 GNKlgMH+nmxL for <ietf@ietfa.amsl.com>; Mon,  5 Mar 2012 18:24:51 -0800 (PST)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id 7E4CE21F8559 for <ietf@ietf.org>; Mon,  5 Mar 2012 18:24:51 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OCRLEN0YHS00YGJG@mauve.mrochek.com> for ietf@ietf.org; Mon, 5 Mar 2012 18:24:47 -0800 (PST)
MIME-version: 1.0
Content-type: TEXT/PLAIN; charset=iso-8859-1
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OCPMUVDUMO00ZUIL@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Mon, 5 Mar 2012 18:24:40 -0800 (PST)
From: ned+ietf@mauve.mrochek.com
Message-id: <01OCRLEJG1VA00ZUIL@mauve.mrochek.com>
Date: Mon, 05 Mar 2012 18:24:01 -0800 (PST)
Subject: Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to	Proposed Standard
In-reply-to: "Your message dated Mon, 05 Mar 2012 14:40:57 -0500" <CAC4RtVDzvaY0uF6oEVaK_HK_DuS8YyaJbUni25M6TG5uudSLuA@mail.gmail.com>
References: <20120301004219.15266.76505.idtracker@ietfa.amsl.com> <CAC4RtVDeXwCLh9R_bNmLwEC5g_4Dv9HadOpXMwbSz5RT2m+jUg@mail.gmail.com> <4F549FC0.1060609@isode.com> <CAC4RtVDzvaY0uF6oEVaK_HK_DuS8YyaJbUni25M6TG5uudSLuA@mail.gmail.com>
To: Barry Leiba <barryleiba@computer.org>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mrochek.com; s=mauve; t=1331000694; i=@mrochek.com; bh=BRizoXHRpUTrtVJw56OT2xRJtjZ50Kpb2wvaFYhKfAs=;  h=MIME-version:Content-type:From:Cc:Message-id:Date:Subject: In-reply-to:References:To; b=Qqo8d0+u7QauALe9hckgoDFjCqqZkV7soIOm7fUJKM1OCCd2ug1qGxx3MepsLK8Ap Z/LnU5U6POhVWTcvoEPWWTfye9L+1BWlMrUoFgIBP3G8KjcUtkTpFF4++ZFKHeYzru jWTmh4R5bj/bCfjecyj+gpWi915ABw37tKLdWh6o=
Cc: Pete Resnick <presnick@qualcomm.com>, Alexey Melnikov <alexey.melnikov@isode.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Mar 2012 02:24:52 -0000

> >> 2. I, too, noticed all the lower-case "should" and "may" words.  I
> >> suggest that the best way to handle this is to make the following
> >> change to the RFC 2119 citation text at the beginning of section 2:
> >>
> >> NEW
> >>    The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
> >>    "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
> >>    document are to be interpreted as described in [RFC2119] when they
> >> appear
> >>    in ALL CAPS.  These words also appear in this document in lower case as
> >> plain
> >>    English words, absent their normative meanings.
> >
> > I don't mind changing that, but ID-nits gives a warning when the text about
> > keywords is changed and *everybody* likes to complain about that. Please
> > talk to IESG about whether using a variant of the standard text is
> > acceptable.

> I've used text like this before, and the IESG has never objected to
> it.  One advantage with this formulation, which uses the standard 2119
> text and *appends* to it, is that idnits likes it and doesn't generate
> a warning.

More generally, ID-nits is supposed to be helpful. Straightjackets are not
helpful.

				Ned

From barryleiba.mailing.lists@gmail.com  Mon Mar  5 18:30:18 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 B50F621F85F3 for <ietf@ietfa.amsl.com>; Mon,  5 Mar 2012 18:30:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.986
X-Spam-Level: 
X-Spam-Status: No, score=-102.986 tagged_above=-999 required=5 tests=[AWL=-0.009, 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 NOE6vckcz+I2 for <ietf@ietfa.amsl.com>; Mon,  5 Mar 2012 18:30:18 -0800 (PST)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id 1078821F84A7 for <ietf@ietf.org>; Mon,  5 Mar 2012 18:30:18 -0800 (PST)
Received: by ggmi1 with SMTP id i1so2267510ggm.31 for <ietf@ietf.org>; Mon, 05 Mar 2012 18:30:17 -0800 (PST)
Received-SPF: pass (google.com: domain of barryleiba.mailing.lists@gmail.com designates 10.236.180.193 as permitted sender) client-ip=10.236.180.193; 
Authentication-Results: mr.google.com; spf=pass (google.com: domain of barryleiba.mailing.lists@gmail.com designates 10.236.180.193 as permitted sender) smtp.mail=barryleiba.mailing.lists@gmail.com; dkim=pass header.i=barryleiba.mailing.lists@gmail.com
Received: from mr.google.com ([10.236.180.193]) by 10.236.180.193 with SMTP id j41mr30073741yhm.55.1331001017695 (num_hops = 1); Mon, 05 Mar 2012 18:30:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=BTusdhmBRmQlVsq8usQaVYxK145QsfRCdCpjiHkCpBM=; b=OGGH5ObR0brQmkavPvkbWZQ+4dNYo77YOq9k4tLQ10kAWfb0p0VJ/vjAUDnOQR6uV7 zA34pttEfIBCbYPDvTq2rKeIXWWEp/5JxTnXXUv8VeD9tOR7giSLFOEPjj4fUG94JY/7 7CxiVz33evjf6KgPC3lm5QGZdsy+NfQY4i9InshpTAnfVt0JLYKU8CaVHUGr4wdS5Ezh ndP8Slio5YgQOfET0I/JUveMPzTBzZziCRJtdkGXiAuT0jiatXomp+HEm7fq1GQKt4Sj X3F6TyMKBrl5WRWkTl9YlXp90QN/1bRKQFt3oGO0AvzM/XRU2E0dg/VDfYG6Ts1E0I64 hTLQ==
MIME-Version: 1.0
Received: by 10.236.180.193 with SMTP id j41mr23744335yhm.55.1331001017654; Mon, 05 Mar 2012 18:30:17 -0800 (PST)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.147.106.16 with HTTP; Mon, 5 Mar 2012 18:30:17 -0800 (PST)
In-Reply-To: <01OCRLEJG1VA00ZUIL@mauve.mrochek.com>
References: <20120301004219.15266.76505.idtracker@ietfa.amsl.com> <CAC4RtVDeXwCLh9R_bNmLwEC5g_4Dv9HadOpXMwbSz5RT2m+jUg@mail.gmail.com> <4F549FC0.1060609@isode.com> <CAC4RtVDzvaY0uF6oEVaK_HK_DuS8YyaJbUni25M6TG5uudSLuA@mail.gmail.com> <01OCRLEJG1VA00ZUIL@mauve.mrochek.com>
Date: Mon, 5 Mar 2012 21:30:17 -0500
X-Google-Sender-Auth: O7kzKj3lra78yP1czeh8NwcbpF4
Message-ID: <CAC4RtVACkUX2Uo1UVWXGF-EFpbsRfaJX53=1MoEM66GxFJnxPQ@mail.gmail.com>
Subject: Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard
From: Barry Leiba <barryleiba@computer.org>
To: ned+ietf@mauve.mrochek.com
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: Pete Resnick <presnick@qualcomm.com>, Alexey Melnikov <alexey.melnikov@isode.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Mar 2012 02:30:18 -0000

>> I've used text like this before, and the IESG has never objected to
>> it. =A0One advantage with this formulation, which uses the standard 2119
>> text and *appends* to it, is that idnits likes it and doesn't generate
>> a warning.
>
> More generally, ID-nits is supposed to be helpful. Straightjackets are no=
t
> helpful.

I absolutely agree.  And even in cases where my alternative 2119 text
has generated idnits complaints, the IESG didn't care.  They only
cared that the text accurately explained the terms the document used.

Barry

From ned+ietf@mauve.mrochek.com  Mon Mar  5 18:59:48 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 66D1B21F8639 for <ietf@ietfa.amsl.com>; Mon,  5 Mar 2012 18:59:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.59
X-Spam-Level: 
X-Spam-Status: No, score=-2.59 tagged_above=-999 required=5 tests=[AWL=0.009,  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 L5Qpzn5isjl2 for <ietf@ietfa.amsl.com>; Mon,  5 Mar 2012 18:59:47 -0800 (PST)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id 85BBB21F856A for <ietf@ietf.org>; Mon,  5 Mar 2012 18:59:47 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OCRMMXWTGG00OVQ6@mauve.mrochek.com> for ietf@ietf.org; Mon, 5 Mar 2012 18:59:43 -0800 (PST)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OCPMUVDUMO00ZUIL@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Mon, 5 Mar 2012 18:59:37 -0800 (PST)
From: ned+ietf@mauve.mrochek.com
Message-id: <01OCRMMT4IVM00ZUIL@mauve.mrochek.com>
Date: Mon, 05 Mar 2012 18:56:34 -0800 (PST)
Subject: Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to	Proposed Standard
In-reply-to: "Your message dated Mon, 05 Mar 2012 10:41:56 -0500" <alpine.BSF.2.00.1203051040260.47190@joyce.lan>
MIME-version: 1.0
Content-type: TEXT/PLAIN; Format=flowed
References: <CAC4RtVA3F8gsBWY65W5KNDE+408EvtP+hp5GTzLg4FMgC1bdcQ@mail.gmail.com> <20120303041153.23749.qmail@joyce.lan> <01OCOC18E6PI00ZUIL@mauve.mrochek.com> <4F54D198.3000607@isode.com> <alpine.BSF.2.00.1203051040260.47190@joyce.lan>
To: "John R. Levine" <johnl@iecc.com>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mrochek.com; s=mauve; t=1331002790; i=@mrochek.com; bh=0p7C2XnmCApSGX6iDDwuIBm7hvCFBZH86t4T26gy2xg=;  h=From:Cc:Message-id:Date:Subject:In-reply-to:MIME-version: Content-type:References:To; b=tH+Dx5DpDlMTPlvyGhDIH9qa5M6HStW9bD5qaAs0Mz278chnYuLYkV3Ha91DAxC3A RhcT1hCtUzCE/ba95w1UY3kjHFGsVw8ps7FjrJDVEDpXwo9Ygbe3/yrs7GQp/Z/xyY YqsotP0u9HCWO0IRh9/vzoiaoUIMCdk9prTTSC1Q=
Cc: Alexey Melnikov <alexey.melnikov@isode.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Mar 2012 02:59:48 -0000

> > I do prefer the latter as well (and yes, happy to remove the restriction),
> > but I don't feel very comfortable pretending that tunneling wouldn't happen.

> Of course people will tunnel stuff.  But will they all tunnel it the same
> way, in which case a standard could be useful, or will they each have
> their own hacks?  Given the vagueness about how you can tell that
> something should come out of the tunnel back into the envelope, it sounds
> more like the latter.

If the only issue was tunneling, I'm not sure it would matter as much as it
does. After all, if we have a spec that says use MT-Priority and someone
uses something else within their ADMD, who will even know?

But this isn't just about tunneling. There are a bunch of ad-hoc priority
mechanisms out there, some in fairly widespread use. If we cannot align
ourselves with those nobody is going to be interested in deploying this
extension. Instead they will be asking us to retain our present capability of
interoperating with those existing systems. And doing both is ... messy to say
the least, not to mention a violation of the current language in the
specification.

				Ned

From ned+ietf@mauve.mrochek.com  Mon Mar  5 19:12:15 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 AA85821F876C for <ietf@ietfa.amsl.com>; Mon,  5 Mar 2012 19:12:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.59
X-Spam-Level: 
X-Spam-Status: No, score=-2.59 tagged_above=-999 required=5 tests=[AWL=0.009,  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 qva7Z1tDaUpG for <ietf@ietfa.amsl.com>; Mon,  5 Mar 2012 19:12:15 -0800 (PST)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id EAD5321F876A for <ietf@ietf.org>; Mon,  5 Mar 2012 19:12:14 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OCRN2EKKKW00VPYT@mauve.mrochek.com> for ietf@ietf.org; Mon, 5 Mar 2012 19:12:10 -0800 (PST)
MIME-version: 1.0
Content-type: TEXT/PLAIN; charset=ISO-8859-1
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OCPMUVDUMO00ZUIL@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Mon, 5 Mar 2012 19:12:03 -0800 (PST)
From: ned+ietf@mauve.mrochek.com
Message-id: <01OCRN2AA2KE00ZUIL@mauve.mrochek.com>
Date: Mon, 05 Mar 2012 19:02:21 -0800 (PST)
Subject: Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard
In-reply-to: "Your message dated Mon, 05 Mar 2012 11:07:16 -0500" <CALaySJJ1CJSPFEh3MfdGCP=FeuiM7Gvzf9MU0F_83qtbWcazew@mail.gmail.com>
References: <20120301004219.15266.76505.idtracker@ietfa.amsl.com> <CAC4RtVDeXwCLh9R_bNmLwEC5g_4Dv9HadOpXMwbSz5RT2m+jUg@mail.gmail.com> <CAC4RtVB1G_HjYNug0Fvq7LPSnzqG2KxH-PY6nv=nBZKv-uXTLA@mail.gmail.com> <01OCM8WDJZKI00ZUIL@mauve.mrochek.com> <4F54C9B1.4010100@isode.com> <CALaySJJUE02R7NP08HB-Si7vOZHRg28vtKqLF9Y45=6d43QHdA@mail.gmail.com> <01OCQZFYBOQA00ZUIL@mauve.mrochek.com> <CALaySJJ1CJSPFEh3MfdGCP=FeuiM7Gvzf9MU0F_83qtbWcazew@mail.gmail.com>
To: Barry Leiba <barryleiba@computer.org>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mrochek.com; s=mauve; t=1331003538; i=@mrochek.com; bh=g414sR/xghxMEotHYC4I1oCtwHKsi8ODee73FrZ8oZA=;  h=MIME-version:Content-type:From:Cc:Message-id:Date:Subject: In-reply-to:References:To; b=C/VPtE84zhAAINFeD1+b4vWKL9o4VYylpjcNmrs2TUYICsxu3/piEQluEQ28tncfE ogSP/xboustobT+XWLIF6jaHqUShCKD8woZXXuMw+Lo94tEi1VzDwYps3H4RClAWBg wn/jQDiu++dHD6LOto82HkwfKWCd64wCokt1lOyM=
Cc: Pete Resnick <presnick@qualcomm.com>, Alexey Melnikov <alexey.melnikov@isode.com>, Ned Freed <ned.freed@mrochek.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Mar 2012 03:12:15 -0000

> >>    Other message header fields, such as Importance [RFC2156], Priority
> >>    [RFC2156] and X-Priority, are used inconsistently and often with
> >>    different semantics from MT-Priority.  Message Submission Agents
> >>    [RFC6409] MAY use such fields to assign an initial priority in the
> >>    absence of an SMTP PRIORITY parameter.  Otherwise, such fields
> >>    MUST NOT be used for determining the priority under this "Priority
> >>    Message Handling" SMTP extension.
> >
> > It seems you're complaining about other people doing something they never
> > wanted to do while actually making that error yourself.

> I have no idea what you mean, so perhaps you can be more specific
> about what it is that you want to do.

I'm talking about the inclusion of Importance: in both the original and revised
text as a field we're suggesting might make sense to map. It should not be
there - the semantics are not compatible with MTA priority. And even if you
think it makes sense that messages marked "important" in the MUA should receive
an MTA priority boost, allow me to point out that by GOSIP rules (which are
still in effect in some places) elevated MTA priority is used to shorten the
time messages are retained before returning them as undeliverable. That's
really not a good idea to do for all messages marked "important", and some
people with systems that do this are probably unaware of the behavior.

Mind you, I have no problem with someone doing it because it makes sense in
their case. But we should not be suggesting doing it in the text, and getting
into a discussion of the pitfalls of doing it doesn't is unnecessarily
distracting.

The semantics of X-Priority are less clear. It's sometimes used for MTA
priority setting, other times it's been an MUA field. AFAIK it has never had
the problematic semantics I just discussed. Mapping it is therefore a judgement
call implementations should be allowed to make, and that makes it a good
example to include in this sort of text.

				Ned

From barryleiba@gmail.com  Mon Mar  5 19:23:03 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 492C921F8554 for <ietf@ietfa.amsl.com>; Mon,  5 Mar 2012 19:23:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.986
X-Spam-Level: 
X-Spam-Status: No, score=-102.986 tagged_above=-999 required=5 tests=[AWL=-0.009, 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 M796n06MNa4H for <ietf@ietfa.amsl.com>; Mon,  5 Mar 2012 19:23:02 -0800 (PST)
Received: from mail-tul01m020-f172.google.com (mail-tul01m020-f172.google.com [209.85.214.172]) by ietfa.amsl.com (Postfix) with ESMTP id B3DC021F8516 for <ietf@ietf.org>; Mon,  5 Mar 2012 19:23:02 -0800 (PST)
Received: by obbta4 with SMTP id ta4so3423969obb.31 for <ietf@ietf.org>; Mon, 05 Mar 2012 19:23:02 -0800 (PST)
Received-SPF: pass (google.com: domain of barryleiba@gmail.com designates 10.60.7.70 as permitted sender) client-ip=10.60.7.70; 
Authentication-Results: mr.google.com; spf=pass (google.com: domain of barryleiba@gmail.com designates 10.60.7.70 as permitted sender) smtp.mail=barryleiba@gmail.com; dkim=pass header.i=barryleiba@gmail.com
Received: from mr.google.com ([10.60.7.70]) by 10.60.7.70 with SMTP id h6mr8552157oea.44.1331004182209 (num_hops = 1); Mon, 05 Mar 2012 19:23:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=NX85MTJ4vK9G1BfWYBYNa6wUvMwATfS0cVLO71Vj/DY=; b=xNV/a4BGx6RerxPTngObN/jNlgTbFhP+9/YFsuEY6Gz5KWsjzLVqasvLtaDG2YEYrm Ds+SOGQTzHC4iWan8hLT8wKDV7UB1n+wMvTJ2D0h2lThAvPktp3um8Rx6CkfdlSSn/HB 68i0YVoWUpz71Hj/r9K+cUtzoYz27eEkdkLSf0pGOqtfXR+ryP+91tk+Gc0PfakaV9/6 7XOtrMPFlWoGbtChMdndutXjBY7baTG1HVb2dMvRVRn0ZJrrmQMssi12nEP2SvHoWHkI Fmccx9WMtrJ3yqGpic6F0/7AvEmPYRCtAvtTRHEQ4N7C0Z2Re9a6Gc2t1UOZXxfr2Qek IEUA==
MIME-Version: 1.0
Received: by 10.60.7.70 with SMTP id h6mr7553209oea.44.1331004182125; Mon, 05 Mar 2012 19:23:02 -0800 (PST)
Sender: barryleiba@gmail.com
Received: by 10.60.125.37 with HTTP; Mon, 5 Mar 2012 19:23:01 -0800 (PST)
In-Reply-To: <01OCRN2AA2KE00ZUIL@mauve.mrochek.com>
References: <20120301004219.15266.76505.idtracker@ietfa.amsl.com> <CAC4RtVDeXwCLh9R_bNmLwEC5g_4Dv9HadOpXMwbSz5RT2m+jUg@mail.gmail.com> <CAC4RtVB1G_HjYNug0Fvq7LPSnzqG2KxH-PY6nv=nBZKv-uXTLA@mail.gmail.com> <01OCM8WDJZKI00ZUIL@mauve.mrochek.com> <4F54C9B1.4010100@isode.com> <CALaySJJUE02R7NP08HB-Si7vOZHRg28vtKqLF9Y45=6d43QHdA@mail.gmail.com> <01OCQZFYBOQA00ZUIL@mauve.mrochek.com> <CALaySJJ1CJSPFEh3MfdGCP=FeuiM7Gvzf9MU0F_83qtbWcazew@mail.gmail.com> <01OCRN2AA2KE00ZUIL@mauve.mrochek.com>
Date: Mon, 5 Mar 2012 22:23:01 -0500
X-Google-Sender-Auth: zEG64QLgXR2IbKAql4I6B4E2RlY
Message-ID: <CALaySJ+J1ywDOqHweJVLtYBgn_AXtDPSrdZOacX=dx1_QN7pNg@mail.gmail.com>
Subject: Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard
From: Barry Leiba <barryleiba@computer.org>
To: Ned Freed <ned.freed@mrochek.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: Pete Resnick <presnick@qualcomm.com>, Alexey Melnikov <alexey.melnikov@isode.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Mar 2012 03:23:03 -0000

On Mon, Mar 5, 2012 at 22:02, Ned Freed <ned.freed@mrochek.com> wrote:
>> >> =A0 =A0Other message header fields, such as Importance [RFC2156], Pri=
ority
>> >> =A0 =A0[RFC2156] and X-Priority, are used inconsistently and often wi=
th
>> >> =A0 =A0different semantics from MT-Priority. =A0Message Submission Ag=
ents
>> >> =A0 =A0[RFC6409] MAY use such fields to assign an initial priority in=
 the
>> >> =A0 =A0absence of an SMTP PRIORITY parameter. =A0Otherwise, such fiel=
ds
>> >> =A0 =A0MUST NOT be used for determining the priority under this "Prio=
rity
>> >> =A0 =A0Message Handling" SMTP extension.
>> >
>> > It seems you're complaining about other people doing something they ne=
ver
>> > wanted to do while actually making that error yourself.
>
>> I have no idea what you mean, so perhaps you can be more specific
>> about what it is that you want to do.
>
> I'm talking about the inclusion of Importance: in both the original and r=
evised
> text as a field we're suggesting might make sense to map. It should not b=
e
> there - the semantics are not compatible with MTA priority.

Ah, OK.  So there's no strawman that I've been constructing, or any such.

Alexey had just included Important, along with Priority and
X-Priority, as an example of other priority-like fields that he didn't
want implementations to use for this purpose.  When you balked at the
blanket ban, I proposed an alternative that just called out the same
set of fields.

What we need is replacement text that makes sense: that says which
(known) fields can maybe-kinda-sorta-ifyouhaveto be used here, and
which ones absolutely can't (wrong semantics).  I think such advice is
important if we're going to keep the tunneling thing in here.  If
you'd like to take a stab at suggesting replacement text, I, and I
think Alexey, would be very grateful.  You have a much better idea
than I do of what actual use is being made of the different fields
currently.

> The semantics of X-Priority are less clear. It's sometimes used for MTA
> priority setting, other times it's been an MUA field.

That's why I added "inconsistently" into my text.

So... can we get text that gives the proper fields, the proper
warnings, the proper MAYs, SHOULDs, and MUST NOTs, and all that?

Barry

From ned+ietf@mauve.mrochek.com  Mon Mar  5 20:13:07 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 5C29621E8074 for <ietf@ietfa.amsl.com>; Mon,  5 Mar 2012 20:13:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.591
X-Spam-Level: 
X-Spam-Status: No, score=-2.591 tagged_above=-999 required=5 tests=[AWL=0.008,  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 2+y6J3KQ4ewm for <ietf@ietfa.amsl.com>; Mon,  5 Mar 2012 20:13:06 -0800 (PST)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id 2A40821E8045 for <ietf@ietf.org>; Mon,  5 Mar 2012 20:13:06 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OCRP6VBUZK004J2Q@mauve.mrochek.com> for ietf@ietf.org; Mon, 5 Mar 2012 20:13:02 -0800 (PST)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OCPMUVDUMO00ZUIL@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Mon, 5 Mar 2012 20:12:58 -0800 (PST)
From: ned+ietf@mauve.mrochek.com
Message-id: <01OCRP6SYT8Q00ZUIL@mauve.mrochek.com>
Date: Mon, 05 Mar 2012 19:56:15 -0800 (PST)
Subject: Re: provisioning software, was DNS RRTYPEs, the difficulty with
In-reply-to: "Your message dated Mon, 05 Mar 2012 20:01:53 +0100" <4F550DA1.8060304@tana.it>
MIME-version: 1.0
Content-type: TEXT/PLAIN
References: <20120305170938.57919.qmail@joyce.lan> <4F550DA1.8060304@tana.it>
To: Alessandro Vesely <vesely@tana.it>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mrochek.com; s=mauve; t=1331007190; i=@mrochek.com; bh=sgAglaxqRUuDUpkqoGHxV13ymx65tkOs3BJPy2rGWcg=;  h=From:Cc:Message-id:Date:Subject:In-reply-to:MIME-version: Content-type:References:To; b=Uwrf51taOw1J3G/7HnyMKBFDkF2YX0taVHXdgaERt9l3xLVAZdLkjgmO2JSXSpiJb c7MJ5EnjBF2ltPv72XcOQoyFkE2h9YIi2RBR/6qs1GOvbbdstXhIJC5WiQzxm7aEdL xKnoZlJISVYCOvemlmhoiumAd6jhP6vigVZOqxao=
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Mar 2012 04:13:07 -0000

> On 05/Mar/12 18:09, John Levine wrote:
> >>> Sometimes an ASCII text record will be fine, in other cases, it probably won't.
> >>
> >>My point is as we move again towards multiple text representations of "the digit five" for example,
> >>both encoding and parsing is easier and more secure if that digit is really for example eight bits
> >>and not "text" that someone has to parse.
> >
> > Unless you provision your DNS zones with a hex debugger, the digit
> > will always start out as text that someone has to parse.  The question
> > is who does the parsing, the DNS server or the application.  As I said
> > in a previous message, I can see plausible reasons to put the parser into
> > the application.
> >
> > Would you really want to build an SPF or DKIM parser into every DNS
> > server?  That's a lot of code that the DNS manager doesn't care about,
> > but the mail manager does.

> But it would be the same code, most likely by the same author(s).  It
> may be generic for a kind of syntax or specific for a RR type,
> according to its author's convenience.  On a system that allows new RR
> types without recompiling, the code would come as some sort of plugin
> in both cases.

There are some false equivalences floating around here. I don't think anyone is
suggesting that having provisioning systems or even DNS servers themselves
check for syntax errors in the contents of complex records like DKIM, SPF,
DMARC, or whatever is necessarily a bad idea. (Whether or not it will actually
happen is another matter; I'm dubious.)

Rather, the issue is with requiring it to happen in order to deploy a new
RRTYPE of this sort, which is the result you get if the DNS server returns some
series of tokens instead of the original text string. That's the sort of thing
that forces people to upgrade, or search around for a script to do the
conversion (which won't even occur to some), and that's an extra burden we
don't need to impose.

> Why is it important what the DNS manager cares about?

Speaking as a DNS manager myself, I care a lot about being forced to upgrade.
Upgrades bring unwanted bugs in other areas.

In fact I'm not entirely thrilled with the idea of plugins to do some extra
syntax. More code means more possibilities of bugs. I'd actually prefer to see
more cross-checking of existing stuff - less code and greater benefit.

> Parsers,
> including null parsers, would come with the same sub-package that
> enables the new RR type definition.  Their complexity would only
> matter to the people who read/maintain their sources.

I'm sorry, but you're being naive about this. Complexity does matter to the
people who just use software because added complexity translates to more bugs.

> > PS: For anyone who didn't read my previous message, I am NOT saying
> > that it's fine to overload everything into TXT.  I am saying that new
> > RRTYPEs that are text blobs interpreted by client software wouldn't
> > necessarily be bad.

> Agreed.  That doesn't preclude syntax checking on loading the zone,
> though.

As long as we stick with syntax checking I'm (mostly) OK with it.

				Ned

From johnl@iecc.com  Mon Mar  5 20:46:53 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 A0D1121E8092 for <ietf@ietfa.amsl.com>; Mon,  5 Mar 2012 20:46:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.244
X-Spam-Level: 
X-Spam-Status: No, score=-110.244 tagged_above=-999 required=5 tests=[AWL=0.355, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, J_CHICKENPOX_35=0.6, 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 e-o959jkHRWD for <ietf@ietfa.amsl.com>; Mon,  5 Mar 2012 20:46:53 -0800 (PST)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id CE4EF21E8091 for <ietf@ietf.org>; Mon,  5 Mar 2012 20:46:52 -0800 (PST)
Received: (qmail 31095 invoked from network); 6 Mar 2012 04:46:50 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 6 Mar 2012 04:46:50 -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=4f5596ba.xn--30v786c.k1203; i=johnl@user.iecc.com; bh=HNiW6qaNfGDrKTfEOnqTZ4AV/JWz6CxbZlxjz16pqB8=; b=Si9gRaY5Hj+zcpK89lEVJbbdYI00vkpA7k0qb0xH8HX3hrGFz2UE/qMHVBO3TB2rFpxCzrPXL6gY+fz0GHYjNogKpCjFzeJFsBRHNpQPu3WggaBiwtBW/LynQBMzf6iS8dwsUCe7Nt/0drjt05+6H0TGScb52z7TESSCVssmRjk=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 6 Mar 2012 04:46:28 -0000
Message-ID: <20120306044628.87718.qmail@joyce.lan>
From: "John Levine" <johnl@iecc.com>
To: ietf@ietf.org
Subject: Re: provisioning software, was DNS RRTYPEs, the difficulty with
In-Reply-To: <4F550DA1.8060304@tana.it>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
Cc: vesely@tana.it
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Mar 2012 04:46:53 -0000

>> Would you really want to build an SPF or DKIM parser into every DNS
>> server?

Here's another thought experiment.  DKIM records are a sequence of
tag=value fields.  Let's imagine a binary version of DKIM records
where each field is a length byte, a tag byte, and a suitably coded
value.  For the values that are currently strings, it's the string,
for the values that are currently base64, it's the binary value.

Since DNS TXT records are a sequence of binary strings each preceded
by a length byte, we could just stuff this version of DKIM directly
into a TXT record, with the first binary string being "v=DKIM2".
Would that be a good idea?  DNS servers can serve the records without
adding any new features, the records will be marginally faster to
parse.

Would that be a good idea?  Why or why not?  Assume we wave our hands
and we have some way to create the records, hacks in provisioning
systems, or a wizard web site into which you type your parameters and
it gives you a TXT master file record full of hex escapes.  

Or wave them even more vigorously and assume the parser is built into
some future version of BIND.

R's,
John

From paf@frobbit.se  Mon Mar  5 20:59:35 2012
Return-Path: <paf@frobbit.se>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5DF3321E809C for <ietf@ietfa.amsl.com>; Mon,  5 Mar 2012 20:59:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[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 KUS2VcV29kyZ for <ietf@ietfa.amsl.com>; Mon,  5 Mar 2012 20:59:35 -0800 (PST)
Received: from srv01.frobbit.se (srv01.frobbit.se [IPv6:2a02:80:3ffe::39]) by ietfa.amsl.com (Postfix) with ESMTP id 99C8121E809B for <ietf@ietf.org>; Mon,  5 Mar 2012 20:59:34 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by srv01.frobbit.se (Postfix) with ESMTP id D87D0133CB620; Tue,  6 Mar 2012 05:59:32 +0100 (CET)
X-Virus-Scanned: amavisd-new at frobbit.se
Received: from srv01.frobbit.se ([127.0.0.1]) by localhost (srv01.frobbit.se [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0ZsThSdu-vZH; Tue,  6 Mar 2012 05:59:32 +0100 (CET)
Received: from [10.0.1.8] (s83-180-234-193.cust.tele2.se [83.180.234.193]) (Authenticated sender: paf01) by srv01.frobbit.se (Postfix) with ESMTP id 9A367133CB619; Tue,  6 Mar 2012 05:59:32 +0100 (CET)
Subject: Re: provisioning software, was DNS RRTYPEs, the difficulty with
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=us-ascii
From: =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
In-Reply-To: <20120306044628.87718.qmail@joyce.lan>
Date: Tue, 6 Mar 2012 05:59:32 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <77075C8C-04ED-48A2-B501-B2296BCFC8C6@frobbit.se>
References: <20120306044628.87718.qmail@joyce.lan>
To: "John Levine" <johnl@iecc.com>
X-Mailer: Apple Mail (2.1257)
Cc: "ietf@ietf.org Discussion" <ietf@ietf.org>, Alessandro Vesely <vesely@tana.it>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Mar 2012 04:59:35 -0000

I think we should look a bit on the flow of data. If I simplify we have =
a flow like this:

Input -P-> DNS server -D-> DNS stub -Q-> Output

P is the provisioning
D is the DNS protocol
Q is the query/parsing in the consumer of the data

What we want is (as described in the IAB RFC on extensions of DNS) the =
ability to query (in D) for as precise data as possible in the triple =
{owner, type, class}. Some RR types like NAPTR and TXT have flaws where =
the selection between records in an RRSet is not in this triple. In some =
applications that is resolved by having a prefix to the owner. In some =
other applications that is resolved by parsing the RRSet.

We all do believe that IF it was easier to add a new RRType for each =
application that would be an architecturally better solution (as adding =
prefix to the owner have its drawbacks). Now, the question is what =
blocks the ability to add new RRTypes.

We seem to believe that the "D" part is deployed so that adding new =
"unknown" RRTypes is not an issue.

Problem is then in "P" and "Q".

And when we talk about parsing, we talk about what the mapping between =
provisioning and DNS packet format is.

Are we aligned so far?

   Patrik


From marka@isc.org  Mon Mar  5 21:42:33 2012
Return-Path: <marka@isc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 456C921E8047 for <ietf@ietfa.amsl.com>; Mon,  5 Mar 2012 21:42:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level: 
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, 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 tyH160NwT4eJ for <ietf@ietfa.amsl.com>; Mon,  5 Mar 2012 21:42:32 -0800 (PST)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) by ietfa.amsl.com (Postfix) with ESMTP id 4835A21E8045 for <ietf@ietf.org>; Mon,  5 Mar 2012 21:42:32 -0800 (PST)
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mail.isc.org", Issuer "RapidSSL CA" (not verified)) by mx.pao1.isc.org (Postfix) with ESMTPS id AC633C9425; Tue,  6 Mar 2012 05:42:19 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (unknown [IPv6:2001:470:1f00:820:254b:f761:ce8a:f684]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by bikeshed.isc.org (Postfix) with ESMTPSA id 4E775216C33; Tue,  6 Mar 2012 05:42:19 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (Postfix) with ESMTP id 1C1F91E19F87; Tue,  6 Mar 2012 16:42:12 +1100 (EST)
To: =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
From: Mark Andrews <marka@isc.org>
References: <20120306044628.87718.qmail@joyce.lan> <77075C8C-04ED-48A2-B501-B2296BCFC8C6@frobbit.se>
Subject: Re: provisioning software, was DNS RRTYPEs, the difficulty with
In-reply-to: Your message of "Tue, 06 Mar 2012 05:59:32 BST." <77075C8C-04ED-48A2-B501-B2296BCFC8C6@frobbit.se>
Date: Tue, 06 Mar 2012 16:42:12 +1100
Message-Id: <20120306054213.1C1F91E19F87@drugs.dv.isc.org>
Cc: John Levine <johnl@iecc.com>, "ietf@ietf.org Discussion" <ietf@ietf.org>, Alessandro Vesely <vesely@tana.it>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Mar 2012 05:42:33 -0000

In message <77075C8C-04ED-48A2-B501-B2296BCFC8C6@frobbit.se>, =?iso-8859-1?Q?Pa
trik_F=E4ltstr=F6m?= writes:
> I think we should look a bit on the flow of data. If I simplify we have a flo
> w like this:
> 
> Input -P-> DNS server -D-> DNS stub -Q-> Output
> 
> P is the provisioning
> D is the DNS protocol
> Q is the query/parsing in the consumer of the data
> 
> What we want is (as described in the IAB RFC on extensions of DNS) the abilit
> y to query (in D) for as precise data as possible in the triple {owner, type,
>  class}. Some RR types like NAPTR and TXT have flaws where the selection betw
> een records in an RRSet is not in this triple. In some applications that is r
> esolved by having a prefix to the owner. In some other applications that is r
> esolved by parsing the RRSet.
> 
> We all do believe that IF it was easier to add a new RRType for each applicat
> ion that would be an architecturally better solution (as adding prefix to the
>  owner have its drawbacks). Now, the question is what blocks the ability to a
> dd new RRTypes.
> 
> We seem to believe that the "D" part is deployed so that adding new "unknown"
>  RRTypes is not an issue.
> 
> Problem is then in "P" and "Q".
> 
> And when we talk about parsing, we talk about what the mapping between provis
> ioning and DNS packet format is.
> 
> Are we aligned so far?
> 
>    Patrik

I would say DNS master file representation -> DNS wire representation
is one of the main issues on the provisioning side.  This conversion
needs to be done at some point.  The other this is verification of
the input.

DNS wire representation -> text or structured object on the application
side.  Part of the issue here is that some libraries don't provide
hooks to return unknown types as a raw data blob so even if you can
enter the data there isn't a exit path.  I don't know what such
library developers were thinking.  There has been a long but slow
history of new types being added to the DNS and the original set
of types was never expected to be sufficient for all uses.

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

From ned+ietf@mauve.mrochek.com  Mon Mar  5 22:18:46 2012
Return-Path: <ned+ietf@mauve.mrochek.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8F63F21E80A2 for <ietf@ietfa.amsl.com>; Mon,  5 Mar 2012 22:18:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.441
X-Spam-Level: 
X-Spam-Status: No, score=-2.441 tagged_above=-999 required=5 tests=[AWL=-0.142, 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 WRSqpuW0o2MM for <ietf@ietfa.amsl.com>; Mon,  5 Mar 2012 22:18:46 -0800 (PST)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id D1A5821E8045 for <ietf@ietf.org>; Mon,  5 Mar 2012 22:18:45 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OCRTKNDKB4004J9U@mauve.mrochek.com> for ietf@ietf.org; Mon, 5 Mar 2012 22:18:41 -0800 (PST)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OCPMUVDUMO00ZUIL@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Mon, 5 Mar 2012 22:18:35 -0800 (PST)
From: ned+ietf@mauve.mrochek.com
Message-id: <01OCRTKK8TSO00ZUIL@mauve.mrochek.com>
Date: Mon, 05 Mar 2012 22:08:54 -0800 (PST)
Subject: Re: provisioning software, was DNS RRTYPEs, the difficulty with
In-reply-to: "Your message dated Tue, 06 Mar 2012 05:59:32 +0100" <77075C8C-04ED-48A2-B501-B2296BCFC8C6@frobbit.se>
MIME-version: 1.0
Content-type: TEXT/PLAIN
References: <20120306044628.87718.qmail@joyce.lan> <77075C8C-04ED-48A2-B501-B2296BCFC8C6@frobbit.se>
To: =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mrochek.com; s=mauve; t=1331014729; i=@mrochek.com; bh=L3W/2rJjU+O/attf8yT4oFmiS0B9gkLVvtUm7RVw5XI=;  h=From:Cc:Message-id:Date:Subject:In-reply-to:MIME-version: Content-type:References:To; b=CIA+LzXAfxqsVzF7C1w724z2E4R2HYsC/ASkCeBTUrjYLV4aq2+7JkFZJ8CiIxUJt FYg381ZBVsd2CPI3NlBetA5TfckQDbW/JSLaMQMz57jM2KseVWKas05ARM2K0x4X3M gnJhJbxHcgjDf1fUDMJjTrs1EG+rhG5TJmae+vV0=
Cc: John Levine <johnl@iecc.com>, "ietf@ietf.org Discussion" <ietf@ietf.org>, Alessandro Vesely <vesely@tana.it>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Mar 2012 06:18:46 -0000

> I think we should look a bit on the flow of data. If I simplify we have a
> flow like this:

Looking at data flows is usually a good idea.

> Input -P-> DNS server -D-> DNS stub -Q-> Output

> P is the provisioning

I think you want to break that into the provisioning interface and the data
format it produces that the DNS server consumes. (My reason for that is we have
a specification for at least such format, with all that implies.)

> D is the DNS protocol
> Q is the query/parsing in the consumer of the data

> What we want is (as described in the IAB RFC on extensions of DNS) the
> ability to query (in D) for as precise data as possible in the triple {owner,
> type, class}. Some RR types like NAPTR and TXT have flaws where the selection
> between records in an RRSet is not in this triple. In some applications that
> is resolved by having a prefix to the owner. In some other applications that
> is resolved by parsing the RRSet.

> We all do believe that IF it was easier to add a new RRType for each
> application that would be an architecturally better solution (as adding prefix
> to the owner have its drawbacks). Now, the question is what blocks the ability
> to add new RRTypes.

Yes, I think we have agreement on all of that.

> We seem to believe that the "D" part is deployed so that adding new "unknown"
> RRTypes is not an issue.

I think this is correct, but OTOH someone recently asked about possible issues
in this area, and if I remember correctly, received no response.

> Problem is then in "P" and "Q".

I personally don't see a big problem with "Q", but others clearly do so
we need to leave it in.

> And when we talk about parsing, we talk about what the mapping between
> provisioning and DNS packet format is.

I think we need to be a little finer grained than that, per the above.

> Are we aligned so far?

Yes, pretty much.

				Ned

From alexey.melnikov@isode.com  Tue Mar  6 02:50:47 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 A902C21F8681 for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 02:50:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.82
X-Spam-Level: 
X-Spam-Status: No, score=-101.82 tagged_above=-999 required=5 tests=[AWL=-0.213, 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 HmJGHSB+HQdk for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 02:50:46 -0800 (PST)
Received: from rufus.isode.com (cl-125.lon-03.gb.sixxs.net [IPv6:2a00:14f0:e000:7c::2]) by ietfa.amsl.com (Postfix) with ESMTP id CBF1521F8687 for <ietf@ietf.org>; Tue,  6 Mar 2012 02:50:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1331031043; d=isode.com; s=selector; i=@isode.com; bh=tGYXo5g+KR88pH3Ff1pCoBrcIj3UR13ro8QBG/f2sIE=; 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=n40Nrc08RfXV9I8BXeBoPSSvqes7hhpZYm7W9OUo9f8x4x5Z5HundNhhx0nwo58l4a+ww3 uuvt/cg4HDcYD0O9iW97+7H004DcNz47Xwo35Ai2QemxzpW3vw85vY9KAWsawmUmQLPmHp zRYnFeTdgFVCMq8QzUgEBb6YA53CHsM=;
Received: from [172.16.1.29] (shiny.isode.com [62.3.217.250])  by rufus.isode.com (submission channel) via TCP with ESMTPSA  id <T1Xr=QBhulTJ@rufus.isode.com>; Tue, 6 Mar 2012 10:50:42 +0000
Message-ID: <4F553613.4030007@isode.com>
Date: Mon, 05 Mar 2012 21:54:27 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:9.0) Gecko/20111222 Thunderbird/9.0.1
To: Barry Leiba <barryleiba@computer.org>
Subject: Re: Last Call: <draft-melnikov-smtp-priority-07.txt>  (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard
References: <20120301004219.15266.76505.idtracker@ietfa.amsl.com> <CAC4RtVDeXwCLh9R_bNmLwEC5g_4Dv9HadOpXMwbSz5RT2m+jUg@mail.gmail.com> <4F549FC0.1060609@isode.com> <CAC4RtVDzvaY0uF6oEVaK_HK_DuS8YyaJbUni25M6TG5uudSLuA@mail.gmail.com>
In-Reply-To: <CAC4RtVDzvaY0uF6oEVaK_HK_DuS8YyaJbUni25M6TG5uudSLuA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Pete Resnick <presnick@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: Tue, 06 Mar 2012 10:50:47 -0000

On 05/03/2012 19:40, Barry Leiba wrote:
>>> 2. I, too, noticed all the lower-case "should" and "may" words.  I
>>> suggest that the best way to handle this is to make the following
>>> change to the RFC 2119 citation text at the beginning of section 2:
>>>
>>> NEW
>>>     The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
>>>     "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
>>>     document are to be interpreted as described in [RFC2119] when they
>>> appear
>>>     in ALL CAPS.  These words also appear in this document in lower case as
>>> plain
>>>     English words, absent their normative meanings.
>> I don't mind changing that, but ID-nits gives a warning when the text about
>> keywords is changed and *everybody* likes to complain about that. Please
>> talk to IESG about whether using a variant of the standard text is
>> acceptable.
> I've used text like this before, and the IESG has never objected to
> it.  One advantage with this formulation, which uses the standard 2119
> text and *appends* to it, is that idnits likes it and doesn't generate
> a warning.
Ok then.


From alexey.melnikov@isode.com  Tue Mar  6 02:50:47 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 E7E1321F8687 for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 02:50:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.814
X-Spam-Level: 
X-Spam-Status: No, score=-101.814 tagged_above=-999 required=5 tests=[AWL=-0.207, 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 uknqDlDtCJBv for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 02:50:47 -0800 (PST)
Received: from rufus.isode.com (cl-125.lon-03.gb.sixxs.net [IPv6:2a00:14f0:e000:7c::2]) by ietfa.amsl.com (Postfix) with ESMTP id D8CC121F87D8 for <ietf@ietf.org>; Tue,  6 Mar 2012 02:50:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1331031045; d=isode.com; s=selector; i=@isode.com; bh=0T98etA60gn3orqJx/MTO9jqW8OUCUrWG0pucs3DfhA=; 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=ho6bwMBpXzAAaxsVP02lKI1ruCw9CoUW8M4VmoyBvWW4zNa3dpItec8nliGYHQKLiVC+ro 7P09nkvtyGwsm5gQSnH6Vo6ZWhWZuDxGsHuf3RZlIB8dhEPw0sNgJaJk1jt2T9lOxKDlc+ /CWQlZteWEM2GB303JgDCP+7RN9M9MI=;
Received: from [172.16.1.29] (shiny.isode.com [62.3.217.250])  by rufus.isode.com (submission channel) via TCP with ESMTPSA  id <T1XsBQBhulXK@rufus.isode.com>; Tue, 6 Mar 2012 10:50:45 +0000
Message-ID: <4F553D29.5090706@isode.com>
Date: Mon, 05 Mar 2012 22:24:41 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:9.0) Gecko/20111222 Thunderbird/9.0.1
To: "Murray S. Kucherawy" <msk@cloudmark.com>
Subject: Re: Last Call: <draft-melnikov-smtp-priority-07.txt>  (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard
References: <20120301004219.15266.76505.idtracker@ietfa.amsl.com> <9452079D1A51524AA5749AD23E00392806E6F5@exch-mbx901.corp.cloudmark.com> <4F54AAB7.5000703@isode.com> <9452079D1A51524AA5749AD23E00392807ABA1@exch-mbx901.corp.cloudmark.com>
In-Reply-To: <9452079D1A51524AA5749AD23E00392807ABA1@exch-mbx901.corp.cloudmark.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Mar 2012 10:50:48 -0000

On 05/03/2012 18:00, Murray S. Kucherawy wrote:
>> -----Original Message-----
>> From: Alexey Melnikov [mailto:alexey.melnikov@isode.com]
>> Sent: Monday, March 05, 2012 4:00 AM
>> To: Murray S. Kucherawy
>> Cc:ietf@ietf.org
>> Subject: Re: Last Call:<draft-melnikov-smtp-priority-07.txt>  (Simple
>> Mail Transfer Protocol extension for Message Transfer Priorities) to
>> Proposed Standard
>>> - Section 4.3 says "For example, once an MTA accepts a message, the MTA MUST NOT change a (syntactically valid) priority value if the MTA
>>> doesn't support it."  There seems to be a chicken-and-egg going on
>>> here: If the MTA doesn't support the extension, how can it know not to
>>> change the priority outbound?
>>>
>> I meant "supports the extension, but doesn't support a particular value
>> as distinct priority level". Suggestions on how to make this clear
>> would be appreciated.
> Suggest:
>
> For example, once an MTA accepts a message, the MTA MUST not change a (syntactically valid) priority value if that value is not supported by the MTA's implementation of this extension.
Ok, changed.
>>> - There are lots of SHOULDs in here that might benefit from example
>>> situations in which one might deviate from the normative statement
>>> containing the SHOULD.
>> I will review. I had some discussion with SM about some of these and
>> argued that not all of them should be explained. But I agree that some
>> of them need explanation.
> There are some that are in more need of this than others, and I know lately that I've been thanked by ADs during IESG evaluation for providing this kind of text, so it can only help where it's possible to provide it.
Sure. I've asked for explanation while I was on IESG as well.

>>> - Section 11: Why use "PRI" and not "priority"?  The existing set of
>>> Received clause names are lowercase words, so it seems strange to
>>> deviate.
>> I don't mind to switching to "PRIORITY". But section 4.4 of RFC 5321
>> uses uppercase variants (and yes, I know they are case insensitive).
> I don't think I've ever seen them in the wild, which is why it caught my attention.
I've changed "PRI" to "PRIORITY" in my copy.


From alexey.melnikov@isode.com  Tue Mar  6 02:50:53 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 1FC8221F8823 for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 02:50:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.808
X-Spam-Level: 
X-Spam-Status: No, score=-101.808 tagged_above=-999 required=5 tests=[AWL=-0.201, 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 ApJ+okpnoPUi for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 02:50:52 -0800 (PST)
Received: from rufus.isode.com (cl-125.lon-03.gb.sixxs.net [IPv6:2a00:14f0:e000:7c::2]) by ietfa.amsl.com (Postfix) with ESMTP id 436A021F8814 for <ietf@ietf.org>; Tue,  6 Mar 2012 02:50:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1331031051; d=isode.com; s=selector; i=@isode.com; bh=gW6W4M9lQam+mmBPO4JflsJfnaEOICI8w9T4CrXzjHo=; 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=he6zpSlC3NiC646FqnN8IuYbuwgcYZsrtroJBdKeidBk82rFRDFqrwBm0h3euyeQmk8SMZ Y1x3MbF8CQs1NnHLfdqekVIE45XalN+DmX5wqbhbDpKLkQ7/+AZymU4Tjy9gYjckFoZnsC GnuxW/hWhIcQJRtaT7KaePJEUhF81ZY=;
Received: from [172.16.1.29] (shiny.isode.com [62.3.217.250])  by rufus.isode.com (submission channel) via TCP with ESMTPSA  id <T1XsCABhuqXM@rufus.isode.com>; Tue, 6 Mar 2012 10:50:51 +0000
Message-ID: <4F553F2C.3050100@isode.com>
Date: Mon, 05 Mar 2012 22:33:16 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:9.0) Gecko/20111222 Thunderbird/9.0.1
To: Ned Freed <ned.freed@mrochek.com>
Subject: Re: Last Call: <draft-melnikov-smtp-priority-07.txt>  (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard
References: <20120301004219.15266.76505.idtracker@ietfa.amsl.com> <CAC4RtVDeXwCLh9R_bNmLwEC5g_4Dv9HadOpXMwbSz5RT2m+jUg@mail.gmail.com> <CAC4RtVB1G_HjYNug0Fvq7LPSnzqG2KxH-PY6nv=nBZKv-uXTLA@mail.gmail.com> <01OCM8WDJZKI00ZUIL@mauve.mrochek.com> <4F54C9B1.4010100@isode.com> <01OCQZ44DUX800ZUIL@mauve.mrochek.com>
In-Reply-To: <01OCQZ44DUX800ZUIL@mauve.mrochek.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Pete Resnick <presnick@qualcomm.com>, 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, 06 Mar 2012 10:50:53 -0000

Hi Ned,

On 05/03/2012 15:34, Ned Freed wrote:
>> > That said, I think an important omission in this document is that it
>> > only allows MSA's to change message priorities to conform to site 
>> policy.
>> > MTAs should also be allowed to do this.
>
>> Can you elaborate a bit more on possible use cases?
>
> Nobody is going to simply allow priorities to be set willy-nilly on 
> mail coming
> from random sources outside their administrative domain. That's absurd.
Agreed.
> However, they may be will to make bilateral arrangements with selected
> partners, identified by IP address or whatever, that would allow such a
> setting, perhaps within a restricted range of allowed values.
Right. Not allowing this actually bothered me. So I've reworded to allow 
for that.
>> Would such an MTA
>> only lower the priority or do you think it might also raise it?
>
> I don't see any reason to limit it to lowering it.
>
>> > Another issue is the silly prohibition against using Priority: and 
>> other header
>> > fields to set priority levels. What if is existing site policy is 
>> in fact to
>> > use those fields to determine message priority?
>
>> (Ignoring the question of whether use of MT-Priority header field is a
>> good thing or not for a moment.)
>
>> I actually don't have a strong feeling against usage of other existing
>> header fields.  Some of the existing header fields don't have the exact
>> semantics desired here.
>
> Well, sure. You most definitely don't want to mix in Importance or other
> MUA level priority fields.
>
>> Others (like the MIXER's Priority) have the right semantics but don't 
>> support
>> sufficient number of priorities required by MMHS (6 levels).
>
> I think you're going to have to accept the fact that the overwhelming 
> majority
> of people out there running email systems have never even heard of 
> MMHS and
> even if they have don't give a damn about faithfully retaining it's
> semantics. But they do care that new mechanism be made compatible with
> whatever ad-hoc scheme they are currently using, even if said scheme
> doesn't have the full range of values.
>
> For example, I can easily see a site wanting to map this to and from 
> the field
> used by Microsoft Exchange (sorry, I forget the exact name) even 
> though if
> memory serves that field only accepts three values. And either this is 
> going to
> happen no matter what the specification says, or the specification 
> simply won't
> deploy in any meaningful way.
Ok, I tend to agree. Our implementation will do this kind of mapping in 
absence of MT-Priority anyway.
>> That is why a new header field was introduced.
>
>> But anyway, I am happy for this restriction to be removed/relaxed. 
>> Can you
>> recommend some specific text?
>
> I'll try to do so later this week.
Is the following better:

<t>The Importance <xref target="RFC2156"/> header field MUST NOT be used 
for determining
       the priority under this "Priority Message Handling" SMTP extension.
       In absence of both the PRIORITY MAIL FROM parameter and the 
MT-Priority header field,
       other message header fields, such as Priority <xref 
target="RFC2156"/> and X-Priority,
       MAY be used for determining the priority under this "Priority 
Message Handling" SMTP extension.
</t>
?


From daedulus@btconnect.com  Tue Mar  6 03:32:46 2012
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 974D621F883B for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 03:32:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.142
X-Spam-Level: 
X-Spam-Status: No, score=-2.142 tagged_above=-999 required=5 tests=[AWL=0.457,  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 PzQ0k-zQdFC3 for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 03:32:46 -0800 (PST)
Received: from mail.btconnect.com (c2bthomr10.btconnect.com [213.123.20.128]) by ietfa.amsl.com (Postfix) with ESMTP id 8AD1121F8834 for <ietf@ietf.org>; Tue,  6 Mar 2012 03:32:45 -0800 (PST)
Received: from host86-163-139-217.range86-163.btcentralplus.com (HELO pc6) ([86.163.139.217]) by c2bthomr10.btconnect.com with SMTP id GPP36030; Tue, 06 Mar 2012 11:32:11 +0000 (GMT)
Message-ID: <029b01ccfb84$4e4e2220$4001a8c0@gateway.2wire.net>
From: "t.petch" <daedulus@btconnect.com>
To: "John C Klensin" <john-ietf@jck.com>, <stbryant@cisco.com>
References: <20120222151252.32262.82157.idtracker@ietfa.amsl.com><03a301ccf174$ff953290$febf97b0$@olddog.co.uk><515703B08A3A064C9CC8C09ACCC710DC0631679E@XMB-RCD-103.cisco.com><C71DA9B1-A61F-4C5D-8DCE-3702271CBB6D@vigilsec.com><4F4FA70B.2030906@pi.nu><D0F60388-D852-4815-917A-B14BF40C64FB@vigilsec.com><BD60EA38ED03AF5A21868DF1@PST.JCK.COM> <4F4FC252.9010001@cisco.com> <C3E581FB44D46BF4128A2229@PST.JCK.COM>
Subject: Re: Last Call:<draft-betts-itu-oam-ach-code-point-03.txt>	(Allocation of anAssociated Channel Code Point for Use by	ITU-T Ethernet basedOAM) to Informational RFC
Date: Tue, 6 Mar 2012 11:31:31 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Mirapoint-IP-Reputation: reputation=Fair-1, source=Queried, refid=tid=0001.0A0B0303.4F55F5BB.0033, actions=tag
X-Junkmail-Premium-Raw: score=7/50, refid=2.7.2:2012.3.6.103624:17:7.944, ip=86.163.139.217, rules=__HAS_MSGID, __OUTLOOK_MSGID_1, __SANE_MSGID, __TO_MALFORMED_2, __BOUNCE_CHALLENGE_SUBJ, __BOUNCE_NDR_SUBJ_EXEMPT, __MIME_VERSION, __CT, CT_TP_8859_1, __CT_TEXT_PLAIN, __CTE, __HAS_X_PRIORITY, __HAS_MSMAIL_PRI, __HAS_X_MAILER, USER_AGENT_OE, __OUTLOOK_MUA_1, __USER_AGENT_MS_GENERIC, __ANY_URI, __URI_NO_PATH, BODY_SIZE_3000_3999, __MIME_TEXT_ONLY, RDNS_GENERIC_POOLED, HTML_00_01, HTML_00_10, BODY_SIZE_5000_LESS, RDNS_SUSP_GENERIC, __OUTLOOK_MUA, RDNS_SUSP, BODY_SIZE_7000_LESS
X-Junkmail-Status: score=10/50, host=c2bthomr10.btconnect.com
X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A0B0206.4F55F5BB.0185,ss=1,re=0.000,fgs=0, ip=0.0.0.0, so=2011-07-25 19:15:43, dmn=2011-05-27 18:58:46, mode=multiengine
X-Junkmail-IWF: false
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Mar 2012 11:32:46 -0000

I am finding myself with some unfamiliar bedfellows on this issue, but yes, it
should be approved - see inline.

Tom Petch

----- Original Message -----
From: "John C Klensin" <john-ietf@jck.com>
To: <stbryant@cisco.com>
Cc: <ietf@ietf.org>
Sent: Friday, March 02, 2012 12:04 AM
Subject: Re: Last Call:<draft-betts-itu-oam-ach-code-point-03.txt> (Allocation
of anAssociated Channel Code Point for Use by ITU-T Ethernet basedOAM) to
Informational RFC


 <snip>

> (2) Whether it is reasonable or appropriate for the IETF to use
> our responsibility for code point assignments and consequent
> relationship with IANA to try to keep protocols that are not
> consistent with our design judgment and aesthetics --no matter
> how grounded in experience and good engineering-- off the
> Internet.  That is the "Internet gatekeeper" function about
> which, as you know, I've expressed concern in other contexts.  I
> think the answer has got to be "we can, should, and always will
> exercise quality control on stable specifications and normative
> references but, unless we can justify being sure of our own
> infallibility, we cannot and should not try to prevent another
> body from deploying a specification on the Internet by using our
> control of the registration model".   Telling people why we
> think their ideas are sub-optimal is fine, as is identifying any
> risks we see in appropriate and visible places, but telling
> another group what they can't do because the IETF doesn't like
> the idea isn't.

We claim ownership of the name space on behalf of all parties, all SDOs
governments, NGOs, anyone and anything, and this gives us a special
responsibility to exercise that wisely.  We should beware of imposing
our ideas of correctness of any kind on another SDO - that is up to
 them to decide, not us.

Of course, one open technical solution to a problem is best but the RFC
Series is suitable cluttered with instances of the IETF failing to achieve
that so any argument based on those grounds is hypocritical.

A stable, approved reference is ideal, but we have been told of the
widespread deployment of this approach using an experimental
code point so the running code very much exists.   If that is camping
on something that it would be better if it were not, then that is
something to fix, and something we can fix.

There is no reason not to approve the allocation of a code point
and furthermore, I believe we should do it now, to facilitate the migration
of the existing boxes to an approved solution.  If that leaves another
SDO with an incompatability between what is working and what
their documents say, well, the IETF has been there too; not a
good place to be, but it is up to the SDO to resolve that, not
the IETF.

Tom Petch

> And I think that distinction is entirely consistent with Russ's
> suggestion.
>
> best,
>    john
>
>
>
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>
>


From lear@cisco.com  Tue Mar  6 03:46:59 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 3F34C21F8834 for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 03:46:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.241
X-Spam-Level: 
X-Spam-Status: No, score=-110.241 tagged_above=-999 required=5 tests=[AWL=-0.243, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_15=0.6, 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 5J6xgmgpsqsy for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 03:46:58 -0800 (PST)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by ietfa.amsl.com (Postfix) with ESMTP id CF22421F8877 for <ietf@ietf.org>; Tue,  6 Mar 2012 03:46:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=lear@cisco.com; l=6245; q=dns/txt; s=iport; t=1331034418; x=1332244018; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to; bh=DotR4+mwu/puz6v8sdwrYVWqtpdjrOR7D0KX+KMUtSM=; b=WbbCyN+zeqdVPKgO8rxYIMjmnySFX4meFZRXbBEimBKFgYqpaq4zV0YQ iWJl6ZOMXiPkZB177WHF6vSGD8woDGKyTtaV1RiE+3AEwZHPw/TnPe4Gr eW2xZNhQXt7TokOdjTOHbgCDjmWHROMvAC5akaBKTeYgKDKpGeqpiKM4p c=;
X-IronPort-AV: E=Sophos;i="4.73,539,1325462400"; d="scan'208,217";a="67780050"
Received: from ams-core-1.cisco.com ([144.254.72.81]) by ams-iport-2.cisco.com with ESMTP; 06 Mar 2012 11:46:56 +0000
Received: from dhcp-10-55-81-19.cisco.com (dhcp-10-55-81-19.cisco.com [10.55.81.19]) by ams-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id q26BkuOB010282; Tue, 6 Mar 2012 11:46:56 GMT
Message-ID: <4F55F92F.1020105@cisco.com>
Date: Tue, 06 Mar 2012 12:46:55 +0100
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: "t.petch" <daedulus@btconnect.com>
Subject: Re: Last Call:<draft-betts-itu-oam-ach-code-point-03.txt>	(Allocation of anAssociated Channel Code Point for Use by	ITU-T Ethernet basedOAM) to Informational RFC
References: <20120222151252.32262.82157.idtracker@ietfa.amsl.com><03a301ccf174$ff953290$febf97b0$@olddog.co.uk><515703B08A3A064C9CC8C09ACCC710DC0631679E@XMB-RCD-103.cisco.com><C71DA9B1-A61F-4C5D-8DCE-3702271CBB6D@vigilsec.com><4F4FA70B.2030906@pi.nu><D0F60388-D852-4815-917A-B14BF40C64FB@vigilsec.com><BD60EA38ED03AF5A21868DF1@PST.JCK.COM> <4F4FC252.9010001@cisco.com> <C3E581FB44D46BF4128A2229@PST.JCK.COM> <029b01ccfb84$4e4e2220$4001a8c0@gateway.2wire.net>
In-Reply-To: <029b01ccfb84$4e4e2220$4001a8c0@gateway.2wire.net>
X-Enigmail-Version: 1.3.5
Content-Type: multipart/alternative; boundary="------------070309040101010505010008"
Cc: John C Klensin <john-ietf@jck.com>, ietf@ietf.org, stbryant@cisco.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Mar 2012 11:46:59 -0000

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

Hi,

I speak now as an individual and in no other capacity with no other hats on.


On 3/6/12 11:31 AM, t.petch wrote:
> I am finding myself with some unfamiliar bedfellows on this issue, but yes, it
> should be approved - see inline.
>
>
> We claim ownership of the name space on behalf of all parties, all SDOs
> governments, NGOs, anyone and anything, and this gives us a special
> responsibility to exercise that wisely.  We should beware of imposing
> our ideas of correctness of any kind on another SDO - that is up to
>  them to decide, not us.

Our responsibility is to ourselves first and foremost, and to see that
our process is followed.  That process exists to, amongst other things,
insure safe use and interoperable use of our own protocols.

Here the process for approval of a codepoint calls for IETF review. 
That is this.  IETF Review is defined as follows in RFC-5226:

            IETF Review - (Formerly called "IETF Consensus" in
            [IANA-CONSIDERATIONS]) New values are assigned only through
            RFCs that have been shepherded through the IESG as AD-
            Sponsored or IETF WG Documents [RFC3932] [RFC3978].  The
            intention is that the document and proposed assignment will
            be reviewed by the IESG and appropriate IETF WGs (or
            experts, if suitable working groups no longer exist) to
            ensure that the proposed assignment will not negatively
            impact interoperability or otherwise extend IETF protocols
            in an inappropriate or damaging manner.

In addition, we have spoken on what it means for other SDOs to request
code points in RFC-4775 Section 3.2, which says, in part:


   Experience shows that the importance of this is often underestimated
   during extension design; designers sometimes assume that a new
   codepoint is theirs for the asking, or even simply for the taking.
   This is hazardous; it is far too likely that someone just taking a
   protocol value will find that the same value will later be formally
   assigned to another function, thus guaranteeing an interoperability
   problem.


Our processes direct us to consider a codepoint assignment in this
light.  Finally:


>
> There is no reason not to approve the allocation of a code point

The purpose of this review is to determine whether or not there is
reason *not* to approve.  Others disagree with you.


Eliot


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

<html>
  <head>
    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    Hi,<br>
    <br>
    I speak now as an individual and in no other capacity with no other
    hats on.<br>
    <br>
    <br>
    On 3/6/12 11:31 AM, t.petch wrote:
    <blockquote
      cite="mid:029b01ccfb84$4e4e2220$4001a8c0@gateway.2wire.net"
      type="cite">
      <pre wrap="">I am finding myself with some unfamiliar bedfellows on this issue, but yes, it
should be approved - see inline.


We claim ownership of the name space on behalf of all parties, all SDOs
governments, NGOs, anyone and anything, and this gives us a special
responsibility to exercise that wisely.  We should beware of imposing
our ideas of correctness of any kind on another SDO - that is up to
 them to decide, not us.</pre>
    </blockquote>
    <br>
    Our responsibility is to ourselves first and foremost, and to see
    that our process is followed.  That process exists to, amongst other
    things, insure safe use and interoperable use of our own protocols.<br>
    <br>
    Here the process for approval of a codepoint calls for IETF review. 
    That is this.  IETF Review is defined as follows in RFC-5226:<br>
    <br>
                IETF Review - (Formerly called "IETF Consensus" in<br>
                [IANA-CONSIDERATIONS]) New values are assigned only
    through<br>
                RFCs that have been shepherded through the IESG as AD-<br>
                Sponsored or IETF WG Documents [RFC3932] [RFC3978].  The<br>
                intention is that the document and proposed assignment
    will<br>
                be reviewed by the IESG and appropriate IETF WGs (or<br>
                experts, if suitable working groups no longer exist) to<br>
                ensure that the proposed assignment will not negatively<br>
                impact interoperability or otherwise extend IETF
    protocols<br>
                in an inappropriate or damaging manner.<br>
    <br>
    In addition, we have spoken on what it means for other SDOs to
    request code points in RFC-4775 Section 3.2, which says, in part:<br>
    <br>
    <br>
       Experience shows that the importance of this is often
    underestimated<br>
       during extension design; designers sometimes assume that a new<br>
       codepoint is theirs for the asking, or even simply for the
    taking.<br>
       This is hazardous; it is far too likely that someone just taking
    a<br>
       protocol value will find that the same value will later be
    formally<br>
       assigned to another function, thus guaranteeing an
    interoperability<br>
       problem.<br>
    <br>
    <br>
    Our processes direct us to consider a codepoint assignment in this
    light.  Finally:<br>
    <br>
    <br>
    <blockquote
      cite="mid:029b01ccfb84$4e4e2220$4001a8c0@gateway.2wire.net"
      type="cite">
      <pre wrap="">

There is no reason not to approve the allocation of a code point
</pre>
    </blockquote>
    <br>
    The purpose of this review is to determine whether or not there is
    reason <b>not</b> to approve.  Others disagree with you.<br>
    <br>
    <br>
    Eliot<br>
    <br>
  </body>
</html>

--------------070309040101010505010008--

From fanf2@hermes.cam.ac.uk  Tue Mar  6 05:15:23 2012
Return-Path: <fanf2@hermes.cam.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C3FB221F85F1 for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 05:15:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.687
X-Spam-Level: 
X-Spam-Status: No, score=-5.687 tagged_above=-999 required=5 tests=[AWL=-0.577, BAYES_05=-1.11, 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 eOQZQCnWthxk for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 05:15:23 -0800 (PST)
Received: from ppsw-50.csi.cam.ac.uk (ppsw-50.csi.cam.ac.uk [131.111.8.150]) by ietfa.amsl.com (Postfix) with ESMTP id 8D47B21F85DA for <ietf@ietf.org>; Tue,  6 Mar 2012 05:15:22 -0800 (PST)
X-Cam-AntiVirus: no malware found
X-Cam-SpamDetails: not scanned
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
Received: from hermes-2.csi.cam.ac.uk ([131.111.8.54]:48547) by ppsw-50.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.157]:25) with esmtpa (EXTERNAL:fanf2) id 1S4uEX-0001HW-rt (Exim 4.72) (return-path <fanf2@hermes.cam.ac.uk>); Tue, 06 Mar 2012 13:15:17 +0000
Received: from fanf2 (helo=localhost) by hermes-2.csi.cam.ac.uk (hermes.cam.ac.uk) with local-esmtp id 1S4uEX-0003vk-LT (Exim 4.67) (return-path <fanf2@hermes.cam.ac.uk>); Tue, 06 Mar 2012 13:15:17 +0000
Date: Tue, 6 Mar 2012 13:15:17 +0000
From: Tony Finch <dot@dotat.at>
X-X-Sender: fanf2@hermes-2.csi.cam.ac.uk
To: Mark Andrews <marka@isc.org>
Subject: Re: provisioning software, was DNS RRTYPEs, the difficulty with
In-Reply-To: <20120306054213.1C1F91E19F87@drugs.dv.isc.org>
Message-ID: <alpine.LSU.2.00.1203061314260.22944@hermes-2.csi.cam.ac.uk>
References: <20120306044628.87718.qmail@joyce.lan> <77075C8C-04ED-48A2-B501-B2296BCFC8C6@frobbit.se> <20120306054213.1C1F91E19F87@drugs.dv.isc.org>
User-Agent: Alpine 2.00 (LSU 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: Tony Finch <fanf2@hermes.cam.ac.uk>
Cc: John Levine <johnl@iecc.com>, Alessandro Vesely <vesely@tana.it>, "ietf@ietf.org Discussion" <ietf@ietf.org>, =?ISO-8859-15?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Mar 2012 13:15:23 -0000

Mark Andrews <marka@isc.org> wrote:
>
> I would say DNS master file representation -> DNS wire representation
> is one of the main issues on the provisioning side.  This conversion
> needs to be done at some point.

John's draft addresses that.

> The other this is verification of the input.

What kind of verification?

Tony.
-- 
f.anthony.n.finch  <dot@dotat.at>  http://dotat.at/
Plymouth, Biscay: Variable 4, becoming west 5 to 7. Moderate or rough. Rain or
showers. Good, occasionally poor.

From xavier.marjou@gmail.com  Tue Mar  6 05:41:33 2012
Return-Path: <xavier.marjou@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 60C4A21F87B4 for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 05:41:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Abw1hMthZPdu for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 05:41:33 -0800 (PST)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id B05F421F8782 for <ietf@ietf.org>; Tue,  6 Mar 2012 05:41:32 -0800 (PST)
Received: by ggmi1 with SMTP id i1so2461352ggm.31 for <ietf@ietf.org>; Tue, 06 Mar 2012 05:41:32 -0800 (PST)
Received-SPF: pass (google.com: domain of xavier.marjou@gmail.com designates 10.60.26.8 as permitted sender) client-ip=10.60.26.8; 
Authentication-Results: mr.google.com; spf=pass (google.com: domain of xavier.marjou@gmail.com designates 10.60.26.8 as permitted sender) smtp.mail=xavier.marjou@gmail.com; dkim=pass header.i=xavier.marjou@gmail.com
Received: from mr.google.com ([10.60.26.8]) by 10.60.26.8 with SMTP id h8mr9808994oeg.15.1331041292102 (num_hops = 1); Tue, 06 Mar 2012 05:41:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=93NrjxN1VJk2LNX0ctGA6BQ2g1OAYLUzHbMy9gMh0cM=; b=kImsDxaBoBZDWtI0ObHxYWO1Js6+ecLI/KmkQ7Kua9hkY41xFNvqiwHVVcU1WQMPDq 2J3dGTWq7j7Vaxvga9wujAMtL2xXbgI/vIP8npeKixWoYTnvSVJclOItYGomKMFQwNrD X8/0qijZasw4kFmKSz+Hu5/t6n8t/DSGTwab4qSJ7FsfHZPpYZzVZmLO/BNJlAivBAn9 AgSS+dZJDjfxuVsT/h39IY5zgdu0HCQiMbV/FGsEpIuC2xUsNIIUNI2RnfBUYO9Gyy+V Q2iVammkjxGShR/aLc46lyg+3Q/93/Tml6Fm2h34rqwTMLb0OHMVeoU1DSRvMbe4b8Al YveQ==
MIME-Version: 1.0
Received: by 10.60.26.8 with SMTP id h8mr8522430oeg.15.1331041292057; Tue, 06 Mar 2012 05:41:32 -0800 (PST)
Received: by 10.60.2.70 with HTTP; Tue, 6 Mar 2012 05:41:32 -0800 (PST)
Date: Tue, 6 Mar 2012 14:41:32 +0100
Message-ID: <CAErhfrxPe=KSKB7fVHLankkk5XRQ87oarg17kXqNB0o0jGD4hw@mail.gmail.com>
Subject: Add a link to the HTML version in i-d-announce mails ?
From: Xavier Marjou <xavier.marjou@gmail.com>
To: IETF Discussion <ietf@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Mar 2012 13:41:33 -0000

As a subscriber of the i-d-announce@ietf.org list, I generally prefer
reading the HTML version of the draft rather than the TXT version.

I thus often need to manually rewrite the TXT link to fetch the HTML
version of the draft. I can not believe I'm the only one.

Hence, would it be possible to also include a link like
http://tools.ietf.org/html/draft-name in the mail of the announced
draft?

Cheers,
Xavier

From julian.reschke@gmx.de  Tue Mar  6 05:51:59 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 8CCE921F886A for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 05:51:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.484
X-Spam-Level: 
X-Spam-Status: No, score=-104.484 tagged_above=-999 required=5 tests=[AWL=-1.885, 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 6yDO8zdXnUe1 for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 05:51:57 -0800 (PST)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by ietfa.amsl.com (Postfix) with SMTP id A06CD21F862A for <ietf@ietf.org>; Tue,  6 Mar 2012 05:51:56 -0800 (PST)
Received: (qmail invoked by alias); 06 Mar 2012 13:51:53 -0000
Received: from mail.greenbytes.de (EHLO [192.168.1.140]) [217.91.35.233] by mail.gmx.net (mp038) with SMTP; 06 Mar 2012 14:51:53 +0100
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX193CGlRbOd3cLYOQXF88ehwoDI/fVvhPyg3PBCp10 LzdDRaqRMt7LQv
Message-ID: <4F561677.9030401@gmx.de>
Date: Tue, 06 Mar 2012 14:51:51 +0100
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: Xavier Marjou <xavier.marjou@gmail.com>
Subject: Re: Add a link to the HTML version in i-d-announce mails ?
References: <CAErhfrxPe=KSKB7fVHLankkk5XRQ87oarg17kXqNB0o0jGD4hw@mail.gmail.com>
In-Reply-To: <CAErhfrxPe=KSKB7fVHLankkk5XRQ87oarg17kXqNB0o0jGD4hw@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Mar 2012 13:51:59 -0000

On 2012-03-06 14:41, Xavier Marjou wrote:
> As a subscriber of the i-d-announce@ietf.org list, I generally prefer
> reading the HTML version of the draft rather than the TXT version.
>
> I thus often need to manually rewrite the TXT link to fetch the HTML
> version of the draft. I can not believe I'm the only one.
>
> Hence, would it be possible to also include a link like
> http://tools.ietf.org/html/draft-name in the mail of the announced
> draft?
> ...

+1000

From simon.perreault@viagenie.ca  Tue Mar  6 05:53:52 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 E6EBD21F8864 for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 05:53:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.543
X-Spam-Level: 
X-Spam-Status: No, score=-2.543 tagged_above=-999 required=5 tests=[AWL=0.057,  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 dr+YSRt0rXVH for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 05:53:52 -0800 (PST)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by ietfa.amsl.com (Postfix) with ESMTP id 5D27021F8826 for <ietf@ietf.org>; Tue,  6 Mar 2012 05:53:52 -0800 (PST)
Received: from ringo.viagenie.ca (unknown [IPv6:2620:0:230:c000:a11b:9b29:9caf:fd8a]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 9FE9420E2E for <ietf@ietf.org>; Tue,  6 Mar 2012 08:53:51 -0500 (EST)
Message-ID: <4F5616EF.8010004@viagenie.ca>
Date: Tue, 06 Mar 2012 08:53:51 -0500
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: ietf@ietf.org
Subject: Re: Add a link to the HTML version in i-d-announce mails ?
References: <CAErhfrxPe=KSKB7fVHLankkk5XRQ87oarg17kXqNB0o0jGD4hw@mail.gmail.com> <4F561677.9030401@gmx.de>
In-Reply-To: <4F561677.9030401@gmx.de>
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, 06 Mar 2012 13:53:53 -0000

On 2012-03-06 08:51, Julian Reschke wrote:
> On 2012-03-06 14:41, Xavier Marjou wrote:
>> As a subscriber of the i-d-announce@ietf.org list, I generally prefer
>> reading the HTML version of the draft rather than the TXT version.
>>
>> I thus often need to manually rewrite the TXT link to fetch the HTML
>> version of the draft. I can not believe I'm the only one.
>>
>> Hence, would it be possible to also include a link like
>> http://tools.ietf.org/html/draft-name in the mail of the announced
>> draft?
>> ...
>
> +1000

+INT_MAX

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 ynir@checkpoint.com  Tue Mar  6 05:56:31 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 E0E8B21F88AC for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 05:56:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.463
X-Spam-Level: 
X-Spam-Status: No, score=-10.463 tagged_above=-999 required=5 tests=[AWL=0.136, 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 kFKd8oAp4Cxe for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 05:56:31 -0800 (PST)
Received: from michael.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id DF83A21F88AB for <ietf@ietf.org>; Tue,  6 Mar 2012 05:56:30 -0800 (PST)
Received: from il-ex01.ad.checkpoint.com (il-ex01.ad.checkpoint.com [194.29.34.26]) by michael.checkpoint.com (8.13.8/8.13.8) with ESMTP id q26DuSwP014992;  Tue, 6 Mar 2012 15:56:28 +0200
X-CheckPoint: {4F5617E2-0-1B221DC2-5FFFF}
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; Tue, 6 Mar 2012 15:56:27 +0200
Received: from il-ex01.ad.checkpoint.com ([126.0.0.2]) by il-ex03.ad.checkpoint.com ([194.29.34.71]) with mapi; Tue, 6 Mar 2012 15:56:27 +0200
From: Yoav Nir <ynir@checkpoint.com>
To: Xavier Marjou <xavier.marjou@gmail.com>
Date: Tue, 6 Mar 2012 15:56:29 +0200
Subject: Re: Add a link to the HTML version in i-d-announce mails ?
Thread-Topic: Add a link to the HTML version in i-d-announce mails ?
Thread-Index: Acz7oOxwerhfCOfDTBGvTTyGVSWEbg==
Message-ID: <C0545B4B-84B4-41DD-91CA-D8C4A6754D61@checkpoint.com>
References: <CAErhfrxPe=KSKB7fVHLankkk5XRQ87oarg17kXqNB0o0jGD4hw@mail.gmail.com>
In-Reply-To: <CAErhfrxPe=KSKB7fVHLankkk5XRQ87oarg17kXqNB0o0jGD4hw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-KSE-AntiSpam-Interceptor-Info: protection disabled
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Mar 2012 13:56:32 -0000

Even better, also add the XML2RFC output if it's available at the same time=
:  http://tools.ietf.org/id/draft-name.html

for example, (just picking my own latest draft as an example): http://tools=
.ietf.org/id/draft-nir-websec-extended-origin-02.html

I don't know which drafts get this version (perhaps those submitted along w=
ith XML?), but they're sure easier to read than TXT.

Yoav

On Mar 6, 2012, at 3:41 PM, Xavier Marjou wrote:

> As a subscriber of the i-d-announce@ietf.org list, I generally prefer
> reading the HTML version of the draft rather than the TXT version.
>=20
> I thus often need to manually rewrite the TXT link to fetch the HTML
> version of the draft. I can not believe I'm the only one.
>=20
> Hence, would it be possible to also include a link like
> http://tools.ietf.org/html/draft-name in the mail of the announced
> draft?
>=20
> Cheers,
> Xavier


From framefritti@gmail.com  Tue Mar  6 06:02:26 2012
Return-Path: <framefritti@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8AF7421F88F6 for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 06:02:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wh+iJDylbsOE for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 06:02:25 -0800 (PST)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id E11F821F8904 for <ietf@ietf.org>; Tue,  6 Mar 2012 06:02:23 -0800 (PST)
Received: by ggmi1 with SMTP id i1so2477891ggm.31 for <ietf@ietf.org>; Tue, 06 Mar 2012 06:02:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=WDss+0LnFa9H6Zxo8yVqVYiNWxt5SDzP+SWDwR5Yrg4=; b=bpt+5wUDLO+8AmcaEvi7l6sp0IG9LF4PQPBNHBG6irl3GJ4ZmmT+O+/JfsfjrnGHDB ZXGxmxDiW6CNqDxeil0qNzqR+uzUN/HrK63PWU6u0CriYp5WBZbSIqju88BjsJ27Hbyd 8efGoOs9G31JRsnsztYPJ1OoIDtIp88IKK2kp230mKUnlrzVbuEa32l09QDhin6Du2F4 pT4oozIQ5B7b9t2v/4vEuMxvMeqM3pFX45208dJwNdI7OSSe7tyr7KnwKpZTh3EZip7a 5rb+MSBYXDYlaCXuPShW469pF0caoz2pgODCODj2u9rsMyLXTM1OsNY2XN5Ix2pN6XNO j2tg==
MIME-Version: 1.0
Received: by 10.50.189.134 with SMTP id gi6mr8676928igc.18.1331042533053; Tue, 06 Mar 2012 06:02:13 -0800 (PST)
Received: by 10.231.185.219 with HTTP; Tue, 6 Mar 2012 06:02:12 -0800 (PST)
In-Reply-To: <4F5616EF.8010004@viagenie.ca>
References: <CAErhfrxPe=KSKB7fVHLankkk5XRQ87oarg17kXqNB0o0jGD4hw@mail.gmail.com> <4F561677.9030401@gmx.de> <4F5616EF.8010004@viagenie.ca>
Date: Tue, 6 Mar 2012 15:02:12 +0100
Message-ID: <CABSMSPWxX4TkYT+_PojryUWN1JrXROXq9aBenK5ufRgBzOrFYQ@mail.gmail.com>
Subject: Re: Add a link to the HTML version in i-d-announce mails ?
From: Riccardo Bernardini <framefritti@gmail.com>
To: ietf@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Mar 2012 14:02:26 -0000

On Tue, Mar 6, 2012 at 2:53 PM, Simon Perreault
<simon.perreault@viagenie.ca> wrote:
> On 2012-03-06 08:51, Julian Reschke wrote:
>>
>> On 2012-03-06 14:41, Xavier Marjou wrote:
>>>
>>> As a subscriber of the i-d-announce@ietf.org list, I generally prefer
>>> reading the HTML version of the draft rather than the TXT version.
>>>
>>> I thus often need to manually rewrite the TXT link to fetch the HTML
>>> version of the draft. I can not believe I'm the only one.
>>>
>>> Hence, would it be possible to also include a link like
>>> http://tools.ietf.org/html/draft-name in the mail of the announced
>>> draft?
>>> ...
>>
>>
>> +1000
>
>
> +INT_MAX

+\aleph_0 :-)

Seriously, it would be really nice to have this feature.


>
> Simon
> --
> DTN made easy, lean, and smart --> http://postellation.viagenie.ca
> NAT64/DNS64 open-source =A0 =A0 =A0 =A0--> http://ecdysis.viagenie.ca
> STUN/TURN server =A0 =A0 =A0 =A0 =A0 =A0 =A0 --> http://numb.viagenie.ca
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf

From julian.reschke@gmx.de  Tue Mar  6 06:04:22 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 D50E821F890F for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 06:04:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.465
X-Spam-Level: 
X-Spam-Status: No, score=-104.465 tagged_above=-999 required=5 tests=[AWL=-1.866, 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 y9mSZzfzDV65 for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 06:04:22 -0800 (PST)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by ietfa.amsl.com (Postfix) with SMTP id E34F421F890B for <ietf@ietf.org>; Tue,  6 Mar 2012 06:04:21 -0800 (PST)
Received: (qmail invoked by alias); 06 Mar 2012 14:04:20 -0000
Received: from mail.greenbytes.de (EHLO [192.168.1.140]) [217.91.35.233] by mail.gmx.net (mp035) with SMTP; 06 Mar 2012 15:04:20 +0100
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX19d69ork4tdX5UnhXtQ0w76cUkiCpSk1mi1UhIWcp FEywlLzXmE1/4z
Message-ID: <4F561962.8040705@gmx.de>
Date: Tue, 06 Mar 2012 15:04:18 +0100
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: Yoav Nir <ynir@checkpoint.com>
Subject: Re: Add a link to the HTML version in i-d-announce mails ?
References: <CAErhfrxPe=KSKB7fVHLankkk5XRQ87oarg17kXqNB0o0jGD4hw@mail.gmail.com> <C0545B4B-84B4-41DD-91CA-D8C4A6754D61@checkpoint.com>
In-Reply-To: <C0545B4B-84B4-41DD-91CA-D8C4A6754D61@checkpoint.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Mar 2012 14:04:22 -0000

On 2012-03-06 14:56, Yoav Nir wrote:
> Even better, also add the XML2RFC output if it's available at the same time:  http://tools.ietf.org/id/draft-name.html
>
> for example, (just picking my own latest draft as an example): http://tools.ietf.org/id/draft-nir-websec-extended-origin-02.html

+1

> I don't know which drafts get this version (perhaps those submitted along with XML?), but they're sure easier to read than TXT.

Indeed I'd like to understand that as well. In particular, as this 
apparently runs an outdated version of rfc2629.xslt, and then mangles 
it's output (HTML tidy maybe?) causing what's served to be invalid HTML.

Best regards, Julian

From sant9442@gmail.com  Tue Mar  6 06:06:32 2012
Return-Path: <sant9442@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 273F321F8910 for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 06:06:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.581
X-Spam-Level: 
X-Spam-Status: No, score=-2.581 tagged_above=-999 required=5 tests=[AWL=-0.274, BAYES_00=-2.599, MISSING_HEADERS=1.292, 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 6fMhPTxUYyjE for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 06:06:31 -0800 (PST)
Received: from mail-gy0-f172.google.com (mail-gy0-f172.google.com [209.85.160.172]) by ietfa.amsl.com (Postfix) with ESMTP id EF1EE21F8732 for <ietf@ietf.org>; Tue,  6 Mar 2012 06:06:29 -0800 (PST)
Received: by ghbg16 with SMTP id g16so2475626ghb.31 for <ietf@ietf.org>; Tue, 06 Mar 2012 06:06:29 -0800 (PST)
Received-SPF: pass (google.com: domain of sant9442@gmail.com designates 10.236.184.6 as permitted sender) client-ip=10.236.184.6; 
Authentication-Results: mr.google.com; spf=pass (google.com: domain of sant9442@gmail.com designates 10.236.184.6 as permitted sender) smtp.mail=sant9442@gmail.com; dkim=pass header.i=sant9442@gmail.com
Received: from mr.google.com ([10.236.184.6]) by 10.236.184.6 with SMTP id r6mr34029404yhm.82.1331042789573 (num_hops = 1); Tue, 06 Mar 2012 06:06:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=/u8psLqt5eA9QRYtwK1AED++szBrNO+1shqLkcqMYwU=; b=Iz9Dvt0Zpb5ny0pL5b24hcazKqXUn9IfdNyAuM6ygoRIMueQDpqhiBZMm3/QxpACM6 b9iP2Agejf/HckvXYjVZnvNf6vIlofp2F7gXSdr4zQBd2iQ9w9YIfZqHOtCn1C35UxGy n/d+AB/ndjCzSBHarxbA/xnnwO1jR4w1tjX3tXo8NWzbkkG2Hvq0cYs39eUY9+EyLoXc xLbYJxvTfTt+5CRVPsfvmeaft8Q6ksfvnBdkFF5r/kytr2GPyDJreLdm4NpgXrtDoh9v AkskabzOd1WXXOaQ3YKH2xMrBKojMaz8L292pH/BH7PLpKlGiKm6vNbrfZt/gzDRCZD8 piyA==
Received: by 10.236.184.6 with SMTP id r6mr26876495yhm.82.1331042788425; Tue, 06 Mar 2012 06:06:28 -0800 (PST)
Received: from adsl-215-50-126.mia.bellsouth.net (99-3-147-93.lightspeed.miamfl.sbcglobal.net. [99.3.147.93]) by mx.google.com with ESMTPS id u20sm12042823yhi.10.2012.03.06.06.06.26 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 06 Mar 2012 06:06:26 -0800 (PST)
Message-ID: <4F561A1C.1040406@gmail.com>
Date: Tue, 06 Mar 2012 09:07:24 -0500
From: Hector <sant9442@gmail.com>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
CC: IETF Discussion <ietf@ietf.org>
Subject: Re: Add a link to the HTML version in i-d-announce mails ?
References: <CAErhfrxPe=KSKB7fVHLankkk5XRQ87oarg17kXqNB0o0jGD4hw@mail.gmail.com>
In-Reply-To: <CAErhfrxPe=KSKB7fVHLankkk5XRQ87oarg17kXqNB0o0jGD4hw@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Mar 2012 14:06:32 -0000

+1.  This will save a few typing and clicks.

Xavier Marjou wrote:
> As a subscriber of the i-d-announce@ietf.org list, I generally prefer
> reading the HTML version of the draft rather than the TXT version.
> 
> I thus often need to manually rewrite the TXT link to fetch the HTML
> version of the draft. I can not believe I'm the only one.
> 
> Hence, would it be possible to also include a link like
> http://tools.ietf.org/html/draft-name in the mail of the announced
> draft?
> 
> Cheers,
> Xavier
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
> 
> 

From housley@vigilsec.com  Tue Mar  6 06:13:02 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 918F721F87A7 for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 06:13:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4-rY9gq4zucH for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 06:13:01 -0800 (PST)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id E6BBF21F87A1 for <ietf@ietf.org>; Tue,  6 Mar 2012 06:12:56 -0800 (PST)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id D05859A4728; Tue,  6 Mar 2012 09:12:56 -0500 (EST)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([208.254.26.82]) by localhost (ronin.smetech.net [208.254.26.81]) (amavisd-new, port 10024) with ESMTP id b-vU-yTyF57K; Tue,  6 Mar 2012 09:12:55 -0500 (EST)
Received: from [192.168.2.104] (pool-96-241-165-215.washdc.fios.verizon.net [96.241.165.215]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id EC7A69A4727; Tue,  6 Mar 2012 09:12:55 -0500 (EST)
Subject: Re: Add a link to the HTML version in i-d-announce mails ?
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <CAErhfrxPe=KSKB7fVHLankkk5XRQ87oarg17kXqNB0o0jGD4hw@mail.gmail.com>
Date: Tue, 6 Mar 2012 09:12:54 -0500
Content-Transfer-Encoding: 7bit
Message-Id: <A37C45BE-963E-49AE-9BAE-4A5E2B68D2DB@vigilsec.com>
References: <CAErhfrxPe=KSKB7fVHLankkk5XRQ87oarg17kXqNB0o0jGD4hw@mail.gmail.com>
To: Xavier Marjou <xavier.marjou@gmail.com>
X-Mailer: Apple Mail (2.1084)
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Mar 2012 14:13:02 -0000

I would be much happier with a link to the datatracker HTML version:
https://datatracker.ietf.org/doc/draft-name/

Would this meet your needs?

Russ


On Mar 6, 2012, at 8:41 AM, Xavier Marjou wrote:

> As a subscriber of the i-d-announce@ietf.org list, I generally prefer
> reading the HTML version of the draft rather than the TXT version.
> 
> I thus often need to manually rewrite the TXT link to fetch the HTML
> version of the draft. I can not believe I'm the only one.
> 
> Hence, would it be possible to also include a link like
> http://tools.ietf.org/html/draft-name in the mail of the announced
> draft?
> 
> Cheers,
> Xavier


From randy@psg.com  Tue Mar  6 06:24:18 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 2646521F8918 for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 06:24:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.5
X-Spam-Level: 
X-Spam-Status: No, score=-2.5 tagged_above=-999 required=5 tests=[AWL=0.099, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1DRiZm33PTP4 for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 06:24:17 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id B0C1221F8909 for <ietf@ietf.org>; Tue,  6 Mar 2012 06:24:17 -0800 (PST)
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 1S4vJI-000Jtp-Gj; Tue, 06 Mar 2012 14:24:16 +0000
Date: Tue, 06 Mar 2012 23:24:15 +0900
Message-ID: <m2eht54xkg.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Russ Housley <housley@vigilsec.com>
Subject: Re: Add a link to the HTML version in i-d-announce mails ?
In-Reply-To: <A37C45BE-963E-49AE-9BAE-4A5E2B68D2DB@vigilsec.com>
References: <CAErhfrxPe=KSKB7fVHLankkk5XRQ87oarg17kXqNB0o0jGD4hw@mail.gmail.com> <A37C45BE-963E-49AE-9BAE-4A5E2B68D2DB@vigilsec.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 <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Mar 2012 14:24:18 -0000

> I would be much happier with a link to the datatracker HTML version:
> https://datatracker.ietf.org/doc/draft-name/
> Would this meet your needs?

then we can each have our cake and eat it too.  but i fear folk may just
want the bright shiny.

randy

From dhc@dcrocker.net  Tue Mar  6 06:31:40 2012
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3AD0C21F87D5 for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 06:31:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.607
X-Spam-Level: 
X-Spam-Status: No, score=-6.607 tagged_above=-999 required=5 tests=[AWL=-0.008, 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 hadSyEvtAedI for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 06:31:39 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id BD57921F87CB for <ietf@ietf.org>; Tue,  6 Mar 2012 06:31:39 -0800 (PST)
Received: from [192.168.1.11] (adsl-67-127-58-62.dsl.pltn13.pacbell.net [67.127.58.62]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q26EVW1d000883 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 6 Mar 2012 06:31:37 -0800
Message-ID: <4F561FBA.30003@dcrocker.net>
Date: Tue, 06 Mar 2012 06:31:22 -0800
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: Russ Housley <housley@vigilsec.com>
Subject: Re: Add a link to the HTML version in i-d-announce mails ?
References: <CAErhfrxPe=KSKB7fVHLankkk5XRQ87oarg17kXqNB0o0jGD4hw@mail.gmail.com> <A37C45BE-963E-49AE-9BAE-4A5E2B68D2DB@vigilsec.com>
In-Reply-To: <A37C45BE-963E-49AE-9BAE-4A5E2B68D2DB@vigilsec.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Tue, 06 Mar 2012 06:31:38 -0800 (PST)
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Mar 2012 14:31:40 -0000

On 3/6/2012 6:12 AM, Russ Housley wrote:
> I would be much happier with a link to the datatracker HTML version:
> https://datatracker.ietf.org/doc/draft-name/


+1

d/
-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From marka@isc.org  Tue Mar  6 06:34:50 2012
Return-Path: <marka@isc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7C03721F8523 for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 06:34:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.578
X-Spam-Level: 
X-Spam-Status: No, score=-2.578 tagged_above=-999 required=5 tests=[AWL=0.021,  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 p4Zcg8mAGiqL for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 06:34:50 -0800 (PST)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [IPv6:2001:500:60::65]) by ietfa.amsl.com (Postfix) with ESMTP id D626921F8516 for <ietf@ietf.org>; Tue,  6 Mar 2012 06:34:49 -0800 (PST)
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mail.isc.org", Issuer "RapidSSL CA" (not verified)) by mx.ams1.isc.org (Postfix) with ESMTPS id 677135F9887; Tue,  6 Mar 2012 14:34:29 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (unknown [IPv6:2001:470:1f00:820:6107:6d2:780c:c90b]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by bikeshed.isc.org (Postfix) with ESMTPSA id 89E04216C31; Tue,  6 Mar 2012 14:34:27 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (Postfix) with ESMTP id E3DEC1E1C607; Wed,  7 Mar 2012 01:34:21 +1100 (EST)
To: Tony Finch <dot@dotat.at>
From: Mark Andrews <marka@isc.org>
References: <20120306044628.87718.qmail@joyce.lan> <77075C8C-04ED-48A2-B501-B2296BCFC8C6@frobbit.se> <20120306054213.1C1F91E19F87@drugs.dv.isc.org> <alpine.LSU.2.00.1203061314260.22944@hermes-2.csi.cam.ac.uk>
Subject: Re: provisioning software, was DNS RRTYPEs, the difficulty with
In-reply-to: Your message of "Tue, 06 Mar 2012 13:15:17 -0000." <alpine.LSU.2.00.1203061314260.22944@hermes-2.csi.cam.ac.uk>
Date: Wed, 07 Mar 2012 01:34:21 +1100
Message-Id: <20120306143421.E3DEC1E1C607@drugs.dv.isc.org>
Cc: John Levine <johnl@iecc.com>, Alessandro Vesely <vesely@tana.it>, "ietf@ietf.org Discussion" <ietf@ietf.org>, =?ISO-8859-15?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Mar 2012 14:34:50 -0000

In message <alpine.LSU.2.00.1203061314260.22944@hermes-2.csi.cam.ac.uk>, Tony F
inch writes:
> Mark Andrews <marka@isc.org> wrote:
> >
> > I would say DNS master file representation -> DNS wire representation
> > is one of the main issues on the provisioning side.  This conversion
> > needs to be done at some point.
> 
> John's draft addresses that.
> 
> > The other this is verification of the input.
> 
> What kind of verification?
> 
> Tony.

Most front ends want to make sure what they are feeding to the back
ends wont make it choke.  It also make for a better user experience.

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

From barryleiba@gmail.com  Tue Mar  6 06:35: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 38B3121F887F for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 06:35:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.986
X-Spam-Level: 
X-Spam-Status: No, score=-102.986 tagged_above=-999 required=5 tests=[AWL=-0.009, 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 aJ779-QLVWTB for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 06:35:44 -0800 (PST)
Received: from mail-tul01m020-f172.google.com (mail-tul01m020-f172.google.com [209.85.214.172]) by ietfa.amsl.com (Postfix) with ESMTP id 645C621F8864 for <ietf@ietf.org>; Tue,  6 Mar 2012 06:35:44 -0800 (PST)
Received: by obbta4 with SMTP id ta4so4156919obb.31 for <ietf@ietf.org>; Tue, 06 Mar 2012 06:35:44 -0800 (PST)
Received-SPF: pass (google.com: domain of barryleiba@gmail.com designates 10.182.38.7 as permitted sender) client-ip=10.182.38.7; 
Authentication-Results: mr.google.com; spf=pass (google.com: domain of barryleiba@gmail.com designates 10.182.38.7 as permitted sender) smtp.mail=barryleiba@gmail.com; dkim=pass header.i=barryleiba@gmail.com
Received: from mr.google.com ([10.182.38.7]) by 10.182.38.7 with SMTP id c7mr9756681obk.44.1331044544125 (num_hops = 1); Tue, 06 Mar 2012 06:35:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=24b7tLOo9+x2qRswwYip+teQHDaWK0VXoXBDRxqImVA=; b=sPgu5buUKb6fBfsQjPFYERj1bjMHwv9cENz1i6jv6mwp6fodpqKmW7i2KvtNGjOxeZ 50769JkBZFqgX/c93Y05qCCu+AxUgwAVrjyVnkWWLFS4VNfQ15lPqxe5M3hDFiRHiABw pZAmcDpP5W1H5x1AB4VilmSxnlhCOKiSIo8Wu4m1cQWgefLc/i3276SH+jBkvp9/W95m j/rMKQunv86O6IeBO0hG8qlrGExVfNGKlEvk6jzHEkQMZXUxwkYXc9io6zi+fpYnzwgI dghOT6X8WcCi837laq/ND5soXSE4dHyoih8sp3Om0dwTgUlO6FnzwVbkSby1hU7U+oTF fLTw==
MIME-Version: 1.0
Received: by 10.182.38.7 with SMTP id c7mr8604799obk.44.1331044544077; Tue, 06 Mar 2012 06:35:44 -0800 (PST)
Sender: barryleiba@gmail.com
Received: by 10.60.125.37 with HTTP; Tue, 6 Mar 2012 06:35:43 -0800 (PST)
In-Reply-To: <4F553F2C.3050100@isode.com>
References: <20120301004219.15266.76505.idtracker@ietfa.amsl.com> <CAC4RtVDeXwCLh9R_bNmLwEC5g_4Dv9HadOpXMwbSz5RT2m+jUg@mail.gmail.com> <CAC4RtVB1G_HjYNug0Fvq7LPSnzqG2KxH-PY6nv=nBZKv-uXTLA@mail.gmail.com> <01OCM8WDJZKI00ZUIL@mauve.mrochek.com> <4F54C9B1.4010100@isode.com> <01OCQZ44DUX800ZUIL@mauve.mrochek.com> <4F553F2C.3050100@isode.com>
Date: Tue, 6 Mar 2012 09:35:43 -0500
X-Google-Sender-Auth: vvF_KwMZ96wEL7DPcPNjdxRafOI
Message-ID: <CALaySJ+QdVLBS5yYyKvHrapWd=1p20tsTHYxeSGuvMiHUwjXOA@mail.gmail.com>
Subject: Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities) to Proposed Standard
From: Barry Leiba <barryleiba@computer.org>
To: Alexey Melnikov <alexey.melnikov@isode.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: Pete Resnick <presnick@qualcomm.com>, Ned Freed <ned.freed@mrochek.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Mar 2012 14:35:45 -0000

> Is the following better:
>
> <t>The Importance <xref target=3D"RFC2156"/> header field MUST NOT be use=
d for
> determining
> =A0 =A0 =A0the priority under this "Priority Message Handling" SMTP exten=
sion.
> =A0 =A0 =A0In absence of both the PRIORITY MAIL FROM parameter and the MT=
-Priority
> header field,
> =A0 =A0 =A0other message header fields, such as Priority <xref target=3D"=
RFC2156"/>
> and X-Priority,
> =A0 =A0 =A0MAY be used for determining the priority under this "Priority =
Message
> Handling" SMTP extension.
> </t>

What I don't like about that are:
1. It forbids using Importance, but doesn't say *why*, which could
invite misuse of other similar fields that are floating around.
2. I think MAY is fine for MSAs, but too weak for MTAs.  I accept what
Ned says, that MTAs will do this regardless of what we say.  That can
argue against MUST NOT, but I think SHOULD NOT is appropriate.  I
think the *standard* does want to discourage it, even while accepting
that it will happen.

I'd still like to wait for Ned's version of some text.  While we wait,
let me alter my earlier proposal and re-propose it here:
----------------------------
  Other message header fields, such as "Importance" [RFC2156],
  "Priority" [RFC2156] and "X-Priority", are used inconsistently and
  often with different semantics from MT-Priority.  Fields, such as
  "Importance", that are used to show a sense of importance to the
  end user are particularly ill-suited to convey transport priority, as
  these are distinct aspects of a message. Fields used inconsistently,
  such as "X-Priority", are problematic in this regard: we don't know
  what the intent was when the field was added.

  Therefore:

  1. Message header fields that have a sense of showing importance
  to the end user MUST NOT be used to determine the priority under
  this SMTP extension.

  2. Message Submission Agents [RFC6409] MAY use other header
  fields that have a sense of transport priority in order to assign an
  initial priority in the absence of an SMTP PRIORITY parameter.

  3. Message Transfer Agents handling messages after submission
  SHOULD NOT use any field other than MT-Priority to determine the
  priority under this SMTP extension.
----------------------------

Are we getting close?

Barry

From framefritti@gmail.com  Tue Mar  6 06:36:25 2012
Return-Path: <framefritti@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 36F7021F887C for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 06:36:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QxHwxHZdsHIw for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 06:36:24 -0800 (PST)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id 97C1521F8864 for <ietf@ietf.org>; Tue,  6 Mar 2012 06:36:24 -0800 (PST)
Received: by iazz13 with SMTP id z13so8379422iaz.31 for <ietf@ietf.org>; Tue, 06 Mar 2012 06:36:24 -0800 (PST)
Received-SPF: pass (google.com: domain of framefritti@gmail.com designates 10.42.155.193 as permitted sender) client-ip=10.42.155.193; 
Authentication-Results: mr.google.com; spf=pass (google.com: domain of framefritti@gmail.com designates 10.42.155.193 as permitted sender) smtp.mail=framefritti@gmail.com; dkim=pass header.i=framefritti@gmail.com
Received: from mr.google.com ([10.42.155.193]) by 10.42.155.193 with SMTP id v1mr16510735icw.26.1331044584304 (num_hops = 1); Tue, 06 Mar 2012 06:36:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=kA2AdBHSI2BFMOyvgVNpQ/2J+Rr3Mqg07ybIsdy79qc=; b=GO/cesA2oZc2/yLhf8ed9QGD+zPc3VHJYVdfg8C3rNsZpaOGakyucB7ecnwa13jqzx qQnrXIwzoHm/rAhQZn5faN49K/tQC1tlA+ofL3oXeMVatcU5QqrSHcirzTRa3eviRLJT zKz8bs3Iqmf1j12Qzn/mrze9rI/8uJ/SrifdYMQvxm/n5ictkZUaV6M3GcpuAdyu//Le bZZtGk+A/I/uY7pGSYMdA5KriyhywLT5sA900j+nNOb60KlMkKGdL0C/XxEggwJJCBjp TrBginvgaIuTDX44MaCJWGBm5kqvpyestVQOYmiRyuCjLGkJQyd56pBHKpLwOVZN47BZ gOnw==
MIME-Version: 1.0
Received: by 10.42.155.193 with SMTP id v1mr13630697icw.26.1331044584259; Tue, 06 Mar 2012 06:36:24 -0800 (PST)
Received: by 10.231.185.219 with HTTP; Tue, 6 Mar 2012 06:36:24 -0800 (PST)
In-Reply-To: <m2eht54xkg.wl%randy@psg.com>
References: <CAErhfrxPe=KSKB7fVHLankkk5XRQ87oarg17kXqNB0o0jGD4hw@mail.gmail.com> <A37C45BE-963E-49AE-9BAE-4A5E2B68D2DB@vigilsec.com> <m2eht54xkg.wl%randy@psg.com>
Date: Tue, 6 Mar 2012 15:36:24 +0100
Message-ID: <CABSMSPV0ufE4SiXAbH0VXX6Yc2gm5B4mGyCRJafbpfJ=1Hif1Q@mail.gmail.com>
Subject: Re: Add a link to the HTML version in i-d-announce mails ?
From: Riccardo Bernardini <framefritti@gmail.com>
To: IETF Discussion <ietf@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Mar 2012 14:36:25 -0000

On Tue, Mar 6, 2012 at 3:24 PM, Randy Bush <randy@psg.com> wrote:
>> I would be much happier with a link to the datatracker HTML version:
>> https://datatracker.ietf.org/doc/draft-name/
>> Would this meet your needs?
>

Yes, it would be fine.  From my point of view the two versions are
almost equivalent, this latter maybe is more flexible (at the expense
of one more click, which is negligible)

> then we can each have our cake and eat it too. =A0but i fear folk may jus=
t
> want the bright shiny.
>
> randy
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf

From tony@att.com  Tue Mar  6 06:44:35 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 7B5E021F8969 for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 06:44:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ndxwzx9uboLv for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 06:44:35 -0800 (PST)
Received: from mail119.messagelabs.com (mail119.messagelabs.com [216.82.241.195]) by ietfa.amsl.com (Postfix) with ESMTP id C40EA21F8965 for <ietf@ietf.org>; Tue,  6 Mar 2012 06:44:34 -0800 (PST)
X-Env-Sender: tony@att.com
X-Msg-Ref: server-13.tower-119.messagelabs.com!1331045073!14342123!1
X-Originating-IP: [144.160.20.145]
X-StarScan-Version: 6.5.5; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 11850 invoked from network); 6 Mar 2012 14:44:33 -0000
Received: from sbcsmtp6.sbc.com (HELO mlpd192.enaf.sfdc.sbc.com) (144.160.20.145) by server-13.tower-119.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 6 Mar 2012 14:44:33 -0000
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 q26Ej3U9010641 for <ietf@ietf.org>; Tue, 6 Mar 2012 09:45:04 -0500
Received: from sflint02.pst.cso.att.com (sflint02.pst.cso.att.com [144.154.234.229]) by mlpd192.enaf.sfdc.sbc.com (8.14.5/8.14.5) with ESMTP id q26EiuVi010580 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Tue, 6 Mar 2012 09:44:57 -0500
Received: from alpd052.aldc.att.com (alpd052.aldc.att.com [130.8.42.31]) by sflint02.pst.cso.att.com (RSA Interceptor) for <ietf@ietf.org>; Tue, 6 Mar 2012 09:44:14 -0500
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 q26EiEkT026926 for <ietf@ietf.org>; Tue, 6 Mar 2012 09:44:14 -0500
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 q26Ei8NS026590 for <ietf@ietf.org>; Tue, 6 Mar 2012 09:44:08 -0500
Received: from [130.10.97.126] (vpn-130-10-97-126.vpn.swst.att.com[130.10.97.126]) by maillennium.att.com (mailgw1) with ESMTP id <20120306144138gw1004or2le> (Authid: tony); Tue, 6 Mar 2012 14:41:38 +0000
X-Originating-IP: [130.10.97.126]
Message-ID: <4F5622B7.3090800@att.com>
Date: Tue, 06 Mar 2012 09:44:07 -0500
From: Tony Hansen <tony@att.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: IETF Discussion <ietf@ietf.org>
Subject: Re: Add a link to the HTML version in i-d-announce mails ?
References: <CAErhfrxPe=KSKB7fVHLankkk5XRQ87oarg17kXqNB0o0jGD4hw@mail.gmail.com> <A37C45BE-963E-49AE-9BAE-4A5E2B68D2DB@vigilsec.com>
In-Reply-To: <A37C45BE-963E-49AE-9BAE-4A5E2B68D2DB@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-RSA-Action: allow
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Mar 2012 14:44:35 -0000

It would be acceptable to me, especially since there's a link from there 
to the tools HTML version. (Look for the "html" link at the top.)

     Tony Hansen

On 3/6/2012 9:12 AM, Russ Housley wrote:
> I would be much happier with a link to the datatracker HTML version:
> https://datatracker.ietf.org/doc/draft-name/
>
> Would this meet your needs?
>
> Russ
>
>
> On Mar 6, 2012, at 8:41 AM, Xavier Marjou wrote:
>
>> As a subscriber of the i-d-announce@ietf.org list, I generally prefer
>> reading the HTML version of the draft rather than the TXT version.
>>
>> I thus often need to manually rewrite the TXT link to fetch the HTML
>> version of the draft. I can not believe I'm the only one.
>>
>> Hence, would it be possible to also include a link like
>> http://tools.ietf.org/html/draft-name in the mail of the announced
>> draft?
>>
>> Cheers,
>> Xavier

From johnl@iecc.com  Tue Mar  6 07:00:24 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 86FB021F872B for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 07:00:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.372
X-Spam-Level: 
X-Spam-Status: No, score=-102.372 tagged_above=-999 required=5 tests=[AWL=0.228, 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 kztWabTk4rtI for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 07:00:23 -0800 (PST)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 7112521F86AF for <ietf@ietf.org>; Tue,  6 Mar 2012 07:00:20 -0800 (PST)
Received: (qmail 5111 invoked from network); 6 Mar 2012 15:00:18 -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=13f1.4f562682.k1203; bh=1yKiwXtM3ZHRmzB1eAg+gzlvynfp4FDaWc19fE8pnys=; b=R8zFXEPvXB6e4qETgHY6imrYztwnlaBdHrEdlIoLUosoWVjucmUGXhyEJitvyN72ju6gEQKqHGfWIktXOjIPfogn62xjZksf7jHaCYLCvp+wT2bTLp+yxCgdUSsT7/zOmbA5V4wcMX6ZnVfH9GTroPl9d1BdsCRSC3tSaUph3iE=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Received: (ofmipd 127.0.0.1); 6 Mar 2012 14:59:56 -0000
Date: 6 Mar 2012 10:00:17 -0500
Message-ID: <alpine.BSF.2.00.1203060950080.10148@joyce.lan>
From: "John R. Levine" <johnl@iecc.com>
To: "Ned Freed" <ned.freed@mrochek.com>
Subject: Re: provisioning software, was DNS RRTYPEs, the difficulty with
In-Reply-To: <01OCRTKK8TSO00ZUIL@mauve.mrochek.com>
References: <20120306044628.87718.qmail@joyce.lan> <77075C8C-04ED-48A2-B501-B2296BCFC8C6@frobbit.se> <01OCRTKK8TSO00ZUIL@mauve.mrochek.com>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
Cleverness: None detected
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: "ietf@ietf.org Discussion" <ietf@ietf.org>, =?UTF-8?Q?Patrik_F=C3=A4ltstr=C3=B6m?= <paf@frobbit.se>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Mar 2012 15:00:24 -0000

>> Input -P-> DNS server -D-> DNS stub -Q-> Output
>
>> P is the provisioning
>
> I think you want to break that into the provisioning interface and the data
> format it produces that the DNS server consumes. (My reason for that is we have
> a specification for at least such format, with all that implies.)

I was also going to mention that.  There's a lot of different formats for 
zone file data, with BIND-ish master files being only one of them.

>> We seem to believe that the "D" part is deployed so that adding new "unknown"
>> RRTypes is not an issue.
>
> I think this is correct, but OTOH someone recently asked about possible issues
> in this area, and if I remember correctly, received no response.

Last month I ran into a guy on the dmarc list who complained that 
his server returns NOTIMP in response to queries for SPF records ("because 
it doesn't implement them") and clients were doing odd things.  But it's 
been a long time since I've run into anyone else like that, so I agree, 
it's not an issue.

>> Problem is then in "P" and "Q".
>
> I personally don't see a big problem with "Q", but others clearly do so
> we need to leave it in.

I'm not aware of problems, but I don't use Windows which is where the 
problems are supposed to be.

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

From xavier.marjou@gmail.com  Tue Mar  6 07:11:07 2012
Return-Path: <xavier.marjou@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AE4BB21F87B0 for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 07:11:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zyebTDEg2-Sy for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 07:11:07 -0800 (PST)
Received: from mail-tul01m020-f172.google.com (mail-tul01m020-f172.google.com [209.85.214.172]) by ietfa.amsl.com (Postfix) with ESMTP id 1A04121F878B for <ietf@ietf.org>; Tue,  6 Mar 2012 07:11:07 -0800 (PST)
Received: by obbta4 with SMTP id ta4so4199275obb.31 for <ietf@ietf.org>; Tue, 06 Mar 2012 07:11:06 -0800 (PST)
Received-SPF: pass (google.com: domain of xavier.marjou@gmail.com designates 10.182.183.73 as permitted sender) client-ip=10.182.183.73; 
Authentication-Results: mr.google.com; spf=pass (google.com: domain of xavier.marjou@gmail.com designates 10.182.183.73 as permitted sender) smtp.mail=xavier.marjou@gmail.com; dkim=pass header.i=xavier.marjou@gmail.com
Received: from mr.google.com ([10.182.183.73]) by 10.182.183.73 with SMTP id ek9mr3898507obc.15.1331046666780 (num_hops = 1); Tue, 06 Mar 2012 07:11:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=+JWs4Tk/eWnJZuqGH+Nf5sGilcJ5CVhTA/vuFMK01vg=; b=KmhSpEZIaGnK2vdupwhI1bQhKuOJ7i/jry9FGaYTHHvLW0bo3Z46y04xH0+zdxh6m6 OfEGjcb6dC8XLCXqCc3juNR1ySIPjgZHaeatoRs9Xy/Ti9/VnyTMXNPuIN4jAQfww61t +teFCo47D3mxbKziRSv2IOE5ohrS0D2plNC/uBe9gvpD6oF49MSP391gNPIwXHLVvku1 /3UbaUOXo+pgCD7FsfrL32LnPZBPPiAoUdo4bc5cCGYM/ScxI/ySUnhKWiE9a3np3vMj SZcik9xfhCGkV0nN5286jTnJTQR3z25benULPJ+eBVIe70ONp6qvwlSVLseH5ov8JSGx LG3Q==
MIME-Version: 1.0
Received: by 10.182.183.73 with SMTP id ek9mr3412667obc.15.1331046666689; Tue, 06 Mar 2012 07:11:06 -0800 (PST)
Received: by 10.60.2.70 with HTTP; Tue, 6 Mar 2012 07:11:06 -0800 (PST)
In-Reply-To: <A37C45BE-963E-49AE-9BAE-4A5E2B68D2DB@vigilsec.com>
References: <CAErhfrxPe=KSKB7fVHLankkk5XRQ87oarg17kXqNB0o0jGD4hw@mail.gmail.com> <A37C45BE-963E-49AE-9BAE-4A5E2B68D2DB@vigilsec.com>
Date: Tue, 6 Mar 2012 16:11:06 +0100
Message-ID: <CAErhfrxUQTqBwRL5asJnnoMnBRi0CHAN4RDfAXyBMKwPr7z8OA@mail.gmail.com>
Subject: Re: Add a link to the HTML version in i-d-announce mails ?
From: Xavier Marjou <xavier.marjou@gmail.com>
To: Russ Housley <housley@vigilsec.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Mar 2012 15:11:07 -0000

With a link like https://datatracker.ietf.org/doc/draft-name/ (e.g.
https://datatracker.ietf.org/doc/draft-nir-websec-extended-origin/ ),
I will most often then click again on the html top right link. But I'm
fine with it too.

On Tue, Mar 6, 2012 at 3:12 PM, Russ Housley <housley@vigilsec.com> wrote:
> I would be much happier with a link to the datatracker HTML version:
> https://datatracker.ietf.org/doc/draft-name/
>
> Would this meet your needs?
>
> Russ
>
>
> On Mar 6, 2012, at 8:41 AM, Xavier Marjou wrote:
>
>> As a subscriber of the i-d-announce@ietf.org list, I generally prefer
>> reading the HTML version of the draft rather than the TXT version.
>>
>> I thus often need to manually rewrite the TXT link to fetch the HTML
>> version of the draft. I can not believe I'm the only one.
>>
>> Hence, would it be possible to also include a link like
>> http://tools.ietf.org/html/draft-name in the mail of the announced
>> draft?
>>
>> Cheers,
>> Xavier
>

From ynir@checkpoint.com  Tue Mar  6 07:26:54 2012
Return-Path: <ynir@checkpoint.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 97F7C21F86A8 for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 07:26:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.466
X-Spam-Level: 
X-Spam-Status: No, score=-10.466 tagged_above=-999 required=5 tests=[AWL=0.133, 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 cVWHFhsKzlxK for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 07:26:54 -0800 (PST)
Received: from michael.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id 7AB9921F8690 for <ietf@ietf.org>; Tue,  6 Mar 2012 07:26:53 -0800 (PST)
Received: from il-ex01.ad.checkpoint.com (il-ex01.ad.checkpoint.com [194.29.34.26]) by michael.checkpoint.com (8.13.8/8.13.8) with ESMTP id q26FQo0d008434;  Tue, 6 Mar 2012 17:26:50 +0200
X-CheckPoint: {4F562D0F-0-1B221DC2-5FFFF}
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; Tue, 6 Mar 2012 17:26:49 +0200
Received: from il-ex01.ad.checkpoint.com ([126.0.0.2]) by il-ex03.ad.checkpoint.com ([194.29.34.71]) with mapi; Tue, 6 Mar 2012 17:26:49 +0200
From: Yoav Nir <ynir@checkpoint.com>
To: Xavier Marjou <xavier.marjou@gmail.com>
Date: Tue, 6 Mar 2012 17:26:50 +0200
Subject: Re: Add a link to the HTML version in i-d-announce mails ?
Thread-Topic: Add a link to the HTML version in i-d-announce mails ?
Thread-Index: Acz7rYv7UjZivyrETUi9nlXG0p8uAw==
Message-ID: <1D3193A0-B115-4700-A66B-A4ACD1C5FD64@checkpoint.com>
References: <CAErhfrxPe=KSKB7fVHLankkk5XRQ87oarg17kXqNB0o0jGD4hw@mail.gmail.com> <A37C45BE-963E-49AE-9BAE-4A5E2B68D2DB@vigilsec.com> <CAErhfrxUQTqBwRL5asJnnoMnBRi0CHAN4RDfAXyBMKwPr7z8OA@mail.gmail.com>
In-Reply-To: <CAErhfrxUQTqBwRL5asJnnoMnBRi0CHAN4RDfAXyBMKwPr7z8OA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-KSE-AntiSpam-Interceptor-Info: protection disabled
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Mar 2012 15:26:54 -0000

The XML2RFC version is not linked from there. If that was added to the "Oth=
er versions" field, that would be great.

On Mar 6, 2012, at 5:11 PM, Xavier Marjou wrote:

> With a link like https://datatracker.ietf.org/doc/draft-name/ (e.g.
> https://datatracker.ietf.org/doc/draft-nir-websec-extended-origin/ ),
> I will most often then click again on the html top right link. But I'm
> fine with it too.
>=20
> On Tue, Mar 6, 2012 at 3:12 PM, Russ Housley <housley@vigilsec.com> wrote=
:
>> I would be much happier with a link to the datatracker HTML version:
>> https://datatracker.ietf.org/doc/draft-name/
>>=20
>> Would this meet your needs?
>>=20
>> Russ
>>=20
>>=20
>> On Mar 6, 2012, at 8:41 AM, Xavier Marjou wrote:
>>=20
>>> As a subscriber of the i-d-announce@ietf.org list, I generally prefer
>>> reading the HTML version of the draft rather than the TXT version.
>>>=20
>>> I thus often need to manually rewrite the TXT link to fetch the HTML
>>> version of the draft. I can not believe I'm the only one.
>>>=20
>>> Hence, would it be possible to also include a link like
>>> http://tools.ietf.org/html/draft-name in the mail of the announced
>>> draft?
>>>=20
>>> Cheers,
>>> Xavier
>>=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>=20
> Scanned by Check Point Total Security Gateway.


From ned+ietf@mauve.mrochek.com  Tue Mar  6 07:32:46 2012
Return-Path: <ned+ietf@mauve.mrochek.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DDEC821F8828 for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 07:32:46 -0800 (PST)
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.015,  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 exnOlC7A5Nn0 for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 07:32:46 -0800 (PST)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id F423521F8826 for <ietf@ietf.org>; Tue,  6 Mar 2012 07:32:45 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OCSCXJBSGG0060C6@mauve.mrochek.com> for ietf@ietf.org; Tue, 6 Mar 2012 07:32:43 -0800 (PST)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OCPMUVDUMO00ZUIL@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Tue, 6 Mar 2012 07:32:36 -0800 (PST)
From: ned+ietf@mauve.mrochek.com
Message-id: <01OCSCXFS9D600ZUIL@mauve.mrochek.com>
Date: Tue, 06 Mar 2012 07:30:18 -0800 (PST)
Subject: Re: provisioning software, was DNS RRTYPEs, the difficulty with
In-reply-to: "Your message dated Tue, 06 Mar 2012 10:00:17 -0500" <alpine.BSF.2.00.1203060950080.10148@joyce.lan>
MIME-version: 1.0
Content-type: TEXT/PLAIN; format=flowed
References: <20120306044628.87718.qmail@joyce.lan> <77075C8C-04ED-48A2-B501-B2296BCFC8C6@frobbit.se> <01OCRTKK8TSO00ZUIL@mauve.mrochek.com> <alpine.BSF.2.00.1203060950080.10148@joyce.lan>
To: "John R. Levine" <johnl@iecc.com>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mrochek.com; s=mauve; t=1331047971; i=@mrochek.com; bh=m5W++q5xtQiXkCNjB1w6TpSn7PU7eLp9C1yVolGICXs=;  h=From:Cc:Message-id:Date:Subject:In-reply-to:MIME-version: Content-type:References:To; b=lrKNeoKwIgKE950A/DhHwfeabB0SlusnfsAUpjDmKONtXJ1bv8LaNzbIHJlRZGQ4T Yc6R3JleUFwnHsx2QyHQz4svvMDO39RTzMBuEffc4vp2sCJnOTzCCrVDbApoU7brjJ 8W2UYujgN4UelOqLJDwY9EMbU7ElP3+uUxSM+jv4=
Cc: Ned Freed <ned.freed@mrochek.com>, "ietf@ietf.org Discussion" <ietf@ietf.org>, =?UTF-8?Q?Patrik_F=C3=A4ltstr=C3=B6m?= <paf@frobbit.se>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Mar 2012 15:32:47 -0000

> >> Input -P-> DNS server -D-> DNS stub -Q-> Output
> >
> >> P is the provisioning
> >
> > I think you want to break that into the provisioning interface and the data
> > format it produces that the DNS server consumes. (My reason for that is we have
> > a specification for at least such format, with all that implies.)

> I was also going to mention that.  There's a lot of different formats for
> zone file data, with BIND-ish master files being only one of them.

> >> We seem to believe that the "D" part is deployed so that adding new "unknown"
> >> RRTypes is not an issue.
> >
> > I think this is correct, but OTOH someone recently asked about possible issues
> > in this area, and if I remember correctly, received no response.

> Last month I ran into a guy on the dmarc list who complained that
> his server returns NOTIMP in response to queries for SPF records ("because
> it doesn't implement them") and clients were doing odd things.  But it's
> been a long time since I've run into anyone else like that, so I agree,
> it's not an issue.

> >> Problem is then in "P" and "Q".
> >
> > I personally don't see a big problem with "Q", but others clearly do so
> > we need to leave it in.

> I'm not aware of problems, but I don't use Windows which is where the
> problems are supposed to be.

Exactly - neither do I. (Well, OK, I have a Windows laptop at work to handle
the company HR stuff that won't work in anything other than IE, but I try
really, really hard never to use it.)

				Ned

From warren@kumari.net  Tue Mar  6 08:01:29 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 9F53621F89A9 for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 08:01:29 -0800 (PST)
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 5Pj2X14PzdYi for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 08:01:29 -0800 (PST)
Received: from vimes.kumari.net (vimes.kumari.net [198.186.192.250]) by ietfa.amsl.com (Postfix) with ESMTP id 0440021F89CF for <ietf@ietf.org>; Tue,  6 Mar 2012 08:01:29 -0800 (PST)
Received: from dhcp-172-19-119-93.cbf.corp.google.com (unknown [64.13.52.115]) by vimes.kumari.net (Postfix) with ESMTPSA id 2C3A61B4120E; Tue,  6 Mar 2012 11:01:28 -0500 (EST)
Subject: Re: [IETF] Add a link to the HTML version in i-d-announce mails ?
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Warren Kumari <warren@kumari.net>
In-Reply-To: <CAErhfrxPe=KSKB7fVHLankkk5XRQ87oarg17kXqNB0o0jGD4hw@mail.gmail.com>
Date: Tue, 6 Mar 2012 11:01:26 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <3DEB2E7A-CED3-46CA-8891-43A51E61CA0A@kumari.net>
References: <CAErhfrxPe=KSKB7fVHLankkk5XRQ87oarg17kXqNB0o0jGD4hw@mail.gmail.com>
To: Xavier Marjou <xavier.marjou@gmail.com>
X-Mailer: Apple Mail (2.1084)
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Mar 2012 16:01:29 -0000

On Mar 6, 2012, at 8:41 AM, Xavier Marjou wrote:

> As a subscriber of the i-d-announce@ietf.org list, I generally prefer
> reading the HTML version of the draft rather than the TXT version.
>=20
> I thus often need to manually rewrite the TXT link to fetch the HTML
> version of the draft. I can not believe I'm the only one.

Yup, you are not the only one -- this annoyed me sufficiently that I =
finally gave in and wrote a Chrome extension to do this for me.
Basically it watches the address bard and looks for =
www.ietf.org/id/<foo> and, depending on the setting in the options page, =
will redirect to the Tools or Datatracker.

So, if I follow a link like =
http://www.ietf.org/id/draft-ietf-idr-as0-03.txt the extension will =
notice and rewrite it to =
http://tools.ietf.org/html/draft-ietf-idr-as0-03 (or =
https://datatracker.ietf.org/doc/draft-ietf-idr-as0/ ).

This is my first extension/ javascript, and it's not particularity =
polished, etc but if folk are interested it is on the tools page ( =
http://tools.ietf.org/ ) or, direct: =
https://chrome.google.com/webstore/detail/aiccdpabeagpjcebilebhlifplfkinao=



Share and enjoy.
W

>=20
> Hence, would it be possible to also include a link like
> http://tools.ietf.org/html/draft-name in the mail of the announced
> draft?
>=20
> Cheers,
> Xavier
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>=20


From vesely@tana.it  Tue Mar  6 08:02:05 2012
Return-Path: <vesely@tana.it>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0334121E8017 for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 08:02:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.653
X-Spam-Level: 
X-Spam-Status: No, score=-4.653 tagged_above=-999 required=5 tests=[AWL=0.066,  BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mdY-vZoojE02 for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 08:02:04 -0800 (PST)
Received: from wmail.tana.it (www.tana.it [62.94.243.226]) by ietfa.amsl.com (Postfix) with ESMTP id BFFB921E803E for <ietf@ietf.org>; Tue,  6 Mar 2012 08:02:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=test; t=1331049717; bh=2XrKjTVeApDg2AVGKjAh3r+LRUDdNe2yWlAs/bExJ0k=; l=3412; h=Message-ID:Date:From:MIME-Version:To:References:In-Reply-To: Content-Transfer-Encoding; b=mBqTgsPbR0l3pSr7styLeaDgMcfu4XYHr8sn1uPQYeKCWs9fknuqtBrhQ6tsrls95 xkD166Qf4auYG2h3FZuL4et08DV95Ontkg23BXCszftChq+TL2FnZuhJ8XjCQ8FPEW f5n0BAO75EWcj3Wp2rDz+YIVkJryGO1f1N+PxUKY=
Received: from [172.25.197.158] (pcale.tana [172.25.197.158]) (AUTH: CRAM-MD5 515, TLS: TLS1.0,256bits,RSA_AES_256_CBC_SHA1) by wmail.tana.it with ESMTPSA; Tue, 06 Mar 2012 17:01:57 +0100 id 00000000005DC033.000000004F5634F5.00007143
Message-ID: <4F5634F5.5090909@tana.it>
Date: Tue, 06 Mar 2012 17:01:57 +0100
From: Alessandro Vesely <vesely@tana.it>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: provisioning software, was DNS RRTYPEs, the difficulty with
References: <20120305170938.57919.qmail@joyce.lan> <4F550DA1.8060304@tana.it> <01OCRP6SYT8Q00ZUIL@mauve.mrochek.com>
In-Reply-To: <01OCRP6SYT8Q00ZUIL@mauve.mrochek.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Mar 2012 16:02:05 -0000

On 06/Mar/12 04:56, ned+ietf@mauve.mrochek.com wrote:
>> On 05/Mar/12 18:09, John Levine wrote:
>>
>>> Would you really want to build an SPF or DKIM parser into every
>>> DNS server?  That's a lot of code that the DNS manager doesn't
>>> care about, but the mail manager does.
>> 
>> But it would be the same code, most likely by the same author(s).
> 
> There are some false equivalences floating around here. I don't
> think anyone is suggesting that having provisioning systems or even
> DNS servers themselves check for syntax errors in the contents of
> complex records like DKIM, SPF, DMARC, or whatever is necessarily a
> bad idea. (Whether or not it will actually happen is another
> matter; I'm dubious.)
> 
> Rather, the issue is with requiring it to happen in order to deploy
> a new RRTYPE of this sort, which is the result you get if the DNS
> server returns some series of tokens instead of the original text
> string. That's the sort of thing that forces people to upgrade, or
> search around for a script to do the conversion (which won't even
> occur to some), and that's an extra burden we don't need to
> impose.

It would still be possible to work around the need for a plugin, e.g.
by depending on some wizard web site, as in John's thought experiment.

For the rest of us, the possibility to install a plugin that takes
care of all the nitty-gritty details, instead of having to wait for
the release and distribution of the next version of BIND, can make the
difference between deploying a new RR type right away and
procrastinating endlessly.

>> Why is it important what the DNS manager cares about?
> 
> Speaking as a DNS manager myself, I care a lot about being forced
> to upgrade. Upgrades bring unwanted bugs in other areas.

(I'd be surprised if bugs in any area were wanted ;-)

The issue is to upgrade once rather than on each new RR type.

> In fact I'm not entirely thrilled with the idea of plugins to do
> some extra syntax. More code means more possibilities of bugs. I'd
> actually prefer to see more cross-checking of existing stuff - less
> code and greater benefit.

Depending on how the plugin mechanism is engineered, code insulation,
data encapsulation, and component tests against large samples of data
may help reduce bugs.

To me, an important point is that zone files keep containing data
"source", rather than the output of possibly unreproducible commands.
 Diagnostic-mode execution of the plugin together with a text-based
/etc/rrtypes may even allow to mechanically build GUI dialogs for each
type, whether for the web or for the desktop.

>> Parsers, including null parsers, would come with the same
>> sub-package that enables the new RR type definition.  Their
>> complexity would only matter to the people who read/maintain
>> their sources.
> 
> I'm sorry, but you're being naive about this. Complexity does
> matter to the people who just use software because added complexity
> translates to more bugs.

Correct, but when you publish a complex record you are calling forth
that complexity.  I don't see much difference if the bug is at mines
or at the remote site, since their effects are comparable.

Generating zone files full of hex escapes, so as to do without any
plugin, can --perhaps should-- stay possible.  However, I doubt that
such usage would result in less bugs, on average.

From daedulus@btconnect.com  Tue Mar  6 08:26:10 2012
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5D60321F86E1 for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 08:26:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[AWL=0.100,  BAYES_00=-2.599, J_CHICKENPOX_15=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GQPW1qnj+LRp for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 08:26:09 -0800 (PST)
Received: from mail.btconnect.com (c2bthomr10.btconnect.com [213.123.20.128]) by ietfa.amsl.com (Postfix) with ESMTP id 1FE3B21F86D9 for <ietf@ietf.org>; Tue,  6 Mar 2012 08:26:07 -0800 (PST)
Received: from host86-163-139-217.range86-163.btcentralplus.com (HELO pc6) ([86.163.139.217]) by c2bthomr10.btconnect.com with SMTP id GPT26319; Tue, 06 Mar 2012 16:26:05 +0000 (GMT)
Message-ID: <005701ccfbad$5c6d9060$4001a8c0@gateway.2wire.net>
From: "t.petch" <daedulus@btconnect.com>
To: "Eliot Lear" <lear@cisco.com>
References: <20120222151252.32262.82157.idtracker@ietfa.amsl.com><03a301ccf174$ff953290$febf97b0$@olddog.co.uk><515703B08A3A064C9CC8C09ACCC710DC0631679E@XMB-RCD-103.cisco.com><C71DA9B1-A61F-4C5D-8DCE-3702271CBB6D@vigilsec.com><4F4FA70B.2030906@pi.nu><D0F60388-D852-4815-917A-B14BF40C64FB@vigilsec.com><BD60EA38ED03AF5A21868DF1@PST.JCK.COM> <4F4FC252.9010001@cisco.com> <C3E581FB44D46BF4128A2229@PST.JCK.COM> <029b01ccfb84$4e4e2220$4001a8c0@gateway.2wire.net> <4F55F92F.1020105@cisco.com>
Subject: Re: Last Call:<draft-betts-itu-oam-ach-code-point-03.txt>	(Allocation of anAssociated Channel Code Point for Use by	ITU-T Ethernet basedOAM) to Informational RFC
Date: Tue, 6 Mar 2012 16:25:24 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Mirapoint-IP-Reputation: reputation=Fair-1, source=Queried, refid=tid=0001.0A0B0303.4F563A9C.011B, actions=tag
X-Junkmail-Premium-Raw: score=7/50, refid=2.7.2:2012.3.6.153335:17:7.944, ip=86.163.139.217, rules=__HAS_MSGID, __OUTLOOK_MSGID_1, __SANE_MSGID, __TO_MALFORMED_2, __BOUNCE_CHALLENGE_SUBJ, __BOUNCE_NDR_SUBJ_EXEMPT, __MIME_VERSION, __CT, __CT_TEXT_PLAIN, __CTE, __HAS_X_PRIORITY, __HAS_MSMAIL_PRI, __HAS_X_MAILER, USER_AGENT_OE, __OUTLOOK_MUA_1, __USER_AGENT_MS_GENERIC, __ANY_URI, __URI_NO_WWW, __URI_NO_PATH, BODY_SIZE_3000_3999, __MIME_TEXT_ONLY, RDNS_GENERIC_POOLED, HTML_00_01, HTML_00_10, BODY_SIZE_5000_LESS, RDNS_SUSP_GENERIC, __OUTLOOK_MUA, RDNS_SUSP, BODY_SIZE_7000_LESS
X-Junkmail-Status: score=10/50, host=c2bthomr10.btconnect.com
X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A0B0201.4F563A9D.0081,ss=1,re=0.000,fgs=0, ip=0.0.0.0, so=2011-07-25 19:15:43, dmn=2011-05-27 18:58:46, mode=multiengine
X-Junkmail-IWF: false
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Mar 2012 16:26:10 -0000

----- Original Message -----
From: "Eliot Lear" <lear@cisco.com>
To: "t.petch" <daedulus@btconnect.com>
Cc: "John C Klensin" <john-ietf@jck.com>; <stbryant@cisco.com>; <ietf@ietf.org>
Sent: Tuesday, March 06, 2012 12:46 PM


> Hi,
>
> I speak now as an individual and in no other capacity with no other hats on.
>
>
> On 3/6/12 11:31 AM, t.petch wrote:
> > I am finding myself with some unfamiliar bedfellows on this issue, but yes,
it
> > should be approved - see inline.
> >
> >
> > We claim ownership of the name space on behalf of all parties, all SDOs
> > governments, NGOs, anyone and anything, and this gives us a special
> > responsibility to exercise that wisely.  We should beware of imposing
> > our ideas of correctness of any kind on another SDO - that is up to
> >  them to decide, not us.
>
> Our responsibility is to ourselves first and foremost, and to see that
> our process is followed.  That process exists to, amongst other things,
> insure safe use and interoperable use of our own protocols.

Which, Eliot, is where we part company.  Given the interest in and uptake
of MPLS outside the original definition, we have a wider responsibility,
as we have in, say, managing the IP address or domain name space.  As
with the last two, if we do not consider the needs of all parties, and not just
ourselves, we may lose our influence in these matters.  Yes we must follow our
processes but in the interests of a wider community than just ourselves.

Tom Petch
>
> Here the process for approval of a codepoint calls for IETF review.
> That is this.  IETF Review is defined as follows in RFC-5226:
>
>             IETF Review - (Formerly called "IETF Consensus" in
>             [IANA-CONSIDERATIONS]) New values are assigned only through
>             RFCs that have been shepherded through the IESG as AD-
>             Sponsored or IETF WG Documents [RFC3932] [RFC3978].  The
>             intention is that the document and proposed assignment will
>             be reviewed by the IESG and appropriate IETF WGs (or
>             experts, if suitable working groups no longer exist) to
>             ensure that the proposed assignment will not negatively
>             impact interoperability or otherwise extend IETF protocols
>             in an inappropriate or damaging manner.
>
> In addition, we have spoken on what it means for other SDOs to request
> code points in RFC-4775 Section 3.2, which says, in part:
>
>
>    Experience shows that the importance of this is often underestimated
>    during extension design; designers sometimes assume that a new
>    codepoint is theirs for the asking, or even simply for the taking.
>    This is hazardous; it is far too likely that someone just taking a
>    protocol value will find that the same value will later be formally
>    assigned to another function, thus guaranteeing an interoperability
>    problem.
>
>
> Our processes direct us to consider a codepoint assignment in this
> light.  Finally:
>
>
> >
> > There is no reason not to approve the allocation of a code point
>
> The purpose of this review is to determine whether or not there is
> reason *not* to approve.  Others disagree with you.
>
>
> Eliot
>
>


From R.E.Sonneveld@sonnection.nl  Tue Mar  6 08:34:58 2012
Return-Path: <R.E.Sonneveld@sonnection.nl>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B8BC121F86C8 for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 08:34:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.639
X-Spam-Level: 
X-Spam-Status: No, score=-3.639 tagged_above=-999 required=5 tests=[AWL=-0.040, 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 eWfYn72q-UI5 for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 08:34:57 -0800 (PST)
Received: from mx20.mailtransaction.com (mx20.mailtransaction.com [78.46.16.213]) by ietfa.amsl.com (Postfix) with ESMTP id 81C4821F8817 for <ietf@ietf.org>; Tue,  6 Mar 2012 08:34:56 -0800 (PST)
Received: from process-dkim-sign-daemon.helium.mailtransaction.com by helium.mailtransaction.com (Oracle Communications Messaging Exchange Server 7u4-18.01 64bit (built Jul 15 2010)) id <0M0H00B002230H00@helium.mailtransaction.com>; Tue, 06 Mar 2012 17:34:51 +0100 (CET)
Received: from lion.sonnection.nl (lion.sonnection.nl [80.127.135.138]) by helium.mailtransaction.com (Oracle Communications Messaging Exchange Server 7u4-18.01 64bit (built Jul 15 2010)) with ESMTP id <0M0H003M1222DG00@helium.mailtransaction.com>; Tue, 06 Mar 2012 17:34:51 +0100 (CET)
MIME-version: 1.0
Content-transfer-encoding: 8BIT
Content-type: text/plain; charset=UTF-8; format=flowed
Received: from a80-127-135-139.adsl.xs4all.nl (a80-127-135-139.adsl.xs4all.nl [80.127.135.139]) by lion.sonnection.nl (Sun Java(tm) System Messaging Server 7.3-11.01 32bit (built Sep 1 2009)) with ESMTPA id <0M0H00E5Z2221G00@lion.sonnection.nl> for ietf@ietf.org; Tue, 06 Mar 2012 17:34:50 +0100 (CET)
Message-id: <4F563E2E.4050804@sonnection.nl>
Date: Tue, 06 Mar 2012 17:41:18 +0100
From: "Rolf E. Sonneveld" <R.E.Sonneveld@sonnection.nl>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
To: ned+ietf@mauve.mrochek.com
Subject: Re: Last Call: <draft-melnikov-smtp-priority-07.txt> (Simple Mail Transfer Protocol extension for Message Transfer Priorities)	to	Proposed Standard
References: <CAC4RtVA3F8gsBWY65W5KNDE+408EvtP+hp5GTzLg4FMgC1bdcQ@mail.gmail.com> <20120303041153.23749.qmail@joyce.lan> <01OCOC18E6PI00ZUIL@mauve.mrochek.com>
In-reply-to: <01OCOC18E6PI00ZUIL@mauve.mrochek.com>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=sonnection.nl; s=2009;  t=1331051691; bh=1tg63lbJRrF9yMhh5q3UIeY3u51Ua4uzJdlwG+SBAZc=;  h=MIME-version:Content-transfer-encoding:Content-type:Message-id: Date:From:To:Cc:Subject:References:In-reply-to; b=WQ92e+mwnouUgaLFlverfd0JM9+7ltZfGDye2ZvP3+kVXBKn3jJutVNObUPwUMAwS rioJOwVzglJ6B09MJMKekXtJ49C6GckhYoYRtbqdAotZV37xGThzfrSjWjR5vVyG7v mbqM3UKcJ8UQDMEk1e+GU8Yy80KH3/QqBc8BjFYo=
X-DKIM: OpenDKIM Filter v2.4.3 helium.mailtransaction.com 0M0H00B002230H00
Cc: John Levine <johnl@iecc.com>, 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, 06 Mar 2012 16:34:58 -0000

On 3/3/12 7:07 PM, ned+ietf@mauve.mrochek.com wrote:
>>>> This draft also defines the MT-Priority header field. �It is quite unusual
>>>> for a SMTP extension specification to define a mail header field. ...
>>> This is my major concern about this protocol as well, as I note in the
>>> PROTO writeup (which, unfortunately, can't be seen publicly because of
>>> a limitation in the datatracker; perhaps I should post it here).  I'm
>>> interested in hearing whether others share this concern, and what the
>>> community consensus is about it.
>> I have no problem logging stuff from the SMTP session into a message
>> header, we've been doing that since forever.  But I have a lot of
>> problem turning a header back into SMTP for a subsequent relay, for
>> two reasons.
>> One is just that it's ugly.  There were good reasons to separate the
>> envelope from the body back in the 1970s, and I think those reasons
>> are just as good now.  Over in the EAI group, there was a valiant
>> effort to tunnel EAI messages through non-EAI SMTP servers via
>> downgrades, and we eventually gave up.  Now, if you want to send an
>> EAI message, there has to be an EAI path all the way from the sender
>> to the recipient.  This isn't exactly analogous, but it's instructive.
>> The other reason is that I think it's too ill-specified to
>> interoperate.  The theory seems to be that the relay server notices an
>> MT-Priority: header, and (vigorous waving of hands) somehow decides if
>> the message has sufficient virtue to promote the header back into the
>> SMTP session.  The hand-waving is not persuasive; the suggestion of
>> S/MIME, which obviously won't work, is not encouraging.
> Both good points. While I personally am indifferent to header modification
> being an issue - I believe we've long since crossed that bridge - I will also
> note that simply changing this proposal to always insert the MT-Priority: field
> at submission time and leave it unchanged throughout message transit would
> leave most of the functionality intact and eliminate the header modification
> issue entirely.
>
> But the upleveling of header to envelope would remain. John is quite correct in
> his assertion that these are mostly uncharted waters: The only remotely
> comparable case I can think of is the mapping of some X.400 fields to the
> NOTARY extension, but in that case the mapping was from X.400 envelope material
> to SMTP envelope material. Additionally, the mapping was precisly specified
> with no wiggle room for "site policy".

+1

And there's another issue, I think. As there is 'upleveling of header to 
envelope', the draft also describes the reverse process. In par. 4.4 an 
SMTP client that talks to a non-confirming SMTP server MUST add it's own 
MT-Priority header with a priority determined by the process described 
in par. 4.2. This means an MTA can receive a mail with priority 
determined by envelope information and sends the message using header 
information. Those of us who wrote SMTP client software are in a better 
position to comment on this than I am. But having dealt with different 
MTA's it strikes me as fairly unusual for an SMTP client to add 
headerlines to the message-in-transit at such a late stage during 
transmission of the message to the SMTP server.

/rolf


From fanf2@hermes.cam.ac.uk  Tue Mar  6 09:00:15 2012
Return-Path: <fanf2@hermes.cam.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0859321F86B3 for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 09:00:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.414
X-Spam-Level: 
X-Spam-Status: No, score=-6.414 tagged_above=-999 required=5 tests=[AWL=0.185,  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 HnlRKmHfBz6A for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 09:00:13 -0800 (PST)
Received: from ppsw-50.csi.cam.ac.uk (ppsw-50.csi.cam.ac.uk [131.111.8.150]) by ietfa.amsl.com (Postfix) with ESMTP id 780AC21F8510 for <ietf@ietf.org>; Tue,  6 Mar 2012 09:00:13 -0800 (PST)
X-Cam-AntiVirus: no malware found
X-Cam-SpamDetails: not scanned
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
Received: from hermes-2.csi.cam.ac.uk ([131.111.8.54]:39326) by ppsw-50.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.157]:25) with esmtpa (EXTERNAL:fanf2) id 1S4xk7-0001Vv-rS (Exim 4.72) (return-path <fanf2@hermes.cam.ac.uk>); Tue, 06 Mar 2012 17:00:07 +0000
Received: from fanf2 (helo=localhost) by hermes-2.csi.cam.ac.uk (hermes.cam.ac.uk) with local-esmtp id 1S4xk7-0002EO-He (Exim 4.67) (return-path <fanf2@hermes.cam.ac.uk>); Tue, 06 Mar 2012 17:00:07 +0000
Date: Tue, 6 Mar 2012 17:00:07 +0000
From: Tony Finch <dot@dotat.at>
X-X-Sender: fanf2@hermes-2.csi.cam.ac.uk
To: "John R. Levine" <johnl@iecc.com>
Subject: Re: provisioning software, was DNS RRTYPEs, the difficulty with
In-Reply-To: <alpine.BSF.2.00.1203060950080.10148@joyce.lan>
Message-ID: <alpine.LSU.2.00.1203061658110.2756@hermes-2.csi.cam.ac.uk>
References: <20120306044628.87718.qmail@joyce.lan> <77075C8C-04ED-48A2-B501-B2296BCFC8C6@frobbit.se> <01OCRTKK8TSO00ZUIL@mauve.mrochek.com> <alpine.BSF.2.00.1203060950080.10148@joyce.lan>
User-Agent: Alpine 2.00 (LSU 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: Tony Finch <fanf2@hermes.cam.ac.uk>
Cc: Ned Freed <ned.freed@mrochek.com>, "ietf@ietf.org Discussion" <ietf@ietf.org>, =?ISO-8859-15?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Mar 2012 17:00:15 -0000

John R. Levine <johnl@iecc.com> wrote:
>
> I was also going to mention that.  There's a lot of different formats for zone
> file data, with BIND-ish master files being only one of them.

DNS master files are specified in RFC 1035 so it's wrong to imply they are
implementation-specific.

Tony.
-- 
f.anthony.n.finch  <dot@dotat.at>  http://dotat.at/
Humber, Thames: Variable, becoming southwest, 4, increasing 6 to gale 8.
Slight or moderate, occasionally rough later. Showers, rain later. Good,
occasionally poor later.

From johnl@iecc.com  Tue Mar  6 09:04:10 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 4206D21F866C for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 09:04:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.378
X-Spam-Level: 
X-Spam-Status: No, score=-102.378 tagged_above=-999 required=5 tests=[AWL=0.222, 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 lIXsokQOjqsz for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 09:04:09 -0800 (PST)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 4832821F85F1 for <ietf@ietf.org>; Tue,  6 Mar 2012 09:04:07 -0800 (PST)
Received: (qmail 50430 invoked from network); 6 Mar 2012 17:04:05 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:vbr-info:user-agent:cleverness; s=c4fd.4f564385.k1203; bh=MZqf6jpTiEAxZWXjkvmHXaM+ptTIkAUiaz+OcsbR404=; b=lyaz9GotQpNfIWmIZveK84O1B9ibhJngvzextbpnHYwpenJpaBgoNant6nzuQzaaWnx8uMvc4U8P7wcPuSqGHmBuVAOHa+yczQunnBxMdyT0Kdz11zwFBfTddaLDrI51bYv9Jj+LXIIAyw8c+DvBBpyGKpziNJPwNRfl8ztmv1U=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Received: (ofmipd 127.0.0.1); 6 Mar 2012 17:03:43 -0000
Date: 6 Mar 2012 12:04:05 -0500
Message-ID: <alpine.BSF.2.00.1203061203020.14450@joyce.lan>
From: "John R. Levine" <johnl@iecc.com>
To: "Tony Finch" <dot@dotat.at>
Subject: Re: provisioning software, was DNS RRTYPEs, the difficulty with
In-Reply-To: <alpine.LSU.2.00.1203061658110.2756@hermes-2.csi.cam.ac.uk>
References: <20120306044628.87718.qmail@joyce.lan> <77075C8C-04ED-48A2-B501-B2296BCFC8C6@frobbit.se> <01OCRTKK8TSO00ZUIL@mauve.mrochek.com> <alpine.BSF.2.00.1203060950080.10148@joyce.lan> <alpine.LSU.2.00.1203061658110.2756@hermes-2.csi.cam.ac.uk>
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 Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Mar 2012 17:04:10 -0000

>> I was also going to mention that.  There's a lot of different formats for zone
>> file data, with BIND-ish master files being only one of them.
>
> DNS master files are specified in RFC 1035 so it's wrong to imply they are
> implementation-specific.

They're not implementation specific, but they're also not required to 
interoperate, as the wire format queries and responses are.

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

From dwing@cisco.com  Tue Mar  6 09:25:09 2012
Return-Path: <dwing@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 E793A21F8789; Tue,  6 Mar 2012 09:25:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -108.773
X-Spam-Level: 
X-Spam-Status: No, score=-108.773 tagged_above=-999 required=5 tests=[AWL=1.526, BAYES_00=-2.599, MIME_8BIT_HEADER=0.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 OYiiJiqFh+rO; Tue,  6 Mar 2012 09:25:08 -0800 (PST)
Received: from mtv-iport-4.cisco.com (mtv-iport-4.cisco.com [173.36.130.15]) by ietfa.amsl.com (Postfix) with ESMTP id ADF4D21F8733; Tue,  6 Mar 2012 09:25:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=dwing@cisco.com; l=6709; q=dns/txt; s=iport; t=1331054708; x=1332264308; h=from:to:cc:references:in-reply-to:subject:date: message-id:mime-version:content-transfer-encoding; bh=zhTQr6vzhcvHC2g2qe48Q8IOmBkFcLZAbmiCPSH6tAw=; b=HqLfd4J6R8IuPkdJh6ianwOiWZj+q03ufrFALk7LOt02vKXOD6QZO+Pq X7ZStIt8ozXBZ03ffiGmqPvoTfO6IGSLT6oESZE36daqMdKqqcs0iZj+s RZguN7Hl0iExiZknxlNC1QUjWazteS1sUFsU9qiK4SFwXDgWYf+AWnsUC E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AigFAN1HVk+rRDoI/2dsb2JhbABDpQSPaoEHgX0BAQEDAQgKARdPBQcBAwIJDwIEAQEoBxkjCgkIAgQBEgsXh2AEmkUBnxmQXgSIHzOFCpd5gwQ
X-IronPort-AV: E=Sophos;i="4.73,540,1325462400"; d="scan'208";a="34678553"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by mtv-iport-4.cisco.com with ESMTP; 06 Mar 2012 17:25:08 +0000
Received: from dwingWS ([10.32.240.194]) by mtv-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id q26HP8V9029007; Tue, 6 Mar 2012 17:25:08 GMT
From: "Dan Wing" <dwing@cisco.com>
To: "=?iso-8859-1?Q?'Alberto_Garc=EDa'?=" <alberto@it.uc3m.es>, "'IETF discussion list'" <ietf@ietf.org>
References: <023f01ccf756$e4d4a110$ae7de330$@com> <00ab01ccfbbb$7e7d0380$7b770a80$@it.uc3m.es>
In-Reply-To: <00ab01ccfbbb$7e7d0380$7b770a80$@it.uc3m.es>
Subject: RE: tsv-dir review of draft-garcia-shim6-applicability-03
Date: Tue, 6 Mar 2012 09:25:07 -0800
Message-ID: <07e001ccfbbe$13eaba50$3bc02ef0$@com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AQDWY9DRXMH2S1eCM54jIy0w4V/WFZhKmLgQgAAbKlA=
Content-Language: en-us
Cc: 'marcelo bagnulo braun' <marcelo@it.uc3m.es>, joe.abley@icann.org, tsv-area@ietf.org, 'Transport Directorate' <tsv-dir@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Mar 2012 17:25:10 -0000

> -----Original Message-----
> From: Alberto Garc=EDa [mailto:alberto@it.uc3m.es]
> Sent: Tuesday, March 06, 2012 9:07 AM
> To: 'Dan Wing'; 'IETF discussion list'
> Cc: 'Transport Directorate'; tsv-area@ietf.org; joe.abley@icann.org;
> 'marcelo bagnulo braun'
> Subject: RE: tsv-dir review of draft-garcia-shim6-applicability-03
>=20
> Hi Dan,
> Thank you very much for your review
>=20
> |  -----Mensaje original-----
> |  De: Dan Wing [mailto:dwing@cisco.com]
> |  Enviado el: jueves, 01 de marzo de 2012 3:56
> |  Para: 'IETF discussion list'
> |  CC: 'Transport Directorate'; tsv-area@ietf.org; =
joe.abley@icann.org;
> |  'marcelo bagnulo braun'; alberto@it.uc3m.es
> |  Asunto: tsv-dir review of draft-garcia-shim6-applicability-03
> |
> |  I have reviewed this document as part of the transport area
> directorate's
> |  ongoing effort to review key IETF documents. These comments were
> written
> |  primarily for the transport area directors, but are copied to the
> document's
> |  authors for their information and to allow them to address any
> issues
> |  raised. When done at the time of IETF Last Call, the authors should
> consider
> |  this review together with any other last-call comments they =
receive.
> Please
> |  always CC tsv-dir@ietf.org if you reply to or forward this review.
> |
> |  This draft is basically ready for publication, but has nits that
> should
> be fixed
> |  before publication.
> |
> |
> |
> |  Nits:
> |
> |  Section 1:
> |
> |     Such problems are not specific of Shim6, but
> |     are suffered by the hosts of any site which is connected to
> multiple
> |     transit providers, and which receives an IPv6 prefix from each =
of
> the
> |     providers.
> |
> |  It might be useful to add a non-normative reference to RFC5220 at
> the end
> |  of that sentence.
> Ok
>=20
> |
> |
> |  Section 3.4:
> |
> |     The use of HBA is more efficient in the sense that addresses
> require
> |     less computation than CGA, involving only hash operations for
> both
> |     the generation and the verification of locator sets.  However,
> the
> |     locators of an HBA set are determined during the generation
> process,
> |     and cannot be subsequently changed; the addition of new locators
> to
> |     that initial set is not supported, except by re-generation of =
the
> |     entire set which will in turn cause all addresses to change.
> |
> |  I think that paragraph is too harsh, as it implies the old =
addresses
> have
> to be
> |  invalidated immediately.  I expect existing connections could
> continue
> with
> |  the old addresses, and, if the host wanted to, could even have new
> |  connections use the old addresses.  If that is not possible, the
> draft
> should
> |  explain why.  If that is possible, the draft should probably =
explain
> it
> is
> |  possible.
> |
>=20
> I have rewritten the paragraph:
>=20
>    "The use of HBA is more efficient in the sense that addresses
> require
>    less computation than CGA, involving only hash operations for both
>    the generation and the verification of locator sets.  However, the
>    locators of an HBA set are determined during the generation =
process,
>    and cannot be subsequently changed; the addition of new locators to
>    that initial set is not supported.  Therefore, a node using an HBA
> as
>    ULID for a Shim6 session can only use the locators associated to
> that
>    HBA for the considered Shim6 session.  If the node wants to use a
> new
>    set of locators, it has to generate a new HBA including the =
prefixes
>    of the new locators (which will result with very high probability =
in
>    different addresses to those of the previous set).  New sessions
>    initiated with a ULID belonging to the new HBA address set could =
use
>    the new locators."
>=20
> Do you think it is now more clear?

Yes, thanks.


> |
> |  Section 4:
> |
> |     In order to configure source and destination address selection,
> tools
> |     such as DHCPv6 can be used to disseminate a [RFC3484] policy
> table to
> |     a host.
> |
> |  It might be useful to add a non-normative reference to draft-ietf-
> 6man-
> |  addr-select-opt.
> Sure
>=20
> |
> |
> |  Section 4:
> |
> |  The sentence ending with "properties exhibited by REAP." needs a
> reference
> |  to RFC5544, which seems to be the RFC defining REAP.
> Ok
>=20
> |
> |
> |
> |  Section 7.7, "Shim6 and IPv6 NAT", the problem could be overcome by
> the
> |  Shim6 node knowing its IPv6 address after NPTv6 translation.
> Probably
> not
> |  worth adjusting the document, though, as NPTv6 is experimental.
>=20
> Well, this would not work for HBA, since in this case the addresses =
are
> fixed once generated.

NPTv6 does not change the host portion of the address (it only changes
the network portion -- the IPv6 prefix), so HBA should work with NPTv6.

> It could work for the CGA, since the Shim6 host could sign dynamically
> the
> translated address. But in this case a protocol would be needed to
> convey
> the translated address to the Shim6 node which has to sign it. A =
threat
> analysis of this operation should be performed, in order not to
> introduce
> new vulnerabilities in the process...
> As you suggest, I think this is not worth.

I agree, it can be discussed in a later document, should someone=20
find it useful to have Shim6 work with NPTv6.

> |
> |
> |  Section 7.7:
> |
> |     Note that an Application Level Gateway designed to modify the
> Shim6
> |     control packets would not be able to generate a valid signature,
> in
> |     case a CGA is being used, or a Parameter Data Structure binding
> the
> |     translated locator to the other locators of a node, in case a =
HBA
> is
> |     being used.  Therefore, the same failure cases described before
> would
> |     remain.
> |
> |  Applications are layer 7, Shim6 is layer 3, so an "Application =
Layer
> Gateway"
> |  that modifies Shim6 control packets seems an abuse of terminology.
> |  Suggest:
> |
> |  OLD:
> |     Note that an Application Level Gateway designed to modify the
> Shim6
> |     control packets would not be able to generate a valid signature,
> in
> |  NEW:
> |     Note that modification of the Shim6 control packets by the IPv6
> NAT
> |
> .............^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> |  ^
> |     would not be able to generate a valid signature, in
>=20
> Changed.

Thanks.
-d


> Thanks again,
> Alberto
>=20
> |
> |  -d
> |
> |
> |
> |
> |
> |
> |



From vesely@tana.it  Tue Mar  6 09:35:01 2012
Return-Path: <vesely@tana.it>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 272CF11E8079 for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 09:35:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.653
X-Spam-Level: 
X-Spam-Status: No, score=-4.653 tagged_above=-999 required=5 tests=[AWL=0.066,  BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VaWTE3yVqiqQ for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 09:35:00 -0800 (PST)
Received: from wmail.tana.it (www.tana.it [62.94.243.226]) by ietfa.amsl.com (Postfix) with ESMTP id 3537B11E8074 for <ietf@ietf.org>; Tue,  6 Mar 2012 09:35:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=test; t=1331055299; bh=HHeCz75wnOpVJknf2Y/sTuP9Fpt4eL2Uo/UbGQwB+eI=; l=1232; h=Message-ID:Date:From:MIME-Version:To:References:In-Reply-To: Content-Transfer-Encoding; b=UFItdP/N4Odj8eKeKuviikQowFig3AfhIH1bjLDSn42WsvaQftqW12ao3UctIcJlr q+IuOQvkGw5HQdOqi+x3i2G3BMldEDE+VoINIsPsvIdd2kvlTaNIdwLY1kOVnDVsLS bR1DeGvcpMBCIZrP4GbT+yFzlJu8WEKo5BWyKalg=
Received: from [172.25.197.158] (pcale.tana [172.25.197.158]) (AUTH: CRAM-MD5 515, TLS: TLS1.0,256bits,RSA_AES_256_CBC_SHA1) by wmail.tana.it with ESMTPSA; Tue, 06 Mar 2012 18:34:59 +0100 id 00000000005DC039.000000004F564AC3.00000AFE
Message-ID: <4F564AC2.1040502@tana.it>
Date: Tue, 06 Mar 2012 18:34:58 +0100
From: Alessandro Vesely <vesely@tana.it>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: provisioning software, was DNS RRTYPEs, the difficulty with
References: <20120306044628.87718.qmail@joyce.lan> <77075C8C-04ED-48A2-B501-B2296BCFC8C6@frobbit.se> <01OCRTKK8TSO00ZUIL@mauve.mrochek.com> <alpine.BSF.2.00.1203060950080.10148@joyce.lan>
In-Reply-To: <alpine.BSF.2.00.1203060950080.10148@joyce.lan>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Mar 2012 17:35:01 -0000

On 06/Mar/12 16:00, John R. Levine wrote:
> 
>>> We seem to believe that the "D" part is deployed so that adding new
>>> "unknown" RRTypes is not an issue.
>>
>> I think this is correct, but OTOH someone recently asked about 
>> possible issues in this area, and if I remember correctly,
>> received no response.
> 
> Last month I ran into a guy on the dmarc list who complained that his
> server returns NOTIMP in response to queries for SPF records ("because
> it doesn't implement them") and clients were doing odd things.  But
> it's been a long time since I've run into anyone else like that, so I
> agree, it's not an issue.

Hm... I have no idea how such response gets cached.  RFC 2136 says
that "an appropriate error will be returned to the requestor's caller"
when RCODE is SERVFAIL or NOTIMP.

Is that the same case that Scott noticed when he wrote:

   Particularly when querying for SPF records of type SPF, persistent
   2 ServFail results are /not rare/.

   http://www.ietf.org/mail-archive/web/spfbis/current/msg00259.html
   (emphasis added)
?

IIRC there was also a mirroring issue...

At least, I think these issues will gradually vanish as the software
at the relevant servers gets upgraded.

From scott@kitterman.com  Tue Mar  6 09:40:40 2012
Return-Path: <scott@kitterman.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1188611E8074 for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 09:40:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.586
X-Spam-Level: 
X-Spam-Status: No, score=-2.586 tagged_above=-999 required=5 tests=[AWL=0.013,  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 JvXwAhUGT4m0 for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 09:40:39 -0800 (PST)
Received: from mailout02.controlledmail.com (mailout02.controlledmail.com [72.81.252.18]) by ietfa.amsl.com (Postfix) with ESMTP id 04BF121F84C3 for <ietf@ietf.org>; Tue,  6 Mar 2012 09:40:39 -0800 (PST)
Received: from mailout02.controlledmail.com (localhost [127.0.0.1]) by mailout02.controlledmail.com (Postfix) with ESMTP id 8F61820E4126; Tue,  6 Mar 2012 12:40:38 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=2007-00; t=1331055638; bh=lqXE/MCxYmvqZg8FbaU2H1smeWuwHKX9wpqrrBkLznw=; h=From:To:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version:Content-Transfer-Encoding:Content-Type; b=fRrbPR82vpIiic1miJCX7W0QpFzFoZ1oRPK/Fe8JLOH/5/x2Y1YmFhxCeISTxXVcu dJ37WW7vxZgurWasQDmnmZnRJbpHM0Oup+zaz4/+iCRwXtVwNA9VrHi4rz2pjOa1F8 Lh+2IlVde7HglcjINF7e8K3ZbziK2p8PsjtSXR0g=
Received: from scott-latitude-e6320.localnet (static-72-81-252-21.bltmmd.fios.verizon.net [72.81.252.21]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailout02.controlledmail.com (Postfix) with ESMTPSA id 7629D20E4043;  Tue,  6 Mar 2012 12:40:38 -0500 (EST)
From: Scott Kitterman <scott@kitterman.com>
To: ietf@ietf.org
Subject: Re: provisioning software, was DNS RRTYPEs, the difficulty with
Date: Tue, 06 Mar 2012 12:40:37 -0500
Message-ID: <3917427.WyNNUMIDg1@scott-latitude-e6320>
User-Agent: KMail/4.7.3 (Linux/3.0.0-16-generic-pae; KDE/4.7.4; i686; ; )
In-Reply-To: <4F564AC2.1040502@tana.it>
References: <20120306044628.87718.qmail@joyce.lan> <alpine.BSF.2.00.1203060950080.10148@joyce.lan> <4F564AC2.1040502@tana.it>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
X-AV-Checked: ClamAV using ClamSMTP
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Mar 2012 17:40:40 -0000

On Tuesday, March 06, 2012 06:34:58 PM Alessandro Vesely wrote:
> On 06/Mar/12 16:00, John R. Levine wrote:
> >>> We seem to believe that the "D" part is deployed so that adding new
> >>> "unknown" RRTypes is not an issue.
> >> 
> >> I think this is correct, but OTOH someone recently asked about
> >> possible issues in this area, and if I remember correctly,
> >> received no response.
> > 
> > Last month I ran into a guy on the dmarc list who complained that his
> > server returns NOTIMP in response to queries for SPF records ("because
> > it doesn't implement them") and clients were doing odd things.  But
> > it's been a long time since I've run into anyone else like that, so I
> > agree, it's not an issue.
> 
> Hm... I have no idea how such response gets cached.  RFC 2136 says
> that "an appropriate error will be returned to the requestor's caller"
> when RCODE is SERVFAIL or NOTIMP.
> 
> Is that the same case that Scott noticed when he wrote:
> 
>    Particularly when querying for SPF records of type SPF, persistent
>    2 ServFail results are /not rare/.
> 
>    http://www.ietf.org/mail-archive/web/spfbis/current/msg00259.html
>    (emphasis added)
> ?
> 
> IIRC there was also a mirroring issue...
> 
> At least, I think these issues will gradually vanish as the software
> at the relevant servers gets upgraded.

I don't think it's the same.  It's been awhile since I had data because I 
simply stopped doing any type SPF queries in software I use or support due to 
issues with it (and there's no upside to go expend effort on revisiting the 
issue), but these were definitely SERVFAIL and not NOTIMP, but either would 
have had the same effect of a permanent "temporary error".

Scott K

From barryleiba.mailing.lists@gmail.com  Tue Mar  6 09:44:46 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 E2F1821F8613 for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 09:44:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.985
X-Spam-Level: 
X-Spam-Status: No, score=-102.985 tagged_above=-999 required=5 tests=[AWL=-0.008, 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 4IUAG1mhOUFm for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 09:44:46 -0800 (PST)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id 31EC821F8617 for <ietf@ietf.org>; Tue,  6 Mar 2012 09:44:46 -0800 (PST)
Received: by ggmi1 with SMTP id i1so2687902ggm.31 for <ietf@ietf.org>; Tue, 06 Mar 2012 09:44:45 -0800 (PST)
Received-SPF: pass (google.com: domain of barryleiba.mailing.lists@gmail.com designates 10.236.195.37 as permitted sender) client-ip=10.236.195.37; 
Authentication-Results: mr.google.com; spf=pass (google.com: domain of barryleiba.mailing.lists@gmail.com designates 10.236.195.37 as permitted sender) smtp.mail=barryleiba.mailing.lists@gmail.com; dkim=pass header.i=barryleiba.mailing.lists@gmail.com
Received: from mr.google.com ([10.236.195.37]) by 10.236.195.37 with SMTP id o25mr2678917yhn.55.1331055885828 (num_hops = 1); Tue, 06 Mar 2012 09:44:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=Lebauv9nR97bq9Qnn7OBmTUQArP1PN6oOPw02lTjC6Q=; b=nBrra2AXrgXs3y6NABN9Nz7ZUujjYgcO3v74+W179VgaGM5ulfeaGWFBeStXTyjm1O i9cOH3fGO1vS12bQGBYdPOxCKq0pHshALrReR1EDQAViF8Gs8TtjCDtT0GcxMEKaMTxe C4vnXJa11Ph7nGv55L7SYLXfXaAPgqDM+xY8yevCWU5FuiUJwrego35ew4jUtJQNnKeG l6/SBgRCaIshQlI8YHw2OHIHEK+LNi+apPogsSqaL724xaCD2zsd2kb/xLDE/fw/SNq5 5ep/f+/SJyV6hCP56KsWfhkvkuoGTWyT8PHpGXyaMJCoV2K8hIH29Uiy3vj1AhGPOKy1 i1aw==
MIME-Version: 1.0
Received: by 10.236.195.37 with SMTP id o25mr2231609yhn.55.1331055885710; Tue, 06 Mar 2012 09:44:45 -0800 (PST)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.147.106.16 with HTTP; Tue, 6 Mar 2012 09:44:45 -0800 (PST)
In-Reply-To: <CABSMSPV0ufE4SiXAbH0VXX6Yc2gm5B4mGyCRJafbpfJ=1Hif1Q@mail.gmail.com>
References: <CAErhfrxPe=KSKB7fVHLankkk5XRQ87oarg17kXqNB0o0jGD4hw@mail.gmail.com> <A37C45BE-963E-49AE-9BAE-4A5E2B68D2DB@vigilsec.com> <m2eht54xkg.wl%randy@psg.com> <CABSMSPV0ufE4SiXAbH0VXX6Yc2gm5B4mGyCRJafbpfJ=1Hif1Q@mail.gmail.com>
Date: Tue, 6 Mar 2012 12:44:45 -0500
X-Google-Sender-Auth: 0XjCzzfs3X8Riv-4kkbsl4Q_zuk
Message-ID: <CAC4RtVAvQR5Enwy98vMGM6g7NvU7_RWPqbjsrfMG_oaYUADr5A@mail.gmail.com>
Subject: Re: Add a link to the HTML version in i-d-announce mails ?
From: Barry Leiba <barryleiba@computer.org>
To: Riccardo Bernardini <framefritti@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Mar 2012 17:44:47 -0000

> almost equivalent, this latter maybe is more flexible (at the expense
> of one more click, which is negligible)

Re: one more click...

https://datatracker.ietf.org/cookies/

Note the third item.

Barry

From stpeter@stpeter.im  Tue Mar  6 09:49:05 2012
Return-Path: <stpeter@stpeter.im>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C9C3021F8664 for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 09:49:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.769
X-Spam-Level: 
X-Spam-Status: No, score=-102.769 tagged_above=-999 required=5 tests=[AWL=-0.170, 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 ij8JoHfmQ4fo for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 09:49:05 -0800 (PST)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 834F321F8665 for <ietf@ietf.org>; Tue,  6 Mar 2012 09:49:04 -0800 (PST)
Received: from dhcp-64-101-72-162.cisco.com (unknown [64.101.72.162]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 0AAB140058 for <ietf@ietf.org>; Tue,  6 Mar 2012 11:01:00 -0700 (MST)
Message-ID: <4F564E0F.5080505@stpeter.im>
Date: Tue, 06 Mar 2012 10:49:03 -0700
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.5; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Last Call: <draft-snell-atompub-tombstones-15.txt> (The Atom "deleted-entry" Element) to Proposed Standard
References: <20120306174519.29706.83558.idtracker@ietfa.amsl.com>
In-Reply-To: <20120306174519.29706.83558.idtracker@ietfa.amsl.com>
X-Enigmail-Version: 1.3.5
OpenPGP: url=https://stpeter.im/stpeter.asc
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Mar 2012 17:49:05 -0000

Folks, we've issued a second Last Call on this document because based on
IESG feedback the intended status has changed from Informational to
Proposed Standard.

On 3/6/12 10:45 AM, The IESG wrote:
> 
> The IESG has received a request from an individual submitter to consider
> the following document:
> - 'The Atom "deleted-entry" Element'
>   <draft-snell-atompub-tombstones-15.txt> as a 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-04-03. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
> 
> Abstract
> 
> 
>    This specification adds mechanisms to the Atom Syndication Format
>    which publishers of Atom Feed and Entry documents can use to
>    explicitly identify Atom entries that have been removed.
> 
> 
> 
> 
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-snell-atompub-tombstones/
> 
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-snell-atompub-tombstones/ballot/
> 
> 
> No IPR declarations have been submitted directly on this I-D.
> 
> 
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-announce

From barryleiba.mailing.lists@gmail.com  Tue Mar  6 10:29:33 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 E1EAF21E80C2; Tue,  6 Mar 2012 10:29:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.985
X-Spam-Level: 
X-Spam-Status: No, score=-102.985 tagged_above=-999 required=5 tests=[AWL=-0.008, 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 yWg8j6emP7pT; Tue,  6 Mar 2012 10:29:31 -0800 (PST)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id B359C21F84D7; Tue,  6 Mar 2012 10:27:48 -0800 (PST)
Received: by yhpp34 with SMTP id p34so2721790yhp.31 for <multiple recipients>; Tue, 06 Mar 2012 10:27:43 -0800 (PST)
Received-SPF: pass (google.com: domain of barryleiba.mailing.lists@gmail.com designates 10.236.181.193 as permitted sender) client-ip=10.236.181.193; 
Authentication-Results: mr.google.com; spf=pass (google.com: domain of barryleiba.mailing.lists@gmail.com designates 10.236.181.193 as permitted sender) smtp.mail=barryleiba.mailing.lists@gmail.com; dkim=pass header.i=barryleiba.mailing.lists@gmail.com
Received: from mr.google.com ([10.236.181.193]) by 10.236.181.193 with SMTP id l41mr35287336yhm.38.1331058463766 (num_hops = 1); Tue, 06 Mar 2012 10:27:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=yYliFU04J8Lyo8J9VSbnH+WTMXj6WBQti+OmN8enzf4=; b=0JjyMtaNlGVZrXkz1/2PB8seYmPmOYwYYlG3oovWrpD2xPqzEFIH0OrquXN0HIZxvL RTJZijUY5wAXKdn6BL4B8z0JXrsc4uFjOucZ4OwziVtdo0C7/+miDd7NZeIA/h91SAvA Y0nvR1ut80OGQ/cKKyddyvU01PD42LiYLh8vUiD5Kr7vEIPpoANjDGPD/Lgu3Wu4A21h 5J3CSMWATt7xyYvUGAq9hfgdCNCxZZgzFiI2SHxwT0rgsLIDdYjMFIGulxZRLcIKAyNf 4YJOo+gEZkraYNmgJsn8sU1mdqs6yTy6vNCtcaieMOMKoNLP0KcZ3dVbsKyhOX4KenSF J+oQ==
MIME-Version: 1.0
Received: by 10.236.181.193 with SMTP id l41mr27988510yhm.38.1331058463710; Tue, 06 Mar 2012 10:27:43 -0800 (PST)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.147.106.16 with HTTP; Tue, 6 Mar 2012 10:27:43 -0800 (PST)
In-Reply-To: <20120306181626.6061.683.idtracker@ietfa.amsl.com>
References: <20120306181626.6061.683.idtracker@ietfa.amsl.com>
Date: Tue, 6 Mar 2012 13:27:43 -0500
X-Google-Sender-Auth: kLzJxw0PfZ24z3_BXVmJ3ZhtYAc
Message-ID: <CAC4RtVCvB9WANvd-s_oxz0WRJvwPRT3zp+0To6OpcHw2Qdu8qg@mail.gmail.com>
Subject: Re: WG Review: INtermediary-safe SIP session ID (insipid)
From: Barry Leiba <barryleiba@computer.org>
To: IESG <iesg@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Mar 2012 18:29:34 -0000

> A new IETF working group has been proposed in the Real-Time Applications
> and Infrastructure Area.
...
> INtermediary-safe SIP session ID (insipid)

I think the working group is a good idea, and I think the charter is
fine.  Charter away.

Just a very, very small point:
There's some value in being able to search for these things in Google
(or Bing, or whatever), and we've had (minor) problems in the past
when working groups have had very cutesy names that have amusement
value, but don't do well in web searches.  "lemonade" comes to mind,
and there are others.

Let me encourage you to choose something other than "insipid".

That said, let me encourage you not to waste very much time on this point.

Barry

> ------------------------------------------
> Status: Proposed Working Group
> Last Updated: 2012-03-01
>
> Chairs:
> =A0TBD
>
> Real-Time Applications and Infrastructure Area Directors:
> =A0Gonzalo Camarillo <gonzalo.camarillo@ericsson.com>
> =A0Robert Sparks <rjsparks@nostrum.com>
>
> Real-Time Applications and Infrastructure Area Advisor:
> =A0Gonzalo Camarillo <gonzalo.camarillo@ericsson.com>
>
> Mailing Lists:
> =A0General Discussion: TBD
> =A0To Subscribe: =A0TBD
> =A0Archive: =A0 =A0 =A0 TBD
>
> An end-to-end session identifier in SIP-based multimedia
> communication networks refers to the ability for endpoints,
> intermediate devices, and management and monitoring system to
> identify and correlate SIP messages and dialogs of the same
> higher-level end-to-end "communication session" across multiple
> SIP devices, hops, and administrative domains. =A0Unfortunately,
> there are a number of factors that contribute to the fact that
> the current dialog identifiers defined in SIP are not suitable
> for end-to-end session identification. Perhaps the most important
> factor worth describing is that in real-world deployments of
> Back-to-Back User Agents (B2BUAs) devices like Session Border
> Controllers (SBC) often change the call identifiers (e.g., the
> From-tag and To-tag that are used in conjunction with the Call-ID
> header to make the dialog-id) as the session signaling passes
> through.
>
> An end-to-end session identifier should allow the possibility to
> identify the communication session from the point of origin,
> passing through any number of intermediaries, to the ultimate
> point of termination. It should have the same aim as the
> From-tag, To-tag and Call-ID conjunction, but should not be
> mangled by intermediaries.
>
> A SIP end-to-end session identifier has been considered as possible
> solution of different use cases like troubleshooting, billing, session
> tracking, session recording, media and signaling correlation, and so
> forth. =A0Some of these requirements come from other working groups
> within the RAI area (e.g., SIPRec). Moreover, other standards
> organizations have identified the need for SIP and H.323 to carry the
> same "session ID" value so that it is possible to identify a call
> end-to end even when performing inter working between protocols.
>
> This group will focus on a document that will specify an SIP
> identifier that have the same aim as the From-tag, To-tag and Call-ID
> conjunction, but is less likely to be mangled by intermediaries. In
> doing this work, the group will pay attention to the privacy
> implications of a "session ID", for example considering the
> possibility to make it intractable for nodes to correlate "session IDs"
> generated by the same user for different sessions.
>
> Goal and Milestone:
>
> Dec 2012 - Specification of the new identifier sent to the IESG (PS)
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-announce

From msk@cloudmark.com  Tue Mar  6 10:33:10 2012
Return-Path: <msk@cloudmark.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 27B1021E8087 for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 10:33:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.604
X-Spam-Level: 
X-Spam-Status: No, score=-102.604 tagged_above=-999 required=5 tests=[AWL=-0.005, 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 SRKUa4pMQjie for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 10:33:09 -0800 (PST)
Received: from ht2-outbound.cloudmark.com (ht2-outbound.cloudmark.com [72.5.239.26]) by ietfa.amsl.com (Postfix) with ESMTP id 02C5421E800C for <ietf@ietf.org>; Tue,  6 Mar 2012 10:33:03 -0800 (PST)
Received: from EXCH-MBX901.corp.cloudmark.com ([fe80::addf:849a:f71c:4a82]) by exch-htcas902.corp.cloudmark.com ([fe80::e82a:4f80:7f44:eaf7%12]) with mapi id 14.01.0355.002; Tue, 6 Mar 2012 10:33:02 -0800
From: "Murray S. Kucherawy" <msk@cloudmark.com>
To: IETF Discussion <ietf@ietf.org>
Subject: RE: Add a link to the HTML version in i-d-announce mails ?
Thread-Topic: Add a link to the HTML version in i-d-announce mails ?
Thread-Index: AQHM+57dZDLAMUWo6E+naoIftHKruJZdl8kQ
Date: Tue, 6 Mar 2012 18:33:01 +0000
Message-ID: <9452079D1A51524AA5749AD23E00392807CC0D@exch-mbx901.corp.cloudmark.com>
References: <CAErhfrxPe=KSKB7fVHLankkk5XRQ87oarg17kXqNB0o0jGD4hw@mail.gmail.com>
In-Reply-To: <CAErhfrxPe=KSKB7fVHLankkk5XRQ87oarg17kXqNB0o0jGD4hw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.20.2.121]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Mar 2012 18:33:10 -0000

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of X=
avier Marjou
> Sent: Tuesday, March 06, 2012 5:42 AM
> To: IETF Discussion
> Subject: Add a link to the HTML version in i-d-announce mails ?
>=20
> As a subscriber of the i-d-announce@ietf.org list, I generally prefer
> reading the HTML version of the draft rather than the TXT version.
>=20
> I thus often need to manually rewrite the TXT link to fetch the HTML
> version of the draft. I can not believe I'm the only one.
>=20
> Hence, would it be possible to also include a link like
> http://tools.ietf.org/html/draft-name in the mail of the announced
> draft?

...or a link to the datatracker page, which in turn has links to all availa=
ble formats?

-MSK

From msk@cloudmark.com  Tue Mar  6 10:34:03 2012
Return-Path: <msk@cloudmark.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 72D6D21E808F for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 10:34:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.604
X-Spam-Level: 
X-Spam-Status: No, score=-102.604 tagged_above=-999 required=5 tests=[AWL=-0.005, 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 iTgV5eZWzMqf for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 10:34:03 -0800 (PST)
Received: from ht1-outbound.cloudmark.com (ht1-outbound.cloudmark.com [72.5.239.25]) by ietfa.amsl.com (Postfix) with ESMTP id 9A77B21E800C for <ietf@ietf.org>; Tue,  6 Mar 2012 10:33:55 -0800 (PST)
Received: from EXCH-MBX901.corp.cloudmark.com ([fe80::addf:849a:f71c:4a82]) by EXCH-HTCAS901.corp.cloudmark.com ([fe80::2966:6846:8d89:4681%12]) with mapi id 14.01.0355.002; Tue, 6 Mar 2012 10:33:55 -0800
From: "Murray S. Kucherawy" <msk@cloudmark.com>
To: IETF Discussion <ietf@ietf.org>
Subject: RE: Add a link to the HTML version in i-d-announce mails ?
Thread-Topic: Add a link to the HTML version in i-d-announce mails ?
Thread-Index: AQHM+57dZDLAMUWo6E+naoIftHKruJZd1VAA///Cr6A=
Date: Tue, 6 Mar 2012 18:33:54 +0000
Message-ID: <9452079D1A51524AA5749AD23E00392807CC2D@exch-mbx901.corp.cloudmark.com>
References: <CAErhfrxPe=KSKB7fVHLankkk5XRQ87oarg17kXqNB0o0jGD4hw@mail.gmail.com> <A37C45BE-963E-49AE-9BAE-4A5E2B68D2DB@vigilsec.com>
In-Reply-To: <A37C45BE-963E-49AE-9BAE-4A5E2B68D2DB@vigilsec.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.20.2.121]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Mar 2012 18:34:03 -0000

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of R=
uss Housley
> Sent: Tuesday, March 06, 2012 6:13 AM
> To: Xavier Marjou
> Cc: IETF Discussion
> Subject: Re: Add a link to the HTML version in i-d-announce mails ?
>=20
> I would be much happier with a link to the datatracker HTML version:
> https://datatracker.ietf.org/doc/draft-name/
>=20
> Would this meet your needs?

Serves me right for not reading the thread before replying.

+ULONG_MAX, so there.

-MSK

From alberto@it.uc3m.es  Tue Mar  6 09:06:41 2012
Return-Path: <alberto@it.uc3m.es>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E7C8D21F8714; Tue,  6 Mar 2012 09:06:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.069
X-Spam-Level: 
X-Spam-Status: No, score=-6.069 tagged_above=-999 required=5 tests=[AWL=0.230,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id E4L30BgFCd3R; Tue,  6 Mar 2012 09:06:40 -0800 (PST)
Received: from smtp02.uc3m.es (smtp02.uc3m.es [163.117.176.132]) by ietfa.amsl.com (Postfix) with ESMTP id 7DDD221F8751; Tue,  6 Mar 2012 09:06:39 -0800 (PST)
X-uc3m-safe: yes
Received: from BOMBO (unknown [163.117.139.62]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp02.uc3m.es (Postfix) with ESMTP id 3CA137581EE; Tue,  6 Mar 2012 18:06:38 +0100 (CET)
From: =?iso-8859-1?Q?Alberto_Garc=EDa?= <alberto@it.uc3m.es>
To: "'Dan Wing'" <dwing@cisco.com>, "'IETF discussion list'" <ietf@ietf.org>
References: <023f01ccf756$e4d4a110$ae7de330$@com>
In-Reply-To: <023f01ccf756$e4d4a110$ae7de330$@com>
Subject: RE: tsv-dir review of draft-garcia-shim6-applicability-03
Date: Tue, 6 Mar 2012 18:06:38 +0100
Message-ID: <00ab01ccfbbb$7e7d0380$7b770a80$@it.uc3m.es>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQDWY9DRXMH2S1eCM54jIy0w4V/WFZhKmLgQ
Content-Language: es
X-TM-AS-Product-Ver: IMSS-7.0.0.3116-6.8.0.1017-18758.000
X-Mailman-Approved-At: Tue, 06 Mar 2012 12:02:13 -0800
Cc: 'marcelo bagnulo braun' <marcelo@it.uc3m.es>, joe.abley@icann.org, tsv-area@ietf.org, 'Transport Directorate' <tsv-dir@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Mar 2012 17:06:41 -0000

Hi Dan,
Thank you very much for your review

|  -----Mensaje original-----
|  De: Dan Wing [mailto:dwing@cisco.com]
|  Enviado el: jueves, 01 de marzo de 2012 3:56
|  Para: 'IETF discussion list'
|  CC: 'Transport Directorate'; tsv-area@ietf.org; joe.abley@icann.org;
|  'marcelo bagnulo braun'; alberto@it.uc3m.es
|  Asunto: tsv-dir review of draft-garcia-shim6-applicability-03
|  
|  I have reviewed this document as part of the transport area directorate's
|  ongoing effort to review key IETF documents. These comments were written
|  primarily for the transport area directors, but are copied to the
document's
|  authors for their information and to allow them to address any issues
|  raised. When done at the time of IETF Last Call, the authors should
consider
|  this review together with any other last-call comments they receive.
Please
|  always CC tsv-dir@ietf.org if you reply to or forward this review.
|  
|  This draft is basically ready for publication, but has nits that should
be fixed
|  before publication.
|  
|  
|  
|  Nits:
|  
|  Section 1:
|  
|     Such problems are not specific of Shim6, but
|     are suffered by the hosts of any site which is connected to multiple
|     transit providers, and which receives an IPv6 prefix from each of the
|     providers.
|  
|  It might be useful to add a non-normative reference to RFC5220 at the end
|  of that sentence.
Ok

|  
|  
|  Section 3.4:
|  
|     The use of HBA is more efficient in the sense that addresses require
|     less computation than CGA, involving only hash operations for both
|     the generation and the verification of locator sets.  However, the
|     locators of an HBA set are determined during the generation process,
|     and cannot be subsequently changed; the addition of new locators to
|     that initial set is not supported, except by re-generation of the
|     entire set which will in turn cause all addresses to change.
|  
|  I think that paragraph is too harsh, as it implies the old addresses have
to be
|  invalidated immediately.  I expect existing connections could continue
with
|  the old addresses, and, if the host wanted to, could even have new
|  connections use the old addresses.  If that is not possible, the draft
should
|  explain why.  If that is possible, the draft should probably explain it
is
|  possible.
|  

I have rewritten the paragraph:

   "The use of HBA is more efficient in the sense that addresses require
   less computation than CGA, involving only hash operations for both
   the generation and the verification of locator sets.  However, the
   locators of an HBA set are determined during the generation process,
   and cannot be subsequently changed; the addition of new locators to
   that initial set is not supported.  Therefore, a node using an HBA as
   ULID for a Shim6 session can only use the locators associated to that
   HBA for the considered Shim6 session.  If the node wants to use a new
   set of locators, it has to generate a new HBA including the prefixes
   of the new locators (which will result with very high probability in
   different addresses to those of the previous set).  New sessions
   initiated with a ULID belonging to the new HBA address set could use
   the new locators."

Do you think it is now more clear?

|  
|  Section 4:
|  
|     In order to configure source and destination address selection, tools
|     such as DHCPv6 can be used to disseminate a [RFC3484] policy table to
|     a host.
|  
|  It might be useful to add a non-normative reference to draft-ietf-6man-
|  addr-select-opt.
Sure

|  
|  
|  Section 4:
|  
|  The sentence ending with "properties exhibited by REAP." needs a
reference
|  to RFC5544, which seems to be the RFC defining REAP.
Ok

|  
|  
|  
|  Section 7.7, "Shim6 and IPv6 NAT", the problem could be overcome by the
|  Shim6 node knowing its IPv6 address after NPTv6 translation.  Probably
not
|  worth adjusting the document, though, as NPTv6 is experimental.

Well, this would not work for HBA, since in this case the addresses are
fixed once generated. 
It could work for the CGA, since the Shim6 host could sign dynamically the
translated address. But in this case a protocol would be needed to convey
the translated address to the Shim6 node which has to sign it. A threat
analysis of this operation should be performed, in order not to introduce
new vulnerabilities in the process... 
As you suggest, I think this is not worth.

|  
|  
|  Section 7.7:
|  
|     Note that an Application Level Gateway designed to modify the Shim6
|     control packets would not be able to generate a valid signature, in
|     case a CGA is being used, or a Parameter Data Structure binding the
|     translated locator to the other locators of a node, in case a HBA is
|     being used.  Therefore, the same failure cases described before would
|     remain.
|  
|  Applications are layer 7, Shim6 is layer 3, so an "Application Layer
Gateway"
|  that modifies Shim6 control packets seems an abuse of terminology.
|  Suggest:
|  
|  OLD:
|     Note that an Application Level Gateway designed to modify the Shim6
|     control packets would not be able to generate a valid signature, in
|  NEW:
|     Note that modification of the Shim6 control packets by the IPv6 NAT
|  .............^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|  ^
|     would not be able to generate a valid signature, in

Changed.

Thanks again,
Alberto

|  
|  -d
|  
|  
|  
|  
|  
|  
|  



From julian.reschke@gmx.de  Tue Mar  6 13:44:33 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 A62FC21E8032 for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 13:44:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.453
X-Spam-Level: 
X-Spam-Status: No, score=-104.453 tagged_above=-999 required=5 tests=[AWL=-1.854, 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 hCuKXF1Y4C8H for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 13:44:33 -0800 (PST)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by ietfa.amsl.com (Postfix) with SMTP id CA85E21E8013 for <ietf@ietf.org>; Tue,  6 Mar 2012 13:44:32 -0800 (PST)
Received: (qmail invoked by alias); 06 Mar 2012 21:44:31 -0000
Received: from mail.greenbytes.de (EHLO [192.168.1.140]) [217.91.35.233] by mail.gmx.net (mp034) with SMTP; 06 Mar 2012 22:44:31 +0100
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1/NeKkiaqHN2Hu03OVMsoxkm25D+yvxWzKmpvyNOQ sTcXRLgnfF8YgG
Message-ID: <4F56853D.6000301@gmx.de>
Date: Tue, 06 Mar 2012 22:44:29 +0100
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: Yoav Nir <ynir@checkpoint.com>
Subject: Re: Add a link to the HTML version in i-d-announce mails ?
References: <CAErhfrxPe=KSKB7fVHLankkk5XRQ87oarg17kXqNB0o0jGD4hw@mail.gmail.com> <A37C45BE-963E-49AE-9BAE-4A5E2B68D2DB@vigilsec.com> <CAErhfrxUQTqBwRL5asJnnoMnBRi0CHAN4RDfAXyBMKwPr7z8OA@mail.gmail.com> <1D3193A0-B115-4700-A66B-A4ACD1C5FD64@checkpoint.com>
In-Reply-To: <1D3193A0-B115-4700-A66B-A4ACD1C5FD64@checkpoint.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Mar 2012 21:44:33 -0000

On 2012-03-06 16:26, Yoav Nir wrote:
> The XML2RFC version is not linked from there. If that was added to the "Other versions" field, that would be great.
 > ...

Indeed. HTMLized plain text is progress over plain text, but properly 
generated HTML is better.

But I fear we're getting close to our beloved permathread.

Best regards, Julian

From ynir@checkpoint.com  Tue Mar  6 14:02:12 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 3B95521E80BF for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 14:02:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.468
X-Spam-Level: 
X-Spam-Status: No, score=-10.468 tagged_above=-999 required=5 tests=[AWL=0.131, 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 83WMB7WQyfxY for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 14:02:11 -0800 (PST)
Received: from michael.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id 29B8021E80DF for <ietf@ietf.org>; Tue,  6 Mar 2012 14:02:10 -0800 (PST)
Received: from il-ex01.ad.checkpoint.com (il-ex01.ad.checkpoint.com [194.29.34.26]) by michael.checkpoint.com (8.13.8/8.13.8) with ESMTP id q26M25VW030649;  Wed, 7 Mar 2012 00:02:06 +0200
X-CheckPoint: {4F5689AF-2-1B221DC2-5FFFF}
Received: from il-ex01.ad.checkpoint.com ([126.0.0.2]) by il-ex01.ad.checkpoint.com ([126.0.0.2]) with mapi; Wed, 7 Mar 2012 00:02:05 +0200
From: Yoav Nir <ynir@checkpoint.com>
To: Julian Reschke <julian.reschke@gmx.de>
Date: Wed, 7 Mar 2012 00:02:03 +0200
Subject: Re: Add a link to the HTML version in i-d-announce mails ?
Thread-Topic: Add a link to the HTML version in i-d-announce mails ?
Thread-Index: Acz75MPx4fuNSDmtTtCkzVQQ4kWwNg==
Message-ID: <D080D5A9-0C8D-4108-8BAD-26D778FE7C8E@checkpoint.com>
References: <CAErhfrxPe=KSKB7fVHLankkk5XRQ87oarg17kXqNB0o0jGD4hw@mail.gmail.com> <A37C45BE-963E-49AE-9BAE-4A5E2B68D2DB@vigilsec.com> <CAErhfrxUQTqBwRL5asJnnoMnBRi0CHAN4RDfAXyBMKwPr7z8OA@mail.gmail.com> <1D3193A0-B115-4700-A66B-A4ACD1C5FD64@checkpoint.com> <4F56853D.6000301@gmx.de>
In-Reply-To: <4F56853D.6000301@gmx.de>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Mar 2012 22:02:12 -0000

On Mar 6, 2012, at 11:44 PM, Julian Reschke wrote:

> On 2012-03-06 16:26, Yoav Nir wrote:
>> The XML2RFC version is not linked from there. If that was added to the "=
Other versions" field, that would be great.
>> ...
>=20
> Indeed. HTMLized plain text is progress over plain text, but properly=20
> generated HTML is better.
>=20
> But I fear we're getting close to our beloved permathread.

Pictures in RFCs?=

From marka@isc.org  Tue Mar  6 14:09:35 2012
Return-Path: <marka@isc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2842421E80CA for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 14:09:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.58
X-Spam-Level: 
X-Spam-Status: No, score=-2.58 tagged_above=-999 required=5 tests=[AWL=0.019,  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 Ip73lKHIQ8gN for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 14:09:33 -0800 (PST)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [IPv6:2001:500:60::65]) by ietfa.amsl.com (Postfix) with ESMTP id B98BF21E8032 for <ietf@ietf.org>; Tue,  6 Mar 2012 14:09:33 -0800 (PST)
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mail.isc.org", Issuer "RapidSSL CA" (not verified)) by mx.ams1.isc.org (Postfix) with ESMTPS id EC4225F9865; Tue,  6 Mar 2012 22:09:17 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (unknown [IPv6:2001:470:1f00:820:17d:90bc:5fc8:434]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by bikeshed.isc.org (Postfix) with ESMTPSA id 8B52F216C33; Tue,  6 Mar 2012 22:09:15 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (Postfix) with ESMTP id 8B52C1E1DE9F; Wed,  7 Mar 2012 09:09:11 +1100 (EST)
To: "John R. Levine" <johnl@iecc.com>
From: Mark Andrews <marka@isc.org>
References: <20120306044628.87718.qmail@joyce.lan> <77075C8C-04ED-48A2-B501-B2296BCFC8C6@frobbit.se> <01OCRTKK8TSO00ZUIL@mauve.mrochek.com> <alpine.BSF.2.00.1203060950080.10148@joyce.lan> <alpine.LSU.2.00.1203061658110.2756@hermes-2.csi.cam.ac.uk> <alpine.BSF.2.00.1203061203020.14450@joyce.lan>
Subject: Re: provisioning software, was DNS RRTYPEs, the difficulty with
In-reply-to: Your message of "06 Mar 2012 12:04:05 CDT." <alpine.BSF.2.00.1203061203020.14450@joyce.lan>
Date: Wed, 07 Mar 2012 09:09:11 +1100
Message-Id: <20120306220911.8B52C1E1DE9F@drugs.dv.isc.org>
Cc: "ietf@ietf.org Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Mar 2012 22:09:35 -0000

In message <alpine.BSF.2.00.1203061203020.14450@joyce.lan>, "John R. Levine" wr
ites:
> >> I was also going to mention that.  There's a lot of different formats for 
> zone
> >> file data, with BIND-ish master files being only one of them.
> >
> > DNS master files are specified in RFC 1035 so it's wrong to imply they are
> > implementation-specific.
> 
> They're not implementation specific, but they're also not required to 
> interoperate, as the wire format queries and responses are.

They are a interchange standard as per RFC 1034.

The standard format of master files allows them to be exchanged between
hosts (via FTP, mail, or some other mechanism); this facility is useful
when an organization wants a domain, but doesn't want to support a name
server.  The organization can maintain the master files locally using a
text editor, transfer them to a foreign host which runs a name server,
and then arrange with the system administrator of the name server to get
the files loaded.


> Regards,
> John Levine, johnl@iecc.com, Primary Perpetrator of "The Internet for Dummies
> ",
> Please consider the environment before reading this e-mail. http://jl.ly
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org

From housley@vigilsec.com  Tue Mar  6 14:15:42 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 360E721E8013 for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 14:15:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.549
X-Spam-Level: 
X-Spam-Status: No, score=-102.549 tagged_above=-999 required=5 tests=[AWL=0.050, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id T+iMCDNw3i9f for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 14:15:41 -0800 (PST)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id 8879211E8072 for <ietf@ietf.org>; Tue,  6 Mar 2012 14:15:41 -0800 (PST)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id CBF5D9A4725; Tue,  6 Mar 2012 17:15:41 -0500 (EST)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([208.254.26.82]) by localhost (ronin.smetech.net [208.254.26.81]) (amavisd-new, port 10024) with ESMTP id 3OmRpRhHznRe; Tue,  6 Mar 2012 17:15:38 -0500 (EST)
Received: from [192.168.2.104] (pool-96-241-165-215.washdc.fios.verizon.net [96.241.165.215]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 383A29A4724; Tue,  6 Mar 2012 17:15:41 -0500 (EST)
Subject: Re: Add a link to the HTML version in i-d-announce mails ?
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <D080D5A9-0C8D-4108-8BAD-26D778FE7C8E@checkpoint.com>
Date: Tue, 6 Mar 2012 17:15:39 -0500
Content-Transfer-Encoding: 7bit
Message-Id: <7CEA9124-7B72-4906-B5B4-E0C32E319433@vigilsec.com>
References: <CAErhfrxPe=KSKB7fVHLankkk5XRQ87oarg17kXqNB0o0jGD4hw@mail.gmail.com> <A37C45BE-963E-49AE-9BAE-4A5E2B68D2DB@vigilsec.com> <CAErhfrxUQTqBwRL5asJnnoMnBRi0CHAN4RDfAXyBMKwPr7z8OA@mail.gmail.com> <1D3193A0-B115-4700-A66B-A4ACD1C5FD64@checkpoint.com> <4F56853D.6000301@gmx.de> <D080D5A9-0C8D-4108-8BAD-26D778FE7C8E@checkpoint.com>
To: Yoav Nir <ynir@checkpoint.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: Tue, 06 Mar 2012 22:15:42 -0000

> Pictures in RFCs?

Come to the RFCFORM BOF to voice opinions on this topic.

Russ

From johnl@iecc.com  Tue Mar  6 14:15:51 2012
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 496F521E80DF for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 14:15:51 -0800 (PST)
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.217, 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 rrtA6OxA9C4w for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 14:15:50 -0800 (PST)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 24BE421E80CA for <ietf@ietf.org>; Tue,  6 Mar 2012 14:15:49 -0800 (PST)
Received: (qmail 39878 invoked from network); 6 Mar 2012 22:15:47 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:vbr-info:user-agent:cleverness; s=9bc5.4f568c93.k1203; bh=9utzghJJWfsyUszdkZCCV2PVnH0eBgF9+pjtGUqIjr0=; b=mpNocE3jKqG+peQxhhsYYyKNyqMLLwt4qD6E+16/25LJzgoLAbYoRMN/KvbVXGwigN7RwJO/CN5m9mj2roiAYp33ZHI8mH74AVY11IWPLybtNTqRzkpk1BhthzJH1qWekasLNchdcXQJbN2I93rhVvu2E6Toa2rLJnBaSu/VvY4=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Received: (ofmipd 127.0.0.1); 6 Mar 2012 22:15:25 -0000
Date: 6 Mar 2012 17:15:46 -0500
Message-ID: <alpine.BSF.2.00.1203061711470.25059@joyce.lan>
From: "John R. Levine" <johnl@iecc.com>
To: "Mark Andrews" <marka@isc.org>
Subject: Re: provisioning software, was DNS RRTYPEs, the difficulty with
In-Reply-To: <20120306220911.8B52C1E1DE9F@drugs.dv.isc.org>
References: <20120306044628.87718.qmail@joyce.lan> <77075C8C-04ED-48A2-B501-B2296BCFC8C6@frobbit.se> <01OCRTKK8TSO00ZUIL@mauve.mrochek.com> <alpine.BSF.2.00.1203060950080.10148@joyce.lan> <alpine.LSU.2.00.1203061658110.2756@hermes-2.csi.cam.ac.uk> <alpine.BSF.2.00.1203061203020.14450@joyce.lan> <20120306220911.8B52C1E1DE9F@drugs.dv.isc.org>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
Cleverness: None detected
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
Cc: "ietf@ietf.org Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Mar 2012 22:15:51 -0000

>> They're not implementation specific, but they're also not required to
>> interoperate, as the wire format queries and responses are.
>
> They are a interchange standard as per RFC 1034.

Yes, we all know that.  But as I presume you also know, there are plenty 
of DNS servers that store the zone info in other ways, ranging from djbdns 
mutant syntax text files to various databases.

Whatever the server uses, the provisioning system better match.

> The standard format of master files allows them to be exchanged between
> hosts (via FTP, mail, or some other mechanism); this facility is useful
> when an organization wants a domain, but doesn't want to support a name
> server.  The organization can maintain the master files locally using a
> text editor, transfer them to a foreign host which runs a name server,
> and then arrange with the system administrator of the name server to get
> the files loaded.

That is one implementation.  But it's far from the only one.

My system has a web front end that lets my users edit groups of their 
djbdns RRs, which it stores in a database.  Once an hour, a perl script 
goes through the database, regenerates the mutant text files, and stuffs 
them into the name servers.  It's not fabulous, but it gets the job done.

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

From stpeter@stpeter.im  Tue Mar  6 14:19:43 2012
Return-Path: <stpeter@stpeter.im>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 99DAE21E80A9 for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 14:19:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.784
X-Spam-Level: 
X-Spam-Status: No, score=-102.784 tagged_above=-999 required=5 tests=[AWL=-0.185, 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 rKaK6BKdt2Ce for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 14:19:42 -0800 (PST)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id D738D21E8013 for <ietf@ietf.org>; Tue,  6 Mar 2012 14:19:42 -0800 (PST)
Received: from squire.local (unknown [64.101.72.114]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id B846B40058; Tue,  6 Mar 2012 15:31:39 -0700 (MST)
Message-ID: <4F568D7D.8070502@stpeter.im>
Date: Tue, 06 Mar 2012 15:19:41 -0700
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.5; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: Scott Kitterman <scott@kitterman.com>
Subject: Re: Last Call: <draft-ietf-appsawg-xdash-03.txt> (Deprecating Use of the "X-" Prefix in Application Protocols) to Best Current Practice
References: <20120301184750.21152.93044.idtracker@ietfa.amsl.com> <2328831.zKV7qZlmPL@scott-latitude-e6320> <4F4FFB75.5080303@stpeter.im> <61623076-6684-46d9-94bc-eefb2b1de6b9@email.android.com>
In-Reply-To: <61623076-6684-46d9-94bc-eefb2b1de6b9@email.android.com>
X-Enigmail-Version: 1.3.5
OpenPGP: url=https://stpeter.im/stpeter.asc
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Mar 2012 22:19:43 -0000

On 3/1/12 5:14 PM, Scott Kitterman wrote:
> 
> 
> Peter Saint-Andre <stpeter@stpeter.im> wrote:
> 
>> On 3/1/12 12:00 PM, Scott Kitterman wrote:
>>> On Thursday, March 01, 2012 10:47:50 AM The IESG wrote:
>>>> The IESG has received a request from the Applications Area Working
>> Group
>>>> WG (appsawg) to consider the following document:
>>>> - 'Deprecating Use of the "X-" Prefix in Application Protocols'
>>>>   <draft-ietf-appsawg-xdash-03.txt> as a 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-03-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
>>>>
>>>>
>>>>    Historically, designers and implementers of application protocols
>>>>    have often distinguished between "standard" and "non-standard"
>>>>    parameters by prefixing the latter with the string "X-" or
>> similar
>>>>    constructions.  In practice, this convention causes more problems
>>>>    than it solves.  Therefore, this document deprecates the "X-"
>>>>    convention for textual parameters in application protocols.
>>> ...
>>>
>>> 2.  Recommendations for Implementers of Application Protocols
>>>
>>>    Implementers of application protocols MUST NOT treat the general
>>>    categories of "standard" and "non-standard" parameters in
>>>    programatically different ways within their applications.
>>>
>>> Shouldn't this restrict itself to the naming of parameters?  Perhaps:
>>>
>>> 2.  Recommendations for Implementers of Application Protocols
>>>
>>>    Implementers of application protocols MUST NOT treat the general
>>>    naming of parameters in programmatically different ways within
>>>    their applications depending on if they are "standard" or
>> "non-standard".
>>
>> How about this?
>>
>>   Implementations of application protocols MUST NOT programatically
>>   discriminate between "standard" and "non-standard" parameters based
>>   solely on the names of such parameters.
> 
> I'm not quite sure.
> 
> Is this supposed to be about how one selects names or how one uses them. I'd thought it meant the former, but your revised text sounds like the latter to me.

The concept behind this text was always about how one uses names, or
more precisely how code implementations treat them, because the authors
are of the opinion that it's a bad idea for implementations to hardcode
their handling of parameter based solely on the existence of the string
'x-' at the start of the parameter name. I think the revised text I
provided captures this more clearly.

Peter

-- 
Peter Saint-Andre
https://stpeter.im/



From marka@isc.org  Tue Mar  6 14:19:49 2012
Return-Path: <marka@isc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5C77021E80A9 for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 14:19:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.582
X-Spam-Level: 
X-Spam-Status: No, score=-2.582 tagged_above=-999 required=5 tests=[AWL=0.017,  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 awO9XPC8SRVY for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 14:19:48 -0800 (PST)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) by ietfa.amsl.com (Postfix) with ESMTP id 79BCC21F864F for <ietf@ietf.org>; Tue,  6 Mar 2012 14:19:48 -0800 (PST)
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mail.isc.org", Issuer "RapidSSL CA" (not verified)) by mx.pao1.isc.org (Postfix) with ESMTPS id 49A42C9422; Tue,  6 Mar 2012 22:19:36 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (unknown [IPv6:2001:470:1f00:820:17d:90bc:5fc8:434]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by bikeshed.isc.org (Postfix) with ESMTPSA id 11C93216C31; Tue,  6 Mar 2012 22:19:36 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (Postfix) with ESMTP id E60E41E1DF40; Wed,  7 Mar 2012 09:19:31 +1100 (EST)
To: Alessandro Vesely <vesely@tana.it>
From: Mark Andrews <marka@isc.org>
References: <20120306044628.87718.qmail@joyce.lan> <77075C8C-04ED-48A2-B501-B2296BCFC8C6@frobbit.se> <01OCRTKK8TSO00ZUIL@mauve.mrochek.com> <alpine.BSF.2.00.1203060950080.10148@joyce.lan> <4F564AC2.1040502@tana.it>
Subject: Re: provisioning software, was DNS RRTYPEs, the difficulty with
In-reply-to: Your message of "Tue, 06 Mar 2012 18:34:58 BST." <4F564AC2.1040502@tana.it>
Date: Wed, 07 Mar 2012 09:19:31 +1100
Message-Id: <20120306221931.E60E41E1DF40@drugs.dv.isc.org>
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Mar 2012 22:19:49 -0000

In message <4F564AC2.1040502@tana.it>, Alessandro Vesely writes:
> On 06/Mar/12 16:00, John R. Levine wrote:
> > 
> >>> We seem to believe that the "D" part is deployed so that adding new
> >>> "unknown" RRTypes is not an issue.
> >>
> >> I think this is correct, but OTOH someone recently asked about 
> >> possible issues in this area, and if I remember correctly,
> >> received no response.
> > 
> > Last month I ran into a guy on the dmarc list who complained that his
> > server returns NOTIMP in response to queries for SPF records ("because
> > it doesn't implement them") and clients were doing odd things.  But
> > it's been a long time since I've run into anyone else like that, so I
> > agree, it's not an issue.
> 
> Hm... I have no idea how such response gets cached.  RFC 2136 says
> that "an appropriate error will be returned to the requestor's caller"
> when RCODE is SERVFAIL or NOTIMP.
> 
> Is that the same case that Scott noticed when he wrote:
> 
>    Particularly when querying for SPF records of type SPF, persistent
>    2 ServFail results are /not rare/.
> 
>    http://www.ietf.org/mail-archive/web/spfbis/current/msg00259.html
>    (emphasis added)
> ?
> 
> IIRC there was also a mirroring issue...
> 
> At least, I think these issues will gradually vanish as the software
> at the relevant servers gets upgraded.

A RFC 1035 recursive server should be able to handle SPF.  It's
just a opaque data blob to it with a name, type, class and ttl
attributes.  To serve SPF a RFC 1035 needed to be upgraded as it had
no way to store / load the record.

DNS software developers should read Section 3.6. "Defining new types,
classes, and special namespaces", especially the sentence:

		New definitions should be expected.

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

From scott@kitterman.com  Tue Mar  6 14:24:42 2012
Return-Path: <scott@kitterman.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9B9B721E80CA for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 14:24:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.587
X-Spam-Level: 
X-Spam-Status: No, score=-2.587 tagged_above=-999 required=5 tests=[AWL=0.012,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 21ArlmK7DXA8 for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 14:24:41 -0800 (PST)
Received: from mailout02.controlledmail.com (mailout02.controlledmail.com [72.81.252.18]) by ietfa.amsl.com (Postfix) with ESMTP id ADED021E8013 for <ietf@ietf.org>; Tue,  6 Mar 2012 14:24:41 -0800 (PST)
Received: from mailout02.controlledmail.com (localhost [127.0.0.1]) by mailout02.controlledmail.com (Postfix) with ESMTP id 3255920E40C0; Tue,  6 Mar 2012 17:24:41 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=2007-00; t=1331072681; bh=YYGrMjY35P1pQMEKcM1kdqlmQJTKWQPION/Vr2DNeXk=; h=From:To:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version:Content-Transfer-Encoding:Content-Type; b=FQ9nuwzmrMbQo3tyZ9cqrzz6lNO1rJDgebXdZyKk052ouvW74SJjetYJJcEOgHmvw MvXHancNEWzV4FUPgXPXRp3qLqUiLhplEFf9te132fU0Fllc0CPt4PbSsZmNXH+iOG 52LVpPCi3uQXhd4IfvR/3TX2PTgDyY0Xs1/TcXTM=
Received: from scott-latitude-e6320.localnet (static-72-81-252-21.bltmmd.fios.verizon.net [72.81.252.21]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailout02.controlledmail.com (Postfix) with ESMTPSA id 13C4320E4099;  Tue,  6 Mar 2012 17:24:40 -0500 (EST)
From: Scott Kitterman <scott@kitterman.com>
To: ietf@ietf.org
Subject: Re: Last Call: <draft-ietf-appsawg-xdash-03.txt> (Deprecating Use of the "X-" Prefix in Application Protocols) to Best Current Practice
Date: Tue, 06 Mar 2012 17:24:40 -0500
Message-ID: <1633774.E10J87jy7A@scott-latitude-e6320>
User-Agent: KMail/4.7.3 (Linux/3.0.0-16-generic-pae; KDE/4.7.4; i686; ; )
In-Reply-To: <4F568D7D.8070502@stpeter.im>
References: <20120301184750.21152.93044.idtracker@ietfa.amsl.com> <61623076-6684-46d9-94bc-eefb2b1de6b9@email.android.com> <4F568D7D.8070502@stpeter.im>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
X-AV-Checked: ClamAV using ClamSMTP
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Mar 2012 22:24:42 -0000

On Tuesday, March 06, 2012 03:19:41 PM Peter Saint-Andre wrote:
> On 3/1/12 5:14 PM, Scott Kitterman wrote:
> > Peter Saint-Andre <stpeter@stpeter.im> wrote:
> >> On 3/1/12 12:00 PM, Scott Kitterman wrote:
> >>> On Thursday, March 01, 2012 10:47:50 AM The IESG wrote:
> >>>> The IESG has received a request from the Applications Area Working
> >> 
> >> Group
> >> 
> >>>> WG (appsawg) to consider the following document:
> >>>> - 'Deprecating Use of the "X-" Prefix in Application Protocols'
> >>>> 
> >>>>   <draft-ietf-appsawg-xdash-03.txt> as a 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-03-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
> >>>> 
> >>>>    Historically, designers and implementers of application
> >>>>    protocols
> >>>>    have often distinguished between "standard" and
> >>>>    "non-standard"
> >>>>    parameters by prefixing the latter with the string "X-" or
> >> 
> >> similar
> >> 
> >>>>    constructions.  In practice, this convention causes more
> >>>>    problems
> >>>>    than it solves.  Therefore, this document deprecates the
> >>>>    "X-"
> >>>>    convention for textual parameters in application protocols.
> >>> 
> >>> ...
> >>> 
> >>> 2.  Recommendations for Implementers of Application Protocols
> >>> 
> >>>    Implementers of application protocols MUST NOT treat the
> >>>    general
> >>>    categories of "standard" and "non-standard" parameters in
> >>>    programatically different ways within their applications.
> >>> 
> >>> Shouldn't this restrict itself to the naming of parameters? 
> >>> Perhaps:
> >>> 
> >>> 2.  Recommendations for Implementers of Application Protocols
> >>> 
> >>>    Implementers of application protocols MUST NOT treat the
> >>>    general
> >>>    naming of parameters in programmatically different ways within
> >>>    their applications depending on if they are "standard" or
> >> 
> >> "non-standard".
> >> 
> >> How about this?
> >> 
> >>   Implementations of application protocols MUST NOT programatically
> >>   discriminate between "standard" and "non-standard" parameters
> >>   based
> >>   solely on the names of such parameters.
> > 
> > I'm not quite sure.
> > 
> > Is this supposed to be about how one selects names or how one uses them.
> > I'd thought it meant the former, but your revised text sounds like the
> > latter to me.
> The concept behind this text was always about how one uses names, or
> more precisely how code implementations treat them, because the authors
> are of the opinion that it's a bad idea for implementations to hardcode
> their handling of parameter based solely on the existence of the string
> 'x-' at the start of the parameter name. I think the revised text I
> provided captures this more clearly.

Yes.  Thanks for clarifying.

Scott K

From stpeter@stpeter.im  Tue Mar  6 14:30:46 2012
Return-Path: <stpeter@stpeter.im>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9968B21E80EF for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 14:30:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.783
X-Spam-Level: 
X-Spam-Status: No, score=-102.783 tagged_above=-999 required=5 tests=[AWL=-0.184, 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 P7L7Qu1XIKOB for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 14:30:45 -0800 (PST)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 95AAD21E8034 for <ietf@ietf.org>; Tue,  6 Mar 2012 14:30:45 -0800 (PST)
Received: from squire.local (unknown [64.101.72.114]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 931FA40058; Tue,  6 Mar 2012 15:42:42 -0700 (MST)
Message-ID: <4F569014.1030208@stpeter.im>
Date: Tue, 06 Mar 2012 15:30:44 -0700
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.5; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: Scott Kitterman <scott@kitterman.com>
Subject: Re: Last Call: <draft-ietf-appsawg-xdash-03.txt> (Deprecating Use of the "X-" Prefix in Application Protocols) to Best Current Practice
References: <20120301184750.21152.93044.idtracker@ietfa.amsl.com> <61623076-6684-46d9-94bc-eefb2b1de6b9@email.android.com> <4F568D7D.8070502@stpeter.im> <1633774.E10J87jy7A@scott-latitude-e6320>
In-Reply-To: <1633774.E10J87jy7A@scott-latitude-e6320>
X-Enigmail-Version: 1.3.5
OpenPGP: url=https://stpeter.im/stpeter.asc
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Mar 2012 22:30:46 -0000

On 3/6/12 3:24 PM, Scott Kitterman wrote:
> On Tuesday, March 06, 2012 03:19:41 PM Peter Saint-Andre wrote:
>> On 3/1/12 5:14 PM, Scott Kitterman wrote:
>>> Peter Saint-Andre <stpeter@stpeter.im> wrote:
>>>> On 3/1/12 12:00 PM, Scott Kitterman wrote:
>>>>> On Thursday, March 01, 2012 10:47:50 AM The IESG wrote:
>>>>>> The IESG has received a request from the Applications Area Working
>>>>
>>>> Group
>>>>
>>>>>> WG (appsawg) to consider the following document:
>>>>>> - 'Deprecating Use of the "X-" Prefix in Application Protocols'
>>>>>>
>>>>>>   <draft-ietf-appsawg-xdash-03.txt> as a 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-03-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
>>>>>>
>>>>>>    Historically, designers and implementers of application
>>>>>>    protocols
>>>>>>    have often distinguished between "standard" and
>>>>>>    "non-standard"
>>>>>>    parameters by prefixing the latter with the string "X-" or
>>>>
>>>> similar
>>>>
>>>>>>    constructions.  In practice, this convention causes more
>>>>>>    problems
>>>>>>    than it solves.  Therefore, this document deprecates the
>>>>>>    "X-"
>>>>>>    convention for textual parameters in application protocols.
>>>>>
>>>>> ...
>>>>>
>>>>> 2.  Recommendations for Implementers of Application Protocols
>>>>>
>>>>>    Implementers of application protocols MUST NOT treat the
>>>>>    general
>>>>>    categories of "standard" and "non-standard" parameters in
>>>>>    programatically different ways within their applications.
>>>>>
>>>>> Shouldn't this restrict itself to the naming of parameters? 
>>>>> Perhaps:
>>>>>
>>>>> 2.  Recommendations for Implementers of Application Protocols
>>>>>
>>>>>    Implementers of application protocols MUST NOT treat the
>>>>>    general
>>>>>    naming of parameters in programmatically different ways within
>>>>>    their applications depending on if they are "standard" or
>>>>
>>>> "non-standard".
>>>>
>>>> How about this?
>>>>
>>>>   Implementations of application protocols MUST NOT programatically
>>>>   discriminate between "standard" and "non-standard" parameters
>>>>   based
>>>>   solely on the names of such parameters.
>>>
>>> I'm not quite sure.
>>>
>>> Is this supposed to be about how one selects names or how one uses them.
>>> I'd thought it meant the former, but your revised text sounds like the
>>> latter to me.
>> The concept behind this text was always about how one uses names, or
>> more precisely how code implementations treat them, because the authors
>> are of the opinion that it's a bad idea for implementations to hardcode
>> their handling of parameter based solely on the existence of the string
>> 'x-' at the start of the parameter name. I think the revised text I
>> provided captures this more clearly.
> 
> Yes.  Thanks for clarifying.

Thanks for requesting clarification.

In my working copy I've changed that paragraph to:

   Implementations of application protocols MUST NOT programatically
   discriminate between "standard" and "non-standard" parameters based
   solely on the names of such parameters (i.e., based solely on
   whether the name begins with 'x-' or a similar string of characters).

Peter

-- 
Peter Saint-Andre
https://stpeter.im/



From scott@kitterman.com  Tue Mar  6 14:32:13 2012
Return-Path: <scott@kitterman.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E25B721E80E6 for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 14:32:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.587
X-Spam-Level: 
X-Spam-Status: No, score=-2.587 tagged_above=-999 required=5 tests=[AWL=0.012,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X9mwWHwaVQYY for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 14:32:13 -0800 (PST)
Received: from mailout02.controlledmail.com (mailout02.controlledmail.com [72.81.252.18]) by ietfa.amsl.com (Postfix) with ESMTP id 083D021E8043 for <ietf@ietf.org>; Tue,  6 Mar 2012 14:32:13 -0800 (PST)
Received: from mailout02.controlledmail.com (localhost [127.0.0.1]) by mailout02.controlledmail.com (Postfix) with ESMTP id 9ACF520E40C0; Tue,  6 Mar 2012 17:32:12 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=2007-00; t=1331073132; bh=nJHPMGOAEA4Fb8fhHd6Z5w5vSCHhppi59TVC2D8ppWk=; h=From:To:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version:Content-Transfer-Encoding:Content-Type; b=gEdsLMTTpwNdtoCaTc47FLfyReK1rWXgNcdvdKUzr3S2rJbXGnC5dvBmMyy49jSbb QdPgFWjS8FWeACatv4rp1NKQEQAhEYURh4gREjpw0G7opOkpVObYVyaa9iHbDclbop SWjCLfMtG7m5EQH5H2KW3fVDKhgqVoOC6eYfgnlw=
Received: from scott-latitude-e6320.localnet (static-72-81-252-21.bltmmd.fios.verizon.net [72.81.252.21]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailout02.controlledmail.com (Postfix) with ESMTPSA id 7D40320E4099;  Tue,  6 Mar 2012 17:32:12 -0500 (EST)
From: Scott Kitterman <scott@kitterman.com>
To: ietf@ietf.org
Subject: Re: Last Call: <draft-ietf-appsawg-xdash-03.txt> (Deprecating Use of the "X-" Prefix in Application Protocols) to Best Current Practice
Date: Tue, 06 Mar 2012 17:32:11 -0500
Message-ID: <1594750.fYz7DhtRup@scott-latitude-e6320>
User-Agent: KMail/4.7.3 (Linux/3.0.0-16-generic-pae; KDE/4.7.4; i686; ; )
In-Reply-To: <4F569014.1030208@stpeter.im>
References: <20120301184750.21152.93044.idtracker@ietfa.amsl.com> <1633774.E10J87jy7A@scott-latitude-e6320> <4F569014.1030208@stpeter.im>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
X-AV-Checked: ClamAV using ClamSMTP
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Mar 2012 22:32:14 -0000

On Tuesday, March 06, 2012 03:30:44 PM Peter Saint-Andre wrote:
> On 3/6/12 3:24 PM, Scott Kitterman wrote:
> > On Tuesday, March 06, 2012 03:19:41 PM Peter Saint-Andre wrote:
> >> On 3/1/12 5:14 PM, Scott Kitterman wrote:
> >>> Peter Saint-Andre <stpeter@stpeter.im> wrote:
> >>>> On 3/1/12 12:00 PM, Scott Kitterman wrote:
> >>>>> On Thursday, March 01, 2012 10:47:50 AM The IESG wrote:
> >>>>>> The IESG has received a request from the Applications Area
> >>>>>> Working
> >>>> 
> >>>> Group
> >>>> 
> >>>>>> WG (appsawg) to consider the following document:
> >>>>>> - 'Deprecating Use of the "X-" Prefix in Application
> >>>>>> Protocols'
> >>>>>> 
> >>>>>>   <draft-ietf-appsawg-xdash-03.txt> as a 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-03-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
> >>>>>> 
> >>>>>>    Historically, designers and implementers of application
> >>>>>>    protocols
> >>>>>>    have often distinguished between "standard" and
> >>>>>>    "non-standard"
> >>>>>>    parameters by prefixing the latter with the string "X-"
> >>>>>>    or
> >>>> 
> >>>> similar
> >>>> 
> >>>>>>    constructions.  In practice, this convention causes more
> >>>>>>    problems
> >>>>>>    than it solves.  Therefore, this document deprecates the
> >>>>>>    "X-"
> >>>>>>    convention for textual parameters in application
> >>>>>>    protocols.
> >>>>> 
> >>>>> ...
> >>>>> 
> >>>>> 2.  Recommendations for Implementers of Application Protocols
> >>>>> 
> >>>>>    Implementers of application protocols MUST NOT treat the
> >>>>>    general
> >>>>>    categories of "standard" and "non-standard" parameters in
> >>>>>    programatically different ways within their applications.
> >>>>> 
> >>>>> Shouldn't this restrict itself to the naming of parameters?
> >>>>> Perhaps:
> >>>>> 
> >>>>> 2.  Recommendations for Implementers of Application Protocols
> >>>>> 
> >>>>>    Implementers of application protocols MUST NOT treat the
> >>>>>    general
> >>>>>    naming of parameters in programmatically different ways
> >>>>>    within
> >>>>>    their applications depending on if they are "standard" or
> >>>> 
> >>>> "non-standard".
> >>>> 
> >>>> How about this?
> >>>> 
> >>>>   Implementations of application protocols MUST NOT
> >>>>   programatically
> >>>>   discriminate between "standard" and "non-standard" parameters
> >>>>   based
> >>>>   solely on the names of such parameters.
> >>> 
> >>> I'm not quite sure.
> >>> 
> >>> Is this supposed to be about how one selects names or how one uses
> >>> them. I'd thought it meant the former, but your revised text sounds
> >>> like the latter to me.
> >> 
> >> The concept behind this text was always about how one uses names, or
> >> more precisely how code implementations treat them, because the
> >> authors
> >> are of the opinion that it's a bad idea for implementations to
> >> hardcode
> >> their handling of parameter based solely on the existence of the
> >> string
> >> 'x-' at the start of the parameter name. I think the revised text I
> >> provided captures this more clearly.
> > 
> > Yes.  Thanks for clarifying.
> 
> Thanks for requesting clarification.
> 
> In my working copy I've changed that paragraph to:
> 
>    Implementations of application protocols MUST NOT programatically
>    discriminate between "standard" and "non-standard" parameters based
>    solely on the names of such parameters (i.e., based solely on
>    whether the name begins with 'x-' or a similar string of characters).
> 
> Peter

Looks good to me.

Scott K

From randy@qualcomm.com  Tue Mar  6 15:19:05 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 F0FAF21E805D for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 15:19:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.062
X-Spam-Level: 
X-Spam-Status: No, score=-106.062 tagged_above=-999 required=5 tests=[AWL=0.537, 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 cshxoWm48NRn for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 15:19:05 -0800 (PST)
Received: from wolverine01.qualcomm.com (wolverine01.qualcomm.com [199.106.114.254]) by ietfa.amsl.com (Postfix) with ESMTP id 5B18F21E800F for <ietf@ietf.org>; Tue,  6 Mar 2012 15:19:05 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=randy@qualcomm.com; q=dns/txt; s=qcdkim; t=1331075945; x=1362611945; h=message-id:in-reply-to:references:x-mailer:date:to:from: subject:cc:mime-version:content-type:x-random-sig-tag: x-originating-ip; z=Message-ID:=20<p06240606cb7c4ab0a3af@loud.pensive.org> |In-Reply-To:=20<4F569014.1030208@stpeter.im>|References: =20<20120301184750.21152.93044.idtracker@ietfa.amsl.com> =0D=0A=20<61623076-6684-46d9-94bc-eefb2b1de6b9@email.andr oid.com>=0D=0A=20<4F568D7D.8070502@stpeter.im>=0D=0A=20<1 633774.E10J87jy7A@scott-latitude-e6320>=0D=0A=20<4F569014 .1030208@stpeter.im>|X-Mailer:=20Eudora=20for=20Mac=20OS =20X|Date:=20Tue,=206=20Mar=202012=2015:19:01=20-0800|To: =20Peter=20Saint-Andre=20<stpeter@stpeter.im>,=20Scott=20 Kitterman=0D=0A=09<scott@kitterman.com>|From:=20Randall =20Gellens=20<randy@qualcomm.com>|Subject:=20Re:=20Last =20Call:=20<draft-ietf-appsawg-xdash-03.txt>=20(Deprecati ng=0D=0A=20Use=20=09of=20the=20"X-"=20Prefix=20in=20Appli cation=20Protocols)=20to=20Best=20Current=0D=0A=20Practic e|CC:=20<ietf@ietf.org>|MIME-Version:=201.0|Content-Type: =20text/plain=3B=20charset=3D"us-ascii"=3B=20format=3Dflo wed|X-Random-Sig-Tag:=201.0b28|X-Originating-IP:=20[172.3 0.39.5]; bh=//stwundr2CfpJFgxiwLWHEp7BJYhzjSIFgdoJB67nw=; b=E7DG8XA94i5oNcGDpJJaeV+DA0iTIbGJCSmlmYTqGOLB9WzxS7kQgBqV 6eJHzDMbH175Wo/BrmSqxxTENS1o/vCPWUbDL6F6VpSHmi/WwQ8+nz0GW 9icxasr/rya6s9IFtwliCb+qKIWThDd0f9yhM6Q7X9hTp7bN5mCKhiknX o=;
X-IronPort-AV: E=McAfee;i="5400,1158,6641"; a="169943204"
Received: from ironmsg02-r.qualcomm.com ([172.30.46.16]) by wolverine01.qualcomm.com with ESMTP; 06 Mar 2012 15:19:04 -0800
X-IronPort-AV: E=Sophos;i="4.73,540,1325491200"; d="scan'208";a="157807429"
Received: from nasanexhc08.na.qualcomm.com ([172.30.39.7]) by ironmsg02-R.qualcomm.com with ESMTP/TLS/AES128-SHA; 06 Mar 2012 15:19:04 -0800
Received: from loud.pensive.org (172.30.39.5) by qcmail1.qualcomm.com (172.30.39.7) with Microsoft SMTP Server (TLS) id 14.1.339.1; Tue, 6 Mar 2012 15:19:04 -0800
Message-ID: <p06240606cb7c4ab0a3af@loud.pensive.org>
In-Reply-To: <4F569014.1030208@stpeter.im>
References: <20120301184750.21152.93044.idtracker@ietfa.amsl.com> <61623076-6684-46d9-94bc-eefb2b1de6b9@email.android.com> <4F568D7D.8070502@stpeter.im> <1633774.E10J87jy7A@scott-latitude-e6320> <4F569014.1030208@stpeter.im>
X-Mailer: Eudora for Mac OS X
Date: Tue, 6 Mar 2012 15:19:01 -0800
To: Peter Saint-Andre <stpeter@stpeter.im>, Scott Kitterman <scott@kitterman.com>
From: Randall Gellens <randy@qualcomm.com>
Subject: Re: Last Call: <draft-ietf-appsawg-xdash-03.txt> (Deprecating Use 	of the "X-" Prefix in Application Protocols) to Best Current Practice
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Random-Sig-Tag: 1.0b28
X-Originating-IP: [172.30.39.5]
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Mar 2012 23:19:06 -0000

At 3:30 PM -0700 3/6/12, Peter Saint-Andre wrote:

>  In my working copy I've changed that paragraph to:
>
>     Implementations of application protocols MUST NOT programatically
>     discriminate between "standard" and "non-standard" parameters based
>     solely on the names of such parameters (i.e., based solely on
>     whether the name begins with 'x-' or a similar string of characters).

I like this wording, especially because it more clearly gets at the 
heart of the document, which is to not discriminate based only on the 
name prefix.

One question, though: should this be "SHOULD NOT" rather than "MUST 
NOT"?   The interoperability doesn't depend on implementations 
refraining from doing so, rather, we consider it more problematic to 
do so than not, so we are making a strong recommendation to not to 
so.  Hence, "SHOULD NOT".

 From RFC 2119:
    Imperatives of the type defined in this memo must be used with care
    and sparingly.  In particular, they MUST only be used where it is
    actually required for interoperation or to limit behavior which has
    potential for causing harm (e.g., limiting retransmisssions)  For
    example, they must not be used to try to impose a particular method
    on implementors where the method is not required for
    interoperability.


-- 
Randall Gellens
Opinions are personal;    facts are suspect;    I speak for myself only
-------------- Randomly selected tag: ---------------
Language is a virus from outer space.  --William S. Burroughs

From tbray@textuality.com  Tue Mar  6 15:31:53 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 5695A21E8011 for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 15:31:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.977
X-Spam-Level: 
X-Spam-Status: No, score=-2.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sk4gmpMAayTo for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 15:31:52 -0800 (PST)
Received: from mail-tul01m020-f172.google.com (mail-tul01m020-f172.google.com [209.85.214.172]) by ietfa.amsl.com (Postfix) with ESMTP id 9D44421E800F for <ietf@ietf.org>; Tue,  6 Mar 2012 15:31:52 -0800 (PST)
Received: by obbta4 with SMTP id ta4so4771945obb.31 for <ietf@ietf.org>; Tue, 06 Mar 2012 15:31:52 -0800 (PST)
Received-SPF: pass (google.com: domain of tbray@textuality.com designates 10.182.31.47 as permitted sender) client-ip=10.182.31.47; 
Authentication-Results: mr.google.com; spf=pass (google.com: domain of tbray@textuality.com designates 10.182.31.47 as permitted sender) smtp.mail=tbray@textuality.com
Received: from mr.google.com ([10.182.31.47]) by 10.182.31.47 with SMTP id x15mr10469755obh.76.1331076712352 (num_hops = 1); Tue, 06 Mar 2012 15:31:52 -0800 (PST)
MIME-Version: 1.0
Received: by 10.182.31.47 with SMTP id x15mr9201531obh.76.1331076712269; Tue, 06 Mar 2012 15:31:52 -0800 (PST)
Received: by 10.182.164.41 with HTTP; Tue, 6 Mar 2012 15:31:52 -0800 (PST)
X-Originating-IP: [2620:0:1000:2404:fa1e:dfff:fef0:5c5f]
In-Reply-To: <7CEA9124-7B72-4906-B5B4-E0C32E319433@vigilsec.com>
References: <CAErhfrxPe=KSKB7fVHLankkk5XRQ87oarg17kXqNB0o0jGD4hw@mail.gmail.com> <A37C45BE-963E-49AE-9BAE-4A5E2B68D2DB@vigilsec.com> <CAErhfrxUQTqBwRL5asJnnoMnBRi0CHAN4RDfAXyBMKwPr7z8OA@mail.gmail.com> <1D3193A0-B115-4700-A66B-A4ACD1C5FD64@checkpoint.com> <4F56853D.6000301@gmx.de> <D080D5A9-0C8D-4108-8BAD-26D778FE7C8E@checkpoint.com> <7CEA9124-7B72-4906-B5B4-E0C32E319433@vigilsec.com>
Date: Tue, 6 Mar 2012 15:31:52 -0800
Message-ID: <CAHBU6is-gLBm8QpshAHCfD0sUGtwuRRmdmg-tO=FDSb-ODYchA@mail.gmail.com>
Subject: Re: Add a link to the HTML version in i-d-announce mails ?
From: Tim Bray <tbray@textuality.com>
To: Russ Housley <housley@vigilsec.com>
Content-Type: text/plain; charset=ISO-8859-1
X-Gm-Message-State: ALoCoQnDULD101J/jrFXCmVkzxwuqnRVdYNvP/f6Ewff1MEhmgkD/v0XU7mE2KWGZCj5ktihpBeH
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Mar 2012 23:31:53 -0000

Not that voicing opinions on this topic has ever done any good. -T

On Tue, Mar 6, 2012 at 2:15 PM, Russ Housley <housley@vigilsec.com> wrote:
>
>> Pictures in RFCs?
>
> Come to the RFCFORM BOF to voice opinions on this topic.
>
> Russ
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf

From stpeter@stpeter.im  Tue Mar  6 15:32:16 2012
Return-Path: <stpeter@stpeter.im>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7078E21E80CA for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 15:32:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.78
X-Spam-Level: 
X-Spam-Status: No, score=-102.78 tagged_above=-999 required=5 tests=[AWL=-0.181, 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 54It4c5ZOaT5 for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 15:32:15 -0800 (PST)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id BEE2321E8015 for <ietf@ietf.org>; Tue,  6 Mar 2012 15:32:15 -0800 (PST)
Received: from squire.local (unknown [64.101.72.114]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id C53D940058; Tue,  6 Mar 2012 16:44:12 -0700 (MST)
Message-ID: <4F569E7E.8030307@stpeter.im>
Date: Tue, 06 Mar 2012 16:32:14 -0700
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.5; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: Randall Gellens <randy@qualcomm.com>
Subject: Re: Last Call: <draft-ietf-appsawg-xdash-03.txt> (Deprecating Use of the "X-" Prefix in Application Protocols) to Best Current Practice
References: <20120301184750.21152.93044.idtracker@ietfa.amsl.com> <61623076-6684-46d9-94bc-eefb2b1de6b9@email.android.com> <4F568D7D.8070502@stpeter.im> <1633774.E10J87jy7A@scott-latitude-e6320> <4F569014.1030208@stpeter.im> <p06240606cb7c4ab0a3af@loud.pensive.org>
In-Reply-To: <p06240606cb7c4ab0a3af@loud.pensive.org>
X-Enigmail-Version: 1.3.5
OpenPGP: url=https://stpeter.im/stpeter.asc
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Mark Nottingham <mnot@mnot.net>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Mar 2012 23:32:16 -0000

On 3/6/12 4:19 PM, Randall Gellens wrote:
> At 3:30 PM -0700 3/6/12, Peter Saint-Andre wrote:
> 
>>  In my working copy I've changed that paragraph to:
>>
>>     Implementations of application protocols MUST NOT programatically
>>     discriminate between "standard" and "non-standard" parameters based
>>     solely on the names of such parameters (i.e., based solely on
>>     whether the name begins with 'x-' or a similar string of characters).
> 
> I like this wording, especially because it more clearly gets at the
> heart of the document, which is to not discriminate based only on the
> name prefix.
> 
> One question, though: should this be "SHOULD NOT" rather than "MUST
> NOT"?   The interoperability doesn't depend on implementations
> refraining from doing so, rather, we consider it more problematic to do
> so than not, so we are making a strong recommendation to not to so. 
> Hence, "SHOULD NOT".

Hi Randall,

My co-author Mark Nottingham feels even more strongly about this issue
than I do, so I will let him comment.

However, note the existence of things like the "x-gzip" and "gzip"
content codings in HTTP, which RFC 2068 says are equivalent. An
implementation that programmatically discriminated between "standard"
and "non-standard" parameters based solely on the parameter names might
automatically reject entities for which a content-coding of "x-gzip" is
specified, but automatically accept entities for which a content-coding
of "gzip" is specified. IMHO that's just wrong, and MUST NOT is appropriate.

Peter

-- 
Peter Saint-Andre
https://stpeter.im/



From stpeter@stpeter.im  Tue Mar  6 15:42:12 2012
Return-Path: <stpeter@stpeter.im>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 45B3421E8011 for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 15:42:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.779
X-Spam-Level: 
X-Spam-Status: No, score=-102.779 tagged_above=-999 required=5 tests=[AWL=-0.180, 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 SuNTGj34EdUb for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 15:42:11 -0800 (PST)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 56A9921E800F for <ietf@ietf.org>; Tue,  6 Mar 2012 15:42:11 -0800 (PST)
Received: from squire.local (unknown [64.101.72.114]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 595B940058; Tue,  6 Mar 2012 16:54:08 -0700 (MST)
Message-ID: <4F56A0D1.8060700@stpeter.im>
Date: Tue, 06 Mar 2012 16:42:09 -0700
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.5; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: Randall Gellens <randy@qualcomm.com>
Subject: Re: Last Call: <draft-ietf-appsawg-xdash-03.txt>
References: <p06240605cb7713381b6a@loud.pensive.org>
In-Reply-To: <p06240605cb7713381b6a@loud.pensive.org>
X-Enigmail-Version: 1.3.5
OpenPGP: url=https://stpeter.im/stpeter.asc
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Mark Nottingham <mnot@mnot.net>, ietf@ietf.org, Dave Crocker <dcrocker@bbiw.net>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Mar 2012 23:42:12 -0000

On 3/2/12 5:48 PM, Randall Gellens wrote:
> Hi all,

Hi Randall, thank you for the review and suggested text.

> Three suggestions for edits:
> 
> First: I suggest adding a brief note to this text in Appendix B:
> 
>    2.  When parameter names might have significant meaning.  However,
>        this case too is rare, since implementers can almost always find
>        a synonym for an existing term (e.g., "urgency" instead of
>        "priority") or simply invent a more creative name (e.g., "get-it-
>        there-fast").
> 
> At the end, I suggest adding an additional sentence:
> 
>     The existence of multiple similarly-named paramaters can
>     be confusing, but this is true regardless if there is an
>     attempt to segregate standard and non-standard (e.g.,
>     "X-Priority" can be confused with "Urgency").

True. If my co-authors agree, I'll add that to our working copy.

> Second, consider this the text in Appendix B:
> 
>    Furthermore, often standardization of a non-standard parameter or
>    protocol element leads to subtly different behavior (e.g., the
>    standard version might have different security properties as a result
>    of security review provided during the standardization process).  If
>    implementers treat the old, non-standard parameter and the new,
>    standard parameter as equivalent, interoperability and security
>    problems can ensue.
> 
> This is of course true, but I think it is somewhat misleading:  If a
> parameter starts out as non-standard, gets some deployment, then as part
> of an effort to standardize it, flaws are discovered which require
> different behavior, I think we want the new, standardized parameter to
> have a different name so it can be distinguished and the new, more
> desirable behavior mandated.  This is the same regardless if the old and
> new parameters are, say, "x-priority" and "priority", or "priority" and
> "urgency".  In either case, implementers shouldn't treat the old
> parameter as identical to the new, standardized one.

Yet that's what RFC 2068 says:

      For compatibility with previous implementations of HTTP,
      applications should consider "x-gzip" and "x-compress" to be
      equivalent to "gzip" and "compress" respectively.

However, as far as I have been able to determine there were no
significant differences between the "standard" and "non-standard"
versions of those parameters (others here would know better than I do).

> Further, I think it's a good thing when an old, non-standard parameter
> is standardized and flaws are corrected.  We should encourage, not
> discourage this.

Indeed.

> It would be good to have at least a little text along these lines.
> Specifically, I suggest adding new text at the end:
> 
>     Analysis of non-standard parameters and protocol elements
>     to detect and correct flaws is in general a good thing and
>     is not intended to be discouraged by the lack of
>     distinction in element names.  Whenever an originally
>     non-standard parameter or protocol element is standardized
>     and the new form has differences which affect
>     interoperability or security properties, implementations
>     MUST NOT treat the old form as identical to the new form.

That seems fine (although I would not include "protocol element" because
this document is only about parameters).

> Further in the appendix, justification 1 is over-drawn.  I suggest
> toning it down slightly, from:
> 
>    1.  Implementers are easily confused and can't be expected to know
>        that a parameter is non-standard unless it contains the "X-"
>        prefix.  However, implementers already are quite flexible about
>        using both prefixed and non-prefixed names based on what works in
>        the field, so the distinction between de facto names (e.g.,
>        "X-foo") and de jure names (e.g., "foo") is without force.
> 
> To:
> 
>    1.  Implementers may confuse parameters that have similar
>    names; a rigid distinction such as an "X-" prefix can make
>    this clear.  However, in practice implementers are forced
>    to blur the distinction (e.g., by treating "X-foo" as a de
>    facto standard) and so it inevitably becomes meaningless.

WFM, let's see if my co-authors agree.

Proposed text is always appreciated.

Peter

-- 
Peter Saint-Andre
https://stpeter.im/



From msk@cloudmark.com  Tue Mar  6 15:46:17 2012
Return-Path: <msk@cloudmark.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 87B2821E8011 for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 15:46:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.604
X-Spam-Level: 
X-Spam-Status: No, score=-102.604 tagged_above=-999 required=5 tests=[AWL=-0.005, 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 dSTGtRiRNE7Z for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 15:46:16 -0800 (PST)
Received: from ht1-outbound.cloudmark.com (ht1-outbound.cloudmark.com [72.5.239.25]) by ietfa.amsl.com (Postfix) with ESMTP id 13C7221F859A for <ietf@ietf.org>; Tue,  6 Mar 2012 15:46:08 -0800 (PST)
Received: from EXCH-MBX901.corp.cloudmark.com ([fe80::addf:849a:f71c:4a82]) by EXCH-HTCAS901.corp.cloudmark.com ([fe80::2966:6846:8d89:4681%12]) with mapi id 14.01.0355.002; Tue, 6 Mar 2012 15:46:07 -0800
From: "Murray S. Kucherawy" <msk@cloudmark.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: Last Call: <draft-ietf-appsawg-xdash-03.txt> (Deprecating Use of the "X-" Prefix in Application Protocols) to Best Current Practice
Thread-Topic: Last Call: <draft-ietf-appsawg-xdash-03.txt> (Deprecating Use of the "X-" Prefix in Application Protocols) to Best Current Practice
Thread-Index: AQHM+/Fuu7ieUwZOf0m2MQSiMH7E35Zd7ojA
Date: Tue, 6 Mar 2012 23:46:07 +0000
Message-ID: <9452079D1A51524AA5749AD23E00392807D4EC@exch-mbx901.corp.cloudmark.com>
References: <20120301184750.21152.93044.idtracker@ietfa.amsl.com> <61623076-6684-46d9-94bc-eefb2b1de6b9@email.android.com> <4F568D7D.8070502@stpeter.im>	<1633774.E10J87jy7A@scott-latitude-e6320> <4F569014.1030208@stpeter.im>	<p06240606cb7c4ab0a3af@loud.pensive.org> <4F569E7E.8030307@stpeter.im>
In-Reply-To: <4F569E7E.8030307@stpeter.im>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.20.2.121]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Mar 2012 23:46:18 -0000

Hey Peter,

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of P=
eter Saint-Andre
> Sent: Tuesday, March 06, 2012 3:32 PM
> To: Randall Gellens
> Cc: Mark Nottingham; ietf@ietf.org
> Subject: Re: Last Call: <draft-ietf-appsawg-xdash-03.txt> (Deprecating
> Use of the "X-" Prefix in Application Protocols) to Best Current
> Practice
>=20
> However, note the existence of things like the "x-gzip" and "gzip"
> content codings in HTTP, which RFC 2068 says are equivalent. An
> implementation that programmatically discriminated between "standard"
> and "non-standard" parameters based solely on the parameter names might
> automatically reject entities for which a content-coding of "x-gzip" is
> specified, but automatically accept entities for which a content-coding
> of "gzip" is specified. IMHO that's just wrong, and MUST NOT is
> appropriate.

So should this document note that it "Updates 2068"?

-MSK

From stpeter@stpeter.im  Tue Mar  6 15:50:01 2012
Return-Path: <stpeter@stpeter.im>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 51AA121E803D for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 15:50:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.778
X-Spam-Level: 
X-Spam-Status: No, score=-102.778 tagged_above=-999 required=5 tests=[AWL=-0.179, 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 PqHuvh-IcC1Q for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 15:50:00 -0800 (PST)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id B54FC21E8015 for <ietf@ietf.org>; Tue,  6 Mar 2012 15:49:58 -0800 (PST)
Received: from squire.local (unknown [64.101.72.114]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id F236240058; Tue,  6 Mar 2012 17:01:55 -0700 (MST)
Message-ID: <4F56A2A5.8000507@stpeter.im>
Date: Tue, 06 Mar 2012 16:49:57 -0700
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.5; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: "Murray S. Kucherawy" <msk@cloudmark.com>
Subject: Re: Last Call: <draft-ietf-appsawg-xdash-03.txt> (Deprecating Use of the "X-" Prefix in Application Protocols) to Best Current Practice
References: <20120301184750.21152.93044.idtracker@ietfa.amsl.com> <61623076-6684-46d9-94bc-eefb2b1de6b9@email.android.com> <4F568D7D.8070502@stpeter.im>	<1633774.E10J87jy7A@scott-latitude-e6320> <4F569014.1030208@stpeter.im>	<p06240606cb7c4ab0a3af@loud.pensive.org> <4F569E7E.8030307@stpeter.im> <9452079D1A51524AA5749AD23E00392807D4EC@exch-mbx901.corp.cloudmark.com>
In-Reply-To: <9452079D1A51524AA5749AD23E00392807D4EC@exch-mbx901.corp.cloudmark.com>
X-Enigmail-Version: 1.3.5
OpenPGP: url=https://stpeter.im/stpeter.asc
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Mar 2012 23:50:01 -0000

On 3/6/12 4:46 PM, Murray S. Kucherawy wrote:
> Hey Peter,

Howdy. :)

>> -----Original Message-----
>> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of Peter Saint-Andre
>> Sent: Tuesday, March 06, 2012 3:32 PM
>> To: Randall Gellens
>> Cc: Mark Nottingham; ietf@ietf.org
>> Subject: Re: Last Call: <draft-ietf-appsawg-xdash-03.txt> (Deprecating
>> Use of the "X-" Prefix in Application Protocols) to Best Current
>> Practice
>>
>> However, note the existence of things like the "x-gzip" and "gzip"
>> content codings in HTTP, which RFC 2068 says are equivalent. An
>> implementation that programmatically discriminated between "standard"
>> and "non-standard" parameters based solely on the parameter names might
>> automatically reject entities for which a content-coding of "x-gzip" is
>> specified, but automatically accept entities for which a content-coding
>> of "gzip" is specified. IMHO that's just wrong, and MUST NOT is
>> appropriate.
> 
> So should this document note that it "Updates 2068"?

I don't think so, because "x-gzip" and "gzip" were in fact equivalent
(as far as I can see), so treating them as equivalent seems just fine.

Peter

-- 
Peter Saint-Andre
https://stpeter.im/



From randy@qualcomm.com  Tue Mar  6 16:03:27 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 EE1D721E8069 for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 16:03:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.152
X-Spam-Level: 
X-Spam-Status: No, score=-106.152 tagged_above=-999 required=5 tests=[AWL=0.447, 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 KvABdwjk3UhO for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 16:03:27 -0800 (PST)
Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) by ietfa.amsl.com (Postfix) with ESMTP id 2D7EF21E806D for <ietf@ietf.org>; Tue,  6 Mar 2012 16:03:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=randy@qualcomm.com; q=dns/txt; s=qcdkim; t=1331078607; x=1362614607; h=message-id:in-reply-to:references:x-mailer:date:to:from: subject:cc:mime-version:content-type:x-random-sig-tag: x-originating-ip; z=Message-ID:=20<p06240607cb7c5510122d@loud.pensive.org> |In-Reply-To:=20<4F569E7E.8030307@stpeter.im>|References: =20<20120301184750.21152.93044.idtracker@ietfa.amsl.com> =0D=0A=20<61623076-6684-46d9-94bc-eefb2b1de6b9@email.andr oid.com>=0D=0A=20<4F568D7D.8070502@stpeter.im>=0D=0A=20<1 633774.E10J87jy7A@scott-latitude-e6320>=0D=0A=20<4F569014 .1030208@stpeter.im>=0D=0A=20<p06240606cb7c4ab0a3af@loud. pensive.org>=20<4F569E7E.8030307@stpeter.im>|X-Mailer:=20 Eudora=20for=20Mac=20OS=20X|Date:=20Tue,=206=20Mar=202012 =2016:03:23=20-0800|To:=20Peter=20Saint-Andre=20<stpeter@ stpeter.im>|From:=20Randall=20Gellens=20<randy@qualcomm.c om>|Subject:=20Re:=20Last=20Call:=20<draft-ietf-appsawg-x dash-03.txt>=20(Deprecating=0D=0A=20Use=20=20=09of=20the =20"X-"=20Prefix=20in=20Application=20Protocols)=20to=20B est=20Current=0D=0A=20Practice|CC:=20Scott=20Kitterman=20 <scott@kitterman.com>,=20<ietf@ietf.org>,=20Mark=20Nottin gham=0D=0A=09<mnot@mnot.net>|MIME-Version:=201.0 |Content-Type:=20text/plain=3B=20charset=3D"us-ascii"=3B =20format=3Dflowed|X-Random-Sig-Tag:=201.0b28 |X-Originating-IP:=20[172.30.39.5]; bh=WeBbY9rO298CxoT7JxFyNBV1mYFwo6sFPQ5LnPH5c1g=; b=ScASd2AE76JW3X3MaDQ1nVX7Hga2US8wr+hDVmiWYxR3R22i+Z80SSZQ 54Wb/YZNokoN+wZxPJW1lw0+Gwi1lugAT86DGsudHYz9Sgd7GcFFnckhs rxa6ew5KvAiRRSmJWwIsjCEPsHcDRqKsUteOt0j5NOFHjArbumciVXf2p I=;
X-IronPort-AV: E=McAfee;i="5400,1158,6641"; a="167645537"
Received: from ironmsg02-r.qualcomm.com ([172.30.46.16]) by wolverine02.qualcomm.com with ESMTP; 06 Mar 2012 16:03:26 -0800
X-IronPort-AV: E=Sophos;i="4.73,540,1325491200"; d="scan'208";a="157808132"
Received: from nasanexhc08.na.qualcomm.com ([172.30.39.7]) by ironmsg02-R.qualcomm.com with ESMTP/TLS/AES128-SHA; 06 Mar 2012 16:03:26 -0800
Received: from loud.pensive.org (172.30.39.5) by qcmail1.qualcomm.com (172.30.39.7) with Microsoft SMTP Server (TLS) id 14.1.339.1; Tue, 6 Mar 2012 16:03:26 -0800
Message-ID: <p06240607cb7c5510122d@loud.pensive.org>
In-Reply-To: <4F569E7E.8030307@stpeter.im>
References: <20120301184750.21152.93044.idtracker@ietfa.amsl.com> <61623076-6684-46d9-94bc-eefb2b1de6b9@email.android.com> <4F568D7D.8070502@stpeter.im> <1633774.E10J87jy7A@scott-latitude-e6320> <4F569014.1030208@stpeter.im> <p06240606cb7c4ab0a3af@loud.pensive.org> <4F569E7E.8030307@stpeter.im>
X-Mailer: Eudora for Mac OS X
Date: Tue, 6 Mar 2012 16:03:23 -0800
To: Peter Saint-Andre <stpeter@stpeter.im>
From: Randall Gellens <randy@qualcomm.com>
Subject: Re: Last Call: <draft-ietf-appsawg-xdash-03.txt> (Deprecating Use  	of the "X-" Prefix in Application Protocols) to Best Current Practice
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Random-Sig-Tag: 1.0b28
X-Originating-IP: [172.30.39.5]
Cc: Mark Nottingham <mnot@mnot.net>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Mar 2012 00:03:28 -0000

At 4:32 PM -0700 3/6/12, Peter Saint-Andre wrote:

>  On 3/6/12 4:19 PM, Randall Gellens wrote:
>>  At 3:30 PM -0700 3/6/12, Peter Saint-Andre wrote:
>>
>>>   In my working copy I've changed that paragraph to:
>>>
>>>      Implementations of application protocols MUST NOT programatically
>>>      discriminate between "standard" and "non-standard" parameters based
>>>      solely on the names of such parameters (i.e., based solely on
>>>      whether the name begins with 'x-' or a similar string of characters).
>>
>>  I like this wording, especially because it more clearly gets at the
>>  heart of the document, which is to not discriminate based only on the
>>  name prefix.
>>
>>  One question, though: should this be "SHOULD NOT" rather than "MUST
>>  NOT"?   The interoperability doesn't depend on implementations
>>  refraining from doing so, rather, we consider it more problematic to do
>>  so than not, so we are making a strong recommendation to not to so.
>>  Hence, "SHOULD NOT".
>
>  Hi Randall,
>
>  My co-author Mark Nottingham feels even more strongly about this issue
>  than I do, so I will let him comment.
>
>  However, note the existence of things like the "x-gzip" and "gzip"
>  content codings in HTTP, which RFC 2068 says are equivalent. An
>  implementation that programmatically discriminated between "standard"
>  and "non-standard" parameters based solely on the parameter names might
>  automatically reject entities for which a content-coding of "x-gzip" is
>  specified, but automatically accept entities for which a content-coding
>  of "gzip" is specified. IMHO that's just wrong, and MUST NOT is appropriate.

Hi Peter,

Is the hypothetical application discriminating between all "x-" and 
everything else, or is it only doing so for parameters it does not 
recognize?  In the case of "x-gzip" and "gzip", wouldn't the 
application be doing whatever it does based on recognizing that this 
is gzip?

Anyway, it's hard for me to imagine a real application doing 
something like what the text suggests (say, bouncing email with 
"x-gzip" or refusing to expand an file or attachment of "x-gzip"), 
and even if there were such an application, it would be a very broken 
implementation, but not something that harmed the Internet or even 
anyone else whose applications worked properly.  At most it would 
harm its own user, who I assume would quickly dump it.

-- 
Randall Gellens
Opinions are personal;    facts are suspect;    I speak for myself only
-------------- Randomly selected tag: ---------------
Computers are not intelligent.  They only think they are.

From johnl@iecc.com  Tue Mar  6 16:08:38 2012
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BC7EC21E803C for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 16:08:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.565
X-Spam-Level: 
X-Spam-Status: No, score=-110.565 tagged_above=-999 required=5 tests=[AWL=0.634, 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 CHDk8rBuE12R for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 16:08:38 -0800 (PST)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 0140D21E801F for <ietf@ietf.org>; Tue,  6 Mar 2012 16:08:37 -0800 (PST)
Received: (qmail 59199 invoked from network); 7 Mar 2012 00:08:36 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 7 Mar 2012 00:08:36 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=4f56a704.xn--30v786c.k1203; i=johnl@user.iecc.com; bh=2SA2fdYD4RmzaQraioT2gbzj/fuOlYkZHzdN70MIMyY=; b=m2xGRa5N5Qs0UT7h/TS3MrR6nFmXemsvbd9HXGgkcJsAwNXeu8H7a/5z3S038o2DD+Ca8qJIMDJ9dfL805JK97vcCXmXABcyHozXpjfV25tKqfXFZ0T0jIfpUXCLjPuli+EpbFBf+6tebqguGVDXXu5bX7ffUge3cG3Z0g7r6as=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 7 Mar 2012 00:08:14 -0000
Message-ID: <20120307000814.29422.qmail@joyce.lan>
From: "John Levine" <johnl@iecc.com>
To: ietf@ietf.org
Subject: Re: provisioning software, was DNS RRTYPEs, the difficulty with
In-Reply-To: <20120306221931.E60E41E1DF40@drugs.dv.isc.org>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Mar 2012 00:08:38 -0000

>> > Last month I ran into a guy on the dmarc list who complained that his
>> > server returns NOTIMP in response to queries for SPF records ("because
>> > it doesn't implement them") and clients were doing odd things.  But
>> > it's been a long time since I've run into anyone else like that, so I
>> > agree, it's not an issue.

In case it wasn't clear, this is an authoritative server.

>A RFC 1035 recursive server should be able to handle SPF.  It's
>just a opaque data blob to it with a name, type, class and ttl
>attributes.

Agreed.  Other than a few dusty Suns still running obsolete BIND 4.x,
I don't know of any DNS caches that have problems with arbitrary RRs.

R's,
John

From randy@qualcomm.com  Tue Mar  6 16:16:40 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 EBA0721E801A for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 16:16:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.216
X-Spam-Level: 
X-Spam-Status: No, score=-106.216 tagged_above=-999 required=5 tests=[AWL=0.383, 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 JGnXlhoPcLDC for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 16:16:39 -0800 (PST)
Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) by ietfa.amsl.com (Postfix) with ESMTP id E9BC421E800F for <ietf@ietf.org>; Tue,  6 Mar 2012 16:16:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=randy@qualcomm.com; q=dns/txt; s=qcdkim; t=1331079398; x=1362615398; h=message-id:in-reply-to:references:x-mailer:date:to:from: subject:cc:mime-version:content-type:x-random-sig-tag: x-originating-ip; z=Message-ID:=20<p06240608cb7c56a27084@loud.pensive.org> |In-Reply-To:=20<4F56A0D1.8060700@stpeter.im>|References: =20<p06240605cb7713381b6a@loud.pensive.org>=0D=0A=20<4F56 A0D1.8060700@stpeter.im>|X-Mailer:=20Eudora=20for=20Mac =20OS=20X|Date:=20Tue,=206=20Mar=202012=2016:16:34=20-080 0|To:=20Peter=20Saint-Andre=20<stpeter@stpeter.im>|From: =20Randall=20Gellens=20<randy@qualcomm.com>|Subject:=20Re :=20Last=20Call:=20<draft-ietf-appsawg-xdash-03.txt>|CC: =20<ietf@ietf.org>,=20Dave=20Crocker=20<dcrocker@bbiw.net >,=20Mark=20Nottingham=0D=0A=09<mnot@mnot.net> |MIME-Version:=201.0|Content-Type:=20text/plain=3B=20char set=3D"us-ascii"=3B=20format=3Dflowed|X-Random-Sig-Tag: =201.0b28|X-Originating-IP:=20[172.30.39.5]; bh=0N6W9pfgk/Kn3FjCRtshElvJrCILhsGQv+Lu5cjnp5E=; b=OGi27R6cymQ4Xw4DpmTKu5y0+XxUWd3bm0KxV1ampcIjJHZs9ff1mVP4 PSmke1dD6SZ5Dhv3cOQniqbXy9iGqFC/H968rvVUkylpLgv2bniMq19JJ OH9+eA2cLyRnIJnKJtRh9/7GtWAukMMHaGw2ERxSO7THWPsvHdjyVAuq3 M=;
X-IronPort-AV: E=McAfee;i="5400,1158,6641"; a="167648440"
Received: from ironmsg03-r.qualcomm.com ([172.30.46.17]) by wolverine02.qualcomm.com with ESMTP; 06 Mar 2012 16:16:38 -0800
X-IronPort-AV: E=Sophos;i="4.73,540,1325491200"; d="scan'208";a="212407051"
Received: from nasanexhc08.na.qualcomm.com ([172.30.39.7]) by Ironmsg03-R.qualcomm.com with ESMTP/TLS/AES128-SHA; 06 Mar 2012 16:16:38 -0800
Received: from loud.pensive.org (172.30.39.5) by qcmail1.qualcomm.com (172.30.39.7) with Microsoft SMTP Server (TLS) id 14.1.339.1; Tue, 6 Mar 2012 16:16:37 -0800
Message-ID: <p06240608cb7c56a27084@loud.pensive.org>
In-Reply-To: <4F56A0D1.8060700@stpeter.im>
References: <p06240605cb7713381b6a@loud.pensive.org> <4F56A0D1.8060700@stpeter.im>
X-Mailer: Eudora for Mac OS X
Date: Tue, 6 Mar 2012 16:16:34 -0800
To: Peter Saint-Andre <stpeter@stpeter.im>
From: Randall Gellens <randy@qualcomm.com>
Subject: Re: Last Call: <draft-ietf-appsawg-xdash-03.txt>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Random-Sig-Tag: 1.0b28
X-Originating-IP: [172.30.39.5]
Cc: Mark Nottingham <mnot@mnot.net>, ietf@ietf.org, Dave Crocker <dcrocker@bbiw.net>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Mar 2012 00:16:40 -0000

Hi Peter,

At 4:42 PM -0700 3/6/12, Peter Saint-Andre wrote:

>  On 3/2/12 5:48 PM, Randall Gellens wrote:
>>  Hi all,
>
>  Hi Randall, thank you for the review and suggested text.
>
>>  Three suggestions for edits:
>>
>>  First: I suggest adding a brief note to this text in Appendix B:
>>
>>     2.  When parameter names might have significant meaning.  However,
>>         this case too is rare, since implementers can almost always find
>>         a synonym for an existing term (e.g., "urgency" instead of
>>         "priority") or simply invent a more creative name (e.g., "get-it-
>>         there-fast").
>>
>>  At the end, I suggest adding an additional sentence:
>>
>>      The existence of multiple similarly-named paramaters can
>>      be confusing, but this is true regardless if there is an
>>      attempt to segregate standard and non-standard (e.g.,
>>      "X-Priority" can be confused with "Urgency").
>
>  True. If my co-authors agree, I'll add that to our working copy.
>
>>  Second, consider this the text in Appendix B:
>>
>>     Furthermore, often standardization of a non-standard parameter or
>>     protocol element leads to subtly different behavior (e.g., the
>>     standard version might have different security properties as a result
>>     of security review provided during the standardization process).  If
>>     implementers treat the old, non-standard parameter and the new,
>>     standard parameter as equivalent, interoperability and security
>>     problems can ensue.
>>
>>  This is of course true, but I think it is somewhat misleading:  If a
>>  parameter starts out as non-standard, gets some deployment, then as part
>>  of an effort to standardize it, flaws are discovered which require
>>  different behavior, I think we want the new, standardized parameter to
>>  have a different name so it can be distinguished and the new, more
>>  desirable behavior mandated.  This is the same regardless if the old and
>>  new parameters are, say, "x-priority" and "priority", or "priority" and
>>  "urgency".  In either case, implementers shouldn't treat the old
>>  parameter as identical to the new, standardized one.
>
>  Yet that's what RFC 2068 says:
>
>        For compatibility with previous implementations of HTTP,
>        applications should consider "x-gzip" and "x-compress" to be
>        equivalent to "gzip" and "compress" respectively.
>
>  However, as far as I have been able to determine there were no
>  significant differences between the "standard" and "non-standard"
>  versions of those parameters (others here would know better than I do).

Thanks for digging that up.  I think this goes to my point, which is 
that either there are important differences, or there aren't; if 
there are (especially security-related ones) then we don't want to 
treat the old, non-standard and the new standard as equivalent, 
because it isn't safe to treat them as the same.  But if it is safe 
to treat them as the same, then of course it makes sense to do so. 
And this is orthogonal to an attempt to segregate standard and 
non-standard names.  I think it also makes your point, which is that 
the attempt at segregating the names doesn't help; we still want to 
either treat them as the same or not, based on specifics of the 
situation, not the name.  I'd even suggest that this aspect is a 
strong argument in favor of this document: it doesn't work to use the 
names as an automatic discriminator, there needs to be case-by-case 
evaluation.

>   > Further, I think it's a good thing when an old, non-standard parameter
>>  is standardized and flaws are corrected.  We should encourage, not
>>  discourage this.
>
>  Indeed.
>
>>  It would be good to have at least a little text along these lines.
>>  Specifically, I suggest adding new text at the end:
>>
>>      Analysis of non-standard parameters and protocol elements
>>      to detect and correct flaws is in general a good thing and
>>      is not intended to be discouraged by the lack of
>   >     distinction in element names.  Whenever an originally
>>      non-standard parameter or protocol element is standardized
>>      and the new form has differences which affect
>>      interoperability or security properties, implementations
>>      MUST NOT treat the old form as identical to the new form.
>
>  That seems fine (although I would not include "protocol element" because
>  this document is only about parameters).

Sounds good to me.  I only added "protocol element" because I saw it 
elsewhere in the document.


>   > Further in the appendix, justification 1 is over-drawn.  I suggest
>>  toning it down slightly, from:
>>
>>     1.  Implementers are easily confused and can't be expected to know
>>         that a parameter is non-standard unless it contains the "X-"
>>         prefix.  However, implementers already are quite flexible about
>>         using both prefixed and non-prefixed names based on what works in
>>         the field, so the distinction between de facto names (e.g.,
>>         "X-foo") and de jure names (e.g., "foo") is without force.
>>
>>  To:
>>
>>     1.  Implementers may confuse parameters that have similar
>>     names; a rigid distinction such as an "X-" prefix can make
>>     this clear.  However, in practice implementers are forced
>>     to blur the distinction (e.g., by treating "X-foo" as a de
>>     facto standard) and so it inevitably becomes meaningless.
>
>  WFM, let's see if my co-authors agree.
>
>  Proposed text is always appreciated.


-- 
Randall Gellens
Opinions are personal;    facts are suspect;    I speak for myself only
-------------- Randomly selected tag: ---------------
Do not drink coffee in early A.M.  It will keep you awake until noon.

From barryleiba.mailing.lists@gmail.com  Tue Mar  6 16:43:38 2012
Return-Path: <barryleiba.mailing.lists@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4420821F8704 for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 16:43:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.985
X-Spam-Level: 
X-Spam-Status: No, score=-102.985 tagged_above=-999 required=5 tests=[AWL=-0.008, 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 zPrJf5zlixH6 for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 16:43:37 -0800 (PST)
Received: from mail-gy0-f172.google.com (mail-gy0-f172.google.com [209.85.160.172]) by ietfa.amsl.com (Postfix) with ESMTP id 957F221F8714 for <ietf@ietf.org>; Tue,  6 Mar 2012 16:43:37 -0800 (PST)
Received: by ghbg16 with SMTP id g16so2945017ghb.31 for <ietf@ietf.org>; Tue, 06 Mar 2012 16:43:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=Jnk34HhVosPL/2Is7t9BxV9O+jlzZ9SoSFCQdBNr4+M=; b=qICWsn1wKOq8WeoCWrbA7wh/lmntMJh2CLmhKVYjnhjrmQJ+9iwVUeZ1pDE7OLxXgL i3lV7Foi82QqvUIyYoLRRsWbpiHV03dAdpM+mgylMmSYhadckUyCjuBvrK3rIGHkn3St w4F8CigvyolUJg4bbdBsyzh95FdJyWPQOS4xnrZwd2YRHCRAYrn0C3/jFnpmS+D/slK8 xptSeLOTxbQRhR2GJAwPYLR7C6ZKXoGlg+kiSwi9JyRo9HwnQvW4knpi3XNjX9TCFYr7 xecbgSdZH9gXzGho4aiEOe3RIaY9Z53Yb2lgV9opYMF9W6qAD73nJU5BBlP2IPwLb36f nfEQ==
MIME-Version: 1.0
Received: by 10.236.186.1 with SMTP id v1mr210512yhm.4.1331081017259; Tue, 06 Mar 2012 16:43:37 -0800 (PST)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.147.106.16 with HTTP; Tue, 6 Mar 2012 16:43:37 -0800 (PST)
In-Reply-To: <3DEB2E7A-CED3-46CA-8891-43A51E61CA0A@kumari.net>
References: <CAErhfrxPe=KSKB7fVHLankkk5XRQ87oarg17kXqNB0o0jGD4hw@mail.gmail.com> <3DEB2E7A-CED3-46CA-8891-43A51E61CA0A@kumari.net>
Date: Tue, 6 Mar 2012 19:43:37 -0500
X-Google-Sender-Auth: 0ivWbq6mZLMTaeJuvyb8tRx4yCw
Message-ID: <CAC4RtVC0KvX-XOwXn0wDMev5Ohu=yz53Mewu1XA=evOEH0cz5g@mail.gmail.com>
Subject: Re: [IETF] Add a link to the HTML version in i-d-announce mails ?
From: Barry Leiba <barryleiba@computer.org>
To: Warren Kumari <warren@kumari.net>
Content-Type: text/plain; charset=ISO-8859-1
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Mar 2012 00:43:38 -0000

> Yup, you are not the only one -- this annoyed me sufficiently that I finally gave
> in and wrote a Chrome extension to do this for me.
> Basically it watches the address bard and looks for www.ietf.org/id/<foo> and,
> depending on the setting in the options page, will redirect to the Tools or Datatracker.

Inspired by that, I wrote a completely trivial (one-line) Greasemonkey
script this afternoon, to do it for Firefox.  It's so short that I'll
just paste it below.  Works nicely.

Barry

--------------------------------------------------
// ==UserScript==
// @name           IETF draft html
// @namespace      ...whatever...
// @description    Redirect txt drafts to html
// @include        http://www.ietf.org/id/*
// @include        https://www.ietf.org/id/*
// ==/UserScript==

(function () {
    window.location = new
String(window.location).replace("www.ietf.org/id",
"tools.ietf.org/html").replace(".txt", "");
})();
--------------------------------------------------

From barryleiba.mailing.lists@gmail.com  Tue Mar  6 16:53:42 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 604B421F85EE for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 16:53:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.985
X-Spam-Level: 
X-Spam-Status: No, score=-102.985 tagged_above=-999 required=5 tests=[AWL=-0.008, 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 hkJAJr7-QOGg for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 16:53:41 -0800 (PST)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by ietfa.amsl.com (Postfix) with ESMTP id 60B8E21F85EC for <ietf@ietf.org>; Tue,  6 Mar 2012 16:53:41 -0800 (PST)
Received: by yenm5 with SMTP id m5so2946541yen.31 for <ietf@ietf.org>; Tue, 06 Mar 2012 16:53:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=Uq5qIG/vDLtcozYhZ20Kps9wiodVRofy4UqcrJSlCZ8=; b=e3PX98yMAIO6/DmzDlREfSQt5KCjy+FvGCbF8kpXXPzlO8JhjH0xrCUaxIJA2n/V9E 2MmfCXo0aM/RvaIvuYV8wUCnf9Vr38/rWvIERQsD4j/JebYwyTyI+h3Qmy3r+kQsO8S1 /ZdknC/F3KU70FUpF2+ZGLuPTHM9hL4qPJqq37Txmd4cy2V7b11Ov0iWO/FnnSCDtSXs tyou03tRs5dKoUkqoracrhBSqnXHB0XhD5jFYTRs4rLhKUVskfrtu/US+iJhdIcwZ0Lj 5GqEXQqWvDOFb/gisIJIGPYSBRlDf0yoz8D5R1eG9eF8epOYjZFBLK3s0gxp6DAkSQIb dpvQ==
MIME-Version: 1.0
Received: by 10.236.186.1 with SMTP id v1mr266574yhm.4.1331081620945; Tue, 06 Mar 2012 16:53:40 -0800 (PST)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.147.106.16 with HTTP; Tue, 6 Mar 2012 16:53:40 -0800 (PST)
In-Reply-To: <p06240607cb7c5510122d@loud.pensive.org>
References: <20120301184750.21152.93044.idtracker@ietfa.amsl.com> <61623076-6684-46d9-94bc-eefb2b1de6b9@email.android.com> <4F568D7D.8070502@stpeter.im> <1633774.E10J87jy7A@scott-latitude-e6320> <4F569014.1030208@stpeter.im> <p06240606cb7c4ab0a3af@loud.pensive.org> <4F569E7E.8030307@stpeter.im> <p06240607cb7c5510122d@loud.pensive.org>
Date: Tue, 6 Mar 2012 19:53:40 -0500
X-Google-Sender-Auth: cYsSV6lnloAiqvq0RYMeuMeFDos
Message-ID: <CAC4RtVC=EMrbZCujKEQW_JrMcKDHdad=nSg1=3thRkPtkvVA4w@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-appsawg-xdash-03.txt> (Deprecating Use of the "X-" Prefix in Application Protocols) to Best Current Practice
From: Barry Leiba <barryleiba@computer.org>
To: Randall Gellens <randy@qualcomm.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: Mark Nottingham <mnot@mnot.net>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Mar 2012 00:53:42 -0000

> it would be a very broken implementation, but not something
> that harmed the Internet or even anyone else whose applications worked
> properly. =A0At most it would harm its own user, who I assume would quick=
ly
> dump it.

I don't think harm to the Internet is the bar for MUST.  If your
implementation would generally be considered broken if you did X, then
I think that rates a MUST NOT X.  It's often a bit of judgment whether
to use MUST NOT or SHOULD NOT, and we have some latitude in making
that judgment.  I agree with PSA and MNot that this case should be
MUST NOT.

Barry

From randy@qualcomm.com  Tue Mar  6 17:02:38 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 7879B21E801F for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 17:02:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.264
X-Spam-Level: 
X-Spam-Status: No, score=-106.264 tagged_above=-999 required=5 tests=[AWL=0.335, 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 3EydOo5aaYjN for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 17:02:37 -0800 (PST)
Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) by ietfa.amsl.com (Postfix) with ESMTP id C0D8521E8011 for <ietf@ietf.org>; Tue,  6 Mar 2012 17:02:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=randy@qualcomm.com; q=dns/txt; s=qcdkim; t=1331082157; x=1362618157; h=message-id:in-reply-to:references:x-mailer:date:to:from: subject:cc:mime-version:content-type:x-random-sig-tag: x-originating-ip; z=Message-ID:=20<p06240609cb7c63686edd@loud.pensive.org> |In-Reply-To:=20<CAC4RtVC=3DEMrbZCujKEQW_JrMcKDHdad=3DnSg 1=3D3thRkPtkvVA4w@mail.gmail.com>|References:=20<20120301 184750.21152.93044.idtracker@ietfa.amsl.com>=0D=0A=20<616 23076-6684-46d9-94bc-eefb2b1de6b9@email.android.com>=0D =0A=20<4F568D7D.8070502@stpeter.im>=0D=0A=20<1633774.E10J 87jy7A@scott-latitude-e6320>=0D=0A=20<4F569014.1030208@st peter.im>=0D=0A=20<p06240606cb7c4ab0a3af@loud.pensive.org >=0D=0A=20<4F569E7E.8030307@stpeter.im>=0D=0A=20<p0624060 7cb7c5510122d@loud.pensive.org>=0D=0A=20<CAC4RtVC=3DEMrbZ CujKEQW_JrMcKDHdad=3DnSg1=3D3thRkPtkvVA4w@mail.gmail.com> |X-Mailer:=20Eudora=20for=20Mac=20OS=20X|Date:=20Tue,=206 =20Mar=202012=2017:02:34=20-0800|To:=20Barry=20Leiba=20<b arryleiba@computer.org>|From:=20Randall=20Gellens=20<rand y@qualcomm.com>|Subject:=20Re:=20Last=20Call:=20<draft-ie tf-appsawg-xdash-03.txt>=20(Deprecating=0D=0A=20Use=20of =20=20the=20"X-"=20Prefix=20in=20Application=20Protocols) =20to=20Best=20Current=0D=0A=20Practice|CC:=20Peter=20Sai nt-Andre=20<stpeter@stpeter.im>,=20Mark=20Nottingham=20<m not@mnot.net>,=0D=0A=09<ietf@ietf.org>|MIME-Version:=201. 0|Content-Type:=20text/plain=3B=20charset=3D"us-ascii"=3B =20format=3Dflowed|X-Random-Sig-Tag:=201.0b28 |X-Originating-IP:=20[172.30.39.5]; bh=fH8khCgPmDv7X3syGDkvB8qkQ9Im8moofZHFxONtdVg=; b=cnpXpgYRU5254m8DtXge++8vg7IsMFiqbsZIp5/YaOzaNchj15q1zTKw bVFYk3N7QpmF75bVNlkfi1l5/iFEi9dLAbPMmEvnUjnKSLl+1hzNUSscy VsILux+gn/XSV7j5C8gwlGqmKtT1h5qbw3CAtFoQCskyL5qB7LhJ6FO9Y Q=;
X-IronPort-AV: E=McAfee;i="5400,1158,6641"; a="167677199"
Received: from ironmsg03-l.qualcomm.com ([172.30.48.18]) by wolverine02.qualcomm.com with ESMTP; 06 Mar 2012 17:02:37 -0800
X-IronPort-AV: E=Sophos;i="4.73,540,1325491200"; d="scan'208";a="189445177"
Received: from nasanexhc08.na.qualcomm.com ([172.30.39.7]) by Ironmsg03-L.qualcomm.com with ESMTP/TLS/AES128-SHA; 06 Mar 2012 17:02:37 -0800
Received: from loud.pensive.org (172.30.39.5) by qcmail1.qualcomm.com (172.30.39.7) with Microsoft SMTP Server (TLS) id 14.1.339.1; Tue, 6 Mar 2012 17:02:36 -0800
Message-ID: <p06240609cb7c63686edd@loud.pensive.org>
In-Reply-To: <CAC4RtVC=EMrbZCujKEQW_JrMcKDHdad=nSg1=3thRkPtkvVA4w@mail.gmail.com>
References: <20120301184750.21152.93044.idtracker@ietfa.amsl.com> <61623076-6684-46d9-94bc-eefb2b1de6b9@email.android.com> <4F568D7D.8070502@stpeter.im> <1633774.E10J87jy7A@scott-latitude-e6320> <4F569014.1030208@stpeter.im> <p06240606cb7c4ab0a3af@loud.pensive.org> <4F569E7E.8030307@stpeter.im> <p06240607cb7c5510122d@loud.pensive.org> <CAC4RtVC=EMrbZCujKEQW_JrMcKDHdad=nSg1=3thRkPtkvVA4w@mail.gmail.com>
X-Mailer: Eudora for Mac OS X
Date: Tue, 6 Mar 2012 17:02:34 -0800
To: Barry Leiba <barryleiba@computer.org>
From: Randall Gellens <randy@qualcomm.com>
Subject: Re: Last Call: <draft-ietf-appsawg-xdash-03.txt> (Deprecating Use of  the "X-" Prefix in Application Protocols) to Best Current Practice
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Random-Sig-Tag: 1.0b28
X-Originating-IP: [172.30.39.5]
Cc: Mark Nottingham <mnot@mnot.net>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Mar 2012 01:02:38 -0000

At 7:53 PM -0500 3/6/12, Barry Leiba wrote:

>   > it would be a very broken implementation, but not something
>>  that harmed the Internet or even anyone else whose applications worked
>>  properly.  At most it would harm its own user, who I assume would quickly
>>  dump it.
>
>  I don't think harm to the Internet is the bar for MUST.  If your
>  implementation would generally be considered broken if you did X, then
>  I think that rates a MUST NOT X.  It's often a bit of judgment whether
>  to use MUST NOT or SHOULD NOT, and we have some latitude in making
>  that judgment.  I agree with PSA and MNot that this case should be
>  MUST NOT.

Yeah, harm to the Internet is overblown, sorry.  But still, if a 
violation doesn't harm anyone else, then I don't think a MUST NOT is 
justified.  My reading of 2119 is the basis for this:

    Imperatives of the type defined in this memo must be used with care
    and sparingly.  In particular, they MUST only be used where it is
    actually required for interoperation or to limit behavior which has
    potential for causing harm (e.g., limiting retransmisssions)  For
    example, they must not be used to try to impose a particular method
    on implementors where the method is not required for
    interoperability.

-- 
Randall Gellens
Opinions are personal;    facts are suspect;    I speak for myself only
-------------- Randomly selected tag: ---------------
He knows nothing, and he thinks he knows everything. That points
clearly to a political career.
     -- George Bernard Shaw

From warren@kumari.net  Tue Mar  6 17:03:21 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 D872221E8028 for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 17:03:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.485
X-Spam-Level: 
X-Spam-Status: No, score=-106.485 tagged_above=-999 required=5 tests=[AWL=0.114, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id e7UyyD746SYY for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 17:03:21 -0800 (PST)
Received: from vimes.kumari.net (vimes.kumari.net [198.186.192.250]) by ietfa.amsl.com (Postfix) with ESMTP id EB93B21E8011 for <ietf@ietf.org>; Tue,  6 Mar 2012 17:03:20 -0800 (PST)
Received: from [192.168.0.12] (unknown [64.13.52.115]) by vimes.kumari.net (Postfix) with ESMTPSA id 64CE11B4120E; Tue,  6 Mar 2012 20:03:17 -0500 (EST)
Subject: Re: [IETF] Add a link to the HTML version in i-d-announce mails ?
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=windows-1252
From: Warren Kumari <warren@kumari.net>
In-Reply-To: <CAC4RtVC0KvX-XOwXn0wDMev5Ohu=yz53Mewu1XA=evOEH0cz5g@mail.gmail.com>
Date: Tue, 6 Mar 2012 20:03:26 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <F7B36D04-E53C-4DAE-AD78-5B87B3AE3500@kumari.net>
References: <CAErhfrxPe=KSKB7fVHLankkk5XRQ87oarg17kXqNB0o0jGD4hw@mail.gmail.com> <3DEB2E7A-CED3-46CA-8891-43A51E61CA0A@kumari.net> <CAC4RtVC0KvX-XOwXn0wDMev5Ohu=yz53Mewu1XA=evOEH0cz5g@mail.gmail.com>
To: Barry Leiba <barryleiba@computer.org>
X-Mailer: Apple Mail (2.1084)
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Mar 2012 01:03:22 -0000

On Mar 6, 2012, at 7:43 PM, Barry Leiba wrote:

>> Yup, you are not the only one -- this annoyed me sufficiently that I =
finally gave
>> in and wrote a Chrome extension to do this for me.
>> Basically it watches the address bard and looks for =
www.ietf.org/id/<foo> and,
>> depending on the setting in the options page, will redirect to the =
Tools or Datatracker.
>=20
> Inspired by that, I wrote a completely trivial (one-line) Greasemonkey
> script this afternoon, to do it for Firefox.  It's so short that I'll
> just paste it below.  Works nicely.

Oooh, very cool=85.

W


>=20
> Barry
>=20
> --------------------------------------------------
> // =3D=3DUserScript=3D=3D
> // @name           IETF draft html
> // @namespace      ...whatever...
> // @description    Redirect txt drafts to html
> // @include        http://www.ietf.org/id/*
> // @include        https://www.ietf.org/id/*
> // =3D=3D/UserScript=3D=3D
>=20
> (function () {
>    window.location =3D new
> String(window.location).replace("www.ietf.org/id",
> "tools.ietf.org/html").replace(".txt", "");
> })();
> --------------------------------------------------
>=20

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






From mnot@mnot.net  Tue Mar  6 18:02:29 2012
Return-Path: <mnot@mnot.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3458221F8587 for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 18:02:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.872
X-Spam-Level: 
X-Spam-Status: No, score=-104.872 tagged_above=-999 required=5 tests=[AWL=-2.273, 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 AMPIFuYG609Q for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 18:02:28 -0800 (PST)
Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) by ietfa.amsl.com (Postfix) with ESMTP id 5A0EE21F851B for <ietf@ietf.org>; Tue,  6 Mar 2012 18:02:28 -0800 (PST)
Received: from mnot-mini.mnot.net (unknown [118.209.12.241]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 44E85509B4; Tue,  6 Mar 2012 21:02:19 -0500 (EST)
Subject: Re: Last Call: <draft-ietf-appsawg-xdash-03.txt> (Deprecating Use of the "X-" Prefix in Application Protocols) to Best Current Practice
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=us-ascii
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <4F569E7E.8030307@stpeter.im>
Date: Wed, 7 Mar 2012 13:02:17 +1100
Content-Transfer-Encoding: quoted-printable
Message-Id: <81440926-31E4-4BDA-BE66-443196709952@mnot.net>
References: <20120301184750.21152.93044.idtracker@ietfa.amsl.com> <61623076-6684-46d9-94bc-eefb2b1de6b9@email.android.com> <4F568D7D.8070502@stpeter.im> <1633774.E10J87jy7A@scott-latitude-e6320> <4F569014.1030208@stpeter.im> <p06240606cb7c4ab0a3af@loud.pensive.org> <4F569E7E.8030307@stpeter.im>
To: Peter Saint-Andre <stpeter@stpeter.im>
X-Mailer: Apple Mail (2.1257)
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, 07 Mar 2012 02:02:29 -0000

On 07/03/2012, at 10:32 AM, Peter Saint-Andre wrote:

> On 3/6/12 4:19 PM, Randall Gellens wrote:
>> At 3:30 PM -0700 3/6/12, Peter Saint-Andre wrote:
>>=20
>>> In my working copy I've changed that paragraph to:
>>>=20
>>>    Implementations of application protocols MUST NOT programatically
>>>    discriminate between "standard" and "non-standard" parameters =
based
>>>    solely on the names of such parameters (i.e., based solely on
>>>    whether the name begins with 'x-' or a similar string of =
characters).
>>=20
>> I like this wording, especially because it more clearly gets at the
>> heart of the document, which is to not discriminate based only on the
>> name prefix.
>>=20
>> One question, though: should this be "SHOULD NOT" rather than "MUST
>> NOT"?   The interoperability doesn't depend on implementations
>> refraining from doing so, rather, we consider it more problematic to =
do
>> so than not, so we are making a strong recommendation to not to so.=20=

>> Hence, "SHOULD NOT".
>=20
> Hi Randall,
>=20
> My co-author Mark Nottingham feels even more strongly about this issue
> than I do, so I will let him comment.


To me, the target of that language is software that generically treats =
protocol elements beginning with "x-" in a fundamentally different way, =
without knowledge of its semantics. That is broken, causes real harm, =
and I have seen it deployed.=20

Regards,

--
Mark Nottingham   http://www.mnot.net/




From randy@qualcomm.com  Tue Mar  6 18:38:06 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 7BFCF21E8047 for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 18:38:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.301
X-Spam-Level: 
X-Spam-Status: No, score=-106.301 tagged_above=-999 required=5 tests=[AWL=0.298, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TC1excJgOs18 for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 18:38:05 -0800 (PST)
Received: from wolverine01.qualcomm.com (wolverine01.qualcomm.com [199.106.114.254]) by ietfa.amsl.com (Postfix) with ESMTP id 9456F21E8049 for <ietf@ietf.org>; Tue,  6 Mar 2012 18:38:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=randy@qualcomm.com; q=dns/txt; s=qcdkim; t=1331087883; x=1362623883; h=message-id:in-reply-to:references:x-mailer:date:to:from: subject:cc:mime-version:content-type:x-random-sig-tag: x-originating-ip; z=Message-ID:=20<p0624060bcb7c780944ae@loud.pensive.org> |In-Reply-To:=20<81440926-31E4-4BDA-BE66-443196709952@mno t.net>|References:=20<20120301184750.21152.93044.idtracke r@ietfa.amsl.com>=0D=0A=20<61623076-6684-46d9-94bc-eefb2b 1de6b9@email.android.com>=0D=0A=20<4F568D7D.8070502@stpet er.im>=0D=0A=20<1633774.E10J87jy7A@scott-latitude-e6320> =0D=0A=20<4F569014.1030208@stpeter.im>=0D=0A=20<p06240606 cb7c4ab0a3af@loud.pensive.org>=0D=0A=20<4F569E7E.8030307@ stpeter.im>=0D=0A=20<81440926-31E4-4BDA-BE66-443196709952 @mnot.net>|X-Mailer:=20Eudora=20for=20Mac=20OS=20X|Date: =20Tue,=206=20Mar=202012=2018:34:28=20-0800|To:=20Mark=20 Nottingham=20<mnot@mnot.net>,=20Peter=20Saint-Andre=20<st peter@stpeter.im>|From:=20Randall=20Gellens=20<randy@qual comm.com>|Subject:=20Re:=20Last=20Call:=20<draft-ietf-app sawg-xdash-03.txt>=20(Deprecating=0D=0A=20Use=20of=20the =20"X-"=20Prefix=20in=20Application=20Protocols)=20to=20B est=20Current=0D=0A=20Practice|CC:=20Scott=20Kitterman=20 <scott@kitterman.com>,=20<ietf@ietf.org>|MIME-Version:=20 1.0|Content-Type:=20text/plain=3B=20charset=3D"us-ascii" =3B=20format=3Dflowed|X-Random-Sig-Tag:=201.0b28 |X-Originating-IP:=20[172.30.39.5]; bh=nZyahrFVi4ahGV+cM4H0Mv/N4uecFIXldoCvvul1ZsQ=; b=ugyLAzuw9/78gL5M79xJAPGF6ZgslW7f9SRqzLjmx7eEtlFqDaM4NXrJ Be9fgdXOd1ZMJl7VOP6gEWWjC3yAVM//5/HaQqgb36hvtpJDlWOl+CjZb DMZEUcUMmv1dDCpxTw+8ac+kTC6JVPOMds1JpfgFeUdIoIyy7H8O+4BjF 8=;
X-IronPort-AV: E=McAfee;i="5400,1158,6641"; a="170108474"
Received: from ironmsg02-r.qualcomm.com ([172.30.46.16]) by wolverine01.qualcomm.com with ESMTP; 06 Mar 2012 18:37:48 -0800
X-IronPort-AV: E=Sophos;i="4.73,543,1325491200"; d="scan'208";a="157810240"
Received: from nasanexhc08.na.qualcomm.com ([172.30.39.7]) by ironmsg02-R.qualcomm.com with ESMTP/TLS/AES128-SHA; 06 Mar 2012 18:37:48 -0800
Received: from loud.pensive.org (172.30.39.5) by qcmail1.qualcomm.com (172.30.39.7) with Microsoft SMTP Server (TLS) id 14.1.339.1; Tue, 6 Mar 2012 18:37:47 -0800
Message-ID: <p0624060bcb7c780944ae@loud.pensive.org>
In-Reply-To: <81440926-31E4-4BDA-BE66-443196709952@mnot.net>
References: <20120301184750.21152.93044.idtracker@ietfa.amsl.com> <61623076-6684-46d9-94bc-eefb2b1de6b9@email.android.com> <4F568D7D.8070502@stpeter.im> <1633774.E10J87jy7A@scott-latitude-e6320> <4F569014.1030208@stpeter.im> <p06240606cb7c4ab0a3af@loud.pensive.org> <4F569E7E.8030307@stpeter.im> <81440926-31E4-4BDA-BE66-443196709952@mnot.net>
X-Mailer: Eudora for Mac OS X
Date: Tue, 6 Mar 2012 18:34:28 -0800
To: Mark Nottingham <mnot@mnot.net>, Peter Saint-Andre <stpeter@stpeter.im>
From: Randall Gellens <randy@qualcomm.com>
Subject: Re: Last Call: <draft-ietf-appsawg-xdash-03.txt> (Deprecating Use of the "X-" Prefix in Application Protocols) to Best Current Practice
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Random-Sig-Tag: 1.0b28
X-Originating-IP: [172.30.39.5]
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Mar 2012 02:38:06 -0000

At 1:02 PM +1100 3/7/12, Mark Nottingham wrote:

>  On 07/03/2012, at 10:32 AM, Peter Saint-Andre wrote:
>
>>  On 3/6/12 4:19 PM, Randall Gellens wrote:
>>>  At 3:30 PM -0700 3/6/12, Peter Saint-Andre wrote:
>>>
>>>>  In my working copy I've changed that paragraph to:
>>>>
>>>>     Implementations of application protocols MUST NOT programatically
>>>>     discriminate between "standard" and "non-standard" parameters based
>>>>     solely on the names of such parameters (i.e., based solely on
>>>>     whether the name begins with 'x-' or a similar string of characters).
>>>
>>>  I like this wording, especially because it more clearly gets at the
>>>  heart of the document, which is to not discriminate based only on the
>>>  name prefix.
>>>
>>>  One question, though: should this be "SHOULD NOT" rather than "MUST
>>>  NOT"?   The interoperability doesn't depend on implementations
>>>  refraining from doing so, rather, we consider it more problematic to do
>>>  so than not, so we are making a strong recommendation to not to so.
>>>  Hence, "SHOULD NOT".
>>
>>  Hi Randall,
>>
>>  My co-author Mark Nottingham feels even more strongly about this issue
>>  than I do, so I will let him comment.
>
>  To me, the target of that language is software that generically 
> treats protocol elements beginning with "x-" in a fundamentally 
> different way, without knowledge of its semantics. That is broken, 
> causes real harm, and I have seen it deployed.

Hi Mark,

The point of the draft is to say that it's a bad idea to do this or 
to try and have a system where this is expected.  The draft does a 
good job at saying this.  I just think a "MUST NOT" isn't warranted 
here; I think a "SHOULD NOT" is justified per RFC 2119.  I think a 
"SHOULD NOT" makes the point: Doing it makes bad things happen.

-- 
Randall Gellens
Opinions are personal;    facts are suspect;    I speak for myself only
-------------- Randomly selected tag: ---------------
I personally think we developed language because of our
deep need to complain.                    --Lily Tomlin

From marka@isc.org  Tue Mar  6 18:43:13 2012
Return-Path: <marka@isc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2C89221E8013 for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 18:43:13 -0800 (PST)
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.014,  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 VKSoRK79RR2P for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 18:43:12 -0800 (PST)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [IPv6:2001:500:60::65]) by ietfa.amsl.com (Postfix) with ESMTP id 8D44121F856A for <ietf@ietf.org>; Tue,  6 Mar 2012 18:43:12 -0800 (PST)
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mail.isc.org", Issuer "RapidSSL CA" (not verified)) by mx.ams1.isc.org (Postfix) with ESMTPS id A6F1C5F9887; Wed,  7 Mar 2012 02:42:56 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (unknown [IPv6:2001:470:1f00:820:17d:90bc:5fc8:434]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by bikeshed.isc.org (Postfix) with ESMTPSA id 6533E216C31; Wed,  7 Mar 2012 02:42:54 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (Postfix) with ESMTP id EF0151E2080D; Wed,  7 Mar 2012 13:42:47 +1100 (EST)
To: "John R. Levine" <johnl@iecc.com>
From: Mark Andrews <marka@isc.org>
References: <20120306044628.87718.qmail@joyce.lan> <77075C8C-04ED-48A2-B501-B2296BCFC8C6@frobbit.se> <01OCRTKK8TSO00ZUIL@mauve.mrochek.com> <alpine.BSF.2.00.1203060950080.10148@joyce.lan> <alpine.LSU.2.00.1203061658110.2756@hermes-2.csi.cam.ac.uk> <alpine.BSF.2.00.1203061203020.14450@joyce.lan> <20120306220911.8B52C1E1DE9F@drugs.dv.isc.org> <alpine.BSF.2.00.1203061711470.25059@joyce.lan>
Subject: Re: provisioning software, was DNS RRTYPEs, the difficulty with
In-reply-to: Your message of "06 Mar 2012 17:15:46 CDT." <alpine.BSF.2.00.1203061711470.25059@joyce.lan>
Date: Wed, 07 Mar 2012 13:42:47 +1100
Message-Id: <20120307024247.EF0151E2080D@drugs.dv.isc.org>
Cc: "ietf@ietf.org Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Mar 2012 02:43:13 -0000

In message <alpine.BSF.2.00.1203061711470.25059@joyce.lan>, "John R. Levine" wr
ites:
> >> They're not implementation specific, but they're also not required to
> >> interoperate, as the wire format queries and responses are.
> >
> > They are a interchange standard as per RFC 1034.
> 
> Yes, we all know that.  But as I presume you also know, there are plenty 
> of DNS servers that store the zone info in other ways, ranging from djbdns 
> mutant syntax text files to various databases.
> 
> Whatever the server uses, the provisioning system better match.

BIND stores zones in other ways as well.  You just have to be able
accept them and produce them or else you don't have a comforming
implementation.

> > The standard format of master files allows them to be exchanged between
> > hosts (via FTP, mail, or some other mechanism); this facility is useful
> > when an organization wants a domain, but doesn't want to support a name
> > server.  The organization can maintain the master files locally using a
> > text editor, transfer them to a foreign host which runs a name server,
> > and then arrange with the system administrator of the name server to get
> > the files loaded.
> 
> That is one implementation.  But it's far from the only one.
> 
> My system has a web front end that lets my users edit groups of their 
> djbdns RRs, which it stores in a database.  Once an hour, a perl script 
> goes through the database, regenerates the mutant text files, and stuffs 
> them into the name servers.  It's not fabulous, but it gets the job done.

Nobody says you can't have propriatry methods of data entry.

However we do have standard presentation/entry formats defined and a good
front end will accept those as well.

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

From johnl@iecc.com  Tue Mar  6 18:50:00 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 8578E21E8019 for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 18:50:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.389
X-Spam-Level: 
X-Spam-Status: No, score=-102.389 tagged_above=-999 required=5 tests=[AWL=0.211, 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 FKx2hkM74Gc1 for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 18:49:59 -0800 (PST)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id B982521E8013 for <ietf@ietf.org>; Tue,  6 Mar 2012 18:49:59 -0800 (PST)
Received: (qmail 86994 invoked from network); 7 Mar 2012 02:49:57 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:in-reply-to:references:mime-version:content-type:vbr-info:user-agent:cleverness; s=153d1.4f56ccd5.k1203; bh=0BgH4QaCfGbT0mldKXv84iezEr9txGAyB8OnNSVcDVw=; b=Ync/AuSIgxhBsQySCzDv9XgnaWUy1XszbORSERCBIgFNNjnG24qlyAOsfowxLL4/cQRNraQ6eoZuV/XRu9VMW8tLxr8raHso0k3KH2tuw09KrLeVvG1hOwZtRGC0Ve8papIkLc35Lr+qvq4ycojXBKDjydJ2rz0HBfWC/l7TLI4=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Received: (ofmipd 127.0.0.1); 7 Mar 2012 02:49:35 -0000
Date: 6 Mar 2012 21:49:56 -0500
Message-ID: <alpine.BSF.2.00.1203062148410.34594@joyce.lan>
From: "John R. Levine" <johnl@iecc.com>
To: "ietf@ietf.org Discussion" <ietf@ietf.org>
Subject: Re: provisioning software, was DNS RRTYPEs, the difficulty with
In-Reply-To: <20120307024247.EF0151E2080D@drugs.dv.isc.org>
References: <20120306044628.87718.qmail@joyce.lan> <77075C8C-04ED-48A2-B501-B2296BCFC8C6@frobbit.se> <01OCRTKK8TSO00ZUIL@mauve.mrochek.com> <alpine.BSF.2.00.1203060950080.10148@joyce.lan> <alpine.LSU.2.00.1203061658110.2756@hermes-2.csi.cam.ac.uk> <alpine.BSF.2.00.1203061203020.14450@joyce.lan> <20120306220911.8B52C1E1DE9F@drugs.dv.isc.org> <alpine.BSF.2.00.1203061711470.25059@joyce.lan> <20120307024247.EF0151E2080D@drugs.dv.isc.org>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
Cleverness: None detected
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Mar 2012 02:50:00 -0000

> However we do have standard presentation/entry formats defined and a good
> front end will accept those as well.

Sigh.  Now we're back to "people who don't do it my way are wrong", so I 
guess we're done.

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

From mnot@mnot.net  Tue Mar  6 18:50:55 2012
Return-Path: <mnot@mnot.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 422C121E8047 for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 18:50:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.853
X-Spam-Level: 
X-Spam-Status: No, score=-104.853 tagged_above=-999 required=5 tests=[AWL=-2.254, 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 1+XSyD6OeDls for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 18:50:54 -0800 (PST)
Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) by ietfa.amsl.com (Postfix) with ESMTP id 5396521E8013 for <ietf@ietf.org>; Tue,  6 Mar 2012 18:50:54 -0800 (PST)
Received: from mnot-mini.mnot.net (unknown [118.209.12.241]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id F073E509B4; Tue,  6 Mar 2012 21:50:46 -0500 (EST)
Subject: Re: Last Call: <draft-ietf-appsawg-xdash-03.txt> (Deprecating Use of the "X-" Prefix in Application Protocols) to Best Current Practice
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=us-ascii
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <p0624060bcb7c780944ae@loud.pensive.org>
Date: Wed, 7 Mar 2012 13:50:43 +1100
Content-Transfer-Encoding: quoted-printable
Message-Id: <C7B1AFB5-C81B-4A8C-BFE9-963F70C7A049@mnot.net>
References: <20120301184750.21152.93044.idtracker@ietfa.amsl.com> <61623076-6684-46d9-94bc-eefb2b1de6b9@email.android.com> <4F568D7D.8070502@stpeter.im> <1633774.E10J87jy7A@scott-latitude-e6320> <4F569014.1030208@stpeter.im> <p06240606cb7c4ab0a3af@loud.pensive.org> <4F569E7E.8030307@stpeter.im> <81440926-31E4-4BDA-BE66-443196709952@mnot.net> <p0624060bcb7c780944ae@loud.pensive.org>
To: Randall Gellens <randy@qualcomm.com>
X-Mailer: Apple Mail (2.1257)
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, 07 Mar 2012 02:50:55 -0000

On 07/03/2012, at 1:34 PM, Randall Gellens wrote:

> At 1:02 PM +1100 3/7/12, Mark Nottingham wrote:
>=20
>> On 07/03/2012, at 10:32 AM, Peter Saint-Andre wrote:
>>=20
>>> On 3/6/12 4:19 PM, Randall Gellens wrote:
>>>> At 3:30 PM -0700 3/6/12, Peter Saint-Andre wrote:
>>>>=20
>>>>> In my working copy I've changed that paragraph to:
>>>>>=20
>>>>>    Implementations of application protocols MUST NOT =
programatically
>>>>>    discriminate between "standard" and "non-standard" parameters =
based
>>>>>    solely on the names of such parameters (i.e., based solely on
>>>>>    whether the name begins with 'x-' or a similar string of =
characters).
>>>>=20
>>>> I like this wording, especially because it more clearly gets at the
>>>> heart of the document, which is to not discriminate based only on =
the
>>>> name prefix.
>>>>=20
>>>> One question, though: should this be "SHOULD NOT" rather than "MUST
>>>> NOT"?   The interoperability doesn't depend on implementations
>>>> refraining from doing so, rather, we consider it more problematic =
to do
>>>> so than not, so we are making a strong recommendation to not to so.
>>>> Hence, "SHOULD NOT".
>>>=20
>>> Hi Randall,
>>>=20
>>> My co-author Mark Nottingham feels even more strongly about this =
issue
>>> than I do, so I will let him comment.
>>=20
>> To me, the target of that language is software that generically =
treats protocol elements beginning with "x-" in a fundamentally =
different way, without knowledge of its semantics. That is broken, =
causes real harm, and I have seen it deployed.
>=20
> Hi Mark,
>=20
> The point of the draft is to say that it's a bad idea to do this or to =
try and have a system where this is expected.  The draft does a good job =
at saying this.  I just think a "MUST NOT" isn't warranted here; I think =
a "SHOULD NOT" is justified per RFC 2119.  I think a "SHOULD NOT" makes =
the point: Doing it makes bad things happen.


I have to disagree; MUST NOT *is* justified. Deploying systems like this =
causes real interoperability problems, which is in scope for a MUST NOT.



--
Mark Nottingham   http://www.mnot.net/




From randy@psg.com  Tue Mar  6 18:52:52 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 1509121E8048 for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 18:52:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.502
X-Spam-Level: 
X-Spam-Status: No, score=-2.502 tagged_above=-999 required=5 tests=[AWL=0.097,  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 uhAKS9CbxYYz for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 18:52:51 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id AF07421E8013 for <ietf@ietf.org>; Tue,  6 Mar 2012 18:52:51 -0800 (PST)
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 1S56zd-000M4O-GX; Wed, 07 Mar 2012 02:52:45 +0000
Date: Wed, 07 Mar 2012 11:52:44 +0900
Message-ID: <m24nu1gm0z.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Mark Nottingham <mnot@mnot.net>
Subject: Re: Last Call: <draft-ietf-appsawg-xdash-03.txt> (Deprecating Use of	the "X-" Prefix in Application Protocols) to Best Current Practice
In-Reply-To: <81440926-31E4-4BDA-BE66-443196709952@mnot.net>
References: <20120301184750.21152.93044.idtracker@ietfa.amsl.com> <61623076-6684-46d9-94bc-eefb2b1de6b9@email.android.com> <4F568D7D.8070502@stpeter.im> <1633774.E10J87jy7A@scott-latitude-e6320> <4F569014.1030208@stpeter.im> <p06240606cb7c4ab0a3af@loud.pensive.org> <4F569E7E.8030307@stpeter.im> <81440926-31E4-4BDA-BE66-443196709952@mnot.net>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
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, 07 Mar 2012 02:52:52 -0000

> To me, the target of that language is software that generically treats
> protocol elements beginning with "x-" in a fundamentally different
> way, without knowledge of its semantics. That is broken, causes real
> harm, and I have seen it deployed.

clue bat please?  is there any general semantic to X-?

randy

From marka@isc.org  Tue Mar  6 18:59:00 2012
Return-Path: <marka@isc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 222EC21E8048 for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 18:59:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.587
X-Spam-Level: 
X-Spam-Status: No, score=-2.587 tagged_above=-999 required=5 tests=[AWL=0.012,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yeEiCXji+4xE for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 18:58:59 -0800 (PST)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [IPv6:2001:500:60::65]) by ietfa.amsl.com (Postfix) with ESMTP id 919A621E8013 for <ietf@ietf.org>; Tue,  6 Mar 2012 18:58:59 -0800 (PST)
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mail.isc.org", Issuer "RapidSSL CA" (not verified)) by mx.ams1.isc.org (Postfix) with ESMTPS id C68245F9887; Wed,  7 Mar 2012 02:58:46 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (unknown [IPv6:2001:470:1f00:820:17d:90bc:5fc8:434]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by bikeshed.isc.org (Postfix) with ESMTPSA id 19B7C216C31; Wed,  7 Mar 2012 02:58:45 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (Postfix) with ESMTP id EC52B1E208D0; Wed,  7 Mar 2012 13:58:39 +1100 (EST)
To: "John Levine" <johnl@iecc.com>
From: Mark Andrews <marka@isc.org>
References: <20120307000814.29422.qmail@joyce.lan>
Subject: Re: provisioning software, was DNS RRTYPEs, the difficulty with
In-reply-to: Your message of "07 Mar 2012 00:08:14 -0000." <20120307000814.29422.qmail@joyce.lan>
Date: Wed, 07 Mar 2012 13:58:39 +1100
Message-Id: <20120307025839.EC52B1E208D0@drugs.dv.isc.org>
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, 07 Mar 2012 02:59:00 -0000

In message <20120307000814.29422.qmail@joyce.lan>, "John Levine" writes:
> >> > Last month I ran into a guy on the dmarc list who complained that his
> >> > server returns NOTIMP in response to queries for SPF records ("because
> >> > it doesn't implement them") and clients were doing odd things.  But
> >> > it's been a long time since I've run into anyone else like that, so I
> >> > agree, it's not an issue.
> 
> In case it wasn't clear, this is an authoritative server.

A authoritative server should be returning NOERROR / NXDOMAIN not
NOTIMP provided the zone loads otherwise SERVFAIL if the load fails
for any type other than those in the reserved meta type range.  If
the data isn't in the zone and the name is in use NOERROR is the
response you send.  If the name isn't in use NXDOMAIN is the response
you send.  Failure to load all of the zone is supposed to stop any
of it being served according to RFC 1035.

If you want to be a nameserver developer you don't stop counting
at 1035.  The meta type range was initially reserved in RFC 2929
(Sep 2000).

> >A RFC 1035 recursive server should be able to handle SPF.  It's
> >just a opaque data blob to it with a name, type, class and ttl
> >attributes.
> 
> Agreed.  Other than a few dusty Suns still running obsolete BIND 4.x,
> I don't know of any DNS caches that have problems with arbitrary RRs.
> 
> R's,
> John
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org

From johnl@iecc.com  Tue Mar  6 19:46:47 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 C516121E8052 for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 19:46:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.394
X-Spam-Level: 
X-Spam-Status: No, score=-102.394 tagged_above=-999 required=5 tests=[AWL=0.206, 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 vmKUcNX8SqUT for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 19:46:47 -0800 (PST)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id EA2DB21E8068 for <ietf@ietf.org>; Tue,  6 Mar 2012 19:46:46 -0800 (PST)
Received: (qmail 95898 invoked from network); 7 Mar 2012 03:46:45 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:vbr-info:user-agent:cleverness; s=1768f.4f56da25.k1203; bh=Fkg/N1EBrTX9vyaBT4BAC7xbNezKw4fupVqooiq3198=; b=elBVwMhh1xIPI0Ho7FaCrU1rw4E9QVIxhskBSX50/YT78QshGhziubUvWXFJnHWFyfmLGLiRs6lRWKV6S9BOIuFFQyam4lxQBQ0rUvFc+Is7d2kpDab9MUZcoRIovxswQIi/csq3Zekn7mqJrlII+Js0wXa1CUJ+CQRCP64v+qU=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Received: (ofmipd 127.0.0.1); 7 Mar 2012 03:46:23 -0000
Date: 6 Mar 2012 22:46:45 -0500
Message-ID: <alpine.BSF.2.00.1203062245080.36850@joyce.lan>
From: "John R. Levine" <johnl@iecc.com>
To: "Mark Andrews" <marka@isc.org>
Subject: Re: provisioning software, was DNS RRTYPEs, the difficulty with
In-Reply-To: <20120307025839.EC52B1E208D0@drugs.dv.isc.org>
References: <20120307000814.29422.qmail@joyce.lan> <20120307025839.EC52B1E208D0@drugs.dv.isc.org>
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: Wed, 07 Mar 2012 03:46:47 -0000

>>>>> Last month I ran into a guy on the dmarc list who complained that his
>>>>> server returns NOTIMP in response to queries for SPF records ("because
>>>>> it doesn't implement them") and clients were doing odd things.  But
>>>>> it's been a long time since I've run into anyone else like that, so I
>>>>> agree, it's not an issue.
>>
>> In case it wasn't clear, this is an authoritative server.
>
> A authoritative server should be returning NOERROR / NXDOMAIN not
> NOTIMP

Yes, we all know that.  My point, which I would have thought was obvious, 
was that it's been a long time since I've run into anyone whose server was 
broken like that.  As I said, it's not an issue.

R's,
John

From mnot@mnot.net  Tue Mar  6 20:11:13 2012
Return-Path: <mnot@mnot.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5EDA321E8047 for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 20:11:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.848
X-Spam-Level: 
X-Spam-Status: No, score=-104.848 tagged_above=-999 required=5 tests=[AWL=-2.249, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id n-rGNinYOpyQ for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 20:11:13 -0800 (PST)
Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) by ietfa.amsl.com (Postfix) with ESMTP id E1A0921E8013 for <ietf@ietf.org>; Tue,  6 Mar 2012 20:11:12 -0800 (PST)
Received: from mnot-mini.mnot.net (unknown [118.209.12.241]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 7E4A6509EB; Tue,  6 Mar 2012 23:11:05 -0500 (EST)
Subject: Re: Last Call: <draft-ietf-appsawg-xdash-03.txt> (Deprecating Use of	the "X-" Prefix in Application Protocols) to Best Current Practice
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=us-ascii
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <m24nu1gm0z.wl%randy@psg.com>
Date: Wed, 7 Mar 2012 15:11:04 +1100
Content-Transfer-Encoding: quoted-printable
Message-Id: <A2C45799-D342-48EF-B5D6-5F06A70F1EA1@mnot.net>
References: <20120301184750.21152.93044.idtracker@ietfa.amsl.com> <61623076-6684-46d9-94bc-eefb2b1de6b9@email.android.com> <4F568D7D.8070502@stpeter.im> <1633774.E10J87jy7A@scott-latitude-e6320> <4F569014.1030208@stpeter.im> <p06240606cb7c4ab0a3af@loud.pensive.org> <4F569E7E.8030307@stpeter.im> <81440926-31E4-4BDA-BE66-443196709952@mnot.net> <m24nu1gm0z.wl%randy@psg.com>
To: Randy Bush <randy@psg.com>
X-Mailer: Apple Mail (2.1257)
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, 07 Mar 2012 04:11:13 -0000

On 07/03/2012, at 1:52 PM, Randy Bush wrote:

>> To me, the target of that language is software that generically =
treats
>> protocol elements beginning with "x-" in a fundamentally different
>> way, without knowledge of its semantics. That is broken, causes real
>> harm, and I have seen it deployed.
>=20
> clue bat please?  is there any general semantic to X-?


I think one of the main points of the draft is to answer that question =
with "no."

--
Mark Nottingham   http://www.mnot.net/




From marka@isc.org  Tue Mar  6 20:12:31 2012
Return-Path: <marka@isc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0D80521E8048 for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 20:12:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.587
X-Spam-Level: 
X-Spam-Status: No, score=-2.587 tagged_above=-999 required=5 tests=[AWL=0.012,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id x+ImbvTYpfaK for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 20:12:30 -0800 (PST)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) by ietfa.amsl.com (Postfix) with ESMTP id 39EE821E8013 for <ietf@ietf.org>; Tue,  6 Mar 2012 20:12:30 -0800 (PST)
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mail.isc.org", Issuer "RapidSSL CA" (not verified)) by mx.pao1.isc.org (Postfix) with ESMTPS id 886C5C941E; Wed,  7 Mar 2012 04:12:16 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (unknown [IPv6:2001:470:1f00:820:17d:90bc:5fc8:434]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by bikeshed.isc.org (Postfix) with ESMTPSA id 2FB7F216C31; Wed,  7 Mar 2012 04:12:16 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (Postfix) with ESMTP id 6E9BA1E215C4; Wed,  7 Mar 2012 15:12:13 +1100 (EST)
To: "John R. Levine" <johnl@iecc.com>
From: Mark Andrews <marka@isc.org>
References: <20120306044628.87718.qmail@joyce.lan> <77075C8C-04ED-48A2-B501-B2296BCFC8C6@frobbit.se> <01OCRTKK8TSO00ZUIL@mauve.mrochek.com> <alpine.BSF.2.00.1203060950080.10148@joyce.lan> <alpine.LSU.2.00.1203061658110.2756@hermes-2.csi.cam.ac.uk> <alpine.BSF.2.00.1203061203020.14450@joyce.lan> <20120306220911.8B52C1E1DE9F@drugs.dv.isc.org> <alpine.BSF.2.00.1203061711470.25059@joyce.lan> <20120307024247.EF0151E2080D@drugs.dv.isc.org> <alpine.BSF.2.00.1203062148410.34594@joyce.lan>
Subject: Re: provisioning software, was DNS RRTYPEs, the difficulty with
In-reply-to: Your message of "06 Mar 2012 21:49:56 CDT." <alpine.BSF.2.00.1203062148410.34594@joyce.lan>
Date: Wed, 07 Mar 2012 15:12:13 +1100
Message-Id: <20120307041213.6E9BA1E215C4@drugs.dv.isc.org>
Cc: "ietf@ietf.org Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Mar 2012 04:12:31 -0000

In message <alpine.BSF.2.00.1203062148410.34594@joyce.lan>, "John R. Levine" wr
ites:
> > However we do have standard presentation/entry formats defined and a good
> > front end will accept those as well.
> 
> Sigh.  Now we're back to "people who don't do it my way are wrong", so I 
> guess we're done.

One of point of having standard presentation formats is that they
facilitate data interchange.  I can use my tools to generate the
records and your system can just accept it.  Having to re-format
data is a pain.  If you want to do something else as well there is
no problem with that.

It's a little like credit card numbers.  Breaking them up into 4
boxes of 4 digits and having to move the focus between boxes is a
absolute pain.  These should be cut and pastable, with or without
spaces in the middle.

There are international standards for telephone numbers but every
web developer seems to think they know best.

> Regards,
> John Levine, johnl@iecc.com, Primary Perpetrator of "The Internet for Dummies
> ",
> Please consider the environment before reading this e-mail. http://jl.ly
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org

From randy@psg.com  Tue Mar  6 20:22:11 2012
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8B04021E806B for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 20:22:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.503
X-Spam-Level: 
X-Spam-Status: No, score=-2.503 tagged_above=-999 required=5 tests=[AWL=0.096,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 51wNmutpsPz6 for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 20:22:11 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 2052321E8062 for <ietf@ietf.org>; Tue,  6 Mar 2012 20:22:11 -0800 (PST)
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 1S58O9-000MGh-Aw; Wed, 07 Mar 2012 04:22:09 +0000
Date: Wed, 07 Mar 2012 13:22:08 +0900
Message-ID: <m2obs9f3bj.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Mark Andrews <marka@isc.org>
Subject: Re: provisioning software, was DNS RRTYPEs, the difficulty with
In-Reply-To: <20120307041213.6E9BA1E215C4@drugs.dv.isc.org>
References: <20120306044628.87718.qmail@joyce.lan> <77075C8C-04ED-48A2-B501-B2296BCFC8C6@frobbit.se> <01OCRTKK8TSO00ZUIL@mauve.mrochek.com> <alpine.BSF.2.00.1203060950080.10148@joyce.lan> <alpine.LSU.2.00.1203061658110.2756@hermes-2.csi.cam.ac.uk> <alpine.BSF.2.00.1203061203020.14450@joyce.lan> <20120306220911.8B52C1E1DE9F@drugs.dv.isc.org> <alpine.BSF.2.00.1203061711470.25059@joyce.lan> <20120307024247.EF0151E2080D@drugs.dv.isc.org> <alpine.BSF.2.00.1203062148410.34594@joyce.lan> <20120307041213.6E9BA1E215C4@drugs.dv.isc.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 Disgust <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Mar 2012 04:22:11 -0000

> One of point of having standard presentation formats is that they
> facilitate data interchange.

bind's zone format is not a standard, and many implementations are not
compatible with it.  get over it.

randy

From marka@isc.org  Tue Mar  6 21:04:04 2012
Return-Path: <marka@isc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5F97921E8048 for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 21:04:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.588
X-Spam-Level: 
X-Spam-Status: No, score=-2.588 tagged_above=-999 required=5 tests=[AWL=0.011,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kFrarxyuQ-Ow for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 21:04:04 -0800 (PST)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [IPv6:2001:500:60::65]) by ietfa.amsl.com (Postfix) with ESMTP id CBA9121E8013 for <ietf@ietf.org>; Tue,  6 Mar 2012 21:04:03 -0800 (PST)
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mail.isc.org", Issuer "RapidSSL CA" (not verified)) by mx.ams1.isc.org (Postfix) with ESMTPS id A72B45F9887; Wed,  7 Mar 2012 05:03:48 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (unknown [IPv6:2001:470:1f00:820:4871:3721:df34:ff58]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by bikeshed.isc.org (Postfix) with ESMTPSA id A54C5216C31; Wed,  7 Mar 2012 05:03:46 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (Postfix) with ESMTP id 6077F1E21D88; Wed,  7 Mar 2012 16:03:41 +1100 (EST)
To: Randy Bush <randy@psg.com>
From: Mark Andrews <marka@isc.org>
References: <20120306044628.87718.qmail@joyce.lan> <77075C8C-04ED-48A2-B501-B2296BCFC8C6@frobbit.se> <01OCRTKK8TSO00ZUIL@mauve.mrochek.com> <alpine.BSF.2.00.1203060950080.10148@joyce.lan> <alpine.LSU.2.00.1203061658110.2756@hermes-2.csi.cam.ac.uk> <alpine.BSF.2.00.1203061203020.14450@joyce.lan> <20120306220911.8B52C1E1DE9F@drugs.dv.isc.org> <alpine.BSF.2.00.1203061711470.25059@joyce.lan> <20120307024247.EF0151E2080D@drugs.dv.isc.org> <alpine.BSF.2.00.1203062148410.34594@joyce.lan> <20120307041213.6E9BA1E215C4@drugs.dv.isc.org> <m2obs9f3bj.wl%randy@psg.com>
Subject: Re: provisioning software, was DNS RRTYPEs, the difficulty with
In-reply-to: Your message of "Wed, 07 Mar 2012 13:22:08 +0900." <m2obs9f3bj.wl%randy@psg.com>
Date: Wed, 07 Mar 2012 16:03:40 +1100
Message-Id: <20120307050341.6077F1E21D88@drugs.dv.isc.org>
Cc: IETF Disgust <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Mar 2012 05:04:04 -0000

In message <m2obs9f3bj.wl%randy@psg.com>, Randy Bush writes:
> > One of point of having standard presentation formats is that they
> > facilitate data interchange.
> 
> bind's zone format is not a standard, and many implementations are not
> compatible with it.  get over it.

Actually it is STD 13.  Get over it.
 
> randy
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org

From mrex@sap.com  Tue Mar  6 21:39:55 2012
Return-Path: <mrex@sap.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 33D8721E8070 for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 21:39:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.049
X-Spam-Level: 
X-Spam-Status: No, score=-10.049 tagged_above=-999 required=5 tests=[AWL=0.200, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mEtHxybbR1Vm for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 21:39:54 -0800 (PST)
Received: from smtpde02.sap-ag.de (smtpde02.sap-ag.de [155.56.68.140]) by ietfa.amsl.com (Postfix) with ESMTP id ED33021E806B for <ietf@ietf.org>; Tue,  6 Mar 2012 21:39:53 -0800 (PST)
Received: from mail.sap.corp by smtpde02.sap-ag.de (26) with ESMTP id q275dmnP013966 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 7 Mar 2012 06:39:48 +0100 (MET)
From: Martin Rex <mrex@sap.com>
Message-Id: <201203070539.q275dmj8001960@fs4113.wdf.sap.corp>
Subject: Re: provisioning software, was DNS RRTYPEs, the difficulty with
To: marka@isc.org (Mark Andrews)
Date: Wed, 7 Mar 2012 06:39:48 +0100 (MET)
In-Reply-To: <20120307025839.EC52B1E208D0@drugs.dv.isc.org> from "Mark Andrews" at Mar 7, 12 01:58:39 pm
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-SAP: out
Cc: johnl@iecc.com, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: mrex@sap.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Mar 2012 05:39:55 -0000

Mark Andrews wrote:
> 
> "John Levine" writes:
> >
> > In case it wasn't clear, this is an authoritative server.

If this is about permitted RCODEs here

  http://tools.ietf.org/html/rfc1035#section-4.1.1

then an RCODE of 4 in the response looks like a perfectly valid response
for a DNS Server to a query, authoritative or not is irrelevant, and
if any client chokes on such an answer, it is likely the client that
is broken.

-Martin

From paulej@packetizer.com  Tue Mar  6 21:54:03 2012
Return-Path: <paulej@packetizer.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 76B3921F8569 for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 21:54:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.478
X-Spam-Level: 
X-Spam-Status: No, score=-2.478 tagged_above=-999 required=5 tests=[AWL=0.121,  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 WNaIotvdEESX for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 21:54:02 -0800 (PST)
Received: from dublin.packetizer.com (dublin.packetizer.com [75.101.130.125]) by ietfa.amsl.com (Postfix) with ESMTP id 2695F21F8568 for <ietf@ietf.org>; Tue,  6 Mar 2012 21:54:02 -0800 (PST)
Received: from sydney (rrcs-98-101-148-48.midsouth.biz.rr.com [98.101.148.48]) (authenticated bits=0) by dublin.packetizer.com (8.14.5/8.14.5) with ESMTP id q275s0Ru031538 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 7 Mar 2012 00:54:01 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=packetizer.com; s=dublin; t=1331099641; bh=BP1Jdn2EQFooe8DnpyDJ5vxb+ArzMnAgk4sBG2+gKEI=; h=From:To:Cc:References:In-Reply-To:Subject:Date:Message-ID: MIME-Version:Content-Type:Content-Transfer-Encoding; b=RORXeAcPGIwgiceYfKTTsRP9OvbjhlRXfBUn/IHj7lgGbVCo2LQhcNvjtcjlc3utk 4SYY96CSzbikvSTJD66FsJfCjm7pIUN1a+DBqUBQDQknNs7/XLD2pODAhBEsAkUtT6 COk9G7eJ1HPsURPOYynGRiFuQnb196BGMV5luYjM=
From: "Paul E. Jones" <paulej@packetizer.com>
To: "'Mark Nottingham'" <mnot@mnot.net>, "'Randy Bush'" <randy@psg.com>
References: <20120301184750.21152.93044.idtracker@ietfa.amsl.com>	<61623076-6684-46d9-94bc-eefb2b1de6b9@email.android.com>	<4F568D7D.8070502@stpeter.im>	<1633774.E10J87jy7A@scott-latitude-e6320>	<4F569014.1030208@stpeter.im>	<p06240606cb7c4ab0a3af@loud.pensive.org>	<4F569E7E.8030307@stpeter.im>	<81440926-31E4-4BDA-BE66-443196709952@mnot.net>	<m24nu1gm0z.wl%randy@psg.com> <A2C45799-D342-48EF-B5D6-5F06A70F1EA1@mnot.net>
In-Reply-To: <A2C45799-D342-48EF-B5D6-5F06A70F1EA1@mnot.net>
Subject: RE: Last Call: <draft-ietf-appsawg-xdash-03.txt> (Deprecating Use	of	the "X-" Prefix in Application Protocols) to Best Current Practice
Date: Wed, 7 Mar 2012 00:54:07 -0500
Message-ID: <03ed01ccfc26$b6288f50$2279adf0$@packetizer.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQJGX7VXjh2TMwwk5yOLFUO8dQDcFAExncKOAWHcU2sCH0banQFl9LMIAg9wNdABx3wsxQJeglFWAsXHvZAAxGphfJTsyzLQ
Content-Language: en-us
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, 07 Mar 2012 05:54:03 -0000

But it does clue one in immediately to the fact that the parameter is
non-standard.

Paul

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
> Mark Nottingham
> Sent: Tuesday, March 06, 2012 11:11 PM
> To: Randy Bush
> Cc: Randall Gellens; ietf@ietf.org
> Subject: Re: Last Call: <draft-ietf-appsawg-xdash-03.txt> (Deprecating Use
> of the "X-" Prefix in Application Protocols) to Best Current Practice
> 
> 
> On 07/03/2012, at 1:52 PM, Randy Bush wrote:
> 
> >> To me, the target of that language is software that generically
> >> treats protocol elements beginning with "x-" in a fundamentally
> >> different way, without knowledge of its semantics. That is broken,
> >> causes real harm, and I have seen it deployed.
> >
> > clue bat please?  is there any general semantic to X-?
> 
> 
> I think one of the main points of the draft is to answer that question
> with "no."
> 
> --
> Mark Nottingham   http://www.mnot.net/
> 
> 
> 
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From mnot@mnot.net  Tue Mar  6 21:57:13 2012
Return-Path: <mnot@mnot.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4DEAC21E8091 for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 21:57:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.83
X-Spam-Level: 
X-Spam-Status: No, score=-104.83 tagged_above=-999 required=5 tests=[AWL=-2.231, 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 WOrMMetJl9hY for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 21:57:12 -0800 (PST)
Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) by ietfa.amsl.com (Postfix) with ESMTP id 502F621E808B for <ietf@ietf.org>; Tue,  6 Mar 2012 21:57:08 -0800 (PST)
Received: from mnot-mini.mnot.net (unknown [118.209.12.241]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 79B8C50A5D; Wed,  7 Mar 2012 00:57:00 -0500 (EST)
Subject: Re: Last Call: <draft-ietf-appsawg-xdash-03.txt> (Deprecating Use	of	the "X-" Prefix in Application Protocols) to Best Current Practice
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=us-ascii
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <03ed01ccfc26$b6288f50$2279adf0$@packetizer.com>
Date: Wed, 7 Mar 2012 16:56:57 +1100
Content-Transfer-Encoding: quoted-printable
Message-Id: <DD153596-9B87-4BA2-8379-ADACF9EDD7B1@mnot.net>
References: <20120301184750.21152.93044.idtracker@ietfa.amsl.com>	<61623076-6684-46d9-94bc-eefb2b1de6b9@email.android.com>	<4F568D7D.8070502@stpeter.im>	<1633774.E10J87jy7A@scott-latitude-e6320>	<4F569014.1030208@stpeter.im>	<p06240606cb7c4ab0a3af@loud.pensive.org>	<4F569E7E.8030307@stpeter.im>	<81440926-31E4-4BDA-BE66-443196709952@mnot.net>	<m24nu1gm0z.wl%randy@psg.com> <A2C45799-D342-48EF-B5D6-5F06A70F1EA1@mnot.net> <03ed01ccfc26$b6288f50$2279adf0$@packetizer.com>
To: "Paul E. Jones" <paulej@packetizer.com>
X-Mailer: Apple Mail (2.1257)
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, 07 Mar 2012 05:57:13 -0000

Yes, but (as the draft tries to explain) putting this kind of metadata =
in a name is prone to issues, because it can change -- i.e., when a =
header (or other protocol element) becomes standard.=20


On 07/03/2012, at 4:54 PM, Paul E. Jones wrote:

> But it does clue one in immediately to the fact that the parameter is
> non-standard.
>=20
> Paul
>=20
>> -----Original Message-----
>> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf =
Of
>> Mark Nottingham
>> Sent: Tuesday, March 06, 2012 11:11 PM
>> To: Randy Bush
>> Cc: Randall Gellens; ietf@ietf.org
>> Subject: Re: Last Call: <draft-ietf-appsawg-xdash-03.txt> =
(Deprecating Use
>> of the "X-" Prefix in Application Protocols) to Best Current Practice
>>=20
>>=20
>> On 07/03/2012, at 1:52 PM, Randy Bush wrote:
>>=20
>>>> To me, the target of that language is software that generically
>>>> treats protocol elements beginning with "x-" in a fundamentally
>>>> different way, without knowledge of its semantics. That is broken,
>>>> causes real harm, and I have seen it deployed.
>>>=20
>>> clue bat please?  is there any general semantic to X-?
>>=20
>>=20
>> I think one of the main points of the draft is to answer that =
question
>> with "no."
>>=20
>> --
>> Mark Nottingham   http://www.mnot.net/
>>=20
>>=20
>>=20
>> _______________________________________________
>> Ietf mailing list
>> Ietf@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf
>=20

--
Mark Nottingham   http://www.mnot.net/




From marka@isc.org  Tue Mar  6 22:04:59 2012
Return-Path: <marka@isc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 12B0821F8516 for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 22:04:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.589
X-Spam-Level: 
X-Spam-Status: No, score=-2.589 tagged_above=-999 required=5 tests=[AWL=0.010,  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 HteesyRF8JT2 for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 22:04:57 -0800 (PST)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [IPv6:2001:500:60::65]) by ietfa.amsl.com (Postfix) with ESMTP id A6E6221F8510 for <ietf@ietf.org>; Tue,  6 Mar 2012 22:04:57 -0800 (PST)
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mail.isc.org", Issuer "RapidSSL CA" (not verified)) by mx.ams1.isc.org (Postfix) with ESMTPS id B10845F9865; Wed,  7 Mar 2012 06:04:39 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (unknown [IPv6:2001:470:1f00:820:4871:3721:df34:ff58]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by bikeshed.isc.org (Postfix) with ESMTPSA id CD6C1216C31; Wed,  7 Mar 2012 06:04:35 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (Postfix) with ESMTP id 5B70E1E22182; Wed,  7 Mar 2012 17:04:30 +1100 (EST)
To: mrex@sap.com
From: Mark Andrews <marka@isc.org>
References: <201203070539.q275dmj8001960@fs4113.wdf.sap.corp>
Subject: Re: provisioning software, was DNS RRTYPEs, the difficulty with
In-reply-to: Your message of "Wed, 07 Mar 2012 06:39:48 BST." <201203070539.q275dmj8001960@fs4113.wdf.sap.corp>
Date: Wed, 07 Mar 2012 17:04:30 +1100
Message-Id: <20120307060430.5B70E1E22182@drugs.dv.isc.org>
Cc: johnl@iecc.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, 07 Mar 2012 06:04:59 -0000

In message <201203070539.q275dmj8001960@fs4113.wdf.sap.corp>, Martin Rex writes
:
> Mark Andrews wrote:
> > 
> > "John Levine" writes:
> > >
> > > In case it wasn't clear, this is an authoritative server.
> 
> If this is about permitted RCODEs here
> 
>   http://tools.ietf.org/html/rfc1035#section-4.1.1
> 
> then an RCODE of 4 in the response looks like a perfectly valid response
> for a DNS Server to a query, authoritative or not is irrelevant, and
> if any client chokes on such an answer, it is likely the client that
> is broken.

No, its about what should be generated.  NOTIMP != NOERROR no data.
 
> -Martin
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org

From paulej@packetizer.com  Tue Mar  6 22:19:39 2012
Return-Path: <paulej@packetizer.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0632B21E8086 for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 22:19:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.489
X-Spam-Level: 
X-Spam-Status: No, score=-2.489 tagged_above=-999 required=5 tests=[AWL=0.110,  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 spkTw0shpOEY for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 22:19:37 -0800 (PST)
Received: from dublin.packetizer.com (dublin.packetizer.com [75.101.130.125]) by ietfa.amsl.com (Postfix) with ESMTP id 3632721E807D for <ietf@ietf.org>; Tue,  6 Mar 2012 22:19:37 -0800 (PST)
Received: from sydney (rrcs-98-101-148-48.midsouth.biz.rr.com [98.101.148.48]) (authenticated bits=0) by dublin.packetizer.com (8.14.5/8.14.5) with ESMTP id q276JZY7032563 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 7 Mar 2012 01:19:36 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=packetizer.com; s=dublin; t=1331101176; bh=mxNUEnfmyq0sF1DLATKS+T+UA8NslL6vY45WB0jo0Ig=; h=From:To:Cc:References:In-Reply-To:Subject:Date:Message-ID: MIME-Version:Content-Type:Content-Transfer-Encoding; b=pfC2EvApa3Q7C/aoPX8qZIPr6qdcaL64HtkFLjfCdKWJp8aYsVIHu7ZkrOI2ReY6l nHhU9HQbBXUgy0j74qIpwUtDOz26kl1/5E/2wjPaULT+DXw7+P2AP3f22BeWI5uNG6 kTV/DDovJ15WgrlaYbecmHHmJ5dI+o7Zk+NbC1II=
From: "Paul E. Jones" <paulej@packetizer.com>
To: "'Mark Nottingham'" <mnot@mnot.net>
References: <20120301184750.21152.93044.idtracker@ietfa.amsl.com>	<61623076-6684-46d9-94bc-eefb2b1de6b9@email.android.com>	<4F568D7D.8070502@stpeter.im>	<1633774.E10J87jy7A@scott-latitude-e6320>	<4F569014.1030208@stpeter.im>	<p06240606cb7c4ab0a3af@loud.pensive.org>	<4F569E7E.8030307@stpeter.im>	<81440926-31E4-4BDA-BE66-443196709952@mnot.net>	<m24nu1gm0z.wl%randy@psg.com> <A2C45799-D342-48EF-B5D6-5F06A70F1EA1@mnot.net> <03ed01ccfc26$b6288f50$2279adf0$@packetizer.com> <DD153596-9B87-4BA2-8379-ADACF9EDD7B1@mnot.net>
In-Reply-To: <DD153596-9B87-4BA2-8379-ADACF9EDD7B1@mnot.net>
Subject: RE: Last Call: <draft-ietf-appsawg-xdash-03.txt> (Deprecating Use	of	the "X-" Prefix in Application Protocols) to Best Current Practice
Date: Wed, 7 Mar 2012 01:19:42 -0500
Message-ID: <03f201ccfc2a$49324900$db96db00$@packetizer.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQJGX7VXjh2TMwwk5yOLFUO8dQDcFAExncKOAWHcU2sCH0banQFl9LMIAg9wNdABx3wsxQJeglFWAsXHvZAAxGphfAJ0BSfuAf31ee6UyUGxcA==
Content-Language: en-us
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, 07 Mar 2012 06:19:39 -0000

I suppose one could argue that X- should never be on the Public Internet,
anyway.  But they are.  If we remove X-, then what will happen is developers
will use names that don't have X-.  Will that make things better?  No.  I'd
argue it will make it worse.

Non-standard extensions do present issues, that's no in question.  However,
killing X- will only mean other values will be used.  At least X- can be
ignored.

I'm not going to throw up a roadblock to the draft.  Call for the end of X-
if you want, but I know it will not stop introduction of non-standard values
in protocols, so a problem will remain.

One way to help this is to get standards through the IETF faster.  Some take
forever.

Paul

> -----Original Message-----
> From: Mark Nottingham [mailto:mnot@mnot.net]
> Sent: Wednesday, March 07, 2012 12:57 AM
> To: Paul E. Jones
> Cc: 'Randy Bush'; 'Randall Gellens'; ietf@ietf.org
> Subject: Re: Last Call: <draft-ietf-appsawg-xdash-03.txt> (Deprecating Use
> of the "X-" Prefix in Application Protocols) to Best Current Practice
> 
> Yes, but (as the draft tries to explain) putting this kind of metadata in
> a name is prone to issues, because it can change -- i.e., when a header
> (or other protocol element) becomes standard.
> 
> 
> On 07/03/2012, at 4:54 PM, Paul E. Jones wrote:
> 
> > But it does clue one in immediately to the fact that the parameter is
> > non-standard.
> >
> > Paul
> >
> >> -----Original Message-----
> >> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf
> >> Of Mark Nottingham
> >> Sent: Tuesday, March 06, 2012 11:11 PM
> >> To: Randy Bush
> >> Cc: Randall Gellens; ietf@ietf.org
> >> Subject: Re: Last Call: <draft-ietf-appsawg-xdash-03.txt>
> >> (Deprecating Use of the "X-" Prefix in Application Protocols) to Best
> >> Current Practice
> >>
> >>
> >> On 07/03/2012, at 1:52 PM, Randy Bush wrote:
> >>
> >>>> To me, the target of that language is software that generically
> >>>> treats protocol elements beginning with "x-" in a fundamentally
> >>>> different way, without knowledge of its semantics. That is broken,
> >>>> causes real harm, and I have seen it deployed.
> >>>
> >>> clue bat please?  is there any general semantic to X-?
> >>
> >>
> >> I think one of the main points of the draft is to answer that
> >> question with "no."
> >>
> >> --
> >> Mark Nottingham   http://www.mnot.net/
> >>
> >>
> >>
> >> _______________________________________________
> >> Ietf mailing list
> >> Ietf@ietf.org
> >> https://www.ietf.org/mailman/listinfo/ietf
> >
> 
> --
> Mark Nottingham   http://www.mnot.net/
> 
> 



From randy@qualcomm.com  Tue Mar  6 22:26:40 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 0384D21F855D for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 22:26:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.331
X-Spam-Level: 
X-Spam-Status: No, score=-106.331 tagged_above=-999 required=5 tests=[AWL=0.268, 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 DqKY66u4Sryr for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 22:26:39 -0800 (PST)
Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) by ietfa.amsl.com (Postfix) with ESMTP id 6D7BA21F855A for <ietf@ietf.org>; Tue,  6 Mar 2012 22:26:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=randy@qualcomm.com; q=dns/txt; s=qcdkim; t=1331101599; x=1362637599; h=message-id:in-reply-to:references:x-mailer:date:to:from: subject:cc:mime-version:content-type:x-random-sig-tag: x-originating-ip; z=Message-ID:=20<p06240610cb7caf4c386e@loud.pensive.org> |In-Reply-To:=20<03f201ccfc2a$49324900$db96db00$@packetiz er.com>|References:=20<20120301184750.21152.93044.idtrack er@ietfa.amsl.com>=0D=0A=20<61623076-6684-46d9-94bc-eefb2 b1de6b9@email.android.com>=0D=0A=20<4F568D7D.8070502@stpe ter.im>=0D=0A=20<1633774.E10J87jy7A@scott-latitude-e6320> =0D=0A=20<4F569014.1030208@stpeter.im>=0D=0A=20<p06240606 cb7c4ab0a3af@loud.pensive.org>=0D=0A=20<4F569E7E.8030307@ stpeter.im>=0D=0A=20<81440926-31E4-4BDA-BE66-443196709952 @mnot.net>=0D=0A=20<m24nu1gm0z.wl%randy@psg.com>=0D=0A=20 <A2C45799-D342-48EF-B5D6-5F06A70F1EA1@mnot.net>=0D=0A=20< 03ed01ccfc26$b6288f50$2279adf0$@packetizer.com>=0D=0A=20< DD153596-9B87-4BA2-8379-ADACF9EDD7B1@mnot.net>=0D=0A=20<0 3f201ccfc2a$49324900$db96db00$@packetizer.com>|X-Mailer: =20Eudora=20for=20Mac=20OS=20X|Date:=20Tue,=206=20Mar=202 012=2022:26:20=20-0800|To:=20"Paul=20E.=20Jones"=20<paule j@packetizer.com>,=20'Mark=20Nottingham'=20<mnot@mnot.net >|From:=20Randall=20Gellens=20<randy@qualcomm.com> |Subject:=20RE:=20Last=20Call:=20<draft-ietf-appsawg-xdas h-03.txt>=20(Deprecating=0D=0A=20Use=09of=09the=20"X-"=20 Prefix=20in=20Application=20Protocols)=20to=20Best=20Curr ent=0D=0A=20Practice|CC:=20'Randy=20Bush'=20<randy@psg.co m>,=20<ietf@ietf.org>|MIME-Version:=201.0|Content-Type: =20text/plain=3B=20charset=3D"us-ascii"=3B=20format=3Dflo wed|X-Random-Sig-Tag:=201.0b28|X-Originating-IP:=20[172.3 0.48.1]; bh=ISq+Q2BVTq8jyLMQIpgLPBFhlaM+yktGgxUgxiCU/LU=; b=N4hRszqtW4+q19h1H5YN0CUp8sjA7vemUC96xVx3cZA9HrBLa3mMOExO CXeHG8L7cIjZZUhfXKmx2P0Jwn8FbEz7WWb65DyVuM/qNTLXpSE32E/y8 noxH1D8XF6ssCN88PSE6bniT9s9ZpBqAxX9weJcko7/W4Cz5yEv2Qzh+d s=;
X-IronPort-AV: E=McAfee;i="5400,1158,6641"; a="167850032"
Received: from ironmsg03-l.qualcomm.com ([172.30.48.18]) by wolverine02.qualcomm.com with ESMTP; 06 Mar 2012 22:26:38 -0800
X-IronPort-AV: E=Sophos;i="4.73,543,1325491200"; d="scan'208";a="189542469"
Received: from nasanexhc05.na.qualcomm.com ([172.30.48.2]) by Ironmsg03-L.qualcomm.com with ESMTP/TLS/AES128-SHA; 06 Mar 2012 22:26:38 -0800
Received: from loud.pensive.org (172.30.48.1) by qcmail1.qualcomm.com (172.30.48.2) with Microsoft SMTP Server (TLS) id 14.1.339.1; Tue, 6 Mar 2012 22:26:37 -0800
Message-ID: <p06240610cb7caf4c386e@loud.pensive.org>
In-Reply-To: <03f201ccfc2a$49324900$db96db00$@packetizer.com>
References: <20120301184750.21152.93044.idtracker@ietfa.amsl.com> <61623076-6684-46d9-94bc-eefb2b1de6b9@email.android.com> <4F568D7D.8070502@stpeter.im> <1633774.E10J87jy7A@scott-latitude-e6320> <4F569014.1030208@stpeter.im> <p06240606cb7c4ab0a3af@loud.pensive.org> <4F569E7E.8030307@stpeter.im> <81440926-31E4-4BDA-BE66-443196709952@mnot.net> <m24nu1gm0z.wl%randy@psg.com> <A2C45799-D342-48EF-B5D6-5F06A70F1EA1@mnot.net> <03ed01ccfc26$b6288f50$2279adf0$@packetizer.com> <DD153596-9B87-4BA2-8379-ADACF9EDD7B1@mnot.net> <03f201ccfc2a$49324900$db96db00$@packetizer.com>
X-Mailer: Eudora for Mac OS X
Date: Tue, 6 Mar 2012 22:26:20 -0800
To: "Paul E. Jones" <paulej@packetizer.com>, 'Mark Nottingham' <mnot@mnot.net>
From: Randall Gellens <randy@qualcomm.com>
Subject: RE: Last Call: <draft-ietf-appsawg-xdash-03.txt> (Deprecating Use	of	the "X-" Prefix in Application Protocols) to Best Current Practice
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]
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, 07 Mar 2012 06:26:40 -0000

At 1:19 AM -0500 3/7/12, Paul E. Jones wrote:

>  I suppose one could argue that X- should never be on the Public Internet,
>  anyway.  But they are.  If we remove X-, then what will happen is developers
>  will use names that don't have X-.  Will that make things better?  No.  I'd
>  argue it will make it worse.
>
>  Non-standard extensions do present issues, that's no in question.  However,
>  killing X- will only mean other values will be used.  At least X- can be
>  ignored.

I was quite skeptical for a while, but came around to seeing the case 
that trying to segregate non-standard parameters ends up creating 
more problems than it solves.

You're right that people will use names without an 'x' and the draft 
encourages this.  So, we'll end up with (as I think the draft 
suggests), situations where 'priority' is the old, non-standard name, 
and 'urgency' is the new, standardized name, instead of 'x-priority' 
and 'priority'.  But the fact is that names which start out as 
non-standard hacks end up being de facto standards.  That's no better.

-- 
Randall Gellens
Opinions are personal;    facts are suspect;    I speak for myself only
-------------- Randomly selected tag: ---------------
We adore chaos because we love to produce order.
                                  --M. C. Escher

From paf@frobbit.se  Tue Mar  6 23:13:10 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 35EE521E8035 for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 23:13:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[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 yDqQasvtNESS for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 23:13:09 -0800 (PST)
Received: from srv01.frobbit.se (srv01.frobbit.se [IPv6:2a02:80:3ffe::39]) by ietfa.amsl.com (Postfix) with ESMTP id 8207521E8028 for <ietf@ietf.org>; Tue,  6 Mar 2012 23:13:09 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by srv01.frobbit.se (Postfix) with ESMTP id 940CF133F2F22; Wed,  7 Mar 2012 08:13:06 +0100 (CET)
X-Virus-Scanned: amavisd-new at frobbit.se
Received: from srv01.frobbit.se ([127.0.0.1]) by localhost (srv01.frobbit.se [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KQQyHnayZqh4; Wed,  7 Mar 2012 08:13:06 +0100 (CET)
Received: from [192.165.72.14] (unknown [192.165.72.14]) (Authenticated sender: paf01) by srv01.frobbit.se (Postfix) with ESMTP id 5731A133F2F16; Wed,  7 Mar 2012 08:13:06 +0100 (CET)
Subject: Re: provisioning software, was DNS RRTYPEs, the difficulty with
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=us-ascii
From: =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
In-Reply-To: <alpine.BSF.2.00.1203062148410.34594@joyce.lan>
Date: Wed, 7 Mar 2012 08:13:06 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <D468354F-BE26-41D4-9F75-EA10C5189B73@frobbit.se>
References: <20120306044628.87718.qmail@joyce.lan> <77075C8C-04ED-48A2-B501-B2296BCFC8C6@frobbit.se> <01OCRTKK8TSO00ZUIL@mauve.mrochek.com> <alpine.BSF.2.00.1203060950080.10148@joyce.lan> <alpine.LSU.2.00.1203061658110.2756@hermes-2.csi.cam.ac.uk> <alpine.BSF.2.00.1203061203020.14450@joyce.lan> <20120306220911.8B52C1E1DE9F@drugs.dv.isc.org> <alpine.BSF.2.00.1203061711470.25059@joyce.lan> <20120307024247.EF0151E2080D@drugs.dv.isc.org> <alpine.BSF.2.00.1203062148410.34594@joyce.lan>
To: John R. Levine <johnl@iecc.com>
X-Mailer: Apple Mail (2.1257)
Cc: "ietf@ietf.org Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Mar 2012 07:13:10 -0000

On 7 mar 2012, at 03:49, John R. Levine wrote:

>> However we do have standard presentation/entry formats defined and a =
good
>> front end will accept those as well.
>=20
> Sigh.  Now we're back to "people who don't do it my way are wrong", so =
I guess we're done.

I disagree.

"People who don't accept the standardized zone format are wrong" is =
Mark's statement.

What you say is "as people do not support the standardized zone format =
as input, what do we do".

   Patrik


From marka@isc.org  Tue Mar  6 23:54:35 2012
Return-Path: <marka@isc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BADC021E806E for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 23:54:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.44
X-Spam-Level: 
X-Spam-Status: No, score=-2.44 tagged_above=-999 required=5 tests=[AWL=-0.141,  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 2f5nW7VD--qO for <ietf@ietfa.amsl.com>; Tue,  6 Mar 2012 23:54:35 -0800 (PST)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) by ietfa.amsl.com (Postfix) with ESMTP id E9F8A21E8019 for <ietf@ietf.org>; Tue,  6 Mar 2012 23:54:34 -0800 (PST)
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mail.isc.org", Issuer "RapidSSL CA" (not verified)) by mx.pao1.isc.org (Postfix) with ESMTPS id 0E6AEC941E; Wed,  7 Mar 2012 07:54:18 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (unknown [IPv6:2001:470:1f00:820:4871:3721:df34:ff58]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by bikeshed.isc.org (Postfix) with ESMTPSA id AC322216C31; Wed,  7 Mar 2012 07:54:17 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (Postfix) with ESMTP id 6E63A1E23E05; Wed,  7 Mar 2012 18:54:14 +1100 (EST)
To: =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
From: Mark Andrews <marka@isc.org>
References: <20120306044628.87718.qmail@joyce.lan> <77075C8C-04ED-48A2-B501-B2296BCFC8C6@frobbit.se> <01OCRTKK8TSO00ZUIL@mauve.mrochek.com> <alpine.BSF.2.00.1203060950080.10148@joyce.lan> <alpine.LSU.2.00.1203061658110.2756@hermes-2.csi.cam.ac.uk> <alpine.BSF.2.00.1203061203020.14450@joyce.lan> <20120306220911.8B52C1E1DE9F@drugs.dv.isc.org> <alpine.BSF.2.00.1203061711470.25059@joyce.lan> <20120307024247.EF0151E2080D@drugs.dv.isc.org> <alpine.BSF.2.00.1203062148410.34594@joyce.lan> <D468354F-BE26-41D4-9F75-EA10C5189B73@frobbit.se>
Subject: Re: provisioning software, was DNS RRTYPEs, the difficulty with
In-reply-to: Your message of "Wed, 07 Mar 2012 08:13:06 BST." <D468354F-BE26-41D4-9F75-EA10C5189B73@frobbit.se>
Date: Wed, 07 Mar 2012 18:54:14 +1100
Message-Id: <20120307075414.6E63A1E23E05@drugs.dv.isc.org>
Cc: "John R. Levine" <johnl@iecc.com>, "ietf@ietf.org Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Mar 2012 07:54:35 -0000

In message <D468354F-BE26-41D4-9F75-EA10C5189B73@frobbit.se>, =?iso-8859-1?Q?Pa
trik_F=E4ltstr=F6m?= writes:
> 
> On 7 mar 2012, at 03:49, John R. Levine wrote:
> 
> >> However we do have standard presentation/entry formats defined and a good
> >> front end will accept those as well.
> > 
> > Sigh.  Now we're back to "people who don't do it my way are wrong", so I gu
> ess we're done.
> 
> I disagree.
> 
> "People who don't accept the standardized zone format are wrong" is Mark's st
> atement.
>
> What you say is "as people do not support the standardized zone format as inp
> ut, what do we do".
> 
>    Patrik

The point of RFC 3597 was to provide a STANDARD text representation
that could handle any DNS record format.  It isn't pretty but as
long as you accept it and emit it you are future proof.  Its a
lowest common format.

	    A 1.2.3.4 == TYPE1 \# 4 01020304

Most provisioning systems really don't care about most of the data
they are throwing about.  It may as well be a opaque blob.

Pretty is for the next revision of the provisioning software.  Look
at what data you have in raw format and use that to decide what you
need to handle in a prettier manner in the next revision.  You don't
even need to to change the database tables.  It's just front end
presentation that needs to be changed.

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

From ned+ietf@mauve.mrochek.com  Wed Mar  7 00:57:45 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 5677121F876E for <ietf@ietfa.amsl.com>; Wed,  7 Mar 2012 00:57:45 -0800 (PST)
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.014,  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 AJG9J9XKcQU0 for <ietf@ietfa.amsl.com>; Wed,  7 Mar 2012 00:57:44 -0800 (PST)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id 5FBD621F8768 for <ietf@ietf.org>; Wed,  7 Mar 2012 00:57:44 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OCTDEZCXY8007LP1@mauve.mrochek.com> for ietf@ietf.org; Wed, 7 Mar 2012 00:57:37 -0800 (PST)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OCPMUVDUMO00ZUIL@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Wed, 7 Mar 2012 00:57:26 -0800 (PST)
From: ned+ietf@mauve.mrochek.com
Message-id: <01OCTDEUL9G200ZUIL@mauve.mrochek.com>
Date: Wed, 07 Mar 2012 00:42:47 -0800 (PST)
Subject: Re: provisioning software, was DNS RRTYPEs, the difficulty with
In-reply-to: "Your message dated Tue, 06 Mar 2012 17:01:57 +0100" <4F5634F5.5090909@tana.it>
MIME-version: 1.0
Content-type: TEXT/PLAIN
References: <20120305170938.57919.qmail@joyce.lan> <4F550DA1.8060304@tana.it> <01OCRP6SYT8Q00ZUIL@mauve.mrochek.com> <4F5634F5.5090909@tana.it>
To: Alessandro Vesely <vesely@tana.it>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mrochek.com; s=mauve; t=1331110664; i=@mrochek.com; bh=PgzHUKWouEjsdm9r5PcKMhiHocfuMy6e6TdBAi7x3DM=;  h=From:Cc:Message-id:Date:Subject:In-reply-to:MIME-version: Content-type:References:To; b=RwtWSLJhn3plyEBW7oBO4OJp9TxZ0/XDJQU6LRD+Skj618mV8lE3sIa1VNRkb9dkE 3gaYWC9Ibj+bWCu01nen642EZI4Cq+/oQLm4iqEMQhSOGBRx54TEwrbQ9SUBJMrAXK ZarP+YF+94Q0K30jAzPIvcIiU8QjaW3YmCP8WWAA=
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, 07 Mar 2012 08:57:45 -0000

> > There are some false equivalences floating around here. I don't
> > think anyone is suggesting that having provisioning systems or even
> > DNS servers themselves check for syntax errors in the contents of
> > complex records like DKIM, SPF, DMARC, or whatever is necessarily a
> > bad idea. (Whether or not it will actually happen is another
> > matter; I'm dubious.)
> >
> > Rather, the issue is with requiring it to happen in order to deploy
> > a new RRTYPE of this sort, which is the result you get if the DNS
> > server returns some series of tokens instead of the original text
> > string. That's the sort of thing that forces people to upgrade, or
> > search around for a script to do the conversion (which won't even
> > occur to some), and that's an extra burden we don't need to
> > impose.

> It would still be possible to work around the need for a plugin, e.g.
> by depending on some wizard web site, as in John's thought experiment.

> For the rest of us, the possibility to install a plugin that takes
> care of all the nitty-gritty details, instead of having to wait for
> the release and distribution of the next version of BIND, can make the
> difference between deploying a new RR type right away and
> procrastinating endlessly.

You're still not separating the two cases. Again, an *optional* plugin to check
syntax of a record but not produce any sort of tokenized result is fine, a
plugin that's *mandatory* to deploy is going to be almost as much of an
impediment to deployment as requiring an upgrade. Code is code, and people
don't install new code willy-nilly.

> The issue is to upgrade once rather than on each new RR type.

Exactly. That's why mandatory plugins are a bad idea.

> Correct, but when you publish a complex record you are calling forth
> that complexity.  I don't see much difference if the bug is at mines
> or at the remote site, since their effects are comparable.

They most certainly are not. A bug in my client only affects me, a bug
in the server can easily kill the entire zone. And even if separation
techniques are employed, if the plugin fails the best you're going to be
able to do is server out a domain with missing entries.

				Ned

From daedulus@btconnect.com  Wed Mar  7 02:08:18 2012
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6458521F86FF for <ietf@ietfa.amsl.com>; Wed,  7 Mar 2012 02:08:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.21
X-Spam-Level: 
X-Spam-Status: No, score=-2.21 tagged_above=-999 required=5 tests=[AWL=0.389,  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 UBGg6jI41T0s for <ietf@ietfa.amsl.com>; Wed,  7 Mar 2012 02:08:17 -0800 (PST)
Received: from mail.btconnect.com (c2beaomr06.btconnect.com [213.123.26.184]) by ietfa.amsl.com (Postfix) with ESMTP id 4175021F86E1 for <ietf@ietf.org>; Wed,  7 Mar 2012 02:08:16 -0800 (PST)
Received: from host86-163-139-217.range86-163.btcentralplus.com (HELO pc6) ([86.163.139.217]) by c2beaomr06.btconnect.com with SMTP id GTM21628; Wed, 07 Mar 2012 10:08:12 +0000 (GMT)
Message-ID: <00ca01ccfc41$bc24bda0$4001a8c0@gateway.2wire.net>
From: "t.petch" <daedulus@btconnect.com>
To: "Paul E. Jones" <paulej@packetizer.com>
References: <20120301184750.21152.93044.idtracker@ietfa.amsl.com>	<61623076-6684-46d9-94bc-eefb2b1de6b9@email.android.com>	<4F568D7D.8070502@stpeter.im>	<1633774.E10J87jy7A@scott-latitude-e6320>	<4F569014.1030208@stpeter.im>	<p06240606cb7c4ab0a3af@loud.pensive.org>	<4F569E7E.8030307@stpeter.im>	<81440926-31E4-4BDA-BE66-443196709952@mnot.net>	<m24nu1gm0z.wl%randy@psg.com><A2C45799-D342-48EF-B5D6-5F06A70F1EA1@mnot.net><03ed01ccfc26$b6288f50$2279adf0$@packetizer.com><DD153596-9B87-4BA2-8379-ADACF9EDD7B1@mnot.net> <03f201ccfc2a$49324900$db96db00$@packetizer.com>
Subject: Re: Last Call: <draft-ietf-appsawg-xdash-03.txt> (DeprecatingUse	of	the "X-" Prefix in Application Protocols) to BestCurrent Practice
Date: Wed, 7 Mar 2012 10:07:30 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Mirapoint-IP-Reputation: reputation=Fair-1, source=Queried, refid=tid=0001.0A0B0301.4F57338C.0015, actions=TAG
X-Junkmail-Premium-Raw: score=7/50, refid=2.7.2:2012.3.6.211239:17:7.944, ip=86.163.139.217, rules=__HAS_MSGID, __OUTLOOK_MSGID_1, __SANE_MSGID, __TO_MALFORMED_2, __BOUNCE_CHALLENGE_SUBJ, __BOUNCE_NDR_SUBJ_EXEMPT, __MIME_VERSION, __CT, CT_TP_8859_1, __CT_TEXT_PLAIN, __CTE, __HAS_X_PRIORITY, __HAS_MSMAIL_PRI, __HAS_X_MAILER, USER_AGENT_OE, __OUTLOOK_MUA_1, __USER_AGENT_MS_GENERIC, __ANY_URI, __URI_NO_WWW, __URI_NO_PATH, BODY_SIZE_700_799, BODYTEXTP_SIZE_3000_LESS, __MIME_TEXT_ONLY, RDNS_GENERIC_POOLED, HTML_00_01, HTML_00_10, BODY_SIZE_5000_LESS, RDNS_SUSP_GENERIC, __OUTLOOK_MUA, BODY_SIZE_1000_LESS, RDNS_SUSP, BODY_SIZE_2000_LESS, BODY_SIZE_7000_LESS
X-Junkmail-Status: score=10/50, host=c2beaomr06.btconnect.com
X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A0B0207.4F57338C.01A3,ss=1,re=0.000,fgs=0, ip=0.0.0.0, so=2011-07-25 19:15:43, dmn=2011-05-27 18:58:46, mode=multiengine
X-Junkmail-IWF: false
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, 07 Mar 2012 10:08:18 -0000

----- Original Message -----
From: "Paul E. Jones" <paulej@packetizer.com>
To: "'Mark Nottingham'" <mnot@mnot.net>
Cc: "'Randall Gellens'" <randy@qualcomm.com>; <ietf@ietf.org>
Sent: Wednesday, March 07, 2012 7:19 AM
Subject: RE: Last Call: <draft-ietf-appsawg-xdash-03.txt> (DeprecatingUse of the
"X-" Prefix in Application Protocols) to BestCurrent Practice


> I suppose one could argue that X- should never be on the Public Internet,
> anyway.  But they are.

Yup, your e-mail reached me with 14 different lines starting X- in the header,
none of which were added by my ISP.  Whether their presence makes any difference
to what I see and I get, I have no idea.

I suspect that like DNS TXT records, they are with use for eternity.

Tom Petch
<snip>


From vesely@tana.it  Wed Mar  7 04:56:57 2012
Return-Path: <vesely@tana.it>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6981821F87A3 for <ietf@ietfa.amsl.com>; Wed,  7 Mar 2012 04:56:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.656
X-Spam-Level: 
X-Spam-Status: No, score=-4.656 tagged_above=-999 required=5 tests=[AWL=0.063,  BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Jl+LTrQgJMC8 for <ietf@ietfa.amsl.com>; Wed,  7 Mar 2012 04:56:56 -0800 (PST)
Received: from wmail.tana.it (mail.tana.it [62.94.243.226]) by ietfa.amsl.com (Postfix) with ESMTP id 707FB21F87A0 for <ietf@ietf.org>; Wed,  7 Mar 2012 04:56:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=test; t=1331125015; bh=OUHDu+J6fpPCdP8hWeQkMdJ5JRpXiGdrj8BIQWkVTeI=; l=2156; h=Message-ID:Date:From:MIME-Version:To:References:In-Reply-To: Content-Transfer-Encoding; b=ARPMnWlB/lrFGoQiCaSdIKwnKuF3QfJ9HvA8bbpIrhYaC2AC+JSd67J4H6OTfgUnj mwBVyf2iIBcSmwZMrieYmCJhYw40hZj3BitKctAp39RwAB3HgFxjSQnwKj/NXa46pm 4yjDSRgi4wucX1OXBZtDSin0hF8nrv/WvSS3Hj/w=
Received: from [172.25.197.158] (pcale.tana [172.25.197.158]) (AUTH: CRAM-MD5 515, TLS: TLS1.0,256bits,RSA_AES_256_CBC_SHA1) by wmail.tana.it with ESMTPSA; Wed, 07 Mar 2012 13:56:55 +0100 id 00000000005DC039.000000004F575B17.000022A0
Message-ID: <4F575B17.9030502@tana.it>
Date: Wed, 07 Mar 2012 13:56:55 +0100
From: Alessandro Vesely <vesely@tana.it>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: provisioning software, was DNS RRTYPEs, the difficulty with
References: <20120305170938.57919.qmail@joyce.lan> <4F550DA1.8060304@tana.it> <01OCRP6SYT8Q00ZUIL@mauve.mrochek.com> <4F5634F5.5090909@tana.it> <01OCTDEUL9G200ZUIL@mauve.mrochek.com>
In-Reply-To: <01OCTDEUL9G200ZUIL@mauve.mrochek.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Mar 2012 12:56:57 -0000

On 07/Mar/12 09:42, ned+ietf@mauve.mrochek.com wrote:
> 
>> It would still be possible to work around the need for a plugin, e.g.
>> by depending on some wizard web site, as in John's thought experiment.
> 
>> For the rest of us, the possibility to install a plugin that takes
>> care of all the nitty-gritty details, instead of having to wait for
>> the release and distribution of the next version of BIND, can make the
>> difference between deploying a new RR type right away and
>> procrastinating endlessly.
> 
> You're still not separating the two cases.

I think I did, however badly.  Let me try by example, assuming my
server doesn't recognize SPF.  As it's unrecognized, I have to write
it as such, e.g.

  TYPE99 \# 12 0B 763D73706631 20 2D613131

> Again, an *optional* plugin to check syntax of a record but not
> produce any sort of tokenized result is fine,

Now the plugin can check the syntax and spot the error.  I may correct
it or not.  If I don't, I'll just serve bad data.  In any case, my
zone source still contains the line above.  Thus the plugin is optional.

> a plugin that's *mandatory* to deploy is going to be almost as much
> of an impediment to deployment as requiring an upgrade. Code is
> code, and people don't install new code willy-nilly.

Possibly, I can also run, say:

  echo 'SPF "v=spf1 -a11"' | plugin --dump-hex --silent

and have it dump the TYPE99 line above (without signalling the error,
since I said --silent).  Then I copy its output and paste it into the
zone source.

Finally, I can enable automatic invocation of the plugin.  That way, I
can write the SPF record directly in the zone source and have my
DNS-fictional server do the copy and paste on the fly for me.

I wouldn't call such thing "mandatory".

>> Correct, but when you publish a complex record you are calling forth
>> that complexity.  I don't see much difference if the bug is at mines
>> or at the remote site, since their effects are comparable.
> 
> They most certainly are not. A bug in my client only affects me, a bug
> in the server can easily kill the entire zone.

Ooops, yes, that's right.

From johnl@iecc.com  Wed Mar  7 07:14:04 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 8D5E621E8082 for <ietf@ietfa.amsl.com>; Wed,  7 Mar 2012 07:14:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.398
X-Spam-Level: 
X-Spam-Status: No, score=-102.398 tagged_above=-999 required=5 tests=[AWL=0.202, 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 qCjDSUXRCrHV for <ietf@ietfa.amsl.com>; Wed,  7 Mar 2012 07:14:04 -0800 (PST)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 9451B21E801B for <ietf@ietf.org>; Wed,  7 Mar 2012 07:14:03 -0800 (PST)
Received: (qmail 35593 invoked from network); 7 Mar 2012 15:14:02 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:vbr-info:user-agent:cleverness; s=8b08.4f577b3a.k1203; bh=+52gBkI545h3yYS+mfsJaQX4tbylUJil1mMo+1YEhUM=; b=snpGkN626iSC8X+jGrSgYSljSiDkTr5ec0Jn+fEIznbt+CshyybRr4RRrqi0RCXFBnE3WuYUOjRTe4xIamXVdQBvHA80taYcjKAVIa+zH8xWZaBCAi98T3sWVM6iL7wVW0bHKvJsUu81HhtmzWID6HM8IcMC/q4YyGEdZhOef0s=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Received: (ofmipd 127.0.0.1); 7 Mar 2012 15:13:39 -0000
Date: 7 Mar 2012 10:14:01 -0500
Message-ID: <alpine.BSF.2.00.1203070926260.60146@joyce.lan>
From: "John R. Levine" <johnl@iecc.com>
To: "Mark Andrews" <marka@isc.org>
Subject: Re: provisioning software, was DNS RRTYPEs, the difficulty with
In-Reply-To: <20120307075414.6E63A1E23E05@drugs.dv.isc.org>
References: <20120306044628.87718.qmail@joyce.lan> <77075C8C-04ED-48A2-B501-B2296BCFC8C6@frobbit.se> <01OCRTKK8TSO00ZUIL@mauve.mrochek.com> <alpine.BSF.2.00.1203060950080.10148@joyce.lan> <alpine.LSU.2.00.1203061658110.2756@hermes-2.csi.cam.ac.uk> <alpine.BSF.2.00.1203061203020.14450@joyce.lan> <20120306220911.8B52C1E1DE9F@drugs.dv.isc.org> <alpine.BSF.2.00.1203061711470.25059@joyce.lan> <20120307024247.EF0151E2080D@drugs.dv.isc.org> <alpine.BSF.2.00.1203062148410.34594@joyce.lan>  <D468354F-BE26-41D4-9F75-EA10C5189B73@frobbit.se> <20120307075414.6E63A1E23E05@drugs.dv.isc.org>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
Cleverness: None detected
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
Cc: "ietf@ietf.org Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Mar 2012 15:14:04 -0000

Gee, by sheer random walk this has wandered back to the original topic, 
that provisioning software is the major bar to deploying new RRs.

> Most provisioning systems really don't care about most of the data
> they are throwing about.  It may as well be a opaque blob.

I couldn't disagree more.  Other than my own homebrew system, all the 
provisioning systems I know support a handful of specific RR types and 
make it somewhere between painful and impossible to install anything else.

Godaddy's is a good and very large example of this.  They have a "wizard" 
to create an SPF record, but it turns out to be a TXT record.  If you want 
a real type 99 SPF record, you're out of luck.

Assuming you're not talking about editing zone files with vi, can you give 
some specific examples of what you're talking about?

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

From stbryant@cisco.com  Wed Mar  7 09:02:39 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 B1AF621E801B; Wed,  7 Mar 2012 09:02:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.576
X-Spam-Level: 
X-Spam-Status: No, score=-110.576 tagged_above=-999 required=5 tests=[AWL=0.022, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id o7nBsDVkOKlz; Wed,  7 Mar 2012 09:02:39 -0800 (PST)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by ietfa.amsl.com (Postfix) with ESMTP id 649A121F861A; Wed,  7 Mar 2012 09:02:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=stbryant@cisco.com; l=6270; q=dns/txt; s=iport; t=1331139757; x=1332349357; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to; bh=+Z01LIlb8EViqTXylZZRBlPu5/fqiJcTjiEx58ayf3w=; b=P2QckAjUVz303K9nE1GMq8Y+bjTKgeIptBH1DZhbwd2udONkB4Qnhnuq NCl34spYmVtbz7XobXEB2k3+SBT2K4XBgOWFu9afjy79wfjPumXt1SI1Z ZjFKVDWOOTXzBnMiP+OUNj5BPQd5wNvdEa7G282fbMYZ9ZJLaTcxQP71e A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAFADOUV0+Q/khM/2dsb2JhbABCtSmBB4IKAQEBBAEBAQ8BAgFYCgEMBBwDAQIKFgQLCQMCAQIBFR8HAggGAQwBBQIBAR6HZgugDAGDMQ8Bk3aQbwSVQZAXgmM
X-IronPort-AV: E=Sophos;i="4.73,546,1325462400"; d="scan'208,217";a="67918220"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-2.cisco.com with ESMTP; 07 Mar 2012 17:02:36 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by ams-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id q27H2ah4014528; Wed, 7 Mar 2012 17:02:36 GMT
Received: from stbryant-mac2.local (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id q27H2VBp007435; Wed, 7 Mar 2012 17:02:31 GMT
Message-ID: <4F5794A6.4020107@cisco.com>
Date: Wed, 07 Mar 2012 17:02:30 +0000
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: "mpls@ietf.org" <mpls@ietf.org>, "l2vpn@ietf.org" <l2vpn@ietf.org>
Subject: Fwd: Last Call: <draft-ietf-pwe3-pw-typed-wc-fec-03.txt> (LDP Typed Wildcard FEC for PWid and Generalized PWid FEC Elements) to Proposed Standard
References: <20120307163304.11989.2410.idtracker@ietfa.amsl.com>
In-Reply-To: <20120307163304.11989.2410.idtracker@ietfa.amsl.com>
X-Forwarded-Message-Id: <20120307163304.11989.2410.idtracker@ietfa.amsl.com>
Content-Type: multipart/alternative; boundary="------------050705040201070605070501"
Cc: "Ietf@ietf.org" <Ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Mar 2012 17:02:39 -0000

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

FYI MPLS and L2VPN WGs.

Stewart

-------- Original Message --------
Subject: 	Last Call: (LDP Typed Wildcard FEC for PWid and Generalized 
PWid FEC Elements) to Proposed Standard
Date: 	Wed, 07 Mar 2012 08:33:04 -0800
From: 	The IESG <iesg-secretary@ietf.org>
Reply-To: 	ietf@ietf.org
To: 	IETF-Announce <ietf-announce@ietf.org>
CC: 	pwe3@ietf.org



The IESG has received a request from the Pseudowire Emulation Edge to
Edge WG (pwe3) to consider the following document:
- 'LDP Typed Wildcard FEC for PWid and Generalized PWid FEC Elements'
   <draft-ietf-pwe3-pw-typed-wc-fec-03.txt>  as a 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-03-21. 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 "Typed Wildcard Forwarding Equivalence Class (FEC) Element"
    defines an extension to the Label Distribution Protocol (LDP) that
    can be used when it is desired to request or withdraw or release all
    label bindings for a given FEC Element type.  However, a typed
    wildcard FEC element must be individually defined for each FEC
    element type.  This specification defines the typed wildcard FEC
    elements for the PWid (0x80) and Generalized PWid (0x81) FEC element
    types.





The file can be obtained via
http://datatracker.ietf.org/doc/draft-ietf-pwe3-pw-typed-wc-fec/

IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-ietf-pwe3-pw-typed-wc-fec/ballot/


No IPR declarations have been submitted directly on this I-D.


_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce



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

<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <tt>FYI MPLS and L2VPN WGs.<br>
      <br>
      Stewart<br>
    </tt><br>
    -------- Original Message --------
    <table class="moz-email-headers-table" border="0" cellpadding="0"
      cellspacing="0">
      <tbody>
        <tr>
          <th align="RIGHT" nowrap="nowrap" valign="BASELINE">Subject: </th>
          <td>Last Call: <draft-ietf-pwe3-pw-typed-wc-fec-03.txt> (LDP
              Typed Wildcard FEC for PWid and Generalized PWid FEC
              Elements) to Proposed Standard</draft-ietf-pwe3-pw-typed-wc-fec-03.txt></td>
        </tr>
        <tr>
          <th align="RIGHT" nowrap="nowrap" valign="BASELINE">Date: </th>
          <td>Wed, 07 Mar 2012 08:33:04 -0800</td>
        </tr>
        <tr>
          <th align="RIGHT" nowrap="nowrap" valign="BASELINE">From: </th>
          <td>The IESG <a class="moz-txt-link-rfc2396E" href="mailto:iesg-secretary@ietf.org">&lt;iesg-secretary@ietf.org&gt;</a></td>
        </tr>
        <tr>
          <th align="RIGHT" nowrap="nowrap" valign="BASELINE">Reply-To:
          </th>
          <td><a class="moz-txt-link-abbreviated" href="mailto:ietf@ietf.org">ietf@ietf.org</a></td>
        </tr>
        <tr>
          <th align="RIGHT" nowrap="nowrap" valign="BASELINE">To: </th>
          <td>IETF-Announce <a class="moz-txt-link-rfc2396E" href="mailto:ietf-announce@ietf.org">&lt;ietf-announce@ietf.org&gt;</a></td>
        </tr>
        <tr>
          <th align="RIGHT" nowrap="nowrap" valign="BASELINE">CC: </th>
          <td><a class="moz-txt-link-abbreviated" href="mailto:pwe3@ietf.org">pwe3@ietf.org</a></td>
        </tr>
      </tbody>
    </table>
    <br>
    <br>
    <pre>The IESG has received a request from the Pseudowire Emulation Edge to
Edge WG (pwe3) to consider the following document:
- 'LDP Typed Wildcard FEC for PWid and Generalized PWid FEC Elements'
  &lt;draft-ietf-pwe3-pw-typed-wc-fec-03.txt&gt; as a 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
<a class="moz-txt-link-abbreviated" href="mailto:ietf@ietf.org">ietf@ietf.org</a> mailing lists by 2012-03-21. Exceptionally, comments may be
sent to <a class="moz-txt-link-abbreviated" href="mailto:iesg@ietf.org">iesg@ietf.org</a> instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

Abstract


   The "Typed Wildcard Forwarding Equivalence Class (FEC) Element"
   defines an extension to the Label Distribution Protocol (LDP) that
   can be used when it is desired to request or withdraw or release all
   label bindings for a given FEC Element type.  However, a typed
   wildcard FEC element must be individually defined for each FEC
   element type.  This specification defines the typed wildcard FEC
   elements for the PWid (0x80) and Generalized PWid (0x81) FEC element
   types.





The file can be obtained via
<a class="moz-txt-link-freetext" href="http://datatracker.ietf.org/doc/draft-ietf-pwe3-pw-typed-wc-fec/">http://datatracker.ietf.org/doc/draft-ietf-pwe3-pw-typed-wc-fec/</a>

IESG discussion can be tracked via
<a class="moz-txt-link-freetext" href="http://datatracker.ietf.org/doc/draft-ietf-pwe3-pw-typed-wc-fec/ballot/">http://datatracker.ietf.org/doc/draft-ietf-pwe3-pw-typed-wc-fec/ballot/</a>


No IPR declarations have been submitted directly on this I-D.


_______________________________________________
IETF-Announce mailing list
<a class="moz-txt-link-abbreviated" href="mailto:IETF-Announce@ietf.org">IETF-Announce@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/ietf-announce">https://www.ietf.org/mailman/listinfo/ietf-announce</a>

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

--------------050705040201070605070501--

From stbryant@cisco.com  Wed Mar  7 09:47:38 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 6AB5521E80B1; Wed,  7 Mar 2012 09:47:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.576
X-Spam-Level: 
X-Spam-Status: No, score=-110.576 tagged_above=-999 required=5 tests=[AWL=0.023, 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 pk+DdIp010NR; Wed,  7 Mar 2012 09:47:36 -0800 (PST)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by ietfa.amsl.com (Postfix) with ESMTP id 2CE1521E8017; Wed,  7 Mar 2012 09:47:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=stbryant@cisco.com; l=2468; q=dns/txt; s=iport; t=1331142456; x=1332352056; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=oIzDZmDtj9WF8gdcCGmGIVhI7NDXgMWrvnYnDPuQFcY=; b=FFKricc0UIOWwiuFo8k9D6UF8XHAgQeWTRei8ZOa1g+ubh06RWes/KMS pCBve87G5OYkNynYwRlAU66Ou9dd2ZPol3mKw79q76ZYuDQ8iapHc50uM FkUcfZhSWAVxJ//pVqLWpMmik8fAy4WP9z/74p1Nc/KJgTaL0qv4+bBSI Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAEKeV0+Q/khN/2dsb2JhbABEtR2BB4IKAQEBBAEBAQ8BAgEiNgoBEAsYCRYECwkDAgECARUfERMBBQIBAR6HZguaPwGDMQ8Bm1mNTYMiBJVBkBeCYw
X-IronPort-AV: E=Sophos;i="4.73,547,1325462400"; d="scan'208";a="131622045"
Received: from ams-core-4.cisco.com ([144.254.72.77]) by ams-iport-1.cisco.com with ESMTP; 07 Mar 2012 17:47:34 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by ams-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id q27HlYjR006994; Wed, 7 Mar 2012 17:47:34 GMT
Received: from stbryant-mac2.local (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id q27HlVTN011204; Wed, 7 Mar 2012 17:47:32 GMT
Message-ID: <4F579F33.7050508@cisco.com>
Date: Wed, 07 Mar 2012 17:47:31 +0000
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: draft-ietf-pwe3-redundancy-bit@tools.ietf.org
Subject: Re: Last Call: <draft-ietf-pwe3-redundancy-bit-06.txt> (Pseudowire Preferential Forwarding Status Bit) to Proposed Standard
References: <20120307170032.20594.20281.idtracker@ietfa.amsl.com>
In-Reply-To: <20120307170032.20594.20281.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: pwe3@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Mar 2012 17:47:38 -0000

Authors

There was on point that I notice that you did not address
from the AD review and so I am picking it up as a LC comment:

In section 10 you say:

    "This document makes the following update to the PwOperStatusTC
    textual convention in RFC5542 [8]: "

This update should be recorded in the metadata (top left front page)
and it is usual to put a one line note in the abstract.

Stewart



On 07/03/2012 17:00, The IESG wrote:
> The IESG has received a request from the Pseudowire Emulation Edge to
> Edge WG (pwe3) to consider the following document:
> - 'Pseudowire Preferential Forwarding Status Bit'
>    <draft-ietf-pwe3-redundancy-bit-06.txt>  as a 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-03-21. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
>
> Abstract
>
>
>     This document describes a mechanism for standby status signaling of
>     redundant pseudowires (PWs) between their termination points. A set
>     of redundant PWs is configured between provider edge (PE) nodes in
>     single-segment pseudowire (SS-PW) applications, or between
>     terminating provider edge (T-PE) nodes in multi-segment pseudowire
>     (MS-PW) applications.
>
>     In order for the PE/T-PE nodes to indicate the preferred PW to use
>     for forwarding PW packets to one another, a new status bit is needed
>     to indicate a preferential forwarding status of Active or Standby for
>     each PW in a redundant set.
>
>     In addition, a second status bit is defined to allow peer PE nodes to
>     coordinate a switchover operation of the PW.
>
>
>
>
>
>
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-pwe3-redundancy-bit/
>
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-pwe3-redundancy-bit/ballot/
>
>
> No IPR declarations have been submitted directly on this I-D.
>
>
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-announce
>


-- 
For corporate legal information go to:

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



From tnadeau@lucidvision.com  Wed Mar  7 11:31:40 2012
Return-Path: <tnadeau@lucidvision.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 948A111E8091; Wed,  7 Mar 2012 11:31:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.548
X-Spam-Level: 
X-Spam-Status: No, score=-2.548 tagged_above=-999 required=5 tests=[AWL=0.051,  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 8e7K5c1p7gZa; Wed,  7 Mar 2012 11:31:39 -0800 (PST)
Received: from lucidvision.com (lucidvision.com [72.71.250.34]) by ietfa.amsl.com (Postfix) with ESMTP id 8CFFF11E8085; Wed,  7 Mar 2012 11:31:39 -0800 (PST)
Received: from [192.168.1.53] (static-72-71-250-38.cncdnh.fast04.myfairpoint.net [72.71.250.38]) by lucidvision.com (Postfix) with ESMTP id E0E2217F66A; Wed,  7 Mar 2012 14:31:38 -0500 (EST)
Subject: Re: [PWE3] Last Call: <draft-ietf-pwe3-redundancy-bit-06.txt> (Pseudowire Preferential Forwarding Status Bit) to Proposed Standard
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=us-ascii
From: Thomas Nadeau <tnadeau@lucidvision.com>
In-Reply-To: <5DF53972F7E9134782DCE51624466FE50AD5811DAC@USNAVSXCHMBSC2.ndc.alcatel-lucent.com>
Date: Wed, 7 Mar 2012 14:31:38 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <70493619-9792-49DF-AAA4-C81074854CF7@lucidvision.com>
References: <20120307170032.20594.20281.idtracker@ietfa.amsl.com> <4F579F33.7050508@cisco.com> <5DF53972F7E9134782DCE51624466FE50AD5811DAC@USNAVSXCHMBSC2.ndc.alcatel-lucent.com>
To: "Aissaoui, Mustapha (Mustapha)" <mustapha.aissaoui@alcatel-lucent.com>
X-Mailer: Apple Mail (2.1257)
Cc: "draft-ietf-pwe3-redundancy-bit@tools.ietf.org" <draft-ietf-pwe3-redundancy-bit@tools.ietf.org>, "pwe3@ietf.org" <pwe3@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "stbryant@cisco.com" <stbryant@cisco.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Mar 2012 19:31:40 -0000

	After looking over this just now - and forgive me as I didn't =
realize it contained a reference to 5542 until now - it seems to me that =
rather that including this in the RFC as "an update to RFC5542", this be =
added as an errata entry to 5542.  It seems odd to me to note that the =
single sentence represented here "updates" the RFC version, when what it =
does is really clarify it based on the new behavior outlined in the =
redundancy-bit draft, and even then "clarify" is difficult to use since =
it is more of an example of such a case of a 'dormant' interface.

	--Tom


On Mar 7, 2012, at 12:49 PM, Aissaoui, Mustapha (Mustapha) wrote:

> Ooops. Thank you for pointing this out Stewart. I will make the update =
and publish a new revision.
>=20
> Mustapha.=20
>=20
> -----Original Message-----
> From: Stewart Bryant [mailto:stbryant@cisco.com]=20
> Sent: Wednesday, March 07, 2012 12:48 PM
> To: draft-ietf-pwe3-redundancy-bit@tools.ietf.org
> Cc: ietf@ietf.org; pwe3@ietf.org
> Subject: Re: Last Call: <draft-ietf-pwe3-redundancy-bit-06.txt> =
(Pseudowire Preferential Forwarding Status Bit) to Proposed Standard
>=20
>=20
> Authors
>=20
> There was on point that I notice that you did not address from the AD =
review and so I am picking it up as a LC comment:
>=20
> In section 10 you say:
>=20
>    "This document makes the following update to the PwOperStatusTC
>    textual convention in RFC5542 [8]: "
>=20
> This update should be recorded in the metadata (top left front page) =
and it is usual to put a one line note in the abstract.
>=20
> Stewart
>=20
>=20
>=20
> On 07/03/2012 17:00, The IESG wrote:
>> The IESG has received a request from the Pseudowire Emulation Edge to=20=

>> Edge WG (pwe3) to consider the following document:
>> - 'Pseudowire Preferential Forwarding Status Bit'
>>   <draft-ietf-pwe3-redundancy-bit-06.txt>  as a Proposed Standard
>>=20
>> The IESG plans to make a decision in the next few weeks, and solicits=20=

>> final comments on this action. Please send substantive comments to =
the=20
>> ietf@ietf.org mailing lists by 2012-03-21. Exceptionally, comments =
may=20
>> be sent to iesg@ietf.org instead. In either case, please retain the=20=

>> beginning of the Subject line to allow automated sorting.
>>=20
>> Abstract
>>=20
>>=20
>>    This document describes a mechanism for standby status signaling =
of
>>    redundant pseudowires (PWs) between their termination points. A =
set
>>    of redundant PWs is configured between provider edge (PE) nodes in
>>    single-segment pseudowire (SS-PW) applications, or between
>>    terminating provider edge (T-PE) nodes in multi-segment pseudowire
>>    (MS-PW) applications.
>>=20
>>    In order for the PE/T-PE nodes to indicate the preferred PW to use
>>    for forwarding PW packets to one another, a new status bit is =
needed
>>    to indicate a preferential forwarding status of Active or Standby =
for
>>    each PW in a redundant set.
>>=20
>>    In addition, a second status bit is defined to allow peer PE nodes =
to
>>    coordinate a switchover operation of the PW.
>>=20
>>=20
>>=20
>>=20
>>=20
>>=20
>> The file can be obtained via
>> http://datatracker.ietf.org/doc/draft-ietf-pwe3-redundancy-bit/
>>=20
>> IESG discussion can be tracked via
>> =
http://datatracker.ietf.org/doc/draft-ietf-pwe3-redundancy-bit/ballot/
>>=20
>>=20
>> No IPR declarations have been submitted directly on this I-D.
>>=20
>>=20
>> _______________________________________________
>> IETF-Announce mailing list
>> IETF-Announce@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf-announce
>>=20
>=20
>=20
> --
> For corporate legal information go to:
>=20
> http://www.cisco.com/web/about/doing_business/legal/cri/index.html
>=20
>=20
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www.ietf.org/mailman/listinfo/pwe3
>=20


From stbryant@cisco.com  Wed Mar  7 11:46:06 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 EFFDF11E8086; Wed,  7 Mar 2012 11:46:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.577
X-Spam-Level: 
X-Spam-Status: No, score=-110.577 tagged_above=-999 required=5 tests=[AWL=0.022, 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 DwsFuvUK0cOr; Wed,  7 Mar 2012 11:46:06 -0800 (PST)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by ietfa.amsl.com (Postfix) with ESMTP id B2CC811E8072; Wed,  7 Mar 2012 11:45:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=stbryant@cisco.com; l=4568; q=dns/txt; s=iport; t=1331149554; x=1332359154; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=mjcA3jxwM7v2vhJflGsVM3nRRY2EzDcgVmyc16euwBk=; b=bg+XTg4vADaUyM58PYsY1uO26iQ73kHwV8HTPKacF1TQ+mRU9SRS+oYN +RX3YYeHWUj58bU2UGqifz5JrQiluvqb4fA4zkUIr9M4RLrRBEvIw6dNw UIKauc3sFbbcq1NEEz1HigFcEdrSlkrdB4qka0AqL9ndT+GroeHKCmyVN E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgEFALO5V0+Q/khL/2dsb2JhbABEtSKBB4IKAQEBBAEBAQ8BAgEiNgoBDAQLDgMEAQEBCRYEBAcJAwIBAgEVHwkIBg0BBQIBAR6HZguaRgGDMQ8Bm0mQbwSVQZAXgmM
X-IronPort-AV: E=Sophos;i="4.73,547,1325462400"; d="scan'208";a="67929983"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by ams-iport-2.cisco.com with ESMTP; 07 Mar 2012 19:45:53 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by ams-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id q27Jjr5M007355; Wed, 7 Mar 2012 19:45:53 GMT
Received: from stbryant-mac2.lan (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id q27JjqsX019064; Wed, 7 Mar 2012 19:45:52 GMT
Message-ID: <4F57BAEF.6090007@cisco.com>
Date: Wed, 07 Mar 2012 19:45:51 +0000
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: Thomas Nadeau <tnadeau@lucidvision.com>
Subject: Re: [PWE3] Last Call: <draft-ietf-pwe3-redundancy-bit-06.txt> (Pseudowire Preferential Forwarding Status Bit) to Proposed Standard
References: <20120307170032.20594.20281.idtracker@ietfa.amsl.com> <4F579F33.7050508@cisco.com> <5DF53972F7E9134782DCE51624466FE50AD5811DAC@USNAVSXCHMBSC2.ndc.alcatel-lucent.com> <70493619-9792-49DF-AAA4-C81074854CF7@lucidvision.com>
In-Reply-To: <70493619-9792-49DF-AAA4-C81074854CF7@lucidvision.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "Aissaoui, Mustapha \(Mustapha\)" <mustapha.aissaoui@alcatel-lucent.com>, "draft-ietf-pwe3-redundancy-bit@tools.ietf.org" <draft-ietf-pwe3-redundancy-bit@tools.ietf.org>, "pwe3@ietf.org" <pwe3@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Mar 2012 19:46:07 -0000

It cannot be an erratum.

An erratum indicated an error a the time of writing and that is clearly 
not the case.

Is the text " For example, the PW Preferential Forwarding status state 
machine as defined in [RFCXXXX (this document)] is in state "STANDBY". " 
actually in the MIB definition itself?

If so it's an update to the MIB (as explained in  the draft).

If not then why not simply explain the event's action on the MIB and not 
update the MIB itself?

- Stewart





On 07/03/2012 19:31, Thomas Nadeau wrote:
> 	After looking over this just now - and forgive me as I didn't realize it contained a reference to 5542 until now - it seems to me that rather that including this in the RFC as "an update to RFC5542", this be added as an errata entry to 5542.  It seems odd to me to note that the single sentence represented here "updates" the RFC version, when what it does is really clarify it based on the new behavior outlined in the redundancy-bit draft, and even then "clarify" is difficult to use since it is more of an example of such a case of a 'dormant' interface.
>
> 	--Tom
>
>
> On Mar 7, 2012, at 12:49 PM, Aissaoui, Mustapha (Mustapha) wrote:
>
>> Ooops. Thank you for pointing this out Stewart. I will make the update and publish a new revision.
>>
>> Mustapha.
>>
>> -----Original Message-----
>> From: Stewart Bryant [mailto:stbryant@cisco.com]
>> Sent: Wednesday, March 07, 2012 12:48 PM
>> To: draft-ietf-pwe3-redundancy-bit@tools.ietf.org
>> Cc: ietf@ietf.org; pwe3@ietf.org
>> Subject: Re: Last Call:<draft-ietf-pwe3-redundancy-bit-06.txt>  (Pseudowire Preferential Forwarding Status Bit) to Proposed Standard
>>
>>
>> Authors
>>
>> There was on point that I notice that you did not address from the AD review and so I am picking it up as a LC comment:
>>
>> In section 10 you say:
>>
>>     "This document makes the following update to the PwOperStatusTC
>>     textual convention in RFC5542 [8]: "
>>
>> This update should be recorded in the metadata (top left front page) and it is usual to put a one line note in the abstract.
>>
>> Stewart
>>
>>
>>
>> On 07/03/2012 17:00, The IESG wrote:
>>> The IESG has received a request from the Pseudowire Emulation Edge to
>>> Edge WG (pwe3) to consider the following document:
>>> - 'Pseudowire Preferential Forwarding Status Bit'
>>>    <draft-ietf-pwe3-redundancy-bit-06.txt>   as a 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-03-21. Exceptionally, comments may
>>> be sent to iesg@ietf.org instead. In either case, please retain the
>>> beginning of the Subject line to allow automated sorting.
>>>
>>> Abstract
>>>
>>>
>>>     This document describes a mechanism for standby status signaling of
>>>     redundant pseudowires (PWs) between their termination points. A set
>>>     of redundant PWs is configured between provider edge (PE) nodes in
>>>     single-segment pseudowire (SS-PW) applications, or between
>>>     terminating provider edge (T-PE) nodes in multi-segment pseudowire
>>>     (MS-PW) applications.
>>>
>>>     In order for the PE/T-PE nodes to indicate the preferred PW to use
>>>     for forwarding PW packets to one another, a new status bit is needed
>>>     to indicate a preferential forwarding status of Active or Standby for
>>>     each PW in a redundant set.
>>>
>>>     In addition, a second status bit is defined to allow peer PE nodes to
>>>     coordinate a switchover operation of the PW.
>>>
>>>
>>>
>>>
>>>
>>>
>>> The file can be obtained via
>>> http://datatracker.ietf.org/doc/draft-ietf-pwe3-redundancy-bit/
>>>
>>> IESG discussion can be tracked via
>>> http://datatracker.ietf.org/doc/draft-ietf-pwe3-redundancy-bit/ballot/
>>>
>>>
>>> No IPR declarations have been submitted directly on this I-D.
>>>
>>>
>>> _______________________________________________
>>> IETF-Announce mailing list
>>> IETF-Announce@ietf.org
>>> https://www.ietf.org/mailman/listinfo/ietf-announce
>>>
>>
>> --
>> For corporate legal information go to:
>>
>> http://www.cisco.com/web/about/doing_business/legal/cri/index.html
>>
>>
>> _______________________________________________
>> pwe3 mailing list
>> pwe3@ietf.org
>> https://www.ietf.org/mailman/listinfo/pwe3
>>
>


-- 
For corporate legal information go to:

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



From alberto@it.uc3m.es  Wed Mar  7 02:02:23 2012
Return-Path: <alberto@it.uc3m.es>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 14C8621F87AD; Wed,  7 Mar 2012 02:02:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.135
X-Spam-Level: 
X-Spam-Status: No, score=-6.135 tagged_above=-999 required=5 tests=[AWL=0.164,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CUnXbeCnZdv7; Wed,  7 Mar 2012 02:02:22 -0800 (PST)
Received: from smtp01.uc3m.es (smtp01.uc3m.es [163.117.176.131]) by ietfa.amsl.com (Postfix) with ESMTP id 6570221F87AB; Wed,  7 Mar 2012 02:02:22 -0800 (PST)
X-uc3m-safe: yes
Received: from BOMBO (unknown [163.117.139.62]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp01.uc3m.es (Postfix) with ESMTP id 0177EC28659; Wed,  7 Mar 2012 11:02:21 +0100 (CET)
From: =?iso-8859-1?Q?Alberto_Garc=EDa?= <alberto@it.uc3m.es>
To: "'Dan Wing'" <dwing@cisco.com>, "'IETF discussion list'" <ietf@ietf.org>
References: <023f01ccf756$e4d4a110$ae7de330$@com> <00ab01ccfbbb$7e7d0380$7b770a80$@it.uc3m.es> <07e001ccfbbe$13eaba50$3bc02ef0$@com>
In-Reply-To: <07e001ccfbbe$13eaba50$3bc02ef0$@com>
Subject: RE: tsv-dir review of draft-garcia-shim6-applicability-03
Date: Wed, 7 Mar 2012 11:02:21 +0100
Message-ID: <000001ccfc49$640ae6f0$2c20b4d0$@it.uc3m.es>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQDWY9DRXMH2S1eCM54jIy0w4V/WFQFLnuCDAxpINIWYKIQl8A==
Content-Language: es
X-TM-AS-Product-Ver: IMSS-7.0.0.3116-6.8.0.1017-18758.003
X-Mailman-Approved-At: Wed, 07 Mar 2012 12:07:42 -0800
Cc: 'marcelo bagnulo braun' <marcelo@it.uc3m.es>, joe.abley@icann.org, tsv-area@ietf.org, 'Transport Directorate' <tsv-dir@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Mar 2012 10:02:23 -0000

Hi Dan,

|  > |  Section 7.7, "Shim6 and IPv6 NAT", the problem could be overcome by
|  > the
|  > |  Shim6 node knowing its IPv6 address after NPTv6 translation.
|  > Probably
|  > not
|  > |  worth adjusting the document, though, as NPTv6 is experimental.
|  >
|  > Well, this would not work for HBA, since in this case the addresses
|  > are fixed once generated.
|  
|  NPTv6 does not change the host portion of the address (it only changes
the
|  network portion -- the IPv6 prefix), so HBA should work with NPTv6.
|  

Well, HBAs are built as a hash of many things, including the different
prefixes for which you want to generate an address. Different interface
identifiers are generated by changing the order in which the hash is
performed. 
The issue with NPTv6 is that, in order to verify that the locator is a valid
HBA, the receiver checks that the prefix of the locator is included in the
HBA Parameter Data Structure, and then that the appropriate hash of the
Parameter Data Structure corresponds to the interface identifier. If the
NPTv6 changes the prefix, the first validation, the one regarding to the
prefix, will fail, and HBAs will not work.

Regards,
Alberto


From mustapha.aissaoui@alcatel-lucent.com  Wed Mar  7 09:49:48 2012
Return-Path: <mustapha.aissaoui@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 04D8421F84E0; Wed,  7 Mar 2012 09:49:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.12
X-Spam-Level: 
X-Spam-Status: No, score=-9.12 tagged_above=-999 required=5 tests=[AWL=1.479,  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 fhljSYyt8VRa; Wed,  7 Mar 2012 09:49:47 -0800 (PST)
Received: from ihemail2.lucent.com (ihemail2.lucent.com [135.245.0.35]) by ietfa.amsl.com (Postfix) with ESMTP id 3898921F84DE; Wed,  7 Mar 2012 09:49:47 -0800 (PST)
Received: from usnavsmail4.ndc.alcatel-lucent.com (usnavsmail4.ndc.alcatel-lucent.com [135.3.39.12]) by ihemail2.lucent.com (8.13.8/IER-o) with ESMTP id q27HnjZn012214 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 7 Mar 2012 11:49:45 -0600 (CST)
Received: from USNAVSXCHHUB03.ndc.alcatel-lucent.com (usnavsxchhub03.ndc.alcatel-lucent.com [135.3.39.112]) by usnavsmail4.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id q27HniUO018423 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 7 Mar 2012 11:49:44 -0600
Received: from USNAVSXCHMBSC2.ndc.alcatel-lucent.com ([135.3.39.147]) by USNAVSXCHHUB03.ndc.alcatel-lucent.com ([135.3.39.112]) with mapi; Wed, 7 Mar 2012 11:49:44 -0600
From: "Aissaoui, Mustapha (Mustapha)" <mustapha.aissaoui@alcatel-lucent.com>
To: "stbryant@cisco.com" <stbryant@cisco.com>, "draft-ietf-pwe3-redundancy-bit@tools.ietf.org" <draft-ietf-pwe3-redundancy-bit@tools.ietf.org>
Date: Wed, 7 Mar 2012 11:49:43 -0600
Subject: RE: Last Call: <draft-ietf-pwe3-redundancy-bit-06.txt> (Pseudowire Preferential Forwarding Status Bit) to Proposed Standard
Thread-Topic: Last Call: <draft-ietf-pwe3-redundancy-bit-06.txt> (Pseudowire Preferential Forwarding Status Bit) to Proposed Standard
Thread-Index: Acz8imr3BjHtt4oFQ6a+R4rxvz1BRQAACvjg
Message-ID: <5DF53972F7E9134782DCE51624466FE50AD5811DAC@USNAVSXCHMBSC2.ndc.alcatel-lucent.com>
References: <20120307170032.20594.20281.idtracker@ietfa.amsl.com> <4F579F33.7050508@cisco.com>
In-Reply-To: <4F579F33.7050508@cisco.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-Scanned-By: MIMEDefang 2.57 on 135.245.2.35
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.12
X-Mailman-Approved-At: Wed, 07 Mar 2012 12:07:42 -0800
Cc: "pwe3@ietf.org" <pwe3@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, 07 Mar 2012 17:49:48 -0000

Ooops. Thank you for pointing this out Stewart. I will make the update and =
publish a new revision.

Mustapha.=20

-----Original Message-----
From: Stewart Bryant [mailto:stbryant@cisco.com]=20
Sent: Wednesday, March 07, 2012 12:48 PM
To: draft-ietf-pwe3-redundancy-bit@tools.ietf.org
Cc: ietf@ietf.org; pwe3@ietf.org
Subject: Re: Last Call: <draft-ietf-pwe3-redundancy-bit-06.txt> (Pseudowire=
 Preferential Forwarding Status Bit) to Proposed Standard


Authors

There was on point that I notice that you did not address from the AD revie=
w and so I am picking it up as a LC comment:

In section 10 you say:

    "This document makes the following update to the PwOperStatusTC
    textual convention in RFC5542 [8]: "

This update should be recorded in the metadata (top left front page) and it=
 is usual to put a one line note in the abstract.

Stewart



On 07/03/2012 17:00, The IESG wrote:
> The IESG has received a request from the Pseudowire Emulation Edge to=20
> Edge WG (pwe3) to consider the following document:
> - 'Pseudowire Preferential Forwarding Status Bit'
>    <draft-ietf-pwe3-redundancy-bit-06.txt>  as a Proposed Standard
>
> The IESG plans to make a decision in the next few weeks, and solicits=20
> final comments on this action. Please send substantive comments to the=20
> ietf@ietf.org mailing lists by 2012-03-21. Exceptionally, comments may=20
> be sent to iesg@ietf.org instead. In either case, please retain the=20
> beginning of the Subject line to allow automated sorting.
>
> Abstract
>
>
>     This document describes a mechanism for standby status signaling of
>     redundant pseudowires (PWs) between their termination points. A set
>     of redundant PWs is configured between provider edge (PE) nodes in
>     single-segment pseudowire (SS-PW) applications, or between
>     terminating provider edge (T-PE) nodes in multi-segment pseudowire
>     (MS-PW) applications.
>
>     In order for the PE/T-PE nodes to indicate the preferred PW to use
>     for forwarding PW packets to one another, a new status bit is needed
>     to indicate a preferential forwarding status of Active or Standby for
>     each PW in a redundant set.
>
>     In addition, a second status bit is defined to allow peer PE nodes to
>     coordinate a switchover operation of the PW.
>
>
>
>
>
>
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-pwe3-redundancy-bit/
>
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-pwe3-redundancy-bit/ballot/
>
>
> No IPR declarations have been submitted directly on this I-D.
>
>
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-announce
>


--
For corporate legal information go to:

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



From amalis@gmail.com  Wed Mar  7 09:53:30 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 607BB21F8555; Wed,  7 Mar 2012 09:53:30 -0800 (PST)
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 WUr20WSm3W8f; Wed,  7 Mar 2012 09:53:29 -0800 (PST)
Received: from mail-gy0-f172.google.com (mail-gy0-f172.google.com [209.85.160.172]) by ietfa.amsl.com (Postfix) with ESMTP id 488AF21F8531; Wed,  7 Mar 2012 09:53:29 -0800 (PST)
Received: by ghbg16 with SMTP id g16so3442901ghb.31 for <multiple recipients>; Wed, 07 Mar 2012 09:53:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=pDLkcToLNAj06QnJfDYdNqD1vbg4kui48szl1unZUhU=; b=HvjSXe9xmFhAxJcAzoAbuMskIU/l25vvJnXHhgXLpqW7Eijb36mxuJhyDLhhR4AyrU HUXsegiROa216re00qT524PtTE7Uyxwz0IcpVHcoYyPStr9PH6jqSBTE5tfKGUreaKHN uH3cCwzf1RkACmUtw4oFSPEHqw3/PfRxXPr/c/oUvCcSP0qov/IJMPk2gcmQjw3fag+D 4Lek1QOdzvsTx2DkHRWidWhO+GPoq0p1k0v081sfs4AifRHZ74yiDNj22GsYiMsCaU4n xwi96+f9z/T1pVQDhNrwLpA7IH+5/wY+jlcw3KYes/ELLZxPQc0LUdOPXmfjI4IzI6BB rsnA==
Received: by 10.236.43.68 with SMTP id k44mr5722304yhb.77.1331142808879; Wed, 07 Mar 2012 09:53:28 -0800 (PST)
MIME-Version: 1.0
Received: by 10.146.164.19 with HTTP; Wed, 7 Mar 2012 09:53:08 -0800 (PST)
In-Reply-To: <5DF53972F7E9134782DCE51624466FE50AD5811DAC@USNAVSXCHMBSC2.ndc.alcatel-lucent.com>
References: <20120307170032.20594.20281.idtracker@ietfa.amsl.com> <4F579F33.7050508@cisco.com> <5DF53972F7E9134782DCE51624466FE50AD5811DAC@USNAVSXCHMBSC2.ndc.alcatel-lucent.com>
From: "Andrew G. Malis" <amalis@gmail.com>
Date: Wed, 7 Mar 2012 09:53:08 -0800
Message-ID: <CAK+d4xsS9GVrM1u2QPhsfXXK6xhzmQzGDDaVNhqay8VM_eQbaQ@mail.gmail.com>
Subject: Re: [PWE3] Last Call: <draft-ietf-pwe3-redundancy-bit-06.txt> (Pseudowire Preferential Forwarding Status Bit) to Proposed Standard
To: "Aissaoui, Mustapha (Mustapha)" <mustapha.aissaoui@alcatel-lucent.com>
Content-Type: multipart/alternative; boundary=20cf300e543344c30b04baaad673
X-Mailman-Approved-At: Wed, 07 Mar 2012 12:07:42 -0800
Cc: "draft-ietf-pwe3-redundancy-bit@tools.ietf.org" <draft-ietf-pwe3-redundancy-bit@tools.ietf.org>, "pwe3@ietf.org" <pwe3@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "stbryant@cisco.com" <stbryant@cisco.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Mar 2012 17:53:30 -0000

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

Mustapha,

You might want to wait for any other LC comments before updating.

Thanks,
Andy

On Wed, Mar 7, 2012 at 9:49 AM, Aissaoui, Mustapha (Mustapha) <
mustapha.aissaoui@alcatel-lucent.com> wrote:

> Ooops. Thank you for pointing this out Stewart. I will make the update and
> publish a new revision.
>
> Mustapha.
>
> -----Original Message-----
> From: Stewart Bryant [mailto:stbryant@cisco.com]
> Sent: Wednesday, March 07, 2012 12:48 PM
> To: draft-ietf-pwe3-redundancy-bit@tools.ietf.org
> Cc: ietf@ietf.org; pwe3@ietf.org
> Subject: Re: Last Call: <draft-ietf-pwe3-redundancy-bit-06.txt>
> (Pseudowire Preferential Forwarding Status Bit) to Proposed Standard
>
>
> Authors
>
> There was on point that I notice that you did not address from the AD
> review and so I am picking it up as a LC comment:
>
> In section 10 you say:
>
>    "This document makes the following update to the PwOperStatusTC
>    textual convention in RFC5542 [8]: "
>
> This update should be recorded in the metadata (top left front page) and
> it is usual to put a one line note in the abstract.
>
> Stewart
>
>
>
> On 07/03/2012 17:00, The IESG wrote:
> > The IESG has received a request from the Pseudowire Emulation Edge to
> > Edge WG (pwe3) to consider the following document:
> > - 'Pseudowire Preferential Forwarding Status Bit'
> >    <draft-ietf-pwe3-redundancy-bit-06.txt>  as a 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-03-21. Exceptionally, comments may
> > be sent to iesg@ietf.org instead. In either case, please retain the
> > beginning of the Subject line to allow automated sorting.
> >
> > Abstract
> >
> >
> >     This document describes a mechanism for standby status signaling of
> >     redundant pseudowires (PWs) between their termination points. A set
> >     of redundant PWs is configured between provider edge (PE) nodes in
> >     single-segment pseudowire (SS-PW) applications, or between
> >     terminating provider edge (T-PE) nodes in multi-segment pseudowire
> >     (MS-PW) applications.
> >
> >     In order for the PE/T-PE nodes to indicate the preferred PW to use
> >     for forwarding PW packets to one another, a new status bit is needed
> >     to indicate a preferential forwarding status of Active or Standby for
> >     each PW in a redundant set.
> >
> >     In addition, a second status bit is defined to allow peer PE nodes to
> >     coordinate a switchover operation of the PW.
> >
> >
> >
> >
> >
> >
> > The file can be obtained via
> > http://datatracker.ietf.org/doc/draft-ietf-pwe3-redundancy-bit/
> >
> > IESG discussion can be tracked via
> > http://datatracker.ietf.org/doc/draft-ietf-pwe3-redundancy-bit/ballot/
> >
> >
> > No IPR declarations have been submitted directly on this I-D.
> >
> >
> > _______________________________________________
> > IETF-Announce mailing list
> > IETF-Announce@ietf.org
> > https://www.ietf.org/mailman/listinfo/ietf-announce
> >
>
>
> --
> For corporate legal information go to:
>
> http://www.cisco.com/web/about/doing_business/legal/cri/index.html
>
>
> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www.ietf.org/mailman/listinfo/pwe3
>

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

Mustapha,<br><br>You might want to wait for any other LC comments before up=
dating.<br><br>Thanks,<br>Andy<br><br><div class=3D"gmail_quote">On Wed, Ma=
r 7, 2012 at 9:49 AM, Aissaoui, Mustapha (Mustapha) <span dir=3D"ltr">&lt;<=
a href=3D"mailto:mustapha.aissaoui@alcatel-lucent.com">mustapha.aissaoui@al=
catel-lucent.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">Ooops. Thank you for pointing this out Stewa=
rt. I will make the update and publish a new revision.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
Mustapha.<br>
</font></span><div class=3D"HOEnZb"><div class=3D"h5"><br>
-----Original Message-----<br>
From: Stewart Bryant [mailto:<a href=3D"mailto:stbryant@cisco.com">stbryant=
@cisco.com</a>]<br>
Sent: Wednesday, March 07, 2012 12:48 PM<br>
To: <a href=3D"mailto:draft-ietf-pwe3-redundancy-bit@tools.ietf.org">draft-=
ietf-pwe3-redundancy-bit@tools.ietf.org</a><br>
Cc: <a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a>; <a href=3D"mailto:p=
we3@ietf.org">pwe3@ietf.org</a><br>
Subject: Re: Last Call: &lt;draft-ietf-pwe3-redundancy-bit-06.txt&gt; (Pseu=
dowire Preferential Forwarding Status Bit) to Proposed Standard<br>
<br>
<br>
Authors<br>
<br>
There was on point that I notice that you did not address from the AD revie=
w and so I am picking it up as a LC comment:<br>
<br>
In section 10 you say:<br>
<br>
 =A0 =A0&quot;This document makes the following update to the PwOperStatusT=
C<br>
 =A0 =A0textual convention in RFC5542 [8]: &quot;<br>
<br>
This update should be recorded in the metadata (top left front page) and it=
 is usual to put a one line note in the abstract.<br>
<br>
Stewart<br>
<br>
<br>
<br>
On 07/03/2012 17:00, The IESG wrote:<br>
&gt; The IESG has received a request from the Pseudowire Emulation Edge to<=
br>
&gt; Edge WG (pwe3) to consider the following document:<br>
&gt; - &#39;Pseudowire Preferential Forwarding Status Bit&#39;<br>
&gt; =A0 =A0&lt;draft-ietf-pwe3-redundancy-bit-06.txt&gt; =A0as a Proposed =
Standard<br>
&gt;<br>
&gt; The IESG plans to make a decision in the next few weeks, and solicits<=
br>
&gt; final comments on this action. Please send substantive comments to the=
<br>
&gt; <a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a> mailing lists by 20=
12-03-21. Exceptionally, comments may<br>
&gt; be sent to <a href=3D"mailto:iesg@ietf.org">iesg@ietf.org</a> instead.=
 In either case, please retain the<br>
&gt; beginning of the Subject line to allow automated sorting.<br>
&gt;<br>
&gt; Abstract<br>
&gt;<br>
&gt;<br>
&gt; =A0 =A0 This document describes a mechanism for standby status signali=
ng of<br>
&gt; =A0 =A0 redundant pseudowires (PWs) between their termination points. =
A set<br>
&gt; =A0 =A0 of redundant PWs is configured between provider edge (PE) node=
s in<br>
&gt; =A0 =A0 single-segment pseudowire (SS-PW) applications, or between<br>
&gt; =A0 =A0 terminating provider edge (T-PE) nodes in multi-segment pseudo=
wire<br>
&gt; =A0 =A0 (MS-PW) applications.<br>
&gt;<br>
&gt; =A0 =A0 In order for the PE/T-PE nodes to indicate the preferred PW to=
 use<br>
&gt; =A0 =A0 for forwarding PW packets to one another, a new status bit is =
needed<br>
&gt; =A0 =A0 to indicate a preferential forwarding status of Active or Stan=
dby for<br>
&gt; =A0 =A0 each PW in a redundant set.<br>
&gt;<br>
&gt; =A0 =A0 In addition, a second status bit is defined to allow peer PE n=
odes to<br>
&gt; =A0 =A0 coordinate a switchover operation of the PW.<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; The file can be obtained via<br>
&gt; <a href=3D"http://datatracker.ietf.org/doc/draft-ietf-pwe3-redundancy-=
bit/" target=3D"_blank">http://datatracker.ietf.org/doc/draft-ietf-pwe3-red=
undancy-bit/</a><br>
&gt;<br>
&gt; IESG discussion can be tracked via<br>
&gt; <a href=3D"http://datatracker.ietf.org/doc/draft-ietf-pwe3-redundancy-=
bit/ballot/" target=3D"_blank">http://datatracker.ietf.org/doc/draft-ietf-p=
we3-redundancy-bit/ballot/</a><br>
&gt;<br>
&gt;<br>
&gt; No IPR declarations have been submitted directly on this I-D.<br>
&gt;<br>
&gt;<br>
&gt; _______________________________________________<br>
&gt; IETF-Announce mailing list<br>
&gt; <a href=3D"mailto:IETF-Announce@ietf.org">IETF-Announce@ietf.org</a><b=
r>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/ietf-announce" target=
=3D"_blank">https://www.ietf.org/mailman/listinfo/ietf-announce</a><br>
&gt;<br>
<br>
<br>
--<br>
For corporate legal information go to:<br>
<br>
<a href=3D"http://www.cisco.com/web/about/doing_business/legal/cri/index.ht=
ml" target=3D"_blank">http://www.cisco.com/web/about/doing_business/legal/c=
ri/index.html</a><br>
<br>
<br>
_______________________________________________<br>
pwe3 mailing list<br>
<a href=3D"mailto:pwe3@ietf.org">pwe3@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/pwe3" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/pwe3</a><br>
</div></div></blockquote></div><br>

--20cf300e543344c30b04baaad673--

From mustapha.aissaoui@alcatel-lucent.com  Wed Mar  7 09:55:45 2012
Return-Path: <mustapha.aissaoui@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 5661621F850B; Wed,  7 Mar 2012 09:55:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.233
X-Spam-Level: 
X-Spam-Status: No, score=-9.233 tagged_above=-999 required=5 tests=[AWL=1.365,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QIarkYKasEXh; Wed,  7 Mar 2012 09:55:44 -0800 (PST)
Received: from ihemail2.lucent.com (ihemail2.lucent.com [135.245.0.35]) by ietfa.amsl.com (Postfix) with ESMTP id 54CF821F8499; Wed,  7 Mar 2012 09:55:44 -0800 (PST)
Received: from usnavsmail3.ndc.alcatel-lucent.com (usnavsmail3.ndc.alcatel-lucent.com [135.3.39.11]) by ihemail2.lucent.com (8.13.8/IER-o) with ESMTP id q27HtfTV014460 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 7 Mar 2012 11:55:41 -0600 (CST)
Received: from USNAVSXCHHUB01.ndc.alcatel-lucent.com (usnavsxchhub01.ndc.alcatel-lucent.com [135.3.39.110]) by usnavsmail3.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id q27Htfff016717 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 7 Mar 2012 11:55:41 -0600
Received: from USNAVSXCHMBSC2.ndc.alcatel-lucent.com ([135.3.39.147]) by USNAVSXCHHUB01.ndc.alcatel-lucent.com ([135.3.39.110]) with mapi; Wed, 7 Mar 2012 11:55:41 -0600
From: "Aissaoui, Mustapha (Mustapha)" <mustapha.aissaoui@alcatel-lucent.com>
To: "Andrew G. Malis" <amalis@gmail.com>
Date: Wed, 7 Mar 2012 11:55:40 -0600
Subject: RE: [PWE3] Last Call: <draft-ietf-pwe3-redundancy-bit-06.txt> (Pseudowire Preferential Forwarding Status Bit) to Proposed Standard
Thread-Topic: [PWE3] Last Call: <draft-ietf-pwe3-redundancy-bit-06.txt> (Pseudowire Preferential Forwarding Status Bit) to Proposed Standard
Thread-Index: Acz8izeZXI9/dkIbSZqtuo9E9fuJLwAADwaw
Message-ID: <5DF53972F7E9134782DCE51624466FE50AD5811DB2@USNAVSXCHMBSC2.ndc.alcatel-lucent.com>
References: <20120307170032.20594.20281.idtracker@ietfa.amsl.com> <4F579F33.7050508@cisco.com> <5DF53972F7E9134782DCE51624466FE50AD5811DAC@USNAVSXCHMBSC2.ndc.alcatel-lucent.com> <CAK+d4xsS9GVrM1u2QPhsfXXK6xhzmQzGDDaVNhqay8VM_eQbaQ@mail.gmail.com>
In-Reply-To: <CAK+d4xsS9GVrM1u2QPhsfXXK6xhzmQzGDDaVNhqay8VM_eQbaQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_5DF53972F7E9134782DCE51624466FE50AD5811DB2USNAVSXCHMBSC_"
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.35
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.11
X-Mailman-Approved-At: Wed, 07 Mar 2012 12:07:42 -0800
Cc: "draft-ietf-pwe3-redundancy-bit@tools.ietf.org" <draft-ietf-pwe3-redundancy-bit@tools.ietf.org>, "pwe3@ietf.org" <pwe3@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "stbryant@cisco.com" <stbryant@cisco.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Mar 2012 17:55:45 -0000

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

makes sense Andy.

Thanks,
Mustapha.

________________________________
From: Andrew G. Malis [mailto:amalis@gmail.com]
Sent: Wednesday, March 07, 2012 12:53 PM
To: Aissaoui, Mustapha (Mustapha)
Cc: stbryant@cisco.com; draft-ietf-pwe3-redundancy-bit@tools.ietf.org; pwe3=
@ietf.org; ietf@ietf.org
Subject: Re: [PWE3] Last Call: <draft-ietf-pwe3-redundancy-bit-06.txt> (Pse=
udowire Preferential Forwarding Status Bit) to Proposed Standard

Mustapha,

You might want to wait for any other LC comments before updating.

Thanks,
Andy

On Wed, Mar 7, 2012 at 9:49 AM, Aissaoui, Mustapha (Mustapha) <mustapha.ais=
saoui@alcatel-lucent.com<mailto:mustapha.aissaoui@alcatel-lucent.com>> wrot=
e:
Ooops. Thank you for pointing this out Stewart. I will make the update and =
publish a new revision.

Mustapha.

-----Original Message-----
From: Stewart Bryant [mailto:stbryant@cisco.com<mailto:stbryant@cisco.com>]
Sent: Wednesday, March 07, 2012 12:48 PM
To: draft-ietf-pwe3-redundancy-bit@tools.ietf.org<mailto:draft-ietf-pwe3-re=
dundancy-bit@tools.ietf.org>
Cc: ietf@ietf.org<mailto:ietf@ietf.org>; pwe3@ietf.org<mailto:pwe3@ietf.org=
>
Subject: Re: Last Call: <draft-ietf-pwe3-redundancy-bit-06.txt> (Pseudowire=
 Preferential Forwarding Status Bit) to Proposed Standard


Authors

There was on point that I notice that you did not address from the AD revie=
w and so I am picking it up as a LC comment:

In section 10 you say:

   "This document makes the following update to the PwOperStatusTC
   textual convention in RFC5542 [8]: "

This update should be recorded in the metadata (top left front page) and it=
 is usual to put a one line note in the abstract.

Stewart



On 07/03/2012 17:00, The IESG wrote:
> The IESG has received a request from the Pseudowire Emulation Edge to
> Edge WG (pwe3) to consider the following document:
> - 'Pseudowire Preferential Forwarding Status Bit'
>    <draft-ietf-pwe3-redundancy-bit-06.txt>  as a Proposed Standard
>
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org<mailto:ietf@ietf.org> mailing lists by 2012-03-21. Exceptio=
nally, comments may
> be sent to iesg@ietf.org<mailto:iesg@ietf.org> instead. In either case, p=
lease retain the
> beginning of the Subject line to allow automated sorting.
>
> Abstract
>
>
>     This document describes a mechanism for standby status signaling of
>     redundant pseudowires (PWs) between their termination points. A set
>     of redundant PWs is configured between provider edge (PE) nodes in
>     single-segment pseudowire (SS-PW) applications, or between
>     terminating provider edge (T-PE) nodes in multi-segment pseudowire
>     (MS-PW) applications.
>
>     In order for the PE/T-PE nodes to indicate the preferred PW to use
>     for forwarding PW packets to one another, a new status bit is needed
>     to indicate a preferential forwarding status of Active or Standby for
>     each PW in a redundant set.
>
>     In addition, a second status bit is defined to allow peer PE nodes to
>     coordinate a switchover operation of the PW.
>
>
>
>
>
>
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-pwe3-redundancy-bit/
>
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-pwe3-redundancy-bit/ballot/
>
>
> No IPR declarations have been submitted directly on this I-D.
>
>
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org<mailto:IETF-Announce@ietf.org>
> https://www.ietf.org/mailman/listinfo/ietf-announce
>


--
For corporate legal information go to:

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


_______________________________________________
pwe3 mailing list
pwe3@ietf.org<mailto:pwe3@ietf.org>
https://www.ietf.org/mailman/listinfo/pwe3


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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" http-equiv=3DContent-Type=
>
<META name=3DGENERATOR content=3D"MSHTML 8.00.6001.19190"></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D954155517-07032012><FONT size=3D2=
=20
face=3DArial>makes sense Andy. </FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D954155517-07032012><FONT size=3D2=
=20
face=3DArial></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D954155517-07032012><FONT size=3D2=
=20
face=3DArial>Thanks,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D954155517-07032012><FONT size=3D2=
=20
face=3DArial>Mustapha.</FONT></SPAN></DIV><BR>
<DIV dir=3Dltr lang=3Den-us class=3DOutlookMessageHeader align=3Dleft>
<HR tabIndex=3D-1>
<FONT size=3D2 face=3DTahoma><B>From:</B> Andrew G. Malis [mailto:amalis@gm=
ail.com]=20
<BR><B>Sent:</B> Wednesday, March 07, 2012 12:53 PM<BR><B>To:</B> Aissaoui,=
=20
Mustapha (Mustapha)<BR><B>Cc:</B> stbryant@cisco.com;=20
draft-ietf-pwe3-redundancy-bit@tools.ietf.org; pwe3@ietf.org;=20
ietf@ietf.org<BR><B>Subject:</B> Re: [PWE3] Last Call:=20
&lt;draft-ietf-pwe3-redundancy-bit-06.txt&gt; (Pseudowire Preferential=20
Forwarding Status Bit) to Proposed Standard<BR></FONT><BR></DIV>
<DIV></DIV>Mustapha,<BR><BR>You might want to wait for any other LC comment=
s=20
before updating.<BR><BR>Thanks,<BR>Andy<BR><BR>
<DIV class=3Dgmail_quote>On Wed, Mar 7, 2012 at 9:49 AM, Aissaoui, Mustapha=
=20
(Mustapha) <SPAN dir=3Dltr>&lt;<A=20
href=3D"mailto:mustapha.aissaoui@alcatel-lucent.com">mustapha.aissaoui@alca=
tel-lucent.com</A>&gt;</SPAN>=20
wrote:<BR>
<BLOCKQUOTE=20
style=3D"BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LE=
FT: 1ex"=20
class=3Dgmail_quote>Ooops. Thank you for pointing this out Stewart. I will =
make=20
  the update and publish a new revision.<BR><SPAN class=3DHOEnZb><FONT=20
  color=3D#888888><BR>Mustapha.<BR></FONT></SPAN>
  <DIV class=3DHOEnZb>
  <DIV class=3Dh5><BR>-----Original Message-----<BR>From: Stewart Bryant=20
  [mailto:<A href=3D"mailto:stbryant@cisco.com">stbryant@cisco.com</A>]<BR>=
Sent:=20
  Wednesday, March 07, 2012 12:48 PM<BR>To: <A=20
  href=3D"mailto:draft-ietf-pwe3-redundancy-bit@tools.ietf.org">draft-ietf-=
pwe3-redundancy-bit@tools.ietf.org</A><BR>Cc:=20
  <A href=3D"mailto:ietf@ietf.org">ietf@ietf.org</A>; <A=20
  href=3D"mailto:pwe3@ietf.org">pwe3@ietf.org</A><BR>Subject: Re: Last Call=
:=20
  &lt;draft-ietf-pwe3-redundancy-bit-06.txt&gt; (Pseudowire Preferential=20
  Forwarding Status Bit) to Proposed Standard<BR><BR><BR>Authors<BR><BR>The=
re=20
  was on point that I notice that you did not address from the AD review an=
d so=20
  I am picking it up as a LC comment:<BR><BR>In section 10 you=20
  say:<BR><BR>&nbsp; &nbsp;"This document makes the following update to the=
=20
  PwOperStatusTC<BR>&nbsp; &nbsp;textual convention in RFC5542 [8]:=20
  "<BR><BR>This update should be recorded in the metadata (top left front p=
age)=20
  and it is usual to put a one line note in the=20
  abstract.<BR><BR>Stewart<BR><BR><BR><BR>On 07/03/2012 17:00, The IESG=20
  wrote:<BR>&gt; The IESG has received a request from the Pseudowire Emulat=
ion=20
  Edge to<BR>&gt; Edge WG (pwe3) to consider the following document:<BR>&gt=
; -=20
  'Pseudowire Preferential Forwarding Status Bit'<BR>&gt; &nbsp;=20
  &nbsp;&lt;draft-ietf-pwe3-redundancy-bit-06.txt&gt; &nbsp;as a Proposed=20
  Standard<BR>&gt;<BR>&gt; The IESG plans to make a decision in the next fe=
w=20
  weeks, and solicits<BR>&gt; final comments on this action. Please send=20
  substantive comments to the<BR>&gt; <A=20
  href=3D"mailto:ietf@ietf.org">ietf@ietf.org</A> mailing lists by 2012-03-=
21.=20
  Exceptionally, comments may<BR>&gt; be sent to <A=20
  href=3D"mailto:iesg@ietf.org">iesg@ietf.org</A> instead. In either case, =
please=20
  retain the<BR>&gt; beginning of the Subject line to allow automated=20
  sorting.<BR>&gt;<BR>&gt; Abstract<BR>&gt;<BR>&gt;<BR>&gt; &nbsp; &nbsp; T=
his=20
  document describes a mechanism for standby status signaling of<BR>&gt; &n=
bsp;=20
  &nbsp; redundant pseudowires (PWs) between their termination points. A=20
  set<BR>&gt; &nbsp; &nbsp; of redundant PWs is configured between provider=
 edge=20
  (PE) nodes in<BR>&gt; &nbsp; &nbsp; single-segment pseudowire (SS-PW)=20
  applications, or between<BR>&gt; &nbsp; &nbsp; terminating provider edge=
=20
  (T-PE) nodes in multi-segment pseudowire<BR>&gt; &nbsp; &nbsp; (MS-PW)=20
  applications.<BR>&gt;<BR>&gt; &nbsp; &nbsp; In order for the PE/T-PE node=
s to=20
  indicate the preferred PW to use<BR>&gt; &nbsp; &nbsp; for forwarding PW=
=20
  packets to one another, a new status bit is needed<BR>&gt; &nbsp; &nbsp; =
to=20
  indicate a preferential forwarding status of Active or Standby for<BR>&gt=
;=20
  &nbsp; &nbsp; each PW in a redundant set.<BR>&gt;<BR>&gt; &nbsp; &nbsp; I=
n=20
  addition, a second status bit is defined to allow peer PE nodes to<BR>&gt=
;=20
  &nbsp; &nbsp; coordinate a switchover operation of the=20
  PW.<BR>&gt;<BR>&gt;<BR>&gt;<BR>&gt;<BR>&gt;<BR>&gt;<BR>&gt; The file can =
be=20
  obtained via<BR>&gt; <A=20
  href=3D"http://datatracker.ietf.org/doc/draft-ietf-pwe3-redundancy-bit/"=
=20
  target=3D_blank>http://datatracker.ietf.org/doc/draft-ietf-pwe3-redundanc=
y-bit/</A><BR>&gt;<BR>&gt;=20
  IESG discussion can be tracked via<BR>&gt; <A=20
  href=3D"http://datatracker.ietf.org/doc/draft-ietf-pwe3-redundancy-bit/ba=
llot/"=20
  target=3D_blank>http://datatracker.ietf.org/doc/draft-ietf-pwe3-redundanc=
y-bit/ballot/</A><BR>&gt;<BR>&gt;<BR>&gt;=20
  No IPR declarations have been submitted directly on this=20
  I-D.<BR>&gt;<BR>&gt;<BR>&gt;=20
  _______________________________________________<BR>&gt; IETF-Announce mai=
ling=20
  list<BR>&gt; <A=20
  href=3D"mailto:IETF-Announce@ietf.org">IETF-Announce@ietf.org</A><BR>&gt;=
 <A=20
  href=3D"https://www.ietf.org/mailman/listinfo/ietf-announce"=20
  target=3D_blank>https://www.ietf.org/mailman/listinfo/ietf-announce</A><B=
R>&gt;<BR><BR><BR>--<BR>For=20
  corporate legal information go to:<BR><BR><A=20
  href=3D"http://www.cisco.com/web/about/doing_business/legal/cri/index.htm=
l"=20
  target=3D_blank>http://www.cisco.com/web/about/doing_business/legal/cri/i=
ndex.html</A><BR><BR><BR>_______________________________________________<BR=
>pwe3=20
  mailing list<BR><A href=3D"mailto:pwe3@ietf.org">pwe3@ietf.org</A><BR><A=
=20
  href=3D"https://www.ietf.org/mailman/listinfo/pwe3"=20
  target=3D_blank>https://www.ietf.org/mailman/listinfo/pwe3</A><BR></DIV><=
/DIV></BLOCKQUOTE></DIV><BR></BODY></HTML>

--_000_5DF53972F7E9134782DCE51624466FE50AD5811DB2USNAVSXCHMBSC_--

From ned+ietf@mauve.mrochek.com  Wed Mar  7 13:47:19 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 6B48D11E80AF for <ietf@ietfa.amsl.com>; Wed,  7 Mar 2012 13:47:19 -0800 (PST)
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.014,  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 GUnEsFDmYBei for <ietf@ietfa.amsl.com>; Wed,  7 Mar 2012 13:47:18 -0800 (PST)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id 5223411E80A3 for <ietf@ietf.org>; Wed,  7 Mar 2012 13:47:18 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OCU4B6UHWG0162U8@mauve.mrochek.com> for ietf@ietf.org; Wed, 7 Mar 2012 13:47:13 -0800 (PST)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OCPMUVDUMO00ZUIL@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Wed, 7 Mar 2012 13:47:09 -0800 (PST)
From: ned+ietf@mauve.mrochek.com
Message-id: <01OCU4B4XQ7000ZUIL@mauve.mrochek.com>
Date: Wed, 07 Mar 2012 11:46:39 -0800 (PST)
Subject: Re: provisioning software, was DNS RRTYPEs, the difficulty with
In-reply-to: "Your message dated Wed, 07 Mar 2012 13:56:55 +0100" <4F575B17.9030502@tana.it>
MIME-version: 1.0
Content-type: TEXT/PLAIN
References: <20120305170938.57919.qmail@joyce.lan> <4F550DA1.8060304@tana.it> <01OCRP6SYT8Q00ZUIL@mauve.mrochek.com> <4F5634F5.5090909@tana.it> <01OCTDEUL9G200ZUIL@mauve.mrochek.com> <4F575B17.9030502@tana.it>
To: Alessandro Vesely <vesely@tana.it>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mrochek.com; s=mauve; t=1331156843; i=@mrochek.com; bh=+A6w4K/R7sHXLdgC7SMl9wVzzUKEEMuBng6C8Bi5Qwk=;  h=From:Cc:Message-id:Date:Subject:In-reply-to:MIME-version: Content-type:References:To; b=qSi8LVmw7b22fNXa5pAocMwxuyHTI+gBDNcVUZHSKQvwSlsA1y0Cb+XWbE297PELN H4IK+HdEVHOwjPNpv8yvJnSqS2205BoR9VvSmtcMzMAPvuzHi/5jImSyWtZ1WEcbJp Y28vB8huUxqKpiATrqkfmDvjyCG2E6lPOipS0ftg=
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, 07 Mar 2012 21:47:19 -0000

> On 07/Mar/12 09:42, ned+ietf@mauve.mrochek.com wrote:
> >
> >> It would still be possible to work around the need for a plugin, e.g.
> >> by depending on some wizard web site, as in John's thought experiment.
> >
> >> For the rest of us, the possibility to install a plugin that takes
> >> care of all the nitty-gritty details, instead of having to wait for
> >> the release and distribution of the next version of BIND, can make the
> >> difference between deploying a new RR type right away and
> >> procrastinating endlessly.
> >
> > You're still not separating the two cases.

> I think I did, however badly.  Let me try by example, assuming my
> server doesn't recognize SPF.  As it's unrecognized, I have to write
> it as such, e.g.

>   TYPE99 \# 12 0B 763D73706631 20 2D613131

OK, now I'm completely confused. What does lack of SPF record support in your
server input format have to to with syntax checking of the *content* of the SPF
record? I can write the record as text or in hex or base64 or whatever format I
want; the issue is looking *inside* the data and either (a) just checking it's
syntax versus (b) checking it and turning it into some kind of tokenized stuff
the DNS server actually serves out.

> > Again, an *optional* plugin to check syntax of a record but not
> > produce any sort of tokenized result is fine,

> Now the plugin can check the syntax and spot the error.  I may correct
> it or not.  If I don't, I'll just serve bad data.  In any case, my
> zone source still contains the line above.  Thus the plugin is optional.

> > a plugin that's *mandatory* to deploy is going to be almost as much
> > of an impediment to deployment as requiring an upgrade. Code is
> > code, and people don't install new code willy-nilly.

Any plugin that's necessary to transform a nontrivial input format into a
tokenized result is effectively mandatory. Sure, you can substitute a
preprocessing script that does the transform and spits out hex or whatever, but
no matter how you do it there's an essential translation component involved in
provisioning those records. You may be able to avoid having that component 
cause the entire server fail, but it's still in the critical path for
setting up those records.

> Possibly, I can also run, say:

>   echo 'SPF "v=spf1 -a11"' | plugin --dump-hex --silent

> and have it dump the TYPE99 line above (without signalling the error,
> since I said --silent).  Then I copy its output and paste it into the
> zone source.

Let's please stop talking about what you can do manually. This isn't about
people whose main provisioning tool is emacs or bind, and who operate their own
servers with full autonomy and report to nobody. This audience doesn't have
issues with any of this stuff.

> Finally, I can enable automatic invocation of the plugin.  That way, I
> can write the SPF record directly in the zone source and have my
> DNS-fictional server do the copy and paste on the fly for me.

> I wouldn't call such thing "mandatory".

Again, it depends on whether or not it's in the critical provisioning
path. A syntax checker isn't, a parser and tokenizer is.

				Ned

From marka@isc.org  Wed Mar  7 13:49:55 2012
Return-Path: <marka@isc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4AE2721F84D9 for <ietf@ietfa.amsl.com>; Wed,  7 Mar 2012 13:49:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.581
X-Spam-Level: 
X-Spam-Status: No, score=-2.581 tagged_above=-999 required=5 tests=[AWL=0.018,  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 vjsYEplavEU4 for <ietf@ietfa.amsl.com>; Wed,  7 Mar 2012 13:49:54 -0800 (PST)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [IPv6:2001:500:60::65]) by ietfa.amsl.com (Postfix) with ESMTP id 08E6721F84D6 for <ietf@ietf.org>; Wed,  7 Mar 2012 13:49:54 -0800 (PST)
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mail.isc.org", Issuer "RapidSSL CA" (not verified)) by mx.ams1.isc.org (Postfix) with ESMTPS id E026A5F984C; Wed,  7 Mar 2012 21:49:29 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (unknown [IPv6:2001:470:1f00:820:d6f:a002:cd07:ed09]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by bikeshed.isc.org (Postfix) with ESMTPSA id 16BC6216C36; Wed,  7 Mar 2012 21:49:27 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (Postfix) with ESMTP id 2833D1E269AE; Thu,  8 Mar 2012 08:49:22 +1100 (EST)
To: "John R. Levine" <johnl@iecc.com>
From: Mark Andrews <marka@isc.org>
References: <20120306044628.87718.qmail@joyce.lan> <77075C8C-04ED-48A2-B501-B2296BCFC8C6@frobbit.se> <01OCRTKK8TSO00ZUIL@mauve.mrochek.com> <alpine.BSF.2.00.1203060950080.10148@joyce.lan> <alpine.LSU.2.00.1203061658110.2756@hermes-2.csi.cam.ac.uk> <alpine.BSF.2.00.1203061203020.14450@joyce.lan> <20120306220911.8B52C1E1DE9F@drugs.dv.isc.org> <alpine.BSF.2.00.1203061711470.25059@joyce.lan> <20120307024247.EF0151E2080D@drugs.dv.isc.org> <alpine.BSF.2.00.1203062148410.34594@joyce.lan> <D468354F-BE26-41D4-9F75-EA10C5189B73@frobbit.se> <20120307075414.6E63A1E23E05@drugs.dv.isc.org> <alpine.BSF.2.00.1203070926260.60146@joyce.lan>
Subject: Re: provisioning software, was DNS RRTYPEs, the difficulty with
In-reply-to: Your message of "07 Mar 2012 10:14:01 CDT." <alpine.BSF.2.00.1203070926260.60146@joyce.lan>
Date: Thu, 08 Mar 2012 08:49:22 +1100
Message-Id: <20120307214922.2833D1E269AE@drugs.dv.isc.org>
Cc: "ietf@ietf.org Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Mar 2012 21:49:55 -0000

In message <alpine.BSF.2.00.1203070926260.60146@joyce.lan>, "John R. Levine" wr
ites:
> Gee, by sheer random walk this has wandered back to the original topic, 
> that provisioning software is the major bar to deploying new RRs.
> 
> > Most provisioning systems really don't care about most of the data
> > they are throwing about.  It may as well be a opaque blob.
> 
> I couldn't disagree more.  Other than my own homebrew system, all the 
> provisioning systems I know support a handful of specific RR types and 
> make it somewhere between painful and impossible to install anything else.
> 
> Godaddy's is a good and very large example of this.  They have a "wizard" 
> to create an SPF record, but it turns out to be a TXT record.  If you want 
> a real type 99 SPF record, you're out of luck.
> 
> Assuming you're not talking about editing zone files with vi, can you give 
> some specific examples of what you're talking about?

Most provisioning systems dump the records into a database and have
some other process extract them from the database and build the
input to the nameserver.  Those database records are also what the
customer updates when they next come back.

One of the problems with provisioning systems is they are mostly
based on a pre RFC 3597 view of the world where you *needed* to
know the type specific presentation format to enter the data.  In
a post RFC 3597 world it is possible to enter any record you want
with a common format.  You can dump that record straight into the
nameserver, nsupdate or any other RFC 3597 aware tool and it will
handle it.

GoDaddy, for example, could handle HIP, SSHFP and IPSECKEY with the
same input dialog if they wanted to by accepting the UNKNOWN record
format.  They could also handle the next type that is invented with
that same dialog box.

Stop asking for type XXXX support and ask for UNKNOWN record support
from your provider.  UNKNOWN record support will handle type XXXX
and anything new that will come along.

By supporting UNKNOWN record format, providers get to know which
types are actually being used by their customers and can then hire
developers to add support for the types that are actually being
used.

Tools to convert between UNKNOWN and type specific representations
will appear.  They are trivial to write.  This is the sort of thing
a 1st year CS student should be able to write as a learning exercise.
I would give the one type to convert for the exercise but that the
level of skill needed.

Take SPF as a example.  If providers had supported UNKNOWN format
then the SPF generation tools would have done UNKNOWN + SPF type
specific rather than TXT + SPF.

Mark

> Regards,
> John Levine, johnl@iecc.com, Primary Perpetrator of "The Internet for Dummies
> ",
> Please consider the environment before reading this e-mail. http://jl.ly
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org

From johnl@iecc.com  Wed Mar  7 14:21:43 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 D341511E8074 for <ietf@ietfa.amsl.com>; Wed,  7 Mar 2012 14:21:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.407
X-Spam-Level: 
X-Spam-Status: No, score=-102.407 tagged_above=-999 required=5 tests=[AWL=0.193, 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 EL+-9dTM5gWu for <ietf@ietfa.amsl.com>; Wed,  7 Mar 2012 14:21:42 -0800 (PST)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 9EEB811E80AF for <ietf@ietf.org>; Wed,  7 Mar 2012 14:21:41 -0800 (PST)
Received: (qmail 36762 invoked from network); 7 Mar 2012 22:21: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:references:mime-version:content-type:vbr-info:user-agent:cleverness; s=8f99.4f57df74.k1203; bh=1pVQoORpJSL2B1Rc5Bq693pneJPZARM2vbRlL6nYQ9E=; b=tV4s2MOkXrHGYNI/qTVl4xov+tb8QTgNbt18LTiflqZGizzJh2O/CMSWCS4WTE4jcd/qhpUe+qbYI1ERqU0v352SoUjfPZxnInoCIxXfmx9MjLQfIQPchN0m6a5BUrNBuJoY5Tu1aSMiuTUzObJ2c9NSyz6cWyU7QeC3AcOLLjE=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Received: (ofmipd 127.0.0.1); 7 Mar 2012 22:21:18 -0000
Date: 7 Mar 2012 17:21:40 -0500
Message-ID: <alpine.BSF.2.00.1203071719100.78429@joyce.lan>
From: "John R. Levine" <johnl@iecc.com>
To: "Mark Andrews" <marka@isc.org>
Subject: Re: provisioning software, was DNS RRTYPEs, the difficulty with
In-Reply-To: <20120307214922.2833D1E269AE@drugs.dv.isc.org>
References: <20120306044628.87718.qmail@joyce.lan> <77075C8C-04ED-48A2-B501-B2296BCFC8C6@frobbit.se> <01OCRTKK8TSO00ZUIL@mauve.mrochek.com> <alpine.BSF.2.00.1203060950080.10148@joyce.lan> <alpine.LSU.2.00.1203061658110.2756@hermes-2.csi.cam.ac.uk> <alpine.BSF.2.00.1203061203020.14450@joyce.lan> <20120306220911.8B52C1E1DE9F@drugs.dv.isc.org> <alpine.BSF.2.00.1203061711470.25059@joyce.lan> <20120307024247.EF0151E2080D@drugs.dv.isc.org> <alpine.BSF.2.00.1203062148410.34594@joyce.lan> <D468354F-BE26-41D4-9F75-EA10C5189B73@frobbit.se> <20120307075414.6E63A1E23E05@drugs.dv.isc.org> <alpine.BSF.2.00.1203070926260.60146@joyce.lan> <20120307214922.2833D1E269AE@drugs.dv.isc.org>
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 Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Mar 2012 22:21:43 -0000

>>> Most provisioning systems really don't care about most of the data
>>> they are throwing about.  It may as well be a opaque blob.  ...

>> Assuming you're not talking about editing zone files with vi, can you give
>> some specific examples of what you're talking about?
>
> Most provisioning systems ...

Hi.  Could you give some concrete examples of DNS provisioning systems 
that let you enter arbitrary RRs?  I've never seen one in the wild, other 
than the one I wrote for myself.

Yes, I know that hypothetically they could do all sorts of stuff.  But 
they don't.

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

From ajs@anvilwalrusden.com  Wed Mar  7 14:39:09 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 A0E6B11E80BC for <ietf@ietfa.amsl.com>; Wed,  7 Mar 2012 14:39:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.474
X-Spam-Level: 
X-Spam-Status: No, score=-3.474 tagged_above=-999 required=5 tests=[AWL=1.125,  BAYES_00=-2.599, GB_I_INVITATION=-2]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id msMrMW4GuVAw for <ietf@ietfa.amsl.com>; Wed,  7 Mar 2012 14:39:09 -0800 (PST)
Received: from mail.yitter.info (mail.yitter.info [208.86.224.201]) by ietfa.amsl.com (Postfix) with ESMTP id 2B80811E8074 for <ietf@ietf.org>; Wed,  7 Mar 2012 14:39:09 -0800 (PST)
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 mail.yitter.info (Postfix) with ESMTPSA id 265131ECB41D for <ietf@ietf.org>; Wed,  7 Mar 2012 22:39:08 +0000 (UTC)
Date: Wed, 7 Mar 2012 17:39:05 -0500
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: Re: provisioning software, was DNS RRTYPEs, the difficulty with
Message-ID: <20120307223904.GW79276@mail.yitter.info>
References: <alpine.LSU.2.00.1203061658110.2756@hermes-2.csi.cam.ac.uk> <alpine.BSF.2.00.1203061203020.14450@joyce.lan> <20120306220911.8B52C1E1DE9F@drugs.dv.isc.org> <alpine.BSF.2.00.1203061711470.25059@joyce.lan> <20120307024247.EF0151E2080D@drugs.dv.isc.org> <alpine.BSF.2.00.1203062148410.34594@joyce.lan> <D468354F-BE26-41D4-9F75-EA10C5189B73@frobbit.se> <20120307075414.6E63A1E23E05@drugs.dv.isc.org> <alpine.BSF.2.00.1203070926260.60146@joyce.lan> <20120307214922.2833D1E269AE@drugs.dv.isc.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20120307214922.2833D1E269AE@drugs.dv.isc.org>
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: Wed, 07 Mar 2012 22:39:09 -0000

On Thu, Mar 08, 2012 at 08:49:22AM +1100, Mark Andrews wrote:

> Take SPF as a example.  If providers had supported UNKNOWN format
> then the SPF generation tools would have done UNKNOWN + SPF type
> specific rather than TXT + SPF.

My father used to have a saying: "If Johnny hadn't died, they wouldn't
have buried him."  Counterfactuals in engineering are just not that
interesting.

But anyway, providers (I am employed by one, FWIW) are not going to
blindly support UNKNOWN on the input side.  That's just an invitation
to behaviour we don't understand and therefore cannot price
correctly.  More importantly, any plan that involves UNKNOWN types
also automatically comes with unknown support costs.  We will be
forced to provide customer support for types we don't even know exist,
and that will necessarily lead to unhappy customers.

A plan something like the one John Levine has proposed is the only
viable one, in my view.

Best,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

From marka@isc.org  Wed Mar  7 14:40:51 2012
Return-Path: <marka@isc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 56F3811E80CA for <ietf@ietfa.amsl.com>; Wed,  7 Mar 2012 14:40:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.582
X-Spam-Level: 
X-Spam-Status: No, score=-2.582 tagged_above=-999 required=5 tests=[AWL=0.017,  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 eTBbqvPUEFmd for <ietf@ietfa.amsl.com>; Wed,  7 Mar 2012 14:40:50 -0800 (PST)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [IPv6:2001:500:60::65]) by ietfa.amsl.com (Postfix) with ESMTP id A9ACE11E8074 for <ietf@ietf.org>; Wed,  7 Mar 2012 14:40:50 -0800 (PST)
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mail.isc.org", Issuer "RapidSSL CA" (not verified)) by mx.ams1.isc.org (Postfix) with ESMTPS id 3004F5F984C; Wed,  7 Mar 2012 22:40:38 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (unknown [IPv6:2001:470:1f00:820:d6f:a002:cd07:ed09]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by bikeshed.isc.org (Postfix) with ESMTPSA id 17AAE216C31; Wed,  7 Mar 2012 22:40:36 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (Postfix) with ESMTP id 26F751E276F0; Thu,  8 Mar 2012 09:40:30 +1100 (EST)
To: "John R. Levine" <johnl@iecc.com>
From: Mark Andrews <marka@isc.org>
References: <20120306044628.87718.qmail@joyce.lan> <77075C8C-04ED-48A2-B501-B2296BCFC8C6@frobbit.se> <01OCRTKK8TSO00ZUIL@mauve.mrochek.com> <alpine.BSF.2.00.1203060950080.10148@joyce.lan> <alpine.LSU.2.00.1203061658110.2756@hermes-2.csi.cam.ac.uk> <alpine.BSF.2.00.1203061203020.14450@joyce.lan> <20120306220911.8B52C1E1DE9F@drugs.dv.isc.org> <alpine.BSF.2.00.1203061711470.25059@joyce.lan> <20120307024247.EF0151E2080D@drugs.dv.isc.org> <alpine.BSF.2.00.1203062148410.34594@joyce.lan> <D468354F-BE26-41D4-9F75-EA10C5189B73@frobbit.se> <20120307075414.6E63A1E23E05@drugs.dv.isc.org> <alpine.BSF.2.00.1203070926260.60146@joyce.lan> <20120307214922.2833D1E269AE@drugs.dv.isc.org> <alpine.BSF.2.00.1203071719100.78429@joyce.lan>
Subject: Re: provisioning software, was DNS RRTYPEs, the difficulty with
In-reply-to: Your message of "07 Mar 2012 17:21:40 CDT." <alpine.BSF.2.00.1203071719100.78429@joyce.lan>
Date: Thu, 08 Mar 2012 09:40:29 +1100
Message-Id: <20120307224030.26F751E276F0@drugs.dv.isc.org>
Cc: "ietf@ietf.org Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Mar 2012 22:40:51 -0000

In message <alpine.BSF.2.00.1203071719100.78429@joyce.lan>, "John R. Levine" wr
ites:
> >>> Most provisioning systems really don't care about most of the data
> >>> they are throwing about.  It may as well be a opaque blob.  ...
> 
> >> Assuming you're not talking about editing zone files with vi, can you give
> >> some specific examples of what you're talking about?
> >
> > Most provisioning systems ...
> 
> Hi.  Could you give some concrete examples of DNS provisioning systems 
> that let you enter arbitrary RRs?  I've never seen one in the wild, other 
> than the one I wrote for myself.
> 
> Yes, I know that hypothetically they could do all sorts of stuff.  But 
> they don't.

I well know they don't because they are still stuck in 1980's think
mode.  It's how do we get then out of 1980's think mode and get
them to use some of the tools that were provided to them nearly a
decade ago now.

How do we apply the clue bat to the CTO and the CEO of these
provisioning providers to get them to come out of the dark ages?

ICANN might be able to do some something.  Lots of their accredited
registrar are also in the provisioning business.

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

From johnl@iecc.com  Wed Mar  7 14:48:04 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 782BA21F8616 for <ietf@ietfa.amsl.com>; Wed,  7 Mar 2012 14:48:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.412
X-Spam-Level: 
X-Spam-Status: No, score=-102.412 tagged_above=-999 required=5 tests=[AWL=0.188, 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 9Ffin7Cq62dl for <ietf@ietfa.amsl.com>; Wed,  7 Mar 2012 14:48:03 -0800 (PST)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id A730B21F8625 for <ietf@ietf.org>; Wed,  7 Mar 2012 14:48:03 -0800 (PST)
Received: (qmail 41509 invoked from network); 7 Mar 2012 22:48:03 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:vbr-info:user-agent:cleverness; s=a21f.4f57e5a3.k1203; bh=Y7qHQrunhm1Ijb1nEcuhMtrHBkOtGgoZPMjAwXIgNfc=; b=ilzfDhEQq4Orny3x0TWKum52Or2NoZXLSwJ0I0Xmj2BQjJFFRdvYnY8XZMvNcz8cb93K8HJqh8n88keSOq2rDVtXn92OnHBlwY9LsoMr13VhpJkJh5eSje0Lpy+z6AGTYQVl9W9qdK7bxWsc6u+wm7xGitCHxDnaOtzsGlWgGFs=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Received: (ofmipd 127.0.0.1); 7 Mar 2012 22:47:40 -0000
Date: 7 Mar 2012 17:48:02 -0500
Message-ID: <alpine.BSF.2.00.1203071747290.78429@joyce.lan>
From: "John R. Levine" <johnl@iecc.com>
To: "Mark Andrews" <marka@isc.org>
Subject: Re: provisioning software, was DNS RRTYPEs, the difficulty with
In-Reply-To: <20120307224030.26F751E276F0@drugs.dv.isc.org>
References: <20120306044628.87718.qmail@joyce.lan> <77075C8C-04ED-48A2-B501-B2296BCFC8C6@frobbit.se> <01OCRTKK8TSO00ZUIL@mauve.mrochek.com> <alpine.BSF.2.00.1203060950080.10148@joyce.lan> <alpine.LSU.2.00.1203061658110.2756@hermes-2.csi.cam.ac.uk> <alpine.BSF.2.00.1203061203020.14450@joyce.lan> <20120306220911.8B52C1E1DE9F@drugs.dv.isc.org> <alpine.BSF.2.00.1203061711470.25059@joyce.lan> <20120307024247.EF0151E2080D@drugs.dv.isc.org> <alpine.BSF.2.00.1203062148410.34594@joyce.lan> <D468354F-BE26-41D4-9F75-EA10C5189B73@frobbit.se> <20120307075414.6E63A1E23E05@drugs.dv.isc.org> <alpine.BSF.2.00.1203070926260.60146@joyce.lan> <20120307214922.2833D1E269AE@drugs.dv.isc.org> <alpine.BSF.2.00.1203071719100.78429@joyce.lan> <20120307224030.26F751E276F0@drugs.dv.isc.org>
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 Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Mar 2012 22:48:04 -0000

>>> Most provisioning systems ...

> I well know they don't because they are still stuck in 1980's think
> mode.  ...

Hi.  Could you give some concrete examples of DNS provisioning systems
that let you enter arbitrary RRs?  I've never seen one in the wild, other
than the one I wrote for myself.

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

From sant9442@gmail.com  Wed Mar  7 14:54:49 2012
Return-Path: <sant9442@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2EF6F11E8088 for <ietf@ietfa.amsl.com>; Wed,  7 Mar 2012 14:54:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.216
X-Spam-Level: 
X-Spam-Status: No, score=-3.216 tagged_above=-999 required=5 tests=[AWL=0.383,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mXvy4Ep+vsNl for <ietf@ietfa.amsl.com>; Wed,  7 Mar 2012 14:54:48 -0800 (PST)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id 22AA221F85E4 for <ietf@ietf.org>; Wed,  7 Mar 2012 14:54:48 -0800 (PST)
Received: by yhpp34 with SMTP id p34so3671847yhp.31 for <ietf@ietf.org>; Wed, 07 Mar 2012 14:54:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=t65JvRbP9h3cerGYp3YhVjzsTaNKz8FC28/SHwsTcmY=; b=etnGvKFB6dzLvpTrJI4sloTMYrluoU6h7XaOAS4r9gEetZflb5lm9xywxc0kLdPaKE GJ3e1GSTKY15SvYazwYcbk2haynTBJ8PGaUWwQcjd2jHjU5JQ9nrASuAe3tfEHCDnGJH JIbRkO3jKGqc+c2NpzxnyMWdhEuWQsZ8msmfTZH9uQXA90JG6JUtZQ48B/jG90FcfW1/ nFLbg2ZX9dC/DKUsy8z0czdWVlUd4/BXtM4TVU1zTpS5Uz+Es/UnHtS4JLPU1nF9c2kp 9IFba0wtR6ZmNvegKDFwVLnZV78YSPdSYpdV2plqwy6vNl7Lbu2+n2NzSP65/sQVL3G7 QkYw==
Received: by 10.236.197.41 with SMTP id s29mr8361683yhn.7.1331160887718; Wed, 07 Mar 2012 14:54:47 -0800 (PST)
Received: from adsl-215-50-126.mia.bellsouth.net (99-3-147-93.lightspeed.miamfl.sbcglobal.net. [99.3.147.93]) by mx.google.com with ESMTPS id v26sm62006380yhk.1.2012.03.07.14.54.45 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 07 Mar 2012 14:54:46 -0800 (PST)
Message-ID: <4F57E77F.3090908@gmail.com>
Date: Wed, 07 Mar 2012 17:55:59 -0500
From: Hector <sant9442@gmail.com>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: "ietf@ietf.org Discussion" <ietf@ietf.org>
Subject: Re: provisioning software, was DNS RRTYPEs, the difficulty with
References: <20120306044628.87718.qmail@joyce.lan>	<77075C8C-04ED-48A2-B501-B2296BCFC8C6@frobbit.se>	<01OCRTKK8TSO00ZUIL@mauve.mrochek.com>	<alpine.BSF.2.00.1203060950080.10148@joyce.lan>	<alpine.LSU.2.00.1203061658110.2756@hermes-2.csi.cam.ac.uk>	<alpine.BSF.2.00.1203061203020.14450@joyce.lan>	<20120306220911.8B52C1E1DE9F@drugs.dv.isc.org>	<alpine.BSF.2.00.1203061711470.25059@joyce.lan>	<20120307024247.EF0151E2080D@drugs.dv.isc.org>	<alpine.BSF.2.00.1203062148410.34594@joyce.lan>	<D468354F-BE26-41D4-9F75-EA10C5189B73@frobbit.se>	<20120307075414.6E63A1E23E05@drugs.dv.isc.org>	<alpine.BSF.2.00.1203070926260.60146@joyce.lan> <20120307214922.2833D1E269AE@drugs.dv.isc.org>
In-Reply-To: <20120307214922.2833D1E269AE@drugs.dv.isc.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Mar 2012 22:54:49 -0000

Mark Andrews wrote:

> Stop asking for type XXXX support and ask for UNKNOWN record support
> from your provider.  UNKNOWN record support will handle type XXXX
> and anything new that will come along.

+1

> By supporting UNKNOWN record format, providers get to know which
> types are actually being used by their customers and can then hire
> developers to add support for the types that are actually being
> used.

+1

> Tools to convert between UNKNOWN and type specific representations
> will appear.  They are trivial to write.  

and most likely its specifics to tied to backend I/O storage methods. 
Not everything is a droppable text file and not everyone is going to 
be using EDLIN, QEDIT, NotePad or some *nix flavor text editor.

Bind hass command line (CLI) tool to automatic the process of addng 
unnamed types, I am trying to find out if Windows DNS 5.0 DNSCMDS 
does, and so far it doesn't.  But Microsoft .NET Provisioning  API 
does support the creation of unnamed resource records.  But from what 
I am reading so far, it seems to have been abandon starting with 
VS2010.  I posted a question in the MSDN Directory Services and 
Network Infrastructure Servers support forums and so far, NADA.

Personally, I thought this was resolved with DNS 5.0 which finally did 
add direct support for the previous wish list "unknown type" SRV and 
other records required for AD (Active Directory) and DNSSEC.

But if the reality is such that the Default Window Server brand (not 
desktop brands) with its already optional installation DNS server 
option, does not come with an out of the box RFC3597 support by now, 
even if undocumented or via a registry option, well, its beating a 
dead horse now. I am all ready to support going with TXT only for SPF.

> Take SPF as a example.  If providers had supported UNKNOWN format
> then the SPF generation tools would have done UNKNOWN + SPF type
> specific rather than TXT + SPF.

+1.

From mrex@sap.com  Wed Mar  7 15:04:36 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 EEDD721F84F6 for <ietf@ietfa.amsl.com>; Wed,  7 Mar 2012 15:04:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.05
X-Spam-Level: 
X-Spam-Status: No, score=-10.05 tagged_above=-999 required=5 tests=[AWL=0.199,  BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wahusbmOxDUR for <ietf@ietfa.amsl.com>; Wed,  7 Mar 2012 15:04:36 -0800 (PST)
Received: from smtpde01.sap-ag.de (smtpde01.sap-ag.de [155.56.68.170]) by ietfa.amsl.com (Postfix) with ESMTP id 3728221F84F3 for <ietf@ietf.org>; Wed,  7 Mar 2012 15:04:24 -0800 (PST)
Received: from mail.sap.corp by smtpde01.sap-ag.de (26) with ESMTP id q27N4H36005402 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 8 Mar 2012 00:04:17 +0100 (MET)
From: Martin Rex <mrex@sap.com>
Message-Id: <201203072304.q27N4GdX000106@fs4113.wdf.sap.corp>
Subject: Re: provisioning software, was DNS RRTYPEs, the difficulty with
To: marka@isc.org (Mark Andrews)
Date: Thu, 8 Mar 2012 00:04:16 +0100 (MET)
In-Reply-To: <20120307060430.5B70E1E22182@drugs.dv.isc.org> from "Mark Andrews" at Mar 7, 12 05:04:30 pm
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-SAP: out
Cc: johnl@iecc.com, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: mrex@sap.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Mar 2012 23:04:37 -0000

Mark Andrews wrote:
> 
> Martin Rex writes:
> > Mark Andrews wrote:
> > > 
> > > "John Levine" writes:
> > > >
> > > > In case it wasn't clear, this is an authoritative server.
> > 
> > If this is about permitted RCODEs here
> > 
> >   http://tools.ietf.org/html/rfc1035#section-4.1.1
> > 
> > then an RCODE of 4 in the response looks like a perfectly valid response
> > for a DNS Server to a query, authoritative or not is irrelevant, and
> > if any client chokes on such an answer, it is likely the client that
> > is broken.
> 
> No, its about what should be generated.  NOTIMP != NOERROR no data.

Maybe you believe that NOTIMP should be limited to unsupported OPCODES only?
But that is definitely not what the spec says.

Generating RCODE 4 (NOTIMP) seems _perfectly_ permissible for a DNS server
when responding to a query for an QCLASS or QTYPE that the server
does not implement.

                4               Not Implemented - The name server does
                                not support the requested kind of query.


1034&1035 are both at document maturity level "Full Standard",
1034 says:

  3.7.1. Standard queries


  A standard query specifies a target domain name (QNAME), query type

  (QTYPE), and query class (QCLASS) and asks for RRs which match.  This
  type of query makes up such a vast majority of DNS queries that we use
  the term "query" to mean standard query unless otherwise specified.  The
  QTYPE and QCLASS fields are each 16 bits long, and are a superset of
  defined types and classes.

1035 says:

  RCODE         Response code - this 4 bit field is set as part of
                responses.  The values have the following
                interpretation:

                0               No error condition

                1               Format error - The name server was
                                unable to interpret the query.

                2               Server failure - The name server was
                                unable to process this query due to a
                                problem with the name server.

                3               Name Error - Meaningful only for
                                responses from an authoritative name
                                server, this code signifies that the
                                domain name referenced in the query does
                                not exist.

                4               Not Implemented - The name server does
                                not support the requested kind of query.

                5               Refused - The name server refuses to
                                perform the specified operation for
                                policy reasons.  For example, a name
                                server may not wish to provide the
                                information to the particular requester,
                                or a name server may not wish to perform
                                a particular operation (e.g., zone
                                transfer) for particular data.

                6-15            Reserved for future use.


-Martin

From marka@isc.org  Wed Mar  7 15:07:10 2012
Return-Path: <marka@isc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5E04521F858E for <ietf@ietfa.amsl.com>; Wed,  7 Mar 2012 15:07:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.583
X-Spam-Level: 
X-Spam-Status: No, score=-3.583 tagged_above=-999 required=5 tests=[AWL=1.016,  BAYES_00=-2.599, GB_I_INVITATION=-2]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p04VcO8TI3zJ for <ietf@ietfa.amsl.com>; Wed,  7 Mar 2012 15:07:09 -0800 (PST)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [IPv6:2001:500:60::65]) by ietfa.amsl.com (Postfix) with ESMTP id EA30921F84F2 for <ietf@ietf.org>; Wed,  7 Mar 2012 15:07:08 -0800 (PST)
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mail.isc.org", Issuer "RapidSSL CA" (not verified)) by mx.ams1.isc.org (Postfix) with ESMTPS id E61B15F98B9; Wed,  7 Mar 2012 23:06:48 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (unknown [IPv6:2001:470:1f00:820:d6f:a002:cd07:ed09]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by bikeshed.isc.org (Postfix) with ESMTPSA id 03B52216C33; Wed,  7 Mar 2012 23:06:46 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (Postfix) with ESMTP id 334FC1E277D3; Thu,  8 Mar 2012 10:06:40 +1100 (EST)
To: Andrew Sullivan <ajs@anvilwalrusden.com>
From: Mark Andrews <marka@isc.org>
References: <alpine.LSU.2.00.1203061658110.2756@hermes-2.csi.cam.ac.uk> <alpine.BSF.2.00.1203061203020.14450@joyce.lan> <20120306220911.8B52C1E1DE9F@drugs.dv.isc.org> <alpine.BSF.2.00.1203061711470.25059@joyce.lan> <20120307024247.EF0151E2080D@drugs.dv.isc.org> <alpine.BSF.2.00.1203062148410.34594@joyce.lan> <D468354F-BE26-41D4-9F75-EA10C5189B73@frobbit.se> <20120307075414.6E63A1E23E05@drugs.dv.isc.org> <alpine.BSF.2.00.1203070926260.60146@joyce.lan> <20120307214922.2833D1E269AE@drugs.dv.isc.org> <20120307223904.GW79276@mail.yitter.info>
Subject: Re: provisioning software, was DNS RRTYPEs, the difficulty with
In-reply-to: Your message of "Wed, 07 Mar 2012 17:39:05 CDT." <20120307223904.GW79276@mail.yitter.info>
Date: Thu, 08 Mar 2012 10:06:39 +1100
Message-Id: <20120307230640.334FC1E277D3@drugs.dv.isc.org>
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, 07 Mar 2012 23:07:10 -0000

In message <20120307223904.GW79276@mail.yitter.info>, Andrew Sullivan writes:
> On Thu, Mar 08, 2012 at 08:49:22AM +1100, Mark Andrews wrote:
> 
> > Take SPF as a example.  If providers had supported UNKNOWN format
> > then the SPF generation tools would have done UNKNOWN + SPF type
> > specific rather than TXT + SPF.
> 
> My father used to have a saying: "If Johnny hadn't died, they wouldn't
> have buried him."  Counterfactuals in engineering are just not that
> interesting.
> 
> But anyway, providers (I am employed by one, FWIW) are not going to
> blindly support UNKNOWN on the input side.  That's just an invitation
> to behaviour we don't understand and therefore cannot price
> correctly.

Charge by records, bytes and queries.  Nameservers don't care beyond that.

> More importantly, any plan that involves UNKNOWN types
> also automatically comes with unknown support costs.

These are "as is" services.  You can add them and remove them.  We don't
provide additional support beyond that.

> We will be
> forced to provide customer support for types we don't even know exist,
> and that will necessarily lead to unhappy customers.

You have unhappy customers now because they can't add record types
they would like to use. 

As for support its possible to support for unknown type what more
can be expected of you beyond "does what is served match what is in
the database" and the pre-dnssec type code roll version of dig shows
that would be possible.

If you are worried about "this type may need special processing"
then provide a simple way for the customer to ask for the type code
to be added and base level support is "unknown record format"
advanced support is "type specific record format".

Mark

bsdi:marka 09:48 {104} % dig -t 46 dv.isc.org

; <<>> DiG 8.3 <<>> -t dv.isc.org 
;; res options: init recurs defnam dnsrch no-tld-query edns0
;; got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 1819
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 6, AUTHORITY: 2, ADDITIONAL: 6
;; QUERY SECTION:
;;	dv.isc.org, type = TYPE46, class = IN

;; ANSWER SECTION:
dv.isc.org.		1H IN TYPE46	\# 94 (	; unknown RR type
	00 06 05 03 00 00 0e 10 4f a1 d8 a5 4f 52 b0 95 ; ........O...OR..
	38 64 02 64 76 03 69 73 63 03 6f 72 67 00 62 7b ; 8d.dv.isc.org.b{
	3d c8 d0 31 85 0a 71 c3 cf 43 69 e4 9c f9 05 34 ; =..1..q..Ci....4
	31 6f d3 8f a3 c4 12 f0 0d 00 61 6f be 35 0b 9e ; 1o........ao.5..
	1c 85 5a 6a 6d e8 15 87 f6 d4 30 ee b4 57 35 e4 ; ..Zjm.....0..W5.
	7c 54 46 ac be 65 b5 48 c2 9f fe 4a 0a 26 )	; |TF..e.H...J.&
dv.isc.org.		1D IN TYPE46	\# 94 (	; unknown RR type
	00 02 05 03 00 01 51 80 4f 8b 89 c2 4f 3c 63 3e ; ......Q.O...O<c>
	38 64 02 64 76 03 69 73 63 03 6f 72 67 00 92 a7 ; 8d.dv.isc.org...
	13 64 9d 31 85 aa 31 28 99 a0 7c af 56 a1 7b 0c ; .d.1..1(..|.V.{.
	8f 99 4d bc c0 a2 38 b0 92 0f ed fc 77 fc f5 f8 ; ..M...8.....w...
	bb ff 38 8e f0 e2 a6 08 65 8a 3b 98 4b ee e1 ea ; ..8.....e.;.K...
	5a e8 9f 71 4d 41 10 ba f2 84 58 a8 5e 14 )	; Z..qMA....X.^.
dv.isc.org.		1D IN TYPE46	\# 94 (	; unknown RR type
	00 0f 05 03 00 01 51 80 4f 8b 89 c2 4f 3c 63 3e ; ......Q.O...O<c>
	38 64 02 64 76 03 69 73 63 03 6f 72 67 00 23 71 ; 8d.dv.isc.org.#q
	d1 ff e6 08 6d a6 6c 4e 94 92 c7 83 e5 21 23 f7 ; ....m.lN.....!#.
	37 58 51 b5 0f f6 a2 d6 68 6b 83 8e 73 fb 46 b0 ; 7XQ.....hk..s.F.
	e5 c3 93 7b 5f 4f 79 9f ee 14 9e 7f 4e 8a e2 65 ; ...{_Oy.....N..e
	55 e4 99 d8 14 64 43 4a b6 9e ac 90 1c ee )	; U....dCJ......
dv.isc.org.		1D IN TYPE46	\# 94 (	; unknown RR type
	00 2f 05 03 00 01 51 80 4f 96 dc 75 4f 47 bd 1c ; ./....Q.O..uOG..
	38 64 02 64 76 03 69 73 63 03 6f 72 67 00 7a b5 ; 8d.dv.isc.org.z.
	3b 7f 55 0d 46 ca 29 29 9d 3c 93 74 fd b5 96 35 ; ;.U.F.)).<.t...5
	76 d4 65 18 fe 8a c2 17 42 e2 0a ba 38 9f ea 96 ; v.e.....B...8...
	5f 84 cc f0 6e df a2 da 83 c9 40 13 da e6 8c 3a ; _...n.....@....:
	66 3c 7f 4e 92 6b d5 cc e0 5f 8a f5 49 be )	; f<.N.k..._..I.
dv.isc.org.		1D IN TYPE46	\# 158 (	; unknown RR type
	00 30 05 03 00 01 51 80 4f 8b 9e 5a 4f 3c 79 a8 ; .0....Q.O..ZO<y.
	28 30 02 64 76 03 69 73 63 03 6f 72 67 00 24 51 ; (0.dv.isc.org.$Q
	3c 2c 11 00 3f 77 aa ea 5f 94 f7 fc f6 9a 97 af ; <,..?w.._.......
	58 29 ef 76 3d a7 4b ab ea 90 f4 15 ac 22 7c 27 ; X).v=.K......"|'
	b2 cc e6 8b 1e 6b f9 b0 ba c8 7c 49 60 ed a8 4d ; .....k....|I`..M
	89 1d c6 c4 f0 e9 a5 16 5f 4e ad 59 17 5d cf ce ; ........_N.Y.]..
	79 a3 8a 81 8b 06 30 12 c4 27 8d 87 7a 0a 7f d5 ; y.....0..'..z...
	65 2e 1e 63 35 98 6c 38 dc 0a e0 75 40 1d 0b 75 ; e..c5.l8...u@..u
	51 b6 cb 6d a7 b8 08 6f 46 f7 2a bf c5 7b 3c 56 ; Q..m...oF.*..{<V
	5b 84 17 fd a4 43 22 dd b0 99 db c2 9f 33 )	; [....C"......3
dv.isc.org.		1D IN TYPE46	\# 94 (	; unknown RR type
	00 30 05 03 00 01 51 80 4f 8b 9e 5a 4f 3c 79 a8 ; .0....Q.O..ZO<y.
	38 64 02 64 76 03 69 73 63 03 6f 72 67 00 20 8e ; 8d.dv.isc.org. .
	e1 b2 e5 5c e9 ec b8 96 d8 06 ae c1 b6 91 19 6c ; ...\...........l
	6e f2 01 98 92 e5 4a af 9a f4 cf 5c 2d bc b9 5b ; n.....J....\-..[
	c0 19 7f f6 35 ee 16 fd 0b 52 ff ac d8 aa 96 6f ; ....5....R.....o
	4f 26 0d c4 6d eb c2 ee 4d 89 39 86 8b 1e )	; O&..m...M.9...

;; AUTHORITY SECTION:
dv.isc.org.		1D IN NS	bsdi1.dv.isc.org.
dv.isc.org.		1D IN NS	drugs.dv.isc.org.

;; ADDITIONAL SECTION:
bsdi1.dv.isc.org.	1D IN A		192.168.191.233
drugs.dv.isc.org.	1H IN A		192.168.191.240
drugs.dv.isc.org.	1H IN A		192.168.191.223
drugs.dv.isc.org.	1H IN AAAA	2001:470:1f00:820:ea06:88ff:fef3:4f9c
drugs.dv.isc.org.	1H IN AAAA	2001:470:1f00:820:6233:4bff:fe01:7585
; EDNS: version: 0, udp=4096, flags=0000

;; Total query time: 46 msec
;; FROM: bsdi.dv.isc.org to SERVER: 127.0.0.1
;; WHEN: Thu Mar  8 09:48:51 2012
;; MSG SIZE  sent: 39  rcvd: 883

bsdi:marka 09:48 {105} %

> A plan something like the one John Levine has proposed is the only
> viable one, in my view.
> 
> Best,
> 
> A
> 
> -- 
> Andrew Sullivan
> ajs@anvilwalrusden.com
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org

From marka@isc.org  Wed Mar  7 15:28:06 2012
Return-Path: <marka@isc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 108E611E808F for <ietf@ietfa.amsl.com>; Wed,  7 Mar 2012 15:28:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.634
X-Spam-Level: 
X-Spam-Status: No, score=-2.634 tagged_above=-999 required=5 tests=[AWL=-0.035, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZBylJPjL57j4 for <ietf@ietfa.amsl.com>; Wed,  7 Mar 2012 15:28:05 -0800 (PST)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [IPv6:2001:500:60::65]) by ietfa.amsl.com (Postfix) with ESMTP id 3D30911E8072 for <ietf@ietf.org>; Wed,  7 Mar 2012 15:28:05 -0800 (PST)
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mail.isc.org", Issuer "RapidSSL CA" (not verified)) by mx.ams1.isc.org (Postfix) with ESMTPS id BF11D5F9887; Wed,  7 Mar 2012 23:27:41 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (unknown [IPv6:2001:470:1f00:820:d6f:a002:cd07:ed09]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by bikeshed.isc.org (Postfix) with ESMTPSA id 60818216C31; Wed,  7 Mar 2012 23:27:39 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (Postfix) with ESMTP id 7A20F1E27B66; Thu,  8 Mar 2012 10:27:33 +1100 (EST)
To: mrex@sap.com
From: Mark Andrews <marka@isc.org>
References: <201203072304.q27N4GdX000106@fs4113.wdf.sap.corp>
Subject: Re: provisioning software, was DNS RRTYPEs, the difficulty with
In-reply-to: Your message of "Thu, 08 Mar 2012 00:04:16 BST." <201203072304.q27N4GdX000106@fs4113.wdf.sap.corp>
Date: Thu, 08 Mar 2012 10:27:33 +1100
Message-Id: <20120307232733.7A20F1E27B66@drugs.dv.isc.org>
Cc: johnl@iecc.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, 07 Mar 2012 23:28:06 -0000

In message <201203072304.q27N4GdX000106@fs4113.wdf.sap.corp>, Martin Rex writes
:
> Mark Andrews wrote:
> > 
> > Martin Rex writes:
> > > Mark Andrews wrote:
> > > > 
> > > > "John Levine" writes:
> > > > >
> > > > > In case it wasn't clear, this is an authoritative server.
> > > 
> > > If this is about permitted RCODEs here
> > > 
> > >   http://tools.ietf.org/html/rfc1035#section-4.1.1
> > > 
> > > then an RCODE of 4 in the response looks like a perfectly valid response
> > > for a DNS Server to a query, authoritative or not is irrelevant, and
> > > if any client chokes on such an answer, it is likely the client that
> > > is broken.
> > 
> > No, its about what should be generated.  NOTIMP != NOERROR no data.
> 
> Maybe you believe that NOTIMP should be limited to unsupported OPCODES only?
> But that is definitely not what the spec says.

Yet someone else that can't count beyond 1035.
 
> Generating RCODE 4 (NOTIMP) seems _perfectly_ permissible for a DNS server
> when responding to a query for an QCLASS or QTYPE that the server
> does not implement.
> 
>                 4               Not Implemented - The name server does
>                                 not support the requested kind of query.
> 
> 
> 1034&1035 are both at document maturity level "Full Standard",
> 1034 says:
> 
>   3.7.1. Standard queries
> 
> 
>   A standard query specifies a target domain name (QNAME), query type
> 
>   (QTYPE), and query class (QCLASS) and asks for RRs which match.  This
>   type of query makes up such a vast majority of DNS queries that we use
>   the term "query" to mean standard query unless otherwise specified.  The
>   QTYPE and QCLASS fields are each 16 bits long, and are a superset of
>   defined types and classes.
> 
> 1035 says:
> 
>   RCODE         Response code - this 4 bit field is set as part of
>                 responses.  The values have the following
>                 interpretation:
> 
>                 0               No error condition
> 
>                 1               Format error - The name server was
>                                 unable to interpret the query.
> 
>                 2               Server failure - The name server was
>                                 unable to process this query due to a
>                                 problem with the name server.
> 
>                 3               Name Error - Meaningful only for
>                                 responses from an authoritative name
>                                 server, this code signifies that the
>                                 domain name referenced in the query does
>                                 not exist.
> 
>                 4               Not Implemented - The name server does
>                                 not support the requested kind of query.
> 
>                 5               Refused - The name server refuses to
>                                 perform the specified operation for
>                                 policy reasons.  For example, a name
>                                 server may not wish to provide the
>                                 information to the particular requester,
>                                 or a name server may not wish to perform
>                                 a particular operation (e.g., zone
>                                 transfer) for particular data.
> 
>                 6-15            Reserved for future use.
> 
> 
> -Martin
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org

From msk@cloudmark.com  Wed Mar  7 16:44:10 2012
Return-Path: <msk@cloudmark.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2C64A11E8085 for <ietf@ietfa.amsl.com>; Wed,  7 Mar 2012 16:44:10 -0800 (PST)
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 tg+Ksoc3qcdC for <ietf@ietfa.amsl.com>; Wed,  7 Mar 2012 16:44:09 -0800 (PST)
Received: from ht1-outbound.cloudmark.com (ht1-outbound.cloudmark.com [72.5.239.25]) by ietfa.amsl.com (Postfix) with ESMTP id AAB4F11E8080 for <ietf@ietf.org>; Wed,  7 Mar 2012 16:44:09 -0800 (PST)
Received: from EXCH-MBX901.corp.cloudmark.com ([fe80::addf:849a:f71c:4a82]) by EXCH-HTCAS901.corp.cloudmark.com ([fe80::2966:6846:8d89:4681%12]) with mapi id 14.01.0355.002; Wed, 7 Mar 2012 16:44:09 -0800
From: "Murray S. Kucherawy" <msk@cloudmark.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: provisioning software, was DNS RRTYPEs, the difficulty with
Thread-Topic: provisioning software, was DNS RRTYPEs, the difficulty with
Thread-Index: AQHM/LaejL91hLxbakSZS7QQB//GaZZfeoG+gAAT7iA=
Date: Thu, 8 Mar 2012 00:44:09 +0000
Message-ID: <9452079D1A51524AA5749AD23E00392807EFEF@exch-mbx901.corp.cloudmark.com>
References: <201203072304.q27N4GdX000106@fs4113.wdf.sap.corp> <20120307232733.7A20F1E27B66@drugs.dv.isc.org>
In-Reply-To: <20120307232733.7A20F1E27B66@drugs.dv.isc.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.20.2.121]
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, 08 Mar 2012 00:44:10 -0000

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of M=
ark Andrews
> Sent: Wednesday, March 07, 2012 3:28 PM
> To: mrex@sap.com
> Cc: johnl@iecc.com; ietf@ietf.org
> Subject: Re: provisioning software, was DNS RRTYPEs, the difficulty with
>=20
> > Maybe you believe that NOTIMP should be limited to unsupported OPCODES =
only?
> > But that is definitely not what the spec says.
>=20
> Yet someone else that can't count beyond 1035.

Weren't you the one that said "Actually it is STD 13.  Get over it." earlie=
r in this thread?

I looked at least at the titles of all the documents that update 1035, and =
none of them appear to be related to the above.  So where should we be look=
ing?

-MSK

From marka@isc.org  Wed Mar  7 18:10:48 2012
Return-Path: <marka@isc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8F77D21E803F for <ietf@ietfa.amsl.com>; Wed,  7 Mar 2012 18:10:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.631
X-Spam-Level: 
X-Spam-Status: No, score=-2.631 tagged_above=-999 required=5 tests=[AWL=-0.032, 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 yVJEIZ41AWjF for <ietf@ietfa.amsl.com>; Wed,  7 Mar 2012 18:10:48 -0800 (PST)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [IPv6:2001:500:60::65]) by ietfa.amsl.com (Postfix) with ESMTP id F39F521E8020 for <ietf@ietf.org>; Wed,  7 Mar 2012 18:10:47 -0800 (PST)
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mail.isc.org", Issuer "RapidSSL CA" (not verified)) by mx.ams1.isc.org (Postfix) with ESMTPS id E0ACA5F989F; Thu,  8 Mar 2012 02:10:33 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (unknown [IPv6:2001:470:1f00:820:d6f:a002:cd07:ed09]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by bikeshed.isc.org (Postfix) with ESMTPSA id A6FA5216C33; Thu,  8 Mar 2012 02:10:28 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (Postfix) with ESMTP id 560681E29350; Thu,  8 Mar 2012 13:10:24 +1100 (EST)
To: "Murray S. Kucherawy" <msk@cloudmark.com>
From: Mark Andrews <marka@isc.org>
References: <201203072304.q27N4GdX000106@fs4113.wdf.sap.corp> <20120307232733.7A20F1E27B66@drugs.dv.isc.org> <9452079D1A51524AA5749AD23E00392807EFEF@exch-mbx901.corp.cloudmark.com>
Subject: Re: provisioning software, was DNS RRTYPEs, the difficulty with
In-reply-to: Your message of "Thu, 08 Mar 2012 00:44:09 -0000." <9452079D1A51524AA5749AD23E00392807EFEF@exch-mbx901.corp.cloudmark.com>
Date: Thu, 08 Mar 2012 13:10:24 +1100
Message-Id: <20120308021024.560681E29350@drugs.dv.isc.org>
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Mar 2012 02:10:48 -0000

In message <9452079D1A51524AA5749AD23E00392807EFEF@exch-mbx901.corp.cloudmark.c
om>, "Murray S. Kucherawy" writes:
> > -----Original Message-----
> > From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of Mar
> k Andrews
> > Sent: Wednesday, March 07, 2012 3:28 PM
> > To: mrex@sap.com
> > Cc: johnl@iecc.com; ietf@ietf.org
> > Subject: Re: provisioning software, was DNS RRTYPEs, the difficulty with
> > 
> > > Maybe you believe that NOTIMP should be limited to unsupported OPCODES on
> ly?
> > > But that is definitely not what the spec says.
> > 
> > Yet someone else that can't count beyond 1035.
> 
> Weren't you the one that said "Actually it is STD 13.  Get over it." earlier 
> in this thread?

Randy claimed that presentation formats were not standardised.  They
are.  Randy and others claimed that the presentation formats were
owned by BIND and they are not.

I never claimed that STD 13 was the be all and end all w.r.t. DNS.

STD 13 didn't follow the normal process required to make a STD.
There are lots of corrections to STD 13 in the RFC series.

> I looked at least at the titles of all the documents that update 1035, and no
> ne of them appear to be related to the above.  So where should we be looking?
> 
> -MSK
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org

From mrex@sap.com  Wed Mar  7 19:20:00 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 2D14C21E8029 for <ietf@ietfa.amsl.com>; Wed,  7 Mar 2012 19:20:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.052
X-Spam-Level: 
X-Spam-Status: No, score=-10.052 tagged_above=-999 required=5 tests=[AWL=0.197, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id M8MTEcnXG4zi for <ietf@ietfa.amsl.com>; Wed,  7 Mar 2012 19:19:59 -0800 (PST)
Received: from smtpde02.sap-ag.de (smtpde02.sap-ag.de [155.56.68.140]) by ietfa.amsl.com (Postfix) with ESMTP id 0A6AA21E800F for <ietf@ietf.org>; Wed,  7 Mar 2012 19:19:58 -0800 (PST)
Received: from mail.sap.corp by smtpde02.sap-ag.de (26) with ESMTP id q283JsD0028575 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 8 Mar 2012 04:19:54 +0100 (MET)
From: Martin Rex <mrex@sap.com>
Message-Id: <201203080319.q283JrrD014874@fs4113.wdf.sap.corp>
Subject: Re: provisioning software, was DNS RRTYPEs, the difficulty with
To: marka@isc.org (Mark Andrews)
Date: Thu, 8 Mar 2012 04:19:53 +0100 (MET)
In-Reply-To: <20120308021024.560681E29350@drugs.dv.isc.org> from "Mark Andrews" at Mar 8, 12 01:10:24 pm
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
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: Thu, 08 Mar 2012 03:20:00 -0000

Mark Andrews wrote:
> 
> Randy claimed that presentation formats were not standardised.  They
> are.  Randy and others claimed that the presentation formats were
> owned by BIND and they are not.
> 
> I never claimed that STD 13 was the be all and end all w.r.t. DNS.
> 
> STD 13 didn't follow the normal process required to make a STD.

That does not matter here.  By assigning the "full standard" document
maturity label to rfc1034/rfc1035 


>
> There are lots of corrections to STD 13 in the RFC series.

That is a misunderstanding of the standards process.  The only corrections
to rfc1034/rfc1035 that exist are those that have been filed as errata
and confirmed (accessible with the Errata URL here):
    http://tools.ietf.org/html/rfc1034
    http://tools.ietf.org/html/rfc1035

But even the posted erratas are "soft" and not visible here:

    http://tools.ietf.org/html/std13

The only document that could be reasonably expected to be "considered"
be a new implementation is rfc2181 (plus maybe rfc4343), although
you have to keep in mind that neither of this is mentioned by STD13.



Btw. the updates metadata on rfc1035 looks like a big mess to me.
Expecting *anyone* to read all of the documents and merge them
in their heads while implementing is completely unrealistic.

The normal implementation approach is to use the base specification
plus a "clarifications" document if one exists, implement the mandatory
parts of that, and ship the result as a first step.  As a second step,
depending on requirements and funding/resouces, selected optional features
from the base spec and from other optional protocol extensions may get added.


> 
> > I looked at least at the titles of all the documents that update 1035,
> > and none of them appear to be related to the above.  So where should
> > we be looking?

To answer the question "does my client have to expect and cope gracefully
with an RCODE 4 response", only 1034/1035 and the filed erratas are relevant.


-Martin

From fanf2@hermes.cam.ac.uk  Thu Mar  8 06:02:20 2012
Return-Path: <fanf2@hermes.cam.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8294D21F867E for <ietf@ietfa.amsl.com>; Thu,  8 Mar 2012 06:02:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.45
X-Spam-Level: 
X-Spam-Status: No, score=-6.45 tagged_above=-999 required=5 tests=[AWL=0.149,  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 soIwgmd0G4o6 for <ietf@ietfa.amsl.com>; Thu,  8 Mar 2012 06:02:17 -0800 (PST)
Received: from ppsw-41.csi.cam.ac.uk (ppsw-41.csi.cam.ac.uk [131.111.8.141]) by ietfa.amsl.com (Postfix) with ESMTP id C8B3C21F8674 for <ietf@ietf.org>; Thu,  8 Mar 2012 06:02:16 -0800 (PST)
X-Cam-AntiVirus: no malware found
X-Cam-SpamDetails: not scanned
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
Received: from hermes-2.csi.cam.ac.uk ([131.111.8.54]:45769) by ppsw-41.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.156]:25) with esmtpa (EXTERNAL:fanf2) id 1S5dv5-00004w-SN (Exim 4.72) (return-path <fanf2@hermes.cam.ac.uk>); Thu, 08 Mar 2012 14:02:15 +0000
Received: from fanf2 (helo=localhost) by hermes-2.csi.cam.ac.uk (hermes.cam.ac.uk) with local-esmtp id 1S5dv5-0005hi-OV (Exim 4.67) (return-path <fanf2@hermes.cam.ac.uk>); Thu, 08 Mar 2012 14:02:15 +0000
Date: Thu, 8 Mar 2012 14:02:15 +0000
From: Tony Finch <dot@dotat.at>
X-X-Sender: fanf2@hermes-2.csi.cam.ac.uk
To: "Murray S. Kucherawy" <msk@cloudmark.com>
Subject: RE: provisioning software, was DNS RRTYPEs, the difficulty with
In-Reply-To: <9452079D1A51524AA5749AD23E00392807EFEF@exch-mbx901.corp.cloudmark.com>
Message-ID: <alpine.LSU.2.00.1203081346470.2756@hermes-2.csi.cam.ac.uk>
References: <201203072304.q27N4GdX000106@fs4113.wdf.sap.corp> <20120307232733.7A20F1E27B66@drugs.dv.isc.org> <9452079D1A51524AA5749AD23E00392807EFEF@exch-mbx901.corp.cloudmark.com>
User-Agent: Alpine 2.00 (LSU 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: Tony Finch <fanf2@hermes.cam.ac.uk>
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Mar 2012 14:02:20 -0000

Murray S. Kucherawy <msk@cloudmark.com> wrote:

> I looked at least at the titles of all the documents that update 1035,
> and none of them appear to be related to the above.  So where should we
> be looking?

The only thing I have found that implies NOTIMP doesn't apply to queries
for unknown RR types is in RFC 4074, "Common Misbehavior Against DNS
Queries for IPv6 Addresses":

4.3.  Return Other Erroneous Codes

   Other authoritative servers return a response with erroneous response
   codes other than RCODE 3 ("Name Error").  One such RCODE is 4 ("Not
   Implemented"), indicating that the servers do not support the
   requested type of query.

But I guess that NOTIMP *would* be an appropriate response if the request
is for an unknown QTYPE between 128 and 255.

Tony.
-- 
f.anthony.n.finch  <dot@dotat.at>  http://dotat.at/
Trafalgar: Mainly northeasterly 4 or 5, occasionally 6 in southeast Fitzroy.
Moderate, becoming rough or very rough except in southeast Trafalgar. Fair.
Good, occasionally poor.

From fanf2@hermes.cam.ac.uk  Thu Mar  8 06:06:27 2012
Return-Path: <fanf2@hermes.cam.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8679821F8691 for <ietf@ietfa.amsl.com>; Thu,  8 Mar 2012 06:06:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.454
X-Spam-Level: 
X-Spam-Status: No, score=-6.454 tagged_above=-999 required=5 tests=[AWL=0.145,  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 YjgHBcyQYT9V for <ietf@ietfa.amsl.com>; Thu,  8 Mar 2012 06:06:26 -0800 (PST)
Received: from ppsw-51.csi.cam.ac.uk (ppsw-51.csi.cam.ac.uk [131.111.8.151]) by ietfa.amsl.com (Postfix) with ESMTP id 66A5F21F8685 for <ietf@ietf.org>; Thu,  8 Mar 2012 06:06:26 -0800 (PST)
X-Cam-AntiVirus: no malware found
X-Cam-SpamDetails: not scanned
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
Received: from hermes-2.csi.cam.ac.uk ([131.111.8.54]:44694) by ppsw-51.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.158]:25) with esmtpa (EXTERNAL:fanf2) id 1S5dyy-0001eG-ZO (Exim 4.72) (return-path <fanf2@hermes.cam.ac.uk>); Thu, 08 Mar 2012 14:06:16 +0000
Received: from fanf2 (helo=localhost) by hermes-2.csi.cam.ac.uk (hermes.cam.ac.uk) with local-esmtp id 1S5dyy-0006W6-QC (Exim 4.67) (return-path <fanf2@hermes.cam.ac.uk>); Thu, 08 Mar 2012 14:06:16 +0000
Date: Thu, 8 Mar 2012 14:06:16 +0000
From: Tony Finch <dot@dotat.at>
X-X-Sender: fanf2@hermes-2.csi.cam.ac.uk
To: Martin Rex <mrex@sap.com>
Subject: Re: provisioning software, was DNS RRTYPEs, the difficulty with
In-Reply-To: <201203080319.q283JrrD014874@fs4113.wdf.sap.corp>
Message-ID: <alpine.LSU.2.00.1203081403490.2756@hermes-2.csi.cam.ac.uk>
References: <201203080319.q283JrrD014874@fs4113.wdf.sap.corp>
User-Agent: Alpine 2.00 (LSU 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: Tony Finch <fanf2@hermes.cam.ac.uk>
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Mar 2012 14:06:27 -0000

Martin Rex <mrex@sap.com> wrote:
>
> Btw. the updates metadata on rfc1035 looks like a big mess to me.
> Expecting *anyone* to read all of the documents and merge them
> in their heads while implementing is completely unrealistic.

http://blog.nominet.org.uk/tech/2010/05/24/436/ - DNS RFC dependency graphs

Tony.
-- 
f.anthony.n.finch  <dot@dotat.at>  http://dotat.at/
Hebrides, Bailey, Fair Isle: West or southwest 6 to gale 8, occasionally
severe gale 9. High or very high. Rain or squally showers. Moderate or good,
occasionally poor.

From jari.arkko@piuha.net  Thu Mar  8 09:25:39 2012
Return-Path: <jari.arkko@piuha.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7B21321F85C5; Thu,  8 Mar 2012 09:25:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.453
X-Spam-Level: 
X-Spam-Status: No, score=-102.453 tagged_above=-999 required=5 tests=[AWL=0.145, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gos0ai1FlI2c; Thu,  8 Mar 2012 09:25:38 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by ietfa.amsl.com (Postfix) with ESMTP id 3EFD621F858F; Thu,  8 Mar 2012 09:25:37 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 394BE2DA0D; Thu,  8 Mar 2012 19:25:35 +0200 (EET)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CmC1LCzarC0J; Thu,  8 Mar 2012 19:25:33 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id EC1E72CC3C; Thu,  8 Mar 2012 19:25:32 +0200 (EET)
Message-ID: <4F58EB8C.1000700@piuha.net>
Date: Thu, 08 Mar 2012 19:25:32 +0200
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0) Gecko/20120129 Thunderbird/10.0
MIME-Version: 1.0
To: John Scudder <jgs@juniper.net>
Subject: Re: [lisp] WG Review: Recharter of Locator/ID Separation Protocol (lisp)
References: <20120214222316.CF29521E800E@ietfa.amsl.com> <201202152131.q1FLVB9E028114@cichlid.raleigh.ibm.com> <EF3C34EB-C0AA-45F2-ADE0-407CEF5172DD@juniper.net> <4F3E4EDB.7070509@piuha.net> <0E0C6A25-FBA6-4E11-9E89-DEBFFCF41108@juniper.net>
In-Reply-To: <0E0C6A25-FBA6-4E11-9E89-DEBFFCF41108@juniper.net>
Content-Type: multipart/mixed; boundary="------------080007080800030309000004"
Cc: "iesg@ietf.org IESG" <iesg@ietf.org>, "ietf@ietf.org list" <ietf@ietf.org>, "lisp@ietf.org" <lisp@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Mar 2012 17:25:39 -0000

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

Thanks for your feedback, John. Would a modified charter with these changes work for you:

Jari


--------------080007080800030309000004
Content-Type: text/plain;
 name="charter-as-modified.txt"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
 filename="charter-as-modified.txt"

Locator/ID Separation Protocol (lisp)
-------------------------------------
Current Status: Active
Last updated: 2012-03-08

 Chairs:
     Joel Halpern <jmh@joelhalpern.com>
     Terry Manderson <terry.manderson@icann.org>

 Internet Area Directors:
     Ralph Droms <rdroms.ietf@gmail.com>
     Jari Arkko <jari.arkko@piuha.net>

 Internet Area Advisor:
     Jari Arkko <jari.arkko@piuha.net>

 Secretaries:
     Wassim Haddad <Wassim.Haddad@ericsson.com>
     Luigi Iannone <luigi@net.t-labs.tu-berlin.de>

 Mailing Lists:
     General Discussion: lisp@ietf.org
     To Subscribe:       https://www.ietf.org/mailman/listinfo/lisp
     Archive:            http://www.ietf.org/mail-archive/web/lisp/current/maillist.html

Description of Working Group:

The IAB's October 2006 Routing and Addressing Workshop (RFC 4984)
rekindled interest in scalable routing and addressing architectures for
the Internet. Among the many issues driving this renewed interest are
concerns about the scalability of the routing system. Since the IAB
workshop, several proposals have emerged which attempt to address the
concerns expressed there and elsewhere. In general, these proposals are
based on the "locator/identifier separation".

The basic idea behind the separation is that the Internet architecture
combines two functions, routing locators, (where you are attached to the
network) and identifiers (who you are) in one number space: The IP
address. Proponents of the separation architecture postulate that
splitting these functions apart will yield several advantages, including
improved scalability for the routing system. The separation aims to
decouple locators and identifiers, thus allowing for efficient
aggregation of the routing locator space and providing persistent
identifiers in the identifier space.

A number of approaches are being looked at in parallel in other
contexts. The IRTF RRG examined several proposals, some of which were
published as IRTF-track Experimental RFCs.

The LISP WG has completed the first set of Experimental RFCs
describing the Locator/ID Separation Protocol. LISP requires no
changes to end-systems or to routers that do not directly participate
in the LISP deployment. LISP aims for an incrementally deployable
protocol.

The LISP WG is chartered to continue work on the LISP base protocol, completing
the ongoing work, and any items which directly impact LISP protocol
structures and which are related to using LISP for improving Internet routing
scalability. Specifically, the group will work on:

- Architecture description: This document will describe the
  architecture of the entire LISP system, making it easier to read the
  rest of the LISP specifications and providing a basis for discussion
  about the details of the LISP protocols.

- Deployment models: This document will describe what kind of
  deployments can be expected for LISP, and give operational advice on
  how they can be set up.

- A description of the impacts of LISP: This document will describe
  the problems that LISP is intended to address and the impacts that
  employing LISP has. While the work on LISP was initiated by Internet
  routing scaling concerns, there has also been an interest on
  improved solutions to a number of different problems, such as
  traffic engineering. This document should describe problem areas
  (such as scaling or traffic engineer) where LISP is expected to have
  a positive effect, as well as any tradeoffs that are caused by
  LISP's design.

- LISP security threats and solutions: This document will describe the
  security analysis of the LISP system, what issues it needs to
  protect against, and a solution that helps defend against those
  issues. The replay attack problem discussed on the mailing list
  should be included in this work.

- Allocation of Endpoint IDentifier (EID) space: This document
  requests address space to be used for the LISP experiment as
  identifier space

- Provide example specifications for performing cache management
  and ETR synchronization.

- Alternate mapping system designs: Develop alternative mapping
  designs to be tested.

- Data models for management of LISP.

The first three items (architecture, deployment models, impacts) need
to be completed first before other items can be submitted as RFCs. The
three first documents also need to complement each other, by
describing how the architecture supports a solution for a particular
problem area and how the solution can be deployed to help with that
problem.

In addition, if work chartered in some other IETF WG requires changes
in the LISP base protocol or any items which directly impact LISP
protocol structures, then the LISP WG is chartered to work on such
changes.

It is expected that the results of specifying, implementing, and testing
LISP will be fed to the general efforts at the IETF and IRTF to
understand which type of a solution is optimal. The LISP WG is not
chartered to develop a standard solution for solving the routing
scalability problem at this time. The specifications developed by the WG
are Experimental and labeled with accurate disclaimers  about their
limitations and not fully understood implications for Internet traffic.
In addition, as these issues are understood, the working group will
analyze and document the implications of LISP on Internet traffic,
applications, routers, and security.

Goals and Milestones

September 2012: Submit an architecture description to the IESG for
publication as an Experimental RFC

September 2012: Submit a deployment model document to the IESG for
publication as an Experimental RFC

September 2012: Submit a LISP impact discussion document to the IESG
for publication as an Experimental RFC

October 2012: Submit a LISP threats analysis document to the IESG for
publication as an Experimental RFC

October 2012: Submit an EID allocation document to the IESG for
publication as an Experimental RFC

January 2013: Submit an lternate mapping system designs to the IESG
for publication as an Experimental RFC

January 2013: Publish an example cache management specification.

January 2013: Publish an example ETR synchronization specification.

March 2013: Submit a data model (e.g., a MIB) document to the IESG for
publication as an Experimental RFC

March 2013: Summarize results of specifying, implementing, and testing
LISP and forward to IESG and/or IRTF.

--------------080007080800030309000004
Content-Type: text/html; charset=ISO-8859-1;
 name="charter-as-modifi-from-propos.diff.html"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
 filename="charter-as-modifi-from-propos.diff.html"

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> 
<!-- Generated by rfcdiff 1.32: rfcdiff charter-as-proposed.txt charter-as-modified.txt --> 
<!-- <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional" > -->
<!-- System: Linux dummy 2.6.38-13-generic #56-Ubuntu SMP Tue Feb 14 12:39:59 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux --> 
<!-- Using awk: /usr/bin/gawk: GNU Awk 3.1.7 --> 
<!-- Using diff: /usr/bin/diff: diff (GNU diffutils) 3.0 --> 
<!-- Using wdiff: /usr/bin/wdiff: wdiff (GNU wdiff) 0.6.3 --> 
<html> 
<head> 
  <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> 
  <meta http-equiv="Content-Style-Type" content="text/css" /> 
  <title>Diff: charter-as-proposed.txt - charter-as-modified.txt</title> 
  <style type="text/css"> 
    body    { margin: 0.4ex; margin-right: auto; } 
    tr      { } 
    td      { white-space: pre; font-family: monospace; vertical-align: top; font-size: 0.86em;} 
    th      { font-size: 0.86em; } 
    .small  { font-size: 0.6em; font-style: italic; font-family: Verdana, Helvetica, sans-serif; } 
    .left   { background-color: #EEE; } 
    .right  { background-color: #FFF; } 
    .diff   { background-color: #CCF; } 
    .lblock { background-color: #BFB; } 
    .rblock { background-color: #FF8; } 
    .insert { background-color: #8FF; } 
    .delete { background-color: #ACF; } 
    .void   { background-color: #FFB; } 
    .cont   { background-color: #EEE; } 
    .linebr { background-color: #AAA; } 
    .lineno { color: red; background-color: #FFF; font-size: 0.7em; text-align: right; padding: 0 2px; } 
    .elipsis{ background-color: #AAA; } 
    .left .cont { background-color: #DDD; } 
    .right .cont { background-color: #EEE; } 
    .lblock .cont { background-color: #9D9; } 
    .rblock .cont { background-color: #DD6; } 
    .insert .cont { background-color: #0DD; } 
    .delete .cont { background-color: #8AD; } 
    .stats, .stats td, .stats th { background-color: #EEE; padding: 2px 0; } 
  </style> 
</head> 
<body > 
  <table border="0" cellpadding="0" cellspacing="0"> 
  <tr bgcolor="orange"><th></th><th>&nbsp;charter-as-proposed.txt&nbsp;</th><th> </th><th>&nbsp;charter-as-modified.txt&nbsp;</th><th></th></tr> 
      <tr><td class="lineno" valign="top"></td><td class="left">Locator/ID Separation Protocol (lisp)</td><td> </td><td class="right">Locator/ID Separation Protocol (lisp)</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">-------------------------------------</td><td> </td><td class="right">-------------------------------------</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">Current Status: Active</td><td> </td><td class="right">Current Status: Active</td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0001" /></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">Last updated: 2012-0<span class="delete">2-14</span></td><td> </td><td class="rblock">Last updated: 2012-0<span class="insert">3-08</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"> Chairs:</td><td> </td><td class="right"> Chairs:</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">     Joel Halpern &lt;jmh@joelhalpern.com&gt;</td><td> </td><td class="right">     Joel Halpern &lt;jmh@joelhalpern.com&gt;</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">     Terry Manderson &lt;terry.manderson@icann.org&gt;</td><td> </td><td class="right">     Terry Manderson &lt;terry.manderson@icann.org&gt;</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"> Internet Area Directors:</td><td> </td><td class="right"> Internet Area Directors:</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">     Ralph Droms &lt;rdroms.ietf@gmail.com&gt;</td><td> </td><td class="right">     Ralph Droms &lt;rdroms.ietf@gmail.com&gt;</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">     Jari Arkko &lt;jari.arkko@piuha.net&gt;</td><td> </td><td class="right">     Jari Arkko &lt;jari.arkko@piuha.net&gt;</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"> Internet Area Advisor:</td><td> </td><td class="right"> Internet Area Advisor:</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
      <tr bgcolor="gray" ><td></td><th><a name="part-l2" /><small>skipping to change at</small><em> line 90</em></th><th> </th><th><a name="part-r2" /><small>skipping to change at</small><em> line 90</em></th><td></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">- LISP security threats and solutions: This document will describe the</td><td> </td><td class="right">- LISP security threats and solutions: This document will describe the</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">  security analysis of the LISP system, what issues it needs to</td><td> </td><td class="right">  security analysis of the LISP system, what issues it needs to</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">  protect against, and a solution that helps defend against those</td><td> </td><td class="right">  protect against, and a solution that helps defend against those</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">  issues. The replay attack problem discussed on the mailing list</td><td> </td><td class="right">  issues. The replay attack problem discussed on the mailing list</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">  should be included in this work.</td><td> </td><td class="right">  should be included in this work.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">- Allocation of Endpoint IDentifier (EID) space: This document</td><td> </td><td class="right">- Allocation of Endpoint IDentifier (EID) space: This document</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">  requests address space to be used for the LISP experiment as</td><td> </td><td class="right">  requests address space to be used for the LISP experiment as</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">  identifier space</td><td> </td><td class="right">  identifier space</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0002" /></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">- Provide example specifications for performing cache management</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">  and ETR synchronization.</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock">                                                                         </td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">- Alternate mapping system designs: Develop alternative mapping</td><td> </td><td class="right">- Alternate mapping system designs: Develop alternative mapping</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">  designs to be tested.</td><td> </td><td class="right">  designs to be tested.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">- Data models for management of LISP.</td><td> </td><td class="right">- Data models for management of LISP.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0003" /></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">The first three items need to be completed first before other items</td><td> </td><td class="rblock">The first three items <span class="insert">(architecture, deployment models, impacts)</span> need</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">can be submitted as RFCs. The three first documents also need to</td><td> </td><td class="rblock">to be completed first before other items can be submitted as RFCs. The</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">complement each other, by describing how the architecture supports a</td><td> </td><td class="rblock">three first documents also need to complement each other, by</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">solution for a particular problem area and how the solution can be</td><td> </td><td class="rblock">describing how the architecture supports a solution for a particular</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">deployed to help with that problem.</td><td> </td><td class="rblock">problem area and how the solution can be deployed to help with that</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock">problem.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">In addition, if work chartered in some other IETF WG requires changes</td><td> </td><td class="right">In addition, if work chartered in some other IETF WG requires changes</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">in the LISP base protocol or any items which directly impact LISP</td><td> </td><td class="right">in the LISP base protocol or any items which directly impact LISP</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">protocol structures, then the LISP WG is chartered to work on such</td><td> </td><td class="right">protocol structures, then the LISP WG is chartered to work on such</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">changes.</td><td> </td><td class="right">changes.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">It is expected that the results of specifying, implementing, and testing</td><td> </td><td class="right">It is expected that the results of specifying, implementing, and testing</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">LISP will be fed to the general efforts at the IETF and IRTF to</td><td> </td><td class="right">LISP will be fed to the general efforts at the IETF and IRTF to</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">understand which type of a solution is optimal. The LISP WG is not</td><td> </td><td class="right">understand which type of a solution is optimal. The LISP WG is not</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">chartered to develop a standard solution for solving the routing</td><td> </td><td class="right">chartered to develop a standard solution for solving the routing</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
      <tr bgcolor="gray" ><td></td><th><a name="part-l3" /><small>skipping to change at</small><em> line 137</em></th><th> </th><th><a name="part-r3" /><small>skipping to change at</small><em> line 141</em></th><td></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">October 2012: Submit a LISP threats analysis document to the IESG for</td><td> </td><td class="right">October 2012: Submit a LISP threats analysis document to the IESG for</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">publication as an Experimental RFC</td><td> </td><td class="right">publication as an Experimental RFC</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">October 2012: Submit an EID allocation document to the IESG for</td><td> </td><td class="right">October 2012: Submit an EID allocation document to the IESG for</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">publication as an Experimental RFC</td><td> </td><td class="right">publication as an Experimental RFC</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">January 2013: Submit an lternate mapping system designs to the IESG</td><td> </td><td class="right">January 2013: Submit an lternate mapping system designs to the IESG</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">for publication as an Experimental RFC</td><td> </td><td class="right">for publication as an Experimental RFC</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0004" /></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">January 2013: Publish an example cache management specification.</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"></span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">January 2013: Publish an example ETR synchronization specification.</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock">                                                                         </td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">March 2013: Submit a data model (e.g., a MIB) document to the IESG for</td><td> </td><td class="right">March 2013: Submit a data model (e.g., a MIB) document to the IESG for</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">publication as an Experimental RFC</td><td> </td><td class="right">publication as an Experimental RFC</td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0005" /></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock">                                                                         </td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">March 2013: Summarize results of specifying, implementing, and testing</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">LISP and forward to IESG and/or IRTF.</span></td><td class="lineno" valign="top"></td></tr>

     <tr><td></td><td class="left"></td><td> </td><td class="right"></td><td></td></tr>
     <tr bgcolor="gray"><th colspan="5" align="center"><a name="end">&nbsp;End of changes. 5 change blocks.&nbsp;</a></th></tr>
     <tr class="stats"><td></td><th><i>6 lines changed or deleted</i></th><th><i> </i></th><th><i>14 lines changed or added</i></th><td></td></tr>
     <tr><td colspan="5" align="center" class="small"><br/>This html diff was produced by rfcdiff 1.32. The latest version is available from <a href="http://www.levkowetz.com/ietf/tools/rfcdiff/" >http://www.levkowetz.com/ietf/tools/rfcdiff/</a> </td></tr>
   </table>
   </body>
   </html>

--------------080007080800030309000004--

From eran@hueniverse.com  Wed Mar  7 17:22:58 2012
Return-Path: <eran@hueniverse.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 29EE221E8025 for <ietf@ietfa.amsl.com>; Wed,  7 Mar 2012 17:22:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.531
X-Spam-Level: 
X-Spam-Status: No, score=-2.531 tagged_above=-999 required=5 tests=[AWL=0.068,  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 X5rEIbd7Ya9A for <ietf@ietfa.amsl.com>; Wed,  7 Mar 2012 17:22:57 -0800 (PST)
Received: from p3plex1out01.prod.phx3.secureserver.net (p3plex1out01.prod.phx3.secureserver.net [72.167.180.17]) by ietfa.amsl.com (Postfix) with SMTP id 758F521E800C for <ietf@ietf.org>; Wed,  7 Mar 2012 17:22:57 -0800 (PST)
Received: (qmail 29307 invoked from network); 7 Mar 2012 23:39:53 -0000
Received: from unknown (HELO smtp.ex1.secureserver.net) (72.167.180.20) by p3plex1out01.prod.phx3.secureserver.net with SMTP; 7 Mar 2012 23:39:51 -0000
Received: from P3PW5EX1MB01.EX1.SECURESERVER.NET ([10.6.135.20]) by P3PW5EX1HT002.EX1.SECURESERVER.NET ([72.167.180.20]) with mapi; Wed, 7 Mar 2012 16:18:25 -0700
From: Eran Hammer <eran@hueniverse.com>
To: John Bradley <ve7jtb@ve7jtb.com>
Date: Wed, 7 Mar 2012 16:18:17 -0700
Subject: RE: [OAUTH-WG] Last Call: <draft-ietf-oauth-v2-bearer-15.txt> (The OAuth 2.0	Authorization Protocol: Bearer Tokens) to Proposed Standard
Thread-Topic: [OAUTH-WG] Last Call: <draft-ietf-oauth-v2-bearer-15.txt> (The OAuth 2.0	Authorization Protocol: Bearer Tokens) to Proposed Standard
Thread-Index: AczlNNN25d70S7GxRlKDI7eb2HdniAXg6QXA
Message-ID: <90C41DD21FB7C64BB94121FBBC2E723453AFCD4072@P3PW5EX1MB01.EX1.SECURESERVER.NET>
References: <20120123154643.16223.44509.idtracker@ietfa.amsl.com> <4F1D8391.3080009@gmx.de> <4F1F3D84.1030300@gmx.de> <90C41DD21FB7C64BB94121FBBC2E723453AAB9682E@P3PW5EX1MB01.EX1.SECURESERVER.NET> <7D4DB9C9-7194-42A0-A573-4243FE27E512@ve7jtb.com>
In-Reply-To: <7D4DB9C9-7194-42A0-A573-4243FE27E512@ve7jtb.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Thu, 08 Mar 2012 09:42:43 -0800
Cc: Julian Reschke <julian.reschke@gmx.de>, "oauth@ietf.org" <oauth@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, The IESG <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Mar 2012 01:22:58 -0000

New text:

          The probability of an attacker guessing generated tokens (and oth=
er credentials not
          intended for handling by end-users) MUST be less than or equal to=
 2^(-128) and SHOULD be
          less than or equal to 2^(-160).

Removed reference to RFC 1750.

EH

> -----Original Message-----
> From: John Bradley [mailto:ve7jtb@ve7jtb.com]
> Sent: Monday, February 06, 2012 5:07 PM
> To: Eran Hammer
> Cc: Julian Reschke; ietf@ietf.org; The IESG; oauth@ietf.org
> Subject: Re: [OAUTH-WG] Last Call: <draft-ietf-oauth-v2-bearer-15.txt> (T=
he
> OAuth 2.0 Authorization Protocol: Bearer Tokens) to Proposed Standard
>=20
> RE new text in Draft 23
>=20
> http://tools.ietf.org/html/draft-ietf-oauth-v2-23#section-10.10
>=20
> Generated tokens and other credentials not intended for handling by
>    end-users MUST be constructed from a cryptographically strong random
>    or pseudo-random number sequence ([RFC1750]) generated by the
>    authorization server.
>=20
> Given that many implementations may elect to use signed tokens, such as
> SAML or JWT (JOSE) this should not be a MUST.
>=20
> Giving people sensible defaults such as the probability of an attacker
> guessing a valid access token for the protected resource should be less t=
han
> 2^(-128).
>=20
> The probability of generating hash colisions randomly is a odd metric,  2=
^(-
> 128) for a SHA256 as I recall.
> Many factors play into what is secure, token lifetime etc.
>=20
> I don't mind some reasonable defaults but adding a requirement for
> unstructured tokens is a bit much.
>=20
> Regards
> John B.
>=20
>=20


From ve7jtb@ve7jtb.com  Thu Mar  8 08:13:29 2012
Return-Path: <ve7jtb@ve7jtb.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D2BD321F8557 for <ietf@ietfa.amsl.com>; Thu,  8 Mar 2012 08:13:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.99
X-Spam-Level: 
X-Spam-Status: No, score=-2.99 tagged_above=-999 required=5 tests=[AWL=-0.610,  BAYES_00=-2.599, J_CHICKENPOX_44=0.6, RCVD_IN_DNSWL_LOW=-1, RCVD_IN_SORBS_WEB=0.619]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nXdpzlBHFlLh for <ietf@ietfa.amsl.com>; Thu,  8 Mar 2012 08:13:29 -0800 (PST)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id 21ECF21F854E for <ietf@ietf.org>; Thu,  8 Mar 2012 08:13:28 -0800 (PST)
Received: by yhpp34 with SMTP id p34so348895yhp.31 for <ietf@ietf.org>; Thu, 08 Mar 2012 08:13:28 -0800 (PST)
Received: by 10.236.185.42 with SMTP id t30mr10838763yhm.105.1331223207198; Thu, 08 Mar 2012 08:13:27 -0800 (PST)
Received: from 201-188-194-239.bam.movistar.cl ([201.188.194.239]) by mx.google.com with ESMTPS id n10sm3759581ani.8.2012.03.08.08.13.23 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 08 Mar 2012 08:13:25 -0800 (PST)
Subject: Re: [OAUTH-WG] Last Call: <draft-ietf-oauth-v2-bearer-15.txt> (The OAuth 2.0	Authorization Protocol: Bearer Tokens) to Proposed Standard
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: multipart/signed; boundary="Apple-Mail=_412498E1-4386-4610-9617-F3A2197AA9FD"; protocol="application/pkcs7-signature"; micalg=sha1
From: John Bradley <ve7jtb@ve7jtb.com>
In-Reply-To: <90C41DD21FB7C64BB94121FBBC2E723453AFCD4072@P3PW5EX1MB01.EX1.SECURESERVER.NET>
Date: Thu, 8 Mar 2012 13:13:21 -0300
Message-Id: <A7D328CF-C7E5-4A78-A60C-BE34FC65B2BD@ve7jtb.com>
References: <20120123154643.16223.44509.idtracker@ietfa.amsl.com> <4F1D8391.3080009@gmx.de> <4F1F3D84.1030300@gmx.de> <90C41DD21FB7C64BB94121FBBC2E723453AAB9682E@P3PW5EX1MB01.EX1.SECURESERVER.NET> <7D4DB9C9-7194-42A0-A573-4243FE27E512@ve7jtb.com> <90C41DD21FB7C64BB94121FBBC2E723453AFCD4072@P3PW5EX1MB01.EX1.SECURESERVER.NET>
To: Eran Hammer <eran@hueniverse.com>
X-Mailer: Apple Mail (2.1257)
X-Gm-Message-State: ALoCoQkTM2bSNdo5Luwl5FT6dkcBUGYzoZwjkJ4f1slwNCjIrj/ni/sDVk+9pztSVAo+A46Xuh0d
X-Mailman-Approved-At: Thu, 08 Mar 2012 09:42:43 -0800
Cc: Julian Reschke <julian.reschke@gmx.de>, "oauth@ietf.org" <oauth@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, The IESG <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Mar 2012 16:13:30 -0000

--Apple-Mail=_412498E1-4386-4610-9617-F3A2197AA9FD
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Thanks that is better.

Without knowing the lifetime of the token these are per guess =
probabilities.
Effectively 128bits for a random value and 256bits for a HMAC or other =
signature.

For tokens intended for handling by end-users it may be useful to give =
some advice.
In general you don't want an attacker having more than a one in 2^14 =
chance of guessing a valid code for a AS during the lifetime of the =
code(NIST LoA 2).

For a code randomly generated from a 94 character code set 4 characters =
gets you 26.3 bits of entropy.
5 characters requires limiting an attacker to 2^12.3 (5,042) guesses per =
token lifetime.=20

For a code randomly generated from a 94 character code set 5 characters =
gets you 32.9 bits of entropy.
5 characters requires limiting an attacker to 2^18.9 (489,178) guesses =
per token lifetime.=20

If the token is single use and the client uses it right away that is =
easy,  however in a worst case scenario the token might live 10min?
That would be 8.4 attempts per second as a max for a 4 character code or =
815 per second for 5 characters.

That is all way too much to explain however I would recommend as a =
general rule:

Credentials intended for handling by end users SHOULD be a minimum of 5 =
randomly generated charters from a set of 94 or otherwise contain a =
minimum entropy of 2^32.9.

That is probably high enough that the AS will notice an attack,  lower =
entropy may pass under the radar. =20
Also the chances of an attacker being successful go up proportionally to =
the number simultaneous codes in flight at any point (it becomes a non =
targeted attack).  =20

It isn't something that I will loose sleep over,  It gives me something =
else to profile:)

Thanks=20
John B.

On 2012-03-07, at 8:18 PM, Eran Hammer wrote:

> New text:
>=20
>          The probability of an attacker guessing generated tokens (and =
other credentials not
>          intended for handling by end-users) MUST be less than or =
equal to 2^(-128) and SHOULD be
>          less than or equal to 2^(-160).
>=20
> Removed reference to RFC 1750.
>=20
> EH
>=20
>> -----Original Message-----
>> From: John Bradley [mailto:ve7jtb@ve7jtb.com]
>> Sent: Monday, February 06, 2012 5:07 PM
>> To: Eran Hammer
>> Cc: Julian Reschke; ietf@ietf.org; The IESG; oauth@ietf.org
>> Subject: Re: [OAUTH-WG] Last Call: =
<draft-ietf-oauth-v2-bearer-15.txt> (The
>> OAuth 2.0 Authorization Protocol: Bearer Tokens) to Proposed Standard
>>=20
>> RE new text in Draft 23
>>=20
>> http://tools.ietf.org/html/draft-ietf-oauth-v2-23#section-10.10
>>=20
>> Generated tokens and other credentials not intended for handling by
>>   end-users MUST be constructed from a cryptographically strong =
random
>>   or pseudo-random number sequence ([RFC1750]) generated by the
>>   authorization server.
>>=20
>> Given that many implementations may elect to use signed tokens, such =
as
>> SAML or JWT (JOSE) this should not be a MUST.
>>=20
>> Giving people sensible defaults such as the probability of an =
attacker
>> guessing a valid access token for the protected resource should be =
less than
>> 2^(-128).
>>=20
>> The probability of generating hash colisions randomly is a odd =
metric,  2^(-
>> 128) for a SHA256 as I recall.
>> Many factors play into what is secure, token lifetime etc.
>>=20
>> I don't mind some reasonable defaults but adding a requirement for
>> unstructured tokens is a bit much.
>>=20
>> Regards
>> John B.
>>=20
>>=20
>=20


--Apple-Mail=_412498E1-4386-4610-9617-F3A2197AA9FD
Content-Disposition: attachment;
	filename=smime.p7s
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIO9TCCBwsw
ggXzoAMCAQICAgZDMA0GCSqGSIb3DQEBBQUAMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3Rh
cnRDb20gTHRkLjErMCkGA1UECxMiU2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4
MDYGA1UEAxMvU3RhcnRDb20gQ2xhc3MgMiBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0Ew
HhcNMTAwMzE3MTM0NDQ1WhcNMTIwMzE4MTE1NTExWjCBzTEgMB4GA1UEDRMXMTY1NTU1LTJHU3FU
T1ZUbkk4OHhOSW4xCzAJBgNVBAYTAkNMMSIwIAYDVQQIExlNZXRyb3BvbGl0YW5hIGRlIFNhbnRp
YWdvMREwDwYDVQQHEwhWaXRhY3VyYTEtMCsGA1UECxMkU3RhcnRDb20gVmVyaWZpZWQgQ2VydGlm
aWNhdGUgTWVtYmVyMRUwEwYDVQQDEwxKb2huIEJyYWRsZXkxHzAdBgkqhkiG9w0BCQEWEGpicmFk
bGV5QG1hYy5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDB7DXf6x80dsJiB9B9
Ds4cBQdA+9bNuZMBeXkUAHrvYH2taw6y8fcadbhgk92FyPiCbsHtB1VTaJThaMqtXuTkS4r5Sfb8
k5kboz3OQVPMmrOJIUpaoDP2heKEhMUSL6ev9CvsuYs+XXe7f9vY3w/A8cVg/NoOXbdqKXbWOMMd
NSdg7uJWSsmpqILFzQsumwqVH24tYX0sqvpJy/r+pc84j6QM+Ew0B9bz3OkEMafjcCeGRfdsQnLB
+rIR8BPDeeKRP6a5e8Lf6slUQ3s/rh33otnkNaz6DMLTJrj0qoAD7FxB7LlLalIjrg08BNZDJUQK
7zTlNxkPqVHVTg3H0OG/AgMBAAGjggMyMIIDLjAJBgNVHRMEAjAAMAsGA1UdDwQEAwIEsDAdBgNV
HSUEFjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwHQYDVR0OBBYEFMjJGKHWsNb6VU54Wkktqcu2on3B
MB8GA1UdIwQYMBaAFK5Vg2/sMcq59x36r2sx88gd46y7MFQGA1UdEQRNMEuBEGpicmFkbGV5QG1h
Yy5jb22BEXZlN2p0YkB2ZTdqdGIuY29tgRNqYnJhZGxleUB3aW5nYWEuY29tgQ9qYnJhZGxleUBt
ZS5jb20wggFCBgNVHSAEggE5MIIBNTCCATEGCysGAQQBgbU3AQIBMIIBIDAuBggrBgEFBQcCARYi
aHR0cDovL3d3dy5zdGFydHNzbC5jb20vcG9saWN5LnBkZjA0BggrBgEFBQcCARYoaHR0cDovL3d3
dy5zdGFydHNzbC5jb20vaW50ZXJtZWRpYXRlLnBkZjCBtwYIKwYBBQUHAgIwgaowFBYNU3RhcnRD
b20gTHRkLjADAgEBGoGRTGltaXRlZCBMaWFiaWxpdHksIHNlZSBzZWN0aW9uICpMZWdhbCBMaW1p
dGF0aW9ucyogb2YgdGhlIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5IFBvbGljeSBh
dmFpbGFibGUgYXQgaHR0cDovL3d3dy5zdGFydHNzbC5jb20vcG9saWN5LnBkZjBjBgNVHR8EXDBa
MCugKaAnhiVodHRwOi8vd3d3LnN0YXJ0c3NsLmNvbS9jcnR1Mi1jcmwuY3JsMCugKaAnhiVodHRw
Oi8vY3JsLnN0YXJ0c3NsLmNvbS9jcnR1Mi1jcmwuY3JsMIGOBggrBgEFBQcBAQSBgTB/MDkGCCsG
AQUFBzABhi1odHRwOi8vb2NzcC5zdGFydHNzbC5jb20vc3ViL2NsYXNzMi9jbGllbnQvY2EwQgYI
KwYBBQUHMAKGNmh0dHA6Ly93d3cuc3RhcnRzc2wuY29tL2NlcnRzL3N1Yi5jbGFzczIuY2xpZW50
LmNhLmNydDAjBgNVHRIEHDAahhhodHRwOi8vd3d3LnN0YXJ0c3NsLmNvbS8wDQYJKoZIhvcNAQEF
BQADggEBAHu8WZHdSu+I5GMzGDrkxFVUzZ2JAcwzgSscYNFX2CFJlU8ncC+/E5Y18oiGcIR9o7J3
Hh4fGrjJmxTsq2O3E9/qg0yWSEzlCBhAXl/D+GTyUJA/KfIuCbdsuS5opprSrBZztqMYcGSCQJFz
lE+esdbCXazdyEww5XfiGVgKiRyV2ycXyxNjekowbcDffSsOYplGBjJwPRYpESgfCYDXm+yyDQhy
Xk0pxNEA7ob5fAMellN8FcgLfQtwSRcg8cYl/m8/BeVl6+eZuzCb061PdUN+mDf6erS55tXqgWJ3
toTp3GGaaOwwGs/bA1UnLqYm93RfTyL3kU1OWG8syPFMLoIwggfiMIIFyqADAgECAgEOMA0GCSqG
SIb3DQEBBQUAMH0xCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSswKQYDVQQL
EyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMSkwJwYDVQQDEyBTdGFydENvbSBD
ZXJ0aWZpY2F0aW9uIEF1dGhvcml0eTAeFw0wNzEwMjQyMTAyNTRaFw0xMjEwMjIyMTAyNTRaMIGM
MQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjErMCkGA1UECxMiU2VjdXJlIERp
Z2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYGA1UEAxMvU3RhcnRDb20gQ2xhc3MgMiBQcmlt
YXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0EwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIB
AQDLKIVFnAEs+xnyq6UzjCqgDcvQVe1dIoFnRsQPCFO+y92k8RK0Pn3MbQ2Gd+mehh9GBZ+36uUQ
A7Xj9AGM6wgPhEE34vKtfpAN5tJ8LcFxveDObCKrL7O5UT9WsnAZHv7OYPYSR68mdmnEnJ83M4wQ
gKO19b+Rt8sPDAz9ptkQsntCn4GeJzg3q2SVc4QJTg/WHo7wF2ah5LMOeh8xJVSKGEmd6uPkSbj1
13yKMm8vmNptRPmM1+YgmVwcdOYJOjCgFtb2sOP79jji8uhWR91xx7TpM1K3hv/wrBZwffrmmEpU
euXHRs07JqCCvFh9coKF4UQZvfEg+x3/69xRCzb1AgMBAAGjggNbMIIDVzAMBgNVHRMEBTADAQH/
MAsGA1UdDwQEAwIBpjAdBgNVHQ4EFgQUrlWDb+wxyrn3HfqvazHzyB3jrLswgagGA1UdIwSBoDCB
nYAUTgvvGqRAW6UXaYcwyjRoQ9BBrvKhgYGkfzB9MQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3Rh
cnRDb20gTHRkLjErMCkGA1UECxMiU2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzEp
MCcGA1UEAxMgU3RhcnRDb20gQ2VydGlmaWNhdGlvbiBBdXRob3JpdHmCAQEwCQYDVR0SBAIwADA9
BggrBgEFBQcBAQQxMC8wLQYIKwYBBQUHMAKGIWh0dHA6Ly93d3cuc3RhcnRzc2wuY29tL3Nmc2Nh
LmNydDBgBgNVHR8EWTBXMCygKqAohiZodHRwOi8vY2VydC5zdGFydGNvbS5vcmcvc2ZzY2EtY3Js
LmNybDAnoCWgI4YhaHR0cDovL2NybC5zdGFydHNzbC5jb20vc2ZzY2EuY3JsMIIBXQYDVR0gBIIB
VDCCAVAwggFMBgsrBgEEAYG1NwEBBDCCATswLwYIKwYBBQUHAgEWI2h0dHA6Ly9jZXJ0LnN0YXJ0
Y29tLm9yZy9wb2xpY3kucGRmMDUGCCsGAQUFBwIBFilodHRwOi8vY2VydC5zdGFydGNvbS5vcmcv
aW50ZXJtZWRpYXRlLnBkZjCB0AYIKwYBBQUHAgIwgcMwJxYgU3RhcnQgQ29tbWVyY2lhbCAoU3Rh
cnRDb20pIEx0ZC4wAwIBARqBl0xpbWl0ZWQgTGlhYmlsaXR5LCByZWFkIHRoZSBzZWN0aW9uICpM
ZWdhbCBMaW1pdGF0aW9ucyogb2YgdGhlIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5
IFBvbGljeSBhdmFpbGFibGUgYXQgaHR0cDovL2NlcnQuc3RhcnRjb20ub3JnL3BvbGljeS5wZGYw
EQYJYIZIAYb4QgEBBAQDAgAHMFAGCWCGSAGG+EIBDQRDFkFTdGFydENvbSBDbGFzcyAyIFByaW1h
cnkgSW50ZXJtZWRpYXRlIEZyZWUgU1NMIEVtYWlsIENlcnRpZmljYXRlczANBgkqhkiG9w0BAQUF
AAOCAgEAHvcQF/726YR5L5A3Ta7JV1nTu3w9yWqp00945pg7uea+1KVtR/7/yeNFAV7MPQylPE8p
ROEcGU+RwwDFuNn9cePfAMzOBTpy/6VE076+gYkZa4n8uWaL5A2FVo8tRmEyfoT4gRL9B5h5w8Y4
ZySCJBLyfp4jByyxHaTTIWZ8TIkxUQLSBeFnmHKYFwYwMbBA0Sgb8ONCvq9zeJcpMkkDadhJSCfB
9c9gZocbaaVHVqTlSeENRr5/Y31dapzIRQg2Pl9V/A65Cq03KQxMXBpXn8HkLO/g2FCt7KYkJCaT
e6qT2JX8thmB3nb+5RmtWQIITCP+PPNkFQCts6ujOtJx6TlDLWA+tV7QLN2Q+S98p/SwnXito+GW
0N7kXcL8QDBVsF8lCvwCz+JQrvUIcW5xEzpAVk9xSbpePxVIMzNEUQhBobkFojhUqGt+VyU3GH/+
BP2brzl4StOJ1KXuw2EzFs0ai9OMsqCUFRyhykm6MrbnsnSrqhWSnSQPYIu+zpzwWC/8sZFxoJCw
vbbIu+6E+AIGa8tP+pYF+empPn/7pkIoTT4LSkkEIxGKvUvDJTh86VDNL8bIIQE2LHVDwcOq+mcQ
x416FAA9Nw1DBGyrFr6hQe5yTVXrJ4G7vJosNRGCwPnx302gonaFdwi++YyqjPyhPO6q4fRarYvW
yqp5L6UxggNsMIIDaAIBATCBkzCBjDELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0
ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcxODA2BgNVBAMT
L1N0YXJ0Q29tIENsYXNzIDIgUHJpbWFyeSBJbnRlcm1lZGlhdGUgQ2xpZW50IENBAgIGQzAJBgUr
DgMCGgUAoIIBrTAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xMjAz
MDgxNjEzMjFaMCMGCSqGSIb3DQEJBDEWBBQef3mDeDCjKu8tZa9JZ7ue/VYveTCBpAYJKwYBBAGC
NxAEMYGWMIGTMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjErMCkGA1UE
CxMiU2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYGA1UEAxMvU3RhcnRDb20g
Q2xhc3MgMiBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0ECAgZDMIGmBgsqhkiG9w0BCRAC
CzGBlqCBkzCBjDELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4xKzApBgNVBAsT
IlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcxODA2BgNVBAMTL1N0YXJ0Q29tIENs
YXNzIDIgUHJpbWFyeSBJbnRlcm1lZGlhdGUgQ2xpZW50IENBAgIGQzANBgkqhkiG9w0BAQEFAASC
AQAexJNRq7wYCUOOP2pYQwFyBilvjp4KELC5AivyDoODeWpEBJGx4aRhjqfTd5Pt+RgKE9IPOGzS
4RZDiKtyyt53qcaWtoRrtAj+IFXu8370W/xREU0mEkqIbAZc4uCfvlLwqlCEuPDGONrOnWSdKgm/
cfmhmKNSsC/76S9L8QU2f004WcU3WiDt3EC7DZ3Ef/q3PQ+WzNzIk0ZXIHE/Gonw90BJx6NG1eli
GqQ73NxBBYT7y0zohXF4Sh22mGi5faRxg9FJ2RVtF8YvJ59zPsz7ajQaFiXrv9Y06u9iq8BC/llT
wlsXGx2VUoVKqo6cB28pt79VQ7jqcZpz9t8EAPgJAAAAAAAA

--Apple-Mail=_412498E1-4386-4610-9617-F3A2197AA9FD--

From john-ietf@jck.com  Thu Mar  8 10:01: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 F2C6621F8575; Thu,  8 Mar 2012 10:01:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.833
X-Spam-Level: 
X-Spam-Status: No, score=-102.833 tagged_above=-999 required=5 tests=[AWL=-0.234, 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 OvIf6cGQs4Jg; Thu,  8 Mar 2012 10:01:51 -0800 (PST)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id AC31021F84BD; Thu,  8 Mar 2012 10:01:51 -0800 (PST)
Received: from [198.252.137.7] (helo=PST.JCK.COM) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1S5haT-000AxZ-B0; Thu, 08 Mar 2012 12:57:13 -0500
Date: Thu, 08 Mar 2012 13:01:46 -0500
From: John C Klensin <john-ietf@jck.com>
To: ietf@ietf.org
Subject: Re: Last Call: <draft-ietf-appsawg-xdash-03.txt> (Deprecating Use of the "X-" Prefix in Application Protocols)	to Best Current Practice
Message-ID: <E25079DB412F23314FAA91D2@PST.JCK.COM>
In-Reply-To: <20120301184750.21152.93044.idtracker@ietfa.amsl.com>
References: <20120301184750.21152.93044.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: 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, 08 Mar 2012 18:01:53 -0000

Hi.

I realize I'm probably in the minority on this, but I think the
document overstates its case a bit and, perhaps recognizing the
actual complexity of the situation, even may contradict itself a
bit.  For example, I note that it says:

	(Section 1) "Therefore this document deprecates the "X-"
	convention for named parameters in application
	protocols" 
	
	but 
	
	(Section 4 (4)) "SHOULD identify a convention to allow
	local or implementation-specific extensions, and reserve
	delimeters for such uses as needed." presumably as long
	as those delimiters don't consist of "X-".

While I believe that the general strategy of treating textual
parameters as hierarchical (or consisting of subsets) so that
private allocations can exist in a separate tree is a good one,
I think we also need to recognize that "X-" is just one more way
to make that division.  If it not a wonderful one, and it
carries around a lot of baggage, but neither justifies the
amount of venom that has been directed toward it over the years
nor some of the strong language of this document (which is much
better than some of its earlier drafts in that respect).  

The reality is that, when "X-" has been used to identify purely
private and/or implementation-specific parameters, it has not
been a problem.  It has been a problem for experimental
parameters, but that is a different matter... and a distinction
this document fails to make clearly enough, at least IMO.

Overstating the case for something like this, e.g., by inserting
MUST NOT language where there is little justification for more
than "SHOULD NOT" won't be likely change the behavior of those
creating or maintaining implementations.  MUST NOTs that are
ignored do nothing positive for the reputation or credibility of
the IETF.  I largely agree with Randy Gellens's reasoning about
this.  However, I don't think the choice of requirements
language is a showstopper: I think it is a judgment call and
that, unless there is a basis for strong consensus, judgment
calls should generally be resolved in favor of a less-strong
requirement.

While Appendix A mentions the history of using "X" (without the
dash) for experimental and private command names, the document
does not address that issue at all.

The second "primary objection" listed in Appendix B is, IMO,
somewhat misstated.  It would be more accurate to say, more or
less, 

	"Collisions are undesirable and it would be bad for a
	parameter 'foo' to designate two different sets of
	semantics, whether either of those sets is standard or
	not.  The only ways to avoid that situation are for all
	parameters to be registered so that someone considering
	defining a new one can determine whether the name string
	is already in use _or_ for all parameters to contain a
	relatively-long randomly-generated substring to make the
	likelihood of accidental collision infinitesimal.  The
	problem is that it is impossible to achieve universal
	registration despite the changes represented by more
	recent registration specifications, so there is some
	merit to being able to lexically distinguish private use
	(not to be accepted in interchange without out-of-band
	knowledge) parameter values from broader-use (and
	possibly standardized) ones."

I note that no one has seriously proposed the "random substring"
solution but, if we were serious about the problem for
parameters users are unlikely to see, it is part of the logical
solution space.

Finally, the effect of this document is to update a rather large
collection of existing specifications, not all of which are
included in textual discussion or references.  Those
specifications are not listed in the text or in an "updates"
header, much less called out in the Introduction and/or Abstract.

Recommendations:

(1) As suggested by several others, remove the "MUST" from
Section 2, replacing it with "SHOULD".

(2) Clarify whether this document is intended to deprecate
giving special treatment to protocol commands starting in "X"
rather than merely parameters starting in "X-" and why or why
not.

(3) Clarify the difference between "private-use" parameters,
"implementation-specific" parameters, and "experimental"
parameters.  Strong language discouraging the latter is probably
appropriate, but clearly-defined private uses may be reasonable
(at least for some protocols), and implementation-specific
parameters may fall somewhere in between. 

(4) Correct the explanation of the counterarguments as outlined
above so that the document is not attacking straw men.

(5) Either (i) explicitly identify the complete list of
specifications that this one updates, doing so with all of the
decorations that the IESG has required in other specifications,
(ii) incorporate language into this specification and a revised
Last Call that identifies the reasons why this specification is
exempt, or (iii) clarify, before this document is approved, what
the requirements (and "really strong suggestions") actually are
in a way that makes it clear why they should not apply to
documents of this type.

Just my opinion.
    john



--On Thursday, March 01, 2012 10:47 -0800 The IESG
<iesg-secretary@ietf.org> wrote:

> 
> The IESG has received a request from the Applications Area
> Working Group WG (appsawg) to consider the following document:
> - 'Deprecating Use of the "X-" Prefix in Application Protocols'
>   <draft-ietf-appsawg-xdash-03.txt> as a 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-03-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.
> 


From mrex@sap.com  Thu Mar  8 10:45:23 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 3E9D421F859F for <ietf@ietfa.amsl.com>; Thu,  8 Mar 2012 10:45:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.054
X-Spam-Level: 
X-Spam-Status: No, score=-10.054 tagged_above=-999 required=5 tests=[AWL=0.195, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jvMdbjDUgwZh for <ietf@ietfa.amsl.com>; Thu,  8 Mar 2012 10:45:22 -0800 (PST)
Received: from smtpde01.sap-ag.de (smtpde01.sap-ag.de [155.56.68.170]) by ietfa.amsl.com (Postfix) with ESMTP id 4AE7321F8595 for <ietf@ietf.org>; Thu,  8 Mar 2012 10:45:22 -0800 (PST)
Received: from mail.sap.corp by smtpde01.sap-ag.de (26) with ESMTP id q28IjG3c029213 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 8 Mar 2012 19:45:16 +0100 (MET)
From: Martin Rex <mrex@sap.com>
Message-Id: <201203081845.q28IjGF0006949@fs4113.wdf.sap.corp>
Subject: Re: provisioning software, was DNS RRTYPEs, the difficulty with
To: dot@dotat.at (Tony Finch)
Date: Thu, 8 Mar 2012 19:45:16 +0100 (MET)
In-Reply-To: <alpine.LSU.2.00.1203081346470.2756@hermes-2.csi.cam.ac.uk> from "Tony Finch" at Mar 8, 12 02:02:15 pm
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
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: Thu, 08 Mar 2012 18:45:23 -0000

Tony Finch wrote:
> 
> Murray S. Kucherawy <msk@cloudmark.com> wrote:
> >
> > I looked at least at the titles of all the documents that update 1035,
> > and none of them appear to be related to the above.  So where should we
> > be looking?
> 
> The only thing I have found that implies NOTIMP doesn't apply to queries
> for unknown RR types is in RFC 4074, "Common Misbehavior Against DNS
> Queries for IPv6 Addresses":

Thanks for mentioning rfc 4074.  The stuff in that document matches
the thoroughly broken behaviour of the IPv6 DNS resolver client of
Windows 2003 that I had encountered just recently.

IMO, rfc4074 exhibits a significant amount of cluelessness about DNS,
the "Full Standard" document maturity level, and the realities of
backwards compatibilities for an incredibly huge installed base.


The answer to the question "what can I infer from a failed AAAA lookup"
must be deduced from STD 13 **ALONE**, and it amounts to "very close to
nothing at all".

Now this puts the slow adoption of IPv6 into perspective if it takes
the IPv6 crowds >10 years to figure that one out, 


-Martin

From mrex@sap.com  Thu Mar  8 11:57:20 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 6AF3021F8678 for <ietf@ietfa.amsl.com>; Thu,  8 Mar 2012 11:57:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.055
X-Spam-Level: 
X-Spam-Status: No, score=-10.055 tagged_above=-999 required=5 tests=[AWL=0.194, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tehCB8kyXvoy for <ietf@ietfa.amsl.com>; Thu,  8 Mar 2012 11:57:20 -0800 (PST)
Received: from smtpde01.sap-ag.de (smtpde01.sap-ag.de [155.56.68.170]) by ietfa.amsl.com (Postfix) with ESMTP id A2A2B21F8677 for <ietf@ietf.org>; Thu,  8 Mar 2012 11:57:16 -0800 (PST)
Received: from mail.sap.corp by smtpde01.sap-ag.de (26) with ESMTP id q28JvE85009372 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 8 Mar 2012 20:57:14 +0100 (MET)
From: Martin Rex <mrex@sap.com>
Message-Id: <201203081957.q28JvDmr010951@fs4113.wdf.sap.corp>
Subject: Re: provisioning software, was DNS RRTYPEs, the difficulty with
To: mrex@sap.com
Date: Thu, 8 Mar 2012 20:57:13 +0100 (MET)
In-Reply-To: <201203081845.q28IjGF0006949@fs4113.wdf.sap.corp> from "Martin Rex" at Mar 8, 12 07:45:16 pm
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
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: Thu, 08 Mar 2012 19:57:20 -0000

Martin Rex wrote:
> 
> Tony Finch wrote:
> > 
> > Murray S. Kucherawy <msk@cloudmark.com> wrote:
> > >
> > > I looked at least at the titles of all the documents that update 1035,
> > > and none of them appear to be related to the above.  So where should we
> > > be looking?
> > 
> > The only thing I have found that implies NOTIMP doesn't apply to queries
> > for unknown RR types is in RFC 4074, "Common Misbehavior Against DNS
> > Queries for IPv6 Addresses":
> 
> Thanks for mentioning rfc 4074.  The stuff in that document matches
> the thoroughly broken behaviour of the IPv6 DNS resolver client of
> Windows 2003 that I had encountered just recently.
> 
> IMO, rfc4074 exhibits a significant amount of cluelessness about DNS,
> the "Full Standard" document maturity level, and the realities of
> backwards compatibilities for an incredibly huge installed base.
> 
> 
> The answer to the question "what can I infer from a failed AAAA lookup"
> must be deduced from STD 13 **ALONE**, and it amounts to "very close to
> nothing at all".

In case this isn't clear:  this applies to DNS responses with one of
the failure RCODEs (1,2,3,4,5) defined in rfc1035 _unless_ the response
is accompanied by some protocol extension that can be used to **reliably**
distinguish 1034/1035 DNS responders from those conforming to a later,
optional DNS protocol extension.


-Martin

From jari.arkko@piuha.net  Thu Mar  8 13:13:44 2012
Return-Path: <jari.arkko@piuha.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4CE7E21F8683; Thu,  8 Mar 2012 13:13:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.463
X-Spam-Level: 
X-Spam-Status: No, score=-102.463 tagged_above=-999 required=5 tests=[AWL=0.136, 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 bMHrb-K-8odw; Thu,  8 Mar 2012 13:13:41 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by ietfa.amsl.com (Postfix) with ESMTP id E7C1521F862A; Thu,  8 Mar 2012 13:13:38 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id E70FE2DA0D; Thu,  8 Mar 2012 23:13:36 +0200 (EET)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Aqemv3H_6Xlc; Thu,  8 Mar 2012 23:13:36 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 4522B2CC3C; Thu,  8 Mar 2012 23:13:36 +0200 (EET)
Message-ID: <4F5920FF.6070502@piuha.net>
Date: Thu, 08 Mar 2012 23:13:35 +0200
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0) Gecko/20120129 Thunderbird/10.0
MIME-Version: 1.0
To: John Scudder <jgs@juniper.net>
Subject: Re: [lisp] WG Review: Recharter of Locator/ID Separation Protocol (lisp)
References: <20120214222316.CF29521E800E@ietfa.amsl.com> <201202152131.q1FLVB9E028114@cichlid.raleigh.ibm.com> <EF3C34EB-C0AA-45F2-ADE0-407CEF5172DD@juniper.net> <4F3E4EDB.7070509@piuha.net> <0E0C6A25-FBA6-4E11-9E89-DEBFFCF41108@juniper.net> <4F58EB8C.1000700@piuha.net> <70EB276F-D77E-45AE-851C-AB08A8D56D0A@juniper.net>
In-Reply-To: <70EB276F-D77E-45AE-851C-AB08A8D56D0A@juniper.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "iesg@ietf.org IESG" <iesg@ietf.org>, "ietf@ietf.org list" <ietf@ietf.org>, "lisp@ietf.org" <lisp@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Mar 2012 21:13:44 -0000

I hear what you are saying. But I think the opinion in the IESG at least was, however, that those three really are high priority, and that other documents before them are not so useful before they are completed. I guess it is a different perspective, whether you do things top-down or bottom-up. I do agree with both points of view, actually.

Jari


From barryleiba@gmail.com  Thu Mar  8 13:34:33 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 EAC3F21F8648; Thu,  8 Mar 2012 13:34:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.985
X-Spam-Level: 
X-Spam-Status: No, score=-102.985 tagged_above=-999 required=5 tests=[AWL=-0.008, 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 90DNIuNQPA8A; Thu,  8 Mar 2012 13:34:31 -0800 (PST)
Received: from mail-tul01m020-f172.google.com (mail-tul01m020-f172.google.com [209.85.214.172]) by ietfa.amsl.com (Postfix) with ESMTP id C0CC221F8646; Thu,  8 Mar 2012 13:34:30 -0800 (PST)
Received: by obbta4 with SMTP id ta4so1334541obb.31 for <multiple recipients>; Thu, 08 Mar 2012 13:34:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=M//lSNI1QWNBzGqAm2ON2EfwXgGqw1kmtItYP9mDw4I=; b=yZ7n9wuzxSl8BHq+EZNAJStaYOBApwouVJROBrajDSpGUfK5FTIeD+s3+AEfXa8Li+ wty+TXsVUt5bIaAl1tUuH/zFclijNpaIdzFKuBjSlIc7DQ618XjBziQR5qpMt0d5AZ/C 1f2n2S8Qsumu9KgohW0VmgA7P9e0uCBTTrOVAV1J1B/KJ1EiVr3nXHED9j05WBYzbHaC IKouDOGgwbmD2OWXHfVXYmSAVI5c+boLf0NlDrZ4wDOFDbWit5gLg49tENPczT7YMnHB py9vGH3Unovqi2u3QgfUod1BvgJAqiZgt+6933jeLWRsAn1NeWPSLfiqD1hlgRBDWt93 gn5Q==
MIME-Version: 1.0
Received: by 10.182.75.103 with SMTP id b7mr425364obw.54.1331242470434; Thu, 08 Mar 2012 13:34:30 -0800 (PST)
Sender: barryleiba@gmail.com
Received: by 10.60.125.37 with HTTP; Thu, 8 Mar 2012 13:34:30 -0800 (PST)
In-Reply-To: <4F5920FF.6070502@piuha.net>
References: <20120214222316.CF29521E800E@ietfa.amsl.com> <201202152131.q1FLVB9E028114@cichlid.raleigh.ibm.com> <EF3C34EB-C0AA-45F2-ADE0-407CEF5172DD@juniper.net> <4F3E4EDB.7070509@piuha.net> <0E0C6A25-FBA6-4E11-9E89-DEBFFCF41108@juniper.net> <4F58EB8C.1000700@piuha.net> <70EB276F-D77E-45AE-851C-AB08A8D56D0A@juniper.net> <4F5920FF.6070502@piuha.net>
Date: Thu, 8 Mar 2012 16:34:30 -0500
X-Google-Sender-Auth: qV5aljO7K0nT7rSw8OSPjzF8QuM
Message-ID: <CALaySJKvS5QbtXuMx7TwFiL4hdgi1cT0sYu8EJtYLD6T2yOzKQ@mail.gmail.com>
Subject: Re: [lisp] WG Review: Recharter of Locator/ID Separation Protocol (lisp)
From: Barry Leiba <barryleiba@computer.org>
To: Jari Arkko <jari.arkko@piuha.net>
Content-Type: text/plain; charset=ISO-8859-1
Cc: John Scudder <jgs@juniper.net>, "lisp@ietf.org" <lisp@ietf.org>, "iesg@ietf.org IESG" <iesg@ietf.org>, "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Mar 2012 21:34:33 -0000

>> But it's not clear to me that these (especially architecture and impacts) can
>> be said to have been properly analyzed until some of the lower-priority items
>> (I'm thinking of threats, cache, ETR sync) have been fleshed out.
>
> I hear what you are saying. But I think the opinion in the IESG at least
> was, however, that those three really are high priority, and that other
> documents before them are not so useful before they are completed. I guess
> it is a different perspective, whether you do things top-down or bottom-up.
> I do agree with both points of view, actually.

The dependencies (threats, cache, ETR sync, and whatever else) can
certainly be discussed to the extent needed to lay out the
architecture and other priority documents, with notes taken and saved
for when other documents need to be produced.  That still says that
the working group needs to focus on discussion that leads to the
completion of the three priority documents first, before tackling the
others.  Everyone understands that these priority items can't be
developed in a vacuum; we just don't want things to wander off into
lower-level details such as protocol elements and text that can wait
for the next phase.

Barry

From mrex@sap.com  Thu Mar  8 13:48:46 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 5300021F8649 for <ietf@ietfa.amsl.com>; Thu,  8 Mar 2012 13:48:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.057
X-Spam-Level: 
X-Spam-Status: No, score=-10.057 tagged_above=-999 required=5 tests=[AWL=0.192, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FZ-XeEqUsnPh for <ietf@ietfa.amsl.com>; Thu,  8 Mar 2012 13:48:45 -0800 (PST)
Received: from smtpde01.sap-ag.de (smtpde01.sap-ag.de [155.56.68.170]) by ietfa.amsl.com (Postfix) with ESMTP id 4A84121F8644 for <ietf@ietf.org>; Thu,  8 Mar 2012 13:48:45 -0800 (PST)
Received: from mail.sap.corp by smtpde01.sap-ag.de (26) with ESMTP id q28Lmheu026005 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for <ietf@ietf.org>; Thu, 8 Mar 2012 22:48:43 +0100 (MET)
From: Martin Rex <mrex@sap.com>
Message-Id: <201203082148.q28LmgQV019885@fs4113.wdf.sap.corp>
Subject: Re: Add a link to the HTML version in i-d-announce mails ?
To: ietf@ietf.org
Date: Thu, 8 Mar 2012 22:48:42 +0100 (MET)
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-SAP: out
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: mrex@sap.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Mar 2012 21:48:46 -0000

The id-announce mails are defective.

I thought the proposal was to "ADD a URL" to the HTML/tools or
datatracker versions of the I-D, rather than remove the URL
to the versioned TXT file.

While Barry Leibas suggested Greasemonkey script curiously fixes the
404 error created by the recent change to the I-D announcements
for the Browser usage case, my download script that receives those
I-D announce mailings doesn't run GreaseMonkey, and would appreciate
the continuing presence of a URL to the versioned TXT file that
this particular announcement is about.

Otherwise I'm just fine with *ADD*ional URLs to either tools-HTML
or datatracker or both.

-Martin

From marka@isc.org  Thu Mar  8 15:22:12 2012
Return-Path: <marka@isc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C25ED21E8042 for <ietf@ietfa.amsl.com>; Thu,  8 Mar 2012 15:22:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.564
X-Spam-Level: 
X-Spam-Status: No, score=-2.564 tagged_above=-999 required=5 tests=[AWL=0.035,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8A-+hSKcf9zy for <ietf@ietfa.amsl.com>; Thu,  8 Mar 2012 15:22:11 -0800 (PST)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) by ietfa.amsl.com (Postfix) with ESMTP id DD57321E8050 for <ietf@ietf.org>; Thu,  8 Mar 2012 15:22:09 -0800 (PST)
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mail.isc.org", Issuer "RapidSSL CA" (not verified)) by mx.pao1.isc.org (Postfix) with ESMTPS id 0542AC9422; Thu,  8 Mar 2012 23:21:56 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (unknown [IPv6:2001:470:1f00:820:5df4:2bae:698c:ea04]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by bikeshed.isc.org (Postfix) with ESMTPSA id A0DAB216C31; Thu,  8 Mar 2012 23:21:55 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (Postfix) with ESMTP id DB8A81E34B2A; Fri,  9 Mar 2012 10:21:46 +1100 (EST)
To: mrex@sap.com
From: Mark Andrews <marka@isc.org>
References: <201203081845.q28IjGF0006949@fs4113.wdf.sap.corp>
Subject: Re: provisioning software, was DNS RRTYPEs, the difficulty with
In-reply-to: Your message of "Thu, 08 Mar 2012 19:45:16 BST." <201203081845.q28IjGF0006949@fs4113.wdf.sap.corp>
Date: Fri, 09 Mar 2012 10:21:46 +1100
Message-Id: <20120308232146.DB8A81E34B2A@drugs.dv.isc.org>
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Mar 2012 23:22:12 -0000

In message <201203081845.q28IjGF0006949@fs4113.wdf.sap.corp>, Martin Rex writes
:
> Tony Finch wrote:
> > 
> > Murray S. Kucherawy <msk@cloudmark.com> wrote:
> > >
> > > I looked at least at the titles of all the documents that update 1035,
> > > and none of them appear to be related to the above.  So where should we
> > > be looking?
> > 
> > The only thing I have found that implies NOTIMP doesn't apply to queries
> > for unknown RR types is in RFC 4074, "Common Misbehavior Against DNS
> > Queries for IPv6 Addresses":
> 
> Thanks for mentioning rfc 4074.  The stuff in that document matches
> the thoroughly broken behaviour of the IPv6 DNS resolver client of
> Windows 2003 that I had encountered just recently.
> 
> IMO, rfc4074 exhibits a significant amount of cluelessness about DNS,
> the "Full Standard" document maturity level, and the realities of
> backwards compatibilities for an incredibly huge installed base.

So not answering a query because the type is 28 matches RFC 1034
behaviour?  DNS is a query/response protocol.

So returning NXDOMAIN because the query type is 28 when you have
type 1 in the database matches RFC 1034 behaviour?

Returning A record content in software written *after* type code
28 was defined matched RFC 103[45] behaviour?  The same servers
shove A rdata into TXT rdata.  Everything is a A record.


> The answer to the question "what can I infer from a failed AAAA lookup"
> must be deduced from STD 13 **ALONE**, and it amounts to "very close to
> nothing at all".
> 
> Now this puts the slow adoption of IPv6 into perspective if it takes
> the IPv6 crowds >10 years to figure that one out, 
> 
> 
> -Martin
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org

From mrex@sap.com  Thu Mar  8 15:59:56 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 DF75921F86D1 for <ietf@ietfa.amsl.com>; Thu,  8 Mar 2012 15:59:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.04
X-Spam-Level: 
X-Spam-Status: No, score=-10.04 tagged_above=-999 required=5 tests=[AWL=0.209,  BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LsjEl7Ntap95 for <ietf@ietfa.amsl.com>; Thu,  8 Mar 2012 15:59:56 -0800 (PST)
Received: from smtpde01.sap-ag.de (smtpde01.sap-ag.de [155.56.68.170]) by ietfa.amsl.com (Postfix) with ESMTP id AC29B21F86D0 for <ietf@ietf.org>; Thu,  8 Mar 2012 15:59:55 -0800 (PST)
Received: from mail.sap.corp by smtpde01.sap-ag.de (26) with ESMTP id q28Nxq9r009005 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 9 Mar 2012 00:59:52 +0100 (MET)
From: Martin Rex <mrex@sap.com>
Message-Id: <201203082359.q28NxpwU027318@fs4113.wdf.sap.corp>
Subject: Re: provisioning software, was DNS RRTYPEs, the difficulty with
To: marka@isc.org (Mark Andrews)
Date: Fri, 9 Mar 2012 00:59:51 +0100 (MET)
In-Reply-To: <20120308232146.DB8A81E34B2A@drugs.dv.isc.org> from "Mark Andrews" at Mar 9, 12 10:21:46 am
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
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: Thu, 08 Mar 2012 23:59:57 -0000

Mark Andrews wrote:
> 
> Martin Rex writes:
> >
> > Thanks for mentioning rfc 4074.  The stuff in that document matches
> > the thoroughly broken behaviour of the IPv6 DNS resolver client of
> > Windows 2003 that I had encountered just recently.
> > 
> > IMO, rfc4074 exhibits a significant amount of cluelessness about DNS,
> > the "Full Standard" document maturity level, and the realities of
> > backwards compatibilities for an incredibly huge installed base.
> 
> So not answering a query because the type is 28 matches RFC 1034
> behaviour?  DNS is a query/response protocol.
> 
> So returning NXDOMAIN because the query type is 28 when you have
> type 1 in the database matches RFC 1034 behaviour?
> 
> Returning A record content in software written *after* type code
> 28 was defined matched RFC 103[45] behaviour?  The same servers
> shove A rdata into TXT rdata.  Everything is a A record.

We started this with the NOTIMP, which is certainly a permissible
response for an AAAA query per rfc1035.

What I briefly saw the win2003 DNS client doing in a wireshark trace
(which I forgot to save before I had to reboot after windows disabled
all networking) was visualized as a mixture of "no name" and "server fail"
for 23 consecutive AAAA lookups until ~18 seconds later the first A lookup
was finally sent.
I assume the two locally configured DNS Server were caching(-only) servers,
not authoritative ones (at least our current DNS Zones do not contain
NS records for any of the two).


Besides what you can deduce from the spec itself, you will also have
to take into account how that incredibly huge installed base was
created.  A number of software vendors perform only black-box testing
and limited interop testing, so it will not be unusual that your
AAAA queries may be the first queries of that kind that a DNS responder
might be seeing. 

So if the behaviour (how to exactly respond to queries for unknown
QTYPEs) is neither explicitly specified, nor likely have been part of
the usual/common interop tests performed by the vendor,
what you're left with might be "ureflected&untested guessing"
on part of the implementors to fill those gaps.

Bottom line, the receiver must be VERY conservative with assumptions
about what exactly can be infered from error responses for situations
that are fairly vague in the spec and potentially untested in the
installed base.  That is called "robustness principle".


-Martin

From mrex@sap.com  Thu Mar  8 17:07:44 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 283CA11E8073 for <ietf@ietfa.amsl.com>; Thu,  8 Mar 2012 17:07:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.042
X-Spam-Level: 
X-Spam-Status: No, score=-10.042 tagged_above=-999 required=5 tests=[AWL=0.207, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4GGjZ5mgm8jS for <ietf@ietfa.amsl.com>; Thu,  8 Mar 2012 17:07:43 -0800 (PST)
Received: from smtpde02.sap-ag.de (smtpde02.sap-ag.de [155.56.68.140]) by ietfa.amsl.com (Postfix) with ESMTP id 0EC6621E8010 for <ietf@ietf.org>; Thu,  8 Mar 2012 17:07:42 -0800 (PST)
Received: from mail.sap.corp by smtpde02.sap-ag.de (26) with ESMTP id q2917dXP003473 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 9 Mar 2012 02:07:39 +0100 (MET)
From: Martin Rex <mrex@sap.com>
Message-Id: <201203090107.q2917ctH001003@fs4113.wdf.sap.corp>
Subject: Re: provisioning software, was DNS RRTYPEs, the difficulty with
To: mrex@sap.com
Date: Fri, 9 Mar 2012 02:07:38 +0100 (MET)
In-Reply-To: <201203082359.q28NxpwU027318@fs4113.wdf.sap.corp> from "Martin Rex" at Mar 9, 12 00:59:51 am
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
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: Fri, 09 Mar 2012 01:07:44 -0000

Martin Rex wrote:
> 
> So if the behaviour (how to exactly respond to queries for unknown
> QTYPEs) is neither explicitly specified, nor likely have been part of
> the usual/common interop tests performed by the vendor,
> what you're left with might be "ureflected&untested guessing"
> on part of the implementors to fill those gaps.

What you typically have is a certain amount of code processing a query,
and some 3-4 conditions under which this code fails, and where the
implementor will have to decide which RCODE to return.  The choices
available in rfc1035 are:

RCODE           Response code - this 4 bit field is set as part of
                responses.  The values have the following
                interpretation:

                0               No error condition

                1               Format error - The name server was
                                unable to interpret the query.

                2               Server failure - The name server was
                                unable to process this query due to a
                                problem with the name server.

                3               Name Error - Meaningful only for
                                responses from an authoritative name
                                server, this code signifies that the
                                domain name referenced in the query does
                                not exist.

                4               Not Implemented - The name server does
                                not support the requested kind of query.

                5               Refused - The name server refuses to
                                perform the specified operation for
                                policy reasons.  For example, a name
                                server may not wish to provide the
                                information to the particular requester,
                                or a name server may not wish to perform
                                a particular operation (e.g., zone
                                transfer) for particular data.

                6-15            Reserved for future use.


The choice between RCODEs 1, 2 and 4 for failed AAAA queries
might be fairly random, the description for 3 is slightly confusing
in whether a DNS server might use this RCODE "creatively" by
returning it without AA.

For an implementor that is being told "do not use use RCODE 4 for
unknown QTYPES", not sending any response at all to an unsupported
AAAA query seems like a reasonable choice.


-Martin

From mrex@sap.com  Thu Mar  8 17:08:34 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 27C4C21E8048 for <ietf@ietfa.amsl.com>; Thu,  8 Mar 2012 17:08:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.043
X-Spam-Level: 
X-Spam-Status: No, score=-10.043 tagged_above=-999 required=5 tests=[AWL=0.206, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CGeYzc-BCoVD for <ietf@ietfa.amsl.com>; Thu,  8 Mar 2012 17:08:33 -0800 (PST)
Received: from smtpde01.sap-ag.de (smtpde01.sap-ag.de [155.56.68.170]) by ietfa.amsl.com (Postfix) with ESMTP id E160411E8072 for <ietf@ietf.org>; Thu,  8 Mar 2012 17:08:32 -0800 (PST)
Received: from mail.sap.corp by smtpde01.sap-ag.de (26) with ESMTP id q2918UYE015847 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 9 Mar 2012 02:08:30 +0100 (MET)
From: Martin Rex <mrex@sap.com>
Message-Id: <201203090108.q2918TcT001035@fs4113.wdf.sap.corp>
Subject: Re: provisioning software, was DNS RRTYPEs, the difficulty with
To: mrex@sap.com
Date: Fri, 9 Mar 2012 02:08:29 +0100 (MET)
In-Reply-To: <201203090107.q2917ctH001003@fs4113.wdf.sap.corp> from "Martin Rex" at Mar 9, 12 02:07:38 am
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
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: Fri, 09 Mar 2012 01:08:34 -0000

Sorry,

s/some 3-4 conditions/some 3-4 dozen conditions/

Martin Rex wrote:
> 
> Martin Rex wrote:
> > 
> > So if the behaviour (how to exactly respond to queries for unknown
> > QTYPEs) is neither explicitly specified, nor likely have been part of
> > the usual/common interop tests performed by the vendor,
> > what you're left with might be "ureflected&untested guessing"
> > on part of the implementors to fill those gaps.
> 
> What you typically have is a certain amount of code processing a query,
> and some 3-4 conditions under which this code fails, and where the
> implementor will have to decide which RCODE to return.  The choices
> available in rfc1035 are:
> 
> RCODE           Response code - this 4 bit field is set as part of
>                 responses.  The values have the following
>                 interpretation:
> 
>                 0               No error condition
> 
>                 1               Format error - The name server was
>                                 unable to interpret the query.
> 
>                 2               Server failure - The name server was
>                                 unable to process this query due to a
>                                 problem with the name server.
> 
>                 3               Name Error - Meaningful only for
>                                 responses from an authoritative name
>                                 server, this code signifies that the
>                                 domain name referenced in the query does
>                                 not exist.
> 
>                 4               Not Implemented - The name server does
>                                 not support the requested kind of query.
> 
>                 5               Refused - The name server refuses to
>                                 perform the specified operation for
>                                 policy reasons.  For example, a name
>                                 server may not wish to provide the
>                                 information to the particular requester,
>                                 or a name server may not wish to perform
>                                 a particular operation (e.g., zone
>                                 transfer) for particular data.
> 
>                 6-15            Reserved for future use.
> 
> 
> The choice between RCODEs 1, 2 and 4 for failed AAAA queries
> might be fairly random, the description for 3 is slightly confusing
> in whether a DNS server might use this RCODE "creatively" by
> returning it without AA.
> 
> For an implementor that is being told "do not use use RCODE 4 for
> unknown QTYPES", not sending any response at all to an unsupported
> AAAA query seems like a reasonable choice.
> 
> 
> -Martin
> 


From marka@isc.org  Thu Mar  8 17:15:52 2012
Return-Path: <marka@isc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8056621F8499 for <ietf@ietfa.amsl.com>; Thu,  8 Mar 2012 17:15:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.566
X-Spam-Level: 
X-Spam-Status: No, score=-2.566 tagged_above=-999 required=5 tests=[AWL=0.033,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JPTspXZfVxwO for <ietf@ietfa.amsl.com>; Thu,  8 Mar 2012 17:15:51 -0800 (PST)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) by ietfa.amsl.com (Postfix) with ESMTP id BA44421F8498 for <ietf@ietf.org>; Thu,  8 Mar 2012 17:15:51 -0800 (PST)
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mail.isc.org", Issuer "RapidSSL CA" (not verified)) by mx.pao1.isc.org (Postfix) with ESMTPS id 6FB90C9422; Fri,  9 Mar 2012 01:15:41 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (unknown [IPv6:2001:470:1f00:820:5df4:2bae:698c:ea04]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by bikeshed.isc.org (Postfix) with ESMTPSA id ABD0E216C31; Fri,  9 Mar 2012 01:15:40 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (Postfix) with ESMTP id 9AAB41E35B28; Fri,  9 Mar 2012 12:15:33 +1100 (EST)
To: mrex@sap.com
From: Mark Andrews <marka@isc.org>
References: <201203082359.q28NxpwU027318@fs4113.wdf.sap.corp>
Subject: Re: provisioning software, was DNS RRTYPEs, the difficulty with
In-reply-to: Your message of "Fri, 09 Mar 2012 00:59:51 BST." <201203082359.q28NxpwU027318@fs4113.wdf.sap.corp>
Date: Fri, 09 Mar 2012 12:15:33 +1100
Message-Id: <20120309011533.9AAB41E35B28@drugs.dv.isc.org>
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Mar 2012 01:15:52 -0000

In message <201203082359.q28NxpwU027318@fs4113.wdf.sap.corp>, Martin Rex writes
:
> Mark Andrews wrote:
> > 
> > Martin Rex writes:
> > >
> > > Thanks for mentioning rfc 4074.  The stuff in that document matches
> > > the thoroughly broken behaviour of the IPv6 DNS resolver client of
> > > Windows 2003 that I had encountered just recently.
> > > 
> > > IMO, rfc4074 exhibits a significant amount of cluelessness about DNS,
> > > the "Full Standard" document maturity level, and the realities of
> > > backwards compatibilities for an incredibly huge installed base.
> > 
> > So not answering a query because the type is 28 matches RFC 1034
> > behaviour?  DNS is a query/response protocol.
> > 
> > So returning NXDOMAIN because the query type is 28 when you have
> > type 1 in the database matches RFC 1034 behaviour?
> > 
> > Returning A record content in software written *after* type code
> > 28 was defined matched RFC 103[45] behaviour?  The same servers
> > shove A rdata into TXT rdata.  Everything is a A record.
> 
> We started this with the NOTIMP, which is certainly a permissible
> response for an AAAA query per rfc1035.
> 
> What I briefly saw the win2003 DNS client doing in a wireshark trace
> (which I forgot to save before I had to reboot after windows disabled
> all networking) was visualized as a mixture of "no name" and "server fail"
> for 23 consecutive AAAA lookups until ~18 seconds later the first A lookup
> was finally sent.
> I assume the two locally configured DNS Server were caching(-only) servers,
> not authoritative ones (at least our current DNS Zones do not contain
> NS records for any of the two).
> 
> 
> Besides what you can deduce from the spec itself, you will also have
> to take into account how that incredibly huge installed base was
> created.  A number of software vendors perform only black-box testing
> and limited interop testing, so it will not be unusual that your
> AAAA queries may be the first queries of that kind that a DNS responder
> might be seeing. 

The incredibly huge base that returned NOERROR to type 28 queries
when AAAA was defined.  Almost all of the offending boxes were
designed after AAAA was defined.

Lots of them get responses to RFC 1035 types wrong.  If you don't
implement the type then you can't load the zone if it contains the
type, partial zone loads are not permitted as per RFC 1035.  If you
have loaded the zone then the type doesn't exist, so it doesn't
matter that you don't implement it, you therefore can't match the
type as per RFC 1034 so the answer is NOERROR or NXDOMAIN depending
apon whether the name exists in the zone or not.


> So if the behaviour (how to exactly respond to queries for unknown
> QTYPEs) is neither explicitly specified, nor likely have been part of
> the usual/common interop tests performed by the vendor,
> what you're left with might be "ureflected&untested guessing"
> on part of the implementors to fill those gaps.
> 
> Bottom line, the receiver must be VERY conservative with assumptions
> about what exactly can be infered from error responses for situations
> that are fairly vague in the spec and potentially untested in the
> installed base.  That is called "robustness principle".

Which is why there are lots of SERVFAILs as you can't infer anything
from NOTIMP.
 
> -Martin
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org

From marka@isc.org  Thu Mar  8 18:04:17 2012
Return-Path: <marka@isc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 74E4821F84E7 for <ietf@ietfa.amsl.com>; Thu,  8 Mar 2012 18:04:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.567
X-Spam-Level: 
X-Spam-Status: No, score=-2.567 tagged_above=-999 required=5 tests=[AWL=0.032,  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 Ecmevib9dce2 for <ietf@ietfa.amsl.com>; Thu,  8 Mar 2012 18:04:16 -0800 (PST)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [IPv6:2001:500:60::65]) by ietfa.amsl.com (Postfix) with ESMTP id A234821F84E6 for <ietf@ietf.org>; Thu,  8 Mar 2012 18:04:16 -0800 (PST)
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mail.isc.org", Issuer "RapidSSL CA" (not verified)) by mx.ams1.isc.org (Postfix) with ESMTPS id BC0165F98C5; Fri,  9 Mar 2012 02:04:02 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (unknown [IPv6:2001:470:1f00:820:5df4:2bae:698c:ea04]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by bikeshed.isc.org (Postfix) with ESMTPSA id 474B5216C31; Fri,  9 Mar 2012 02:04:00 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (Postfix) with ESMTP id 07C8C1E36085; Fri,  9 Mar 2012 13:03:56 +1100 (EST)
To: mrex@sap.com
From: Mark Andrews <marka@isc.org>
References: <201203090107.q2917ctH001003@fs4113.wdf.sap.corp>
Subject: Re: provisioning software, was DNS RRTYPEs, the difficulty with
In-reply-to: Your message of "Fri, 09 Mar 2012 02:07:38 BST." <201203090107.q2917ctH001003@fs4113.wdf.sap.corp>
Date: Fri, 09 Mar 2012 13:03:55 +1100
Message-Id: <20120309020356.07C8C1E36085@drugs.dv.isc.org>
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Mar 2012 02:04:17 -0000

In message <201203090107.q2917ctH001003@fs4113.wdf.sap.corp>, Martin Rex writes
:
> Martin Rex wrote:
> > 
> > So if the behaviour (how to exactly respond to queries for unknown
> > QTYPEs) is neither explicitly specified, nor likely have been part of
> > the usual/common interop tests performed by the vendor,
> > what you're left with might be "ureflected&untested guessing"
> > on part of the implementors to fill those gaps.
> 
> What you typically have is a certain amount of code processing a query,
> and some 3-4 conditions under which this code fails, and where the
> implementor will have to decide which RCODE to return.  The choices
> available in rfc1035 are:
> 
> RCODE           Response code - this 4 bit field is set as part of
>                 responses.  The values have the following
>                 interpretation:
> 
>                 0               No error condition
> 
>                 1               Format error - The name server was
>                                 unable to interpret the query.
> 
>                 2               Server failure - The name server was
>                                 unable to process this query due to a
>                                 problem with the name server.
> 
>                 3               Name Error - Meaningful only for
>                                 responses from an authoritative name
>                                 server, this code signifies that the
>                                 domain name referenced in the query does
>                                 not exist.
> 
>                 4               Not Implemented - The name server does
>                                 not support the requested kind of query.
> 
>                 5               Refused - The name server refuses to
>                                 perform the specified operation for
>                                 policy reasons.  For example, a name
>                                 server may not wish to provide the
>                                 information to the particular requester,
>                                 or a name server may not wish to perform
>                                 a particular operation (e.g., zone
>                                 transfer) for particular data.
> 
>                 6-15            Reserved for future use.
> 
> 
> The choice between RCODEs 1, 2 and 4 for failed AAAA queries
> might be fairly random, the description for 3 is slightly confusing
> in whether a DNS server might use this RCODE "creatively" by
> returning it without AA.
> 
> For an implementor that is being told "do not use use RCODE 4 for
> unknown QTYPES", not sending any response at all to an unsupported
> AAAA query seems like a reasonable choice.

They are much more likely to have been told "you should be sending
NOERROR or NXDOMAIN not NOTIMP" rather than just "you should not
be sending NOTIMP".

There are nameservers that don't respond to EDNS queries for type
A, class IN.  FORMERR, NOTIMP, REFUSED all trigger a retry with
plain DNS.  Silence is much harder to work out what to do with and
it takes muuuuuuuuuch loooooooooooonger.  As silence can be caused
by lots of things not just EDNS so you can't infer anything if you
succeed with plain DNS.  Success after FORMERR, NOTIMP or REFUSED,
for an otherwise identical query, is a reasonable indication that
EDNS is not supported.

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

From mrex@sap.com  Thu Mar  8 18:23:15 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 BBA2111E8085 for <ietf@ietfa.amsl.com>; Thu,  8 Mar 2012 18:23:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.045
X-Spam-Level: 
X-Spam-Status: No, score=-10.045 tagged_above=-999 required=5 tests=[AWL=0.204, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tSyBBl540dsh for <ietf@ietfa.amsl.com>; Thu,  8 Mar 2012 18:23:14 -0800 (PST)
Received: from smtpde02.sap-ag.de (smtpde02.sap-ag.de [155.56.68.140]) by ietfa.amsl.com (Postfix) with ESMTP id 827EF11E8083 for <ietf@ietf.org>; Thu,  8 Mar 2012 18:23:14 -0800 (PST)
Received: from mail.sap.corp by smtpde02.sap-ag.de (26) with ESMTP id q292NBMx011686 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 9 Mar 2012 03:23:11 +0100 (MET)
From: Martin Rex <mrex@sap.com>
Message-Id: <201203090223.q292NAZS005402@fs4113.wdf.sap.corp>
Subject: Re: provisioning software, was DNS RRTYPEs, the difficulty with
To: marka@isc.org (Mark Andrews)
Date: Fri, 9 Mar 2012 03:23:10 +0100 (MET)
In-Reply-To: <20120309011533.9AAB41E35B28@drugs.dv.isc.org> from "Mark Andrews" at Mar 9, 12 12:15:33 pm
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
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: Fri, 09 Mar 2012 02:23:15 -0000

Mark Andrews wrote:
> 
> The incredibly huge base that returned NOERROR to type 28 queries
> when AAAA was defined.  Almost all of the offending boxes were
> designed after AAAA was defined.


When AAAA was defined is marginally relevant.  Since IPv6 was designed
as a completely seperate universe, it was flying below the radar
for most software apps developers for >10 years.  I was first bothered
about IPv6 in 2004.

Had there been versions of BIND exhibiting such behaviour?

I know that during its development, BIND sometimes adopted annoying
unnecessary backwards-incompatible changes that caused folks to
not upgrade.  IIRC, suddenly refusing to load zone with hostnames
containing underscores was one BIND change I remember from my early
days as DNS admin, that caused me to ignore BIND software updates
for several years (waiting for the "offending" hosts to die of age).


> 
> Lots of them get responses to RFC 1035 types wrong.  If you don't
> implement the type then you can't load the zone if it contains the
> type, partial zone loads are not permitted as per RFC 1035.

"not permitted" would require a "must not", but
I only see a "should not" here:
http://tools.ietf.org/html/rfc1035#section-5.2


>
> If you have loaded the zone then the type doesn't exist, so it doesn't
> matter that you don't implement it, you therefore can't match the
> type as per RFC 1034 so the answer is NOERROR or NXDOMAIN depending
> apon whether the name exists in the zone or not.

>From these discussions, your explanations and my latest reading of
1034/1035 I believe I have a hunch what might have happened (to our
internal DNS) when my w2k3 IPv6 stack freaked out...

It might be related to the particular fashion in which I originally
set up the private DNS universe as an intern in 1993.  And while I
joined development in 1995 and the tools I had written to to generate
the DNS zone files got replaced ~1999 with a commercial solution,
the structure of the private DNS universe seems to be still the
way I originally set it up.

Thank you for your patience and elaborate responses.


> 
> > So if the behaviour (how to exactly respond to queries for unknown
> > QTYPEs) is neither explicitly specified, nor likely have been part of
> > the usual/common interop tests performed by the vendor,
> > what you're left with might be "ureflected&untested guessing"
> > on part of the implementors to fill those gaps.
> > 
> > Bottom line, the receiver must be VERY conservative with assumptions
> > about what exactly can be infered from error responses for situations
> > that are fairly vague in the spec and potentially untested in the
> > installed base.  That is called "robustness principle".
> 
> Which is why there are lots of SERVFAILs as you can't infer anything
> from NOTIMP.

Servfail is supposed to be a transient error.

What should a _new_ recursive non-authoritative server send as response
back to the stub resolver when it encounters a NOTIMP response from the
authoritative server for an AAAA query?


-Martin

From marka@isc.org  Thu Mar  8 18:56:49 2012
Return-Path: <marka@isc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C01A21F853B for <ietf@ietfa.amsl.com>; Thu,  8 Mar 2012 18:56:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.568
X-Spam-Level: 
X-Spam-Status: No, score=-2.568 tagged_above=-999 required=5 tests=[AWL=0.031,  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 vujw9zs7nUy4 for <ietf@ietfa.amsl.com>; Thu,  8 Mar 2012 18:56:48 -0800 (PST)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) by ietfa.amsl.com (Postfix) with ESMTP id 09E6921F8539 for <ietf@ietf.org>; Thu,  8 Mar 2012 18:56:48 -0800 (PST)
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mail.isc.org", Issuer "RapidSSL CA" (not verified)) by mx.pao1.isc.org (Postfix) with ESMTPS id C6A51C9425; Fri,  9 Mar 2012 02:56:33 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (unknown [IPv6:2001:470:1f00:820:5df4:2bae:698c:ea04]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by bikeshed.isc.org (Postfix) with ESMTPSA id 31DC7216C31; Fri,  9 Mar 2012 02:56:33 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (Postfix) with ESMTP id E66A81E366B7; Fri,  9 Mar 2012 13:56:23 +1100 (EST)
To: mrex@sap.com
From: Mark Andrews <marka@isc.org>
References: <201203090223.q292NAZS005402@fs4113.wdf.sap.corp>
Subject: Re: provisioning software, was DNS RRTYPEs, the difficulty with
In-reply-to: Your message of "Fri, 09 Mar 2012 03:23:10 BST." <201203090223.q292NAZS005402@fs4113.wdf.sap.corp>
Date: Fri, 09 Mar 2012 13:56:23 +1100
Message-Id: <20120309025623.E66A81E366B7@drugs.dv.isc.org>
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Mar 2012 02:56:49 -0000

In message <201203090223.q292NAZS005402@fs4113.wdf.sap.corp>, Martin Rex writes
:
> Mark Andrews wrote:
> > 
> > The incredibly huge base that returned NOERROR to type 28 queries
> > when AAAA was defined.  Almost all of the offending boxes were
> > designed after AAAA was defined.
> 
> 
> When AAAA was defined is marginally relevant.  Since IPv6 was designed
> as a completely seperate universe, it was flying below the radar
> for most software apps developers for >10 years.  I was first bothered
> about IPv6 in 2004.
> 
> Had there been versions of BIND exhibiting such behaviour?

No.  Unknown types were always NOERROR/NXDOMAIN.
 
> I know that during its development, BIND sometimes adopted annoying
> unnecessary backwards-incompatible changes that caused folks to
> not upgrade.  IIRC, suddenly refusing to load zone with hostnames
> containing underscores was one BIND change I remember from my early
> days as DNS admin, that caused me to ignore BIND software updates
> for several years (waiting for the "offending" hosts to die of age).

Which was controllable behaviour.
 
> > Lots of them get responses to RFC 1035 types wrong.  If you don't
> > implement the type then you can't load the zone if it contains the
> > type, partial zone loads are not permitted as per RFC 1035.
> 
> "not permitted" would require a "must not", but
> I only see a "should not" here:
> http://tools.ietf.org/html/rfc1035#section-5.2

RFC 1035 pre-dates the formalisation of MUST NOT/SHOULD NOT etc.

5.2. Use of master files to define zones

When a master file is used to load a zone, the operation should be
suppressed if any errors are encountered in the master file.  The
rationale for this is that a single error can have widespread
consequences.  For example, suppose that the RRs defining a delegation
have syntax errors; then the server will return authoritative name
errors for all names in the subzone (except in the case where the
subzone is also present on the server).

How anyone could rationalize serving a zone with missing data after
reading that I don't know.  I do know that doing so does cause
operational problems and fixing named to stop serving the zone on
load errors was was one of the ealier things I did.

> > If you have loaded the zone then the type doesn't exist, so it doesn't
> > matter that you don't implement it, you therefore can't match the
> > type as per RFC 1034 so the answer is NOERROR or NXDOMAIN depending
> > apon whether the name exists in the zone or not.
> 
> From these discussions, your explanations and my latest reading of
> 1034/1035 I believe I have a hunch what might have happened (to our
> internal DNS) when my w2k3 IPv6 stack freaked out...
> 
> It might be related to the particular fashion in which I originally
> set up the private DNS universe as an intern in 1993.  And while I
> joined development in 1995 and the tools I had written to to generate
> the DNS zone files got replaced ~1999 with a commercial solution,
> the structure of the private DNS universe seems to be still the
> way I originally set it up.
> 
> Thank you for your patience and elaborate responses.
> 
> 
> > > So if the behaviour (how to exactly respond to queries for unknown
> > > QTYPEs) is neither explicitly specified, nor likely have been part of
> > > the usual/common interop tests performed by the vendor,
> > > what you're left with might be "ureflected&untested guessing"
> > > on part of the implementors to fill those gaps.
> > > 
> > > Bottom line, the receiver must be VERY conservative with assumptions
> > > about what exactly can be infered from error responses for situations
> > > that are fairly vague in the spec and potentially untested in the
> > > installed base.  That is called "robustness principle".
> > 
> > Which is why there are lots of SERVFAILs as you can't infer anything
> > from NOTIMP.
> 
> Servfail is supposed to be a transient error.
> 
> What should a _new_ recursive non-authoritative server send as response
> back to the stub resolver when it encounters a NOTIMP response from the
> authoritative server for an AAAA query?

Well the server should try the next server for the zone.  If all of them
return NOTIMP, SERVFAIL/NOTIMP.


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

From sant9442@gmail.com  Thu Mar  8 19:39:33 2012
Return-Path: <sant9442@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F160221E801C for <ietf@ietfa.amsl.com>; Thu,  8 Mar 2012 19:39:33 -0800 (PST)
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.278, BAYES_00=-2.599, MISSING_HEADERS=1.292, 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 T0lu2DUBPn7D for <ietf@ietfa.amsl.com>; Thu,  8 Mar 2012 19:39:33 -0800 (PST)
Received: from mail-gy0-f172.google.com (mail-gy0-f172.google.com [209.85.160.172]) by ietfa.amsl.com (Postfix) with ESMTP id E43A221E8010 for <ietf@ietf.org>; Thu,  8 Mar 2012 19:39:32 -0800 (PST)
Received: by ghbg16 with SMTP id g16so741644ghb.31 for <ietf@ietf.org>; Thu, 08 Mar 2012 19:39:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=94fwCZIVBY6tsECrPjieS0VzyIQz981XupNgdhztN3E=; b=zO0CdXvhVPN6iWO7ESKdajXVgq+y4Mv7tVxO0jxNSH/+39t4jPTJyr6Mgnst2zyh2S 7d9IkebpSAX7jcBcvu+aOwWIvnViKAUOFXJkbHxF5hU4GZH5PgLRaiLGlJmcAf1p97AV JlQLn05T8qDuZpsfKWKUfM/B7EVtoYZzDh/2mkt4/jwrp9fK7v9AupmwWFzWC2Qd+uUn DHLNKM1BPG4a3IJLJ7DqzPYjDkw++RmepTf7f4BGGpl1yA6ZcOed06Fbd4h4spMGG321 9wlKaFZjUmWMthaC5ajwjFXRfTTfGQBJFHxZ+5q4zBOkLnTF+4Hs7hIHqxGbV9tMYkty eYfw==
Received: by 10.236.76.138 with SMTP id b10mr688592yhe.34.1331264372573; Thu, 08 Mar 2012 19:39:32 -0800 (PST)
Received: from adsl-215-50-126.mia.bellsouth.net (99-3-147-93.lightspeed.miamfl.sbcglobal.net. [99.3.147.93]) by mx.google.com with ESMTPS id a24sm6952151ana.10.2012.03.08.19.39.29 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 08 Mar 2012 19:39:30 -0800 (PST)
Message-ID: <4F597BB4.7070600@gmail.com>
Date: Thu, 08 Mar 2012 22:40:36 -0500
From: Hector <sant9442@gmail.com>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
CC: ietf@ietf.org
Subject: Re: provisioning software, was DNS RRTYPEs, the difficulty with
References: <201203090223.q292NAZS005402@fs4113.wdf.sap.corp> <20120309025623.E66A81E366B7@drugs.dv.isc.org>
In-Reply-To: <20120309025623.E66A81E366B7@drugs.dv.isc.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Mar 2012 03:39:34 -0000

Mark Andrews wrote:

>> What should a _new_ recursive non-authoritative server send as response
>> back to the stub resolver when it encounters a NOTIMP response from the
>> authoritative server for an AAAA query?
> 
> Well the server should try the next server for the zone.  If all of them
> return NOTIMP, SERVFAIL/NOTIMP.

+1, this seems logical.

What is perhaps ultimately important to a developer is its application 
translation of DNS query results, including the application tracking 
for the redundancy of failures.  *Rhetorically,* does a NOIMP enable 
an automated trigger to disable a specific DOMAIN query?  Should a 
protocol translate SERVFAIL as an application temporary or permanent 
failure?  Can a temp status change to permanent due to redundancy?, etc.

--
HLS

From mrex@sap.com  Thu Mar  8 20:22:36 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 DA3A821E8017 for <ietf@ietfa.amsl.com>; Thu,  8 Mar 2012 20:22:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.05
X-Spam-Level: 
X-Spam-Status: No, score=-10.05 tagged_above=-999 required=5 tests=[AWL=0.199,  BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uyffapv7IEcM for <ietf@ietfa.amsl.com>; Thu,  8 Mar 2012 20:22:36 -0800 (PST)
Received: from smtpde02.sap-ag.de (smtpde02.sap-ag.de [155.56.68.140]) by ietfa.amsl.com (Postfix) with ESMTP id C3FE021E8012 for <ietf@ietf.org>; Thu,  8 Mar 2012 20:22:35 -0800 (PST)
Received: from mail.sap.corp by smtpde02.sap-ag.de (26) with ESMTP id q294MSlR025279 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 9 Mar 2012 05:22:33 +0100 (MET)
From: Martin Rex <mrex@sap.com>
Message-Id: <201203090422.q294MRA2012090@fs4113.wdf.sap.corp>
Subject: Re: provisioning software, was DNS RRTYPEs, the difficulty with
To: marka@isc.org (Mark Andrews)
Date: Fri, 9 Mar 2012 05:22:27 +0100 (MET)
In-Reply-To: <20120309025623.E66A81E366B7@drugs.dv.isc.org> from "Mark Andrews" at Mar 9, 12 01:56:23 pm
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
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: Fri, 09 Mar 2012 04:22:37 -0000

Mark Andrews wrote:
> 
> > 
> > "not permitted" would require a "must not", but
> > I only see a "should not" here:
> > http://tools.ietf.org/html/rfc1035#section-5.2
> 
> RFC 1035 pre-dates the formalisation of MUST NOT/SHOULD NOT etc.
> 
> 5.2. Use of master files to define zones
> 
> When a master file is used to load a zone, the operation should be
> suppressed if any errors are encountered in the master file.  The
> rationale for this is that a single error can have widespread
> consequences.  For example, suppose that the RRs defining a delegation
> have syntax errors; then the server will return authoritative name
> errors for all names in the subzone (except in the case where the
> subzone is also present on the server).
> 
> How anyone could rationalize serving a zone with missing data after
> reading that I don't know.  I do know that doing so does cause
> operational problems and fixing named to stop serving the zone on
> load errors was was one of the ealier things I did.

A zone file loaded by a DNS server is not necessarily an authoritative
zone file! And for a non-authoritative zone, a partial zone might
be considerably better than no data at all.

In 1993 we had a worldwide private network with modate-size links
to remote locations and the links would occasionally fail for a
few hours.  So I setup *all* DNS servers (primary&secondaries,
delegated primaries&secondaries and caching-only) to obtain all
zones via XFER in a tree structure.


-Martin

From narten@us.ibm.com  Thu Mar  8 21:53:11 2012
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B950821F855B for <ietf@ietfa.amsl.com>; Thu,  8 Mar 2012 21:53:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.663
X-Spam-Level: 
X-Spam-Status: No, score=-109.663 tagged_above=-999 required=5 tests=[AWL=0.936, 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 lmJd9hz9VZXt for <ietf@ietfa.amsl.com>; Thu,  8 Mar 2012 21:53:09 -0800 (PST)
Received: from e2.ny.us.ibm.com (e2.ny.us.ibm.com [32.97.182.142]) by ietfa.amsl.com (Postfix) with ESMTP id 9AC1021F8551 for <ietf@ietf.org>; Thu,  8 Mar 2012 21:53:08 -0800 (PST)
Received: from /spool/local by e2.ny.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <ietf@ietf.org> from <narten@us.ibm.com>; Fri, 9 Mar 2012 00:53:07 -0500
Received: from d01dlp02.pok.ibm.com (9.56.224.85) by e2.ny.us.ibm.com (192.168.1.102) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Fri, 9 Mar 2012 00:53:05 -0500
Received: from d01relay05.pok.ibm.com (d01relay05.pok.ibm.com [9.56.227.237]) by d01dlp02.pok.ibm.com (Postfix) with ESMTP id 065636E804A for <ietf@ietf.org>; Fri,  9 Mar 2012 00:53:05 -0500 (EST)
Received: from d01av04.pok.ibm.com (d01av04.pok.ibm.com [9.56.224.64]) by d01relay05.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id q295r4wU257388 for <ietf@ietf.org>; Fri, 9 Mar 2012 00:53:04 -0500
Received: from d01av04.pok.ibm.com (loopback [127.0.0.1]) by d01av04.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id q295r4BS017920 for <ietf@ietf.org>; Fri, 9 Mar 2012 00:53:04 -0500
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.27.192.143]) by d01av04.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id q295r3aT017883 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Fri, 9 Mar 2012 00:53:04 -0500
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [127.0.0.1]) by rotala.raleigh.ibm.com (8.14.4/8.12.5) with ESMTP id q295r3tJ006722 for <ietf@ietf.org>; Fri, 9 Mar 2012 00:53:03 -0500
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.4/8.14.4/Submit) id q295r2eV006684 for ietf@ietf.org; Fri, 9 Mar 2012 00:53:02 -0500
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201203090553.q295r2eV006684@rotala.raleigh.ibm.com>
Date: Fri, 09 Mar 2012 00:53:02 -0500
To: ietf@ietf.org
Subject: Weekly posting summary for ietf@ietf.org
User-Agent: Heirloom mailx 12.5 7/5/10
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 12030905-5112-0000-0000-000006032340
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Mar 2012 05:53:11 -0000

Total of 202 messages in the last 7 days.
 
script run at: Fri Mar  9 00:53:02 EST 2012
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
  9.90% |   20 |  9.92% |   155968 | marka@isc.org
  8.42% |   17 |  7.10% |   111637 | johnl@iecc.com
  7.43% |   15 |  7.41% |   116450 | ned+ietf@mauve.mrochek.com
  5.94% |   12 |  5.89% |    92615 | barryleiba@computer.org
  5.45% |   11 |  4.58% |    72027 | mrex@sap.com
  4.46% |    9 |  4.61% |    72420 | scott@kitterman.com
  4.46% |    9 |  4.45% |    69929 | sant9442@gmail.com
  4.46% |    9 |  3.78% |    59420 | msk@cloudmark.com
  3.47% |    7 |  4.29% |    67514 | randy@qualcomm.com
  3.47% |    7 |  3.84% |    60422 | alexey.melnikov@isode.com
  2.97% |    6 |  2.86% |    44951 | stpeter@stpeter.im
  2.97% |    6 |  2.72% |    42688 | vesely@tana.it
  1.98% |    4 |  1.96% |    30866 | dougb@dougbarton.us
  1.98% |    4 |  1.66% |    26077 | mnot@mnot.net
  1.98% |    4 |  1.65% |    25950 | paf@frobbit.se
  1.98% |    4 |  1.51% |    23670 | dot@dotat.at
  1.49% |    3 |  1.99% |    31265 | stbryant@cisco.com
  0.99% |    2 |  2.35% |    37002 | jari.arkko@piuha.net
  1.49% |    3 |  1.63% |    25596 | daedulus@btconnect.com
  1.49% |    3 |  1.44% |    22594 | housley@vigilsec.com
  1.49% |    3 |  1.20% |    18908 | ynir@checkpoint.com
  0.99% |    2 |  1.66% |    26131 | mustapha.aissaoui@alcatel-lucent.com
  1.49% |    3 |  1.04% |    16403 | julian.reschke@gmx.de
  1.49% |    3 |  1.01% |    15855 | randy@psg.com
  0.99% |    2 |  1.06% |    16640 | alberto@it.uc3m.es
  0.99% |    2 |  0.98% |    15386 | paulej@packetizer.com
  0.99% |    2 |  0.84% |    13183 | framefritti@gmail.com
  0.99% |    2 |  0.82% |    12933 | xavier.marjou@gmail.com
  0.99% |    2 |  0.78% |    12301 | warren@kumari.net
  0.50% |    1 |  1.04% |    16345 | ve7jtb@ve7jtb.com
  0.50% |    1 |  0.94% |    14724 | amalis@gmail.com
  0.50% |    1 |  0.84% |    13215 | nurit.sprecher@nsn.com
  0.50% |    1 |  0.79% |    12466 | lear@cisco.com
  0.50% |    1 |  0.78% |    12251 | dwing@cisco.com
  0.50% |    1 |  0.73% |    11549 | agmalis@gmail.com
  0.50% |    1 |  0.69% |    10772 | jdrake@juniper.net
  0.50% |    1 |  0.66% |    10443 | john-ietf@jck.com
  0.50% |    1 |  0.61% |     9532 | r.e.sonneveld@sonnection.nl
  0.50% |    1 |  0.60% |     9408 | narten@us.ibm.com
  0.50% |    1 |  0.59% |     9219 | sob@sobco.com
  0.50% |    1 |  0.56% |     8793 | tnadeau@lucidvision.com
  0.50% |    1 |  0.52% |     8254 | d3e3e3@gmail.com
  0.50% |    1 |  0.51% |     8084 | julien.meuric@orange.com
  0.50% |    1 |  0.51% |     7951 | hsantos@isdg.net
  0.50% |    1 |  0.49% |     7670 | paul.hoffman@vpnc.org
  0.50% |    1 |  0.48% |     7600 | sm@resistor.net
  0.50% |    1 |  0.47% |     7350 | bernard_aboba@hotmail.com
  0.50% |    1 |  0.46% |     7270 | tony@att.com
  0.50% |    1 |  0.46% |     7201 | eran@hueniverse.com
  0.50% |    1 |  0.41% |     6475 | adrian@olddog.co.uk
  0.50% |    1 |  0.39% |     6206 | ajs@anvilwalrusden.com
  0.50% |    1 |  0.39% |     6122 | tbray@textuality.com
  0.50% |    1 |  0.36% |     5711 | patrik@frobbit.se
  0.50% |    1 |  0.35% |     5474 | simon.perreault@viagenie.ca
  0.50% |    1 |  0.34% |     5334 | dhc@dcrocker.net
--------+------+--------+----------+------------------------
100.00% |  202 |100.00% |  1572220 | Total


From marka@isc.org  Thu Mar  8 22:04:34 2012
Return-Path: <marka@isc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AC9CA21F85B6 for <ietf@ietfa.amsl.com>; Thu,  8 Mar 2012 22:04:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.569
X-Spam-Level: 
X-Spam-Status: No, score=-2.569 tagged_above=-999 required=5 tests=[AWL=0.030,  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 ixOv87xApJ3w for <ietf@ietfa.amsl.com>; Thu,  8 Mar 2012 22:04:33 -0800 (PST)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) by ietfa.amsl.com (Postfix) with ESMTP id BE7C621F85B1 for <ietf@ietf.org>; Thu,  8 Mar 2012 22:04:33 -0800 (PST)
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mail.isc.org", Issuer "RapidSSL CA" (not verified)) by mx.pao1.isc.org (Postfix) with ESMTPS id 4FDE1C942D; Fri,  9 Mar 2012 06:04:22 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (unknown [IPv6:2001:470:1f00:820:5df4:2bae:698c:ea04]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by bikeshed.isc.org (Postfix) with ESMTPSA id ED850216C33; Fri,  9 Mar 2012 06:04:21 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (Postfix) with ESMTP id 795971E3BCA7; Fri,  9 Mar 2012 17:04:04 +1100 (EST)
To: mrex@sap.com
From: Mark Andrews <marka@isc.org>
References: <201203090422.q294MRA2012090@fs4113.wdf.sap.corp>
Subject: Re: provisioning software, was DNS RRTYPEs, the difficulty with
In-reply-to: Your message of "Fri, 09 Mar 2012 05:22:27 BST." <201203090422.q294MRA2012090@fs4113.wdf.sap.corp>
Date: Fri, 09 Mar 2012 17:04:03 +1100
Message-Id: <20120309060404.795971E3BCA7@drugs.dv.isc.org>
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Mar 2012 06:04:34 -0000

In message <201203090422.q294MRA2012090@fs4113.wdf.sap.corp>, Martin Rex writes
:
> Mark Andrews wrote:
> > 
> > > 
> > > "not permitted" would require a "must not", but
> > > I only see a "should not" here:
> > > http://tools.ietf.org/html/rfc1035#section-5.2
> > 
> > RFC 1035 pre-dates the formalisation of MUST NOT/SHOULD NOT etc.
> > 
> > 5.2. Use of master files to define zones
> > 
> > When a master file is used to load a zone, the operation should be
> > suppressed if any errors are encountered in the master file.  The
> > rationale for this is that a single error can have widespread
> > consequences.  For example, suppose that the RRs defining a delegation
> > have syntax errors; then the server will return authoritative name
> > errors for all names in the subzone (except in the case where the
> > subzone is also present on the server).
> > 
> > How anyone could rationalize serving a zone with missing data after
> > reading that I don't know.  I do know that doing so does cause
> > operational problems and fixing named to stop serving the zone on
> > load errors was was one of the ealier things I did.
> 
> A zone file loaded by a DNS server is not necessarily an authoritative
> zone file! And for a non-authoritative zone, a partial zone might
> be considerably better than no data at all.

You were still authoritative for it, just not a official server.
The act of loading from a zone file makes you authoritative.  Your
content may have been slightly older if it had been updated on the
master but it was still complete for the version of the zone you
had.  You were also within the expected tolerences for changes to
be made visible to everyone.  Those are specified in the SOA record.

> In 1993 we had a worldwide private network with modate-size links
> to remote locations and the links would occasionally fail for a
> few hours.  So I setup *all* DNS servers (primary&secondaries,
> delegated primaries&secondaries and caching-only) to obtain all
> zones via XFER in a tree structure.
> 
> 
> -Martin
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org

From bortzmeyer@nic.fr  Fri Mar  9 01:57:42 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 6687D21F8610 for <ietf@ietfa.amsl.com>; Fri,  9 Mar 2012 01:57:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.456
X-Spam-Level: 
X-Spam-Status: No, score=-102.456 tagged_above=-999 required=5 tests=[AWL=0.143, 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 Iv8nmMs0eP1i for <ietf@ietfa.amsl.com>; Fri,  9 Mar 2012 01:57:41 -0800 (PST)
Received: from mx2.nic.fr (mx2.nic.fr [IPv6:2001:660:3003:2::4:11]) by ietfa.amsl.com (Postfix) with ESMTP id 3C86221F8611 for <ietf@ietf.org>; Fri,  9 Mar 2012 01:57:41 -0800 (PST)
Received: from mx2.nic.fr (localhost [127.0.0.1]) by mx2.nic.fr (Postfix) with SMTP id 152531C012A; Fri,  9 Mar 2012 10:57:40 +0100 (CET)
Received: by mx2.nic.fr (Postfix, from userid 500) id F36FE1C0131; Fri,  9 Mar 2012 10:57:37 +0100 (CET)
Received: from relay1.nic.fr (relay1.nic.fr [IPv6:2001:67c:2218:9::4:162]) by mx2.nic.fr (Postfix) with ESMTP id C2C061C012A; Fri,  9 Mar 2012 10:57:37 +0100 (CET)
Received: from bortzmeyer.nic.fr (batilda.nic.fr [IPv6:2001:67c:2219:8::6:69]) by relay1.nic.fr (Postfix) with ESMTP id C04FD4C0081; Fri,  9 Mar 2012 10:57:37 +0100 (CET)
Date: Fri, 9 Mar 2012 10:57:37 +0100
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: "John R. Levine" <johnl@iecc.com>
Subject: Re: provisioning software, was DNS RRTYPEs, the difficulty with
Message-ID: <20120309095737.GA13215@nic.fr>
References: <alpine.BSF.2.00.1203061203020.14450@joyce.lan> <20120306220911.8B52C1E1DE9F@drugs.dv.isc.org> <alpine.BSF.2.00.1203061711470.25059@joyce.lan> <20120307024247.EF0151E2080D@drugs.dv.isc.org> <alpine.BSF.2.00.1203062148410.34594@joyce.lan> <D468354F-BE26-41D4-9F75-EA10C5189B73@frobbit.se> <20120307075414.6E63A1E23E05@drugs.dv.isc.org> <alpine.BSF.2.00.1203070926260.60146@joyce.lan> <20120307214922.2833D1E269AE@drugs.dv.isc.org> <alpine.BSF.2.00.1203071719100.78429@joyce.lan>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <alpine.BSF.2.00.1203071719100.78429@joyce.lan>
X-Operating-System: Debian GNU/Linux wheezy/sid
X-Kernel: Linux 3.1.0-1-686-pae i686
Organization: NIC France
X-URL: http://www.nic.fr/
User-Agent: Mutt/1.5.21 (2010-09-15)
X-Bogosity: No, tests=bogofilter, spamicity=0.000000, version=1.1.5
X-PMX-Version: 5.4.6.353000, Antispam-Engine: 2.6.1.350677, Antispam-Data: 2012.3.9.94519
X-PerlMx-Spam: Gauge=IIIIIIII, Probability=8%, Report='MULTIPLE_RCPTS 0.1, HTML_00_01 0.05, HTML_00_10 0.05, BODYTEXTP_SIZE_3000_LESS 0, BODY_SIZE_1000_LESS 0, BODY_SIZE_2000_LESS 0, BODY_SIZE_5000_LESS 0, BODY_SIZE_600_699 0, BODY_SIZE_7000_LESS 0, __ANY_URI 0, __BOUNCE_CHALLENGE_SUBJ 0, __BOUNCE_NDR_SUBJ_EXEMPT 0, __CD 0, __CP_URI_IN_BODY 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __MULTIPLE_RCPTS_CC_X2 0, __SANE_MSGID 0, __SUBJ_ALPHA_END 0, __TO_MALFORMED_2 0, __USER_AGENT 0'
Cc: "ietf@ietf.org Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Mar 2012 09:57:42 -0000

On Wed, Mar 07, 2012 at 05:21:40PM -0500,
 John R. Levine <johnl@iecc.com> wrote 
 a message of 22 lines which said:

> Could you give some concrete examples of DNS provisioning systems
> that let you enter arbitrary RRs?  I've never seen one in the wild,
> other than the one I wrote for myself.

My registrar and DNS hoster, Gandi <http://www.gandi.net/> allows it,
in a mode called "Expert mode". As its name suggest, it is not easy to
use (you have to translate the record in RFC1035-section5 format
yourself).

There is of course a "User mode" with the usual closed list of known
types, and easy entry of values.


From bortzmeyer@nic.fr  Fri Mar  9 02:01:56 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 6995221F8613 for <ietf@ietfa.amsl.com>; Fri,  9 Mar 2012 02:01:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.464
X-Spam-Level: 
X-Spam-Status: No, score=-102.464 tagged_above=-999 required=5 tests=[AWL=0.135, 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 9oo7EMIwFYBx for <ietf@ietfa.amsl.com>; Fri,  9 Mar 2012 02:01:55 -0800 (PST)
Received: from mx2.nic.fr (mx2.nic.fr [IPv6:2001:660:3003:2::4:11]) by ietfa.amsl.com (Postfix) with ESMTP id 7DB5D21F8610 for <ietf@ietf.org>; Fri,  9 Mar 2012 02:01:55 -0800 (PST)
Received: from mx2.nic.fr (localhost [127.0.0.1]) by mx2.nic.fr (Postfix) with SMTP id D57331C0131; Fri,  9 Mar 2012 11:01:54 +0100 (CET)
Received: by mx2.nic.fr (Postfix, from userid 500) id C05D91C012E; Fri,  9 Mar 2012 11:01:52 +0100 (CET)
Received: from relay1.nic.fr (relay1.nic.fr [IPv6:2001:67c:2218:9::4:162]) by mx2.nic.fr (Postfix) with ESMTP id A03131C012E; Fri,  9 Mar 2012 11:01:52 +0100 (CET)
Received: from bortzmeyer.nic.fr (batilda.nic.fr [IPv6:2001:67c:2219:8::6:69]) by relay1.nic.fr (Postfix) with ESMTP id 9DB514C0081; Fri,  9 Mar 2012 11:01:52 +0100 (CET)
Date: Fri, 9 Mar 2012 11:01:52 +0100
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: Mark Andrews <marka@isc.org>
Subject: Re: provisioning software, was DNS RRTYPEs, the difficulty with
Message-ID: <20120309100152.GB13215@nic.fr>
References: <201203072304.q27N4GdX000106@fs4113.wdf.sap.corp> <20120307232733.7A20F1E27B66@drugs.dv.isc.org> <9452079D1A51524AA5749AD23E00392807EFEF@exch-mbx901.corp.cloudmark.com> <20120308021024.560681E29350@drugs.dv.isc.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20120308021024.560681E29350@drugs.dv.isc.org>
X-Operating-System: Debian GNU/Linux wheezy/sid
X-Kernel: Linux 3.1.0-1-686-pae i686
Organization: NIC France
X-URL: http://www.nic.fr/
User-Agent: Mutt/1.5.21 (2010-09-15)
X-Bogosity: No, tests=bogofilter, spamicity=0.000017, version=1.1.5
X-PMX-Version: 5.4.6.353000, Antispam-Engine: 2.6.1.350677, Antispam-Data: 2012.3.9.95132
X-PerlMx-Spam: Gauge=IIIIIIII, Probability=8%, Report='MULTIPLE_RCPTS 0.1, HTML_00_01 0.05, HTML_00_10 0.05, BODYTEXTP_SIZE_3000_LESS 0, BODY_SIZE_1000_LESS 0, BODY_SIZE_2000_LESS 0, BODY_SIZE_5000_LESS 0, BODY_SIZE_7000_LESS 0, BODY_SIZE_700_799 0, __ANY_URI 0, __BOUNCE_CHALLENGE_SUBJ 0, __BOUNCE_NDR_SUBJ_EXEMPT 0, __CD 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __MULTIPLE_RCPTS_CC_X2 0, __SANE_MSGID 0, __SUBJ_ALPHA_END 0, __TO_MALFORMED_2 0, __URI_NO_PATH 0, __URI_NO_WWW 0, __USER_AGENT 0'
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Mar 2012 10:01:56 -0000

On Thu, Mar 08, 2012 at 01:10:24PM +1100,
 Mark Andrews <marka@isc.org> wrote 
 a message of 45 lines which said:

> Randy claimed that presentation formats were not standardised.  They
> are.  Randy and others claimed that the presentation formats were
> owned by BIND and they are not.

A better description of the situation would be "there is a standard
format, standardized in section 5 of RFC 1035 and in many other RFC
for new RR types" and "its standard description is quite poor, with
many unspecified things, so, in practice, a zone file accepted by a
compliant implementation may not always work with another". Today, the
IESG would never accept the sloppy language of RFC 1035.

Also, some programs added non-standard extensions to this format (such
as BIND's $TTL).

From marka@isc.org  Fri Mar  9 03:57:57 2012
Return-Path: <marka@isc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9668821F8606 for <ietf@ietfa.amsl.com>; Fri,  9 Mar 2012 03:57:57 -0800 (PST)
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 sp+dunSYOsQP for <ietf@ietfa.amsl.com>; Fri,  9 Mar 2012 03:57:57 -0800 (PST)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) by ietfa.amsl.com (Postfix) with ESMTP id 2C91321F85F1 for <ietf@ietf.org>; Fri,  9 Mar 2012 03:57:57 -0800 (PST)
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mail.isc.org", Issuer "RapidSSL CA" (not verified)) by mx.pao1.isc.org (Postfix) with ESMTPS id C3133C9432; Fri,  9 Mar 2012 11:57:40 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (unknown [IPv6:2001:470:1f00:820:9de6:a1ff:53de:99cf]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by bikeshed.isc.org (Postfix) with ESMTPSA id 6426F216C36; Fri,  9 Mar 2012 11:57:40 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (Postfix) with ESMTP id A93F71E3D336; Fri,  9 Mar 2012 22:57:36 +1100 (EST)
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>
From: Mark Andrews <marka@isc.org>
References: <201203072304.q27N4GdX000106@fs4113.wdf.sap.corp> <20120307232733.7A20F1E27B66@drugs.dv.isc.org> <9452079D1A51524AA5749AD23E00392807EFEF@exch-mbx901.corp.cloudmark.com> <20120308021024.560681E29350@drugs.dv.isc.org> <20120309100152.GB13215@nic.fr>
Subject: Re: provisioning software, was DNS RRTYPEs, the difficulty with
In-reply-to: Your message of "Fri, 09 Mar 2012 11:01:52 BST." <20120309100152.GB13215@nic.fr>
Date: Fri, 09 Mar 2012 22:57:36 +1100
Message-Id: <20120309115736.A93F71E3D336@drugs.dv.isc.org>
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Mar 2012 11:57:57 -0000

In message <20120309100152.GB13215@nic.fr>, Stephane Bortzmeyer writes:
> Also, some programs added non-standard extensions to this format (such
> as BIND's $TTL).

$TTL is defined in RFC 2181.

$GENERATE is a BIND extension and is documented as such.

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

From jgs@juniper.net  Thu Mar  8 12:56:13 2012
Return-Path: <jgs@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 9561C21F8607; Thu,  8 Mar 2012 12:56:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.508
X-Spam-Level: 
X-Spam-Status: No, score=-6.508 tagged_above=-999 required=5 tests=[AWL=0.091,  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 c9XjsAQ-jIaE; Thu,  8 Mar 2012 12:56:12 -0800 (PST)
Received: from exprod7og123.obsmtp.com (exprod7og123.obsmtp.com [64.18.2.24]) by ietfa.amsl.com (Postfix) with ESMTP id 7AA4621F85F0; Thu,  8 Mar 2012 12:56:10 -0800 (PST)
Received: from P-EMHUB02-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob123.postini.com ([64.18.6.12]) with SMTP ID DSNKT1kc6YdbjxVyYe28acgDU4lwkqddEkik@postini.com; Thu, 08 Mar 2012 12:56:12 PST
Received: from EMBX02-HQ.jnpr.net ([fe80::18fe:d666:b43e:f97e]) by P-EMHUB02-HQ.jnpr.net ([fe80::88f9:77fd:dfc:4d51%11]) with mapi; Thu, 8 Mar 2012 12:51:10 -0800
From: John Scudder <jgs@juniper.net>
To: Jari Arkko <jari.arkko@piuha.net>
Date: Thu, 8 Mar 2012 12:51:10 -0800
Subject: Re: [lisp] WG Review: Recharter of Locator/ID Separation Protocol (lisp)
Thread-Topic: [lisp] WG Review: Recharter of Locator/ID Separation Protocol (lisp)
Thread-Index: Acz9bTEhFSoZro7BRVCb+DADC+uVCQ==
Message-ID: <70EB276F-D77E-45AE-851C-AB08A8D56D0A@juniper.net>
References: <20120214222316.CF29521E800E@ietfa.amsl.com> <201202152131.q1FLVB9E028114@cichlid.raleigh.ibm.com> <EF3C34EB-C0AA-45F2-ADE0-407CEF5172DD@juniper.net> <4F3E4EDB.7070509@piuha.net> <0E0C6A25-FBA6-4E11-9E89-DEBFFCF41108@juniper.net> <4F58EB8C.1000700@piuha.net>
In-Reply-To: <4F58EB8C.1000700@piuha.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="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Fri, 09 Mar 2012 08:25:02 -0800
Cc: "iesg@ietf.org IESG" <iesg@ietf.org>, "ietf@ietf.org list" <ietf@ietf.org>, "lisp@ietf.org" <lisp@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Mar 2012 20:56:13 -0000

Jari,

This is pretty good, thank you. I have one further comment. You guys have p=
rioritized three of the work items:

"The first three items (architecture, deployment models, impacts) need
to be completed first before other items can be submitted as RFCs."

But it's not clear to me that these (especially architecture and impacts) c=
an be said to have been properly analyzed until some of the lower-priority =
items (I'm thinking of threats, cache, ETR sync) have been fleshed out. So =
although I understand your desire to move these three forward I question wh=
ether the strong mandate to do them first is a good idea. Possibly continue=
 to state that they're a priority without actually gating other work, so th=
at the WG can make its own decision about working on dependencies as needed=
?

--John

On Mar 8, 2012, at 12:25 PM, Jari Arkko wrote:

Thanks for your feedback, John. Would a modified charter with these changes=
 work for you:

Jari

<charter-as-modified.txt><charter-as-modifi-from-propos.diff.html>


From nkukich@verilan.com  Fri Mar  9 11:32:16 2012
Return-Path: <nkukich@verilan.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 41F7021E8062 for <ietf@ietfa.amsl.com>; Fri,  9 Mar 2012 11:32:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qPlk32BSzEVJ for <ietf@ietfa.amsl.com>; Fri,  9 Mar 2012 11:32:15 -0800 (PST)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id 8CD3921E8091 for <ietf@ietf.org>; Fri,  9 Mar 2012 11:32:15 -0800 (PST)
Received: by yhpp34 with SMTP id p34so1194366yhp.31 for <ietf@ietf.org>; Fri, 09 Mar 2012 11:32:15 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=from:content-type:content-transfer-encoding:subject:date:message-id :to:mime-version:x-mailer:x-gm-message-state; bh=Z2cQn1NXcc5vFlv+WhLNAYY7h/yRrc5PJ3QU6jZY+uQ=; b=IFApK+5xk6Yfmrt9VmZvkG3V6/Or3noYW5Hk4YaKtmYGTgU2t9eONE5NGIVkHl5WXZ N+Gx+P9TDsLhOqaVZIoewQT8cy4nMlxviqD3QMUOUEAa7BBkTW2LlXZBHNrop7k+MkM7 V+uV+YxrUtbdiBoemZOrGWSfbxUWR8YgpMhoqihL5zZITdDoFbc1oqRIXxlFytkczsOG iMFcTc63NWvxv9WqBhq/lDsWcYuiHFP1rLsTWHMWCxfxBIhf6o6jM7M36L695878ZHB6 dPWKp4pD+jdlxAs6VOs/S39QwS+/U0ielxczayc09E4RKf04t1pX9G/zpNYW4HheVysa tMmg==
Received: by 10.68.74.74 with SMTP id r10mr6210506pbv.83.1331321534651; Fri, 09 Mar 2012 11:32:14 -0800 (PST)
Received: from [10.196.0.202] ([199.91.192.129]) by mx.google.com with ESMTPS id i1sm4961298pbj.70.2012.03.09.11.32.12 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 09 Mar 2012 11:32:13 -0800 (PST)
From: Nick Kukich <nkukich@verilan.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: IETF83 Audio Streaming info
Date: Fri, 9 Mar 2012 13:32:10 -0600
Message-Id: <1D286EF9-D15F-4EFD-896B-F61E23332D9B@verilan.com>
To: ietf@ietf.org
Mime-Version: 1.0 (Apple Message framework v1084)
X-Mailer: Apple Mail (2.1084)
X-Gm-Message-State: ALoCoQnx4y/VZuxgWOVWPKO/tNkp9bTwQ/E+ezrGF3L++bS3W9o6Y/CO3AMnaOGCEZQXUrITbuMM
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Mar 2012 19:32:16 -0000

Greetings!

We're two weeks out from the beginning of meeting streaming. For those
interested in monitoring sessions or participating remotely the
following information may prove useful.

For general remote participation including meetecho support see:

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

-Audio Streaming-

All 8 parallel tracks at the IETF 83 meeting will be broadcast starting
with the commencement of working group sessions on Monday, March 26 2012
at 0900 CET (GMT+1) and continue until the close of sessions on Friday,
March 30.

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

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

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

-Jabber/XMPP-

For information on IETF Jabber participation see:

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

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

-Webex-

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

-Ticketing-

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

mtd@ietf.org

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

Thanks!

Nick Kukich
Verilan, Inc.


From loa@pi.nu  Mon Mar 12 01:31:51 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 8618D21F86D0 for <ietf@ietfa.amsl.com>; Mon, 12 Mar 2012 01:31:51 -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.024, 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 onKyVcsESa2G for <ietf@ietfa.amsl.com>; Mon, 12 Mar 2012 01:31:50 -0700 (PDT)
Received: from mail.pi.nu (mail.pi.nu [194.71.127.148]) by ietfa.amsl.com (Postfix) with ESMTP id 4E51721F86E5 for <ietf@ietf.org>; Mon, 12 Mar 2012 01:31:44 -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 693A82A8002 for <ietf@ietf.org>; Mon, 12 Mar 2012 09:31:42 +0100 (CET)
Message-ID: <4F5DB46F.10009@pi.nu>
Date: Mon, 12 Mar 2012 09:31:43 +0100
From: Loa Andersson <loa@pi.nu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: [PWE3] FW: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt>(Allocation of	an Associated Channel Code Point for Use byITU-T Ethernet	based OAM) to Informational RFC
References: <20120222151252.32262.82157.idtracker@ietfa.amsl.com> <039f01ccf174$fe79d780$fb6d8680$@olddog.co.uk> <44F4E579A764584EA9BDFD07D0CA0813075C936F@tlvmail1> <4F4B7EA2.7070305@cisco.com> <4F4B8A75.6000207@pi.nu>
In-Reply-To: <4F4B8A75.6000207@pi.nu>
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, 12 Mar 2012 08:31:51 -0000

All,

I've been asked to clarify thee comments in this mail, I done
so by proposing new text to draft-betts-.

I hope this helps.


Title
=====

Comment: We want to assign a Associated Channel Type. The registry
that it  will be assigned from is "Pseudowire Associated Channel
Types"; however RFC 5586, makes the Channel Types generic and I
think the title should be changed as follows:

OLD:
Allocation of an Associated Channel Code Point for Use by ITU-T
Ethernet based OAM

NEW:
Allocation of an Generic Associated Channel Type for ITU-T
MPLS-TP OAM

Note: Neither MPLS-TP or OAM are in the RFC Editors list of wellknown
acronyms, therfore the title probably should be:

NEW:
Allocation of an Generic Associated Channel Type for ITU-T
MPLS Transport Profile Operation, Maintenance and Administration.


Introduction - first paragraph
==============================

In the first paragraph of the introduction, there seems to be an
oddity in the description of the role of the ietf-tp-oam-analysis
document.  Instead of:

OLD
"tools defined by the IETF [I-D.ietf-mpls-tp-oam-analysis], that
are intended to meet the OAM functional requirements defined in
[RFC5860]."

NEW:
"tools described by the IETF [I-D.ietf-mpls-tp-oam-analysis], which
are used to meet the OAM functional requirements defined
in [RFC5860]."

Intrduction - second paragraph
==============================

The next paragraph in describing G.8113.1, stumbles over the current
vs anticipated future state of G.8113.1 and its relationship to
its antecedents.  I'm a bit un-certain about the correct terminology,
but I think the following change would improve the document.

OLD:

The ITU-T has documented, in draft new Recommendation [G.8113.1], the
use of Ethernet based OAM mechanisms, originally defined in [Y.1731],
carried in the MPLS Generic Associated Channel (G-ACh). This approach
requires the allocation of an ACH Type from the registry of ACH types
maintained by IANA in order that the messages that will be described
in [G.8113.1] can be identified by an implementation.

NEW:

"The ITU-T has Draft Recommendation [G.8113.1] documented MPLS OAM
which as of this writing is undergoing the ITU-T Traditional
Approval Process (TAP). This Recommendation builds upon Ethernet
OAM as documented in [Y.1731]. The messages in [G.8113.1] are defined
to be carried in a new Associated Channel Type in the MPLS Generaic
  Associated Channel (G-Ach).  In order to carry these messages in an
interoperable fashion, an Associated Channel Type from the IANA
maintained registry "Pseudowire Associated Channel Types is to be
used."

Note there are confusion around some of the Associated Channel
acronyms that are refledted in this document.

ACh is Associated Channel
ACH is Associated Chamnnel Header
G-ACh is Generic Associated Channel

"ACH Type" is not used anywhere in IETF documents; we talk about
Associated Channel Type or Generic Associated Channel Type
(G-ACh Type).

Introduction - third paragraph
==============================

In the third paragraph, there seems to be an unnecessary reference
to experimental types.  When asking for a code point for a standard,
it is not helped to bring up experimental code space.  Can we remove
the text reading:

OLD:
"without continuing to resorting to the use of an experimental
ACH Type,"

NEW
-


Section 2 - first paragraph
===========================



In section 2, the first sentence refers to Ethernet based OAM
messages. As far as I know, the messages in G.8113.1 are either
MPLS-TP OAM messages, or they are simply the OAM messages defined
in G.8113.1.  The simplest path to clarity would seem to be to
replace "Ethernet based OAM messages" in that sentence with
"messages".

The second sentence of that paragraph does not seem to say anything
we need to say.  Can we remove it?

OLD:

    The code point allocated by this document is intended to be used only
    for Ethernet based OAM messages, defined in the ITU-T Recommendation
    [G.8113.1], carried in the G-ACh . These Ethernet based OAM messages
    and procedures, address the OAM functional requirements defined in
    [RFC5860]. Other message types should not be carried behind this code
    point.

NEW:

    The code point allocated by this document is intended to be used
    only for OAM messages, defined in the ITU-T Recommendation
    [G.8113.1], carried in the G-ACh . Other message types should not
    be carried behind this Associated Channel Type.

Section 2 - second paragraph
============================

A matter of some clarity, can we change this paragrap like this:

OLD:
    This code point may be used on any transport construct that uses
    the G-ACh, e.g., MPLS-TP Sections, MPLS-TP LSPs or PWs.

NEW:

    The Generic Associated Channel Type assigned by this
    document may be used on any transport construct that uses the
    G-ACh, e.g., MPLS-TP Sections, MPLS-TP LSPs or PWs as specified
    by G.8113.1.


Section 2 - third paragraph
===========================

With regard to revisions, which is what I think the third paragraph
is about, I am not clear what you are trying to say.  A code point
allocation must point to a stable referent.  If the desired referent
changes, then process needs to be followed to make sure that the IANA
is updated in accordance with IETF procedures.  Hence, I am left to
the conclusion that the third paragraph is actually asking for
something we can not do.  Can we remove that?

OLD:
    All ITU-T Recommendations are subject to revisions. Therefore, the
    code point allocated by this document may be used for future versions
    of [G.8113.1].

NEW:
    -








On 2012-02-27 14:51, Loa Andersson wrote:
> All,
>
> I agree with Stewart, while shortage of code points might be a reason
> to think twice before allocating one, "abundance" in itself is never
> a reason to allocate code points.
>
> I'm way less inclined to approve of this draft in the condition it
> is now. Actually I believe that we should think very careful before
> approving it at all.
>
> /Loa
>
> On 2012-02-27 14:01, Stewart Bryant wrote:
>>
>> Daniel
>>
>> Shortage of ACh types was never an issue.
>>
>> The issue issue is the concerns articulated in
>> draft-sprecher-mpls-tp-oam-considerations
>>
>> Stewart
>>
>>
>> On 23/02/2012 10:35, Daniel Cohn wrote:
>>> Support - as there is no foreseen shortage in ACH types, I don't see a
>>> reason why this code point should not be allocated to an ITU developed
>>> protocol that is already deployed in the field.
>>>
>>> DC
>>>
>>>> -----Original Message-----
>>>> From: ietf-announce-bounces@ietf.org [mailto:ietf-announce-
>>>> bounces@ietf.org] On Behalf Of The IESG
>>>> Sent: 22 February 2012 15:13
>>>> To: IETF-Announce
>>>> Subject: Last Call:<draft-betts-itu-oam-ach-code-point-03.txt>
>>> (Allocation of
>>> an
>>>> Associated Channel Code Point for Use by ITU-T Ethernet based OAM) to
>>>> Informational RFC
>>>>
>>>>
>>>> The IESG has received a request from an individual submitter to
>>> consider
>>>> the following document:
>>>> - 'Allocation of an Associated Channel Code Point for Use by ITU-T
>>>> Ethernet based OAM'
>>>> <draft-betts-itu-oam-ach-code-point-03.txt> as an 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-03-21. 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 assigns an Associated Channel Type code point for
>>>> carrying Ethernet based Operations, Administration, and Management
>>>> messages in the MPLS Generic Associated Channel (G-ACh).
>>>>
>>>> The file can be obtained via
>>>> http://datatracker.ietf.org/doc/draft-betts-itu-oam-ach-code-point/
>>>>
>>>> IESG discussion can be tracked via
>>>> http://datatracker.ietf.org/doc/draft-betts-itu-oam-ach-code-point/
>>>>
>>>>
>>>> No IPR declarations have been submitted directly on this I-D.
>>>> _______________________________________________
>>>> IETF-Announce mailing list
>>>> IETF-Announce@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/ietf-announce
>>> _______________________________________________
>>> pwe3 mailing list
>>> pwe3@ietf.org
>>> https://www.ietf.org/mailman/listinfo/pwe3
>>> _______________________________________________
>>> Ietf mailing list
>>> Ietf@ietf.org
>>> https://www.ietf.org/mailman/listinfo/ietf
>>>
>>
>>
>

-- 


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 ben@nostrum.com  Mon Mar 12 09:15:17 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 36CE511E8085; Mon, 12 Mar 2012 09:15:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.253
X-Spam-Level: 
X-Spam-Status: No, score=-102.253 tagged_above=-999 required=5 tests=[AWL=-0.253, BAYES_00=-2.599, J_CHICKENPOX_22=0.6, 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 pnTJwz3Li+GF; Mon, 12 Mar 2012 09:15:16 -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 8E8AF11E8083; Mon, 12 Mar 2012 09:15:16 -0700 (PDT)
Received: from [10.0.1.2] (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 q2CGFFnC099573 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 12 Mar 2012 11:15:16 -0500 (CDT) (envelope-from ben@nostrum.com)
From: Ben Campbell <ben@nostrum.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Gen-ART LC/Telechat review of draft-reschke-http-status-308-05
Date: Mon, 12 Mar 2012 11:15:25 -0500
Message-Id: <27FD8C7A-7636-4D60-A65E-C2B264857A0E@nostrum.com>
To: draft-reschke-http-status-308.all@tools.ietf.org
Mime-Version: 1.0 (Apple Message framework v1257)
X-Mailer: Apple Mail (2.1257)
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: Mon, 12 Mar 2012 16:15:17 -0000

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at
< http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

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

Document: draft-reschke-http-status-308-05
Reviewer: Ben Campbell=09
Review Date: 2012-03-12
IETF LC End Date: 2012-03-16
IESG Telechat date: 2012-03-15

Summary: This draft is basically ready for publication as an =
experimental RFC. I have a few minor comments that might be worth =
considering whether they would improve the document prior to =
publication.=20

Note: Since this draft is on a Telechat that precedes the end of the =
IETF Last Call, this review serves as both the LC and Telechat review.


Major issues:

None:

Minor issues:

-- General: I see some discussion about existing UA behavior, but =
nothing about what a UA should do with a 308 other than as an =
implication the fact that this is a "permanent version of 307". It's =
probably worth describing that explicitly. (Or is that what the "clients =
with link-editing capabilities" statement is intended to do?If so, does =
that cover everything?)

-- section 1, last paragraph:=20

The fact that a 308 can't change the method is left as an implication of =
being based on 307. It would be good to state that explicitly and =
normatively here.

-- section 3, 1st paragraph: "Clients with link-editing capabilities =
ought to..."

Should that be stated normatively?

-- section 3, third paragraph: "The new permanent URI SHOULD be =
given..."

I'm curious why that is not a MUST. Is there a reasonable (i.e. =
interoperable)  way to send a 308 _without_ a URI in the location field? =
Is the meta refresh directive something that can be used _instead_ of =
the Location header field?

-- section 4:=20

The example uses _both_ the location field and the HTML <meta> refresh =
directive. Is this considered a recommended practice to the degree you =
might normatively recommend it in the text?

Nits/editorial comments:

None=

From julian.reschke@gmx.de  Mon Mar 12 10:16:35 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 D63DF21F8876 for <ietf@ietfa.amsl.com>; Mon, 12 Mar 2012 10:16:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.299
X-Spam-Level: 
X-Spam-Status: No, score=-106.299 tagged_above=-999 required=5 tests=[AWL=-4.300, BAYES_00=-2.599, J_CHICKENPOX_22=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id y4zlpmkkikAa for <ietf@ietfa.amsl.com>; Mon, 12 Mar 2012 10:16:35 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by ietfa.amsl.com (Postfix) with SMTP id B34F821F8865 for <ietf@ietf.org>; Mon, 12 Mar 2012 10:16:34 -0700 (PDT)
Received: (qmail invoked by alias); 12 Mar 2012 17:16:31 -0000
Received: from unknown (EHLO [192.168.2.100]) [89.204.137.43] by mail.gmx.net (mp020) with SMTP; 12 Mar 2012 18:16:31 +0100
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1+kEIFGWjWkmCGQRYBEJYfNklfhtZykzVsyvzhcDP aTB+P0vbnwIsZ3
Message-ID: <4F5E2F65.1000706@gmx.de>
Date: Mon, 12 Mar 2012 18:16:21 +0100
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: Ben Campbell <ben@nostrum.com>
Subject: Re: Gen-ART LC/Telechat review of draft-reschke-http-status-308-05
References: <27FD8C7A-7636-4D60-A65E-C2B264857A0E@nostrum.com>
In-Reply-To: <27FD8C7A-7636-4D60-A65E-C2B264857A0E@nostrum.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, The IETF <ietf@ietf.org>, draft-reschke-http-status-308.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, 12 Mar 2012 17:16:36 -0000

On 2012-03-12 17:15, Ben Campbell wrote:
> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
> <  http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>
> Please wait for direction from your document shepherd
> or AD before posting a new version of the draft.
>
> Document: draft-reschke-http-status-308-05
> Reviewer: Ben Campbell	
> Review Date: 2012-03-12
> IETF LC End Date: 2012-03-16
> IESG Telechat date: 2012-03-15
>
> Summary: This draft is basically ready for publication as an experimental RFC. I have a few minor comments that might be worth considering whether they would improve the document prior to publication.
>
> Note: Since this draft is on a Telechat that precedes the end of the IETF Last Call, this review serves as both the LC and Telechat review.

Thanks.

> Major issues:
>
> None:
>
> Minor issues:
>
> -- General: I see some discussion about existing UA behavior, but nothing about what a UA should do with a 308 other than as an implication the fact that this is a "permanent version of 307". It's probably worth describing that explicitly. (Or is that what the "clients with link-editing capabilities" statement is intended to do?If so, does that cover everything?)

The draft uses *exactly* the same words as the base spec (HTTPbis), 
except that it combines aspects of 302 (permanence) with those of 307. I 
thought that's clear enough.

> -- section 1, last paragraph:
>
> The fact that a 308 can't change the method is left as an implication of being based on 307. It would be good to state that explicitly and normatively here.

We don't state it in HTTPbis either. 301, 302, and 303 are exceptions. 
See the new introduction in 
<http://greenbytes.de/tech/webdav/draft-ietf-httpbis-p2-semantics-18.html#rfc.section.7.3>.

> -- section 3, 1st paragraph: "Clients with link-editing capabilities ought to..."
>
> Should that be stated normatively?

No. Again, this is consistent with the text in HTTPbis for status code 302.

> -- section 3, third paragraph: "The new permanent URI SHOULD be given..."
>
> I'm curious why that is not a MUST. Is there a reasonable (i.e. interoperable)  way to send a 308 _without_ a URI in the location field? Is the meta refresh directive something that can be used _instead_ of the Location header field?

Again, consistency with RFC 2616 and HTTPbis.

> -- section 4:
>
> The example uses _both_ the location field and the HTML<meta>  refresh directive. Is this considered a recommended practice to the degree you might normatively recommend it in the text?

No, it's a hack that makes deployment easier until all UAs do the right 
thing; we don't want to make that permanent.

> Nits/editorial comments:
>
> None

Note that I have an updated version waiting to be submitted in two weeks 
(or earlier, if the AD allows me to). It updates references, and adds an 
informative ref to the HTML spec, as suggested during LC. See 
<http://greenbytes.de/tech/webdav/draft-reschke-http-status-308-latest.html>.

Best regards, Julian

From stpeter@stpeter.im  Mon Mar 12 10:48:30 2012
Return-Path: <stpeter@stpeter.im>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1BDAE21F89AD; Mon, 12 Mar 2012 10:48:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.418
X-Spam-Level: 
X-Spam-Status: No, score=-102.418 tagged_above=-999 required=5 tests=[AWL=-0.419, BAYES_00=-2.599, J_CHICKENPOX_22=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7NjfTDQbFlfY; Mon, 12 Mar 2012 10:48:29 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 436C821F89AC; Mon, 12 Mar 2012 10:48:29 -0700 (PDT)
Received: from dhcp-64-101-72-193.cisco.com (unknown [64.101.72.193]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id A3FEE40058; Mon, 12 Mar 2012 12:00:44 -0600 (MDT)
Message-ID: <4F5E36EA.3080309@stpeter.im>
Date: Mon, 12 Mar 2012 11:48:26 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.5; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: Julian Reschke <julian.reschke@gmx.de>
Subject: Re: Gen-ART LC/Telechat review of draft-reschke-http-status-308-05
References: <27FD8C7A-7636-4D60-A65E-C2B264857A0E@nostrum.com> <4F5E2F65.1000706@gmx.de>
In-Reply-To: <4F5E2F65.1000706@gmx.de>
X-Enigmail-Version: 1.3.5
OpenPGP: url=https://stpeter.im/stpeter.asc
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Ben Campbell <ben@nostrum.com>, "gen-art@ietf.org Review Team" <gen-art@ietf.org>, The IETF <ietf@ietf.org>, draft-reschke-http-status-308.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, 12 Mar 2012 17:48:30 -0000

On 3/12/12 11:16 AM, Julian Reschke wrote:
> On 2012-03-12 17:15, Ben Campbell wrote:
>> I am the assigned Gen-ART reviewer for this draft. For background on
>> Gen-ART, please see the FAQ at
>> <  http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>>
>> Please wait for direction from your document shepherd
>> or AD before posting a new version of the draft.
>>
>> Document: draft-reschke-http-status-308-05
>> Reviewer: Ben Campbell   
>> Review Date: 2012-03-12
>> IETF LC End Date: 2012-03-16
>> IESG Telechat date: 2012-03-15
>>
>> Summary: This draft is basically ready for publication as an
>> experimental RFC. I have a few minor comments that might be worth
>> considering whether they would improve the document prior to publication.
>>
>> Note: Since this draft is on a Telechat that precedes the end of the
>> IETF Last Call, this review serves as both the LC and Telechat review.
> 
> Thanks.
> 
>> Major issues:
>>
>> None:
>>
>> Minor issues:
>>
>> -- General: I see some discussion about existing UA behavior, but
>> nothing about what a UA should do with a 308 other than as an
>> implication the fact that this is a "permanent version of 307". It's
>> probably worth describing that explicitly. (Or is that what the
>> "clients with link-editing capabilities" statement is intended to
>> do?If so, does that cover everything?)
> 
> The draft uses *exactly* the same words as the base spec (HTTPbis),
> except that it combines aspects of 302 (permanence) with those of 307. I
> thought that's clear enough.
> 
>> -- section 1, last paragraph:
>>
>> The fact that a 308 can't change the method is left as an implication
>> of being based on 307. It would be good to state that explicitly and
>> normatively here.
> 
> We don't state it in HTTPbis either. 301, 302, and 303 are exceptions.
> See the new introduction in
> <http://greenbytes.de/tech/webdav/draft-ietf-httpbis-p2-semantics-18.html#rfc.section.7.3>.
> 
> 
>> -- section 3, 1st paragraph: "Clients with link-editing capabilities
>> ought to..."
>>
>> Should that be stated normatively?
> 
> No. Again, this is consistent with the text in HTTPbis for status code 302.
> 
>> -- section 3, third paragraph: "The new permanent URI SHOULD be given..."
>>
>> I'm curious why that is not a MUST. Is there a reasonable (i.e.
>> interoperable)  way to send a 308 _without_ a URI in the location
>> field? Is the meta refresh directive something that can be used
>> _instead_ of the Location header field?
> 
> Again, consistency with RFC 2616 and HTTPbis.
> 
>> -- section 4:
>>
>> The example uses _both_ the location field and the HTML<meta>  refresh
>> directive. Is this considered a recommended practice to the degree you
>> might normatively recommend it in the text?
> 
> No, it's a hack that makes deployment easier until all UAs do the right
> thing; we don't want to make that permanent.
> 
>> Nits/editorial comments:
>>
>> None
> 
> Note that I have an updated version waiting to be submitted in two weeks
> (or earlier, if the AD allows me to). It updates references, and adds an
> informative ref to the HTML spec, as suggested during LC. See
> <http://greenbytes.de/tech/webdav/draft-reschke-http-status-308-latest.html>.

<hat type='AD'/>

Julian, I think it would be helpful for you to submit your latest copy
before the deadline today, so that we don't need to wait until March 26.

Peter

-- 
Peter Saint-Andre
https://stpeter.im/



From rpelletier@isoc.org  Mon Mar 12 21:42:55 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 2772E21F88E8 for <ietf@ietfa.amsl.com>; Mon, 12 Mar 2012 21:42:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.131
X-Spam-Level: 
X-Spam-Status: No, score=-103.131 tagged_above=-999 required=5 tests=[AWL=0.134, 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 AMr552t2Jnyh for <ietf@ietfa.amsl.com>; Mon, 12 Mar 2012 21:42:54 -0700 (PDT)
Received: from smtp197.dfw.emailsrvr.com (smtp197.dfw.emailsrvr.com [67.192.241.197]) by ietfa.amsl.com (Postfix) with ESMTP id A59E521F88E2 for <ietf@ietf.org>; Mon, 12 Mar 2012 21:42:53 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp19.relay.dfw1a.emailsrvr.com (SMTP Server) with ESMTP id 38ACF3C84A4; Tue, 13 Mar 2012 00:42:53 -0400 (EDT)
X-Virus-Scanned: OK
Received: by smtp19.relay.dfw1a.emailsrvr.com (Authenticated sender: rpelletier-AT-isoc.org) with ESMTPSA id 665A73C80EB;  Tue, 13 Mar 2012 00:42:52 -0400 (EDT)
From: Ray Pelletier <rpelletier@isoc.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Tue, 13 Mar 2012 00:43:01 -0400
Subject: IETF Mail Archive Tools RFI
To: Discussion IETF <ietf@ietf.org>, IESG The <iesg@ietf.org>, IAOC <iaoc@ietf.org>, Chairs Working Group <wgchairs@ietf.org>, tools-development@ietf.org
Message-Id: <CC6F7CF7-08D0-45A6-B3A0-E9F9B20BBA3F@isoc.org>
Mime-Version: 1.0 (Apple Message framework v1084)
X-Mailer: Apple Mail (2.1084)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Mar 2012 04:42:56 -0000

This is a Request for Information (RFI).  The purpose of this RFI is to =
obtain feedback from the IETF community on the Statement of Work (SOW), =
identify potential suppliers and developers for an IETF IETF Email List =
Archiving, Web-based Browsing and Search Tool, and to seek comments on =
the (SOW) from such suppliers/developers to inform the preparation of a =
possible RFP.=20

We seek information on how to improve the IETF email list archiving and =
searching systems.  The IETF makes heavy use of email lists to conduct =
its work.    Participants frequently need to search the archives of =
these lists, and have asked for improved search capabilities, =
particularly when the search needs to cover a large period of time, or =
cross several lists.  The current tools for performing these searches =
require several manually coordinated steps, which are error prone.  More =
advanced search capabilities have been constructed for a limited subset =
of the available lists and are exposed in the "Email Archives Quick =
Search" section of the main IETF website.  While these tools are of =
great assistance, there is still significant need for   improvement.  =
The current archive mechanism could also be made more efficient. =20

The RFI can be found at: <http://iaoc.ietf.org/rfpsrfis.html>
The Statement of Work can be found at: =
<http://tools.ietf.org/html/draft-sparks-genarea-mailarch-05> =20

Expressions of interest from potential bidders and all SOW comments are =
due by 16 April 2012 and should be submitted to mailarch@ietf-bids.org.  =
See the RFI for more details.

Questions about this RFI can be addressed to mailarch@ietf-bids.org by =
19 March 2012.
All questions and answers will be posted on the website at =
http://iaoc.ietf.org/rfpsrfis.html.
The identity of the question's originator will not be disclosed.

All information submitted in response to this announcement is voluntary =
and may be used in the development of the RFP.

Ray Pelletier
IETF Administrative Director



From daedulus@btconnect.com  Tue Mar 13 03:38:46 2012
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2885E21F86B4 for <ietf@ietfa.amsl.com>; Tue, 13 Mar 2012 03:38:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qf9l5exYjSJD for <ietf@ietfa.amsl.com>; Tue, 13 Mar 2012 03:38:45 -0700 (PDT)
Received: from mail.btconnect.com (c2bthomr13.btconnect.com [213.123.20.131]) by ietfa.amsl.com (Postfix) with ESMTP id 9082521F8669 for <ietf@ietf.org>; Tue, 13 Mar 2012 03:38:40 -0700 (PDT)
Received: from host86-151-41-215.range86-151.btcentralplus.com (HELO pc6) ([86.151.41.215]) by c2bthomr13.btconnect.com with SMTP id GQX84264; Tue, 13 Mar 2012 10:38:39 +0000 (GMT)
Message-ID: <028601cd00fc$f5ba5380$4001a8c0@gateway.2wire.net>
From: "t.petch" <daedulus@btconnect.com>
To: <ietf@ietf.org>
References: <20120301184750.21152.93044.idtracker@ietfa.amsl.com>
Subject: Re: Last Call: <draft-ietf-appsawg-xdash-03.txt> (Deprecating Use of the"X-" Prefix in Application Protocols) to Best Current Practice
Date: Tue, 13 Mar 2012 10:37:43 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Mirapoint-IP-Reputation: reputation=Neutral-1, source=Queried, refid=tid=0001.0A020301.4F5F23AF.0038, actions=tag
X-Junkmail-Premium-Raw: score=9/50, refid=2.7.2:2012.3.13.83315:17:9.975, ip=86.151.41.215, rules=__HAS_MSGID, __OUTLOOK_MSGID_1, __SANE_MSGID, __TO_MALFORMED_2, __TO_NO_NAME, __BOUNCE_CHALLENGE_SUBJ, __BOUNCE_NDR_SUBJ_EXEMPT, __MIME_VERSION, __CT, CT_TP_8859_1, __CT_TEXT_PLAIN, __CTE, __HAS_X_PRIORITY, __HAS_MSMAIL_PRI, __HAS_X_MAILER, USER_AGENT_OE, __OUTLOOK_MUA_1, __USER_AGENT_MS_GENERIC, TO_IN_SUBJECT, __ANY_URI, __FRAUD_CONTACT_NAME, __CP_URI_IN_BODY, BODY_SIZE_3000_3999, __MIME_TEXT_ONLY, RDNS_GENERIC_POOLED, HTML_00_01, HTML_00_10, BODY_SIZE_5000_LESS, RDNS_SUSP_GENERIC, __OUTLOOK_MUA, RDNS_SUSP, BODY_SIZE_7000_LESS
X-Junkmail-Status: score=10/50, host=c2bthomr13.btconnect.com
X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A0B0203.4F5F23AF.01DF,ss=1,re=0.000,fgs=0, ip=0.0.0.0, so=2011-07-25 19:15:43, dmn=2011-05-27 18:58:46, mode=multiengine
X-Junkmail-IWF: false
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Mar 2012 10:38:46 -0000

I am surprised at the lack of comment on this I-D on its use of terminology.  I
have seen and learnt from many discussions on this list that have teased out
what concept it is we are really talking about (e.g. identity v identifier) and
this I-D seems somewhat weak in that regard.

Thus the summary talks of
'parameters by prefixing the latter '
while the  introduction changes that to
'the "X-" convention for named parameters in application protocols '
which is then refined to
'only parameters with textual names, not parameters that are expressed as
numbers'
which seems to me a false dichotomy.

The I-D seems to be conflating the ideas of name and value and a few other
things as well.  I know of very few parameters in IETF protocols that do not
have names and cannot recall one where the name is not textual.  The I-D seems
to be assuming that the parameter name and the parameter value and so on are
synonymous, identical, equivalent and perhaps a few other things as well, and
having assumed that, then it is sufficient to say that one or other of these
concepts are textual and it is to these that this I-D applies.  This seems to me
to be rather too loosely worded to become an RFC.

Tom Petch

----- Original Message -----
From: "The IESG" <iesg-secretary@ietf.org>
To: "IETF-Announce" <ietf-announce@ietf.org>
Cc: <apps-discuss@ietf.org>
Sent: Thursday, March 01, 2012 7:47 PM
Subject: Last Call: <draft-ietf-appsawg-xdash-03.txt> (Deprecating Use of
the"X-" Prefix in Application Protocols) to Best Current Practice


>
> The IESG has received a request from the Applications Area Working Group
> WG (appsawg) to consider the following document:
> - 'Deprecating Use of the "X-" Prefix in Application Protocols'
>   <draft-ietf-appsawg-xdash-03.txt> as a 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-03-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
>
>
>    Historically, designers and implementers of application protocols
>    have often distinguished between "standard" and "non-standard"
>    parameters by prefixing the latter with the string "X-" or similar
>    constructions.  In practice, this convention causes more problems
>    than it solves.  Therefore, this document deprecates the "X-"
>    convention for textual parameters in application protocols.
>
>
>
>
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-appsawg-xdash/
>
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-appsawg-xdash/ballot/
>
>
> No IPR declarations have been submitted directly on this I-D.
>
>
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-announce
>
>


From ron.even.tlv@gmail.com  Tue Mar 13 04:25:54 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 986D621F86D1; Tue, 13 Mar 2012 04:25:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.029
X-Spam-Level: 
X-Spam-Status: No, score=-3.029 tagged_above=-999 required=5 tests=[AWL=0.569,  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 BpiaheKH5KEa; Tue, 13 Mar 2012 04:25:53 -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 3D26321F871A; Tue, 13 Mar 2012 04:25:53 -0700 (PDT)
Received: by werb10 with SMTP id b10so495038wer.31 for <multiple recipients>; Tue, 13 Mar 2012 04:25:52 -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=KdWkY7nbESJyzM/ybxdA6jy9mDM18zn4NQih3RfwOT4=; b=iLpwpFCUKo29/oK5+YANaM0bvdKEWADpqg/+c3JHUg//tqc5l4O4GvUqvvjoLGiuhS 2bOnL97G/Sz+7oVBD5unBELErCoJFgRLx2MLCwJsi1mWBHDxdiJz4SCmfwU7p0m+JdNh 9Xjq8WJLat/26xTsJPZzHWYNcPNvufg0oRZpKJmvJTcFu7GFrHCsNKwpY1QgnblsTkui ZAwD8ZV2CZJPwEBpoBmfHL4cC0vGeEiYQ0mlATf/nN894n4ejc8yYHHwt+yE+ssb/nzV 0x41E3NVSBIIGzTwGJEUuDkWhor05fVgP4WBXRzfZxx+yDyBVKnnwoollFLeJs3zGQWL OKQQ==
Received: by 10.180.19.37 with SMTP id b5mr6556377wie.9.1331637952142; Tue, 13 Mar 2012 04:25:52 -0700 (PDT)
Received: from windows8d787f9 (bzq-79-179-219-130.red.bezeqint.net. [79.179.219.130]) by mx.google.com with ESMTPS id d7sm1053858wiz.6.2012.03.13.04.25.49 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 13 Mar 2012 04:25:50 -0700 (PDT)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: <draft-ietf-behave-nat64-learn-analysis.all@tools.ietf.org>
Subject: GenART last call review of draft-ietf-behave-nat64-learn-analysis-03
Date: Tue, 13 Mar 2012 13:24:59 +0200
Message-ID: <4f5f2ebe.0755b40a.4d27.257b@mx.google.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_00FE_01CD011C.B1F5CB00"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac0BC+yBNfRKKMa5SRGpWscXSW4ZEg==
Content-Language: en-us
Cc: gen-art@ietf.org, 'IETF-Discussion list' <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Mar 2012 11:25:54 -0000

This is a multi-part message in MIME format.

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

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

 

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

 

Document: draft-ietf-behave-nat64-learn-analysis-03

Reviewer: Roni Even

Review Date:2012-3-13

IETF LC End Date: 2012-3-22

IESG Telechat date:

 

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

 

Major issues:

 

Minor issues:

 

Nits/editorial comments:

 

Section 5.1.1 third paragraph change to  "provided by some"

 


------=_NextPart_000_00FE_01CD011C.B1F5CB00
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 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: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;}
@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 =
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-ietf-=
behave-nat64-learn-analysis-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;3&#8211;13<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;3&#8211;22<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=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><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Section =
5.1.1 third paragraph change to&nbsp; &#8220;provided <b><u>by</u></b> =
some&#8221;<o:p></o:p></span></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_00FE_01CD011C.B1F5CB00--


From elevyabe@cisco.com  Tue Mar 13 08:05:40 2012
Return-Path: <elevyabe@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 3BC2C21F886B; Tue, 13 Mar 2012 08:05:40 -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 y8bSj9-M2hvt; Tue, 13 Mar 2012 08:05:39 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by ietfa.amsl.com (Postfix) with ESMTP id 2C25721F886A; Tue, 13 Mar 2012 08:05:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=elevyabe@cisco.com; l=3122; q=dns/txt; s=iport; t=1331651139; x=1332860739; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=CCYv3DmWqCOKt0gkbeSOHJxx0KnWVx9DX9xUA7cyqnc=; b=hQDTDA1W3wG5io2bA6t7+pYZ2EyJfS7t3QQssgTvLX/VJ2vZVJmmGuSM riznQW4aIjDAVk8SWtRLfpeAwwlJzzszw351hjYZZQx5exG1soEc48c7C ZAzWe+IsO0DFOgcVQ6IiQrrZ5EwFT0K17+W+iSufDAn8aCoTk4PdzgN+n 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAMJhX0+Q/khL/2dsb2JhbABDtV+BB4IJAQEBBAEBAQ8BJS8HCgEQCxgJFg8JAwIBAgEVHxETAQUCAQEXB4doC51rAZ8HkGUElVCFaYo6gmaBVRc
X-IronPort-AV: E=Sophos;i="4.73,577,1325462400"; d="scan'208";a="132187796"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by ams-iport-1.cisco.com with ESMTP; 13 Mar 2012 15:05:37 +0000
Received: from xbh-ams-201.cisco.com (xbh-ams-201.cisco.com [144.254.75.7]) by ams-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id q2DF5bY4024863; Tue, 13 Mar 2012 15:05:37 GMT
Received: from xmb-ams-105.cisco.com ([144.254.74.80]) by xbh-ams-201.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 13 Mar 2012 16:05:37 +0100
Received: from [144.254.53.114] ([144.254.53.114]) by xmb-ams-105.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 13 Mar 2012 16:05:37 +0100
Message-ID: <4F5F623F.3030907@cisco.com>
Date: Tue, 13 Mar 2012 16:05:35 +0100
From: eric levy-abegnoli <elevyabe@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.27) Gecko/20120216 Thunderbird/3.1.19
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: [savi] Last Call: <draft-ietf-savi-dhcp-12.txt> (SAVI Solution for	DHCP) to	Proposed Standard
References: <20120306150141.8315.38572.idtracker@ietfa.amsl.com>
In-Reply-To: <20120306150141.8315.38572.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 13 Mar 2012 15:05:37.0071 (UTC) FILETIME=[BF248BF0:01CD012A]
X-Mailman-Approved-At: Tue, 13 Mar 2012 08:09:47 -0700
Cc: savi@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Mar 2012 15:05:40 -0000

Hi,
here are my substantive comments
Look for  [eric].
Eric

7.3.1. Timer Expiration Event

    EVE_ENTRY_EXPIRE: The lifetime of an entry expires

[eric] 2 minutes sounds very long. DHCP client timeout is 1 sec for the 
first
message. Then multiplied by 2, etc. What is the rational behind this 
value, which increase the window for DoS attacks?

8. Supplemental Binding Process
[eric] This section is very unclear. The conditional SHOULD
    based on  "vendor ability" sounds like a "MAY" to me, which is not
    what I remember of the WG consensus. In addition, hosts are not
    required to (DHCP) re-configure upon link flapping, even when they
    are directly attached.  The text seems to indicate otherwise.
    In practice, in the absence of such mechanism, traffic will be blocked.

   8.1. Binding Recovery Process
[eric] It is unclear what the address is bound to. In the normal case,
      the entry is created upon receiving a message (i.e. REQUEST) from
      the client, and the anchor is stored by that time. You should
      specified where the anchor comes from in this scenario, and where
      was it stored (given that the section specifies the binding entry 
creattion on LQ Reply)

10. State Restoration
[eric] Requiring non-volatile memory sounds wrong. Other techniques
exists such as redundant boxes (switches) synchronizing states. I
don't recall that non-volatile memory was discussed at length in the
WG, especially given that it carries its own challenges: frequency
for saving states, load incurred, etc)
The one technique that was discussed in the WG was Binding Recovery
process.  One solution should be enough.

Eric

On 06/03/12 16:01, The IESG wrote:
> The IESG has received a request from the Source Address Validation
> Improvements WG (savi) to consider the following document:
> - 'SAVI Solution for DHCP'
>    <draft-ietf-savi-dhcp-12.txt>  as a 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-03-20. 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 specifies the procedure for creating bindings between a
>     DHCPv4 [RFC2131]/DHCPv6 [RFC3315] assigned source IP address and a
>     binding anchor [I-D.ietf-savi-framework] on SAVI (Source Address
>     Validation Improvements) device. The bindings can be used to filter
>     packets generated on the local link with forged source IP address.
>
>
>
>
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-savi-dhcp/
>
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-savi-dhcp/ballot/
>
>
> No IPR declarations have been submitted directly on this I-D.
>
>
> _______________________________________________
> savi mailing list
> savi@ietf.org
> https://www.ietf.org/mailman/listinfo/savi
>


From julian.reschke@greenbytes.de  Mon Mar 12 11:38:20 2012
Return-Path: <julian.reschke@greenbytes.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 9143021F8983; Mon, 12 Mar 2012 11:38:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level: 
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i+4GEVCPAbmF; Mon, 12 Mar 2012 11:38:20 -0700 (PDT)
Received: from donbot.greenbytes.de (mail.greenbytes.de [217.91.35.233]) by ietfa.amsl.com (Postfix) with ESMTP id DD19821F8982; Mon, 12 Mar 2012 11:38:19 -0700 (PDT)
Received: from [192.168.2.100] (unknown [82.113.106.99]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by donbot.greenbytes.de (Postfix) with ESMTPSA id 8C1EAC4C0E7; Mon, 12 Mar 2012 19:38:11 +0100 (CET)
Message-ID: <4F5E428F.3080302@greenbytes.de>
Date: Mon, 12 Mar 2012 19:38:07 +0100
From: Julian Reschke <julian.reschke@greenbytes.de>
Organization: greenbytes GmbH
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: Peter Saint-Andre <stpeter@stpeter.im>
Subject: Re: Gen-ART LC/Telechat review of draft-reschke-http-status-308-05
References: <27FD8C7A-7636-4D60-A65E-C2B264857A0E@nostrum.com> <4F5E2F65.1000706@gmx.de> <4F5E36EA.3080309@stpeter.im>
In-Reply-To: <4F5E36EA.3080309@stpeter.im>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Mailman-Approved-At: Tue, 13 Mar 2012 08:10:02 -0700
Cc: Julian Reschke <julian.reschke@gmx.de>, Ben Campbell <ben@nostrum.com>, "gen-art@ietf.org Review Team" <gen-art@ietf.org>, The IETF <ietf@ietf.org>, draft-reschke-http-status-308.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, 12 Mar 2012 18:38:20 -0000

On 2012-03-12 18:48, Peter Saint-Andre wrote:
> ...
> <hat type='AD'/>
>
> Julian, I think it would be helpful for you to submit your latest copy
> before the deadline today, so that we don't need to wait until March 26.

Done; I usually avoid changing drafts during LC; but I think it makes 
sense in this case.

Best regards, Julian

-- 
<green/>bytes GmbH, Hafenweg 16, D-48155 Münster, Germany
Amtsgericht Münster: HRB5782


From gregory.mirsky@ericsson.com  Mon Mar 12 12:36:23 2012
Return-Path: <gregory.mirsky@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 7A55F21E8096; Mon, 12 Mar 2012 12:36:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.531
X-Spam-Level: 
X-Spam-Status: No, score=-6.531 tagged_above=-999 required=5 tests=[AWL=0.067,  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 z07A3Ang1Ebh; Mon, 12 Mar 2012 12:36:22 -0700 (PDT)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.9]) by ietfa.amsl.com (Postfix) with ESMTP id C0B7A21E8095; Mon, 12 Mar 2012 12:36:22 -0700 (PDT)
Received: from eusaamw0712.eamcs.ericsson.se ([147.117.20.181]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id q2CJaLoA022754; Mon, 12 Mar 2012 14:36:22 -0500
Received: from EUSAACMS0715.eamcs.ericsson.se ([169.254.2.76]) by eusaamw0712.eamcs.ericsson.se ([147.117.20.181]) with mapi; Mon, 12 Mar 2012 15:36:15 -0400
From: Gregory Mirsky <gregory.mirsky@ericsson.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Date: Mon, 12 Mar 2012 15:36:14 -0400
Subject: RE: Last Call: <draft-ietf-bmwg-protection-meth-09.txt> (Methodology for benchmarking MPLS protection mechanisms) to Informational RFC
Thread-Topic: RE: Last Call: <draft-ietf-bmwg-protection-meth-09.txt> (Methodology for benchmarking MPLS protection mechanisms) to Informational RFC
Thread-Index: Ac0Ah2L2izJRLkfhR1Wobgx1tFN2lQ==
Message-ID: <FE60A4E52763E84B935532D7D9294FF135501CCB6C@EUSAACMS0715.eamcs.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_FE60A4E52763E84B935532D7D9294FF135501CCB6CEUSAACMS0715e_"
MIME-Version: 1.0
X-Mailman-Approved-At: Tue, 13 Mar 2012 08:10:02 -0700
Cc: "mpls@ietf.org" <mpls@ietf.org>, "bmwg@ietf.org" <bmwg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Mar 2012 19:36:23 -0000

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

Dear All,
Please consider my comments for the LC:
*       I'm concerned with the very title of the document, Methodology for =
benchmarking MPLS protection mechanisms, even though only MPLS-TE FRR being=
 considered while LSP end-to-end and segment protection implicitly being ke=
pt out of the scope.
*       I've found several textual inaccuracies related to both MPLS and BF=
D to make me wonder if the document was liasioned to MPLS WG.
*       List of acronyms is missing - PLR, OIR, LOS, AIS, etc.
*       Introduction. I think that for "planned link or node failure" MBB i=
s more efficient and useful than FRR. But MBB is not being mentioned in the=
 document.
*       Introduction. "A correlated failure is the simultaneous occurrence =
of two or more failures." Personally, as correlated events I consider event=
s with cause-effect relationship.
*       Introduction. Path restoration after FRR discussion does not appear=
 logical, in the scope of benchmarking document.
*       Document Scope. "Protection from Bi-directional Forwarding Detectio=
n (BFD) is outside the scope of this document." I frankly couldn't decode t=
his sentense.
*        Document Scope. Several references to Path Restoration as Re-optim=
ization - doubt that it belongs in the document at all.
*        Sections 6.1.1 through 6.2.4 - what is relevance of listing number=
s of labels in the stack?
*       Peerformance of control plane should be outside of the scope of ben=
chmarking as it is end-to-end metrics, not explicitly of DUT.


Regards,
        Greg


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

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Exchange Server">
<!-- converted from rtf -->
<style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left:=
 #800000 2px solid; } --></style>
</head>
<body>
<font face=3D"Arial, sans-serif" size=3D"2">
<div>Dear All,</div>
<div>Please consider my comments for the LC:</div>
<ul style=3D"margin-top: 0pt; margin-bottom: 0pt; margin-left: 19pt; ">
<li>I'm concerned with the very title of the document, Methodology for benc=
hmarking MPLS protection mechanisms, even though only MPLS-TE FRR being con=
sidered while LSP end-to-end and segment protection implicitly being kept o=
ut of the scope.</li><li>I've found several textual inaccuracies related to=
 both MPLS and BFD to make me wonder if the document was liasioned to MPLS =
WG.</li></ul>
<ul style=3D"margin-top: 0pt; margin-bottom: 0pt; margin-left: 38pt; ">
<li>List of acronyms is missing - PLR, OIR, LOS, AIS, etc.</li><li>Introduc=
tion. I think that for &quot;planned link or node failure&quot; MBB is more=
 efficient and useful than FRR. But MBB is not being mentioned in the docum=
ent.</li><li>Introduction. &quot;A correlated failure is the simultaneous o=
ccurrence of two or more failures.&quot; Personally, as correlated events I=
 consider events with cause-effect relationship.</li><li>Introduction. Path=
 restoration after FRR discussion does not appear logical, in the scope of =
benchmarking document.</li><li>Document Scope. &quot;Protection from Bi-dir=
ectional Forwarding Detection (BFD) is outside the scope of this document.&=
quot; I frankly couldn't decode this sentense.</li><li> Document Scope. Sev=
eral references to Path Restoration as Re-optimization - doubt that it belo=
ngs in the document at all.</li><li> Sections 6.1.1 through 6.2.4 - what is=
 relevance of listing numbers of labels in the stack?</li><li>Peerformance =
of control plane should be outside of the scope of benchmarking as it is en=
d-to-end metrics, not explicitly of DUT.</li></ul>
<div>&nbsp;</div>
<div>&nbsp;</div>
<div>Regards,</div>
<div>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Greg</div>
<div>&nbsp;</div>
</font>
</body>
</html>

--_000_FE60A4E52763E84B935532D7D9294FF135501CCB6CEUSAACMS0715e_--

From rcallon@juniper.net  Tue Mar 13 11:27:24 2012
Return-Path: <rcallon@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 4B97B21E804E for <ietf@ietfa.amsl.com>; Tue, 13 Mar 2012 11:27:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.581
X-Spam-Level: 
X-Spam-Status: No, score=-106.581 tagged_above=-999 required=5 tests=[AWL=0.018, 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 DXiUzsk0WbNy for <ietf@ietfa.amsl.com>; Tue, 13 Mar 2012 11:27:23 -0700 (PDT)
Received: from exprod7og118.obsmtp.com (exprod7og118.obsmtp.com [64.18.2.8]) by ietfa.amsl.com (Postfix) with ESMTP id 3F61721E8017 for <ietf@ietf.org>; Tue, 13 Mar 2012 11:27:20 -0700 (PDT)
Received: from P-EMHUB02-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob118.postini.com ([64.18.6.12]) with SMTP ID DSNKT1+Rh5IYcT9FT7S8LXSLOlrHAV+cRZFw@postini.com; Tue, 13 Mar 2012 11:27:22 PDT
Received: from p-emfe01-wf.jnpr.net (172.28.145.24) by P-EMHUB02-HQ.jnpr.net (172.24.192.36) with Microsoft SMTP Server (TLS) id 8.3.213.0; Tue, 13 Mar 2012 11:26:43 -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; Tue, 13 Mar 2012 14:26:43 -0400
From: Ross Callon <rcallon@juniper.net>
To: "Andrew G. Malis" <agmalis@gmail.com>, "Sprecher, Nurit (NSN - IL/Hod HaSharon)" <nurit.sprecher@nsn.com>
Date: Tue, 13 Mar 2012 14:26:41 -0400
Subject: RE: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt>(Allocationof	an Associated Channel Code Point for Use byITU-T Ethernetbased OAM) to	Informational RFC
Thread-Topic: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt>(Allocationof	an Associated Channel Code Point for Use byITU-T Ethernetbased OAM) to	Informational RFC
Thread-Index: Acz7K1zGcZQazOWqRhqgfGIuwk8+cwGGgb0g
Message-ID: <DF7F294AF4153D498141CBEFADB17704C70C831867@EMBX01-WF.jnpr.net>
References: <20120222151252.32262.82157.idtracker@ietfa.amsl.com> <03a301ccf174$ff953290$febf97b0$@olddog.co.uk> <515703B08A3A064C9CC8C09ACCC710DC0631679E@XMB-RCD-103.cisco.com> <E4873516F3FC7547BCFE792C7D94039C015D117D@DEMUEXC013.nsn-intra.net> <E4873516F3FC7547BCFE792C7D94039C015D118B@DEMUEXC013.nsn-intra.net> <CAA=duU21qzU3s4xPhPH-0_V7buteVXPo5Kx5m2iu5+7F8qu28A@mail.gmail.com>
In-Reply-To: <CAA=duU21qzU3s4xPhPH-0_V7buteVXPo5Kx5m2iu5+7F8qu28A@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EXCLAIMER-MD-CONFIG: e4081efb-6d29-443c-8708-750833aec629
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, 13 Mar 2012 18:27:24 -0000

I agree that the allocation of a code point should be to a specific version=
 of 8113.1, and specifically should be to the final version that is approve=
d by the ITU-T (assuming that a final version of 8113.1 will be approved by=
 the ITU-T). This would imply that draft-betts-itu-oam-ach-code-point shoul=
d contain a normative reference to the final approved version of 8113.1.=20

Given normal IETF processes, this implies that the final RFC resulting from=
 draft-betts-itu-oam-ach-code-point could be published as soon as the final=
 version of 8113.1 is approved (with the understanding that there will be a=
 small normal delay between "approved" and "published" which gives time for=
 coordination). Given that the final version of 8113.1 might need to refere=
nce the RFC resulting from draft-betts-itu-oam-ach-code-point, a bit of coo=
peration might be needed between editorial staff at the ITU and RFC editori=
al staff, but I don't see why this should be a problem (I am sure that they=
 all have access to email).=20

Ross

-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of And=
rew G. Malis
Sent: Monday, March 05, 2012 6:54 PM
To: Sprecher, Nurit (NSN - IL/Hod HaSharon)
Cc: ietf@ietf.org
Subject: Re: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt>(Allocat=
ionof an Associated Channel Code Point for Use byITU-T Ethernetbased OAM) t=
o Informational RFC

I would like to support Nurit's comments below. In particular, in the
past the ITU-T has expanded upon or changed the usage of IETF
codepoint allocations, in some cases incompatibly with its original
usage or definition. In the future, all codepoint allocations to the
ITU-T should be tied to one specific, dated revision of their
specification only. This is similar to the ITU-T's own processes, such
as section 2.2.1 of Rec. A.5, which requires a version number and/or
date for referenced outside documents in ITU-T recommendations.

Cheers,
Andy

On Thu, Mar 1, 2012 at 7:20 AM, Sprecher, Nurit (NSN - IL/Hod
HaSharon) <nurit.sprecher@nsn.com> wrote:
> Hi,
>
>
>
> I cannot support the publication of the document in its current version.
>
>
>
> I have the following concerns:
>
>
>
> .=A0=A0=A0=A0=A0=A0=A0 It is indicated that the channel is intended to be=
 used to carry
> Ethernet based OAM messages. It is not clear why there is a need for ACH.
> PWs can be used to transmit Ethernet OAM.
>
> If the intention is to use the channel for OAM messages for operating
> MPLS-TP based networks, the IETF *already* defined a solution for MPLS-TP
> OAM and I expect to see first a technical *justification* why a second
> solution is needed. In addition, I would expect to see *references to the
> arguments* raised in draft-sprecher-mpls-tp-oam-considerations.
>
>
>
> .=A0=A0=A0=A0=A0=A0=A0 It is not clear what the maturity status of G.8113=
.1 is. It seems
> that the document was not approved by SG15 and the discussion was deferre=
d
> to WTSA. This indicates that there is *no consensus* for the approval of
> G.8113.1. A code point should not be allocated before a consensus/decisio=
n
> is reached in the ITU-T and before the document is mature and approved. I=
 do
> not think it is appropriate to allocate a code point and try to force a
> resolution in the ITU-T.
>
>
>
> .=A0=A0=A0=A0=A0=A0=A0 I find a contradiction in the draft. In one place =
it is mentioned:
> "These Ethernet based OAM messages and procedures, address the OAM
> functional requirements defined in [RFC5860]. Other message types should =
not
> be carried behind this code point." In another place it is mentioned: "al=
l
> ITU-T Recommendations are subject to revision. Therefore, the code point
> allocated by this document may be used for future versions of [G.8113.1].=
".
> The last statement opens the door for the definition of additional messag=
es
> in G.8113.1 in the following versions, for example, for APS (supporting
> linear or ring protection mechanisms) and by this creates two solutions f=
or
> other mechanisms as well.
>
>
>
> The use of the code point can go much beyond its original purpose and it
> will hide other messages....a code point should not be allocated at this
> point at all, but specifically not for unknown usage that may be defined =
in
> future versions of G.8113.1.
>
>
>
> Best regards,
>
> Nurit
>
>
>
>
>
>
>
>> -----Original Message-----
>
>> From: ietf-announce-bounces@ietf.org [mailto:ietf-announce-
>
>> bounces@ietf.org] On Behalf Of The IESG
>
>> Sent: 22 February 2012 15:13
>
>> To: IETF-Announce
>
>> Subject: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt>
>
> (Allocation of
>
> an
>
>> Associated Channel Code Point for Use by ITU-T Ethernet based OAM) to
>
>> Informational RFC
>
>>
>
>>
>
>> The IESG has received a request from an individual submitter to
>
> consider
>
>> the following document:
>
>> - 'Allocation of an Associated Channel Code Point for Use by ITU-T
>
>>=A0=A0=A0 Ethernet based OAM'
>
>>=A0=A0 <draft-betts-itu-oam-ach-code-point-03.txt> as an Informational RF=
C
>
>>
>
>> 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-03-21. 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
>
>>
>
>>=A0=A0=A0 This document assigns an Associated Channel Type code point for
>
>>=A0=A0=A0 carrying Ethernet based Operations, Administration, and Managem=
ent
>
>>=A0=A0=A0 messages in the MPLS Generic Associated Channel (G-ACh).
>
>>
>
>> The file can be obtained via
>
>> http://datatracker.ietf.org/doc/draft-betts-itu-oam-ach-code-point/
>
>>
>
>> IESG discussion can be tracked via
>
>> http://datatracker.ietf.org/doc/draft-betts-itu-oam-ach-code-point/
>
>>
>
>>
>
>> No IPR declarations have been submitted directly on this I-D.
>
>> _______________________________________________
>
>> IETF-Announce mailing list
>
>> IETF-Announce@ietf.org
>
>> https://www.ietf.org/mailman/listinfo/ietf-announce
>
>
>
> _______________________________________________
>
> mpls mailing list
>
> mpls@ietf.org
>
> https://www.ietf.org/mailman/listinfo/mpls
>
> _______________________________________________
>
> Ietf mailing list
>
> Ietf@ietf.org
>
> https://www.ietf.org/mailman/listinfo/ietf
>
> _______________________________________________
>
> Ietf mailing list
>
> Ietf@ietf.org
>
> https://www.ietf.org/mailman/listinfo/ietf
>
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>
_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf

From jmh@joelhalpern.com  Tue Mar 13 12:04:44 2012
Return-Path: <jmh@joelhalpern.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 19A6321E8060; Tue, 13 Mar 2012 12:04:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.114
X-Spam-Level: 
X-Spam-Status: No, score=-102.114 tagged_above=-999 required=5 tests=[AWL=0.151, 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 Z8twS8KkXQDU; Tue, 13 Mar 2012 12:04:43 -0700 (PDT)
Received: from morbo.mail.tigertech.net (morbo.mail.tigertech.net [67.131.251.54]) by ietfa.amsl.com (Postfix) with ESMTP id 5495721E8057; Tue, 13 Mar 2012 12:04:43 -0700 (PDT)
Received: from mailc2.tigertech.net (mailc2.tigertech.net [208.80.4.156]) by morbo.tigertech.net (Postfix) with ESMTP id E413FCCFC8; Tue, 13 Mar 2012 12:04:42 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailc2.tigertech.net (Postfix) with ESMTP id 6291926152B; Tue, 13 Mar 2012 12:04:41 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at c2.tigertech.net
Received: from [10.10.10.100] (pool-71-161-51-182.clppva.btas.verizon.net [71.161.51.182]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailc2.tigertech.net (Postfix) with ESMTPSA id 423EB2613AC; Tue, 13 Mar 2012 12:04:40 -0700 (PDT)
Message-ID: <4F5F9A44.4020600@joelhalpern.com>
Date: Tue, 13 Mar 2012 15:04:36 -0400
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: John Scudder <jgs@juniper.net>
Subject: Re: [lisp] WG Review: Recharter of Locator/ID Separation Protocol (lisp)
References: <20120214222316.CF29521E800E@ietfa.amsl.com> <201202152131.q1FLVB9E028114@cichlid.raleigh.ibm.com> <EF3C34EB-C0AA-45F2-ADE0-407CEF5172DD@juniper.net> <4F3E4EDB.7070509@piuha.net> <0E0C6A25-FBA6-4E11-9E89-DEBFFCF41108@juniper.net> <4F58EB8C.1000700@piuha.net> <70EB276F-D77E-45AE-851C-AB08A8D56D0A@juniper.net> <4F5920FF.6070502@piuha.net> <CALaySJKvS5QbtXuMx7TwFiL4hdgi1cT0sYu8EJtYLD6T2yOzKQ@mail.gmail.com> <1D2FF8E9-8E60-4126-AC30-12DFDC854BC6@juniper.net>
In-Reply-To: <1D2FF8E9-8E60-4126-AC30-12DFDC854BC6@juniper.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Barry Leiba <barryleiba@computer.org>, "ietf@ietf.org list" <ietf@ietf.org>, "lisp@ietf.org" <lisp@ietf.org>, "iesg@ietf.org IESG" <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Mar 2012 19:04:44 -0000

Actually John, I would have to disagree with your assertion about what 
it takes to describe the archtiecture.
It may take engineering and evaluating some cache management schemes 
before one can decide whether the archtiecture is a good one.  But that 
is very different from being able to describe the archteicture so that 
one can understand the system level behavior.

Yours,
Joel

On 3/13/2012 2:37 PM, John Scudder wrote:
> Barry and all,
>
> On Mar 8, 2012, at 4:34 PM, Barry Leiba wrote:
> ...
>>>> But it's not clear to me that these (especially architecture and impacts) can
>>>> be said to have been properly analyzed until some of the lower-priority items
>>>> (I'm thinking of threats, cache, ETR sync) have been fleshed out.
>>>
>>> I hear what you are saying. But I think the opinion in the IESG at least
>>> was, however, that those three really are high priority, and that other
>>> documents before them are not so useful before they are completed. I guess
>>> it is a different perspective, whether you do things top-down or bottom-up.
>>> I do agree with both points of view, actually.
>>
>> The dependencies (threats, cache, ETR sync, and whatever else) can
>> certainly be discussed to the extent needed to lay out the
>> architecture and other priority documents, with notes taken and saved
>> for when other documents need to be produced.  That still says that
>> the working group needs to focus on discussion that leads to the
>> completion of the three priority documents first, before tackling the
>> others.  Everyone understands that these priority items can't be
>> developed in a vacuum; we just don't want things to wander off into
>> lower-level details such as protocol elements and text that can wait
>> for the next phase.
>
> You don't want to boil the ocean; that's fine. My point is that without covering (at least) cache management and ETR synchronization, the architecture will not be done. Think about the old joke about the mathematical proof that includes "... then a miracle occurs" as one of its steps (http://star.psy.ohio-state.edu/coglab/Miracle.html). Similarly, threats and the impacts document.
>
> One way to handle this (other than what I've already suggested) might be to explicitly note that the respective documents should cover these topics. For example (edits set off by [[ ]]):
>
> - Architecture description: This document will describe the
>    architecture of the entire LISP system, making it easier to read the
>    rest of the LISP specifications and providing a basis for discussion
>    about the details of the LISP protocols. [[The document will
>    cover relevant issues including though not limited to cache
>    management and ETR synchronization.]]
>
> and
>
> - A description of the impacts of LISP: This document will describe
>    the problems that LISP is intended to address and the impacts that
>    employing LISP has. While the work on LISP was initiated by Internet
>    routing scaling concerns, there has also been an interest on
>    improved solutions to a number of different problems, such as
>    traffic engineering. This document should describe problem areas
>    (such as scaling or traffic engineer) where LISP is expected to have
>    a positive effect, as well as any tradeoffs that are caused by
>    LISP's design. [[The document will discuss potential security-
>    related impacts, whether positive or negative.]]
>
> Regards,
>
> --John
> _______________________________________________
> lisp mailing list
> lisp@ietf.org
> https://www.ietf.org/mailman/listinfo/lisp
>

From nurit.sprecher@nsn.com  Tue Mar 13 12:09:56 2012
Return-Path: <nurit.sprecher@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 6E7C821E8069 for <ietf@ietfa.amsl.com>; Tue, 13 Mar 2012 12:09:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.321
X-Spam-Level: 
X-Spam-Status: No, score=-6.321 tagged_above=-999 required=5 tests=[AWL=-0.174, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4, SARE_SUB_ENC_UTF8=0.152]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UjPlV7EgDT+d for <ietf@ietfa.amsl.com>; Tue, 13 Mar 2012 12:09:55 -0700 (PDT)
Received: from demumfd001.nsn-inter.net (demumfd001.nsn-inter.net [93.183.12.32]) by ietfa.amsl.com (Postfix) with ESMTP id D81BB21E8050 for <ietf@ietf.org>; Tue, 13 Mar 2012 12:09:54 -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 q2DJ9qTd021447 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 13 Mar 2012 20:09:53 +0100
Received: from DEMUEXC048.nsn-intra.net ([10.159.32.94]) by demuprx017.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id q2DJ9qSU003545; Tue, 13 Mar 2012 20:09:52 +0100
Received: from DEMUEXC013.nsn-intra.net ([10.150.128.24]) by DEMUEXC048.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 13 Mar 2012 20:09:53 +0100
Received: from 10.159.32.94 ([10.159.32.94]) by DEMUEXC013.nsn-intra.net ([10.150.128.29]) with Microsoft Exchange Server HTTP-DAV ;  Tue, 13 Mar 2012 19:09:52 +0000
From: "Sprecher, Nurit (NSN - IL/Hod HaSharon)" <nurit.sprecher@nsn.com>
To: "Andrew G. Malis" <agmalis@gmail.com>, "ext Ross Callon" <rcallon@juniper.net>
X-MimeOLE: Produced By Microsoft Exchange V6.5
Thread-Topic: ?????: RE: Last Call:<draft-betts-itu-oam-ach-code-point-03.txt>(Allocationof	an Associated Channel Code Point for Use byITU-T Ethernetbased OAM) to	Informational RFC
Thread-Index: Acz7K1zGcZQazOWqRhqgfGIuwk8+cwGGgb0gAAHeu6s=
Subject: =?UTF-8?B?15TXoNeT15XXnzogUkU6IExhc3QgQ2FsbDo8ZHJhZnQtYmV0dA==?= =?UTF-8?B?cy1pdHUtb2FtLWFjaC1jb2RlLXBvaW50LTAzLnR4dD4=?= =?UTF-8?B?KEFsbG9jYXRpb25vZglhbiBBc3NvY2lhdGVkIENoYW4=?= =?UTF-8?B?bmVsIENvZGUgUG9pbnQgZm9yIFVzZSBieUlUVS1UIEU=?= =?UTF-8?B?dGhlcm5ldGJhc2VkIE9BTSkgdG8JSW5mb3JtYXRpb24=?= =?UTF-8?B?YWwgUkZD?=
Date: Tue, 13 Mar 2012 20:09:47 +0100
Message-ID: <8fab01cd014c$dea8f551$5e209f0a@nsnintra.net>
X-Mailer: EAS Version 1.00
MIME-Version: 1.0
Content-Language: i-default
Content-Type: multipart/mixed; boundary="EPOC32-lxFY_kRZZ-69LvD5+1f9FQDbsyxw,hpmf,CK06ll+0qRM1Yq"
X-OriginalArrivalTime: 13 Mar 2012 19:09:53.0368 (UTC) FILETIME=[DEF9FD80:01CD014C]
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: 8259
X-purgate-ID: 151667::1331665793-000044A2-48E77EEB/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: Tue, 13 Mar 2012 19:09:56 -0000

This is a multi-part message in MIME format.

--EPOC32-lxFY_kRZZ-69LvD5+1f9FQDbsyxw,hpmf,CK06ll+0qRM1Yq
Content-Type: text/plain;
	charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Ross,
i am afraid that you missed the point. There will not be a final version =
since as written in draft-betts, all  ITU recommendations are subject to =
revisions, and the code point will also be used for future revisions of =
the document. New messages/protocols can be defined in future revisions =
of the recommendation and they will use the same code point that is =
allocated for the first version.
This is a real issue.
Regards,
Nurit=20
-----=D7=94=D7=95=D7=93=D7=A2=D7=94 =
=D7=9E=D7=A7=D7=95=D7=A8=D7=99=D7=AA-----
=D7=9E=D7=90=D7=AA: ext Ross Callon
=D7=A0=D7=A9=D7=9C=D7=97:  13/03/2012, 19:27=20
=D7=90=D7=9C: Andrew G. Malis; Sprecher, Nurit (NSN - IL/Hod HaSharon)
=D7=A2=D7=95=D7=AA=D7=A7: ietf@ietf.org
=D7=A0=D7=95=D7=A9=D7=90: RE: Last =
Call:<draft-betts-itu-oam-ach-code-point-03.txt>(Allocationof	an =
Associated Channel Code Point for Use byITU-T Ethernetbased OAM) to	=
Informational RFC
I agree that the allocation of a code point should be to a specific =
version of 8113.1, and specifically should be to the final version that =
is approved by the ITU-T (assuming that a final version of 8113.1 will =
be approved by the ITU-T). This would imply that =
draft-betts-itu-oam-ach-code-point should contain a normative reference =
to the final approved version of 8113.1.=20

Given normal IETF processes, this implies that the final RFC resulting =
from draft-betts-itu-oam-ach-code-point could be published as soon as =
the final version of 8113.1 is approved (with the understanding that =
there will be a small normal delay between "approved" and "published" =
which gives time for coordination). Given that the final version of =
8113.1 might need to reference the RFC resulting from =
draft-betts-itu-oam-ach-code-point, a bit of cooperation might be needed =
between editorial staff at the ITU and RFC editorial staff, but I don't =
see why this should be a problem (I am sure that they all have access to =
email).=20

Ross

-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of =
Andrew G. Malis
Sent: Monday, March 05, 2012 6:54 PM
To: Sprecher, Nurit (NSN - IL/Hod HaSharon)
Cc: ietf@ietf.org
Subject: Re: Last Call: =
<draft-betts-itu-oam-ach-code-point-03.txt>(Allocationof an Associated =
Channel Code Point for Use byITU-T Ethernetbased OAM) to Informational =
RFC

I would like to support Nurit's comments below. In particular, in the
past the ITU-T has expanded upon or changed the usage of IETF
codepoint allocations, in some cases incompatibly with its original
usage or definition. In the future, all codepoint allocations to the
ITU-T should be tied to one specific, dated revision of their
specification only. This is similar to the ITU-T's own processes, such
as section 2.2.1 of Rec. A.5, which requires a version number and/or
date for referenced outside documents in ITU-T recommendations.

Cheers,
Andy

On Thu, Mar 1, 2012 at 7:20 AM, Sprecher, Nurit (NSN - IL/Hod
HaSharon) <nurit.sprecher@nsn.com> wrote:
> Hi,
>
>
>
> I cannot support the publication of the document in its current =
version.
>
>
>
> I have the following concerns:
>
>
>
> .        It is indicated that the channel is intended to be used to =
carry
> Ethernet based OAM messages. It is not clear why there is a need for =
ACH.
> PWs can be used to transmit Ethernet OAM.
>
> If the intention is to use the channel for OAM messages for operating
> MPLS-TP based networks, the IETF *already* defined a solution for =
MPLS-TP
> OAM and I expect to see first a technical *justification* why a second
> solution is needed. In addition, I would expect to see *references to =
the
> arguments* raised in draft-sprecher-mpls-tp-oam-considerations.
>
>
>
> .        It is not clear what the maturity status of G.8113.1 is. It =
seems
> that the document was not approved by SG15 and the discussion was =
deferred
> to WTSA. This indicates that there is *no consensus* for the approval =
of
> G.8113.1. A code point should not be allocated before a =
consensus/decision
> is reached in the ITU-T and before the document is mature and =
approved. I do
> not think it is appropriate to allocate a code point and try to force =
a
> resolution in the ITU-T.
>
>
>
> .        I find a contradiction in the draft. In one place it is =
mentioned:
> "These Ethernet based OAM messages and procedures, address the OAM
> functional requirements defined in [RFC5860]. Other message types =
should not
> be carried behind this code point." In another place it is mentioned: =
"all
> ITU-T Recommendations are subject to revision. Therefore, the code =
point
> allocated by this document may be used for future versions of =
[G.8113.1].".
> The last statement opens the door for the definition of additional =
messages
> in G.8113.1 in the following versions, for example, for APS =
(supporting
> linear or ring protection mechanisms) and by this creates two =
solutions for
> other mechanisms as well.
>
>
>
> The use of the code point can go much beyond its original purpose and =
it
> will hide other messages....a code point should not be allocated at =
this
> point at all, but specifically not for unknown usage that may be =
defined in
> future versions of G.8113.1.
>
>
>
> Best regards,
>
> Nurit
>
>
>
>
>
>
>
>> -----Original Message-----
>
>> From: ietf-announce-bounces@ietf.org [mailto:ietf-announce-
>
>> bounces@ietf.org] On Behalf Of The IESG
>
>> Sent: 22 February 2012 15:13
>
>> To: IETF-Announce
>
>> Subject: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt>
>
> (Allocation of
>
> an
>
>> Associated Channel Code Point for Use by ITU-T Ethernet based OAM) to
>
>> Informational RFC
>
>>
>
>>
>
>> The IESG has received a request from an individual submitter to
>
> consider
>
>> the following document:
>
>> - 'Allocation of an Associated Channel Code Point for Use by ITU-T
>
>>    Ethernet based OAM'
>
>>   <draft-betts-itu-oam-ach-code-point-03.txt> as an 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-03-21. 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 assigns an Associated Channel Type code point for
>
>>    carrying Ethernet based Operations, Administration, and Management
>
>>    messages in the MPLS Generic Associated Channel (G-ACh).
>
>>
>
>> The file can be obtained via
>
>> http://datatracker.ietf.org/doc/draft-betts-itu-oam-ach-code-point/
>
>>
>
>> IESG discussion can be tracked via
>
>> http://datatracker.ietf.org/doc/draft-betts-itu-oam-ach-code-point/
>
>>
>
>>
>
>> No IPR declarations have been submitted directly on this I-D.
>
>> _______________________________________________
>
>> IETF-Announce mailing list
>
>> IETF-Announce@ietf.org
>
>> https://www.ietf.org/mailman/listinfo/ietf-announce
>
>
>
> _______________________________________________
>
> mpls mailing list
>
> mpls@ietf.org
>
> https://www.ietf.org/mailman/listinfo/mpls
>
> _______________________________________________
>
> Ietf mailing list
>
> Ietf@ietf.org
>
> https://www.ietf.org/mailman/listinfo/ietf
>
> _______________________________________________
>
> Ietf mailing list
>
> Ietf@ietf.org
>
> https://www.ietf.org/mailman/listinfo/ietf
>
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>
_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf

--EPOC32-lxFY_kRZZ-69LvD5+1f9FQDbsyxw,hpmf,CK06ll+0qRM1Yq--

From ron.even.tlv@gmail.com  Tue Mar 13 12:26:12 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 0626521E806A; Tue, 13 Mar 2012 12:26:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.171
X-Spam-Level: 
X-Spam-Status: No, score=-3.171 tagged_above=-999 required=5 tests=[AWL=0.427,  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 5LdqRuNv6UBi; Tue, 13 Mar 2012 12:26: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 DAB5D21E804F; Tue, 13 Mar 2012 12:26:09 -0700 (PDT)
Received: by werb10 with SMTP id b10so1107548wer.31 for <multiple recipients>; Tue, 13 Mar 2012 12:26:08 -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=uGIDrycOtOSmXLa7iiHyBRPItkDPjilOUAWWbVb9Qgw=; b=0FxbbfTVGWD56GBiqNAbgKAyvVxc4l69HnEkLp2XTihDAzNJzEArxi8uo3uYZ9fR4q cWTf+iGKVG9VNySv33KeGGgmMYyx2QOYeqXQccVjvKPyuoWz6TbCj1SWfPPE54/9O5z6 C+m/inh+3O8meL+Aaw91d37d4mgap/LUlsizPjBO07tX5PAGtDrysiZTFCjwwRSy0cWd Od6RBF4XuWU+X6/yjhZBmuTgbdFAW6a7I5hX5xqwGW3CF8IwQXhdJedSGadOgwQ4gjmP zSdPdEQ71ziBaoUFXNrqlzBpoYe6JqGgWLiNPW2kIlK/Teovkq+sJA33B45BDQg5R9Oi IWNw==
Received: by 10.180.14.230 with SMTP id s6mr10304083wic.2.1331666768840; Tue, 13 Mar 2012 12:26:08 -0700 (PDT)
Received: from windows8d787f9 (bzq-79-179-219-130.red.bezeqint.net. [79.179.219.130]) by mx.google.com with ESMTPS id ff9sm6892005wib.2.2012.03.13.12.26.06 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 13 Mar 2012 12:26:08 -0700 (PDT)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: <draft-melnikov-smtp-priority.all@tools.ietf.org>
Subject: Gen-ART LC review of draft-melnikov-smtp-priority-09
Date: Tue, 13 Mar 2012 21:25:14 +0200
Message-ID: <4f5f9f50.6965b40a.7aaa.6114@mx.google.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_013B_01CD015F.C98A7E30"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac0BTwMc+gwlflbzSpuG4aNP5alsxA==
Content-Language: en-us
Cc: gen-art@ietf.org, 'IETF-Discussion list' <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Mar 2012 19:26:12 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_013B_01CD015F.C98A7E30
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-melnikov-smtp-priority-09

Reviewer: Roni Even

Review Date:2012-3-13

IETF LC End Date: 2012-3-28

IESG Telechat date:

 

Summary: This draft is almost ready for publication as a standard track RFC.

 

Major issues:

 

Minor issues:

 

1.       In section 4.2  "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." .      My
understanding  from the third bullet in this section is that for this case
the message priority is "0" so I am not clear what this sentence means and
why is there a  difference if the MT-PRIORITY or MT-Priority values do exist
with regards to "Priority" and "X-Priority" for this case.

2.       In section 8 "MT-PRIORITY=3". I did not see where the MT-PRIORITY
SMTP  extension is specified and has the syntax of using "=" before the
value.

 

 

Nits/editorial comments:

 

1.       MUA is used in section 1 but expanded only in section 5. 

2.       Some typos in section 5. "syntatically - syntactically" "prioritiy
- priority" "comminicate - communicate" "contraints -constraints"

3.       In section 10 for X.3.TBD3 "Description:  The message mas accepted"
I assume you meant "was"

4.       In section D.2 first paragraph some typos "focusses -focuses"
"comparision - comparison"

 

 


------=_NextPart_000_013B_01CD015F.C98A7E30
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 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: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;}
@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:1208569498;
	mso-list-type:hybrid;
	mso-list-template-ids:1331728552 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-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level4
	{mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level7
	{mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1
	{mso-list-id:1999921501;
	mso-list-type:hybrid;
	mso-list-template-ids:-1736538686 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-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level3
	{mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level4
	{mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level5
	{mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level6
	{mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level7
	{mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level8
	{mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level9
	{mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
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>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 =
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-melni=
kov-smtp-priority-09<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;3&#8211;13<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;3&#8211;28<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 a standard track =
</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>RFC</span><=
span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>.<o:p></o:p=
></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Major =
issues:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Minor =
issues:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list: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"'>In section =
4.2&nbsp; &#8220;In absence of both the MT-PRIORITY MAIL FROM =
parameter&nbsp; and the MT-Priority header field, other message header =
fields, such&nbsp; as Priority [RFC2156] and X-Priority, MAY be used for =
determining the&nbsp; priority under this &quot;Priority Message =
Handling&quot; SMTP extension.&#8221; . &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;My =
understanding&nbsp; from the third bullet in this section is that for =
this case the message priority is &#8220;0&#8221; so I am not clear what =
this sentence means and why is there a &nbsp;difference if the =
MT-PRIORITY or MT-Priority values do exist with regards to =
&#8220;Priority&#8221; and &#8220;X-Priority&#8221; for this =
case.<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"'>In section =
8 &#8220;MT-PRIORITY=3D3&#8221;. I did not see where </span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>the =
MT-PRIORITY SMTP&nbsp; extension is specified and has the syntax of =
using &#8220;=3D&#8221; before the value.</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p></o:p>=
</span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>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"'>MUA is =
used in section 1 but expanded only in section 5. =
<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"'>Some typos =
in section 5. </span><span style=3D'font-family:"Courier =
New"'>&#8220;</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>syntaticall=
y &#8211; syntactically&#8221; &#8220;prioritiy &#8211; priority&#8221; =
&#8220;comminicate &#8211; communicate&#8221; &#8220;contraints =
&#8211;constraints&#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 for X.3.TBD3 &#8220;Description:&nbsp; The message mas =
accepted&#8221; I assume you meant =
&#8220;was&#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'>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"'>In section =
D.2 first paragraph some typos </span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>&#8220;focu=
sses &#8211;focuses&#8221; &#8220;comparision &#8211; =
comparison&#8221;<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_013B_01CD015F.C98A7E30--


From lear@cisco.com  Tue Mar 13 12:43:53 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 3CE4621F8496; Tue, 13 Mar 2012 12:43:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.558
X-Spam-Level: 
X-Spam-Status: No, score=-110.558 tagged_above=-999 required=5 tests=[AWL=0.041, 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 gVYNvXw5PiTW; Tue, 13 Mar 2012 12:43:52 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by ietfa.amsl.com (Postfix) with ESMTP id B76D421F8484; Tue, 13 Mar 2012 12:43:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=lear@cisco.com; l=698; q=dns/txt; s=iport; t=1331667832; x=1332877432; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=OUk2bvCpX8AP+OOxoU10AZriwLM6bnpkMJcV2oMmKq0=; b=VxyP16yFJmKjluT/FoGMM6jyQT8dYsBQdglgWa15VglAZmO1y6QVpPsJ A6pPzw4xogyp+yRBCM0sz731zL1EwF8zkKnULhRPSPlendHuKIW+VPNmi DYrzQ1OyG+6Lf7CcdGoURiZ4WFjIU5tM3kN/x+v1dMdDlgK4OoW8y4+ey A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAHOiX0+Q/khL/2dsb2JhbABDhTqwMoEHggkBAQEEEgEQVhALDgQGAgIFIQICDwI4DgYNAQcBAR6HaJx8AYxxkg6BL44ggRYElVCQI4Jm
X-IronPort-AV: E=Sophos;i="4.73,579,1325462400"; d="scan'208";a="132220039"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by ams-iport-1.cisco.com with ESMTP; 13 Mar 2012 19:43:50 +0000
Received: from dhcp-10-61-99-194.cisco.com (dhcp-10-61-99-194.cisco.com [10.61.99.194]) by ams-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id q2DJho8V022595; Tue, 13 Mar 2012 19:43:50 GMT
Message-ID: <4F5FA375.20908@cisco.com>
Date: Tue, 13 Mar 2012 20:43:49 +0100
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: John Scudder <jgs@juniper.net>
Subject: Re: [lisp] WG Review: Recharter of Locator/ID Separation Protocol (lisp)
References: <20120214222316.CF29521E800E@ietfa.amsl.com> <201202152131.q1FLVB9E028114@cichlid.raleigh.ibm.com> <EF3C34EB-C0AA-45F2-ADE0-407CEF5172DD@juniper.net> <4F3E4EDB.7070509@piuha.net> <0E0C6A25-FBA6-4E11-9E89-DEBFFCF41108@juniper.net> <4F58EB8C.1000700@piuha.net> <70EB276F-D77E-45AE-851C-AB08A8D56D0A@juniper.net> <4F5920FF.6070502@piuha.net> <CALaySJKvS5QbtXuMx7TwFiL4hdgi1cT0sYu8EJtYLD6T2yOzKQ@mail.gmail.com> <1D2FF8E9-8E60-4126-AC30-12DFDC854BC6@juniper.net> <4F5F9A44.4020600@joelhalpern.com> <754A7276-FC6F-4C76-8627-4AEDB5FBB4C4@juniper.net>
In-Reply-To: <754A7276-FC6F-4C76-8627-4AEDB5FBB4C4@juniper.net>
X-Enigmail-Version: 1.4
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: "iesg@ietf.org IESG" <iesg@ietf.org>, "ietf@ietf.org list" <ietf@ietf.org>, Barry Leiba <barryleiba@computer.org>, "lisp@ietf.org" <lisp@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Mar 2012 19:43:53 -0000

John,

On 3/13/12 8:23 PM, John Scudder wrote:
> Re cache management schemes, I think that depends on whether you mean "system level behavior" of a small-scale system, or one operating at large scale or under some kind of stress. The earlier discussion notwithstanding, for practical purposes caching is central to LISP; as such, it's a little weird to say it's architecturally unimportant.

I don't think Joel is saying that it is architecturally unimportant, but
rather that within the architecture it various caching schemes may work
better than others, and that experience may dictate the answer to this. 
What are system effects, by the way, is its own interesting question.

Eliot

From jnc@mercury.lcs.mit.edu  Tue Mar 13 12:53:28 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 DFCC321F8637; Tue, 13 Mar 2012 12:53:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.448
X-Spam-Level: 
X-Spam-Status: No, score=-6.448 tagged_above=-999 required=5 tests=[AWL=0.151,  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 PrCJkNUvUsoT; Tue, 13 Mar 2012 12:53:27 -0700 (PDT)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id E037421F8636; Tue, 13 Mar 2012 12:53:26 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id CE16B18C0BA; Tue, 13 Mar 2012 15:53:25 -0400 (EDT)
To: ietf@ietf.org, lisp@ietf.org
Subject: Re: [lisp] WG Review: Recharter of Locator/ID Separation Protocol (lisp)
Message-Id: <20120313195325.CE16B18C0BA@mercury.lcs.mit.edu>
Date: Tue, 13 Mar 2012 15:53:25 -0400 (EDT)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: iesg@ietf.org, 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: Tue, 13 Mar 2012 19:53:28 -0000

    > From: John Scudder <jgs@juniper.net>

    > Re cache management schemes, I think that depends on whether you
    > mean "system level behavior" of a small-scale system, or one
    > operating at large scale or under some kind of stress. The earlier
    > discussion notwithstanding, for practical purposes caching is
    > central to LISP; as such, it's a little weird to say it's
    > architecturally unimportant.

I didn't hear him say that. I think he said 'the details of particular
cache management algorithm(s) aren't important to an _architectural_
understanding of LISP'.

Now, what you mean by 'architectural understanding' and what I (and
probably Joel) mean by 'architectural understanding' may be two different
things, which may be the source of the problem.

What I mean by that term is 'how is the entire system broken up into
subsystems' (i.e. what are the functional units), and 'how do they
interact'. I.e. a very high-level view of how the system as a whole
operates - an overview in which more detailed views of individual
subsystems can be slotted.

That is something totally different from 'a complete model/understanding of
how the system operates in various operational environments', which is
somewhere in the direction of what you seem to want?


Now, clearly the latter is something useful to have, but I'd like to point
out that in its maximum generality it may be a 'boil the ocean' kind of
goal.

E.g. to have a complete and total understanding of how, say, the Internet
path selection system as whole operates, you'd have to model every last
piece of it (every router, etc, etc), because there's no analytical proof
that it operates in any particular way. However, of necessity, any such a
model is probably infeasible - we can build smaller models, and see how
they operate, but they can only offer limited insight (how limited, we
cannot say for sure) into just how the full-scale system is going to work.

To do that, we just built it (why do multi-dimensional mice come to mind
here?), and we can instrument it and watch it (as numerous studies have
done, e.g. the very fine work by Craig Leibowitz and Abha Ahuja some years
ago). But any sub-full-scale model is necessarily going to be 'an
incomplete description of reality', to use the fine phrase from EPR.


Which is not to say that better understanding of how the caching in LISP works
in various operating environments (e.g. under various kinds of attack/stress),
and how different potential cache management algorithms would work across a
range of operational scenarios, is not useful and/or desirable. Of course it
would be.

(Do we have any volunteers? A considerable amount of work on caching
simulation has already been done, but of course there's an infinite space of
possible things to explore, both on the algorithm side and the operational
scenario side.)

However, i) such work is not a 'description of the architecture' as I
understand it, nor ii) is it _absolutely_ necessary before trying a system in
large scale, because to do it 'perfectly' is an impossible 'chicken and egg'
situation: there is no perfect model _other than the system itself_. The only
way to _really_ see how it works is to build it.

Or am I too misunderstanding something?

	Noel

From stpeter@stpeter.im  Tue Mar 13 15:19:20 2012
Return-Path: <stpeter@stpeter.im>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DEB5C21F8445 for <ietf@ietfa.amsl.com>; Tue, 13 Mar 2012 15:19:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.41
X-Spam-Level: 
X-Spam-Status: No, score=-102.41 tagged_above=-999 required=5 tests=[AWL=-0.411, BAYES_00=-2.599, J_CHICKENPOX_15=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6z+ZFFvtGEe0 for <ietf@ietfa.amsl.com>; Tue, 13 Mar 2012 15:19:20 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 0216321E8028 for <ietf@ietf.org>; Tue, 13 Mar 2012 15:19:20 -0700 (PDT)
Received: from squire.local (unknown [64.101.72.114]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id B573140058; Tue, 13 Mar 2012 16:31:29 -0600 (MDT)
Message-ID: <4F5FC7DC.5040203@stpeter.im>
Date: Tue, 13 Mar 2012 16:19:08 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.5; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: "t.petch" <daedulus@btconnect.com>
Subject: Re: Last Call: <draft-ietf-appsawg-xdash-03.txt> (Deprecating Use of the"X-" Prefix in Application Protocols) to Best Current Practice
References: <20120301184750.21152.93044.idtracker@ietfa.amsl.com> <028601cd00fc$f5ba5380$4001a8c0@gateway.2wire.net>
In-Reply-To: <028601cd00fc$f5ba5380$4001a8c0@gateway.2wire.net>
X-Enigmail-Version: 1.3.5
OpenPGP: url=https://stpeter.im/stpeter.asc
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Mark Nottingham <mnot@mnot.net>, ietf@ietf.org, Dave CROCKER <dcrocker@bbiw.net>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Mar 2012 22:19:21 -0000

On 3/13/12 3:37 AM, t.petch wrote:
> I am surprised at the lack of comment on this I-D on its use of terminology.  I
> have seen and learnt from many discussions on this list that have teased out
> what concept it is we are really talking about (e.g. identity v identifier) and
> this I-D seems somewhat weak in that regard.
> 
> Thus the summary 

Clarifying quesiton: do you mean the abstract?

> talks of
> 'parameters by prefixing the latter '

http://tools.ietf.org/html/draft-ietf-appsawg-xdash-04 does not contain
that string. The discussions on this list and with the IESG have led to
some changes in the text. The Abstract now reads:

   Historically, designers and implementers of application protocols
   have often distinguished between "standard" and "non-standard"
   parameters by prefixing the names of "non-standard" parameters with
   the string "X-" or similar constructs.  In practice, that convention
   causes more problems than it solves.  Therefore, this document
   deprecates the convention for the names of newly-defined textual
   parameters in application protocols.

> while the  introduction changes that to
> 'the "X-" convention for named parameters in application protocols '
> which is then refined to
> 'only parameters with textual names, not parameters that are expressed as
> numbers'
> which seems to me a false dichotomy.

The relevant paragraph of the Introduction now reads:

   Many application protocols use parameters with textual names to
   identify data (media types, header fields in Internet mail messages
   and HTTP requests, vCard parameters and properties, etc.).
   Historically, designers and implementers of application protocols
   have often distinguished between "standard" and "non-standard"
   parameters by prefixing the names of "non-standard" parameters with
   the string "X-" or similar constructs (e.g., "x."), where the "X" is
   commonly understood to stand for "eXperimental" or "eXtension".  That
   is, instead of just identifying the data, the name also embedded the
   status of the name as "non-standard" into the name itself.

> The I-D seems to be conflating the ideas of name and value 

In my opinion, I think those ideas are clearer now in -04, again based
on feedback we have received and addressed. Please take a look at the
latest version and let us know what you think.

> and a few other
> things as well. 

Please do clarify what other things you think are conflated.

> I know of very few parameters in IETF protocols that do not
> have names and cannot recall one where the name is not textual. 

The contrast is with parameters whose names are numerical, not textual.
Often parameter spaces whose names are numerical are smaller, i.e., do
not allow such a wide range of names; in such cases, the considerations
in BCP 82 might apply.

> The I-D seems
> to be assuming that the parameter name and the parameter value and so on are
> synonymous, identical, equivalent and perhaps a few other things as well, and
> having assumed that, then it is sufficient to say that one or other of these
> concepts are textual and it is to these that this I-D applies.  This seems to me
> to be rather too loosely worded to become an RFC.

This I-D says absolutely nothing about parameter values. If some folks
have understood differently, then we need to clarify the wording. I can
now see that "the names of newly-defined textual parameters" in the
Abstract could be misconstrued, although I think the phrasing in the
Introduction is clearer: "parameters with textual names". In both
instances we could further clarify our intent by using the phrase
"parameters with textual (as opposed to numerical) names".

Peter

-- 
Peter Saint-Andre
https://stpeter.im/



From stpeter@stpeter.im  Tue Mar 13 15:24:00 2012
Return-Path: <stpeter@stpeter.im>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 74F2321F85C7 for <ietf@ietfa.amsl.com>; Tue, 13 Mar 2012 15:23:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.408
X-Spam-Level: 
X-Spam-Status: No, score=-102.408 tagged_above=-999 required=5 tests=[AWL=-0.409, BAYES_00=-2.599, J_CHICKENPOX_15=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a-W5vbdTHO5S for <ietf@ietfa.amsl.com>; Tue, 13 Mar 2012 15:23:57 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 46E0E21F85C6 for <ietf@ietf.org>; Tue, 13 Mar 2012 15:23:57 -0700 (PDT)
Received: from squire.local (unknown [64.101.72.114]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 69CD540058; Tue, 13 Mar 2012 16:36:16 -0600 (MDT)
Message-ID: <4F5FC8FB.5010405@stpeter.im>
Date: Tue, 13 Mar 2012 16:23:55 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.5; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: "t.petch" <daedulus@btconnect.com>
Subject: Re: Last Call: <draft-ietf-appsawg-xdash-03.txt> (Deprecating Use of the"X-" Prefix in Application Protocols) to Best Current Practice
References: <20120301184750.21152.93044.idtracker@ietfa.amsl.com> <028601cd00fc$f5ba5380$4001a8c0@gateway.2wire.net> <4F5FC7DC.5040203@stpeter.im>
In-Reply-To: <4F5FC7DC.5040203@stpeter.im>
X-Enigmail-Version: 1.3.5
OpenPGP: url=https://stpeter.im/stpeter.asc
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Mark Nottingham <mnot@mnot.net>, ietf@ietf.org, Dave CROCKER <dcrocker@bbiw.net>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Mar 2012 22:24:00 -0000

On 3/13/12 4:19 PM, Peter Saint-Andre wrote:
> On 3/13/12 3:37 AM, t.petch wrote:
>> I am surprised at the lack of comment on this I-D on its use of terminology.  I
>> have seen and learnt from many discussions on this list that have teased out
>> what concept it is we are really talking about (e.g. identity v identifier) and
>> this I-D seems somewhat weak in that regard.
>>
>> Thus the summary 
> 
> Clarifying quesiton: do you mean the abstract?
> 
>> talks of
>> 'parameters by prefixing the latter '
> 
> http://tools.ietf.org/html/draft-ietf-appsawg-xdash-04 does not contain
> that string. The discussions on this list and with the IESG have led to
> some changes in the text. The Abstract now reads:
> 
>    Historically, designers and implementers of application protocols
>    have often distinguished between "standard" and "non-standard"
>    parameters by prefixing the names of "non-standard" parameters with
>    the string "X-" or similar constructs.  In practice, that convention
>    causes more problems than it solves.  Therefore, this document
>    deprecates the convention for the names of newly-defined textual
>    parameters in application protocols.
> 
>> while the  introduction changes that to
>> 'the "X-" convention for named parameters in application protocols '
>> which is then refined to
>> 'only parameters with textual names, not parameters that are expressed as
>> numbers'
>> which seems to me a false dichotomy.
> 
> The relevant paragraph of the Introduction now reads:
> 
>    Many application protocols use parameters with textual names to
>    identify data (media types, header fields in Internet mail messages
>    and HTTP requests, vCard parameters and properties, etc.).
>    Historically, designers and implementers of application protocols
>    have often distinguished between "standard" and "non-standard"
>    parameters by prefixing the names of "non-standard" parameters with
>    the string "X-" or similar constructs (e.g., "x."), where the "X" is
>    commonly understood to stand for "eXperimental" or "eXtension".  That
>    is, instead of just identifying the data, the name also embedded the
>    status of the name as "non-standard" into the name itself.
> 
>> The I-D seems to be conflating the ideas of name and value 
> 
> In my opinion, I think those ideas are clearer now in -04, again based
> on feedback we have received and addressed. Please take a look at the
> latest version and let us know what you think.
> 
>> and a few other
>> things as well. 
> 
> Please do clarify what other things you think are conflated.
> 
>> I know of very few parameters in IETF protocols that do not
>> have names and cannot recall one where the name is not textual. 
> 
> The contrast is with parameters whose names are numerical, not textual.
> Often parameter spaces whose names are numerical are smaller, i.e., do
> not allow such a wide range of names; in such cases, the considerations
> in BCP 82 might apply.
> 
>> The I-D seems
>> to be assuming that the parameter name and the parameter value and so on are
>> synonymous, identical, equivalent and perhaps a few other things as well, and
>> having assumed that, then it is sufficient to say that one or other of these
>> concepts are textual and it is to these that this I-D applies.  This seems to me
>> to be rather too loosely worded to become an RFC.
> 
> This I-D says absolutely nothing about parameter values. If some folks
> have understood differently, then we need to clarify the wording. I can
> now see that "the names of newly-defined textual parameters" in the
> Abstract could be misconstrued, although I think the phrasing in the
> Introduction is clearer: "parameters with textual names". In both
> instances we could further clarify our intent by using the phrase
> "parameters with textual (as opposed to numerical) names".

In our working copy I have changed the last sentence of the Abstract to:

   Therefore, this document deprecates the convention for newly-defined
   parameters with textual (as opposed to numerical) names in
   application protocols.

Peter

-- 
Peter Saint-Andre
https://stpeter.im/



From yang.jian90@zte.com.cn  Wed Mar 14 00:46:23 2012
Return-Path: <yang.jian90@zte.com.cn>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AB17121F8624 for <ietf@ietfa.amsl.com>; Wed, 14 Mar 2012 00:46:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -97.007
X-Spam-Level: 
X-Spam-Status: No, score=-97.007 tagged_above=-999 required=5 tests=[AWL=4.832, BAYES_00=-2.599, RCVD_DOUBLE_IP_LOOSE=0.76, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QCOCodUGI7BQ for <ietf@ietfa.amsl.com>; Wed, 14 Mar 2012 00:46:23 -0700 (PDT)
Received: from mx5.zte.com.cn (mx6.zte.com.cn [95.130.199.165]) by ietfa.amsl.com (Postfix) with ESMTP id A6F4821F8622 for <ietf@ietf.org>; Wed, 14 Mar 2012 00:46:22 -0700 (PDT)
Received: from [10.30.17.99] by mx5.zte.com.cn with surfront esmtp id 1228011182326; Wed, 14 Mar 2012 15:12:32 +0800 (CST)
Received: from [10.30.3.20] by [192.168.168.15] with StormMail ESMTP id 65905.11182326; Wed, 14 Mar 2012 15:46:11 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse01.zte.com.cn with ESMTP id q2E7k2G3071136 for <ietf@ietf.org>; Wed, 14 Mar 2012 15:46:02 +0800 (GMT-8) (envelope-from yang.jian90@zte.com.cn)
Subject: RE: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt>(Allocation of an Associated Channel Code Point for Use byITU-T Ethernet based OAM) to Informational RFC
To: <ietf@ietf.org>
X-Mailer: Lotus Notes Release 6.5.4 March 27, 2005
Message-ID: <OF3C543221.C8BC381A-ON482579C1.00293D49-482579C1.002AABD6@zte.com.cn>
From: yang.jian90@zte.com.cn
Date: Wed, 14 Mar 2012 15:46:01 +0800
X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 8.5.1FP4|July 25, 2010) at 2012-03-14 15:46:04
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
X-MAIL: mse01.zte.com.cn q2E7k2G3071136
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Mar 2012 07:46:23 -0000

Hi all,

I support the allocation of the code point to G.8113.1.

Since the collaboration on MPLS-TP within two SDOs, IETF should should
allow the ITU-T to progress refinements to G.8113.1 such that it can
satisfy all the functional requirements defined in RFC 5860.

Jian


> -----Original Message-----
> From: ietf-announce-bounces@ietf.org [mailto:ietf-announce-
> bounces@ietf.org] On Behalf Of The IESG
> Sent: 22 February 2012 15:13
> To: IETF-Announce
> Subject: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt>
(Allocation of
an
> Associated Channel Code Point for Use by ITU-T Ethernet based OAM) to
> Informational RFC
>
>
> The IESG has received a request from an individual submitter to
consider
> the following document:
> - 'Allocation of an Associated Channel Code Point for Use by ITU-T
>    Ethernet based OAM'
>   <draft-betts-itu-oam-ach-code-point-03.txt> as an 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-03-21. 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 assigns an Associated Channel Type code point for
>    carrying Ethernet based Operations, Administration, and Management
>    messages in the MPLS Generic Associated Channel (G-ACh).
>
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-betts-itu-oam-ach-code-point/
>
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-betts-itu-oam-ach-code-point/
>
>
> No IPR declarations have been submitted directly on this I-D.
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-announce

_______________________________________________
pwe3 mailing list
pwe3@ietf.org
https://www.ietf.org/mailman/listinfo/pwe3
_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf

                                                            
                                                            
                                                            





From mansaxel@besserwisser.org  Wed Mar 14 00:47:10 2012
Return-Path: <mansaxel@besserwisser.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 814C321F86A1 for <ietf@ietfa.amsl.com>; Wed, 14 Mar 2012 00:47:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.3
X-Spam-Level: 
X-Spam-Status: No, score=-2.3 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Aa7XOGIFm7dn for <ietf@ietfa.amsl.com>; Wed, 14 Mar 2012 00:47:09 -0700 (PDT)
Received: from jaja.besserwisser.org (primary.se [IPv6:2a01:298:4::53]) by ietfa.amsl.com (Postfix) with ESMTP id B31E721F86A0 for <ietf@ietf.org>; Wed, 14 Mar 2012 00:47:09 -0700 (PDT)
Received: by jaja.besserwisser.org (Postfix, from userid 1004) id 24E709E72; Wed, 14 Mar 2012 08:47:07 +0100 (CET)
Date: Wed, 14 Mar 2012 08:47:07 +0100
From: =?iso-8859-1?Q?M=E5ns?= Nilsson <mansaxel@besserwisser.org>
To: nanog@nanog.org
Subject: Re: shared address space... a reality!
Message-ID: <20120314074707.GZ16111@besserwisser.org>
References: <CAL9jLaZyPBDaGyom4Qrdt+TfzBONftH_Zxtjp1MfiH3tBLXejA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <CAL9jLaZyPBDaGyom4Qrdt+TfzBONftH_Zxtjp1MfiH3tBLXejA@mail.gmail.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Mar 2012 07:47:10 -0000

On Wed, Mar 14, 2012 at 02:22:04AM -0400, Christopher Morrow wrote:
> NetRange:       100.64.0.0 - 100.127.255.255
> CIDR:           100.64.0.0/10
> OriginAS:
> NetName:        SHARED-ADDRESS-SPACE-RFCTBD-IANA-RESERVED
 
GOOD.

Now I can BOTH keep sticking my head in the sand AND get NEW RFC 1918
space to number my devices!

Trailing edge WINS!

Congrats, all you people who joined the ietf mailing list to get your
VOTE through. You can sign off now and continue non-contributing to the
developement of the future.

-- 
/Måns, pissed off. 

From rogerj@gmail.com  Wed Mar 14 01:31:50 2012
Return-Path: <rogerj@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BF34121F869C for <ietf@ietfa.amsl.com>; Wed, 14 Mar 2012 01:31:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.138
X-Spam-Level: 
X-Spam-Status: No, score=-3.138 tagged_above=-999 required=5 tests=[AWL=0.161,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a9V3qwOn53XR for <ietf@ietfa.amsl.com>; Wed, 14 Mar 2012 01:31:49 -0700 (PDT)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id 62D1C21F8615 for <ietf@ietf.org>; Wed, 14 Mar 2012 01:31:49 -0700 (PDT)
Received: by iazz13 with SMTP id z13so2335570iaz.31 for <ietf@ietf.org>; Wed, 14 Mar 2012 01:31: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:content-transfer-encoding; bh=OLD0RDAqExxTdezsdV0hkznyo6KxD+AKg8eGKpeg8M0=; b=awDeLRMg7pPGDTo+EGvikRlpWKUsNE0/oThKqAK4WZEz/aJc1yL/ahcP65Q/rIo60z 12vH2FPJs4xllbnHDhRcV46UhZgffXCvt5Cm1fnh/4P82/NrtkikYVMh2DdWZ7tjs68d 48q6cCC1Thep3fkgAlMJiThxHoLz7fntA2RsSoAXrB5mvEDce7MeSPzbVKKR4HA/hKH4 uswbTk2GFx/hV4LHS/BfjQgHDXARH5x82owrqcPFBsTR62kFDyQTHBvPYXURjo0vpP3V CW5GKVE+8df+n+ZL4hPlPRCsu9nzK3imJdQYZBHp742MldawTz9/l2/q3rgV0ctdkNOl PwAA==
MIME-Version: 1.0
Received: by 10.50.216.231 with SMTP id ot7mr3369118igc.8.1331713908962; Wed, 14 Mar 2012 01:31:48 -0700 (PDT)
Received: by 10.42.117.200 with HTTP; Wed, 14 Mar 2012 01:31:48 -0700 (PDT)
In-Reply-To: <20120314074707.GZ16111@besserwisser.org>
References: <CAL9jLaZyPBDaGyom4Qrdt+TfzBONftH_Zxtjp1MfiH3tBLXejA@mail.gmail.com> <20120314074707.GZ16111@besserwisser.org>
Date: Wed, 14 Mar 2012 09:31:48 +0100
Message-ID: <CAKFn1SEGpUSyTnM5kOFT9J=y1AbXDLxti7g-KGKk7dXFWyfNwg@mail.gmail.com>
Subject: Re: shared address space... a reality!
From: =?ISO-8859-1?Q?Roger_J=F8rgensen?= <rogerj@gmail.com>
To: =?ISO-8859-1?Q?M=E5ns_Nilsson?= <mansaxel@besserwisser.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Mar 2012 08:31:50 -0000

On Wed, Mar 14, 2012 at 8:47 AM, M=E5ns Nilsson <mansaxel@besserwisser.org>=
 wrote:
> On Wed, Mar 14, 2012 at 02:22:04AM -0400, Christopher Morrow wrote:
>> NetRange: =A0 =A0 =A0 100.64.0.0 - 100.127.255.255
>> CIDR: =A0 =A0 =A0 =A0 =A0 100.64.0.0/10
>> OriginAS:
>> NetName: =A0 =A0 =A0 =A0SHARED-ADDRESS-SPACE-RFCTBD-IANA-RESERVED
>
> GOOD.
>
> Now I can BOTH keep sticking my head in the sand AND get NEW RFC 1918
> space to number my devices!

This is really "good" news for some people, that already have address
conflict within RFC1918 and don't want to get public address space :p


--- Roger J ---

>
> Trailing edge WINS!
>
> Congrats, all you people who joined the ietf mailing list to get your
> VOTE through. You can sign off now and continue non-contributing to the
> developement of the future.
>
> --
> /M=E5ns, pissed off.



--=20

Roger Jorgensen=A0 =A0 =A0 =A0 =A0=A0 |
rogerj@gmail.com=A0 =A0 =A0 =A0 =A0 | - IPv6 is The Key!
http://www.jorgensen.no=A0=A0 | roger@jorgensen.no

From nurit.sprecher@nsn.com  Wed Mar 14 03:24:18 2012
Return-Path: <nurit.sprecher@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 29F2721F8754 for <ietf@ietfa.amsl.com>; Wed, 14 Mar 2012 03:24:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.544
X-Spam-Level: 
X-Spam-Status: No, score=-6.544 tagged_above=-999 required=5 tests=[AWL=0.055,  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 8ISLJVbPXIVH for <ietf@ietfa.amsl.com>; Wed, 14 Mar 2012 03:24:17 -0700 (PDT)
Received: from demumfd002.nsn-inter.net (demumfd002.nsn-inter.net [93.183.12.31]) by ietfa.amsl.com (Postfix) with ESMTP id 1A15A21F8768 for <ietf@ietf.org>; Wed, 14 Mar 2012 03:24:16 -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 q2EAOFRV005460 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 14 Mar 2012 11:24:15 +0100
Received: from DEMUEXC048.nsn-intra.net ([10.159.32.94]) by demuprx017.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id q2EAO70u028164; Wed, 14 Mar 2012 11:24:15 +0100
Received: from DEMUEXC013.nsn-intra.net ([10.150.128.24]) by DEMUEXC048.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 14 Mar 2012 11:24:06 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="windows-1255"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt>(Allocationof anAssociated Channel Code Point for Use byITU-T Ethernet based OAM) toInformational RFC
Date: Wed, 14 Mar 2012 11:19:29 +0100
Message-ID: <E4873516F3FC7547BCFE792C7D94039C016F6EDF@DEMUEXC013.nsn-intra.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt>(Allocationof anAssociated Channel Code Point for Use byITU-T Ethernet based OAM) toInformational RFC
Thread-Index: Ac0Btq6LkN8G/loaQgO+/CqYJpEPVwAFUKXO
References: <OF3C543221.C8BC381A-ON482579C1.00293D49-482579C1.002AABD6@zte.com.cn>
From: "Sprecher, Nurit (NSN - IL/Hod HaSharon)" <nurit.sprecher@nsn.com>
To: <yang.jian90@zte.com.cn>, <ietf@ietf.org>
X-OriginalArrivalTime: 14 Mar 2012 10:24:06.0191 (UTC) FILETIME=[95CE8BF0:01CD01CC]
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: 3425
X-purgate-ID: 151667::1331720655-000033AC-1EA160AF/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, 14 Mar 2012 10:24:18 -0000

Jian hello,
I would warmly recommend you not to mention the collaboration on =
MPLS-TP.
According to the collaborative agreement between the organziations we =
were supposed to see a single solution developed in the IETF using the =
IETF processess...
The developmenet of an alternative solution in the ITU-T for MPLS-TP OAM =
is obviously in contrary to the collaborative agreement and in contarry =
to the ITU-T's commitment for the collaboration in TD7 as sent to the =
IETF in a liaison, where the ITU-T clearly mentioned that the soltuions =
will be developed in the IETF using the IETF processes.=20
Best regards,
Nurit

________________________________

=EE=E0=FA: ietf-bounces@ietf.org =E1=F9=ED ext yang.jian90@zte.com.cn
=F0=F9=EC=E7: =E3 14/03/2012 08:46
=E0=EC: ietf@ietf.org
=F0=E5=F9=E0: RE: Last Call: =
<draft-betts-itu-oam-ach-code-point-03.txt>(Allocationof anAssociated =
Channel Code Point for Use byITU-T Ethernet based OAM) toInformational =
RFC




Hi all,

I support the allocation of the code point to G.8113.1.

Since the collaboration on MPLS-TP within two SDOs, IETF should should
allow the ITU-T to progress refinements to G.8113.1 such that it can
satisfy all the functional requirements defined in RFC 5860.

Jian


> -----Original Message-----
> From: ietf-announce-bounces@ietf.org [mailto:ietf-announce-
> bounces@ietf.org] On Behalf Of The IESG
> Sent: 22 February 2012 15:13
> To: IETF-Announce
> Subject: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt>
(Allocation of
an
> Associated Channel Code Point for Use by ITU-T Ethernet based OAM) to
> Informational RFC
>
>
> The IESG has received a request from an individual submitter to
consider
> the following document:
> - 'Allocation of an Associated Channel Code Point for Use by ITU-T
>    Ethernet based OAM'
>   <draft-betts-itu-oam-ach-code-point-03.txt> as an 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-03-21. 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 assigns an Associated Channel Type code point for
>    carrying Ethernet based Operations, Administration, and Management
>    messages in the MPLS Generic Associated Channel (G-ACh).
>
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-betts-itu-oam-ach-code-point/
>
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-betts-itu-oam-ach-code-point/
>
>
> No IPR declarations have been submitted directly on this I-D.
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-announce

_______________________________________________
pwe3 mailing list
pwe3@ietf.org
https://www.ietf.org/mailman/listinfo/pwe3
_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf

                                                          =20
                                                          =20
                                                          =20







From nurit.sprecher@nsn.com  Wed Mar 14 03:43:41 2012
Return-Path: <nurit.sprecher@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 E59E221F85FF for <ietf@ietfa.amsl.com>; Wed, 14 Mar 2012 03:43:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.072
X-Spam-Level: 
X-Spam-Status: No, score=-6.072 tagged_above=-999 required=5 tests=[AWL=-0.420, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4, SARE_SUB_ENC_WIN1255=0.647]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dC9UNDHbFC76 for <ietf@ietfa.amsl.com>; Wed, 14 Mar 2012 03:43:41 -0700 (PDT)
Received: from demumfd002.nsn-inter.net (demumfd002.nsn-inter.net [93.183.12.31]) by ietfa.amsl.com (Postfix) with ESMTP id 8025B21F85FB for <ietf@ietf.org>; Wed, 14 Mar 2012 03:43:40 -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 q2EAhc8b028395 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 14 Mar 2012 11:43:38 +0100
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 q2EAhZOD004840; Wed, 14 Mar 2012 11:43:35 +0100
Received: from DEMUEXC013.nsn-intra.net ([10.150.128.24]) by demuexc023.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 14 Mar 2012 11:43:35 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="windows-1255"
Content-Transfer-Encoding: quoted-printable
Subject: =?windows-1255?Q?RE=3A_=E4=F0=E3=E5=EF=3A_RE=3A_Last_Call=3A=3Cdraft-bett?= =?windows-1255?Q?s-itu-oam-ach-code-point-03=2Etxt=3E=28Allocationof=09an?= =?windows-1255?Q?_Associated_Channel_Code_Point_for_Use_byITU-T_Ethernetb?= =?windows-1255?Q?ased_OAM=29_to=09Informational_RFC?=
Date: Wed, 14 Mar 2012 11:43:33 +0100
Message-ID: <E4873516F3FC7547BCFE792C7D94039C016F6EE0@DEMUEXC013.nsn-intra.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: ?????: RE: LastCall:<draft-betts-itu-oam-ach-code-point-03.txt>(Allocationof	anAssociated Channel Code Point for Use byITU-T EthernetbasedOAM) to	Informational RFC
Thread-Index: Acz7K1zGcZQazOWqRhqgfGIuwk8+cwGGgb0gAAHeu6sAIDyGbA==
References: <8fab01cd014c$dea8f551$5e209f0a@nsnintra.net>
From: "Sprecher, Nurit (NSN - IL/Hod HaSharon)" <nurit.sprecher@nsn.com>
To: "Sprecher, Nurit (NSN - IL/Hod HaSharon)" <nurit.sprecher@nsn.com>, "Andrew G. Malis" <agmalis@gmail.com>, "ext Ross Callon" <rcallon@juniper.net>, <malcolm.betts@zte.com.cn>
X-OriginalArrivalTime: 14 Mar 2012 10:43:35.0137 (UTC) FILETIME=[4E8D8D10:01CD01CF]
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: 8768
X-purgate-ID: 151667::1331721818-000033AC-57819158/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: Wed, 14 Mar 2012 10:43:42 -0000

Malcolm,
As mentioned before, I cannot support the publication of the current =
version of draft-betts...it must be revised first to address the =
concerns I and others raised on the list.=20
Maybe you could clarify how the text in your draft can be improved to =
protect the use of the code point from future extensions beyond the =
purpose of the code point allocation?
Best regards,
Nurit=20

________________________________

=EE=E0=FA: ietf-bounces@ietf.org =E1=F9=ED Sprecher, Nurit (NSN - IL/Hod =
HaSharon)
=F0=F9=EC=E7: =E2 13/03/2012 20:09
=E0=EC: Andrew G. Malis; ext Ross Callon
=F2=E5=FA=F7 =EC=E9=E3=E9=F2=E4: ietf@ietf.org
=F0=E5=F9=E0: =E4=F0=E3=E5=EF: RE: Last =
Call:<draft-betts-itu-oam-ach-code-point-03.txt>(Allocationof an =
Associated Channel Code Point for Use byITU-T Ethernetbased OAM) to =
Informational RFC



Ross,
i am afraid that you missed the point. There will not be a final version =
since as written in draft-betts, all  ITU recommendations are subject to =
revisions, and the code point will also be used for future revisions of =
the document. New messages/protocols can be defined in future revisions =
of the recommendation and they will use the same code point that is =
allocated for the first version.
This is a real issue.
Regards,
Nurit
-----=E4=E5=E3=F2=E4 =EE=F7=E5=F8=E9=FA-----
=EE=E0=FA: ext Ross Callon
=F0=F9=EC=E7:  13/03/2012, 19:27
=E0=EC: Andrew G. Malis; Sprecher, Nurit (NSN - IL/Hod HaSharon)
=F2=E5=FA=F7: ietf@ietf.org
=F0=E5=F9=E0: RE: Last =
Call:<draft-betts-itu-oam-ach-code-point-03.txt>(Allocationof    an =
Associated Channel Code Point for Use byITU-T Ethernetbased OAM) to  =
Informational RFC
I agree that the allocation of a code point should be to a specific =
version of 8113.1, and specifically should be to the final version that =
is approved by the ITU-T (assuming that a final version of 8113.1 will =
be approved by the ITU-T). This would imply that =
draft-betts-itu-oam-ach-code-point should contain a normative reference =
to the final approved version of 8113.1.

Given normal IETF processes, this implies that the final RFC resulting =
from draft-betts-itu-oam-ach-code-point could be published as soon as =
the final version of 8113.1 is approved (with the understanding that =
there will be a small normal delay between "approved" and "published" =
which gives time for coordination). Given that the final version of =
8113.1 might need to reference the RFC resulting from =
draft-betts-itu-oam-ach-code-point, a bit of cooperation might be needed =
between editorial staff at the ITU and RFC editorial staff, but I don't =
see why this should be a problem (I am sure that they all have access to =
email).

Ross

-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of =
Andrew G. Malis
Sent: Monday, March 05, 2012 6:54 PM
To: Sprecher, Nurit (NSN - IL/Hod HaSharon)
Cc: ietf@ietf.org
Subject: Re: Last Call: =
<draft-betts-itu-oam-ach-code-point-03.txt>(Allocationof an Associated =
Channel Code Point for Use byITU-T Ethernetbased OAM) to Informational =
RFC

I would like to support Nurit's comments below. In particular, in the
past the ITU-T has expanded upon or changed the usage of IETF
codepoint allocations, in some cases incompatibly with its original
usage or definition. In the future, all codepoint allocations to the
ITU-T should be tied to one specific, dated revision of their
specification only. This is similar to the ITU-T's own processes, such
as section 2.2.1 of Rec. A.5, which requires a version number and/or
date for referenced outside documents in ITU-T recommendations.

Cheers,
Andy

On Thu, Mar 1, 2012 at 7:20 AM, Sprecher, Nurit (NSN - IL/Hod
HaSharon) <nurit.sprecher@nsn.com> wrote:
> Hi,
>
>
>
> I cannot support the publication of the document in its current =
version.
>
>
>
> I have the following concerns:
>
>
>
> .        It is indicated that the channel is intended to be used to =
carry
> Ethernet based OAM messages. It is not clear why there is a need for =
ACH.
> PWs can be used to transmit Ethernet OAM.
>
> If the intention is to use the channel for OAM messages for operating
> MPLS-TP based networks, the IETF *already* defined a solution for =
MPLS-TP
> OAM and I expect to see first a technical *justification* why a second
> solution is needed. In addition, I would expect to see *references to =
the
> arguments* raised in draft-sprecher-mpls-tp-oam-considerations.
>
>
>
> .        It is not clear what the maturity status of G.8113.1 is. It =
seems
> that the document was not approved by SG15 and the discussion was =
deferred
> to WTSA. This indicates that there is *no consensus* for the approval =
of
> G.8113.1. A code point should not be allocated before a =
consensus/decision
> is reached in the ITU-T and before the document is mature and =
approved. I do
> not think it is appropriate to allocate a code point and try to force =
a
> resolution in the ITU-T.
>
>
>
> .        I find a contradiction in the draft. In one place it is =
mentioned:
> "These Ethernet based OAM messages and procedures, address the OAM
> functional requirements defined in [RFC5860]. Other message types =
should not
> be carried behind this code point." In another place it is mentioned: =
"all
> ITU-T Recommendations are subject to revision. Therefore, the code =
point
> allocated by this document may be used for future versions of =
[G.8113.1].".
> The last statement opens the door for the definition of additional =
messages
> in G.8113.1 in the following versions, for example, for APS =
(supporting
> linear or ring protection mechanisms) and by this creates two =
solutions for
> other mechanisms as well.
>
>
>
> The use of the code point can go much beyond its original purpose and =
it
> will hide other messages....a code point should not be allocated at =
this
> point at all, but specifically not for unknown usage that may be =
defined in
> future versions of G.8113.1.
>
>
>
> Best regards,
>
> Nurit
>
>
>
>
>
>
>
>> -----Original Message-----
>
>> From: ietf-announce-bounces@ietf.org [mailto:ietf-announce-
>
>> bounces@ietf.org] On Behalf Of The IESG
>
>> Sent: 22 February 2012 15:13
>
>> To: IETF-Announce
>
>> Subject: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt>
>
> (Allocation of
>
> an
>
>> Associated Channel Code Point for Use by ITU-T Ethernet based OAM) to
>
>> Informational RFC
>
>>
>
>>
>
>> The IESG has received a request from an individual submitter to
>
> consider
>
>> the following document:
>
>> - 'Allocation of an Associated Channel Code Point for Use by ITU-T
>
>>    Ethernet based OAM'
>
>>   <draft-betts-itu-oam-ach-code-point-03.txt> as an 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-03-21. 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 assigns an Associated Channel Type code point for
>
>>    carrying Ethernet based Operations, Administration, and Management
>
>>    messages in the MPLS Generic Associated Channel (G-ACh).
>
>>
>
>> The file can be obtained via
>
>> http://datatracker.ietf.org/doc/draft-betts-itu-oam-ach-code-point/
>
>>
>
>> IESG discussion can be tracked via
>
>> http://datatracker.ietf.org/doc/draft-betts-itu-oam-ach-code-point/
>
>>
>
>>
>
>> No IPR declarations have been submitted directly on this I-D.
>
>> _______________________________________________
>
>> IETF-Announce mailing list
>
>> IETF-Announce@ietf.org
>
>> https://www.ietf.org/mailman/listinfo/ietf-announce
>
>
>
> _______________________________________________
>
> mpls mailing list
>
> mpls@ietf.org
>
> https://www.ietf.org/mailman/listinfo/mpls
>
> _______________________________________________
>
> Ietf mailing list
>
> Ietf@ietf.org
>
> https://www.ietf.org/mailman/listinfo/ietf
>
> _______________________________________________
>
> Ietf mailing list
>
> Ietf@ietf.org
>
> https://www.ietf.org/mailman/listinfo/ietf
>
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>
_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf



From turchanyi.geza@gmail.com  Wed Mar 14 03:51:21 2012
Return-Path: <turchanyi.geza@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4C1CD21F8776 for <ietf@ietfa.amsl.com>; Wed, 14 Mar 2012 03:51:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.297
X-Spam-Level: 
X-Spam-Status: No, score=-3.297 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, NORMAL_HTTP_TO_IP=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 KmEm9snnLuVj for <ietf@ietfa.amsl.com>; Wed, 14 Mar 2012 03:51:20 -0700 (PDT)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id 38DF821F8778 for <ietf@ietf.org>; Wed, 14 Mar 2012 03:51:20 -0700 (PDT)
Received: by ggmi1 with SMTP id i1so1872139ggm.31 for <ietf@ietf.org>; Wed, 14 Mar 2012 03:51:19 -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=dvjfhNmGtPTGQKkROyK5WCeY9ivhtQ7OJam2HvVDMnY=; b=MWdvgnJbX2bIaMqy1wUruAJ+KB5VxXB0Gt1lm82KbPn/oJ+omnRFJQLTfBUa54fL9X 08NH5TKMBB0EJL1m05nhPIALnVZDjlIkqeLY799OFK0rKwU9ByeDcMUj+xxU8tN3bQtx b1+usNmYmIU0gNL+NeZh4L3cdL/iMrFwd6rDU2zFTLunKsh2gVO1LKtylm6QWEdGyw0n rnU8JQkYtbIRUXPe9c4Tt8mCy6ZmcVHHu53mhxCLUu8m1Uhfc0ZwZEj78y9m6Ndvoyd6 PmO4P0GxUuStWZtxBvkn/DDxBHcCCLDjfx6CB1EQiqno1jpfy4gd6fNbQxjHhJgwy/7U t4Kg==
MIME-Version: 1.0
Received: by 10.224.184.1 with SMTP id ci1mr2331542qab.70.1331722279618; Wed, 14 Mar 2012 03:51:19 -0700 (PDT)
Received: by 10.229.135.65 with HTTP; Wed, 14 Mar 2012 03:51:19 -0700 (PDT)
In-Reply-To: <CAKFn1SEGpUSyTnM5kOFT9J=y1AbXDLxti7g-KGKk7dXFWyfNwg@mail.gmail.com>
References: <CAL9jLaZyPBDaGyom4Qrdt+TfzBONftH_Zxtjp1MfiH3tBLXejA@mail.gmail.com> <20120314074707.GZ16111@besserwisser.org> <CAKFn1SEGpUSyTnM5kOFT9J=y1AbXDLxti7g-KGKk7dXFWyfNwg@mail.gmail.com>
Date: Wed, 14 Mar 2012 11:51:19 +0100
Message-ID: <CAJfR-+OfTaXsr37x5-+svxFt1kZnfiyALFn+wU5BtoC9HwpZNA@mail.gmail.com>
Subject: Re: shared address space... a reality!
From: Turchanyi Geza <turchanyi.geza@gmail.com>
To: =?ISO-8859-1?Q?Roger_J=F8rgensen?= <rogerj@gmail.com>
Content-Type: multipart/alternative; boundary=20cf303b42fb6a8a4204bb31c196
Cc: =?ISO-8859-1?Q?M=E5ns_Nilsson?= <mansaxel@besserwisser.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, 14 Mar 2012 10:51:21 -0000

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

Hello,

This is really good news, however, I did not know it before.

Extending the reusable address space is a good idea, I think, however, the
scope of the address space should be well-defined.

I wrote a draft in 2007 and a Japonais group wrote a draft in 2008. The
similarity of the drafts included the extension of the reusable address
space by IANA, and both drafts explained how and why this space should be
used in the IPv4->IPv6 transition.

My draft had been lost as I changed job and email address (and nobody
explained me that this is a problem).

The Japanaise draft was discussed in the Internet area meeting in Dublin,
but then it was no room for continuing the discussion.

Probably we should continue it.

G=E9za
(one of the contributors of RFC1918)

2012/3/14 Roger J=F8rgensen <rogerj@gmail.com>

> On Wed, Mar 14, 2012 at 8:47 AM, M=E5ns Nilsson <mansaxel@besserwisser.or=
g>
> wrote:
> > On Wed, Mar 14, 2012 at 02:22:04AM -0400, Christopher Morrow wrote:
> >> NetRange:       100.64.0.0 - 100.127.255.255
> >> CIDR:           100.64.0.0/10
> >> OriginAS:
> >> NetName:        SHARED-ADDRESS-SPACE-RFCTBD-IANA-RESERVED
> >
> > GOOD.
> >
> > Now I can BOTH keep sticking my head in the sand AND get NEW RFC 1918
> > space to number my devices!
>
> This is really "good" news for some people, that already have address
> conflict within RFC1918 and don't want to get public address space :p
>
>
> --- Roger J ---
>
> >
> > Trailing edge WINS!
> >
> > Congrats, all you people who joined the ietf mailing list to get your
> > VOTE through. You can sign off now and continue non-contributing to the
> > developement of the future.
> >
> > --
> > /M=E5ns, pissed off.
>
>
>
> --
>
> Roger Jorgensen           |
> rogerj@gmail.com          | - IPv6 is The Key!
> http://www.jorgensen.no   | roger@jorgensen.no
>

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

Hello,<br><br>This is really good news, however, I did not know it before.<=
br><br>Extending the reusable address space is a good idea, I think, howeve=
r, the scope of the address space should be well-defined.<br><br>I wrote a =
draft in 2007 and a Japonais group wrote a draft in 2008. The similarity of=
 the drafts included the extension of the reusable address space by IANA, a=
nd both drafts explained how and why this space should be used in the IPv4-=
&gt;IPv6 transition.<br>

<br>My draft had been lost as I changed job and email address (and nobody e=
xplained me that this is a problem).<br><br>The Japanaise draft was discuss=
ed in the Internet area meeting in Dublin, but then it was no room for cont=
inuing the discussion.<br>
<br>Probably we should continue it.<br><br>G=E9za<br>(one of the contributo=
rs of RFC1918)<br><br><div class=3D"gmail_quote">
2012/3/14 Roger J=F8rgensen <span dir=3D"ltr">&lt;<a href=3D"mailto:rogerj@=
gmail.com" target=3D"_blank">rogerj@gmail.com</a>&gt;</span><br><blockquote=
 class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc soli=
d;padding-left:1ex">
<div>
On Wed, Mar 14, 2012 at 8:47 AM, M=E5ns Nilsson &lt;<a href=3D"mailto:mansa=
xel@besserwisser.org" target=3D"_blank">mansaxel@besserwisser.org</a>&gt; w=
rote:<br>
&gt; On Wed, Mar 14, 2012 at 02:22:04AM -0400, Christopher Morrow wrote:<br=
>
&gt;&gt; NetRange: =A0 =A0 =A0 100.64.0.0 - 100.127.255.255<br>
&gt;&gt; CIDR: =A0 =A0 =A0 =A0 =A0 <a href=3D"http://100.64.0.0/10" target=
=3D"_blank">100.64.0.0/10</a><br>
&gt;&gt; OriginAS:<br>
&gt;&gt; NetName: =A0 =A0 =A0 =A0SHARED-ADDRESS-SPACE-RFCTBD-IANA-RESERVED<=
br>
&gt;<br>
&gt; GOOD.<br>
&gt;<br>
&gt; Now I can BOTH keep sticking my head in the sand AND get NEW RFC 1918<=
br>
&gt; space to number my devices!<br>
<br>
</div>This is really &quot;good&quot; news for some people, that already ha=
ve address<br>
conflict within RFC1918 and don&#39;t want to get public address space :p<b=
r>
<br>
<br>
--- Roger J ---<br>
<div><div><br>
&gt;<br>
&gt; Trailing edge WINS!<br>
&gt;<br>
&gt; Congrats, all you people who joined the ietf mailing list to get your<=
br>
&gt; VOTE through. You can sign off now and continue non-contributing to th=
e<br>
&gt; developement of the future.<br>
&gt;<br>
&gt; --<br>
&gt; /M=E5ns, pissed off.<br>
<br>
<br>
<br>
</div></div><span><font color=3D"#888888">--<br>
<br>
Roger Jorgensen=A0 =A0 =A0 =A0 =A0=A0 |<br>
<a href=3D"mailto:rogerj@gmail.com" target=3D"_blank">rogerj@gmail.com</a>=
=A0 =A0 =A0 =A0 =A0 | - IPv6 is The Key!<br>
<a href=3D"http://www.jorgensen.no" target=3D"_blank">http://www.jorgensen.=
no</a>=A0=A0 | <a href=3D"mailto:roger@jorgensen.no" target=3D"_blank">roge=
r@jorgensen.no</a><br>
</font></span></blockquote></div><br>

--20cf303b42fb6a8a4204bb31c196--

From Rolf.Winter@neclab.eu  Wed Mar 14 04:39:22 2012
Return-Path: <Rolf.Winter@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 48C5621F86A4 for <ietf@ietfa.amsl.com>; Wed, 14 Mar 2012 04:39:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.581
X-Spam-Level: 
X-Spam-Status: No, score=-102.581 tagged_above=-999 required=5 tests=[AWL=0.018, 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 9e1a++E4FF30 for <ietf@ietfa.amsl.com>; Wed, 14 Mar 2012 04:39:21 -0700 (PDT)
Received: from mailer1.neclab.eu (mailer1.neclab.eu [195.37.70.40]) by ietfa.amsl.com (Postfix) with ESMTP id 3E39821F8692 for <ietf@ietf.org>; Wed, 14 Mar 2012 04:39:21 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailer1.neclab.eu (Postfix) with ESMTP id CCA851008C4; Wed, 14 Mar 2012 12:39:46 +0100 (CET)
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 7NtdGXVRWuhi; Wed, 14 Mar 2012 12:39:46 +0100 (CET)
Received: from METHONE.office.hd (unknown [192.168.24.54]) by mailer1.neclab.eu (Postfix) with ESMTP id B10EB1008BB; Wed, 14 Mar 2012 12:39:31 +0100 (CET)
Received: from Polydeuces.office.hd ([169.254.3.36]) by METHONE.office.hd ([192.168.24.54]) with mapi id 14.01.0323.003; Wed, 14 Mar 2012 12:38:23 +0100
From: Rolf Winter <Rolf.Winter@neclab.eu>
To: Russ Housley <housley@vigilsec.com>, "Sprecher, Nurit (NSN - IL/Hod HaSharon)" <nurit.sprecher@nsn.com>
Subject: RE: Last Call:<draft-betts-itu-oam-ach-code-point-03.txt> (Allocation	of anAssociated Channel Code Point for Use by	ITU-T Ethernet basedOAM) to Informational RFC
Thread-Topic: Last Call:<draft-betts-itu-oam-ach-code-point-03.txt> (Allocation	of anAssociated Channel Code Point for Use by	ITU-T Ethernet basedOAM) to Informational RFC
Thread-Index: AQHM9+JmSeDfktX6akC7+Kg8RkvkHpZWDBIAgBOqYUA=
Date: Wed, 14 Mar 2012 11:38:22 +0000
Message-ID: <791AD3077F94194BB2BDD13565B6295D25046517@Polydeuces.office.hd>
References: <20120222151252.32262.82157.idtracker@ietfa.amsl.com><03a301ccf174$ff953290$febf97b0$@olddog.co.uk><515703B08A3A064C9CC8C09ACCC710DC0631679E@XMB-RCD-103.cisco.com><C71DA9B1-A61F-4C5D-8DCE-3702271CBB6D@vigilsec.com><4F4FA70B.2030906@pi.nu><D0F60388-D852-4815-917A-B14BF40C64FB@vigilsec.com><BD60EA38ED03AF5A21868DF1@PST.JCK.COM> <4F4FC252.9010001@cisco.com> <444F9B86-84CD-4A21-BD02-067877052A0A@vigilsec.com> <E4873516F3FC7547BCFE792C7D94039C015D125D@DEMUEXC013.nsn-intra.net> <28D09181-4EAF-4770-963F-A57073D77AE7@vigilsec.com>
In-Reply-To: <28D09181-4EAF-4770-963F-A57073D77AE7@vigilsec.com>
Accept-Language: en-US, de-DE
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.7.0.200]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Mar 2012 11:39:22 -0000

Having thought about this for some time, I think I concur with Russ' reason=
ing and the allocation should be made.=20

NEC Europe Limited | Registered Office: NEC House, 1 Victoria Road, London =
W3 6BL | Registered in England 2832014=20


> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
> Russ Housley
> Sent: Freitag, 2. M=E4rz 2012 00:52
> To: Sprecher, Nurit (NSN - IL/Hod HaSharon)
> Cc: IETF
> Subject: Re: Last Call:<draft-betts-itu-oam-ach-code-point-03.txt>
> (Allocation of anAssociated Channel Code Point for Use by ITU-T
> Ethernet basedOAM) to Informational RFC
>=20
> Nurit:
>=20
> Some people are using the lack of a code point as the reason that the
> cannot support the ITU-T document.  My approach tells the ITU-T that a
> code point is available to them IFF they are able to reach consensus.
> The removes IETF from the discussion.  This creates a situation where
> G.8113.1 succeeded or fails based on the ITU-T members actions, with no
> finger pointing at the IETF.  This is completely a Layer 9
> consideration, and it has noting to do with the technical content of
> the document.
>=20
> Russ
>=20
>=20
> On Mar 1, 2012, at 2:33 PM, Sprecher, Nurit (NSN - IL/Hod HaSharon)
> wrote:
>=20
> > Russ,
> > I propose to simply re-discuss it when and IFF G.8113.1 is mature and
> > approved...
> > Best regards,
> > Nurit
> >
> >
> > -----Original Message-----
> > From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf
> > Of ext Russ Housley
> > Sent: Thursday, March 01, 2012 9:12 PM
> > To: IETF
> > Subject: Re: Last Call:<draft-betts-itu-oam-ach-code-point-03.txt>
> > (Allocation of anAssociated Channel Code Point for Use by ITU-T
> > Ethernet
> > basedOAM) to Informational RFC
> >
> >>>> Right now, there is no ITU-T approved document to reference.
> >>>> I am certainly not an expert on ITU-T process, but my
> understanding
> >>>> is that earliest that we could see an approved
> >>>> G.8113.1 is December 2012.  My point is that we don't want to
> >>>> assign a code point until the ITU-T approves their document.
> >>>> However, if we are willing to assign a code point to G.8113.1 once
> >>>> it is approved, then this would be an approach where the code
> point
> >>>> assignment would block on the approval of the normative reference.
> >>>>
> >>>> I like this approach from the political point of view.  With this
> >>>> approach the IETF tells the ITU-T that if and only if they are
> able
> >>>> to achieve consensus on G.8113.1, then a code point will be
> >>>> assigned.
> >>> FWIW, this seems entirely appropriate to me.  If we do it this way,
> >>> I think it is important to note --for the benefit of those more
> >>> historically involved with the ITU and others-- that we routinely
> >>> block our own documents on normative references to work that is
> >>> still in progress and, usually, do not do related code point
> >>> allocations until the blocking referenced documents are ready.
> Once
> >>> the present I-D is judged to be sufficiently ready, this approach
> >>> would therefore be IETF approval and a formal guarantee to the ITU
> >>> that a code point will be allocated if an when G.8113.1 is approved
> >>> and published, but not assignment of that code point until the
> >>> referenced base document is finished.
> >>>
> >>> Completely normal procedurally.
> >>>
> >> To be clear John our normal requirement would be that the technical
> >> community achieved consensus that the base document was ready. I
> have
> >> never seen ITU-T consensus on the contents of G.8113.1 at any
> meeting
> >> that I have observed. What in your view is the criteria for
> >> determining that  G.8113.1 has achieved consensus?
> >
> >
> > This is not an IETF problem, and I do not think that the IETF ought
> to
> > be discussing the internal workings of the ITU-T process.  The point
> > is to come up with a mechanism that allows the code point to be
> > assigned if and only if the ITU-T does come to a consensus by
> whatever
> > means is allowed by their own process.
> >
> > Russ
> > _______________________________________________
> > Ietf mailing list
> > Ietf@ietf.org
> > https://www.ietf.org/mailman/listinfo/ietf
>=20
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf

From daedulus@btconnect.com  Wed Mar 14 04:57:07 2012
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1085721E804C for <ietf@ietfa.amsl.com>; Wed, 14 Mar 2012 04:57:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.468
X-Spam-Level: 
X-Spam-Status: No, score=-1.468 tagged_above=-999 required=5 tests=[AWL=-1.131, BAD_ENC_HEADER=1.81, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, SARE_SUB_ENC_UTF8=0.152]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AZmM4Ez8zzG0 for <ietf@ietfa.amsl.com>; Wed, 14 Mar 2012 04:57:06 -0700 (PDT)
Received: from mail.btconnect.com (c2bthomr10.btconnect.com [213.123.20.128]) by ietfa.amsl.com (Postfix) with ESMTP id 91BE921E8013 for <ietf@ietf.org>; Wed, 14 Mar 2012 04:57:04 -0700 (PDT)
Received: from host86-151-41-215.range86-151.btcentralplus.com (HELO pc6) ([86.151.41.215]) by c2bthomr10.btconnect.com with SMTP id GSU31165; Wed, 14 Mar 2012 11:57:00 +0000 (GMT)
Message-ID: <050401cd01d1$10aa47c0$4001a8c0@gateway.2wire.net>
From: "t.petch" <daedulus@btconnect.com>
To: "Sprecher, Nurit \(NSN - IL/Hod HaSharon\)" <nurit.sprecher@nsn.com>, "ext Ross Callon" <rcallon@juniper.net>
References: <8fab01cd014c$dea8f551$5e209f0a@nsnintra.net>
Subject: =?utf-8?Q?Re:_=D7=94=D7=A0=D7=93=D7=95=D7=9F:_RE:_Last_Call:=3Cdraft-?= =?utf-8?Q?betts-itu-oam-ach-code-point-03.?= =?utf-8?Q?txt=3E=28Allocationof	an_Associated_?= =?utf-8?Q?Channel_Code_Point_for_Use_byITU?= =?utf-8?Q?-T_Ethernetbased_OAM=29_to	Informa?= =?utf-8?Q?tional_RFC?=
Date: Wed, 14 Mar 2012 11:56:00 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Mirapoint-IP-Reputation: reputation=Fair-1, source=Queried, refid=tid=0001.0A0B0301.4F60878B.0170, actions=tag
X-Junkmail-Premium-Raw: score=8/50, refid=2.7.2:2012.3.14.111220:17:8.129, ip=86.151.41.215, rules=__HAS_MSGID, __OUTLOOK_MSGID_1, __SANE_MSGID, __TO_MALFORMED_2, __SUBJ_HIGHBIT, __BOUNCE_CHALLENGE_SUBJ, __BOUNCE_NDR_SUBJ_EXEMPT, __MIME_VERSION, __CT, __CT_TEXT_PLAIN, __CTE, __HAS_X_PRIORITY, __HAS_MSMAIL_PRI, __HAS_X_MAILER, USER_AGENT_OE, __OUTLOOK_MUA_1, __USER_AGENT_MS_GENERIC, __UTF8_SUBJ, __ANY_URI, __FRAUD_BODY_WEBMAIL, __HIGHBITS, __CP_URI_IN_BODY, SUPERLONG_LINE, __MIME_TEXT_ONLY, RDNS_GENERIC_POOLED, HTML_00_01, HTML_00_10, RDNS_SUSP_GENERIC, __OUTLOOK_MUA, RDNS_SUSP, __FRAUD_WEBMAIL
X-Junkmail-Status: score=10/50, host=c2bthomr10.btconnect.com
X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A0B0202.4F60878C.00C0,ss=1,re=0.000,fgs=0, ip=0.0.0.0, so=2011-07-25 19:15:43, dmn=2011-05-27 18:58:46, mode=multiengine
X-Junkmail-IWF: false
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Mar 2012 11:57:07 -0000

----- Original Message -----
From: "Sprecher, Nurit (NSN - IL/Hod HaSharon)" <nurit.sprecher@nsn.com>
To: "Andrew G. Malis" <agmalis@gmail.com>; "ext Ross Callon"
<rcallon@juniper.net>
Cc: <ietf@ietf.org>
Sent: Tuesday, March 13, 2012 8:09 PM
Subject: הנדון: RE: Last
Call:<draft-betts-itu-oam-ach-code-point-03.txt>(Allocationof an Associated
Channel Code Point for Use byITU-T Ethernetbased OAM) to Informational RFC


Ross,
i am afraid that you missed the point. There will not be a final version since
as written in draft-betts, all  ITU recommendations are subject to revisions,
and the code point will also be used for future revisions of the document. New
messages/protocols can be defined in future revisions of the recommendation and
they will use the same code point that is allocated for the first version.
This is a real issue.
Regards,
Nurit
-----הודעה מקורית-----
מאת: ext Ross Callon
נשלח:  13/03/2012, 19:27
אל: Andrew G. Malis; Sprecher, Nurit (NSN - IL/Hod HaSharon)
עותק: ietf@ietf.org
נושא: RE: Last Call:<draft-betts-itu-oam-ach-code-point-03.txt>(Allocationof an
Associated Channel Code Point for Use byITU-T Ethernetbased OAM) to
Informational RFC
I agree that the allocation of a code point should be to a specific version of
8113.1,

<tp>
Why?

I can understand a new code point being required if there is a new and backwards
incompatible format for the messages, but if the messages are extended in a
forwards compatible manner, adding new TLV for example, or a new format of
IF_ID, then why should we burn a new code point?

Would you say that we should have a dozen different port numbers for HTTP to
reflect its evolution over time?  If not, why not?

Demanding that the ITU-T come back to us for a new round of negotiation when it
is technically unnecessary seems to be placing an unnecessary barrier between
the two SDOs.

Tom Petch

and specifically should be to the final version that is approved by the ITU-T
(assuming that a final version of 8113.1 will be approved by the ITU-T). This
would imply that draft-betts-itu-oam-ach-code-point should contain a normative
reference to the final approved version of 8113.1.

Given normal IETF processes, this implies that the final RFC resulting from
draft-betts-itu-oam-ach-code-point could be published as soon as the final
version of 8113.1 is approved (with the understanding that there will be a small
normal delay between "approved" and "published" which gives time for
coordination). Given that the final version of 8113.1 might need to reference
the RFC resulting from draft-betts-itu-oam-ach-code-point, a bit of cooperation
might be needed between editorial staff at the ITU and RFC editorial staff, but
I don't see why this should be a problem (I am sure that they all have access to
email).

Ross

-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of Andrew
G. Malis
Sent: Monday, March 05, 2012 6:54 PM
To: Sprecher, Nurit (NSN - IL/Hod HaSharon)
Cc: ietf@ietf.org
Subject: Re: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt>(Allocationof
an Associated Channel Code Point for Use byITU-T Ethernetbased OAM) to
Informational RFC

I would like to support Nurit's comments below. In particular, in the
past the ITU-T has expanded upon or changed the usage of IETF
codepoint allocations, in some cases incompatibly with its original
usage or definition. In the future, all codepoint allocations to the
ITU-T should be tied to one specific, dated revision of their
specification only. This is similar to the ITU-T's own processes, such
as section 2.2.1 of Rec. A.5, which requires a version number and/or
date for referenced outside documents in ITU-T recommendations.

Cheers,
Andy

On Thu, Mar 1, 2012 at 7:20 AM, Sprecher, Nurit (NSN - IL/Hod
HaSharon) <nurit.sprecher@nsn.com> wrote:
> Hi,
>
>
>
> I cannot support the publication of the document in its current version.
>
>
>
> I have the following concerns:
>
>
>
> .        It is indicated that the channel is intended to be used to carry
> Ethernet based OAM messages. It is not clear why there is a need for ACH.
> PWs can be used to transmit Ethernet OAM.
>
> If the intention is to use the channel for OAM messages for operating
> MPLS-TP based networks, the IETF *already* defined a solution for MPLS-TP
> OAM and I expect to see first a technical *justification* why a second
> solution is needed. In addition, I would expect to see *references to the
> arguments* raised in draft-sprecher-mpls-tp-oam-considerations.
>
>
>
> .        It is not clear what the maturity status of G.8113.1 is. It seems
> that the document was not approved by SG15 and the discussion was deferred
> to WTSA. This indicates that there is *no consensus* for the approval of
> G.8113.1. A code point should not be allocated before a consensus/decision
> is reached in the ITU-T and before the document is mature and approved. I do
> not think it is appropriate to allocate a code point and try to force a
> resolution in the ITU-T.
>
>
>
> .        I find a contradiction in the draft. In one place it is mentioned:
> "These Ethernet based OAM messages and procedures, address the OAM
> functional requirements defined in [RFC5860]. Other message types should not
> be carried behind this code point." In another place it is mentioned: "all
> ITU-T Recommendations are subject to revision. Therefore, the code point
> allocated by this document may be used for future versions of [G.8113.1].".
> The last statement opens the door for the definition of additional messages
> in G.8113.1 in the following versions, for example, for APS (supporting
> linear or ring protection mechanisms) and by this creates two solutions for
> other mechanisms as well.
>
>
>
> The use of the code point can go much beyond its original purpose and it
> will hide other messages....a code point should not be allocated at this
> point at all, but specifically not for unknown usage that may be defined in
> future versions of G.8113.1.
>
>
>
> Best regards,
>
> Nurit
>
>
>
>
>
>
>
>> -----Original Message-----
>
>> From: ietf-announce-bounces@ietf.org [mailto:ietf-announce-
>
>> bounces@ietf.org] On Behalf Of The IESG
>
>> Sent: 22 February 2012 15:13
>
>> To: IETF-Announce
>
>> Subject: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt>
>
> (Allocation of
>
> an
>
>> Associated Channel Code Point for Use by ITU-T Ethernet based OAM) to
>
>> Informational RFC
>
>>
>
>>
>
>> The IESG has received a request from an individual submitter to
>
> consider
>
>> the following document:
>
>> - 'Allocation of an Associated Channel Code Point for Use by ITU-T
>
>>    Ethernet based OAM'
>
>>   <draft-betts-itu-oam-ach-code-point-03.txt> as an 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-03-21. 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 assigns an Associated Channel Type code point for
>
>>    carrying Ethernet based Operations, Administration, and Management
>
>>    messages in the MPLS Generic Associated Channel (G-ACh).
>
>>
>
>> The file can be obtained via
>
>> http://datatracker.ietf.org/doc/draft-betts-itu-oam-ach-code-point/
>
>>
>
>> IESG discussion can be tracked via
>
>> http://datatracker.ietf.org/doc/draft-betts-itu-oam-ach-code-point/
>
>>
>
>>
>
>> No IPR declarations have been submitted directly on this I-D.
>
>> _______________________________________________
>
>> IETF-Announce mailing list
>
>> IETF-Announce@ietf.org
>
>> https://www.ietf.org/mailman/listinfo/ietf-announce
>
>
>
> _______________________________________________
>
> mpls mailing list
>
> mpls@ietf.org
>
> https://www.ietf.org/mailman/listinfo/mpls
>
> _______________________________________________
>
> Ietf mailing list
>
> Ietf@ietf.org
>
> https://www.ietf.org/mailman/listinfo/ietf
>
> _______________________________________________
>
> Ietf mailing list
>
> Ietf@ietf.org
>
> https://www.ietf.org/mailman/listinfo/ietf
>
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>
_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf



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


> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>


From jouni.nospam@gmail.com  Wed Mar 14 05:49:41 2012
Return-Path: <jouni.nospam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8B15021E807D; Wed, 14 Mar 2012 05:49:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.435
X-Spam-Level: 
X-Spam-Status: No, score=-3.435 tagged_above=-999 required=5 tests=[AWL=0.164,  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 PgsAXwAgv7FI; Wed, 14 Mar 2012 05:49:40 -0700 (PDT)
Received: from mail-lpp01m010-f44.google.com (mail-lpp01m010-f44.google.com [209.85.215.44]) by ietfa.amsl.com (Postfix) with ESMTP id 2A0F521E807C; Wed, 14 Mar 2012 05:49:39 -0700 (PDT)
Received: by lagj5 with SMTP id j5so1657512lag.31 for <multiple recipients>; Wed, 14 Mar 2012 05:49:39 -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=EVzmxVUNsGaJxSBR7QnKsCS9zkOi3FPAt0D175K8pXE=; b=EheFIy27lQMyE96jiLGShyEAO+45M/NdC/O7TkmJ9VHH/M/1tec6P/DxuwWaldJqOs Aixp5elYgANIyUuvoO0cek6jMfKJLg8HbGxG+iKRqKapeabpHMslgnmUHaeTGnpdhOnu F9Lq5ZLDvh+mGOYG1wcbfojt0u4cmgmOUTInXS7A6LNurki2yPXs2v+sdnqXfUublimC aVRg+VA2xtYwJILwt3ofDuIsE2wnYLHcSzPa22ZOYjBtYPOlCDFQDnb5hG8xb/omZepO hL+tIc90aU8wt5xLDlEFEvVXiPO+kTU9lXHRDVjEoXbofUOKtwuTcsNtXo3Vx2Ohxc91 BaNA==
Received: by 10.112.23.135 with SMTP id m7mr908291lbf.46.1331729379139; Wed, 14 Mar 2012 05:49:39 -0700 (PDT)
Received: from a88-114-7-204.elisa-laajakaista.fi (a88-114-7-204.elisa-laajakaista.fi. [88.114.7.204]) by mx.google.com with ESMTPS id u4sm3550050lad.5.2012.03.14.05.49.37 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 14 Mar 2012 05:49:37 -0700 (PDT)
Subject: Re: GenART last call review of draft-ietf-behave-nat64-learn-analysis-03
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=windows-1252
From: jouni korhonen <jouni.nospam@gmail.com>
In-Reply-To: <4f5f2ebe.0755b40a.4d27.257b@mx.google.com>
Date: Wed, 14 Mar 2012 14:49:35 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <EC918252-D6C6-4250-9761-6865E2A15774@gmail.com>
References: <4f5f2ebe.0755b40a.4d27.257b@mx.google.com>
To: Roni Even <ron.even.tlv@gmail.com>
X-Mailer: Apple Mail (2.1084)
Cc: gen-art@ietf.org, draft-ietf-behave-nat64-learn-analysis.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: Wed, 14 Mar 2012 12:49:41 -0000

Roni,

Thanks for the review. We'll take care of the editorials.

- Jouni

On Mar 13, 2012, at 1:24 PM, Roni Even 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
> =20
>=20
> Please resolve these comments along with any other Last Call comments =
you may receive.
>=20
> =20
> Document: draft-ietf-behave-nat64-learn-analysis-03
> Reviewer: Roni Even
> Review Date:2012=963=9613
> IETF LC End Date: 2012=963=9622
> IESG Telechat date:
> =20
> Summary: This draft is ready for publication as an Informational RFC.
> =20
> Major issues:
> =20
> Minor issues:
> =20
> Nits/editorial comments:
> =20
> Section 5.1.1 third paragraph change to  =93provided by some=94
> =20
>=20


From lihan@chinamobile.com  Wed Mar 14 06:13:33 2012
Return-Path: <lihan@chinamobile.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F241721F8703 for <ietf@ietfa.amsl.com>; Wed, 14 Mar 2012 06:13:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.317
X-Spam-Level: **
X-Spam-Status: No, score=2.317 tagged_above=-999 required=5 tests=[AWL=2.694,  BAYES_00=-2.599, RELAY_IS_221=2.222]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vaZ3vsjuRgAu for <ietf@ietfa.amsl.com>; Wed, 14 Mar 2012 06:13:32 -0700 (PDT)
Received: from imss.chinamobile.com (imss.chinamobile.com [221.130.253.135]) by ietfa.amsl.com (Postfix) with ESMTP id 5D24421F86F4 for <ietf@ietf.org>; Wed, 14 Mar 2012 06:13:29 -0700 (PDT)
Received: from imss.chinamobile.com (localhost [127.0.0.1]) by localhost.chinamobile.com (Postfix) with ESMTP id CC679E597 for <ietf@ietf.org>; Wed, 14 Mar 2012 21:13:24 +0800 (CST)
Received: from mail.chinamobile.com (unknown [10.1.28.22]) by imss.chinamobile.com (Postfix) with ESMTP id C3974E4AA for <ietf@ietf.org>; Wed, 14 Mar 2012 21:13:22 +0800 (CST)
Received: from lihan ([10.1.5.3]) by mail.chinamobile.com (Lotus Domino Release 6.5.6) with ESMTP id 2012031421131934-21994 ; Wed, 14 Mar 2012 21:13:19 +0800 
From: "lihan" <lihan@chinamobile.com>
To: <ietf@ietf.org>
Subject: re: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt>(Allocation	of an	Associated Channel Code Point for Use byITU-T Ethernet based OAM) to	Informational RFC
Date: Wed, 14 Mar 2012 21:13:17 +0800
Message-ID: <1184A97B0E4049B9916ADF47D77F738B@lihan>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 11
Thread-Index: Ac0Btpk5/5WIJlLgQKKxfJNWvckKpgALFCCwAABEDbA=
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157
X-MIMETrack: Itemize by SMTP Server on jtgsml01/servers/cmcc(Release 6.5.6|March 06, 2007) at 2012-03-14 21:13:19, Serialize by Router on jtgsml01/servers/cmcc(Release 6.5.6|March 06, 2007) at 2012-03-14 21:13:24, Serialize complete at 2012-03-14 21:13:24
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"
X-TM-AS-Product-Ver: IMSS-7.0.0.8231-6.8.0.1017-18772.007
X-TM-AS-Result: No--24.845-7.0-31-10
X-imss-scan-details: No--24.845-7.0-31-10;No--24.845-7.0-31-10
X-TM-AS-User-Approved-Sender: No;No
X-TM-AS-User-Blocked-Sender: No;No
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Mar 2012 13:13:33 -0000

Support!

Best regards,

		Han Li
 
********************************************************************
Han Li, Ph.D 
China Mobile Research Institute
No.32 Xuanwumen west street,Xicheng District, Beijing 100053, China 
Fax: +86 10 63135198 
MOBILE: 13501093385 
********************************************************************


> -----Original Message-----
> From: ietf-announce-bounces@ietf.org [mailto:ietf-announce-
> bounces@ietf.org] On Behalf Of The IESG
> Sent: 22 February 2012 15:13
> To: IETF-Announce
> Subject: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt>
(Allocation of
an
> Associated Channel Code Point for Use by ITU-T Ethernet based OAM) to
> Informational RFC
>
>
> The IESG has received a request from an individual submitter to
consider
> the following document:
> - 'Allocation of an Associated Channel Code Point for Use by ITU-T
>    Ethernet based OAM'
>   <draft-betts-itu-oam-ach-code-point-03.txt> as an 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-03-21. 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 assigns an Associated Channel Type code point for
>    carrying Ethernet based Operations, Administration, and Management
>    messages in the MPLS Generic Associated Channel (G-ACh).
>
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-betts-itu-oam-ach-code-point/
>
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-betts-itu-oam-ach-code-point/
>
>
> No IPR declarations have been submitted directly on this I-D.
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-announce

_______________________________________________
pwe3 mailing list
pwe3@ietf.org
https://www.ietf.org/mailman/listinfo/pwe3
_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf

                                                            
                                                            
                                                            





From fangyuli1999@gmail.com  Wed Mar 14 06:36:30 2012
Return-Path: <fangyuli1999@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 029DB21F8764 for <ietf@ietfa.amsl.com>; Wed, 14 Mar 2012 06:36:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.246
X-Spam-Level: 
X-Spam-Status: No, score=-3.246 tagged_above=-999 required=5 tests=[AWL=0.352,  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 oV55ymJMWX3U for <ietf@ietfa.amsl.com>; Wed, 14 Mar 2012 06:36:29 -0700 (PDT)
Received: from mail-gy0-f194.google.com (mail-gy0-f194.google.com [209.85.160.194]) by ietfa.amsl.com (Postfix) with ESMTP id 07AEB21F8755 for <ietf@ietf.org>; Wed, 14 Mar 2012 06:36:28 -0700 (PDT)
Received: by ghbf20 with SMTP id f20so440620ghb.1 for <ietf@ietf.org>; Wed, 14 Mar 2012 06:36:28 -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=l7y2oDmsGxKZMJmHiEEXFjYbCHn6JGZexOPE1BQNASI=; b=RMHci9m4P31m2duC7JOx/2TPCfKhCv9ozq/Qir5CCfbsy1xNBymUWQrXq9snw17GSR V7n2s+4niLB2QDCA0FJlAL4J/I2qJwhYt1ZMHKpzkoznYFkiAwQWGSUSXYF9MtN5I8Dx wOwe5+t+RF7mM/fzajqn6PX20SV8mXm4aShmWHqDTlxRlzvqEfPPbX0GYsx0aCuu2v9r 7xWFxtymxCgC8yfQtf/eVgA5L5l/6eDUq8A5nTMdbgIaEATdM3IRPY1egfTgJ6svUGW6 B6qeGJ5k52ha18LbUUDI0iEqi64JbYoJY3KSHg1oz7DNHio7Pl0N8qKiw76Df/IlPlpg GepQ==
MIME-Version: 1.0
Received: by 10.60.28.229 with SMTP id e5mr3317127oeh.63.1331732188486; Wed, 14 Mar 2012 06:36:28 -0700 (PDT)
Received: by 10.182.199.105 with HTTP; Wed, 14 Mar 2012 06:36:28 -0700 (PDT)
Date: Wed, 14 Mar 2012 21:36:28 +0800
Message-ID: <CAAHpaZ=JrKVKHZ0xkK-nszFDf-ttVNoi1p9iZiWa93vKuiNxZA@mail.gmail.com>
Subject: RE: Last Call:<draft-betts-itu-oam-ach-code-point-03.txt>(Allocation of an Associated Channel Code Point for Use by ITU-T Ethernet based OAM) to Informational RFC
From: Fangyu Li <fangyuli1999@gmail.com>
To: ietf@ietf.org
Content-Type: multipart/alternative; boundary=e89a8fb2056407dc7604bb341002
Cc: lifang@catr.cn
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Mar 2012 13:36:30 -0000

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

I support the allocation of an ACH codepoint to G.8113.1.

For G.8113.1 had reached the technical and industry maturity to be assigned
a code point, the codepoint allocation from IETF should allow the ITU-T to
progress refinements to G.8113.1 such that it could satisfy all the
functional requirements defined in RFC 5860.

-----????? ??????-----
???: ext Ross Callon
????:  13/03/2012, 19:27
??: Andrew G. Malis; Sprecher, Nurit (NSN - IL/Hod HaSharon)
????: ietf@ietf.org
????: RE: Last
Call:<draft-betts-itu-oam-ach-code-point-03.txt>(Allocationof    an
Associated Channel Code Point for Use byITU-T Ethernetbased OAM) to
Informational RFC
I agree that the allocation of a code point should be to a specific version
of 8113.1, and specifically should be to the final version that is approved
by the ITU-T (assuming that a final version of 8113.1 will be approved by
the ITU-T). This would imply that draft-betts-itu-oam-ach-code-point should
contain a normative reference to the final approved version of 8113.1.
Given normal IETF processes, this implies that the final RFC resulting from
draft-betts-itu-oam-ach-code-point could be published as soon as the final
version of 8113.1 is approved (with the understanding that there will be a
small normal delay between "approved" and "published" which gives time for
coordination). Given that the final version of 8113.1 might need to
reference the RFC resulting from draft-betts-itu-oam-ach-code-point, a bit
of cooperation might be needed between editorial staff at the ITU and RFC
editorial staff, but I don't see why this should be a problem (I am sure
that they all have access to email).
Ross

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

<div><span style lang=3D"EN-GB">I support the allocation of an ACH codepoin=
t to G.8113.1. </span></div>
<div><span style lang=3D"EN-GB"></span>=A0</div>
<div><span style lang=3D"EN-GB">For G.8113.1 had reached the technical and =
industry maturity to be assigned a code point, <span style lang=3D"EN-GB">t=
he codepoint allocation from IETF should allow the ITU-T to progress refine=
ments to G.8113.1 such that it could satisfy all the functional requirement=
s defined in RFC 5860. </span></span></div>

<div><span style lang=3D"EN-GB"><span style lang=3D"EN-GB"></span></span>=
=A0</div>
<div><span style lang=3D"EN-GB"><span style lang=3D"EN-GB">-----????? ?????=
?-----<br>???: ext Ross Callon<br>????:=A0 13/03/2012, 19:27<br>??: Andrew =
G. Malis; Sprecher, Nurit (NSN - IL/Hod HaSharon)<br>????: <a href=3D"mailt=
o:ietf@ietf.org">ietf@ietf.org</a><br>
????: RE: Last Call:&lt;draft-betts-itu-oam-ach-code-point-03.txt&gt;(Alloc=
ationof=A0=A0=A0 an Associated Channel Code Point for Use byITU-T Ethernetb=
ased OAM) to=A0 Informational RFC<br>I agree that the allocation of a code =
point should be to a specific version of 8113.1, and specifically should be=
 to the final version that is approved by the ITU-T (assuming that a final =
version of 8113.1 will be approved by the ITU-T). This would imply that dra=
ft-betts-itu-oam-ach-code-point should contain a normative reference to the=
 final approved version of 8113.1.</span></span></div>

<div><span style lang=3D"EN-GB"><span style lang=3D"EN-GB">Given normal IET=
F processes, this implies that the final RFC resulting from draft-betts-itu=
-oam-ach-code-point could be published as soon as the final version of 8113=
.1 is approved (with the understanding that there will be a small normal de=
lay between &quot;approved&quot; and &quot;published&quot; which gives time=
 for coordination). Given that the final version of 8113.1 might need to re=
ference the RFC resulting from draft-betts-itu-oam-ach-code-point, a bit of=
 cooperation might be needed between editorial staff at the ITU and RFC edi=
torial staff, but I don&#39;t see why this should be a problem (I am sure t=
hat they all have access to email).</span></span></div>

<div><span style lang=3D"EN-GB"><span style lang=3D"EN-GB">Ross</span></spa=
n></div>
<div>=A0</div>

--e89a8fb2056407dc7604bb341002--

From nurit.sprecher@nsn.com  Wed Mar 14 06:42:36 2012
Return-Path: <nurit.sprecher@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 DC3EE21F87BF for <ietf@ietfa.amsl.com>; Wed, 14 Mar 2012 06:42:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.528
X-Spam-Level: 
X-Spam-Status: No, score=-6.528 tagged_above=-999 required=5 tests=[AWL=0.070,  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 xRaiDF7fsc9Y for <ietf@ietfa.amsl.com>; Wed, 14 Mar 2012 06:42:34 -0700 (PDT)
Received: from demumfd001.nsn-inter.net (demumfd001.nsn-inter.net [93.183.12.32]) by ietfa.amsl.com (Postfix) with ESMTP id 68CD621F8789 for <ietf@ietf.org>; Wed, 14 Mar 2012 06:42:34 -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 q2EDg3LU020356 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 14 Mar 2012 14:42:03 +0100
Received: from DEMUEXC048.nsn-intra.net ([10.159.32.94]) by demuprx017.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id q2EDftEm007811; Wed, 14 Mar 2012 14:42:03 +0100
Received: from DEMUEXC013.nsn-intra.net ([10.150.128.24]) by DEMUEXC048.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 14 Mar 2012 14:41:57 +0100
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_01CD01E8.399385C9"
Subject: RE: Last Call:<draft-betts-itu-oam-ach-code-point-03.txt>(Allocationof an Associated Channel Code Point for Use by ITU-T Ethernet basedOAM) to Informational RFC
Date: Wed, 14 Mar 2012 14:41:55 +0100
Message-ID: <E4873516F3FC7547BCFE792C7D94039C016C533A@DEMUEXC013.nsn-intra.net>
In-Reply-To: <CAAHpaZ=JrKVKHZ0xkK-nszFDf-ttVNoi1p9iZiWa93vKuiNxZA@mail.gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Last Call:<draft-betts-itu-oam-ach-code-point-03.txt>(Allocationof an Associated Channel Code Point for Use by ITU-T Ethernet basedOAM) to Informational RFC
Thread-Index: Ac0B54TlEUFprJ3LQlWEWiBHir0jLwAADV2Q
References: <CAAHpaZ=JrKVKHZ0xkK-nszFDf-ttVNoi1p9iZiWa93vKuiNxZA@mail.gmail.com>
From: "Sprecher, Nurit (NSN - IL/Hod HaSharon)" <nurit.sprecher@nsn.com>
To: "ext Fangyu Li" <fangyuli1999@gmail.com>, <ietf@ietf.org>
X-OriginalArrivalTime: 14 Mar 2012 13:41:57.0923 (UTC) FILETIME=[39E91730:01CD01E8]
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: 9143
X-purgate-ID: 151667::1331732523-000044A2-C5D6E451/0-0/0-0
Cc: lifang@catr.cn
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Mar 2012 13:42:37 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CD01E8.399385C9
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi,

Which version of G.8113.1 has reached the technical and industry
maturity? Is it the one that was submitted to WTSA or is it the one that
the ITU worked on the December meeting? Or maybe it is the same document
that the ITU worked on in the December meeting and sent to WTSA? Can you
please clarify the point?

You say that " the codepoint allocation from IETF should allow the ITU-T
to progress refinements to G.8113.1 such that it could satisfy all the
functional requirements defined in RFC 5860" - does it meant that the
matured version does not fully satisfy the requirements presented in RFC
5860?

Best regards,

Nurit

=20

From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
ext Fangyu Li
Sent: Wednesday, March 14, 2012 3:36 PM
To: ietf@ietf.org
Cc: lifang@catr.cn
Subject: RE: Last
Call:<draft-betts-itu-oam-ach-code-point-03.txt>(Allocationof an
Associated Channel Code Point for Use by ITU-T Ethernet basedOAM) to
Informational RFC

=20

I support the allocation of an ACH codepoint to G.8113.1.=20

=20

For G.8113.1 had reached the technical and industry maturity to be
assigned a code point, the codepoint allocation from IETF should allow
the ITU-T to progress refinements to G.8113.1 such that it could satisfy
all the functional requirements defined in RFC 5860.=20

=20

-----????? ??????-----
???: ext Ross Callon
????:  13/03/2012, 19:27
??: Andrew G. Malis; Sprecher, Nurit (NSN - IL/Hod HaSharon)
????: ietf@ietf.org
????: RE: Last
Call:<draft-betts-itu-oam-ach-code-point-03.txt>(Allocationof    an
Associated Channel Code Point for Use byITU-T Ethernetbased OAM) to
Informational RFC
I agree that the allocation of a code point should be to a specific
version of 8113.1, and specifically should be to the final version that
is approved by the ITU-T (assuming that a final version of 8113.1 will
be approved by the ITU-T). This would imply that
draft-betts-itu-oam-ach-code-point should contain a normative reference
to the final approved version of 8113.1.

Given normal IETF processes, this implies that the final RFC resulting
from draft-betts-itu-oam-ach-code-point could be published as soon as
the final version of 8113.1 is approved (with the understanding that
there will be a small normal delay between "approved" and "published"
which gives time for coordination). Given that the final version of
8113.1 might need to reference the RFC resulting from
draft-betts-itu-oam-ach-code-point, a bit of cooperation might be needed
between editorial staff at the ITU and RFC editorial staff, but I don't
see why this should be a problem (I am sure that they all have access to
email).

Ross

=20


------_=_NextPart_001_01CD01E8.399385C9
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:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin: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:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.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:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Hi,<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Which version of G.8113.1 </span>has reached the technical and =
industry maturity<span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>? Is it the one that was submitted to WTSA or is it the one that the =
ITU worked on the December meeting? Or maybe it is the same document =
that the ITU worked on in the December meeting and sent to WTSA? Can you =
please clarify the point?<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>You say that &quot;</span> the codepoint allocation from IETF should =
allow the ITU-T to progress refinements to G.8113.1 such that it could =
satisfy all the functional requirements defined in RFC 5860&quot; =
&#8211; does it meant that the matured version does not fully satisfy =
the requirements presented in RFC 5860?<o:p></o:p></p><p =
class=3DMsoNormal>Best regards,<o:p></o:p></p><p =
class=3DMsoNormal>Nurit<span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><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-bounces@ietf.org [mailto:ietf-bounces@ietf.org] <b>On Behalf Of =
</b>ext Fangyu Li<br><b>Sent:</b> Wednesday, March 14, 2012 3:36 =
PM<br><b>To:</b> ietf@ietf.org<br><b>Cc:</b> =
lifang@catr.cn<br><b>Subject:</b> RE: Last =
Call:&lt;draft-betts-itu-oam-ach-code-point-03.txt&gt;(Allocationof an =
Associated Channel Code Point for Use by ITU-T Ethernet basedOAM) to =
Informational RFC<o:p></o:p></span></p></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><p class=3DMsoNormal>I =
support the allocation of an ACH codepoint to G.8113.1. =
<o:p></o:p></p></div><div><p =
class=3DMsoNormal>&nbsp;<o:p></o:p></p></div><div><p =
class=3DMsoNormal>For G.8113.1 had reached the technical and industry =
maturity to be assigned a code point, the codepoint allocation from IETF =
should allow the ITU-T to progress refinements to G.8113.1 such that it =
could satisfy all the functional requirements defined in RFC 5860. =
<o:p></o:p></p></div><div><p =
class=3DMsoNormal>&nbsp;<o:p></o:p></p></div><div><p =
class=3DMsoNormal>-----????? ??????-----<br>???: ext Ross =
Callon<br>????:&nbsp; 13/03/2012, 19:27<br>??: Andrew G. Malis; =
Sprecher, Nurit (NSN - IL/Hod HaSharon)<br>????: <a =
href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a><br>????: RE: Last =
Call:&lt;draft-betts-itu-oam-ach-code-point-03.txt&gt;(Allocationof&nbsp;=
&nbsp;&nbsp; an Associated Channel Code Point for Use byITU-T =
Ethernetbased OAM) to&nbsp; Informational RFC<br>I agree that the =
allocation of a code point should be to a specific version of 8113.1, =
and specifically should be to the final version that is approved by the =
ITU-T (assuming that a final version of 8113.1 will be approved by the =
ITU-T). This would imply that draft-betts-itu-oam-ach-code-point should =
contain a normative reference to the final approved version of =
8113.1.<o:p></o:p></p></div><div><p class=3DMsoNormal>Given normal IETF =
processes, this implies that the final RFC resulting from =
draft-betts-itu-oam-ach-code-point could be published as soon as the =
final version of 8113.1 is approved (with the understanding that there =
will be a small normal delay between &quot;approved&quot; and =
&quot;published&quot; which gives time for coordination). Given that the =
final version of 8113.1 might need to reference the RFC resulting from =
draft-betts-itu-oam-ach-code-point, a bit of cooperation might be needed =
between editorial staff at the ITU and RFC editorial staff, but I don't =
see why this should be a problem (I am sure that they all have access to =
email).<o:p></o:p></p></div><div><p =
class=3DMsoNormal>Ross<o:p></o:p></p></div><div><p =
class=3DMsoNormal>&nbsp;<o:p></o:p></p></div></div></body></html>
------_=_NextPart_001_01CD01E8.399385C9--

From fangyuli1999@gmail.com  Wed Mar 14 07:07:48 2012
Return-Path: <fangyuli1999@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3408321F87D6 for <ietf@ietfa.amsl.com>; Wed, 14 Mar 2012 07:07:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.305
X-Spam-Level: 
X-Spam-Status: No, score=-3.305 tagged_above=-999 required=5 tests=[AWL=0.293,  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 ySTMtUZiiwPv for <ietf@ietfa.amsl.com>; Wed, 14 Mar 2012 07:07:47 -0700 (PDT)
Received: from mail-gx0-f194.google.com (mail-gx0-f194.google.com [209.85.161.194]) by ietfa.amsl.com (Postfix) with ESMTP id B0BFE21F87A4 for <ietf@ietf.org>; Wed, 14 Mar 2012 07:07:38 -0700 (PDT)
Received: by ggdk2 with SMTP id k2so458660ggd.1 for <ietf@ietf.org>; Wed, 14 Mar 2012 07:07:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=f/j6dMLKPjyAAEcykSF7NHBFIkuaT2Vee3y2dGDaeL8=; b=nq7+yJZOhPDZbWFOM/KZ0T7P3cALSx90Yw/+GyQC727ApcNCoad9W38gQnSRLJ8Zrd MeR+Hxw10+74eXfvIGVUIAdo+B/uhtm0xI4spzJj2+FOMAv5vWJWtH+mxIdHiWBo7uU6 JU8TEiqbnb0Q6c6pMksJcRp+fEUlEcMK2fPW91pr1F5px6D25XxK5rYZU5621BZz0NnX poCANxKfGfitzVI9NldBOvA9OXdL3JSo7j7OP/1RsvHOmTuk4dcDF+eVxV9GKTekrteV Wlzdcp3GNo8mdvsr+PoqrJgFRMl1dvy7SXLdkreagq683DV6f7xhHBOVimHKMytJjwzC UPWg==
MIME-Version: 1.0
Received: by 10.60.1.3 with SMTP id 3mr3447086oei.73.1331734053523; Wed, 14 Mar 2012 07:07:33 -0700 (PDT)
Received: by 10.182.199.105 with HTTP; Wed, 14 Mar 2012 07:07:33 -0700 (PDT)
In-Reply-To: <E4873516F3FC7547BCFE792C7D94039C016C533A@DEMUEXC013.nsn-intra.net>
References: <CAAHpaZ=JrKVKHZ0xkK-nszFDf-ttVNoi1p9iZiWa93vKuiNxZA@mail.gmail.com> <E4873516F3FC7547BCFE792C7D94039C016C533A@DEMUEXC013.nsn-intra.net>
Date: Wed, 14 Mar 2012 22:07:33 +0800
Message-ID: <CAAHpaZkiYO0HujZe6vsBounS7ea7jPmVWn+QZ_K8eAz-bNRxKA@mail.gmail.com>
Subject: Re: Last Call:<draft-betts-itu-oam-ach-code-point-03.txt>(Allocationof an Associated Channel Code Point for Use by ITU-T Ethernet basedOAM) to Informational RFC
From: Fangyu Li <fangyuli1999@gmail.com>
To: ietf@ietf.org,  "Sprecher, Nurit (NSN - IL/Hod HaSharon)" <nurit.sprecher@nsn.com>
Content-Type: multipart/alternative; boundary=e89a8fb1fa5632117004bb347f4d
Cc: lifang@catr.cn
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Mar 2012 14:07:48 -0000

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

Hi,

For your questions:

 1) Both of the versions of G.8113.1 reach the technical and industry
maturity, for there are only editorial and little modifications such as
Global ICC based MEP/MIP formats.
 2) In last SG15 plenary meeting in Dec, at the drafting session of Q10 on
G.8113.1 and G.8113.2, both OAM solutions could not meet all the
requirements of RFC5654 and RFC5860, you could check this in
 wd16_MPLS-TP_requirementsTable_G.8113.1and
wd15r1_MPLS-TP_requirementsTable-G-8113-2-R1 in
http://ifa.itu.int/t/2009/sg15/exchange/wp3/q10/2011-12-Geneva/.

Li Fang from CATR



2012/3/14 Sprecher, Nurit (NSN - IL/Hod HaSharon) <nurit.sprecher@nsn.com>

>  Hi,****
>
> Which version of G.8113.1 has reached the technical and industry maturity=
?
> Is it the one that was submitted to WTSA or is it the one that the ITU
> worked on the December meeting? Or maybe it is the same document that the
> ITU worked on in the December meeting and sent to WTSA? Can you please
> clarify the point?****
>
> You say that " the codepoint allocation from IETF should allow the ITU-T
> to progress refinements to G.8113.1 such that it could satisfy all the
> functional requirements defined in RFC 5860" =96 does it meant that the
> matured version does not fully satisfy the requirements presented in RFC
> 5860?****
>
> Best regards,****
>
> Nurit****
>
> ** **
>
> *From:* ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] *On Behalf
> Of *ext Fangyu Li
> *Sent:* Wednesday, March 14, 2012 3:36 PM
> *To:* ietf@ietf.org
> *Cc:* lifang@catr.cn
> *Subject:* RE: Last
> Call:<draft-betts-itu-oam-ach-code-point-03.txt>(Allocationof an Associat=
ed
> Channel Code Point for Use by ITU-T Ethernet basedOAM) to Informational R=
FC
> ****
>
> ** **
>
> I support the allocation of an ACH codepoint to G.8113.1. ****
>
>  ****
>
> For G.8113.1 had reached the technical and industry maturity to be
> assigned a code point, the codepoint allocation from IETF should allow th=
e
> ITU-T to progress refinements to G.8113.1 such that it could satisfy all
> the functional requirements defined in RFC 5860. ****
>
>  ****
>
> -----????? ??????-----
> ???: ext Ross Callon
> ????:  13/03/2012, 19:27
> ??: Andrew G. Malis; Sprecher, Nurit (NSN - IL/Hod HaSharon)
> ????: ietf@ietf.org
> ????: RE: Last
> Call:<draft-betts-itu-oam-ach-code-point-03.txt>(Allocationof    an
> Associated Channel Code Point for Use byITU-T Ethernetbased OAM) to
> Informational RFC
> I agree that the allocation of a code point should be to a specific
> version of 8113.1, and specifically should be to the final version that i=
s
> approved by the ITU-T (assuming that a final version of 8113.1 will be
> approved by the ITU-T). This would imply that
> draft-betts-itu-oam-ach-code-point should contain a normative reference t=
o
> the final approved version of 8113.1.****
>
> Given normal IETF processes, this implies that the final RFC resulting
> from draft-betts-itu-oam-ach-code-point could be published as soon as the
> final version of 8113.1 is approved (with the understanding that there wi=
ll
> be a small normal delay between "approved" and "published" which gives ti=
me
> for coordination). Given that the final version of 8113.1 might need to
> reference the RFC resulting from draft-betts-itu-oam-ach-code-point, a bi=
t
> of cooperation might be needed between editorial staff at the ITU and RFC
> editorial staff, but I don't see why this should be a problem (I am sure
> that they all have access to email).****
>
> Ross****
>
>  ****
>

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

<div style=3D"MARGIN:0cm 0cm 0pt;TEXT-AUTOSPACE:ideograph-numeric" class=3D=
"MsoNormal"><font face=3D"Times New Roman"><span style lang=3D"EN-US">Hi,</=
span></font></div>
<div style=3D"MARGIN:0cm 0cm 0pt;TEXT-AUTOSPACE:ideograph-numeric" class=3D=
"MsoNormal"><font face=3D"Times New Roman"><span style lang=3D"EN-US"></spa=
n></font>=A0</div>
<div style=3D"MARGIN:0cm 0cm 0pt;TEXT-AUTOSPACE:ideograph-numeric" class=3D=
"MsoNormal"><font face=3D"Times New Roman"><span style lang=3D"EN-US">For y=
our questions:</span><span style lang=3D"EN-US"></span></font></div>
<p style=3D"MARGIN:0cm 0cm 0pt;TEXT-AUTOSPACE:ideograph-numeric" class=3D"M=
soNormal"><span style lang=3D"EN-US">=A0</span><font face=3D"Times New Roma=
n"><span style lang=3D"EN-US">1) Both=A0of the versions of G.8113.1 reach t=
he technical and industry maturity, for there are only editorial and little=
 modifications such as Global ICC based MEP/MIP formats.</span><span style =
lang=3D"EN-US"></span></font></p>

<div><span style lang=3D"EN-US">=A0</span><span style lang=3D"EN-US">2) In =
last SG15 plenary meeting in Dec, at the drafting session of Q10 on G.8113.=
1 and G.8113.2, both OAM solutions could not meet all the requirements of R=
FC5654 and RFC5860,=A0you could=A0check this in =A0wd16_MPLS-TP_requirement=
sTable_G.8113.1and wd15r1_MPLS-TP_requirementsTable-G-8113-2-R1 in <a href=
=3D"http://ifa.itu.int/t/2009/sg15/exchange/wp3/q10/2011-12-Geneva/">http:/=
/ifa.itu.int/t/2009/sg15/exchange/wp3/q10/2011-12-Geneva/</a>.</span></div>

<div><span style lang=3D"EN-US"></span>=A0</div>
<div><span style lang=3D"EN-US">Li Fang from CATR</span></div>
<div><br><br>=A0</div>
<div class=3D"gmail_quote">2012/3/14 Sprecher, Nurit (NSN - IL/Hod HaSharon=
) <span dir=3D"ltr">&lt;<a href=3D"mailto:nurit.sprecher@nsn.com">nurit.spr=
echer@nsn.com</a>&gt;</span><br>
<blockquote style=3D"BORDER-LEFT:#ccc 1px solid;MARGIN:0px 0px 0px 0.8ex;PA=
DDING-LEFT:1ex" class=3D"gmail_quote">
<div lang=3D"EN-US" vlink=3D"purple" link=3D"blue">
<div>
<p class=3D"MsoNormal"><span style=3D"FONT-FAMILY:&#39;Calibri&#39;,&#39;sa=
ns-serif&#39;;COLOR:#1f497d;FONT-SIZE:11pt">Hi,<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-FAMILY:&#39;Calibri&#39;,&#39;sa=
ns-serif&#39;;COLOR:#1f497d;FONT-SIZE:11pt">Which version of G.8113.1 </spa=
n>has reached the technical and industry maturity<span style=3D"FONT-FAMILY=
:&#39;Calibri&#39;,&#39;sans-serif&#39;;COLOR:#1f497d;FONT-SIZE:11pt">? Is =
it the one that was submitted to WTSA or is it the one that the ITU worked =
on the December meeting? Or maybe it is the same document that the ITU work=
ed on in the December meeting and sent to WTSA? Can you please clarify the =
point?<u></u><u></u></span></p>

<p class=3D"MsoNormal"><span style=3D"FONT-FAMILY:&#39;Calibri&#39;,&#39;sa=
ns-serif&#39;;COLOR:#1f497d;FONT-SIZE:11pt">You say that &quot;</span> the =
codepoint allocation from IETF should allow the ITU-T to progress refinemen=
ts to G.8113.1 such that it could satisfy all the functional requirements d=
efined in RFC 5860&quot; =96 does it meant that the matured version does no=
t fully satisfy the requirements presented in RFC 5860?<u></u><u></u></p>

<p class=3D"MsoNormal">Best regards,<u></u><u></u></p>
<p class=3D"MsoNormal">Nurit<span style=3D"FONT-FAMILY:&#39;Calibri&#39;,&#=
39;sans-serif&#39;;COLOR:#1f497d;FONT-SIZE:11pt"><u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"FONT-FAMILY:&#39;Calibri&#39;,&#39;sa=
ns-serif&#39;;COLOR:#1f497d;FONT-SIZE:11pt"><u></u>=A0<u></u></span></p>
<div style=3D"BORDER-BOTTOM:medium none;BORDER-LEFT:medium none;PADDING-BOT=
TOM:0cm;PADDING-LEFT:0cm;PADDING-RIGHT:0cm;BORDER-TOP:#b5c4df 1pt solid;BOR=
DER-RIGHT:medium none;PADDING-TOP:3pt">
<p class=3D"MsoNormal"><b><span style=3D"FONT-FAMILY:&#39;Tahoma&#39;,&#39;=
sans-serif&#39;;FONT-SIZE:10pt">From:</span></b><span style=3D"FONT-FAMILY:=
&#39;Tahoma&#39;,&#39;sans-serif&#39;;FONT-SIZE:10pt"> <a href=3D"mailto:ie=
tf-bounces@ietf.org" target=3D"_blank">ietf-bounces@ietf.org</a> [mailto:<a=
 href=3D"mailto:ietf-bounces@ietf.org" target=3D"_blank">ietf-bounces@ietf.=
org</a>] <b>On Behalf Of </b>ext Fangyu Li<br>
<b>Sent:</b> Wednesday, March 14, 2012 3:36 PM<br><b>To:</b> <a href=3D"mai=
lto:ietf@ietf.org" target=3D"_blank">ietf@ietf.org</a><br><b>Cc:</b> <a hre=
f=3D"mailto:lifang@catr.cn" target=3D"_blank">lifang@catr.cn</a><br><b>Subj=
ect:</b> RE: Last Call:&lt;draft-betts-itu-oam-ach-code-point-03.txt&gt;(Al=
locationof an Associated Channel Code Point for Use by ITU-T Ethernet based=
OAM) to Informational RFC<u></u><u></u></span></p>
</div>
<div>
<div class=3D"h5">
<p class=3D"MsoNormal"><u></u>=A0<u></u></p>
<div>
<p class=3D"MsoNormal">I support the allocation of an ACH codepoint to G.81=
13.1. <u></u><u></u></p></div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p></div>
<div>
<p class=3D"MsoNormal">For G.8113.1 had reached the technical and industry =
maturity to be assigned a code point, the codepoint allocation from IETF sh=
ould allow the ITU-T to progress refinements to G.8113.1 such that it could=
 satisfy all the functional requirements defined in RFC 5860. <u></u><u></u=
></p>
</div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p></div>
<div>
<p class=3D"MsoNormal">-----????? ??????-----<br>???: ext Ross Callon<br>??=
??:=A0 13/03/2012, 19:27<br>??: Andrew G. Malis; Sprecher, Nurit (NSN - IL/=
Hod HaSharon)<br>????: <a href=3D"mailto:ietf@ietf.org" target=3D"_blank">i=
etf@ietf.org</a><br>
????: RE: Last Call:&lt;draft-betts-itu-oam-ach-code-point-03.txt&gt;(Alloc=
ationof=A0=A0=A0 an Associated Channel Code Point for Use byITU-T Ethernetb=
ased OAM) to=A0 Informational RFC<br>I agree that the allocation of a code =
point should be to a specific version of 8113.1, and specifically should be=
 to the final version that is approved by the ITU-T (assuming that a final =
version of 8113.1 will be approved by the ITU-T). This would imply that dra=
ft-betts-itu-oam-ach-code-point should contain a normative reference to the=
 final approved version of 8113.1.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Given normal IETF processes, this implies that the f=
inal RFC resulting from draft-betts-itu-oam-ach-code-point could be publish=
ed as soon as the final version of 8113.1 is approved (with the understandi=
ng that there will be a small normal delay between &quot;approved&quot; and=
 &quot;published&quot; which gives time for coordination). Given that the f=
inal version of 8113.1 might need to reference the RFC resulting from draft=
-betts-itu-oam-ach-code-point, a bit of cooperation might be needed between=
 editorial staff at the ITU and RFC editorial staff, but I don&#39;t see wh=
y this should be a problem (I am sure that they all have access to email).<=
u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Ross<u></u><u></u></p></div>
<div>
<p class=3D"MsoNormal">=A0<u></u><u></u></p></div></div></div></div></div><=
/blockquote></div><br>

--e89a8fb1fa5632117004bb347f4d--

From iljitsch@muada.com  Wed Mar 14 07:24:47 2012
Return-Path: <iljitsch@muada.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1D8BE21F881F; Wed, 14 Mar 2012 07:24:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level: 
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S7FINa-p0oIN; Wed, 14 Mar 2012 07:24:46 -0700 (PDT)
Received: from sequoia.muada.com (sequoia.muada.com [IPv6:2001:1af8:3100:a006:1::]) by ietfa.amsl.com (Postfix) with ESMTP id 6500221E8050; Wed, 14 Mar 2012 07:24:43 -0700 (PDT)
Received: from [IPv6:2001:470:1f0b:1289:7039:9930:70e3:1c36] ([IPv6:2001:470:1f0b:1289:7039:9930:70e3:1c36]) (authenticated bits=0) by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id q2EEOWTe040513 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 14 Mar 2012 15:24:34 +0100 (CET) (envelope-from iljitsch@muada.com)
Subject: Re: [83attendees] Usual recreational venue diatribe (was Ground transportation from/to CDG)
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=us-ascii
From: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <DDD8B097-08F4-46E2-BB22-55B566F95E06@mimecast.com>
Date: Wed, 14 Mar 2012 15:24:40 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <53A710F7-2BF9-40FE-A2FA-CA001D0F7CD5@muada.com>
References: <CABOxzu3P_OsrteZwnn5Ntskw8AoRB-Mp26RyZ_SH02u0ekfbqQ@mail.gmail.com> <alpine.BSF.2.00.1203112218050.5094@joyce.lan> <0B7D9C2C-CDED-42EE-99E9-8D188D050CD5@commcorp.com.br> <018601cd0050$0b8a2940$229e7bc0$@gmail.com> <737E053B-81B7-43DF-AF25-F33FA152E77D@muada.com> <CAC4RtVCbuBA1TU0gaQ=OdL4VfqkaUSWG1dvx9_7MQt9547+oSw@mail.gmail.com> <AD9F9C4F-9245-4125-ABC9-3BD7E3502EBC@softarmor.com> <alpine.OSX.2.01.1203131552360.16882@rabdullah.local> <m2zkbkdqnz.wl%randy@psg.com> <B2D62B70-AD02-40D1-9D8F-0DD8A9DDA3CA@softarmor.com> <6A46D6D5-D4A2-4006-B402-E4724E56D4C3@fugue.com> <4F60A14C.4080309@alum.mit.edu> <DDD8B097-08F4-46E2-BB22-55B566F95E06@mimecast.com>
To: Nathaniel Borenstein <nsb@mimecast.com>
X-Mailer: Apple Mail (2.1257)
Cc: 83attendees@ietf.org, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Mar 2012 14:24:47 -0000

[cc to ietf@ietf]

On 14 Mar 2012, at 14:58 , Nathaniel Borenstein wrote:

> One idea I've toyed with idly for years is halfway in between:  keep =
the physical meetings, but break them up into multiple locations.  We =
could have physical meetings in Europe, North America, and Asia, with =
strong telecom links among them.  We'd still have to all be on the same =
schedule, but the people making the time shift would at least be =
surrounded by others on the same odd schedule, and there'd be critical =
mass for services like meals in the middle of the night.  Meanwhile, the =
travel costs and visa hassles would be reduced.

That would combine the worst aspects of being at a meeting with the =
worst aspects of NOT being at a meeting. Also, regional travel is a lot =
cheaper than intercontinental travel, but when you add up all the other =
costs you really don't save that much.

We still haven't figured out how to use jabber effectively during =
meetings (either the jabber channel replicates all the info that's also =
in the audio stream or it's pretty much idle), so PLEASE no experiments =
in this area. Let others figure this out and then we can adopt what =
works.=

From christopher.morrow@gmail.com  Wed Mar 14 07:36:25 2012
Return-Path: <christopher.morrow@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3978921F8741 for <ietf@ietfa.amsl.com>; Wed, 14 Mar 2012 07:36:25 -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, MIME_8BIT_HEADER=0.3, 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 MwbWBQDk74lr for <ietf@ietfa.amsl.com>; Wed, 14 Mar 2012 07:36:24 -0700 (PDT)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id 9445721F8717 for <ietf@ietf.org>; Wed, 14 Mar 2012 07:36:24 -0700 (PDT)
Received: by ggmi1 with SMTP id i1so2153568ggm.31 for <ietf@ietf.org>; Wed, 14 Mar 2012 07:36:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=DQSFI2jEmhPfd3QhWk/rHLxJa28sC/gYg9LLyu6xE7s=; b=jWz/k29P/kC0YzR76UKvJMTZpTrqg5hQTcNHwfJHHzV3AYyWY+Vpm8PLa54eikgoyC vs85pLm1cPtfBDDYlBnm3LleCorS43tlqPeOWVmUmtK81U50IgoWiWbJT/8FU5hq0Irv wqbzMIzw2k9vFIcNeMj0IDCPsR8c8Qgh3ErJEf4wp01oAMrcBJA3QzBn8+oV/mcB6/o6 tR9Uwg/KldWttOG1l8AqxnyM6Z7DmWrM1J7zrOpjcEkKFPO4gLlgRS5/CkWhP57uLWtx T8/SAqZlI4lzVVX82T3CeIAa9uJtKC2JE6YbvqaM4H1TYcilc0aJNnjNoWpyqWCXZajB AWig==
MIME-Version: 1.0
Received: by 10.60.4.170 with SMTP id l10mr3476180oel.67.1331735784132; Wed, 14 Mar 2012 07:36:24 -0700 (PDT)
Sender: christopher.morrow@gmail.com
Received: by 10.182.220.100 with HTTP; Wed, 14 Mar 2012 07:36:24 -0700 (PDT)
In-Reply-To: <CAKFn1SEGpUSyTnM5kOFT9J=y1AbXDLxti7g-KGKk7dXFWyfNwg@mail.gmail.com>
References: <CAL9jLaZyPBDaGyom4Qrdt+TfzBONftH_Zxtjp1MfiH3tBLXejA@mail.gmail.com> <20120314074707.GZ16111@besserwisser.org> <CAKFn1SEGpUSyTnM5kOFT9J=y1AbXDLxti7g-KGKk7dXFWyfNwg@mail.gmail.com>
Date: Wed, 14 Mar 2012 10:36:24 -0400
X-Google-Sender-Auth: 63hgYzZ2j2Rt8RUGi1_VM9byuNs
Message-ID: <CAL9jLaYxW=pkmCcrKU3qoFCu1sGde918tGuf3YubQ2x-O12D1A@mail.gmail.com>
Subject: Re: shared address space... a reality!
From: Christopher Morrow <morrowc.lists@gmail.com>
To: =?ISO-8859-1?Q?Roger_J=F8rgensen?= <rogerj@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: =?ISO-8859-1?Q?M=E5ns_Nilsson?= <mansaxel@besserwisser.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, 14 Mar 2012 14:36:25 -0000

2012/3/14 Roger J=F8rgensen <rogerj@gmail.com>:

> This is really "good" news for some people, that already have address
> conflict within RFC1918 and don't want to get public address space :p

you mean every enterprise on the planet? (or probably 99.999%)

From jmh@joelhalpern.com  Wed Mar 14 07:46:41 2012
Return-Path: <jmh@joelhalpern.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 038B121F8810; Wed, 14 Mar 2012 07:46:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.112
X-Spam-Level: 
X-Spam-Status: No, score=-102.112 tagged_above=-999 required=5 tests=[AWL=0.153, 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 9uPPap1VZRbt; Wed, 14 Mar 2012 07:46:40 -0700 (PDT)
Received: from morbo.mail.tigertech.net (morbo.mail.tigertech.net [67.131.251.54]) by ietfa.amsl.com (Postfix) with ESMTP id 98F8D21F880F; Wed, 14 Mar 2012 07:46:40 -0700 (PDT)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) by morbo.tigertech.net (Postfix) with ESMTP id 627CF103D71; Wed, 14 Mar 2012 07:46:40 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id E91C11C0870; Wed, 14 Mar 2012 07:46:39 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from [10.10.10.100] (pool-71-161-51-182.clppva.btas.verizon.net [71.161.51.182]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id E7D421C0801; Wed, 14 Mar 2012 07:46:38 -0700 (PDT)
Message-ID: <4F60AF4D.1090506@joelhalpern.com>
Date: Wed, 14 Mar 2012 10:46:37 -0400
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: John Scudder <jgs@juniper.net>
Subject: Re: [lisp] WG Review: Recharter of Locator/ID Separation Protocol (lisp)
References: <20120214222316.CF29521E800E@ietfa.amsl.com> <201202152131.q1FLVB9E028114@cichlid.raleigh.ibm.com> <EF3C34EB-C0AA-45F2-ADE0-407CEF5172DD@juniper.net> <4F3E4EDB.7070509@piuha.net> <0E0C6A25-FBA6-4E11-9E89-DEBFFCF41108@juniper.net> <4F58EB8C.1000700@piuha.net> <70EB276F-D77E-45AE-851C-AB08A8D56D0A@juniper.net> <4F5920FF.6070502@piuha.net> <CALaySJKvS5QbtXuMx7TwFiL4hdgi1cT0sYu8EJtYLD6T2yOzKQ@mail.gmail.com> <1D2FF8E9-8E60-4126-AC30-12DFDC854BC6@juniper.net> <4F5F9A44.4020600@joelhalpern.com> <7CDFAED4-30C6-4CC4-BA91-F8B34857C9B4@juniper.net>
In-Reply-To: <7CDFAED4-30C6-4CC4-BA91-F8B34857C9B4@juniper.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Barry Leiba <barryleiba@computer.org>, "ietf@ietf.org list" <ietf@ietf.org>, "lisp@ietf.org" <lisp@ietf.org>, "iesg@ietf.org IESG" <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Mar 2012 14:46:41 -0000

Relevant?  Yes.
Gating?  No.

In fact, I would put it the other way around.
The architecture documentis very useful, almost necessary, for deciding 
whether the solution is a good one.
The cache management evaluations are another component of such an 
evaluation.
Even understanding the cache management quesiton is made significantly 
easier by having a clean architecture description.

Yours,
Joel

On 3/14/2012 10:40 AM, John Scudder wrote:
> One further remark:
>
> On Mar 13, 2012, at 3:04 PM, Joel M. Halpern wrote:
> ...
>> It may take engineering and evaluating some cache management schemes
>> before one can decide whether the archtiecture is a good one.
> ...
>
> Agreed.
>
> Isn't it relevant to the architecture document, that it be possible for a reader to judge whether the architecture is a good one or not?
>
> --John

From barryleiba@gmail.com  Wed Mar 14 08:02:57 2012
Return-Path: <barryleiba@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6ACB921F87E3; Wed, 14 Mar 2012 08:02:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.984
X-Spam-Level: 
X-Spam-Status: No, score=-102.984 tagged_above=-999 required=5 tests=[AWL=-0.007, 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 kyC5PS+oZJdj; Wed, 14 Mar 2012 08:02:57 -0700 (PDT)
Received: from mail-gy0-f172.google.com (mail-gy0-f172.google.com [209.85.160.172]) by ietfa.amsl.com (Postfix) with ESMTP id C3BC321F87DE; Wed, 14 Mar 2012 08:02:56 -0700 (PDT)
Received: by ghbg16 with SMTP id g16so2184956ghb.31 for <multiple recipients>; Wed, 14 Mar 2012 08:02:56 -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 :content-transfer-encoding; bh=TXhmMWoIbKpL1RsyCpTUJRDMKzKgXXw/SUDxW5eAmdY=; b=iOnzqVniaFlhpvogkfKaNdQhsARW9u3k0LamsT2PhaYV5++q0dzueTmjVKKHECqz4/ jMEzb6xtyieORIw10QkBrj0eJexZ2rA12/bH5wlrV5Ni49pmvyeIugsO6S/ouFLqtrue cEVUcgH1BS0lycD103zWf1wdKiuslAIb5XBZZ/EENkOl8PCblzf6+w3vFKPsguzLV7NE iTiGrcQYGJP2pOiUjqIpg1pab/sWmDNkudldrggf41sT96DUlVEsEROmJUf87mW+mzBA aGhUHolORszqzpEWyPoimZdY4gHbkHg7ejTSO/JeajWww/kuVoJghYXUX/hRBHd7Etn6 hiXQ==
MIME-Version: 1.0
Received: by 10.60.3.226 with SMTP id f2mr3652820oef.44.1331737376285; Wed, 14 Mar 2012 08:02:56 -0700 (PDT)
Sender: barryleiba@gmail.com
Received: by 10.60.125.37 with HTTP; Wed, 14 Mar 2012 08:02:56 -0700 (PDT)
In-Reply-To: <4F60AF4D.1090506@joelhalpern.com>
References: <20120214222316.CF29521E800E@ietfa.amsl.com> <201202152131.q1FLVB9E028114@cichlid.raleigh.ibm.com> <EF3C34EB-C0AA-45F2-ADE0-407CEF5172DD@juniper.net> <4F3E4EDB.7070509@piuha.net> <0E0C6A25-FBA6-4E11-9E89-DEBFFCF41108@juniper.net> <4F58EB8C.1000700@piuha.net> <70EB276F-D77E-45AE-851C-AB08A8D56D0A@juniper.net> <4F5920FF.6070502@piuha.net> <CALaySJKvS5QbtXuMx7TwFiL4hdgi1cT0sYu8EJtYLD6T2yOzKQ@mail.gmail.com> <1D2FF8E9-8E60-4126-AC30-12DFDC854BC6@juniper.net> <4F5F9A44.4020600@joelhalpern.com> <7CDFAED4-30C6-4CC4-BA91-F8B34857C9B4@juniper.net> <4F60AF4D.1090506@joelhalpern.com>
Date: Wed, 14 Mar 2012 11:02:56 -0400
X-Google-Sender-Auth: uWi4mvr14vVtrLitAePYCs5zLz8
Message-ID: <CALaySJ+xPdJJKAj3m+h6cLHPev5MhbVzRb8YwBO+CE5F8AKtbw@mail.gmail.com>
Subject: Re: [lisp] WG Review: Recharter of Locator/ID Separation Protocol (lisp)
From: Barry Leiba <barryleiba@computer.org>
To: John Scudder <jgs@juniper.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "ietf@ietf.org list" <ietf@ietf.org>, "lisp@ietf.org" <lisp@ietf.org>, "iesg@ietf.org IESG" <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Mar 2012 15:02:57 -0000

> Relevant? =A0Yes.
> Gating? =A0No.
>
> In fact, I would put it the other way around.
> The architecture documentis very useful, almost necessary, for deciding
> whether the solution is a good one.
> The cache management evaluations are another component of such an
> evaluation.
> Even understanding the cache management question is made significantly
> easier by having a clean architecture description.

Indeed.

At the risk of straining things with an analogy, I'll liken this to
architecture of a building.  At the architecture level, we do have to
consider, say, bathrooms, and it's reasonable at that level to talk
about having bathrooms on each floor, and perhaps the extent to which
accessible bathrooms are needed.  Deciding whether to have two pairs
or three per floor is something that can be left to the detailed
post-architecture specifications, and things like what sorts of
fixtures to put in them *absolutely* come later.

No one is saying that some discussion of caching issues (etc) won't be
needed in defining and specifying the architecture.  We're just saying
that it's not necessary to do the caching document before, as long as
the related discussion that happens at the architecture stage is
preserved for when it's time to work on the caching doc.

Barry

From jgs@juniper.net  Tue Mar 13 11:38:17 2012
Return-Path: <jgs@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 142FC21E8059; Tue, 13 Mar 2012 11:38:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.487
X-Spam-Level: 
X-Spam-Status: No, score=-6.487 tagged_above=-999 required=5 tests=[AWL=0.112,  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 zfRAgCTUypW9; Tue, 13 Mar 2012 11:38:16 -0700 (PDT)
Received: from exprod7og107.obsmtp.com (exprod7og107.obsmtp.com [64.18.2.167]) by ietfa.amsl.com (Postfix) with ESMTP id B132321E8019; Tue, 13 Mar 2012 11:38:15 -0700 (PDT)
Received: from P-EMHUB01-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob107.postini.com ([64.18.6.12]) with SMTP ID DSNKT1+UABF4xCzr8WQwdQWFCibuBj2wyazH@postini.com; Tue, 13 Mar 2012 11:38:16 PDT
Received: from EMBX02-HQ.jnpr.net ([fe80::18fe:d666:b43e:f97e]) by P-EMHUB01-HQ.jnpr.net ([fe80::fc92:eb1:759:2c72%11]) with mapi; Tue, 13 Mar 2012 11:37:06 -0700
From: John Scudder <jgs@juniper.net>
To: Barry Leiba <barryleiba@computer.org>
Date: Tue, 13 Mar 2012 11:37:05 -0700
Subject: Re: [lisp] WG Review: Recharter of Locator/ID Separation Protocol (lisp)
Thread-Topic: [lisp] WG Review: Recharter of Locator/ID Separation Protocol (lisp)
Thread-Index: Ac0BSEoZUP3kQBwNQNeUNM+ApKZgZA==
Message-ID: <1D2FF8E9-8E60-4126-AC30-12DFDC854BC6@juniper.net>
References: <20120214222316.CF29521E800E@ietfa.amsl.com> <201202152131.q1FLVB9E028114@cichlid.raleigh.ibm.com> <EF3C34EB-C0AA-45F2-ADE0-407CEF5172DD@juniper.net> <4F3E4EDB.7070509@piuha.net> <0E0C6A25-FBA6-4E11-9E89-DEBFFCF41108@juniper.net> <4F58EB8C.1000700@piuha.net> <70EB276F-D77E-45AE-851C-AB08A8D56D0A@juniper.net> <4F5920FF.6070502@piuha.net> <CALaySJKvS5QbtXuMx7TwFiL4hdgi1cT0sYu8EJtYLD6T2yOzKQ@mail.gmail.com>
In-Reply-To: <CALaySJKvS5QbtXuMx7TwFiL4hdgi1cT0sYu8EJtYLD6T2yOzKQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
x-exclaimer-md-config: e4081efb-6d29-443c-8708-750833aec629
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Wed, 14 Mar 2012 08:15:38 -0700
Cc: "lisp@ietf.org" <lisp@ietf.org>, "iesg@ietf.org IESG" <iesg@ietf.org>, "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Mar 2012 18:38:17 -0000

Barry and all,

On Mar 8, 2012, at 4:34 PM, Barry Leiba wrote:
...
>>> But it's not clear to me that these (especially architecture and impact=
s) can
>>> be said to have been properly analyzed until some of the lower-priority=
 items
>>> (I'm thinking of threats, cache, ETR sync) have been fleshed out.
>>=20
>> I hear what you are saying. But I think the opinion in the IESG at least
>> was, however, that those three really are high priority, and that other
>> documents before them are not so useful before they are completed. I gue=
ss
>> it is a different perspective, whether you do things top-down or bottom-=
up.
>> I do agree with both points of view, actually.
>=20
> The dependencies (threats, cache, ETR sync, and whatever else) can
> certainly be discussed to the extent needed to lay out the
> architecture and other priority documents, with notes taken and saved
> for when other documents need to be produced.  That still says that
> the working group needs to focus on discussion that leads to the
> completion of the three priority documents first, before tackling the
> others.  Everyone understands that these priority items can't be
> developed in a vacuum; we just don't want things to wander off into
> lower-level details such as protocol elements and text that can wait
> for the next phase.

You don't want to boil the ocean; that's fine. My point is that without cov=
ering (at least) cache management and ETR synchronization, the architecture=
 will not be done. Think about the old joke about the mathematical proof th=
at includes "... then a miracle occurs" as one of its steps (http://star.ps=
y.ohio-state.edu/coglab/Miracle.html). Similarly, threats and the impacts d=
ocument.

One way to handle this (other than what I've already suggested) might be to=
 explicitly note that the respective documents should cover these topics. F=
or example (edits set off by [[ ]]):

- Architecture description: This document will describe the
  architecture of the entire LISP system, making it easier to read the
  rest of the LISP specifications and providing a basis for discussion
  about the details of the LISP protocols. [[The document will
  cover relevant issues including though not limited to cache
  management and ETR synchronization.]]

and

- A description of the impacts of LISP: This document will describe
  the problems that LISP is intended to address and the impacts that
  employing LISP has. While the work on LISP was initiated by Internet
  routing scaling concerns, there has also been an interest on
  improved solutions to a number of different problems, such as
  traffic engineering. This document should describe problem areas
  (such as scaling or traffic engineer) where LISP is expected to have
  a positive effect, as well as any tradeoffs that are caused by
  LISP's design. [[The document will discuss potential security-
  related impacts, whether positive or negative.]]=20
 =20
Regards,

--John=

From jgs@juniper.net  Tue Mar 13 12:24:35 2012
Return-Path: <jgs@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 8CA1721E806A; Tue, 13 Mar 2012 12:24:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.496
X-Spam-Level: 
X-Spam-Status: No, score=-6.496 tagged_above=-999 required=5 tests=[AWL=0.103,  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 BauAJlo+Nju2; Tue, 13 Mar 2012 12:24:33 -0700 (PDT)
Received: from exprod7og103.obsmtp.com (exprod7og103.obsmtp.com [64.18.2.159]) by ietfa.amsl.com (Postfix) with ESMTP id 6104121E8024; Tue, 13 Mar 2012 12:24:33 -0700 (PDT)
Received: from P-EMHUB02-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob103.postini.com ([64.18.6.12]) with SMTP ID DSNKT1+e41BhkNLNhETxSD92BOHp6x0TEljf@postini.com; Tue, 13 Mar 2012 12:24:33 PDT
Received: from EMBX02-HQ.jnpr.net ([fe80::18fe:d666:b43e:f97e]) by P-EMHUB02-HQ.jnpr.net ([fe80::88f9:77fd:dfc:4d51%11]) with mapi; Tue, 13 Mar 2012 12:23:21 -0700
From: John Scudder <jgs@juniper.net>
To: "Joel M. Halpern" <jmh@joelhalpern.com>
Date: Tue, 13 Mar 2012 12:23:20 -0700
Subject: Re: [lisp] WG Review: Recharter of Locator/ID Separation Protocol (lisp)
Thread-Topic: [lisp] WG Review: Recharter of Locator/ID Separation Protocol (lisp)
Thread-Index: Ac0BTsCkcu2c2EazTrO88abiPtK/mg==
Message-ID: <754A7276-FC6F-4C76-8627-4AEDB5FBB4C4@juniper.net>
References: <20120214222316.CF29521E800E@ietfa.amsl.com> <201202152131.q1FLVB9E028114@cichlid.raleigh.ibm.com> <EF3C34EB-C0AA-45F2-ADE0-407CEF5172DD@juniper.net> <4F3E4EDB.7070509@piuha.net> <0E0C6A25-FBA6-4E11-9E89-DEBFFCF41108@juniper.net> <4F58EB8C.1000700@piuha.net> <70EB276F-D77E-45AE-851C-AB08A8D56D0A@juniper.net> <4F5920FF.6070502@piuha.net> <CALaySJKvS5QbtXuMx7TwFiL4hdgi1cT0sYu8EJtYLD6T2yOzKQ@mail.gmail.com> <1D2FF8E9-8E60-4126-AC30-12DFDC854BC6@juniper.net> <4F5F9A44.4020600@joelhalpern.com>
In-Reply-To: <4F5F9A44.4020600@joelhalpern.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
x-exclaimer-md-config: e4081efb-6d29-443c-8708-750833aec629
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Wed, 14 Mar 2012 08:15:38 -0700
Cc: Barry Leiba <barryleiba@computer.org>, "ietf@ietf.org list" <ietf@ietf.org>, "lisp@ietf.org" <lisp@ietf.org>, "iesg@ietf.org IESG" <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Mar 2012 19:24:35 -0000

Joel,

Re cache management schemes, I think that depends on whether you mean "syst=
em level behavior" of a small-scale system, or one operating at large scale=
 or under some kind of stress. The earlier discussion notwithstanding, for =
practical purposes caching is central to LISP; as such, it's a little weird=
 to say it's architecturally unimportant.

Re ETR sync, I think not even that much wiggle room exists.

--John

On Mar 13, 2012, at 3:04 PM, Joel M. Halpern wrote:

Actually John, I would have to disagree with your assertion about what
it takes to describe the archtiecture.
It may take engineering and evaluating some cache management schemes
before one can decide whether the archtiecture is a good one.  But that
is very different from being able to describe the archteicture so that
one can understand the system level behavior.

Yours,
Joel

On 3/13/2012 2:37 PM, John Scudder wrote:
Barry and all,

On Mar 8, 2012, at 4:34 PM, Barry Leiba wrote:
...
But it's not clear to me that these (especially architecture and impacts) c=
an
be said to have been properly analyzed until some of the lower-priority ite=
ms
(I'm thinking of threats, cache, ETR sync) have been fleshed out.

I hear what you are saying. But I think the opinion in the IESG at least
was, however, that those three really are high priority, and that other
documents before them are not so useful before they are completed. I guess
it is a different perspective, whether you do things top-down or bottom-up.
I do agree with both points of view, actually.

The dependencies (threats, cache, ETR sync, and whatever else) can
certainly be discussed to the extent needed to lay out the
architecture and other priority documents, with notes taken and saved
for when other documents need to be produced.  That still says that
the working group needs to focus on discussion that leads to the
completion of the three priority documents first, before tackling the
others.  Everyone understands that these priority items can't be
developed in a vacuum; we just don't want things to wander off into
lower-level details such as protocol elements and text that can wait
for the next phase.

You don't want to boil the ocean; that's fine. My point is that without cov=
ering (at least) cache management and ETR synchronization, the architecture=
 will not be done. Think about the old joke about the mathematical proof th=
at includes "... then a miracle occurs" as one of its steps (http://star.ps=
y.ohio-state.edu/coglab/Miracle.html). Similarly, threats and the impacts d=
ocument.

One way to handle this (other than what I've already suggested) might be to=
 explicitly note that the respective documents should cover these topics. F=
or example (edits set off by [[ ]]):

- Architecture description: This document will describe the
  architecture of the entire LISP system, making it easier to read the
  rest of the LISP specifications and providing a basis for discussion
  about the details of the LISP protocols. [[The document will
  cover relevant issues including though not limited to cache
  management and ETR synchronization.]]

and

- A description of the impacts of LISP: This document will describe
  the problems that LISP is intended to address and the impacts that
  employing LISP has. While the work on LISP was initiated by Internet
  routing scaling concerns, there has also been an interest on
  improved solutions to a number of different problems, such as
  traffic engineering. This document should describe problem areas
  (such as scaling or traffic engineer) where LISP is expected to have
  a positive effect, as well as any tradeoffs that are caused by
  LISP's design. [[The document will discuss potential security-
  related impacts, whether positive or negative.]]

Regards,

--John
_______________________________________________
lisp mailing list
lisp@ietf.org<mailto:lisp@ietf.org>
https://www.ietf.org/mailman/listinfo/lisp



From dino@cisco.com  Tue Mar 13 21:07:02 2012
Return-Path: <dino@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 D9EE121E803A; Tue, 13 Mar 2012 21:07:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.544
X-Spam-Level: 
X-Spam-Status: No, score=-8.544 tagged_above=-999 required=5 tests=[AWL=2.055,  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 Mood94f7Xl0b; Tue, 13 Mar 2012 21:07:02 -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 72A4121E800F; Tue, 13 Mar 2012 21:07:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=dino@cisco.com; l=507; q=dns/txt; s=iport; t=1331698021; x=1332907621; h=subject:mime-version:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=M0ZAlKs7Kx625UmWCSPJSHH28X53dKfv/4VuneONPv4=; b=QOm431QjYJNhMjdsJSJYWwf9A7HqhVZnGiupKd8GxvJt6FuQs9sDLDVY VWAUZJdvDi5TxD26iMkQTMVRNmNWbsPfEanHmyPR/m3Mj7reejBF3J7Vj 2RuFGBGCvU58cJslawOMXAJekWCA0TcQ/DvlyxD/YiUaNaooTnl6iVyc2 g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAHgYYE+rRDoG/2dsb2JhbABDtXiBB4IJAQEBAwESASc/BQsLDgQ0SQ4GNYdjBJ0TAZ52kBNjBIhVjHuQI4MF
X-IronPort-AV: E=Sophos;i="4.73,582,1325462400"; d="scan'208";a="36034430"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by mtv-iport-2.cisco.com with ESMTP; 14 Mar 2012 04:07:01 +0000
Received: from sjc-vpn6-920.cisco.com (sjc-vpn6-920.cisco.com [10.21.123.152]) by mtv-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id q2E4703t005754; Wed, 14 Mar 2012 04:07:00 GMT
Subject: Re: [lisp] WG Review: Recharter of Locator/ID Separation Protocol (lisp)
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: text/plain; charset=us-ascii
From: Dino Farinacci <dino@cisco.com>
In-Reply-To: <754A7276-FC6F-4C76-8627-4AEDB5FBB4C4@juniper.net>
Date: Tue, 13 Mar 2012 21:07:00 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <A5E2173A-DFFB-44E2-B535-1A66AB35F230@cisco.com>
References: <20120214222316.CF29521E800E@ietfa.amsl.com> <201202152131.q1FLVB9E028114@cichlid.raleigh.ibm.com> <EF3C34EB-C0AA-45F2-ADE0-407CEF5172DD@juniper.net> <4F3E4EDB.7070509@piuha.net> <0E0C6A25-FBA6-4E11-9E89-DEBFFCF41108@juniper.net> <4F58EB8C.1000700@piuha.net> <70EB276F-D77E-45AE-851C-AB08A8D56D0A@juniper.net> <4F5920FF.6070502@piuha.net> <CALaySJKvS5QbtXuMx7TwFiL4hdgi1cT0sYu8EJtYLD6T2yOzKQ@mail.gmail.com> <1D2FF8E9-8E60-4126-AC30-12DFDC854BC6@juniper.net> <4F5F9A44.4020600@joelhalpern.com> <754A7276-FC6F-4C76-8627-4AEDB5FBB4C4@juniper.net>
To: John Scudder <jgs@juniper.net>
X-Mailer: Apple Mail (2.1251.1)
X-Mailman-Approved-At: Wed, 14 Mar 2012 08:15:38 -0700
Cc: "iesg@ietf.org IESG" <iesg@ietf.org>, "ietf@ietf.org list" <ietf@ietf.org>, Barry Leiba <barryleiba@computer.org>, "lisp@ietf.org" <lisp@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Mar 2012 04:07:03 -0000

> Re ETR sync, I think not even that much wiggle room exists.

I beg to differ. What happens if an iBGP mesh is not configured =
properly? Does that mean the BGP architecture is broken?=20

We have said in the past, several times, that if the ETRs are out of =
sync, then the ITR that gets a Map-Reply from one of them, then the ITR =
uses the locators configured from that ETR. The system works, if it is =
misconfigured, it works less well.

So I believe the issue could be closed IMO.

Dino


From jgs@juniper.net  Wed Mar 14 07:41:16 2012
Return-Path: <jgs@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 D819E21F87F4; Wed, 14 Mar 2012 07:41:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.499
X-Spam-Level: 
X-Spam-Status: No, score=-6.499 tagged_above=-999 required=5 tests=[AWL=0.100,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rnPwkWNVU0A1; Wed, 14 Mar 2012 07:41:16 -0700 (PDT)
Received: from exprod7og111.obsmtp.com (exprod7og111.obsmtp.com [64.18.2.175]) by ietfa.amsl.com (Postfix) with ESMTP id C862921F86DC; Wed, 14 Mar 2012 07:41:14 -0700 (PDT)
Received: from P-EMHUB01-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob111.postini.com ([64.18.6.12]) with SMTP ID DSNKT2CuB7PrVbh6xX/ZhYJ5yic0xog7j5VC@postini.com; Wed, 14 Mar 2012 07:41:15 PDT
Received: from EMBX02-HQ.jnpr.net ([fe80::18fe:d666:b43e:f97e]) by P-EMHUB01-HQ.jnpr.net ([fe80::fc92:eb1:759:2c72%11]) with mapi; Wed, 14 Mar 2012 07:40:37 -0700
From: John Scudder <jgs@juniper.net>
To: "Joel M. Halpern" <jmh@joelhalpern.com>
Date: Wed, 14 Mar 2012 07:40:36 -0700
Subject: Re: [lisp] WG Review: Recharter of Locator/ID Separation Protocol (lisp)
Thread-Topic: [lisp] WG Review: Recharter of Locator/ID Separation Protocol (lisp)
Thread-Index: Ac0B8Gt+smnlt48ASum0SgXOaKipqw==
Message-ID: <7CDFAED4-30C6-4CC4-BA91-F8B34857C9B4@juniper.net>
References: <20120214222316.CF29521E800E@ietfa.amsl.com> <201202152131.q1FLVB9E028114@cichlid.raleigh.ibm.com> <EF3C34EB-C0AA-45F2-ADE0-407CEF5172DD@juniper.net> <4F3E4EDB.7070509@piuha.net> <0E0C6A25-FBA6-4E11-9E89-DEBFFCF41108@juniper.net> <4F58EB8C.1000700@piuha.net> <70EB276F-D77E-45AE-851C-AB08A8D56D0A@juniper.net> <4F5920FF.6070502@piuha.net> <CALaySJKvS5QbtXuMx7TwFiL4hdgi1cT0sYu8EJtYLD6T2yOzKQ@mail.gmail.com> <1D2FF8E9-8E60-4126-AC30-12DFDC854BC6@juniper.net> <4F5F9A44.4020600@joelhalpern.com>
In-Reply-To: <4F5F9A44.4020600@joelhalpern.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
x-exclaimer-md-config: e4081efb-6d29-443c-8708-750833aec629
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Wed, 14 Mar 2012 08:15:38 -0700
Cc: Barry Leiba <barryleiba@computer.org>, "ietf@ietf.org list" <ietf@ietf.org>, "lisp@ietf.org" <lisp@ietf.org>, "iesg@ietf.org IESG" <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Mar 2012 14:41:17 -0000

One further remark:

On Mar 13, 2012, at 3:04 PM, Joel M. Halpern wrote:
...
> It may take engineering and evaluating some cache management schemes=20
> before one can decide whether the archtiecture is a good one.
...

Agreed.

Isn't it relevant to the architecture document, that it be possible for a r=
eader to judge whether the architecture is a good one or not?

--John=

From barryleiba@gmail.com  Wed Mar 14 08:30:09 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 E631F21F862F; Wed, 14 Mar 2012 08:30:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.984
X-Spam-Level: 
X-Spam-Status: No, score=-102.984 tagged_above=-999 required=5 tests=[AWL=-0.007, 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 G-bk5V2IlO2U; Wed, 14 Mar 2012 08:30:04 -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 044EB21F871C; Wed, 14 Mar 2012 08:30:01 -0700 (PDT)
Received: by yhpp34 with SMTP id p34so2221844yhp.31 for <multiple recipients>; Wed, 14 Mar 2012 08:30:01 -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=A/hKsbHXToTiiTvyMO1zk/8V0PvtnZhFxGx2+ays9qM=; b=mb6CTmYDSSNLSIGcnwZEWnXPonM638nTFC9X3riS7jTAF6t4ratMaGRH9kVVSnAsIY kPY//A2PWLk+wS44gAt+H3h9wf55fO5fSeVKVKzc2HoBxcyARyfAw/L4ZKk5ftYuHkt7 piqkevCvG/tkDOD6QG4/jFAdBixKvZaohAQs9AKoIi7kWsqmIf67jaG5eo42hCwpDlH4 Ceh/9iYYKuz3XfKtUsnes/VOaoFN4JQEYNTie0L/EOxoXDYLJcmYc5a0UI/V+StBQbkb te1XFLPJh3cYWR/xJoyonD2AR8x6LWdglHYY9Xu1JUIULGBLoneDP9PRTR0uGMCZ3H5S pUUw==
MIME-Version: 1.0
Received: by 10.60.3.2 with SMTP id 2mr3948340oey.0.1331739001561; Wed, 14 Mar 2012 08:30:01 -0700 (PDT)
Sender: barryleiba@gmail.com
Received: by 10.60.125.37 with HTTP; Wed, 14 Mar 2012 08:30:01 -0700 (PDT)
In-Reply-To: <F8BC059E-144B-4155-B6B7-75F47EDBD45D@juniper.net>
References: <20120214222316.CF29521E800E@ietfa.amsl.com> <201202152131.q1FLVB9E028114@cichlid.raleigh.ibm.com> <EF3C34EB-C0AA-45F2-ADE0-407CEF5172DD@juniper.net> <4F3E4EDB.7070509@piuha.net> <0E0C6A25-FBA6-4E11-9E89-DEBFFCF41108@juniper.net> <4F58EB8C.1000700@piuha.net> <70EB276F-D77E-45AE-851C-AB08A8D56D0A@juniper.net> <4F5920FF.6070502@piuha.net> <CALaySJKvS5QbtXuMx7TwFiL4hdgi1cT0sYu8EJtYLD6T2yOzKQ@mail.gmail.com> <1D2FF8E9-8E60-4126-AC30-12DFDC854BC6@juniper.net> <4F5F9A44.4020600@joelhalpern.com> <7CDFAED4-30C6-4CC4-BA91-F8B34857C9B4@juniper.net> <4F60AF4D.1090506@joelhalpern.com> <CALaySJ+xPdJJKAj3m+h6cLHPev5MhbVzRb8YwBO+CE5F8AKtbw@mail.gmail.com> <F8BC059E-144B-4155-B6B7-75F47EDBD45D@juniper.net>
Date: Wed, 14 Mar 2012 11:30:01 -0400
X-Google-Sender-Auth: ZIQ2weE9InOLHI5QRL4r2TvigIA
Message-ID: <CALaySJLO+EmagVJsck3ccP5iFLDvL9H2W_Qd9PZNRpUCM2uscg@mail.gmail.com>
Subject: Re: [lisp] WG Review: Recharter of Locator/ID Separation Protocol (lisp)
From: Barry Leiba <barryleiba@computer.org>
To: John Scudder <jgs@juniper.net>
Content-Type: text/plain; charset=ISO-8859-1
Cc: "ietf@ietf.org list" <ietf@ietf.org>, "lisp@ietf.org" <lisp@ietf.org>, "iesg@ietf.org IESG" <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Mar 2012 15:30:10 -0000

> I don't think the proper analogy
> is a bathroom. Everyone knows you can build bathrooms that work, having
> seen successful examples in the past. You might instead think of a building
> which includes a perpetual motion machine [*] as a key element.

Fair enough, and now I understand where you fall on the issue.

I agree that my analogy wasn't fully to the point.  But here's the question:
Do you really think the entire discussion has to finish in order to do
a meaningful architecture?  Is it not possible for the architecture
document to have a section about <strike>perpetual-motion
machines</strike> caching that talks about the needs, the benefits,
the drawbacks, and the tradeoffs, and leaves the final design and
decisions for later?  Such a section might well explain why the
required caching is difficult, bordering on impossible to get right,
or whatever.

At this level, do we need to *resolve* the questions and all the
design points?  Or is it possible to have a useful document that helps
everyone understand the issues, while leaving many of those issues
unresolved until later?

Barry

From stbryant@cisco.com  Wed Mar 14 08:53:44 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 92E3E21F8598 for <ietf@ietfa.amsl.com>; Wed, 14 Mar 2012 08:53:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.549
X-Spam-Level: 
X-Spam-Status: No, score=-110.549 tagged_above=-999 required=5 tests=[AWL=0.050, 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 oqyHPdVrSxW9 for <ietf@ietfa.amsl.com>; Wed, 14 Mar 2012 08:53:42 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by ietfa.amsl.com (Postfix) with ESMTP id 79CB421F87BD for <ietf@ietf.org>; Wed, 14 Mar 2012 08:53:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=stbryant@cisco.com; l=568; q=dns/txt; s=iport; t=1331740421; x=1332950021; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=5ZeCyQEMO33kV41ITuHvJ+iaDehsymv2DvCB+FUtZmY=; b=QFf+TwnOGNcynBxkGarM49FWX3IaiNDWI7lZ6uvpDeJLSUGHh9eZ/Kob 1wntNam3lYLoFZCEP5lTdhM1R2Lvib+FMsv5xu9ScUbT6zyvvfRjYUymR O3QMc3dZ1fSaToY53Wg4ozdvIw8Nxbz1K/J0xzBvKgN3lfHnDMziz3E/T 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AuAFAAi+YE+Q/khM/2dsb2JhbABDsxCDHIEHggkBAQEEEgECI0ABEAsYCRYECwkDAgECAUUGDQEHAQEeh2iceIM8EJthkH4ElVaOQIECZoJm
X-IronPort-AV: E=Sophos;i="4.73,584,1325462400"; d="scan'208";a="132309135"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-1.cisco.com with ESMTP; 14 Mar 2012 15:53:40 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by ams-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id q2EFrehj015741; Wed, 14 Mar 2012 15:53:40 GMT
Received: from stbryant-mac2.local (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id q2EFrcuN026567; Wed, 14 Mar 2012 15:53:38 GMT
Message-ID: <4F60BF02.1010507@cisco.com>
Date: Wed, 14 Mar 2012 15:53:38 +0000
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: Fangyu Li <fangyuli1999@gmail.com>
Subject: Re: Last Call:<draft-betts-itu-oam-ach-code-point-03.txt>(Allocation of an Associated Channel Code Point for Use by ITU-T Ethernet based OAM) to Informational RFC
References: <CAAHpaZ=JrKVKHZ0xkK-nszFDf-ttVNoi1p9iZiWa93vKuiNxZA@mail.gmail.com>
In-Reply-To: <CAAHpaZ=JrKVKHZ0xkK-nszFDf-ttVNoi1p9iZiWa93vKuiNxZA@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: lifang@catr.cn, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Mar 2012 15:53:44 -0000

On 14/03/2012 13:36, Fangyu Li wrote:
> I support the allocation of an ACH codepoint to G.8113.1.
> For G.8113.1 had reached the technical and industry maturity to be 
> assigned a code point, the codepoint allocation from IETF should allow 
> the ITU-T to progress refinements to G.8113.1 such that it could 
> satisfy all the functional requirements defined in RFC 5860.

Please can you tell me version of the G.8113.1 text one would
need to implement to be able to seamlessly interwork with the
equipment that has already been been deployed?

- Stewart

From rjsparks@nostrum.com  Wed Mar 14 08:53:54 2012
Return-Path: <rjsparks@nostrum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C72C121F85B8; Wed, 14 Mar 2012 08:53:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.543
X-Spam-Level: 
X-Spam-Status: No, score=-102.543 tagged_above=-999 required=5 tests=[AWL=0.057, 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 zPDcSjpt-PTg; Wed, 14 Mar 2012 08:53:54 -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 8031D21F85F6; Wed, 14 Mar 2012 08:53:52 -0700 (PDT)
Received: from dn3-177.estacado.net (vicuna-alt.estacado.net [75.53.54.121]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id q2EFrpam077216 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Wed, 14 Mar 2012 10:53:51 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
Message-ID: <4F60BF0F.3030203@nostrum.com>
Date: Wed, 14 Mar 2012 10:53:51 -0500
From: Robert Sparks <rjsparks@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: ietf@ietf.org, codesprints@ietf.org, wgchairs@ietf.org
Subject: Re: Paris IETF Codesprint
References: <68346139-29F8-4B71-9CCA-6AC158C85E6F@ietf.org>
In-Reply-To: <68346139-29F8-4B71-9CCA-6AC158C85E6F@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted mechanism)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Mar 2012 15:53:54 -0000

If you are planning to join this codesprint, please make sure you've let 
us know by
adding yourself to this page:
<http://trac.tools.ietf.org/tools/ietfdb/wiki/IETF83SprintSignUp>
so we can provision correctly.

If you've not thought about the codesprint, take a couple of minutes now 
to look over
the kinds of things we're planning to work on:
<http://trac.tools.ietf.org/tools/ietfdb/wiki/EnhancementIdeas>
Please add to that list if there's something important to you that you 
see missing.
If see something there you'd really like to have, please join us and 
make it happen.

RjS

On 1/15/12 2:12 PM, IETF Chair wrote:
> Paris IETF Codesprint
>
> When:  Saturday, 24 March 2012, starting at 9:30 AM
>
> Where: IETF Hotel
>
> What:  A bunch of hackers get together to work on code for the IETF.
>      All code will become part of the open source IETF tools.
>
> Who:   Hopefully you can help
>
> Many of the results of previous codesprint activities are being
> used every day by the IETF community.  Shortly before the Paris
> meeting, we will transition from the current database schema to a
> new one.  We believe that the new schema will make many tasks
> much easier.  No doubt, the transition will uncover new bugs.
> Work to polish or improve existing tools, fix bugs, or make new
> tools.  All efforts are appreciated and most welcome.
>
> Steve Conte will be helping with advance planning.  Henrik Levkowetz
> will be coordinating the event in Paris.  You can find more information
> here:
>
>   http://trac.tools.ietf.org/tools/ietfdb/wiki/IETF83Sprint
>
> If you are able to participate, please sign up on the wiki at:
>
>   http://trac.tools.ietf.org/tools/ietfdb/wiki/IETF83SprintSignUp
>
> Please support the tools development effort,
>   Russ
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf

From warren@kumari.net  Wed Mar 14 10:06:23 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 0B67221F8803 for <ietf@ietfa.amsl.com>; Wed, 14 Mar 2012 10:06:23 -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 8AOZHAwA7IqH for <ietf@ietfa.amsl.com>; Wed, 14 Mar 2012 10:06:18 -0700 (PDT)
Received: from vimes.kumari.net (vimes.kumari.net [198.186.192.250]) by ietfa.amsl.com (Postfix) with ESMTP id 5480B21F8733 for <ietf@ietf.org>; Wed, 14 Mar 2012 10:06:13 -0700 (PDT)
Received: from [10.196.208.139] (unknown [199.91.193.1]) by vimes.kumari.net (Postfix) with ESMTPSA id 08AD11B403ED; Wed, 14 Mar 2012 13:06:11 -0400 (EDT)
Subject: Re: [IETF] Re: shared address space... a reality!
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=windows-1252
From: Warren Kumari <warren@kumari.net>
In-Reply-To: <CAL9jLaYxW=pkmCcrKU3qoFCu1sGde918tGuf3YubQ2x-O12D1A@mail.gmail.com>
Date: Wed, 14 Mar 2012 11:06:10 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <12C2889B-FC98-45D4-B8D2-461E7F59047C@kumari.net>
References: <CAL9jLaZyPBDaGyom4Qrdt+TfzBONftH_Zxtjp1MfiH3tBLXejA@mail.gmail.com> <20120314074707.GZ16111@besserwisser.org> <CAKFn1SEGpUSyTnM5kOFT9J=y1AbXDLxti7g-KGKk7dXFWyfNwg@mail.gmail.com> <CAL9jLaYxW=pkmCcrKU3qoFCu1sGde918tGuf3YubQ2x-O12D1A@mail.gmail.com>
To: Christopher Morrow <morrowc.lists@gmail.com>
X-Mailer: Apple Mail (2.1084)
Cc: =?iso-8859-1?Q?M=E5ns_Nilsson?= <mansaxel@besserwisser.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, 14 Mar 2012 17:06:23 -0000

On Mar 14, 2012, at 8:36 AM, Christopher Morrow wrote:

> 2012/3/14 Roger J=F8rgensen <rogerj@gmail.com>:
>=20
>> This is really "good" news for some people, that already have address
>> conflict within RFC1918 and don't want to get public address space :p
>=20
> you mean every enterprise on the planet? (or probably 99.999%)
>=20


Don't forget consumers -- I have renumbered some of my home network to =
use this=85

It just solved a problem that I didn't have=85

W


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






From jnc@mercury.lcs.mit.edu  Wed Mar 14 14:30:33 2012
Return-Path: <jnc@mercury.lcs.mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 86A9B11E8080; Wed, 14 Mar 2012 14:30:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.454
X-Spam-Level: 
X-Spam-Status: No, score=-6.454 tagged_above=-999 required=5 tests=[AWL=0.145,  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 r68iWKiSzuHz; Wed, 14 Mar 2012 14:30:33 -0700 (PDT)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id DD7B411E807F; Wed, 14 Mar 2012 14:30:32 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 1419F18C0B1; Wed, 14 Mar 2012 17:30:32 -0400 (EDT)
To: ietf@ietf.org, lisp@ietf.org
Subject: Re: [lisp] WG Review: Recharter of Locator/ID Separation Protocol (lisp)
Message-Id: <20120314213032.1419F18C0B1@mercury.lcs.mit.edu>
Date: Wed, 14 Mar 2012 17:30:32 -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: Wed, 14 Mar 2012 21:30:33 -0000

    > From: John Scudder <jgs@juniper.net>

    > On Mar 13, 2012, at 3:04 PM, Joel M. Halpern wrote:

    >> It may take engineering and evaluating some cache management
    >> schemes

    > Isn't it relevant to the architecture document, that it be possible
    > for a reader to judge whether the architecture is a good one or not?

Yes and no.

At the _architectural_ level, the details of the algorithms are not
generally visible - and, more importantly, as explained below, in a 'good'
architecture, it's _designed_ so that algorithms can be changed. (As
Corbato so neatly put it in his Multics design paper, without the ability
to change course, one has a boat without a rudder.) So in one sense, no,
it's not an 'architectural' issue.

However, an architecture might be a failure if there is _no possible_
algorithm which can perform a certain required function. But that
condition is awfully hard to ascertain (it's hard to prove a negative).


For some insight into this, look at TCP: _could_ you say, looking at the
TCP specs circa 1977, that it was "[architecturally] a good [design] or
not"?

Even more importantly, was it right to go off and build the Internet, with
the retransmission/etc algorithms we had in TCP in the late 1970s?
(Especially given that the retransmission algorithms later turned out to
be colossally wrong, leading to congestive collapse of the network about 5
years later.)

Sometimes you just gotta go build it and see what happens, and see if
smart people can figure out ways around whatever issues crop up. Not being
able to absolutely, cast-iron prove, a priori up front, that it's
feasible, is not a reasonable requirement: had we had that in place in the
late 1970s, we'd never have built the Internet.


_At an architectural level_, TCP did have one thing going for it with
regard to its algorithms: the retransmission, window management, etc,
algorithms could be replaced piece-meal (i.e. we did not have to have a
co-ordinated flag day). That really saved our bacon when it turned out
they had issues (and not just with retranmission - I actually remember
Silly Window Syndrome).

The same thing is true of the cache management algorithm(s) in the xTRs.
There's no requirement that everyone run the same one, and if the current
cache management algorithms turns out to have issues, it will be no more
hassle to change them than it was to change TCP's retransmission algorithm.

So, at the _architectural level_, LISP's cache management does have that
desirable property: we can experiment with new ones, and deploy better
ones, whenever we want. Also, some sites might have load patterns that are
different from othersm, so that we might want to run different cache
management algorithms in different places. Again, _at an architectural
level_, this turns out to be trivial to do.

	Noel

From nurit.sprecher@nsn.com  Wed Mar 14 15:43:30 2012
Return-Path: <nurit.sprecher@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 5FE9E11E8075 for <ietf@ietfa.amsl.com>; Wed, 14 Mar 2012 15:43:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.227
X-Spam-Level: 
X-Spam-Status: No, score=-6.227 tagged_above=-999 required=5 tests=[AWL=-0.228, BAYES_00=-2.599, J_CHICKENPOX_32=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tVFzWM1aV6c2 for <ietf@ietfa.amsl.com>; Wed, 14 Mar 2012 15:43:29 -0700 (PDT)
Received: from demumfd001.nsn-inter.net (demumfd001.nsn-inter.net [93.183.12.32]) by ietfa.amsl.com (Postfix) with ESMTP id CF2A521F867F for <ietf@ietf.org>; Wed, 14 Mar 2012 15:43:28 -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 q2EMhRaG007914 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 14 Mar 2012 23:43:27 +0100
Received: from DEMUEXC048.nsn-intra.net ([10.159.32.94]) by demuprx017.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id q2EMhQc2026985; Wed, 14 Mar 2012 23:43:27 +0100
Received: from DEMUEXC013.nsn-intra.net ([10.150.128.24]) by DEMUEXC048.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 14 Mar 2012 23:42:45 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [PWE3] FW: Last Call:<draft-betts-itu-oam-ach-code-point-03.txt>(Allocationof	an Associated Channel Code Point for Use byITU-T Ethernet	based OAM)to Informational RFC
Date: Wed, 14 Mar 2012 23:42:42 +0100
Message-ID: <E4873516F3FC7547BCFE792C7D94039C016C556F@DEMUEXC013.nsn-intra.net>
In-Reply-To: <4F5DB46F.10009@pi.nu>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [PWE3] FW: Last Call:<draft-betts-itu-oam-ach-code-point-03.txt>(Allocationof	an Associated Channel Code Point for Use byITU-T Ethernet	based OAM)to Informational RFC
Thread-Index: Ac0AKqpe3J8T22x9TUmU2BH82drJYwCCBuIg
References: <20120222151252.32262.82157.idtracker@ietfa.amsl.com><039f01ccf174$fe79d780$fb6d8680$@olddog.co.uk><44F4E579A764584EA9BDFD07D0CA0813075C936F@tlvmail1><4F4B7EA2.7070305@cisco.com> <4F4B8A75.6000207@pi.nu> <4F5DB46F.10009@pi.nu>
From: "Sprecher, Nurit (NSN - IL/Hod HaSharon)" <nurit.sprecher@nsn.com>
To: "ext Loa Andersson" <loa@pi.nu>, <ietf@ietf.org>
X-OriginalArrivalTime: 14 Mar 2012 22:42:45.0350 (UTC) FILETIME=[C6158860:01CD0233]
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: 10610
X-purgate-ID: 151667::1331765007-000044A2-5BBC099B/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, 14 Mar 2012 22:43:31 -0000

Loa hi,
I think your proposal is productive and provides a good basis to
progress.=20
Please see some comments inline (<Nurit>...\<Nurit>).
Best regards,
Nurit

-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
ext Loa Andersson
Sent: Monday, March 12, 2012 10:32 AM
To: ietf@ietf.org
Subject: Re: [PWE3] FW: Last
Call:<draft-betts-itu-oam-ach-code-point-03.txt>(Allocationof an
Associated Channel Code Point for Use byITU-T Ethernet based OAM)to
Informational RFC

All,

I've been asked to clarify thee comments in this mail, I done
so by proposing new text to draft-betts-.

I hope this helps.


Title
=3D=3D=3D=3D=3D

Comment: We want to assign a Associated Channel Type. The registry
that it  will be assigned from is "Pseudowire Associated Channel
Types"; however RFC 5586, makes the Channel Types generic and I
think the title should be changed as follows:

OLD:
Allocation of an Associated Channel Code Point for Use by ITU-T
Ethernet based OAM

NEW:
Allocation of an Generic Associated Channel Type for ITU-T
MPLS-TP OAM

Note: Neither MPLS-TP or OAM are in the RFC Editors list of wellknown
acronyms, therfore the title probably should be:

NEW:
Allocation of an Generic Associated Channel Type for ITU-T
MPLS Transport Profile Operation, Maintenance and Administration.


Introduction - first paragraph
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D

In the first paragraph of the introduction, there seems to be an
oddity in the description of the role of the ietf-tp-oam-analysis
document.  Instead of:

OLD
"tools defined by the IETF [I-D.ietf-mpls-tp-oam-analysis], that
are intended to meet the OAM functional requirements defined in
[RFC5860]."

NEW:
"tools described by the IETF [I-D.ietf-mpls-tp-oam-analysis], which
are used to meet the OAM functional requirements defined
in [RFC5860]."

<Nurit> should we say "described and referred by..."? \<Nurit>
<Nurit> should we say "...that satisfies the OAM functional requirements
defined in [RFC586]"?
=20
Intrduction - second paragraph
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D

The next paragraph in describing G.8113.1, stumbles over the current
vs anticipated future state of G.8113.1 and its relationship to
its antecedents.  I'm a bit un-certain about the correct terminology,
but I think the following change would improve the document.

OLD:

The ITU-T has documented, in draft new Recommendation [G.8113.1], the
use of Ethernet based OAM mechanisms, originally defined in [Y.1731],
carried in the MPLS Generic Associated Channel (G-ACh). This approach
requires the allocation of an ACH Type from the registry of ACH types
maintained by IANA in order that the messages that will be described
in [G.8113.1] can be identified by an implementation.

NEW:

"The ITU-T has Draft Recommendation [G.8113.1] documented MPLS OAM
which as of this writing is undergoing the ITU-T Traditional
Approval Process (TAP). This Recommendation builds upon Ethernet
OAM as documented in [Y.1731]. The messages in [G.8113.1] are defined
to be carried in a new Associated Channel Type in the MPLS Generaic
  Associated Channel (G-Ach).  In order to carry these messages in an
interoperable fashion, an Associated Channel Type from the IANA
maintained registry "Pseudowire Associated Channel Types is to be
used."

Note there are confusion around some of the Associated Channel
acronyms that are refledted in this document.

ACh is Associated Channel
ACH is Associated Chamnnel Header
G-ACh is Generic Associated Channel

"ACH Type" is not used anywhere in IETF documents; we talk about
Associated Channel Type or Generic Associated Channel Type
(G-ACh Type).

Introduction - third paragraph
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D

In the third paragraph, there seems to be an unnecessary reference
to experimental types.  When asking for a code point for a standard,
it is not helped to bring up experimental code space.  Can we remove
the text reading:

OLD:
"without continuing to resorting to the use of an experimental
ACH Type,"

NEW
-


Section 2 - first paragraph
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D



In section 2, the first sentence refers to Ethernet based OAM
messages. As far as I know, the messages in G.8113.1 are either
MPLS-TP OAM messages, or they are simply the OAM messages defined
in G.8113.1.  The simplest path to clarity would seem to be to
replace "Ethernet based OAM messages" in that sentence with
"messages".

The second sentence of that paragraph does not seem to say anything
we need to say.  Can we remove it?

OLD:

    The code point allocated by this document is intended to be used
only
    for Ethernet based OAM messages, defined in the ITU-T Recommendation
    [G.8113.1], carried in the G-ACh . These Ethernet based OAM messages
    and procedures, address the OAM functional requirements defined in
    [RFC5860]. Other message types should not be carried behind this
code
    point.

NEW:

    The code point allocated by this document is intended to be used
    only for OAM messages, defined in the ITU-T Recommendation
    [G.8113.1], carried in the G-ACh . Other message types should not
    be carried behind this Associated Channel Type.

<Nurit> here we should be clearer about which OAM messages we refer to.
It should be clear that these are the only ones that satisfy the
requirements of RFC 5860. I want to make sure that messages of
protection mechanisms are not included and are not hidden by the
allocated codepoint. \<Nurit>

Section 2 - second paragraph
=3D=3D=3D=3D=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 matter of some clarity, can we change this paragrap like this:

OLD:
    This code point may be used on any transport construct that uses
    the G-ACh, e.g., MPLS-TP Sections, MPLS-TP LSPs or PWs.

NEW:

    The Generic Associated Channel Type assigned by this
    document may be used on any transport construct that uses the
    G-ACh, e.g., MPLS-TP Sections, MPLS-TP LSPs or PWs as specified
    by G.8113.1.


Section 2 - third paragraph
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D

With regard to revisions, which is what I think the third paragraph
is about, I am not clear what you are trying to say.  A code point
allocation must point to a stable referent.  If the desired referent
changes, then process needs to be followed to make sure that the IANA
is updated in accordance with IETF procedures.  Hence, I am left to
the conclusion that the third paragraph is actually asking for
something we can not do.  Can we remove that?

OLD:
    All ITU-T Recommendations are subject to revisions. Therefore, the
    code point allocated by this document may be used for future
versions
    of [G.8113.1].

NEW:
    -








On 2012-02-27 14:51, Loa Andersson wrote:
> All,
>
> I agree with Stewart, while shortage of code points might be a reason
> to think twice before allocating one, "abundance" in itself is never
> a reason to allocate code points.
>
> I'm way less inclined to approve of this draft in the condition it
> is now. Actually I believe that we should think very careful before
> approving it at all.
>
> /Loa
>
> On 2012-02-27 14:01, Stewart Bryant wrote:
>>
>> Daniel
>>
>> Shortage of ACh types was never an issue.
>>
>> The issue issue is the concerns articulated in
>> draft-sprecher-mpls-tp-oam-considerations
>>
>> Stewart
>>
>>
>> On 23/02/2012 10:35, Daniel Cohn wrote:
>>> Support - as there is no foreseen shortage in ACH types, I don't see
a
>>> reason why this code point should not be allocated to an ITU
developed
>>> protocol that is already deployed in the field.
>>>
>>> DC
>>>
>>>> -----Original Message-----
>>>> From: ietf-announce-bounces@ietf.org [mailto:ietf-announce-
>>>> bounces@ietf.org] On Behalf Of The IESG
>>>> Sent: 22 February 2012 15:13
>>>> To: IETF-Announce
>>>> Subject: Last Call:<draft-betts-itu-oam-ach-code-point-03.txt>
>>> (Allocation of
>>> an
>>>> Associated Channel Code Point for Use by ITU-T Ethernet based OAM)
to
>>>> Informational RFC
>>>>
>>>>
>>>> The IESG has received a request from an individual submitter to
>>> consider
>>>> the following document:
>>>> - 'Allocation of an Associated Channel Code Point for Use by ITU-T
>>>> Ethernet based OAM'
>>>> <draft-betts-itu-oam-ach-code-point-03.txt> as an 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-03-21. 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 assigns an Associated Channel Type code point for
>>>> carrying Ethernet based Operations, Administration, and Management
>>>> messages in the MPLS Generic Associated Channel (G-ACh).
>>>>
>>>> The file can be obtained via
>>>> http://datatracker.ietf.org/doc/draft-betts-itu-oam-ach-code-point/
>>>>
>>>> IESG discussion can be tracked via
>>>> http://datatracker.ietf.org/doc/draft-betts-itu-oam-ach-code-point/
>>>>
>>>>
>>>> No IPR declarations have been submitted directly on this I-D.
>>>> _______________________________________________
>>>> IETF-Announce mailing list
>>>> IETF-Announce@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/ietf-announce
>>> _______________________________________________
>>> pwe3 mailing list
>>> pwe3@ietf.org
>>> https://www.ietf.org/mailman/listinfo/pwe3
>>> _______________________________________________
>>> Ietf mailing list
>>> Ietf@ietf.org
>>> https://www.ietf.org/mailman/listinfo/ietf
>>>
>>
>>
>

--=20


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

From housley@vigilsec.com  Wed Mar 14 16:46:20 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 1235011E8094 for <ietf@ietfa.amsl.com>; Wed, 14 Mar 2012 16:46:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[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 jETVjgHvcCub for <ietf@ietfa.amsl.com>; Wed, 14 Mar 2012 16:46:19 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id 611F411E808E for <ietf@ietf.org>; Wed, 14 Mar 2012 16:46:19 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 00B929A471B for <ietf@ietf.org>; Wed, 14 Mar 2012 19:46:29 -0400 (EDT)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([208.254.26.82]) by localhost (ronin.smetech.net [208.254.26.81]) (amavisd-new, port 10024) with ESMTP id alBtQJDHnQFo for <ietf@ietf.org>; Wed, 14 Mar 2012 19:46:09 -0400 (EDT)
Received: from [12.22.58.150] (unknown [12.22.58.150]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 762909A470F for <ietf@ietf.org>; Wed, 14 Mar 2012 19:46:27 -0400 (EDT)
From: Russ Housley <housley@vigilsec.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: Issues relating to managing a mailing list... 
Date: Wed, 14 Mar 2012 19:46:15 -0400
References: <1344A266-28E8-4228-908F-395FB41EDA83@amsl.com>
To: IETF <ietf@ietf.org>
Message-Id: <30461C26-EDCE-4BFD-8E82-AF1CC5BC371C@vigilsec.com>
Mime-Version: 1.0 (Apple Message framework v1084)
X-Mailer: Apple Mail (2.1084)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Mar 2012 23:46:20 -0000

Some suggestions have been made about the IETF mail lists.
There is a way for mailman to strip attachments and put them
in a place for downloading with a web browser.  This would be
a significant change to current practice, so the community
needs to consider this potential policy change.

What do you think?

Russ


>>>> The only bug in the soup is that it seemed to me that we might
>>>> want to look into an alternative approach.  We have asked people
>>>> to post large documents somewhere and only send a pointer.  Not
>>>> everyone can do that, lots of people forget, and some people are
>>>> just not willing to take the extra step.
>>>> 
>>>> Plus, we cannot expect people to keep things posted on their own
>>>> personal, or their company's, web-site indefinitely.  If they
>>>> don't keep it there, then the pointer in the archive will become
>>>> stale, and information that should probably be there is lost.
>>>> 
>>>> So we need a solution to the issue with really big email messages
>>>> sometime.
>>>> 
>>>> One solution might be to simpy strip attachments off, put them
>>>> in the archive and replace them with a pointer.  That shouldn't
>>>> be that hard, since a lot of anti-virus software does something
>>>> similar with suspect attachment types.
>>>> 
>>>> Or we could - once again - ask people to post attachments and use
>>>> a pointer in their mail, only provide them with a place to post
>>>> them in the same general area as the mail archive.
>>>> 
>>>> If there is already something like this in place, please let me
>>>> know what it is and I will add a pointer to it in my "too big"
>>>> rejection messages.
>>>> 
>>>> The thing about threaded messages getting too big is a slightly
>>>> different issue, brought about by the increasing use of HTML
>>>> format email.  I talked years ago about this with Scott Bradner
>>>> because I really think that HTML format messages are useful and
>>>> relatively easy to read when compared to plain old text.
>>>> 
>>>> But using HTML leads to messages that are deceptively big.
>>>> 
>>>> Possibly the right answer in that case is to bump the size limit
>>>> up to maybe 100K.  Even with HTML format, people will many likely
>>>> realize that nobody is going to read past the 10th back message
>>>> in any case (or if they do want to, they can look at the thread
>>>> in the archive).
>>>> 
>>>> But even that approach is not fool proof, and there are a lot of
>>>> resourceful fools out there.
>>>> 
>>>> Just trying to be creative, and help out...


From robert@raszuk.net  Wed Mar 14 16:56:54 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 3387A11E8083 for <ietf@ietfa.amsl.com>; Wed, 14 Mar 2012 16:56:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.524
X-Spam-Level: 
X-Spam-Status: No, score=-2.524 tagged_above=-999 required=5 tests=[AWL=0.075,  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 ZVfUaQbYCsE6 for <ietf@ietfa.amsl.com>; Wed, 14 Mar 2012 16:56:53 -0700 (PDT)
Received: from mail1310.opentransfer.com (mail1310.opentransfer.com [76.162.254.103]) by ietfa.amsl.com (Postfix) with ESMTP id 09E2511E8075 for <ietf@ietf.org>; Wed, 14 Mar 2012 16:56:53 -0700 (PDT)
Received: (qmail 2167 invoked by uid 399); 14 Mar 2012 23:56:52 -0000
Received: from unknown (HELO ?192.168.1.57?) (pbs:robert@raszuk.net@83.9.127.245) by mail1310.opentransfer.com with ESMTPM; 14 Mar 2012 23:56:52 -0000
X-Originating-IP: 83.9.127.245
Message-ID: <4F613045.4090306@raszuk.net>
Date: Thu, 15 Mar 2012 00:56:53 +0100
From: Robert Raszuk <robert@raszuk.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: Russ Housley <housley@vigilsec.com>
Subject: Re: Issues relating to managing a mailing list...
References: <1344A266-28E8-4228-908F-395FB41EDA83@amsl.com> <30461C26-EDCE-4BFD-8E82-AF1CC5BC371C@vigilsec.com>
In-Reply-To: <30461C26-EDCE-4BFD-8E82-AF1CC5BC371C@vigilsec.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: 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: Wed, 14 Mar 2012 23:56:54 -0000

Hello Russ,

IMHO this is a great idea and I fully support it's deployment asap. It 
is well overdue one too not only in IETF but in many other mailing lists 
in the community.

--

The only few maybe too detailed at this point questions:

- what would be (if not infinity) the expiration data of such attachment 
repository ?

- what would be the automated interface to periodically sync such 
repository on a per WG group to a local space ?

- would email contain full link or just a url short cut ?

- would the document as attachments be google indexed and fully searchable ?

- what attachment formats would be supported ?

Regards,
R.

> Some suggestions have been made about the IETF mail lists.
> There is a way for mailman to strip attachments and put them
> in a place for downloading with a web browser.  This would be
> a significant change to current practice, so the community
> needs to consider this potential policy change.
>
> What do you think?
>
> Russ

From ned+ietf@mauve.mrochek.com  Wed Mar 14 17:44:47 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 3CD5321F86A7 for <ietf@ietfa.amsl.com>; Wed, 14 Mar 2012 17:44:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.586
X-Spam-Level: 
X-Spam-Status: No, score=-2.586 tagged_above=-999 required=5 tests=[AWL=0.013,  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 iHJQn1aFWT8T for <ietf@ietfa.amsl.com>; Wed, 14 Mar 2012 17:44:46 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id CE4FA21F8527 for <ietf@ietf.org>; Wed, 14 Mar 2012 17:44:45 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OD44N1QF4W00596Y@mauve.mrochek.com> for ietf@ietf.org; Wed, 14 Mar 2012 17:44:42 -0700 (PDT)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OCPMUVDUMO00ZUIL@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Wed, 14 Mar 2012 17:44:36 -0700 (PDT)
From: ned+ietf@mauve.mrochek.com
Message-id: <01OD44MYQ1ZY00ZUIL@mauve.mrochek.com>
Date: Wed, 14 Mar 2012 17:33:20 -0700 (PDT)
Subject: Re: Issues relating to managing a mailing list...
In-reply-to: "Your message dated Wed, 14 Mar 2012 19:46:15 -0400" <30461C26-EDCE-4BFD-8E82-AF1CC5BC371C@vigilsec.com>
MIME-version: 1.0
Content-type: TEXT/PLAIN
References: <1344A266-28E8-4228-908F-395FB41EDA83@amsl.com> <30461C26-EDCE-4BFD-8E82-AF1CC5BC371C@vigilsec.com>
To: Russ Housley <housley@vigilsec.com>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mrochek.com; s=mauve; t=1331772285; i=@mrochek.com; bh=cy1Dq/ZlGCQ8wG99mpjUK9B8Swgl6K1IJcceO6JsF+E=;  h=From:Cc:Message-id:Date:Subject:In-reply-to:MIME-version: Content-type:References:To; b=G95G2JOFJiQscgRIuKjBw2ZBlRpimiNbNorUkyM9l6J0a1T0z/6Vk4wVlnAQUTYRI i5bX1kVOiwdZ4HgWB/WYvrjfztI0QTlgnpkPPRmXaSviGPaEvl7ZcfhMOoVf0b0rRS 6z9OvoZW1gpCnKUkQP6lCkEVzNPu+HVT7n223WpY=
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Mar 2012 00:44:47 -0000

> Some suggestions have been made about the IETF mail lists.
> There is a way for mailman to strip attachments and put them
> in a place for downloading with a web browser.  This would be
> a significant change to current practice, so the community
> needs to consider this potential policy change.

> What do you think?

Is this really a big enough problem to be worth solving? I can't recall a
single instance where I received IETF list with a problematic attachment. OTOH,
I routinely get IETF messages with useful attachements - typically a critical
revision to a draft which for whatever reason can't be posted as an I-D - that
I really need to be able see without having to bother with some indirection.
There are also times when I have access to email but no web access. What am I
supposed to do then?

This also creates significant problems for list archiving. Right now I can
easily capture the entire content of the list and preserve it for however long
I want. Do this and that becomes significantly more difficult - I have to
detect these indirections, fetch and stuff the attachments back in, because
regardless of stated policy I cannot assume that web link will be valid for as
long as I need it to be.

I also worry about the ability of mailman to actually know what an attachment
is versus a message constructed in multiple parts. And there's also the issue
of what sort of indirection it uses. Past experience with "advanced" list
manager features like this doesn't give me a whole lot of confidence in their
MIME chops.

I suppose I could live with this - but not actively support it - if the
stripping was limited to abusively large attachments - say ones over 5Mb or
thereabouts. But otherwise it's a TERRIBLE idea, and will simply result in 
everyone including the draft or whatever in the primary message text in order
to avoid this nonsense, which results in a degradation of list quality for all
concerned.

				Ned

From dwm@xpasc.com  Wed Mar 14 18:26:18 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 60AA921F86BD for <ietf@ietfa.amsl.com>; Wed, 14 Mar 2012 18:26:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.402
X-Spam-Level: 
X-Spam-Status: No, score=-5.402 tagged_above=-999 required=5 tests=[AWL=-2.803, 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 iHs6hSbpyiYs for <ietf@ietfa.amsl.com>; Wed, 14 Mar 2012 18:26:17 -0700 (PDT)
Received: from c2w3p-2.abacamail.com (c2w3p-2.abacamail.com [209.133.53.32]) by ietfa.amsl.com (Postfix) with ESMTP id E73FD21F86BB for <ietf@ietf.org>; Wed, 14 Mar 2012 18:26:17 -0700 (PDT)
Received: from xpasc.com (unknown [68.164.244.188]) by c2w3p-2.abacamail.com (Postfix) with ESMTP id 5CF683F825; Thu, 15 Mar 2012 01:26:17 +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 q2F1Q2dT008615; Wed, 14 Mar 2012 18:26:02 -0700
Date: Wed, 14 Mar 2012 18:26:02 -0700 (PDT)
From: David Morris <dwm@xpasc.com>
To: Robert Raszuk <robert@raszuk.net>
Subject: Re: Issues relating to managing a mailing list...
In-Reply-To: <4F613045.4090306@raszuk.net>
Message-ID: <Pine.LNX.4.64.1203141824440.5244@egate.xpasc.com>
References: <1344A266-28E8-4228-908F-395FB41EDA83@amsl.com> <30461C26-EDCE-4BFD-8E82-AF1CC5BC371C@vigilsec.com> <4F613045.4090306@raszuk.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-AV-Type: clean
X-AV-Accuracy: exact
X-Milter-Version: master.24-gef8a08a
X-CLX-ID: a110AD3GD2zQ1vr-2E1826H
X-CLX-Spam: false
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Mar 2012 01:26:18 -0000

Sounds like a good idea ... I'd add one more question to the list below 
... How would these attachments appear in the archive? Are they already
linked objects, must be I guess, would that change?

On Thu, 15 Mar 2012, Robert Raszuk wrote:

> Hello Russ,
> 
> IMHO this is a great idea and I fully support it's deployment asap. It is well
> overdue one too not only in IETF but in many other mailing lists in the
> community.
> 
> --
> 
> The only few maybe too detailed at this point questions:
> 
> - what would be (if not infinity) the expiration data of such attachment
> repository ?
> 
> - what would be the automated interface to periodically sync such repository
> on a per WG group to a local space ?
> 
> - would email contain full link or just a url short cut ?
> 
> - would the document as attachments be google indexed and fully searchable ?
> 
> - what attachment formats would be supported ?
> 
> Regards,
> R.
> 
> > Some suggestions have been made about the IETF mail lists.
> > There is a way for mailman to strip attachments and put them
> > in a place for downloading with a web browser.  This would be
> > a significant change to current practice, so the community
> > needs to consider this potential policy change.
> > 
> > What do you think?
> > 
> > Russ
> 

From brian.e.carpenter@gmail.com  Wed Mar 14 18:28:12 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 B7A1021F86C2 for <ietf@ietfa.amsl.com>; Wed, 14 Mar 2012 18:28:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.493
X-Spam-Level: 
X-Spam-Status: No, score=-103.493 tagged_above=-999 required=5 tests=[AWL=0.106, 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 6HEdCUfbcaXv for <ietf@ietfa.amsl.com>; Wed, 14 Mar 2012 18:28:12 -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 0D38121F86BB for <ietf@ietf.org>; Wed, 14 Mar 2012 18:28:11 -0700 (PDT)
Received: by eeke51 with SMTP id e51so1468457eek.31 for <ietf@ietf.org>; Wed, 14 Mar 2012 18:28:11 -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=r6lBCRqB7sHbaojjMRSHb43vGmhEEUpdYB9smlzxtbg=; b=Xy7+7rIUp1I/SKiOLeWtVrlLskIbvPr9SMbc1oEc3agl2M+wYSGOCRXoAKoWPXtID8 9ulHjkmA4L6bfkAxHcKGtGdc+SZ4cdoklTLxcyp6jIXyRhiy4b1MrGjzafEpgoEV4/FT QkvP4RtJoM/CYHr6RCaNNHhWFaDEq5GL5YL4fCsGD39F+/ZBrZCz1HcuKJNgzFEVj8H6 CrFLvk/ht3fv/Elj9gyG023CtPpA2SG23/3rhJkPYuzc7Fy3W4XIz4j+ObqDKH6R6EdJ 13YcV6SDwoTiPiN+f+4F9DiVywe3Uaj71Snyos3Hd/sXWMPa1pVhMZuD8KP7x38jIV7J y7hg==
Received: by 10.14.28.65 with SMTP id f41mr683808eea.23.1331774891193; Wed, 14 Mar 2012 18:28:11 -0700 (PDT)
Received: from [10.1.1.4] ([121.98.251.219]) by mx.google.com with ESMTPS id p57sm1234997eei.8.2012.03.14.18.28.07 (version=SSLv3 cipher=OTHER); Wed, 14 Mar 2012 18:28:10 -0700 (PDT)
Message-ID: <4F6145A0.3020705@gmail.com>
Date: Thu, 15 Mar 2012 14:28:00 +1300
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: ned+ietf@mauve.mrochek.com
Subject: Re: Issues relating to managing a mailing list...
References: <1344A266-28E8-4228-908F-395FB41EDA83@amsl.com>	<30461C26-EDCE-4BFD-8E82-AF1CC5BC371C@vigilsec.com> <01OD44MYQ1ZY00ZUIL@mauve.mrochek.com>
In-Reply-To: <01OD44MYQ1ZY00ZUIL@mauve.mrochek.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Mar 2012 01:28:12 -0000

On 2012-03-15 13:33, ned+ietf@mauve.mrochek.com wrote:
...
> I suppose I could live with this - but not actively support it - if the
> stripping was limited to abusively large attachments - say ones over 5Mb or
> thereabouts. 

+0.9; maybe set the limit a bit lower, for those who still have network
capacity issues. However, it would be extremely inconvenient to have small
attachments stripped.

> But otherwise it's a TERRIBLE idea, and will simply result in 
> everyone including the draft or whatever in the primary message text in order
> to avoid this nonsense, which results in a degradation of list quality for all
> concerned.

+1

    Brian

From scott@kitterman.com  Wed Mar 14 18:44:54 2012
Return-Path: <scott@kitterman.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5E8D821F84A2 for <ietf@ietfa.amsl.com>; Wed, 14 Mar 2012 18:44:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.619
X-Spam-Level: 
X-Spam-Status: No, score=-2.619 tagged_above=-999 required=5 tests=[AWL=-0.020, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 76OYy5r8rvas for <ietf@ietfa.amsl.com>; Wed, 14 Mar 2012 18:44:53 -0700 (PDT)
Received: from mailout02.controlledmail.com (mailout02.controlledmail.com [72.81.252.18]) by ietfa.amsl.com (Postfix) with ESMTP id B185121F84A1 for <ietf@ietf.org>; Wed, 14 Mar 2012 18:44:53 -0700 (PDT)
Received: from mailout02.controlledmail.com (localhost [127.0.0.1]) by mailout02.controlledmail.com (Postfix) with ESMTP id 21B9C20E40D0; Wed, 14 Mar 2012 21:44:53 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=2007-00; t=1331775893; bh=8LBacR5+gld1q5L4+v5h3Jic3a2e5YRlcJKfOP8Pw0k=; h=From:To:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version:Content-Transfer-Encoding:Content-Type; b=g9kkeAKPbzJqvPq+87HypS0o6YwIN5Rb9k6QU4rQJxhs8vWeBjHlPPx9G3XNbStqA kIASOSdcq49RdbcFqpWJmwZl1mtfSIpMKU7K8/VKNqnNyrlJIFRR6LTEIkzFrq9jqD dRpn8Up9D1bqkivULMMnm4jvhwlL6oEpM5d0tsuI=
Received: from scott-latitude-e6320.localnet (static-72-81-252-21.bltmmd.fios.verizon.net [72.81.252.21]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailout02.controlledmail.com (Postfix) with ESMTPSA id 033C220E40A3;  Wed, 14 Mar 2012 21:44:52 -0400 (EDT)
From: Scott Kitterman <scott@kitterman.com>
To: ietf@ietf.org
Subject: Re: Issues relating to managing a mailing list...
Date: Wed, 14 Mar 2012 21:44:52 -0400
Message-ID: <2103063.rDf6FqNnG2@scott-latitude-e6320>
User-Agent: KMail/4.7.3 (Linux/3.0.0-16-generic-pae; KDE/4.7.4; i686; ; )
In-Reply-To: <4F6145A0.3020705@gmail.com>
References: <1344A266-28E8-4228-908F-395FB41EDA83@amsl.com> <01OD44MYQ1ZY00ZUIL@mauve.mrochek.com> <4F6145A0.3020705@gmail.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
X-AV-Checked: ClamAV using ClamSMTP
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Mar 2012 01:44:54 -0000

On Thursday, March 15, 2012 02:28:00 PM Brian E Carpenter wrote:
> On 2012-03-15 13:33, ned+ietf@mauve.mrochek.com wrote:
> ...
> 
> > I suppose I could live with this - but not actively support it - if the
> > stripping was limited to abusively large attachments - say ones over 5Mb
> > or thereabouts.
> 
> +0.9; maybe set the limit a bit lower, for those who still have network
> capacity issues. However, it would be extremely inconvenient to have small
> attachments stripped.
> 
> > But otherwise it's a TERRIBLE idea, and will simply result in
> > everyone including the draft or whatever in the primary message text in
> > order to avoid this nonsense, which results in a degradation of list
> > quality for all concerned.
> 
> +1

+1 to it's a terrible idea.

Scott K

From ma.yuxia@zte.com.cn  Wed Mar 14 20:13:22 2012
Return-Path: <ma.yuxia@zte.com.cn>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 99EA711E8074; Wed, 14 Mar 2012 20:13:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -97.635
X-Spam-Level: 
X-Spam-Status: No, score=-97.635 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45, RCVD_DOUBLE_IP_LOOSE=0.76, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eSZPp+2pJmsG; Wed, 14 Mar 2012 20:13:21 -0700 (PDT)
Received: from mx5.zte.com.cn (mx6.zte.com.cn [95.130.199.165]) by ietfa.amsl.com (Postfix) with ESMTP id 0721711E8087; Wed, 14 Mar 2012 20:13:20 -0700 (PDT)
Received: from [10.30.17.99] by mx5.zte.com.cn with surfront esmtp id 12280301151118; Thu, 15 Mar 2012 10:40:15 +0800 (CST)
Received: from [10.30.3.20] by [192.168.168.15] with StormMail ESMTP id 65905.301151118; Thu, 15 Mar 2012 11:13:07 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse01.zte.com.cn with ESMTP id q2F3D2hi049492; Thu, 15 Mar 2012 11:13:02 +0800 (GMT-8) (envelope-from ma.yuxia@zte.com.cn)
In-Reply-To: <28D09181-4EAF-4770-963F-A57073D77AE7@vigilsec.com>
To: IETF <ietf@ietf.org>, ietf-bounces@ietf.org
Subject: Re: Re: Last Call:<draft-betts-itu-oam-ach-code-point-03.txt> (Allocation of anAssociated Channel Code Point for Use by ITU-T Ethernet basedOAM) to Informational RFC
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.5.6 March 06, 2007
Message-ID: <OF49862E95.B830CD70-ON482579C2.0010FE82-482579C2.0011AD98@zte.com.cn>
From: ma.yuxia@zte.com.cn
Date: Thu, 15 Mar 2012 11:13:01 +0800
X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 8.5.1FP4|July 25, 2010) at 2012-03-15 11:13:03, Serialize complete at 2012-03-15 11:13:03
Content-Type: multipart/alternative; boundary="=_alternative 0011AD97482579C2_="
X-MAIL: mse01.zte.com.cn q2F3D2hi049492
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Mar 2012 03:13:22 -0000

This is a multipart message in MIME format.
--=_alternative 0011AD97482579C2_=
Content-Type: text/plain; charset="GB2312"
Content-Transfer-Encoding: base64

SGkgYWxsLA0KDQpJIGFncmVlIHdpdGggUnVzcyBhbmQgc3VwcG9ydCB0aGUgYWxsb2NhdGlvbiBv
ZiBhbiBBQ0ggY29kZXBvaW50IHRvIA0KRy44MTEzLjEuDQoNCll1eGlhDQoNCg0KaWV0Zi1ib3Vu
Y2VzQGlldGYub3JnINC009ogMjAxMi0wMy0wMiAwNzo1MjowNDoNCg0KPiBOdXJpdDoNCj4gDQo+
IFNvbWUgcGVvcGxlIGFyZSB1c2luZyB0aGUgbGFjayBvZiBhIGNvZGUgcG9pbnQgYXMgdGhlIHJl
YXNvbiB0aGF0IA0KPiB0aGUgY2Fubm90IHN1cHBvcnQgdGhlIElUVS1UIGRvY3VtZW50LiAgTXkg
YXBwcm9hY2ggdGVsbHMgdGhlIElUVS1UIA0KPiB0aGF0IGEgY29kZSBwb2ludCBpcyBhdmFpbGFi
bGUgdG8gdGhlbSBJRkYgdGhleSBhcmUgYWJsZSB0byByZWFjaCANCj4gY29uc2Vuc3VzLiAgVGhl
IHJlbW92ZXMgSUVURiBmcm9tIHRoZSBkaXNjdXNzaW9uLiAgVGhpcyBjcmVhdGVzIGEgDQo+IHNp
dHVhdGlvbiB3aGVyZSBHLjgxMTMuMSBzdWNjZWVkZWQgb3IgZmFpbHMgYmFzZWQgb24gdGhlIElU
VS1UIA0KPiBtZW1iZXJzIGFjdGlvbnMsIHdpdGggbm8gZmluZ2VyIHBvaW50aW5nIGF0IHRoZSBJ
RVRGLiAgVGhpcyBpcyANCj4gY29tcGxldGVseSBhIExheWVyIDkgY29uc2lkZXJhdGlvbiwgYW5k
IGl0IGhhcyBub3RpbmcgdG8gZG8gd2l0aCB0aGUNCj4gdGVjaG5pY2FsIGNvbnRlbnQgb2YgdGhl
IGRvY3VtZW50Lg0KPiANCj4gUnVzcw0KPiANCj4gDQo+IE9uIE1hciAxLCAyMDEyLCBhdCAyOjMz
IFBNLCBTcHJlY2hlciwgTnVyaXQgKE5TTiAtIElML0hvZCBIYVNoYXJvbikgDQp3cm90ZToNCj4g
DQo+ID4gUnVzcywgDQo+ID4gSSBwcm9wb3NlIHRvIHNpbXBseSByZS1kaXNjdXNzIGl0IHdoZW4g
YW5kIElGRiBHLjgxMTMuMSBpcyBtYXR1cmUgYW5kDQo+ID4gYXBwcm92ZWQuLi4NCj4gPiBCZXN0
IHJlZ2FyZHMsDQo+ID4gTnVyaXQNCj4gPiANCj4gPiANCj4gPiAtLS0tLU9yaWdpbmFsIE1lc3Nh
Z2UtLS0tLQ0KPiA+IEZyb206IGlldGYtYm91bmNlc0BpZXRmLm9yZyBbbWFpbHRvOmlldGYtYm91
bmNlc0BpZXRmLm9yZ10gT24gQmVoYWxmIA0KT2YNCj4gPiBleHQgUnVzcyBIb3VzbGV5DQo+ID4g
U2VudDogVGh1cnNkYXksIE1hcmNoIDAxLCAyMDEyIDk6MTIgUE0NCj4gPiBUbzogSUVURg0KPiA+
IFN1YmplY3Q6IFJlOiBMYXN0IENhbGw6PGRyYWZ0LWJldHRzLWl0dS1vYW0tYWNoLWNvZGUtcG9p
bnQtMDMudHh0Pg0KPiA+IChBbGxvY2F0aW9uIG9mIGFuQXNzb2NpYXRlZCBDaGFubmVsIENvZGUg
UG9pbnQgZm9yIFVzZSBieSBJVFUtVCANCkV0aGVybmV0DQo+ID4gYmFzZWRPQU0pIHRvIEluZm9y
bWF0aW9uYWwgUkZDDQo+ID4gDQo+ID4+Pj4gUmlnaHQgbm93LCB0aGVyZSBpcyBubyBJVFUtVCBh
cHByb3ZlZCBkb2N1bWVudCB0byByZWZlcmVuY2UuDQo+ID4+Pj4gSSBhbSBjZXJ0YWlubHkgbm90
IGFuIGV4cGVydCBvbiBJVFUtVCBwcm9jZXNzLCBidXQgbXkNCj4gPj4+PiB1bmRlcnN0YW5kaW5n
IGlzIHRoYXQgZWFybGllc3QgdGhhdCB3ZSBjb3VsZCBzZWUgYW4gYXBwcm92ZWQNCj4gPj4+PiBH
LjgxMTMuMSBpcyBEZWNlbWJlciAyMDEyLiAgTXkgcG9pbnQgaXMgdGhhdCB3ZSBkb24ndCB3YW50
IHRvDQo+ID4+Pj4gYXNzaWduIGEgY29kZSBwb2ludCB1bnRpbCB0aGUgSVRVLVQgYXBwcm92ZXMg
dGhlaXIgZG9jdW1lbnQuDQo+ID4+Pj4gSG93ZXZlciwgaWYgd2UgYXJlIHdpbGxpbmcgdG8gYXNz
aWduIGEgY29kZSBwb2ludCB0byBHLjgxMTMuMQ0KPiA+Pj4+IG9uY2UgaXQgaXMgYXBwcm92ZWQs
IHRoZW4gdGhpcyB3b3VsZCBiZSBhbiBhcHByb2FjaCB3aGVyZSB0aGUNCj4gPj4+PiBjb2RlIHBv
aW50IGFzc2lnbm1lbnQgd291bGQgYmxvY2sgb24gdGhlIGFwcHJvdmFsIG9mIHRoZQ0KPiA+Pj4+
IG5vcm1hdGl2ZSByZWZlcmVuY2UuDQo+ID4+Pj4gDQo+ID4+Pj4gSSBsaWtlIHRoaXMgYXBwcm9h
Y2ggZnJvbSB0aGUgcG9saXRpY2FsIHBvaW50IG9mIHZpZXcuICBXaXRoDQo+ID4+Pj4gdGhpcyBh
cHByb2FjaCB0aGUgSUVURiB0ZWxscyB0aGUgSVRVLVQgdGhhdCBpZiBhbmQgb25seSBpZg0KPiA+
Pj4+IHRoZXkgYXJlIGFibGUgdG8gYWNoaWV2ZSBjb25zZW5zdXMgb24gRy44MTEzLjEsIHRoZW4g
YSBjb2RlDQo+ID4+Pj4gcG9pbnQgd2lsbCBiZSBhc3NpZ25lZC4NCj4gPj4+IEZXSVcsIHRoaXMg
c2VlbXMgZW50aXJlbHkgYXBwcm9wcmlhdGUgdG8gbWUuICBJZiB3ZSBkbyBpdCB0aGlzDQo+ID4+
PiB3YXksIEkgdGhpbmsgaXQgaXMgaW1wb3J0YW50IHRvIG5vdGUgLS1mb3IgdGhlIGJlbmVmaXQg
b2YgdGhvc2UNCj4gPj4+IG1vcmUgaGlzdG9yaWNhbGx5IGludm9sdmVkIHdpdGggdGhlIElUVSBh
bmQgb3RoZXJzLS0gdGhhdCB3ZQ0KPiA+Pj4gcm91dGluZWx5IGJsb2NrIG91ciBvd24gZG9jdW1l
bnRzIG9uIG5vcm1hdGl2ZSByZWZlcmVuY2VzIHRvDQo+ID4+PiB3b3JrIHRoYXQgaXMgc3RpbGwg
aW4gcHJvZ3Jlc3MgYW5kLCB1c3VhbGx5LCBkbyBub3QgZG8gcmVsYXRlZA0KPiA+Pj4gY29kZSBw
b2ludCBhbGxvY2F0aW9ucyB1bnRpbCB0aGUgYmxvY2tpbmcgcmVmZXJlbmNlZCBkb2N1bWVudHMN
Cj4gPj4+IGFyZSByZWFkeS4gIE9uY2UgdGhlIHByZXNlbnQgSS1EIGlzIGp1ZGdlZCB0byBiZSBz
dWZmaWNpZW50bHkNCj4gPj4+IHJlYWR5LCB0aGlzIGFwcHJvYWNoIHdvdWxkIHRoZXJlZm9yZSBi
ZSBJRVRGIGFwcHJvdmFsIGFuZCBhDQo+ID4+PiBmb3JtYWwgZ3VhcmFudGVlIHRvIHRoZSBJVFUg
dGhhdCBhIGNvZGUgcG9pbnQgd2lsbCBiZSBhbGxvY2F0ZWQNCj4gPj4+IGlmIGFuIHdoZW4gRy44
MTEzLjEgaXMgYXBwcm92ZWQgYW5kIHB1Ymxpc2hlZCwgYnV0IG5vdA0KPiA+Pj4gYXNzaWdubWVu
dCBvZiB0aGF0IGNvZGUgcG9pbnQgdW50aWwgdGhlIHJlZmVyZW5jZWQgYmFzZSBkb2N1bWVudA0K
PiA+Pj4gaXMgZmluaXNoZWQuDQo+ID4+PiANCj4gPj4+IENvbXBsZXRlbHkgbm9ybWFsIHByb2Nl
ZHVyYWxseS4NCj4gPj4+IA0KPiA+PiBUbyBiZSBjbGVhciBKb2huIG91ciBub3JtYWwgcmVxdWly
ZW1lbnQgd291bGQgYmUgdGhhdCB0aGUNCj4gPj4gdGVjaG5pY2FsIGNvbW11bml0eSBhY2hpZXZl
ZCBjb25zZW5zdXMgdGhhdCB0aGUgYmFzZSBkb2N1bWVudA0KPiA+PiB3YXMgcmVhZHkuIEkgaGF2
ZSBuZXZlciBzZWVuIElUVS1UIGNvbnNlbnN1cyBvbiB0aGUgY29udGVudHMNCj4gPj4gb2YgRy44
MTEzLjEgYXQgYW55IG1lZXRpbmcgdGhhdCBJIGhhdmUgb2JzZXJ2ZWQuIFdoYXQgaW4geW91cg0K
PiA+PiB2aWV3IGlzIHRoZSBjcml0ZXJpYSBmb3IgZGV0ZXJtaW5pbmcgdGhhdCAgRy44MTEzLjEg
aGFzIGFjaGlldmVkDQo+ID4+IGNvbnNlbnN1cz8NCj4gPiANCj4gPiANCj4gPiBUaGlzIGlzIG5v
dCBhbiBJRVRGIHByb2JsZW0sIGFuZCBJIGRvIG5vdCB0aGluayB0aGF0IHRoZSBJRVRGIG91Z2h0
IHRvDQo+ID4gYmUgZGlzY3Vzc2luZyB0aGUgaW50ZXJuYWwgd29ya2luZ3Mgb2YgdGhlIElUVS1U
IHByb2Nlc3MuICBUaGUgcG9pbnQgDQppcw0KPiA+IHRvIGNvbWUgdXAgd2l0aCBhIG1lY2hhbmlz
bSB0aGF0IGFsbG93cyB0aGUgY29kZSBwb2ludCB0byBiZSBhc3NpZ25lZCANCmlmDQo+ID4gYW5k
IG9ubHkgaWYgdGhlIElUVS1UIGRvZXMgY29tZSB0byBhIGNvbnNlbnN1cyBieSB3aGF0ZXZlciBt
ZWFucyBpcw0KPiA+IGFsbG93ZWQgYnkgdGhlaXIgb3duIHByb2Nlc3MuDQo+ID4gDQo+ID4gUnVz
cw0KPiA+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+
ID4gSWV0ZiBtYWlsaW5nIGxpc3QNCj4gPiBJZXRmQGlldGYub3JnDQo+ID4gaHR0cHM6Ly93d3cu
aWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9pZXRmDQo+IA0KPiBfX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPiBJZXRmIG1haWxpbmcgbGlzdA0KPiBJZXRm
QGlldGYub3JnDQo+IGh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vaWV0Zg0K
PiANCg0K
--=_alternative 0011AD97482579C2_=
Content-Type: text/html; charset="GB2312"
Content-Transfer-Encoding: base64

DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPkhpIGFsbCw8L2ZvbnQ+DQo8YnI+
DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPkkgYWdyZWUgd2l0aCBSdXNzIGFu
ZCBzdXBwb3J0IHRoZSBhbGxvY2F0aW9uDQpvZiBhbiBBQ0ggY29kZXBvaW50IHRvIEcuODExMy4x
LjwvZm9udD4NCjxicj4NCjxicj48Zm9udCBzaXplPTIgZmFjZT0ic2Fucy1zZXJpZiI+WXV4aWE8
L2ZvbnQ+DQo8YnI+DQo8YnI+DQo8YnI+PHR0Pjxmb250IHNpemU9Mj5pZXRmLWJvdW5jZXNAaWV0
Zi5vcmcg0LTT2iAyMDEyLTAzLTAyIDA3OjUyOjA0Ojxicj4NCjxicj4NCiZndDsgTnVyaXQ6PGJy
Pg0KJmd0OyA8YnI+DQomZ3Q7IFNvbWUgcGVvcGxlIGFyZSB1c2luZyB0aGUgbGFjayBvZiBhIGNv
ZGUgcG9pbnQgYXMgdGhlIHJlYXNvbiB0aGF0DQo8YnI+DQomZ3Q7IHRoZSBjYW5ub3Qgc3VwcG9y
dCB0aGUgSVRVLVQgZG9jdW1lbnQuICZuYnNwO015IGFwcHJvYWNoIHRlbGxzIHRoZQ0KSVRVLVQg
PGJyPg0KJmd0OyB0aGF0IGEgY29kZSBwb2ludCBpcyBhdmFpbGFibGUgdG8gdGhlbSBJRkYgdGhl
eSBhcmUgYWJsZSB0byByZWFjaA0KPGJyPg0KJmd0OyBjb25zZW5zdXMuICZuYnNwO1RoZSByZW1v
dmVzIElFVEYgZnJvbSB0aGUgZGlzY3Vzc2lvbi4gJm5ic3A7VGhpcw0KY3JlYXRlcyBhIDxicj4N
CiZndDsgc2l0dWF0aW9uIHdoZXJlIEcuODExMy4xIHN1Y2NlZWRlZCBvciBmYWlscyBiYXNlZCBv
biB0aGUgSVRVLVQgPGJyPg0KJmd0OyBtZW1iZXJzIGFjdGlvbnMsIHdpdGggbm8gZmluZ2VyIHBv
aW50aW5nIGF0IHRoZSBJRVRGLiAmbmJzcDtUaGlzIGlzDQo8YnI+DQomZ3Q7IGNvbXBsZXRlbHkg
YSBMYXllciA5IGNvbnNpZGVyYXRpb24sIGFuZCBpdCBoYXMgbm90aW5nIHRvIGRvIHdpdGggdGhl
PGJyPg0KJmd0OyB0ZWNobmljYWwgY29udGVudCBvZiB0aGUgZG9jdW1lbnQuPGJyPg0KJmd0OyA8
YnI+DQomZ3Q7IFJ1c3M8YnI+DQomZ3Q7IDxicj4NCiZndDsgPGJyPg0KJmd0OyBPbiBNYXIgMSwg
MjAxMiwgYXQgMjozMyBQTSwgU3ByZWNoZXIsIE51cml0IChOU04gLSBJTC9Ib2QgSGFTaGFyb24p
DQp3cm90ZTo8YnI+DQomZ3Q7IDxicj4NCiZndDsgJmd0OyBSdXNzLCA8YnI+DQomZ3Q7ICZndDsg
SSBwcm9wb3NlIHRvIHNpbXBseSByZS1kaXNjdXNzIGl0IHdoZW4gYW5kIElGRiBHLjgxMTMuMSBp
cyBtYXR1cmUNCmFuZDxicj4NCiZndDsgJmd0OyBhcHByb3ZlZC4uLjxicj4NCiZndDsgJmd0OyBC
ZXN0IHJlZ2FyZHMsPGJyPg0KJmd0OyAmZ3Q7IE51cml0PGJyPg0KJmd0OyAmZ3Q7IDxicj4NCiZn
dDsgJmd0OyA8YnI+DQomZ3Q7ICZndDsgLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS08YnI+DQom
Z3Q7ICZndDsgRnJvbTogaWV0Zi1ib3VuY2VzQGlldGYub3JnIFttYWlsdG86aWV0Zi1ib3VuY2Vz
QGlldGYub3JnXSBPbg0KQmVoYWxmIE9mPGJyPg0KJmd0OyAmZ3Q7IGV4dCBSdXNzIEhvdXNsZXk8
YnI+DQomZ3Q7ICZndDsgU2VudDogVGh1cnNkYXksIE1hcmNoIDAxLCAyMDEyIDk6MTIgUE08YnI+
DQomZ3Q7ICZndDsgVG86IElFVEY8YnI+DQomZ3Q7ICZndDsgU3ViamVjdDogUmU6IExhc3QgQ2Fs
bDombHQ7ZHJhZnQtYmV0dHMtaXR1LW9hbS1hY2gtY29kZS1wb2ludC0wMy50eHQmZ3Q7PGJyPg0K
Jmd0OyAmZ3Q7IChBbGxvY2F0aW9uIG9mIGFuQXNzb2NpYXRlZCBDaGFubmVsIENvZGUgUG9pbnQg
Zm9yIFVzZSBieSBJVFUtVA0KRXRoZXJuZXQ8YnI+DQomZ3Q7ICZndDsgYmFzZWRPQU0pIHRvIElu
Zm9ybWF0aW9uYWwgUkZDPGJyPg0KJmd0OyAmZ3Q7IDxicj4NCiZndDsgJmd0OyZndDsmZ3Q7Jmd0
OyBSaWdodCBub3csIHRoZXJlIGlzIG5vIElUVS1UIGFwcHJvdmVkIGRvY3VtZW50IHRvDQpyZWZl
cmVuY2UuPGJyPg0KJmd0OyAmZ3Q7Jmd0OyZndDsmZ3Q7IEkgYW0gY2VydGFpbmx5IG5vdCBhbiBl
eHBlcnQgb24gSVRVLVQgcHJvY2VzcywgYnV0DQpteTxicj4NCiZndDsgJmd0OyZndDsmZ3Q7Jmd0
OyB1bmRlcnN0YW5kaW5nIGlzIHRoYXQgZWFybGllc3QgdGhhdCB3ZSBjb3VsZCBzZWUNCmFuIGFw
cHJvdmVkPGJyPg0KJmd0OyAmZ3Q7Jmd0OyZndDsmZ3Q7IEcuODExMy4xIGlzIERlY2VtYmVyIDIw
MTIuICZuYnNwO015IHBvaW50IGlzIHRoYXQNCndlIGRvbid0IHdhbnQgdG88YnI+DQomZ3Q7ICZn
dDsmZ3Q7Jmd0OyZndDsgYXNzaWduIGEgY29kZSBwb2ludCB1bnRpbCB0aGUgSVRVLVQgYXBwcm92
ZXMgdGhlaXINCmRvY3VtZW50Ljxicj4NCiZndDsgJmd0OyZndDsmZ3Q7Jmd0OyBIb3dldmVyLCBp
ZiB3ZSBhcmUgd2lsbGluZyB0byBhc3NpZ24gYSBjb2RlIHBvaW50DQp0byBHLjgxMTMuMTxicj4N
CiZndDsgJmd0OyZndDsmZ3Q7Jmd0OyBvbmNlIGl0IGlzIGFwcHJvdmVkLCB0aGVuIHRoaXMgd291
bGQgYmUgYW4gYXBwcm9hY2gNCndoZXJlIHRoZTxicj4NCiZndDsgJmd0OyZndDsmZ3Q7Jmd0OyBj
b2RlIHBvaW50IGFzc2lnbm1lbnQgd291bGQgYmxvY2sgb24gdGhlIGFwcHJvdmFsDQpvZiB0aGU8
YnI+DQomZ3Q7ICZndDsmZ3Q7Jmd0OyZndDsgbm9ybWF0aXZlIHJlZmVyZW5jZS48YnI+DQomZ3Q7
ICZndDsmZ3Q7Jmd0OyZndDsgPGJyPg0KJmd0OyAmZ3Q7Jmd0OyZndDsmZ3Q7IEkgbGlrZSB0aGlz
IGFwcHJvYWNoIGZyb20gdGhlIHBvbGl0aWNhbCBwb2ludCBvZg0Kdmlldy4gJm5ic3A7V2l0aDxi
cj4NCiZndDsgJmd0OyZndDsmZ3Q7Jmd0OyB0aGlzIGFwcHJvYWNoIHRoZSBJRVRGIHRlbGxzIHRo
ZSBJVFUtVCB0aGF0IGlmIGFuZA0Kb25seSBpZjxicj4NCiZndDsgJmd0OyZndDsmZ3Q7Jmd0OyB0
aGV5IGFyZSBhYmxlIHRvIGFjaGlldmUgY29uc2Vuc3VzIG9uIEcuODExMy4xLCB0aGVuDQphIGNv
ZGU8YnI+DQomZ3Q7ICZndDsmZ3Q7Jmd0OyZndDsgcG9pbnQgd2lsbCBiZSBhc3NpZ25lZC48YnI+
DQomZ3Q7ICZndDsmZ3Q7Jmd0OyBGV0lXLCB0aGlzIHNlZW1zIGVudGlyZWx5IGFwcHJvcHJpYXRl
IHRvIG1lLiAmbmJzcDtJZg0Kd2UgZG8gaXQgdGhpczxicj4NCiZndDsgJmd0OyZndDsmZ3Q7IHdh
eSwgSSB0aGluayBpdCBpcyBpbXBvcnRhbnQgdG8gbm90ZSAtLWZvciB0aGUgYmVuZWZpdA0Kb2Yg
dGhvc2U8YnI+DQomZ3Q7ICZndDsmZ3Q7Jmd0OyBtb3JlIGhpc3RvcmljYWxseSBpbnZvbHZlZCB3
aXRoIHRoZSBJVFUgYW5kIG90aGVycy0tDQp0aGF0IHdlPGJyPg0KJmd0OyAmZ3Q7Jmd0OyZndDsg
cm91dGluZWx5IGJsb2NrIG91ciBvd24gZG9jdW1lbnRzIG9uIG5vcm1hdGl2ZSByZWZlcmVuY2Vz
DQp0bzxicj4NCiZndDsgJmd0OyZndDsmZ3Q7IHdvcmsgdGhhdCBpcyBzdGlsbCBpbiBwcm9ncmVz
cyBhbmQsIHVzdWFsbHksIGRvIG5vdCBkbw0KcmVsYXRlZDxicj4NCiZndDsgJmd0OyZndDsmZ3Q7
IGNvZGUgcG9pbnQgYWxsb2NhdGlvbnMgdW50aWwgdGhlIGJsb2NraW5nIHJlZmVyZW5jZWQNCmRv
Y3VtZW50czxicj4NCiZndDsgJmd0OyZndDsmZ3Q7IGFyZSByZWFkeS4gJm5ic3A7T25jZSB0aGUg
cHJlc2VudCBJLUQgaXMganVkZ2VkIHRvIGJlDQpzdWZmaWNpZW50bHk8YnI+DQomZ3Q7ICZndDsm
Z3Q7Jmd0OyByZWFkeSwgdGhpcyBhcHByb2FjaCB3b3VsZCB0aGVyZWZvcmUgYmUgSUVURiBhcHBy
b3ZhbA0KYW5kIGE8YnI+DQomZ3Q7ICZndDsmZ3Q7Jmd0OyBmb3JtYWwgZ3VhcmFudGVlIHRvIHRo
ZSBJVFUgdGhhdCBhIGNvZGUgcG9pbnQgd2lsbCBiZQ0KYWxsb2NhdGVkPGJyPg0KJmd0OyAmZ3Q7
Jmd0OyZndDsgaWYgYW4gd2hlbiBHLjgxMTMuMSBpcyBhcHByb3ZlZCBhbmQgcHVibGlzaGVkLCBi
dXQgbm90PGJyPg0KJmd0OyAmZ3Q7Jmd0OyZndDsgYXNzaWdubWVudCBvZiB0aGF0IGNvZGUgcG9p
bnQgdW50aWwgdGhlIHJlZmVyZW5jZWQgYmFzZQ0KZG9jdW1lbnQ8YnI+DQomZ3Q7ICZndDsmZ3Q7
Jmd0OyBpcyBmaW5pc2hlZC48YnI+DQomZ3Q7ICZndDsmZ3Q7Jmd0OyA8YnI+DQomZ3Q7ICZndDsm
Z3Q7Jmd0OyBDb21wbGV0ZWx5IG5vcm1hbCBwcm9jZWR1cmFsbHkuPGJyPg0KJmd0OyAmZ3Q7Jmd0
OyZndDsgPGJyPg0KJmd0OyAmZ3Q7Jmd0OyBUbyBiZSBjbGVhciBKb2huIG91ciBub3JtYWwgcmVx
dWlyZW1lbnQgd291bGQgYmUgdGhhdCB0aGU8YnI+DQomZ3Q7ICZndDsmZ3Q7IHRlY2huaWNhbCBj
b21tdW5pdHkgYWNoaWV2ZWQgY29uc2Vuc3VzIHRoYXQgdGhlIGJhc2UgZG9jdW1lbnQ8YnI+DQom
Z3Q7ICZndDsmZ3Q7IHdhcyByZWFkeS4gSSBoYXZlIG5ldmVyIHNlZW4gSVRVLVQgY29uc2Vuc3Vz
IG9uIHRoZSBjb250ZW50czxicj4NCiZndDsgJmd0OyZndDsgb2YgRy44MTEzLjEgYXQgYW55IG1l
ZXRpbmcgdGhhdCBJIGhhdmUgb2JzZXJ2ZWQuIFdoYXQgaW4NCnlvdXI8YnI+DQomZ3Q7ICZndDsm
Z3Q7IHZpZXcgaXMgdGhlIGNyaXRlcmlhIGZvciBkZXRlcm1pbmluZyB0aGF0ICZuYnNwO0cuODEx
My4xDQpoYXMgYWNoaWV2ZWQ8YnI+DQomZ3Q7ICZndDsmZ3Q7IGNvbnNlbnN1cz88YnI+DQomZ3Q7
ICZndDsgPGJyPg0KJmd0OyAmZ3Q7IDxicj4NCiZndDsgJmd0OyBUaGlzIGlzIG5vdCBhbiBJRVRG
IHByb2JsZW0sIGFuZCBJIGRvIG5vdCB0aGluayB0aGF0IHRoZSBJRVRGDQpvdWdodCB0bzxicj4N
CiZndDsgJmd0OyBiZSBkaXNjdXNzaW5nIHRoZSBpbnRlcm5hbCB3b3JraW5ncyBvZiB0aGUgSVRV
LVQgcHJvY2Vzcy4gJm5ic3A7VGhlDQpwb2ludCBpczxicj4NCiZndDsgJmd0OyB0byBjb21lIHVw
IHdpdGggYSBtZWNoYW5pc20gdGhhdCBhbGxvd3MgdGhlIGNvZGUgcG9pbnQgdG8gYmUNCmFzc2ln
bmVkIGlmPGJyPg0KJmd0OyAmZ3Q7IGFuZCBvbmx5IGlmIHRoZSBJVFUtVCBkb2VzIGNvbWUgdG8g
YSBjb25zZW5zdXMgYnkgd2hhdGV2ZXIgbWVhbnMNCmlzPGJyPg0KJmd0OyAmZ3Q7IGFsbG93ZWQg
YnkgdGhlaXIgb3duIHByb2Nlc3MuPGJyPg0KJmd0OyAmZ3Q7IDxicj4NCiZndDsgJmd0OyBSdXNz
PGJyPg0KJmd0OyAmZ3Q7IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fPGJyPg0KJmd0OyAmZ3Q7IElldGYgbWFpbGluZyBsaXN0PGJyPg0KJmd0OyAmZ3Q7IEll
dGZAaWV0Zi5vcmc8YnI+DQomZ3Q7ICZndDsgaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9s
aXN0aW5mby9pZXRmPGJyPg0KJmd0OyA8YnI+DQomZ3Q7IF9fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fPGJyPg0KJmd0OyBJZXRmIG1haWxpbmcgbGlzdDxicj4N
CiZndDsgSWV0ZkBpZXRmLm9yZzxicj4NCiZndDsgaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1h
bi9saXN0aW5mby9pZXRmPGJyPg0KJmd0OyA8YnI+DQo8L2ZvbnQ+PC90dD4NCg==
--=_alternative 0011AD97482579C2_=--


From john-ietf@jck.com  Wed Mar 14 20:48:14 2012
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C5AE211E8075 for <ietf@ietfa.amsl.com>; Wed, 14 Mar 2012 20:48:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.759
X-Spam-Level: 
X-Spam-Status: No, score=-102.759 tagged_above=-999 required=5 tests=[AWL=-0.160, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id N-AoU4UJuAmI for <ietf@ietfa.amsl.com>; Wed, 14 Mar 2012 20:48:14 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 4757211E8074 for <ietf@ietf.org>; Wed, 14 Mar 2012 20:48:14 -0700 (PDT)
Received: from [198.252.137.7] (helo=PST.JCK.COM) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1S81b2-00006H-Eb; Wed, 14 Mar 2012 23:43:24 -0400
Date: Wed, 14 Mar 2012 23:48:08 -0400
From: John C Klensin <john-ietf@jck.com>
To: Scott Kitterman <scott@kitterman.com>, ietf@ietf.org
Subject: Re: Issues relating to managing a mailing list...
Message-ID: <39AB1CE59499893A8E276552@PST.JCK.COM>
In-Reply-To: <2103063.rDf6FqNnG2@scott-latitude-e6320>
References: <1344A266-28E8-4228-908F-395FB41EDA83@amsl.com> <01OD44MYQ1ZY00ZUIL@mauve.mrochek.com> <4F6145A0.3020705@gmail.com> <2103063.rDf6FqNnG2@scott-latitude-e6320>
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, 15 Mar 2012 03:48:14 -0000

--On Wednesday, March 14, 2012 21:44 -0400 Scott Kitterman
<scott@kitterman.com> wrote:

>...
>> > But otherwise it's a TERRIBLE idea, and will simply result
>> > in everyone including the draft or whatever in the primary
>> > message text in order to avoid this nonsense, which results
>> > in a degradation of list quality for all concerned.
>> 
>> +1
> 
> +1 to it's a terrible idea.

Let me add to the reasons the observation that there are still
some of us who read IETF mailing lists on airplanes or in other
environments with limited, expensive, or zero connectivity.  If
everything is in the email message then downloading messages
with POP3 or synchronizing a local ("offline") copy with IMAP is
easy and easy to automate.  No need to read those messages at
all before heading for the airport (or whatever).  If some
messages have important stuff in URL references, it creates a
nightmare because the only way to find those is to skim all the
messages before departure.

Terrible, terrible, idea with a high likelihood of a significant
reduction in productivity.

    john




From rcallon@juniper.net  Wed Mar 14 21:01:31 2012
Return-Path: <rcallon@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 E5A4011E8093 for <ietf@ietfa.amsl.com>; Wed, 14 Mar 2012 21:01:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.582
X-Spam-Level: 
X-Spam-Status: No, score=-106.582 tagged_above=-999 required=5 tests=[AWL=0.017, 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 vUJI7O+AYN4Y for <ietf@ietfa.amsl.com>; Wed, 14 Mar 2012 21:01:31 -0700 (PDT)
Received: from exprod7og112.obsmtp.com (exprod7og112.obsmtp.com [64.18.2.177]) by ietfa.amsl.com (Postfix) with ESMTP id B8F2611E8074 for <ietf@ietf.org>; Wed, 14 Mar 2012 21:01:30 -0700 (PDT)
Received: from P-EMHUB01-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob112.postini.com ([64.18.6.12]) with SMTP ID DSNKT2FphGHdRPX5xXdLhfsIplqUps6zFkH1@postini.com; Wed, 14 Mar 2012 21:01:30 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, 14 Mar 2012 21:00:33 -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, 14 Mar 2012 21:00:31 -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; Thu, 15 Mar 2012 00:00:29 -0400
From: Ross Callon <rcallon@juniper.net>
To: Russ Housley <housley@vigilsec.com>, IETF <ietf@ietf.org>
Date: Thu, 15 Mar 2012 00:00:28 -0400
Subject: RE: Issues relating to managing a mailing list... 
Thread-Topic: Issues relating to managing a mailing list... 
Thread-Index: Ac0CPKxDDQo1N+70T2iZjAsNXkyqAAAIpPoA
Message-ID: <DF7F294AF4153D498141CBEFADB17704C70C8FC930@EMBX01-WF.jnpr.net>
References: <1344A266-28E8-4228-908F-395FB41EDA83@amsl.com> <30461C26-EDCE-4BFD-8E82-AF1CC5BC371C@vigilsec.com>
In-Reply-To: <30461C26-EDCE-4BFD-8E82-AF1CC5BC371C@vigilsec.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-EXCLAIMER-MD-CONFIG: e4081efb-6d29-443c-8708-750833aec629
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Mar 2012 04:01:32 -0000

I don't like this proposal for two reasons: I frequently read email while n=
ot connected; When connected, bandwidths have gotten high enough that attac=
hments on the most part are not slowing things down in an uncomfortable way=
.=20

It might be okay for really large attachments, as long as only a few messag=
es are affected.=20

Ross

-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of Rus=
s Housley
Sent: Wednesday, March 14, 2012 7:46 PM
To: IETF
Subject: Issues relating to managing a mailing list...=20

Some suggestions have been made about the IETF mail lists.
There is a way for mailman to strip attachments and put them
in a place for downloading with a web browser.  This would be
a significant change to current practice, so the community
needs to consider this potential policy change.

What do you think?

Russ


>>>> The only bug in the soup is that it seemed to me that we might
>>>> want to look into an alternative approach.  We have asked people
>>>> to post large documents somewhere and only send a pointer.  Not
>>>> everyone can do that, lots of people forget, and some people are
>>>> just not willing to take the extra step.
>>>>=20
>>>> Plus, we cannot expect people to keep things posted on their own
>>>> personal, or their company's, web-site indefinitely.  If they
>>>> don't keep it there, then the pointer in the archive will become
>>>> stale, and information that should probably be there is lost.
>>>>=20
>>>> So we need a solution to the issue with really big email messages
>>>> sometime.
>>>>=20
>>>> One solution might be to simpy strip attachments off, put them
>>>> in the archive and replace them with a pointer.  That shouldn't
>>>> be that hard, since a lot of anti-virus software does something
>>>> similar with suspect attachment types.
>>>>=20
>>>> Or we could - once again - ask people to post attachments and use
>>>> a pointer in their mail, only provide them with a place to post
>>>> them in the same general area as the mail archive.
>>>>=20
>>>> If there is already something like this in place, please let me
>>>> know what it is and I will add a pointer to it in my "too big"
>>>> rejection messages.
>>>>=20
>>>> The thing about threaded messages getting too big is a slightly
>>>> different issue, brought about by the increasing use of HTML
>>>> format email.  I talked years ago about this with Scott Bradner
>>>> because I really think that HTML format messages are useful and
>>>> relatively easy to read when compared to plain old text.
>>>>=20
>>>> But using HTML leads to messages that are deceptively big.
>>>>=20
>>>> Possibly the right answer in that case is to bump the size limit
>>>> up to maybe 100K.  Even with HTML format, people will many likely
>>>> realize that nobody is going to read past the 10th back message
>>>> in any case (or if they do want to, they can look at the thread
>>>> in the archive).
>>>>=20
>>>> But even that approach is not fool proof, and there are a lot of
>>>> resourceful fools out there.
>>>>=20
>>>> Just trying to be creative, and help out...


From jnc@mercury.lcs.mit.edu  Wed Mar 14 22:06:54 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 C564921F877E for <ietf@ietfa.amsl.com>; Wed, 14 Mar 2012 22:06:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.46
X-Spam-Level: 
X-Spam-Status: No, score=-6.46 tagged_above=-999 required=5 tests=[AWL=0.139,  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 35rtrzFYGG5g for <ietf@ietfa.amsl.com>; Wed, 14 Mar 2012 22:06:53 -0700 (PDT)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id 6570521F877C for <ietf@ietf.org>; Wed, 14 Mar 2012 22:06:53 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 6B57918C0B1; Thu, 15 Mar 2012 01:06:52 -0400 (EDT)
To: ietf@ietf.org
Subject: RE: Issues relating to managing a mailing list...
Message-Id: <20120315050652.6B57918C0B1@mercury.lcs.mit.edu>
Date: Thu, 15 Mar 2012 01:06:52 -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: Thu, 15 Mar 2012 05:06:55 -0000

Since there's no way to pick one choice which will make most people happy
(whichever one is picked, the proponents of the other will be unhappy), maybe
we should try and avoid making a choice? We could have two different back-end
distributions versions of the list: one which strips attachments, and one
which doesn't (both fed from the same input name). Then, people can sign up
for whichever one they prefer. ("All problems in computer science can be
solved by another level of indirection", etc, etc.)

    Noel

From randy@psg.com  Wed Mar 14 23:44: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 B622321F8758 for <ietf@ietfa.amsl.com>; Wed, 14 Mar 2012 23:44:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.522
X-Spam-Level: 
X-Spam-Status: No, score=-2.522 tagged_above=-999 required=5 tests=[AWL=0.077,  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 pc30bjokPb4W for <ietf@ietfa.amsl.com>; Wed, 14 Mar 2012 23:44:58 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 5443A21F85DD for <ietf@ietf.org>; Wed, 14 Mar 2012 23:44:58 -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 1S84Qa-000OTS-GL; Thu, 15 Mar 2012 06:44:48 +0000
Date: Thu, 15 Mar 2012 02:44:47 -0400
Message-ID: <m27gymcqhs.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: ned+ietf@mauve.mrochek.com
Subject: Re: Issues relating to managing a mailing list...
In-Reply-To: <01OD44MYQ1ZY00ZUIL@mauve.mrochek.com>
References: <1344A266-28E8-4228-908F-395FB41EDA83@amsl.com> <30461C26-EDCE-4BFD-8E82-AF1CC5BC371C@vigilsec.com> <01OD44MYQ1ZY00ZUIL@mauve.mrochek.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@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Mar 2012 06:44:58 -0000

> Is this really a big enough problem to be worth solving? I can't
> recall a single instance where I received IETF list with a problematic
> attachment.

i travel to places with very poor bandwidth.  it is a problem.

and the vast majority of users just do not get it.  "we send 20mb
documents around the office all the time.  suck it up."

randy

From randy@psg.com  Wed Mar 14 23:48:09 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 10E5521F879C for <ietf@ietfa.amsl.com>; Wed, 14 Mar 2012 23:48:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.523
X-Spam-Level: 
X-Spam-Status: No, score=-2.523 tagged_above=-999 required=5 tests=[AWL=0.076,  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 ew0bXhoh+4DC for <ietf@ietfa.amsl.com>; Wed, 14 Mar 2012 23:48:08 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id A6CD621F879B for <ietf@ietf.org>; Wed, 14 Mar 2012 23:48: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 1S84Tg-000OU9-RY; Thu, 15 Mar 2012 06:48:01 +0000
Date: Thu, 15 Mar 2012 02:48:00 -0400
Message-ID: <m262e6cqcf.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: ned+ietf@mauve.mrochek.com
Subject: Re: Issues relating to managing a mailing list...
In-Reply-To: <01OD44MYQ1ZY00ZUIL@mauve.mrochek.com>
References: <1344A266-28E8-4228-908F-395FB41EDA83@amsl.com> <30461C26-EDCE-4BFD-8E82-AF1CC5BC371C@vigilsec.com> <01OD44MYQ1ZY00ZUIL@mauve.mrochek.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@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Mar 2012 06:48:09 -0000

> I suppose I could live with this - but not actively support it - if
> the stripping was limited to abusively large attachments - say ones
> over 5Mb or thereabouts. But otherwise it's a TERRIBLE idea, and will
> simply result in everyone including the draft or whatever in the
> primary message text in order to avoid this nonsense, which results in
> a degradation of list quality for all concerned.

i prefer not to get 1MB without my consent.  and i will leave to your
imagination what i think of multi-megabite internet-drafts in general.

randy

From lear@cisco.com  Thu Mar 15 00:16:08 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 7032521F85C2 for <ietf@ietfa.amsl.com>; Thu, 15 Mar 2012 00:16:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.56
X-Spam-Level: 
X-Spam-Status: No, score=-110.56 tagged_above=-999 required=5 tests=[AWL=0.039, 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 cussPNPg7lI8 for <ietf@ietfa.amsl.com>; Thu, 15 Mar 2012 00:16:07 -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 5D0CF21F85BE for <ietf@ietf.org>; Thu, 15 Mar 2012 00:16:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=lear@cisco.com; l=481; q=dns/txt; s=iport; t=1331795767; x=1333005367; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=ySrIxSjgVzNRXzaJF5cYzg1Dp80hFWpDPlIQ3zmtduQ=; b=lFXmA5gfr8nRVPNPDUJTQDtf+t7Nup6jco7/203njb5eb+w0dgP6EtKv 2eotr3P+GCO5xi580QW32WdUnxwFrRb6jazK92jVKVybuvdFBCrz8ZhfO S0Vkyf/VkI4X2xStdh7aB+57D2XvA8LwqxPuzeeTcVPN4O38aY4ekl7zU Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AsELANqWYU+Q/khN/2dsb2JhbABDhTyvawICAgKBC4EHggkBAQEEEgEQSwoBEAsYAgIFFgsCAgkDAgECAUUGDQEHAQEQDodomxaNBJIwgS+JCoUwgRYElViOQoFogmeBWw
X-IronPort-AV: E=Sophos;i="4.73,588,1325462400"; d="scan'208";a="68517558"
Received: from ams-core-4.cisco.com ([144.254.72.77]) by ams-iport-2.cisco.com with ESMTP; 15 Mar 2012 07:16:06 +0000
Received: from dhcp-10-55-82-125.cisco.com (dhcp-10-55-82-125.cisco.com [10.55.82.125]) by ams-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id q2F7G6rt024026; Thu, 15 Mar 2012 07:16:06 GMT
Message-ID: <4F619739.6090609@cisco.com>
Date: Thu, 15 Mar 2012 08:16:09 +0100
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: Russ Housley <housley@vigilsec.com>
Subject: Re: Issues relating to managing a mailing list...
References: <1344A266-28E8-4228-908F-395FB41EDA83@amsl.com> <30461C26-EDCE-4BFD-8E82-AF1CC5BC371C@vigilsec.com>
In-Reply-To: <30461C26-EDCE-4BFD-8E82-AF1CC5BC371C@vigilsec.com>
X-Enigmail-Version: 1.4
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Mar 2012 07:16:08 -0000

Hi Russ,

On 3/15/12 12:46 AM, Russ Housley wrote:
> Some suggestions have been made about the IETF mail lists.
> There is a way for mailman to strip attachments and put them
> in a place for downloading with a web browser.  This would be
> a significant change to current practice, so the community
> needs to consider this potential policy change.
>
> What do you think?
>
> Russ


-1.  Offline readers would find it difficult to deal with such messages.

Eliot

From francesco.gennai@isti.cnr.it  Thu Mar 15 00:18:47 2012
Return-Path: <francesco.gennai@isti.cnr.it>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9135521F84FB for <ietf@ietfa.amsl.com>; Thu, 15 Mar 2012 00:18:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.606
X-Spam-Level: 
X-Spam-Status: No, score=-0.606 tagged_above=-999 required=5 tests=[AWL=1.113,  BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, 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 CDBZkMMN444r for <ietf@ietfa.amsl.com>; Thu, 15 Mar 2012 00:18:46 -0700 (PDT)
Received: from blade3.isti.cnr.it (blade3.isti.cnr.it [194.119.192.19]) by ietfa.amsl.com (Postfix) with ESMTP id AD16C21F84A6 for <ietf@ietf.org>; Thu, 15 Mar 2012 00:18:46 -0700 (PDT)
Received: from notarynodsn-daemon.mx.isti.cnr.it by mx.isti.cnr.it (PMDF V6.5-x6 #31988) id <01OD4Z4M51JQL6W5GD@mx.isti.cnr.it> for ietf@ietf.org; Thu, 15 Mar 2012 08:17:49 +0100 (MET)
Received: from mx.isti.cnr.it by mx.isti.cnr.it (PMDF V6.5 #31825) id <01OD4YEOQHHSKN0DXO@mx.isti.cnr.it>; Thu, 15 Mar 2012 08:17:49 +0100 (MET)
Date: Thu, 15 Mar 2012 08:07:49 +0100 (MET)
From: Francesco Gennai <francesco.gennai@isti.cnr.it>
Subject: Re: Issues relating to managing a mailing list...
In-reply-to: "Your message dated Thu, 15 Mar 2012 02:44:47 -0400" <m27gymcqhs.wl%randy@psg.com>
To: Randy Bush <randy@psg.com>
Message-id: <01OD4Z4LSYYWKN0DXO@mx.isti.cnr.it>
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=us-ascii
X-INSM-ip-source: localhost
X-INSM-ip-source: localhost
X-INSM-ip-source: localhost
X-INSM-ip-source: localhost
X-INSM-ip-source: localhost
X-INSM-ip-source: localhost
References: <1344A266-28E8-4228-908F-395FB41EDA83@amsl.com> <30461C26-EDCE-4BFD-8E82-AF1CC5BC371C@vigilsec.com> <01OD44MYQ1ZY00ZUIL@mauve.mrochek.com>
Cc: ned+ietf@mauve.mrochek.com, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Mar 2012 07:18:47 -0000

> > Is this really a big enough problem to be worth solving? I can't
> > recall a single instance where I received IETF list with a problematic
> > attachment.

> i travel to places with very poor bandwidth.  it is a problem.

> and the vast majority of users just do not get it.  "we send 20mb
> documents around the office all the time.  suck it up."


for who has problem in attachment downloading the solution should be
at the delivery Message Store level, where the strip of the attachment could be
done accordingly to an user configurable mailbox parameter
(as we do on our server, where we call it Easy Delivery).

Francesco


> randy


From alexandru.petrescu@gmail.com  Thu Mar 15 02:04:15 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 A767721F867C for <ietf@ietfa.amsl.com>; Thu, 15 Mar 2012 02:04:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.86
X-Spam-Level: 
X-Spam-Status: No, score=-8.86 tagged_above=-999 required=5 tests=[AWL=1.389,  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 Hx7fOg4OSZdD for <ietf@ietfa.amsl.com>; Thu, 15 Mar 2012 02:04:15 -0700 (PDT)
Received: from oxalide-out.extra.cea.fr (oxalide-out.extra.cea.fr [132.168.224.8]) by ietfa.amsl.com (Postfix) with ESMTP id EFB8921F8468 for <ietf@ietf.org>; Thu, 15 Mar 2012 02:04:12 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by oxalide.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id q2F94BXd026416 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <ietf@ietf.org>; Thu, 15 Mar 2012 10:04:11 +0100
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (8.14.4/8.14.4) with ESMTP id q2F94Boo017938 for <ietf@ietf.org>; Thu, 15 Mar 2012 10:04:11 +0100 (envelope-from alexandru.petrescu@gmail.com)
Received: from [127.0.0.1] (is010446-4.intra.cea.fr [10.8.33.116]) by muguet2.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id q2F94AK2025226 for <ietf@ietf.org>; Thu, 15 Mar 2012 10:04:11 +0100
Message-ID: <4F61B08A.4070705@gmail.com>
Date: Thu, 15 Mar 2012 10:04:10 +0100
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:11.0) Gecko/20120312 Thunderbird/11.0
MIME-Version: 1.0
To: IETF Discussion <ietf@ietf.org>
Subject: New ITS email list for discussing IPv6 and vehicular communications
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Mar 2012 09:04:15 -0000

Dear participants at IETF,

A new email list ITS Intelligent Transportation Systems has been set up
at IETF.  It is intended for discussions of IP and vehicular communications.

       https://www.ietf.org/mailman/listinfo/its

Let us meet in Paris about this as well (details to follow).

Alex


From framefritti@gmail.com  Thu Mar 15 02:49:52 2012
Return-Path: <framefritti@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 56B6B21F866B for <ietf@ietfa.amsl.com>; Thu, 15 Mar 2012 02:49:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.932
X-Spam-Level: 
X-Spam-Status: No, score=-3.932 tagged_above=-999 required=5 tests=[AWL=-0.333, 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 vlXzcZXDJZlA for <ietf@ietfa.amsl.com>; Thu, 15 Mar 2012 02:49:51 -0700 (PDT)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id 6DD2C21F8664 for <ietf@ietf.org>; Thu, 15 Mar 2012 02:49:51 -0700 (PDT)
Received: by iazz13 with SMTP id z13so4239053iaz.31 for <ietf@ietf.org>; Thu, 15 Mar 2012 02:49:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=AutTH0pTASZ9eCfcWBIfwA8gjtA5xYT3A1rwpFLcADE=; b=QchTgCOVLLgk3YYnCUSjirxMUizK+0c4+xgaEIO3hVNZnng5roc1HNpXi4Q/gqwI4V jS0wda9ItCb8H/c8beL0n/072oENXJtduFkI7riesMzUmb9RB49MglveU+AajxFGuxpb /CuoS32P1hyclCUw3dZy7b34jiDe+pn8oBjkZN7wy1EEMDkTcGdsjAVtvQidWS70yNY0 DFCuIse2oFHvU5Zi/ggSiyzuyKQc7Fq6vQgKzyeARhXSSyh+B79qmEKGOYg2igjMv0OV D35MbAIwSbdRPMU9tdm9WT7GDDP0vkaCpF0nR+1YcuwF9HFJpDBBXPSFyLsOv7+EIEC6 88OQ==
MIME-Version: 1.0
Received: by 10.50.41.230 with SMTP id i6mr4824135igl.18.1331804990891; Thu, 15 Mar 2012 02:49:50 -0700 (PDT)
Received: by 10.231.185.219 with HTTP; Thu, 15 Mar 2012 02:49:50 -0700 (PDT)
In-Reply-To: <01OD4Z4LSYYWKN0DXO@mx.isti.cnr.it>
References: <1344A266-28E8-4228-908F-395FB41EDA83@amsl.com> <30461C26-EDCE-4BFD-8E82-AF1CC5BC371C@vigilsec.com> <01OD44MYQ1ZY00ZUIL@mauve.mrochek.com> <m27gymcqhs.wl%randy@psg.com> <01OD4Z4LSYYWKN0DXO@mx.isti.cnr.it>
Date: Thu, 15 Mar 2012 10:49:50 +0100
Message-ID: <CABSMSPWLpO09ZCZyHfpUuYQaKv8goLx55YvQGoEaw+d=dht-XA@mail.gmail.com>
Subject: Re: Issues relating to managing a mailing list...
From: Riccardo Bernardini <framefritti@gmail.com>
To: IETF <ietf@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Mar 2012 09:49:52 -0000

On Thu, Mar 15, 2012 at 8:07 AM, Francesco Gennai
<francesco.gennai@isti.cnr.it> wrote:
>> > Is this really a big enough problem to be worth solving? I can't
>> > recall a single instance where I received IETF list with a problematic
>> > attachment.
>
>> i travel to places with very poor bandwidth. =A0it is a problem.
>
>> and the vast majority of users just do not get it. =A0"we send 20mb
>> documents around the office all the time. =A0suck it up."
>
>
> for who has problem in attachment downloading the solution should be
> at the delivery Message Store level, where the strip of the attachment co=
uld be
> done accordingly to an user configurable mailbox parameter
> (as we do on our server, where we call it Easy Delivery).
>
> Francesco
>
>
>> randy
>

A proposal: what about something configurable?  Everyone already has a
personal "setup" page for his/her own mailman account.  It would
suffice to add an option "send attachment as link," possibly with a
configurable threshold.  Honestly, I do not anything about the
internal structure of mailman, so I do not know if this would be a
huge change (wrt the "pure link" solution) or not.  But, you know,
"nothing is impossible if you do not have to do it..." :)

For me, I like the idea of using the link since, depending on where I
am, I work with different PCs.  Because of this, I read the mail via
web services and I do not download it on my local disk.  Large
attachments clog up my quota (do you see why I am using a gmail
account?).  However, I understand the "dual" situation where people
download the mail on local disk and the "physical" attachment would
allow them to have the attachment even when offline.

Letting each one doing his/her choice looks like a good compromise to me.

Riccardo

From sant9442@gmail.com  Thu Mar 15 03:53:23 2012
Return-Path: <sant9442@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2A18A21F8670 for <ietf@ietfa.amsl.com>; Thu, 15 Mar 2012 03:53:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.221
X-Spam-Level: 
X-Spam-Status: No, score=-3.221 tagged_above=-999 required=5 tests=[AWL=0.378,  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 4ecNcvPqxZVo for <ietf@ietfa.amsl.com>; Thu, 15 Mar 2012 03:53:21 -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 A6C0D21F8534 for <ietf@ietf.org>; Thu, 15 Mar 2012 03:53:21 -0700 (PDT)
Received: by yhkk25 with SMTP id k25so241061yhk.31 for <ietf@ietf.org>; Thu, 15 Mar 2012 03:53:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=Ne6wR5G073ZSDu0y04zNgXAMOgUvFiELRfYC70D1kPE=; b=Q/R8mm9KpcIAvZ+z/4evow55l9cduf5VCRs3d199wgU6MYifwlfihVyK5+ooFb01i7 1kpCm0VxxmYuenYqdCwQr3bxp5tbsrE9CJnb5GhgOsSSt7dFXYOiZhlXUFjnD5H/DUmm Zm27KsvaNb3pPB8SK5AbFEx8hjly2CPeJr9Vbgivsw76tvhIzQtVDEyq/XdRL1Sxt3Di tCcprz26yl9qtLl4WBnRXsYEkBV+MoOyb0MjF9mBvDQDzFHqJpbXVzo1g1lApLkiC0wd l8Jac88tq4AWD5CQSalW0TNNdEsoIE+yEVNqtPV7/nRoOZYzi6iNKd3Ll49uJcT88Xt5 sO9A==
Received: by 10.236.181.5 with SMTP id k5mr7426464yhm.61.1331808801228; Thu, 15 Mar 2012 03:53:21 -0700 (PDT)
Received: from adsl-215-50-126.mia.bellsouth.net (99-3-147-93.lightspeed.miamfl.sbcglobal.net. [99.3.147.93]) by mx.google.com with ESMTPS id i7sm1826102ani.17.2012.03.15.03.53.18 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 15 Mar 2012 03:53:19 -0700 (PDT)
Message-ID: <4F61CAAA.20509@gmail.com>
Date: Thu, 15 Mar 2012 06:55:38 -0400
From: Hector <sant9442@gmail.com>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: IETF <ietf@ietf.org>
Subject: Re: Issues relating to managing a mailing list...
References: <1344A266-28E8-4228-908F-395FB41EDA83@amsl.com>	<30461C26-EDCE-4BFD-8E82-AF1CC5BC371C@vigilsec.com>	<01OD44MYQ1ZY00ZUIL@mauve.mrochek.com>	<m27gymcqhs.wl%randy@psg.com> <01OD4Z4LSYYWKN0DXO@mx.isti.cnr.it> <CABSMSPWLpO09ZCZyHfpUuYQaKv8goLx55YvQGoEaw+d=dht-XA@mail.gmail.com>
In-Reply-To: <CABSMSPWLpO09ZCZyHfpUuYQaKv8goLx55YvQGoEaw+d=dht-XA@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Mar 2012 10:53:23 -0000

It will be more work, but going to mixed connectivity solution 
addresses the old, current and new.  Going online will serve better 
the rebirth on online connectivity, mixed bandwidths and smaller 
devices.  Using forums via web, newsgroups with email components has 
long been part of the RFC-based MUA.

But even for companies that have gone with mixed connectivity with RFC 
based and Online Web forums, going to Online web access may be 
inevitable. Microsoft is a prime example after nearly 30 years it 
abandoned the newsgroups for online forums early last year.  To help 
with the transition, several NNTP Bridges were written to allow for 
users familiar with their favorite MUA Email/News Readers to use the 
online forums.  That is what I did when Microsoft migration NNTP 
bridge was too poor. So I wrote WcLEX (Wildcat! Live Exchange) 
http://opensite.winserver.com/wclex

There is plenty of open source BBS forums for the web that offers a 
wide degree of group ware support features. Some many already have 
component to allow members to receive list mail via email accounts 
which came after much request to offer the "legacy" mode.

I suggest to keep the current mode, and look at Online BBS forums as a 
migration, and it may also using calendaring many always come with and 
also probably be able to augment the Online IETF Meeting efforts.

Go West.

---
Hector Santos, CTO
http://www.santronics.com

Riccardo Bernardini wrote:
> On Thu, Mar 15, 2012 at 8:07 AM, Francesco Gennai
> <francesco.gennai@isti.cnr.it> wrote:
>>>> Is this really a big enough problem to be worth solving? I can't
>>>> recall a single instance where I received IETF list with a problematic
>>>> attachment.
>>> i travel to places with very poor bandwidth. �it is a problem.
>>> and the vast majority of users just do not get it. �"we send 20mb
>>> documents around the office all the time. �suck it up."
>>
>> for who has problem in attachment downloading the solution should be
>> at the delivery Message Store level, where the strip of the attachment could be
>> done accordingly to an user configurable mailbox parameter
>> (as we do on our server, where we call it Easy Delivery).
>>
>> Francesco
>>
>>
>>> randy
> 
> A proposal: what about something configurable?  Everyone already has a
> personal "setup" page for his/her own mailman account.  It would
> suffice to add an option "send attachment as link," possibly with a
> configurable threshold.  Honestly, I do not anything about the
> internal structure of mailman, so I do not know if this would be a
> huge change (wrt the "pure link" solution) or not.  But, you know,
> "nothing is impossible if you do not have to do it..." :)
> 
> For me, I like the idea of using the link since, depending on where I
> am, I work with different PCs.  Because of this, I read the mail via
> web services and I do not download it on my local disk.  Large
> attachments clog up my quota (do you see why I am using a gmail
> account?).  However, I understand the "dual" situation where people
> download the mail on local disk and the "physical" attachment would
> allow them to have the attachment even when offline.
> 
> Letting each one doing his/her choice looks like a good compromise to me.
> 
> Riccardo
> 
> 

From iljitsch@muada.com  Thu Mar 15 05:46:07 2012
Return-Path: <iljitsch@muada.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1F06521F86A7; Thu, 15 Mar 2012 05:46: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 MmZ4gPJ0zbIv; Thu, 15 Mar 2012 05:46:06 -0700 (PDT)
Received: from sequoia.muada.com (sequoia.muada.com [IPv6:2001:1af8:3100:a006:1::]) by ietfa.amsl.com (Postfix) with ESMTP id 5109D21F8693; Thu, 15 Mar 2012 05:46:06 -0700 (PDT)
Received: from [192.168.0.101] (static-67-21-228-77.ipcom.comunitel.net [77.228.21.67] (may be forged)) (authenticated bits=0) by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id q2FCjvMF048702 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 15 Mar 2012 13:45:58 +0100 (CET) (envelope-from iljitsch@muada.com)
Subject: Re: [83attendees] Usual recreational venue diatribe (was Ground transportation from/to CDG)
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=us-ascii
From: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <20120315114708.353d7f73@shane-desktop>
Date: Thu, 15 Mar 2012 13:45:57 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <47AF028D-E05B-46C2-B056-CC1F9A03589A@muada.com>
References: <CABOxzu3P_OsrteZwnn5Ntskw8AoRB-Mp26RyZ_SH02u0ekfbqQ@mail.gmail.com> <alpine.BSF.2.00.1203112218050.5094@joyce.lan> <0B7D9C2C-CDED-42EE-99E9-8D188D050CD5@commcorp.com.br> <018601cd0050$0b8a2940$229e7bc0$@gmail.com> <737E053B-81B7-43DF-AF25-F33FA152E77D@muada.com> <CAC4RtVCbuBA1TU0gaQ=OdL4VfqkaUSWG1dvx9_7MQt9547+oSw@mail.gmail.com> <AD9F9C4F-9245-4125-ABC9-3BD7E3502EBC@softarmor.com> <alpine.OSX.2.01.1203131552360.16882@rabdullah.local> <m2zkbkdqnz.wl%randy@psg.com> <B2D62B70-AD02-40D1-9D8F-0DD8A9DDA3CA@softarmor.com> <6A46D6D5-D4A2-4006-B402-E4724E56D4C3@fugue.com> <4F60A14C.4080309@alum.mit.edu> <DDD8B097-08F4-46E2-BB22-55B566F95E06@mimecast.com> <E379BA87-83F9-43B3-BAF4-53DC68AA5D25@fugue.com> <20120315114708.353d7f73@shane-desktop>
To: Shane Kerr <shane@isc.org>
X-Mailer: Apple Mail (2.1257)
Cc: 83attendees@ietf.org, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Mar 2012 12:46:07 -0000

On 15 Mar 2012, at 11:47 , Shane Kerr wrote:

> Yet we know based on country attendance statistics that people attend
> meetings in their region much more than where they have to travel a
> great distance. So even if cost is not a huge factor, SOMETHING is.

Not everyone goes to every meeting. Obviously for those of us who only =
go to some of them, it makes more sense to go to ones that are less =
costly/inconvenient.

> Maybe this is something that could be tried in a smaller scale first,
> for interim meetings or suchlike?

If we're going to do experiments, I think there are better ones that we =
could do.

One obvious one is video streaming rather than just audio streaming. =
Video that is good enough to read the slides would be very helpful.

The next step would be for remote participants to send audio and =
preferably video back for asking questions and doing remote =
presentations.

And we should also figure out that the purpose of the jabber rooms is / =
should be.=

From scott.brim@gmail.com  Thu Mar 15 06:18:05 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 4D9DF21F85E0 for <ietf@ietfa.amsl.com>; Thu, 15 Mar 2012 06:18:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.568
X-Spam-Level: 
X-Spam-Status: No, score=-103.568 tagged_above=-999 required=5 tests=[AWL=0.031, 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 qhyaIE1WLL5r for <ietf@ietfa.amsl.com>; Thu, 15 Mar 2012 06:18:04 -0700 (PDT)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id B186021F84F5 for <ietf@ietf.org>; Thu, 15 Mar 2012 06:18:04 -0700 (PDT)
Received: by vcbfk13 with SMTP id fk13so3852346vcb.31 for <ietf@ietf.org>; Thu, 15 Mar 2012 06:18:04 -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=Th7LAOBp+Tk7eJ2mYcF3/GJmdYFQo9Cp/mReNewer/U=; b=NH94NFcaWEwAfYbkHvT7DD20SJK+t+2y8Cll/eRpqoBic2epCRnRr+S3uUGhGsS2W7 gNszjTx+mZpMjh+TkSFSzGxTN5psFsYc5dVcIEPUobNhC2FCGogyfEZiThtfbbhzdq8I +fk1y0JWlo+gX+la7CTgXiA5jwc7RzQMJCtdF/PgBnP1VrLc1vmWjaQW0IDzaYNiBd0O Vu4vZxYvuJrZY+Y9CRyooF6Pbd/anLT8dDB/yAGFNdOGHDCwuvv2zyzgT9z8Ap8tPSMo os4e6lryYvAWWGtVqKN8Ub8scs3/E5YOr5SnBlZl07LqtfJOA9Oa/wc/JQUjPQ8qv4tt +3eg==
Received: by 10.52.93.18 with SMTP id cq18mr4599808vdb.40.1331817484206; Thu, 15 Mar 2012 06:18:04 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.220.60.74 with HTTP; Thu, 15 Mar 2012 06:17:44 -0700 (PDT)
In-Reply-To: <20120315050652.6B57918C0B1@mercury.lcs.mit.edu>
References: <20120315050652.6B57918C0B1@mercury.lcs.mit.edu>
From: Scott Brim <scott.brim@gmail.com>
Date: Thu, 15 Mar 2012 09:17:44 -0400
Message-ID: <CAPv4CP8hF0g6sp-6RuaMwyMAAQ2rF_bW0D2HtbZpE1wv1nwMnA@mail.gmail.com>
Subject: Re: Issues relating to managing a mailing list...
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Mar 2012 13:18:05 -0000

+1 on having two options, by some means.  Having a low bandwidth
distribution of text only is a very good idea, but there are more
people who want attachments intact, and problems in having the
stripped version be the archive version.  If it's too difficult to
provide an option, I apologize to Randy but I would recommend keeping
attachments attached -- most mail environments have a way to download
just the first <n>K of a message.

From mcr@sandelman.ca  Thu Mar 15 06:18:07 2012
Return-Path: <mcr@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F2C0F21F85F4 for <ietf@ietfa.amsl.com>; Thu, 15 Mar 2012 06:18:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.645
X-Spam-Level: 
X-Spam-Status: No, score=-1.645 tagged_above=-999 required=5 tests=[AWL=0.309,  BAYES_00=-2.599, HOST_MISMATCH_NET=0.311, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fkCdiMg442IS for <ietf@ietfa.amsl.com>; Thu, 15 Mar 2012 06:18:06 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [67.23.6.41]) by ietfa.amsl.com (Postfix) with ESMTP id 2D4D021F85E0 for <ietf@ietf.org>; Thu, 15 Mar 2012 06:18:06 -0700 (PDT)
Received: from marajade.sandelman.ca (unknown [132.213.238.4]) by relay.sandelman.ca (Postfix) with ESMTPS id 80F90A0079 for <ietf@ietf.org>; Thu, 15 Mar 2012 09:15:29 -0400 (EDT)
Received: by marajade.sandelman.ca (Postfix, from userid 179) id 3680D983B9; Thu, 15 Mar 2012 09:18:04 -0400 (EDT)
Received: from marajade.sandelman.ca (localhost [127.0.0.1]) by marajade.sandelman.ca (Postfix) with ESMTP id 2B11698281 for <ietf@ietf.org>; Thu, 15 Mar 2012 09:18:04 -0400 (EDT)
From: Michael Richardson <mcr@sandelman.ca>
To: IETF <ietf@ietf.org>
Subject: Re: Issues relating to managing a mailing list...
In-Reply-To: <01OD44MYQ1ZY00ZUIL@mauve.mrochek.com>
References: <1344A266-28E8-4228-908F-395FB41EDA83@amsl.com> <30461C26-EDCE-4BFD-8E82-AF1CC5BC371C@vigilsec.com> <01OD44MYQ1ZY00ZUIL@mauve.mrochek.com>
X-Mailer: MH-E 8.3; nmh 1.3-dev; XEmacs 21.4 (patch 22)
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Thu, 15 Mar 2012 09:18:04 -0400
Message-ID: <5457.1331817484@marajade.sandelman.ca>
Sender: mcr@sandelman.ca
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Mar 2012 13:18:07 -0000

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


>>>>> "ned" =3D=3D ned  <ned+ietf@mauve.mrochek.com> writes:
    ned> Is this really a big enough problem to be worth solving? I
    ned> can't recall a single instance where I received IETF list with
    ned> a problematic attachment. OTOH, I routinely get IETF messages
    ned> with useful attachements - typically a critical revision to a
    ned> draft which for whatever reason can't be posted as an I-D -
    ned> that I really need to be able see without having to bother with

I regard those situation as a violation of process.
If that ID can't go on an HTTP site, then something is missing.

=2D-=20
]       He who is tired of Weird Al is tired of life!           |  firewall=
s  [
]   Michael Richardson, Sandelman Software Works, Ottawa, ON    |net archit=
ect[
] mcr@sandelman.ottawa.on.ca http://www.sandelman.ottawa.on.ca/ |device dri=
ver[
   Kyoto Plus: watch the video <http://www.youtube.com/watch?v=3Dkzx1ycLXQS=
E>
	               then sign the petition.=20

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

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

iQCVAwUAT2HsC4qHRg3pndX9AQKshQQAvsP+D4SqaLNjfe6HAAQuaF8TE6Qdnvch
ISpGQfv/vk/wxDTYGoKUOWwD6wO5+xstiqdAO0kkoznxXvqq+gOcC7s9JeDx3vUA
UepEbdZWNOtno5Hg0hKYbuBLdT8y2nF7pfHKugeGw10bJZ/OxzrxbZhJg34aL9FE
OpE1hPdbEXI=
=iVOw
-----END PGP SIGNATURE-----
--=-=-=--

From mcr@sandelman.ca  Thu Mar 15 06:27:36 2012
Return-Path: <mcr@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 01E8D21F8666 for <ietf@ietfa.amsl.com>; Thu, 15 Mar 2012 06:27:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.658
X-Spam-Level: 
X-Spam-Status: No, score=-1.658 tagged_above=-999 required=5 tests=[AWL=0.296,  BAYES_00=-2.599, HOST_MISMATCH_NET=0.311, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CU5M-Z0AIHPQ for <ietf@ietfa.amsl.com>; Thu, 15 Mar 2012 06:27:35 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [67.23.6.41]) by ietfa.amsl.com (Postfix) with ESMTP id 6DEF321F8655 for <ietf@ietf.org>; Thu, 15 Mar 2012 06:27:35 -0700 (PDT)
Received: from marajade.sandelman.ca (unknown [132.213.238.4]) by relay.sandelman.ca (Postfix) with ESMTPS id 287B0A0079 for <ietf@ietf.org>; Thu, 15 Mar 2012 09:24:59 -0400 (EDT)
Received: by marajade.sandelman.ca (Postfix, from userid 179) id 33FFB983B9; Thu, 15 Mar 2012 09:27:31 -0400 (EDT)
Received: from marajade.sandelman.ca (localhost [127.0.0.1]) by marajade.sandelman.ca (Postfix) with ESMTP id 30A1898281 for <ietf@ietf.org>; Thu, 15 Mar 2012 09:27:31 -0400 (EDT)
From: Michael Richardson <mcr@sandelman.ca>
To: IETF <ietf@ietf.org>
Subject: Re: Issues relating to managing a mailing list... 
In-Reply-To: <30461C26-EDCE-4BFD-8E82-AF1CC5BC371C@vigilsec.com>
References: <1344A266-28E8-4228-908F-395FB41EDA83@amsl.com> <30461C26-EDCE-4BFD-8E82-AF1CC5BC371C@vigilsec.com>
X-Mailer: MH-E 8.3; nmh 1.3-dev; XEmacs 21.4 (patch 22)
Date: Thu, 15 Mar 2012 09:27:31 -0400
Message-ID: <7150.1331818051@marajade.sandelman.ca>
Sender: mcr@sandelman.ca
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Mar 2012 13:27:36 -0000

>>>>> "Russ" == Russ Housley <housley@vigilsec.com> writes:
    Russ> Some suggestions have been made about the IETF mail lists.
    Russ> There is a way for mailman to strip attachments and put them
    Russ> in a place for downloading with a web browser.  This would be
    Russ> a significant change to current practice, so the community
    Russ> needs to consider this potential policy change.

I like it.

    Russ> What do you think?

Is text/html an attachment?
What about text/plain that hasn't got format=flowed, but has lines
longer than 77 lines?  

-- 
]       He who is tired of Weird Al is tired of life!           |  firewalls  [
]   Michael Richardson, Sandelman Software Works, Ottawa, ON    |net architect[
] mcr@sandelman.ottawa.on.ca http://www.sandelman.ottawa.on.ca/ |device driver[
   Kyoto Plus: watch the video <http://www.youtube.com/watch?v=kzx1ycLXQSE>
	               then sign the petition. 



From dhc@dcrocker.net  Thu Mar 15 06:37:53 2012
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0741C21F86AA for <ietf@ietfa.amsl.com>; Thu, 15 Mar 2012 06:37:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.606
X-Spam-Level: 
X-Spam-Status: No, score=-6.606 tagged_above=-999 required=5 tests=[AWL=-0.007, 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 FAhZXHmWDWAX for <ietf@ietfa.amsl.com>; Thu, 15 Mar 2012 06:37:50 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 40E9F21F86A3 for <ietf@ietf.org>; Thu, 15 Mar 2012 06:37:50 -0700 (PDT)
Received: from [192.168.1.11] (adsl-67-127-58-62.dsl.pltn13.pacbell.net [67.127.58.62]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q2FDbikU026113 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Thu, 15 Mar 2012 06:37:50 -0700
Message-ID: <4F61F08E.6010603@dcrocker.net>
Date: Thu, 15 Mar 2012 06:37:18 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Issues relating to managing a mailing list...
References: <1344A266-28E8-4228-908F-395FB41EDA83@amsl.com> <30461C26-EDCE-4BFD-8E82-AF1CC5BC371C@vigilsec.com>
In-Reply-To: <30461C26-EDCE-4BFD-8E82-AF1CC5BC371C@vigilsec.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Thu, 15 Mar 2012 06:37:50 -0700 (PDT)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Mar 2012 13:37:53 -0000

On 3/14/2012 4:46 PM, Russ Housley wrote:
> Some suggestions have been made about the IETF mail lists.
> There is a way for mailman to strip attachments and put them
> in a place for downloading with a web browser.  This would be
> a significant change to current practice, so the community
> needs to consider this potential policy change.
>
> What do you think?


It is an entirely reasonable idea.

However has some very core operational problems that are being nicely listed by 
others already.  IMO, they are all real and serious.  They decrease the flexible 
usage styles of IETF mailing lists that is now possible.

Ultimately, as at least Ned noted, the major problem with the suggestion is that 
is seeks to solve a problem that we don't have.

So concerning the proposal:  -1


d/
-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From cyrus@daboo.name  Thu Mar 15 06:41:31 2012
Return-Path: <cyrus@daboo.name>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B584621F84B6 for <ietf@ietfa.amsl.com>; Thu, 15 Mar 2012 06:41:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.625
X-Spam-Level: 
X-Spam-Status: No, score=-102.625 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 RbkT+5xyBSpy for <ietf@ietfa.amsl.com>; Thu, 15 Mar 2012 06:41:30 -0700 (PDT)
Received: from daboo.name (daboo.name [173.13.55.49]) by ietfa.amsl.com (Postfix) with ESMTP id CE56821F8624 for <ietf@ietf.org>; Thu, 15 Mar 2012 06:41:30 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by daboo.name (Postfix) with ESMTP id 4830F239B5FA; Thu, 15 Mar 2012 09:41:30 -0400 (EDT)
X-Virus-Scanned: amavisd-new at daboo.name
Received: from daboo.name ([127.0.0.1]) by localhost (daboo.name [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ha0BFAZzrbxQ; Thu, 15 Mar 2012 09:41:28 -0400 (EDT)
Received: from caldav.corp.apple.com (unknown [17.45.162.46]) by daboo.name (Postfix) with ESMTPSA id 902DB239B5EB; Thu, 15 Mar 2012 09:41:27 -0400 (EDT)
Date: Thu, 15 Mar 2012 09:41:35 -0400
From: Cyrus Daboo <cyrus@daboo.name>
To: ietf@ietf.org
Subject: Re: Issues relating to managing a mailing list...
Message-ID: <8E4035C3ECF01FAE0CCDB05B@caldav.corp.apple.com>
In-Reply-To: <39AB1CE59499893A8E276552@PST.JCK.COM>
References: <1344A266-28E8-4228-908F-395FB41EDA83@amsl.com> <01OD44MYQ1ZY00ZUIL@mauve.mrochek.com> <4F6145A0.3020705@gmail.com>	<2103063.rDf6FqNnG2@scott-latitude-e6320> <39AB1CE59499893A8E276552@PST.JCK.COM>
X-Mailer: Mulberry/4.1.0a3 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline; size=1602
Cc: John C Klensin <john-ietf@jck.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Mar 2012 13:41:31 -0000

Hi,

--On March 14, 2012 11:48:08 PM -0400 John C Klensin <john-ietf@jck.com> 
wrote:

> Let me add to the reasons the observation that there are still
> some of us who read IETF mailing lists on airplanes or in other
> environments with limited, expensive, or zero connectivity.  If
> everything is in the email message then downloading messages
> with POP3 or synchronizing a local ("offline") copy with IMAP is
> easy and easy to automate.  No need to read those messages at
> all before heading for the airport (or whatever).  If some
> messages have important stuff in URL references, it creates a
> nightmare because the only way to find those is to skim all the
> messages before departure.

Along those lines how about setting up an IETF IMAP server with mailboxes 
for each mailing list hosted by the IETF? That way anyone with a capable 
IMAP client (one that can separately download text and attachments as 
preferred by the user on a per-mailbox basis) can choose to sync the 
messages as they prefer based on their own circumstances. What is more, if 
people use the IMAP server as their main way to access to the mailing lists 
there are other big benefits: the mailboxes provide a comprehensive 
searchable archive of messages directly within the email client, users can 
subscribe with an option to not have list email delivered to their own 
account - that would remove the need to deliver lots of messages.

Yes, this would be a fairly big infrastructure change, but there are 
significant benefits and flexibility to using IMAP as a shared mailing list 
repository.

-- 
Cyrus Daboo


From dave@cridland.net  Thu Mar 15 06:44:38 2012
Return-Path: <dave@cridland.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 14F4521F86B2 for <ietf@ietfa.amsl.com>; Thu, 15 Mar 2012 06:44:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.408
X-Spam-Level: 
X-Spam-Status: No, score=-2.408 tagged_above=-999 required=5 tests=[AWL=0.191,  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 PzaJGPqqJ-tq for <ietf@ietfa.amsl.com>; Thu, 15 Mar 2012 06:44:37 -0700 (PDT)
Received: from peirce.dave.cridland.net (peirce.dave.cridland.net [IPv6:2001:470:1f09:882:2e0:81ff:fe29:d16a]) by ietfa.amsl.com (Postfix) with ESMTP id 1EC8F21F869A for <ietf@ietf.org>; Thu, 15 Mar 2012 06:44:37 -0700 (PDT)
Received: from localhost (peirce.dave.cridland.net [127.0.0.1]) by peirce.dave.cridland.net (Postfix) with ESMTP id EFB3E1168087; Thu, 15 Mar 2012 13:44:30 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at peirce.dave.cridland.net
Received: from peirce.dave.cridland.net ([127.0.0.1]) by localhost (peirce.dave.cridland.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yTVP8sN4UwUT; Thu, 15 Mar 2012 13:44:27 +0000 (GMT)
Received: from puncture (puncture.dave.cridland.net [IPv6:2001:470:1f09:882:221:85ff:fe3f:1696]) by peirce.dave.cridland.net (Postfix) with ESMTPA id 896AA1168067; Thu, 15 Mar 2012 13:44:27 +0000 (GMT)
Subject: Re: Issues relating to managing a mailing list...
References: <1344A266-28E8-4228-908F-395FB41EDA83@amsl.com> <30461C26-EDCE-4BFD-8E82-AF1CC5BC371C@vigilsec.com> <01OD44MYQ1ZY00ZUIL@mauve.mrochek.com> <4F6145A0.3020705@gmail.com>
In-Reply-To: <4F6145A0.3020705@gmail.com>
MIME-Version: 1.0
Message-Id: <2803.1331819067.508677@puncture>
Date: Thu, 15 Mar 2012 13:44:27 +0000
From: Dave Cridland <dave@cridland.net>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, IETF-Discussion <ietf@ietf.org>, "ned+ietf@mauve.mrochek.com" <ned+ietf@mauve.mrochek.com>
Content-Type: text/plain; delsp="yes"; charset="us-ascii"; format="flowed"
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Mar 2012 13:44:38 -0000

On Thu Mar 15 01:28:00 2012, Brian E Carpenter wrote:
> On 2012-03-15 13:33, ned+ietf@mauve.mrochek.com wrote:
> ...
> > I suppose I could live with this - but not actively support it -  
> if the
> > stripping was limited to abusively large attachments - say ones  
> over 5Mb or
> > thereabouts.
> 
> +0.9; maybe set the limit a bit lower, for those who still have  
> network
> capacity issues. However, it would be extremely inconvenient to  
> have small
> attachments stripped.
> 
> 
I'd be against this - any cut-off picked would be an arbitrary  
number, and given there exist well-deployed, well-supported  
specifications for accessing internet message stores without  
downloading all parts of a message, I see no need for this at all.

I'd prefer rejecting outright particularly large messages, to  
mangling them in unpredictable ways - however, I have been reading  
IETF lists over expensive and slow networks for years without running  
into any such messages.


> > But otherwise it's a TERRIBLE idea, and will simply result in
> > everyone including the draft or whatever in the primary message  
> text in order
> > to avoid this nonsense, which results in a degradation of list  
> quality for all
> > concerned.
> 
> +1

Right, we're merely introducing damage for people to route around.

If we're seriously making a statement that messages with attachments  
cannot be handled properly in the deployed network due to Technical  
Reason X, then I would be very interested to hear what X is. The  
message Russ quotes merely suggests that large messages are a problem  
in themselves - if they are genuinely a problem, how? And why on  
earth are they a problem in this group?

Dave.
-- 
Dave Cridland - mailto:dave@cridland.net - xmpp:dwd@dave.cridland.net
  - acap://acap.dave.cridland.net/byowner/user/dwd/bookmarks/
  - http://dave.cridland.net/
Infotrope Polymer - ACAP, IMAP, ESMTP, and Lemonade

From john-ietf@jck.com  Thu Mar 15 06:48:06 2012
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A95A621F86B7 for <ietf@ietfa.amsl.com>; Thu, 15 Mar 2012 06:48:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.756
X-Spam-Level: 
X-Spam-Status: No, score=-102.756 tagged_above=-999 required=5 tests=[AWL=-0.157, 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 4doXxxQ3t2F5 for <ietf@ietfa.amsl.com>; Thu, 15 Mar 2012 06:48:05 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id B4E5421F8667 for <ietf@ietf.org>; Thu, 15 Mar 2012 06:48:05 -0700 (PDT)
Received: from [198.252.137.7] (helo=PST.JCK.COM) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1S8AxU-0001ES-HC; Thu, 15 Mar 2012 09:43:12 -0400
Date: Thu, 15 Mar 2012 09:47:57 -0400
From: John C Klensin <john-ietf@jck.com>
To: Ross Callon <rcallon@juniper.net>, Russ Housley <housley@vigilsec.com>, IETF <ietf@ietf.org>
Subject: RE: Issues relating to managing a mailing list...
Message-ID: <5A3E73081B60554E45A3722B@PST.JCK.COM>
In-Reply-To: <DF7F294AF4153D498141CBEFADB17704C70C8FC930@EMBX01-WF.jnpr.net>
References: <1344A266-28E8-4228-908F-395FB41EDA83@amsl.com> <30461C26-EDCE-4BFD-8E82-AF1CC5BC371C@vigilsec.com> <DF7F294AF4153D498141CBEFADB17704C70C8FC930@EMBX01-WF.jnpr.net>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Mar 2012 13:48:06 -0000

--On Thursday, March 15, 2012 00:00 -0400 Ross Callon
<rcallon@juniper.net> wrote:

> I don't like this proposal for two reasons: I frequently read
> email while not connected; When connected, bandwidths have
> gotten high enough that attachments on the most part are not
> slowing things down in an uncomfortable way. 
> 
> It might be okay for really large attachments, as long as only
> a few messages are affected. 

Borrowing a bit from Randy, the solution to really large
attachments is to ban them.  Personally, I'd find it perfectly
reasonable to have any message in the megabyte range or above
(or probably even an order of magnitude smaller) rejected with a
message that amounted to "if you have that much to say, write an
I-D, post it, and point to it".  That is much more plausible
today, when the mean time between I-D submission and posting is
measured in minutes (except during blackout periods) than when
it was in days.  During blackout periods, the last thing the
community needs is people adding to already-overloaded lists by
posting long documents in email.

If people want to use up part of their maximum size quota by
posting html in addition to text, or appending long disclaimers
or autobiographies, that shouldn't the community's problem.

    john



From john-ietf@jck.com  Thu Mar 15 06:55:44 2012
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 34C9621F85E1 for <ietf@ietfa.amsl.com>; Thu, 15 Mar 2012 06:55:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.754
X-Spam-Level: 
X-Spam-Status: No, score=-102.754 tagged_above=-999 required=5 tests=[AWL=-0.155, 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 4PBygiJg9hv5 for <ietf@ietfa.amsl.com>; Thu, 15 Mar 2012 06:55:43 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 2863B21F85D9 for <ietf@ietf.org>; Thu, 15 Mar 2012 06:55:43 -0700 (PDT)
Received: from [198.252.137.7] (helo=PST.JCK.COM) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1S8B4v-0001FB-6h; Thu, 15 Mar 2012 09:50:53 -0400
Date: Thu, 15 Mar 2012 09:55:37 -0400
From: John C Klensin <john-ietf@jck.com>
To: Cyrus Daboo <cyrus@daboo.name>, ietf@ietf.org
Subject: Re: Issues relating to managing a mailing list...
Message-ID: <11D2EA1671AA525051B9E95D@PST.JCK.COM>
In-Reply-To: <8E4035C3ECF01FAE0CCDB05B@caldav.corp.apple.com>
References: <1344A266-28E8-4228-908F-395FB41EDA83@amsl.com> <01OD44MYQ1ZY00ZUIL@mauve.mrochek.com> <4F6145A0.3020705@gmail.com> <2103063.rDf6FqNnG2@scott-latitude-e6320> <39AB1CE59499893A8E276552@PST.JCK.COM> <8E4035C3ECF01FAE0CCDB05B@caldav.corp.apple.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, 15 Mar 2012 13:55:44 -0000

--On Thursday, March 15, 2012 09:41 -0400 Cyrus Daboo
<cyrus@daboo.name> wrote:

>...
> Along those lines how about setting up an IETF IMAP server
> with mailboxes for each mailing list hosted by the IETF? That
> way anyone with a capable IMAP client (one that can separately
> download text and attachments as preferred by the user on a
> per-mailbox basis) can choose to sync the messages as they
> prefer based on their own circumstances. What is more, if
> people use the IMAP server as their main way to access to the
> mailing lists there are other big benefits: the mailboxes
> provide a comprehensive searchable archive of messages
> directly within the email client, users can subscribe with an
> option to not have list email delivered to their own account -
> that would remove the need to deliver lots of messages.
> 
> Yes, this would be a fairly big infrastructure change, but
> there are significant benefits and flexibility to using IMAP
> as a shared mailing list repository.

Including the traditional argument for eating our own dog food
rather than inventing and using idiosyncratic and non-standard
solutions.

Now, if only I could find a fully-competent IMAP client with a
decent IMAP-oriented UI and support for recently-added features
(not just to IMAP but including good support for current
versions of S/MIME and OpenPGPO, certificate formats, EAI,
etc.).  :-(

       john


From lixia@cs.ucla.edu  Thu Mar 15 07:43:23 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 8E43B21F8624 for <ietf@ietfa.amsl.com>; Thu, 15 Mar 2012 07:43:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XBTp6HQ7bHbU for <ietf@ietfa.amsl.com>; Thu, 15 Mar 2012 07:43:23 -0700 (PDT)
Received: from smtp.cs.ucla.edu (smtp.cs.ucla.edu [131.179.128.62]) by ietfa.amsl.com (Postfix) with ESMTP id 1D64721F8607 for <ietf@ietf.org>; Thu, 15 Mar 2012 07:43:23 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp.cs.ucla.edu (Postfix) with ESMTP id BCA04A60003; Thu, 15 Mar 2012 07:43:22 -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 RFSXQpVmOCwr; Thu, 15 Mar 2012 07:43:22 -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 12486A60001; Thu, 15 Mar 2012 07:43:22 -0700 (PDT)
Subject: Re: Issues relating to managing a mailing list...
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=us-ascii
From: Lixia Zhang <lixia@cs.ucla.edu>
In-Reply-To: <5A3E73081B60554E45A3722B@PST.JCK.COM>
Date: Thu, 15 Mar 2012 07:43:25 -0700
Content-Transfer-Encoding: 7bit
Message-Id: <069D10CA-94C2-4482-8E9A-6FFA6C716FD2@cs.ucla.edu>
References: <1344A266-28E8-4228-908F-395FB41EDA83@amsl.com> <30461C26-EDCE-4BFD-8E82-AF1CC5BC371C@vigilsec.com> <DF7F294AF4153D498141CBEFADB17704C70C8FC930@EMBX01-WF.jnpr.net> <5A3E73081B60554E45A3722B@PST.JCK.COM>
To: John C Klensin <john-ietf@jck.com>
X-Mailer: Apple Mail (2.1257)
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Mar 2012 14:43:23 -0000

On Mar 15, 2012, at 6:47 AM, John C Klensin wrote:

> 
> 
> --On Thursday, March 15, 2012 00:00 -0400 Ross Callon
> <rcallon@juniper.net> wrote:
> 
>> I don't like this proposal for two reasons: I frequently read
>> email while not connected; When connected, bandwidths have
>> gotten high enough that attachments on the most part are not
>> slowing things down in an uncomfortable way. 
>> 
>> It might be okay for really large attachments, as long as only
>> a few messages are affected. 
> 
> Borrowing a bit from Randy, the solution to really large
> attachments is to ban them. 

+1

Lixia


From sm@resistor.net  Thu Mar 15 07:51:45 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 21F7B21F86EC for <ietf@ietfa.amsl.com>; Thu, 15 Mar 2012 07:51:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.035
X-Spam-Level: 
X-Spam-Status: No, score=-102.035 tagged_above=-999 required=5 tests=[AWL=-0.636, BAYES_00=-2.599, J_CHICKENPOX_44=0.6, J_CHICKENPOX_72=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UtTongHMnqAh for <ietf@ietfa.amsl.com>; Thu, 15 Mar 2012 07:51:42 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id E1CC021F86C1 for <ietf@ietf.org>; Thu, 15 Mar 2012 07:51:42 -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 q2FEpbJJ004236 for <ietf@ietf.org>; Thu, 15 Mar 2012 07:51:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1331823101; i=@resistor.net; bh=TXiiH6dc8IQkFqYsRQSOwGMqxKxnNDTzUGlBdn8wRcE=; h=Date:To:From:Subject:In-Reply-To:References:Cc; b=mKfsjVZBmIJII7VYYj8pQyyAMTIQn32tFpVw9f3dhPwmLIWuTernTjh9nkMqTBfMu WRK4/AuvMcRvrHhKd21VtEw3rdHK6qvDkcXL4wxsCzEvowbpgJciaj62V4x6GURBAI ELTOjabCkZk1KInTmVRukM6TmpMkB7FWdTIXWzJU=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1331823101; i=@resistor.net; bh=TXiiH6dc8IQkFqYsRQSOwGMqxKxnNDTzUGlBdn8wRcE=; h=Date:To:From:Subject:In-Reply-To:References:Cc; b=US1Dj5aPKiWezKQEZRi23vEh/qmeysN5RawLRs0/X6jE6QNkNVhWSySDnuHIdpIA1 /i8pLh4nnurjcJ7COf/YtmVuFwYUKZ5Drgm/s9Jn90HaBRwhVTE0q80VdEATWO6hgh 47k4INTNtYL48FVZkmcGAax3y/d3CmzS7kXAjClA=
Message-Id: <6.2.5.6.2.20120315072508.0b2359e8@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 15 Mar 2012 07:50:44 -0700
To: Discussion IETF <ietf@ietf.org>
From: SM <sm@resistor.net>
Subject: Re: IETF Mail Archive Tools RFI
In-Reply-To: <CC6F7CF7-08D0-45A6-B3A0-E9F9B20BBA3F@isoc.org>
References: <CC6F7CF7-08D0-45A6-B3A0-E9F9B20BBA3F@isoc.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Mar 2012 14:51:45 -0000

At 21:43 12-03-2012, Ray Pelletier wrote:
>Expressions of interest from potential bidders and all SOW comments 
>are due by 16 April 2012 and should be submitted to 
>mailarch@ietf-bids.org.  See the RFI for more details.

Domain Name:IETF-BIDS.ORG
Created On:06-Mar-2012 22:09:29 UTC
Registrant Name:ietf-bids.org Private Registrant
Registrant Organization:A Happy DreamHost Customer
Registrant Street1:417 Associated Rd #324
Registrant Street2:
Registrant Street3:
Registrant City:Brea
Registrant State/Province:CA
Registrant Postal Code:92821
Registrant Country:US
Registrant Phone:+1.2139471032
Registrant Phone Ext.:
Registrant FAX:
Registrant FAX Ext.:
Registrant Email:ietf-bids.org@proxy.dreamhost.com

ietf-bids.org.          14400   IN      MX      0 
mx1.sub4.homie.mail.dreamhost.com.
ietf-bids.org.          14400   IN      MX      0 
mx2.sub4.homie.mail.dreamhost.com.

Is ietf-bids.org an IETF domain name?

As a FYI, draft-sparks-genarea-imaparch-01 discusses about IMAP 
access to IETF mail archives.

Regards,
-sm 


From framefritti@gmail.com  Thu Mar 15 07:56:37 2012
Return-Path: <framefritti@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 32CAD21F867E for <ietf@ietfa.amsl.com>; Thu, 15 Mar 2012 07:56:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.849
X-Spam-Level: 
X-Spam-Status: No, score=-3.849 tagged_above=-999 required=5 tests=[AWL=-0.250, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ptpzgPsXmZRG for <ietf@ietfa.amsl.com>; Thu, 15 Mar 2012 07:56:36 -0700 (PDT)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id 9998721F8645 for <ietf@ietf.org>; Thu, 15 Mar 2012 07:56:36 -0700 (PDT)
Received: by iazz13 with SMTP id z13so4651733iaz.31 for <ietf@ietf.org>; Thu, 15 Mar 2012 07:56:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=4i7pQh1PSHqqNt6HRO7n0TQTo14eWNOcAV+BfpgVIi8=; b=u4E2BG0WOKLfB41fiMFySO+1fylsJhI9ONsI0JPTkNymjYaqqBcgr7tj6dot7CRpLt 0Aq/jHKC2DYOQo7v4PgLSmhkWVxTUsYyegecnlApmWpA/UxzygHgNdXoG6a1c6Vhg3xp w4o+A5ZOyphHVKKn9eVOqsWQJy9T34HHZxSpuY7BZ14ZFH4D2q9HzEPvwd6dR5FFOx8E CsuVa/B9Sezph6YlPsGR/8tSsa8eNmMDDof98bIKDvTk6v0erhiYA/Q//LmaGIaRuBJu bH6Du0vorMF9PzQ8PL4rmkDXpg+S88lcWe4XWdg3tsyCcjTmVuUU+wAAJzhEPgBscqZA bY8Q==
MIME-Version: 1.0
Received: by 10.43.119.129 with SMTP id fu1mr1211075icc.26.1331823395830; Thu, 15 Mar 2012 07:56:35 -0700 (PDT)
Received: by 10.231.185.219 with HTTP; Thu, 15 Mar 2012 07:56:35 -0700 (PDT)
In-Reply-To: <069D10CA-94C2-4482-8E9A-6FFA6C716FD2@cs.ucla.edu>
References: <1344A266-28E8-4228-908F-395FB41EDA83@amsl.com> <30461C26-EDCE-4BFD-8E82-AF1CC5BC371C@vigilsec.com> <DF7F294AF4153D498141CBEFADB17704C70C8FC930@EMBX01-WF.jnpr.net> <5A3E73081B60554E45A3722B@PST.JCK.COM> <069D10CA-94C2-4482-8E9A-6FFA6C716FD2@cs.ucla.edu>
Date: Thu, 15 Mar 2012 15:56:35 +0100
Message-ID: <CABSMSPWfySSd_KVLp9tO96g=T1Jz4UnVc7_JHvx=jv+M9hA5KQ@mail.gmail.com>
Subject: Re: Issues relating to managing a mailing list...
From: Riccardo Bernardini <framefritti@gmail.com>
To: IETF <ietf@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Mar 2012 14:56:37 -0000

On Thu, Mar 15, 2012 at 3:43 PM, Lixia Zhang <lixia@cs.ucla.edu> wrote:
>
> On Mar 15, 2012, at 6:47 AM, John C Klensin wrote:
>
>>
>>
>> --On Thursday, March 15, 2012 00:00 -0400 Ross Callon
>> <rcallon@juniper.net> wrote:
>>
>>> I don't like this proposal for two reasons: I frequently read
>>> email while not connected; When connected, bandwidths have
>>> gotten high enough that attachments on the most part are not
>>> slowing things down in an uncomfortable way.
>>>
>>> It might be okay for really large attachments, as long as only
>>> a few messages are affected.
>>

>> Borrowing a bit from Randy, the solution to really large
>> attachments is to ban them.
>
> +1
>
> Lixia
>

Indeed, it is simple, effective and no big changes are necessary.
Moreover, as someone else pointed out, large attachments are very,
very unusual, so a limitation on the maximum attachment size should
not be a problem most of the time.

How do we fix the maximum size?  I just checked that the PDF version
of RFC 3261 (SIP) is 388 K.  Double it and fix the bound to 800 K.
Twice the size of SIP spec should be more than reasonable.

Riccardo

From housley@vigilsec.com  Thu Mar 15 08:00:41 2012
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BA9B321F870A for <ietf@ietfa.amsl.com>; Thu, 15 Mar 2012 08:00: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 I2jPVCTeJrIm for <ietf@ietfa.amsl.com>; Thu, 15 Mar 2012 08:00:39 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id 87AA621F86A5 for <ietf@ietf.org>; Thu, 15 Mar 2012 08:00:39 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 849349A471B; Thu, 15 Mar 2012 11:00: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 esYI3Pd1ZrU7; Thu, 15 Mar 2012 11:00:29 -0400 (EDT)
Received: from [10.71.1.211] (70-35-43-66.static.wiline.com [70.35.43.66]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 59FE29A470F; Thu, 15 Mar 2012 11:00:54 -0400 (EDT)
Subject: Re: IETF Mail Archive Tools RFI
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <6.2.5.6.2.20120315072508.0b2359e8@resistor.net>
Date: Thu, 15 Mar 2012 11:00:35 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <4263AB79-61FB-4C25-8B87-811B79D47B04@vigilsec.com>
References: <CC6F7CF7-08D0-45A6-B3A0-E9F9B20BBA3F@isoc.org> <6.2.5.6.2.20120315072508.0b2359e8@resistor.net>
To: SM <sm@resistor.net>
X-Mailer: Apple Mail (2.1084)
Cc: Discussion IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Mar 2012 15:00:41 -0000

Yes.  This is used for mail lists associated with bids for the IETF.  We =
wanted to make sure that no IETF vendor was able to see these messages, =
such as the one that operates the servers for ietf.org.

Russ


On Mar 15, 2012, at 10:50 AM, SM wrote:

> Is ietf-bids.org an IETF domain name?


From ned+ietf@mauve.mrochek.com  Thu Mar 15 08:10:11 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 3AD6B21F86B5 for <ietf@ietfa.amsl.com>; Thu, 15 Mar 2012 08:10:11 -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 ERFlhjCzbjWI for <ietf@ietfa.amsl.com>; Thu, 15 Mar 2012 08:10:10 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id 6349E21F852E for <ietf@ietf.org>; Thu, 15 Mar 2012 08:10:10 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OD4YV0JYXC00RPYP@mauve.mrochek.com> for ietf@ietf.org; Thu, 15 Mar 2012 08:10:07 -0700 (PDT)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OCPMUVDUMO00ZUIL@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Thu, 15 Mar 2012 08:10:01 -0700 (PDT)
From: ned+ietf@mauve.mrochek.com
Message-id: <01OD4YUXNIUY00ZUIL@mauve.mrochek.com>
Date: Thu, 15 Mar 2012 08:03:50 -0700 (PDT)
Subject: Re: Issues relating to managing a mailing list...
In-reply-to: "Your message dated Thu, 15 Mar 2012 08:07:49 +0100 (MET)" <01OD4Z4LSYYWKN0DXO@mx.isti.cnr.it>
MIME-version: 1.0
Content-type: TEXT/PLAIN
References: <1344A266-28E8-4228-908F-395FB41EDA83@amsl.com> <30461C26-EDCE-4BFD-8E82-AF1CC5BC371C@vigilsec.com> <01OD44MYQ1ZY00ZUIL@mauve.mrochek.com> <m27gymcqhs.wl%randy@psg.com> <01OD4Z4LSYYWKN0DXO@mx.isti.cnr.it>
To: Francesco Gennai <francesco.gennai@isti.cnr.it>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mrochek.com; s=mauve; t=1331824211; i=@mrochek.com; bh=Zogo+nE24Iv6dEpaUzWOb/MRRWoQn6geR7J8QGiBv2o=;  h=From:Cc:Message-id:Date:Subject:In-reply-to:MIME-version: Content-type:References:To; b=etMnM5V3GRnm+pBfXj0iaYtjIKddF8JITGvPnBwZhKjWrIIMbk1Cs/lodfx4e+ChS bnCgEtMCVk5fWxFV3d6qlgzvxI13McpFJuKaVy/MggVSCb4pQMehrQUBsD/ObABuIF aOLGMba1XAdqu9/ss5ulPwgvJPJVJi+xx2wWARl8=
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Mar 2012 15:10:11 -0000

> > > Is this really a big enough problem to be worth solving? I can't
> > > recall a single instance where I received IETF list with a problematic
> > > attachment.

> > i travel to places with very poor bandwidth.  it is a problem.

> > and the vast majority of users just do not get it.  "we send 20mb
> > documents around the office all the time.  suck it up."


> for who has problem in attachment downloading the solution should be
> at the delivery Message Store level, where the strip of the attachment could be
> done accordingly to an user configurable mailbox parameter
> (as we do on our server, where we call it Easy Delivery).

Or better still, don't strip anything. Use a reasonably capable client and
that doesn't fetch attachments unless you tell it to.

I'll again note that implementation of this policy will cause people to send
single part messages in order to avoid attachment stripping, which will make it
impossible for clients to avoid downloading material they do not want. In other
words, it will exacerbate, rather than solve, the problem.

				Ned

From petithug@acm.org  Thu Mar 15 08:13:03 2012
Return-Path: <petithug@acm.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F19CE21F8744 for <ietf@ietfa.amsl.com>; Thu, 15 Mar 2012 08:13:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.403
X-Spam-Level: 
X-Spam-Status: No, score=-102.403 tagged_above=-999 required=5 tests=[AWL=0.197, 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 gqfZi4Gz2yG0 for <ietf@ietfa.amsl.com>; Thu, 15 Mar 2012 08:13:02 -0700 (PDT)
Received: from implementers.org (implementers.org [IPv6:2604:3400:dc1:41:216:3eff:fe5b:8240]) by ietfa.amsl.com (Postfix) with ESMTP id 10E8121F86B8 for <ietf@ietf.org>; Thu, 15 Mar 2012 08:13:01 -0700 (PDT)
Received: from [IPv6:2001:470:1f05:616:213:d4ff:fe04:3e08] (shalmaneser.org [IPv6:2001:470:1f05:616:213:d4ff:fe04:3e08]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client CN "petithug", Issuer "implementers.org" (verified OK)) by implementers.org (Postfix) with ESMTPS id 48BF7201BE; Thu, 15 Mar 2012 14:55:35 +0000 (UTC)
Message-ID: <4F6206F9.6060901@acm.org>
Date: Thu, 15 Mar 2012 08:12:57 -0700
From: Marc Petit-Huguenin <petithug@acm.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:8.0) Gecko/20120216 Icedove/8.0
MIME-Version: 1.0
To: Lixia Zhang <lixia@cs.ucla.edu>
Subject: Re: Issues relating to managing a mailing list...
References: <1344A266-28E8-4228-908F-395FB41EDA83@amsl.com> <30461C26-EDCE-4BFD-8E82-AF1CC5BC371C@vigilsec.com> <DF7F294AF4153D498141CBEFADB17704C70C8FC930@EMBX01-WF.jnpr.net> <5A3E73081B60554E45A3722B@PST.JCK.COM> <069D10CA-94C2-4482-8E9A-6FFA6C716FD2@cs.ucla.edu>
In-Reply-To: <069D10CA-94C2-4482-8E9A-6FFA6C716FD2@cs.ucla.edu>
X-Enigmail-Version: 1.3.4
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: John C Klensin <john-ietf@jck.com>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Mar 2012 15:13:03 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 03/15/2012 07:43 AM, Lixia Zhang wrote:
> 
> On Mar 15, 2012, at 6:47 AM, John C Klensin wrote:
> 
>> 
>> 
>> --On Thursday, March 15, 2012 00:00 -0400 Ross Callon 
>> <rcallon@juniper.net> wrote:
>> 
>>> I don't like this proposal for two reasons: I frequently read email
>>> while not connected; When connected, bandwidths have gotten high enough
>>> that attachments on the most part are not slowing things down in an
>>> uncomfortable way.
>>> 
>>> It might be okay for really large attachments, as long as only a few
>>> messages are affected.
>> 
>> Borrowing a bit from Randy, the solution to really large attachments is
>> to ban them.
> 
> +1
> 
> Lixia
> 

I support the ban of attachments in IETF emails.

On the other hand, one feature that would be very useful is to add in the
email footer a link to the archive in each email forwarded by mailman (mailman
does not support that currently), so referencing a past email in a discussion
does not require having to search the archive.  For example the previous email
should contain a link for
https://www.ietf.org/mail-archive/web/ietf/current/msg72476.html.

- -- 
Marc Petit-Huguenin
Personal email: marc@petit-huguenin.org
Professional email: petithug@acm.org
Blog: http://blog.marc.petit-huguenin.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBCAAGBQJPYgb2AAoJECnERZXWan7E2egQALYEMBWiAmzaed519zBiAUqD
TbKJzMU77sD39PuzxFHe4ZP713/xpzxNhTvZ2iXXJ63L+NmkxM7D7zA/zdsL7bCe
36Ae2XNlWTPMbL5UUVsUL18DMFWJf2dICYK1UDSqDsg18yFRWsH//GUhLCYcbcVA
amRcj2LbNaLrFSCndJhz/QAaCS279cjGO1nc+8bjnNAcPeN1Fzlv1BJTvDg07u2J
knRP4/sn5muRevK1Yigbz5G4vlNTppUvQ8TqkUAVEBsjzTV4gPuBbfOFAhrpvMdV
ExuWgn//1UkzDdSJJDLp8gL5xiHMrSXg6ItEf1H/xcJQR+e7qyM7i2QngDUp6CGf
pdFwUIjAQ64WUibR0Xr0UvSTpAy7XXKxyKky+AZEzv2VRXaX0BxQR8ZvvlYlte1G
BkMPuq1WoAvHHHCkaMFm4ShoZPw8Hxq77yp7xMlfjaNqK6OYISraJ0oSDjmo0LnT
wIG2fexUtOIAYy4dwx/6p+4B5RpyU9WBFI8V6iQVbbFe3Tlete813UvGDgjq84K8
fhO6YtI2UVw5PvfLCnhGr7rGEATbe+1TbfDsxwQBCAlP754SkAKwSOAawGfLXS/0
fXSBYyU1WxCFf8xH7Yxog19p1+RvsdTQ35NWRgi9+N7jSkpVtK7X4DN70I5JexVu
a6XqMRyQzblok958Wpzx
=i1YY
-----END PGP SIGNATURE-----

From ajs@anvilwalrusden.com  Thu Mar 15 08:24:07 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 EF0BD21F84E1 for <ietf@ietfa.amsl.com>; Thu, 15 Mar 2012 08:24:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 scI-iui7j7hv for <ietf@ietfa.amsl.com>; Thu, 15 Mar 2012 08:24:06 -0700 (PDT)
Received: from mail.yitter.info (mail.yitter.info [208.86.224.201]) by ietfa.amsl.com (Postfix) with ESMTP id 8D45321F84D8 for <ietf@ietf.org>; Thu, 15 Mar 2012 08:24:05 -0700 (PDT)
Received: from mail.yitter.info (unknown [199.91.193.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.yitter.info (Postfix) with ESMTPSA id 6D3C81ECB41C for <ietf@ietf.org>; Thu, 15 Mar 2012 15:24:04 +0000 (UTC)
Date: Thu, 15 Mar 2012 11:24:05 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: Re: Issues relating to managing a mailing list...
Message-ID: <20120315152405.GB18304@mail.yitter.info>
References: <1344A266-28E8-4228-908F-395FB41EDA83@amsl.com> <30461C26-EDCE-4BFD-8E82-AF1CC5BC371C@vigilsec.com> <01OD44MYQ1ZY00ZUIL@mauve.mrochek.com> <m27gymcqhs.wl%randy@psg.com> <01OD4Z4LSYYWKN0DXO@mx.isti.cnr.it> <01OD4YUXNIUY00ZUIL@mauve.mrochek.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <01OD4YUXNIUY00ZUIL@mauve.mrochek.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Mar 2012 15:24:07 -0000

On Thu, Mar 15, 2012 at 08:03:50AM -0700, ned+ietf@mauve.mrochek.com wrote:
> 
> Or better still, don't strip anything. Use a reasonably capable client and
> that doesn't fetch attachments unless you tell it to.

Yes.  What problem is this proposal to do anything about attachments
trying to solve?  Of all the non-problems around the IETF in search of
a lot of extra rules, at first glance this one seems to me like the
noniest.

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

From ned+ietf@mauve.mrochek.com  Thu Mar 15 08:29:16 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 8394321F8697 for <ietf@ietfa.amsl.com>; Thu, 15 Mar 2012 08:29:16 -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 s5RAT3yIXkEM for <ietf@ietfa.amsl.com>; Thu, 15 Mar 2012 08:29:15 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id 9057621F8666 for <ietf@ietf.org>; Thu, 15 Mar 2012 08:29:15 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OD4ZILB75S004P5B@mauve.mrochek.com> for ietf@ietf.org; Thu, 15 Mar 2012 08:29:07 -0700 (PDT)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OCPMUVDUMO00ZUIL@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Thu, 15 Mar 2012 08:29:02 -0700 (PDT)
From: ned+ietf@mauve.mrochek.com
Message-id: <01OD4ZIIFXJM00ZUIL@mauve.mrochek.com>
Date: Thu, 15 Mar 2012 08:16:29 -0700 (PDT)
Subject: RE: Issues relating to managing a mailing list...
In-reply-to: "Your message dated Thu, 15 Mar 2012 09:47:57 -0400" <5A3E73081B60554E45A3722B@PST.JCK.COM>
MIME-version: 1.0
Content-type: TEXT/PLAIN
References: <1344A266-28E8-4228-908F-395FB41EDA83@amsl.com> <30461C26-EDCE-4BFD-8E82-AF1CC5BC371C@vigilsec.com> <DF7F294AF4153D498141CBEFADB17704C70C8FC930@EMBX01-WF.jnpr.net> <5A3E73081B60554E45A3722B@PST.JCK.COM>
To: John C Klensin <john-ietf@jck.com>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mrochek.com; s=mauve; t=1331825352; i=@mrochek.com; bh=0nXa0v8Cqi3F1jE0L89jD+hE1nFCSl7Gek4yPYHthLQ=;  h=From:Cc:Message-id:Date:Subject:In-reply-to:MIME-version: Content-type:References:To; b=NB9jv9QVLN6mXsndAPOo4eTqGas2sOYl+wohzIt43t0VoQeBMS/S3ZhsaiSbY1WgF f0oU+c0bItOgQ5/TZlyVrz1G1WqboNZzJJVKCsluJ0KBdLjBkUfnIwEUqozgdEZirg cq7Iw7a8bR0kKE9Y35tRCL+IC4hzKjUe0X9vpKlc=
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Mar 2012 15:29:16 -0000

> --On Thursday, March 15, 2012 00:00 -0400 Ross Callon
> <rcallon@juniper.net> wrote:

> > I don't like this proposal for two reasons: I frequently read
> > email while not connected; When connected, bandwidths have
> > gotten high enough that attachments on the most part are not
> > slowing things down in an uncomfortable way.
> >
> > It might be okay for really large attachments, as long as only
> > a few messages are affected.

> Borrowing a bit from Randy, the solution to really large
> attachments is to ban them.  Personally, I'd find it perfectly
> reasonable to have any message in the megabyte range or above
> (or probably even an order of magnitude smaller) rejected with a
> message that amounted to "if you have that much to say, write an
> I-D, post it, and point to it".  That is much more plausible
> today, when the mean time between I-D submission and posting is
> measured in minutes (except during blackout periods) than when
> it was in days.  During blackout periods, the last thing the
> community needs is people adding to already-overloaded lists by
> posting long documents in email.

> If people want to use up part of their maximum size quota by
> posting html in addition to text, or appending long disclaimers
> or autobiographies, that shouldn't the community's problem.

You begin by talking about "banning large attachments". You then segue
into a discussion where you talk about a maximum size that includes the
primary message content, not attachments, then you throw in disclaimers,
which may or may not be attachments.

Other have followed up by supporting the limit on attachment size, others
still have talked about banning attachments regardless of size.

Do you see the problem here? The minute you start focusing on specifics
of message content, you're in a rathole. What counts as an attachment?
(And yes, we have a precise definition for what constitutes an attachement,
but following that definition gives people the ability to route around
it.)

It follows that any limit needs to be on overall message size. (Even
this is a little perilous because message sizes can change due to
MIME downgrading or upgrading, both of which happen regularly.) I would
not be opposed to imposing such a limit, although it's going to need to
be higher than some people would probably like - it's surprising how
easily you can approach 1Mb with a single part, plain text message
containing nothing remotely resembling an "attachment".

				Ned

From jgs@juniper.net  Wed Mar 14 08:21:07 2012
Return-Path: <jgs@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 2578D21E805F; Wed, 14 Mar 2012 08:21:07 -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 tMpqI37gThNi; Wed, 14 Mar 2012 08:21:06 -0700 (PDT)
Received: from exprod7og112.obsmtp.com (exprod7og112.obsmtp.com [64.18.2.177]) by ietfa.amsl.com (Postfix) with ESMTP id D13F121E8054; Wed, 14 Mar 2012 08:21:05 -0700 (PDT)
Received: from P-EMHUB03-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob112.postini.com ([64.18.6.12]) with SMTP ID DSNKT2C3XO2x9QV1wWEcgUg68uEeZ8+wLoQI@postini.com; Wed, 14 Mar 2012 08:21:06 PDT
Received: from EMBX02-HQ.jnpr.net ([fe80::18fe:d666:b43e:f97e]) by P-EMHUB03-HQ.jnpr.net ([::1]) with mapi; Wed, 14 Mar 2012 08:20:27 -0700
From: John Scudder <jgs@juniper.net>
To: Barry Leiba <barryleiba@computer.org>
Date: Wed, 14 Mar 2012 08:20:26 -0700
Subject: Re: [lisp] WG Review: Recharter of Locator/ID Separation Protocol (lisp)
Thread-Topic: [lisp] WG Review: Recharter of Locator/ID Separation Protocol (lisp)
Thread-Index: Ac0B9fxBhSt98SA/Tw+ckfZkDHOfBw==
Message-ID: <F8BC059E-144B-4155-B6B7-75F47EDBD45D@juniper.net>
References: <20120214222316.CF29521E800E@ietfa.amsl.com> <201202152131.q1FLVB9E028114@cichlid.raleigh.ibm.com> <EF3C34EB-C0AA-45F2-ADE0-407CEF5172DD@juniper.net> <4F3E4EDB.7070509@piuha.net> <0E0C6A25-FBA6-4E11-9E89-DEBFFCF41108@juniper.net> <4F58EB8C.1000700@piuha.net> <70EB276F-D77E-45AE-851C-AB08A8D56D0A@juniper.net> <4F5920FF.6070502@piuha.net> <CALaySJKvS5QbtXuMx7TwFiL4hdgi1cT0sYu8EJtYLD6T2yOzKQ@mail.gmail.com> <1D2FF8E9-8E60-4126-AC30-12DFDC854BC6@juniper.net> <4F5F9A44.4020600@joelhalpern.com> <7CDFAED4-30C6-4CC4-BA91-F8B34857C9B4@juniper.net> <4F60AF4D.1090506@joelhalpern.com> <CALaySJ+xPdJJKAj3m+h6cLHPev5MhbVzRb8YwBO+CE5F8AKtbw@mail.gmail.com>
In-Reply-To: <CALaySJ+xPdJJKAj3m+h6cLHPev5MhbVzRb8YwBO+CE5F8AKtbw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
x-exclaimer-md-config: e4081efb-6d29-443c-8708-750833aec629
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Thu, 15 Mar 2012 08:43:28 -0700
Cc: "ietf@ietf.org list" <ietf@ietf.org>, "lisp@ietf.org" <lisp@ietf.org>, "iesg@ietf.org IESG" <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Mar 2012 15:21:07 -0000

Barry,

On Mar 14, 2012, at 11:02 AM, Barry Leiba wrote:

Relevant?  Yes.
Gating?  No.

In fact, I would put it the other way around.
The architecture documentis very useful, almost necessary, for deciding
whether the solution is a good one.
The cache management evaluations are another component of such an
evaluation.
Even understanding the cache management question is made significantly
easier by having a clean architecture description.

Indeed.

At the risk of straining things with an analogy, I'll liken this to
architecture of a building.  At the architecture level, we do have to
consider, say, bathrooms, and it's reasonable at that level to talk
about having bathrooms on each floor, and perhaps the extent to which
accessible bathrooms are needed.  Deciding whether to have two pairs
or three per floor is something that can be left to the detailed
post-architecture specifications, and things like what sorts of
fixtures to put in them *absolutely* come later.

No one is saying that some discussion of caching issues (etc) won't be
needed in defining and specifying the architecture.  We're just saying
that it's not necessary to do the caching document before, as long as
the related discussion that happens at the architecture stage is
preserved for when it's time to work on the caching doc.

Analogies are always risky, but I'll continue. I don't think the proper ana=
logy is a bathroom. Everyone knows you can build bathrooms that work, havin=
g seen successful examples in the past. You might instead think of a buildi=
ng which includes a perpetual motion machine [*] as a key element.

--John

[*] Forgive me, press of time prevents me from finding an example which is =
both less inflammatory, and still has the property "something whose practic=
ability is debatable." Feel free to fill in your favorite.

From rsk@gsp.org  Thu Mar 15 07:04:59 2012
Return-Path: <rsk@gsp.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1888821F8649 for <ietf@ietfa.amsl.com>; Thu, 15 Mar 2012 07:04:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9mAHz9e0MTxi for <ietf@ietfa.amsl.com>; Thu, 15 Mar 2012 07:04:58 -0700 (PDT)
Received: from taos.firemountain.net (taos.firemountain.net [207.114.3.54]) by ietfa.amsl.com (Postfix) with ESMTP id 877D121F8645 for <ietf@ietf.org>; Thu, 15 Mar 2012 07:04:58 -0700 (PDT)
Received: from squonk.gsp.org (bltmd-207.114.17.210.dsl.charm.net [207.114.17.210]) by taos.firemountain.net (8.14.5/8.14.5) with ESMTP id q2FE4toc008648 for <ietf@ietf.org>; Thu, 15 Mar 2012 10:04:56 -0400 (EDT)
Received: from vorlon.gsp.org (vorlon.gsp.org [192.168.0.20]) by squonk.gsp.org (8.14.3/8.14.3) with ESMTP id q2FEB5wM006724 for <ietf@ietf.org>; Thu, 15 Mar 2012 10:11:05 -0400 (EDT)
Received: from localhost6.localdomain6 (localhost.localdomain [127.0.0.1]) by vorlon.gsp.org (8.14.3/8.14.3/Debian-9.2ubuntu1) with ESMTP id q2FE4lNn016175 for <ietf@ietf.org>; Thu, 15 Mar 2012 10:04:47 -0400
Received: (from rsk@localhost) by localhost6.localdomain6 (8.14.3/8.14.3/Submit) id q2FE4lQh016174 for ietf@ietf.org; Thu, 15 Mar 2012 10:04:47 -0400
Date: Thu, 15 Mar 2012 10:04:46 -0400
From: Rich Kulawiec <rsk@gsp.org>
To: ietf@ietf.org
Subject: Re: Issues relating to managing a mailing list...
Message-ID: <20120315140445.GA15795@gsp.org>
References: <1344A266-28E8-4228-908F-395FB41EDA83@amsl.com> <30461C26-EDCE-4BFD-8E82-AF1CC5BC371C@vigilsec.com> <DF7F294AF4153D498141CBEFADB17704C70C8FC930@EMBX01-WF.jnpr.net> <5A3E73081B60554E45A3722B@PST.JCK.COM>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <5A3E73081B60554E45A3722B@PST.JCK.COM>
User-Agent: Mutt/1.5.20 (2009-06-14)
X-Mailman-Approved-At: Thu, 15 Mar 2012 08:43:28 -0700
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Mar 2012 14:04:59 -0000

On Thu, Mar 15, 2012 at 09:47:57AM -0400, John C Klensin wrote:
> Borrowing a bit from Randy, the solution to really large
> attachments is to ban them.  Personally, I'd find it perfectly
> reasonable to have any message in the megabyte range or above
> (or probably even an order of magnitude smaller) rejected with a
> message that amounted to "if you have that much to say, write an
> I-D, post it, and point to it".  [...]
> 
> If people want to use up part of their maximum size quota by
> posting html in addition to text, or appending long disclaimers
> or autobiographies, that shouldn't the community's problem.

I strong concur with all points (including those elided).  Attachments
which are in open formats and of modest size are often useful; those
which are in closed formats and of enormous size tend not to be.

---rsk

From presnick@qualcomm.com  Thu Mar 15 08:49:33 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 2261321F867B for <ietf@ietfa.amsl.com>; Thu, 15 Mar 2012 08:49:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.571
X-Spam-Level: 
X-Spam-Status: No, score=-106.571 tagged_above=-999 required=5 tests=[AWL=0.028, 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 fcIbZ52drBDj for <ietf@ietfa.amsl.com>; Thu, 15 Mar 2012 08:49:32 -0700 (PDT)
Received: from wolverine01.qualcomm.com (wolverine01.qualcomm.com [199.106.114.254]) by ietfa.amsl.com (Postfix) with ESMTP id 7132C21F85D3 for <ietf@ietf.org>; Thu, 15 Mar 2012 08:49:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=presnick@qualcomm.com; q=dns/txt; s=qcdkim; t=1331826572; x=1363362572; h=message-id:date:from:user-agent:mime-version:to:cc: subject:references:in-reply-to:content-type: content-transfer-encoding:x-originating-ip; z=Message-ID:=20<4F620F85.9030702@qualcomm.com>|Date:=20Th u,=2015=20Mar=202012=2010:49:25=20-0500|From:=20Pete=20Re snick=20<presnick@qualcomm.com>|User-Agent:=20Mozilla/5.0 =20(Macintosh=3B=20U=3B=20Intel=20Mac=20OS=20X=2010.6=3B =20en-US=3B=20rv:1.9.1.9)=20Gecko/20100630=20Eudora/3.0.4 |MIME-Version:=201.0|To:=20Cyrus=20Daboo=20<cyrus@daboo.n ame>|CC:=20<ietf@ietf.org>|Subject:=20Re:=20Issues=20rela ting=20to=20managing=20a=20mailing=20list...|References: =20<1344A266-28E8-4228-908F-395FB41EDA83@amsl.com>=09<01O D44MYQ1ZY00ZUIL@mauve.mrochek.com>=09<4F6145A0.3020705@gm ail.com>=09<2103063.rDf6FqNnG2@scott-latitude-e6320>=09<3 9AB1CE59499893A8E276552@PST.JCK.COM>=20<8E4035C3ECF01FAE0 CCDB05B@caldav.corp.apple.com>|In-Reply-To:=20<8E4035C3EC F01FAE0CCDB05B@caldav.corp.apple.com>|Content-Type:=20tex t/plain=3B=20charset=3D"ISO-8859-1"=3B=20format=3Dflowed |Content-Transfer-Encoding:=207bit|X-Originating-IP:=20[1 72.30.39.5]; bh=z4HdhWhfQnS+oGBtT1NzXiq7VimN6dArkrfzdIAkBBc=; b=kmttGfNB7ON2cuCNpCxWX6Ts8FYkiegUW0MbVacU+5vFXzPnsTj1J/Z3 LdSuj2DkNjyGGEWjZ58j6Cbnhh3dd4RxxN+mRr6tXNIeUMVZMRkvHR+8v lj2R01LuxSlnXNgYLcs8LBmuOm9hoh1bYZzM52MRhcAcmg/y6wb9JwfEC w=;
X-IronPort-AV: E=McAfee;i="5400,1158,6649"; a="172765319"
Received: from ironmsg04-l.qualcomm.com ([172.30.48.19]) by wolverine01.qualcomm.com with ESMTP; 15 Mar 2012 08:49:28 -0700
X-IronPort-AV: E=Sophos;i="4.73,591,1325491200"; d="scan'208";a="176735993"
Received: from nasanexhc07.na.qualcomm.com ([172.30.39.190]) by Ironmsg04-L.qualcomm.com with ESMTP/TLS/AES128-SHA; 15 Mar 2012 08:49:28 -0700
Received: from resnick2.qualcomm.com (172.30.39.5) by qcmail1.qualcomm.com (172.30.39.190) with Microsoft SMTP Server (TLS) id 14.1.339.1; Thu, 15 Mar 2012 08:49:28 -0700
Message-ID: <4F620F85.9030702@qualcomm.com>
Date: Thu, 15 Mar 2012 10:49:25 -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: Cyrus Daboo <cyrus@daboo.name>
Subject: Re: Issues relating to managing a mailing list...
References: <1344A266-28E8-4228-908F-395FB41EDA83@amsl.com>	<01OD44MYQ1ZY00ZUIL@mauve.mrochek.com>	<4F6145A0.3020705@gmail.com>	<2103063.rDf6FqNnG2@scott-latitude-e6320>	<39AB1CE59499893A8E276552@PST.JCK.COM> <8E4035C3ECF01FAE0CCDB05B@caldav.corp.apple.com>
In-Reply-To: <8E4035C3ECF01FAE0CCDB05B@caldav.corp.apple.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.39.5]
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Mar 2012 15:49:33 -0000

On 3/15/12 8:41 AM, Cyrus Daboo wrote:

> Along those lines how about setting up an IETF IMAP server with 
> mailboxes for each mailing list hosted by the IETF?

There has been a discussion under way for some time to get that to 
happen. I believe RFP's are being thought about (or written).

pr

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


From housley@vigilsec.com  Thu Mar 15 10:03:26 2012
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1832721F87A8 for <ietf@ietfa.amsl.com>; Thu, 15 Mar 2012 10:03:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8kmMs898XhCd for <ietf@ietfa.amsl.com>; Thu, 15 Mar 2012 10:03:25 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id 203BE21F876D for <ietf@ietf.org>; Thu, 15 Mar 2012 10:03:25 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id B6EDC9A4732 for <ietf@ietf.org>; Thu, 15 Mar 2012 13:03:45 -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 KNHdh63UG1PH for <ietf@ietf.org>; Thu, 15 Mar 2012 13:03:15 -0400 (EDT)
Received: from v234.vpn.iad.rg.net (v234.vpn.iad.rg.net [198.180.150.234]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 89D589A4730 for <ietf@ietf.org>; Thu, 15 Mar 2012 13:03:44 -0400 (EDT)
From: Russ Housley <housley@vigilsec.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: Re: Issues relating to managing a mailing list...
Date: Thu, 15 Mar 2012 13:03:21 -0400
In-Reply-To: <224EFEBA-5436-4ED2-87D5-1F88E55BD355@vigilsec.com>
To: IETF <ietf@ietf.org>
Message-Id: <E523B03A-EE7D-4D85-9D7A-0D4CC507B32B@vigilsec.com>
Mime-Version: 1.0 (Apple Message framework v1084)
X-Mailer: Apple Mail (2.1084)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Mar 2012 17:03:26 -0000

>>>> for who has problem in attachment downloading the solution should be
>>>> at the delivery Message Store level, where the strip of the
>>>> attachment could be
>>>> done accordingly to an user configurable mailbox parameter
>>>> (as we do on our server, where we call it Easy Delivery).

There is no option in Mailman to specify attachment-stripping by user,
only by list.

Russ


From francesco.gennai@isti.cnr.it  Thu Mar 15 10:03:40 2012
Return-Path: <francesco.gennai@isti.cnr.it>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5C08721F87DD for <ietf@ietfa.amsl.com>; Thu, 15 Mar 2012 10:03:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.884
X-Spam-Level: 
X-Spam-Status: No, score=-0.884 tagged_above=-999 required=5 tests=[AWL=0.835,  BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, 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 DUgYXz3q1oPr for <ietf@ietfa.amsl.com>; Thu, 15 Mar 2012 10:03:39 -0700 (PDT)
Received: from blade3.isti.cnr.it (blade3.isti.cnr.it [194.119.192.19]) by ietfa.amsl.com (Postfix) with ESMTP id 87DEC21F87DB for <ietf@ietf.org>; Thu, 15 Mar 2012 10:03:39 -0700 (PDT)
Received: from notarynodsn-daemon.mx.isti.cnr.it by mx.isti.cnr.it (PMDF V6.5-x6 #31988) id <01OD5JKABYGGL6WINM@mx.isti.cnr.it> for ietf@ietf.org; Thu, 15 Mar 2012 18:03:07 +0100 (MET)
Received: from mx.isti.cnr.it by mx.isti.cnr.it (PMDF V6.5 #31994) id <01OD5GX872IOKHXOTX@mx.isti.cnr.it>; Thu, 15 Mar 2012 18:03:08 +0100 (MET)
Date: Thu, 15 Mar 2012 17:52:53 +0100 (MET)
From: Francesco Gennai <francesco.gennai@isti.cnr.it>
Subject: Re: Issues relating to managing a mailing list...
In-reply-to: "Your message dated Thu, 15 Mar 2012 08:03:50 -0700 (PDT)" <01OD4YUXNIUY00ZUIL@mauve.mrochek.com>
To: Ned Freed <ned.freed@mrochek.com>
Message-id: <01OD5JKATQOEKHXOTX@mx.isti.cnr.it>
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=us-ascii
X-INSM-ip-source: localhost
X-INSM-ip-source: localhost
X-INSM-ip-source: localhost
References: <1344A266-28E8-4228-908F-395FB41EDA83@amsl.com> <30461C26-EDCE-4BFD-8E82-AF1CC5BC371C@vigilsec.com> <01OD44MYQ1ZY00ZUIL@mauve.mrochek.com> <m27gymcqhs.wl%randy@psg.com> <01OD4Z4LSYYWKN0DXO@mx.isti.cnr.it>
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Mar 2012 17:03:40 -0000

> > > > Is this really a big enough problem to be worth solving? I can't
> > > > recall a single instance where I received IETF list with a problematic
> > > > attachment.

> > > i travel to places with very poor bandwidth.  it is a problem.

> > > and the vast majority of users just do not get it.  "we send 20mb
> > > documents around the office all the time.  suck it up."


> > for who has problem in attachment downloading the solution should be
> > at the delivery Message Store level, where the strip of the attachment could be
> > done accordingly to an user configurable mailbox parameter
> > (as we do on our server, where we call it Easy Delivery).

> Or better still, don't strip anything. Use a reasonably capable client and
> that doesn't fetch attachments unless you tell it to.

Yes, I agree, but we can leave the end user to choose accordingly their own 
no capable/capable clients or maybe accordingly to temporary condition.

> I'll again note that implementation of this policy will cause people to send
> single part messages in order to avoid attachment stripping, which will make 
> it impossible for clients to avoid downloading material they do not want. 

I think that a part in a single part message can be replaced as any other part 
in a multipart message.

> In other words, it will exacerbate, rather than solve, the problem.

> 				Ned

Francesco

From jnc@mercury.lcs.mit.edu  Thu Mar 15 10:41:43 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 E27AA21F8758 for <ietf@ietfa.amsl.com>; Thu, 15 Mar 2012 10:41:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.465
X-Spam-Level: 
X-Spam-Status: No, score=-6.465 tagged_above=-999 required=5 tests=[AWL=0.134,  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 8DJar7vnMzQ8 for <ietf@ietfa.amsl.com>; Thu, 15 Mar 2012 10:41:43 -0700 (PDT)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id 5629721F8745 for <ietf@ietf.org>; Thu, 15 Mar 2012 10:41:43 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 6329118C0AD; Thu, 15 Mar 2012 13:41:35 -0400 (EDT)
To: ietf@ietf.org
Subject: Re: Issues relating to managing a mailing list...
Message-Id: <20120315174142.6329118C0AD@mercury.lcs.mit.edu>
Date: Thu, 15 Mar 2012 13:41:35 -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: Thu, 15 Mar 2012 17:41:44 -0000

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

    > There is no option in Mailman to specify attachment-stripping by
    > user, only by list.

So? Have 'ietf@ietf.org' send a copy to to a new list, 'ietf-strippedietf.org'
(the latter being set in Mailman to strip), and those who prefer their IETF
email without inclusions can subscribe to the latter, instead of the former.

(This whole discussion is so typical of the IETF: what should be a 30-second
exercise for one person to deal with in a simple, obvious way turns into a
multi-day discussion in which some try to redesign entire email systems.)

	Noel

From hartmans@mit.edu  Thu Mar 15 10:54:43 2012
Return-Path: <hartmans@mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4032F21F86A5 for <ietf@ietfa.amsl.com>; Thu, 15 Mar 2012 10:54:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.407
X-Spam-Level: 
X-Spam-Status: No, score=-103.407 tagged_above=-999 required=5 tests=[AWL=-1.142, 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 tV5MwvJwxq3w for <ietf@ietfa.amsl.com>; Thu, 15 Mar 2012 10:54:42 -0700 (PDT)
Received: from permutation-city.suchdamage.org (permutation-city.suchdamage.org [69.25.196.28]) by ietfa.amsl.com (Postfix) with ESMTP id C4EC521F8571 for <ietf@ietf.org>; Thu, 15 Mar 2012 10:54:42 -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 A15542021E; Thu, 15 Mar 2012 13:54:11 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id C07324767; Thu, 15 Mar 2012 13:54:26 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: Russ Housley <housley@vigilsec.com>
Subject: Re: Issues relating to managing a mailing list...
References: <1344A266-28E8-4228-908F-395FB41EDA83@amsl.com> <30461C26-EDCE-4BFD-8E82-AF1CC5BC371C@vigilsec.com>
Date: Thu, 15 Mar 2012 13:54:26 -0400
In-Reply-To: <30461C26-EDCE-4BFD-8E82-AF1CC5BC371C@vigilsec.com> (Russ Housley's message of "Wed, 14 Mar 2012 19:46:15 -0400")
Message-ID: <tslhaxphhrh.fsf@mit.edu>
User-Agent: Gnus/5.110009 (No Gnus v0.9) Emacs/22.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Mar 2012 17:54:43 -0000

>>>>> "Russ" == Russ Housley <housley@vigilsec.com> writes:

    Russ> Some suggestions have been made about the IETF mail lists.
    Russ> There is a way for mailman to strip attachments and put them
    Russ> in a place for downloading with a web browser.  This would be
    Russ> a significant change to current practice, so the community
    Russ> needs to consider this potential policy change.

    Russ> What do you think?

I agree with those who believe this would be a bad idea. I often read
IETf mail on airplanes where downloading an attachment would be
problematic.  It is much less common for me to want to download IETF
messages where I have any concerns about bandwidth.

From dhc@dcrocker.net  Thu Mar 15 10:56:12 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 BFC5221F87B8 for <ietf@ietfa.amsl.com>; Thu, 15 Mar 2012 10:56:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.606
X-Spam-Level: 
X-Spam-Status: No, score=-6.606 tagged_above=-999 required=5 tests=[AWL=-0.007, 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 vGMlsFWLubXE for <ietf@ietfa.amsl.com>; Thu, 15 Mar 2012 10:56:12 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 2FADF21F8767 for <ietf@ietf.org>; Thu, 15 Mar 2012 10:56:12 -0700 (PDT)
Received: from [192.168.1.11] (adsl-67-127-58-62.dsl.pltn13.pacbell.net [67.127.58.62]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q2FHu5ea000753 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 15 Mar 2012 10:56:11 -0700
Message-ID: <4F622D1B.3060601@dcrocker.net>
Date: Thu, 15 Mar 2012 10:55:39 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Subject: Re: Issues relating to managing a mailing list...
References: <20120315174142.6329118C0AD@mercury.lcs.mit.edu>
In-Reply-To: <20120315174142.6329118C0AD@mercury.lcs.mit.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Thu, 15 Mar 2012 10:56:11 -0700 (PDT)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Mar 2012 17:56:12 -0000

On 3/15/2012 10:41 AM, Noel Chiappa wrote:
> (This whole discussion is so typical of the IETF: what should be a 30-second
> exercise for one person to deal with in a simple, obvious way turns into a
> multi-day discussion in which some try to redesign entire email systems.)


Noel,

We have a significant number of serious problems that do need solving but are 
difficult.  That's frustrating.

So it's a lot more comforting to debate problems we /don't/ have.

d/
-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From cyrus@daboo.name  Thu Mar 15 10:57:38 2012
Return-Path: <cyrus@daboo.name>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 75CDE21F87CF for <ietf@ietfa.amsl.com>; Thu, 15 Mar 2012 10:57:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.624
X-Spam-Level: 
X-Spam-Status: No, score=-102.624 tagged_above=-999 required=5 tests=[AWL=-0.025, 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 JRJ0yxhabMDf for <ietf@ietfa.amsl.com>; Thu, 15 Mar 2012 10:57:38 -0700 (PDT)
Received: from daboo.name (daboo.name [173.13.55.49]) by ietfa.amsl.com (Postfix) with ESMTP id E766021F87C5 for <ietf@ietf.org>; Thu, 15 Mar 2012 10:57:37 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by daboo.name (Postfix) with ESMTP id 7360A239E760; Thu, 15 Mar 2012 13:57:37 -0400 (EDT)
X-Virus-Scanned: amavisd-new at daboo.name
Received: from daboo.name ([127.0.0.1]) by localhost (daboo.name [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OBkL75u-9Xde; Thu, 15 Mar 2012 13:57:36 -0400 (EDT)
Received: from caldav.corp.apple.com (unknown [17.45.162.46]) by daboo.name (Postfix) with ESMTPSA id 059BD239E753; Thu, 15 Mar 2012 13:57:34 -0400 (EDT)
Date: Thu, 15 Mar 2012 13:57:43 -0400
From: Cyrus Daboo <cyrus@daboo.name>
To: Pete Resnick <presnick@qualcomm.com>
Subject: Re: Issues relating to managing a mailing list...
Message-ID: <28C0FE4753BC78A85D5C66CB@caldav.corp.apple.com>
In-Reply-To: <4F620F85.9030702@qualcomm.com>
References: <1344A266-28E8-4228-908F-395FB41EDA83@amsl.com> <01OD44MYQ1ZY00ZUIL@mauve.mrochek.com>	<4F6145A0.3020705@gmail.com> <2103063.rDf6FqNnG2@scott-latitude-e6320> <39AB1CE59499893A8E276552@PST.JCK.COM> <8E4035C3ECF01FAE0CCDB05B@caldav.corp.apple.com> <4F620F85.9030702@qualcomm.com>
X-Mailer: Mulberry/4.1.0a3 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline; size=769
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Mar 2012 17:57:38 -0000

Hi Pete,

--On March 15, 2012 10:49:25 AM -0500 Pete Resnick <presnick@qualcomm.com> 
wrote:

>> Along those lines how about setting up an IETF IMAP server with
>> mailboxes for each mailing list hosted by the IETF?
>
> There has been a discussion under way for some time to get that to
> happen. I believe RFP's are being thought about (or written).

Right, so isn't this, 
<http://tools.ietf.org/html/draft-sparks-genarea-mailarch-05>, entirely 
satisfiable via IMAP? At the very least I think that draft needs another 
requirement:

* Users must be easily able to reply to archived messages using their email 
client of choice. In particular, replies need to preserve threading 
information in the form of References and In-Reply-To email headers.


-- 
Cyrus Daboo


From john-ietf@jck.com  Thu Mar 15 11:16:13 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 BAFFB21F87C3 for <ietf@ietfa.amsl.com>; Thu, 15 Mar 2012 11:16:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.751
X-Spam-Level: 
X-Spam-Status: No, score=-102.751 tagged_above=-999 required=5 tests=[AWL=-0.152, 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 E93AXdTLqCVD for <ietf@ietfa.amsl.com>; Thu, 15 Mar 2012 11:16:13 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id D374121F878B for <ietf@ietf.org>; Thu, 15 Mar 2012 11:16:12 -0700 (PDT)
Received: from [198.252.137.7] (helo=PST.JCK.COM) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1S8F8a-0001ZI-JK; Thu, 15 Mar 2012 14:10:56 -0400
Date: Thu, 15 Mar 2012 14:15:41 -0400
From: John C Klensin <john-ietf@jck.com>
To: Ned Freed <ned.freed@mrochek.com>
Subject: RE: Issues relating to managing a mailing list...
Message-ID: <949262FC3AC56C8CBDD2DFA9@PST.JCK.COM>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: 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, 15 Mar 2012 18:16:13 -0000

--On Thursday, March 15, 2012 08:16 -0700 Ned Freed
<ned.freed@mrochek.com> wrote:

>...
>> > It might be okay for really large attachments, as long as
>> > only a few messages are affected.
> 
>> Borrowing a bit from Randy, the solution to really large
>> attachments is to ban them.  Personally, I'd find it perfectly
>> reasonable to have any message in the megabyte range or above
>> (or probably even an order of magnitude smaller) rejected
>> with a message that amounted to "if you have that much to
>> say, write an I-D, post it, and point to it".  That is much
>> more plausible today, when the mean time between I-D
>> submission and posting is measured in minutes (except during
>> blackout periods) than when it was in days.  During blackout
>> periods, the last thing the community needs is people adding
>> to already-overloaded lists by posting long documents in
>> email.
>...
> You begin by talking about "banning large attachments". You
> then segue into a discussion where you talk about a maximum
> size that includes the primary message content, not
> attachments, then you throw in disclaimers, which may or may
> not be attachments.
> 
> Other have followed up by supporting the limit on attachment
> size, others still have talked about banning attachments
> regardless of size.
> 
> Do you see the problem here? The minute you start focusing on
> specifics of message content, you're in a rathole. What counts
> as an attachment? (And yes, we have a precise definition for
> what constitutes an attachement, but following that definition
> gives people the ability to route around it.)

Ok, that is fair.  At best, I skipped being explicit about
several steps in my thinking. I personally see the attachment
issue as almost irrelevant, in part because of the "what
constitutes an attachment" issue you identify above.  In partial
defense, I was distracted a bit by comments from others about
"the first N bytes of a message" and "text and attachment"
models (which, as you know better than almost anyone, is a user
construct about how messages might be assembled but one that
doesn't necessarily map directly and usefully back from MIME
body parts).  

I think the issue is almost entirely about 

	(i) size, independent of how a message is structured, and
	
	(ii) what, in IMAP terms, is automatic synchronization
	into offline or disconnected mode.  More generally, it
	is ability to read and work with IETF mailing lists at a
	time when one has little or no connectivity.

>From that point of view, Russ's original question is about
something that is not only a bad idea but an ill-formed
proposition... at least unless we could agree on and enforce a
particular model of IETF participants assemble messages and send
them -- a goal that I believe is so hopeless as to not be worth
discussing.

> It follows that any limit needs to be on overall message size.
> (Even this is a little perilous because message sizes can
> change due to MIME downgrading or upgrading, both of which
> happen regularly.)

Exactly.   And that also identifies the other distraction I was
trying to get at.  In addition to MIME downgrading and
upgrading, the size of a message can be distorted by such things
as addition (possibly by submission servers or list exploders
and out of user control) of lengthy explanatory headers
(including some called for by IETF standards like DKIM), body
text (including the notorious "unless you agree to this
conditions, please un-read the message" announcements but all
list-added footers), or duplicate content (e.g., sending both
text/plain and text/html with multipart/alternative).  If we
were to start trying to split hairs on how to count message
sizes, I think we would rapidly go down a slightly different rat
hole.

>  I would not be opposed to imposing such a
> limit, although it's going to need to be higher than some
> people would probably like - it's surprising how easily you
> can approach 1Mb with a single part, plain text message
> containing nothing remotely resembling an "attachment".

Yes.  But an entirely anecdotal survey of recent postings to the
IETF list and comparison with Thomas Narten's statistics
indicates that a posting to that list of 50K in aggregate size
is well out on the upper tail.  Most messages of twice that size
and larger are either duplicate content or inclusion of a great
deal of content from multiple previous messages. I'd be happy
discouraging both of those patterns for other reasons so
wouldn't be upset if a size rule had the accidental side-effect
of pushing back on them.  I can well imagine the averages for
some WG lists being much larger, especially if editors are
including blocks of existing and proposed text for comment.
But, as a notorious author of long messages and someone who
often prefers consolidated responses to a lot of small messages,
I'd struggle to believe that messages over even a half-megabyte
are frequent or that, when they do occur, we wouldn't be better
off if they were broken into multiple messages (and probably
threads).  But all of that is about how we would discuss setting
a size, not whether limits on, or special handling of, messages
of a particular size or "attachment" structure is desirable.

     john



From ned+ietf@mauve.mrochek.com  Thu Mar 15 11:21:07 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 4E47F21F87F1 for <ietf@ietfa.amsl.com>; Thu, 15 Mar 2012 11:21:07 -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 FAUEwIGfyC3s for <ietf@ietfa.amsl.com>; Thu, 15 Mar 2012 11:21:06 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id 6956321F87D2 for <ietf@ietf.org>; Thu, 15 Mar 2012 11:21:06 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OD55IQQOTS0176YX@mauve.mrochek.com> for ietf@ietf.org; Thu, 15 Mar 2012 11:21:03 -0700 (PDT)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OCPMUVDUMO00ZUIL@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Thu, 15 Mar 2012 11:20:56 -0700 (PDT)
From: ned+ietf@mauve.mrochek.com
Message-id: <01OD55IN7ESG00ZUIL@mauve.mrochek.com>
Date: Thu, 15 Mar 2012 11:14:16 -0700 (PDT)
Subject: Re: Issues relating to managing a mailing list...
In-reply-to: "Your message dated Thu, 15 Mar 2012 17:52:53 +0100 (MET)" <01OD5JKATQOEKHXOTX@mx.isti.cnr.it>
MIME-version: 1.0
Content-type: TEXT/PLAIN
References: <1344A266-28E8-4228-908F-395FB41EDA83@amsl.com> <30461C26-EDCE-4BFD-8E82-AF1CC5BC371C@vigilsec.com> <01OD44MYQ1ZY00ZUIL@mauve.mrochek.com> <m27gymcqhs.wl%randy@psg.com> <01OD4Z4LSYYWKN0DXO@mx.isti.cnr.it> <01OD4YUXNIUY00ZUIL@mauve.mrochek.com> <01OD5JKATQOEKHXOTX@mx.isti.cnr.it>
To: Francesco Gennai <francesco.gennai@isti.cnr.it>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mrochek.com; s=mauve; t=1331835668; i=@mrochek.com; bh=fjYJtA4PpVfIVd6GgGlGEFKUH1BoWWcuJniZq8mB7qw=;  h=From:Cc:Message-id:Date:Subject:In-reply-to:MIME-version: Content-type:References:To; b=KAEqjgsIZ9GTxS2yssw1w4qnsLrEPQ+hmkli2w3N2Lha4OATR+tdm4N3jLsslppQY DiRQoiPxqg2K65263DQgVRIEF5/A0+4ETI6NTll5X1oeq1XdgayaKkUjTAtwfOr9DB GSP+Vo2kbncqpuEhaXD6A5pLQ/C29mQYdHFJfUFk=
Cc: Ned Freed <ned.freed@mrochek.com>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Mar 2012 18:21:07 -0000

> > > > > Is this really a big enough problem to be worth solving? I can't
> > > > > recall a single instance where I received IETF list with a problematic
> > > > > attachment.

> > > > i travel to places with very poor bandwidth.  it is a problem.

> > > > and the vast majority of users just do not get it.  "we send 20mb
> > > > documents around the office all the time.  suck it up."


> > > for who has problem in attachment downloading the solution should be
> > > at the delivery Message Store level, where the strip of the attachment could be
> > > done accordingly to an user configurable mailbox parameter
> > > (as we do on our server, where we call it Easy Delivery).

> > Or better still, don't strip anything. Use a reasonably capable client and
> > that doesn't fetch attachments unless you tell it to.

> Yes, I agree, but we can leave the end user to choose accordingly their own
> no capable/capable clients or maybe accordingly to temporary condition.

You can as long as attachments remain as attachments, which will no longer be
true if this proposal is implemented. If they don't the "strip attachments"
approach no longer works. You either (a) Only strip attachments, which leaves
you with large messages to deal with, (b) Strip by part size, which will leave
you with empty message, or (c) Cut parts down to a given size, which is
guaranteed to work poorly.

The two list approach, if secondary list proves popaular, may lead to the same
result, BTW. As I commented previously in a private email, it never ceases
to amaze me how people in this community only apply the "route around
problems" mantra when it suits their purpose to do so.

				Ned

From mcr@sandelman.ca  Thu Mar 15 11:24:07 2012
Return-Path: <mcr@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B6E7821F867B for <ietf@ietfa.amsl.com>; Thu, 15 Mar 2012 11:24:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.681
X-Spam-Level: 
X-Spam-Status: No, score=-1.681 tagged_above=-999 required=5 tests=[AWL=0.273,  BAYES_00=-2.599, HOST_MISMATCH_NET=0.311, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id e3mBH4U-RT35 for <ietf@ietfa.amsl.com>; Thu, 15 Mar 2012 11:24:07 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [67.23.6.41]) by ietfa.amsl.com (Postfix) with ESMTP id A3FF221F86E8 for <ietf@ietf.org>; Thu, 15 Mar 2012 11:24:06 -0700 (PDT)
Received: from marajade.sandelman.ca (unknown [132.213.236.41]) by relay.sandelman.ca (Postfix) with ESMTPS id 5153FA0080 for <ietf@ietf.org>; Thu, 15 Mar 2012 14:21:30 -0400 (EDT)
Received: by marajade.sandelman.ca (Postfix, from userid 179) id 0ED5F983B9; Thu, 15 Mar 2012 14:24:06 -0400 (EDT)
Received: from marajade.sandelman.ca (localhost [127.0.0.1]) by marajade.sandelman.ca (Postfix) with ESMTP id 0DFFA983B8 for <ietf@ietf.org>; Thu, 15 Mar 2012 14:24:06 -0400 (EDT)
From: Michael Richardson <mcr@sandelman.ca>
To: ietf@ietf.org
Subject: Re: Issues relating to managing a mailing list...
In-Reply-To: <8E4035C3ECF01FAE0CCDB05B@caldav.corp.apple.com>
References: <1344A266-28E8-4228-908F-395FB41EDA83@amsl.com> <01OD44MYQ1ZY00ZUIL@mauve.mrochek.com> <4F6145A0.3020705@gmail.com> <2103063.rDf6FqNnG2@scott-latitude-e6320> <39AB1CE59499893A8E276552@PST.JCK.COM> <8E4035C3ECF01FAE0CCDB05B@caldav.corp.apple.com>
X-Mailer: MH-E 8.3; nmh 1.3-dev; XEmacs 21.4 (patch 22)
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Thu, 15 Mar 2012 14:24:06 -0400
Message-ID: <22119.1331835846@marajade.sandelman.ca>
Sender: mcr@sandelman.ca
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Mar 2012 18:24:08 -0000

--=-=-=


>>>>> "Cyrus" == Cyrus Daboo <cyrus@daboo.name> writes:

    Cyrus> Along those lines how about setting up an IETF IMAP server
    Cyrus> with mailboxes for each mailing list hosted by the IETF? That
    Cyrus> way anyone with a capable IMAP client (one that can

How about we use the protocol that was designed for this...  NNTP?




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

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

iQCVAwUAT2IzxYqHRg3pndX9AQL8pAQAxafPLQLnYXHjAnp4njvxiZZJPFQgWq9a
5Pzmv1hU//4MIQaoDrT6k/ePUXrutQL43jIRQ7MK+8IQGxBOBZAAieO2XQDcfUjj
tc2U4njAhRZpm0R8OHL2/EXihhPKyjQ8VRuGmFcj5prxE2dHaLHvU21E7w64lbPp
NMsier4JsdI=
=Pc2p
-----END PGP SIGNATURE-----
--=-=-=--

From rjsparks@nostrum.com  Thu Mar 15 11:37:29 2012
Return-Path: <rjsparks@nostrum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E1DE021F8704 for <ietf@ietfa.amsl.com>; Thu, 15 Mar 2012 11:37:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.555
X-Spam-Level: 
X-Spam-Status: No, score=-102.555 tagged_above=-999 required=5 tests=[AWL=0.045, 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 5WBnIjW8FzXD for <ietf@ietfa.amsl.com>; Thu, 15 Mar 2012 11:37:29 -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 5166021F86BE for <ietf@ietf.org>; Thu, 15 Mar 2012 11:37:29 -0700 (PDT)
Received: from unexplicable.local (pool-71-170-125-181.dllstx.fios.verizon.net [71.170.125.181]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id q2FIbR1w044527 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Thu, 15 Mar 2012 13:37:28 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
Message-ID: <4F6236E6.5030303@nostrum.com>
Date: Thu, 15 Mar 2012 13:37:26 -0500
From: Robert Sparks <rjsparks@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Issues relating to managing a mailing list...
References: <1344A266-28E8-4228-908F-395FB41EDA83@amsl.com> <01OD44MYQ1ZY00ZUIL@mauve.mrochek.com>	<4F6145A0.3020705@gmail.com> <2103063.rDf6FqNnG2@scott-latitude-e6320> <39AB1CE59499893A8E276552@PST.JCK.COM> <8E4035C3ECF01FAE0CCDB05B@caldav.corp.apple.com> <4F620F85.9030702@qualcomm.com> <28C0FE4753BC78A85D5C66CB@caldav.corp.apple.com>
In-Reply-To: <28C0FE4753BC78A85D5C66CB@caldav.corp.apple.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (nostrum.com: 71.170.125.181 is authenticated by a trusted mechanism)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Mar 2012 18:37:30 -0000

The current plan is to investigate both a web based archive access 
mechanism and an IMAP based one.

I split the requirements for them into two drafts so the projects could 
be pursued separately.
See also <https://datatracker.ietf.org/doc/draft-sparks-genarea-imaparch/>



On 3/15/12 12:57 PM, Cyrus Daboo wrote:
> Hi Pete,
>
> --On March 15, 2012 10:49:25 AM -0500 Pete Resnick 
> <presnick@qualcomm.com> wrote:
>
>>> Along those lines how about setting up an IETF IMAP server with
>>> mailboxes for each mailing list hosted by the IETF?
>>
>> There has been a discussion under way for some time to get that to
>> happen. I believe RFP's are being thought about (or written).
>
> Right, so isn't this, 
> <http://tools.ietf.org/html/draft-sparks-genarea-mailarch-05>, 
> entirely satisfiable via IMAP? At the very least I think that draft 
> needs another requirement:
>
> * Users must be easily able to reply to archived messages using their 
> email client of choice. In particular, replies need to preserve 
> threading information in the form of References and In-Reply-To email 
> headers.
Ack.
>
>

From ned+ietf@mauve.mrochek.com  Thu Mar 15 11:39:06 2012
Return-Path: <ned+ietf@mauve.mrochek.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B8BC521F849C for <ietf@ietfa.amsl.com>; Thu, 15 Mar 2012 11:39:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.588
X-Spam-Level: 
X-Spam-Status: No, score=-2.588 tagged_above=-999 required=5 tests=[AWL=0.011,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xM61zdADi35D for <ietf@ietfa.amsl.com>; Thu, 15 Mar 2012 11:39:05 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id 3A22421F8698 for <ietf@ietf.org>; Thu, 15 Mar 2012 11:38:59 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OD565PC0SW006QT2@mauve.mrochek.com> for ietf@ietf.org; Thu, 15 Mar 2012 11:38:47 -0700 (PDT)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OCPMUVDUMO00ZUIL@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Thu, 15 Mar 2012 11:38:41 -0700 (PDT)
From: ned+ietf@mauve.mrochek.com
Message-id: <01OD565M711800ZUIL@mauve.mrochek.com>
Date: Thu, 15 Mar 2012 11:38:04 -0700 (PDT)
Subject: RE: Issues relating to managing a mailing list...
In-reply-to: "Your message dated Thu, 15 Mar 2012 14:15:41 -0400" <949262FC3AC56C8CBDD2DFA9@PST.JCK.COM>
MIME-version: 1.0
Content-type: TEXT/PLAIN
References: <949262FC3AC56C8CBDD2DFA9@PST.JCK.COM>
To: John C Klensin <john-ietf@jck.com>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mrochek.com; s=mauve; t=1331836732; i=@mrochek.com; bh=42aYSpr3Twhtdysxfr8StfxoeoDlASu3uFRSjXU7caw=;  h=From:Cc:Message-id:Date:Subject:In-reply-to:MIME-version: Content-type:References:To; b=bH31VSA7L2WpT6g7GnqhXwO0PV9exPj4ExFpLgCBsbIZxYj6NKU24I5+X+wCY51fv Y/KtcRgSJDizwJ8RBKkAoEGbUInjj77Hnk7MYQUQkKCrIYFC0k8mzxZgBCU6Z6cUhd y+yAyIMmwnIiCuiCJnQlLnc6dJTA6b3wmnuiAuB8=
Cc: Ned Freed <ned.freed@mrochek.com>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Mar 2012 18:39:06 -0000

John, I agree completely with everything you say here.

				Ned

> --On Thursday, March 15, 2012 08:16 -0700 Ned Freed
> <ned.freed@mrochek.com> wrote:

> >...
> >> > It might be okay for really large attachments, as long as
> >> > only a few messages are affected.
> >
> >> Borrowing a bit from Randy, the solution to really large
> >> attachments is to ban them.  Personally, I'd find it perfectly
> >> reasonable to have any message in the megabyte range or above
> >> (or probably even an order of magnitude smaller) rejected
> >> with a message that amounted to "if you have that much to
> >> say, write an I-D, post it, and point to it".  That is much
> >> more plausible today, when the mean time between I-D
> >> submission and posting is measured in minutes (except during
> >> blackout periods) than when it was in days.  During blackout
> >> periods, the last thing the community needs is people adding
> >> to already-overloaded lists by posting long documents in
> >> email.
> >...
> > You begin by talking about "banning large attachments". You
> > then segue into a discussion where you talk about a maximum
> > size that includes the primary message content, not
> > attachments, then you throw in disclaimers, which may or may
> > not be attachments.
> >
> > Other have followed up by supporting the limit on attachment
> > size, others still have talked about banning attachments
> > regardless of size.
> >
> > Do you see the problem here? The minute you start focusing on
> > specifics of message content, you're in a rathole. What counts
> > as an attachment? (And yes, we have a precise definition for
> > what constitutes an attachement, but following that definition
> > gives people the ability to route around it.)

> Ok, that is fair.  At best, I skipped being explicit about
> several steps in my thinking. I personally see the attachment
> issue as almost irrelevant, in part because of the "what
> constitutes an attachment" issue you identify above.  In partial
> defense, I was distracted a bit by comments from others about
> "the first N bytes of a message" and "text and attachment"
> models (which, as you know better than almost anyone, is a user
> construct about how messages might be assembled but one that
> doesn't necessarily map directly and usefully back from MIME
> body parts).

> I think the issue is almost entirely about

> 	(i) size, independent of how a message is structured, and
	
> 	(ii) what, in IMAP terms, is automatic synchronization
> 	into offline or disconnected mode.  More generally, it
> 	is ability to read and work with IETF mailing lists at a
> 	time when one has little or no connectivity.

> >From that point of view, Russ's original question is about
> something that is not only a bad idea but an ill-formed
> proposition... at least unless we could agree on and enforce a
> particular model of IETF participants assemble messages and send
> them -- a goal that I believe is so hopeless as to not be worth
> discussing.

> > It follows that any limit needs to be on overall message size.
> > (Even this is a little perilous because message sizes can
> > change due to MIME downgrading or upgrading, both of which
> > happen regularly.)

> Exactly.   And that also identifies the other distraction I was
> trying to get at.  In addition to MIME downgrading and
> upgrading, the size of a message can be distorted by such things
> as addition (possibly by submission servers or list exploders
> and out of user control) of lengthy explanatory headers
> (including some called for by IETF standards like DKIM), body
> text (including the notorious "unless you agree to this
> conditions, please un-read the message" announcements but all
> list-added footers), or duplicate content (e.g., sending both
> text/plain and text/html with multipart/alternative).  If we
> were to start trying to split hairs on how to count message
> sizes, I think we would rapidly go down a slightly different rat
> hole.

> >  I would not be opposed to imposing such a
> > limit, although it's going to need to be higher than some
> > people would probably like - it's surprising how easily you
> > can approach 1Mb with a single part, plain text message
> > containing nothing remotely resembling an "attachment".

> Yes.  But an entirely anecdotal survey of recent postings to the
> IETF list and comparison with Thomas Narten's statistics
> indicates that a posting to that list of 50K in aggregate size
> is well out on the upper tail.  Most messages of twice that size
> and larger are either duplicate content or inclusion of a great
> deal of content from multiple previous messages. I'd be happy
> discouraging both of those patterns for other reasons so
> wouldn't be upset if a size rule had the accidental side-effect
> of pushing back on them.  I can well imagine the averages for
> some WG lists being much larger, especially if editors are
> including blocks of existing and proposed text for comment.
> But, as a notorious author of long messages and someone who
> often prefers consolidated responses to a lot of small messages,
> I'd struggle to believe that messages over even a half-megabyte
> are frequent or that, when they do occur, we wouldn't be better
> off if they were broken into multiple messages (and probably
> threads).  But all of that is about how we would discuss setting
> a size, not whether limits on, or special handling of, messages
> of a particular size or "attachment" structure is desirable.

>      john



From dhc@dcrocker.net  Thu Mar 15 11:39:34 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 AB02921E8019 for <ietf@ietfa.amsl.com>; Thu, 15 Mar 2012 11:39:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.606
X-Spam-Level: 
X-Spam-Status: No, score=-6.606 tagged_above=-999 required=5 tests=[AWL=-0.007, 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 HlRPVCA5wCJ0 for <ietf@ietfa.amsl.com>; Thu, 15 Mar 2012 11:39:33 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id D70AC21F8574 for <ietf@ietf.org>; Thu, 15 Mar 2012 11:39:33 -0700 (PDT)
Received: from [192.168.1.11] (adsl-67-127-58-62.dsl.pltn13.pacbell.net [67.127.58.62]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q2FIdPuu001673 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 15 Mar 2012 11:39:30 -0700
Message-ID: <4F623742.9010604@dcrocker.net>
Date: Thu, 15 Mar 2012 11:38:58 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: Pete Resnick <presnick@qualcomm.com>
Subject: Re: Issues relating to managing a mailing list...
References: <1344A266-28E8-4228-908F-395FB41EDA83@amsl.com>	<01OD44MYQ1ZY00ZUIL@mauve.mrochek.com>	<4F6145A0.3020705@gmail.com>	<2103063.rDf6FqNnG2@scott-latitude-e6320>	<39AB1CE59499893A8E276552@PST.JCK.COM> <8E4035C3ECF01FAE0CCDB05B@caldav.corp.apple.com> <4F620F85.9030702@qualcomm.com>
In-Reply-To: <4F620F85.9030702@qualcomm.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Thu, 15 Mar 2012 11:39:30 -0700 (PDT)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Mar 2012 18:39:34 -0000

On 3/15/2012 8:49 AM, Pete Resnick wrote:
>
> There has been a discussion under way for some time to get that to happen. I
> believe RFP's are being thought about (or written).


we have just entered the RFI stage.  I see that as progress.

d/
-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From presnick@qualcomm.com  Thu Mar 15 11:41:00 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 DA2BF21F8734 for <ietf@ietfa.amsl.com>; Thu, 15 Mar 2012 11:41:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.571
X-Spam-Level: 
X-Spam-Status: No, score=-106.571 tagged_above=-999 required=5 tests=[AWL=0.028, 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 LsGibuFr3-gD for <ietf@ietfa.amsl.com>; Thu, 15 Mar 2012 11:41:00 -0700 (PDT)
Received: from wolverine01.qualcomm.com (wolverine01.qualcomm.com [199.106.114.254]) by ietfa.amsl.com (Postfix) with ESMTP id F40D421F8722 for <ietf@ietf.org>; Thu, 15 Mar 2012 11:40:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=presnick@qualcomm.com; q=dns/txt; s=qcdkim; t=1331836859; x=1363372859; h=message-id:date:from:user-agent:mime-version:to:cc: subject:references:in-reply-to:content-type: content-transfer-encoding:x-originating-ip; z=Message-ID:=20<4F6237B8.4090600@qualcomm.com>|Date:=20Th u,=2015=20Mar=202012=2013:40:56=20-0500|From:=20Pete=20Re snick=20<presnick@qualcomm.com>|User-Agent:=20Mozilla/5.0 =20(Macintosh=3B=20U=3B=20Intel=20Mac=20OS=20X=2010.6=3B =20en-US=3B=20rv:1.9.1.9)=20Gecko/20100630=20Eudora/3.0.4 |MIME-Version:=201.0|To:=20<dcrocker@bbiw.net>|CC:=20Dave =20Crocker=20<dhc@dcrocker.net>,=20<ietf@ietf.org> |Subject:=20Re:=20Issues=20relating=20to=20managing=20a =20mailing=20list...|References:=20<1344A266-28E8-4228-90 8F-395FB41EDA83@amsl.com>=09<01OD44MYQ1ZY00ZUIL@mauve.mro chek.com>=09<4F6145A0.3020705@gmail.com>=09<2103063.rDf6F qNnG2@scott-latitude-e6320>=09<39AB1CE59499893A8E276552@P ST.JCK.COM>=20<8E4035C3ECF01FAE0CCDB05B@caldav.corp.apple .com>=20<4F620F85.9030702@qualcomm.com>=20<4F623742.90106 04@dcrocker.net>|In-Reply-To:=20<4F623742.9010604@dcrocke r.net>|Content-Type:=20text/plain=3B=20charset=3D"ISO-885 9-1"=3B=20format=3Dflowed|Content-Transfer-Encoding:=207b it|X-Originating-IP:=20[172.30.39.5]; bh=1Jhao4f63RuTrKfNDdnKCZKyHwhUuk7hLCGmmDg+orw=; b=zb4seP0SaibjLHdLSbuOoP7F0oH5bJ753VmovKzNN4KLreXiMElbgyyR Hb5ev7iBYUGejDJ1C8eBiSGo3PbmVZ9uqQwWKQjDXyPz/fbrLevRDvA6f 4Y2cKI4nuSdlrX+OFI9mjclPL3S/BD32vjMcn5XWAUMEh0OkMMqZQl8Jt 8=;
X-IronPort-AV: E=McAfee;i="5400,1158,6650"; a="172828430"
Received: from ironmsg03-l.qualcomm.com ([172.30.48.18]) by wolverine01.qualcomm.com with ESMTP; 15 Mar 2012 11:40:59 -0700
X-IronPort-AV: E=Sophos;i="4.73,591,1325491200"; d="scan'208";a="191523479"
Received: from nasanexhc08.na.qualcomm.com ([172.30.39.7]) by Ironmsg03-L.qualcomm.com with ESMTP/TLS/AES128-SHA; 15 Mar 2012 11:40:59 -0700
Received: from resnick2.qualcomm.com (172.30.39.5) by qcmail1.qualcomm.com (172.30.39.7) with Microsoft SMTP Server (TLS) id 14.1.339.1; Thu, 15 Mar 2012 11:40:58 -0700
Message-ID: <4F6237B8.4090600@qualcomm.com>
Date: Thu, 15 Mar 2012 13:40:56 -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: <dcrocker@bbiw.net>
Subject: Re: Issues relating to managing a mailing list...
References: <1344A266-28E8-4228-908F-395FB41EDA83@amsl.com>	<01OD44MYQ1ZY00ZUIL@mauve.mrochek.com>	<4F6145A0.3020705@gmail.com>	<2103063.rDf6FqNnG2@scott-latitude-e6320>	<39AB1CE59499893A8E276552@PST.JCK.COM> <8E4035C3ECF01FAE0CCDB05B@caldav.corp.apple.com> <4F620F85.9030702@qualcomm.com> <4F623742.9010604@dcrocker.net>
In-Reply-To: <4F623742.9010604@dcrocker.net>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.39.5]
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Mar 2012 18:41:01 -0000

On 3/15/12 1:38 PM, Dave Crocker wrote:
> we have just entered the RFI stage.  I see that as progress.

For draft-sparks-genarea-imaparch, or just draft-sparks-genarea-mailarch?

pr

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


From presnick@qualcomm.com  Thu Mar 15 11:45:54 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 8B88921E8014 for <ietf@ietfa.amsl.com>; Thu, 15 Mar 2012 11:45:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.571
X-Spam-Level: 
X-Spam-Status: No, score=-106.571 tagged_above=-999 required=5 tests=[AWL=0.028, 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 gh5VSW+nNt61 for <ietf@ietfa.amsl.com>; Thu, 15 Mar 2012 11:45:52 -0700 (PDT)
Received: from wolverine01.qualcomm.com (wolverine01.qualcomm.com [199.106.114.254]) by ietfa.amsl.com (Postfix) with ESMTP id A149721F8716 for <ietf@ietf.org>; Thu, 15 Mar 2012 11:45:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=presnick@qualcomm.com; q=dns/txt; s=qcdkim; t=1331837152; x=1363373152; h=message-id:date:from:user-agent:mime-version:to:cc: subject:references:in-reply-to:content-type: content-transfer-encoding:x-originating-ip; z=Message-ID:=20<4F6238DD.4070008@qualcomm.com>|Date:=20Th u,=2015=20Mar=202012=2013:45:49=20-0500|From:=20Pete=20Re snick=20<presnick@qualcomm.com>|User-Agent:=20Mozilla/5.0 =20(Macintosh=3B=20U=3B=20Intel=20Mac=20OS=20X=2010.6=3B =20en-US=3B=20rv:1.9.1.9)=20Gecko/20100630=20Eudora/3.0.4 |MIME-Version:=201.0|To:=20<dcrocker@bbiw.net>|CC:=20<iet f@ietf.org>|Subject:=20Re:=20Issues=20relating=20to=20man aging=20a=20mailing=20list...|References:=20<1344A266-28E 8-4228-908F-395FB41EDA83@amsl.com>=09<01OD44MYQ1ZY00ZUIL@ mauve.mrochek.com>=09<4F6145A0.3020705@gmail.com>=09<2103 063.rDf6FqNnG2@scott-latitude-e6320>=09<39AB1CE59499893A8 E276552@PST.JCK.COM>=09<8E4035C3ECF01FAE0CCDB05B@caldav.c orp.apple.com>=09<4F620F85.9030702@qualcomm.com>=20<4F623 742.9010604@dcrocker.net>=20<4F6237B8.4090600@qualcomm.co m>|In-Reply-To:=20<4F6237B8.4090600@qualcomm.com> |Content-Type:=20text/plain=3B=20charset=3D"ISO-8859-1" =3B=20format=3Dflowed|Content-Transfer-Encoding:=207bit |X-Originating-IP:=20[172.30.39.5]; bh=7/aTqgUEnoceExZojmhzsRUYFkCqzbuhDgNkZBn376A=; b=c43u1G75Z3Xy8pPZE6zAr3I3A8VYJeyQDg9atsH5zkfKQxlQ9ZbdBpJv wlOG0CwgmyG/f8QjxGHMn5OzPlid/98gE/cAX6mpQPROD445lYF1qCQLe +xIt7DTXbkHTtc67PEyUTlhPtbudXzVpXXBDscEINuVA8jqGuYyBrzSmU A=;
X-IronPort-AV: E=McAfee;i="5400,1158,6650"; a="172829825"
Received: from ironmsg04-l.qualcomm.com ([172.30.48.19]) by wolverine01.qualcomm.com with ESMTP; 15 Mar 2012 11:45:52 -0700
X-IronPort-AV: E=Sophos;i="4.73,591,1325491200"; d="scan'208";a="176780729"
Received: from nasanexhc08.na.qualcomm.com ([172.30.39.7]) by Ironmsg04-L.qualcomm.com with ESMTP/TLS/AES128-SHA; 15 Mar 2012 11:45:52 -0700
Received: from resnick2.qualcomm.com (172.30.39.5) by qcmail1.qualcomm.com (172.30.39.7) with Microsoft SMTP Server (TLS) id 14.1.339.1; Thu, 15 Mar 2012 11:45:52 -0700
Message-ID: <4F6238DD.4070008@qualcomm.com>
Date: Thu, 15 Mar 2012 13:45:49 -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: <dcrocker@bbiw.net>
Subject: Re: Issues relating to managing a mailing list...
References: <1344A266-28E8-4228-908F-395FB41EDA83@amsl.com>	<01OD44MYQ1ZY00ZUIL@mauve.mrochek.com>	<4F6145A0.3020705@gmail.com>	<2103063.rDf6FqNnG2@scott-latitude-e6320>	<39AB1CE59499893A8E276552@PST.JCK.COM>	<8E4035C3ECF01FAE0CCDB05B@caldav.corp.apple.com>	<4F620F85.9030702@qualcomm.com> <4F623742.9010604@dcrocker.net> <4F6237B8.4090600@qualcomm.com>
In-Reply-To: <4F6237B8.4090600@qualcomm.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.39.5]
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Mar 2012 18:45:54 -0000

On 3/15/12 1:40 PM, Pete Resnick wrote:
> On 3/15/12 1:38 PM, Dave Crocker wrote:
>> we have just entered the RFI stage.  I see that as progress.
>
> For draft-sparks-genarea-imaparch, or just draft-sparks-genarea-mailarch?

Nevermind. I am told it is for the latter. The former is being handled 
separately, and is also making progress.

pr

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


From marshall.eubanks@gmail.com  Thu Mar 15 13:18:47 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 4C3C921F854C for <ietf@ietfa.amsl.com>; Thu, 15 Mar 2012 13:18:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.533
X-Spam-Level: 
X-Spam-Status: No, score=-103.533 tagged_above=-999 required=5 tests=[AWL=0.066, 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 PhIbHvL7AsLB for <ietf@ietfa.amsl.com>; Thu, 15 Mar 2012 13:18:46 -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 5358A21F854B for <ietf@ietf.org>; Thu, 15 Mar 2012 13:18:46 -0700 (PDT)
Received: by lbol12 with SMTP id l12so1953487lbo.31 for <ietf@ietf.org>; Thu, 15 Mar 2012 13:18:45 -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=dlQiKx6UqkhhflV6Jeaagw16vMJaC2UwHWhs9iMID6U=; b=zdusVEF8ktfvVc0X3hqg+rin6tlzw3FI0Lyji7M17wbTLot8it6caCT+ubna/ASImk 0PDklMPtZ2yVGbU364qqk6MQdHLr78tJz0iCJ8oBHqHaXN3USp7H+fpFxdhDVHihAqHp Z4m/zroordcvUewi5TXxs1Sfo+Ap1ollixRQfmW/Fzf8C3A44MOzMrXP9f2Ft5TYboes L0Btqnm6Y4GSBRPNssLfAew3zYXZAVxtMwmqKsiAx69h+AH7FA0CGPKJ0DL6qcpL5QIz iKTKEOUZnF75k0OXa2RwIbW2umF560+45TQ+3I7tpNBD0JThQ/6cEUM5kjONBvIyzoKR FHSQ==
MIME-Version: 1.0
Received: by 10.112.84.233 with SMTP id c9mr26837lbz.1.1331842725311; Thu, 15 Mar 2012 13:18:45 -0700 (PDT)
Received: by 10.112.115.98 with HTTP; Thu, 15 Mar 2012 13:18:45 -0700 (PDT)
In-Reply-To: <28C0FE4753BC78A85D5C66CB@caldav.corp.apple.com>
References: <1344A266-28E8-4228-908F-395FB41EDA83@amsl.com> <01OD44MYQ1ZY00ZUIL@mauve.mrochek.com> <4F6145A0.3020705@gmail.com> <2103063.rDf6FqNnG2@scott-latitude-e6320> <39AB1CE59499893A8E276552@PST.JCK.COM> <8E4035C3ECF01FAE0CCDB05B@caldav.corp.apple.com> <4F620F85.9030702@qualcomm.com> <28C0FE4753BC78A85D5C66CB@caldav.corp.apple.com>
Date: Thu, 15 Mar 2012 16:18:45 -0400
Message-ID: <CAJNg7VK8v1U2Gw9BysO-xZ+gNHjbfeitS1PRbjD0ogQRzNrHag@mail.gmail.com>
Subject: Re: Issues relating to managing a mailing list...
From: Marshall Eubanks <marshall.eubanks@gmail.com>
To: Cyrus Daboo <cyrus@daboo.name>
Content-Type: text/plain; charset=ISO-8859-1
Cc: Pete Resnick <presnick@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: Thu, 15 Mar 2012 20:18:47 -0000

Since the problem is a relative handful of large attachments, could a
solution just be to provide a repository for
mailing list members to store such files, yielding a URL they could
use in an email ? Then, the usual list feedback
would keep the attachment sizes manageable.

Obviously, there would be some issues about security (e.g., avoiding
hidden porn storage),
but they don't seem insurmountable in context For example, the link
could be non-functional until the URL was
used in an email to the appropriate mailing list. Then, the usual
moderation tools should suffice to take care
of inappropriate content.

Regards
Marshall

On Thu, Mar 15, 2012 at 1:57 PM, Cyrus Daboo <cyrus@daboo.name> wrote:
> Hi Pete,
>
>
> --On March 15, 2012 10:49:25 AM -0500 Pete Resnick <presnick@qualcomm.com>
> wrote:
>
>>> Along those lines how about setting up an IETF IMAP server with
>>> mailboxes for each mailing list hosted by the IETF?
>>
>>
>> There has been a discussion under way for some time to get that to
>> happen. I believe RFP's are being thought about (or written).
>
>
> Right, so isn't this,
> <http://tools.ietf.org/html/draft-sparks-genarea-mailarch-05>, entirely
> satisfiable via IMAP? At the very least I think that draft needs another
> requirement:
>
> * Users must be easily able to reply to archived messages using their email
> client of choice. In particular, replies need to preserve threading
> information in the form of References and In-Reply-To email headers.
>
>
> --
> Cyrus Daboo
>

From presnick@qualcomm.com  Thu Mar 15 13:41:05 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 27DC921E8020 for <ietf@ietfa.amsl.com>; Thu, 15 Mar 2012 13:41:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.572
X-Spam-Level: 
X-Spam-Status: No, score=-106.572 tagged_above=-999 required=5 tests=[AWL=0.027, 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 VSZ3M9xMH2-h for <ietf@ietfa.amsl.com>; Thu, 15 Mar 2012 13:41:04 -0700 (PDT)
Received: from wolverine01.qualcomm.com (wolverine01.qualcomm.com [199.106.114.254]) by ietfa.amsl.com (Postfix) with ESMTP id 94CAE21E8010 for <ietf@ietf.org>; Thu, 15 Mar 2012 13:41:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=presnick@qualcomm.com; q=dns/txt; s=qcdkim; t=1331844064; x=1363380064; h=message-id:date:from:user-agent:mime-version:to:cc: subject:references:in-reply-to:content-type: content-transfer-encoding:x-originating-ip; z=Message-ID:=20<4F6253CA.9020507@qualcomm.com>|Date:=20Th u,=2015=20Mar=202012=2015:40:42=20-0500|From:=20Pete=20Re snick=20<presnick@qualcomm.com>|User-Agent:=20Mozilla/5.0 =20(Macintosh=3B=20U=3B=20Intel=20Mac=20OS=20X=2010.6=3B =20en-US=3B=20rv:1.9.1.9)=20Gecko/20100630=20Eudora/3.0.4 |MIME-Version:=201.0|To:=20Marshall=20Eubanks=20<marshall .eubanks@gmail.com>|CC:=20Cyrus=20Daboo=20<cyrus@daboo.na me>,=20<ietf@ietf.org>|Subject:=20Re:=20Issues=20relating =20to=20managing=20a=20mailing=20list...|References:=20<1 344A266-28E8-4228-908F-395FB41EDA83@amsl.com>=09<01OD44MY Q1ZY00ZUIL@mauve.mrochek.com>=20<4F6145A0.3020705@gmail.c om>=09<2103063.rDf6FqNnG2@scott-latitude-e6320>=09<39AB1C E59499893A8E276552@PST.JCK.COM>=09<8E4035C3ECF01FAE0CCDB0 5B@caldav.corp.apple.com>=09<4F620F85.9030702@qualcomm.co m>=09<28C0FE4753BC78A85D5C66CB@caldav.corp.apple.com>=20< CAJNg7VK8v1U2Gw9BysO-xZ+gNHjbfeitS1PRbjD0ogQRzNrHag@mail. gmail.com>|In-Reply-To:=20<CAJNg7VK8v1U2Gw9BysO-xZ+gNHjbf eitS1PRbjD0ogQRzNrHag@mail.gmail.com>|Content-Type:=20tex t/plain=3B=20charset=3D"ISO-8859-1"=3B=20format=3Dflowed |Content-Transfer-Encoding:=207bit|X-Originating-IP:=20[1 72.30.39.5]; bh=vEH9fCPENm/Ps2Rb1KnHpY/fZcY1gv+4D/mYRxVZFy8=; b=lCIQmYSR3++cCH8FLhF1chTx+SXNDTJVxBqHC1blJRv1SwAL1XZIz0YB JxlBL8Y1Nj6JjCwxiH4OnzPTcTDLsHAzAeIe3Sc2pddr5PLrPrFyM16pI e/nuCZRo0I5Dz7Ehl7vyua0RENP/e5bhOgOXOMoE4mk57Ubf9fs3WcvgT Y=;
X-IronPort-AV: E=McAfee;i="5400,1158,6650"; a="172884119"
Received: from ironmsg04-r.qualcomm.com ([172.30.46.18]) by wolverine01.qualcomm.com with ESMTP; 15 Mar 2012 13:41:04 -0700
X-IronPort-AV: E=Sophos;i="4.73,591,1325491200"; d="scan'208";a="284555885"
Received: from nasanexhc07.na.qualcomm.com ([172.30.39.190]) by Ironmsg04-R.qualcomm.com with ESMTP/TLS/AES128-SHA; 15 Mar 2012 13:40:44 -0700
Received: from resnick2.qualcomm.com (172.30.39.5) by qcmail1.qualcomm.com (172.30.39.190) with Microsoft SMTP Server (TLS) id 14.1.339.1; Thu, 15 Mar 2012 13:40:43 -0700
Message-ID: <4F6253CA.9020507@qualcomm.com>
Date: Thu, 15 Mar 2012 15:40:42 -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: Marshall Eubanks <marshall.eubanks@gmail.com>
Subject: Re: Issues relating to managing a mailing list...
References: <1344A266-28E8-4228-908F-395FB41EDA83@amsl.com>	<01OD44MYQ1ZY00ZUIL@mauve.mrochek.com> <4F6145A0.3020705@gmail.com>	<2103063.rDf6FqNnG2@scott-latitude-e6320>	<39AB1CE59499893A8E276552@PST.JCK.COM>	<8E4035C3ECF01FAE0CCDB05B@caldav.corp.apple.com>	<4F620F85.9030702@qualcomm.com>	<28C0FE4753BC78A85D5C66CB@caldav.corp.apple.com> <CAJNg7VK8v1U2Gw9BysO-xZ+gNHjbfeitS1PRbjD0ogQRzNrHag@mail.gmail.com>
In-Reply-To: <CAJNg7VK8v1U2Gw9BysO-xZ+gNHjbfeitS1PRbjD0ogQRzNrHag@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.39.5]
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Mar 2012 20:41:05 -0000

>
> Since the problem is a relative handful of large attachments, could a
> solution just be to provide a repository for
> mailing list members to store such files, yielding a URL they could
> use in an email ? Then, the usual list feedback
> would keep the attachment sizes manageable.

(*mumble*) Folks, let's please not try to engineer around user 
silliness. User silliness will occur no matter what tools we provide.

Anybody can get a place on Dropbox or elsewhere and put a URL to their 
stuff into an email message. The problem is not that the tool isn't 
there. The problem is that people don't use it. They attach dumb things 
instead of pointing to them. Or worse they paste them inline, making it 
even harder for people who use tools that can avoid attachments from 
having to deal with them. What we need is better decisions and a bit 
more considerateness by senders of email, not more things to let them 
continue being dumb.

And there is no "one size fits all" solution here: Setting up a separate 
list that strips out attachments and makes them links helps me some of 
the time (when I'm on a low bandwidth device that can't receive mail 
other than in lump-and-dump mode), but it's lousy for me at other times 
(when my device is now zero bandwith and I would have liked everything 
downloaded while I was online so now I can read it offline). Maybe some 
folks are never offline (or are willing to ignore some of the data that 
was sent while they are), or simply don't have access to tools that 
allow them to only download attachments on demand. Maybe a second list 
with this feature would help. But overall, this seems like a social 
engineering problem more than a computer engineering problem to me.

All of this is independent of an IMAP archive. That let's people 
manipulate message in the archive with their favorite email program, 
downloading attachments (or not), replying (and getting all of the 
References: header fields right), etc. That's a good thing for the 
recipient, independent of this issue.

pr

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


From ted.ietf@gmail.com  Thu Mar 15 16:50:13 2012
Return-Path: <ted.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3513321F864F for <ietf@ietfa.amsl.com>; Thu, 15 Mar 2012 16:50:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.66
X-Spam-Level: 
X-Spam-Status: No, score=-5.66 tagged_above=-999 required=5 tests=[AWL=1.939,  BAYES_00=-2.599, GB_I_INVITATION=-2, GB_I_LETTER=-2, 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 jp2tOy7FSTxX for <ietf@ietfa.amsl.com>; Thu, 15 Mar 2012 16:50:12 -0700 (PDT)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 74DCE21F8647 for <ietf@ietf.org>; Thu, 15 Mar 2012 16:50:12 -0700 (PDT)
Received: by vcbfk13 with SMTP id fk13so4540641vcb.31 for <ietf@ietf.org>; Thu, 15 Mar 2012 16:50:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=78bPtSUu7FC/AsuZW+udzYmK1QXkSkN4/CO66vSvGEI=; b=MMYheJPMBxdum8oOSXu5St+elD3FJO3BTdkZ0Z0DLBiD99npSk7aizKL7paQb7rVeK 0Nem4IboH+Spldz2gQbXG/BRafw88TVz0RpzZqfJW/aCv1hyQdXCawA8FaECTymGXHPg aPjCeQ357TaUr92L/cL2ThZsdKE08Ca+OzLhwK4TR0ZcOYW3b4yszPJhOVZalvTErlVB h/15A7LzKOyDAWLP5CXDz6cUwYoK8A8P3FtlxRSActq9qmgtZVdw5XrTr/HBXu+7w47B ANB0p3127ox+pYCxrNvdABbaVymNcmzvWY6EgPGES1q5SLweNhgdwRzGNF73FZHWiHMa azwg==
MIME-Version: 1.0
Received: by 10.52.34.65 with SMTP id x1mr314232vdi.122.1331855411978; Thu, 15 Mar 2012 16:50:11 -0700 (PDT)
Received: by 10.52.115.66 with HTTP; Thu, 15 Mar 2012 16:50:11 -0700 (PDT)
In-Reply-To: <20120315233921.28488.71548.idtracker@ietfa.amsl.com>
References: <20120315233921.28488.71548.idtracker@ietfa.amsl.com>
Date: Thu, 15 Mar 2012 16:50:11 -0700
Message-ID: <CA+9kkMBRGxM_=J2+TZdmy78HsJ2ZHwpYS0sLTZ5=cDvyzROR3Q@mail.gmail.com>
Subject: Re: SIDR WG Virtual Interim Meeting, March 24, 2012
From: Ted Hardie <ted.ietf@gmail.com>
To: IETF <ietf@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Mar 2012 23:50:13 -0000

Is this date right?  The SIDR working group has decided to hold a
virtual interim meeting the day before the IETF, when it is holding a
working group meeting four days later on the 28th?  And it is
announcing this 9 days before the event?

If this date is correct, this seems to violate both the summary
guidance at  http://www.ietf.org/meeting/interim-meetings.html and
both the letter and the spirit of
http://www.ietf.org/iesg/statement/interim-meetings.html .

Many, many people (including me) have booked travel that runs over
this time period, and they cannot thus make even a virtual interim
meeting.

Explanation please?

thanks,

Ted Hardie


On Thu, Mar 15, 2012 at 4:39 PM, IESG Secretary <iesg-secretary@ietf.org> w=
rote:
>
> The co-chairs have arranged a virtual meeting for Mar 24, 2012.
>
> As per process, an agenda will be announced by one week before the event.
>
> This is scheduled for a full day - we will use this experience to gauge f=
uture meetings.
>
> --Sandy, speaking as wg co-chair
>
> From: messenger@webex.com [messenger@webex.com]
> Subject: Invitation to Web seminar: Virtual meeting - Mar 2012
>
> Hello,
>
> Secure Inter-Domain Routing Working Group invites you to attend a Web sem=
inar using WebEx.
>
> Topic: Virtual meeting - Mar 2012
> Host: Secure Inter-Domain Routing Working Group
> Date and Time:
> Saturday, March 24, 2012 8:00 am, GMT Time (London, GMT)
> Event number: 648 807 999
> Event password: VIRTUAL
>
> -------------------------------------------------------
> To join the online event
> -------------------------------------------------------
> 1. Click here to join the online event.
> Or copy and paste the following link to a browser:
> https://ietf.webex.com/ietf/onstage/g.php?d=3D648807999&t=3Da&EA=3Dsandra=
.murphy%40sparta.com&ET=3D49da78014cc5d3aacc1a55e34a2cff7d&ETR=3D75b14f07e6=
21faef30fd3542aeaa8773&RT=3DMiMxMQ=3D=3D&p
> 2. Click "Join Now".
>
>
> -------------------------------------------------------
> To join the teleconference only
> -------------------------------------------------------
> Call-in toll number (US/Canada): +1-408-600-3600
> Access code: 648 807 999
>
> -------------------------------------------------------
> For assistance
> -------------------------------------------------------
> You can contact Secure Inter-Domain Routing Working Group at:
> sidr-chairs@tools.ietf.org
>
> The playback of UCF (Universal Communications Format) rich media files re=
quires appropriate players. To view this type of rich media files in the me=
eting, please check whether you have the players installed on your computer=
 by going to https://ietf.webex.com/ietf/onstage/systemdiagnosis.php
>
>
>
>
> http://www.webex.com
>
> IMPORTANT NOTICE: This WebEx service includes a feature that allows audio=
 and any documents and other materials exchanged or viewed during the sessi=
on to be recorded. By joining this session, you automatically consent to su=
ch recordings. If you do not consent to the recording, discuss your concern=
s with the meeting host prior to the start of the recording or do not join =
the session. Please note that any such recordings may be subject to discove=
ry in the event of litigation.

From narten@us.ibm.com  Thu Mar 15 21:53:27 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 5510421F8628 for <ietf@ietfa.amsl.com>; Thu, 15 Mar 2012 21:53:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -108.591
X-Spam-Level: 
X-Spam-Status: No, score=-108.591 tagged_above=-999 required=5 tests=[AWL=-0.292, BAYES_00=-2.599, MANGLED_TOOL=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 Q-sEqQC-l+MK for <ietf@ietfa.amsl.com>; Thu, 15 Mar 2012 21:53:26 -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 5885821F8623 for <ietf@ietf.org>; Thu, 15 Mar 2012 21:53:26 -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, 15 Mar 2012 22:53:24 -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, 15 Mar 2012 22:53:05 -0600
Received: from d03relay02.boulder.ibm.com (d03relay02.boulder.ibm.com [9.17.195.227]) by d03dlp01.boulder.ibm.com (Postfix) with ESMTP id 04A681FF0048 for <ietf@ietf.org>; Thu, 15 Mar 2012 22:53:04 -0600 (MDT)
Received: from d03av03.boulder.ibm.com (d03av03.boulder.ibm.com [9.17.195.169]) by d03relay02.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id q2G4r4Bj177980 for <ietf@ietf.org>; Thu, 15 Mar 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 q2G4r3ir022499 for <ietf@ietf.org>; Thu, 15 Mar 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 q2G4r3H5022456 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Thu, 15 Mar 2012 22:53:03 -0600
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [127.0.0.1]) by rotala.raleigh.ibm.com (8.14.4/8.12.5) with ESMTP id q2G4r2eg005833 for <ietf@ietf.org>; Fri, 16 Mar 2012 00:53:02 -0400
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.4/8.14.4/Submit) id q2G4r2hL005800 for ietf@ietf.org; Fri, 16 Mar 2012 00:53:02 -0400
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201203160453.q2G4r2hL005800@rotala.raleigh.ibm.com>
Date: Fri, 16 Mar 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: 12031604-1780-0000-0000-0000040182ED
X-IBM-ISS-SpamDetectors: 
X-IBM-ISS-DetailInfo: BY=3.00000257; HX=3.00000186; KW=3.00000007; PH=3.00000001; SC=3.00000001; SDB=6.00122419; UDB=6.00029441; UTC=2012-03-16 04:53:21
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Mar 2012 04:53:27 -0000

Total of 106 messages in the last 7 days.
 
script run at: Fri Mar 16 00:53:02 EDT 2012
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
  4.72% |    5 |  8.31% |    68699 | nurit.sprecher@nsn.com
  4.72% |    5 |  4.67% |    38596 | ned+ietf@mauve.mrochek.com
  4.72% |    5 |  4.61% |    38135 | jgs@juniper.net
  3.77% |    4 |  3.74% |    30938 | presnick@qualcomm.com
  3.77% |    4 |  3.32% |    27464 | john-ietf@jck.com
  3.77% |    4 |  2.88% |    23860 | jnc@mercury.lcs.mit.edu
  2.83% |    3 |  3.14% |    25971 | stpeter@stpeter.im
  1.89% |    2 |  3.83% |    31715 | ron.even.tlv@gmail.com
  2.83% |    3 |  2.19% |    18127 | housley@vigilsec.com
  1.89% |    2 |  3.09% |    25589 | fangyuli1999@gmail.com
  2.83% |    3 |  2.14% |    17701 | mcr@sandelman.ca
  2.83% |    3 |  2.01% |    16599 | dhc@dcrocker.net
  1.89% |    2 |  2.83% |    23409 | daedulus@btconnect.com
  1.89% |    2 |  2.59% |    21407 | rcallon@juniper.net
  1.89% |    2 |  1.92% |    15861 | jmh@joelhalpern.com
  1.89% |    2 |  1.75% |    14467 | barryleiba@computer.org
  1.89% |    2 |  1.68% |    13900 | bortzmeyer@nic.fr
  1.89% |    2 |  1.65% |    13678 | framefritti@gmail.com
  1.89% |    2 |  1.60% |    13266 | marka@isc.org
  1.89% |    2 |  1.58% |    13068 | iljitsch@muada.com
  1.89% |    2 |  1.56% |    12890 | rjsparks@nostrum.com
  1.89% |    2 |  1.56% |    12871 | lear@cisco.com
  1.89% |    2 |  1.51% |    12449 | cyrus@daboo.name
  1.89% |    2 |  1.44% |    11874 | francesco.gennai@isti.cnr.it
  0.94% |    1 |  2.16% |    17847 | ma.yuxia@zte.com.cn
  1.89% |    2 |  1.21% |    10044 | randy@psg.com
  0.94% |    1 |  1.68% |    13884 | loa@pi.nu
  0.94% |    1 |  1.27% |    10497 | rolf.winter@neclab.eu
  0.94% |    1 |  1.25% |    10317 | turchanyi.geza@gmail.com
  0.94% |    1 |  1.17% |     9651 | gregory.mirsky@ericsson.com
  0.94% |    1 |  1.14% |     9406 | narten@us.ibm.com
  0.94% |    1 |  1.09% |     9022 | elevyabe@cisco.com
  0.94% |    1 |  1.08% |     8892 | sant9442@gmail.com
  0.94% |    1 |  1.02% |     8477 | ted.ietf@gmail.com
  0.94% |    1 |  0.98% |     8081 | julian.reschke@gmx.de
  0.94% |    1 |  0.91% |     7559 | lihan@chinamobile.com
  0.94% |    1 |  0.89% |     7354 | nkukich@verilan.com
  0.94% |    1 |  0.87% |     7186 | yang.jian90@zte.com.cn
  0.94% |    1 |  0.87% |     7157 | petithug@acm.org
  0.94% |    1 |  0.85% |     7012 | marshall.eubanks@gmail.com
  0.94% |    1 |  0.85% |     7001 | dave@cridland.net
  0.94% |    1 |  0.83% |     6839 | rpelletier@isoc.org
  0.94% |    1 |  0.83% |     6832 | ben@nostrum.com
  0.94% |    1 |  0.80% |     6595 | dino@cisco.com
  0.94% |    1 |  0.77% |     6397 | rogerj@gmail.com
  0.94% |    1 |  0.77% |     6383 | stbryant@cisco.com
  0.94% |    1 |  0.77% |     6377 | sm@resistor.net
  0.94% |    1 |  0.77% |     6365 | jouni.nospam@gmail.com
  0.94% |    1 |  0.75% |     6162 | brian.e.carpenter@gmail.com
  0.94% |    1 |  0.74% |     6131 | scott@kitterman.com
  0.94% |    1 |  0.73% |     6011 | rsk@gsp.org
  0.94% |    1 |  0.72% |     5990 | dwm@xpasc.com
  0.94% |    1 |  0.72% |     5942 | morrowc.lists@gmail.com
  0.94% |    1 |  0.69% |     5693 | lixia@cs.ucla.edu
  0.94% |    1 |  0.69% |     5676 | robert@raszuk.net
  0.94% |    1 |  0.68% |     5629 | scott.brim@gmail.com
  0.94% |    1 |  0.67% |     5580 | julian.reschke@greenbytes.de
  0.94% |    1 |  0.67% |     5552 | hartmans-ietf@mit.edu
  0.94% |    1 |  0.66% |     5446 | warren@kumari.net
  0.94% |    1 |  0.64% |     5307 | alexandru.petrescu@gmail.com
  0.94% |    1 |  0.63% |     5198 | ajs@anvilwalrusden.com
  0.94% |    1 |  0.61% |     5036 | mansaxel@besserwisser.org
--------+------+--------+----------+------------------------
100.00% |  106 |100.00% |   827062 | Total


From sant9442@gmail.com  Thu Mar 15 23:28:20 2012
Return-Path: <sant9442@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8365421E800F for <ietf@ietfa.amsl.com>; Thu, 15 Mar 2012 23:28:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.234
X-Spam-Level: 
X-Spam-Status: No, score=-3.234 tagged_above=-999 required=5 tests=[AWL=0.365,  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 zEj2elmwRTrB for <ietf@ietfa.amsl.com>; Thu, 15 Mar 2012 23:28:19 -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 99C8621F86D0 for <ietf@ietf.org>; Thu, 15 Mar 2012 23:28:19 -0700 (PDT)
Received: by yenm5 with SMTP id m5so4386333yen.31 for <ietf@ietf.org>; Thu, 15 Mar 2012 23:28:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=YeKY013q9+CmPSEfHuL7J3LMKPq8eGQSIrUrfDGdbLU=; b=LQV03JFovcGU3k5qpiJhOwEVDMfRT4yCRDWMA8vD8CWbI4OnvzfSGVBAOVUKvoSMpk VcRTJuaIpwKGk90jlB7nFegI0wcYHjru91IG2W3VN4AfV54FM8tuZmDLznm7gfIIKTZ9 O94zp8hPGndC//cd6rtEBhh32+s8aTK3vdPRGBam7JgNLShaC5LlJs/rDahMjWc+QirA loIzsXUWjLncOcyZVs1yj/RGWPEi+de0ZSeQb7BPzjJRUvbf9j3skSkzi4Ks3/MUuTA3 YO7dGg1oSMFLcCnMNn7nrqoCpdHF9EqVO9fo6J2jWL1hpA4DUneVyp2YhgnSQMS9DGs5 or1g==
Received: by 10.236.78.201 with SMTP id g49mr1518611yhe.33.1331879299161; Thu, 15 Mar 2012 23:28:19 -0700 (PDT)
Received: from adsl-215-50-126.mia.bellsouth.net (99-3-147-93.lightspeed.miamfl.sbcglobal.net. [99.3.147.93]) by mx.google.com with ESMTPS id f40sm5197495ani.16.2012.03.15.23.28.16 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 15 Mar 2012 23:28:17 -0700 (PDT)
Message-ID: <4F62DDD9.7040603@gmail.com>
Date: Fri, 16 Mar 2012 02:29:45 -0400
From: Hector <sant9442@gmail.com>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: Russ Housley <housley@vigilsec.com>
Subject: Re: Issues relating to managing a mailing list...
References: <1344A266-28E8-4228-908F-395FB41EDA83@amsl.com> <30461C26-EDCE-4BFD-8E82-AF1CC5BC371C@vigilsec.com>
In-Reply-To: <30461C26-EDCE-4BFD-8E82-AF1CC5BC371C@vigilsec.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Mar 2012 06:28:20 -0000

Russ Housley wrote:
> Some suggestions have been made about the IETF mail lists.
> There is a way for mailman to strip attachments and put them
> in a place for downloading with a web browser.  This would be
> a significant change to current practice, so the community
> needs to consider this potential policy change.
> 
> What do you think?
> 
> Russ


We will never be able to satisfy all unless there an option to do so.

One approach is to keep an focus on what the real issue is as 
presented by the question and just making a change to address this only.

The other, less focus, forward thinking approach is to use the 
opportunity to begin moving the IETF or perhaps "catch up" with new or 
existing Group Ware communications directions the IETF has yet to 
leverage.

So I think it may help to be specific on what we are having to work 
with. If mailman is the only consideration as the current tool, then 
the solution is based on what is it capable of.  Is the question 
dealing with a System Wide policy or does it include the option to 
make it per user (member of a list)?  Off hand, the latter is the more 
democratic solution IFF mailman offers his option.

If it is open ended question, then there are other solutions that 
addresses all the concerns - old and new. However, that is the more 
expensive solution.

--
Hector Santos, CTO
http://www.santronics.com


From sant9442@gmail.com  Fri Mar 16 00:06:20 2012
Return-Path: <sant9442@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 30B7521F8701 for <ietf@ietfa.amsl.com>; Fri, 16 Mar 2012 00:06:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.247
X-Spam-Level: 
X-Spam-Status: No, score=-3.247 tagged_above=-999 required=5 tests=[AWL=0.352,  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 OoHwOpW3RdDy for <ietf@ietfa.amsl.com>; Fri, 16 Mar 2012 00:06:19 -0700 (PDT)
Received: from mail-gy0-f172.google.com (mail-gy0-f172.google.com [209.85.160.172]) by ietfa.amsl.com (Postfix) with ESMTP id 3442421F8702 for <ietf@ietf.org>; Fri, 16 Mar 2012 00:06:19 -0700 (PDT)
Received: by ghbg16 with SMTP id g16so4414541ghb.31 for <ietf@ietf.org>; Fri, 16 Mar 2012 00:06:18 -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=oZnLNIvz8f0SZYvLP3ppxh2pulJ9Pw0DtcHlQbxy9+s=; b=yIeUXTZYXagWtu5ST9OSUJ7esEmpc6zIOFVWmT32DoSIGXCE68M6vJvPzeS1bQ/kYX znBHEbFraenk4BMlJ5LWnOH+tv8+gl0qr9pe+LcrOu11WKmhHY4UUgb59m0ixkuF0/fu lD701YSeAoZ7/HCMwR8jpQCJDxTC8cx5afUaslFyOGhllgOpRKmzSgIWwuRKFRvVmvFh gjDFEiJLetiwEAKjq5BbbIOHbnLxR+Bve8sDpTAAlKSwp1fBq0vBNo8w4eGLRpdVUDAI iR9plezcVqT9Ew0/4Pwj3lrRetsTDu8EKLDGr2vM/JE/psnyftkPvsyB2BUBAzNmIIR2 WmiQ==
Received: by 10.236.185.42 with SMTP id t30mr1440334yhm.105.1331881578575; Fri, 16 Mar 2012 00:06:18 -0700 (PDT)
Received: from adsl-215-50-126.mia.bellsouth.net (99-3-147-93.lightspeed.miamfl.sbcglobal.net. [99.3.147.93]) by mx.google.com with ESMTPS id o68sm11188470yhk.16.2012.03.16.00.06.16 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 16 Mar 2012 00:06:17 -0700 (PDT)
Message-ID: <4F62E6C1.7040009@gmail.com>
Date: Fri, 16 Mar 2012 03:07:45 -0400
From: Hector <sant9442@gmail.com>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: Michael Richardson <mcr@sandelman.ca>
Subject: Re: Issues relating to managing a mailing list...
References: <1344A266-28E8-4228-908F-395FB41EDA83@amsl.com>	<01OD44MYQ1ZY00ZUIL@mauve.mrochek.com> <4F6145A0.3020705@gmail.com>	<2103063.rDf6FqNnG2@scott-latitude-e6320>	<39AB1CE59499893A8E276552@PST.JCK.COM>	<8E4035C3ECF01FAE0CCDB05B@caldav.corp.apple.com> <22119.1331835846@marajade.sandelman.ca>
In-Reply-To: <22119.1331835846@marajade.sandelman.ca>
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: Fri, 16 Mar 2012 07:06:20 -0000

Michael Richardson wrote:
>>>>>> "Cyrus" == Cyrus Daboo <cyrus@daboo.name> writes:
> 
>     Cyrus> Along those lines how about setting up an IETF IMAP server
>     Cyrus> with mailboxes for each mailing list hosted by the IETF? That
>     Cyrus> way anyone with a capable IMAP client (one that can
> 
> How about we use the protocol that was designed for this...  NNTP?

+1, I think NNTP should of been long part of the IETF "group ware" 
offerings.

However, NNTP solutions doesn't address the main original posted 
question which I believe related to bandwidth issues.

The RFC5322 solution proposed in the question begins the emulation 
online solutions where the resources (attachments) are in the backend. 
  So this is more about a system wide vs per user option policy of how 
original mail is transformed and distributed.

We make some popular email based list via NNTP as "Public Local 
Newsgroups" such as the IETF-DRAFT list among them at:

     news://news.winserver.com

This is how some of the our users (and myself) interested in IETF 
catch up with the IETF-DRAFTS email submissions. I use a special 
member address (ietf-drafts@isdg.net) to redirect these incoming 
emails into the public/open newsgroup storage area.

I've done the same with specific IETF list that only I belong to (have 
access to) so I am use my RFC-based MUA, and here I have to often 
decide on the incoming transformation:


   - if I want WYSIWYG, then I set the Preserve MIME option = YES (no 
changes in storage)

   - if TEXT is all that is important, then the option OFF where 
attachments are extracted
     and stored separately.


But for the IETF, it needs to cater to wide range of users, so it will 
need to preserve the originality if it wishes to continue only 
offering an RFC based connectivity method.

When we begin to deviate from standard RFC mail methods, then it has 
to begin to consider the different, new connectivity methods, line 
online web access, etc.

--
HLS


From daedulus@btconnect.com  Fri Mar 16 02:43:59 2012
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2C81221F85C5 for <ietf@ietfa.amsl.com>; Fri, 16 Mar 2012 02:43:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.733
X-Spam-Level: 
X-Spam-Status: No, score=-0.733 tagged_above=-999 required=5 tests=[AWL=-0.734, BAYES_50=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 QjYIZqdza5CB for <ietf@ietfa.amsl.com>; Fri, 16 Mar 2012 02:43:58 -0700 (PDT)
Received: from mail.btconnect.com (c2beaomr09.btconnect.com [213.123.26.187]) by ietfa.amsl.com (Postfix) with ESMTP id 1F13221F85C2 for <ietf@ietf.org>; Fri, 16 Mar 2012 02:43:57 -0700 (PDT)
Received: from host86-151-41-215.range86-151.btcentralplus.com (HELO pc6) ([86.151.41.215]) by c2beaomr09.btconnect.com with SMTP id GRX96096; Fri, 16 Mar 2012 09:43:33 +0000 (GMT)
Message-ID: <008f01cd0350$bf7b2c80$4001a8c0@gateway.2wire.net>
From: "t.petch" <daedulus@btconnect.com>
To: "Russ Housley" <housley@vigilsec.com>, "IETF" <ietf@ietf.org>
References: <1344A266-28E8-4228-908F-395FB41EDA83@amsl.com> <30461C26-EDCE-4BFD-8E82-AF1CC5BC371C@vigilsec.com>
Subject: Re: Issues relating to managing a mailing list... 
Date: Fri, 16 Mar 2012 09:42:34 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Mirapoint-IP-Reputation: reputation=Fair-1, source=Queried, refid=tid=0001.0A0B0303.4F630B45.0029, actions=tag
X-Junkmail-Premium-Raw: score=7/50, refid=2.7.2:2012.3.16.91233:17:7.944, ip=86.151.41.215, rules=__HAS_MSGID, __OUTLOOK_MSGID_1, __SANE_MSGID, __TO_MALFORMED_2, __BOUNCE_CHALLENGE_SUBJ, __BOUNCE_NDR_SUBJ_EXEMPT, __MIME_VERSION, __CT, CT_TP_8859_1, __CT_TEXT_PLAIN, __CTE, __HAS_X_PRIORITY, __HAS_MSMAIL_PRI, __HAS_X_MAILER, USER_AGENT_OE, __OUTLOOK_MUA_1, __USER_AGENT_MS_GENERIC, __ANY_URI, __URI_NO_WWW, __URI_NO_PATH, BODY_SIZE_3000_3999, __MIME_TEXT_ONLY, RDNS_GENERIC_POOLED, HTML_00_01, HTML_00_10, BODY_SIZE_5000_LESS, RDNS_SUSP_GENERIC, __OUTLOOK_MUA, RDNS_SUSP, BODY_SIZE_7000_LESS
X-Junkmail-Status: score=10/50, host=c2beaomr09.btconnect.com
X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A0B0206.4F630B46.0081,ss=1,re=0.000,fgs=0, ip=0.0.0.0, so=2011-07-25 19:15:43, dmn=2011-05-27 18:58:46, mode=multiengine
X-Junkmail-IWF: false
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Mar 2012 09:43:59 -0000

----- Original Message -----
From: "Russ Housley" <housley@vigilsec.com>
To: "IETF" <ietf@ietf.org>
Sent: Thursday, March 15, 2012 12:46 AM

> Some suggestions have been made about the IETF mail lists.
> There is a way for mailman to strip attachments and put them
> in a place for downloading with a web browser.  This would be
> a significant change to current practice, so the community
> needs to consider this potential policy change.
>
> What do you think?

Brilliant idea.

Some WG chairs already limit message size to 40kbyte which is a more basic way
of imposing commen sense on those who post to IETF lists with no awareness of
the damage they do to the work of others by posting successions of megabyte
messages.  Doubtless, the culture they work in is so rich in resources they
cannot conceive of any reason not to and we need to educate them.

The culture to promote is no attachments, zero, zilch.  Anything you cannot send
out through I-D system belongs on an FTP site, something that many WG chairs
recognise and provide as an auxiliary page.  Sadly, automatic stripping would be
a necessary step along the road there.

Tom Petch
>
> Russ
>
>
> >>>> The only bug in the soup is that it seemed to me that we might
> >>>> want to look into an alternative approach.  We have asked people
> >>>> to post large documents somewhere and only send a pointer.  Not
> >>>> everyone can do that, lots of people forget, and some people are
> >>>> just not willing to take the extra step.
> >>>>
> >>>> Plus, we cannot expect people to keep things posted on their own
> >>>> personal, or their company's, web-site indefinitely.  If they
> >>>> don't keep it there, then the pointer in the archive will become
> >>>> stale, and information that should probably be there is lost.
> >>>>
> >>>> So we need a solution to the issue with really big email messages
> >>>> sometime.
> >>>>
> >>>> One solution might be to simpy strip attachments off, put them
> >>>> in the archive and replace them with a pointer.  That shouldn't
> >>>> be that hard, since a lot of anti-virus software does something
> >>>> similar with suspect attachment types.
> >>>>
> >>>> Or we could - once again - ask people to post attachments and use
> >>>> a pointer in their mail, only provide them with a place to post
> >>>> them in the same general area as the mail archive.
> >>>>
> >>>> If there is already something like this in place, please let me
> >>>> know what it is and I will add a pointer to it in my "too big"
> >>>> rejection messages.
> >>>>
> >>>> The thing about threaded messages getting too big is a slightly
> >>>> different issue, brought about by the increasing use of HTML
> >>>> format email.  I talked years ago about this with Scott Bradner
> >>>> because I really think that HTML format messages are useful and
> >>>> relatively easy to read when compared to plain old text.
> >>>>
> >>>> But using HTML leads to messages that are deceptively big.
> >>>>
> >>>> Possibly the right answer in that case is to bump the size limit
> >>>> up to maybe 100K.  Even with HTML format, people will many likely
> >>>> realize that nobody is going to read past the 10th back message
> >>>> in any case (or if they do want to, they can look at the thread
> >>>> in the archive).
> >>>>
> >>>> But even that approach is not fool proof, and there are a lot of
> >>>> resourceful fools out there.
> >>>>
> >>>> Just trying to be creative, and help out...
>
>
>


From daedulus@btconnect.com  Fri Mar 16 02:47:45 2012
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9813E21F86C8 for <ietf@ietfa.amsl.com>; Fri, 16 Mar 2012 02:47:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.789
X-Spam-Level: 
X-Spam-Status: No, score=-1.789 tagged_above=-999 required=5 tests=[AWL=0.810,  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 ijvGO6eJ59V3 for <ietf@ietfa.amsl.com>; Fri, 16 Mar 2012 02:47:44 -0700 (PDT)
Received: from mail.btconnect.com (c2beaomr07.btconnect.com [213.123.26.185]) by ietfa.amsl.com (Postfix) with ESMTP id 4F82821F86C1 for <ietf@ietf.org>; Fri, 16 Mar 2012 02:47:44 -0700 (PDT)
Received: from host86-151-41-215.range86-151.btcentralplus.com (HELO pc6) ([86.151.41.215]) by c2beaomr07.btconnect.com with SMTP id GRU18152; Fri, 16 Mar 2012 09:47:40 +0000 (GMT)
Message-ID: <009b01cd0351$52d5f3c0$4001a8c0@gateway.2wire.net>
From: "t.petch" <daedulus@btconnect.com>
To: <stbryant@cisco.com>, "Fangyu Li" <fangyuli1999@gmail.com>
References: <CAAHpaZ=JrKVKHZ0xkK-nszFDf-ttVNoi1p9iZiWa93vKuiNxZA@mail.gmail.com> <4F60BF02.1010507@cisco.com>
Subject: Re: Last Call:<draft-betts-itu-oam-ach-code-point-03.txt>(Allocationof an Associated Channel Code Point for Use by ITU-T Ethernet basedOAM) to Informational RFC
Date: Fri, 16 Mar 2012 09:46:44 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Mirapoint-IP-Reputation: reputation=Fair-1, source=Queried, refid=tid=0001.0A0B0301.4F630C3C.00E5, actions=tag
X-Junkmail-Premium-Raw: score=9/50, refid=2.7.2:2012.3.16.91233:17:9.975, ip=86.151.41.215, rules=__HAS_MSGID, __OUTLOOK_MSGID_1, __SANE_MSGID, __TO_MALFORMED_2, __TO_NO_NAME, __BOUNCE_CHALLENGE_SUBJ, __BOUNCE_NDR_SUBJ_EXEMPT, __SUBJ_ALPHA_END, __MIME_VERSION, __CT, CT_TP_8859_1, __CT_TEXT_PLAIN, __CTE, __HAS_X_PRIORITY, __HAS_MSMAIL_PRI, __HAS_X_MAILER, USER_AGENT_OE, __OUTLOOK_MUA_1, __USER_AGENT_MS_GENERIC, __ANY_URI, CN_TLD, __FRAUD_BODY_WEBMAIL, __URI_NO_WWW, __URI_NO_PATH, BODYTEXTP_SIZE_3000_LESS, BODY_SIZE_1200_1299, __MIME_TEXT_ONLY, RDNS_GENERIC_POOLED, HTML_00_01, HTML_00_10, BODY_SIZE_5000_LESS, RDNS_SUSP_GENERIC, __OUTLOOK_MUA, RDNS_SUSP, BODY_SIZE_2000_LESS, __FRAUD_WEBMAIL, BODY_SIZE_7000_LESS
X-Junkmail-Status: score=10/50, host=c2beaomr07.btconnect.com
X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A0B0209.4F630C3C.0232,ss=1,re=0.000,fgs=0, ip=0.0.0.0, so=2011-07-25 19:15:43, dmn=2011-05-27 18:58:46, mode=multiengine
X-Junkmail-IWF: false
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Mar 2012 09:47:45 -0000

----- Original Message -----
From: "Stewart Bryant" <stbryant@cisco.com>
To: "Fangyu Li" <fangyuli1999@gmail.com>
Cc: <lifang@catr.cn>; <ietf@ietf.org>
Sent: Wednesday, March 14, 2012 4:53 PM
> On 14/03/2012 13:36, Fangyu Li wrote:
> > I support the allocation of an ACH codepoint to G.8113.1.
> > For G.8113.1 had reached the technical and industry maturity to be
> > assigned a code point, the codepoint allocation from IETF should allow
> > the ITU-T to progress refinements to G.8113.1 such that it could
> > satisfy all the functional requirements defined in RFC 5860.
>
> Please can you tell me version of the G.8113.1 text one would
> need to implement to be able to seamlessly interwork with the
> equipment that has already been been deployed?

Stewart

I am sure you already know the answer to that from posts made to the mpls list,
where we have been told that there is currently an extensive deployment
('running code') using an experimental value (interesting that there is a last
call just ending seeking to exterminate such practice, at least for application
protocols) and that the wish is to move to a standards-based value which will,
perforce, be a different value.

Tom Petch



>
> - Stewart
>
>


From daedulus@btconnect.com  Fri Mar 16 04:02:05 2012
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DA98E21F8649 for <ietf@ietfa.amsl.com>; Fri, 16 Mar 2012 04:02:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.691
X-Spam-Level: 
X-Spam-Status: No, score=-1.691 tagged_above=-999 required=5 tests=[AWL=0.308,  BAYES_00=-2.599, J_CHICKENPOX_15=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L8iHDMXjWA+2 for <ietf@ietfa.amsl.com>; Fri, 16 Mar 2012 04:02:04 -0700 (PDT)
Received: from mail.btconnect.com (c2bthomr07.btconnect.com [213.123.20.125]) by ietfa.amsl.com (Postfix) with ESMTP id 734AA21F8678 for <ietf@ietf.org>; Fri, 16 Mar 2012 04:02:02 -0700 (PDT)
Received: from host86-151-41-215.range86-151.btcentralplus.com (HELO pc6) ([86.151.41.215]) by c2bthomr07.btconnect.com with SMTP id GVR28490; Fri, 16 Mar 2012 11:01:56 +0000 (GMT)
Message-ID: <01dc01cd035b$b2c0cee0$4001a8c0@gateway.2wire.net>
From: "t.petch" <daedulus@btconnect.com>
To: "Peter Saint-Andre" <stpeter@stpeter.im>
References: <20120301184750.21152.93044.idtracker@ietfa.amsl.com> <028601cd00fc$f5ba5380$4001a8c0@gateway.2wire.net> <4F5FC7DC.5040203@stpeter.im>
Subject: Re: Last Call: <draft-ietf-appsawg-xdash-03.txt> (Deprecating Use of the"X-" Prefix in Application Protocols) to Best Current Practice
Date: Fri, 16 Mar 2012 11:00:57 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Mirapoint-IP-Reputation: reputation=Fair-1, source=Queried, refid=tid=0001.0A0B0302.4F631DA3.0144, actions=TAG
X-Junkmail-Premium-Raw: score=8/50, refid=2.7.2:2012.3.16.101221:17:8.317, ip=86.151.41.215, rules=__HAS_MSGID, __OUTLOOK_MSGID_1, __SANE_MSGID, __TO_MALFORMED_2, __MULTIPLE_RCPTS_CC_X2, __BOUNCE_CHALLENGE_SUBJ, __BOUNCE_NDR_SUBJ_EXEMPT, __SUBJ_ALPHA_END, __MIME_VERSION, __CT, __CT_TEXT_PLAIN, __CTE, __HAS_X_PRIORITY, __HAS_MSMAIL_PRI, __HAS_X_MAILER, USER_AGENT_OE, __OUTLOOK_MUA_1, __USER_AGENT_MS_GENERIC, __ANY_URI, __URI_NO_WWW, __FRAUD_CONTACT_NAME, __CP_URI_IN_BODY, BODY_SIZE_4000_4999, __MIME_TEXT_ONLY, RDNS_GENERIC_POOLED, HTML_00_01, HTML_00_10, BODY_SIZE_5000_LESS, RDNS_SUSP_GENERIC, __OUTLOOK_MUA, MULTIPLE_RCPTS, RDNS_SUSP, BODY_SIZE_7000_LESS
X-Junkmail-Status: score=10/50, host=c2bthomr07.btconnect.com
X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A0B0206.4F631DA5.00AC,ss=1,re=0.000,fgs=0, ip=0.0.0.0, so=2011-07-25 19:15:43, dmn=2011-05-27 18:58:46, mode=multiengine
X-Junkmail-IWF: false
Cc: Mark Nottingham <mnot@mnot.net>, ietf@ietf.org, Dave CROCKER <dcrocker@bbiw.net>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Mar 2012 11:02:05 -0000

----- Original Message -----
From: "Peter Saint-Andre" <stpeter@stpeter.im>
To: "t.petch" <daedulus@btconnect.com>
Cc: <ietf@ietf.org>; "Dave CROCKER" <dcrocker@bbiw.net>; "Mark Nottingham"
<mnot@mnot.net>
Sent: Tuesday, March 13, 2012 11:19 PM

> On 3/13/12 3:37 AM, t.petch wrote:
> > I am surprised at the lack of comment on this I-D on its use of terminology.
I
> > have seen and learnt from many discussions on this list that have teased out
> > what concept it is we are really talking about (e.g. identity v identifier)
and
> > this I-D seems somewhat weak in that regard.
> >
> > Thus the summary
>
> Clarifying quesiton: do you mean the abstract? (Yes)
>
> > talks of
> > 'parameters by prefixing the latter '
>
> http://tools.ietf.org/html/draft-ietf-appsawg-xdash-04 does not contain
> that string. The discussions on this list and with the IESG have led to
> some changes in the text. The Abstract now reads:
>
>    Historically, designers and implementers of application protocols
>    have often distinguished between "standard" and "non-standard"
>    parameters by prefixing the names of "non-standard" parameters with
>    the string "X-" or similar constructs.  In practice, that convention
>    causes more problems than it solves.  Therefore, this document
>    deprecates the convention for the names of newly-defined textual
>    parameters in application protocols.

Which I think the completely wrong direction in which to make changes:-(

I might create a private parameter and decide that it should be named the X-Spam
parameter, which can then take values, which may appear in the textual header,
of one of
Signs-of-Spam-Detected
Signs-of-Spam-Not-Detected

What you are saying is that because I have named it X-, this is unacceptable.
What I think that you are assuming, erroneously, is that the value that appears
in the textual header of the protocol is always identical to the name or at
least starts with that name.

Most people will probably understand your wording, but I still find it sloppy
for an RFC (given the way that this list has dissected similar topics in the
past).

Tom Petch

>
> > while the  introduction changes that to
> > 'the "X-" convention for named parameters in application protocols '
> > which is then refined to
> > 'only parameters with textual names, not parameters that are expressed as
> > numbers'
> > which seems to me a false dichotomy.
>
> The relevant paragraph of the Introduction now reads:
>
>    Many application protocols use parameters with textual names to
>    identify data (media types, header fields in Internet mail messages
>    and HTTP requests, vCard parameters and properties, etc.).
>    Historically, designers and implementers of application protocols
>    have often distinguished between "standard" and "non-standard"
>    parameters by prefixing the names of "non-standard" parameters with
>    the string "X-" or similar constructs (e.g., "x."), where the "X" is
>    commonly understood to stand for "eXperimental" or "eXtension".  That
>    is, instead of just identifying the data, the name also embedded the
>    status of the name as "non-standard" into the name itself.
>
> > The I-D seems to be conflating the ideas of name and value
>
> In my opinion, I think those ideas are clearer now in -04, again based
> on feedback we have received and addressed. Please take a look at the
> latest version and let us know what you think.
>
> > and a few other
> > things as well.
>
> Please do clarify what other things you think are conflated.
>
> > I know of very few parameters in IETF protocols that do not
> > have names and cannot recall one where the name is not textual.
>
> The contrast is with parameters whose names are numerical, not textual.
> Often parameter spaces whose names are numerical are smaller, i.e., do
> not allow such a wide range of names; in such cases, the considerations
> in BCP 82 might apply.
>
> > The I-D seems
> > to be assuming that the parameter name and the parameter value and so on are
> > synonymous, identical, equivalent and perhaps a few other things as well,
and
> > having assumed that, then it is sufficient to say that one or other of these
> > concepts are textual and it is to these that this I-D applies.  This seems
to me
> > to be rather too loosely worded to become an RFC.
>
> This I-D says absolutely nothing about parameter values. If some folks
> have understood differently, then we need to clarify the wording. I can
> now see that "the names of newly-defined textual parameters" in the
> Abstract could be misconstrued, although I think the phrasing in the
> Introduction is clearer: "parameters with textual names". In both
> instances we could further clarify our intent by using the phrase
> "parameters with textual (as opposed to numerical) names".
>
> Peter
> --
> Peter Saint-Andre
> https://stpeter.im/


From stbryant@cisco.com  Fri Mar 16 04:40:04 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 588FA21F854D; Fri, 16 Mar 2012 04:40:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -112.547
X-Spam-Level: 
X-Spam-Status: No, score=-112.547 tagged_above=-999 required=5 tests=[AWL=2.051, BAYES_00=-2.599, GB_I_INVITATION=-2, GB_I_LETTER=-2,  HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yHdqUZtSvhq6; Fri, 16 Mar 2012 04:40:03 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by ietfa.amsl.com (Postfix) with ESMTP id 4AF5E21F8555; Fri, 16 Mar 2012 04:40:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=stbryant@cisco.com; l=11456; q=dns/txt; s=iport; t=1331898002; x=1333107602; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to; bh=VMR9QT880qMvv2XpsOA3XXGbY66Gpl2XYv2UlXoHgJ8=; b=XWrWhdqfzoudHg30d+ZlV+qjZaXWqI7Q2XbQaO54atcTn99SXxUb0CRo G0nuABs6EBNY9KYIQNex6okS8LVStANAlebbs3MIjMuUyiQQuotE2m/oZ civY2oPQkrH0E9/K2/wRVHWvvg0WdJ6hWO1jObXWthE8QnHpfv4+ms5GY M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAEIlY0+Q/khN/2dsb2JhbAAoFwO2NoEHggkBAQEEEgECMg4RExALFQIBCQsEDAoPAj4HAQYNAQUCAQEFGYdoCymaO4M8EIlhg0EYjgiKT4MHB4MgBJVmjj+BAmaCH0eBVg
X-IronPort-AV: E=Sophos;i="4.73,597,1325462400";  d="scan'208,217";a="132521342"
Received: from ams-core-4.cisco.com ([144.254.72.77]) by ams-iport-1.cisco.com with ESMTP; 16 Mar 2012 11:40:01 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by ams-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id q2GBe1rB024337; Fri, 16 Mar 2012 11:40:01 GMT
Received: from stbryant-mac2.local (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id q2GBdnHq022803; Fri, 16 Mar 2012 11:39:50 GMT
Message-ID: <4F632685.10506@cisco.com>
Date: Fri, 16 Mar 2012 11:39:49 +0000
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: Ted Hardie <ted.ietf@gmail.com>
Subject: Re: SIDR WG Virtual Interim Meeting, March 24, 2012
References: <20120315233921.28488.71548.idtracker@ietfa.amsl.com> <CA+9kkMBRGxM_=J2+TZdmy78HsJ2ZHwpYS0sLTZ5=cDvyzROR3Q@mail.gmail.com>
In-Reply-To: <CA+9kkMBRGxM_=J2+TZdmy78HsJ2ZHwpYS0sLTZ5=cDvyzROR3Q@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------070501050500030907000009"
Cc: IETF <ietf@ietf.org>, "iesg@ietf.org" <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Mar 2012 11:40:04 -0000

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

Ted

I knew that SIDR was planning to hold this meeting.

The SIDR WG currently needs more interaction time
than can be accommodated within IETF week.

I verified with a number of IESG colleagues that
holding a meeting adjacent to an IETF meeting was
within the guidelines. The important point is that
it is an addition and not a replacement for a normal
IETF WG meeting. Any outcome from the interim
(together with the results of their previous interim)
will be reported at the start of the  SIDR WG session
later that week in Paris.

As a VM the WG Chairs can call this provided
they give two weeks notice to the appropriate lists.
Two weeks notice was given on the SIDR list.
I accept the chairs explanation that the failure to
copy iesg-secretary@ietf.org was a genuine emailing
error, and that they had intended to follow correct
procedure.

No one raised any concerns on the SIDR list to the
meeting when it was announced.

It is my view  that the meeting is useful in
progressing the SIDR work and that despite the
procedural error by the SIDR Chairs the VM
should go ahead as planned.

Stewart


On 15/03/2012 23:50, Ted Hardie wrote:
> Is this date right?  The SIDR working group has decided to hold a
> virtual interim meeting the day before the IETF, when it is holding a
> working group meeting four days later on the 28th?  And it is
> announcing this 9 days before the event?
>
> If this date is correct, this seems to violate both the summary
> guidance at  http://www.ietf.org/meeting/interim-meetings.html and
> both the letter and the spirit of
> http://www.ietf.org/iesg/statement/interim-meetings.html .
>
> Many, many people (including me) have booked travel that runs over
> this time period, and they cannot thus make even a virtual interim
> meeting.
>
> Explanation please?
>
> thanks,
>
> Ted Hardie
>
>
> On Thu, Mar 15, 2012 at 4:39 PM, IESG Secretary<iesg-secretary@ietf.org>  wrote:
>> The co-chairs have arranged a virtual meeting for Mar 24, 2012.
>>
>> As per process, an agenda will be announced by one week before the event.
>>
>> This is scheduled for a full day - we will use this experience to gauge future meetings.
>>
>> --Sandy, speaking as wg co-chair
>>
>> From: messenger@webex.com [messenger@webex.com]
>> Subject: Invitation to Web seminar: Virtual meeting - Mar 2012
>>
>> Hello,
>>
>> Secure Inter-Domain Routing Working Group invites you to attend a Web seminar using WebEx.
>>
>> Topic: Virtual meeting - Mar 2012
>> Host: Secure Inter-Domain Routing Working Group
>> Date and Time:
>> Saturday, March 24, 2012 8:00 am, GMT Time (London, GMT)
>> Event number: 648 807 999
>> Event password: VIRTUAL
>>
>> -------------------------------------------------------
>> To join the online event
>> -------------------------------------------------------
>> 1. Click here to join the online event.
>> Or copy and paste the following link to a browser:
>> https://ietf.webex.com/ietf/onstage/g.php?d=648807999&t=a&EA=sandra.murphy%40sparta.com&ET=49da78014cc5d3aacc1a55e34a2cff7d&ETR=75b14f07e621faef30fd3542aeaa8773&RT=MiMxMQ==&p
>> 2. Click "Join Now".
>>
>>
>> -------------------------------------------------------
>> To join the teleconference only
>> -------------------------------------------------------
>> Call-in toll number (US/Canada): +1-408-600-3600
>> Access code: 648 807 999
>>
>> -------------------------------------------------------
>> For assistance
>> -------------------------------------------------------
>> You can contact Secure Inter-Domain Routing Working Group at:
>> sidr-chairs@tools.ietf.org
>>
>> The playback of UCF (Universal Communications Format) rich media files requires appropriate players. To view this type of rich media files in the meeting, please check whether you have the players installed on your computer by going to https://ietf.webex.com/ietf/onstage/systemdiagnosis.php
>>
>>
>>
>>
>> http://www.webex.com
>>
>> IMPORTANT NOTICE: This WebEx service includes a feature that allows audio and any documents and other materials exchanged or viewed during the session to be recorded. By joining this session, you automatically consent to such recordings. If you do not consent to the recording, discuss your concerns with the meeting host prior to the start of the recording or do not join the session. Please note that any such recordings may be subject to discovery in the event of litigation.


-- 
For corporate legal information go to:

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



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

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    Ted<br>
    <br>
    I knew that SIDR was planning to hold this meeting.<br>
    <br>
    The SIDR WG currently needs more interaction time <br>
    than can be accommodated within IETF week.<br>
    <br>
    I verified with a number of IESG colleagues that <br>
    holding a meeting adjacent to an IETF meeting was <br>
    within the guidelines. The important point is that <br>
    it is an addition and not a replacement for a normal <br>
    IETF WG meeting. Any outcome from the interim <br>
    (together with the results of their previous interim) <br>
    will be reported at the start of the&nbsp; SIDR WG session<br>
    later that week in Paris.<br>
    <br>
    As a VM the WG Chairs can call this provided <br>
    they give two weeks notice to the appropriate lists. <br>
    Two weeks notice was given on the SIDR list.<br>
    I accept the chairs explanation that the failure to <br>
    copy
    <meta http-equiv="content-type" content="text/html;
      charset=ISO-8859-1">
    <a class="moz-txt-link-abbreviated" href="mailto:iesg-secretary@ietf.org">iesg-secretary@ietf.org</a> was a genuine emailing<br>
    error, and that they had intended to follow correct<br>
    procedure.<br>
    <br>
    No one raised any concerns on the SIDR list to the <br>
    meeting when it was announced.<br>
    <br>
    It is my view&nbsp; that the meeting is useful in <br>
    progressing the SIDR work and that despite the <br>
    procedural error by the SIDR Chairs the VM <br>
    should go ahead as planned.<br>
    <br>
    Stewart<br>
    <br>
    <br>
    On 15/03/2012 23:50, Ted Hardie wrote:
    <blockquote
cite="mid:CA+9kkMBRGxM_=J2+TZdmy78HsJ2ZHwpYS0sLTZ5=cDvyzROR3Q@mail.gmail.com"
      type="cite">
      <pre wrap="">Is this date right?  The SIDR working group has decided to hold a
virtual interim meeting the day before the IETF, when it is holding a
working group meeting four days later on the 28th?  And it is
announcing this 9 days before the event?

If this date is correct, this seems to violate both the summary
guidance at  <a class="moz-txt-link-freetext" href="http://www.ietf.org/meeting/interim-meetings.html">http://www.ietf.org/meeting/interim-meetings.html</a> and
both the letter and the spirit of
<a class="moz-txt-link-freetext" href="http://www.ietf.org/iesg/statement/interim-meetings.html">http://www.ietf.org/iesg/statement/interim-meetings.html</a> .

Many, many people (including me) have booked travel that runs over
this time period, and they cannot thus make even a virtual interim
meeting.

Explanation please?

thanks,

Ted Hardie


On Thu, Mar 15, 2012 at 4:39 PM, IESG Secretary <a class="moz-txt-link-rfc2396E" href="mailto:iesg-secretary@ietf.org">&lt;iesg-secretary@ietf.org&gt;</a> wrote:
</pre>
      <blockquote type="cite">
        <pre wrap="">
The co-chairs have arranged a virtual meeting for Mar 24, 2012.

As per process, an agenda will be announced by one week before the event.

This is scheduled for a full day - we will use this experience to gauge future meetings.

--Sandy, speaking as wg co-chair

From: <a class="moz-txt-link-abbreviated" href="mailto:messenger@webex.com">messenger@webex.com</a> [<a class="moz-txt-link-abbreviated" href="mailto:messenger@webex.com">messenger@webex.com</a>]
Subject: Invitation to Web seminar: Virtual meeting - Mar 2012

Hello,

Secure Inter-Domain Routing Working Group invites you to attend a Web seminar using WebEx.

Topic: Virtual meeting - Mar 2012
Host: Secure Inter-Domain Routing Working Group
Date and Time:
Saturday, March 24, 2012 8:00 am, GMT Time (London, GMT)
Event number: 648 807 999
Event password: VIRTUAL

-------------------------------------------------------
To join the online event
-------------------------------------------------------
1. Click here to join the online event.
Or copy and paste the following link to a browser:
<a class="moz-txt-link-freetext" href="https://ietf.webex.com/ietf/onstage/g.php?d=648807999&amp;t=a&amp;EA=sandra.murphy%40sparta.com&amp;ET=49da78014cc5d3aacc1a55e34a2cff7d&amp;ETR=75b14f07e621faef30fd3542aeaa8773&amp;RT=MiMxMQ==&amp;p">https://ietf.webex.com/ietf/onstage/g.php?d=648807999&amp;t=a&amp;EA=sandra.murphy%40sparta.com&amp;ET=49da78014cc5d3aacc1a55e34a2cff7d&amp;ETR=75b14f07e621faef30fd3542aeaa8773&amp;RT=MiMxMQ==&amp;p</a>
2. Click "Join Now".


-------------------------------------------------------
To join the teleconference only
-------------------------------------------------------
Call-in toll number (US/Canada): +1-408-600-3600
Access code: 648 807 999

-------------------------------------------------------
For assistance
-------------------------------------------------------
You can contact Secure Inter-Domain Routing Working Group at:
<a class="moz-txt-link-abbreviated" href="mailto:sidr-chairs@tools.ietf.org">sidr-chairs@tools.ietf.org</a>

The playback of UCF (Universal Communications Format) rich media files requires appropriate players. To view this type of rich media files in the meeting, please check whether you have the players installed on your computer by going to <a class="moz-txt-link-freetext" href="https://ietf.webex.com/ietf/onstage/systemdiagnosis.php">https://ietf.webex.com/ietf/onstage/systemdiagnosis.php</a>




<a class="moz-txt-link-freetext" href="http://www.webex.com">http://www.webex.com</a>

IMPORTANT NOTICE: This WebEx service includes a feature that allows audio and any documents and other materials exchanged or viewed during the session to be recorded. By joining this session, you automatically consent to such recordings. If you do not consent to the recording, discuss your concerns with the meeting host prior to the start of the recording or do not join the session. Please note that any such recordings may be subject to discovery in the event of litigation.
</pre>
      </blockquote>
      <pre wrap="">
</pre>
    </blockquote>
    <br>
    <br>
    <pre class="moz-signature" cols="72">-- 
For corporate legal information go to:

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

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

--------------070501050500030907000009--

From mcr@sandelman.ca  Fri Mar 16 06:28:26 2012
Return-Path: <mcr@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 823A521F870E for <ietf@ietfa.amsl.com>; Fri, 16 Mar 2012 06:28:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.62
X-Spam-Level: 
X-Spam-Status: No, score=-1.62 tagged_above=-999 required=5 tests=[AWL=0.334,  BAYES_00=-2.599, HOST_MISMATCH_NET=0.311, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id k2ayeqzdRvBh for <ietf@ietfa.amsl.com>; Fri, 16 Mar 2012 06:28:25 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [67.23.6.41]) by ietfa.amsl.com (Postfix) with ESMTP id AC97921F8707 for <ietf@ietf.org>; Fri, 16 Mar 2012 06:28:24 -0700 (PDT)
Received: from marajade.sandelman.ca (unknown [38.102.80.246]) by relay.sandelman.ca (Postfix) with ESMTPS id A6E2F344EA for <ietf@ietf.org>; Fri, 16 Mar 2012 09:25:45 -0400 (EDT)
Received: by marajade.sandelman.ca (Postfix, from userid 179) id 42897983BB; Fri, 16 Mar 2012 09:19:43 -0400 (EDT)
Received: from marajade.sandelman.ca (localhost [127.0.0.1]) by marajade.sandelman.ca (Postfix) with ESMTP id 3EB98983BA for <ietf@ietf.org>; Fri, 16 Mar 2012 09:19:43 -0400 (EDT)
From: Michael Richardson <mcr@sandelman.ca>
To: ietf@ietf.org
Subject: Re: Issues relating to managing a mailing list...
In-Reply-To: <4F6253CA.9020507@qualcomm.com>
References: <1344A266-28E8-4228-908F-395FB41EDA83@amsl.com> <01OD44MYQ1ZY00ZUIL@mauve.mrochek.com> <4F6145A0.3020705@gmail.com> <2103063.rDf6FqNnG2@scott-latitude-e6320> <39AB1CE59499893A8E276552@PST.JCK.COM> <8E4035C3ECF01FAE0CCDB05B@caldav.corp.apple.com> <4F620F85.9030702@qualcomm.com> <28C0FE4753BC78A85D5C66CB@caldav.corp.apple.com> <CAJNg7VK8v1U2Gw9BysO-xZ+gNHjbfeitS1PRbjD0ogQRzNrHag@mail.gmail.com> <4F6253CA.9020507@qualcomm.com>
X-Mailer: MH-E 8.3; nmh 1.3-dev; XEmacs 21.4 (patch 22)
Date: Fri, 16 Mar 2012 09:19:43 -0400
Message-ID: <7112.1331903983@marajade.sandelman.ca>
Sender: mcr@sandelman.ca
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Mar 2012 13:28:26 -0000

>>>>> "Pete" == Pete Resnick <presnick@qualcomm.com> writes:
    Pete> (*mumble*) Folks, let's please not try to engineer around user
    Pete> silliness. User silliness will occur no matter what tools we
    Pete> provide.

    Pete> Anybody can get a place on Dropbox or elsewhere and put a URL
    Pete> to their stuff into an email message. The problem is not that
    Pete> the tool isn't there. The problem is that people don't use
    Pete> it. They attach dumb things instead of pointing to them. Or
    Pete> worse they paste them inline, making it even harder for people
    Pete> who use tools that can avoid attachments from having to deal
    Pete> with them. What we need is better decisions and a bit more
    Pete> considerateness by senders of email, not more things to let
    Pete> them continue being dumb.

+1000.

If they can't figure out to produce a URL, then *I* say, they aren't
tall enough to post to an IETF mailing list.

-- 
]       He who is tired of Weird Al is tired of life!           |  firewalls  [
]   Michael Richardson, Sandelman Software Works, Ottawa, ON    |net architect[
] mcr@sandelman.ottawa.on.ca http://www.sandelman.ottawa.on.ca/ |device driver[
   Kyoto Plus: watch the video <http://www.youtube.com/watch?v=kzx1ycLXQSE>
	               then sign the petition. 

From yaoguang.china@gmail.com  Thu Mar 15 23:42:11 2012
Return-Path: <yaoguang.china@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5874121E8035; Thu, 15 Mar 2012 23:42:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.732
X-Spam-Level: 
X-Spam-Status: No, score=-0.732 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_43=0.6, J_CHICKENPOX_46=0.6, RCVD_IN_DNSWL_LOW=-1, SARE_HTML_USL_OBFU=1.666]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QTlTNTcwK4Nv; Thu, 15 Mar 2012 23:42:07 -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 6698021E8020; Thu, 15 Mar 2012 23:42:07 -0700 (PDT)
Received: by obbta4 with SMTP id ta4so191946obb.31 for <multiple recipients>; Thu, 15 Mar 2012 23:42: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; bh=g9wVAb1TKnT/pkPo1wQfTfSPIdSQ7OkrOwVwURIEnMQ=; b=s2QolDtabkEUcEsJ6EcfTAiQIU7z9algqvhCuhXB4w+EPCtKJSlpcjvd6MNunIg5t4 6LurqdFAG7feVFTr+l+sBHmfVOL1JsGKXz/uKObUJDT9JE9soDrsw9/TMSudxJ4ZHCYH k1UzlppfWX06Hs+MTYVp6fX6eDkCbtLU0igMF1aOSZxmPWmEF3vu9iguCXnx2r1kx3xJ btfw71EfFeD5hSKpYkqCJAMKVzJcO/1xXoQRlYkb4qEHQaPmb5O8OwZ3IeKi+M3A2Tsg yL9IJ69RUZSQhGv7a60+ZslLwM14AwZRV9XOJhO7LiShaX1reNCq/0SvaUDaO9Pmjz2y hiHQ==
MIME-Version: 1.0
Received: by 10.182.41.5 with SMTP id b5mr1388049obl.79.1331880126852; Thu, 15 Mar 2012 23:42:06 -0700 (PDT)
Received: by 10.182.124.38 with HTTP; Thu, 15 Mar 2012 23:42:06 -0700 (PDT)
In-Reply-To: <4F5F623F.3030907@cisco.com>
References: <20120306150141.8315.38572.idtracker@ietfa.amsl.com> <4F5F623F.3030907@cisco.com>
Date: Fri, 16 Mar 2012 14:42:06 +0800
Message-ID: <CA+=FF_6wzcSHuKG9mYTZgajb5uKC5G0ikXp2e4F3BPPd3U8+Cg@mail.gmail.com>
Subject: Re: [savi] Last Call: <draft-ietf-savi-dhcp-12.txt> (SAVI Solution for DHCP) to Proposed Standard
From: Guang Yao <yaoguang.china@gmail.com>
To: eric levy-abegnoli <elevyabe@cisco.com>
Content-Type: multipart/mixed; boundary=f46d0445179bd82da204bb5681e8
X-Mailman-Approved-At: Fri, 16 Mar 2012 08:03:58 -0700
Cc: savi@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Mar 2012 06:42:11 -0000

--f46d0445179bd82da204bb5681e8
Content-Type: multipart/alternative; boundary=f46d0445179bd82d9504bb5681e6

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

Hi, Eric

Thank you for the comments. My replies are in the line. We have updated the
text as the attachment. Sorry for it cannot be submitted because the submit
window is closed.

Best regards,
Guang

2012/3/13 eric levy-abegnoli <elevyabe@cisco.com>

> Hi,
> here are my substantive comments
> Look for  [eric].
> Eric
>
> 7.3.1. Timer Expiration Event
>
>   EVE_ENTRY_EXPIRE: The lifetime of an entry expires
>
> [eric] 2 minutes sounds very long. DHCP client timeout is 1 sec for the
> first
> message. Then multiplied by 2, etc. What is the rational behind this
> value, which increase the window for DoS attacks?
>
[guang]
In RFC3315, it reads:
"RT for the first message transmission is based on IRT:

      RT = IRT + RAND*IRT

   RT for each subsequent message transmission is based on the previous
   value of RT:

      RT = 2*RTprev + RAND*RTprev

   MRT specifies an upper bound on the value of RT (disregarding the
   randomization added by the use of RAND).  If MRT has a value of 0,
   there is no upper limit on the value of RT.  Otherwise:

      if (RT > MRT)

RT = MRT + RAND*MRT"

Here MRT is 120s. Based on this value, the maximum  retransmission time is
in range of 120s(+-)12s. Thus, we think 120s is a favorable value to remove
an entry.
The DoS in this window is a problem, but we think the binding number
limitation on each binding anchor can mitigate the damage.

>
> 8. Supplemental Binding Process
> [eric] This section is very unclear. The conditional SHOULD
>   based on  "vendor ability" sounds like a "MAY" to me, which is not
>   what I remember of the WG consensus. In addition, hosts are not
>   required to (DHCP) re-configure upon link flapping, even when they
>   are directly attached.  The text seems to indicate otherwise.
>   In practice, in the absence of such mechanism, traffic will be blocked.
>
> [guang]
We have removed the condition on "vendor ability" . Link flap is handled
through keeping bindings for a period after binding anchor off-link. We
have changed the text to make it clear.


>  8.1. Binding Recovery Process
> [eric] It is unclear what the address is bound to. In the normal case,
>     the entry is created upon receiving a message (i.e. REQUEST) from
>     the client, and the anchor is stored by that time. You should
>     specified where the anchor comes from in this scenario, and where
>     was it stored (given that the section specifies the binding entry
> creattion on LQ Reply)
>
 [guang]
We have changed the text, and specified each step. Tell me if it is still
unclear.

>
> 10. State Restoration
> [eric] Requiring non-volatile memory sounds wrong. Other techniques
> exists such as redundant boxes (switches) synchronizing states. I
> don't recall that non-volatile memory was discussed at length in the
> WG, especially given that it carries its own challenges: frequency
> for saving states, load incurred, etc)
> The one technique that was discussed in the WG was Binding Recovery
> process.  One solution should be enough.

[guang]
There can be a large number of bindings on the savi device. If only relying
on the binding recovery process, there can be a large latency. Especially,
the recovery in this mechanism requires querying the DHCP server.
Moreover, the storing in non-volatile memory is just recommended but not
mandatory. Using redundant box can be  another suggestion. We have change
the MUST to MAY in text.

>
>
> Eric
>
>
> On 06/03/12 16:01, The IESG wrote:
>
>> The IESG has received a request from the Source Address Validation
>> Improvements WG (savi) to consider the following document:
>> - 'SAVI Solution for DHCP'
>>   <draft-ietf-savi-dhcp-12.txt>  as a 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-03-20. 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 specifies the procedure for creating bindings between a
>>    DHCPv4 [RFC2131]/DHCPv6 [RFC3315] assigned source IP address and a
>>    binding anchor [I-D.ietf-savi-framework] on SAVI (Source Address
>>    Validation Improvements) device. The bindings can be used to filter
>>    packets generated on the local link with forged source IP address.
>>
>>
>>
>>
>> The file can be obtained via
>> http://datatracker.ietf.org/**doc/draft-ietf-savi-dhcp/<http://datatracker.ietf.org/doc/draft-ietf-savi-dhcp/>
>>
>> IESG discussion can be tracked via
>> http://datatracker.ietf.org/**doc/draft-ietf-savi-dhcp/**ballot/<http://datatracker.ietf.org/doc/draft-ietf-savi-dhcp/ballot/>
>>
>>
>> No IPR declarations have been submitted directly on this I-D.
>>
>>
>> ______________________________**_________________
>> savi mailing list
>> savi@ietf.org
>> https://www.ietf.org/mailman/**listinfo/savi<https://www.ietf.org/mailman/listinfo/savi>
>>
>>
> ______________________________**_________________
> savi mailing list
> savi@ietf.org
> https://www.ietf.org/mailman/**listinfo/savi<https://www.ietf.org/mailman/listinfo/savi>
>

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

Hi, Eric<div><br></div><div>Thank you for the comments. My replies are in t=
he line. We have updated the text as the attachment. Sorry for it cannot be=
 submitted because the submit window is closed.</div><div><br></div><div>
Best regards,</div><div>Guang<br><div><br><div class=3D"gmail_quote">2012/3=
/13 eric levy-abegnoli <span dir=3D"ltr">&lt;<a href=3D"mailto:elevyabe@cis=
co.com" target=3D"_blank">elevyabe@cisco.com</a>&gt;</span><br><blockquote =
class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid=
;padding-left:1ex">

Hi,<br>
here are my substantive comments<br>
Look for =A0[eric].<br>
Eric<br>
<br>
7.3.1. Timer Expiration Event<br>
<br>
 =A0 EVE_ENTRY_EXPIRE: The lifetime of an entry expires<br>
<br>
[eric] 2 minutes sounds very long. DHCP client timeout is 1 sec for the fir=
st<br>
message. Then multiplied by 2, etc. What is the rational behind this value,=
 which increase the window for DoS attacks?<br></blockquote><div>[guang]</d=
iv><div>In RFC3315, it reads:</div><div>&quot;<span style=3D"white-space:pr=
e-wrap">RT for the first message transmission is based on IRT:</span></div>

<pre style=3D"word-wrap:break-word;white-space:pre-wrap">      RT =3D IRT +=
 RAND*IRT

   RT for each subsequent message transmission is based on the previous
   value of RT:

      RT =3D 2*RTprev + RAND*RTprev

   MRT specifies an upper bound on the value of RT (disregarding the
   randomization added by the use of RAND).  If MRT has a value of 0,
   there is no upper limit on the value of RT.  Otherwise:

      if (RT &gt; MRT)=A0</pre><div><span style=3D"white-space:pre-wrap">  =
       RT =3D MRT + RAND*MRT</span>&quot;</div><div><br></div><div>Here MRT=
 is 120s. Based on this value, the maximum =A0retransmission time is in ran=
ge of 120s(+-)12s. Thus, we think 120s is a=A0favorable value to remove an =
entry.=A0</div>

<div>The DoS in this window is a problem, but we think the binding number l=
imitation on each binding anchor can mitigate the damage.</div><blockquote =
class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid=
;padding-left:1ex">


<br>
8. Supplemental Binding Process<br>
[eric] This section is very unclear. The conditional SHOULD<br>
 =A0 based on =A0&quot;vendor ability&quot; sounds like a &quot;MAY&quot; t=
o me, which is not<br>
 =A0 what I remember of the WG consensus. In addition, hosts are not<br>
 =A0 required to (DHCP) re-configure upon link flapping, even when they<br>
 =A0 are directly attached. =A0The text seems to indicate otherwise.<br>
 =A0 In practice, in the absence of such mechanism, traffic will be blocked=
.<br>
<br></blockquote><div>[guang]</div><div>We have removed the condition on &q=
uot;vendor ability&quot;=A0. Link flap is handled through keeping bindings =
for a period after binding anchor off-link. We have changed the text to mak=
e it clear.<br>
</div><div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0=
 .8ex;border-left:1px #ccc solid;padding-left:1ex">
 =A08.1. Binding Recovery Process<br>
[eric] It is unclear what the address is bound to. In the normal case,<br>
 =A0 =A0 the entry is created upon receiving a message (i.e. REQUEST) from<=
br>
 =A0 =A0 the client, and the anchor is stored by that time. You should<br>
 =A0 =A0 specified where the anchor comes from in this scenario, and where<=
br>
 =A0 =A0 was it stored (given that the section specifies the binding entry =
creattion on LQ Reply)<br></blockquote><div>=A0[guang]</div><div>We have ch=
anged the text, and specified each step. Tell me if it is still unclear.</d=
iv>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">

<br>
10. State Restoration<br>
[eric] Requiring non-volatile memory sounds wrong. Other techniques<br>
exists such as redundant boxes (switches) synchronizing states. I<br>
don&#39;t recall that non-volatile memory was discussed at length in the<br=
>
WG, especially given that it carries its own challenges: frequency<br>
for saving states, load incurred, etc)<br>
The one technique that was discussed in the WG was Binding Recovery<br>
process. =A0One solution should be enough.</blockquote><div>[guang]</div><d=
iv>There can be a large number of bindings on the savi device. If only rely=
ing on the binding recovery process, there can be a large latency. Especial=
ly, the recovery in this mechanism requires querying the DHCP server.=A0</d=
iv>

<div>Moreover, the storing in non-volatile memory is just recommended but n=
ot mandatory. Using redundant box can be=A0=A0another suggestion. We have c=
hange the MUST to MAY in text.</div><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">

<span><font color=3D"#888888"><br>
<br>
Eric</font></span><div><div><br>
<br>
On 06/03/12 16:01, The IESG wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
The IESG has received a request from the Source Address Validation<br>
Improvements WG (savi) to consider the following document:<br>
- &#39;SAVI Solution for DHCP&#39;<br>
 =A0 &lt;draft-ietf-savi-dhcp-12.txt&gt; =A0as a Proposed Standard<br>
<br>
The IESG plans to make a decision in the next few weeks, and solicits<br>
final comments on this action. Please send substantive comments to the<br>
<a href=3D"mailto:ietf@ietf.org" target=3D"_blank">ietf@ietf.org</a> mailin=
g lists by 2012-03-20. Exceptionally, comments may be<br>
sent to <a href=3D"mailto:iesg@ietf.org" target=3D"_blank">iesg@ietf.org</a=
> instead. In either case, please retain the<br>
beginning of the Subject line to allow automated sorting.<br>
<br>
Abstract<br>
<br>
<br>
 =A0 =A0This document specifies the procedure for creating bindings between=
 a<br>
 =A0 =A0DHCPv4 [RFC2131]/DHCPv6 [RFC3315] assigned source IP address and a<=
br>
 =A0 =A0binding anchor [I-D.ietf-savi-framework] on SAVI (Source Address<br=
>
 =A0 =A0Validation Improvements) device. The bindings can be used to filter=
<br>
 =A0 =A0packets generated on the local link with forged source IP address.<=
br>
<br>
<br>
<br>
<br>
The file can be obtained via<br>
<a href=3D"http://datatracker.ietf.org/doc/draft-ietf-savi-dhcp/" target=3D=
"_blank">http://datatracker.ietf.org/<u></u>doc/draft-ietf-savi-dhcp/</a><b=
r>
<br>
IESG discussion can be tracked via<br>
<a href=3D"http://datatracker.ietf.org/doc/draft-ietf-savi-dhcp/ballot/" ta=
rget=3D"_blank">http://datatracker.ietf.org/<u></u>doc/draft-ietf-savi-dhcp=
/<u></u>ballot/</a><br>
<br>
<br>
No IPR declarations have been submitted directly on this I-D.<br>
<br>
<br>
______________________________<u></u>_________________<br>
savi mailing list<br>
<a href=3D"mailto:savi@ietf.org" target=3D"_blank">savi@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/savi" target=3D"_blank">ht=
tps://www.ietf.org/mailman/<u></u>listinfo/savi</a><br>
<br>
</blockquote>
<br>
______________________________<u></u>_________________<br>
savi mailing list<br>
<a href=3D"mailto:savi@ietf.org" target=3D"_blank">savi@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/savi" target=3D"_blank">ht=
tps://www.ietf.org/mailman/<u></u>listinfo/savi</a><br>
</div></div></blockquote></div><br></div></div>

--f46d0445179bd82d9504bb5681e6--
--f46d0445179bd82da204bb5681e8
Content-Type: text/plain; charset=US-ASCII; name="draft-ietf-savi-dhcp-13.txt"
Content-Disposition: attachment; filename="draft-ietf-savi-dhcp-13.txt"
Content-Transfer-Encoding: base64
X-Attachment-Id: f_gzuv0xlo0

U0FWSSAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICBKLiBCaSwg
Si4gV3UsIEcuIFlhbwpJbnRlcm5ldCBEcmFmdCAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgIFRzaW5naHVhIFVuaXYuCkludGVuZGVkIHN0YXR1czogU3RhbmRhcmQgVHJh
Y2tzICAgICAgICAgICAgICAgICAgICAgICAgICAgICBGLiBCYWtlcgpFeHBpcmVzOiBTZXB0ZW1i
ZXIgMjAxMiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICBDaXNjbyBTeXN0ZW1zCiAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgTWFy
Y2ggMTYsIDIwMTIKCgogICAgICAgICAgICAgICAgICAgICAgICAgIFNBVkkgU29sdXRpb24gZm9y
IERIQ1AKICAgICAgICAgICAgICAgICAgICAgICAgZHJhZnQtaWV0Zi1zYXZpLWRoY3AtMTMudHh0
CgoKU3RhdHVzIG9mIHRoaXMgTWVtbwoKICAgVGhpcyBJbnRlcm5ldC1EcmFmdCBpcyBzdWJtaXR0
ZWQgdG8gSUVURiBpbiBmdWxsIGNvbmZvcm1hbmNlIHdpdGggdGhlCiAgIHByb3Zpc2lvbnMgb2Yg
QkNQIDc4IGFuZCBCQ1AgNzkuIFRoaXMgZG9jdW1lbnQgbWF5IG5vdCBiZSBtb2RpZmllZCwKICAg
YW5kIGRlcml2YXRpdmUgd29ya3Mgb2YgaXQgbWF5IG5vdCBiZSBjcmVhdGVkLCBleGNlcHQgdG8g
cHVibGlzaCBpdAogICBhcyBhbiBSRkMgYW5kIHRvIHRyYW5zbGF0ZSBpdCBpbnRvIGxhbmd1YWdl
cyBvdGhlciB0aGFuIEVuZ2xpc2guCgogICBJbnRlcm5ldC1EcmFmdHMgYXJlIHdvcmtpbmcgZG9j
dW1lbnRzIG9mIHRoZSBJbnRlcm5ldCBFbmdpbmVlcmluZwogICBUYXNrIEZvcmNlIChJRVRGKSwg
aXRzIGFyZWFzLCBhbmQgaXRzIHdvcmtpbmcgZ3JvdXBzLiBOb3RlIHRoYXQgb3RoZXIKICAgZ3Jv
dXBzIG1heSBhbHNvIGRpc3RyaWJ1dGUgd29ya2luZyBkb2N1bWVudHMgYXMgSW50ZXJuZXQtRHJh
ZnRzLgoKICAgSW50ZXJuZXQtRHJhZnRzIGFyZSBkcmFmdCBkb2N1bWVudHMgdmFsaWQgZm9yIGEg
bWF4aW11bSBvZiBzaXggbW9udGhzCiAgIGFuZCBtYXkgYmUgdXBkYXRlZCwgcmVwbGFjZWQsIG9y
IG9ic29sZXRlZCBieSBvdGhlciBkb2N1bWVudHMgYXQgYW55CiAgIHRpbWUuICBJdCBpcyBpbmFw
cHJvcHJpYXRlIHRvIHVzZSBJbnRlcm5ldC1EcmFmdHMgYXMgcmVmZXJlbmNlCiAgIG1hdGVyaWFs
IG9yIHRvIGNpdGUgdGhlbSBvdGhlciB0aGFuIGFzICJ3b3JrIGluIHByb2dyZXNzLiIKCiAgIFRo
ZSBsaXN0IG9mIGN1cnJlbnQgSW50ZXJuZXQtRHJhZnRzIGNhbiBiZSBhY2Nlc3NlZCBhdAogICBo
dHRwOi8vd3d3LmlldGYub3JnL2lldGYvMWlkLWFic3RyYWN0cy50eHQKCiAgIFRoZSBsaXN0IG9m
IEludGVybmV0LURyYWZ0IFNoYWRvdyBEaXJlY3RvcmllcyBjYW4gYmUgYWNjZXNzZWQgYXQKICAg
aHR0cDovL3d3dy5pZXRmLm9yZy9zaGFkb3cuaHRtbAoKICAgVGhpcyBJbnRlcm5ldC1EcmFmdCB3
aWxsIGV4cGlyZSBvbiBTZXB0ZW1iZXIgMTUsIDIwMTIuCgpDb3B5cmlnaHQgTm90aWNlCgogICBD
b3B5cmlnaHQgKGMpIDIwMTIgSUVURiBUcnVzdCBhbmQgdGhlIHBlcnNvbnMgaWRlbnRpZmllZCBh
cyB0aGUKICAgZG9jdW1lbnQgYXV0aG9ycy4gQWxsIHJpZ2h0cyByZXNlcnZlZC4KCiAgIFRoaXMg
ZG9jdW1lbnQgaXMgc3ViamVjdCB0byBCQ1AgNzggYW5kIHRoZSBJRVRGIFRydXN0J3MgTGVnYWwK
ICAgUHJvdmlzaW9ucyBSZWxhdGluZyB0byBJRVRGIERvY3VtZW50cwogICAoaHR0cDovL3RydXN0
ZWUuaWV0Zi5vcmcvbGljZW5zZS1pbmZvKSBpbiBlZmZlY3Qgb24gdGhlIGRhdGUgb2YKICAgcHVi
bGljYXRpb24gb2YgdGhpcyBkb2N1bWVudC4gUGxlYXNlIHJldmlldyB0aGVzZSBkb2N1bWVudHMK
ICAgY2FyZWZ1bGx5LCBhcyB0aGV5IGRlc2NyaWJlIHlvdXIgcmlnaHRzIGFuZCByZXN0cmljdGlv
bnMgd2l0aCByZXNwZWN0CiAgIHRvIHRoaXMgZG9jdW1lbnQuIENvZGUgQ29tcG9uZW50cyBleHRy
YWN0ZWQgZnJvbSB0aGlzIGRvY3VtZW50IG11c3QKICAgaW5jbHVkZSBTaW1wbGlmaWVkIEJTRCBM
aWNlbnNlIHRleHQgYXMgZGVzY3JpYmVkIGluIFNlY3Rpb24gNC5lIG9mCgoKCgpCaSAgICAgICAg
ICAgICAgICAgICBFeHBpcmVzIFNlcHRlbWJlciAxNiwgMjAxMiAgICAgICAgICAgICAgIFtQYWdl
IDFdCgwKSW50ZXJuZXQtRHJhZnQgICAgICAgICAgICAgICAgc2F2aS1kaGNwICAgICAgICAgICAg
ICAgICAgICAgTWFyY2ggMjAxMgoKCiAgIHRoZSBUcnVzdCBMZWdhbCBQcm92aXNpb25zIGFuZCBh
cmUgcHJvdmlkZWQgd2l0aG91dCB3YXJyYW50eSBhcwogICBkZXNjcmliZWQgaW4gdGhlIFNpbXBs
aWZpZWQgQlNEIExpY2Vuc2UuCgpBYnN0cmFjdAoKICAgVGhpcyBkb2N1bWVudCBzcGVjaWZpZXMg
dGhlIHByb2NlZHVyZSBmb3IgY3JlYXRpbmcgYmluZGluZ3MgYmV0d2VlbiBhCiAgIERIQ1B2NCBb
UkZDMjEzMV0vREhDUHY2IFtSRkMzMzE1XSBhc3NpZ25lZCBzb3VyY2UgSVAgYWRkcmVzcyBhbmQg
YQogICBiaW5kaW5nIGFuY2hvciBbSS1ELmlldGYtc2F2aS1mcmFtZXdvcmtdIG9uIFNBVkkgKFNv
dXJjZSBBZGRyZXNzCiAgIFZhbGlkYXRpb24gSW1wcm92ZW1lbnRzKSBkZXZpY2UuIFRoZSBiaW5k
aW5ncyBjYW4gYmUgdXNlZCB0byBmaWx0ZXIKICAgcGFja2V0cyBnZW5lcmF0ZWQgb24gdGhlIGxv
Y2FsIGxpbmsgd2l0aCBmb3JnZWQgc291cmNlIElQIGFkZHJlc3MuCgpUYWJsZSBvZiBDb250ZW50
cwoKCiAgIENvcHlyaWdodCBOb3RpY2UgLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4u
Li4uLi4uLi4uLi4uLi4gMQogICBBYnN0cmFjdCAuLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4u
Li4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uIDIKICAgMS4gSW50cm9kdWN0aW9uIC4uLi4uLi4u
Li4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLiAzCiAgIDIuIENvbnZlbnRp
b25zIHVzZWQgaW4gdGhpcyBkb2N1bWVudC4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4gNAog
ICAzLiBUZXJtaW5vbG9neSAuLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4u
Li4uLi4uLi4uIDQKICAgNC4gU0FWSS1ESENQIFNjZW5hcmlvIC4uLi4uLi4uLi4uLi4uLi4uLi4u
Li4uLi4uLi4uLi4uLi4uLi4uLi4uLiA0CiAgIDUuIERhdGEgU3RydWN0dXJlcyAuLi4uLi4uLi4u
Li4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4gNQogICAgICA1LjEuIENvbnRyb2wg
UGxhbmUgRGF0YSBTdHJ1Y3R1cmU6IEJpbmRpbmcgU3RhdGUgVGFibGUgKEJTVCkuIDUKICAgICAg
NS4yLiBEYXRhIFBsYW5lIERhdGEgU3RydWN0dXJlOiBGaWx0ZXJpbmcgVGFibGUgKEZUKS4uLi4u
Li4uLiA2CiAgICAgIDUuMy4gTWFwcGluZyBUYWJsZSBmcm9tIExpbmsgTGF5ZXIgQWRkcmVzcyB0
byBCaW5kaW5nIEFuY2hvci4gNgogICA2LiBCaW5kaW5nIEFuY2hvciBBdHRyaWJ1dGVzLi4uLi4u
Li4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uIDcKICAgICAgNi4xLiBObyBBdHRyaWJ1dGUg
Li4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLiA3CiAgICAgIDYuMi4g
U0FWSS1WYWxpZGF0aW9uIEF0dHJpYnV0ZS4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4g
NwogICAgICA2LjMuIFNBVkktREhDUC1UcnVzdCBBdHRyaWJ1dGUuLi4uLi4uLi4uLi4uLi4uLi4u
Li4uLi4uLi4uLi4uIDcKICAgICAgNi40LiBTQVZJLVNBVkkgQXR0cmlidXRlLi4uLi4uLi4uLi4u
Li4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLiA4CiAgICAgIDYuNS4gU0FWSS1CaW5kUmVjb3Zlcnkg
QXR0cmlidXRlLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4gOAogICA3LiBCaW5kaW5nIFNl
dCBVcCAuLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uIDgKICAg
ICAgNy4xLiBSYXRpb25hbGUgLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4u
Li4uLi4uLiA5CiAgICAgIDcuMi4gQmluZGluZyBTdGF0ZXMgRGVzY3JpcHRpb24uLi4uLi4uLi4u
Li4uLi4uLi4uLi4uLi4uLi4uLi4gOQogICAgICA3LjMuIEV2ZW50cyAuLi4uLi4uLi4uLi4uLi4u
Li4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uIDkKICAgICAgICAgNy4zLjEuIFRpbWVy
IEV4cGlyYXRpb24gRXZlbnQuLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLiA5CiAgICAgICAg
IDcuMy4yLiBDb250cm9sIE1lc3NhZ2UgQXJyaXZpbmcgRXZlbnRzIC4uLi4uLi4uLi4uLi4uLi4u
Li4gOQogICAgICA3LjQuIFByb2Nlc3Mgb2YgREhDUCBQYWNrZXQgU25vb3BpbmcgLi4uLi4uLi4u
Li4uLi4uLi4uLi4uLi4gMTAKICAgICAgICAgNy40LjEuIEZyb20gTk9fQklORCB0byBPdGhlciBT
dGF0ZXMgLi4uLi4uLi4uLi4uLi4uLi4uLi4uIDEwCiAgICAgICAgICAgIDcuNC4xLjEuIFRyaWdn
ZXIgRXZlbnQuLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLiAxMAogICAgICAgICAgICA3
LjQuMS4yLiBGb2xsb3dpbmcgQWN0aW9ucy4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4gMTAK
ICAgICAgICAgNy40LjIuIEZyb20gSU5JVF9CSU5EIHRvIE90aGVyIFN0YXRlcyAuLi4uLi4uLi4u
Li4uLi4uLi4uIDEyCiAgICAgICAgICAgIDcuNC4yLjEuIFRyaWdnZXIgRXZlbnQuLi4uLi4uLi4u
Li4uLi4uLi4uLi4uLi4uLi4uLi4uLiAxMgogICAgICAgICAgICA3LjQuMi4yLiBGb2xsb3dpbmcg
QWN0aW9ucy4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4gMTIKICAgICAgICAgNy40LjMuIEZy
b20gQk9VTkQgdG8gT3RoZXIgU3RhdGVzIC4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uIDEzCiAgICAg
ICAgICAgIDcuNC4zLjEuIFRyaWdnZXIgRXZlbnQuLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4u
Li4uLiAxMwogICAgICAgICAgICA3LjQuMy4yLiBGb2xsb3dpbmcgQWN0aW9ucy4uLi4uLi4uLi4u
Li4uLi4uLi4uLi4uLi4uLi4gMTMKICAgICAgNy41LiBTdGF0ZSBNYWNoaW5lIG9mIERIQ1AgU25v
b3BpbmcgLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uIDE0CgoKQmkgICAgICAgICAgICAgICAgICAg
RXhwaXJlcyBTZXB0ZW1iZXIgMTYsIDIwMTIgICAgICAgICAgICAgICBbUGFnZSAyXQoMCkludGVy
bmV0LURyYWZ0ICAgICAgICAgICAgICAgIHNhdmktZGhjcCAgICAgICAgICAgICAgICAgICAgIE1h
cmNoIDIwMTIKCgogICA4LiBTdXBwbGVtZW50YWwgQmluZGluZyBQcm9jZXNzLi4uLi4uLi4uLi4u
Li4uLi4uLi4uLi4uLi4uLi4uLi4gMTUKICAgICAgOC4xLiBCaW5kaW5nIFN0YXRlcyBEZXNjcmlw
dGlvbi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uIDE1CiAgICAgIDguMi4gRXZlbnRzIC4u
Li4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLiAxNgogICAgICA4
LjMuIEJpbmRpbmcgUmVjb3ZlcnkgUHJvY2Vzcy4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4u
Li4gMTYKICAgICAgICAgOC4zLjEuIEZyb20gTk9fQklORCB0byBPdGhlciBTdGF0ZXMgLi4uLi4u
Li4uLi4uLi4uLi4uLi4uIDE2CiAgICAgICAgICAgIDguMy4xLjEuIFRyaWdnZXIgRXZlbnQuLi4u
Li4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLiAxNgogICAgICAgICAgICA4LjMuMS4yLiBGb2xs
b3dpbmcgQWN0aW9uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4gMTYKICAgICAgICAgOC4z
LjIuIEZyb20gREVURUNUSU9OIHRvIE90aGVyIFN0YXRlcyAuLi4uLi4uLi4uLi4uLi4uLi4uIDE3
CiAgICAgICAgICAgIDguMy4yLjEuIFRyaWdnZXIgRXZlbnQuLi4uLi4uLi4uLi4uLi4uLi4uLi4u
Li4uLi4uLi4uLiAxNwogICAgICAgICAgICA4LjMuMi4yLiBGb2xsb3dpbmcgQWN0aW9uLi4uLi4u
Li4uLi4uLi4uLi4uLi4uLi4uLi4uLi4gMTcKICAgICAgICAgOC4zLjMuIEZyb20gUkVDT1ZFUlkg
dG8gT3RoZXIgU3RhdGVzIC4uLi4uLi4uLi4uLi4uLi4uLi4uIDE3CiAgICAgICAgICAgIDguMy4z
LjEuIFRyaWdnZXIgRXZlbnQuLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLiAxNwogICAg
ICAgICAgICA4LjMuMy4yLiBGb2xsb3dpbmcgQWN0aW9uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4u
Li4uLi4gMTgKICAgOS4gRmlsdGVyaW5nIFNwZWNpZmljYXRpb24uLi4uLi4uLi4uLi4uLi4uLi4u
Li4uLi4uLi4uLi4uLi4uLi4uIDE4CiAgICAgIDkuMS4gRGF0YSBQYWNrZXQgRmlsdGVyaW5nLi4u
Li4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLiAxOAogICAgICA5LjIuIENvbnRyb2wgUGFj
a2V0IEZpbHRlcmluZy4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4gMTkKICAgMTAuIFN0
YXRlIFJlc3RvcmF0aW9uIC4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4u
IDE5CiAgIDExLiBIYW5kbGUgQmluZGluZyBBbmNob3IgT2ZmLWxpbmsgRXZlbnQgLi4uLi4uLi4u
Li4uLi4uLi4uLi4uLiAyMAogICAxMi4gQ29uc3RhbnRzIC4uLi4uLi4uLi4uLi4uLi4uLi4uLi4u
Li4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4gMjAKICAgMTMuIFNlY3VyaXR5IENvbnNpZGVyYXRp
b25zLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uIDIwCiAgICAgIDEzLjEuIFNl
Y3VyaXR5IFByb2JsZW0gYWJvdXQgQmluZGluZyBUcmlnZ2VyZWQgYnkKICAgICAgRVZFX0RIQ1Bf
UkVQTFlfTlVMTCAuLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uIDIwCiAg
ICAgIDEzLjIuIEJpbmRpbmcgTnVtYmVyIExpbWl0YXRpb24uLi4uLi4uLi4uLi4uLi4uLi4uLi4u
Li4uLi4uLiAyMQogICAgICAxMy4zLiBSaXNrIGZyb20gTGluayBMYXllciBSb3V0aW5nIER5bmFt
aWMgLi4uLi4uLi4uLi4uLi4uLi4gMjIKICAgICAgMTMuNC4gRHVwbGljYXRlIEJpbmRpbmdzIG9m
IFNhbWUgQWRkcmVzcyAuLi4uLi4uLi4uLi4uLi4uLi4uIDIyCiAgICAgIDEzLjUuIFNlY3VyaXR5
IFByb2JsZW1zIGFib3V0IEJpbmRpbmcgUmVjb3ZlcnkgUHJvY2Vzcy4uLi4uLiAyMgogICAgICAx
My42LiBDb21wYXRpYmlsaXR5IHdpdGggRE5BIChEZXRlY3RpbmcgTmV0d29yayBBdHRhY2htZW50
KS4gMjMKICAgICAgMTMuNy4gUmVzaWR1YWwgVGhyZWF0cy4uLi4uLi4uLi4uLi4uLi4uLi4uLi4u
Li4uLi4uLi4uLi4uLi4uIDI0CiAgIDE0LiBJQU5BIENvbnNpZGVyYXRpb25zLi4uLi4uLi4uLi4u
Li4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLiAyNAogICAxNS4gUmVmZXJlbmNlcyAuLi4uLi4u
Li4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4gMjQKICAgICAgMTUuMS4g
Tm9ybWF0aXZlIFJlZmVyZW5jZXMuLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uIDI0
CiAgICAgIDE1LjIuIEluZm9ybWF0aXZlIFJlZmVyZW5jZXMuLi4uLi4uLi4uLi4uLi4uLi4uLi4u
Li4uLi4uLi4uLiAyNgogICAxNi4gQWNrbm93bGVkZ21lbnRzIC4uLi4uLi4uLi4uLi4uLi4uLi4u
Li4uLi4uLi4uLi4uLi4uLi4uLi4uLi4gMjYKICAgMTcuIENoYW5nZSBMb2cgLi4uLi4uLi4uLi4u
Li4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uIDI3CgoxLiBJbnRyb2R1Y3Rpb24K
CiAgIFRoaXMgZG9jdW1lbnQgZGVzY3JpYmVzIHRoZSBwcm9jZWR1cmUgZm9yIGNyZWF0aW5nIGJp
bmRpbmcgYmV0d2VlbgogICBESENQIGFkZHJlc3MgYW5kIGJpbmRpbmcgYW5jaG9yIG9uIFNBVkkg
ZGV2aWNlIFtJLUQuaWV0Zi1zYXZpLQogICBmcmFtZXdvcmtdLiBUaGUgcmVtb3ZhbCBhbmQgcmVz
dG9yYXRpb24gb2YgdGhlIGJpbmRpbmdzIGFyZSBhbHNvCiAgIHNwZWNpZmllZCBpbiB0aGlzIGRv
Y3VtZW50LgoKICAgQmluZGluZ3MgY2FuIGJlIHVzZWQgdG8gZmlsdGVyIG9yIGlkZW50aWZ5IHBh
Y2tldHMgd2l0aCBmb3JnZWQgc291cmNlCiAgIElQIGFkZHJlc3MuIFNlY3Rpb24gOSBzdWdnZXN0
cyB1c2FnZSBvZiB0aGVzZSBiaW5kaW5ncyBmb3IgY29tbW9uCiAgIHByYWN0aWNlLgoKCgoKQmkg
ICAgICAgICAgICAgICAgICAgRXhwaXJlcyBTZXB0ZW1iZXIgMTYsIDIwMTIgICAgICAgICAgICAg
ICBbUGFnZSAzXQoMCkludGVybmV0LURyYWZ0ICAgICAgICAgICAgICAgIHNhdmktZGhjcCAgICAg
ICAgICAgICAgICAgICAgIE1hcmNoIDIwMTIKCgogICBUaGUgbWVjaGFuaXNtIHNwZWNpZmllZCBp
biB0aGlzIGRvY3VtZW50IGlzIGRlc2lnbmVkIHRvIHByb3ZpZGUgYQogICBiaW5kaW5nIGFuY2hv
ciBncmFudWxhcml0eSB2YWxpZGF0aW9uLCBhcyBhIHN1cHBsZW1lbnQgdG8gQkNQMzgKICAgW0JD
UDM4XS4gVGhpcyBtZWNoYW5pc20gaXMgZGVwbG95ZWQgb24gdGhlIGFjY2VzcyBkZXZpY2UgKGlu
Y2x1ZGluZwogICBhY2Nlc3Mgc3dpdGNoLCB3aXJlbGVzcyBhY2Nlc3MgcG9pbnQvY29udHJvbGxl
ciwgZXRjKSwgYW5kIHBlcmZvcm1zCiAgIG1haW5seSBESENQIHNub29waW5nIHRvIHNldCB1cCBi
aW5kaW5ncyBiZXR3ZWVuIElQIGFkZHJlc3NlcyBhc3NpZ25lZAogICBieSBESENQIGFuZCBjb3Jy
ZXNwb25kaW5nIGJpbmRpbmcgYW5jaG9ycy4gVGhlIGJpbmRpbmcgcHJvY2VzcyBpcwogICBpbnNw
aXJlZCBieSB0aGUgd29yayBvZiBJUCBTb3VyY2UgR3VhcmQgW0lQIFNvdXJjZSBHdWFyZF0uCgog
ICBUaGlzIHNvbHV0aW9uIGlzIGRlc2lnbmVkIGZvciBzdGF0ZWZ1bCBESENQIHNjZW5hcmlvIFtS
RkMyMTMxXSwKICAgW1JGQzMzMTVdLiBJbiBzdGF0ZWxlc3MgREhDUCBzY2VuYXJpb3MgW1JGQzM3
MzZdLCBhIG5vZGUgbXVzdCBoYXZlCiAgIG9idGFpbmVkIGl0cyBJUHY2IGFkZHJlc3NlcyB0aHJv
dWdoIHNvbWUgb3RoZXIgbWVjaGFuaXNtcyBhbmQgc28gdGhlCiAgIGFkZHJlc3Mgb2YgdGhlIGNs
aWVudCBTSE9VTEQgYmUgYm91bmQgYmFzZWQgb24gb3RoZXIgU0FWSSBzb2x1dGlvbnMKCiAgIFRo
aXMgc29sdXRpb24gaXMgcHJpbWFyaWx5IGRlc2lnbmVkIGZvciBhIHB1cmUgREhDUCBzY2VuYXJp
byBpbiB3aGljaAogICBvbmx5IERIQ1AgYWRkcmVzcyBpcyBsZWdpdGltYXRlIGdsb2JhbCBhZGRy
ZXNzLiBIb3cgdG8gdXNlIHRoaXMKICAgbWVjaGFuaXNtIGluIG11bHRpcGxlIGFkZHJlc3MgYXNz
aWdubWVudHMgc2NlbmFyaW8gaXMgZGlzY3Vzc2VkIGluCiAgIFtJLUQuaWV0Zi1zYXZpLW1peF0u
CgoyLiBDb252ZW50aW9ucyB1c2VkIGluIHRoaXMgZG9jdW1lbnQKCiAgIFRoZSBrZXkgd29yZHMg
Ik1VU1QiLCAiTVVTVCBOT1QiLCAiUkVRVUlSRUQiLCAiU0hBTEwiLCAiU0hBTEwgTk9UIiwKICAg
IlNIT1VMRCIsICJTSE9VTEQgTk9UIiwgIlJFQ09NTUVOREVEIiwgIk5PVCBSRUNPTU1FTkRFRCIs
ICJNQVkiLCBhbmQKICAgIk9QVElPTkFMIiBpbiB0aGlzIGRvY3VtZW50IGFyZSB0byBiZSBpbnRl
cnByZXRlZCBhcyBkZXNjcmliZWQgaW4KICAgW1JGQzIxMTldLgoKMy4gVGVybWlub2xvZ3kKCiAg
IExlYXNlIHRpbWU6ICAgTGVhc2UgdGltZSBpbiBJUHY0IFtSRkMyMTMxXSBhbmQgdmFsaWQgbGlm
ZXRpbWUgaW4KICAgSVB2NiBbUkZDMzMxNV0KCjQuIFNBVkktREhDUCBTY2VuYXJpbwoKICAgRmln
dXJlIDEgc2hvd3MgdGhlIG1haW4gZWxlbWVudHMgaW4gYSBESENQIG5ldHdvcmsuIEF0IGxlYXN0
IG9uZSBESENQCiAgIHNlcnZlciBtdXN0IGJlIGRlcGxveWVkIGluIHRoZSBuZXR3b3JrLCBhbmQg
REhDUCByZWxheSBtYXkgYmUgdXNlZCB0bwogICByZWxheSBtZXNzYWdlIGJldHdlZW4gY2xpZW50
IGFuZCBzZXJ2ZXIuIE11bHRpcGxlIFNBVkkgZGV2aWNlcyBhbmQKICAgbm9uLVNBVkkgZGV2aWNl
cyBjYW4gY28tZXhpc3Qgb24gbGluay4gQSBTQVZJIGRldmljZSBjYW4gYmUgY29ubmVjdGVkCiAg
IHRvIERIQ1AgY2xpZW50LCBESENQIHJlbGF5IChldmVuIERIQ1Agc2VydmVyKSwgU0FWSSBkZXZp
Y2UgYW5kIG5vbi0KICAgU0FWSSBkZXZpY2UuCgogICBPdGhlciBhZGRyZXNzIGFzc2lnbm1lbnQg
bWVjaGFuaXNtcyBtYXkgYmUgYWxzbyB1c2VkIGluIHN1Y2ggYQogICBuZXR3b3JrLiBIb3dldmVy
LCB0aGlzIHNvbHV0aW9uIGlzIHByaW1hcmlseSBkZXNpZ25lZCBmb3IgYSBwdXJlIERIQ1AKICAg
c2NlbmFyaW8sIGluIHdoaWNoIG9ubHkgREhDUCBzZXJ2ZXJzIGNhbiBhc3NpZ24gdmFsaWQgZ2xv
YmFsIGFkZHJlc3MuCgogICBOb3RlIHRoYXQgaW4gSVB2NiBlbnZpcm9ubWVudCwgZXZlcnkgaW50
ZXJmYWNlIGhhcyBhIGxpbmstbG9jYWwKICAgYWRkcmVzcywgd2hpY2ggaXMgbm90IGFzc2lnbmVk
IGJ5IERIQ1AuIFRoaXMgc29sdXRpb24gd2lsbCBub3QKICAgdmFsaWRhdGUgbGluay1sb2NhbCBh
ZGRyZXNzLiBJdCBpcyBTVUdHRVNURUQgdG8gZW5hYmxlIGEgU0FWSQogICBzb2x1dGlvbiBmb3Ig
bGluay1sb2NhbCBhZGRyZXNzZXMsIGUuZy4gW0ktRC5pZXRmLXNhdmktZmNmc10uCgoKQmkgICAg
ICAgICAgICAgICAgICAgRXhwaXJlcyBTZXB0ZW1iZXIgMTYsIDIwMTIgICAgICAgICAgICAgICBb
UGFnZSA0XQoMCkludGVybmV0LURyYWZ0ICAgICAgICAgICAgICAgIHNhdmktZGhjcCAgICAgICAg
ICAgICAgICAgICAgIE1hcmNoIDIwMTIKCgoKICAgICAgICAgICAgICAgICAgICAgICAgICAgICAv
LS0tLS0tLS0tLS0tXAogICAgICAgICAgICAgICstLS0tLS0tLSsgICAgIHwgICAgICAgICAgICB8
CiAgICAgICAgICAgICAgfCBESENQICAgfC0tLS0tfCAgIFJvdXRlciBBIHwKICAgICAgICAgICAg
ICB8IFNlcnZlciB8ICAgICB8ICAgICAgICAgICAgfAogICAgICAgICAgICAgICstLS0tLS0tLSsg
ICAgIFwtLS0tLS0tLS0tLS0vCiAgICAgICAgICAgICAuLi4uLi4uLi4uLi4uLi4uLi4uLi4ufC4u
Li4uLi4uLi4KICAgICAgICAgICAgIC4gICAgICAgICAgICAgICAgICAgICB8ICAgICAgICAgLgog
ICAgICAgICAgICAgLiBQcm90ZWN0aW9uICAgICAgICAgIHwgICAgICAgICAuCiAgICAgICAgICAg
ICAuIFBlcmltZXRlciAgICAgICAgICAgfCAgICAgICAgIC4KICAgICAgICAgICAgIC4gICAgICAg
ICAgICAgICAgICAgICB8ICAgICAgICAgLgogICAgICAgICAgICAgLiAgICAgICAgICAgICAgICAg
ICAgIHwgICAgICAgICAuCiAgICAgICAgICAgICAuICAgICAgICAgICAgICAgICAgICAgfCAgICAg
ICAgIC4KICAgICAgICAgICAgIC4gKy0tLS0tLS0tLS0rICAgICstLS0tJy0tLS0tKyAgLiAgICst
LS0tLS0tLS0tKwogICAgICAgICAgICAgLiB8ICBTQVZJICAgIHwgICAgfCAgU0FWSSAgICB8ICAu
ICAgfCAgTm9uIFNBVkl8CiAgICAgICAgICAgICAuIHwgIERldmljZSBBfC0tLS18ICBEZXZpY2Ug
QnwtLS0tLS18ICBEZXZpY2UgIHwKICAgICAgICAgICAgIC4gKy8tLS0uLS0tLS0rICAgICstLi0t
LS0tLS4tKyAgLiAgICstLS0tLS4tLS0tKwogICAgICAgICAgICAgLi4uLi4uLi4uLi4uLi4uLi4u
Li4uLi4uLi4uLi4uLi4uICAgICAgICAgfAogICAgICAgICAgICAgICAgICAgIHwgICAgICAgICAg
ICB8ICAgICAgfCAgICAgICAgICAgICAgfAogICAgICAgICAgICAgICAgICAgIHwgICAgICAgICAg
ICB8ICAgICAgfCAgICAgICAgICAgICAgfAogICAgICAgICAgICAgICArLS0tLS8tLS0tLSsgKy0t
LS1cLSsgICArXC0tLS0tKyAgICAgKy0tXC0tLSsKICAgICAgICAgICAgICAgfCBSb3V0ZXIgQiB8
IHxESENQICB8ICAgfENsaWVudHwgICAgIHxDbGllbnR8CiAgICAgICAgICAgICAgIHwgICAgICAg
ICAgfCB8UmVsYXkgfCAgIHwgQSAgICB8ICAgICB8IEIgICAgfAogICAgICAgICAgICAgICArLS0t
LS0tLS0tLSsgKy0tLS0tLSsgICArLS0tLS0tKyAgICAgKy0tLS0tLSsKICAgICAgICAgICAgICAg
ICAgICAgICAgICBGaWd1cmUgMSBESENQIFNjZW5hcmlvCgoKCjUuIERhdGEgU3RydWN0dXJlcwoK
ICAgVGhpcyBzZWN0aW9uIGRlc2NyaWJlcyB0aGUgZGF0YSBzdHJ1Y3R1cmVzIHVzZWQgaW4gdGhp
cyBtZWNoYW5pc20uCgogICBUd28gbWFpbiBkYXRhIHN0cnVjdHVyZXMgYXJlIHVzZWQgdG8gcmVj
b3JkIGJpbmRpbmdzIGFuZCB0aGVpciBzdGF0ZXMKICAgcmVzcGVjdGl2ZWx5LiBUaGVyZSBpcyBy
ZWR1bmRhbmN5IGJldHdlZW4gdGhlIHR3byBzdHJ1Y3R1cmVzLCBmb3IgdGhlCiAgIGNvbnNpZGVy
YXRpb24gb2Ygc2VwYXJhdGlvbiBvZiBkYXRhIHBsYW5lIGFuZCBjb250cm9sIHBsYW5lLgoKICAg
QmVzaWRlcyB0aGUgdHdvIG1haW4gZGF0YSBzdHJ1Y3R1cmVzLCBhIG1hcHBpbmcgdGFibGUgZnJv
bSBsaW5rIGxheWVyCiAgIGFkZHJlc3MgdG8gYmluZGluZyBhbmNob3IgbWF5IGJlIHJlcXVpcmVk
LCBhcyBkZXNjcmliZWQgaW4gc2VjdGlvbgogICA3LjQuMS4KCiAgNS4xLiAgIENvbnRyb2wgUGxh
bmUgRGF0YSBTdHJ1Y3R1cmU6IEJpbmRpbmcgU3RhdGUgVGFibGUgKEJTVCkKCiAgIFRoaXMgdGFi
bGUgY29udGFpbnMgdGhlIHN0YXRlIG9mIGJpbmRpbmcgYmV0d2VlbiBzb3VyY2UgYWRkcmVzcyBh
bmQKICAgYmluZGluZyBhbmNob3IuIEVudHJpZXMgYXJlIGtleWVkIG9uIHRoZSBiaW5kaW5nIGFu
Y2hvciBhbmQgc291cmNlIElQCiAgIGFkZHJlc3MuIEVhY2ggZW50cnkgaGFzIGEgbGlmZXRpbWUg
ZmllbGQgcmVjb3JkaW5nIHRoZSByZW1haW5pbmcKICAgbGlmZXRpbWUgb2YgdGhlIGVudHJ5LCBh
IHN0YXRlIGZpZWxkIHJlY29yZGluZyB0aGUgc3RhdGUgb2YgdGhlCiAgIGJpbmRpbmcgYW5kIGEg
VElEIGZpZWxkIHJlY29yZGluZyB0cmFuc2FjdGlvbiBJRCBvZiBESENQIG1lc3NhZ2UuIFRoZQoK
CkJpICAgICAgICAgICAgICAgICAgIEV4cGlyZXMgU2VwdGVtYmVyIDE2LCAyMDEyICAgICAgICAg
ICAgICAgW1BhZ2UgNV0KDApJbnRlcm5ldC1EcmFmdCAgICAgICAgICAgICAgICBzYXZpLWRoY3Ag
ICAgICAgICAgICAgICAgICAgICBNYXJjaCAyMDEyCgoKICAgbGlmZXRpbWUgZmllbGQgaXMgdXNl
ZCB0byBoZWxwIHJlbW92ZSBleHBpcmVkIGJpbmRpbmdzLiBUaGUgc3RhdGUKICAgZmllbGQgaXMg
dXNlZCB0byBpZGVudGlmeSBzdGF0ZS4gVGhlIFRJRCBmaWVsZCBpcyB1c2VkIHRvIGtlZXAgdGhl
CiAgIFRyYW5zYWN0aW9uIElEIChUSUQpIFtSRkMyMTMxXVtSRkMzMzE1XSBpbiBESENQIHJlcXVl
c3QuIFRoZSBUSUQKICAgZmllbGQgY2FuIGJlIGNsZWFyZWQgYWZ0ZXIgdGhlIHN0YXRlIGlzIGNo
YW5nZWQgdG8gQk9VTkQuCgogICAgICAgICAgICstLS0tLS0tLS0rLS0tLS0tLS0tLSstLS0tLS0t
LS0tKy0tLS0tLS0tLS0tKy0tLS0tLS0rCiAgICAgICAgICAgfCBBbmNob3IgIHwgQWRkcmVzcyAg
fCBTdGF0ZSAgICB8IExpZmV0aW1lICB8VElEICAgIHwKICAgICAgICAgICArLS0tLS0tLS0tKy0t
LS0tLS0tLS0rLS0tLS0tLS0tLSstLS0tLS0tLS0tLSstLS0tLS0tKwogICAgICAgICAgIHwgQSAg
ICAgICB8IElQXzEgICAgIHwgQk9VTkQgICAgfCAgNjU1MzUgICAgfFRJRCAxICB8CiAgICAgICAg
ICAgKy0tLS0tLS0tLSstLS0tLS0tLS0tKy0tLS0tLS0tLS0rLS0tLS0tLS0tLS0rLS0tLS0tLSsK
ICAgICAgICAgICB8IEEgICAgICAgfCBJUF8yICAgICB8IEJPVU5EICAgIHwgIDEwMDAwICAgIHxU
SUQgMiAgfAogICAgICAgICAgICstLS0tLS0tLS0rLS0tLS0tLS0tLSstLS0tLS0tLS0tKy0tLS0t
LS0tLS0tKy0tLS0tLS0rCiAgICAgICAgICAgfCBCICAgICAgIHwgSVBfMyAgICAgfElOSVRfQklO
RCB8ICAgICAgMSAgICB8VElEXzMgIHwKICAgICAgICAgICArLS0tLS0tLS0tKy0tLS0tLS0tLS0r
LS0tLS0tLS0tLSstLS0tLS0tLS0tLSstLS0tLS0tKwogICAgICAgICAgICAgICAgICAgICAgICAg
RmlndXJlIDIgSW5zdGFuY2Ugb2YgQlNUCgoKICA1LjIuICAgRGF0YSBQbGFuZSBEYXRhIFN0cnVj
dHVyZTogRmlsdGVyaW5nIFRhYmxlIChGVCkKCiAgIFRoaXMgdGFibGUgY29udGFpbnMgdGhlIGJp
bmRpbmdzIGJldHdlZW4gYmluZGluZyBhbmNob3IgYW5kIGFkZHJlc3MsCiAgIGtleWVkIG9uIGJp
bmRpbmcgYW5jaG9yIGFuZCBhZGRyZXNzLiBUaGlzIHRhYmxlIGRvZXNuJ3QgY29udGFpbiBhbnkK
ICAgc3RhdGUgb2YgdGhlIGJpbmRpbmcuIFRoaXMgdGFibGUgaXMgb25seSB1c2VkIHRvIGZpbHRl
ciBwYWNrZXRzLiBBbgogICBBY2Nlc3MgQ29udHJvbCBMaXN0IGNhbiBiZSByZWdhcmRlZCBhcyBh
IHByYWN0aWNhbCBpbnN0YW5jZSBvZiB0aGlzCiAgIHRhYmxlLiBUaGlzIHRhYmxlIFNIT1VMRCBi
ZSB1cGRhdGVkIGJ5IG90aGVyIFNBVkkgbWVjaGFuaXNtcyBbSS0KICAgRC5pZXRmLXNhdmktbWl4
XSB3aGVuIERIQ1AgU0FWSSBpcyBkZXBsb3llZCBpbiBJUHY2IGVudmlyb25tZW50LCBhcwogICBl
eHBsYWluZWQgaW4gc2VjdGlvbiA0LgoKICAgICAgICAgICAgICAgICAgICAgICAgICArLS0tLS0t
LS0tKy0tLS0tLS0tLS0rCiAgICAgICAgICAgICAgICAgICAgICAgICAgfCBBbmNob3IgIHxBZGRy
ZXNzICAgfAogICAgICAgICAgICAgICAgICAgICAgICAgICstLS0tLS0tLS0rLS0tLS0tLS0tLSsK
ICAgICAgICAgICAgICAgICAgICAgICAgICB8QSAgICAgICAgfElQXzEgICAgICB8CiAgICAgICAg
ICAgICAgICAgICAgICAgICAgKy0tLS0tLS0tLSstLS0tLS0tLS0tKwogICAgICAgICAgICAgICAg
ICAgICAgICAgIHxBICAgICAgICB8SVBfMiAgICAgIHwKICAgICAgICAgICAgICAgICAgICAgICAg
ICArLS0tLS0tLS0tKy0tLS0tLS0tLS0rCiAgICAgICAgICAgICAgICAgICAgICAgICAgRmlndXJl
IDMgSW5zdGFuY2Ugb2YgRlQKCiAgNS4zLiAgTWFwcGluZyBUYWJsZSBmcm9tIExpbmsgTGF5ZXIg
QWRkcmVzcyB0byBCaW5kaW5nIEFuY2hvcgoKICAgQXMgZGVzY3JpYmVkIGluIHNlY3Rpb24gNy40
LjEsIHdoZW5ldmVyIGJpbmRpbmcgYW5jaG9yIG11c3QgYmUKICAgcmVjb3ZlcmVkIGZyb20gRENI
UCBSZXBseSwgc3VjaCBhIG1hcHBpbmcgdGFibGUgaXMgcmVxdWlyZWQuIFRoaXMKICAgdGFibGUg
bWFwcyBsaW5rIGxheWVyIGFkZHJlc3MgdG8gYmluZGluZyBhbmNob3IsIHNvIGFzIHRoYXQgdGhl
IFNBVkkKICAgZGV2aWNlIGNhbiBkZXRlcm1pbmUgb24gd2hpY2ggYmluZGluZyBhbmNob3IgdG8g
c2V0IHVwIGEgYmluZGluZyBvbmx5CiAgIGJhc2VkIG9uIGEgREhDUCBSZXBseSBtZXNzYWdlLgoK
ICAgU3VjaCBhIHRhYmxlIGNhbiBhbHJlYWR5IGV4aXN0IG9uIFNBVkkgZGV2aWNlLiBGb3IgZXhh
bXBsZSwgaWYgdGhlCiAgIGJpbmRpbmcgYW5jaG9yIGlzIHN3aXRjaCBwb3J0LCB0aGUgbWFwcGlu
ZyB0YWJsZSBmcm9tIE1BQyBhZGRyZXNzIHRvCiAgIHN3aXRjaCBwb3J0IGlzIHJlcXVpcmVkIG9u
IHN3aXRjaCBmb3Igc3dpdGNoaW5nIGZyYW1lcy4gV2UgZG9uJ3QKCgpCaSAgICAgICAgICAgICAg
ICAgICBFeHBpcmVzIFNlcHRlbWJlciAxNiwgMjAxMiAgICAgICAgICAgICAgIFtQYWdlIDZdCgwK
SW50ZXJuZXQtRHJhZnQgICAgICAgICAgICAgICAgc2F2aS1kaGNwICAgICAgICAgICAgICAgICAg
ICAgTWFyY2ggMjAxMgoKCiAgIHJlcXVpcmUgU0FWSSBkZXZpY2UgdG8gc2V0IHVwIGEgZGlmZmVy
ZW50IG1hcHBpbmcgdGFibGUgZnJvbSB0aGUKICAgZXhpc3Rpbmcgb25lLiBJbnN0ZWFkLCBTQVZJ
IGRldmljZSBNVVNUIG9ubHkgdXNlIHRoZSBleGlzdGluZyBvbmUuIElmCiAgIHRoZXJlIGlzIG5v
dCBzdWNoIGEgbWFwcGluZyB0YWJsZSB5ZXQsIFNBVkkgZGV2aWNlIE1VU1QgTk9UIHNldCB1cAog
ICBiaW5kaW5nIGJhc2VkIG9uIEVWRV9ESENQX1JFUExZX05VTEwgKGNmLiA3LjQuMSkuCgogICBU
aGUgc2V0IHVwIGFuZCB1cGRhdGUgb2YgdGhpcyB0YWJsZSBpcyBvdXQgb2YgdGhlIHNjb3BlIG9m
IHRoaXMKICAgZG9jdW1lbnQuCgo2LiBCaW5kaW5nIEFuY2hvciBBdHRyaWJ1dGVzCgogICBUaGlz
IHNlY3Rpb24gc3BlY2lmaWVzIHRoZSBiaW5kaW5nIGFuY2hvciBhdHRyaWJ1dGVzIHVzZWQgaW4g
dGhpcwogICBtZWNoYW5pc20uCgogICBBdHRyaWJ1dGUgb2YgZWFjaCBiaW5kaW5nIGFuY2hvciBp
cyBjb25maWd1cmFibGUuIEJ5IGRlZmF1bHQsIGJpbmRpbmcKICAgYW5jaG9yIGhhcyBubyBhdHRy
aWJ1dGUuIEEgYmluZGluZyBhbmNob3IgTUFZIGJlIGNvbmZpZ3VyZWQgdG8gaGF2ZQogICBvbmUg
b3IgbW9yZSBjb21wYXRpYmxlIGF0dHJpYnV0ZXMuCgogIDYuMS4gTm8gQXR0cmlidXRlCgogICBC
ZWZvcmUgY29uZmlndXJhdGlvbiwgYnkgZGVmYXVsdCwgYSBiaW5kaW5nIGFuY2hvciBoYXMgbm8g
YXR0cmlidXRlLgogICBUbyBmaWx0ZXIgYm9ndXMgREhDUCBzZXJ2ZXIgbWVzc2FnZSBieSBkZWZh
dWx0LCBzZXJ2ZXIgdHlwZSBESENQCiAgIG1lc3NhZ2UgZnJvbSBiaW5kaW5nIGFuY2hvciB3aXRo
IG5vIGF0dHJpYnV0ZSBNVVNUIGJlIGRyb3BwZWQuCiAgIEhvd2V2ZXIsIHRvIGF2b2lkIGRpc2Nh
cmRpbmcgbGVnaXRpbWF0ZSB0cmFmZmljLCBvdGhlciBwYWNrZXRzIFNIT1VMRAogICBOT1QgYmUg
ZHJvcHBlZCBiZWZvcmUgYW55IGJpbmRpbmcgaXMgc2V0dXAgb24gc3VjaCBiaW5kaW5nIGFuY2hv
ci4KICAgR2VuZXJhbGx5LCBlYWNoIGJpbmRpbmcgYW5jaG9yIGlzIGNvbmZpZ3VyZWQgdG8gaGF2
ZSBvbmUgb3IgbW9yZQogICBhdHRyaWJ1dGVzIGFmdGVyIGNvbmZpZ3VyYXRpb24uIEhvd2V2ZXIs
IGEgYmluZGluZyBhbmNob3IgTUFZIGFsd2F5cwogICBoYXZlIG5vIGF0dHJpYnV0ZSBpZiBpdCBp
cyBjb25uZWN0ZWQgdG8gYW5vdGhlciBsaW5rLiBGb3IgZXhhbXBsZSwgaW4KICAgRmlndXJlIDEs
IG9uIHRoZSBiaW5kaW5nIGFuY2hvciBvZiBTQVZJIERldmljZSBBIGNvbm5lY3RlZCB0byBSb3V0
ZXIKICAgQiwgaXQgaXMgdW5yZWFzb25hYmxlIGVpdGhlciB0byBzZXQgdXAgYmluZGluZ3MgZm9y
IGhvc3QgYmVoaW5kCiAgIFJvdXRlciBCLCBvciBmaWx0ZXIgb3V0IHRyYWZmaWMgZnJvbSBSb3V0
ZXIgQiwgb3IgYWxsb3cgYm9ndXMgREhDUAogICBtZXNzYWdlIGZyb20gUm91dGVyIEIuIFRodXMs
IG5vIGF0dHJpYnV0ZSBzaG91bGQgYmUgY29uZmlndXJlZCBvbgogICB0aGlzIGJpbmRpbmcgYW5j
aG9yLgoKICA2LjIuIFNBVkktVmFsaWRhdGlvbiBBdHRyaWJ1dGUKCiAgIFNBVkktVmFsaWRhdGlv
biBhdHRyaWJ1dGUgaXMgdXNlZCBvbiBiaW5kaW5nIGFuY2hvciBvbiB3aGljaCB0aGUKICAgc291
cmNlIGFkZHJlc3Mgb2YgZGF0YSBwYWNrZXQgYW5kIERIQ1AgbWVzc2FnZSBpcyB0byBiZSB2YWxp
ZGF0ZWQuCiAgIFRoZSBmaWx0ZXJpbmcgcHJvY2VzcyBvbiBiaW5kaW5nIGFuY2hvciB3aXRoIHN1
Y2ggYXR0cmlidXRlIGlzCiAgIGRlc2NyaWJlZCBpbiBzZWN0aW9uIDkuIEluIEZpZ3VyZSAxLCB0
aGUgYmluZGluZyBhbmNob3IgYmV0d2VlbiBTQVZJCiAgIERldmljZSBCIGFuZCBDbGllbnQgQSwg
YW5kIHRoZSBiaW5kaW5nIGFuY2hvciBiZXR3ZWVuIFNBVkkgRGV2aWNlIEIKICAgYW5kIE5vbiBT
QVZJIERldmljZSBzaG91bGQgYmUgY29uZmlndXJlZCB0byBoYXZlIHRoaXMgYXR0cmlidXRlLgoK
ICA2LjMuIFNBVkktREhDUC1UcnVzdCBBdHRyaWJ1dGUKCiAgIFNBVkktREhDUC1UcnVzdCBBdHRy
aWJ1dGUgaXMgdXNlZCBvbiBiaW5kaW5nIGFuY2hvciBvbiB0aGUgcGF0aCB0byBhCiAgIHRydXN0
YWJsZSBESENQIHNlcnZlci9yZWxheS4gREhDUCBzZXJ2ZXIvcmVsYXkgbWVzc2FnZSBjb21pbmcg
ZnJvbQogICBiaW5kaW5nIGFuY2hvciB3aXRoIHRoaXMgYXR0cmlidXRlIHdpbGwgYmUgZm9yd2Fy
ZGVkLiBJbiBGaWd1cmUgMSwKCgpCaSAgICAgICAgICAgICAgICAgICBFeHBpcmVzIFNlcHRlbWJl
ciAxNiwgMjAxMiAgICAgICAgICAgICAgIFtQYWdlIDddCgwKSW50ZXJuZXQtRHJhZnQgICAgICAg
ICAgICAgICAgc2F2aS1kaGNwICAgICAgICAgICAgICAgICAgICAgTWFyY2ggMjAxMgoKCiAgIHRo
ZSBiaW5kaW5nIGFuY2hvciBiZXR3ZWVuIFNBVkkgRGV2aWNlIEIgYW5kIERIQ1AgUmVsYXksIGFu
ZCB0aGUKICAgYmluZGluZyBhbmNob3IgYmV0d2VlbiBTQVZJIERldmljZSBCIGFuZCBSb3V0ZXIg
QSwgc2hvdWxkIGJlCiAgIGNvbmZpZ3VyZWQgdG8gaGF2ZSB0aGlzIGF0dHJpYnV0ZS4KCiAgNi40
LiBTQVZJLVNBVkkgQXR0cmlidXRlCgogICBUaGlzIGF0dHJpYnV0ZSBpcyB1c2VkIG9uIGJpbmRp
bmcgYW5jaG9yIGZyb20gd2hpY2ggdGhlIGRhdGEgdHJhZmZpYwogICBpcyBub3QgdG8gYmUgY2hl
Y2tlZC4gQmluZGluZyB3aWxsIG5vdCBiZSBzZXQgdXAgb24gYmluZGluZyBhbmNob3IKICAgd2l0
aCB0aGlzIGF0dHJpYnV0ZS4gQWxsIGRhdGEgcGFja2V0cyB3aWxsIGJlIGFsbG93ZWQgZGlyZWN0
bHkuIEluCiAgIEZpZ3VyZSAxLCB0aGUgYmluZGluZyBhbmNob3IgYmV0d2VlbiBTQVZJIERldmlj
ZSBBIGFuZCBTQVZJIERldmljZSBCCiAgIHNob3VsZCBiZSBjb25maWd1cmVkIHdpdGggdGhpcyBh
dHRyaWJ1dGUuCgogICBUaHJvdWdoIGNvbmZpZ3VyaW5nIHRoaXMgYXR0cmlidXRlIG9uIGJpbmRp
bmcgYW5jaG9yIHRoYXQgam9pbnMgdHdvCiAgIG9yIG1vcmUgU0FWSSBkZXZpY2VzLCBTQVZJLVZh
bGlkYXRpb24gYW5kIFNBVkktU0FWSSBhdHRyaWJ1dGVzCiAgIGltcGxlbWVudCB0aGUgc2VjdXJp
dHkgcGVyaW1ldGVyIGNvbmNlcHQgaW4gW0ktRC5pZXRmLXNhdmktCiAgIGZyYW1ld29ya10uIFNp
bmNlIG5vIGJpbmRpbmcgZW50cnkgaXMgbmVlZGVkIG9uIHN1Y2ggYmluZGluZyBhbmNob3IsCiAg
IHRoZSByZXNvdXJjZSByZXF1aXJlbWVudCBjYW4gYmUgcmVkdWNlZCBncmVhdGx5LgoKICAgVGhv
dWdoIHRoZXJlIGlzIG5vIGZhY3R1YWwgZGlmZmVyZW5jZSBpbiBwYWNrZXQgcHJvY2VzcyBiZXR3
ZWVuIGEKICAgYmluZGluZyBhbmNob3Igd2l0aCBubyBhdHRyaWJ1dGUgYW5kIGEgYmluZGluZyBh
bmNob3Igb25seSB3aXRoIFNBVkktCiAgIFNBVkkgYXR0cmlidXRlLCB0aGVpciBjb25ub3RhdGlv
bnMgYXJlIGRpZmZlcmVudC4gU0FWSS1TQVZJIGF0dHJpYnV0ZQogICBpcyBjb25maWd1cmVkIG9u
IGJpbmRpbmcgYW5jaG9yIGJldHdlZW4gU0FWSSBkZXZpY2VzIG9uIHRoZSBzYW1lIGxpbmsKICAg
aW5zaWRlIHRoZSBwcm90ZWN0aW9uIHBlcmltZXRlci4gQnV0IG9ubHkgd2hlbiBhIGJpbmRpbmcg
YW5jaG9yIGlzIG9uCiAgIHRoZSBwcm90ZWN0aW9uIHBlcmltZXRlciBhbmQgY29ubmVjdGVkIHRv
IGFub3RoZXIgbGluaywgaXQgY2FuIGhhdmUKICAgbm8gYXR0cmlidXRlIGFmdGVyIGNvbmZpZ3Vy
YXRpb24uCgogICBUaGlzIGF0dHJpYnV0ZSBpcyBtdXR1YWxseSBleGNsdXNpdmUgd2l0aCBTQVZJ
LVZhbGlkYXRpb24uCgogIDYuNS4gU0FWSS1CaW5kUmVjb3ZlcnkgQXR0cmlidXRlCgogICBUaGlz
IGF0dHJpYnV0ZSBpcyB1c2VkIG9uIGJpbmRpbmcgYW5jaG9yIHRoYXQgcmVxdWlyZXMgZGF0YS10
cmlnZ2VyZWQKICAgYmluZGluZyByZWNvdmVyeSBkZXNjcmliZWQgaW4gc2VjdGlvbiA4LjEuIEl0
IGNhbiBiZSBjb25maWd1cmVkIG9uCiAgIGFueSBiaW5kaW5nIGFuY2hvciB3aXRoIFNBVkktVmFs
aWRhdGlvbiBhdHRyaWJ1dGUsIGVzcGVjaWFsbHksIHRoZQogICBiaW5kaW5nIGFuY2hvciBub3Qg
ZGlyZWN0bHkgYXR0YWNoZWQgYnkgY2xpZW50LiBJbiBGaWd1cmUgMSwgaXQgaXMKICAgc3VnZ2Vz
dGVkIHRvIGNvbmZpZ3VyZSB0aGlzIGF0dHJpYnV0ZSBvbiBiaW5kaW5nIGFuY2hvciBiZXR3ZWVu
IFNBVkkKICAgRGV2aWNlIEIgYW5kIE5vbiBTQVZJIERldmljZS4KCiAgIFRoaXMgYXR0cmlidXRl
IGlzIG11dHVhbGx5IGV4Y2x1c2l2ZSB3aXRoIFNBVkktU0FWSS4KCjcuIEJpbmRpbmcgU2V0IFVw
CgogICBUaGlzIHNlY3Rpb24gc3BlY2lmaWVzIHRoZSBwcm9jZWR1cmUgb2Ygc2V0dGluZyB1cCBi
aW5kaW5ncyBiYXNlZCBvbgogICBESENQIG1lc3NhZ2Ugc25vb3BpbmcuIFRoZSBiaW5kaW5nIHBy
b2NlZHVyZSBzcGVjaWZpZWQgaGVyZSBpcwogICBleGNsdXNpdmVseSBkZXNpZ25lZCBmb3IgYmlu
ZGluZyBhbmNob3Igd2l0aCBTQVZJLVZhbGlkYXRpb24KICAgYXR0cmlidXRlLgoKCgoKQmkgICAg
ICAgICAgICAgICAgICAgRXhwaXJlcyBTZXB0ZW1iZXIgMTYsIDIwMTIgICAgICAgICAgICAgICBb
UGFnZSA4XQoMCkludGVybmV0LURyYWZ0ICAgICAgICAgICAgICAgIHNhdmktZGhjcCAgICAgICAg
ICAgICAgICAgICAgIE1hcmNoIDIwMTIKCgogIDcuMS4gUmF0aW9uYWxlCgogICBUaGUgcmF0aW9u
YWxlIG9mIHRoaXMgbWVjaGFuaXNtIGlzIHRoYXQgaWYgYSBub2RlIGF0dGFjaGVkIHRvIGEKICAg
YmluZGluZyBhbmNob3IgaXMgbGVnaXRpbWF0ZSB0byB1c2UgYSBESENQIGFkZHJlc3MsIHRoZSBE
SENQCiAgIHByb2NlZHVyZSB3aGljaCBhc3NpZ25zIHRoZSBhZGRyZXNzIHRvIHRoZSBub2RlIG11
c3QgaGF2ZSBiZWVuCiAgIHBlcmZvcm1lZCBvbiB0aGUgc2FtZSBiaW5kaW5nIGFuY2hvci4gVGhp
cyBiYXNpcyBzdGFuZHMgd2hlbiB0aGUgbGluawogICBsYXllciByb3V0aW5nIGlzIHN0YWJsZS4g
SG93ZXZlciwgbGF5ZXItMiBtb2JpbGl0eSBhbmQgdW5zdGFibGUgbGluawogICBsYXllciByb3V0
aW5nIG1heSByZXN1bHQgaW4gdGhhdCBkYXRhIHBhY2tldCBpcyByZWNlaXZlZCBmcm9tIGEKICAg
ZGlmZmVyZW50IGJpbmRpbmcgYW5jaG9yLiBJbmZyZXF1ZW50IGxpbmsgbGF5ZXIgcGF0aCBjaGFu
Z2UgY2FuIGJlCiAgIGhhbmRsZWQgKGJ1dCBub3QgcGVyZmVjdGx5KSBieSB0aGUgbWVjaGFuaXNt
IGRlc2NyaWJlZCBpbiBzZWN0aW9uIDguCiAgIFNlY3Rpb24gMTMuMyBkaXNjdXNzZXMgdGhlIHNp
dHVhdGlvbiB0aGF0IGxpbmsgbGF5ZXIgcm91dGluZyBpcwogICBuYXR1cmVkbHkgdW5zdGFibGUu
IEEgc29sdXRpb24gZm9yIHRoaXMgaXNzdWUgaXMgb3V0c2lkZSB0aGUgc2NvcGUgb2YKICAgdGhp
cyBkb2N1bWVudC4KCiAgNy4yLiBCaW5kaW5nIFN0YXRlcyBEZXNjcmlwdGlvbgoKICAgVGhpcyBz
ZWN0aW9uIGRlc2NyaWJlcyB0aGUgYmluZGluZyBzdGF0ZXMgb2YgdGhpcyBtZWNoYW5pc20uCgog
ICBOT19CSU5EICAgICAgIFRoZSBzdGF0ZSBiZWZvcmUgYSBiaW5kaW5nIGhhcyBiZWVuIHNldCB1
cC4KCiAgIElOSVRfQklORCAgICAgICBBIERIQ1AgcmVxdWVzdCAob3IgYSBESENQdjYgQ29uZmly
bSwgb3IgYSBESENQdjYKICAgU29saWNpdGF0aW9uIHdpdGggUmFwaWQgQ29tbWl0IG9wdGlvbikg
aGFzIGJlZW4gcmVjZWl2ZWQgZnJvbSBob3N0LAogICBhbmQgaXQgbWF5IHRyaWdnZXIgYSBuZXcg
YmluZGluZy4KCiAgIEJPVU5EICAgICAgICAgVGhlIGFkZHJlc3MgaXMgYXV0aG9yaXplZCB0byB0
aGUgY2xpZW50LgoKICA3LjMuIEV2ZW50cwoKNy4zLjEuIFRpbWVyIEV4cGlyYXRpb24gRXZlbnQK
CiAgIEVWRV9FTlRSWV9FWFBJUkU6IFRoZSBsaWZldGltZSBvZiBhbiBlbnRyeSBleHBpcmVzCgo3
LjMuMi4gQ29udHJvbCBNZXNzYWdlIEFycml2aW5nIEV2ZW50cwoKICAgT25seSBpZiBhIGNvbnRy
b2wgbWVzc2FnZSBjYW4gcGFzcyB0aGUgY2hlY2sgaW4gc2VjdGlvbiA5LjIsIHRoZQogICBjb3Jy
ZXNwb25kaW5nIGV2ZW50IGlzIGEgdmFsaWQgZXZlbnQuCgogICBFVkVfREhDUF9SRVFVRVNUOiBB
IERIQ1AgUmVxdWVzdCBtZXNzYWdlIGlzIHJlY2VpdmVkIGZyb20gYSBiaW5kaW5nCiAgIGFuY2hv
ciB3aXRoIFNBVkktVmFsaWRhdGlvbiBhdHRyaWJ1dGUsIGFuZCB0aGUgYmluZGluZyBlbnRyeSBs
aW1pdAogICAoY2YuIHNlY3Rpb24gMTMuMikgb24gdGhlIGJpbmRpbmcgYW5jaG9yIGhhcyBub3Qg
YmVlbiByZWFjaGVkLgoKICAgRVZFX0RIQ1BfQ09ORklSTTogQSBESENQdjYgQ29uZmlybSBtZXNz
YWdlIGlzIHJlY2VpdmVkIGZyb20gYSBiaW5kaW5nCiAgIGFuY2hvciB3aXRoIFNBVkktVmFsaWRh
dGlvbiBhdHRyaWJ1dGUsIGFuZCB0aGUgYmluZGluZyBlbnRyeSBsaW1pdCBvbgogICB0aGUgYmlu
ZGluZyBhbmNob3IgaGFzIG5vdCBiZWVuIHJlYWNoZWQuCgogICBFVkVfREhDUF9PUFRJT05fUkM6
IEEgREhDUHY2IFNvbGljaXRhdGlvbiBtZXNzYWdlIHdpdGggUmFwaWQgQ29tbWl0CiAgIG9wdGlv
biBpcyByZWNlaXZlZCBmcm9tIGEgYmluZGluZyBhbmNob3Igd2l0aCBTQVZJLVZhbGlkYXRpb24K
CgpCaSAgICAgICAgICAgICAgICAgICBFeHBpcmVzIFNlcHRlbWJlciAxNiwgMjAxMiAgICAgICAg
ICAgICAgIFtQYWdlIDldCgwKSW50ZXJuZXQtRHJhZnQgICAgICAgICAgICAgICAgc2F2aS1kaGNw
ICAgICAgICAgICAgICAgICAgICAgTWFyY2ggMjAxMgoKCiAgIGF0dHJpYnV0ZSwgYW5kIHRoZSBi
aW5kaW5nIGVudHJ5IGxpbWl0IG9uIHRoZSBiaW5kaW5nIGFuY2hvciBoYXMgbm90CiAgIGJlZW4g
cmVhY2hlZC4KCiAgIEVWRV9ESENQX1JFUExZOiBBIERIQ1B2NCBBY2tub3dsZWRnZW1lbnQgb3Ig
REhDUHY2IFJlcGx5IG1lc3NhZ2UgaXMKICAgcmVjZWl2ZWQgZnJvbSBhIGJpbmRpbmcgYW5jaG9y
IHdpdGggU0FWSS1ESENQLVRydXN0IGF0dHJpYnV0ZSwgYW5kCiAgIHRoZSBtZXNzYWdlIHNob3Vs
ZCBiZSBmb3J3YXJkZWQgdG8gYSBiaW5kaW5nIGFuY2hvciB3aXRoIFNBVkktCiAgIFZhbGlkYXRp
b24gYXR0cmlidXRlLgoKICAgRVZFX0RIQ1BfUkVQTFlfTlVMTDogQSBESENQdjQgQWNrbm93bGVk
Z2VtZW50IG9yIERIQ1B2NiBSZXBseSBtZXNzYWdlCiAgIGlzIHJlY2VpdmVkIGZyb20gYSBiaW5k
aW5nIGFuY2hvciB3aXRoIFNBVkktREhDUC1UcnVzdCBhdHRyaWJ1dGUsIGFuZAogICB0aGVyZSBp
cyBubyBlbnRyeSBpbiBzdGF0ZSBJTklUX0JJTkQgY29udGFpbnMgdGhlIHNhbWUgVElEIGFzIHRo
ZQogICBtZXNzYWdlLgoKICAgRVZFX0RIQ1BfREVDTElORTogQSBESENQIERlY2xpbmUgbWVzc2Fn
ZSBpcyByZWNlaXZlZCBmcm9tIGEgYmluZGluZwogICBhbmNob3Igd2l0aCBTQVZJLVZhbGlkYXRp
b24gYXR0cmlidXRlLgoKICAgRVZFX0RIQ1BfUkVMRUFTRTogQSBESENQIFJlbGVhc2UgbWVzc2Fn
ZSBpcyByZWNlaXZlZCBmcm9tIGEgYmluZGluZwogICBhbmNob3Igd2l0aCBTQVZJLVZhbGlkYXRp
b24gYXR0cmlidXRlLgoKICAgRVZFX0xFQVNFUVVFUllfUkVQTFk6IEEgc3VjY2Vzc2Z1bCBESENQ
IExFQVNFUVVFUllfUkVQTFkgaXMgcmVjZWl2ZWQKICAgZnJvbSBhIGJpbmRpbmcgYW5jaG9yIHdp
dGggU0FWSS1ESENQLVRydXN0IGF0dHJpYnV0ZS4KCiAgNy40LiBQcm9jZXNzIG9mIERIQ1AgUGFj
a2V0IFNub29waW5nCgo3LjQuMS4gRnJvbSBOT19CSU5EIHRvIE90aGVyIFN0YXRlcwoKNy40LjEu
MS4gVHJpZ2dlciBFdmVudAoKICAgRVZFX0RIQ1BfUkVRVUVTVCwgRVZFX0RIQ1BfQ09ORklSTSwg
RVZFX0RIQ1BfT1BUSU9OX1JDLAogICBFVkVfREhDUF9SRVBMWV9OVUxMLgoKNy40LjEuMi4gRm9s
bG93aW5nIEFjdGlvbnMKCiAgIElmIHRoZSB0cmlnZ2VyaW5nIGV2ZW50IGlzIEVWRV9ESENQX1JF
UVVFU1QvRVZFX0RIQ1BfT1BUSU9OX1JDOgoKICAgICAgICAgICAgICAgVGhlIFNBVkkgZGV2aWNl
IE1VU1QgZm9yd2FyZCB0aGUgbWVzc2FnZS4KCiAgICAgVGhlIFNBVkkgZGV2aWNlIE1VU1QgZ2Vu
ZXJhdGUgYW4gZW50cnkgZm9yIHRoZSBiaW5kaW5nIGFuY2hvciBpbgogICAgIHRoZSBCaW5kaW5n
IFN0YXRlIFRhYmxlIChCU1QpIGFuZCBzZXQgdGhlIHN0YXRlIGZpZWxkIHRvIElOSVRfQklORC4K
ICAgICBUaGUgbGlmZXRpbWUgb2YgdGhpcyBlbnRyeSBNVVNUIHNldCB0byBiZSBNQVhfREhDUF9S
RVNQT05TRV9USU1FLgogICAgIFRoZSBUSUQgZmllbGQgb2YgdGhlIHJlcXVlc3QgcGFja2V0IE1V
U1QgYmUgcmVjb3JkZWQgaW4gdGhlIGVudHJ5LgoKCgoKCgoKCkJpICAgICAgICAgICAgICAgICAg
IEV4cGlyZXMgU2VwdGVtYmVyIDE2LCAyMDEyICAgICAgICAgICAgICBbUGFnZSAxMF0KDApJbnRl
cm5ldC1EcmFmdCAgICAgICAgICAgICAgICBzYXZpLWRoY3AgICAgICAgICAgICAgICAgICAgICBN
YXJjaCAyMDEyCgoKICAgKy0tLS0tLS0tLSstLS0tLS0tKy0tLS0tLS0tLSstLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLSstLS0tLS0tKwogICB8IEFuY2hvciAgfEFkZHJlc3N8IFN0YXRlICAgfCBMaWZl
dGltZSAgICAgICAgICAgICAgfFRJRCAgICB8CiAgICstLS0tLS0tLS0rLS0tLS0tLSstLS0tLS0t
LS0rLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0rLS0tLS0tLSsKICAgfCBBICAgICAgIHwgICAgICAg
fElOSVRfQklORHxNQVhfREhDUF9SRVNQT05TRV9USU1FIHwgVElEICAgfAogICArLS0tLS0tLS0t
Ky0tLS0tLS0rLS0tLS0tLS0tKy0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tKy0tLS0tLS0rCiAgICAg
IEZpZ3VyZSA0IEJpbmRpbmcgZW50cnkgaW4gQlNUIG9uIGNsaWVudCB0cmlnZ2VyZWQgaW5pdGlh
bGl6YXRpb24KCiAgICAgVGhlIFRJRCBpcyBzdG9yZWQgYmVjYXVzZSBpdCB3aWxsIGJlIHVzZWQg
aW4gYSBmdXR1cmUgc3RlcCAoY2YuCiAgICAgc2VjdGlvbiA3LjQuMi4yKSB0byBjb3JyZWN0bHkg
YXNzb2NpYXRlIHRoZSBhc3NpZ25lZCBhZGRyZXNzIHRvIHRoZQogICAgIGJpbmRpbmcgYW5jaG9y
LgoKICAgSWYgdGhlIHRyaWdnZXJpbmcgZXZlbnQgaXMgRVZFX0RIQ1BfQ09ORklSTToKCiAgICAg
QmVzaWRlcyBmb3J3YXJkaW5nIHRoZSBtZXNzYWdlIGFuZCBnZW5lcmF0aW5nIGNvcnJlc3BvbmRp
bmcgZW50cnksCiAgICAgdGhlIGFkZHJlc3MgdG8gYmUgY29uZmlybWVkIE1VU1QgYmUgcmVjb3Jk
ZWQgaW4gdGhlIGVudHJ5LiBCZWNhdXNlCiAgICAgbm8gbGVhc2UgdGltZSB3aWxsIGJlIGNvbnRh
aW5lZCBpbiB0aGUgUkVQTFkgZnJvbSBESENQIHNlcnZlciwgdGhlCiAgICAgU0FWSSBkZXZpY2Ug
TVVTVCBsb29rdXAgaW4gQlNUIHRvIGRldGVybWluZSB3aGV0aGVyIHRoZXJlIGlzIGFuCiAgICAg
ZW50cnkgd2l0aCB0aGUgc2FtZSBhZGRyZXNzLiBJZiB0aGVyZSBpcyBzdWNoIGFuIGVudHJ5LCBp
dCBjYW4gYmUgYQogICAgIGxvY2FsIG1vdmVtZW50IGFuZCB0aGUgbGlmZXRpbWUgY2FuIGJlIHJl
Y292ZXJlZCBmcm9tIHRoZSBlbnRyeS4gSWYKICAgICB0aGVyZSBpcyBub3QsIHRoZSBTQVZJIGRl
dmljZSBNVVNUIHNlbmQgYSBMRUFTRVFVRVJZIFtSRkM1MDA3XQogICAgIG1lc3NhZ2UgcXVlcnlp
bmcgYnkgSVAgYWRkcmVzcyB0byBBbGxfREhDUF9SZWxheV9BZ2VudHNfYW5kX1NlcnZlcnMKICAg
ICBtdWx0aWNhc3QgYWRkcmVzcyBbUkZDMzMxNV0gb3IgYSBjb25maWd1cmVkIHNlcnZlciBhZGRy
ZXNzLgoKICAgKy0tLS0tLS0tLSstLS0tLS0tLSstLS0tLS0tLS0rLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0rLS0tLS0tLSsKICAgfCBBbmNob3IgIHwgQWRkcmVzc3wgU3RhdGUgICB8IExpZmV0aW1l
ICAgICAgICAgICAgICB8VElEICAgIHwKICAgKy0tLS0tLS0tLSstLS0tLS0tLSstLS0tLS0tLS0r
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0rLS0tLS0tLSsKICAgfCBBICAgICAgIHwgQWRkciAgIHxJ
TklUX0JJTkR8TUFYX0RIQ1BfUkVTUE9OU0VfVElNRSB8IFRJRCAgIHwKICAgKy0tLS0tLS0tLSst
LS0tLS0tLSstLS0tLS0tLS0rLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0rLS0tLS0tLSsKICAgICBG
aWd1cmUgNSBCaW5kaW5nIGVudHJ5IGluIEJTVCBvbiBDb25maXJtIHRyaWdnZXJlZCBpbml0aWFs
aXphdGlvbgoKICAgSWYgdGhlIHRyaWdnZXJpbmcgZXZlbnQgaXMgRVZFX0RIQ1BfUkVQTFlfTlVM
TDoKCiAgICAgSWYgdGhlIGJpbmRpbmcgYW5jaG9yIGlzIG5vdCBsaW5rIGxheWVyIGFkZHJlc3Mg
YW5kIHRoZXJlIGlzIG5vdCBhCiAgICAgbWFwcGluZyB0YWJsZSBmcm9tIGxpbmsgbGF5ZXIgYWRk
cmVzcyB0byBiaW5kaW5nIGFuY2hvciwgdGhlCiAgICAgbWVzc2FnZSBTSE9VTEQgYmUgZGlzY2Fy
ZGVkLgoKICAgICBFbHNlOgoKICAgICBUaGUgU0FWSSBkZXZpY2UgTVVTVCBkZWxpdmVyIHRoZSBt
ZXNzYWdlIHRvIHRoZSBkZXN0aW5hdGlvbi4KCiAgICAgVGhlIFNBVkkgZGV2aWNlIE1VU1QgZ2Vu
ZXJhdGUgYXMgbWFueSBuZXcgZW50cmllcyBpbiBCU1QgYW5kIEZUIGFzCiAgICAgdGhlIG51bWJl
ciBvZiBJQUREUiBmb3VuZCBpbiB0aGUgbWVzc2FnZS4gSWYgdGhlIGJpbmRpbmcgYW5jaG9yCiAg
ICAgdHlwZSBpbnNpZGUgdGhlIEJTVCBpcyBub3QgbGluayBsYXllciBhZGRyZXNzLCB0aGUgYmlu
ZGluZyBhbmNob3IKICAgICBmb3IgYW4gZW50cnkgaXMgcmVjb3ZlcmVkIGZyb20gdGhlIG1hcHBp
bmcgdGFibGUgZnJvbSBsaW5rIGxheWVyCiAgICAgYWRkcmVzcyB0byBiaW5kaW5nIGFuY2hvciAo
Y2YuIHNlY3Rpb24gNS4zKSBiYXNlZCBvbiB0aGUKICAgICBkZXN0aW5hdGlvbiBsaW5rIGxheWVy
IGFkZHJlc3MgaW5zaWRlIHRoZSBESENQIG1lc3NhZ2UuCgoKCkJpICAgICAgICAgICAgICAgICAg
IEV4cGlyZXMgU2VwdGVtYmVyIDE2LCAyMDEyICAgICAgICAgICAgICBbUGFnZSAxMV0KDApJbnRl
cm5ldC1EcmFmdCAgICAgICAgICAgICAgICBzYXZpLWRoY3AgICAgICAgICAgICAgICAgICAgICBN
YXJjaCAyMDEyCgoKICAgICBUaGUgc3RhdGVzIG9mIHRoZSBjb3JyZXNwb25kaW5nIGVudHJpZXMg
YXJlIHNldCB0byBiZSBCT1VORC4gVGhlCiAgICAgbGlmZXRpbWUgb2YgdGhlIGVudHJpZXMgTVVT
VCBiZSBzZXQgdG8gYmUgdGhlIGxlYXNlIHRpbWUuCgogICAgIFRoZSBiaW5kaW5nIGVudHJ5IGxp
bWl0IGNhbiBiZSBleGNlZWRlZCB3aGVuIHNldHRpbmcgdXAgYmluZGluZ3MKICAgICBmb3IgYWxs
IGFkZHJlc3NlcyBpbiBhIFJFUExZIG1lc3NhZ2UuIElmIHRoZXJlIGlzIGVub3VnaCBiaW5kaW5n
CiAgICAgZW50cnkgcmVzb3VyY2VzLCBjb3JyZXNwb25kaW5nIG5ldyBlbnRyaWVzIE1VU1QgYmUg
Z2VuZXJhdGVkIGV2ZW4KICAgICB0aGUgYmluZGluZyBudW1iZXIgbGltaXQgaXMgZXhjZWVkZWQu
IEluIGNhc2UgdGhhdCB0aGVyZSBpcyBub3QKICAgICBlbm91Z2ggcmVzb3VyY2UgbGVmdCwgYXMg
bWFueSBhcyBwb3NzaWJsZSBlbnRyaWVzIFNIT1VMRCBiZSBzZXQgdXAuCgogICAgIElmIHRoZSBi
aW5kaW5nIGFuY2hvciBpcyBhIHN3aXRjaCBwb3J0LCB0aGVyZSBjYW4gYmUgdnVsbmVyYWJpbGl0
eQogICAgIGluIHRoaXMgcHJvY2VzcyB3aGljaCBpcyBkaXNjdXNzZWQgaW4gc2VjdGlvbiAxMy4x
LiBTaW1pbGFyIHByb2JsZW0KICAgICBjYW4gaGFwcGVuIHdpdGggb3RoZXIgYmluZGluZyBhbmNo
b3JzLgoKICAgKy0tLS0tLS0tLSstLS0tLS0tLS0tKy0tLS0tLS0rLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tKy0tLS0tLS0rCiAgIHwgQW5jaG9yICB8IEFkZHJlc3MgIHwgU3RhdGUgfCBMaWZldGlt
ZSAgICAgICAgICAgICAgIHxUSUQgICAgfAogICArLS0tLS0tLS0tKy0tLS0tLS0tLS0rLS0tLS0t
LSstLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0rLS0tLS0tLSsKICAgfCBBICAgICAgIHwgQWRkcjEg
ICAgfCBCT1VORCB8ICAgTGVhc2UgdGltZSAxICAgICAgICAgfFRJRCAgICB8CiAgICstLS0tLS0t
LS0rLS0tLS0tLS0tLSstLS0tLS0tKy0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLSstLS0tLS0tKwog
ICB8IEEgICAgICAgfCBBZGRyMiAgICB8IEJPVU5EIHwgICBMZWFzZSB0aW1lIDIgICAgICAgICB8
VElEICAgIHwKICAgKy0tLS0tLS0tLSstLS0tLS0tLS0tKy0tLS0tLS0rLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tKy0tLS0tLS0rCiAgICAgIEZpZ3VyZSA2IEJpbmRpbmcgZW50cnkgaW4gQlNUIG9u
IFJlcGx5IHRyaWdnZXJlZCBpbml0aWFsaXphdGlvbgoKICAgICAgICAgICAgICAgICAgICAgICAg
ICArLS0tLS0tLS0tKy0tLS0tLS0tLS0rCiAgICAgICAgICAgICAgICAgICAgICAgICAgfCBBbmNo
b3IgIHxBZGRyZXNzICAgfAogICAgICAgICAgICAgICAgICAgICAgICAgICstLS0tLS0tLS0rLS0t
LS0tLS0tLSsKICAgICAgICAgICAgICAgICAgICAgICAgICB8QSAgICAgICAgfEFkZHIxICAgICB8
CiAgICAgICAgICAgICAgICAgICAgICAgICAgKy0tLS0tLS0tLSstLS0tLS0tLS0tKwogICAgICAg
ICAgICAgICAgICAgICAgICAgIHxBICAgICAgICB8QWRkcjIgICAgIHwKICAgICAgICAgICAgICAg
ICAgICAgICAgICArLS0tLS0tLS0tKy0tLS0tLS0tLS0rCgogICAgICAgRmlndXJlIDcgQmluZGlu
ZyBlbnRyeSBpbiBGVCBvbiBSZXBseSB0cmlnZ2VyZWQgaW5pdGlhbGl6YXRpb24KCjcuNC4yLiBG
cm9tIElOSVRfQklORCB0byBPdGhlciBTdGF0ZXMKCjcuNC4yLjEuIFRyaWdnZXIgRXZlbnQKCiAg
IEVWRV9ESENQX1JFUExZLCBFVkVfRU5UUllfRVhQSVJFLCBFVkVfTEVBU0VRVUVSWV9SRVBMWS4K
CjcuNC4yLjIuIEZvbGxvd2luZyBBY3Rpb25zCgogICBJZiB0aGUgdHJpZ2dlciBldmVudCBpcyBF
VkVfREhDUF9SRVBMWToKCiAgICAgVGhlIFNBVkkgZGV2aWNlIE1VU1QgZGVsaXZlciB0aGUgbWVz
c2FnZSB0byB0aGUgZGVzdGluYXRpb24uCgogICAgICBJZiB0aGUgQWRkcmVzcyBmaWVsZCBpcyBu
dWxsLCB0aGUgbGVhc2UgdGltZSBpbiBSZXBseSBtZXNzYWdlIE1VU1QKICAgICAgYmUgcmVjb3Jk
ZWQgaW4gdGhlIGVudHJ5IHdpdGggbWF0Y2hlZCBUSUQuIFRoZSBzdGF0ZSBvZiB0aGUgZW50cnkK
ICAgICAgaXMgY2hhbmdlZCB0byBiZSBCT1VORC4gSWYgbW9yZSB0aGFuIG9uZSBJQUREUiBpcyBm
b3VuZCBpbiB0aGUKCgpCaSAgICAgICAgICAgICAgICAgICBFeHBpcmVzIFNlcHRlbWJlciAxNiwg
MjAxMiAgICAgICAgICAgICAgW1BhZ2UgMTJdCgwKSW50ZXJuZXQtRHJhZnQgICAgICAgICAgICAg
ICAgc2F2aS1kaGNwICAgICAgICAgICAgICAgICAgICAgTWFyY2ggMjAxMgoKCiAgICAgIG1lc3Nh
Z2UsIGlmIHRoZXJlIGlzIGVub3VnaCBiaW5kaW5nIGVudHJ5IHJlc291cmNlLCBjb3JyZXNwb25k
aW5nCiAgICAgIG5ldyBlbnRyaWVzIE1VU1QgYmUgZ2VuZXJhdGVkIGV2ZW4gdGhlIGJpbmRpbmcg
bnVtYmVyIGxpbWl0IGlzCiAgICAgIGV4Y2VlZGVkLiBJbiBjYXNlIHRoYXQgdGhlcmUgaXMgbm90
IGVub3VnaCByZXNvdXJjZSBsZWZ0LCBhcyBtYW55CiAgICAgIGFzIHBvc3NpYmxlIGVudHJpZXMg
U0hPVUxEIGJlIHNldCB1cC4KCiAgICAgIElmIHRoZSBBZGRyZXNzIGZpZWxkIGlzIG5vdCBudWxs
LCB0aGUgUmVwbHkgaXMgaW4gcmVzcG9uc2UgdG8gYQogICAgICBDb25maXJtIG1lc3NhZ2UuIElm
IHRoZSBSZXBseSBtZXNzYWdlIGlzIG9mIFN0YXR1cyBDb2RlIFN1Y2Nlc3MsCiAgICAgIGFuZCB0
aGVyZSBpcyBhbiBlbnRyeSB3aXRoIHRoZSBzYW1lIGFkZHJlc3MsIHNldCB0aGUgTGlmZXRpbWUg
dG8KICAgICAgYmUgdGhlIHJlbWFpbmluZyBMaWZldGltZSBvZiB0aGUgZXhpc3RpbmcgZW50cnks
IGFuZCByZW1vdmUgdGhlCiAgICAgIGV4aXN0aW5nIGVudHJ5LiBJZiB0aGVyZSBpcyBubyBlbnRy
eSB3aXRoIHRoZSBzYW1lIGFkZHJlc3MsIHNldAogICAgICB0aGUgTGlmZXRpbWUgb2YgY29ycmVz
cG9uZGluZyBlbnRyeSB0byBNQVhfTEVBU0VRVUVSWV9ERUxBWS4gVGhlCiAgICAgIHN0YXRlIG9m
IHRoZSBlbnRyeSBpcyBjaGFuZ2VkIHRvIGJlIEJPVU5ELgoKICAgKy0tLS0tLS0tLSstLS0tLS0t
LS0tKy0tLS0tLS0rLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tKy0tLS0tLS0rCiAgIHwgQW5jaG9y
ICB8IEFkZHJlc3MgIHwgU3RhdGUgfCBMaWZldGltZSAgICAgICAgICAgICAgIHxUSUQgICAgfAog
ICArLS0tLS0tLS0tKy0tLS0tLS0tLS0rLS0tLS0tLSstLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0r
LS0tLS0tLSsKICAgfCBBICAgICAgIHwgQWRkciAgICAgfCBCT1VORCB8ICBMZWFzZSB0aW1lICAg
ICAgICAgICAgfFRJRCAgICB8CiAgICstLS0tLS0tLS0rLS0tLS0tLS0tLSstLS0tLS0tKy0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLSstLS0tLS0tKwogICAgICAgICAgICAgICAgICAgICBGaWd1cmUg
OCBGcm9tIElOSVRfQklORCB0byBCT1VORAoKICAgICAgQSBjb3JyZXNwb25kaW5nIGVudHJ5IE1V
U1QgYWxzbyBiZSBnZW5lcmF0ZWQgaW4gRlQuCgogICBJZiB0aGUgdHJpZ2dlciBldmVudCBpcyBF
VkVfRU5UUllfRVhQSVJFOgoKICAgICAgVGhlIGVudHJ5IE1VU1QgYmUgZGVsZXRlZCBmcm9tIEJT
VC4KCiAgIElmIHRoZSB0cmlnZ2VyIGV2ZW50IGlzIEVWRV9MRUFTRVFVRVJZX1JFUExZOgoKICAg
ICBUaGUgTGlmZXRpbWUgZmllbGQgb2YgZW50cnkgd2l0aCBjb3JyZXNwb25kaW5nIElQIGFkZHJl
c3MgTVVTVCBiZQogICBzZXQgdG8gdGhlIGxlYXNlIHRpbWUgaW4gdGhlIExFQVNFUVVFUllfUkVQ
TFkuIFRoZSBzdGF0ZSBvZiB0aGUgZW50cnkKICAgaXMgY2hhbmdlZCB0byBCT1VORC4KCjcuNC4z
LiBGcm9tIEJPVU5EIHRvIE90aGVyIFN0YXRlcwoKNy40LjMuMS4gVHJpZ2dlciBFdmVudAoKICAg
RVZFX0VOVFJZX0VYUElSRSwgRVZFX0RIQ1BfUkVMRUFTRSwgRVZFX0RIQ1BfREVDTElORSwKICAg
RVZFX0RIQ1BfUkVQTFlfUkVORVcuCgo3LjQuMy4yLiBGb2xsb3dpbmcgQWN0aW9ucwoKICAgSWYg
dGhlIHRyaWdnZXIgZXZlbnQgaXMgRVZFX0VOVFJZX0VYUElSRToKCiAgICAgUmVtb3ZlIHRoZSBj
b3JyZXNwb25kaW5nIGVudHJ5IGluIEJTVCBhbmQgRlQuCgogICBJZiB0aGUgdHJpZ2dlciBldmVu
dCBpcyBFVkVfREhDUF9SRUxFQVNFIG9yIEVWRV9ESENQX0RFQ0xJTkU6CgoKCkJpICAgICAgICAg
ICAgICAgICAgIEV4cGlyZXMgU2VwdGVtYmVyIDE2LCAyMDEyICAgICAgICAgICAgICBbUGFnZSAx
M10KDApJbnRlcm5ldC1EcmFmdCAgICAgICAgICAgICAgICBzYXZpLWRoY3AgICAgICAgICAgICAg
ICAgICAgICBNYXJjaCAyMDEyCgoKICAgICBSZW1vdmUgdGhlIGNvcnJlc3BvbmRpbmcgZW50cnkg
aW4gQlNUIGFuZCBGVC4gVGhlIFJlbGVhc2Ugb3IKICAgICBEZWNsaW5lIG1lc3NhZ2UgTVVTVCBi
ZSBmb3J3YXJkZWQuCgogICBJZiB0aGUgdHJpZ2dlciBldmVudCBpcyBFVkVfREhDUF9SRVBMWV9S
RU5FVzoKCiAgICAgU2V0IHRoZSBsaWZldGltZSBvZiB0aGUgYWRkcmVzcyB0byBiZSB0aGUgbmV3
IGxlYXNlIHRpbWUuCgogIDcuNS4gU3RhdGUgTWFjaGluZSBvZiBESENQIFNub29waW5nCgogICBU
aGUgbWFpbiBzdGF0ZSB0cmFuc2l0cyBhcmUgbGlzdGVkIGFzIGZvbGxvd3MuCgogICBTdGF0ZSAg
ICAgICAgRXZlbnQgICAgICAgICAgICBBY3Rpb24gICAgICAgICAgICAgICAgICAgICAgIE5leHQg
U3RhdGUKCiAgIE5PX0JJTkQgICAgICAgUkVRL1JDICAgIEdlbmVyYXRlIGVudHJ5ICAgICAgICAg
ICAgICAgICAgICAgIElOSVRfQklORAoKICAgTk9fQklORCAgICAgICBDRk0gICAgICAgR2VuZXJh
dGUgZW50cnkgYW5kIHNlbmQgTGVhc2VxdWVyeSAgSU5JVF9CSU5ECgogICAqTk9fQklORCAgICAg
IFJQTF9OVUxMICBHZW5lcmF0ZSBlbnRyeSB3aXRoIGxlYXNlICAgICAgICAgICAgICAgQk9VTkQK
CiAgIElOSVRfQklORCAgICAgUlBMICAgICAgIFJlY29yZCBsZWFzZSB0aW1lL3NldCBMUV9ETFkg
ICAgICAgICAgICBCT1VORAoKICAgSU5JVF9CSU5EICAgICBUaW1lb3V0ICAgUmVtb3ZlIGVudHJ5
ICAgICAgICAgICAgICAgICAgICAgICAgICBOT19CSU5ECgogICBJTklUX0JJTkQgICAgIExRUiAg
ICAgICBSZWNvcmQgbGVhc2UgdGltZSAgICAgICAgICAgICAgICAgICAgICAgQk9VTkQKCiAgIEJP
VU5EICAgICAgICAgUkxTL0RDTCAgIFJlbW92ZSBlbnRyeSAgICAgICAgICAgICAgICAgICAgICAg
ICAgTk9fQklORAoKICAgQk9VTkQgICAgICAgICBUaW1lb3V0ICAgUmVtb3ZlIGVudHJ5ICAgICAg
ICAgICAgICAgICAgICAgICAgICBOT19CSU5ECgogICBCT1VORCAgICAgICAgIFJOVyAgICAgICBT
ZXQgbmV3IGxpZmV0aW1lICAgICAgICAgICAgICAgICAgICAgICAgQk9VTkQKCiAgICo6IG9wdGlv
bmFsIGJ1dCBOT1QgUkVDT01NRU5ERUQuCgogICBSRVE6IEVWRV9ESENQX1JFUVVFU1QKCiAgIENG
TTogRVZFX0RIQ1BfQ09ORklSTQoKICAgUkM6ICBFVkVfREhDUF9PUFRJT05fUkMKCiAgIFJQTDog
RVZFX0RIQ1AgUkVQTFkKCiAgIFJQTF9OVUxMOiBFVkVfREhDUCBSRVBMWV9OVUxMCgogICBEQ0w6
IERIQ1AgREVDTElORQoKICAgUkxTOiBESENQIFJFTEVBU0UKCgoKQmkgICAgICAgICAgICAgICAg
ICAgRXhwaXJlcyBTZXB0ZW1iZXIgMTYsIDIwMTIgICAgICAgICAgICAgIFtQYWdlIDE0XQoMCklu
dGVybmV0LURyYWZ0ICAgICAgICAgICAgICAgIHNhdmktZGhjcCAgICAgICAgICAgICAgICAgICAg
IE1hcmNoIDIwMTIKCgogICBSTlc6IEVWRV9ESENQX1JQTF9SRU5FVwoKICAgTFFSOiBFVkVfTEVB
U0VRVUVSWV9SRVBMWQoKICAgVGltZW91dDogRVZFX0VOVFJZX0VYUElSRQoKICBMUV9ETFk6IE1B
WF9MRUFTRVFVRVJZX0RFTEFZCgo4LiBTdXBwbGVtZW50YWwgQmluZGluZyBQcm9jZXNzCgogICBT
dXBwbGVtZW50YWwgYmluZGluZyBwcm9jZXNzIGlzIGRlc2lnbmVkIHRvIGNvdmVyIHNjZW5hcmlv
cyB3aGVyZSBhCiAgIHBhY2tldCBpcyBzZW50IGJ5IG5vZGUgYnV0IG5vIHByZXZpb3VzIERIQ1Ag
ZXhjaGFuZ2VzIGhhdmUgb2NjdXJyZWQKICAgdG8gdXBkYXRlIGNvcnJlY3RseSB0aGUgU0FWSSBk
ZXZpY2UncyBCU1QuIEEgdHlwaWNhbCBzaXR1YXRpb24gaXMKICAgd2hlbiB0aGUgbGluayB0b3Bv
bG9neSBjaGFuZ2VzIGFmdGVyIHRoZSBiaW5kaW5nIGhhcyBiZWVuIHNldCB1cCwgYW5kCiAgIHRo
ZW4gdGhlIG5vZGUgd2lsbCBzZW5kIHBhY2tldCB0aHJvdWdoIGEgZGlmZmVyZW50IHBvcnQgdGhh
biB0aGUKICAgYm91bmQgcG9ydC4gQW5vdGhlciBzY2VuYXJpbyBpcyB0aGF0IGEgbm9kZSBtb3Zl
cyBvbiB0aGUgbG9jYWwgbGluawogICB3aXRob3V0IHJlLWNvbmZpZ3VyYXRpb24gcHJvY2Vzcy4K
CiAgIFN1cHBsZW1lbnRhbCBiaW5kaW5nIHByb2Nlc3MgaXMgZGVzaWduZWQgdG8gYXZvaWQgYmxv
Y2tpbmcKICAgcGVybWFuZW50bHkgbGVnaXRpbWF0ZSB0cmFmZmljLiBJdCBpcyBub3Qgc3VwcG9z
ZWQgdG8gc2V0IHVwIGEKICAgYmluZGluZyB3aGVuZXZlciBhIGRhdGEgcGFja2V0IHdpdGggdW5i
b3VuZCBzb3VyY2UgYWRkcmVzcyBpcwogICByZWNlaXZlZC4gR2VuZXJhbGx5LCBsb25nZXIgdGlt
ZSBhbmQgbW9yZSBwYWNrZXRzIGFyZSBuZWVkZWQgdG8KICAgdHJpZ2dlciBzdXBwbGVtZW50YWwg
YmluZGluZyBwcm9jZXNzZXMuCgogICBCaW5kaW5nIFJlY292ZXJ5IFByb2Nlc3MgaXMgYSBjb25k
aXRpb25hbCBTSE9VTEQuIElmIHRoZQogICBpbXBsZW1lbnRhdGlvbiBpcyBrbm93biB0byBiZSBk
aXJlY3RseSBhdHRhY2hlZCB0byBob3N0LCB0aGlzCiAgIGZ1bmN0aW9uIE1BWSBOT1QgYmUgaW1w
bGVtZW50ZWQuIElmIGFuIGltcGxlbWVudGF0aW9uIGlzIGRpcmVjdGx5CiAgIGF0dGFjaGVkIHRv
IGhvc3QsIGNoYW5nZSBpbiBsaW5rIHRvcG9sb2d5IHdpbGwgbm90IGFmZmVjdCB0aGUKICAgYmlu
ZGluZ3MsIGFuZCBob3N0IHdpbGwgYWx3YXlzIHN0YXJ0IHJlLWNvbmZpZ3VyYXRpb24gcHJvY2Vz
cyBhZnRlcgogICBpbnRlcmZhY2UgaXMgcmUtY29ubmVjdGVkLiBJbiBjYXNlIG9mIGxpbmsgZmxh
cCwgYmluZGluZyB3aWxsIGJlIGtlcHQKICAgZm9yIGEgcGVyaW9kIGFuZCBubyByZS1jb25maWd1
cmF0aW9uIHByb2Nlc3Mgb24gaG9zdCBpcyByZXF1aXJlZCwgYXMKICAgc3BlY2lmaWVkIGluIHNl
Y3Rpb24gMTEuIFRodXMsIHRoZXJlIGlzIG5vIG5lZWQgdG8gdXNlIGFkZGl0aW9uYWwKICAgcHJv
Y2VzcyB0byByZWNvdmVyeSBiaW5kaW5ncy4gSWYgdGhlIG1lY2hhbmlzbSBpcyBub3QgaW1wbGVt
ZW50ZWQgYW5kCiAgIG1hbmFnZWQgaG9zdHMgYXJlIG5vdCBkaXJlY3RseSBhdHRhY2hlZCwgcGVy
bWFuZW50IGxlZ2l0aW1hdGUgdHJhZmZpYwogICBibG9ja2luZyBjYW4gaGFwcGVuIHVudGlsIHRo
ZSBub2RlIGlzIHJlY29uZmlndXJlZC4KCiAgIFRoZSBzZWN1cml0eSBpc3N1ZXMgYWJvdXQgdGhp
cyBwcm9jZXNzIGlzIGRpc2N1c3NlZCBpcyBzZWN0aW9uIDEzLjUuCgogIDguMS4gQmluZGluZyBT
dGF0ZXMgRGVzY3JpcHRpb24KCiAgIEFkZGl0aW9uYWwgc3RhdGVzIHVzZWQgaW4gdGhpcyBwcm9j
ZXNzIGFyZSBkZXNjcmliZWQgaGVyZToKCiAgIERFVEVDVElPTiAgICAgIFRoZSBhZGRyZXNzIGlz
IHVuZGVyIGxvY2FsIGRldGVjdGlvbi4KCiAgIFJFQ09WRVJZICAgICAgIFRoZSBhZGRyZXNzIGlz
IGluIGJpbmRpbmcgcmVjb3ZlcnkgcHJvY2Vzcy4KCgoKCkJpICAgICAgICAgICAgICAgICAgIEV4
cGlyZXMgU2VwdGVtYmVyIDE2LCAyMDEyICAgICAgICAgICAgICBbUGFnZSAxNV0KDApJbnRlcm5l
dC1EcmFmdCAgICAgICAgICAgICAgICBzYXZpLWRoY3AgICAgICAgICAgICAgICAgICAgICBNYXJj
aCAyMDEyCgoKICA4LjIuIEV2ZW50cwoKICAgQWRkaXRpb25hbCBldmVudHMgaW4gdGhpcyBwcm9j
ZXNzIGFyZSBkZXNjcmliZWQgaGVyZToKCiAgIEVWRV9CUl9VTk1BVENIICAgICAgICAgQSBkYXRh
IHBhY2tldCB3aXRob3V0IG1hdGNoZWQgYmluZGluZyBpbiBGVAogICBpcyByZWNlaXZlZCBmcm9t
IGEgYmluZGluZyBhbmNob3Igd2l0aCBTQVZJLUJpbmRSZWNvdmVyeSBhdHRyaWJ1dGUsCiAgIGFu
ZCB0aGUgYmluZGluZyBlbnRyeSBsaW1pdCBvbiB0aGUgYmluZGluZyBhbmNob3IgaGFzIG5vdCBi
ZWVuCiAgIHJlYWNoZWQuCgogICBFVkVfQlJfQ09ORkxJQ1QgICAgICAgIFJlc3BvbnNlIGFnYWlu
c3QgYW4gYWRkcmVzcyBpbiBERVRFQ1RJT04KICAgc3RhdGUgaXMgcmVjZWl2ZWQuCgogICBFVkVf
QlJfTEVBU0VRVUVSWSAgICAgICBJUHY0OiBhIERIQ1BMRUFTRUFDVElWRSBtZXNzYWdlIHdpdGgg
SVAKICAgQWRkcmVzcyBMZWFzZSBUaW1lIG9wdGlvbiBpcyByZWNlaXZlZCBmcm9tIGEgYmluZGlu
ZyBhbmNob3Igd2l0aAogICBTQVZJLURIQ1AtVHJ1c3QgYXR0cmlidXRlOyBJUHY2OiBhIHN1Y2Nl
c3NmdWwgTEVBU0VRVUVSWS1SRVBMWSBpcwogICByZWNlaXZlZC4KCiAgOC4zLiBCaW5kaW5nIFJl
Y292ZXJ5IFByb2Nlc3MKCjguMy4xLiBGcm9tIE5PX0JJTkQgdG8gT3RoZXIgU3RhdGVzCgo4LjMu
MS4xLiBUcmlnZ2VyIEV2ZW50CgogICBFVkVfQlJfVU5NQVRDSAoKOC4zLjEuMi4gRm9sbG93aW5n
IEFjdGlvbgoKICAgSWYgdGhlcmUgaXMgYSBjb3JyZXNwb25kaW5nIGJpbmRpbmcgaW4gQlNUIG9u
IHRoZSBiaW5kaW5nIGFuY2hvciB3aXRoCiAgIHRoZSBzYW1lIHNvdXJjZSBhZGRyZXNzLCB0aGUg
cGFja2V0IFNIT1VMRCBiZSBkcm9wcGVkLCBhbmQgZm9sbG93aW5nCiAgIGFjdGlvbnMgd2lsbCBu
b3QgYmUgdGFrZW4uCgogICBDaGVjayBpZiB0aGUgdGltZSBzaW5jZSB0aGUgbGFzdCBFVkVfQlJf
VU5NQVRDSCBvbiB0aGUgc2FtZSBiaW5kaW5nCiAgIGFuY2hvciBpcyBsYXJnZXIgdGhhbiBCSU5E
X1JFQ09WRVJZX0lOVEVSVkFMLiBGb2xsb3dpbmcgYWN0aW9ucyB3aWxsCiAgIG5vdCBiZSB0YWtl
biBpZiB0aGUgbGFzdCBFVkVfQlJfVU5NQVRDSCBvbiB0aGUgc2FtZSBiaW5kaW5nIGFuY2hvciBp
bgogICB0aGUgbGFzdCBCSU5EX1JFQ09WRVJZX0lOVEVSVkFMLgoKICAgQ3JlYXRlIGEgbmV3IGVu
dHJ5IGluIHRoZSBCU1QuIFNldCB0aGUgQmluZGluZyBBbmNob3IgZmllbGQgdG8gdGhlCiAgIGNv
cnJlc3BvbmRpbmcgYmluZGluZyBhbmNob3IuIFNldCB0aGUgQWRkcmVzcyBmaWVsZCB0byBiZSBz
b3VyY2UKICAgYWRkcmVzcyBvZiB0aGUgcGFja2V0LiBTZXQgdGhlIHN0YXRlIGZpZWxkIHRvIERF
VEVDVElPTi4gVGhlIGxpZmV0aW1lCiAgIG9mIHRoaXMgZW50cnkgTVVTVCBzZXQgdG8gREFEX1RJ
TUVPVVQuCgogICBDaGVjayBpZiB0aGUgYWRkcmVzcyBoYXMgYSBsb2NhbCBjb25mbGljdCAoaXQg
dmlvbGF0ZXMgYW4gYWRkcmVzcwogICBiZWluZyB1c2VkIGJ5IGFub3RoZXIgbm9kZSkgdGhyb3Vn
aDoKCiAgICAgICBJUHY0IGFkZHJlc3M6IHBlcmZvcm1pbmcgQWRkcmVzcyBSZXNvbHV0aW9uIFBy
b3RvY29sIChBUlApCiAgICAgICBbUkZDODI2XSBvciBBZGRyZXNzIENvbmZsaWN0IERldGVjdGlv
biBbUkZDNTIyN10gdHdpY2Ugb24gdGhlCiAgICAgICBhZGRyZXNzOwoKCkJpICAgICAgICAgICAg
ICAgICAgIEV4cGlyZXMgU2VwdGVtYmVyIDE2LCAyMDEyICAgICAgICAgICAgICBbUGFnZSAxNl0K
DApJbnRlcm5ldC1EcmFmdCAgICAgICAgICAgICAgICBzYXZpLWRoY3AgICAgICAgICAgICAgICAg
ICAgICBNYXJjaCAyMDEyCgoKICAgICAgIElQdjYgYWRkcmVzczogcGVyZm9ybWluZyBEdXBsaWNh
dGUgQWRkcmVzcyBEZXRlY3Rpb24gKERBRCkKICAgICAgIFtSRkM0ODYyXSB0d2ljZSBvbiB0aGUg
YWRkcmVzcy4KCiAgIFRoZSBwYWNrZXQgU0hPVUxEIGJlIGRpc2NhcmRlZC4KCjguMy4yLiBGcm9t
IERFVEVDVElPTiB0byBPdGhlciBTdGF0ZXMKCjguMy4yLjEuIFRyaWdnZXIgRXZlbnQKCiAgIEVW
RV9FTlRSWV9FWFBJUkUsIEVWRV9CUl9DT05GTElDVAoKOC4zLjIuMi4gRm9sbG93aW5nIEFjdGlv
bgoKICAgSWYgdGhlIHRyaWdnZXIgZXZlbnQgaXMgRVZFX0VOVFJZX0VYUElSRToKCiAgICAgSVB2
NCBhZGRyZXNzOgoKICAgICAgICAgU2VuZCBhIERIQ1BMRUFTRVFVRVJZIFtSRkM0Mzg4XSBtZXNz
YWdlIHF1ZXJ5aW5nIGJ5IElQIGFkZHJlc3MKICAgICAgICAgdG8gYWxsIERIQ1B2NCBzZXJ2ZXJz
IHdpdGggSVAgQWRkcmVzcyBMZWFzZSBUaW1lIG9wdGlvbiAob3B0aW9uCiAgICAgICAgIDUxKS4g
VGhlIHNlcnZlciBhZGRyZXNzZXMgY2FuIGJlIGZvdW5kIHRocm91Z2ggREhDUHY0IERpc2NvdmVy
eQogICAgICAgICBvciBmcm9tIGNvbmZpZ3VyYXRpb24uCgogICAgICAgICBDaGFuZ2UgdGhlIHN0
YXRlIG9mIHRoZSBjb3JyZXNwb25kaW5nIGVudHJ5IHRvIFJFQ09WRVJZLiBDaGFuZ2UKICAgICAg
ICAgdGhlIGxpZmV0aW1lIG9mIHRoZSBlbnRyeSB0byBiZSBNQVhfTEVBU0VRVUVSWV9ERUxBWS4K
CiAgICAgSVB2NiBhZGRyZXNzOgoKICAgICAgICAgU2VuZCBhIExFQVNFUVVFUlkgW1JGQzUwMDdd
IG1lc3NhZ2UgcXVlcnlpbmcgYnkgSVAgYWRkcmVzcyB0bwogICAgICAgICBBbGxfREhDUF9SZWxh
eV9BZ2VudHNfYW5kX1NlcnZlcnMgbXVsdGljYXN0IGFkZHJlc3Mgb3IgYQogICAgICAgICBjb25m
aWd1cmVkIHNlcnZlciBhZGRyZXNzLgoKICAgICAgICAgQ2hhbmdlIHRoZSBzdGF0ZSBvZiB0aGUg
Y29ycmVzcG9uZGluZyBlbnRyeSB0byBSRUNPVkVSWS4gQ2hhbmdlCiAgICAgICAgIHRoZSBsaWZl
dGltZSBvZiB0aGUgZW50cnkgdG8gYmUgTUFYX0xFQVNFUVVFUllfREVMQVkuCgogICAgIEluIGNh
c2UgdGhhdCBTQVZJIGRldmljZSBpcyBwdXJlIGxheWVyLTIgZGV2aWNlIHdpdGhvdXQgSVAgYWRk
cmVzcywKICAgICBpdCBpcyBpbXBvc3NpYmxlIHRvIHBlcmZvcm0gREhDUCBMRUFTRVFVRVJZLiBC
ZXNpZGVzLCB0aGlzIHByb2Nlc3MKICAgICBtYXkgZmFpbCBpZiBhbnkgREhDUCBzZXJ2ZXIgZG9l
c24ndCBzdXBwb3J0IERIQ1AgTEVBU0VRVUVSWS4KCiAgIElmIHRoZSB0cmlnZ2VyIGV2ZW50IGlz
IEVWRV9CUl9DT05GTElDVDoKCiAgICAgUmVtb3ZlIHRoZSBlbnRyeS4KCjguMy4zLiBGcm9tIFJF
Q09WRVJZIHRvIE90aGVyIFN0YXRlcwoKOC4zLjMuMS4gVHJpZ2dlciBFdmVudAoKICAgRVZFX0VO
VFJZX0VYUElSRSwgRVZFX0JSX0xFQVNFUVVFUlkKCgpCaSAgICAgICAgICAgICAgICAgICBFeHBp
cmVzIFNlcHRlbWJlciAxNiwgMjAxMiAgICAgICAgICAgICAgW1BhZ2UgMTddCgwKSW50ZXJuZXQt
RHJhZnQgICAgICAgICAgICAgICAgc2F2aS1kaGNwICAgICAgICAgICAgICAgICAgICAgTWFyY2gg
MjAxMgoKCjguMy4zLjIuIEZvbGxvd2luZyBBY3Rpb24KCiAgIElmIHRoZSB0cmlnZ2VyIGV2ZW50
IGlzIEVWRV9CUl9MRUFTRVFVRVJZCgogICAgIElQdjQgYWRkcmVzczoKCiAgICAgICAgIENoYW5n
ZSB0aGUgc3RhdGUgb2YgdGhlIGNvcnJlc3BvbmQgYmluZGluZyB0byBCT1VORC4gU2V0IGxpZmUK
ICAgICAgICAgdGltZSB0byB0aGUgdmFsdWUgZW5jb2RlZCBpbiBJUCBBZGRyZXNzIExlYXNlIFRp
bWUgb3B0aW9uIG9mCiAgICAgICAgIHRoZSBESENQTEVBU0VBQ1RJVkUgbWVzc2FnZS4gQSBjb3Jy
ZXNwb25kaW5nIGVudHJ5IE1VU1QgYWxzbyBiZQogICAgICAgICBnZW5lcmF0ZWQgaW4gRlQuCgog
ICAgIElQdjYgYWRkcmVzczoKCiAgICAgICAgIENoYW5nZSB0aGUgc3RhdGUgb2YgdGhlIGNvcnJl
c3BvbmQgYmluZGluZyB0byBCT1VORC4gU2V0IHRoZQogICAgICAgICBsaWZldGltZSB0byB0aGUg
dmFsaWQgbGlmZXRpbWUgZXh0cmFjdGVkIGZyb20KICAgICAgICAgT1BUSU9OX0NMSUVOVF9EQVRB
IG9wdGlvbiBpbiB0aGUgTEVBU0VRVUVSWS1SRVBMWSBtZXNzYWdlLiBBCiAgICAgICAgIGNvcnJl
c3BvbmRpbmcgZW50cnkgTVVTVCBhbHNvIGJlIGdlbmVyYXRlZCBpbiBGVC4KCiAgICAgICAgIElm
IG11bHRpcGxlIGFkZHJlc3NlcyBhcmUgc3BlY2lmaWVkIGluIHRoZSBMRUFTRVFVRVJZLVJFUExZ
CiAgICAgICAgIG1lc3NhZ2UsIG5ldyBlbnRyaWVzIE1VU1QgYWxzbyBiZSBjcmVhdGVkIGNvcnJl
c3BvbmRpbmdseSBvbgogICAgICAgICB0aGUgc2FtZSBiaW5kaW5nIGFuY2hvci4KCiAgIElmIHRo
ZSB0cmlnZ2VyIGV2ZW50IGlzIEVWRV9FTlRSWV9FWFBJUkUKCiAgICAgUmVtb3ZlIHRoZSBjb3Jy
ZXNwb25kaW5nIGVudHJ5LgoKOS4gRmlsdGVyaW5nIFNwZWNpZmljYXRpb24KCiAgIFRoaXMgc2Vj
dGlvbiBzcGVjaWZpZXMgaG93IHRvIHVzZSBiaW5kaW5ncyB0byBmaWx0ZXIgcGFja2V0cy4KCiAg
IEZpbHRlcmluZyBwb2xpY2llcyBhcmUgZGlmZmVyZW50IGZvciBkYXRhIHBhY2tldCBhbmQgY29u
dHJvbCBwYWNrZXQuCiAgIERIQ1AgYW5kIE5EUCAoTmVpZ2hib3IgRGlzY292ZXJ5IFByb3RvY29s
KSBbUkZDNDg2MV0gbWVzc2FnZXMgdGhhdAogICBtYXkgY2F1c2Ugc3RhdGUgdHJhbnNpdCBhcmUg
Y2xhc3NpZmllZCBpbnRvIGNvbnRyb2wgcGFja2V0LiBOZWlnaGJvcgogICBBZHZlcnRpc2VtZW50
IChOQSkgYW5kIEFSUCBSZXNwb25zZSBhcmUgYWxzbyBpbmNsdWRlZCBpbiBjb250cm9sCiAgIHBh
Y2tldCwgYmVjYXVzZSB0aGUgVGFyZ2V0IEFkZHJlc3Mgb2YgTkEgYW5kIEFSUCBSZXNwb25zZSBz
aG91bGQgYmUKICAgY2hlY2tlZCB0byBwcmV2ZW50IHNwb29maW5nLiBBbGwgb3RoZXIgcGFja2V0
cyBhcmUgY29uc2lkZXJlZCB0byBiZQogICBkYXRhIHBhY2tldHMuCgogIDkuMS4gRGF0YSBQYWNr
ZXQgRmlsdGVyaW5nCgogICBEYXRhIHBhY2tldHMgd2l0aCBhIGJpbmRpbmcgYW5jaG9yIHdoaWNo
IGhhcyBhdHRyaWJ1dGUgU0FWSS0KICAgVmFsaWRhdGlvbiBNVVNUIGJlIGNoZWNrZWQuCgogICBQ
YWNrZXQgd2hvc2Ugc291cmNlIElQIGFkZHJlc3MgaXMgbGluay1sb2NhbCBhZGRyZXNzIFNIT1VM
RCBiZQogICBmb3J3YXJkZWQuCgoKCgpCaSAgICAgICAgICAgICAgICAgICBFeHBpcmVzIFNlcHRl
bWJlciAxNiwgMjAxMiAgICAgICAgICAgICAgW1BhZ2UgMThdCgwKSW50ZXJuZXQtRHJhZnQgICAg
ICAgICAgICAgICAgc2F2aS1kaGNwICAgICAgICAgICAgICAgICAgICAgTWFyY2ggMjAxMgoKCiAg
IElmIHRoZSBzb3VyY2UgSVAgYWRkcmVzcyBvZiBhIHBhY2tldCBpcyBub3QgYSBsaW5rLWxvY2Fs
IGFkZHJlc3MsIGJ1dAogICB0aGUgYWRkcmVzcyBpcyBub3QgYm91bmQgd2l0aCB0aGUgY29ycmVz
cG9uZGluZyBiaW5kaW5nIGFuY2hvciwgdGhpcwogICBwYWNrZXQgTVVTVCBiZSBkaXNjYXJkZWQu
CgogICBUaGUgU0FWSSBkZXZpY2UgU0hPVUxEIHJlY29yZCBhbnkgdmlvbGF0aW9uLgoKICA5LjIu
IENvbnRyb2wgUGFja2V0IEZpbHRlcmluZwoKICAgRm9yIGJpbmRpbmcgYW5jaG9ycyB3aXRoIFNB
VkktVmFsaWRhdGlvbiBhdHRyaWJ1dGU6CgogICAgIERpc2NhcmQgREhDUHY0IFJFUVVFU1QgbWVz
c2FnZSB3aG9zZSBzb3VyY2UgSVAgYWRkcmVzcyBpcyBuZWl0aGVyCiAgICAgYWxsIHplcm9zIG5v
ciBhIGJvdW5kIGFkZHJlc3MgaW4gRlQuCgogICAgIERpc2NhcmQgREhDUHY2IFJlcXVlc3QgbWVz
c2FnZSB3aG9zZSBzb3VyY2UgaXMgbmVpdGhlciBsaW5rLWxvY2FsCiAgICAgYWRkcmVzcyBub3Ig
Ym91bmQgd2l0aCB0aGUgY29ycmVzcG9uZGluZyBiaW5kaW5nIGFuY2hvciBpbiBGVC4KCiAgICAg
RGlzY2FyZCBORFAgbWVzc2FnZXMgd2hvc2Ugc291cmNlIGFkZHJlc3MgaXMgbmVpdGhlciBsaW5r
LWxvY2FsCiAgICAgYWRkcmVzcyBub3IgYm91bmQgd2l0aCB0aGUgY29ycmVzcG9uZGluZyBiaW5k
aW5nIGFuY2hvci4gSW4KICAgICBhZGRpdGlvbiwgZGlzY2FyZCBOQSBtZXNzYWdlIHdob3NlIHRh
cmdldCBhZGRyZXNzIGlzIG5laXRoZXIgbGluay0KICAgICBsb2NhbCBhZGRyZXNzIG5vciBib3Vu
ZCB3aXRoIHRoZSBjb3JyZXNwb25kaW5nIGJpbmRpbmcgYW5jaG9yLgoKICAgICBEaXNjYXJkIEFS
UCBtZXNzYWdlcyB3aG9zZSBwcm90b2NvbCBpcyBJUCBhbmQgc2VuZGVyIHByb3RvY29sCiAgICAg
YWRkcmVzcyBpcyBuZWl0aGVyIGxpbmstbG9jYWwgYWRkcmVzcyBub3IgYm91bmQgd2l0aCB0aGUK
ICAgICBjb3JyZXNwb25kaW5nIGJpbmRpbmcgYW5jaG9yLiBJbiBhZGRpdGlvbiwgZGlzY2FyZCBB
UlAgUmVwbHkKICAgICBtZXNzYWdlcyB3aG9zZSB0YXJnZXQgYWRkcmVzcyBpcyBuZWl0aGVyIGxp
bmstbG9jYWwgYWRkcmVzcyBub3IKICAgICBib3VuZCB3aXRoIHRoZSBjb3JyZXNwb25kaW5nIGJp
bmRpbmcgYW5jaG9yLgoKICAgRm9yIG90aGVyIGJpbmRpbmcgYW5jaG9yczoKCiAgICAgRGlzY2Fy
ZCBESENQIFJlcGx5L0FDSyBtZXNzYWdlcyBub3QgZnJvbSBiaW5kaW5nIGFuY2hvciB3aXRoIHRo
ZQogICAgIFNBVkktREhDUC1UcnVzdCBhdHRyaWJ1dGUgb3IgU0FWSS1TQVZJIGF0dHJpYnV0ZS4K
CiAgIFRoZSBTQVZJIGRldmljZSBTSE9VTEQgcmVjb3JkIGFueSB2aW9sYXRpb24gb2YgdGhlIHBy
ZXZpb3VzIHJ1bGVzLgoKMTAuIFN0YXRlIFJlc3RvcmF0aW9uCgogICBJZiBhIFNBVkkgZGV2aWNl
IHJlYm9vdHMgYWNjaWRlbnRhbGx5IG9yIGRlc2lnbmVkbHksIHRoZSBzdGF0ZXMga2VwdAogICBp
biB2b2xhdGlsZSBtZW1vcnkgd2lsbCBnZXQgbG9zdC4gVGhpcyBtYXkgY2F1c2UgbGVnaXRpbWF0
ZSB0cmFmZmljCiAgIGZyb20gaG9zdHMgaW5kaXJlY3RseSBhdHRhY2hlZCB0byB0aGUgU0FWSSBk
ZXZpY2UgdG8gYmUgYmxvY2tlZCB1bnRpbAogICBhIGJpbmRpbmcgcmVjb3ZlcnkuIFB1cmVseSB1
c2luZyB0aGUgQmluZGluZyBSZWNvdmVyeSBQcm9jZXNzIGlzCiAgIGV4cGFuc2l2ZSBhbmQgcmVz
dWx0cyBkZWxheSB0byByZWNvdmVyIGEgbGFyZ2UgbnVtYmVyIG9mIGJpbmRpbmdzLgogICBUaHVz
LCByZWNvdmVyeSBmcm9tIG5vbi12b2xhdGlsZSBzdG9yYWdlLCBhcyBzcGVjaWZpZWQgYmVsb3cs
IGlzCiAgIHJlY29tbWVuZGVkLgoKICAgSWYgdGhpcyBmdW5jdGlvbiBpcyBzdXBwb3J0ZWQgYnkg
aGFyZHdhcmUsIGJpbmRpbmcgZW50cmllcyBNQVkgYmUKICAgc2F2ZWQgaW50byBub24tdm9sYXRp
bGUgc3RvcmFnZSB3aGVuZXZlciBhIG5ldyBiaW5kaW5nIGVudHJ5IGNoYW5nZXMKCgoKQmkgICAg
ICAgICAgICAgICAgICAgRXhwaXJlcyBTZXB0ZW1iZXIgMTYsIDIwMTIgICAgICAgICAgICAgIFtQ
YWdlIDE5XQoMCkludGVybmV0LURyYWZ0ICAgICAgICAgICAgICAgIHNhdmktZGhjcCAgICAgICAg
ICAgICAgICAgICAgIE1hcmNoIDIwMTIKCgogICB0byBCT1VORCBzdGF0ZS4gSWYgYSBiaW5kaW5n
IHdpdGggQk9VTkQgc3RhdGUgaXMgcmVtb3ZlZCwgdGhlIHNhdmVkCiAgIGVudHJ5IE1VU1QgYmUg
cmVtb3ZlZCBjb3JyZXNwb25kaW5nbHkuCgogICBJbW1lZGlhdGVseSBhZnRlciByZWJvb3QsIHRo
ZSBTQVZJIGRldmljZSBTSE9VTEQgcmVzdG9yZSBiaW5kaW5nCiAgIHN0YXRlcyBmcm9tIHRoZSBu
b24tdm9sYXRpbGUgc3RvcmFnZS4gVGhlIHN5c3RlbSB0aW1lIG9mIHNhdmUgcHJvY2VzcwogICBN
VVNUIGJlIHN0b3JlZC4gQWZ0ZXIgcmVib290aW5nLCB0aGUgU0FWSSBkZXZpY2UgTVVTVCBjaGVj
ayB3aGV0aGVyCiAgIGVhY2ggZW50cnkgaGFzIGJlZW4gb2Jzb2xldGUgdGhyb3VnaCBjb21wYXJp
bmcgdGhlIHNhdmVkIGxpZmV0aW1lIGFuZAogICB0aGUgZGlmZmVyZW5jZSBiZXR3ZWVuIGN1cnJl
bnQgc3lzdGVtIHRpbWUgYW5kIHNhdmVkIHN5c3RlbSB0aW1lLgoKMTEuIEhhbmRsZSBCaW5kaW5n
IEFuY2hvciBPZmYtbGluayBFdmVudAoKICAgUG9ydCBET1dOIGV2ZW50IE1VU1QgYmUgaGFuZGxl
ZCBpZiBzd2l0Y2ggcG9ydCBpcyB1c2VkIGFzIGJpbmRpbmcKICAgYW5jaG9yLiBJbiBtb3JlIGdl
bmVyYWwgY2FzZSwgaWYgYSBiaW5kaW5nIGFuY2hvciB0dXJucyBvZmYtbGluaywKICAgdGhpcyBl
dmVudCBNVVNUIGJlIGhhbmRsZWQuCgogICBXaGVuZXZlciBhIGJpbmRpbmcgYW5jaG9yIHdpdGgg
YXR0cmlidXRlIFNBVkktVmFsaWRhdGlvbiB0dXJucyBkb3duLAogICBzZXQgYSB0aW1lciB3aXRo
IE9GRkxJTktfREVMQVkuIFVudGlsIHRoZSB0aW1lciBiZWNvbWVzIHplcm8sIHRoZQogICBiaW5k
aW5ncyB3aXRoIHRoZSBiaW5kaW5nIGFuY2hvciBTSE9VTEQgYmUga2VwdC4gQXMgYW4gZXhjZXB0
aW9uLCB0bwogICBoYW5kbGUgbm9kZSBtb3ZlbWVudCwgaWYgcmVjZWl2aW5nIERBRCBOZWlnaGJv
cgogICBTb2xpY2l0YXRpb24vR3JhdHVpdG91cyBBUlAgcmVxdWVzdCB0YXJnZXRpbmcgYXQgdGhl
IGFkZHJlc3MgZHVyaW5nCiAgIE9GRkxJTktfREVMQVksIHRoZSBlbnRyeSBNQVkgYmUgcmVtb3Zl
ZC4KCiAgIElmIHRoZSBiaW5kaW5nIGFuY2hvciB0dXJucyBvbi1saW5rIGR1cmluZyBPRkZMSU5L
X0RFTEFZLCB0dXJuIG9mZgogICB0aGUgdGltZXIgYW5kIGtlZXAgY29ycmVzcG9uZGluZyBiaW5k
aW5ncy4KCjEyLiBDb25zdGFudHMKCiAgIE1BWF9ESENQX1JFU1BPTlNFX1RJTUUgICAgIDEyMHMK
CiAgIEJJTkRfUkVDT1ZFUllfSU5URVJWQUwgICAgIDYwcyBhbmQgY29uZmlndXJhYmxlCgogICBN
QVhfTEVBU0VRVUVSWV9ERUxBWSAgICAgICAxMHMKCiAgIE9GRkxJTktfREVMQVkgICAgICAgICAg
ICAgIDMwcwoKICAgREFEX1RJTUVPVVQgICAgICAgICAgICAgICAgMC41cwoKMTMuIFNlY3VyaXR5
IENvbnNpZGVyYXRpb25zCgogIDEzLjEuIFNlY3VyaXR5IFByb2JsZW0gYWJvdXQgQmluZGluZyBU
cmlnZ2VyZWQgYnkKICAgICBFVkVfREhDUF9SRVBMWV9OVUxMCgogICAgV2hlbiB0aGUgYmluZGlu
ZyBhbmNob3IgaXMgc3dpdGNoIHBvcnQsIGJpbmRpbmcgYmFzZWQgb24KICAgIEVWRV9ESENQX1JF
UExZX05VTEwgY2FuIHJlc3VsdCBpbiBzZWN1cml0eSB0aHJlYXRzLiBUaGUgYXNzaWduZWQKICAg
IGFkZHJlc3MgY291bGQgYmUgYm91bmQgdG8gYSB3cm9uZyBzd2l0Y2ggcG9ydCBpZiBhbiBhdHRh
Y2sgY2FuCiAgICBwb2lzb24gdGhlIHRhYmxlIG1hcHBpbmcgYSBsaW5rIGxheWVyIGFkZHJlc3Mg
dG8gc3dpdGNoIHBvcnQgKGNmLgogICAgc2VjdGlvbiA1LjMpLgoKCkJpICAgICAgICAgICAgICAg
ICAgIEV4cGlyZXMgU2VwdGVtYmVyIDE2LCAyMDEyICAgICAgICAgICAgICBbUGFnZSAyMF0KDApJ
bnRlcm5ldC1EcmFmdCAgICAgICAgICAgICAgICBzYXZpLWRoY3AgICAgICAgICAgICAgICAgICAg
ICBNYXJjaCAyMDEyCgoKICAgIEZvciBleGFtcGxlLCBob3N0IEEgcmVxdWVzdHMgYWRkcmVzcyBm
cm9tIHBvcnQgMS4gV2hlbiBTQVZJIHN3aXRjaAogICAgcmVjZWl2ZXMgYSBESENQIFJFUExZIHdp
dGggYXNzaWduZWQgYWRkcmVzcyBJUF9BIGFuZCBkZXN0aW5hdGlvbgogICAgbGluayBsYXllciBh
ZGRyZXNzIE1BQ19BLCBpdCB3aWxsIGNoZWNrIGl0cyBNQUMvcG9ydCB0YWJsZSB0byBmaW5kCiAg
ICB0aGUgcmlnaHQgYmluZGluZyBwb3J0LiBCdXQgTUFDL3BvcnQgdGFibGUgbWlnaHQgYmUgcG9s
bHV0ZWQgYnkgYW4KICAgIGF0dGFja2VyIGhvc3QgQiBhdHRhY2hlZCB0byBwb3J0IDIuIFRoZW4g
U0FWSSBzd2l0Y2ggd2lsbCBmaW5kIHRoZQogICAgTUFDX0EgaXMgYXQgcG9ydCAyIGZyb20gdGhl
IHBvbGx1dGVkIE1BQy9wb3J0IHRhYmxlIGFuZCBpdCB3aWxsCiAgICByZXN1bHQgaW4gYSB3cm9u
ZyBiaW5kaW5nIHdoaWNoIGJpbmRzIElQX0EgYW5kIHBvcnQgMi4KCiAgICBJZiBvbmUgb2YgdGhl
IGZvbGxvd2luZyBjb25kaXRpb25zIGlzIHNhdGlzZmllZCwgdGhlIHNlY3VyaXR5IGNhbiBiZQog
ICAgZW5zdXJlZC4KCiAgIDEuIERIQ1AgT3B0aW9uIDgyIGlzIHVzZWQgdG8ga2VlcCBiaW5kaW5n
IGFuY2hvciBpbiBESENQIFJlcXVlc3QgYW5kCiAgICAgIFJlcGx5LgoKICAgICAgIERIQ1AgT3B0
aW9uIDgyIGNhbiBiZSB1c2VkIHRvIGtlZXAgdGhlIGNpcmN1aXQgaW5mb3JtYXRpb24gb2YgdGhl
CiAgICAgICBjbGllbnQgYW5kIHJldHVybmVkIGJ5IHRoZSBESENQIHNlcnZlci4gVGh1cyB0aGUg
YmluZGluZyBhbmNob3IKICAgICAgIGNhbiBiZSBkZXRlcm1pbmVkIGZyb20gdGhlIGNpcmN1aXQg
aW5mb3JtYXRpb24gaW4gdGhlIE9wdGlvbi4gSXQKICAgICAgIGNhbiBiZSB1c2VkIHdoZW5ldmVy
IGFuIGltcGxlbWVudGF0aW9uIGRvZXNuJ3Qgd2FudCB0byBjcmVhdGUgYW4KICAgICAgIGVudHJ5
IG9uIHRoZSBESENQIFJlcXVlc3QgbWVzc2FnZS4KCiAgIDIuIFVuc3Bvb2ZhYmxlIE1BQyBpcyB1
c2VkIGFzIGJpbmRpbmcgYW5jaG9yICg4MDIuMTFpLCA4MDIuMWFlL2FmKS4KCiAgIDMuIFRoZSBt
YXBwaW5nIHRhYmxlIGZyb20gTUFDIHRvIGJpbmRpbmcgYW5jaG9yIGlzIHNlY3VyZS4KCiAgICAg
ICBJZiB0aGUgYmluZGluZyBhbmNob3IgaXMgYSBsaW5rIGxheWVyIGFkZHJlc3MsIG9yIHRoZXJl
IGFyZQogICAgICAgbWVjaGFuaXNtcyBwcmV2ZW50aW5nIHRoZSBjb3JydXB0aW9uIG9mIHRoZSB0
YWJsZSBtYXBwaW5nIHRoZQogICAgICAgbGluayBsYXllciB0byBhIHN3aXRjaCBwb3J0LCBtYXBw
aW5nIGxpbmsgbGF5ZXIgYWRkcmVzcyB0bwogICAgICAgYmluZGluZyBhbmNob3IgbWF5IGJlIGNv
bnNpZGVyZWQgYXMgc2VjdXJlLgoKICAgSXQgaXMgTk9UIFJFQ09NTUVOREVEIHRvIGluaXRpYWxp
emUgYSBiaW5kaW5nIGJhc2VkIG9uIERIQ1AgUmVwbHksCiAgIHVubGVzcyBhIG1lY2hhbmlzbSBw
cm90ZWN0aW5nIHRoZSBtYXBwaW5nIHRhYmxlIGZyb20gY29ycnVwdGlvbiBpcwogICBhbHNvIGlt
cGxlbWVudGVkLgoKICAgU2ltaWxhciBwcm9ibGVtIG1heSBoYXBwZW4gd2l0aCBiaW5kaW5nIGFu
Y2hvcnMgbm90IGJhc2VkIG9uIGxpbmsKICAgbGF5ZXIgYWRkcmVzc2VzLgoKICAxMy4yLiBCaW5k
aW5nIE51bWJlciBMaW1pdGF0aW9uCgogICBJdCBpcyBzdWdnZXN0ZWQgdG8gY29uZmlndXJlIHNv
bWUgbWVjaGFuaXNtIGluIG9yZGVyIHRvIHByZXZlbnQgYQogICBzaW5nbGUgbm9kZSBmcm9tIGV4
aGF1c3RpbmcgdGhlIGJpbmRpbmcgdGFibGUgZW50cmllcyBvbiB0aGUgU0FWSQogICBkZXZpY2Uu
IEVpdGhlciBvZiB0aGUgZm9sbG93aW5nIG1lY2hhbmlzbSBpcyBzdWZmaWNpZW50IHRvIHByZXZl
bnQKICAgc3VjaCBhdHRhY2suCgogICAxLiBTZXQgdGhlIHVwcGVyIGJvdW5kIG9mIGJpbmRpbmcg
bnVtYmVyIGZvciBlYWNoIGJpbmRpbmcgYW5jaG9yIHdpdGgKICAgICAgU0FWSS1WYWxpZGF0aW9u
LgoKCgoKQmkgICAgICAgICAgICAgICAgICAgRXhwaXJlcyBTZXB0ZW1iZXIgMTYsIDIwMTIgICAg
ICAgICAgICAgIFtQYWdlIDIxXQoMCkludGVybmV0LURyYWZ0ICAgICAgICAgICAgICAgIHNhdmkt
ZGhjcCAgICAgICAgICAgICAgICAgICAgIE1hcmNoIDIwMTIKCgogICAyLiBSZXNlcnZlIGEgbnVt
YmVyIG9mIGJpbmRpbmcgZW50cmllcyBmb3IgZWFjaCBiaW5kaW5nIGFuY2hvciB3aXRoCiAgICAg
IFNBVkktVmFsaWRhdGlvbiBhdHRyaWJ1dGUgYW5kIGFsbCBiaW5kaW5nIGFuY2hvcnMgc2hhcmUg
YSBwb29sIG9mCiAgICAgIHRoZSBvdGhlciBiaW5kaW5nIGVudHJpZXMuCgogICAzLiBMaW1pdCBE
SENQIFJlcXVlc3QgcmF0ZSBwZXIgYmluZGluZyBhbmNob3IuCgogIDEzLjMuIFJpc2sgZnJvbSBM
aW5rIExheWVyIFJvdXRpbmcgRHluYW1pYwoKICAgQW4gaW1wbGljaXQgYXNzdW1wdGlvbiBvZiB0
aGlzIHNvbHV0aW9uIGlzIHRoYXQgZGF0YSBwYWNrZXQgbXVzdAogICBhcnJpdmUgYXQgdGhlIHNh
bWUgYmluZGluZyBhbmNob3Igd2l0aCB0aGUgYmluZGluZyBhbmNob3IgdGhhdCB0aGUKICAgY29u
dHJvbCBwYWNrZXRzIGhhdmUgYXJyaXZlZCBhdC4gSWYgdGhpcyBhc3N1bXB0aW9uIGlzIG5vdCB2
YWxpZCwKICAgdGhpcyBjb250cm9sIHBhY2tldCBiYXNlZCBzb2x1dGlvbiB3aWxsIGZhaWwgb3Ig
YXQgbGVhc3QgZGlzY2FyZAogICBsZWdpdGltYXRlIHBhY2tldC4gVW5mb3J0dW5hdGVseSwgdGhl
IGxpbmsgbGF5ZXIgcm91dGluZyBiZXR3ZWVuIGhvc3QKICAgYW5kIFNBVkkgZGV2aWNlIGNhbiBi
ZSBpbmNvbnNpc3RlbnQgZnJvbSB0aW1lIHRvIHRpbWUuIFRpbWUKICAgY29uc2lzdGVuY3kgb2Yg
bGluayBsYXllciByb3V0aW5nIGlzIG5vdCBhc3N1cmVkIGJ5IGxpbmsgbGF5ZXIKICAgcm91dGlu
ZyBwcm90b2NvbC4gRm9yIGV4YW1wbGUsIFRSSUxMLCBhIHJlY2VudCBsaW5rIGxheWVyIHJvdXRp
bmcKICAgcHJvdG9jb2wsIGlzIGZsZXhpYmxlIGFuZCBtdWx0aXBsZSBsaW5rIGxheWVyIHBhdGhz
IGFyZSBhbGxvd2VkLgoKICAgVG8gbWFrZSB0aGUgYmFzaWMgYXNzdW1wdGlvbiBzdGFuZCwgdGhl
IGJlc3Qgd2F5IGlzIGVuZm9yY2luZyB0aGF0CiAgIHRoZXJlIHNob3VsZCBiZSBvbmx5IG9uZSB0
b3BvbG9neSBwYXRoIGZyb20gZG93bnN0cmVhbSBob3N0IHRvIHRoZQogICBTQVZJIGRldmljZS4g
Rm9yIGV4YW1wbGUsIFNBVkkgZGV2aWNlIGlzIGRpcmVjdGx5IGF0dGFjaGVkIGJ5IGhvc3RzLgoK
ICAgSWYgdGhlIGFzc3VtcHRpb24gZG9lc24ndCBzdGFuZCwgYSBiZXR0ZXIgc29sdXRpb24gaXMg
cmVxdWlyaW5nCiAgIGludGVyLW9wZXJhdGlvbiBiZXR3ZWVuIFNBVkkgcHJvdG9jb2wgYW5kIHRo
ZSBsaW5rIGxheWVyIHJvdXRpbmcKICAgcHJvdG9jb2wgdG8gbWFrZSBTQVZJIHByb3RvY29sIHNl
bnNpdGl2ZSB0byB0aGUgbGluayBsYXllciByb3V0aW5nCiAgIGNoYW5nZS4gVGhpcyBzb2x1dGlv
biBpcyBhYm92ZSB0aGUgc2NvcGUgb2YgdGhpcyBkb2N1bWVudC4KCiAgMTMuNC4gRHVwbGljYXRl
IEJpbmRpbmdzIG9mIFNhbWUgQWRkcmVzcwoKICAgVGhlIHNhbWUgYWRkcmVzcyBtYXkgYmUgYm91
bmQgd2l0aCBtdWx0aXBsZSBiaW5kaW5nIGFuY2hvcnMsIG9ubHkgaWYKICAgdGhlIGJpbmRpbmcg
cHJvY2Vzc2VzIGFyZSBmaW5pc2hlZCBvbiBlYWNoIGJpbmRpbmcgYW5jaG9yCiAgIHN1Y2Nlc3Nm
dWxseSByZXNwZWN0aXZlbHkuIFRoaXMgbWVjaGFuaXNtIGlzIGRlc2lnbmVkIGluCiAgIGNvbnNp
ZGVyYXRpb24gdGhhdCBhIG5vZGUgbWF5IG1vdmUgb24gdGhlIGxvY2FsIGluaywgYW5kIGEgbm9k
ZSBtYXkKICAgaGF2ZSBtdWx0aXBsZSBiaW5kaW5nIGFuY2hvcnMuIEhvd2V2ZXIsIHRoZSB0cmFj
ZWFiaWxpdHkgb2YgYWRkcmVzcwogICBpcyByZWR1Y2VkLgoKICAgTm90ZSB0aGF0IHRoZSBsb2Nh
bCBsaW5rIG1vdmVtZW50IHNjZW5hcmlvIGlzIG5vdCBoYW5kbGVkIHBlcmZlY3RseS4KICAgVGhl
IGZvcm1lciBiaW5kaW5nIG1heSBub3QgYmUgcmVtb3ZlZCwgdW5sZXNzIHRoZSBub2RlIGlzIGRp
cmVjdGx5CiAgIGF0dGFjaGVkIHRvIFNBVkkgZGV2aWNlLiBUaGUgbm9kZXMgc2hhcmluZyB0aGUg
c2FtZSBmb3JtZXIgYmluZGluZwogICBhbmNob3Igb2YgdGhlIG1vdmluZyBub2RlIGhhdmUgdGhl
IGFiaWxpdHkgdG8gdXNlIGl0cyBhZGRyZXNzLgoKICAxMy41LiBTZWN1cml0eSBQcm9ibGVtcyBh
Ym91dCBCaW5kaW5nIFJlY292ZXJ5IFByb2Nlc3MKCiAgIFRoZSBCaW5kaW5nIFJlY292ZXJ5IFBy
b2Nlc3MgKGNmLiBzZWN0aW9uIDguMSkgTVVTVCBiZSByYXRlIGxpbWl0ZWQKICAgdG8gYXZvaWQg
RGVuaWFsIG9mIFNlcnZpY2VzIGF0dGFjayBhZ2FpbnN0IHRoZSBTQVZJIGRldmljZSBpdHNlbGYu
IEEKICAgY29uc3RhbnQgQklORF9SRUNPVkVSWV9JTlRFUlZBTCBpcyB1c2VkIHRvIGNvbnRyb2wg
dGhlIGZyZXF1ZW5jeS4gVHdvCiAgIGRhdGEtdHJpZ2dlcmVkIHJlY292ZXJ5IHByb2Nlc3NlcyBv
biBvbmUgYmluZGluZyBhbmNob3IgTVVTVCBoYXZlIGEKCgpCaSAgICAgICAgICAgICAgICAgICBF
eHBpcmVzIFNlcHRlbWJlciAxNiwgMjAxMiAgICAgICAgICAgICAgW1BhZ2UgMjJdCgwKSW50ZXJu
ZXQtRHJhZnQgICAgICAgICAgICAgICAgc2F2aS1kaGNwICAgICAgICAgICAgICAgICAgICAgTWFy
Y2ggMjAxMgoKCiAgIG1pbmltdW0gaW50ZXJ2YWwgdGltZSBCSU5EX1JFQ09WRVJZX0lOVEVSVkFM
LiBUaGlzIGNvbnN0YW50IFNIT1VMRCBiZQogICBjb25maWd1cmVkIHBydWRlbnRseSB0byBhdm9p
ZCBEZW5pYWwgb2YgU2VydmljZSBhdHRhY2tzLgoKICAgVGhpcyBwcm9jZXNzIGlzIG5vdCBzdHJp
Y3Qgc2VjdXJlLiBUaGUgbm9kZSB3aXRoIFNBVkktQmluZFJlY292ZXJ5CiAgIGJpbmRpbmcgYW5j
aG9yIGhhcyB0aGUgYWJpbGl0eSB0byB1c2UgdGhlIGFkZHJlc3Mgb2YgYW4gaW5hY3RpdmUKICAg
bm9kZSwgd2hpY2ggZG9lc24ndCByZXBseSB0byB0aGUgZGV0ZWN0aW9uIHByb2Jlcy4KCiAgMTMu
Ni4gQ29tcGF0aWJpbGl0eSB3aXRoIEROQSAoRGV0ZWN0aW5nIE5ldHdvcmsgQXR0YWNobWVudCkK
CiAgIEROQSBbUkZDNDQzNl0gW1JGQzYwNTldIGlzIGRlc2lnbmVkIHRvIGRlY3JlYXNlIHRoZSBo
YW5kb3ZlciBsYXRlbmN5CiAgIGFmdGVyIHJlLWF0dGFjaG1lbnQgdG8gdGhlIHNhbWUgbmV0d29y
ay4gRE5BIG1haW5seSByZWxpZXMgb24KICAgcGVyZm9ybWluZyByZWFjaGFiaWxpdHkgdGVzdCB0
aHJvdWdoIHNlbmRpbmcgdW5pY2FzdCBOZWlnaGJvcgogICBTb2xpY2l0YXRpb24vUm91dGVyIFNv
bGljaXRhdGlvbi9BUlAgUmVxdWVzdCBtZXNzYWdlIHRvIGRldGVybWluZQogICB3aGV0aGVyIGEg
cHJldmlvdXNseSBjb25maWd1cmVkIGFkZHJlc3MgaXMgc3RpbGwgdmFsaWQuIFRob3VnaCBETkEK
ICAgcHJvdmlkZXMgYW4gb3B0aW1pemF0aW9uIGZvciBob3N0LCBpdCBkb2Vzbid0IHByb3ZpZGUg
c3VmZmljaWVudAogICBpbmZvcm1hdGlvbiBmb3IgdGhpcyBtZWNoYW5pc20gdG8gbWlncmF0ZSBv
ciBlc3RhYmxpc2ggYSBiaW5kaW5nLiBJZgogICBhIGJpbmRpbmcgaXMgc2V0IHVwIG9ubHkgdGhy
b3VnaCBzbm9vcGluZyB0aGUgcmVhY2hhYmlsaXR5IHRlc3QKICAgbWVzc2FnZSwgdGhlIGJpbmRp
bmcgY2FuIGJlIGludmFsaWQuIEZvciBleGFtcGxlLCBhbiBhdHRhY2tlciBjYW4KICAgcGVyZm9y
bSByZWFjaGFiaWxpdHkgdGVzdCB3aXRoIGFkZHJlc3MgYm91bmQgdG8gYW5vdGhlciBob3N0LiBJ
ZgogICBiaW5kaW5nIGlzIG1pZ3JhdGVkIHRvIHRoZSBhdHRhY2tlciwgdGhlIGF0dGFja2VyIGNh
biBzdWNjZXNzZnVsCiAgIG9idGFpbiB0aGUgYmluZGluZyBmcm9tIHRoZSB2aWN0aW0uIEJlY2F1
c2UgdGhpcyBtZWNoYW5pc20gd291bGRuJ3QKICAgc2V0IHVwIGEgYmluZGluZyBiYXNlZCBvbiBz
bm9vcGluZyB0aGUgRE5BIHByb2NlZHVyZSwgaXQgY2Fubm90CiAgIGFjaGlldmUgcGVyZmVjdCBj
b21wYXRpYmlsaXR5IHdpdGggRE5BLiBIb3dldmVyLCBpdCBvbmx5IG1lYW5zIHRoZQogICByZS1j
b25maWd1cmF0aW9uIG9mIGludGVyZmFjZSBpcyBzbG93ZWQgYnV0IG5vdCBwcmV2ZW50ZWQuIERl
dGFpbHMKICAgYXJlIGRpc2N1c3NlZCBhcyBmb2xsb3dzLgoKICAgSW4gU2ltcGxlIEROQXY2IFtS
RkM2MDU5XSwgdGhlIHByb2JlIGlzIHNlbnQgd2l0aCBzb3VyY2UgYWRkcmVzcyBzZXQKICAgdG8g
bGluay1sb2NhbCBhZGRyZXNzLCBhbmQgc3VjaCBtZXNzYWdlcyB3aWxsIG5vdCBiZSBmaWx0ZXJl
ZCBieSB0aGUKICAgcG9saWN5IHNwZWNpZmllZCBpbiBzZWN0aW9uIDkuMi4gSWYgYW4gaW50ZXJm
YWNlIGlzIHJlLWF0dGFjaGVkIHRvIGEKICAgcHJldmlvdXMgbmV0d29yaywgdGhlIGRldGVjdGlv
biB3aWxsIGJlIGNvbXBsZXRlIGFuZCB0aGUgYWRkcmVzcyB3aWxsCiAgIGJlIHJlZ2FyZGVkIGFz
IHZhbGlkIGJ5IGhvc3QuIFRoZSBjYW5kaWRhdGUgYWRkcmVzcyBpcyBub3QgY29udGFpbmVkCiAg
IGluIHRoZSBwcm9iZS4gVGh1cywgdGhlIGJpbmRpbmcgY2Fubm90IGJlIHJlY292ZXJlZCB0aHJv
dWdoIHNub29waW5nCiAgIHRoZSBwcm9iZS4gVGhlIGJpbmRpbmcgY2FuIG9ubHkgYmUgcmVjb3Zl
cmVkIGZyb20gdGhlIERIQ1Agc25vb3BpbmcKICAgcHJvY2VkdXJlLiBUaGUgREhDUCBSRVFVRVNU
IG1lc3NhZ2VzIHdvdWxkbid0IGJlIGZpbHRlcmVkIGJ5IHRoaXMKICAgc29sdXRpb24gYXMgdGhl
aXIgc291cmNlIGFkZHJlc3MgaXMgbGluay1sb2NhbCBhZGRyZXNzLiBCZWZvcmUgdGhlCiAgIERI
Q1AgcHJvY2VkdXJlIGlzIGNvbXBsZXRlZCwgcGFja2V0cyB3aWxsIGJlIGZpbHRlcmVkIGJ5IFNB
VkkgZGV2aWNlLgogICBJbiBhbm90aGVyIHdvcmQsIGluIFNBVkkgc2NlbmFyaW9zLCBTaW1wbGUg
RE5BdjYgd2lsbCBub3QgaGVscCByZWR1Y2UKICAgdGhlIGhhbmRvdmVyIGxhdGVuY3kuIElmIFNB
VkktQmluZFJlY292ZXJ5IGF0dHJpYnV0ZSBpcyBjb25maWd1cmVkIG9uCiAgIHRoZSBuZXcgYmlu
ZGluZyBhbmNob3IsIGRhdGEgdHJpZ2dlcmVkIHByb2NlZHVyZSBtYXkgcmVkdWNlIHRoZQogICBs
YXRlbmN5LgoKICAgSW4gRE5BdjQgW1JGQzQ0MzZdLCB0aGUgQVJQIHByb2JlIHdpbGwgYmUgZmls
dGVyZWQgYmVjYXVzZSB1bmJvdW5kCiAgIGFkZHJlc3MgaXMgdXNlZCBhcyBzZW5kZXIgcHJvdG9j
b2wgYWRkcmVzcy4gQXMgYSByZXN1bHQsIHRoZQogICBkZXRlY3Rpb24gd2lsbCBub3QgY29tcGxl
dGUgYW5kIGZhbHNlIG5lZ2F0aXZlIGlzIGNhdXNlZC4gVGhlIERIQ1AKICAgUkVRVUVTVCBtZXNz
YWdlIHNlbnQgYnkgdGhlIG5vZGUgd2lsbCBub3QgYmUgZmlsdGVyZWQsIGJlY2F1c2UgdGhlCiAg
IHNvdXJjZSBJUCBhZGRyZXNzIGZpZWxkIHNob3VsZCBiZSBhbGwgemVybyBhcyByZXF1aXJlZCBi
eSBbUkZDMjEzMV0uCgoKCkJpICAgICAgICAgICAgICAgICAgIEV4cGlyZXMgU2VwdGVtYmVyIDE2
LCAyMDEyICAgICAgICAgICAgICBbUGFnZSAyM10KDApJbnRlcm5ldC1EcmFmdCAgICAgICAgICAg
ICAgICBzYXZpLWRoY3AgICAgICAgICAgICAgICAgICAgICBNYXJjaCAyMDEyCgoKICAgVGh1cywg
aWYgdGhlIGFkZHJlc3MgaXMgc3RpbGwgdmFsaWQsIHRoZSBiaW5kaW5nIHdpbGwgYmUgcmVjb3Zl
cmVkCiAgIGZyb20gdGhlIERIQ1Agc25vb3BpbmcgcHJvY2VkdXJlLgoKICAxMy43LiBSZXNpZHVh
bCBUaHJlYXRzCgogICBBcyBkZXNjcmliZWQgaW4gW0ktRC5pZXRmLXNhdmktZnJhbWV3b3JrXSwg
dGhpcyBzb2x1dGlvbiBjYW5ub3QKICAgc3RyaWN0bHkgcHJldmVudCBzcG9vZmluZy4gVGhlcmUg
YXJlIHR3byBzY2VuYXJpb3MgaW4gd2hpY2ggc3Bvb2ZpbmcKICAgY2FuIHN0aWxsIGhhcHBlbjoK
CiAgIDEuIFRoZSBiaW5kaW5nIGFuY2hvciBpcyBzcG9vZmFibGUKCiAgIElmIHRoZSBiaW5kaW5n
IGFuY2hvciBpcyBzcG9vZmFibGUsIGUuZy4sIHBsYWluIE1BQyBhZGRyZXNzLCBhbgogICBhdHRh
Y2tlciBjYW4gdXNlIGZvcmdlZCBiaW5kaW5nIGFuY2hvciB0byBzZW5kIHBhY2tldCB3aGljaCB3
aWxsIG5vdAogICBiZSByZWdhcmRlZCBhcyBzcG9vZmluZyBieSBTQVZJIGRldmljZS4KCiAgIElu
ZGVlZCwgdXNpbmcgYmluZGluZyBhbmNob3IgdGhhdCBjYW4gYmUgZWFzaWx5IHNwb29mZWQgaXMg
ZGFuZ2Vyb3VzLgogICBBbiBhdHRhY2tlciBjYW4gdXNlIHRoZSBiaW5kaW5nIGFuY2hvciBvZiBh
bm90aGVyIGhvc3QgdG8gcGVyZm9ybSBhCiAgIGxvdCBvZiBESENQIHByb2NlZHVyZXMsIGFuZCB0
aGUgU0FWSSBkZXZpY2Ugd2lsbCByZWZ1c2UgdG8gc2V0IHVwIG5ldwogICBiaW5kaW5nIGZvciB0
aGUgaG9zdCB3aGVuZXZlciB0aGUgYmluZGluZyBudW1iZXIgbGltaXRhdGlvbiBoYXMgYmVlbgog
ICByZWFjaGVkLiBUaHVzLCBpdCBpcyBSRUNPTU1FTkRFRCB0byB1c2Ugc3Ryb25nIGVub3VnaCBi
aW5kaW5nIGFuY2hvciwKICAgZS5nLiwgc3dpdGNoIHBvcnQsIHNlY3VyZSBhc3NvY2lhdGlvbiBp
biA4MDIuMTFhZS9hZiBhbmQgODAyLjExaS4KCiAgIDIuIFRoZSBiaW5kaW5nIGFuY2hvciBpcyBz
aGFyZWQgYnkgbW9yZSB0aGFuIG9uZSBob3N0CgogICBJZiB0aGUgYmluZGluZyBhbmNob3IgaXMg
c2hhcmVkIGJ5IG1vcmUgdGhhbiBvbmUgaG9zdCwgdGhleSBjYW4gc3Bvb2YKICAgdGhlIGFkZHJl
c3NlcyBvZiBlYWNoIG90aGVyLiBGb3IgZXhhbXBsZSwgYSBudW1iZXIgb2YgaG9zdHMgY2FuCiAg
IGF0dGFjaCB0byB0aGUgc2FtZSBzd2l0Y2ggcG9ydCBvZiBhIFNBVkkgZGV2aWNlIHRocm91Z2gg
YSBodWIuIFRoZQogICBTQVZJIGRldmljZSBjYW5ub3QgZGlzdGluZ3Vpc2ggcGFja2V0cyBmcm9t
IGRpZmZlcmVudCBob3N0cyBhbmQgdGh1cwogICB0aGUgc3Bvb2ZpbmcgYmV0d2VlbiB0aGVtIHdp
bGwgbm90IGJlIGRldGVjdGVkLiBUaGlzIHByb2JsZW0gY2FuIGJlCiAgIHNvbHZlZCB0aHJvdWdo
IG5vdCBzaGFyaW5nIGJpbmRpbmcgYW5jaG9yIGJldHdlZW4gaG9zdHMuCgoxNC4gSUFOQSBDb25z
aWRlcmF0aW9ucwoKICAgVGhpcyBkb2N1bWVudCBoYXMgbm8gSUFOQSBhY3Rpb25zLgoKICAgW1JG
QyBFZGl0b3I6IHBsZWFzZSByZW1vdmUgdGhpcyBzZWN0aW9uIHByaW9yIHRvIHB1YmxpY2F0aW9u
Ll0KCjE1LiBSZWZlcmVuY2VzCgogIDE1LjEuIE5vcm1hdGl2ZSBSZWZlcmVuY2VzCgogICBbUkZD
MjExOV0gQnJhZG5lciwgUy4sICJLZXkgd29yZHMgZm9yIHVzZSBpbiBSRkNzIHRvIEluZGljYXRl
CiAgICAgICAgICAgICBSZXF1aXJlbWVudCBMZXZlbHMiLCBCQ1AgMTQsIFJGQyAyMTE5LCBNYXJj
aCAxOTk3LgoKICAgW0ktRC5pZXRmLXNhdmktZnJhbWV3b3JrXQoKCgpCaSAgICAgICAgICAgICAg
ICAgICBFeHBpcmVzIFNlcHRlbWJlciAxNiwgMjAxMiAgICAgICAgICAgICAgW1BhZ2UgMjRdCgwK
SW50ZXJuZXQtRHJhZnQgICAgICAgICAgICAgICAgc2F2aS1kaGNwICAgICAgICAgICAgICAgICAg
ICAgTWFyY2ggMjAxMgoKCiAgICAgICAgICAgICBXdSwgSi4sIEJpLCBKLiwgQmFnbnVsbywgTS4s
IEJha2VyLCBGLiwgYW5kIEMuIFZvZ3QsCiAgICAgICAgICAgICAiU291cmNlIEFkZHJlc3MgVmFs
aWRhdGlvbiBJbXByb3ZlbWVudCBGcmFtZXdvcmsiLCBkcmFmdC0KICAgICAgICAgICAgIGlldGYt
c2F2aS1mcmFtZXdvcmstMDQgKHdvcmsgaW4gcHJvZ3Jlc3MpLCBNYXJjaCAyMDExLgoKICAgW0kt
RC5pZXRmLXNhdmktZmNmc10KCiAgICAgICAgICAgICBOb3JkbWFyaywgRS4sIEJhZ251bG8sIE0u
LCBhbmQgRS4gTGV2eS1BYmVnbm9saSwgIkZDRlMtCiAgICAgICAgICAgICBTQVZJOiBGaXJzdC1D
b21lIEZpcnN0LVNlcnZlIFNvdXJjZS1BZGRyZXNzIFZhbGlkYXRpb24gZm9yCiAgICAgICAgICAg
ICBMb2NhbGx5IEFzc2lnbmVkIElQdjYgQWRkcmVzc2VzIiwgZHJhZnQtaWV0Zi1zYXZpLWZjZnMt
MDkKICAgICAgICAgICAgICh3b3JrIGluIHByb2dyZXNzKSwgQXByaWwgMjAxMS4KCiAgIFtJLUQu
aWV0Zi1zYXZpLW1peF0KCiAgICAgICAgICAgICBKdW4gQmksIEd1YW5nIFlhbywgSi4gSGFscGVy
biBhbmQgRS4gTGV2eS1BYmVnbm9saSwgIlNBVkkKICAgICAgICAgICAgIGZvciBNaXhlZCBBZGRy
ZXNzIEFzc2lnbm1lbnQgTWV0aG9kcyBTY2VuYXJpbyIsIGRyYWZ0LWlldGYtCiAgICAgICAgICAg
ICBzYXZpLW1peC0wMCAod29yayBpbiBwcm9ncmVzcyksIE1hcmNoIDIwMTEuCgogICBbUkZDODI2
XSAgUGx1bW1lciwgRC5DLiwgIkV0aGVybmV0IEFkZHJlc3MgUmVzb2x1dGlvbiBQcm90b2NvbDog
IE9yCiAgICAgICAgICAgICBjb252ZXJ0aW5nIG5ldHdvcmsgcHJvdG9jb2wgYWRkcmVzc2VzIHRv
IDQ4LmJpdCBFdGhlcm5ldAogICAgICAgICAgICAgYWRkcmVzcyBmb3IgdHJhbnNtaXNzaW9uIG9u
IEV0aGVybmV0IGhhcmR3YXJlIiwgU1REIDM3LCBSRkMKICAgICAgICAgICAgIDgyNiwgTm92ZW1i
ZXIgMTk4Mi4KCiAgIFtSRkMyMTMxXSBSLiBEcm9tcywgIkR5bmFtaWMgSG9zdCBDb25maWd1cmF0
aW9uIFByb3RvY29sIiwgUkZDMjEzMSwKICAgICAgICAgICAgIE1hcmNoIDE5OTcuCgogICBbUkZD
MzMxNV0gUi4gRHJvbXMsIEVkLiAiRHluYW1pYyBIb3N0IENvbmZpZ3VyYXRpb24gUHJvdG9jb2wg
Zm9yIElQdjYKICAgICAgICAgICAgIChESENQdjYpIiwgUkZDMzMxNSwgSnVseSAyMDAzLgoKICAg
W1JGQzM3MzZdIFIuIERyb21zLCAiU3RhdGVsZXNzIER5bmFtaWMgSG9zdCBDb25maWd1cmF0aW9u
IFByb3RvY29sCiAgICAgICAgICAgICAoREhDUCkgU2VydmljZSBmb3IgSVB2NiIsIFJGQyAzNzM2
LCBBcHJpbCAyMDA0LgoKICAgW1JGQzQzODhdIFIuIFdvdW5keSBhbmQgSy4gS2lubmVhciwgIkR5
bmFtaWMgSG9zdCBDb25maWd1cmF0aW9uCiAgICAgICAgICAgICBQcm90b2NvbCAoREhDUCkgTGVh
c2VxdWVyeSIsIFJGQzQzODgsIEZlYnJ1YXJ5IDIwMDYuCgogICBbUkZDNDQyNl0gQWJvYmEsIEIu
LCBDYXJsc29uLCBKLiwgYW5kIFMuIENoZXNoaXJlLCAiRGV0ZWN0aW5nIE5ldHdvcmsKICAgICAg
ICAgICAgIEF0dGFjaG1lbnQgaW4gSVB2NCAoRE5BdjQpIiwgUkZDIDQ0MzYsIE1hcmNoIDIwMDYu
CgogICBbUkZDNDg2MV0gVC4gTmFydGVuLCBFLiBOb3JkbWFyaywgVy4gU2ltcHNvbiwgYW5kIEgu
IFNvbGltYW4sCiAgICAgICAgICAgICAiTmVpZ2hib3IgRGlzY292ZXJ5IGZvciBJUCB2ZXJzaW9u
IDYgKElQdjYpIiwgUkZDNDg2MSwKICAgICAgICAgICAgIFNlcHRlbWJlciAyMDA3LgoKICAgW1JG
QzQ4NjJdIFRob21zb24sIFMuLCBOYXJ0ZW4sIFQuIGFuZCBKaW5tZWksIFQuLCAiSVB2NiBTdGF0
ZWxlc3MKICAgICAgICAgICAgIEF1dG9jb25maWd1cmF0aW9uIiwgUkZDNDg2MiwgU2VwdGVtYmVy
LCAyMDA3LgoKCgoKQmkgICAgICAgICAgICAgICAgICAgRXhwaXJlcyBTZXB0ZW1iZXIgMTYsIDIw
MTIgICAgICAgICAgICAgIFtQYWdlIDI1XQoMCkludGVybmV0LURyYWZ0ICAgICAgICAgICAgICAg
IHNhdmktZGhjcCAgICAgICAgICAgICAgICAgICAgIE1hcmNoIDIwMTIKCgogICBbUkZDNTAwN10g
Si4gQnJ6b3pvd3NraSwgSy4gS2lubmVhciwgQi4gVm9seiwgUy4gWmVuZywgIkRIQ1B2NgogICAg
ICAgICAgICAgTGVhc2VxdWVyeSIsIFJGQzUwMDcsIFNlcHRlbWJlciAyMDA3LgoKICAgW1JGQzYw
NTldIFMuIEtyaXNobmFuLCBHLiBEYWxleSwgIlNpbXBsZSBQcm9jZWR1cmVzIGZvciBEZXRlY3Rp
bmcKICAgICAgICAgICAgIE5ldHdvcmsgQXR0YWNobWVudCBpbiBJUHY2IiwgUkZDNjA1OSwgTm92
ZW1iZXIgMjAxMC4KCiAgMTUuMi4gSW5mb3JtYXRpdmUgUmVmZXJlbmNlcwoKICAgW0JDUDM4XSAg
IEZlcmd1c29uLCBQLiBhbmQgRC4gU2VuaWUsICJOZXR3b3JrIEluZ3Jlc3MgRmlsdGVyaW5nOgog
ICAgICAgICAgICAgRGVmZWF0aW5nIERlbmlhbCBvZiBTZXJ2aWNlIEF0dGFja3Mgd2hpY2ggZW1w
bG95IElQIFNvdXJjZQogICAgICAgICAgICAgQWRkcmVzcyBTcG9vZmluZyIsIEJDUCAzOCwgUkZD
IDI4MjcsIE1heSAyMDAwLgoKICAgW1JGQzUyMjddIFMuIENoZXNoaXJlLCAiSVB2NCBBZGRyZXNz
IENvbmZsaWN0IERldGVjdGlvbiIsIFJGQzUyMjcsCiAgICAgICAgICAgICBKdWx5IDIwMDguCgog
ICBbSVAgU291cmNlIEd1YXJkXQoKICAgICAgICAgICAgIEJha2VyLCBGLiwgIkNpc2NvIElQIFZl
cnNpb24gNCBTb3VyY2UgR3VhcmQiLCBJRVRGIEludGVybmV0CiAgICAgICAgICAgICBkcmFmdCAo
d29yayBpbiBwcm9ncmVzcyksIE5vdmVtYmVyIDIwMDcuCgoxNi4gQWNrbm93bGVkZ21lbnRzCgpT
cGVjaWFsIHRoYW5rcyB0byBKZWFuLU1pY2hlbCBDb21iZXMsIENocmlzdGlhbiBWb2d0LCBKb2Vs
IE0uIEhhbHBlcm4sCkVyaWMgTGV2eS1BYmVnbm9saSBhbmQgQWxiZXJ0byBHYXJjaWEgZm9yIGNh
cmVmdWwgcmV2aWV3IGFuZCB2YWx1YXRpb24KY29tbWVudHMgb24gdGhlIHN0YXRlIG1hY2hpbmUg
YW5kIHRleHQuClRoYW5rcyB0byBNYXJjZWxvIEJhZ251bG8gQnJhdW4sIE1hcmsgV2lsbGlhbXMs
IEVyaWsgTm9yZG1hcmssIE1pa2FlbApBYnJhaGFtc3NvbiwgSmFyaSBBcmtrbywgRGF2aWQgSGFy
cmluZ3RvbiwgUGVra2EgU2F2b2xhLCBYaW5nIExpLCBMaXhpYQpaaGFuZywgUm9iZXJ0IFJhc3p1
aywgR3JlZyBEYWxleSwgSm9obiBLYWlwcGFsbGltYWxpbCBhbmQgVGFvIExpbiBmb3IKdGhlaXIg
dmFsdWFibGUgY29udHJpYnV0aW9ucy4KCgoKCgoKCgoKCgoKCgoKCgoKCkJpICAgICAgICAgICAg
ICAgICAgIEV4cGlyZXMgU2VwdGVtYmVyIDE2LCAyMDEyICAgICAgICAgICAgICBbUGFnZSAyNl0K
DApJbnRlcm5ldC1EcmFmdCAgICAgICAgICAgICAgICBzYXZpLWRoY3AgICAgICAgICAgICAgICAg
ICAgICBNYXJjaCAyMDEyCgoKQXV0aG9ycycgQWRkcmVzc2VzCgogICBKdW4gQmkKICAgICAgVHNp
bmdodWEgVW5pdmVyc2l0eQogICAgICBOZXR3b3JrIFJlc2VhcmNoIENlbnRlciwgVHNpbmdodWEg
VW5pdmVyc2l0eQogICAgICBCZWlqaW5nICAxMDAwODQKICAgICAgQ2hpbmEKICAgICAgRW1haWw6
ICBqdW5iaUB0c2luZ2h1YS5lZHUuY24KCiAgIEppYW5waW5nIFd1CiAgICAgIFRzaW5naHVhIFVu
aXZlcnNpdHkKICAgICAgQ29tcHV0ZXIgU2NpZW5jZSwgVHNpbmdodWEgVW5pdmVyc2l0eQogICAg
ICBCZWlqaW5nICAxMDAwODQKICAgICAgQ2hpbmEKICAgICAgRW1haWw6ICBqaWFucGluZ0BjZXJu
ZXQuZWR1LmNuCgoKICAgR3VhbmcgWWFvCiAgICAgIFRzaW5naHVhIFVuaXZlcnNpdHkKICAgICAg
Q29tcHV0ZXIgU2NpZW5jZSwgVHNpbmdodWEgVW5pdmVyc2l0eQogICAgICBCZWlqaW5nIDEwMDA4
NAogICAgICBDaGluYQogICAgICBFbWFpbDogeWFvZ0BuZXRhcmNobGFiLnRzaW5naHVhLmVkdS5j
bgoKICAgIEZyZWQgQmFrZXIKICAgICAgIENpc2NvIFN5c3RlbXMKICAgICAgIFNhbnRhIEJhcmJh
cmEsIENBICA5MzExNwogICAgICAgVW5pdGVkIFN0YXRlcwogICAgICAgRW1haWw6ICBmcmVkQGNp
c2NvLmNvbQoKCjE3LiBDaGFuZ2UgTG9nCgogICBGcm9tIDAyIHRvIDAzOgoKICAgICAgICAgLSAg
U2VjdGlvbiAxMiwgZGF0YSB0cmlnZ2VyIGFuZCBjb3VudGVyIHRyaWdnZXIgYXJlIGNvbWJpbmVk
IHRvCiAgICAgICAgICAgIGJpbmRpbmcgcmVjb3ZlcnkgcHJvY2Vzcy4gVGhlIGV4cHJlc3Npb24g
Im9uZSBvZiBNVVNUIiBpcwogICAgICAgICAgICBjaGFuZ2VkIHRvICJjb25kaXRpb25hbCBNVVNU
LiBDb25kaXRpb25zIHJlbGF0ZWQgd2l0aCB0aGUKICAgICAgICAgICAgaW1wbGVtZW50YXRpb24g
YXJlIHNwZWNpZmllZC4gUmVsYXRlZCBjb25zdGFudHMgYXJlIGNoYW5nZWQKICAgICAgICAgICAg
aW4gc2VjdGlvbiAyNi4iCgoKCgoKQmkgICAgICAgICAgICAgICAgICAgRXhwaXJlcyBTZXB0ZW1i
ZXIgMTYsIDIwMTIgICAgICAgICAgICAgIFtQYWdlIDI3XQoMCkludGVybmV0LURyYWZ0ICAgICAg
ICAgICAgICAgIHNhdmktZGhjcCAgICAgICAgICAgICAgICAgICAgIE1hcmNoIDIwMTIKCgogICBN
YWluIGNoYW5nZXMgZnJvbSAwMyB0byAwNDoKCiAgICAgICAgIC0gIFNlY3Rpb24gIlByZWZpeCBj
b25maWd1cmF0aW9uIiBpcyByZW1vdmVkLgoKICAgICAgICAgLSAgU2VjdGlvbiAiU3VwcGxlbWVu
dGFsIGJpbmRpbmcgcHJvY2VzcyIgaXMgbW9kaWZpZWQgaW4KICAgICAgICAgICAgcmVxdWlyZW1l
bnQgbGV2ZWwuCgogICAgICAgICAtICBTdWItc2VjdGlvbiA5LjEgIlJhdGlvbmFsZSIgaXMgYWRk
ZWQuCgogICAgICAgICAtICBTZWN0aW9uICJGaWx0ZXJpbmcgZHVyaW5nIERldGVjdGlvbiIgaXMg
cmVtb3ZlZC4KCiAgICAgICAgIC0gIFNlY3Rpb24gIkhhbmRsaW5nIGxheWVyIDIgcGF0aCBjaGFu
Z2UiIGlzIGNoYW5nZWQgdG8KICAgICAgICAgICAgIkNvbnNpZGVyYXRpb24gb24gTGluayBsYXll
ciByb3V0aW5nIGNvbXBsZXhpdHkiCgogICAgICAgICAtICBTZWN0aW9uICJCYWNrZ3JvdW5kIGFu
ZCByZWxhdGVkIHByb3RvY29scyIgaXMgcmVtb3ZlZC4KCiAgIE1haW4gY2hhbmdlcyBmcm9tIDA0
IHRvIDA1OgoKICAgICAgICAgLSAgVHJpZ2dlciBldmVudHMgYXJlIGxpc3RlZCBleHBsaWNpdGx5
IGluIHNlY3Rpb24gOC4KCiAgICAgICAgIC0gIERldGVjdGlvbiBhbmQgTGl2ZSBzdGF0ZXMgYXJl
IGRlbGV0ZWQsIHRvZ2V0aGVyIHdpdGgKICAgICAgICAgICAgY29ycmVzcG9uZGluZyBzZWN0aW9u
cy4KCiAgIE1haW4gY2hhbmdlIGZyb20gMDUgdG8gMDY6CgogICAgICAgICAtICBTZWN0aW9uIDgu
MTogcmVmZXJlbmNlIHRvIHNlY3Rpb24gMjAgaXMgY2hhbmdlZCB0byBzZWN0aW9uCiAgICAgICAg
ICAgIDE1LgoKICAgTWFpbiBjaGFuZ2VzIGZyb20gMDYgdG8gMDc6CgogICAgICAgICAtICBTbyBt
YW55IGNoYW5nZXMgaW4gdGhpcyBtb2RpZmljYXRpb24uIFdlIHN1Z2dlc3QgdG8gdHJhY2sKICAg
ICAgICAgICAgaHR0cDovL3d3dy5pZXRmLm9yZy9tYWlsYXJjaGl2ZS93ZWIvc2F2aS9jdXJyZW50
L21zZzAxNTQzLmh0CiAgICAgICAgICAgIG1sLiBDaGFuZ2VzIGFyZSBtYWRlIGFjY29yZGluZyB0
byB0aGUgY29tbWVudHMuCgogICBNYWluIGNoYW5nZXMgZnJvbSAwNyB0byAwOCwwOToKCiAgICAg
ICAgIC0gIFRoZSBtb2RpZmljYXRpb25zIGFyZSBtYWRlIGFjY29yZGluZyB0byB0aGUgY29tbWVu
dHMgZnJvbQogICAgICAgICAgICBKZWFuLU1pY2hlbCBDb21iZXMuCgogICBNYWluIGNoYW5nZXMg
ZnJvbSAwOSB0byAxMToKCiAgICAgICAgIC0gIEROQSBpc3N1ZXMKCgoKCgoKCkJpICAgICAgICAg
ICAgICAgICAgIEV4cGlyZXMgU2VwdGVtYmVyIDE2LCAyMDEyICAgICAgICAgICAgICBbUGFnZSAy
OF0KDAo=
--f46d0445179bd82da204bb5681e8--

From sm@resistor.net  Fri Mar 16 08:10: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 38AF121F8672 for <ietf@ietfa.amsl.com>; Fri, 16 Mar 2012 08:10:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.63
X-Spam-Level: 
X-Spam-Status: No, score=-102.63 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 22Gm5Y8C0l8r for <ietf@ietfa.amsl.com>; Fri, 16 Mar 2012 08:09:59 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 163C121F8666 for <ietf@ietf.org>; Fri, 16 Mar 2012 08:09:58 -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 q2GF9rBu017837 for <ietf@ietf.org>; Fri, 16 Mar 2012 08:09:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1331910597; i=@resistor.net; bh=cWbUyJZ2CjMntxJsh/gkKODBIGn0Egx1HpK+lni5Qkg=; h=Date:To:From:Subject:Cc; b=bQQuSIWWKtypKvp8cyE/igG5qJsCYNO8TjkqWjD1PBP4jjxiucqqL7U5K+38UJ3AJ Y3JE9bKHllHQ7QMc5RIQl4KbnzQCgudeOjJeCnLXOTItm2MQUiH5GzvIgxZ1lTL5A2 8B1ikPMMhyghzAtHO5Bl2usSPU7F0kdo/ZsZidpc=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1331910597; i=@resistor.net; bh=cWbUyJZ2CjMntxJsh/gkKODBIGn0Egx1HpK+lni5Qkg=; h=Date:To:From:Subject:Cc; b=yefHCIV0nO6thpuGRQPKtzcjFWdwR/KlpcczTx7uFSC/0hXNJyFq9aq3q0c/ET966 1B25jy0KZZThFh1rwhDHEFUkalLadbf3Cie1O4hOondCuaPt4mSWsw27YuPjWEEmuO 082CyKWpLgYGh1nEYbtVmM4jo1jeGGj/Z4H1I728=
Message-Id: <6.2.5.6.2.20120316075610.0a6a1cd0@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 16 Mar 2012 07:58:15 -0700
To: ietf@ietf.org
From: SM <sm@resistor.net>
Subject: Bad ABNF
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Mar 2012 15:10:01 -0000

http://www.youtube.com/watch?v=LbK-g8tKnoc

Regards,
-sm


From stbryant@cisco.com  Fri Mar 16 08:12:13 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 24EEE21F8672 for <ietf@ietfa.amsl.com>; Fri, 16 Mar 2012 08:12:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.276
X-Spam-Level: 
X-Spam-Status: No, score=-110.276 tagged_above=-999 required=5 tests=[AWL=-0.277, BAYES_00=-2.599, J_CHICKENPOX_15=0.6, 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 41zV+XlvwKZu for <ietf@ietfa.amsl.com>; Fri, 16 Mar 2012 08:12:12 -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 505D921F86CA for <ietf@ietf.org>; Fri, 16 Mar 2012 08:12:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=stbryant@cisco.com; l=1582; q=dns/txt; s=iport; t=1331910732; x=1333120332; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=gEcMyN/TZ4xTn3M0xqkbcP6dR8ZJa7Jyjws/+2dKvic=; b=lXumye2mbqEgH+gmEcR+ILQky4dkAEZxjBlPFjhkn+9+LtX8gg+K7KIi wzQXFBXYsR0o9R3WFK7qA15/e8eMCtRRLWAOSVkJtBcpn3g4smS4rh37J cniGJAFJEiZc5D6fVAQiKI2vWLqGKCxap8fjHJWLYtvkmKYsvMGDGWuUd s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAJZXY0+Q/khR/2dsb2JhbABCtjeBB4IJAQEBBBIBAiNBDAQLFQECCRoLDwIQNgYNAQUCAQEeh2iac4M8EJtaiVOHKgSSL4M3iy6DEYECZoJm
X-IronPort-AV: E=Sophos;i="4.73,598,1325462400"; d="scan'208";a="68664516"
Received: from ams-core-1.cisco.com ([144.254.72.81]) by ams-iport-2.cisco.com with ESMTP; 16 Mar 2012 15:12:11 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by ams-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id q2GFC8HT015766; Fri, 16 Mar 2012 15:12:11 GMT
Received: from stbryant-mac2.local (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id q2GFC6Re006632; Fri, 16 Mar 2012 15:12:07 GMT
Message-ID: <4F635846.60505@cisco.com>
Date: Fri, 16 Mar 2012 15:12:06 +0000
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: "t.petch" <daedulus@btconnect.com>
Subject: Re: Last Call:<draft-betts-itu-oam-ach-code-point-03.txt>(Allocationof an Associated Channel Code Point for Use by ITU-T Ethernet basedOAM) to Informational RFC
References: <CAAHpaZ=JrKVKHZ0xkK-nszFDf-ttVNoi1p9iZiWa93vKuiNxZA@mail.gmail.com> <4F60BF02.1010507@cisco.com> <009b01cd0351$52d5f3c0$4001a8c0@gateway.2wire.net>
In-Reply-To: <009b01cd0351$52d5f3c0$4001a8c0@gateway.2wire.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Fangyu Li <fangyuli1999@gmail.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Mar 2012 15:12:13 -0000

On 16/03/2012 08:46, t.petch wrote:
> ----- Original Message -----
> From: "Stewart Bryant"<stbryant@cisco.com>
> To: "Fangyu Li"<fangyuli1999@gmail.com>
> Cc:<lifang@catr.cn>;<ietf@ietf.org>
> Sent: Wednesday, March 14, 2012 4:53 PM
>> On 14/03/2012 13:36, Fangyu Li wrote:
>>> I support the allocation of an ACH codepoint to G.8113.1.
>>> For G.8113.1 had reached the technical and industry maturity to be
>>> assigned a code point, the codepoint allocation from IETF should allow
>>> the ITU-T to progress refinements to G.8113.1 such that it could
>>> satisfy all the functional requirements defined in RFC 5860.
>> Please can you tell me version of the G.8113.1 text one would
>> need to implement to be able to seamlessly interwork with the
>> equipment that has already been been deployed?
> Stewart
>
> I am sure you already know the answer to that from posts made to the mpls list,
> where we have been told that there is currently an extensive deployment
> ('running code') using an experimental value (interesting that there is a last
> call just ending seeking to exterminate such practice, at least for application
> protocols) and that the wish is to move to a standards-based value which will,
> perforce, be a different value.
>
> Tom Petch

Tom,

I don't think you understood my question.

There are several version of the G.8113.1 text in circulation within
the ITU-T. I was asking which version accurately describes the
deployed protocol.

I would be interested to also know what ACh Type it is actually running
on.

Stewart



From dworley@avaya.com  Fri Mar 16 08:48:02 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 CA92321F8745 for <ietf@ietfa.amsl.com>; Fri, 16 Mar 2012 08:48:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.411
X-Spam-Level: 
X-Spam-Status: No, score=-103.411 tagged_above=-999 required=5 tests=[AWL=0.188, 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 PiUpozZeum0t for <ietf@ietfa.amsl.com>; Fri, 16 Mar 2012 08:48: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 9F67021F86A3 for <ietf@ietf.org>; Fri, 16 Mar 2012 08:48:01 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AroLAGFfY0+HCzI1/2dsb2JhbABCtSIEAgKBDYEHggkBAQEBAgESKEQLAgEIDQghEDIlAQEEARIIGodjBQudYY5PjV2LYxOEJGMEm3SKGYMC
X-IronPort-AV: E=Sophos;i="4.73,598,1325480400"; d="scan'208";a="297519644"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by de307622-de-outbound.net.avaya.com with ESMTP; 16 Mar 2012 11:48:00 -0400
Received: from unknown (HELO DC-US1HCEX4.global.avaya.com) ([135.11.52.35]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 16 Mar 2012 11:32:34 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.202]) by DC-US1HCEX4.global.avaya.com ([135.11.52.35]) with mapi; Fri, 16 Mar 2012 11:47:58 -0400
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: SM <sm@resistor.net>, "ietf@ietf.org" <ietf@ietf.org>
Date: Fri, 16 Mar 2012 11:47:02 -0400
Subject: RE: Bad ABNF
Thread-Topic: Bad ABNF
Thread-Index: Ac0DhuFobZK9XeHLTKCccANAtlyK4gABSV7L
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B22726A097C@DC-US1MBEX4.global.avaya.com>
References: <6.2.5.6.2.20120316075610.0a6a1cd0@elandnews.com>
In-Reply-To: <6.2.5.6.2.20120316075610.0a6a1cd0@elandnews.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Mar 2012 15:48:02 -0000

> From: SM [sm@resistor.net]
>=20
> http://www.youtube.com/watch?v=3DLbK-g8tKnoc

"When Mussolini was Area Director ..."

Dale

From daedulus@btconnect.com  Fri Mar 16 09:06:36 2012
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1878D21F85AC for <ietf@ietfa.amsl.com>; Fri, 16 Mar 2012 09:06:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.753
X-Spam-Level: 
X-Spam-Status: No, score=-1.753 tagged_above=-999 required=5 tests=[AWL=0.246,  BAYES_00=-2.599, J_CHICKENPOX_15=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Wt6yPxst5a4P for <ietf@ietfa.amsl.com>; Fri, 16 Mar 2012 09:06:35 -0700 (PDT)
Received: from mail.btconnect.com (c2bthomr10.btconnect.com [213.123.20.128]) by ietfa.amsl.com (Postfix) with ESMTP id 1124C21F879D for <ietf@ietf.org>; Fri, 16 Mar 2012 09:06:34 -0700 (PDT)
Received: from host86-151-41-215.range86-151.btcentralplus.com (HELO pc6) ([86.151.41.215]) by c2bthomr10.btconnect.com with SMTP id GTS22847; Fri, 16 Mar 2012 16:06:32 +0000 (GMT)
Message-ID: <02e601cd0386$3ff90dc0$4001a8c0@gateway.2wire.net>
From: "t.petch" <daedulus@btconnect.com>
To: <stbryant@cisco.com>
References: <CAAHpaZ=JrKVKHZ0xkK-nszFDf-ttVNoi1p9iZiWa93vKuiNxZA@mail.gmail.com> <4F60BF02.1010507@cisco.com> <009b01cd0351$52d5f3c0$4001a8c0@gateway.2wire.net> <4F635846.60505@cisco.com>
Subject: Re: Last Call:<draft-betts-itu-oam-ach-code-point-03.txt>(Allocationof an Associated Channel Code Point for Use by ITU-T Ethernet basedOAM) to Informational RFC
Date: Fri, 16 Mar 2012 16:05:30 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Mirapoint-IP-Reputation: reputation=Fair-1, source=Queried, refid=tid=0001.0A0B0303.4F636508.001D, actions=tag
X-Junkmail-Premium-Raw: score=9/50, refid=2.7.2:2012.3.16.131537:17:9.975, ip=86.151.41.215, rules=__HAS_MSGID, __OUTLOOK_MSGID_1, __SANE_MSGID, __TO_MALFORMED_2, __TO_NO_NAME, __BOUNCE_CHALLENGE_SUBJ, __BOUNCE_NDR_SUBJ_EXEMPT, __SUBJ_ALPHA_END, __MIME_VERSION, __CT, CT_TP_8859_1, __CT_TEXT_PLAIN, __CTE, __HAS_X_PRIORITY, __HAS_MSMAIL_PRI, __HAS_X_MAILER, USER_AGENT_OE, __OUTLOOK_MUA_1, __USER_AGENT_MS_GENERIC, __ANY_URI, CN_TLD, __FRAUD_BODY_WEBMAIL, __URI_NO_WWW, __URI_NO_PATH, BODY_SIZE_3000_3999, __MIME_TEXT_ONLY, RDNS_GENERIC_POOLED, HTML_00_01, HTML_00_10, BODY_SIZE_5000_LESS, RDNS_SUSP_GENERIC, __OUTLOOK_MUA, RDNS_SUSP, __FRAUD_WEBMAIL, BODY_SIZE_7000_LESS
X-Junkmail-Status: score=10/50, host=c2bthomr10.btconnect.com
X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A0B020D.4F636508.019B,ss=1,re=0.000,fgs=0, ip=0.0.0.0, so=2011-07-25 19:15:43, dmn=2011-05-27 18:58:46, mode=multiengine
X-Junkmail-IWF: false
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Mar 2012 16:06:36 -0000

----- Original Message -----
From: "Stewart Bryant" <stbryant@cisco.com>
To: "t.petch" <daedulus@btconnect.com>
Cc: "Fangyu Li" <fangyuli1999@gmail.com>; <ietf@ietf.org>
Sent: Friday, March 16, 2012 4:12 PM
Subject: Re: Last Call:<draft-betts-itu-oam-ach-code-point-03.txt>(Allocationof
an Associated Channel Code Point for Use by ITU-T Ethernet basedOAM) to
Informational RFC


> On 16/03/2012 08:46, t.petch wrote:
> > ----- Original Message -----
> > From: "Stewart Bryant"<stbryant@cisco.com>
> > To: "Fangyu Li"<fangyuli1999@gmail.com>
> > Cc:<lifang@catr.cn>;<ietf@ietf.org>
> > Sent: Wednesday, March 14, 2012 4:53 PM
> >> On 14/03/2012 13:36, Fangyu Li wrote:
> >>> I support the allocation of an ACH codepoint to G.8113.1.
> >>> For G.8113.1 had reached the technical and industry maturity to be
> >>> assigned a code point, the codepoint allocation from IETF should allow
> >>> the ITU-T to progress refinements to G.8113.1 such that it could
> >>> satisfy all the functional requirements defined in RFC 5860.
> >> Please can you tell me version of the G.8113.1 text one would
> >> need to implement to be able to seamlessly interwork with the
> >> equipment that has already been been deployed?
> > Stewart
> >
> > I am sure you already know the answer to that from posts made to the mpls
list,
> > where we have been told that there is currently an extensive deployment
> > ('running code') using an experimental value (interesting that there is a
last
> > call just ending seeking to exterminate such practice, at least for
application
> > protocols) and that the wish is to move to a standards-based value which
will,
> > perforce, be a different value.
> >
> > Tom Petch
>
> Tom,
>
> I don't think you understood my question.
>
> There are several version of the G.8113.1 text in circulation within
> the ITU-T. I was asking which version accurately describes the
> deployed protocol.

Stewart

One of the e-mails I had in mind was that of Huub Helvoort last December where
he said
"The draft recommendation G.8113.1 is stable, there have been no major technical
changes since it was sent to the IETF (when it still had the draft name G.tpoam)
attache to liaison: https://datatracker.ietf.org/liaison/983/
This is also the status I reported when we did discuss this during IETF82 in
Taipei."

while another such e-mail is that of Malcolm Betts in January where he said
"I can confirm that the draft is requesting a code point for the version of
G.8113.1 that was forwarded to WTSA by SG 15, this is the same as the
draft that was determined in February 2011, I am not anticipating any
changes prior to the approval decision at WTSA.  None of the changes in
G.8113.1 that were anticipated in draft-betts-itu-oam-ach-code-point-01
were implemented,  I will post a new version
draft-betts-itu-oam-ach-code-point to correctly reflect the content and
title on G.8113.1 and respond to the other questions later this week."

I was thinking that that was enough reassurance about the protocol and its
stability.

I agree that the documents as liaised to us specify that special value of XXXX
but we were told, on the mpls list, that an experimental value was in use, ie
one that fell within the remit of section 10 of RFC5586, which, again, I took to
be sufficient information.

Tom Petch

> I would be interested to also know what ACh Type it is actually running
> on.
>
> Stewart
>
>
>
>


From johnl@iecc.com  Fri Mar 16 10:40:22 2012
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A89F621E8043 for <ietf@ietfa.amsl.com>; Fri, 16 Mar 2012 10:40:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.59
X-Spam-Level: 
X-Spam-Status: No, score=-110.59 tagged_above=-999 required=5 tests=[AWL=0.609, 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 uOvxs3wTnvR2 for <ietf@ietfa.amsl.com>; Fri, 16 Mar 2012 10:40:22 -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 9899821E8012 for <ietf@ietf.org>; Fri, 16 Mar 2012 10:40:21 -0700 (PDT)
Received: (qmail 97466 invoked from network); 16 Mar 2012 17:40:15 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 16 Mar 2012 17:40:15 -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=4f637af2.xn--hew.k1203; i=johnl@user.iecc.com; bh=GwFIHTbUX3JYI7wVsx4UC8nlJMU4NAi7x+1ngXMbcwo=; b=jw5mmj/U2p3zy33RaDdPoKUw6nwfo+d8YGlzN9Sm9H+CbGm/4Zs8gahEG+p0bKj3eRUCiNmZ563n4JZpvbuIUT76f/irvzUGMgNGWuAsNn7pSQW/PoPnqrZhaKCKOVq+spPQ7i3z3LUXiGu05dix+Ll8vet+/2KaPgvfUchOZo0=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 16 Mar 2012 17:39:40 -0000
Message-ID: <20120316173940.31467.qmail@joyce.lan>
From: "John Levine" <johnl@iecc.com>
To: ietf@ietf.org
Subject: Re: Issues relating to managing a mailing list...
In-Reply-To: <4F6236E6.5030303@nostrum.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, 16 Mar 2012 17:40:22 -0000

In article <4F6236E6.5030303@nostrum.com> you write:
>The current plan is to investigate both a web based archive access 
>mechanism and an IMAP based one.

Don't forget NNTP (RFC 3977).  I use it locally, deliver list mail to
local per-list newsgroups, and it works really well.

R's,
John

From kpfleming@digium.com  Fri Mar 16 10:59:55 2012
Return-Path: <kpfleming@digium.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6413F21F8768 for <ietf@ietfa.amsl.com>; Fri, 16 Mar 2012 10:59:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.556
X-Spam-Level: 
X-Spam-Status: No, score=-106.556 tagged_above=-999 required=5 tests=[AWL=0.043, 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 d-BAf7s-i6-J for <ietf@ietfa.amsl.com>; Fri, 16 Mar 2012 10:59:54 -0700 (PDT)
Received: from mail.digium.com (mail.digium.com [216.207.245.2]) by ietfa.amsl.com (Postfix) with ESMTP id C9F0621F8764 for <ietf@ietf.org>; Fri, 16 Mar 2012 10:59:54 -0700 (PDT)
Received: from [10.24.55.203] (helo=zimbra.hsv.digium.com) by mail.digium.com with esmtp (Exim 4.69) (envelope-from <kpfleming@digium.com>) id 1S8bRR-0007ss-L9 for ietf@ietf.org; Fri, 16 Mar 2012 12:59:53 -0500
Received: from localhost (localhost.localdomain [127.0.0.1]) by zimbra.hsv.digium.com (Postfix) with ESMTP id A3F8AD8011 for <ietf@ietf.org>; Fri, 16 Mar 2012 12:59:53 -0500 (CDT)
Received: from zimbra.hsv.digium.com ([127.0.0.1]) by localhost (zimbra.hsv.digium.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9FghK81wfdXu for <ietf@ietf.org>; Fri, 16 Mar 2012 12:59:49 -0500 (CDT)
Received: from [10.24.250.46] (unknown [10.24.250.46]) by zimbra.hsv.digium.com (Postfix) with ESMTPSA id DD893D8004 for <ietf@ietf.org>; Fri, 16 Mar 2012 12:59:49 -0500 (CDT)
Message-ID: <4F637F95.6020806@digium.com>
Date: Fri, 16 Mar 2012 12:59:49 -0500
From: "Kevin P. Fleming" <kpfleming@digium.com>
Organization: Digium, Inc.
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Issues relating to managing a mailing list...
References: <20120316173940.31467.qmail@joyce.lan>
In-Reply-To: <20120316173940.31467.qmail@joyce.lan>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Mar 2012 17:59:55 -0000

On 03/16/2012 12:39 PM, John Levine wrote:
> In article<4F6236E6.5030303@nostrum.com>  you write:
>> The current plan is to investigate both a web based archive access
>> mechanism and an IMAP based one.
>
> Don't forget NNTP (RFC 3977).  I use it locally, deliver list mail to
> local per-list newsgroups, and it works really well.

IIRC, mailman has native support for archiving messages via NNTP as well.

-- 
Kevin P. Fleming
Digium, Inc. | Director of Software Technologies
Jabber: kfleming@digium.com | SIP: kpfleming@digium.com | Skype: kpfleming
445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
Check us out at www.digium.com & www.asterisk.org

From stpeter@stpeter.im  Fri Mar 16 11:32:52 2012
Return-Path: <stpeter@stpeter.im>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5646021F8697 for <ietf@ietfa.amsl.com>; Fri, 16 Mar 2012 11:32:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.397
X-Spam-Level: 
X-Spam-Status: No, score=-102.397 tagged_above=-999 required=5 tests=[AWL=-0.398, BAYES_00=-2.599, J_CHICKENPOX_15=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vxt7OD0QvTIY for <ietf@ietfa.amsl.com>; Fri, 16 Mar 2012 11:32:51 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id A25C721F8675 for <ietf@ietf.org>; Fri, 16 Mar 2012 11:32:51 -0700 (PDT)
Received: from squire.local (unknown [64.101.72.114]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id DBF9E40058; Fri, 16 Mar 2012 12:45:19 -0600 (MDT)
Message-ID: <4F638751.2000909@stpeter.im>
Date: Fri, 16 Mar 2012 12:32:49 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.5; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: "t.petch" <daedulus@btconnect.com>
Subject: Re: Last Call: <draft-ietf-appsawg-xdash-03.txt> (Deprecating Use of the"X-" Prefix in Application Protocols) to Best Current Practice
References: <20120301184750.21152.93044.idtracker@ietfa.amsl.com> <028601cd00fc$f5ba5380$4001a8c0@gateway.2wire.net> <4F5FC7DC.5040203@stpeter.im> <01dc01cd035b$b2c0cee0$4001a8c0@gateway.2wire.net>
In-Reply-To: <01dc01cd035b$b2c0cee0$4001a8c0@gateway.2wire.net>
X-Enigmail-Version: 1.4
OpenPGP: url=https://stpeter.im/stpeter.asc
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Mark Nottingham <mnot@mnot.net>, ietf@ietf.org, Dave CROCKER <dcrocker@bbiw.net>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Mar 2012 18:32:52 -0000

On 3/16/12 4:00 AM, t.petch wrote:
> ----- Original Message -----
> From: "Peter Saint-Andre" <stpeter@stpeter.im>
> To: "t.petch" <daedulus@btconnect.com>
> Cc: <ietf@ietf.org>; "Dave CROCKER" <dcrocker@bbiw.net>; "Mark Nottingham"
> <mnot@mnot.net>
> Sent: Tuesday, March 13, 2012 11:19 PM
> 
>> On 3/13/12 3:37 AM, t.petch wrote:
>>> I am surprised at the lack of comment on this I-D on its use of terminology.
> I
>>> have seen and learnt from many discussions on this list that have teased out
>>> what concept it is we are really talking about (e.g. identity v identifier)
> and
>>> this I-D seems somewhat weak in that regard.
>>>
>>> Thus the summary
>>
>> Clarifying quesiton: do you mean the abstract? (Yes)
>>
>>> talks of
>>> 'parameters by prefixing the latter '
>>
>> http://tools.ietf.org/html/draft-ietf-appsawg-xdash-04 does not contain
>> that string. The discussions on this list and with the IESG have led to
>> some changes in the text. The Abstract now reads:
>>
>>    Historically, designers and implementers of application protocols
>>    have often distinguished between "standard" and "non-standard"
>>    parameters by prefixing the names of "non-standard" parameters with
>>    the string "X-" or similar constructs.  In practice, that convention
>>    causes more problems than it solves.  Therefore, this document
>>    deprecates the convention for the names of newly-defined textual
>>    parameters in application protocols.
> 
> Which I think the completely wrong direction in which to make changes:-(
> 
> I might create a private parameter and decide that it should be named the X-Spam
> parameter, which can then take values, which may appear in the textual header,
> of one of
> Signs-of-Spam-Detected
> Signs-of-Spam-Not-Detected
> 
> What you are saying is that because I have named it X-, this is unacceptable.
> What I think that you are assuming, erroneously, is that the value that appears
> in the textual header of the protocol is always identical to the name or at
> least starts with that name.

As I said in my previous reply, this document says absolutely nothing
about the values of parameters, only about the names of parameters. I
must admit that I an confused as to why you construe otherwise. If
indeed strings leak out of the space of parameter names into the space
of parameter values, as in your example, that is purely a byproduct of
the leakage, and does not change the fact that the recommendations in
this I-D apply to parameter names.

> Most people will probably understand your wording, but I still find it sloppy
> for an RFC (given the way that this list has dissected similar topics in the
> past).

Suggested text is always welcome.

Peter

-- 
Peter Saint-Andre
https://stpeter.im/



From bob.hinden@gmail.com  Fri Mar 16 12:49:19 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 B90B321E8015; Fri, 16 Mar 2012 12:49: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 XzbYaRYuvzzz; Fri, 16 Mar 2012 12:49:19 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D16ED21F8610; Fri, 16 Mar 2012 12:49:18 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: IAOC Chair <bob.hinden@gmail.com>
To: IETF Announcement List <ietf-announce@ietf.org>
Subject: Query to the community -- An additional IETF Meeting event?
X-Test-IDTracker: no
X-IETF-IDTracker: 4.00
Message-ID: <20120316194918.18453.89483.idtracker@ietfa.amsl.com>
Date: Fri, 16 Mar 2012 12:49:18 -0700
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Mar 2012 19:49:19 -0000

The IESG and IAOC are considering an addition to the IETF meeting week, and=
 we would like your views before we develop the idea further.

At NANOG, there is a Beer and Gear reception one evening.  There are exhibi=
tor tables with product vendors (hardware and software) and service provide=
rs (registries, registrars, ISPs, ESPs, etc.) and anyone else interested in=
 face time with NANOG participants. They show their equipment and services.=
  There is bar in the center of the room serving beer, wine, and soft drink=
s. There are hors d'oeuvres scattered around the room.

  QUESTION:  What do you think about doing a Beer and Gear style
             of event on an evening that does not conflict with
             other IETF activities?

This would be an opportunity for free food and drink for attendees, for ven=
dors and service providers to talk with IETF participants, and for addition=
al revenue to the IETF.  Obviously, attendance would be optional.

Technical people are at the tables, not sales or marketing staff.  Vendors =
know that the audience is very technical, so they send the people that can =
communicate with that audience.

We would charge for exhibit tables, to raise additional funds for the IETF.=
 A stronger base of opportunities for IETF sponsorship distributes our fund=
ing, making it less fragile; this could make it less likely that we would h=
ave last-minute scrambles for additional sponsors, including hosts. A succe=
ssful Beer-and-Gear like event would not solve this but it would help.

In the past, the IETF has avoided vendor exhibits and demonstrations.  Howe=
ver it is clear that NANOG has found a balance that works and that NANOG pa=
rticipants and the vendors consider the event valuable.  We believe this co=
uld translate well to the IETF.

We are considering some test events, hopefully to be held at IETF 84 (Vanco=
uver, July 2012) and IETF 85 (Atlanta, November 2012).

The kinds of evaluation criteria we are considering could include:

- Did participants enjoy the event?

- Did vendors consider the event successful?

- Did the IETF raise additional funds?

- Did the event "steal" potential sponsors away from other
  aspects of the meeting?

So, what do you think?  Is this something that we should try?

Please respond on the ietf@ietf.org mail list.

On behalf of the IESG and the IAOC,

Russ Housley
Bob Hinden

From framefritti@gmail.com  Fri Mar 16 13:30:38 2012
Return-Path: <framefritti@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5281821F85AA for <ietf@ietfa.amsl.com>; Fri, 16 Mar 2012 13:30:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.799
X-Spam-Level: 
X-Spam-Status: No, score=-3.799 tagged_above=-999 required=5 tests=[AWL=-0.200, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dNfuU-jRcwJ1 for <ietf@ietfa.amsl.com>; Fri, 16 Mar 2012 13:30:37 -0700 (PDT)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id 6C63A21F85A8 for <ietf@ietf.org>; Fri, 16 Mar 2012 13:30:37 -0700 (PDT)
Received: by iazz13 with SMTP id z13so6870844iaz.31 for <ietf@ietf.org>; Fri, 16 Mar 2012 13:30: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 :content-type:content-transfer-encoding; bh=hviAJI9Rii+/p0sSUlFrls7RU8jF3+Bt29P63CYPJzY=; b=oXyDY63zUK/kgKO+IfHtiyR9vVhep5UU0FkvlgP509Js9r+fqZph6W+HIrWBAfLpE+ POHZ1ouCi1yAfH04prrhH6zazNSoEjr+p8LTjEvxs/FemxUhLSCIUXJuQJdXWj7Eaioh vEwh5T26e7PGjvGenYeekN4GSWrWKnBE+ygBTw+ZFBa4Y3bq0YYqYO4qexY1iANAlTHb L2Ftj5QGn+EghXbWKm5wBrZIy6RfKPGHejs/q1JBM2HZnS9NE4QDDioigP1joYPj00G4 zpnQQ7fdGUYXvXwAzbfTzW5zaPs66wuMKfimj4YX7CY3KVTquuF85ZuBnzpABPjSsfnG 0TOw==
MIME-Version: 1.0
Received: by 10.50.219.170 with SMTP id pp10mr427875igc.49.1331929834695; Fri, 16 Mar 2012 13:30:34 -0700 (PDT)
Received: by 10.231.185.219 with HTTP; Fri, 16 Mar 2012 13:30:34 -0700 (PDT)
In-Reply-To: <20120316194918.18453.89483.idtracker@ietfa.amsl.com>
References: <20120316194918.18453.89483.idtracker@ietfa.amsl.com>
Date: Fri, 16 Mar 2012 21:30:34 +0100
Message-ID: <CABSMSPVswLpi_qgaEPEfjissmw5JSaC3uNF5z2_0Zw4N71KgHw@mail.gmail.com>
Subject: Re: Query to the community -- An additional IETF Meeting event?
From: Riccardo Bernardini <framefritti@gmail.com>
To: ietf@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Mar 2012 20:30:38 -0000

On Fri, Mar 16, 2012 at 8:49 PM, IAOC Chair <bob.hinden@gmail.com> wrote:
>
> The IESG and IAOC are considering an addition to the IETF meeting week, a=
nd we would like your views before we develop the idea further.
>
> At NANOG, there is a Beer and Gear reception one evening. =A0There are ex=
hibitor tables with product vendors (hardware and software) and service pro=
viders (registries, registrars, ISPs, ESPs, etc.) and anyone else intereste=
d in face time with NANOG participants. They show their equipment and servi=
ces. =A0There is bar in the center of the room serving beer, wine, and soft=
 drinks. There are hors d'oeuvres scattered around the room.
>
> =A0QUESTION: =A0What do you think about doing a Beer and Gear style
> =A0 =A0 =A0 =A0 =A0 =A0 of event on an evening that does not conflict wit=
h
> =A0 =A0 =A0 =A0 =A0 =A0 other IETF activities?
>
> This would be an opportunity for free food and drink for attendees, for v=
endors and service providers to talk with IETF participants, and for additi=
onal revenue to the IETF. =A0Obviously, attendance would be optional.
>
> Technical people are at the tables, not sales or marketing staff. =A0Vend=
ors know that the audience is very technical, so they send the people that =
can communicate with that audience.
>
> We would charge for exhibit tables, to raise additional funds for the IET=
F. A stronger base of opportunities for IETF sponsorship distributes our fu=
nding, making it less fragile; this could make it less likely that we would=
 have last-minute scrambles for additional sponsors, including hosts. A suc=
cessful Beer-and-Gear like event would not solve this but it would help.
>
> In the past, the IETF has avoided vendor exhibits and demonstrations. =A0=
However it is clear that NANOG has found a balance that works and that NANO=
G participants and the vendors consider the event valuable. =A0We believe t=
his could translate well to the IETF.
>
> We are considering some test events, hopefully to be held at IETF 84 (Van=
couver, July 2012) and IETF 85 (Atlanta, November 2012).
>
> The kinds of evaluation criteria we are considering could include:
>
> - Did participants enjoy the event?
>
> - Did vendors consider the event successful?
>
> - Did the IETF raise additional funds?
>
> - Did the event "steal" potential sponsors away from other
> =A0aspects of the meeting?
>
> So, what do you think? =A0Is this something that we should try?
>
> Please respond on the ietf@ietf.org mail list.
>
> On behalf of the IESG and the IAOC,
>
> Russ Housley
> Bob Hinden

My first gut reaction.

On the plus side:

   * This kind of event is usually fairly interesting (at least,  _I_
enjoy them and since I am a man, every man enjoys them (proof by bad
syllogism :-) )

   * The possibility of raising some more funding is interesting

On the "dubious" side

  * "on an evening that does not conflict with other IETF activities"
I did not attend many meeting so far (I began being involved just a
couple of years ago), but I remember somehow a well-packed schedule.

Anyway, in science (and engineering) experimental results rule: let's
try for a couple of meeting and let see if this can be made to work.
If you say that it works for NANOG (who are still engineers, right?),
why not for us?

Riccardo

From hartmans@mit.edu  Fri Mar 16 13:35:35 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 9CCC621F85C3; Fri, 16 Mar 2012 13:35:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.35
X-Spam-Level: 
X-Spam-Status: No, score=-103.35 tagged_above=-999 required=5 tests=[AWL=-1.085, 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 ydTZRu9Vzxkr; Fri, 16 Mar 2012 13:35:34 -0700 (PDT)
Received: from permutation-city.suchdamage.org (permutation-city.suchdamage.org [69.25.196.28]) by ietfa.amsl.com (Postfix) with ESMTP id C4FB621F85C2; Fri, 16 Mar 2012 13:35:33 -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 B4C0E203BA; Fri, 16 Mar 2012 16:35:02 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 801C14767; Fri, 16 Mar 2012 16:35:17 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: IAOC Chair <bob.hinden@gmail.com>
Subject: Trade show at IETF
References: <20120316194918.18453.89483.idtracker@ietfa.amsl.com>
Date: Fri, 16 Mar 2012 16:35:17 -0400
In-Reply-To: <20120316194918.18453.89483.idtracker@ietfa.amsl.com> (IAOC Chair's message of "Fri, 16 Mar 2012 12:49:18 -0700")
Message-ID: <tslhaxocmii.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: iaoc@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Mar 2012 20:35:35 -0000

>>>>> "IAOC" == IAOC Chair <bob.hinden@gmail.com> writes:

    IAOC>   QUESTION: What do you think about doing a Beer and Gear
    IAOC> style of event on an evening that does not conflict with other
    IAOC> IETF activities?

I think that hallway conversations, private meetings and other
activities that people have already filled Sunday after the
reception,Monday, Thursday and Friday with are more important.  I think
this would make an already crowded event more crowded and while it might
be useful would detract from other more important uses of the time.
So, I am not generally supportive of this idea.

From andy@netconfcentral.org  Fri Mar 16 13:53:09 2012
Return-Path: <andy@netconfcentral.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 30E6A21E807A for <ietf@ietfa.amsl.com>; Fri, 16 Mar 2012 13:53:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.516
X-Spam-Level: 
X-Spam-Status: No, score=-2.516 tagged_above=-999 required=5 tests=[AWL=0.083,  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 UYua+LJEYGhU for <ietf@ietfa.amsl.com>; Fri, 16 Mar 2012 13:53:08 -0700 (PDT)
Received: from omr15.networksolutionsemail.com (omr15.networksolutionsemail.com [205.178.146.65]) by ietfa.amsl.com (Postfix) with ESMTP id 23A5A21E8024 for <ietf@ietf.org>; Fri, 16 Mar 2012 13:53:07 -0700 (PDT)
Received: from cm-omr12 (mail.networksolutionsemail.com [205.178.146.50]) by omr15.networksolutionsemail.com (8.13.8/8.13.8) with ESMTP id q2GKr4CT010843 for <ietf@ietf.org>; Fri, 16 Mar 2012 16:53:07 -0400
Authentication-Results: cm-omr12 smtp.user=andy@andybierman.com; auth=pass (PLAIN)
X-Authenticated-UID: andy@andybierman.com
Received: from [75.84.164.152] ([75.84.164.152:53903] helo=[192.168.0.9]) by cm-omr12 (envelope-from <andy@netconfcentral.org>) (ecelerity 2.2.2.41 r(31179/31189)) with ESMTPA id E1/0B-16767-238A36F4; Fri, 16 Mar 2012 16:53:07 -0400
Message-ID: <4F63A836.4010207@netconfcentral.org>
Date: Fri, 16 Mar 2012 13:53:10 -0700
From: Andy Bierman <andy@netconfcentral.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: Sam Hartman <hartmans-ietf@mit.edu>
Subject: Re: Trade show at IETF
References: <20120316194918.18453.89483.idtracker@ietfa.amsl.com> <tslhaxocmii.fsf@mit.edu>
In-Reply-To: <tslhaxocmii.fsf@mit.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: iaoc@ietf.org, IAOC Chair <bob.hinden@gmail.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Mar 2012 20:53:09 -0000

On 03/16/2012 01:35 PM, Sam Hartman wrote:
>>>>>> "IAOC" == IAOC Chair<bob.hinden@gmail.com>  writes:
>
>      IAOC>    QUESTION: What do you think about doing a Beer and Gear
>      IAOC>  style of event on an evening that does not conflict with other
>      IAOC>  IETF activities?
>
> I think that hallway conversations, private meetings and other
> activities that people have already filled Sunday after the
> reception,Monday, Thursday and Friday with are more important.  I think
> this would make an already crowded event more crowded and while it might
> be useful would detract from other more important uses of the time.
> So, I am not generally supportive of this idea.
>
>

NANOG has network operators as the audience but the IETF has a more mixed audience.
I support ideas to raise money, and I would go to this event, out of curiosity.
I'm not looking to buy any networking equipment though.

I would actually like more lunch-time lectures and discussions.
(Maybe M, T, and Th so WG Chairs lunch on W does not conflict).
Perhaps vendors or researchers would be willing to make a donation
to get one of those lunch slots?


Andy

From fred@cisco.com  Fri Mar 16 14:04:06 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 8E9BA21E800C for <ietf@ietfa.amsl.com>; Fri, 16 Mar 2012 14:04:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.362
X-Spam-Level: 
X-Spam-Status: No, score=-110.362 tagged_above=-999 required=5 tests=[AWL=0.237, 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 HjsvgrUC1JaH for <ietf@ietfa.amsl.com>; Fri, 16 Mar 2012 14:04:05 -0700 (PDT)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) by ietfa.amsl.com (Postfix) with ESMTP id BAB2421F8599 for <ietf@ietf.org>; Fri, 16 Mar 2012 14:04:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fred@cisco.com; l=3450; q=dns/txt; s=iport; t=1331931845; x=1333141445; h=mime-version:subject:from:in-reply-to:date:message-id: references:to:content-transfer-encoding; bh=qlSNPz5WWoRNpwzgouwDuNkXviHQy2bQYQioFn5BqYk=; b=fqPrRDHzY1ShVYFwzfYMZU/3b7SprO4b5yfqvdqIOfjGB5+v8+nxYKTA N9LXC6QceE79pYVbATbY9yqf+k/Gygje2BlfZGsBxJRpCTCxQI9DoWpoc zu4VbRBKpjy/PApbQnr15qxgkVi67n++IHOvkqwVNNTdYAMBa7jo5bCYW U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAKKqY0+tJV2a/2dsb2JhbABCtjqBB4IJAQEBAwEOBAEnJwQKGgtGVwYTFA6HYwWaSZ8jikaFVGMEhSKDNI0QhWyIU4FogwaBPA
X-IronPort-AV: E=Sophos;i="4.73,599,1325462400"; d="scan'208";a="67166596"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by rcdn-iport-5.cisco.com with ESMTP; 16 Mar 2012 21:03:47 +0000
Received: from stealth-10-32-244-218.cisco.com (stealth-10-32-244-218.cisco.com [10.32.244.218]) by rcdn-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id q2GL3fK6013323 for <ietf@ietf.org>; Fri, 16 Mar 2012 21:03:46 GMT
Received: from [127.0.0.1] by stealth-10-32-244-218.cisco.com (PGP Universal service); Fri, 16 Mar 2012 14:03:46 -0700
X-PGP-Universal: processed; by stealth-10-32-244-218.cisco.com on Fri, 16 Mar 2012 14:03:46 -0700
Mime-Version: 1.0 (Apple Message framework v1084)
Subject: Re: Query to the community -- An additional IETF Meeting event?
From: Fred Baker <fred@cisco.com>
In-Reply-To: <20120316194918.18453.89483.idtracker@ietfa.amsl.com>
Date: Fri, 16 Mar 2012 14:03:04 -0700
Message-Id: <CB0BE66D-26E1-492C-B84C-44F6C0449995@cisco.com>
References: <20120316194918.18453.89483.idtracker@ietfa.amsl.com>
To: IETF Discussion <ietf@ietf.org>
X-Mailer: Apple Mail (2.1084)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Mar 2012 21:04:07 -0000

The question I would ask is: "who are the vendors marketing to, and what =
are they selling?" At NANOG, that's fairly clear; companies like Cisco =
and Juniper, and resellers like Network Hardware, are selling to their =
customers, who are often technical decision makers or senior staff in =
companies that buy the stuff. The vendors that sponsor the event go home =
with business cards, which give them the opportunity for sales contacts =
after the event. Those people also come to IETF, but many others at IETF =
are from exactly those vendors, or from research and academia. I'm not =
convinced that the lead generation exercise, which is the vendor's =
reason for showing up and sponsoring the event, is going to be as useful =
for them.

Not opposed to the experiment, but not sure that we're comparing apples =
to apples.

On Mar 16, 2012, at 12:49 PM, IAOC Chair wrote:

>=20
> The IESG and IAOC are considering an addition to the IETF meeting =
week, and we would like your views before we develop the idea further.
>=20
> At NANOG, there is a Beer and Gear reception one evening.  There are =
exhibitor tables with product vendors (hardware and software) and =
service providers (registries, registrars, ISPs, ESPs, etc.) and anyone =
else interested in face time with NANOG participants. They show their =
equipment and services.  There is bar in the center of the room serving =
beer, wine, and soft drinks. There are hors d'oeuvres scattered around =
the room.
>=20
>  QUESTION:  What do you think about doing a Beer and Gear style
>             of event on an evening that does not conflict with
>             other IETF activities?
>=20
> This would be an opportunity for free food and drink for attendees, =
for vendors and service providers to talk with IETF participants, and =
for additional revenue to the IETF.  Obviously, attendance would be =
optional.
>=20
> Technical people are at the tables, not sales or marketing staff.  =
Vendors know that the audience is very technical, so they send the =
people that can communicate with that audience.
>=20
> We would charge for exhibit tables, to raise additional funds for the =
IETF. A stronger base of opportunities for IETF sponsorship distributes =
our funding, making it less fragile; this could make it less likely that =
we would have last-minute scrambles for additional sponsors, including =
hosts. A successful Beer-and-Gear like event would not solve this but it =
would help.
>=20
> In the past, the IETF has avoided vendor exhibits and demonstrations.  =
However it is clear that NANOG has found a balance that works and that =
NANOG participants and the vendors consider the event valuable.  We =
believe this could translate well to the IETF.
>=20
> We are considering some test events, hopefully to be held at IETF 84 =
(Vancouver, July 2012) and IETF 85 (Atlanta, November 2012).
>=20
> The kinds of evaluation criteria we are considering could include:
>=20
> - Did participants enjoy the event?
>=20
> - Did vendors consider the event successful?
>=20
> - Did the IETF raise additional funds?
>=20
> - Did the event "steal" potential sponsors away from other
>  aspects of the meeting?
>=20
> So, what do you think?  Is this something that we should try?
>=20
> Please respond on the ietf@ietf.org mail list.
>=20
> On behalf of the IESG and the IAOC,
>=20
> Russ Housley
> Bob Hinden


From ben@nostrum.com  Fri Mar 16 14:06:18 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 C86DF21E8024; Fri, 16 Mar 2012 14:06:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.244
X-Spam-Level: 
X-Spam-Status: No, score=-102.244 tagged_above=-999 required=5 tests=[AWL=-0.244, BAYES_00=-2.599, J_CHICKENPOX_22=0.6, 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 F7rzzQgQQQLS; Fri, 16 Mar 2012 14:06:12 -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 EBCF821E800C; Fri, 16 Mar 2012 14:06:08 -0700 (PDT)
Received: from frankenstein.test.estacado.net (vicuna-alt.estacado.net [75.53.54.121]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id q2GL6467010649 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 16 Mar 2012 16:06:06 -0500 (CDT) (envelope-from ben@nostrum.com)
Subject: Re: [Gen-art] Gen-ART LC/Telechat review of draft-reschke-http-status-308-05
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=us-ascii
From: Ben Campbell <ben@nostrum.com>
In-Reply-To: <4F5E2F65.1000706@gmx.de>
Date: Fri, 16 Mar 2012 16:06:04 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <1A884C60-A13C-4F37-AF83-3F542DE00153@nostrum.com>
References: <27FD8C7A-7636-4D60-A65E-C2B264857A0E@nostrum.com> <4F5E2F65.1000706@gmx.de>
To: Julian Reschke <julian.reschke@gmx.de>
X-Mailer: Apple Mail (2.1257)
Received-SPF: pass (nostrum.com: 75.53.54.121 is authenticated by a trusted mechanism)
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, The IETF <ietf@ietf.org>, draft-reschke-http-status-308.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, 16 Mar 2012 21:06:18 -0000

Apologies for the delayed response--the day job got in the way this =
week.

Comments inline:

On Mar 12, 2012, at 12:16 PM, Julian Reschke wrote:

> On 2012-03-12 17:15, Ben Campbell wrote:
>> I am the assigned Gen-ART reviewer for this draft. For background on
>> Gen-ART, please see the FAQ at
>> <  http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>>=20
>> Please wait for direction from your document shepherd
>> or AD before posting a new version of the draft.
>>=20
>> Document: draft-reschke-http-status-308-05
>> Reviewer: Ben Campbell=09
>> Review Date: 2012-03-12
>> IETF LC End Date: 2012-03-16
>> IESG Telechat date: 2012-03-15
>>=20
>> Summary: This draft is basically ready for publication as an =
experimental RFC. I have a few minor comments that might be worth =
considering whether they would improve the document prior to =
publication.
>>=20
>> Note: Since this draft is on a Telechat that precedes the end of the =
IETF Last Call, this review serves as both the LC and Telechat review.
>=20
> Thanks.
>=20
>> Major issues:
>>=20
>> None:
>>=20
>> Minor issues:
>>=20
>> -- General: I see some discussion about existing UA behavior, but =
nothing about what a UA should do with a 308 other than as an =
implication the fact that this is a "permanent version of 307". It's =
probably worth describing that explicitly. (Or is that what the "clients =
with link-editing capabilities" statement is intended to do?If so, does =
that cover everything?)
>=20
> The draft uses *exactly* the same words as the base spec (HTTPbis), =
except that it combines aspects of 302 (permanence) with those of 307. I =
thought that's clear enough.

I assume you meant 301 and 307.=20

I note that all of the 3XX responses have their semantics explicitly =
described in httpbis. While some reference other 3XX codes to contrast =
the behavior, none seem to be defined in terms of each other. The 301 =
definition includes an explicit note about the POST to GET behavior. The =
307 definition includes an explicit post about that behavior not being =
allowed. Section 3 of this doc does neither.

Looking further, I see that both the 301 and 307 definitions have =
different language about the response payload (they say if the method =
was not HEAD the payload SHOULD contain short  hypertext note, while =
this doc says the payload can contain one. (which I read as equivalent =
to a MAY).

Finally, both 301 and 307 contain a paragraph about automatic =
redirection for "safe" methods.

>=20
>> -- section 1, last paragraph:
>>=20
>> The fact that a 308 can't change the method is left as an implication =
of being based on 307. It would be good to state that explicitly and =
normatively here.
>=20
> We don't state it in HTTPbis either. 301, 302, and 303 are exceptions. =
See the new introduction in =
<http://greenbytes.de/tech/webdav/draft-ietf-httpbis-p2-semantics-18.html#=
rfc.section.7.3>.

HTTPbis sections 7.3.2, 7.3.3, 7.3.4, and 7.3.8 all contain explicit =
language or notes about about  GET and POST. I recognize that it is not =
stated _normatively_ in each case, but it's at least mentioned.

>=20
>> -- section 3, 1st paragraph: "Clients with link-editing capabilities =
ought to..."
>>=20
>> Should that be stated normatively?
>=20
> No. Again, this is consistent with the text in HTTPbis for status code =
302.

I concur that it says that. I find it unfortunate that HTTPbis used =
non-normative language there, but the text in this draft is consistent.

>=20
>> -- section 3, third paragraph: "The new permanent URI SHOULD be =
given..."
>>=20
>> I'm curious why that is not a MUST. Is there a reasonable (i.e. =
interoperable)  way to send a 308 _without_ a URI in the location field? =
Is the meta refresh directive something that can be used _instead_ of =
the Location header field?
>=20
> Again, consistency with RFC 2616 and HTTPbis.

You are correct.

>=20
>> -- section 4:
>>=20
>> The example uses _both_ the location field and the HTML<meta>  =
refresh directive. Is this considered a recommended practice to the =
degree you might normatively recommend it in the text?
>=20
> No, it's a hack that makes deployment easier until all UAs do the =
right thing; we don't want to make that permanent.

A comment to that effect in the text would be helpful.



From dmm@1-4-5.net  Fri Mar 16 14:13:34 2012
Return-Path: <dmm@1-4-5.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9759621E8024 for <ietf@ietfa.amsl.com>; Fri, 16 Mar 2012 14:13:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.977
X-Spam-Level: 
X-Spam-Status: No, score=-2.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZjJAbFk7xmlW for <ietf@ietfa.amsl.com>; Fri, 16 Mar 2012 14:13:33 -0700 (PDT)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id BBDB621E800C for <ietf@ietf.org>; Fri, 16 Mar 2012 14:13:33 -0700 (PDT)
Received: by ggmi1 with SMTP id i1so5305856ggm.31 for <ietf@ietf.org>; Fri, 16 Mar 2012 14:13:33 -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=lV99LaWFlpJspaEsKu2utbvUCdi855yFC2JqUgvVpwQ=; b=O+MEcsSEx+FbfL0MUN5md3eQVfnHBVRd7q556TQfBXfN+tTMN7LCuMUe3VXxzla5Mx 7uVHFGZr+clc7QRpQCvlTFc52MQi4uGfiGKNb8PoqA92LJOmWaCEp0sWALJlRToegOTN gaQsc3xptVkMu7feYWEzgWxjjAd4dNDC0DzO7CJGJFV48BE6pMv5iN5Bh4SihqQIbFel VLOvO4Zp3LJwKTEVPOOwLQlHN8YoZokphnms5diCDoflGy7vNwHaB363MRt0j/KXVkEX zg2JhVunXEMwFvI/2ICJEDmIz4ApOjGhuQMwGA105ZyPocLcsqjz3oM4xC5rlOpZFdSC 01Ug==
MIME-Version: 1.0
Received: by 10.182.124.41 with SMTP id mf9mr4404989obb.65.1331932413263; Fri, 16 Mar 2012 14:13:33 -0700 (PDT)
Received: by 10.182.73.105 with HTTP; Fri, 16 Mar 2012 14:13:33 -0700 (PDT)
X-Originating-IP: [98.234.99.22]
In-Reply-To: <CB0BE66D-26E1-492C-B84C-44F6C0449995@cisco.com>
References: <20120316194918.18453.89483.idtracker@ietfa.amsl.com> <CB0BE66D-26E1-492C-B84C-44F6C0449995@cisco.com>
Date: Fri, 16 Mar 2012 14:13:33 -0700
Message-ID: <CAHiKxWiLbA7+=Rc+fAfe2goM4dkhttSRvKBAKqBALhWKsNFh6A@mail.gmail.com>
Subject: Re: Query to the community -- An additional IETF Meeting event?
From: David Meyer <dmm@1-4-5.net>
To: Fred Baker <fred@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Gm-Message-State: ALoCoQnSFuHoCqzAqW1npM3MSNfq5E4CT8C5XrAxzviixSFf4DlLIr0dWkFmOBFuP3uKJDpaujyK
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Mar 2012 21:13:34 -0000

On Fri, Mar 16, 2012 at 2:03 PM, Fred Baker <fred@cisco.com> wrote:
> The question I would ask is: "who are the vendors marketing to, and what =
are they selling?" At NANOG, that's fairly clear; companies like Cisco and =
Juniper, and resellers like Network Hardware, are selling to their customer=
s, who are often technical decision makers or senior staff in companies tha=
t buy the stuff. The vendors that sponsor the event go home with business c=
ards, which give them the opportunity for sales contacts after the event. T=
hose people also come to IETF, but many others at IETF are from exactly tho=
se vendors, or from research and academia. I'm not convinced that the lead =
generation exercise, which is the vendor's reason for showing up and sponso=
ring the event, is going to be as useful for them.
>
> Not opposed to the experiment, but not sure that we're comparing apples t=
o apples.

While I agree Fred, what the beer'n'gear really provides is another
venue for our community to socialize (just like any other social
event). Even at the IETF social events are "sponsored" to different
degrees. So while vendors get to display their wares, for the most
part B'n'G provides another "hallway" where people can socialize/talk
while having free beer and food (as well as a way for NANOG to
generate revenue).  In the NANOG case this is a win-win, however, for
the reasons you cite it would be an experiment at the IETF.

Dave

>
> On Mar 16, 2012, at 12:49 PM, IAOC Chair wrote:
>
>>
>> The IESG and IAOC are considering an addition to the IETF meeting week, =
and we would like your views before we develop the idea further.
>>
>> At NANOG, there is a Beer and Gear reception one evening. =A0There are e=
xhibitor tables with product vendors (hardware and software) and service pr=
oviders (registries, registrars, ISPs, ESPs, etc.) and anyone else interest=
ed in face time with NANOG participants. They show their equipment and serv=
ices. =A0There is bar in the center of the room serving beer, wine, and sof=
t drinks. There are hors d'oeuvres scattered around the room.
>>
>> =A0QUESTION: =A0What do you think about doing a Beer and Gear style
>> =A0 =A0 =A0 =A0 =A0 =A0 of event on an evening that does not conflict wi=
th
>> =A0 =A0 =A0 =A0 =A0 =A0 other IETF activities?
>>
>> This would be an opportunity for free food and drink for attendees, for =
vendors and service providers to talk with IETF participants, and for addit=
ional revenue to the IETF. =A0Obviously, attendance would be optional.
>>
>> Technical people are at the tables, not sales or marketing staff. =A0Ven=
dors know that the audience is very technical, so they send the people that=
 can communicate with that audience.
>>
>> We would charge for exhibit tables, to raise additional funds for the IE=
TF. A stronger base of opportunities for IETF sponsorship distributes our f=
unding, making it less fragile; this could make it less likely that we woul=
d have last-minute scrambles for additional sponsors, including hosts. A su=
ccessful Beer-and-Gear like event would not solve this but it would help.
>>
>> In the past, the IETF has avoided vendor exhibits and demonstrations. =
=A0However it is clear that NANOG has found a balance that works and that N=
ANOG participants and the vendors consider the event valuable. =A0We believ=
e this could translate well to the IETF.
>>
>> We are considering some test events, hopefully to be held at IETF 84 (Va=
ncouver, July 2012) and IETF 85 (Atlanta, November 2012).
>>
>> The kinds of evaluation criteria we are considering could include:
>>
>> - Did participants enjoy the event?
>>
>> - Did vendors consider the event successful?
>>
>> - Did the IETF raise additional funds?
>>
>> - Did the event "steal" potential sponsors away from other
>> =A0aspects of the meeting?
>>
>> So, what do you think? =A0Is this something that we should try?
>>
>> Please respond on the ietf@ietf.org mail list.
>>
>> On behalf of the IESG and the IAOC,
>>
>> Russ Housley
>> Bob Hinden
>

From fred@cisco.com  Fri Mar 16 14:21:01 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 CFC5421E807D for <ietf@ietfa.amsl.com>; Fri, 16 Mar 2012 14:21:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.374
X-Spam-Level: 
X-Spam-Status: No, score=-109.374 tagged_above=-999 required=5 tests=[AWL=1.225, 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 mXfyuJZfOyFw for <ietf@ietfa.amsl.com>; Fri, 16 Mar 2012 14:21:00 -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 7EDEB21E8028 for <ietf@ietf.org>; Fri, 16 Mar 2012 14:20:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fred@cisco.com; l=4830; q=dns/txt; s=iport; t=1331932854; x=1333142454; h=subject:mime-version:from:in-reply-to:date:cc:message-id: references:to:content-transfer-encoding; bh=q6TxC2nOTRD8RBvlwoM9jUXD1SXFPBO2X/Oa+TkjaSU=; b=QVayLjqD9oQvD4+jMJguvutDuF3bGfF3dN5ut/6ciUnZX8rvU8e6BGvs kK87SMAAAcreYzmGeQgpc+vnJzeMsXY2dd+8AvZ24Q4JZ/OXWDJZzpQrs +S16Idm7S2sRkC0T/lm1+zKI6TLLDtfow41Y4mg6GzLwyiXWPSJfr+fYS M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EACyuY0+rRDoJ/2dsb2JhbABCtTGBCYEHggkBAQEDAQ4EAScnBAUFCgULCw4KLlcGExQKBIdjBJpGnyaKRoVUYwSFIoM0iVmDN4VsiFOBaIMGgTw
X-IronPort-AV: E=Sophos;i="4.73,599,1325462400"; d="scan'208";a="33903303"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by mtv-iport-3.cisco.com with ESMTP; 16 Mar 2012 21:20:54 +0000
Received: from stealth-10-32-244-218.cisco.com (stealth-10-32-244-218.cisco.com [10.32.244.218]) by mtv-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id q2GLKqoA018182; Fri, 16 Mar 2012 21:20:53 GMT
Received: from [127.0.0.1] by stealth-10-32-244-218.cisco.com (PGP Universal service); Fri, 16 Mar 2012 14:20:53 -0700
X-PGP-Universal: processed; by stealth-10-32-244-218.cisco.com on Fri, 16 Mar 2012 14:20:53 -0700
Subject: Re: Query to the community -- An additional IETF Meeting event?
Mime-Version: 1.0 (Apple Message framework v1084)
From: Fred Baker <fred@cisco.com>
In-Reply-To: <CAHiKxWiLbA7+=Rc+fAfe2goM4dkhttSRvKBAKqBALhWKsNFh6A@mail.gmail.com>
Date: Fri, 16 Mar 2012 14:19:56 -0700
Message-Id: <B70CC2B7-5638-4DC5-8D35-C6DADF42187F@cisco.com>
References: <20120316194918.18453.89483.idtracker@ietfa.amsl.com> <CB0BE66D-26E1-492C-B84C-44F6C0449995@cisco.com> <CAHiKxWiLbA7+=Rc+fAfe2goM4dkhttSRvKBAKqBALhWKsNFh6A@mail.gmail.com>
To: David Meyer <dmm@1-4-5.net>
X-Mailer: Apple Mail (2.1084)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Mar 2012 21:21:01 -0000

On Mar 16, 2012, at 2:13 PM, David Meyer wrote:

> On Fri, Mar 16, 2012 at 2:03 PM, Fred Baker <fred@cisco.com> wrote:
>> The question I would ask is: "who are the vendors marketing to, and =
what are they selling?" At NANOG, that's fairly clear; companies like =
Cisco and Juniper, and resellers like Network Hardware, are selling to =
their customers, who are often technical decision makers or senior staff =
in companies that buy the stuff. The vendors that sponsor the event go =
home with business cards, which give them the opportunity for sales =
contacts after the event. Those people also come to IETF, but many =
others at IETF are from exactly those vendors, or from research and =
academia. I'm not convinced that the lead generation exercise, which is =
the vendor's reason for showing up and sponsoring the event, is going to =
be as useful for them.
>>=20
>> Not opposed to the experiment, but not sure that we're comparing =
apples to apples.
>=20
> While I agree Fred, what the beer'n'gear really provides is another =
venue for our community to socialize (just like any other social event).

Of course, and socializing is a good thing. What I'm looking at is the =
reason for the vendor to sponsor it. When I come to your and my boss and =
say "gee, let's spend a few hundred thousand dollars in the general =
direction of ISOC/IETF", I have to scramble a bit to answer a long list =
of questions headed by "what's in it for me?" and "who's budget does =
this come from?". I think I can say what question I would be asked if I =
said "let's be a beer'n'gear sponsor". I'm not sure that the answer I =
would give ranks with the one NANOG might give.

> Even at the IETF social events are "sponsored" to different degrees. =
So while vendors get to display their wares, for the most part B'n'G =
provides another "hallway" where people can socialize/talk while having =
free beer and food (as well as a way for NANOG to generate revenue). In =
the NANOG case this is a win-win, however, for the reasons you cite it =
would be an experiment at the IETF.
>=20
> Dave
>=20
>>=20
>> On Mar 16, 2012, at 12:49 PM, IAOC Chair wrote:
>>=20
>>>=20
>>> The IESG and IAOC are considering an addition to the IETF meeting =
week, and we would like your views before we develop the idea further.
>>>=20
>>> At NANOG, there is a Beer and Gear reception one evening.  There are =
exhibitor tables with product vendors (hardware and software) and =
service providers (registries, registrars, ISPs, ESPs, etc.) and anyone =
else interested in face time with NANOG participants. They show their =
equipment and services.  There is bar in the center of the room serving =
beer, wine, and soft drinks. There are hors d'oeuvres scattered around =
the room.
>>>=20
>>>  QUESTION:  What do you think about doing a Beer and Gear style
>>>             of event on an evening that does not conflict with
>>>             other IETF activities?
>>>=20
>>> This would be an opportunity for free food and drink for attendees, =
for vendors and service providers to talk with IETF participants, and =
for additional revenue to the IETF.  Obviously, attendance would be =
optional.
>>>=20
>>> Technical people are at the tables, not sales or marketing staff.  =
Vendors know that the audience is very technical, so they send the =
people that can communicate with that audience.
>>>=20
>>> We would charge for exhibit tables, to raise additional funds for =
the IETF. A stronger base of opportunities for IETF sponsorship =
distributes our funding, making it less fragile; this could make it less =
likely that we would have last-minute scrambles for additional sponsors, =
including hosts. A successful Beer-and-Gear like event would not solve =
this but it would help.
>>>=20
>>> In the past, the IETF has avoided vendor exhibits and =
demonstrations.  However it is clear that NANOG has found a balance that =
works and that NANOG participants and the vendors consider the event =
valuable.  We believe this could translate well to the IETF.
>>>=20
>>> We are considering some test events, hopefully to be held at IETF 84 =
(Vancouver, July 2012) and IETF 85 (Atlanta, November 2012).
>>>=20
>>> The kinds of evaluation criteria we are considering could include:
>>>=20
>>> - Did participants enjoy the event?
>>>=20
>>> - Did vendors consider the event successful?
>>>=20
>>> - Did the IETF raise additional funds?
>>>=20
>>> - Did the event "steal" potential sponsors away from other
>>>  aspects of the meeting?
>>>=20
>>> So, what do you think?  Is this something that we should try?
>>>=20
>>> Please respond on the ietf@ietf.org mail list.
>>>=20
>>> On behalf of the IESG and the IAOC,
>>>=20
>>> Russ Housley
>>> Bob Hinden
>>=20


From dhc@dcrocker.net  Fri Mar 16 14:24:23 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 D86AA21E807B for <ietf@ietfa.amsl.com>; Fri, 16 Mar 2012 14:24:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.606
X-Spam-Level: 
X-Spam-Status: No, score=-6.606 tagged_above=-999 required=5 tests=[AWL=-0.007, 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 XmEY0CpJJFBz for <ietf@ietfa.amsl.com>; Fri, 16 Mar 2012 14:24:23 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 3CF9321E807D for <ietf@ietf.org>; Fri, 16 Mar 2012 14:24:21 -0700 (PDT)
Received: from [192.168.1.11] (adsl-67-127-58-62.dsl.pltn13.pacbell.net [67.127.58.62]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q2GLOEXP012148 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 16 Mar 2012 14:24:19 -0700
Message-ID: <4F63AF60.4010004@dcrocker.net>
Date: Fri, 16 Mar 2012 14:23:44 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: Fred Baker <fred@cisco.com>
Subject: Re: Query to the community -- An additional IETF Meeting event?
References: <20120316194918.18453.89483.idtracker@ietfa.amsl.com> <CB0BE66D-26E1-492C-B84C-44F6C0449995@cisco.com>
In-Reply-To: <CB0BE66D-26E1-492C-B84C-44F6C0449995@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Fri, 16 Mar 2012 14:24:19 -0700 (PDT)
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Mar 2012 21:24:24 -0000

Fred, et al,


On 3/16/2012 2:03 PM, Fred Baker wrote:
> Not opposed to the experiment, but not sure that we're comparing apples to apples.


To clarify:

The current question is about IETF community comfort with the IAOC's exploring 
this.  That is, it's a form of "may we proceed to do the research and planning?" 
query.

Part of "exploring" is to develop a sense of the marketing issues, exactly as 
you and others have raised.

But these are worth pursuing only if the community is comfortable with the basic 
idea of doing this kind of event.

d/
-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From housley@vigilsec.com  Fri Mar 16 14:29:54 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 2AC8E21E807B; Fri, 16 Mar 2012 14:29: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=[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 rPzHyeEHITi7; Fri, 16 Mar 2012 14:29:53 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id 723F321F85EE; Fri, 16 Mar 2012 14:29:44 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 85B339A473A; Fri, 16 Mar 2012 17:29:46 -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 3Co1Dfajm3zE; Fri, 16 Mar 2012 17:29:29 -0400 (EDT)
Received: from [192.168.2.104] (pool-96-241-165-215.washdc.fios.verizon.net [96.241.165.215]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 87C4D9A472C; Fri, 16 Mar 2012 17:29:45 -0400 (EDT)
Subject: Re: Trade show at IETF
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <4F63A836.4010207@netconfcentral.org>
Date: Fri, 16 Mar 2012 17:29:38 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <FF6289E8-641B-4CFD-8D2B-4D6191312A65@vigilsec.com>
References: <20120316194918.18453.89483.idtracker@ietfa.amsl.com> <tslhaxocmii.fsf@mit.edu> <4F63A836.4010207@netconfcentral.org>
To: Andy Bierman <andy@netconfcentral.org>
X-Mailer: Apple Mail (2.1084)
Cc: IAOC <iaoc@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: Fri, 16 Mar 2012 21:29:54 -0000

Andy:

> On 03/16/2012 01:35 PM, Sam Hartman wrote:
>>=20
>>     IAOC>    QUESTION: What do you think about doing a Beer and Gear
>>     IAOC>  style of event on an evening that does not conflict with =
other
>>     IAOC>  IETF activities?
>>=20
>> I think that hallway conversations, private meetings and other
>> activities that people have already filled Sunday after the
>> reception,Monday, Thursday and Friday with are more important.  I =
think
>> this would make an already crowded event more crowded and while it =
might
>> be useful would detract from other more important uses of the time.
>> So, I am not generally supportive of this idea.
>=20
> NANOG has network operators as the audience but the IETF has a more =
mixed audience.
> I support ideas to raise money, and I would go to this event, out of =
curiosity.
> I'm not looking to buy any networking equipment though.
>=20
> I would actually like more lunch-time lectures and discussions.
> (Maybe M, T, and Th so WG Chairs lunch on W does not conflict).
> Perhaps vendors or researchers would be willing to make a donation
> to get one of those lunch slots?

Yes.  We need to make sure that lunch-time events do not interfere with =
the IETF meeting.  For the last few years, ISOC has an event on Tuesday, =
the WG Chairs meet on Wednesday, and the Host presents on Thursday.  =
That does leave Monday for a sponsor slot.

Since we did not have a host until very late in the game for Paris, a =
sponsor was given the Thursday lunch slot.  Now that we have a host, and =
Thursday is gone, we have given the host the Monday lunch slot.  So, =
there are no more slots in Paris.  But is also shows that we could =
probably get sponsorship dollars for the Monday lunch slot on an ongoing =
basis.

Russ=

From fred@cisco.com  Fri Mar 16 14:33:16 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 ADDE821E8088 for <ietf@ietfa.amsl.com>; Fri, 16 Mar 2012 14:33:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.387
X-Spam-Level: 
X-Spam-Status: No, score=-109.387 tagged_above=-999 required=5 tests=[AWL=1.212, 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 L8FRaPUW7O1c for <ietf@ietfa.amsl.com>; Fri, 16 Mar 2012 14:33:16 -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 E8AE121F8607 for <ietf@ietf.org>; Fri, 16 Mar 2012 14:33:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fred@cisco.com; l=213; q=dns/txt; s=iport; t=1331933595; x=1333143195; h=subject:mime-version:from:in-reply-to:date:cc:message-id: references:to:content-transfer-encoding; bh=h94o+MIM9moPf4xvOEkVzgmUI/oDlyKlDx1Vecblt2Y=; b=V/CqtHfQsUrbToDRwvSWMrUEVqrCx/jeog1vb6Fk3Qp8fnv91nglF6XA sIi6q9QKiNSecwp58IQ6kBpy4gJvvft6pHW/YUyAYrw7pHR35Q3y+p4wD dAplS1QZPL0d4CFUznygcdTVlFI+9tgopP8744ZolKA/BXvx2kuAnB6CX 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAG+xY0+rRDoG/2dsb2JhbABCtjqBB4IJAQEBAwESASc/BQsLRlctDodjBJpDnyaNW4I/YwSIVo0QhWyIU4FogwY
X-IronPort-AV: E=Sophos;i="4.73,599,1325462400"; d="scan'208";a="33368674"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by mtv-iport-1.cisco.com with ESMTP; 16 Mar 2012 21:33:02 +0000
Received: from stealth-10-32-244-218.cisco.com (stealth-10-32-244-218.cisco.com [10.32.244.218]) by mtv-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id q2GLWkNf000323; Fri, 16 Mar 2012 21:33:02 GMT
Received: from [127.0.0.1] by stealth-10-32-244-218.cisco.com (PGP Universal service); Fri, 16 Mar 2012 14:33:02 -0700
X-PGP-Universal: processed; by stealth-10-32-244-218.cisco.com on Fri, 16 Mar 2012 14:33:02 -0700
Subject: Re: Query to the community -- An additional IETF Meeting event?
Mime-Version: 1.0 (Apple Message framework v1084)
From: Fred Baker <fred@cisco.com>
In-Reply-To: <4F63AF60.4010004@dcrocker.net>
Date: Fri, 16 Mar 2012 14:32:11 -0700
Message-Id: <F60BE240-FE9D-498F-BF1E-1A43214C1416@cisco.com>
References: <20120316194918.18453.89483.idtracker@ietfa.amsl.com> <CB0BE66D-26E1-492C-B84C-44F6C0449995@cisco.com> <4F63AF60.4010004@dcrocker.net>
To: dcrocker@bbiw.net
X-Mailer: Apple Mail (2.1084)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Mar 2012 21:33:16 -0000

On Mar 16, 2012, at 2:23 PM, Dave Crocker wrote:

> But these are worth pursuing only if the community is comfortable with =
the basic idea of doing this kind of event.

I'm willing to do the experiment.=

From dwm@xpasc.com  Fri Mar 16 15:00:31 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 D254621E807B; Fri, 16 Mar 2012 15:00:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.845
X-Spam-Level: 
X-Spam-Status: No, score=-3.845 tagged_above=-999 required=5 tests=[AWL=-3.660, BAYES_40=-0.185]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FqxPTvoiF61r; Fri, 16 Mar 2012 15:00:31 -0700 (PDT)
Received: from c2w3p-2.abacamail.com (c2w3p-2.abacamail.com [209.133.53.32]) by ietfa.amsl.com (Postfix) with ESMTP id 05CF621E807A; Fri, 16 Mar 2012 15:00:17 -0700 (PDT)
Received: from xpasc.com (unknown [68.164.244.188]) by c2w3p-2.abacamail.com (Postfix) with ESMTP id 7E81D3F82D; Fri, 16 Mar 2012 22:00:17 +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 q2GM0HHs000470; Fri, 16 Mar 2012 15:00:17 -0700
Date: Fri, 16 Mar 2012 15:00:17 -0700 (PDT)
From: David Morris <dwm@xpasc.com>
To: IETF <ietf@ietf.org>
Subject: Re: Trade show at IETF
In-Reply-To: <FF6289E8-641B-4CFD-8D2B-4D6191312A65@vigilsec.com>
Message-ID: <Pine.LNX.4.64.1203161454080.348@egate.xpasc.com>
References: <20120316194918.18453.89483.idtracker@ietfa.amsl.com> <tslhaxocmii.fsf@mit.edu> <4F63A836.4010207@netconfcentral.org> <FF6289E8-641B-4CFD-8D2B-4D6191312A65@vigilsec.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-AV-Type: clean
X-AV-Accuracy: exact
X-Milter-Version: master.24-gef8a08a
X-CLX-ID: a120AD3GD2zQ1vr-2G1500H
X-CLX-Spam: false
Cc: IAOC <iaoc@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: Fri, 16 Mar 2012 22:00:32 -0000

On Fri, 16 Mar 2012, Russ Housley wrote:
> Thursday is gone, we have given the host the Monday lunch slot.  So,
> there are no more slots in Paris.  But is also shows that we could
> probably get sponsorship dollars for the Monday lunch slot on an ongoing
> basis.

Another slot to consider ... breakfast before the daily meetings ... might 
be offered to a vendor for the right fee. As a dietician, my wife attends
professional conferences. Recently she spent a week in Las Vegas during
which she attended a catered breakfast training session put on by one of
the nutritional suppliment vendors. Breakfast was nice and free and she
continuing education credits and learned about that companies latest
products for medical nutrition therepy. As I recall the session started at
an obnoxious time like 6am.

I can imagine quite a few topics that a large percentage of IETF attendies
would find useful.

From john-ietf@jck.com  Fri Mar 16 15:31:38 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 560E521F86B6; Fri, 16 Mar 2012 15:31:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.748
X-Spam-Level: 
X-Spam-Status: No, score=-102.748 tagged_above=-999 required=5 tests=[AWL=-0.149, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Uk-fz8k1+nKc; Fri, 16 Mar 2012 15:31:35 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id A1AAA21F86B2; Fri, 16 Mar 2012 15:31:35 -0700 (PDT)
Received: from [198.252.137.7] (helo=PST.JCK.COM) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1S8fbe-0004Pu-AD; Fri, 16 Mar 2012 18:26:42 -0400
Date: Fri, 16 Mar 2012 18:31:29 -0400
From: John C Klensin <john-ietf@jck.com>
To: Sam Hartman <hartmans-ietf@mit.edu>, IAOC Chair <bob.hinden@gmail.com>
Subject: Re: Trade show at IETF
Message-ID: <660B7B697AC872D0B613D905@PST.JCK.COM>
In-Reply-To: <tslhaxocmii.fsf@mit.edu>
References: <20120316194918.18453.89483.idtracker@ietfa.amsl.com> <tslhaxocmii.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: iaoc@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Mar 2012 22:31:38 -0000

--On Friday, March 16, 2012 16:35 -0400 Sam Hartman
<hartmans-ietf@mit.edu> wrote:

>     IAOC>   QUESTION: What do you think about doing a Beer and
> Gear     IAOC> style of event on an evening that does not
> conflict with other     IAOC> IETF activities?
> 
> I think that hallway conversations, private meetings and other
> activities that people have already filled Sunday after the
> reception,Monday, Thursday and Friday with are more important.
> I think this would make an already crowded event more crowded
> and while it might be useful would detract from other more
> important uses of the time. So, I am not generally supportive
> of this idea.

FWIW, I have to agree with Sam.  The notion that we have spare
slots that could reasonably be used for this sort of thing on a
non-conflicting basis is dubious.  In my experience, "free"
evenings tend to turn into individual meetings, design team
meetings, company get-togethers. ISOC events, and lots of other
things that keep either the IETF or other wheels turning.
Similar comments apply to lunch: formally, we've got ISOC, WG
Chairs, and Sponsor.  Informally and in terms of small group
activities, I can't remember an IETF at which I've had a free
lunch slot: directorate meetings, WG Chairs or design team
meetings for particular WGs (with or without an AD or two), IAB
Project meetings, RFC Editor meetings, interviews, and so on,
often with the opportunity to be double- or triple-booked.

Recommendation if you want to try an experiment:  find the next
meeting when there is no sponsor and therefore no social (or no
social scheduled for some other reason) and try Tuesday.   Then
ask the community afterwards whether it prefers this type of
event or a social.

And the above ignores my deep concerns about essentially
inviting a collection of sales and marketing, and maybe
recruiting, types to the IETF.  That interacts with Fred's
concern about audience but goes well beyond it.

   john




From joelja@bogus.com  Fri Mar 16 15:34:26 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 CADE821E801F for <ietf@ietfa.amsl.com>; Fri, 16 Mar 2012 15:34:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.4
X-Spam-Level: 
X-Spam-Status: No, score=-102.4 tagged_above=-999 required=5 tests=[AWL=0.199,  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 KvshKN6-fGV7 for <ietf@ietfa.amsl.com>; Fri, 16 Mar 2012 15:34:26 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id F1CD021E801A for <ietf@ietf.org>; Fri, 16 Mar 2012 15:34:25 -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 q2GMYM8U068887 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Fri, 16 Mar 2012 22:34:23 GMT (envelope-from joelja@bogus.com)
Message-ID: <4F63BFE9.8000306@bogus.com>
Date: Fri, 16 Mar 2012 15:34:17 -0700
From: Joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:11.0) Gecko/20120313 Thunderbird/11.0
MIME-Version: 1.0
To: Fred Baker <fred@cisco.com>
Subject: Re: Query to the community -- An additional IETF Meeting event?
References: <20120316194918.18453.89483.idtracker@ietfa.amsl.com> <CB0BE66D-26E1-492C-B84C-44F6C0449995@cisco.com> <CAHiKxWiLbA7+=Rc+fAfe2goM4dkhttSRvKBAKqBALhWKsNFh6A@mail.gmail.com> <B70CC2B7-5638-4DC5-8D35-C6DADF42187F@cisco.com>
In-Reply-To: <B70CC2B7-5638-4DC5-8D35-C6DADF42187F@cisco.com>
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, 16 Mar 2012 22:34:23 +0000 (UTC)
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Mar 2012 22:34:26 -0000

On 3/16/12 14:19 , Fred Baker wrote:
> 
> On Mar 16, 2012, at 2:13 PM, David Meyer wrote:
> 
>> On Fri, Mar 16, 2012 at 2:03 PM, Fred Baker <fred@cisco.com>
>> wrote:
>>> The question I would ask is: "who are the vendors marketing to,
>>> and what are they selling?" At NANOG, that's fairly clear;
>>> companies like Cisco and Juniper, and resellers like Network
>>> Hardware, are selling to their customers, who are often technical
>>> decision makers or senior staff in companies that buy the stuff.
>>> The vendors that sponsor the event go home with business cards,
>>> which give them the opportunity for sales contacts after the
>>> event. Those people also come to IETF, but many others at IETF
>>> are from exactly those vendors, or from research and academia.
>>> I'm not convinced that the lead generation exercise, which is the
>>> vendor's reason for showing up and sponsoring the event, is going
>>> to be as useful for them.
>>> 
>>> Not opposed to the experiment, but not sure that we're comparing
>>> apples to apples.
>> 
>> While I agree Fred, what the beer'n'gear really provides is another
>> venue for our community to socialize (just like any other social
>> event).
> 
> Of course, and socializing is a good thing. What I'm looking at is
> the reason for the vendor to sponsor it. When I come to your and my
> boss and say "gee, let's spend a few hundred thousand dollars in the
> general direction of ISOC/IETF", I have to scramble a bit to answer a
> long list of questions headed by "what's in it for me?" and "who's
> budget does this come from?". I think I can say what question I would
> be asked if I said "let's be a beer'n'gear sponsor". I'm not sure
> that the answer I would give ranks with the one NANOG might give.

I'm neither for or against it in the particular case but I have served
on the nanog pc so I have been involved in organizing events like this.

There are actual operators why buy actual gear and services, who attend
ietf meetings. We're soemthing of a minority. that's an audience.

I would expect the net needs to be throw a little wider eg around
service organizations, other SDOs, and other entities that want a low
pressure social environment in which to share information about their
products services activities recruitment efforts etc.

>> Even at the IETF social events are "sponsored" to different
>> degrees. So while vendors get to display their wares, for the most
>> part B'n'G provides another "hallway" where people can
>> socialize/talk while having free beer and food (as well as a way
>> for NANOG to generate revenue). In the NANOG case this is a
>> win-win, however, for the reasons you cite it would be an
>> experiment at the IETF.
>> 
>> Dave
>> 
>>> 
>>> On Mar 16, 2012, at 12:49 PM, IAOC Chair wrote:
>>> 
>>>> 
>>>> The IESG and IAOC are considering an addition to the IETF
>>>> meeting week, and we would like your views before we develop
>>>> the idea further.
>>>> 
>>>> At NANOG, there is a Beer and Gear reception one evening.
>>>> There are exhibitor tables with product vendors (hardware and
>>>> software) and service providers (registries, registrars, ISPs,
>>>> ESPs, etc.) and anyone else interested in face time with NANOG
>>>> participants. They show their equipment and services.  There is
>>>> bar in the center of the room serving beer, wine, and soft
>>>> drinks. There are hors d'oeuvres scattered around the room.
>>>> 
>>>> QUESTION:  What do you think about doing a Beer and Gear style 
>>>> of event on an evening that does not conflict with other IETF
>>>> activities?
>>>> 
>>>> This would be an opportunity for free food and drink for
>>>> attendees, for vendors and service providers to talk with IETF
>>>> participants, and for additional revenue to the IETF.
>>>> Obviously, attendance would be optional.
>>>> 
>>>> Technical people are at the tables, not sales or marketing
>>>> staff.  Vendors know that the audience is very technical, so
>>>> they send the people that can communicate with that audience.
>>>> 
>>>> We would charge for exhibit tables, to raise additional funds
>>>> for the IETF. A stronger base of opportunities for IETF
>>>> sponsorship distributes our funding, making it less fragile;
>>>> this could make it less likely that we would have last-minute
>>>> scrambles for additional sponsors, including hosts. A
>>>> successful Beer-and-Gear like event would not solve this but it
>>>> would help.
>>>> 
>>>> In the past, the IETF has avoided vendor exhibits and
>>>> demonstrations.  However it is clear that NANOG has found a
>>>> balance that works and that NANOG participants and the vendors
>>>> consider the event valuable.  We believe this could translate
>>>> well to the IETF.
>>>> 
>>>> We are considering some test events, hopefully to be held at
>>>> IETF 84 (Vancouver, July 2012) and IETF 85 (Atlanta, November
>>>> 2012).
>>>> 
>>>> The kinds of evaluation criteria we are considering could
>>>> include:
>>>> 
>>>> - Did participants enjoy the event?
>>>> 
>>>> - Did vendors consider the event successful?
>>>> 
>>>> - Did the IETF raise additional funds?
>>>> 
>>>> - Did the event "steal" potential sponsors away from other 
>>>> aspects of the meeting?
>>>> 
>>>> So, what do you think?  Is this something that we should try?
>>>> 
>>>> Please respond on the ietf@ietf.org mail list.
>>>> 
>>>> On behalf of the IESG and the IAOC,
>>>> 
>>>> Russ Housley Bob Hinden
>>> 
> 
> 


From dwm@xpasc.com  Fri Mar 16 16:32:55 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 EBB7D21E807B; Fri, 16 Mar 2012 16:32:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.645
X-Spam-Level: 
X-Spam-Status: No, score=-4.645 tagged_above=-999 required=5 tests=[AWL=-2.046, 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 oCNQMgD0LdhB; Fri, 16 Mar 2012 16:32:55 -0700 (PDT)
Received: from c2w3p-2.abacamail.com (c2w3p-2.abacamail.com [209.133.53.32]) by ietfa.amsl.com (Postfix) with ESMTP id 7EDEC21E8014; Fri, 16 Mar 2012 16:32:55 -0700 (PDT)
Received: from xpasc.com (unknown [68.164.244.188]) by c2w3p-2.abacamail.com (Postfix) with ESMTP id E9D963F9CB; Fri, 16 Mar 2012 23:32:54 +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 q2GNWsBS001087; Fri, 16 Mar 2012 16:32:54 -0700
Date: Fri, 16 Mar 2012 16:32:54 -0700 (PDT)
From: David Morris <dwm@xpasc.com>
To: ietf@ietf.org
Subject: Re: Trade show at IETF
In-Reply-To: <tslhaxocmii.fsf@mit.edu>
Message-ID: <Pine.LNX.4.64.1203161629330.348@egate.xpasc.com>
References: <20120316194918.18453.89483.idtracker@ietfa.amsl.com> <tslhaxocmii.fsf@mit.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-AV-Type: clean
X-AV-Accuracy: exact
X-Milter-Version: master.24-gef8a08a
X-CLX-ID: a120AD3GD2zQ1vr-2G1632t
X-CLX-Spam: false
Cc: iaoc@ietf.org
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: Fri, 16 Mar 2012 23:32:56 -0000

On Fri, 16 Mar 2012, Sam Hartman wrote:

> >>>>> "IAOC" == IAOC Chair <bob.hinden@gmail.com> writes:
> 
>     IAOC>   QUESTION: What do you think about doing a Beer and Gear
>     IAOC> style of event on an evening that does not conflict with other
>     IAOC> IETF activities?
> 
> I think that hallway conversations, private meetings and other
> activities that people have already filled Sunday after the
> reception,Monday, Thursday and Friday with are more important.  I think
> this would make an already crowded event more crowded and while it might
> be useful would detract from other more important uses of the time.
> So, I am not generally supportive of this idea.

I find my self needing downtime when I attend an IETF meeting. Crowding
more opportunities into the schedule is possibly counter productive. But
as an experiment, seems useful.

Might thing about exhibit only attendees as well ... I frequently go
to trade shows for the exhibits rather than the sessions. Wouldn't travel
far, but I can see that being a valuable additional audience to
interest vendors?


From melinda.shore@gmail.com  Fri Mar 16 18:49:27 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 45EF721E8026 for <ietf@ietfa.amsl.com>; Fri, 16 Mar 2012 18:49:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kNle7BRow82W for <ietf@ietfa.amsl.com>; Fri, 16 Mar 2012 18:49:26 -0700 (PDT)
Received: from mail-pz0-f44.google.com (mail-pz0-f44.google.com [209.85.210.44]) by ietfa.amsl.com (Postfix) with ESMTP id 5A8FE21E800F for <ietf@ietf.org>; Fri, 16 Mar 2012 18:49:26 -0700 (PDT)
Received: by dakl33 with SMTP id l33so7873168dak.31 for <ietf@ietf.org>; Fri, 16 Mar 2012 18:49:26 -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=sBbe8MYUYPHmNUSr6u71TzQWP/Pc2Y6HCeOJ/nAr4Kk=; b=nCLkAz4cjQeWI2b7D2xYRL5brjKPAJ6x10H2WR6F6rqQtylhBQEV5Ex6r6qkkLuRgU 1KVU5rv+zTjayUtc79sqsjbrSqmNdtOEBEnh8ipg386fVkAltSDHnQZoxLKW5OHR5fkr XSzLqq9LXb1OMy01knqPpAyz0wkNNBAszA1Mt9iDKaAZM+DL+FPDVkLQoGNv6jGIfNvc o47ae8/CIDyBJcSCEi7tr3RCq7I/J2OpkdEX5SFbb07urLwKOjgciQDsj/l0HBkftbD1 pTc6bqnlYUfmyYSACDtWuKAxSqCoSOX3nF7wrs9zjE4hSaUdli2MplD56t5fY26l2Cld HzpA==
Received: by 10.68.236.132 with SMTP id uu4mr2761015pbc.166.1331948966234; Fri, 16 Mar 2012 18:49:26 -0700 (PDT)
Received: from polypro.local (66-230-81-245-rb1.fai.dsl.dynamic.acsalaska.net. [66.230.81.245]) by mx.google.com with ESMTPS id g4sm5491630pbt.58.2012.03.16.18.49.24 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 16 Mar 2012 18:49:25 -0700 (PDT)
Message-ID: <4F63EDA3.8000001@gmail.com>
Date: Fri, 16 Mar 2012 17:49:23 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.27) Gecko/20120216 Lightning/1.0b2 Thunderbird/3.1.19
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Trade show at IETF
References: <20120316194918.18453.89483.idtracker@ietfa.amsl.com>	<tslhaxocmii.fsf@mit.edu> <Pine.LNX.4.64.1203161629330.348@egate.xpasc.com>
In-Reply-To: <Pine.LNX.4.64.1203161629330.348@egate.xpasc.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 17 Mar 2012 01:49:27 -0000

On 3/16/12 3:32 PM, David Morris wrote:
> I find my self needing downtime when I attend an IETF meeting.

Me too, and while I'm pro-beer I'm ambivalent about gear.  I
don't really understand what would be in it for any of the
parties involved.

No harm in looking at it, though.  Questions about what it would
offer that participants would find useful (other than beer).

> Might thing about exhibit only attendees as well ... I frequently go
> to trade shows for the exhibits rather than the sessions. Wouldn't travel
> far, but I can see that being a valuable additional audience to
> interest vendors?

I don't think I'd like that.  Too many people already refer to
IETF meetings as "conferences."  We're there to move work forward.

Melinda

From john-ietf@jck.com  Fri Mar 16 20:04:38 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 E9D0321E8025 for <ietf@ietfa.amsl.com>; Fri, 16 Mar 2012 20:04:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.593
X-Spam-Level: 
X-Spam-Status: No, score=-102.593 tagged_above=-999 required=5 tests=[AWL=-0.294, BAYES_00=-2.599, SARE_WEOFFER=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 todTzYXCcD-R for <ietf@ietfa.amsl.com>; Fri, 16 Mar 2012 20:04:38 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 4B16121E800F for <ietf@ietf.org>; Fri, 16 Mar 2012 20:04:08 -0700 (PDT)
Received: from [198.252.137.7] (helo=PST.JCK.COM) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1S8jrO-00055x-TB; Fri, 16 Mar 2012 22:59:14 -0400
Date: Fri, 16 Mar 2012 23:04:00 -0400
From: John C Klensin <john-ietf@jck.com>
To: Melinda Shore <melinda.shore@gmail.com>, ietf@ietf.org
Subject: Re: Trade show at IETF
Message-ID: <818BA8B64CF795AEFC4DAD5F@PST.JCK.COM>
In-Reply-To: <4F63EDA3.8000001@gmail.com>
References: <20120316194918.18453.89483.idtracker@ietfa.amsl.com> <tslhaxocmii.fsf@mit.edu> <Pine.LNX.4.64.1203161629330.348@egate.xpasc.com> <4F63EDA3.8000001@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: Sat, 17 Mar 2012 03:04:39 -0000

--On Friday, March 16, 2012 17:49 -0800 Melinda Shore
<melinda.shore@gmail.com> wrote:

>...
> No harm in looking at it, though.  Questions about what it
> would
> offer that participants would find useful (other than beer).

Not to pick on Melinda (her note was just handy), but I want to
push back a bit on the "no harm in trying this" hypothesis
("looking" is another issue).

Many participants in the IETF, including people from exactly the
vendors one might expect to be looking for booths (or whatever),
have been complaining in recent years about pressure on travel
budgets, especially for multiple attendees from their
organizations.  So suppose vendor X is now sending 10 people to
the IETF (and used to send 15 or 20).   Suppose we offer them a
show floor or equivalent and they decide they need to send five
market or sales folk to staff it.  There are certainly companies
whose travel budgets for engineering staff are completely
separate from those for sales and marketing, but my experience
and some studies I've seen in recent years suggest not a huge
number of them.

Especially for the others, do we really believe that starting
with 10 engineering attendees and deciding that one needs five
marketing/sales people present is going to produce 15 people
traveling total? I'd say "maybe" if the sales/marketing people
could be pulled out of an office that was local to the IETF
venue but "almost certainly not" if people had to be put on
airplanes and put up in hotels.  For the latter situation, maybe
one would get lucky and end up with a dozen people (i.e., a
reduction in engineering attendance at the IETF of only three).
Less lucky and the "10 people" remains constant and IETF
participant attendance goes down by half.

Note too that, if the company sends only five technical people
and concludes that it doesn't suffer harm from that small a
number, the odds of getting back up to 10 if the experiment is
terminated and those five sales/market types disappear is just
about zero, at least until the economy improves considerable.

Scale and juggle the figures as you like, this is not a
zero-risk experiment.

     john


From dhc@dcrocker.net  Fri Mar 16 21:15:32 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 70AE521E805D for <ietf@ietfa.amsl.com>; Fri, 16 Mar 2012 21:15:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.456
X-Spam-Level: 
X-Spam-Status: No, score=-6.456 tagged_above=-999 required=5 tests=[AWL=-0.157, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_WEOFFER=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 TKA4RaxwtSkl for <ietf@ietfa.amsl.com>; Fri, 16 Mar 2012 21:15:31 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 9C60F21F8609 for <ietf@ietf.org>; Fri, 16 Mar 2012 21:15:26 -0700 (PDT)
Received: from [192.168.1.11] (adsl-67-127-58-62.dsl.pltn13.pacbell.net [67.127.58.62]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q2H4FJuJ018806 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 16 Mar 2012 21:15:25 -0700
Message-ID: <4F640FB9.3050302@dcrocker.net>
Date: Fri, 16 Mar 2012 21:14:49 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
Subject: Re: Trade show at IETF
References: <20120316194918.18453.89483.idtracker@ietfa.amsl.com> <tslhaxocmii.fsf@mit.edu> <Pine.LNX.4.64.1203161629330.348@egate.xpasc.com> <4F63EDA3.8000001@gmail.com> <818BA8B64CF795AEFC4DAD5F@PST.JCK.COM>
In-Reply-To: <818BA8B64CF795AEFC4DAD5F@PST.JCK.COM>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Fri, 16 Mar 2012 21:15:25 -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: Sat, 17 Mar 2012 04:15:32 -0000

On 3/16/2012 8:04 PM, John C Klensin wrote:
> Suppose we offer them a
> show floor or equivalent and they decide they need to send five
> market or sales folk to staff it.


wow.  that's very creative thinking John.

d/
-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From joelja@bogus.com  Fri Mar 16 21:28:22 2012
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7BDDD21E80A1 for <ietf@ietfa.amsl.com>; Fri, 16 Mar 2012 21:28:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.527
X-Spam-Level: 
X-Spam-Status: No, score=-102.527 tagged_above=-999 required=5 tests=[AWL=0.072, 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 VxGBPoqoltR3 for <ietf@ietfa.amsl.com>; Fri, 16 Mar 2012 21:28:21 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id DAAE621E8049 for <ietf@ietf.org>; Fri, 16 Mar 2012 21:28:21 -0700 (PDT)
Received: from Joels-MacBook-Pro.local (c-98-234-216-143.hsd1.ca.comcast.net [98.234.216.143]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id q2H4SJd8075487 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Sat, 17 Mar 2012 04:28:20 GMT (envelope-from joelja@bogus.com)
Message-ID: <4F6412E3.6060901@bogus.com>
Date: Fri, 16 Mar 2012 21:28:19 -0700
From: Joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:11.0) Gecko/20120313 Thunderbird/11.0
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
Subject: Re: Trade show at IETF
References: <20120316194918.18453.89483.idtracker@ietfa.amsl.com> <tslhaxocmii.fsf@mit.edu> <Pine.LNX.4.64.1203161629330.348@egate.xpasc.com> <4F63EDA3.8000001@gmail.com> <818BA8B64CF795AEFC4DAD5F@PST.JCK.COM>
In-Reply-To: <818BA8B64CF795AEFC4DAD5F@PST.JCK.COM>
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]); Sat, 17 Mar 2012 04:28:20 +0000 (UTC)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 17 Mar 2012 04:28:22 -0000

On 3/16/12 20:04 , John C Klensin wrote:
> Note too that, if the company sends only five technical people
> and concludes that it doesn't suffer harm from that small a
> number, the odds of getting back up to 10 if the experiment is
> terminated and those five sales/market types disappear is just
> about zero, at least until the economy improves considerable.
> 
> Scale and juggle the figures as you like, this is not a
> zero-risk experiment.

You know nothing about marketing budgets.

>      john
> 


From joelja@bogus.com  Fri Mar 16 23:10:13 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 CF79021F86B1 for <ietf@ietfa.amsl.com>; Fri, 16 Mar 2012 23:10:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.53
X-Spam-Level: 
X-Spam-Status: No, score=-102.53 tagged_above=-999 required=5 tests=[AWL=0.069, 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 G0+2Sd174v9Y for <ietf@ietfa.amsl.com>; Fri, 16 Mar 2012 23:10:13 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 50CF421F86A8 for <ietf@ietf.org>; Fri, 16 Mar 2012 23:10:13 -0700 (PDT)
Received: from Joels-MacBook-Pro.local (c-98-234-216-143.hsd1.ca.comcast.net [98.234.216.143]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id q2H6ABV3077182 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Sat, 17 Mar 2012 06:10:11 GMT (envelope-from joelja@bogus.com)
Message-ID: <4F642AC2.40200@bogus.com>
Date: Fri, 16 Mar 2012 23:10:10 -0700
From: Joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:11.0) Gecko/20120313 Thunderbird/11.0
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
Subject: Re: Trade show at IETF
References: <20120316194918.18453.89483.idtracker@ietfa.amsl.com> <tslhaxocmii.fsf@mit.edu> <Pine.LNX.4.64.1203161629330.348@egate.xpasc.com> <4F63EDA3.8000001@gmail.com> <818BA8B64CF795AEFC4DAD5F@PST.JCK.COM> <4F6412E3.6060901@bogus.com>
In-Reply-To: <4F6412E3.6060901@bogus.com>
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]); Sat, 17 Mar 2012 06:10:12 +0000 (UTC)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 17 Mar 2012 06:10:13 -0000

On 3/16/12 21:28 , Joel jaeggli wrote:
> On 3/16/12 20:04 , John C Klensin wrote:
>> Note too that, if the company sends only five technical people
>> and concludes that it doesn't suffer harm from that small a
>> number, the odds of getting back up to 10 if the experiment is
>> terminated and those five sales/market types disappear is just
>> about zero, at least until the economy improves considerable.
>>
>> Scale and juggle the figures as you like, this is not a
>> zero-risk experiment.
> 
> You know nothing about marketing budgets.

to me more succint and less terse.

PMO or whatever it's called in given organzation is a different pool of
money. whether it gets spent at the ietf or not has little or nothing to
do with whether R&D dollars are spent on standards activity.
if there are potential customers at the ietf or reach to customers
through the ietf PMO is potentially interested. if not they aren't.


>>      john
>>
> 


From jonne.soininen@renesasmobile.com  Sat Mar 17 02:18:53 2012
Return-Path: <jonne.soininen@renesasmobile.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 648A321F8667 for <ietf@ietfa.amsl.com>; Sat, 17 Mar 2012 02:18:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.348
X-Spam-Level: 
X-Spam-Status: No, score=-4.348 tagged_above=-999 required=5 tests=[AWL=-0.750, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VdA-b1Kp4zPN for <ietf@ietfa.amsl.com>; Sat, 17 Mar 2012 02:18:52 -0700 (PDT)
Received: from mail1.bemta4.messagelabs.com (mail1.bemta4.messagelabs.com [85.158.143.242]) by ietfa.amsl.com (Postfix) with ESMTP id 10C2421F8636 for <ietf@ietf.org>; Sat, 17 Mar 2012 02:18:51 -0700 (PDT)
Received: from [85.158.143.99:46455] by server-1.bemta-4.messagelabs.com id 88/98-20925-BF6546F4; Sat, 17 Mar 2012 09:18:51 +0000
X-Env-Sender: jonne.soininen@renesasmobile.com
X-Msg-Ref: server-11.tower-216.messagelabs.com!1331975930!19057298!1
X-Originating-IP: [213.174.82.10]
X-StarScan-Version: 6.5.7; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 31124 invoked from network); 17 Mar 2012 09:18:51 -0000
Received: from renexfe01.roe2.renesasmobile.com (HELO renexfe01.roe2.renesasmobile.com) (213.174.82.10) by server-11.tower-216.messagelabs.com with AES128-SHA encrypted SMTP; 17 Mar 2012 09:18:51 -0000
Received: from RENEXMB02.roe2.renesasmobile.com ([fe80::b101:43e1:dd7b:2fbb]) by renexfe01.roe2.renesasmobile.com ([fe80::ec94:bbb3:68e:a94a%18]) with mapi id 14.01.0323.003; Sat, 17 Mar 2012 11:18:49 +0200
From: <jonne.soininen@renesasmobile.com>
To: <ietf@ietf.org>
Subject: Re: Query to the community -- An additional IETF Meeting event?
Thread-Topic: Query to the community -- An additional IETF Meeting event?
Thread-Index: AQHNBB71vnU/kk+ecEWAeF/tov7ouA==
Date: Sat, 17 Mar 2012 09:18:48 +0000
Message-ID: <CB8A2398.930F8%jonne.soininen@renesasmobile.com>
Accept-Language: en-US, en-GB
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.21.22.171]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <E4D1CBBCBBD745479721EE580956D30F@roe2.renesasmobile.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 17 Mar 2012 09:18:53 -0000

Hello everybody,

The beer and gear seems to work pretty well at Nanog, and therefore it is
a good idea to consider it for the IETF. However, I am a bit worried that
we are, however, not seeing the difference between the IETF and Nanog.
Nanog is a Network Operator Group. Hence, the name. Vendors come there and
show their products to their potential customers. In addition, sometimes
the people that come to the meetings are a bit different - though, a
significant overlap does exist.

We are a bit different.Though, we do have many operators, many of the
people are from the vendor camp, and other camps (such as academia). For a
vendor, it might seem a bit that showing your product at the IETF, you're
mostly showing it to your competitor.

Therefore, I don't believe an IETF beer would have quite the same interest
than the Nanog one would. I am very skeptical if this concept would work
at the IETF..

That said, if trying it out does not carry financial risk for the IETF,
perhaps we can try this out, and see what happens. I guess we are supposed
to believe in running code, aren't we...

Cheers,

Jonne.

--=20
Jonne Soininen
Renesas Mobile


Tel: +358 40 527 4634
E-mail: jonne.soininen@renesasmobile.com





On 3/16/12 10:13 PM, "IAOC Chair" <bob.hinden@gmail.com> wrote:

>
>The IESG and IAOC are considering an addition to the IETF meeting week,
>and we would like your views before we develop the idea further.
>
>At NANOG, there is a Beer and Gear reception one evening.  There are
>exhibitor tables with product vendors (hardware and software) and service
>providers (registries, registrars, ISPs, ESPs, etc.) and anyone else
>interested in face time with NANOG participants. They show their
>equipment and services.  There is bar in the center of the room serving
>beer, wine, and soft drinks. There are hors d'oeuvres scattered around
>the room.
>
>  QUESTION:  What do you think about doing a Beer and Gear style
>             of event on an evening that does not conflict with
>             other IETF activities?
>
>This would be an opportunity for free food and drink for attendees, for
>vendors and service providers to talk with IETF participants, and for
>additional revenue to the IETF.  Obviously, attendance would be optional.
>
>Technical people are at the tables, not sales or marketing staff.
>Vendors know that the audience is very technical, so they send the people
>that can communicate with that audience.
>
>We would charge for exhibit tables, to raise additional funds for the
>IETF. A stronger base of opportunities for IETF sponsorship distributes
>our funding, making it less fragile; this could make it less likely that
>we would have last-minute scrambles for additional sponsors, including
>hosts. A successful Beer-and-Gear like event would not solve this but it
>would help.
>
>In the past, the IETF has avoided vendor exhibits and demonstrations.
>However it is clear that NANOG has found a balance that works and that
>NANOG participants and the vendors consider the event valuable.  We
>believe this could translate well to the IETF.
>
>We are considering some test events, hopefully to be held at IETF 84
>(Vancouver, July 2012) and IETF 85 (Atlanta, November 2012).
>
>The kinds of evaluation criteria we are considering could include:
>
>- Did participants enjoy the event?
>
>- Did vendors consider the event successful?
>
>- Did the IETF raise additional funds?
>
>- Did the event "steal" potential sponsors away from other
>  aspects of the meeting?
>
>So, what do you think?  Is this something that we should try?
>
>Please respond on the ietf@ietf.org mail list.
>
>On behalf of the IESG and the IAOC,
>
>Russ Housley
>Bob Hinden



From julian.reschke@gmx.de  Sat Mar 17 02:21:13 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 A13A721F870F for <ietf@ietfa.amsl.com>; Sat, 17 Mar 2012 02:21:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.618
X-Spam-Level: 
X-Spam-Status: No, score=-102.618 tagged_above=-999 required=5 tests=[AWL=-1.859, BAYES_00=-2.599, J_CHICKENPOX_22=0.6, SARE_LWSHORTT=1.24, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2sU6gYrjzLXy for <ietf@ietfa.amsl.com>; Sat, 17 Mar 2012 02:21:12 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by ietfa.amsl.com (Postfix) with SMTP id CF07E21F8705 for <ietf@ietf.org>; Sat, 17 Mar 2012 02:21:08 -0700 (PDT)
Received: (qmail invoked by alias); 17 Mar 2012 09:21:07 -0000
Received: from p57A6D822.dip.t-dialin.net (EHLO [192.168.178.36]) [87.166.216.34] by mail.gmx.net (mp016) with SMTP; 17 Mar 2012 10:21:07 +0100
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX18xOF4rfjsxtNda05r+lh14cRYyKHxnmkrHuNWbKc wKZSdk2H7Al68M
Message-ID: <4F645781.70308@gmx.de>
Date: Sat, 17 Mar 2012 10:21:05 +0100
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: Ben Campbell <ben@nostrum.com>
Subject: Re: [Gen-art] Gen-ART LC/Telechat review of draft-reschke-http-status-308-05
References: <27FD8C7A-7636-4D60-A65E-C2B264857A0E@nostrum.com> <4F5E2F65.1000706@gmx.de> <1A884C60-A13C-4F37-AF83-3F542DE00153@nostrum.com>
In-Reply-To: <1A884C60-A13C-4F37-AF83-3F542DE00153@nostrum.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, The IETF <ietf@ietf.org>, draft-reschke-http-status-308.all@tools.ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 17 Mar 2012 09:21:14 -0000

On 2012-03-16 22:06, Ben Campbell wrote:
> Apologies for the delayed response--the day job got in the way this week.
>
> Comments inline:
>
> On Mar 12, 2012, at 12:16 PM, Julian Reschke wrote:
>
>> On 2012-03-12 17:15, Ben Campbell wrote:
>>> I am the assigned Gen-ART reviewer for this draft. For background on
>>> Gen-ART, please see the FAQ at
>>> <   http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>>>
>>> Please wait for direction from your document shepherd
>>> or AD before posting a new version of the draft.
>>>
>>> Document: draft-reschke-http-status-308-05
>>> Reviewer: Ben Campbell	
>>> Review Date: 2012-03-12
>>> IETF LC End Date: 2012-03-16
>>> IESG Telechat date: 2012-03-15
>>>
>>> Summary: This draft is basically ready for publication as an experimental RFC. I have a few minor comments that might be worth considering whether they would improve the document prior to publication.
>>>
>>> Note: Since this draft is on a Telechat that precedes the end of the IETF Last Call, this review serves as both the LC and Telechat review.
>>
>> Thanks.
>>
>>> Major issues:
>>>
>>> None:
>>>
>>> Minor issues:
>>>
>>> -- General: I see some discussion about existing UA behavior, but nothing about what a UA should do with a 308 other than as an implication the fact that this is a "permanent version of 307". It's probably worth describing that explicitly. (Or is that what the "clients with link-editing capabilities" statement is intended to do?If so, does that cover everything?)
>>
>> The draft uses *exactly* the same words as the base spec (HTTPbis), except that it combines aspects of 302 (permanence) with those of 307. I thought that's clear enough.
>
> I assume you meant 301 and 307.

Yes.

> I note that all of the 3XX responses have their semantics explicitly described in httpbis. While some reference other 3XX codes to contrast the behavior, none seem to be defined in terms of each other. The 301 definition includes an explicit note about the POST to GET behavior. The 307 definition includes an explicit post about that behavior not being allowed. Section 3 of this doc does neither.

The note in 307 was written to point out that the equivalent (308) is 
not defined in HTTPbis. That's why the equivalent text is not on the 
definition of 308.

But you are right in that it provides additional information not present 
in the statement for 308, and I can fix that.

> Looking further, I see that both the 301 and 307 definitions have different language about the response payload (they say if the method was not HEAD the payload SHOULD contain short  hypertext note, while this doc says the payload can contain one. (which I read as equivalent to a MAY).
>
> Finally, both 301 and 307 contain a paragraph about automatic redirection for "safe" methods.

Both of this is not true anymore in draft -19 of httpbis, where all 
these statements have been moved to the introduction of the redirect codes.

>>
>>> -- section 1, last paragraph:
>>>
>>> The fact that a 308 can't change the method is left as an implication of being based on 307. It would be good to state that explicitly and normatively here.
>>
>> We don't state it in HTTPbis either. 301, 302, and 303 are exceptions. See the new introduction in<http://greenbytes.de/tech/webdav/draft-ietf-httpbis-p2-semantics-18.html#rfc.section.7.3>.
>
> HTTPbis sections 7.3.2, 7.3.3, 7.3.4, and 7.3.8 all contain explicit language or notes about about  GET and POST. I recognize that it is not stated _normatively_ in each case, but it's at least mentioned.

7.3.2 (301), 7.3.3 (392) and 7.3.4 (303) have these notes because they 
are exceptions. Re: 7.3.8: see above.

>>> -- section 3, 1st paragraph: "Clients with link-editing capabilities ought to..."
>>>
>>> Should that be stated normatively?
>>
>> No. Again, this is consistent with the text in HTTPbis for status code 302.
>
> I concur that it says that. I find it unfortunate that HTTPbis used non-normative language there, but the text in this draft is consistent.
>
>>
>>> -- section 3, third paragraph: "The new permanent URI SHOULD be given..."
>>>
>>> I'm curious why that is not a MUST. Is there a reasonable (i.e. interoperable)  way to send a 308 _without_ a URI in the location field? Is the meta refresh directive something that can be used _instead_ of the Location header field?
>>
>> Again, consistency with RFC 2616 and HTTPbis.
>
> You are correct.
>
>>
>>> -- section 4:
>>>
>>> The example uses _both_ the location field and the HTML<meta>   refresh directive. Is this considered a recommended practice to the degree you might normatively recommend it in the text?
>>
>> No, it's a hack that makes deployment easier until all UAs do the right thing; we don't want to make that permanent.
>
> A comment to that effect in the text would be helpful.

I disagree with this. It's an example for a deployment strategy that can 
help in the short term. That's all.

Best regards, Julian


From john-ietf@jck.com  Sat Mar 17 03:17:09 2012
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 392CF21F8667 for <ietf@ietfa.amsl.com>; Sat, 17 Mar 2012 03:17:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.738
X-Spam-Level: 
X-Spam-Status: No, score=-102.738 tagged_above=-999 required=5 tests=[AWL=-0.139, 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 OxkcC5msJmNX for <ietf@ietfa.amsl.com>; Sat, 17 Mar 2012 03:17:08 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 3DC3621F862A for <ietf@ietf.org>; Sat, 17 Mar 2012 03:17:08 -0700 (PDT)
Received: from [198.252.137.7] (helo=PST.JCK.COM) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1S8qcP-0005sh-Bk; Sat, 17 Mar 2012 06:12:13 -0400
Date: Sat, 17 Mar 2012 06:17:00 -0400
From: John C Klensin <john-ietf@jck.com>
To: Joel jaeggli <joelja@bogus.com>
Subject: Re: Trade show at IETF
Message-ID: <AFB757E6C30BF6E334785373@PST.JCK.COM>
In-Reply-To: <4F6412E3.6060901@bogus.com>
References: <20120316194918.18453.89483.idtracker@ietfa.amsl.com> <tslhaxocmii.fsf@mit.edu> <Pine.LNX.4.64.1203161629330.348@egate.xpasc.com> <4F63EDA3.8000001@gmail.com> <818BA8B64CF795AEFC4DAD5F@PST.JCK.COM> <4F6412E3.6060901@bogus.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: Sat, 17 Mar 2012 10:17:09 -0000

--On Friday, March 16, 2012 21:28 -0700 Joel jaeggli
<joelja@bogus.com> wrote:

> On 3/16/12 20:04 , John C Klensin wrote:
>> Note too that, if the company sends only five technical people
>> and concludes that it doesn't suffer harm from that small a
>> number, the odds of getting back up to 10 if the experiment is
>> terminated and those five sales/market types disappear is just
>> about zero, at least until the economy improves considerable.
>> 
>> Scale and juggle the figures as you like, this is not a
>> zero-risk experiment.
> 
> You know nothing about marketing budgets.

Sorry, Joel.  I have both had to administer those budgets and
policies, been the victim of them, as well as seen it go on in
companies with whom I've done consulting work on organizational
and strategic matters.  Companies differ -- I tried to say that
-- but in many companies that are really oriented toward the
bottom line, marketing controls virtually all travel budgets.
In a few, sales and/or controls and perceptions of their needs
control almost all budget categories: Engineering is rarely a
profit center, the money has to come from somewhere, and the
organizational question is how much control the money source and
its needs affect how it is spent.

I didn't mean to suggest that the effects would be felt
immediately -- there are usually budget cycles.  But, over the
medium term, even more relaxed organizations in tight budget
situations do tend to eventually notice "total number of people
attending from company", and push back.   If the attendees
include both people from cost centers and people from profit
centers, the latter tend to win the battle for slots, or at
least to win less.

But I suppose I should defer to your superior experience in
senior management and corporate finance roles.

    john



From RCosta@ptinovacao.pt  Sat Mar 17 05:01:04 2012
Return-Path: <RCosta@ptinovacao.pt>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D8CB821F85CF for <ietf@ietfa.amsl.com>; Sat, 17 Mar 2012 05:01:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.312
X-Spam-Level: 
X-Spam-Status: No, score=-2.312 tagged_above=-999 required=5 tests=[AWL=0.287,  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 XCdEbFe-jaUE for <ietf@ietfa.amsl.com>; Sat, 17 Mar 2012 05:01:03 -0700 (PDT)
Received: from owa.ptinovacao.pt (webmail.ptinovacao.pt [194.65.138.99]) by ietfa.amsl.com (Postfix) with ESMTP id 8480F21F85EF for <ietf@ietf.org>; Sat, 17 Mar 2012 05:01:01 -0700 (PDT)
Received: from INOAVREX11.ptin.corpPT.com ([10.112.15.122]) by inoavrcas01.ptin.corpPT.com ([10.112.15.99]) with mapi; Sat, 17 Mar 2012 12:00:58 +0000
From: Rui Costa <RCosta@ptinovacao.pt>
To: "ietf@ietf.org" <ietf@ietf.org>
Date: Sat, 17 Mar 2012 12:00:56 +0000
Subject: RE: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt> (Allocation of	an Associated Channel Code Point for Use by	ITU-T Ethernet based OAM) to Informational RFC
Thread-Topic: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt> (Allocation of	an Associated Channel Code Point for Use by	ITU-T Ethernet based OAM) to Informational RFC
Thread-Index: AQGdS0dQFbRu6GyAeWPtVTnp+xX6JJaoUwDwgB+ZhBA=
Message-ID: <52981DB05D3C5247A12D0AEE309F3CC202444231EB23@INOAVREX11.ptin.corpPT.com>
References: <20120222151252.32262.82157.idtracker@ietfa.amsl.com> <03a301ccf174$ff953290$febf97b0$@olddog.co.uk>
In-Reply-To: <03a301ccf174$ff953290$febf97b0$@olddog.co.uk>
Accept-Language: pt-PT
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: pt-PT
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 17 Mar 2012 12:01:05 -0000

Hello,=09

I support the allocation of an ACH codepoint to G.8113.1, not precluding th=
e ITU-T to progress refinements. Ergo, i support this draft and proposal ht=
tp://www.ietf.org/mail-archive/web/ietf/current/msg72191.html.=09

IMHO, the status quo analysis expressed in both http://www.ietf.org/mail-ar=
chive/web/ietf/current/msg72188.html and http://www.ietf.org/mail-archive/w=
eb/ietf/current/msg72273.html is accurate.=09

Regards,=09
Rui=09



-------- Original Message --------
From: The IESG <iesg-secretary@ietf.org>
Sent: Wed, 22 Feb 2012 07:12:52 -0800
To: IETF-Announce <ietf-announce@ietf.org>
Subject: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt> (Allocation=
 of	an Associated Channel Code Point for Use by ITU-T Ethernet	based OAM) t=
o Informational RFC

The IESG has received a request from an individual submitter to consider th=
e following document:
- 'Allocation of an Associated Channel Code Point for Use by ITU-T
    Ethernet based OAM'
   <draft-betts-itu-oam-ach-code-point-03.txt> as an 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-03-21. Exceptionally, comments may be sent to ie=
sg@ietf.org instead. In either case, please retain the beginning of the Sub=
ject line to allow automated sorting.

Abstract

    This document assigns an Associated Channel Type code point for
    carrying Ethernet based Operations, Administration, and Management
    messages in the MPLS Generic Associated Channel (G-ACh).

The file can be obtained via
http://datatracker.ietf.org/doc/draft-betts-itu-oam-ach-code-point/

IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-betts-itu-oam-ach-code-point/


No IPR declarations have been submitted directly on this I-D.
_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce=09


From julian.reschke@gmx.de  Sat Mar 17 05:50:33 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 A74D921F8699 for <ietf@ietfa.amsl.com>; Sat, 17 Mar 2012 05:50:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.306
X-Spam-Level: 
X-Spam-Status: No, score=-103.306 tagged_above=-999 required=5 tests=[AWL=-0.707, 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 j3fKXy9J80qA for <ietf@ietfa.amsl.com>; Sat, 17 Mar 2012 05:50:32 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by ietfa.amsl.com (Postfix) with SMTP id 6B6A821F868C for <ietf@ietf.org>; Sat, 17 Mar 2012 05:50:32 -0700 (PDT)
Received: (qmail invoked by alias); 17 Mar 2012 12:50:30 -0000
Received: from p57A6EBC7.dip.t-dialin.net (EHLO [192.168.178.36]) [87.166.235.199] by mail.gmx.net (mp002) with SMTP; 17 Mar 2012 13:50:30 +0100
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1+kugQX7eGkThRWFXjw2I6BU0bjSfclZyZYHACQuX +jxxfG4A69+CAV
Message-ID: <4F648879.4000909@gmx.de>
Date: Sat, 17 Mar 2012 13:50:01 +0100
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Last Call: <draft-reschke-http-status-308-05.txt> (The Hypertext Transfer Protocol (HTTP) Status Code 308 (Permanent Redirect)) to Experimental RFC
References: <20120217144555.26744.99147.idtracker@ietfa.amsl.com> <4F3E7816.4070709@gmx.de>
In-Reply-To: <4F3E7816.4070709@gmx.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: HTTP Working Group <ietf-http-wg@w3.org>, IETF 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: Sat, 17 Mar 2012 12:50:33 -0000

Hi there,

the IESG has approved the draft for publication as experimental, but a 
few details need some tuning.

I plan to post a revised draft next Monday (when publication restarts), 
and have my current version available over here:

 
<http://greenbytes.de/tech/webdav/draft-reschke-http-status-308-latest.html>

Diffs relative to the WGLC draft can be found here:

 
<http://greenbytes.de/tech/webdav/draft-reschke-http-status-308-latest-from-wglc.diff.html>

The main changes so far are updates to references, an addition of an 
informal ref to the HTML spec (because of the example using HTML), a 
warning against attempting to do UA sniffing, plus the inclusion of a 
note that makes the definition more consistent with what HTTPbis says 
about status code 307.

Feedback appreciated, Julian

On 2012-02-17 16:53, Julian Reschke wrote:
> (FYI)
>
> Also, an HTML version with feedback links is available at
> <http://greenbytes.de/tech/webdav/draft-reschke-http-status-308-05.html>.
>
> Best regards, Julian
>
> On 2012-02-17 15:45, The IESG wrote:
>>
>> The IESG has received a request from an individual submitter to consider
>> the following document:
>> - 'The Hypertext Transfer Protocol (HTTP) Status Code 308 (Permanent
>> Redirect)'
>> <draft-reschke-http-status-308-05.txt> as an Experimental RFC
>>
>> The IESG plans to make a decision in the next few weeks, and solicits
>> final comments on this action. Please send substantive comments to the
>> ietf@ietf.org mailing lists by 2012-03-16. 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 specifies the additional HyperText Transfer Protocol
>> (HTTP) Status Code 308 (Permanent Redirect).
>>
>>
>>
>>
>> The file can be obtained via
>> http://datatracker.ietf.org/doc/draft-reschke-http-status-308/
>>
>> IESG discussion can be tracked via
>> http://datatracker.ietf.org/doc/draft-reschke-http-status-308/
>>
>>
>> No IPR declarations have been submitted directly on this I-D.
>>
>>
>> _______________________________________________
>> IETF-Announce mailing list
>> IETF-Announce@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf-announce
>>
>
>
>


From julian.reschke@gmx.de  Sat Mar 17 06:40:38 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 DEC0621F8668 for <ietf@ietfa.amsl.com>; Sat, 17 Mar 2012 06:40:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.365
X-Spam-Level: 
X-Spam-Status: No, score=-103.365 tagged_above=-999 required=5 tests=[AWL=-0.765, 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 zAu1kYyMfgSh for <ietf@ietfa.amsl.com>; Sat, 17 Mar 2012 06:40:37 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by ietfa.amsl.com (Postfix) with SMTP id 6781C21F865E for <ietf@ietf.org>; Sat, 17 Mar 2012 06:40:37 -0700 (PDT)
Received: (qmail invoked by alias); 17 Mar 2012 13:40:36 -0000
Received: from p57A6EBC7.dip.t-dialin.net (EHLO [192.168.178.36]) [87.166.235.199] by mail.gmx.net (mp037) with SMTP; 17 Mar 2012 14:40:36 +0100
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX18S/8l/Q7cSEzD8DLgOBSNMQQIJiBWvm6ZTr/TAYN zZThd/v6qBMPVC
Message-ID: <4F649435.6000807@gmx.de>
Date: Sat, 17 Mar 2012 14:40:05 +0100
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Last Call: <draft-reschke-http-status-308-05.txt> (The Hypertext Transfer Protocol (HTTP) Status Code 308 (Permanent Redirect)) to Experimental RFC
References: <20120217144555.26744.99147.idtracker@ietfa.amsl.com> <4F3E7816.4070709@gmx.de> <4F648879.4000909@gmx.de>
In-Reply-To: <4F648879.4000909@gmx.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: HTTP Working Group <ietf-http-wg@w3.org>, IETF 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: Sat, 17 Mar 2012 13:40:39 -0000

On 2012-03-17 13:50, Julian Reschke wrote:
> Hi there,
>
> the IESG has approved the draft for publication as experimental, but a
> few details need some tuning.
>
> I plan to post a revised draft next Monday (when publication restarts),
 > ...

Monday, March 26, actually...

From scott.brim@gmail.com  Sat Mar 17 07:35:48 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 EFBB421F8633 for <ietf@ietfa.amsl.com>; Sat, 17 Mar 2012 07:35:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.57
X-Spam-Level: 
X-Spam-Status: No, score=-103.57 tagged_above=-999 required=5 tests=[AWL=0.029, 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 9lW7F4rvDujl for <ietf@ietfa.amsl.com>; Sat, 17 Mar 2012 07:35:48 -0700 (PDT)
Received: from mail-pz0-f44.google.com (mail-pz0-f44.google.com [209.85.210.44]) by ietfa.amsl.com (Postfix) with ESMTP id 9159021F8629 for <ietf@ietf.org>; Sat, 17 Mar 2012 07:35:48 -0700 (PDT)
Received: by dakl33 with SMTP id l33so8580893dak.31 for <ietf@ietf.org>; Sat, 17 Mar 2012 07:35:48 -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=UIxAPPUmkCSV7/XQb40/ci6au9+IeTwKTXbbR2oTkbs=; b=SBdMjpcxG2dBw6msYZ7kuWmJEwpHEAYh9csWLkPZOKyDAbVAkg7Kj7U+7CafZOK1ay MB17hkYNmXox+CDZWVIZbQrdnZDPxdNT0PDQ1ts/dXP5ZqIWGNS9t7O5RuKogv7K5t4f 4VtLEmvzPdB3YkkRVIEkIm+M4PJyIov9sdDI7wsOBVeWpyIPhMILnaEd9MJLNMRy/E6B Vvj/WHSrRTpoMQkc1TENGj+NZS7/mQOYoFzOKU7Q4iLvu+K+WB+QFc6Ppw3SgPumPTHM dxMef+hrgJJnBoOTpL22rJTERHDlAoMqiDB00ijk+SUKW9j14KWXd1TlTh6d3JTApN8c o95w==
Received: by 10.68.203.202 with SMTP id ks10mr10069601pbc.84.1331994948453; Sat, 17 Mar 2012 07:35:48 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.68.2.35 with HTTP; Sat, 17 Mar 2012 07:35:28 -0700 (PDT)
In-Reply-To: <CB8A2398.930F8%jonne.soininen@renesasmobile.com>
References: <CB8A2398.930F8%jonne.soininen@renesasmobile.com>
From: Scott Brim <scott.brim@gmail.com>
Date: Sat, 17 Mar 2012 10:35:28 -0400
Message-ID: <CAPv4CP_QJ_kLdXiGmNjszAj7RUO7b8dgoSWQSQSLc_zHQMFbVw@mail.gmail.com>
Subject: Re: Query to the community -- An additional IETF Meeting event?
To: jonne.soininen@renesasmobile.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: Sat, 17 Mar 2012 14:35:49 -0000

Those vendors who want to organize themselves into a beer & gear
should do so and then coordinate with the IETF early in the planning
process in order to have space they can pay for.  They can either pay
the IETF or pay the hotel for the incremental meeting cost.  There is
no need for the IETF to take responsibility for this, or to spend yet
more administration time on it.

From richard@shockey.us  Sat Mar 17 08:45:40 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 D5EFC21F8633 for <ietf@ietfa.amsl.com>; Sat, 17 Mar 2012 08:45:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.866
X-Spam-Level: 
X-Spam-Status: No, score=-99.866 tagged_above=-999 required=5 tests=[AWL=0.629, 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 FpUj8NCq1WMm for <ietf@ietfa.amsl.com>; Sat, 17 Mar 2012 08:45:40 -0700 (PDT)
Received: from oproxy8-pub.bluehost.com (oproxy8.bluehost.com [IPv6:2605:dc00:100:2::a8]) by ietfa.amsl.com (Postfix) with SMTP id 04E8B21F861A for <ietf@ietf.org>; Sat, 17 Mar 2012 08:45:39 -0700 (PDT)
Received: (qmail 22251 invoked by uid 0); 17 Mar 2012 15:45:39 -0000
Received: from unknown (HELO box462.bluehost.com) (74.220.219.62) by oproxy8.bluehost.com with SMTP; 17 Mar 2012 15:45:39 -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:To:From; bh=u9zSxIT+wdy+sWLZ51xMBu3vn86jkf+GpXVEoglCU1A=;  b=kHjvev7754CZZ6eEEo5WToqxom7jrQvRY1ABnYrBhFWWpV55qAposZuw6fRgEo/7NLxF90szPREIkWJ4mJdcf3jyozWm0/WwOzYvwd4btN7TwH9VaqlwLcPbrz+xbTSr;
Received: from pool-108-48-10-220.washdc.fios.verizon.net ([108.48.10.220] helo=RSHOCKEYPC) by box462.bluehost.com with esmtpa (Exim 4.76) (envelope-from <richard@shockey.us>) id 1S8vp5-0007jU-6Z for ietf@ietf.org; Sat, 17 Mar 2012 09:45:39 -0600
From: "Richard Shockey" <richard@shockey.us>
To: <ietf@ietf.org>
References: <20120316201355.26551.35242.idtracker@ietfa.amsl.com>
In-Reply-To: <20120316201355.26551.35242.idtracker@ietfa.amsl.com>
Subject: RE: Query to the community -- An additional IETF Meeting event?
Date: Sat, 17 Mar 2012 11:45:39 -0400
Message-ID: <009c01cd0455$01b5b7f0$052127d0$@us>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac0DsVJkvmmN89UBTuWyB3/JaQ9qIgAoYUmA
Content-Language: en-us
X-Identified-User: {3286:box462.bluehost.com:shockeyu:shockey.us} {sentby:smtp auth 108.48.10.220 authed with richard@shockey.us}
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 17 Mar 2012 15:45:41 -0000

+1  Its worth a try.=20

I know IETF week is extremely busy for folks. There is the work that has =
to be done. There are dozens of private conversations folks want to have =
but IMHO we have to be realistic about making sure we are doing the =
right things to keep the meetings financially solvent in difficult =
times.=20

In my personal role as SIP Forum chair we also looked at what NANOG did =
in developing our own SIPNOC conference for SIP Network Operators.  We =
wanted peer reviewed presentations but we wanted a low key opportunity =
for vendors to participate especially those with limited budgets that =
would not conflict with full conference sponsorships. The Beer and Gear =
idea was perfect.=20

The question would be what day ..=20

Richard Shockey
Chairman of the Board of Directors SIP Forum
http//www.sipforum.org


-----Original Message-----
From: ietf-announce-bounces@ietf.org =
[mailto:ietf-announce-bounces@ietf.org] On Behalf Of IAOC Chair
Sent: Friday, March 16, 2012 4:14 PM
To: IETF Announcement List
Subject: Query to the community -- An additional IETF Meeting event?


The IESG and IAOC are considering an addition to the IETF meeting week, =
and we would like your views before we develop the idea further.

At NANOG, there is a Beer and Gear reception one evening.  There are =
exhibitor tables with product vendors (hardware and software) and =
service providers (registries, registrars, ISPs, ESPs, etc.) and anyone =
else interested in face time with NANOG participants. They show their =
equipment and services.  There is bar in the center of the room serving =
beer, wine, and soft drinks. There are hors d'oeuvres scattered around =
the room.

  QUESTION:  What do you think about doing a Beer and Gear style
             of event on an evening that does not conflict with
             other IETF activities?

This would be an opportunity for free food and drink for attendees, for =
vendors and service providers to talk with IETF participants, and for =
additional revenue to the IETF.  Obviously, attendance would be =
optional.

Technical people are at the tables, not sales or marketing staff.  =
Vendors know that the audience is very technical, so they send the =
people that can communicate with that audience.

We would charge for exhibit tables, to raise additional funds for the =
IETF. A stronger base of opportunities for IETF sponsorship distributes =
our funding, making it less fragile; this could make it less likely that =
we would have last-minute scrambles for additional sponsors, including =
hosts. A successful Beer-and-Gear like event would not solve this but it =
would help.

In the past, the IETF has avoided vendor exhibits and demonstrations.  =
However it is clear that NANOG has found a balance that works and that =
NANOG participants and the vendors consider the event valuable.  We =
believe this could translate well to the IETF.

We are considering some test events, hopefully to be held at IETF 84 =
(Vancouver, July 2012) and IETF 85 (Atlanta, November 2012).

The kinds of evaluation criteria we are considering could include:

- Did participants enjoy the event?

- Did vendors consider the event successful?

- Did the IETF raise additional funds?

- Did the event "steal" potential sponsors away from other
  aspects of the meeting?

So, what do you think?  Is this something that we should try?

Please respond on the ietf@ietf.org mail list.

On behalf of the IESG and the IAOC,

Russ Housley
Bob Hinden


From nurit.sprecher@nsn.com  Sun Mar 18 04:07:42 2012
Return-Path: <nurit.sprecher@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 67AD221F85EE for <ietf@ietfa.amsl.com>; Sun, 18 Mar 2012 04:07:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.216
X-Spam-Level: 
X-Spam-Status: No, score=-6.216 tagged_above=-999 required=5 tests=[AWL=-0.217, BAYES_00=-2.599, J_CHICKENPOX_15=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5tEHb5VMEmTU for <ietf@ietfa.amsl.com>; Sun, 18 Mar 2012 04:07:41 -0700 (PDT)
Received: from demumfd002.nsn-inter.net (demumfd002.nsn-inter.net [93.183.12.31]) by ietfa.amsl.com (Postfix) with ESMTP id CD64821F85EA for <ietf@ietf.org>; Sun, 18 Mar 2012 04:07:39 -0700 (PDT)
Received: from demuprx016.emea.nsn-intra.net ([10.150.129.55]) by demumfd002.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id q2IB7UCh023954 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sun, 18 Mar 2012 12:07:30 +0100
Received: from demuexc022.nsn-intra.net (demuexc022.nsn-intra.net [10.150.128.35]) by demuprx016.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id q2IB7RaM004794; Sun, 18 Mar 2012 12:07:27 +0100
Received: from DEMUEXC013.nsn-intra.net ([10.150.128.24]) by demuexc022.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.4675);  Sun, 18 Mar 2012 12:07:23 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Last Call:<draft-betts-itu-oam-ach-code-point-03.txt>(Allocationofan Associated Channel Code Point for Use by ITU-T EthernetbasedOAM) to Informational RFC
Date: Sun, 18 Mar 2012 12:07:22 +0100
Message-ID: <E4873516F3FC7547BCFE792C7D94039C01710B31@DEMUEXC013.nsn-intra.net>
In-Reply-To: <02e601cd0386$3ff90dc0$4001a8c0@gateway.2wire.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Last Call:<draft-betts-itu-oam-ach-code-point-03.txt>(Allocationofan Associated Channel Code Point for Use by ITU-T EthernetbasedOAM) to Informational RFC
Thread-Index: Ac0DjtBjhMkVuqnrTsGOytckKt9n2wBaDxnQ
References: <CAAHpaZ=JrKVKHZ0xkK-nszFDf-ttVNoi1p9iZiWa93vKuiNxZA@mail.gmail.com><4F60BF02.1010507@cisco.com><009b01cd0351$52d5f3c0$4001a8c0@gateway.2wire.net><4F635846.60505@cisco.com> <02e601cd0386$3ff90dc0$4001a8c0@gateway.2wire.net>
From: "Sprecher, Nurit (NSN - IL/Hod HaSharon)" <nurit.sprecher@nsn.com>
To: "ext t.petch" <daedulus@btconnect.com>, <stbryant@cisco.com>
X-OriginalArrivalTime: 18 Mar 2012 11:07:23.0899 (UTC) FILETIME=[4BD054B0:01CD04F7]
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: 4022
X-purgate-ID: 151667::1332068851-00007415-352DE4C6/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: Sun, 18 Mar 2012 11:07:42 -0000

Tom,
Did Huub and Malcolm represent the ITU in their assessments?=20
I guess other ITU members have different view on this!
Best regards,
Nurit

-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
ext t.petch
Sent: Friday, March 16, 2012 5:06 PM
To: stbryant@cisco.com
Cc: ietf@ietf.org
Subject: Re: Last
Call:<draft-betts-itu-oam-ach-code-point-03.txt>(Allocationofan
Associated Channel Code Point for Use by ITU-T EthernetbasedOAM) to
Informational RFC

----- Original Message -----
From: "Stewart Bryant" <stbryant@cisco.com>
To: "t.petch" <daedulus@btconnect.com>
Cc: "Fangyu Li" <fangyuli1999@gmail.com>; <ietf@ietf.org>
Sent: Friday, March 16, 2012 4:12 PM
Subject: Re: Last
Call:<draft-betts-itu-oam-ach-code-point-03.txt>(Allocationof
an Associated Channel Code Point for Use by ITU-T Ethernet basedOAM) to
Informational RFC


> On 16/03/2012 08:46, t.petch wrote:
> > ----- Original Message -----
> > From: "Stewart Bryant"<stbryant@cisco.com>
> > To: "Fangyu Li"<fangyuli1999@gmail.com>
> > Cc:<lifang@catr.cn>;<ietf@ietf.org>
> > Sent: Wednesday, March 14, 2012 4:53 PM
> >> On 14/03/2012 13:36, Fangyu Li wrote:
> >>> I support the allocation of an ACH codepoint to G.8113.1.
> >>> For G.8113.1 had reached the technical and industry maturity to be
> >>> assigned a code point, the codepoint allocation from IETF should
allow
> >>> the ITU-T to progress refinements to G.8113.1 such that it could
> >>> satisfy all the functional requirements defined in RFC 5860.
> >> Please can you tell me version of the G.8113.1 text one would
> >> need to implement to be able to seamlessly interwork with the
> >> equipment that has already been been deployed?
> > Stewart
> >
> > I am sure you already know the answer to that from posts made to the
mpls
list,
> > where we have been told that there is currently an extensive
deployment
> > ('running code') using an experimental value (interesting that there
is a
last
> > call just ending seeking to exterminate such practice, at least for
application
> > protocols) and that the wish is to move to a standards-based value
which
will,
> > perforce, be a different value.
> >
> > Tom Petch
>
> Tom,
>
> I don't think you understood my question.
>
> There are several version of the G.8113.1 text in circulation within
> the ITU-T. I was asking which version accurately describes the
> deployed protocol.

Stewart

One of the e-mails I had in mind was that of Huub Helvoort last December
where
he said
"The draft recommendation G.8113.1 is stable, there have been no major
technical
changes since it was sent to the IETF (when it still had the draft name
G.tpoam)
attache to liaison: https://datatracker.ietf.org/liaison/983/
This is also the status I reported when we did discuss this during
IETF82 in
Taipei."

while another such e-mail is that of Malcolm Betts in January where he
said
"I can confirm that the draft is requesting a code point for the version
of
G.8113.1 that was forwarded to WTSA by SG 15, this is the same as the
draft that was determined in February 2011, I am not anticipating any
changes prior to the approval decision at WTSA.  None of the changes in
G.8113.1 that were anticipated in draft-betts-itu-oam-ach-code-point-01
were implemented,  I will post a new version
draft-betts-itu-oam-ach-code-point to correctly reflect the content and
title on G.8113.1 and respond to the other questions later this week."

I was thinking that that was enough reassurance about the protocol and
its
stability.

I agree that the documents as liaised to us specify that special value
of XXXX
but we were told, on the mpls list, that an experimental value was in
use, ie
one that fell within the remit of section 10 of RFC5586, which, again, I
took to
be sufficient information.

Tom Petch

> I would be interested to also know what ACh Type it is actually
running
> on.
>
> Stewart
>
>
>
>


From agmalis@gmail.com  Sun Mar 18 05:32:29 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 9664D21F861C for <ietf@ietfa.amsl.com>; Sun, 18 Mar 2012 05:32:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.239
X-Spam-Level: 
X-Spam-Status: No, score=-3.239 tagged_above=-999 required=5 tests=[AWL=-0.240, BAYES_00=-2.599, J_CHICKENPOX_15=0.6, 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 V5E1yMq19SlT for <ietf@ietfa.amsl.com>; Sun, 18 Mar 2012 05:32:29 -0700 (PDT)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id F240921F860B for <ietf@ietf.org>; Sun, 18 Mar 2012 05:32:23 -0700 (PDT)
Received: by iazz13 with SMTP id z13so9359667iaz.31 for <ietf@ietf.org>; Sun, 18 Mar 2012 05:32:23 -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=+MeZfCNTYwL+KL213qB1DbRdosycY9F3YbeBRkCL8/c=; b=YOiGQBtQE7k42/z+INIZSemdSeRY1Xq3PCgVltBwPanAMzNqR4ZpI3Zp72uz1vf104 9zQrDqH5efkheub22cD4adXLRtMBuKHPpPWBkfHhVJBksfmvoX+sN2yW49mxQwk08zOd 6cuXx/rSMC2VyfJ4Y0b1LhQMnrriwDBF40kYu2MSrKylT5wXPRTw6liR6SdAWhInYtgL Ftv/nQB5iO/4/AzY4cTA/wRKzWIsZEKREpUi3afADPz5CZ3wLwJ15xijGcqtZWVd0aNj p2FQiYqb3PFPsglJQYp06mwYqWN49clN67jibkaUuKE8nJSqA7m0ruahypPjdxxL3Zxx 4Pdg==
Received: by 10.50.155.168 with SMTP id vx8mr3734613igb.11.1332073943409; Sun, 18 Mar 2012 05:32:23 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.50.222.136 with HTTP; Sun, 18 Mar 2012 05:32:02 -0700 (PDT)
In-Reply-To: <4F635846.60505@cisco.com>
References: <CAAHpaZ=JrKVKHZ0xkK-nszFDf-ttVNoi1p9iZiWa93vKuiNxZA@mail.gmail.com> <4F60BF02.1010507@cisco.com> <009b01cd0351$52d5f3c0$4001a8c0@gateway.2wire.net> <4F635846.60505@cisco.com>
From: "Andrew G. Malis" <agmalis@gmail.com>
Date: Sun, 18 Mar 2012 08:32:02 -0400
Message-ID: <CAA=duU2u5iKb+u9BcbtynRmDShXJ_A2DW9BQ2ayC=cQCSmU4HA@mail.gmail.com>
Subject: Re: Last Call:<draft-betts-itu-oam-ach-code-point-03.txt>(Allocationof an Associated Channel Code Point for Use by ITU-T Ethernet basedOAM) to Informational RFC
To: stbryant@cisco.com
Content-Type: text/plain; charset=ISO-8859-1
Cc: Fangyu Li <fangyuli1999@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, 18 Mar 2012 12:32:29 -0000

Stewart,

To answer your second question, SG15 C1123 (January 2011) states that
0x7FFA is the experimental ACh Type actually in use by CT.

Cheers,
Andy

On Fri, Mar 16, 2012 at 11:12 AM, Stewart Bryant <stbryant@cisco.com> wrote:
> On 16/03/2012 08:46, t.petch wrote:
>>
>> ----- Original Message -----
>> From: "Stewart Bryant"<stbryant@cisco.com>
>> To: "Fangyu Li"<fangyuli1999@gmail.com>
>> Cc:<lifang@catr.cn>;<ietf@ietf.org>
>> Sent: Wednesday, March 14, 2012 4:53 PM
>>>
>>> On 14/03/2012 13:36, Fangyu Li wrote:
>>>>
>>>> I support the allocation of an ACH codepoint to G.8113.1.
>>>> For G.8113.1 had reached the technical and industry maturity to be
>>>> assigned a code point, the codepoint allocation from IETF should allow
>>>> the ITU-T to progress refinements to G.8113.1 such that it could
>>>> satisfy all the functional requirements defined in RFC 5860.
>>>
>>> Please can you tell me version of the G.8113.1 text one would
>>> need to implement to be able to seamlessly interwork with the
>>> equipment that has already been been deployed?
>>
>> Stewart
>>
>> I am sure you already know the answer to that from posts made to the mpls
>> list,
>> where we have been told that there is currently an extensive deployment
>> ('running code') using an experimental value (interesting that there is a
>> last
>> call just ending seeking to exterminate such practice, at least for
>> application
>> protocols) and that the wish is to move to a standards-based value which
>> will,
>> perforce, be a different value.
>>
>> Tom Petch
>
>
> Tom,
>
> I don't think you understood my question.
>
> There are several version of the G.8113.1 text in circulation within
> the ITU-T. I was asking which version accurately describes the
> deployed protocol.
>
> I would be interested to also know what ACh Type it is actually running
> on.
>
> Stewart
>
>

From agmalis@gmail.com  Sun Mar 18 05:47:27 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 2D49521F85DA for <ietf@ietfa.amsl.com>; Sun, 18 Mar 2012 05:47:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.217
X-Spam-Level: 
X-Spam-Status: No, score=-3.217 tagged_above=-999 required=5 tests=[AWL=-0.218, BAYES_00=-2.599, J_CHICKENPOX_15=0.6, 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 CV71-3aVcQEM for <ietf@ietfa.amsl.com>; Sun, 18 Mar 2012 05:47:26 -0700 (PDT)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id 8F0CC21F85D9 for <ietf@ietf.org>; Sun, 18 Mar 2012 05:47:26 -0700 (PDT)
Received: by iazz13 with SMTP id z13so9374650iaz.31 for <ietf@ietf.org>; Sun, 18 Mar 2012 05:47:26 -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=nd+twRJnY11Q4eb09g1DBjCEC76/VGxTsflVP9dozGQ=; b=kQyV7dhrwL60hZq+0Xy44nDc41weEFifwMSTYZiJwQdEnpj4f2Prwc4uZgVC/cb02Z 1RAkwp90t+qcHN12KXZadr2Lz/8L9TfAUXj3QSPJsbEy405Ru7oeYyXe7YPc1cZHDvNK CSapOJIkUncVOw1R3Bz8yPSjW4EL9LiUejyiPxjSWw0Q0/+EskNNsI9HEZQte15t6Bch HKWlIMbnY/+5sBnu8eAic2i5npNMHfcDLMm3aEeGLS5B11LjOj7v9bUhGGrNLqJpPqkK R7m8rFP12v4jZLoqc/NJ6GkIS5006jpqToPFaK5jQp4DPo5F5huyfO6l5Y6uMyBypZYi +XYA==
Received: by 10.50.155.168 with SMTP id vx8mr3755425igb.11.1332074846182; Sun, 18 Mar 2012 05:47:26 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.50.222.136 with HTTP; Sun, 18 Mar 2012 05:47:06 -0700 (PDT)
In-Reply-To: <CAA=duU2u5iKb+u9BcbtynRmDShXJ_A2DW9BQ2ayC=cQCSmU4HA@mail.gmail.com>
References: <CAAHpaZ=JrKVKHZ0xkK-nszFDf-ttVNoi1p9iZiWa93vKuiNxZA@mail.gmail.com> <4F60BF02.1010507@cisco.com> <009b01cd0351$52d5f3c0$4001a8c0@gateway.2wire.net> <4F635846.60505@cisco.com> <CAA=duU2u5iKb+u9BcbtynRmDShXJ_A2DW9BQ2ayC=cQCSmU4HA@mail.gmail.com>
From: "Andrew G. Malis" <agmalis@gmail.com>
Date: Sun, 18 Mar 2012 08:47:06 -0400
Message-ID: <CAA=duU1YvFE1eb_kZ=XJCVi-_TCb_=2S83jr8hHyJ+sHWrRn9w@mail.gmail.com>
Subject: Re: Last Call:<draft-betts-itu-oam-ach-code-point-03.txt>(Allocationof an Associated Channel Code Point for Use by ITU-T Ethernet basedOAM) to Informational RFC
To: stbryant@cisco.com
Content-Type: text/plain; charset=ISO-8859-1
Cc: Fangyu Li <fangyuli1999@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, 18 Mar 2012 12:47:27 -0000

Whoops, I slightly misspoke. Amend my previous email to just say "To
answer your second question, SG15 C1123 (January 2011) states that
0x7FFA is the experimental ACh Type actually in use."

Cheers,
Andy

On Sun, Mar 18, 2012 at 8:32 AM, Andrew G. Malis <agmalis@gmail.com> wrote:
> Stewart,
>
> To answer your second question, SG15 C1123 (January 2011) states that
> 0x7FFA is the experimental ACh Type actually in use by CT.
>
> Cheers,
> Andy
>
> On Fri, Mar 16, 2012 at 11:12 AM, Stewart Bryant <stbryant@cisco.com> wrote:
>> On 16/03/2012 08:46, t.petch wrote:
>>>
>>> ----- Original Message -----
>>> From: "Stewart Bryant"<stbryant@cisco.com>
>>> To: "Fangyu Li"<fangyuli1999@gmail.com>
>>> Cc:<lifang@catr.cn>;<ietf@ietf.org>
>>> Sent: Wednesday, March 14, 2012 4:53 PM
>>>>
>>>> On 14/03/2012 13:36, Fangyu Li wrote:
>>>>>
>>>>> I support the allocation of an ACH codepoint to G.8113.1.
>>>>> For G.8113.1 had reached the technical and industry maturity to be
>>>>> assigned a code point, the codepoint allocation from IETF should allow
>>>>> the ITU-T to progress refinements to G.8113.1 such that it could
>>>>> satisfy all the functional requirements defined in RFC 5860.
>>>>
>>>> Please can you tell me version of the G.8113.1 text one would
>>>> need to implement to be able to seamlessly interwork with the
>>>> equipment that has already been been deployed?
>>>
>>> Stewart
>>>
>>> I am sure you already know the answer to that from posts made to the mpls
>>> list,
>>> where we have been told that there is currently an extensive deployment
>>> ('running code') using an experimental value (interesting that there is a
>>> last
>>> call just ending seeking to exterminate such practice, at least for
>>> application
>>> protocols) and that the wish is to move to a standards-based value which
>>> will,
>>> perforce, be a different value.
>>>
>>> Tom Petch
>>
>>
>> Tom,
>>
>> I don't think you understood my question.
>>
>> There are several version of the G.8113.1 text in circulation within
>> the ITU-T. I was asking which version accurately describes the
>> deployed protocol.
>>
>> I would be interested to also know what ACh Type it is actually running
>> on.
>>
>> Stewart
>>
>>

From henk.uijterwaal@gmail.com  Sun Mar 18 08:17:55 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 42CBD21F8646 for <ietf@ietfa.amsl.com>; Sun, 18 Mar 2012 08:17:55 -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 95heQwQf-CDw for <ietf@ietfa.amsl.com>; Sun, 18 Mar 2012 08:17:54 -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 6907B21F85F9 for <ietf@ietf.org>; Sun, 18 Mar 2012 08:17:54 -0700 (PDT)
Received: by eaaq11 with SMTP id q11so2698566eaa.31 for <ietf@ietf.org>; Sun, 18 Mar 2012 08:17:53 -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=KehMpUZIEUCMfthrnqTV08He57WgQcWwFnOtSYWSV4Y=; b=YBHGI5bNyzbZAQW5D2P444cb66EhbhgyOWIaiuiMicYbIPFcAB4oKR6amNf7xejxKo E/TlGuzlpSsc2qrBuKB9XVMFtPbIMxoqA2E5F2mpp7hHFJazzjzEkL2Z1P5+4xy7BTgg SDYUra81vsRsxy4tKjGzoa8Wv7nVfdZFsRHAUQOlxAZpwcaDr2PDsQ0Ad43YjIAse+LY NWjPzxF5uun86fbjMLrsNF89B+g6WJTPj7GImhXtz1oUoshrU/5cWbqdwujKzTPgphx2 CzF7xPRD5wPgs8duz9kikEVENu4+EF7rP8Kw+vsk35MJL8iBu8rm1EOrOC5dZbACFJe0 3qnw==
Received: by 10.213.33.199 with SMTP id i7mr571414ebd.165.1332083873380; Sun, 18 Mar 2012 08:17:53 -0700 (PDT)
Received: from geir.fritz.box ([2001:980:1203:1:e6ce:8fff:fe11:e7a8]) by mx.google.com with ESMTPS id e56sm662209eea.11.2012.03.18.08.17.51 (version=SSLv3 cipher=OTHER); Sun, 18 Mar 2012 08:17:52 -0700 (PDT)
Message-ID: <4F65FCA5.1090101@gmail.com>
Date: Sun, 18 Mar 2012 16:17:57 +0100
From: Henk Uijterwaal <henk.uijterwaal@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Query to the community -- An additional IETF Meeting event?
References: <20120316194918.18453.89483.idtracker@ietfa.amsl.com> <CB0BE66D-26E1-492C-B84C-44F6C0449995@cisco.com> <4F63AF60.4010004@dcrocker.net>
In-Reply-To: <4F63AF60.4010004@dcrocker.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
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: Sun, 18 Mar 2012 15:17:55 -0000

All,

We have had cases where the opening reception was sponsored by somebody other
than the host for the meeting (if there was a host).  The sponsor didn't get
much more than the possibility to put a sign near the front door and get
some recognition during one of the plenary sessions.  This proposal essentially
says that the sponsors can demonstrate equipment during the reception.
If that is helpful to attract sponsors, let's do it.  If there are sufficient
sponsors to support 2 receptions, let's organize 2.

And, having been to such sessions at NANOG and others, I know that you don't
have to look at the gear brought by the vendors, it is perfectly possible to
have the beer (for free) and have the hallway discussion you wanted to have
anyway, while ignoring the demos.

> The current question is about IETF community comfort with the IAOC's exploring
> this.  That is, it's a form of "may we proceed to do the research and planning?"
> query.

I'm fine with the IAOC doing the research.

Henk

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

There appears to have been a collective retreat from reality that day.
                                 (John Glanfield, on an engineering project)

From dhc@dcrocker.net  Sun Mar 18 10:41:31 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 8DC0321F8551 for <ietf@ietfa.amsl.com>; Sun, 18 Mar 2012 10:41:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.604
X-Spam-Level: 
X-Spam-Status: No, score=-6.604 tagged_above=-999 required=5 tests=[AWL=-0.005, 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 1qyszgPKE307 for <ietf@ietfa.amsl.com>; Sun, 18 Mar 2012 10:41:30 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id D41B621F853C for <ietf@ietf.org>; Sun, 18 Mar 2012 10:41:30 -0700 (PDT)
Received: from [192.168.1.11] (adsl-67-127-58-62.dsl.pltn13.pacbell.net [67.127.58.62]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q2IHfN0D005929 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Sun, 18 Mar 2012 10:41:28 -0700
Message-ID: <4F661E24.5060807@dcrocker.net>
Date: Sun, 18 Mar 2012 10:40:52 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Trade show at IETF
References: <20120316194918.18453.89483.idtracker@ietfa.amsl.com> <tslhaxocmii.fsf@mit.edu> <Pine.LNX.4.64.1203161629330.348@egate.xpasc.com> <4F63EDA3.8000001@gmail.com> <818BA8B64CF795AEFC4DAD5F@PST.JCK.COM> <4F6412E3.6060901@bogus.com> <4F642AC2.40200@bogus.com>
In-Reply-To: <4F642AC2.40200@bogus.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]); Sun, 18 Mar 2012 10:41:28 -0700 (PDT)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 18 Mar 2012 17:41:31 -0000

On 3/16/2012 11:10 PM, Joel jaeggli wrote:
> PMO or whatever it's called in given organzation is a different pool of
> money.

+1

-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From mail@sabahattin-gucukoglu.com  Mon Mar 19 03:55:52 2012
Return-Path: <mail@sabahattin-gucukoglu.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4C5F821F8518 for <ietf@ietfa.amsl.com>; Mon, 19 Mar 2012 03:55:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.288
X-Spam-Level: 
X-Spam-Status: No, score=-2.288 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HOST_MISMATCH_COM=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 m3qeyELCRUlc for <ietf@ietfa.amsl.com>; Mon, 19 Mar 2012 03:55:51 -0700 (PDT)
Received: from Mintaka.sabahattin-gucukoglu.com (Mintaka.sabahattin-gucukoglu.com [IPv6:2001:470:babd::1]) by ietfa.amsl.com (Postfix) with ESMTP id D0C8721F84F3 for <ietf@ietf.org>; Mon, 19 Mar 2012 03:55:51 -0700 (PDT)
Received: by Mintaka.sabahattin-gucukoglu.com (Postfix, from userid 1000) id 8C90F104292; Mon, 19 Mar 2012 10:55:50 +0000 (GMT)
Received: from [192.168.1.28] (natbox.sabahattin-gucukoglu.com [213.123.192.30]) (using SMTP over TLS) by Mintaka.sabahattin-gucukoglu.com (tmda-ofmipd) with ESMTP; Mon, 19 Mar 2012 10:55:49 +0000
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: IPv6 Zone Identifiers Considered Hateful
Date: Mon, 19 Mar 2012 10:55:48 +0000
Message-Id: <82A794CE-B328-475F-9300-1B6BE628F7E3@sabahattin-gucukoglu.com>
To: ietf@ietf.org
Mime-Version: 1.0 (Apple Message framework v1257)
X-Mailer: Apple Mail (2.1257)
X-Delivery-Agent: TMDA/1.1.12-kg3 (Haumea)
From: Sabahattin Gucukoglu <mail@sabahattin-gucukoglu.com>
X-Primary-Address: mail@sabahattin-gucukoglu.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Sabahattin Gucukoglu <mail-dated-1334746550.15c4ac@sabahattin-gucukoglu.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, 19 Mar 2012 10:55:52 -0000

I've obviously not been doing all my homework, and RFC 4007 slipped my =
attention.  Worse, for all the communication my IPv6 nodes are doing =
amongst themselves using link-local addresses, it's never really been =
much more than a hastily-justified curiosity why, when I ping one from =
the other using link-local-scoped addresses, I have to put in this zone =
identifier (%ifname on BSD and Linux).

Yesterday, I configured a DNS server to listen just using a link-local =
address, the one autoconfigured for an ethernet card accessible to all =
the nodes.  It's a host, not a router, so I'm relying on that address =
not being routable and being filtered at the router.  It didn't work.  =
The server would not start until I specified the zone suffix.  Now I am =
wondering why, given that there is no ambiguous link-local address =
anywhere around here, I need to do that.  Can't it figure it out itself?

What about the other problems with this suffix?  It's host-specific, so =
it's unsafe to share it over the network (I need to share the DNS server =
using stateless DHCPv6).  The format differs between OSes (Windows uses =
%n).  It interferes with URLs, if Wikipedia is to be believed.  It =
breaks expectations, essentially because it's the exception to the rule =
that the address bits (and hence the address format) conveys all the =
required information.

So zone suffixes are considered hateful.  Yes, it's true, I enjoy a good =
whinge and it's a shame I had to learn this on-demand, but really, their =
use should be limited to just those circs where it's actually necessary, =
and let's be honest, that ought to be very rare.

Cheers,
Sabahattin

From maarten.vissers@huawei.com  Mon Mar 19 03:58:08 2012
Return-Path: <maarten.vissers@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 51AA521F8518 for <ietf@ietfa.amsl.com>; Mon, 19 Mar 2012 03:58: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 LIcWVkM24UMV for <ietf@ietfa.amsl.com>; Mon, 19 Mar 2012 03:58:07 -0700 (PDT)
Received: from dfwrgout.huawei.com (dfwrgout.huawei.com [206.16.17.72]) by ietfa.amsl.com (Postfix) with ESMTP id 6F8BE21F867D for <ietf@ietf.org>; Mon, 19 Mar 2012 03:58:07 -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 AEE91550; Mon, 19 Mar 2012 06:58:07 -0400 (EDT)
Received: from DFWEML405-HUB.china.huawei.com (10.193.5.102) by dfweml201-edg.china.huawei.com (172.18.9.107) with Microsoft SMTP Server (TLS) id 14.1.323.3; Mon, 19 Mar 2012 03:55:34 -0700
Received: from LHREML403-HUB.china.huawei.com (10.201.5.217) by dfweml405-hub.china.huawei.com (10.193.5.102) with Microsoft SMTP Server (TLS) id 14.1.323.3; Mon, 19 Mar 2012 03:55:35 -0700
Received: from LHREML509-MBX.china.huawei.com ([10.201.4.177]) by lhreml403-hub.china.huawei.com ([::1]) with mapi id 14.01.0323.003; Mon, 19 Mar 2012 10:55:31 +0000
From: Maarten vissers <maarten.vissers@huawei.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt> (Allocation of	an Associated Channel Code Point for Use by	ITU-T Ethernet based OAM) to Informational RFC
Thread-Topic: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt> (Allocation of	an Associated Channel Code Point for Use by	ITU-T Ethernet based OAM) to Informational RFC
Thread-Index: AQHNBbwlpj6Vj91Q2Emyt7zwdRdBQJZxb8ng
Date: Mon, 19 Mar 2012 10:55:31 +0000
Message-ID: <D62E6669B3621943B7632961308F8F9E0DD76853@lhreml509-mbx>
References: <52981DB05D3C5247A12D0AEE309F3CC202444231EB23@INOAVREX11.ptin.corpPT.com> <4F670C21.1040905@gmail.com>
In-Reply-To: <4F670C21.1040905@gmail.com>
Accept-Language: en-GB, en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.202.113.179]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Mar 2012 10:58:08 -0000

+1

-------- Original Message --------
From: Rui Costa <RCosta@ptinovacao.pt>
Sent: zaterdag 17 maart 2012 12:00:56 +0000
To: ietf@ietf.org <ietf@ietf.org>
Subject: RE: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt>=20
(Allocation of	an Associated Channel Code Point for Use by	ITU-T=20
Ethernet based OAM) to Informational RFC

Hello,=09

I support the allocation of an ACH codepoint to G.8113.1, not precluding=20
the ITU-T to progress refinements. Ergo, i support this draft and=20
proposal http://www.ietf.org/mail-archive/web/ietf/current/msg72191.html

IMHO, the status quo analysis expressed in both=20
http://www.ietf.org/mail-archive/web/ietf/current/msg72188.html and=20
http://www.ietf.org/mail-archive/web/ietf/current/msg72273.html is=20
accurate.=09

Regards,=09
Rui=09
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D


-------- Original Message --------
From: The IESG <iesg-secretary@ietf.org>
Sent: Wed, 22 Feb 2012 07:12:52 -0800
To: IETF-Announce <ietf-announce@ietf.org>
Subject: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt>=20
(Allocation of	an Associated Channel Code Point for Use by ITU-T=20
Ethernet	based OAM) to Informational RFC

The IESG has received a request from an individual submitter to consider=20
the following document:
- 'Allocation of an Associated Channel Code Point for Use by ITU-T
     Ethernet based OAM'
    <draft-betts-itu-oam-ach-code-point-03.txt> as an Informational RFC

The IESG plans to make a decision in the next few weeks, and solicits=20
final comments on this action. Please send substantive comments to the=20
ietf@ietf.org mailing lists by 2012-03-21. Exceptionally, comments may=20
be sent to iesg@ietf.org instead. In either case, please retain the=20
beginning of the Subject line to allow automated sorting.

Abstract

     This document assigns an Associated Channel Type code point for
     carrying Ethernet based Operations, Administration, and Management
     messages in the MPLS Generic Associated Channel (G-ACh).

The file can be obtained via
http://datatracker.ietf.org/doc/draft-betts-itu-oam-ach-code-point/

IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-betts-itu-oam-ach-code-point/


No IPR declarations have been submitted directly on this I-D.
_______________________________________________
IETF mailing list
IETF@ietf.org
https://www.ietf.org/mailman/listinfo/ietf=09


From wesley.george@twcable.com  Mon Mar 19 05:46:11 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 3A87521F85A0 for <ietf@ietfa.amsl.com>; Mon, 19 Mar 2012 05:46:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.058
X-Spam-Level: 
X-Spam-Status: No, score=-1.058 tagged_above=-999 required=5 tests=[AWL=0.405,  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 maFHThGaiKyF for <ietf@ietfa.amsl.com>; Mon, 19 Mar 2012 05:46:10 -0700 (PDT)
Received: from cdpipgw01.twcable.com (cdpipgw01.twcable.com [165.237.59.22]) by ietfa.amsl.com (Postfix) with ESMTP id 82D2621F8585 for <ietf@ietf.org>; Mon, 19 Mar 2012 05:46:10 -0700 (PDT)
X-SENDER-IP: 10.136.163.11
X-SENDER-REPUTATION: None
X-IronPort-AV: E=Sophos;i="4.73,611,1325480400"; d="scan'208";a="355617834"
Received: from unknown (HELO PRVPEXHUB02.corp.twcable.com) ([10.136.163.11]) by cdpipgw01.twcable.com with ESMTP/TLS/RC4-MD5; 19 Mar 2012 08:45:28 -0400
Received: from PRVPEXVS03.corp.twcable.com ([10.136.163.27]) by PRVPEXHUB02.corp.twcable.com ([10.136.163.11]) with mapi; Mon, 19 Mar 2012 08:46:09 -0400
From: "George, Wes" <wesley.george@twcable.com>
To: "henk@uijterwaal.nl" <henk@uijterwaal.nl>, "ietf@ietf.org" <ietf@ietf.org>
Date: Mon, 19 Mar 2012 08:46:13 -0400
Subject: RE: Query to the community -- An additional IETF Meeting event?
Thread-Topic: Query to the community -- An additional IETF Meeting event?
Thread-Index: Ac0FGltMQG1Smv+xQAS7cDTNU7B2DAAsCJKQ
Message-ID: <DCC302FAA9FE5F4BBA4DCAD465693779173C924EA3@PRVPEXVS03.corp.twcable.com>
References: <20120316194918.18453.89483.idtracker@ietfa.amsl.com> <CB0BE66D-26E1-492C-B84C-44F6C0449995@cisco.com> <4F63AF60.4010004@dcrocker.net> <4F65FCA5.1090101@gmail.com>
In-Reply-To: <4F65FCA5.1090101@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Mar 2012 12:46:11 -0000

> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of H=
enk
> Uijterwaal
>
> We have had cases where the opening reception was sponsored by somebody o=
ther
> than the host for the meeting (if there was a host).  The sponsor didn't =
get
> much more than the possibility to put a sign near the front door and get
> some recognition during one of the plenary sessions.  This proposal
> essentially
> says that the sponsors can demonstrate equipment during the reception.

[WEG] +1
I was one of the people who suggested this to IAOC after recently attending=
 my first NANOG in a good while.  While I realize the audiences (and theref=
ore the attractiveness to marketing budgets) are different, the sharp contr=
ast between the two made it clear that there may be some opportunities to t=
weak IETF's sponsorship methods and potentially reduce the costs attendees =
are asked to bear without turning it into yet another tradeshow or forcing =
I* members to wear auto-racing-style suits emblazoned with vendor logos. :-=
)
In addition to Beer-n-gear, NANOG had 2 other sponsored (i.e. free to all a=
ttendees) socials, and enough free T-shirts to last a person a week, plus 3=
-4 slides full of sponsor logos. Not that we need any more free t-shirts, b=
ut compare that to this IETF, where if you want a shirt, you must purchase =
it because we didn't have a primary sponsor until Cisco took pity on us (an=
d apparently the shirt cannot be sponsored separately).

That said, I don't think that this potential experiment requires a *separat=
e* night. I'd much prefer to replace the  current "overpriced hotel cash ba=
r" arrangement at the welcome reception with something more like beer-n-gea=
r. I'm also willing to try it in lieu of a social event, since those are ty=
pically hit or miss in terms of whether the environment is conducive to soc=
ializing, whether they're worth the additional money one must pay to attend=
 them, and the fact that these are generally limited participation (tickets=
 required), thereby reducing the opportunities for group socialization.

> And, having been to such sessions at NANOG and others, I know that you do=
n't
> have to look at the gear brought by the vendors, it is perfectly possible=
 to
> have the beer (for free) and have the hallway discussion you wanted to ha=
ve
> anyway, while ignoring the demos.
[WEG] This is definitely true. The two are not mutually exclusive.

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 Francis.Dupont@fdupont.fr  Mon Mar 19 05:56:03 2012
Return-Path: <Francis.Dupont@fdupont.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 7522221F8653 for <ietf@ietfa.amsl.com>; Mon, 19 Mar 2012 05:56:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.567
X-Spam-Level: 
X-Spam-Status: No, score=-2.567 tagged_above=-999 required=5 tests=[AWL=0.032,  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 kRqUd3iV7Ml2 for <ietf@ietfa.amsl.com>; Mon, 19 Mar 2012 05:56:03 -0700 (PDT)
Received: from givry.fdupont.fr (givry.fdupont.fr [IPv6:2001:41d0:1:6d55:211:5bff:fe98:d51e]) by ietfa.amsl.com (Postfix) with ESMTP id 9F20521F864D for <ietf@ietf.org>; Mon, 19 Mar 2012 05:56:02 -0700 (PDT)
Received: from givry.fdupont.fr (localhost [127.0.0.1]) by givry.fdupont.fr (8.14.3/8.14.3) with ESMTP id q2JCu0Mn014776; Mon, 19 Mar 2012 13:56:00 +0100 (CET) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201203191256.q2JCu0Mn014776@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: Sabahattin Gucukoglu <mail-dated-1334746550.15c4ac@sabahattin-gucukoglu.com>
Subject: Re: IPv6 Zone Identifiers Considered Hateful 
In-reply-to: Your message of Mon, 19 Mar 2012 10:55:48 GMT. <82A794CE-B328-475F-9300-1B6BE628F7E3@sabahattin-gucukoglu.com> 
Date: Mon, 19 Mar 2012 13:56:00 +0100
Sender: Francis.Dupont@fdupont.fr
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, 19 Mar 2012 12:56:03 -0000

 In your previous mail you wrote:

>  So zone suffixes are considered hateful.

=> in fact it is not the problem: link-local address
are considered hateful.

Regards

Francis.Dupont@fdupont.fr

PS: at least for use in standard applications.

From sant9442@gmail.com  Mon Mar 19 06:13:22 2012
Return-Path: <sant9442@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8126721F84B3 for <ietf@ietfa.amsl.com>; Mon, 19 Mar 2012 06:13:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.259
X-Spam-Level: 
X-Spam-Status: No, score=-3.259 tagged_above=-999 required=5 tests=[AWL=0.340,  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 02JQMVbqJvja for <ietf@ietfa.amsl.com>; Mon, 19 Mar 2012 06:13:21 -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 6854621F866B for <ietf@ietf.org>; Mon, 19 Mar 2012 06:13:21 -0700 (PDT)
Received: by yhkk25 with SMTP id k25so3064946yhk.31 for <ietf@ietf.org>; Mon, 19 Mar 2012 06:13: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=qhmA7Liaa2IhSYH/TKWRbHUn66U8OF0lcwDfKGz8CAY=; b=XjOQawIBUVuETL+ZpqMhdZIXlpR3LZoR777zRjSpoVeG6dcqBIoMuCp4j8Yh+sGhIy TpvZINy4zr9LaEVWa+dHL5O1vWpiera30lniJwYBjck3T+JS3shs9EH3foZyy25Iya42 fxXWehp23+uEIqz8j+/VUr+QDjqv/UR6zzXEv5D5Drz/B40X/i2BQHflRvp/vp1JwmRx 7T9FzQeK9AB92gV0/wWb0td7SJ0MhIBfjPTqqJ8BIbel5Hsxdicojw5o90p41BNmO5IY xd8nY2err4yazpHF4d0kOoNjSi4Ms/1Jg2MWI3YN0+Qis8HM1DJhzK20HxW/HAwvM+GX 8bbQ==
Received: by 10.236.124.3 with SMTP id w3mr12325381yhh.101.1332162800895; Mon, 19 Mar 2012 06:13:20 -0700 (PDT)
Received: from adsl-215-50-126.mia.bellsouth.net (99-3-147-93.lightspeed.miamfl.sbcglobal.net. [99.3.147.93]) by mx.google.com with ESMTPS id j29sm8073111yhi.19.2012.03.19.06.13.18 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 19 Mar 2012 06:13:19 -0700 (PDT)
Message-ID: <4F67313D.8050103@gmail.com>
Date: Mon, 19 Mar 2012 09:14:37 -0400
From: Hector <sant9442@gmail.com>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Trade show at IETF
References: <20120316194918.18453.89483.idtracker@ietfa.amsl.com>	<tslhaxocmii.fsf@mit.edu>	<Pine.LNX.4.64.1203161629330.348@egate.xpasc.com>	<4F63EDA3.8000001@gmail.com> <818BA8B64CF795AEFC4DAD5F@PST.JCK.COM>	<4F6412E3.6060901@bogus.com> <AFB757E6C30BF6E334785373@PST.JCK.COM>
In-Reply-To: <AFB757E6C30BF6E334785373@PST.JCK.COM>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Mar 2012 13:13:22 -0000

Separate budgets, but it really all depends on the type of "Trade 
Shows" the IETF is contemplating. I will note it does spike my 
interest to consider going to a IETF event from a technical sales 
standpoint, illustrating products built on IETF standardized protocol 
efforts, developing technology transfer agreements, joint ventures, 
etc.   But if targeting a consumer market, thats a different set of 
departmental cost issues (Sales, engineers, technicians, etc).

My only warning with this is that it make become too successful! It 
may actually attracts more vendors, especially among those whose main 
interest is as implementators and don't care much for the getting 
involved with the protocol development politics.  As it gets bigger, 
the IETF will need to be ready with larger locations and offering 
pre-ordering space selections for the next events.   This is very 
important part of the strategic booth location planning.  Finally, a 
certain level of commitment will need to be shown because if the IETF 
does eventually decide it no longer wants (or can't) to get into this 
area, then refunds will be needed and whole slew of legal messy 
contract lawyers are needed.   Also, once its reaches of level where 
its big part of the IETF, it might begin to see the unions knocking on 
the door which adds even more cost.

--
HLS

John C Klensin wrote:
> 
> --On Friday, March 16, 2012 21:28 -0700 Joel jaeggli
> <joelja@bogus.com> wrote:
> 
>> On 3/16/12 20:04 , John C Klensin wrote:
>>> Note too that, if the company sends only five technical people
>>> and concludes that it doesn't suffer harm from that small a
>>> number, the odds of getting back up to 10 if the experiment is
>>> terminated and those five sales/market types disappear is just
>>> about zero, at least until the economy improves considerable.
>>>
>>> Scale and juggle the figures as you like, this is not a
>>> zero-risk experiment.
>> You know nothing about marketing budgets.
> 
> Sorry, Joel.  I have both had to administer those budgets and
> policies, been the victim of them, as well as seen it go on in
> companies with whom I've done consulting work on organizational
> and strategic matters.  Companies differ -- I tried to say that
> -- but in many companies that are really oriented toward the
> bottom line, marketing controls virtually all travel budgets.
> In a few, sales and/or controls and perceptions of their needs
> control almost all budget categories: Engineering is rarely a
> profit center, the money has to come from somewhere, and the
> organizational question is how much control the money source and
> its needs affect how it is spent.
> 
> I didn't mean to suggest that the effects would be felt
> immediately -- there are usually budget cycles.  But, over the
> medium term, even more relaxed organizations in tight budget
> situations do tend to eventually notice "total number of people
> attending from company", and push back.   If the attendees
> include both people from cost centers and people from profit
> centers, the latter tend to win the battle for slots, or at
> least to win less.
> 
> But I suppose I should defer to your superior experience in
> senior management and corporate finance roles.
> 
>     john
> 
> 
> 
> 

From eburger@standardstrack.com  Mon Mar 19 06:58:35 2012
Return-Path: <eburger@standardstrack.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EDDD021F8642 for <ietf@ietfa.amsl.com>; Mon, 19 Mar 2012 06:58:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.401
X-Spam-Level: 
X-Spam-Status: No, score=-102.401 tagged_above=-999 required=5 tests=[AWL=0.198, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZXCkIKfxrTpd for <ietf@ietfa.amsl.com>; Mon, 19 Mar 2012 06:58:34 -0700 (PDT)
Received: from biz104.inmotionhosting.com (biz104.inmotionhosting.com [173.247.254.120]) by ietfa.amsl.com (Postfix) with ESMTP id F1AFE21F863F for <ietf@ietf.org>; Mon, 19 Mar 2012 06:58:33 -0700 (PDT)
Received: from ip68-100-199-8.dc.dc.cox.net ([68.100.199.8]:59485 helo=[192.168.15.135]) by biz104.inmotionhosting.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69) (envelope-from <eburger@standardstrack.com>) id 1S9d6L-0007Js-Fj; Mon, 19 Mar 2012 06:58:22 -0700
Subject: Re: Issues relating to managing a mailing list... 
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/signed; boundary=Apple-Mail-103--476494445; protocol="application/pkcs7-signature"; micalg=sha1
From: Eric Burger <eburger@standardstrack.com>
In-Reply-To: <30461C26-EDCE-4BFD-8E82-AF1CC5BC371C@vigilsec.com>
Date: Mon, 19 Mar 2012 09:58:27 -0400
Message-Id: <1D7BB28F-062D-41A0-8536-B9FBA526F0ED@standardstrack.com>
References: <1344A266-28E8-4228-908F-395FB41EDA83@amsl.com> <30461C26-EDCE-4BFD-8E82-AF1CC5BC371C@vigilsec.com>
To: Russ Housley <housley@vigilsec.com>
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: 
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, 19 Mar 2012 13:58:35 -0000

--Apple-Mail-103--476494445
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

I am responding to Russ' original message, because it is too hard to =
pick one of the 52 responses received so far. A quick count is something =
like <10 thinking this is a good idea with the remainder thinking this =
idea ranks somewhere between really bad and evil.

Apps Area people who have thought deeply about the topic over the last =
25 years are in near unanimous agreement this idea is on the evil end of =
the spectrum.  While Apps Area folks do not have a monopoly on email =
ideas, I would offer we listen carefully.  This idea brings out a whole =
host of very old (and solved!) issues:
   o  What constitutes a message? (if you strip stuff, you will break =
signatures)
   o  What is an attachment? (is it useless cruft like TNEF or is it =
S/MIME? What about the next part type?)
   o  What about using 15-year-old solutions like HTTP on the composing =
side?
   o  What about using 10-year-old solutions like IMAP 4?
   o  ...

If another vote in the Nay column is needed, here it is. Nay.
--
- Eric

On Mar 14, 2012, at 7:46 PM, Russ Housley wrote:

> Some suggestions have been made about the IETF mail lists.
> There is a way for mailman to strip attachments and put them
> in a place for downloading with a web browser.  This would be
> a significant change to current practice, so the community
> needs to consider this potential policy change.
>=20
> What do you think?
>=20
> Russ
>=20
>=20
>>>>> The only bug in the soup is that it seemed to me that we might
>>>>> want to look into an alternative approach.  We have asked people
>>>>> to post large documents somewhere and only send a pointer.  Not
>>>>> everyone can do that, lots of people forget, and some people are
>>>>> just not willing to take the extra step.
>>>>>=20
>>>>> Plus, we cannot expect people to keep things posted on their own
>>>>> personal, or their company's, web-site indefinitely.  If they
>>>>> don't keep it there, then the pointer in the archive will become
>>>>> stale, and information that should probably be there is lost.
>>>>>=20
>>>>> So we need a solution to the issue with really big email messages
>>>>> sometime.
>>>>>=20
>>>>> One solution might be to simpy strip attachments off, put them
>>>>> in the archive and replace them with a pointer.  That shouldn't
>>>>> be that hard, since a lot of anti-virus software does something
>>>>> similar with suspect attachment types.
>>>>>=20
>>>>> Or we could - once again - ask people to post attachments and use
>>>>> a pointer in their mail, only provide them with a place to post
>>>>> them in the same general area as the mail archive.
>>>>>=20
>>>>> If there is already something like this in place, please let me
>>>>> know what it is and I will add a pointer to it in my "too big"
>>>>> rejection messages.
>>>>>=20
>>>>> The thing about threaded messages getting too big is a slightly
>>>>> different issue, brought about by the increasing use of HTML
>>>>> format email.  I talked years ago about this with Scott Bradner
>>>>> because I really think that HTML format messages are useful and
>>>>> relatively easy to read when compared to plain old text.
>>>>>=20
>>>>> But using HTML leads to messages that are deceptively big.
>>>>>=20
>>>>> Possibly the right answer in that case is to bump the size limit
>>>>> up to maybe 100K.  Even with HTML format, people will many likely
>>>>> realize that nobody is going to read past the 10th back message
>>>>> in any case (or if they do want to, they can look at the thread
>>>>> in the archive).
>>>>>=20
>>>>> But even that approach is not fool proof, and there are a lot of
>>>>> resourceful fools out there.
>>>>>=20
>>>>> Just trying to be creative, and help out...
>=20


--Apple-Mail-103--476494445
Content-Disposition: attachment;
	filename=smime.p7s
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIPODCCBN0w
ggPFoAMCAQICEHGS++YZX6xNEoV0cTSiGKcwDQYJKoZIhvcNAQEFBQAwezELMAkGA1UEBhMCR0Ix
GzAZBgNVBAgMEkdyZWF0ZXIgTWFuY2hlc3RlcjEQMA4GA1UEBwwHU2FsZm9yZDEaMBgGA1UECgwR
Q29tb2RvIENBIExpbWl0ZWQxITAfBgNVBAMMGEFBQSBDZXJ0aWZpY2F0ZSBTZXJ2aWNlczAeFw0w
NDAxMDEwMDAwMDBaFw0yODEyMzEyMzU5NTlaMIGuMQswCQYDVQQGEwJVUzELMAkGA1UECBMCVVQx
FzAVBgNVBAcTDlNhbHQgTGFrZSBDaXR5MR4wHAYDVQQKExVUaGUgVVNFUlRSVVNUIE5ldHdvcmsx
ITAfBgNVBAsTGGh0dHA6Ly93d3cudXNlcnRydXN0LmNvbTE2MDQGA1UEAxMtVVROLVVTRVJGaXJz
dC1DbGllbnQgQXV0aGVudGljYXRpb24gYW5kIEVtYWlsMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8A
MIIBCgKCAQEAsjmFpPJ9q0E7YkY3rs3BYHW8OWX5ShpHornMSMxqmNVNNRm5pELlzkniii8efNIx
B8dOtINknS4p1aJkxIW9hVE1eaROaJB7HHqkkqgX8pgV8pPMyaQylbsMTzC9mKALi+VuG6JG+ni8
om+rWV6lL8/K2m2qL+usobNqqrcuZzWLeeEeaYji5kbNoKXqvgvOdjp6Dpvq/NonWz1zHyLmSGHG
TPNpsaguG7bUMSAsvIKKjqQOpdeJQ/wWWq8dcdcRWdq6hw2v+vPhwvCkxWeM1tZUOt4KpLoDd7Nl
yP0e03RiqhjKaJMeoYV+9Udly/hNVyh00jT/MLbu9mIwFIws6wIDAQABo4IBJzCCASMwHwYDVR0j
BBgwFoAUoBEKIz6W8Qfs4q8p74Klf9AwpLQwHQYDVR0OBBYEFImCZ33EnSZwAEu0UEh83j2uBG59
MA4GA1UdDwEB/wQEAwIBBjAPBgNVHRMBAf8EBTADAQH/MB0GA1UdJQQWMBQGCCsGAQUFBwMCBggr
BgEFBQcDBDARBgNVHSAECjAIMAYGBFUdIAAwewYDVR0fBHQwcjA4oDagNIYyaHR0cDovL2NybC5j
b21vZG9jYS5jb20vQUFBQ2VydGlmaWNhdGVTZXJ2aWNlcy5jcmwwNqA0oDKGMGh0dHA6Ly9jcmwu
Y29tb2RvLm5ldC9BQUFDZXJ0aWZpY2F0ZVNlcnZpY2VzLmNybDARBglghkgBhvhCAQEEBAMCAQYw
DQYJKoZIhvcNAQEFBQADggEBAJ2Vyzy4fqUJxB6/C8LHdo45PJTGEKpPDMngq4RdiVTgZTvzbRx8
NywlVF+WIfw3hJGdFdwUT4HPVB1rbEVgxy35l1FM+WbKPKCCjKbI8OLp1Er57D9Wyd12jMOCAU9s
APMeGmF0BEcDqcZAV5G8ZSLFJ2dPV9tkWtmNH7qGL/QGrpxp7en0zykX2OBKnxogL5dMUbtGB8SK
N04g4wkxaMeexIud6H4RvDJoEJYRmETYKlFgTYjrdDrfQwYyyDlWjDoRUtNBpEMD9O3vMyfbOeAU
TibJ2PU54om4k123KSZB6rObroP8d3XK6Mq1/uJlSmM+RMTQw16Hc6mYHK9/FX8wggUaMIIEAqAD
AgECAhBtGeqnGU9qMyLmIjJ6qnHeMA0GCSqGSIb3DQEBBQUAMIGuMQswCQYDVQQGEwJVUzELMAkG
A1UECBMCVVQxFzAVBgNVBAcTDlNhbHQgTGFrZSBDaXR5MR4wHAYDVQQKExVUaGUgVVNFUlRSVVNU
IE5ldHdvcmsxITAfBgNVBAsTGGh0dHA6Ly93d3cudXNlcnRydXN0LmNvbTE2MDQGA1UEAxMtVVRO
LVVTRVJGaXJzdC1DbGllbnQgQXV0aGVudGljYXRpb24gYW5kIEVtYWlsMB4XDTExMDQyODAwMDAw
MFoXDTIwMDUzMDEwNDgzOFowgZMxCzAJBgNVBAYTAkdCMRswGQYDVQQIExJHcmVhdGVyIE1hbmNo
ZXN0ZXIxEDAOBgNVBAcTB1NhbGZvcmQxGjAYBgNVBAoTEUNPTU9ETyBDQSBMaW1pdGVkMTkwNwYD
VQQDEzBDT01PRE8gQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBTZWN1cmUgRW1haWwgQ0EwggEi
MA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCShIRbS1eY1F4vi6ThQMijU1hfZmXxMk73nzJ9
VdB4TFW3QpTg+SdxB8XGaaS5MsTxQBqQzCdWYn8XtXFpruUgG+TLY15gyqJB9mrho/+43x9IbWVD
jCouK2M4d9+xF6zC2oIC1tQyatRnbyATj1w1+uVUgK/YcQodNwoCUFNslR2pEBS0mZVZEjH/CaLS
TNxS297iQAFbSGjdxUq04O0kHzqvcV8H46y/FDuwJXFoPfQP1hdYRhWBPGiLi4MPbXohV+Y0sNsy
fuNK4aVScmQmkU6lkg//4LFg/RpvaFGZY40ai6XMQpubfSJj06mg/M6ekN9EGfRcWzW6FvOnm//B
AgMBAAGjggFLMIIBRzAfBgNVHSMEGDAWgBSJgmd9xJ0mcABLtFBIfN49rgRufTAdBgNVHQ4EFgQU
ehNOAHRbxnhjZCfBL+KgW7x5xXswDgYDVR0PAQH/BAQDAgEGMBIGA1UdEwEB/wQIMAYBAf8CAQAw
EQYDVR0gBAowCDAGBgRVHSAAMFgGA1UdHwRRME8wTaBLoEmGR2h0dHA6Ly9jcmwudXNlcnRydXN0
LmNvbS9VVE4tVVNFUkZpcnN0LUNsaWVudEF1dGhlbnRpY2F0aW9uYW5kRW1haWwuY3JsMHQGCCsG
AQUFBwEBBGgwZjA9BggrBgEFBQcwAoYxaHR0cDovL2NydC51c2VydHJ1c3QuY29tL1VUTkFkZFRy
dXN0Q2xpZW50X0NBLmNydDAlBggrBgEFBQcwAYYZaHR0cDovL29jc3AudXNlcnRydXN0LmNvbTAN
BgkqhkiG9w0BAQUFAAOCAQEAhda+eFdVbTN/RFL+QtUGqAEDgIr7DbL9Sr/2r0FJ9RtaxdKtG3Nu
PukmfOZMmMEwKN/L+0I8oSU+CnXW0D05hmbRoZu1TZtvryhsHa/l6nRaqNqxwPF1ei+eupN5yv7i
kR5WdLL4jdPgQ3Ib7Y/9YDkgR/uLrzplSDyYPaUlv73vYOBJ5RbI6z9Dg/Dg7g3B080zX5vQvWBq
szv++tTJOjwf7Zv/m0kzvkIpOYPuM2kugp1FTahp2oAbHj3SGl18R5mlmwhtEpmG1l1XBxunML5L
SUS4kH7K0Xk467Qz+qA6XSZYnmFVGLQh1ZnV4ENAQjC+6qXnlNKw/vN1+X9u5zCCBTUwggQdoAMC
AQICEDWub7CYfsGXUhthgY5vuwcwDQYJKoZIhvcNAQEFBQAwgZMxCzAJBgNVBAYTAkdCMRswGQYD
VQQIExJHcmVhdGVyIE1hbmNoZXN0ZXIxEDAOBgNVBAcTB1NhbGZvcmQxGjAYBgNVBAoTEUNPTU9E
TyBDQSBMaW1pdGVkMTkwNwYDVQQDEzBDT01PRE8gQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBT
ZWN1cmUgRW1haWwgQ0EwHhcNMTEwOTA5MDAwMDAwWhcNMTIwOTA4MjM1OTU5WjArMSkwJwYJKoZI
hvcNAQkBFhplYnVyZ2VyQHN0YW5kYXJkc3RyYWNrLmNvbTCCASIwDQYJKoZIhvcNAQEBBQADggEP
ADCCAQoCggEBAML1VN+kPTw2iXeq1Yag6nChmCSmvCGACE3X9APNsUP2GvbYNFj6qdkayJJdhy0T
aIzCiMW01sD5mSV4mi0w8EfXKn/cwqi1Brw06fwaI4T2iGXA/0zb272GR57uoH1VjMd0/Qc1h2CJ
9ueUwsxP9ufXm7Kb9+DkLGDAU+6jQQv9rTiNz8sSyjOTSmtrsVpk5MTRn0np6fybkyxcjNy2cLTX
56+gfF4SxgukWt0XAWI49y+PAp2AyG9RxX/1kTZPCEPLzitGpDTGPN7HH9sdvXyyhNT73i20BtZ0
FHRfhLIo1bRqnl3W06JjVOkNbUxFbE4p01FrF7O/kRk+WZ+FMVcCAwEAAaOCAeowggHmMB8GA1Ud
IwQYMBaAFHoTTgB0W8Z4Y2QnwS/ioFu8ecV7MB0GA1UdDgQWBBSMC0QogJ7C8csD5XuRaGotm7qC
mDAOBgNVHQ8BAf8EBAMCBaAwDAYDVR0TAQH/BAIwADAgBgNVHSUEGTAXBggrBgEFBQcDBAYLKwYB
BAGyMQEDBQIwEQYJYIZIAYb4QgEBBAQDAgUgMEYGA1UdIAQ/MD0wOwYMKwYBBAGyMQECAQEBMCsw
KQYIKwYBBQUHAgEWHWh0dHBzOi8vc2VjdXJlLmNvbW9kby5uZXQvQ1BTMFcGA1UdHwRQME4wTKBK
oEiGRmh0dHA6Ly9jcmwuY29tb2RvY2EuY29tL0NPTU9ET0NsaWVudEF1dGhlbnRpY2F0aW9uYW5k
U2VjdXJlRW1haWxDQS5jcmwwgYgGCCsGAQUFBwEBBHwwejBSBggrBgEFBQcwAoZGaHR0cDovL2Ny
dC5jb21vZG9jYS5jb20vQ09NT0RPQ2xpZW50QXV0aGVudGljYXRpb25hbmRTZWN1cmVFbWFpbENB
LmNydDAkBggrBgEFBQcwAYYYaHR0cDovL29jc3AuY29tb2RvY2EuY29tMCUGA1UdEQQeMByBGmVi
dXJnZXJAc3RhbmRhcmRzdHJhY2suY29tMA0GCSqGSIb3DQEBBQUAA4IBAQATedFpXp5JcVGrEipp
KirfegdjPe823Noihn8K6Em01BbEuUsPgHVY/a/6v0UNICBEAuQCwF4aJxuxSBN2GZ6XasVvlg+R
nMnJP6ZZLkd8QmRSmt/AyzxCXkDQdPEJ41+ioNUmVpnGHtHliaT8yEF9EwmMDsy+efbjWomPIx5P
e6MWJX/W2qQ60WhPQxD1U+3VbqWYtn6j9M89JpgQyjYku8C+oOuFUnZskIjbnWMsB3ahHEUympe0
okQT0frCohstkscVkhk63zLmHaUmhKGrJvVwFK+RBBAzuVJcwmEvQqsrczwtlO5E/Qr729Kbch6A
JfmJZ7fJIL1+RbB7ORZNMYIDqzCCA6cCAQEwgagwgZMxCzAJBgNVBAYTAkdCMRswGQYDVQQIExJH
cmVhdGVyIE1hbmNoZXN0ZXIxEDAOBgNVBAcTB1NhbGZvcmQxGjAYBgNVBAoTEUNPTU9ETyBDQSBM
aW1pdGVkMTkwNwYDVQQDEzBDT01PRE8gQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBTZWN1cmUg
RW1haWwgQ0ECEDWub7CYfsGXUhthgY5vuwcwCQYFKw4DAhoFAKCCAdcwGAYJKoZIhvcNAQkDMQsG
CSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMTIwMzE5MTM1ODI3WjAjBgkqhkiG9w0BCQQxFgQU
ai38Ndvo/SNZS6BnOSLPjKVbWLowgbkGCSsGAQQBgjcQBDGBqzCBqDCBkzELMAkGA1UEBhMCR0Ix
GzAZBgNVBAgTEkdyZWF0ZXIgTWFuY2hlc3RlcjEQMA4GA1UEBxMHU2FsZm9yZDEaMBgGA1UEChMR
Q09NT0RPIENBIExpbWl0ZWQxOTA3BgNVBAMTMENPTU9ETyBDbGllbnQgQXV0aGVudGljYXRpb24g
YW5kIFNlY3VyZSBFbWFpbCBDQQIQNa5vsJh+wZdSG2GBjm+7BzCBuwYLKoZIhvcNAQkQAgsxgaug
gagwgZMxCzAJBgNVBAYTAkdCMRswGQYDVQQIExJHcmVhdGVyIE1hbmNoZXN0ZXIxEDAOBgNVBAcT
B1NhbGZvcmQxGjAYBgNVBAoTEUNPTU9ETyBDQSBMaW1pdGVkMTkwNwYDVQQDEzBDT01PRE8gQ2xp
ZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBTZWN1cmUgRW1haWwgQ0ECEDWub7CYfsGXUhthgY5vuwcw
DQYJKoZIhvcNAQEBBQAEggEAGWBhlP7cD5hd546wzF888Hbh24wJRbtQ+rYJqvsWc8QvSUzet4PL
mnUQmxrIQSM8CCdCxWeOhcrwnz7b3odgBPeT+jyWtmCLcGSPM1vhggOD7e53SKb8Q8PH9dVzNMzC
pukfqRHjtDWdAQ5rEEvsIE+qXd8TQWPMLLg2O2k4jss3n5aCdULirZWKOCTjFpemCk802KLxZpHy
gxu8czC7pd0CZmt0InE1rvKvj/DavTtjdjSdbsdk9Y3rbtEHTMWqeqzyMkD9AQe0vvDDtJmPkz0s
EJaYBWsoGmI5Nt9z/jvgnNS2iy2XaChcQEVrpjYtPplwuMfv3RSkGJkw4R7d0wAAAAAAAA==

--Apple-Mail-103--476494445--

From michael_oreirdan@cable.comcast.com  Fri Mar 16 13:17:45 2012
Return-Path: <michael_oreirdan@cable.comcast.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C4A9521F8578 for <ietf@ietfa.amsl.com>; Fri, 16 Mar 2012 13:17:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.23
X-Spam-Level: 
X-Spam-Status: No, score=-101.23 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HOST_EQ_MODEMCABLE=1.368, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ymB7MSLLZLeC for <ietf@ietfa.amsl.com>; Fri, 16 Mar 2012 13:17:45 -0700 (PDT)
Received: from cable.comcast.com (copdcavout01.cable.comcast.com [76.96.32.253]) by ietfa.amsl.com (Postfix) with ESMTP id D85A321F855F for <ietf@ietf.org>; Fri, 16 Mar 2012 13:17:44 -0700 (PDT)
Received: from ([24.40.56.116]) by copdcavout01.cable.comcast.com with ESMTP  id C7WM3M1.9686777; Fri, 16 Mar 2012 14:06:00 -0600
Received: from PACDCEXMB13.cable.comcast.com ([169.254.5.104]) by pacdcexhub03.cable.comcast.com ([fe80::5527:6d6b:29a7:f414%15]) with mapi id 14.01.0355.002; Fri, 16 Mar 2012 16:17:40 -0400
From: "O'Reirdan, Michael" <Michael_OReirdan@Cable.Comcast.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: Beer and Gear
Thread-Topic: Beer and Gear
Thread-Index: AQHNA7HWI+tiR8Myb0akbl3OF4mulw==
Date: Fri, 16 Mar 2012 20:17:40 +0000
Message-ID: <CB891822.40482%Michael_OReirdan@Cable.Comcast.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.14.0.111121
x-originating-ip: [24.40.55.71]
Content-Type: multipart/alternative; boundary="_000_CB89182240482MichaelOReirdanCableComcastcom_"
MIME-Version: 1.0
X-Mailman-Approved-At: Mon, 19 Mar 2012 07:09:47 -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, 16 Mar 2012 20:17:46 -0000

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

I think this would be a good idea. I have attended a number of the NANOG ev=
ents and always found I can talk to vendors on a technical level. Additiona=
lly, it provides a convivial forum for attendees to get together and talk t=
o each other. I don=92t think it would detract from other IETF events and t=
o be honest, most large events manage to co-exist with a multiplicity of sp=
onsors. I am thinking of events like NANOG, MAAWG etc.

Mike

--_000_CB89182240482MichaelOReirdanCableComcastcom_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <5AF6EAF86CD7DC42B62407CB75ABFF60@cable.comcast.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-fami=
ly: Calibri, sans-serif; ">
<div>I think this would be a good idea. I have attended a number of the NAN=
OG events and always found I can talk to vendors on a technical level. Addi=
tionally, it provides a convivial forum for attendees to get together and t=
alk to each other. I don=92t think
 it would detract from other IETF events and to be honest, most large event=
s manage to co-exist with a multiplicity of sponsors. I am thinking of even=
ts like NANOG, MAAWG etc.</div>
<div><br>
</div>
<div>Mike</div>
</body>
</html>

--_000_CB89182240482MichaelOReirdanCableComcastcom_--

From Frederick.Knight@netapp.com  Fri Mar 16 17:57:17 2012
Return-Path: <Frederick.Knight@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 F1F8321E804F for <ietf@ietfa.amsl.com>; Fri, 16 Mar 2012 17:57:16 -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 68i7NiaVAwNg for <ietf@ietfa.amsl.com>; Fri, 16 Mar 2012 17:57:16 -0700 (PDT)
Received: from mx2.netapp.com (mx2.netapp.com [216.240.18.37]) by ietfa.amsl.com (Postfix) with ESMTP id 03B5721E8014 for <ietf@ietf.org>; Fri, 16 Mar 2012 17:57:15 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.73,601,1325491200"; d="scan'208";a="634112564"
Received: from smtp1.corp.netapp.com ([10.57.156.124]) by mx2-out.netapp.com with ESMTP; 16 Mar 2012 17:57:15 -0700
Received: from vmwexceht03-prd.hq.netapp.com (vmwexceht03-prd.hq.netapp.com [10.106.76.241]) by smtp1.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id q2H0vFBI029034 for <ietf@ietf.org>; Fri, 16 Mar 2012 17:57:15 -0700 (PDT)
Received: from SACEXCMBX04-PRD.hq.netapp.com ([169.254.6.92]) by vmwexceht03-prd.hq.netapp.com ([10.106.76.241]) with mapi id 14.02.0247.003; Fri, 16 Mar 2012 17:57:14 -0700
From: "Knight, Frederick" <Frederick.Knight@netapp.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: FW: Query to the community -- An additional IETF Meeting event?
Thread-Topic: Query to the community -- An additional IETF Meeting event?
Thread-Index: AQHNA7Fgv0hGjL6PpEeLdmVNOX6PmZZtpQ7w
Date: Sat, 17 Mar 2012 00:57:13 +0000
Message-ID: <FFEE311F0EC80C4EA64EC8757CAD0CD2032D95@SACEXCMBX04-PRD.hq.netapp.com>
References: <20120316201355.26551.35242.idtracker@ietfa.amsl.com>
In-Reply-To: <20120316201355.26551.35242.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.104.60.115]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Mailman-Approved-At: Mon, 19 Mar 2012 07:09:47 -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: Sat, 17 Mar 2012 00:57:17 -0000

SSB0aGluayB0aGlzIGlzIGEgZ29vZCB0aGluZyB0byB0cnkuDQoNCi0tLS0tT3JpZ2luYWwgTWVz
c2FnZS0tLS0tDQpGcm9tOiBpZXRmLWFubm91bmNlLWJvdW5jZXNAaWV0Zi5vcmcgW21haWx0bzpp
ZXRmLWFubm91bmNlLWJvdW5jZXNAaWV0Zi5vcmddIE9uIEJlaGFsZiBPZiBJQU9DIENoYWlyDQpT
ZW50OiBGcmlkYXksIE1hcmNoIDE2LCAyMDEyIDQ6MTQgUE0NClRvOiBJRVRGIEFubm91bmNlbWVu
dCBMaXN0DQpTdWJqZWN0OiBRdWVyeSB0byB0aGUgY29tbXVuaXR5IC0tIEFuIGFkZGl0aW9uYWwg
SUVURiBNZWV0aW5nIGV2ZW50Pw0KDQoNClRoZSBJRVNHIGFuZCBJQU9DIGFyZSBjb25zaWRlcmlu
ZyBhbiBhZGRpdGlvbiB0byB0aGUgSUVURiBtZWV0aW5nIHdlZWssIGFuZCB3ZSB3b3VsZCBsaWtl
IHlvdXIgdmlld3MgYmVmb3JlIHdlIGRldmVsb3AgdGhlIGlkZWEgZnVydGhlci4NCg0KQXQgTkFO
T0csIHRoZXJlIGlzIGEgQmVlciBhbmQgR2VhciByZWNlcHRpb24gb25lIGV2ZW5pbmcuICBUaGVy
ZSBhcmUgZXhoaWJpdG9yIHRhYmxlcyB3aXRoIHByb2R1Y3QgdmVuZG9ycyAoaGFyZHdhcmUgYW5k
IHNvZnR3YXJlKSBhbmQgc2VydmljZSBwcm92aWRlcnMgKHJlZ2lzdHJpZXMsIHJlZ2lzdHJhcnMs
IElTUHMsIEVTUHMsIGV0Yy4pIGFuZCBhbnlvbmUgZWxzZSBpbnRlcmVzdGVkIGluIGZhY2UgdGlt
ZSB3aXRoIE5BTk9HIHBhcnRpY2lwYW50cy4gVGhleSBzaG93IHRoZWlyIGVxdWlwbWVudCBhbmQg
c2VydmljZXMuICBUaGVyZSBpcyBiYXIgaW4gdGhlIGNlbnRlciBvZiB0aGUgcm9vbSBzZXJ2aW5n
IGJlZXIsIHdpbmUsIGFuZCBzb2Z0IGRyaW5rcy4gVGhlcmUgYXJlIGhvcnMgZCdvZXV2cmVzIHNj
YXR0ZXJlZCBhcm91bmQgdGhlIHJvb20uDQoNCiAgUVVFU1RJT046ICBXaGF0IGRvIHlvdSB0aGlu
ayBhYm91dCBkb2luZyBhIEJlZXIgYW5kIEdlYXIgc3R5bGUNCiAgICAgICAgICAgICBvZiBldmVu
dCBvbiBhbiBldmVuaW5nIHRoYXQgZG9lcyBub3QgY29uZmxpY3Qgd2l0aA0KICAgICAgICAgICAg
IG90aGVyIElFVEYgYWN0aXZpdGllcz8NCg0KVGhpcyB3b3VsZCBiZSBhbiBvcHBvcnR1bml0eSBm
b3IgZnJlZSBmb29kIGFuZCBkcmluayBmb3IgYXR0ZW5kZWVzLCBmb3IgdmVuZG9ycyBhbmQgc2Vy
dmljZSBwcm92aWRlcnMgdG8gdGFsayB3aXRoIElFVEYgcGFydGljaXBhbnRzLCBhbmQgZm9yIGFk
ZGl0aW9uYWwgcmV2ZW51ZSB0byB0aGUgSUVURi4gIE9idmlvdXNseSwgYXR0ZW5kYW5jZSB3b3Vs
ZCBiZSBvcHRpb25hbC4NCg0KVGVjaG5pY2FsIHBlb3BsZSBhcmUgYXQgdGhlIHRhYmxlcywgbm90
IHNhbGVzIG9yIG1hcmtldGluZyBzdGFmZi4gIFZlbmRvcnMga25vdyB0aGF0IHRoZSBhdWRpZW5j
ZSBpcyB2ZXJ5IHRlY2huaWNhbCwgc28gdGhleSBzZW5kIHRoZSBwZW9wbGUgdGhhdCBjYW4gY29t
bXVuaWNhdGUgd2l0aCB0aGF0IGF1ZGllbmNlLg0KDQpXZSB3b3VsZCBjaGFyZ2UgZm9yIGV4aGli
aXQgdGFibGVzLCB0byByYWlzZSBhZGRpdGlvbmFsIGZ1bmRzIGZvciB0aGUgSUVURi4gQSBzdHJv
bmdlciBiYXNlIG9mIG9wcG9ydHVuaXRpZXMgZm9yIElFVEYgc3BvbnNvcnNoaXAgZGlzdHJpYnV0
ZXMgb3VyIGZ1bmRpbmcsIG1ha2luZyBpdCBsZXNzIGZyYWdpbGU7IHRoaXMgY291bGQgbWFrZSBp
dCBsZXNzIGxpa2VseSB0aGF0IHdlIHdvdWxkIGhhdmUgbGFzdC1taW51dGUgc2NyYW1ibGVzIGZv
ciBhZGRpdGlvbmFsIHNwb25zb3JzLCBpbmNsdWRpbmcgaG9zdHMuIEEgc3VjY2Vzc2Z1bCBCZWVy
LWFuZC1HZWFyIGxpa2UgZXZlbnQgd291bGQgbm90IHNvbHZlIHRoaXMgYnV0IGl0IHdvdWxkIGhl
bHAuDQoNCkluIHRoZSBwYXN0LCB0aGUgSUVURiBoYXMgYXZvaWRlZCB2ZW5kb3IgZXhoaWJpdHMg
YW5kIGRlbW9uc3RyYXRpb25zLiAgSG93ZXZlciBpdCBpcyBjbGVhciB0aGF0IE5BTk9HIGhhcyBm
b3VuZCBhIGJhbGFuY2UgdGhhdCB3b3JrcyBhbmQgdGhhdCBOQU5PRyBwYXJ0aWNpcGFudHMgYW5k
IHRoZSB2ZW5kb3JzIGNvbnNpZGVyIHRoZSBldmVudCB2YWx1YWJsZS4gIFdlIGJlbGlldmUgdGhp
cyBjb3VsZCB0cmFuc2xhdGUgd2VsbCB0byB0aGUgSUVURi4NCg0KV2UgYXJlIGNvbnNpZGVyaW5n
IHNvbWUgdGVzdCBldmVudHMsIGhvcGVmdWxseSB0byBiZSBoZWxkIGF0IElFVEYgODQgKFZhbmNv
dXZlciwgSnVseSAyMDEyKSBhbmQgSUVURiA4NSAoQXRsYW50YSwgTm92ZW1iZXIgMjAxMikuDQoN
ClRoZSBraW5kcyBvZiBldmFsdWF0aW9uIGNyaXRlcmlhIHdlIGFyZSBjb25zaWRlcmluZyBjb3Vs
ZCBpbmNsdWRlOg0KDQotIERpZCBwYXJ0aWNpcGFudHMgZW5qb3kgdGhlIGV2ZW50Pw0KDQotIERp
ZCB2ZW5kb3JzIGNvbnNpZGVyIHRoZSBldmVudCBzdWNjZXNzZnVsPw0KDQotIERpZCB0aGUgSUVU
RiByYWlzZSBhZGRpdGlvbmFsIGZ1bmRzPw0KDQotIERpZCB0aGUgZXZlbnQgInN0ZWFsIiBwb3Rl
bnRpYWwgc3BvbnNvcnMgYXdheSBmcm9tIG90aGVyDQogIGFzcGVjdHMgb2YgdGhlIG1lZXRpbmc/
DQoNClNvLCB3aGF0IGRvIHlvdSB0aGluaz8gIElzIHRoaXMgc29tZXRoaW5nIHRoYXQgd2Ugc2hv
dWxkIHRyeT8NCg0KUGxlYXNlIHJlc3BvbmQgb24gdGhlIGlldGZAaWV0Zi5vcmcgbWFpbCBsaXN0
Lg0KDQpPbiBiZWhhbGYgb2YgdGhlIElFU0cgYW5kIHRoZSBJQU9DLA0KDQpSdXNzIEhvdXNsZXkN
CkJvYiBIaW5kZW4NCg==

From teemu.savolainen@nokia.com  Sat Mar 17 00:27:13 2012
Return-Path: <teemu.savolainen@nokia.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 51DA921E801B for <ietf@ietfa.amsl.com>; Sat, 17 Mar 2012 00:27:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.876
X-Spam-Level: 
X-Spam-Status: No, score=-4.876 tagged_above=-999 required=5 tests=[AWL=1.723,  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 NR3BtjArt-3x for <ietf@ietfa.amsl.com>; Sat, 17 Mar 2012 00:27:12 -0700 (PDT)
Received: from mgw-sa01.nokia.com (smtp.nokia.com [147.243.1.47]) by ietfa.amsl.com (Postfix) with ESMTP id 62E9021E8013 for <ietf@ietf.org>; Sat, 17 Mar 2012 00:27:11 -0700 (PDT)
Received: from vaebh106.NOE.Nokia.com (vaebh106.europe.nokia.com [10.160.244.32]) by mgw-sa01.nokia.com (Switch-3.4.4/Switch-3.4.4) with ESMTP id q2H7R8uM025317 for <ietf@ietf.org>; Sat, 17 Mar 2012 09:27:08 +0200
Received: from smtp.mgd.nokia.com ([65.54.30.59]) by vaebh106.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675);  Sat, 17 Mar 2012 09:27:07 +0200
Received: from 008-AM1MPN1-053.mgdnok.nokia.com ([169.254.3.161]) by 008-AM1MMR1-004.mgdnok.nokia.com ([65.54.30.59]) with mapi id 14.01.0355.003; Sat, 17 Mar 2012 08:27:07 +0100
From: <teemu.savolainen@nokia.com>
To: <ietf@ietf.org>
Subject: VS: Query to the community -- An additional IETF Meeting event?
Thread-Topic: Query to the community -- An additional IETF Meeting event?
Thread-Index: AQHNA7FiKxx5eM+NckKAsca2qdQZkJZuF1P1
Date: Sat, 17 Mar 2012 07:27:06 +0000
Message-ID: <plfxtQctYyht@YNx0dFbr>
References: <20120316201355.26551.35242.idtracker@ietfa.amsl.com>
In-Reply-To: <20120316201355.26551.35242.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginalArrivalTime: 17 Mar 2012 07:27:07.0895 (UTC) FILETIME=[5C0C6870:01CD040F]
X-Nokia-AV: Clean
X-Mailman-Approved-At: Mon, 19 Mar 2012 07:09:47 -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: Sat, 17 Mar 2012 07:27:13 -0000

Hi,

I would find this educative. So +

Would this be also the centralized place to show prototype implementations =
of IETF technologies still in WGs process, or would/could those be separate=
 events (similar to the past, e.g. dedicated room)?

Teemu

---- alkuper=E4inen viesti ----
L=E4hett.: ext IAOC Chair
L=E4het.:  16.03.2012, 22:14
V.ottaja: IETF Announcement List
Aihe: Query to the community -- An additional IETF Meeting event?


The IESG and IAOC are considering an addition to the IETF meeting week, and=
 we would like your views before we develop the idea further.

At NANOG, there is a Beer and Gear reception one evening.  There are exhibi=
tor tables with product vendors (hardware and software) and service provide=
rs (registries, registrars, ISPs, ESPs, etc.) and anyone else interested in=
 face time with NANOG participants. They show their equipment and services.=
  There is bar in the center of the room serving beer, wine, and soft drink=
s. There are hors d'oeuvres scattered around the room.

  QUESTION:  What do you think about doing a Beer and Gear style
             of event on an evening that does not conflict with
             other IETF activities?

This would be an opportunity for free food and drink for attendees, for ven=
dors and service providers to talk with IETF participants, and for addition=
al revenue to the IETF.  Obviously, attendance would be optional.

Technical people are at the tables, not sales or marketing staff.  Vendors =
know that the audience is very technical, so they send the people that can =
communicate with that audience.

We would charge for exhibit tables, to raise additional funds for the IETF.=
 A stronger base of opportunities for IETF sponsorship distributes our fund=
ing, making it less fragile; this could make it less likely that we would h=
ave last-minute scrambles for additional sponsors, including hosts. A succe=
ssful Beer-and-Gear like event would not solve this but it would help.

In the past, the IETF has avoided vendor exhibits and demonstrations.  Howe=
ver it is clear that NANOG has found a balance that works and that NANOG pa=
rticipants and the vendors consider the event valuable.  We believe this co=
uld translate well to the IETF.

We are considering some test events, hopefully to be held at IETF 84 (Vanco=
uver, July 2012) and IETF 85 (Atlanta, November 2012).

The kinds of evaluation criteria we are considering could include:

- Did participants enjoy the event?

- Did vendors consider the event successful?

- Did the IETF raise additional funds?

- Did the event "steal" potential sponsors away from other
  aspects of the meeting?

So, what do you think?  Is this something that we should try?

Please respond on the ietf@ietf.org mail list.

On behalf of the IESG and the IAOC,

Russ Housley
Bob Hinden

From eran@hueniverse.com  Sat Mar 17 16:11:43 2012
Return-Path: <eran@hueniverse.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5BA9C21F866B for <ietf@ietfa.amsl.com>; Sat, 17 Mar 2012 16:11:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.233
X-Spam-Level: 
X-Spam-Status: No, score=-2.233 tagged_above=-999 required=5 tests=[AWL=-0.234, BAYES_00=-2.599, J_CHICKENPOX_44=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ROui3gAZgswY for <ietf@ietfa.amsl.com>; Sat, 17 Mar 2012 16:11:42 -0700 (PDT)
Received: from p3plex1out01.prod.phx3.secureserver.net (p3plex1out01.prod.phx3.secureserver.net [72.167.180.17]) by ietfa.amsl.com (Postfix) with SMTP id 8654321F8661 for <ietf@ietf.org>; Sat, 17 Mar 2012 16:11:42 -0700 (PDT)
Received: (qmail 20639 invoked from network); 17 Mar 2012 23:11:41 -0000
Received: from unknown (HELO p3plex2out01.prod.phx3.secureserver.net) (184.168.131.12) by p3plex1out01.prod.phx3.secureserver.net with SMTP; 17 Mar 2012 23:11:41 -0000
Received: from P3PW5EX1HT001.EX1.SECURESERVER.NET ([72.167.180.19]) by p3plex2out01.prod.phx3.secureserver.net with bizsmtp id mnBf1i0010RWb6o01nBhV2; Sat, 17 Mar 2012 16:11:41 -0700
Received: from P3PW5EX1MB01.EX1.SECURESERVER.NET ([10.6.135.20]) by P3PW5EX1HT001.EX1.SECURESERVER.NET ([72.167.180.19]) with mapi; Sat, 17 Mar 2012 09:25:35 -0700
From: Eran Hammer <eran@hueniverse.com>
To: John Bradley <ve7jtb@ve7jtb.com>
Date: Sat, 17 Mar 2012 09:25:23 -0700
Subject: RE: [OAUTH-WG] Last Call: <draft-ietf-oauth-v2-bearer-15.txt> (The OAuth 2.0	Authorization Protocol: Bearer Tokens) to Proposed Standard
Thread-Topic: [OAUTH-WG] Last Call: <draft-ietf-oauth-v2-bearer-15.txt> (The OAuth 2.0	Authorization Protocol: Bearer Tokens) to Proposed Standard
Thread-Index: Acz9Rmgmn7QNqLoOT1OzbE+KGkQxzgHFBRcA
Message-ID: <90C41DD21FB7C64BB94121FBBC2E723453AFF08C1D@P3PW5EX1MB01.EX1.SECURESERVER.NET>
References: <20120123154643.16223.44509.idtracker@ietfa.amsl.com> <4F1D8391.3080009@gmx.de> <4F1F3D84.1030300@gmx.de> <90C41DD21FB7C64BB94121FBBC2E723453AAB9682E@P3PW5EX1MB01.EX1.SECURESERVER.NET> <7D4DB9C9-7194-42A0-A573-4243FE27E512@ve7jtb.com> <90C41DD21FB7C64BB94121FBBC2E723453AFCD4072@P3PW5EX1MB01.EX1.SECURESERVER.NET> <A7D328CF-C7E5-4A78-A60C-BE34FC65B2BD@ve7jtb.com>
In-Reply-To: <A7D328CF-C7E5-4A78-A60C-BE34FC65B2BD@ve7jtb.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Mon, 19 Mar 2012 07:09:47 -0700
Cc: Julian Reschke <julian.reschke@gmx.de>, "oauth@ietf.org" <oauth@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, The IESG <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 17 Mar 2012 23:11:43 -0000

I am treating this issue as closed, unless someone wants to proposed langua=
ge changes based on John's analysis below.

EH

> -----Original Message-----
> From: John Bradley [mailto:ve7jtb@ve7jtb.com]
> Sent: Thursday, March 08, 2012 8:13 AM
> To: Eran Hammer
> Cc: Julian Reschke; ietf@ietf.org; The IESG; oauth@ietf.org
> Subject: Re: [OAUTH-WG] Last Call: <draft-ietf-oauth-v2-bearer-15.txt> (T=
he
> OAuth 2.0 Authorization Protocol: Bearer Tokens) to Proposed Standard
>=20
> Thanks that is better.
>=20
> Without knowing the lifetime of the token these are per guess probabiliti=
es.
> Effectively 128bits for a random value and 256bits for a HMAC or other
> signature.
>=20
> For tokens intended for handling by end-users it may be useful to give so=
me
> advice.
> In general you don't want an attacker having more than a one in 2^14 chan=
ce
> of guessing a valid code for a AS during the lifetime of the code(NIST Lo=
A 2).
>=20
> For a code randomly generated from a 94 character code set 4 characters
> gets you 26.3 bits of entropy.
> 5 characters requires limiting an attacker to 2^12.3 (5,042) guesses per =
token
> lifetime.
>=20
> For a code randomly generated from a 94 character code set 5 characters
> gets you 32.9 bits of entropy.
> 5 characters requires limiting an attacker to 2^18.9 (489,178) guesses pe=
r
> token lifetime.
>=20
> If the token is single use and the client uses it right away that is easy=
,
> however in a worst case scenario the token might live 10min?
> That would be 8.4 attempts per second as a max for a 4 character code or =
815
> per second for 5 characters.
>=20
> That is all way too much to explain however I would recommend as a genera=
l
> rule:
>=20
> Credentials intended for handling by end users SHOULD be a minimum of 5
> randomly generated charters from a set of 94 or otherwise contain a
> minimum entropy of 2^32.9.
>=20
> That is probably high enough that the AS will notice an attack,  lower en=
tropy
> may pass under the radar.
> Also the chances of an attacker being successful go up proportionally to =
the
> number simultaneous codes in flight at any point (it becomes a non target=
ed
> attack).
>=20
> It isn't something that I will loose sleep over,  It gives me something e=
lse to
> profile:)
>=20
> Thanks
> John B.
>=20
> On 2012-03-07, at 8:18 PM, Eran Hammer wrote:
>=20
> > New text:
> >
> >          The probability of an attacker guessing generated tokens (and =
other
> credentials not
> >          intended for handling by end-users) MUST be less than or equal=
 to
> 2^(-128) and SHOULD be
> >          less than or equal to 2^(-160).
> >
> > Removed reference to RFC 1750.
> >
> > EH
> >
> >> -----Original Message-----
> >> From: John Bradley [mailto:ve7jtb@ve7jtb.com]
> >> Sent: Monday, February 06, 2012 5:07 PM
> >> To: Eran Hammer
> >> Cc: Julian Reschke; ietf@ietf.org; The IESG; oauth@ietf.org
> >> Subject: Re: [OAUTH-WG] Last Call: <draft-ietf-oauth-v2-bearer-15.txt>
> (The
> >> OAuth 2.0 Authorization Protocol: Bearer Tokens) to Proposed Standard
> >>
> >> RE new text in Draft 23
> >>
> >> http://tools.ietf.org/html/draft-ietf-oauth-v2-23#section-10.10
> >>
> >> Generated tokens and other credentials not intended for handling by
> >>   end-users MUST be constructed from a cryptographically strong random
> >>   or pseudo-random number sequence ([RFC1750]) generated by the
> >>   authorization server.
> >>
> >> Given that many implementations may elect to use signed tokens, such a=
s
> >> SAML or JWT (JOSE) this should not be a MUST.
> >>
> >> Giving people sensible defaults such as the probability of an attacker
> >> guessing a valid access token for the protected resource should be les=
s
> than
> >> 2^(-128).
> >>
> >> The probability of generating hash colisions randomly is a odd metric,=
  2^(-
> >> 128) for a SHA256 as I recall.
> >> Many factors play into what is secure, token lifetime etc.
> >>
> >> I don't mind some reasonable defaults but adding a requirement for
> >> unstructured tokens is a bit much.
> >>
> >> Regards
> >> John B.
> >>
> >>
> >


From mcr@sandelman.ca  Mon Mar 19 07:34:29 2012
Return-Path: <mcr@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D6E7321F87E2 for <ietf@ietfa.amsl.com>; Mon, 19 Mar 2012 07:34:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.794
X-Spam-Level: 
X-Spam-Status: No, score=-1.794 tagged_above=-999 required=5 tests=[AWL=0.160,  BAYES_00=-2.599, HOST_MISMATCH_NET=0.311, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9MOTNeqmXZVh for <ietf@ietfa.amsl.com>; Mon, 19 Mar 2012 07:34:29 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [67.23.6.41]) by ietfa.amsl.com (Postfix) with ESMTP id 2572021F87FF for <ietf@ietf.org>; Mon, 19 Mar 2012 07:34:26 -0700 (PDT)
Received: from marajade.sandelman.ca (desk.marajade.sandelman.ca [209.87.252.247]) by relay.sandelman.ca (Postfix) with ESMTPS id B42C8343DF; Mon, 19 Mar 2012 10:31:46 -0400 (EDT)
Received: by marajade.sandelman.ca (Postfix, from userid 179) id 44BEC983B9; Mon, 19 Mar 2012 10:34:24 -0400 (EDT)
Received: from marajade.sandelman.ca (localhost [127.0.0.1]) by marajade.sandelman.ca (Postfix) with ESMTP id 3D4FC983B8; Mon, 19 Mar 2012 10:34:24 -0400 (EDT)
From: Michael Richardson <mcr@sandelman.ca>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: Query to the community -- An additional IETF Meeting event?
In-Reply-To: <DCC302FAA9FE5F4BBA4DCAD465693779173C924EA3@PRVPEXVS03.corp.twcable.com>
References: <20120316194918.18453.89483.idtracker@ietfa.amsl.com> <CB0BE66D-26E1-492C-B84C-44F6C0449995@cisco.com> <4F63AF60.4010004@dcrocker.net> <4F65FCA5.1090101@gmail.com> <DCC302FAA9FE5F4BBA4DCAD465693779173C924EA3@PRVPEXVS03.corp.twcable.com>
X-Mailer: MH-E 8.3; nmh 1.3-dev; XEmacs 21.4 (patch 22)
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Mon, 19 Mar 2012 10:34:24 -0400
Message-ID: <20858.1332167664@marajade.sandelman.ca>
Sender: mcr@sandelman.ca
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Mar 2012 14:34:30 -0000

--=-=-=


>>>>> "Wes" == Wes George <George> writes:
    Wes> That said, I don't think that this potential experiment
    Wes> requires a *separate* night. I'd much prefer to replace the
    Wes> current "overpriced hotel cash bar" arrangement at the welcome
    Wes> reception with something more like beer-n-gear. I'm also
    Wes> willing to try it in lieu of a social event, since those are
    Wes> typically hit or miss in terms of whether the environment is
    Wes> conducive to socializing, whether they're worth the additional

+1.  If it's really the social, or better, the Sunday night event, then
great. I've been at two NANOGs for beer-n-gear, and while I found it a
bit weak in "gear", and not that well attended, I actually enjoyed it.



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

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

iQCVAwUAT2dD8IqHRg3pndX9AQLHvwQAidIdeMDj7YVcHqy2ZoIstY4ZYDpxHCRU
vsJz15szC/W2/QqkQizLxe7kzgl1XAt7K5iuM0EMATEFprOgnN/fvdvdUPcJpQNz
kwLkrOad8VW+oFb4qon53YXwNsZFeJGR4bG4u5BorLbpqV0lTwLNfNSVVygihtFY
rdtStYgkh0k=
=dDXw
-----END PGP SIGNATURE-----
--=-=-=--

From kpfleming@digium.com  Mon Mar 19 07:38:39 2012
Return-Path: <kpfleming@digium.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 60BC321F8814 for <ietf@ietfa.amsl.com>; Mon, 19 Mar 2012 07:38:39 -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.041, 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 1GoE7ay46FEV for <ietf@ietfa.amsl.com>; Mon, 19 Mar 2012 07:38:38 -0700 (PDT)
Received: from mail.digium.com (mail.digium.com [216.207.245.2]) by ietfa.amsl.com (Postfix) with ESMTP id 6F38821F87E0 for <ietf@ietf.org>; Mon, 19 Mar 2012 07:38:38 -0700 (PDT)
Received: from [10.24.55.203] (helo=zimbra.hsv.digium.com) by mail.digium.com with esmtp (Exim 4.69) (envelope-from <kpfleming@digium.com>) id 1S9djJ-0002Xr-8k for ietf@ietf.org; Mon, 19 Mar 2012 09:38:37 -0500
Received: from localhost (localhost.localdomain [127.0.0.1]) by zimbra.hsv.digium.com (Postfix) with ESMTP id 43421D8010 for <ietf@ietf.org>; Mon, 19 Mar 2012 09:38:37 -0500 (CDT)
Received: from zimbra.hsv.digium.com ([127.0.0.1]) by localhost (zimbra.hsv.digium.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id A00X9VQkCgqE for <ietf@ietf.org>; Mon, 19 Mar 2012 09:38:36 -0500 (CDT)
Received: from [10.24.250.46] (unknown [10.24.250.46]) by zimbra.hsv.digium.com (Postfix) with ESMTPSA id EB38FD8004 for <ietf@ietf.org>; Mon, 19 Mar 2012 09:38:36 -0500 (CDT)
Message-ID: <4F6744EC.3010509@digium.com>
Date: Mon, 19 Mar 2012 09:38:36 -0500
From: "Kevin P. Fleming" <kpfleming@digium.com>
Organization: Digium, Inc.
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: IPv6 Zone Identifiers Considered Hateful
References: <82A794CE-B328-475F-9300-1B6BE628F7E3@sabahattin-gucukoglu.com>
In-Reply-To: <82A794CE-B328-475F-9300-1B6BE628F7E3@sabahattin-gucukoglu.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Mar 2012 14:38:39 -0000

On 03/19/2012 05:55 AM, Sabahattin Gucukoglu wrote:

> Yesterday, I configured a DNS server to listen just using a link-local address, the one autoconfigured for an ethernet card accessible to all the nodes.  It's a host, not a router, so I'm relying on that address not being routable and being filtered at the router.  It didn't work.  The server would not start until I specified the zone suffix.  Now I am wondering why, given that there is no ambiguous link-local address anywhere around here, I need to do that.  Can't it figure it out itself?

Sure, it can, until a new network interface appears on that box (VPN, 
tunnel, hardware, etc.).

-- 
Kevin P. Fleming
Digium, Inc. | Director of Software Technologies
Jabber: kfleming@digium.com | SIP: kpfleming@digium.com | Skype: kpfleming
445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
Check us out at www.digium.com & www.asterisk.org

From ole@cisco.com  Mon Mar 19 07:52:06 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 354B021F8846 for <ietf@ietfa.amsl.com>; Mon, 19 Mar 2012 07:52:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.347
X-Spam-Level: 
X-Spam-Status: No, score=-109.347 tagged_above=-999 required=5 tests=[AWL=1.252, 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 1azXYFKV25Zt for <ietf@ietfa.amsl.com>; Mon, 19 Mar 2012 07:52:05 -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 5F1B021F8844 for <ietf@ietf.org>; Mon, 19 Mar 2012 07:52:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=ole@cisco.com; l=461; q=dns/txt; s=iport; t=1332168725; x=1333378325; h=date:from:reply-to:to:cc:subject:in-reply-to:message-id: references:mime-version; bh=+9TC5Dc26N20ISCgb7y8IwUjaDQ4shTFIiZ7CoYNh1w=; b=Tsu9VRdXt+V0CtcAawZo24a1IKXwzAf+hdKrAWjwFtA9I6HsHGc9uhJ9 LsY3TopKl5kmJ8ZjZ0kbiUa4Yuq24sgX2yzIzEkUURSWRlFXeNd1FfPGL N4jTpqhsDxc0eCJPzhbIEzcvhZBNo6VOCfJ/VkNgTBLRrXTTSP0CRhVFB U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AoYIAAFHZ0+rRDoJ/2dsb2JhbABCgw2zPoEHggkBAQEEEgECJT8QCw4KLlcGJw6HZ5tFgzwQmyCQfASIVpJ/iFOBAmaDBg
X-IronPort-AV: E=Sophos;i="4.73,611,1325462400"; d="scan'208";a="33605239"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by mtv-iport-1.cisco.com with ESMTP; 19 Mar 2012 14:52:05 +0000
Received: from [10.86.255.103] ([10.86.255.103]) by mtv-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id q2JEq3Gw000699; Mon, 19 Mar 2012 14:52:04 GMT
Date: Mon, 19 Mar 2012 07:52:03 -0700 (PDT)
From: Ole Jacobsen <ole@cisco.com>
To: Michael Richardson <mcr@sandelman.ca>
Subject: Re: Query to the community -- An additional IETF Meeting event?
In-Reply-To: <20858.1332167664@marajade.sandelman.ca>
Message-ID: <alpine.OSX.2.01.1203190750280.88004@rabdullah.local>
References: <20120316194918.18453.89483.idtracker@ietfa.amsl.com> <CB0BE66D-26E1-492C-B84C-44F6C0449995@cisco.com> <4F63AF60.4010004@dcrocker.net> <4F65FCA5.1090101@gmail.com> <DCC302FAA9FE5F4BBA4DCAD465693779173C924EA3@PRVPEXVS03.corp.twcable.com> <20858.1332167664@marajade.sandelman.ca>
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" <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: Mon, 19 Mar 2012 14:52:06 -0000

On Mon, 19 Mar 2012, Michael Richardson wrote:
> 
> +1.  If it's really the social, or better, the Sunday night event, then
> great. I've been at two NANOGs for beer-n-gear, and while I found it a
> bit weak in "gear", and not that well attended, I actually enjoyed it.
> 

Must have been a while ago, the 3 last ones I've been to have been 
packed in terms of attendees, and oversold so that not all potential 
exhibitors could get a table.

Ole

From edj.etc@gmail.com  Mon Mar 19 07:58:14 2012
Return-Path: <edj.etc@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 57A1721F87BF for <ietf@ietfa.amsl.com>; Mon, 19 Mar 2012 07:58:14 -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=[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 oI3F2vKw0S4T for <ietf@ietfa.amsl.com>; Mon, 19 Mar 2012 07:58:13 -0700 (PDT)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 4667121F87AB for <ietf@ietf.org>; Mon, 19 Mar 2012 07:58:13 -0700 (PDT)
Received: by vcbfk13 with SMTP id fk13so7732738vcb.31 for <ietf@ietf.org>; Mon, 19 Mar 2012 07:58:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=o7F54/tVGEsGiSu35DJmMGkraqecq76TFwCJHyN5zRk=; b=pfSV5UoQRhTNbWG45IL/kVCJEw2041rEnjDB4L37Cg3LiGb+mLF8t9URYnZqHCaPPH 8PAlnNoon3Beb4k8xaaFKXs0X99Cf+GKwD/naBwWAqWFbWvfK4LyUa0nJLFSptzwBhrK U753QEZbeNaB7IL+sCrK11lVN/gs+Fd0p2/ajju/q9QR2rucpTjPe4GLvi0CagZPB0/B FiuJ4eri6b3pcQC+QxRR8QyoJjNy6aYgP7agSEJkmyjeliD+qboKCS9YGptBVCttlfQa +urlTZ9nDCOXhLAj+tocqwnVjBF33DT/PPOrqmPrYXJ6FQohBGw8j4LMdGk5kmoj/B/O 99yA==
MIME-Version: 1.0
Received: by 10.220.151.71 with SMTP id b7mr4807601vcw.62.1332169092847; Mon, 19 Mar 2012 07:58:12 -0700 (PDT)
Received: by 10.52.65.19 with HTTP; Mon, 19 Mar 2012 07:58:12 -0700 (PDT)
In-Reply-To: <20120316194918.18453.89483.idtracker@ietfa.amsl.com>
References: <20120316194918.18453.89483.idtracker@ietfa.amsl.com>
Date: Mon, 19 Mar 2012 10:58:12 -0400
Message-ID: <CALRYWsMOCSv+ekh=Gtymb2Mp3oVBsrjwKpv_5-a9ZGMvZ95oWA@mail.gmail.com>
Subject: Re: Query to the community -- An additional IETF Meeting event?
From: Ed Juskevicius <edj.etc@gmail.com>
To: ietf@ietf.org
Content-Type: multipart/alternative; boundary=f46d043bdf3a8f574204bb99c984
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Mar 2012 14:58:14 -0000

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

I have two comments on this.

1)  I am in favor of allowing the IAOC to experiment with an event (or two)
like this for the purposes of developing running code with the associated
pros, cons and economics.

2)  I would attend such an additional event if the gear on display was
related to technology I am personally interested in (e.g. commerically
available IPv6 Ready gear).

Regards,

Ed  J.

On Fri, Mar 16, 2012 at 3:49 PM, IAOC Chair <bob.hinden@gmail.com> wrote:

>
> The IESG and IAOC are considering an addition to the IETF meeting week,
> and we would like your views before we develop the idea further.
>
> At NANOG, there is a Beer and Gear reception one evening.  There are
> exhibitor tables with product vendors (hardware and software) and service
> providers (registries, registrars, ISPs, ESPs, etc.) and anyone else
> interested in face time with NANOG participants. They show their equipment
> and services.  There is bar in the center of the room serving beer, wine,
> and soft drinks. There are hors d'oeuvres scattered around the room.
>
>  QUESTION:  What do you think about doing a Beer and Gear style
>             of event on an evening that does not conflict with
>             other IETF activities?
>
> This would be an opportunity for free food and drink for attendees, for
> vendors and service providers to talk with IETF participants, and for
> additional revenue to the IETF.  Obviously, attendance would be optional.
>
> Technical people are at the tables, not sales or marketing staff.  Vendors
> know that the audience is very technical, so they send the people that can
> communicate with that audience.
>
> We would charge for exhibit tables, to raise additional funds for the
> IETF. A stronger base of opportunities for IETF sponsorship distributes our
> funding, making it less fragile; this could make it less likely that we
> would have last-minute scrambles for additional sponsors, including hosts.
> A successful Beer-and-Gear like event would not solve this but it would
> help.
>
> In the past, the IETF has avoided vendor exhibits and demonstrations.
>  However it is clear that NANOG has found a balance that works and that
> NANOG participants and the vendors consider the event valuable.  We believe
> this could translate well to the IETF.
>
> We are considering some test events, hopefully to be held at IETF 84
> (Vancouver, July 2012) and IETF 85 (Atlanta, November 2012).
>
> The kinds of evaluation criteria we are considering could include:
>
> - Did participants enjoy the event?
>
> - Did vendors consider the event successful?
>
> - Did the IETF raise additional funds?
>
> - Did the event "steal" potential sponsors away from other
>  aspects of the meeting?
>
> So, what do you think?  Is this something that we should try?
>
> Please respond on the ietf@ietf.org mail list.
>
> On behalf of the IESG and the IAOC,
>
> Russ Housley
> Bob Hinden
>

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

<div>I have two comments on this.</div>
<div>=A0</div>
<div>1)=A0 I am in favor of allowing the IAOC to experiment=A0with an event=
 (or two) like this for the purposes of developing running code with=A0the =
associated pros, cons and economics.</div>
<div>=A0</div>
<div>2)=A0 I would attend such an additional event if the gear on display=
=A0was related to=A0technology I am personally interested in (e.g.=A0commer=
ically available IPv6 Ready gear).</div>
<div>=A0</div>
<div>Regards,</div>
<div>=A0</div>
<div>Ed=A0 J.=A0=A0<br><br></div>
<div class=3D"gmail_quote">On Fri, Mar 16, 2012 at 3:49 PM, IAOC Chair <spa=
n dir=3D"ltr">&lt;<a href=3D"mailto:bob.hinden@gmail.com">bob.hinden@gmail.=
com</a>&gt;</span> wrote:<br>
<blockquote style=3D"BORDER-LEFT:#ccc 1px solid;MARGIN:0px 0px 0px 0.8ex;PA=
DDING-LEFT:1ex" class=3D"gmail_quote"><br>The IESG and IAOC are considering=
 an addition to the IETF meeting week, and we would like your views before =
we develop the idea further.<br>
<br>At NANOG, there is a Beer and Gear reception one evening. =A0There are =
exhibitor tables with product vendors (hardware and software) and service p=
roviders (registries, registrars, ISPs, ESPs, etc.) and anyone else interes=
ted in face time with NANOG participants. They show their equipment and ser=
vices. =A0There is bar in the center of the room serving beer, wine, and so=
ft drinks. There are hors d&#39;oeuvres scattered around the room.<br>
<br>=A0QUESTION: =A0What do you think about doing a Beer and Gear style<br>=
=A0 =A0 =A0 =A0 =A0 =A0 of event on an evening that does not conflict with<=
br>=A0 =A0 =A0 =A0 =A0 =A0 other IETF activities?<br><br>This would be an o=
pportunity for free food and drink for attendees, for vendors and service p=
roviders to talk with IETF participants, and for additional revenue to the =
IETF. =A0Obviously, attendance would be optional.<br>
<br>Technical people are at the tables, not sales or marketing staff. =A0Ve=
ndors know that the audience is very technical, so they send the people tha=
t can communicate with that audience.<br><br>We would charge for exhibit ta=
bles, to raise additional funds for the IETF. A stronger base of opportunit=
ies for IETF sponsorship distributes our funding, making it less fragile; t=
his could make it less likely that we would have last-minute scrambles for =
additional sponsors, including hosts. A successful Beer-and-Gear like event=
 would not solve this but it would help.<br>
<br>In the past, the IETF has avoided vendor exhibits and demonstrations. =
=A0However it is clear that NANOG has found a balance that works and that N=
ANOG participants and the vendors consider the event valuable. =A0We believ=
e this could translate well to the IETF.<br>
<br>We are considering some test events, hopefully to be held at IETF 84 (V=
ancouver, July 2012) and IETF 85 (Atlanta, November 2012).<br><br>The kinds=
 of evaluation criteria we are considering could include:<br><br>- Did part=
icipants enjoy the event?<br>
<br>- Did vendors consider the event successful?<br><br>- Did the IETF rais=
e additional funds?<br><br>- Did the event &quot;steal&quot; potential spon=
sors away from other<br>=A0aspects of the meeting?<br><br>So, what do you t=
hink? =A0Is this something that we should try?<br>
<br>Please respond on the <a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a=
> mail list.<br><br>On behalf of the IESG and the IAOC,<br><br>Russ Housley=
<br>Bob Hinden<br></blockquote></div><br>

--f46d043bdf3a8f574204bb99c984--

From loa@pi.nu  Mon Mar 19 10:53:29 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 70D5E21F88BC for <ietf@ietfa.amsl.com>; Mon, 19 Mar 2012 10:53:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5j9ldAMlR6pG for <ietf@ietfa.amsl.com>; Mon, 19 Mar 2012 10:53:28 -0700 (PDT)
Received: from mail.pi.nu (mail.pi.nu [194.71.127.148]) by ietfa.amsl.com (Postfix) with ESMTP id 2E0E221F88B6 for <ietf@ietf.org>; Mon, 19 Mar 2012 10:53:27 -0700 (PDT)
Received: from [109.58.198.118] (109.58.198.118.bredband.tre.se [109.58.198.118]) (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 520E92A8002 for <ietf@ietf.org>; Mon, 19 Mar 2012 18:53:26 +0100 (CET)
Message-ID: <4F677294.90503@pi.nu>
Date: Mon, 19 Mar 2012 18:53:24 +0100
From: Loa Andersson <loa@pi.nu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt> (Allocation of	an Associated Channel Code Point for Use by	ITU-T Ethernet based OAM) to Informational RFC
References: <52981DB05D3C5247A12D0AEE309F3CC202444231EB23@INOAVREX11.ptin.corpPT.com> <4F670C21.1040905@gmail.com> <D62E6669B3621943B7632961308F8F9E0DD76853@lhreml509-mbx>
In-Reply-To: <D62E6669B3621943B7632961308F8F9E0DD76853@lhreml509-mbx>
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, 19 Mar 2012 17:53:29 -0000

Maarten,

please be aware of what u asking for - you won't have a
"an ACH codepoint to G.8113.1".

First, what is requested is an "Associated Channel Type"
and it will be assigned to the RFC resulting from draft-betts-.
I will not do my tutorial on Associated Channel acronyms,
but it could do it if needed, but some other venue.

Assigning the Associated Channel Type is what I see that
a solid majority want to happen!
This is not an attempt to end-run the consensus call by the AD,
just my personal read of the situation.

The first remaining caveat is the draft-betts is too poorly written
and need to be improve, suggestions has been sent to this mailing
list, I take it that people who send mails to this list saying
that they support Russ' proposal also implicitly support these
improvements.

The second caveat is that an ITU-T Recommendation is not stable
according to the criteria we normally apply to RFCs.

We are solving this by generating a RFC from draft-betts-.
I believe that the way out here is to "update" "RFC draft-betts-"
every time ITU-T rev G.8113.1. That way we will have our stable
reference pointing to the right version of G.8113.1.

I'd like to hear from the process people on this, but not as part
of this last call.

/Loa

On 2012-03-19 11:55, Maarten vissers wrote:
> +1
>
> -------- Original Message --------
> From: Rui Costa<RCosta@ptinovacao.pt>
> Sent: zaterdag 17 maart 2012 12:00:56 +0000
> To: ietf@ietf.org<ietf@ietf.org>
> Subject: RE: Last Call:<draft-betts-itu-oam-ach-code-point-03.txt>
> (Allocation of	an Associated Channel Code Point for Use by	ITU-T
> Ethernet based OAM) to Informational RFC
>
> Hello,	
>
> I support the allocation of an ACH codepoint to G.8113.1, not precluding
> the ITU-T to progress refinements. Ergo, i support this draft and
> proposal http://www.ietf.org/mail-archive/web/ietf/current/msg72191.html
>
> IMHO, the status quo analysis expressed in both
> http://www.ietf.org/mail-archive/web/ietf/current/msg72188.html and
> http://www.ietf.org/mail-archive/web/ietf/current/msg72273.html is
> accurate.	
>
> Regards,	
> Rui	
> =========================================================
>
>
> -------- Original Message --------
> From: The IESG<iesg-secretary@ietf.org>
> Sent: Wed, 22 Feb 2012 07:12:52 -0800
> To: IETF-Announce<ietf-announce@ietf.org>
> Subject: Last Call:<draft-betts-itu-oam-ach-code-point-03.txt>
> (Allocation of	an Associated Channel Code Point for Use by ITU-T
> Ethernet	based OAM) to Informational RFC
>
> The IESG has received a request from an individual submitter to consider
> the following document:
> - 'Allocation of an Associated Channel Code Point for Use by ITU-T
>       Ethernet based OAM'
>      <draft-betts-itu-oam-ach-code-point-03.txt>  as an 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-03-21. 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 assigns an Associated Channel Type code point for
>       carrying Ethernet based Operations, Administration, and Management
>       messages in the MPLS Generic Associated Channel (G-ACh).
>
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-betts-itu-oam-ach-code-point/
>
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-betts-itu-oam-ach-code-point/
>
>
> No IPR declarations have been submitted directly on this I-D.
> _______________________________________________
> IETF mailing list
> IETF@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf	
>

-- 


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 alexey.melnikov@isode.com  Mon Mar 19 13:23:00 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 BF62B21E801C; Mon, 19 Mar 2012 13:23:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.598
X-Spam-Level: 
X-Spam-Status: No, score=-102.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tIO7hd9wUHBF; Mon, 19 Mar 2012 13:22:58 -0700 (PDT)
Received: from rufus.isode.com (cl-125.lon-03.gb.sixxs.net [IPv6:2a00:14f0:e000:7c::2]) by ietfa.amsl.com (Postfix) with ESMTP id 0E9FE21E8029; Mon, 19 Mar 2012 13:22:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1332188576; d=isode.com; s=selector; i=@isode.com; bh=rqvaxjtf3WiNjHNsarUHUKV2MhbQACiD3scAWaAa9yY=; 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=RroMnLipzVa1z8ZAkFGfa0Y8EB4nYfdV24nRrSBvECmOTiYCm9KLnd4+h5KIJrHTy71fDk jWDtK7bVI8+HNILavi8lsiH2fTPIalDjmbzyBlouQPK7YJ3ENdeKWP2UzBgZqusfEBidCU tHqT7i3gA3qGZgH6K4j7lVDwsRJ1bdk=;
Received: from [188.29.240.8] (188.29.240.8.threembb.co.uk [188.29.240.8])  by rufus.isode.com (submission channel) via TCP with ESMTPSA  id <T2eVlwBhup6a@rufus.isode.com>; Mon, 19 Mar 2012 20:22:52 +0000
X-SMTP-Protocol-Errors: PIPELINING
Message-ID: <4F677B02.8090108@isode.com>
Date: Mon, 19 Mar 2012 18:29:22 +0000
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: Roni Even <ron.even.tlv@gmail.com>
Subject: Re: Gen-ART LC review of draft-melnikov-smtp-priority-09
References: <4f5f9f50.6965b40a.7aaa.6114@mx.google.com>
In-Reply-To: <4f5f9f50.6965b40a.7aaa.6114@mx.google.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="------------080501010100070202020004"
Cc: draft-melnikov-smtp-priority.all@tools.ietf.org, gen-art@ietf.org, 'IETF-Discussion list' <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Mar 2012 20:23:00 -0000

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

Hi Roni,
Thank you for your review.

On 13/03/2012 19:25, Roni Even wrote:
>
> I am the assigned Gen-ART reviewer for this draft. For background on 
> Gen-ART, please see the FAQ at 
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>
> Please resolve these comments along with any other Last Call comments 
> you may receive.
>
> Document: draft-melnikov-smtp-priority-09
>
> Reviewer: Roni Even
>
> Review Date:2012--3--13
>
> IETF LC End Date: 2012--3--28
>
> IESG Telechat date:
>
> Summary: This draft is almost ready for publication as a standard 
> track RFC.
>
> Major issues:
>
> Minor issues:
>
> 1.In section 4.2  "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." .      My understanding  from the third bullet in this 
> section is that for this case the message priority is "0" so I am not 
> clear what this sentence means
>
Ah, good catch. The text should be another bullet point in the list.
>
> and why is there a  difference if the MT-PRIORITY or MT-Priority 
> values do exist with regards to "Priority" and "X-Priority" for this case.
>
Basically there are existing header fields with similar semantics 
already in use, so people want to use them as the last resort.
There was a bit of a debate about specific header fields during the IETF 
LC, so this text will hopefully be improved after the debate.
>
> 2.In section 8 "MT-PRIORITY=3". I did not see where the MT-PRIORITY 
> SMTP  extension is specified and has the syntax of using "=" before 
> the value.
>
This is described by the following text in Section 3:

       One optional parameter ("MT-PRIORITY") is added to the
       MAIL FROM command. The value associated with this parameter is
       a decimal integer number from -9 to 9 (inclusive)
       indicating the priority of the email message.  The syntax of

In SMTP parameter values are separated with "=" from the corresponding 
parameter names.
>
> Nits/editorial comments:
>
> 1.MUA is used in section 1 but expanded only in section 5.
>
> 2.Some typos in section 5. "syntatically -- syntactically" "prioritiy 
> -- priority" "comminicate -- communicate" "contraints --constraints"
>
> 3.In section 10 for X.3.TBD3 "Description:  The message mas accepted" 
> I assume you meant "was"
>
> 4.In section D.2 first paragraph some typos "focusses --focuses" 
> "comparision -- comparison"
>
All of these fixed in my copy, thanks!

Best Regards,
Alexey



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

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    Hi Roni,<br>
    Thank you for your review.<br>
    <br>
    On 13/03/2012 19:25, Roni Even wrote:
    <blockquote cite="mid:4f5f9f50.6965b40a.7aaa.6114@mx.google.com"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=ISO-8859-1">
      <meta name="Generator" content="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: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;}
@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:1208569498;
	mso-list-type:hybrid;
	mso-list-template-ids:1331728552 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-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level4
	{mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level7
	{mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1
	{mso-list-id:1999921501;
	mso-list-type:hybrid;
	mso-list-template-ids:-1736538686 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-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level3
	{mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level4
	{mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level5
	{mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level6
	{mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level7
	{mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level8
	{mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level9
	{mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif][if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
      <div class="WordSection1">
        <p class="MsoNormal">I am the assigned Gen-ART reviewer for this
          draft. For background on Gen-ART, please see the FAQ at &lt;<a
            moz-do-not-send="true"
            href="http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq"
            target="_blank">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq</a>&gt;.<o:p></o:p></p>
        <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
        <p class="MsoNormal">Please resolve these comments along with
          any other Last Call comments you may receive.<o:p></o:p></p>
        <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">Document:

          </span><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">draft-melnikov-smtp-priority-09<o:p></o:p></span></p>
        <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">Reviewer:

            Roni Even<o:p></o:p></span></p>
        <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">Review

            Date:2012&#8211;3&#8211;13<o:p></o:p></span></p>
        <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">IETF

            LC End Date: 2012&#8211;3&#8211;28<o:p></o:p></span></p>
        <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">IESG

            Telechat date:<o:p></o:p></span></p>
        <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">Summary:

            This draft is almost ready for publication as a standard
            track </span><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">RFC</span><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">.<o:p></o:p></span></p>
        <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">Major

            issues:<o:p></o:p></span></p>
        <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">Minor

            issues:<o:p></o:p></span></p>
        <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoPlainText" style="margin-left: 0.5in; text-indent:
          -0.25in;"><!--[if !supportLists]--><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><span
              style="mso-list:Ignore">1.<span style="font:7.0pt
                &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span><!--[endif]--><span
            dir="LTR"></span><span style="font-size: 11pt; font-family:
            &quot;Calibri&quot;,&quot;sans-serif&quot;;">In section 4.2&nbsp;
            &#8220;In absence of both the MT-PRIORITY MAIL FROM parameter&nbsp; and
            the MT-Priority header field, other message header fields,
            such&nbsp; as Priority [RFC2156] and X-Priority, MAY be used for
            determining the&nbsp; priority under this "Priority Message
            Handling" SMTP extension.&#8221; . &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;My understanding&nbsp; from the
            third bullet in this section is that for this case the
            message priority is &#8220;0&#8221; so I am not clear what this sentence
            means</span></p>
      </div>
    </blockquote>
    Ah, good catch. The text should be another bullet point in the list.<br>
    <blockquote cite="mid:4f5f9f50.6965b40a.7aaa.6114@mx.google.com"
      type="cite">
      <div class="WordSection1">
        <p class="MsoPlainText" style="margin-left: 0.5in; text-indent:
          -0.25in;"><span style="font-size: 11pt; font-family:
            &quot;Calibri&quot;,&quot;sans-serif&quot;;">and why is
            there a &nbsp;difference if the MT-PRIORITY or MT-Priority values
            do exist with regards to &#8220;Priority&#8221; and &#8220;X-Priority&#8221; for
            this case.</span></p>
      </div>
    </blockquote>
    Basically there are existing header fields with similar semantics
    already in use, so people want to use them as the last resort.<br>
    There was a bit of a debate about specific header fields during the
    IETF LC, so this text will hopefully be improved after the debate.<br>
    <blockquote cite="mid:4f5f9f50.6965b40a.7aaa.6114@mx.google.com"
      type="cite">
      <div class="WordSection1">
        <p class="MsoPlainText"
          style="margin-left:.5in;text-indent:-.25in;mso-list:l1 level1
          lfo1"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><o:p></o:p></span></p>
        <p class="MsoPlainText" style="margin-left: 0.5in; text-indent:
          -0.25in;"><!--[if !supportLists]--><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><span
              style="mso-list:Ignore">2.<span style="font:7.0pt
                &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span><!--[endif]--><span
            dir="LTR"></span><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">In

            section 8 &#8220;MT-PRIORITY=3&#8221;. I did not see where </span><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">the

            MT-PRIORITY SMTP&nbsp; extension is specified and has the syntax
            of using &#8220;=&#8221; before the value.</span></p>
      </div>
    </blockquote>
    This is described by the following text in Section 3:<br>
    <br>
    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; One optional parameter ("MT-PRIORITY") is added to the<br>
    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; MAIL FROM command. The value associated with this parameter is<br>
    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; a decimal integer number from -9 to 9 (inclusive)<br>
    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; indicating the priority of the email message.&nbsp; The syntax of<br>
    <br>
    In SMTP parameter values are separated with "=" from the
    corresponding parameter names.<span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><o:p><br>
      </o:p></span>
    <blockquote cite="mid:4f5f9f50.6965b40a.7aaa.6114@mx.google.com"
      type="cite">
      <div class="WordSection1"> </div>
    </blockquote>
    <blockquote cite="mid:4f5f9f50.6965b40a.7aaa.6114@mx.google.com"
      type="cite">
      <div class="WordSection1">
        <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">Nits/editorial

            comments:<o:p></o:p></span></p>
        <p class="MsoPlainText"><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoPlainText"
          style="margin-left:.5in;text-indent:-.25in;mso-list:l0 level1
          lfo2"><!--[if !supportLists]--><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><span
              style="mso-list:Ignore">1.<span style="font:7.0pt
                &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span><!--[endif]--><span
            dir="LTR"></span><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">MUA

            is used in section 1 but expanded only in section 5. <o:p></o:p></span></p>
        <p class="MsoPlainText"
          style="margin-left:.5in;text-indent:-.25in;mso-list:l0 level1
          lfo2"><!--[if !supportLists]--><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><span
              style="mso-list:Ignore">2.<span style="font:7.0pt
                &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span><!--[endif]--><span
            dir="LTR"></span><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">Some

            typos in section 5. </span><span
            style="font-family:&quot;Courier New&quot;">&#8220;</span><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">syntatically

            &#8211; syntactically&#8221; &#8220;prioritiy &#8211; priority&#8221; &#8220;comminicate &#8211;
            communicate&#8221; &#8220;contraints &#8211;constraints&#8221;<o:p></o:p></span></p>
        <p class="MsoPlainText"
          style="margin-left:.5in;text-indent:-.25in;mso-list:l0 level1
          lfo2"><!--[if !supportLists]--><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><span
              style="mso-list:Ignore">3.<span style="font:7.0pt
                &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span><!--[endif]--><span
            dir="LTR"></span><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">In

            section 10 for X.3.TBD3 &#8220;Description:&nbsp; The message mas
            accepted&#8221; I assume you meant &#8220;was&#8221;<o:p></o:p></span></p>
        <p class="MsoPlainText" style="margin-left: 0.5in; text-indent:
          -0.25in;"><!--[if !supportLists]--><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"><span
              style="mso-list:Ignore">4.<span style="font:7.0pt
                &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span><!--[endif]--><span
            dir="LTR"></span><span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">In

            section D.2 first paragraph some typos </span><span
            style="font-size: 11pt; font-family:
            &quot;Calibri&quot;,&quot;sans-serif&quot;;">&#8220;focusses
            &#8211;focuses&#8221; &#8220;comparision &#8211; comparison&#8221;</span></p>
      </div>
    </blockquote>
    All of these fixed in my copy, thanks!<br>
    <br>
    Best Regards,<br>
    Alexey<br>
    <span
style="font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"></span>
    <blockquote cite="mid:4f5f9f50.6965b40a.7aaa.6114@mx.google.com"
      type="cite">
      <div class="WordSection1"> </div>
    </blockquote>
    <br>
    <br>
  </body>
</html>

--------------080501010100070202020004--

From daedulus@btconnect.com  Tue Mar 20 02:16:14 2012
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ED00521F8871 for <ietf@ietfa.amsl.com>; Tue, 20 Mar 2012 02:16:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.14
X-Spam-Level: 
X-Spam-Status: No, score=-0.14 tagged_above=-999 required=5 tests=[BAYES_20=-0.74, J_CHICKENPOX_15=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MNdg9QPZbTLA for <ietf@ietfa.amsl.com>; Tue, 20 Mar 2012 02:16:13 -0700 (PDT)
Received: from mail.btconnect.com (c2bthomr14.btconnect.com [213.123.20.132]) by ietfa.amsl.com (Postfix) with ESMTP id D51DD21F885C for <ietf@ietf.org>; Tue, 20 Mar 2012 02:16:12 -0700 (PDT)
Received: from host86-162-135-195.range86-162.btcentralplus.com (HELO pc6) ([86.162.135.195]) by c2bthomr14.btconnect.com with SMTP id GTA35967; Tue, 20 Mar 2012 09:16:09 +0000 (GMT)
Message-ID: <004e01cd0671$91e09ca0$4001a8c0@gateway.2wire.net>
From: "t.petch" <daedulus@btconnect.com>
To: "Sprecher, Nurit \(NSN - IL/Hod HaSharon\)" <nurit.sprecher@nsn.com>, <stbryant@cisco.com>
References: <CAAHpaZ=JrKVKHZ0xkK-nszFDf-ttVNoi1p9iZiWa93vKuiNxZA@mail.gmail.com><4F60BF02.1010507@cisco.com><009b01cd0351$52d5f3c0$4001a8c0@gateway.2wire.net><4F635846.60505@cisco.com> <02e601cd0386$3ff90dc0$4001a8c0@gateway.2wire.net> <E4873516F3FC7547BCFE792C7D94039C01710B31@DEMUEXC013.nsn-intra.net>
Subject: Re: Last Call:<draft-betts-itu-oam-ach-code-point-03.txt>(Allocationofan Associated Channel Code Point for Use by ITU-T EthernetbasedOAM) to Informational RFC
Date: Tue, 20 Mar 2012 09:15:06 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Mirapoint-IP-Reputation: reputation=Fair-1, source=Queried, refid=tid=0001.0A0B0303.4F684AD8.00A2, actions=tag
X-Junkmail-Premium-Raw: score=9/50, refid=2.7.2:2012.3.20.85416:17:9.975, ip=86.162.135.195, rules=__HAS_MSGID, __OUTLOOK_MSGID_1, __SANE_MSGID, __TO_MALFORMED_2, __BOUNCE_CHALLENGE_SUBJ, __BOUNCE_NDR_SUBJ_EXEMPT, __SUBJ_ALPHA_END, __MIME_VERSION, __CT, CT_TP_8859_1, __CT_TEXT_PLAIN, __CTE, __HAS_X_PRIORITY, __HAS_MSMAIL_PRI, __HAS_X_MAILER, USER_AGENT_OE, __OUTLOOK_MUA_1, __USER_AGENT_MS_GENERIC, __ANY_URI, CN_TLD, __FRAUD_BODY_WEBMAIL, __URI_NO_WWW, __URI_NO_PATH, BODY_SIZE_4000_4999, __MIME_TEXT_ONLY, RDNS_GENERIC_POOLED, HTML_00_01, HTML_00_10, BODY_SIZE_5000_LESS, RDNS_SUSP_GENERIC, __OUTLOOK_MUA, RDNS_SUSP, __FRAUD_WEBMAIL, BODY_SIZE_7000_LESS
X-Junkmail-Status: score=10/50, host=c2bthomr14.btconnect.com
X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A0B0209.4F684AD9.00C4,ss=1,re=0.000,fgs=0, ip=0.0.0.0, so=2011-07-25 19:15:43, dmn=2011-05-27 18:58:46, mode=multiengine
X-Junkmail-IWF: false
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Mar 2012 09:16:14 -0000

----- Original Message -----
From: "Sprecher, Nurit (NSN - IL/Hod HaSharon)" <nurit.sprecher@nsn.com>
To: "ext t.petch" <daedulus@btconnect.com>; <stbryant@cisco.com>
Cc: <ietf@ietf.org>
Sent: Sunday, March 18, 2012 12:07 PM
Tom,
Did Huub and Malcolm represent the ITU in their assessments?

<tp>
Nurit

You know full well that, on a WG list such as the mpls one from which my quotes
came, we all speak as individuals, you, I and everyone else, not representing
any organisation.

At the same time, as any WG chair must know and act on, some people's views
deserve more weight than other people's.  My personal judgement is that the
people I quoted are likely to have a good insight into the practices and
processes of the ITU-T, most likely the best view I will get, absent a formal
liaison on this particular point. YMMV.

Tom Petch
</tp>

I guess other ITU members have different view on this!
Best regards,
Nurit

-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
ext t.petch
Sent: Friday, March 16, 2012 5:06 PM
To: stbryant@cisco.com
Cc: ietf@ietf.org

----- Original Message -----
From: "Stewart Bryant" <stbryant@cisco.com>
To: "t.petch" <daedulus@btconnect.com>
Cc: "Fangyu Li" <fangyuli1999@gmail.com>; <ietf@ietf.org>
Sent: Friday, March 16, 2012 4:12 PM

> On 16/03/2012 08:46, t.petch wrote:
> > ----- Original Message -----
> > From: "Stewart Bryant"<stbryant@cisco.com>
> > To: "Fangyu Li"<fangyuli1999@gmail.com>
> > Cc:<lifang@catr.cn>;<ietf@ietf.org>
> > Sent: Wednesday, March 14, 2012 4:53 PM
> >> On 14/03/2012 13:36, Fangyu Li wrote:
> >>> I support the allocation of an ACH codepoint to G.8113.1.
> >>> For G.8113.1 had reached the technical and industry maturity to be
> >>> assigned a code point, the codepoint allocation from IETF should
allow
> >>> the ITU-T to progress refinements to G.8113.1 such that it could
> >>> satisfy all the functional requirements defined in RFC 5860.
> >> Please can you tell me version of the G.8113.1 text one would
> >> need to implement to be able to seamlessly interwork with the
> >> equipment that has already been been deployed?
> > Stewart
> >
> > I am sure you already know the answer to that from posts made to the
mpls
list,
> > where we have been told that there is currently an extensive
deployment
> > ('running code') using an experimental value (interesting that there
is a
last
> > call just ending seeking to exterminate such practice, at least for
application
> > protocols) and that the wish is to move to a standards-based value
which
will,
> > perforce, be a different value.
> >
> > Tom Petch
>
> Tom,
>
> I don't think you understood my question.
>
> There are several version of the G.8113.1 text in circulation within
> the ITU-T. I was asking which version accurately describes the
> deployed protocol.

Stewart

One of the e-mails I had in mind was that of Huub Helvoort last December
where
he said
"The draft recommendation G.8113.1 is stable, there have been no major
technical
changes since it was sent to the IETF (when it still had the draft name
G.tpoam)
attache to liaison: https://datatracker.ietf.org/liaison/983/
This is also the status I reported when we did discuss this during
IETF82 in
Taipei."

while another such e-mail is that of Malcolm Betts in January where he
said
"I can confirm that the draft is requesting a code point for the version
of
G.8113.1 that was forwarded to WTSA by SG 15, this is the same as the
draft that was determined in February 2011, I am not anticipating any
changes prior to the approval decision at WTSA.  None of the changes in
G.8113.1 that were anticipated in draft-betts-itu-oam-ach-code-point-01
were implemented,  I will post a new version
draft-betts-itu-oam-ach-code-point to correctly reflect the content and
title on G.8113.1 and respond to the other questions later this week."

I was thinking that that was enough reassurance about the protocol and
its
stability.

I agree that the documents as liaised to us specify that special value
of XXXX
but we were told, on the mpls list, that an experimental value was in
use, ie
one that fell within the remit of section 10 of RFC5586, which, again, I
took to
be sufficient information.

Tom Petch

> I would be interested to also know what ACh Type it is actually
running
> on.
>
> Stewart
>
>
>
>




From daedulus@btconnect.com  Tue Mar 20 02:25:37 2012
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3066111E8073 for <ietf@ietfa.amsl.com>; Tue, 20 Mar 2012 02:25:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.44
X-Spam-Level: 
X-Spam-Status: No, score=-0.44 tagged_above=-999 required=5 tests=[AWL=0.300,  BAYES_20=-0.74]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VO28-44qR9+b for <ietf@ietfa.amsl.com>; Tue, 20 Mar 2012 02:25:36 -0700 (PDT)
Received: from mail.btconnect.com (c2bthomr10.btconnect.com [213.123.20.128]) by ietfa.amsl.com (Postfix) with ESMTP id C31CA11E8072 for <ietf@ietf.org>; Tue, 20 Mar 2012 02:25:35 -0700 (PDT)
Received: from host86-162-135-195.range86-162.btcentralplus.com (HELO pc6) ([86.162.135.195]) by c2bthomr10.btconnect.com with SMTP id GUT44594; Tue, 20 Mar 2012 09:25:31 +0000 (GMT)
Message-ID: <006f01cd0672$e0e2a2c0$4001a8c0@gateway.2wire.net>
From: "t.petch" <daedulus@btconnect.com>
To: "Sabahattin Gucukoglu" <mail-dated-1334746550.15c4ac@sabahattin-gucukoglu.com>, <ietf@ietf.org>
References: <82A794CE-B328-475F-9300-1B6BE628F7E3@sabahattin-gucukoglu.com>
Subject: Re: IPv6 Zone Identifiers Considered Hateful
Date: Tue, 20 Mar 2012 09:24:27 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Mirapoint-IP-Reputation: reputation=Fair-1, source=Queried, refid=tid=0001.0A0B0303.4F684D0A.009E, actions=tag
X-Junkmail-Premium-Raw: score=8/50, refid=2.7.2:2012.3.20.85416:17:8.317, ip=86.162.135.195, rules=__HAS_MSGID, __OUTLOOK_MSGID_1, __SANE_MSGID, __TO_MALFORMED_2, __BOUNCE_CHALLENGE_SUBJ, __BOUNCE_NDR_SUBJ_EXEMPT, __SUBJ_ALPHA_END, __MIME_VERSION, __CT, CT_TP_8859_1, __CT_TEXT_PLAIN, __CTE, __HAS_X_PRIORITY, __HAS_MSMAIL_PRI, __HAS_X_MAILER, USER_AGENT_OE, __OUTLOOK_MUA_1, __USER_AGENT_MS_GENERIC, __ANY_URI, __CP_URI_IN_BODY, ECARD_WORD, BODY_PARA_IS_SENTENCE_URL, BODYTEXTP_SIZE_3000_LESS, BODY_SIZE_2000_2999, __MIME_TEXT_ONLY, RDNS_GENERIC_POOLED, HTML_00_01, HTML_00_10, BODY_SIZE_5000_LESS, RDNS_SUSP_GENERIC, __OUTLOOK_MUA, RDNS_SUSP, BODY_SIZE_7000_LESS
X-Junkmail-Status: score=10/50, host=c2bthomr10.btconnect.com
X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A0B0209.4F684D0B.0208,ss=1,re=0.000,fgs=0, ip=0.0.0.0, so=2011-07-25 19:15:43, dmn=2011-05-27 18:58:46, mode=multiengine
X-Junkmail-IWF: false
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Mar 2012 09:25:37 -0000

Top posting because it fits the Subject well, the details below less so.

There is currently a thread in 6man on

Subject: Re: 6MAN WG Last Call: draft-ietf-6man-uri-zoneid-00.txt
http://www.ietf.org/mail-archive/web/ipv6/current/msg15505.html

on how to put this zoneid into a URI which, given that zone ids start with a %
and that RFC3986 gives that character special, syntactical significance, would
appear to verge on the impossible.  As and when IPv6 gets rolled out, I suspect
that this topic will bite, or haunt, an ever growing number of people - which
makes it worth some consideration now.

Tom Petch

----- Original Message -----
From: "Sabahattin Gucukoglu" <mail@sabahattin-gucukoglu.com>
To: <ietf@ietf.org>
Sent: Monday, March 19, 2012 11:55 AM
Subject: IPv6 Zone Identifiers Considered Hateful


I've obviously not been doing all my homework, and RFC 4007 slipped my
attention.  Worse, for all the communication my IPv6 nodes are doing amongst
themselves using link-local addresses, it's never really been much more than a
hastily-justified curiosity why, when I ping one from the other using
link-local-scoped addresses, I have to put in this zone identifier (%ifname on
BSD and Linux).

Yesterday, I configured a DNS server to listen just using a link-local address,
the one autoconfigured for an ethernet card accessible to all the nodes.  It's a
host, not a router, so I'm relying on that address not being routable and being
filtered at the router.  It didn't work.  The server would not start until I
specified the zone suffix.  Now I am wondering why, given that there is no
ambiguous link-local address anywhere around here, I need to do that.  Can't it
figure it out itself?

What about the other problems with this suffix?  It's host-specific, so it's
unsafe to share it over the network (I need to share the DNS server using
stateless DHCPv6).  The format differs between OSes (Windows uses %n).  It
interferes with URLs, if Wikipedia is to be believed.  It breaks expectations,
essentially because it's the exception to the rule that the address bits (and
hence the address format) conveys all the required information.

So zone suffixes are considered hateful.  Yes, it's true, I enjoy a good whinge
and it's a shame I had to learn this on-demand, but really, their use should be
limited to just those circs where it's actually necessary, and let's be honest,
that ought to be very rare.

Cheers,
Sabahattin



From nurit.sprecher@nsn.com  Tue Mar 20 02:52:38 2012
Return-Path: <nurit.sprecher@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 DB0B021F8772 for <ietf@ietfa.amsl.com>; Tue, 20 Mar 2012 02:52:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.213
X-Spam-Level: 
X-Spam-Status: No, score=-6.213 tagged_above=-999 required=5 tests=[AWL=-0.214, BAYES_00=-2.599, J_CHICKENPOX_15=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HmiCOeGG5yoJ for <ietf@ietfa.amsl.com>; Tue, 20 Mar 2012 02:52:38 -0700 (PDT)
Received: from demumfd002.nsn-inter.net (demumfd002.nsn-inter.net [93.183.12.31]) by ietfa.amsl.com (Postfix) with ESMTP id 754D421F870F for <ietf@ietf.org>; Tue, 20 Mar 2012 02:52:37 -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 q2K9qV3r021808 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 20 Mar 2012 10:52:31 +0100
Received: from demuexc022.nsn-intra.net (demuexc022.nsn-intra.net [10.150.128.35]) by demuprx017.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id q2K9qSb9016971; Tue, 20 Mar 2012 10:52:30 +0100
Received: from DEMUEXC013.nsn-intra.net ([10.150.128.24]) by demuexc022.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 20 Mar 2012 10:52:25 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Last Call:<draft-betts-itu-oam-ach-code-point-03.txt>(Allocationofan Associated Channel Code Point for Use by ITU-T EthernetbasedOAM) to Informational RFC
Date: Tue, 20 Mar 2012 10:52:23 +0100
Message-ID: <E4873516F3FC7547BCFE792C7D94039C0175ADE9@DEMUEXC013.nsn-intra.net>
In-Reply-To: <004e01cd0671$91e09ca0$4001a8c0@gateway.2wire.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Last Call:<draft-betts-itu-oam-ach-code-point-03.txt>(Allocationofan Associated Channel Code Point for Use by ITU-T EthernetbasedOAM) to Informational RFC
Thread-Index: Ac0GeheU/LHHWYUBR42JPNcF7XT3nQAAECzw
References: <CAAHpaZ=JrKVKHZ0xkK-nszFDf-ttVNoi1p9iZiWa93vKuiNxZA@mail.gmail.com><4F60BF02.1010507@cisco.com><009b01cd0351$52d5f3c0$4001a8c0@gateway.2wire.net><4F635846.60505@cisco.com> <02e601cd0386$3ff90dc0$4001a8c0@gateway.2wire.net> <E4873516F3FC7547BCFE792C7D94039C01710B31@DEMUEXC013.nsn-intra.net> <004e01cd0671$91e09ca0$4001a8c0@gateway.2wire.net>
From: "Sprecher, Nurit (NSN - IL/Hod HaSharon)" <nurit.sprecher@nsn.com>
To: "ext t.petch" <daedulus@btconnect.com>, <stbryant@cisco.com>
X-OriginalArrivalTime: 20 Mar 2012 09:52:25.0421 (UTC) FILETIME=[27568FD0:01CD067F]
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: 5174
X-purgate-ID: 151667::1332237151-00007415-9CEE48AF/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: Tue, 20 Mar 2012 09:52:39 -0000

Your statement that "some people's views deserve more weight than other
people's." is even offending...
Still, since there is clearly no consensus in the ITU (and not even
close to consensus), we cannot rely on anything except of a formal
liaison which is approved by the ITU expert with consensus.=20
Nurit

-----Original Message-----
From: ext t.petch [mailto:daedulus@btconnect.com]=20
Sent: Tuesday, March 20, 2012 10:15 AM
To: Sprecher, Nurit (NSN - IL/Hod HaSharon); stbryant@cisco.com
Cc: ietf@ietf.org
Subject: Re: Last
Call:<draft-betts-itu-oam-ach-code-point-03.txt>(Allocationofan
Associated Channel Code Point for Use by ITU-T EthernetbasedOAM) to
Informational RFC

----- Original Message -----
From: "Sprecher, Nurit (NSN - IL/Hod HaSharon)" <nurit.sprecher@nsn.com>
To: "ext t.petch" <daedulus@btconnect.com>; <stbryant@cisco.com>
Cc: <ietf@ietf.org>
Sent: Sunday, March 18, 2012 12:07 PM
Tom,
Did Huub and Malcolm represent the ITU in their assessments?

<tp>
Nurit

You know full well that, on a WG list such as the mpls one from which my
quotes
came, we all speak as individuals, you, I and everyone else, not
representing
any organisation.

At the same time, as any WG chair must know and act on, some people's
views
deserve more weight than other people's.  My personal judgement is that
the
people I quoted are likely to have a good insight into the practices and
processes of the ITU-T, most likely the best view I will get, absent a
formal
liaison on this particular point. YMMV.

Tom Petch
</tp>

I guess other ITU members have different view on this!
Best regards,
Nurit

-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
ext t.petch
Sent: Friday, March 16, 2012 5:06 PM
To: stbryant@cisco.com
Cc: ietf@ietf.org

----- Original Message -----
From: "Stewart Bryant" <stbryant@cisco.com>
To: "t.petch" <daedulus@btconnect.com>
Cc: "Fangyu Li" <fangyuli1999@gmail.com>; <ietf@ietf.org>
Sent: Friday, March 16, 2012 4:12 PM

> On 16/03/2012 08:46, t.petch wrote:
> > ----- Original Message -----
> > From: "Stewart Bryant"<stbryant@cisco.com>
> > To: "Fangyu Li"<fangyuli1999@gmail.com>
> > Cc:<lifang@catr.cn>;<ietf@ietf.org>
> > Sent: Wednesday, March 14, 2012 4:53 PM
> >> On 14/03/2012 13:36, Fangyu Li wrote:
> >>> I support the allocation of an ACH codepoint to G.8113.1.
> >>> For G.8113.1 had reached the technical and industry maturity to be
> >>> assigned a code point, the codepoint allocation from IETF should
allow
> >>> the ITU-T to progress refinements to G.8113.1 such that it could
> >>> satisfy all the functional requirements defined in RFC 5860.
> >> Please can you tell me version of the G.8113.1 text one would
> >> need to implement to be able to seamlessly interwork with the
> >> equipment that has already been been deployed?
> > Stewart
> >
> > I am sure you already know the answer to that from posts made to the
mpls
list,
> > where we have been told that there is currently an extensive
deployment
> > ('running code') using an experimental value (interesting that there
is a
last
> > call just ending seeking to exterminate such practice, at least for
application
> > protocols) and that the wish is to move to a standards-based value
which
will,
> > perforce, be a different value.
> >
> > Tom Petch
>
> Tom,
>
> I don't think you understood my question.
>
> There are several version of the G.8113.1 text in circulation within
> the ITU-T. I was asking which version accurately describes the
> deployed protocol.

Stewart

One of the e-mails I had in mind was that of Huub Helvoort last December
where
he said
"The draft recommendation G.8113.1 is stable, there have been no major
technical
changes since it was sent to the IETF (when it still had the draft name
G.tpoam)
attache to liaison: https://datatracker.ietf.org/liaison/983/
This is also the status I reported when we did discuss this during
IETF82 in
Taipei."

while another such e-mail is that of Malcolm Betts in January where he
said
"I can confirm that the draft is requesting a code point for the version
of
G.8113.1 that was forwarded to WTSA by SG 15, this is the same as the
draft that was determined in February 2011, I am not anticipating any
changes prior to the approval decision at WTSA.  None of the changes in
G.8113.1 that were anticipated in draft-betts-itu-oam-ach-code-point-01
were implemented,  I will post a new version
draft-betts-itu-oam-ach-code-point to correctly reflect the content and
title on G.8113.1 and respond to the other questions later this week."

I was thinking that that was enough reassurance about the protocol and
its
stability.

I agree that the documents as liaised to us specify that special value
of XXXX
but we were told, on the mpls list, that an experimental value was in
use, ie
one that fell within the remit of section 10 of RFC5586, which, again, I
took to
be sufficient information.

Tom Petch

> I would be interested to also know what ACh Type it is actually
running
> on.
>
> Stewart
>
>
>
>




From john-ietf@jck.com  Tue Mar 20 08:11:45 2012
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4A9A021F8489 for <ietf@ietfa.amsl.com>; Tue, 20 Mar 2012 08:11:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.736
X-Spam-Level: 
X-Spam-Status: No, score=-101.736 tagged_above=-999 required=5 tests=[AWL=-1.137, BAYES_00=-2.599, J_BACKHAIR_33=1, J_BACKHAIR_34=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 I-mbT0Xi0+HU for <ietf@ietfa.amsl.com>; Tue, 20 Mar 2012 08:11:44 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 4BB1F21F8478 for <ietf@ietf.org>; Tue, 20 Mar 2012 08:11:44 -0700 (PDT)
Received: from [198.252.137.7] (helo=PST.JCK.COM) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1SA0e5-000CLp-Ca for ietf@ietf.org; Tue, 20 Mar 2012 11:06:45 -0400
Date: Tue, 20 Mar 2012 11:11:38 -0400
From: John C Klensin <john-ietf@jck.com>
To: ietf@ietf.org
Subject: URIs and zone IDs (was: Re: IPv6 Zone Identifiers Considered Hateful)
Message-ID: <2913294EEA9E72CFB5545F25@PST.JCK.COM>
In-Reply-To: <006f01cd0672$e0e2a2c0$4001a8c0@gateway.2wire.net>
References: <82A794CE-B328-475F-9300-1B6BE628F7E3@sabahattin-gucukoglu.com> <006f01cd0672$e0e2a2c0$4001a8c0@gateway.2wire.net>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Mar 2012 15:11:45 -0000

--On Tuesday, March 20, 2012 09:24 +0100 "t.petch"
<daedulus@btconnect.com> wrote:

> There is currently a thread in 6man on
> 
> Subject: Re: 6MAN WG Last Call:
> draft-ietf-6man-uri-zoneid-00.txt
> http://www.ietf.org/mail-archive/web/ipv6/current/msg15505.html
> 
> on how to put this zoneid into a URI which, given that zone
> ids start with a % and that RFC3986 gives that character
> special, syntactical significance, would appear to verge on
> the impossible.  As and when IPv6 gets rolled out, I suspect
> that this topic will bite, or haunt, an ever growing number of
> people - which makes it worth some consideration now.

Tom,

FWIW, zoneids are nothing special in that regard.  While it has
been used less in recent years than a decade or two ago, "%" has
had a special meaning in some email addresses for a long time,
requiring either special treatment in MAILTO or that users know
how to escape the character and that applications follow the
decoding rules exactly and in the correct order.  Tricky
interpretation of "+" in HTML has also made it difficult to use
that character in email addresses in many web-like contexts and,
for it, incorrect interpretations of the decoding rules in
applications has contributed to making escaping the character
into %2B an insufficient workaround.

While RFC 3986 makes the rules perfectly clear, we've seen
applications get the coding and decoding wrong.  Expecting end
users to understand the rules about when escaping is required
and to apply them correctly is, at least IMO, pretty hopeless.

Having IRIs as an overlay on URIs that can, unbeknown to the
user, create even more %-encodings, increases the risks and
complications.  We will almost certainly see applications that,
in the hope of a better user experience (and regardless of what
we tell them in standards) try to decode URIs that contain %
characters into IRIs and getting that wrong.

I think it is all a nightmare waiting to happen.  You may or may
not agree.  Certainly those who are working on IRIs and URIs
either don't see the risks or see them as acceptable.   

Either way, there is nothing particularly special about IPv6
zone identifiers in that regard.  If nothing, interactions
between those zone identifiers and presentation of IPv6
addresses to users (in URIs or otherwise) ought to reinforce a
conclusion the IETF reached years ago but we seem to keep
forgetting.  That conclusion was that protocols and methods that
expose IP addresses (whether IPv4 or IPv6) to users are
generally a bad idea.  If we believe it, we should be designing
in ways that hide or abstract that information, whether into the
DNS, into better location-identifier separation, or otherwise.
That principle doesn't help with special syntax in email
addresses or with the URI<->IRI<->user interactions, but might
call for some careful thinking about zone identifiers and/or
IPv6 addresses and URIs.

The context in which many of us take the opportunity to pledge
to the universal deployment of IPv6 is not intended to numb the
pain of self-inflicted bullets to our feet.

     john


From spromano@unina.it  Tue Mar 20 08:14:45 2012
Return-Path: <spromano@unina.it>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9604221F8543; Tue, 20 Mar 2012 08:14:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.412
X-Spam-Level: 
X-Spam-Status: No, score=-99.412 tagged_above=-999 required=5 tests=[AWL=-0.553, BAYES_20=-0.74, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245,  HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zDIbkkB0RDNm; Tue, 20 Mar 2012 08:14:44 -0700 (PDT)
Received: from smtp2.unina.it (smtp2.unina.it [192.132.34.62]) by ietfa.amsl.com (Postfix) with ESMTP id 601FA21F852C; Tue, 20 Mar 2012 08:14:43 -0700 (PDT)
Received: from [143.225.229.230] ([143.225.229.230]) (authenticated bits=0) by smtp2.unina.it (8.14.4/8.14.4) with ESMTP id q2KFEdNA017050 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Tue, 20 Mar 2012 16:14:39 +0100
Message-ID: <4F689EDD.3020105@unina.it>
Date: Tue, 20 Mar 2012 16:14:37 +0100
From: Simon Pietro Romano <spromano@unina.it>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: vmeet@ietf.org, "ietf@ietf.org" <ietf@ietf.org>
Subject: UMPIRE moderation experiments at IETF83
Content-Type: multipart/alternative; boundary="------------060305020203080901070204"
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Mar 2012 15:14:45 -0000

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

Dear all,

let me remind you of the upcoming moderation experiments we are going to 
setup in Paris. All the details are at the following URL.

http://ietf83.conf.meetecho.com/index.php/UMPIRE_Project

In brief, we have two moderated sessions: 1) SOC WG (RAI area, 
3:10pm-4:10pm slot on Wednesday); 2) RPS BoF (11:20am-1:30pm slot on 
Friday). If you are willing to be active part in the experiment (either 
as a remote or as a local participant), just drop an e-mail to 
team@meetecho.com. Those of you who will be participating in person will 
be assigned an experimental RFID tag to be used during the session.

See you all in Paris!

Simon

-- 
                             _\\|//_
                             ( O-O )
    ~~~~~~~~~~~~~~~~~~~~~~o00~~(_)~~00o~~~~~~~~~~~~~~~~~~~~~~~~
                     Simon Pietro Romano
               Universita' di Napoli Federico II
                  Computer Science Department
         Phone: +39 081 7683823 -- Fax: +39 081 7684219
                 e-mail: spromano@unina.it
           http://www.comics.unina.it/simonpietro.romano

     <<Molti mi dicono che lo scoraggiamento è l'alibi degli
    idioti. Ci rifletto un istante; e mi scoraggio>>. Magritte.
                          oooO
    ~~~~~~~~~~~~~~~~~~~~~~(   )~~ Oooo~~~~~~~~~~~~~~~~~~~~~~~~~
                           \ (    (   )
                            \_)    ) /
                                  (_/



--------------060305020203080901070204
Content-Type: text/html; charset=ISO-8859-15
Content-Transfer-Encoding: 8bit

<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=ISO-8859-15">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    Dear all,<br>
    <br>
    let me remind you of the upcoming moderation experiments we are
    going to setup in Paris. All the details are at the following URL.<br>
    <br>
    <a href="http://ietf83.conf.meetecho.com/index.php/UMPIRE_Project">http://ietf83.conf.meetecho.com/index.php/UMPIRE_Project</a><br>
    <br>
    In brief, we have two moderated sessions: 1) SOC WG (RAI area, <span
      style="color: rgb(51, 51, 51); font-family: 'Lucida Grande',
      Verdana, 'Bitstream Vera Sans', Arial, sans-serif; font-size:
      14px; font-style: normal; font-variant: normal; font-weight:
      normal; letter-spacing: normal; line-height: normal; orphans: 2;
      text-align: -webkit-auto; text-indent: 0px; text-transform: none;
      white-space: normal; widows: 2; word-spacing: 0px;
      -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;
      background-color: rgb(255, 255, 255); display: inline !important;
      float: none; ">3:10pm-4:10pm slot on Wednesday</span>); 2) RPS BoF
    (<span style="color: rgb(51, 51, 51); font-family: 'Lucida Grande',
      Verdana, 'Bitstream Vera Sans', Arial, sans-serif; font-size:
      14px; font-style: normal; font-variant: normal; font-weight:
      normal; letter-spacing: normal; line-height: normal; orphans: 2;
      text-align: -webkit-auto; text-indent: 0px; text-transform: none;
      white-space: normal; widows: 2; word-spacing: 0px;
      -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;
      background-color: rgb(255, 255, 255); display: inline !important;
      float: none; ">11:20am-1:30pm slot on Friday)</span>. If you are
    willing to be active part in the experiment (either as a remote or
    as a local participant), just drop an e-mail to <a class="moz-txt-link-abbreviated" href="mailto:team@meetecho.com">team@meetecho.com</a>.
    Those of you who will be participating in person will be assigned an
    experimental RFID tag to be used during the session.<br>
    <br>
    See you all in Paris!<br>
    <br>
    Simon<br>
    <pre class="moz-signature" cols="72">-- 
                            _\\|//_
                            ( O-O )
   ~~~~~~~~~~~~~~~~~~~~~~o00~~(_)~~00o~~~~~~~~~~~~~~~~~~~~~~~~
                    Simon Pietro Romano
              Universita' di Napoli Federico II
                 Computer Science Department 
        Phone: +39 081 7683823 -- Fax: +39 081 7684219
                e-mail: <a class="moz-txt-link-abbreviated" href="mailto:spromano@unina.it">spromano@unina.it</a>
          <a class="moz-txt-link-freetext" href="http://www.comics.unina.it/simonpietro.romano">http://www.comics.unina.it/simonpietro.romano</a>

    &lt;&lt;Molti mi dicono che lo scoraggiamento è l'alibi degli 
   idioti. Ci rifletto un istante; e mi scoraggio&gt;&gt;. Magritte.
                         oooO
   ~~~~~~~~~~~~~~~~~~~~~~(   )~~ Oooo~~~~~~~~~~~~~~~~~~~~~~~~~
                          \ (    (   )
                           \_)    ) /
                                 (_/

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

--------------060305020203080901070204--

From brian.e.carpenter@gmail.com  Tue Mar 20 14:16:16 2012
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AB89621F8666 for <ietf@ietfa.amsl.com>; Tue, 20 Mar 2012 14:16:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.442
X-Spam-Level: 
X-Spam-Status: No, score=-102.442 tagged_above=-999 required=5 tests=[AWL=-0.843, BAYES_00=-2.599, J_BACKHAIR_33=1, J_BACKHAIR_34=1, 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 QvAA3A-dlsZx for <ietf@ietfa.amsl.com>; Tue, 20 Mar 2012 14:16:16 -0700 (PDT)
Received: from mail-ob0-f172.google.com (mail-ob0-f172.google.com [209.85.214.172]) by ietfa.amsl.com (Postfix) with ESMTP id 05A3C21F865A for <ietf@ietf.org>; Tue, 20 Mar 2012 14:16:14 -0700 (PDT)
Received: by obbtb4 with SMTP id tb4so260060obb.31 for <ietf@ietf.org>; Tue, 20 Mar 2012 14:16:14 -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=X2bDx1+XIbf+fq3HrBMuFeWIi+dXFevUHP1MdPuBvuo=; b=rxlbnBI4XiAd9vS5SBKqEBk6zfbSEL7TQq2UwIWy7XdLMSxZA/j1uRhl7R/hpP3LXA EJo0xBh2LWMYHhhkq0dB8oVdgR2es9jkfgs4fYu+01lsQtowmWmrlH2A2GjOoO+G06JZ b7N+7Y500UtVcVmaJE+2Mv5VqCJOaj1fUI9Wg+MvBrBE3RKuaDhL1Ti2fqlXt1gQDmWu y5Gg5o5P5HvF6ugYnPcWrreLBGb3v/lu1ehau+Sk85d5oq/Yhnf2UHCAcMfG1I3JvGbK SVotzb9BGeHfhfadV+z5O3o9ltkCcKnQtVyAS9BMivTywwlPUTSYvHFhzuPJTVF76grA bD4g==
Received: by 10.182.174.101 with SMTP id br5mr2049366obc.0.1332278174469; Tue, 20 Mar 2012 14:16:14 -0700 (PDT)
Received: from [130.216.38.124] (stf-brian.sfac.auckland.ac.nz. [130.216.38.124]) by mx.google.com with ESMTPS id c7sm1981129oeh.1.2012.03.20.14.16.12 (version=SSLv3 cipher=OTHER); Tue, 20 Mar 2012 14:16:13 -0700 (PDT)
Message-ID: <4F68F39A.3050307@gmail.com>
Date: Wed, 21 Mar 2012 10:16:10 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
Subject: Re: URIs and zone IDs
References: <82A794CE-B328-475F-9300-1B6BE628F7E3@sabahattin-gucukoglu.com>	<006f01cd0672$e0e2a2c0$4001a8c0@gateway.2wire.net> <2913294EEA9E72CFB5545F25@PST.JCK.COM>
In-Reply-To: <2913294EEA9E72CFB5545F25@PST.JCK.COM>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Mar 2012 21:16:16 -0000

On 2012-03-21 04:11, John C Klensin wrote:
> 
> --On Tuesday, March 20, 2012 09:24 +0100 "t.petch"
> <daedulus@btconnect.com> wrote:
> 
>> There is currently a thread in 6man on
>>
>> Subject: Re: 6MAN WG Last Call:
>> draft-ietf-6man-uri-zoneid-00.txt
>> http://www.ietf.org/mail-archive/web/ipv6/current/msg15505.html
>>
>> on how to put this zoneid into a URI which, given that zone
>> ids start with a % and that RFC3986 gives that character
>> special, syntactical significance, would appear to verge on
>> the impossible.  As and when IPv6 gets rolled out, I suspect
>> that this topic will bite, or haunt, an ever growing number of
>> people - which makes it worth some consideration now.

Just to clarify: the authors of draft-ietf-6man-uri-zoneid
are well aware of the fact that the draft has to be updated
because of that issue, and that discussion is ongoing in the
6man WG for now.

It is also very clear that this whole proposal is only of value
for low-level connectivity diagnosis and has no meaning outside
that context.

    Brian

> 
> Tom,
> 
> FWIW, zoneids are nothing special in that regard.  While it has
> been used less in recent years than a decade or two ago, "%" has
> had a special meaning in some email addresses for a long time,
> requiring either special treatment in MAILTO or that users know
> how to escape the character and that applications follow the
> decoding rules exactly and in the correct order.  Tricky
> interpretation of "+" in HTML has also made it difficult to use
> that character in email addresses in many web-like contexts and,
> for it, incorrect interpretations of the decoding rules in
> applications has contributed to making escaping the character
> into %2B an insufficient workaround.
> 
> While RFC 3986 makes the rules perfectly clear, we've seen
> applications get the coding and decoding wrong.  Expecting end
> users to understand the rules about when escaping is required
> and to apply them correctly is, at least IMO, pretty hopeless.
> 
> Having IRIs as an overlay on URIs that can, unbeknown to the
> user, create even more %-encodings, increases the risks and
> complications.  We will almost certainly see applications that,
> in the hope of a better user experience (and regardless of what
> we tell them in standards) try to decode URIs that contain %
> characters into IRIs and getting that wrong.
> 
> I think it is all a nightmare waiting to happen.  You may or may
> not agree.  Certainly those who are working on IRIs and URIs
> either don't see the risks or see them as acceptable.   
> 
> Either way, there is nothing particularly special about IPv6
> zone identifiers in that regard.  If nothing, interactions
> between those zone identifiers and presentation of IPv6
> addresses to users (in URIs or otherwise) ought to reinforce a
> conclusion the IETF reached years ago but we seem to keep
> forgetting.  That conclusion was that protocols and methods that
> expose IP addresses (whether IPv4 or IPv6) to users are
> generally a bad idea.  If we believe it, we should be designing
> in ways that hide or abstract that information, whether into the
> DNS, into better location-identifier separation, or otherwise.
> That principle doesn't help with special syntax in email
> addresses or with the URI<->IRI<->user interactions, but might
> call for some careful thinking about zone identifiers and/or
> IPv6 addresses and URIs.
> 
> The context in which many of us take the opportunity to pledge
> to the universal deployment of IPv6 is not intended to numb the
> pain of self-inflicted bullets to our feet.
> 
>      john
> 
> 

From huubatwork@gmail.com  Tue Mar 20 16:19:20 2012
Return-Path: <huubatwork@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CEADC21E800F for <ietf@ietfa.amsl.com>; Tue, 20 Mar 2012 16:19:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AZLhvTp3Ddw3 for <ietf@ietfa.amsl.com>; Tue, 20 Mar 2012 16:19:20 -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 0463D21F84DD for <ietf@ietf.org>; Tue, 20 Mar 2012 16:19:19 -0700 (PDT)
Received: by eaaq11 with SMTP id q11so186402eaa.31 for <ietf@ietf.org>; Tue, 20 Mar 2012 16:19:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:disposition-notification-to:date:from:reply-to :user-agent:mime-version:to:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=yLF2VixaCKl1FXYqJQguX/QmMye/Fk1KW7oa5ovO7Fg=; b=y8hCgFjX2HRSmp/pVFn4BJ8GmO+go4Vr6p1/BXZTOsMX8n3N5EZ3xT7fh8fRwqWMFJ 6ZlKM7Wi4LR4waaHCpwMHB3JlHSzkpLKZrdgsOFUY2+MDrLxQxj4ZKb+XlXmotqs8DMl lBul/eEQJncFPmoNOL/Fn6SccHnmHH3I7v16q8Wbmo7qq2+765Dt8Sl9vRpSg8Q7/Yn1 RnqUvFv3mSnoEKneRHnSSGqvstN4bTVYc1x+Z+w25pMb//3ecJbHudqlpnOx3R+G6NgP TSI41ygky+tVAiCT0SYiNGQpHfkLkldmkB+eRKpz9LdKLLfF3avEuuevR3KhPEAJfJir BXHA==
Received: by 10.213.29.198 with SMTP id r6mr176837ebc.51.1332285558896; Tue, 20 Mar 2012 16:19:18 -0700 (PDT)
Received: from McAsterix.local (dhcp-077-250-051-060.chello.nl. [77.250.51.60]) by mx.google.com with ESMTPS id v15sm10000697eem.1.2012.03.20.16.19.17 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 20 Mar 2012 16:19:17 -0700 (PDT)
Message-ID: <4F691073.6030709@gmail.com>
Date: Wed, 21 Mar 2012 00:19:15 +0100
From: Huub van Helvoort <huubatwork@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt> (Allocation of an Associated Channel Code Point for Use by ITU-T Ethernet based OAM) to Informational RFC
References: <20120222151252.32262.82157.idtracker@ietfa.amsl.com>
In-Reply-To: <20120222151252.32262.82157.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
Reply-To: huubatwork@gmail.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, 20 Mar 2012 23:19:20 -0000

Hello,

I continue my support for the codepoint allocation

I agree with Russ's statement in
https://www.ietf.org/ibin/c5i?mid=6&rid=49&gid=0&k1=933&k2=62185&tid=1331648664
"Some people are using the lack of a code point as the reason that
  the cannot support the ITU-T document. My approach tells the ITU-T
  that a code point is available to them IFF they are able to reach
  consensus. The removes IETF from the discussion. This creates a
  situation where G.8113.1 succeeded or fails based on the ITU-T
  members actions, with no finger pointing at the IETF. This is
  completely a Layer 9 consideration, and it has noting to do with
  the technical content of the document. "

The codepoint allocation should allow the ITU-T to make refinements
to G.8113.1 such that it can satisfy the functional requirements defined 
in RFC 5860.

Regards, Huub.

===================================================================
On 22-02-12 16:12, The IESG wrote:
>
> The IESG has received a request from an individual submitter to consider
> the following document:
> - 'Allocation of an Associated Channel Code Point for Use by ITU-T
>     Ethernet based OAM'
>    <draft-betts-itu-oam-ach-code-point-03.txt>  as an 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-03-21. 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 assigns an Associated Channel Type code point for
>     carrying Ethernet based Operations, Administration, and Management
>     messages in the MPLS Generic Associated Channel (G-ACh).
>
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-betts-itu-oam-ach-code-point/
>
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-betts-itu-oam-ach-code-point/
>
>
> No IPR declarations have been submitted directly on this I-D.
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-announce


-- 
*****************************************************************
                          我爱外点一七三一

From ryoo@etri.re.kr  Tue Mar 20 17:51:42 2012
Return-Path: <ryoo@etri.re.kr>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 09E5E21F858A for <ietf@ietfa.amsl.com>; Tue, 20 Mar 2012 17:51:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.859
X-Spam-Level: 
X-Spam-Status: No, score=-98.859 tagged_above=-999 required=5 tests=[AWL=0.005, BAYES_00=-2.599, HELO_MISMATCH_INFO=1.448, HTML_IMAGE_ONLY_20=1.546, HTML_MESSAGE=0.001, MIME_HTML_MOSTLY=0.001, MPART_ALT_DIFF=0.739, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tP1Z6iHyFGue for <ietf@ietfa.amsl.com>; Tue, 20 Mar 2012 17:51:39 -0700 (PDT)
Received: from email1.etri.info (email1.etri.re.kr [129.254.16.131]) by ietfa.amsl.com (Postfix) with ESMTP id 4173221F8587 for <ietf@ietf.org>; Tue, 20 Mar 2012 17:51:38 -0700 (PDT)
Received: from mail pickup service by email1.etri.info with Microsoft SMTPSVC; Wed, 21 Mar 2012 09:51:38 +0900
Priority: normal
X-ReadCheckName: ietf%40ietf.org
Thread-Topic: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt> 
X-ReadCheckMessageID: <abaee738-ebdd-4364-a2f2-399e95644b5c@etri.re.kr>
thread-index: Ac0G/MWQ/KyuW/eWQ3aYx5UfQs/swQ==
Content-Transfer-Encoding: 7bit
From: "Ryoo, Jeong-dong" <ryoo@etri.re.kr>
To: <ietf@ietf.org>
Cc: 
Subject: Re: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt> 
Date: Wed, 21 Mar 2012 09:51:37 +0900
Comment: ??, ???, 
Message-ID: <BC9DC1E61632444BAF2746499819BB0E@etri.info>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_216A_01CD0748.357A9C40"
X-Mailer: Microsoft CDO for Exchange 2000
Content-class: urn:content-classes:message
Importance: normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.4133
X-OriginalArrivalTime: 21 Mar 2012 00:51:38.0191 (UTC) FILETIME=[C5B1EDF0:01CD06FC]
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: "Ryoo, Jeong-dong" <ryoo@etri.re.kr>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Mar 2012 00:51:42 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_216A_01CD0748.357A9C40
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: base64


------=_NextPart_000_216A_01CD0748.357A9C40
Content-Type: text/html;
	charset="utf-8"
Content-Transfer-Encoding: base64

PERJViBzdHlsZT0iRk9OVC1GQU1JTFk6IEFyaWFsOyBGT05ULVNJWkU6IDEwcHQiIGlkPW1zZ2Jv
ZHk+SGksPC9ESVY+DQo8RElWIHN0eWxlPSJGT05ULUZBTUlMWTogQXJpYWw7IEZPTlQtU0laRTog
MTBwdCI+Jm5ic3A7PC9ESVY+DQo8RElWIHN0eWxlPSJGT05ULUZBTUlMWTogQXJpYWw7IEZPTlQt
U0laRTogMTBwdCI+SSBzdXBwb3J0IFJ1c3MncyZuYnNwO2FwcHJvYWNoIHRvIGFsbG9jYXRlIGEg
Y29kZXBvaW50IHRvIEcuODExMy4xJm5ic3A7YXMgc3RhdGVkIGluIGhpcyBlbWFsIChpZXRmIG1l
c3NhZ2UgNjIxODUgLSAwMy8wMS8yMDEyKTwvRElWPg0KPERJViBzdHlsZT0iRk9OVC1GQU1JTFk6
IEFyaWFsOyBGT05ULVNJWkU6IDEwcHQiPiZuYnNwOzwvRElWPg0KPERJViBzdHlsZT0iRk9OVC1G
QU1JTFk6IEFyaWFsOyBGT05ULVNJWkU6IDEwcHQiPiZsdDtSdXNzJmd0OzwvRElWPg0KPERJViBz
dHlsZT0iRk9OVC1GQU1JTFk6IEFyaWFsOyBGT05ULVNJWkU6IDEwcHQiPlNvbWUgcGVvcGxlIGFy
ZSB1c2luZyB0aGUgbGFjayBvZiBhIGNvZGUgcG9pbnQgYXMgdGhlIHJlYXNvbiB0aGF0IHRoZSBj
YW5ub3Qgc3VwcG9ydCB0aGUgSVRVLVQgZG9jdW1lbnQuIE15IGFwcHJvYWNoIHRlbGxzIHRoZSBJ
VFUtVCB0aGF0IGEgY29kZSBwb2ludCBpcyBhdmFpbGFibGUgdG8gdGhlbSBJRkYgdGhleSBhcmUg
YWJsZSB0byByZWFjaCBjb25zZW5zdXMuIFRoZSByZW1vdmVzIElFVEYgZnJvbSB0aGUgZGlzY3Vz
c2lvbi4gVGhpcyBjcmVhdGVzIGEgc2l0dWF0aW9uIHdoZXJlIEcuODExMy4xIHN1Y2NlZWRlZCBv
ciBmYWlscyBiYXNlZCBvbiB0aGUgSVRVLVQgbWVtYmVycyBhY3Rpb25zLCB3aXRoIG5vIGZpbmdl
ciBwb2ludGluZyBhdCB0aGUgSUVURi4gVGhpcyBpcyBjb21wbGV0ZWx5IGEgTGF5ZXIgOSBjb25z
aWRlcmF0aW9uLCBhbmQgaXQgaGFzIG5vdGluZyB0byBkbyB3aXRoIHRoZSB0ZWNobmljYWwgY29u
dGVudCBvZiB0aGUgZG9jdW1lbnQuJm5ic3A7PEJSPiZsdDsvUnVzcyZndDs8L0RJVj4NCjxESVYg
c3R5bGU9IkZPTlQtRkFNSUxZOiBBcmlhbDsgRk9OVC1TSVpFOiAxMHB0Ij4mbmJzcDs8L0RJVj4N
CjxESVYgc3R5bGU9IkZPTlQtRkFNSUxZOiBBcmlhbDsgRk9OVC1TSVpFOiAxMHB0Ij5UaGUgY29k
ZXBvaW50IGFsbG9jYXRpb24gc2hvdWxkIGFsbG93IHRoZSBJVFUtVCB0byBwcm9ncmVzcyByZWZp
bmVtZW50cyB0byBHLjgxMTMuMSBzdWNoIHRoYXQgaXQgY2FuIHNhdGlzZnkgYWxsIHRoZSBmdW5j
dGlvbmFsIHJlcXVpcmVtZW50cyBkZWZpbmVkIGluIFJGQyA1ODYwLjxCUj48L0RJVj4NCjxESVYg
c3R5bGU9IkZPTlQtRkFNSUxZOiBBcmlhbDsgRk9OVC1TSVpFOiAxMHB0Ij5CZXN0IHJlZ2FyZHMs
PC9ESVY+DQo8RElWIHN0eWxlPSJGT05ULUZBTUlMWTogQXJpYWw7IEZPTlQtU0laRTogMTBwdCI+
Jm5ic3A7PC9ESVY+DQo8RElWIHN0eWxlPSJGT05ULUZBTUlMWTogQXJpYWw7IEZPTlQtU0laRTog
MTBwdCI+SmVvbmctZG9uZzwvRElWPg0KPERJViBzdHlsZT0iRk9OVC1GQU1JTFk6IEFyaWFsOyBG
T05ULVNJWkU6IDEwcHQiPiZuYnNwOzwvRElWPjxpbWcgc3R5bGU9ImRpc3BsYXk6bm9uZSIgd2lk
dGg9MCBoZWlnaHQ9MCBzcmM9Imh0dHA6Ly91bWFpbC5ldHJpLnJlLmtyL0V4dGVybmFsX1JlYWRD
aGVjay5hc3B4P2VtYWlsPWlldGZAaWV0Zi5vcmcmbmFtZT1pZXRmJTQwaWV0Zi5vcmcmZnJvbWVt
YWlsPXJ5b29AZXRyaS5yZS5rciZtZXNzYWdlaWQ9JTNDYWJhZWU3MzgtZWJkZC00MzY0LWEyZjIt
Mzk5ZTk1NjQ0YjVjQGV0cmkucmUua3IlM0UiPg==

------=_NextPart_000_216A_01CD0748.357A9C40--

From nurit.sprecher@nsn.com  Wed Mar 21 00:42:15 2012
Return-Path: <nurit.sprecher@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 646DB21F85B5 for <ietf@ietfa.amsl.com>; Wed, 21 Mar 2012 00:42:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.51
X-Spam-Level: 
X-Spam-Status: No, score=-6.51 tagged_above=-999 required=5 tests=[AWL=0.089,  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 nWLpliizytyM for <ietf@ietfa.amsl.com>; Wed, 21 Mar 2012 00:42:14 -0700 (PDT)
Received: from demumfd001.nsn-inter.net (demumfd001.nsn-inter.net [93.183.12.32]) by ietfa.amsl.com (Postfix) with ESMTP id 1A70E21F857A for <ietf@ietf.org>; Wed, 21 Mar 2012 00:42:12 -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 q2L7g9mi010002 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 21 Mar 2012 08:42:09 +0100
Received: from demuexc022.nsn-intra.net (demuexc022.nsn-intra.net [10.150.128.35]) by demuprx017.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id q2L7g5cl029048; Wed, 21 Mar 2012 08:42:06 +0100
Received: from DEMUEXC013.nsn-intra.net ([10.150.128.24]) by demuexc022.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 21 Mar 2012 08:41:59 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Subject: RE: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt> (Allocationof an Associated Channel Code Point for Use by ITU-T Ethernet basedOAM) to Informational RFC
Date: Wed, 21 Mar 2012 08:41:58 +0100
Message-ID: <E4873516F3FC7547BCFE792C7D94039C0175B3F2@DEMUEXC013.nsn-intra.net>
In-Reply-To: <4F691073.6030709@gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt> (Allocationof an Associated Channel Code Point for Use by ITU-T Ethernet basedOAM) to Informational RFC
Thread-Index: Ac0G7+qs5GhCigRQRd2Ua5AtfB5AOgARO0vQ
References: <20120222151252.32262.82157.idtracker@ietfa.amsl.com> <4F691073.6030709@gmail.com>
From: "Sprecher, Nurit (NSN - IL/Hod HaSharon)" <nurit.sprecher@nsn.com>
To: <huubatwork@gmail.com>, <ietf@ietf.org>
X-OriginalArrivalTime: 21 Mar 2012 07:41:59.0774 (UTC) FILETIME=[194D57E0:01CD0736]
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: 4546
X-purgate-ID: 151667::1332315730-00003570-28D24739/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, 21 Mar 2012 07:42:15 -0000

SGVsbG8sDQpJIHN0aWxsIGV4cGVjdCB0aGUgYXV0aG9yIG9mIGRyYWZ0LWJldHRzIHRvIGFuc3dl
ciBteSBxdWVzdGlvbi4uLg0KCSJNYXliZSB5b3UgY291bGQgY2xhcmlmeSBob3cgdGhlIHRleHQg
aW4geW91ciBkcmFmdCBjYW4gYmUgaW1wcm92ZWQgdG8gcHJvdGVjdCB0aGUgdXNlIG9mIHRoZSBj
b2RlIHBvaW50IGZyb20gZnV0dXJlIGV4dGVuc2lvbnMgYmV5b25kIHRoZSBwdXJwb3NlIG9mIHRo
ZSBjb2RlIHBvaW50IGFsbG9jYXRpb24/Ig0KSSBhbSBhIGJpdCBkaXNhcHBvaW50ZWQgdG8gc2Vl
IHRoYXQgdGhlIGF1dGhvciBzaW1wbHkgZG9lcyBub3QgcmVzcG9uZCB0byB0aGUgcXVlc3Rpb25z
IGFuZCBwcm9wb3NlZCBtb2RpZmljYXRpb25zIGhlIGdvdCBvbiB0aGUgbGlzdC4gDQpJZiB3ZSB3
YW50IHRvIHByb2R1Y3RpdmVseSBtb3ZlIGZvcndhcmQsIGl0IHdvdWxkIGJlIGdvb2QgdG8gaGF2
ZSB0aGUgYXV0aG9yIHJlc3BvbmRpbmcgdG8gdGhlIHF1ZXN0aW9ucyBhbmQgcHJvcG9zYWxzLiAN
CkJlc3QgcmVnYXJkcywNCk51cml0DQoNCg0KLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCkZy
b206IGlldGYtYm91bmNlc0BpZXRmLm9yZyBbbWFpbHRvOmlldGYtYm91bmNlc0BpZXRmLm9yZ10g
T24gQmVoYWxmIE9mIGV4dCBIdXViIHZhbiBIZWx2b29ydA0KU2VudDogV2VkbmVzZGF5LCBNYXJj
aCAyMSwgMjAxMiAxOjE5IEFNDQpUbzogaWV0ZkBpZXRmLm9yZw0KU3ViamVjdDogUmU6IExhc3Qg
Q2FsbDogPGRyYWZ0LWJldHRzLWl0dS1vYW0tYWNoLWNvZGUtcG9pbnQtMDMudHh0PiAoQWxsb2Nh
dGlvbm9mIGFuIEFzc29jaWF0ZWQgQ2hhbm5lbCBDb2RlIFBvaW50IGZvciBVc2UgYnkgSVRVLVQg
RXRoZXJuZXQgYmFzZWRPQU0pIHRvIEluZm9ybWF0aW9uYWwgUkZDDQoNCkhlbGxvLA0KDQpJIGNv
bnRpbnVlIG15IHN1cHBvcnQgZm9yIHRoZSBjb2RlcG9pbnQgYWxsb2NhdGlvbg0KDQpJIGFncmVl
IHdpdGggUnVzcydzIHN0YXRlbWVudCBpbg0KaHR0cHM6Ly93d3cuaWV0Zi5vcmcvaWJpbi9jNWk/
bWlkPTYmcmlkPTQ5JmdpZD0wJmsxPTkzMyZrMj02MjE4NSZ0aWQ9MTMzMTY0ODY2NA0KIlNvbWUg
cGVvcGxlIGFyZSB1c2luZyB0aGUgbGFjayBvZiBhIGNvZGUgcG9pbnQgYXMgdGhlIHJlYXNvbiB0
aGF0DQogIHRoZSBjYW5ub3Qgc3VwcG9ydCB0aGUgSVRVLVQgZG9jdW1lbnQuIE15IGFwcHJvYWNo
IHRlbGxzIHRoZSBJVFUtVA0KICB0aGF0IGEgY29kZSBwb2ludCBpcyBhdmFpbGFibGUgdG8gdGhl
bSBJRkYgdGhleSBhcmUgYWJsZSB0byByZWFjaA0KICBjb25zZW5zdXMuIFRoZSByZW1vdmVzIElF
VEYgZnJvbSB0aGUgZGlzY3Vzc2lvbi4gVGhpcyBjcmVhdGVzIGENCiAgc2l0dWF0aW9uIHdoZXJl
IEcuODExMy4xIHN1Y2NlZWRlZCBvciBmYWlscyBiYXNlZCBvbiB0aGUgSVRVLVQNCiAgbWVtYmVy
cyBhY3Rpb25zLCB3aXRoIG5vIGZpbmdlciBwb2ludGluZyBhdCB0aGUgSUVURi4gVGhpcyBpcw0K
ICBjb21wbGV0ZWx5IGEgTGF5ZXIgOSBjb25zaWRlcmF0aW9uLCBhbmQgaXQgaGFzIG5vdGluZyB0
byBkbyB3aXRoDQogIHRoZSB0ZWNobmljYWwgY29udGVudCBvZiB0aGUgZG9jdW1lbnQuICINCg0K
VGhlIGNvZGVwb2ludCBhbGxvY2F0aW9uIHNob3VsZCBhbGxvdyB0aGUgSVRVLVQgdG8gbWFrZSBy
ZWZpbmVtZW50cw0KdG8gRy44MTEzLjEgc3VjaCB0aGF0IGl0IGNhbiBzYXRpc2Z5IHRoZSBmdW5j
dGlvbmFsIHJlcXVpcmVtZW50cyBkZWZpbmVkIA0KaW4gUkZDIDU4NjAuDQoNClJlZ2FyZHMsIEh1
dWIuDQoNCj09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09
PT09PT09PT09PT09PT09PT0NCk9uIDIyLTAyLTEyIDE2OjEyLCBUaGUgSUVTRyB3cm90ZToNCj4N
Cj4gVGhlIElFU0cgaGFzIHJlY2VpdmVkIGEgcmVxdWVzdCBmcm9tIGFuIGluZGl2aWR1YWwgc3Vi
bWl0dGVyIHRvIGNvbnNpZGVyDQo+IHRoZSBmb2xsb3dpbmcgZG9jdW1lbnQ6DQo+IC0gJ0FsbG9j
YXRpb24gb2YgYW4gQXNzb2NpYXRlZCBDaGFubmVsIENvZGUgUG9pbnQgZm9yIFVzZSBieSBJVFUt
VA0KPiAgICAgRXRoZXJuZXQgYmFzZWQgT0FNJw0KPiAgICA8ZHJhZnQtYmV0dHMtaXR1LW9hbS1h
Y2gtY29kZS1wb2ludC0wMy50eHQ+ICBhcyBhbiBJbmZvcm1hdGlvbmFsIFJGQw0KPg0KPiBUaGUg
SUVTRyBwbGFucyB0byBtYWtlIGEgZGVjaXNpb24gaW4gdGhlIG5leHQgZmV3IHdlZWtzLCBhbmQg
c29saWNpdHMNCj4gZmluYWwgY29tbWVudHMgb24gdGhpcyBhY3Rpb24uIFBsZWFzZSBzZW5kIHN1
YnN0YW50aXZlIGNvbW1lbnRzIHRvIHRoZQ0KPiBpZXRmQGlldGYub3JnIG1haWxpbmcgbGlzdHMg
YnkgMjAxMi0wMy0yMS4gRXhjZXB0aW9uYWxseSwgY29tbWVudHMgbWF5IGJlDQo+IHNlbnQgdG8g
aWVzZ0BpZXRmLm9yZyBpbnN0ZWFkLiBJbiBlaXRoZXIgY2FzZSwgcGxlYXNlIHJldGFpbiB0aGUN
Cj4gYmVnaW5uaW5nIG9mIHRoZSBTdWJqZWN0IGxpbmUgdG8gYWxsb3cgYXV0b21hdGVkIHNvcnRp
bmcuDQo+DQo+IEFic3RyYWN0DQo+DQo+ICAgICBUaGlzIGRvY3VtZW50IGFzc2lnbnMgYW4gQXNz
b2NpYXRlZCBDaGFubmVsIFR5cGUgY29kZSBwb2ludCBmb3INCj4gICAgIGNhcnJ5aW5nIEV0aGVy
bmV0IGJhc2VkIE9wZXJhdGlvbnMsIEFkbWluaXN0cmF0aW9uLCBhbmQgTWFuYWdlbWVudA0KPiAg
ICAgbWVzc2FnZXMgaW4gdGhlIE1QTFMgR2VuZXJpYyBBc3NvY2lhdGVkIENoYW5uZWwgKEctQUNo
KS4NCj4NCj4gVGhlIGZpbGUgY2FuIGJlIG9idGFpbmVkIHZpYQ0KPiBodHRwOi8vZGF0YXRyYWNr
ZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0LWJldHRzLWl0dS1vYW0tYWNoLWNvZGUtcG9pbnQvDQo+DQo+
IElFU0cgZGlzY3Vzc2lvbiBjYW4gYmUgdHJhY2tlZCB2aWENCj4gaHR0cDovL2RhdGF0cmFja2Vy
LmlldGYub3JnL2RvYy9kcmFmdC1iZXR0cy1pdHUtb2FtLWFjaC1jb2RlLXBvaW50Lw0KPg0KPg0K
PiBObyBJUFIgZGVjbGFyYXRpb25zIGhhdmUgYmVlbiBzdWJtaXR0ZWQgZGlyZWN0bHkgb24gdGhp
cyBJLUQuDQo+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
DQo+IElFVEYtQW5ub3VuY2UgbWFpbGluZyBsaXN0DQo+IElFVEYtQW5ub3VuY2VAaWV0Zi5vcmcN
Cj4gaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9pZXRmLWFubm91bmNlDQoN
Cg0KLS0gDQoqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioq
KioqKioqKioqKioqKioqKg0KICAgICAgICAgICAgICAgICAgICAgICAgICDmiJHniLHlpJbngrnk
uIDkuIPkuInkuIANCg==

From satoshi.ueno@ntt.com  Wed Mar 21 02:20:46 2012
Return-Path: <satoshi.ueno@ntt.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8C4A821F864E for <ietf@ietfa.amsl.com>; Wed, 21 Mar 2012 02:20:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tnPNP5yTpMK1 for <ietf@ietfa.amsl.com>; Wed, 21 Mar 2012 02:20:46 -0700 (PDT)
Received: from mgw3.noc.ntt.com (mgw3.noc.ntt.com [210.160.15.14]) by ietfa.amsl.com (Postfix) with ESMTP id A80B921F862F for <ietf@ietf.org>; Wed, 21 Mar 2012 02:20:45 -0700 (PDT)
Received: from mop3.noc.ntt.com by mgw3.noc.ntt.com (NTT-Com MailSV) with ESMTP id q2L9Kenk027569 for <ietf@ietf.org>; Wed, 21 Mar 2012 18:20:40 +0900 (JST)
Received: from mip01.noc.ntt.com (mvi2.noc.ntt.com) by mop3.noc.ntt.com (NTT-Com MailSV) with ESMTP id <0M18005Q29Y5M1@ntt.com> for ietf@ietf.org; Wed, 21 Mar 2012 18:20:40 +0900 (JST)
Date: Wed, 21 Mar 2012 18:20:34 +0900
From: "Satoshi UENO" <satoshi.ueno@ntt.com>
Subject: Re: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt> (Allocation of an Associated Channel Code Point for Use by ITU-T Ethernet based OAM) to Informational RFC
To: ietf@ietf.org
Message-id: <016001cd0743$df0f7d70$9d2e7850$@ntt.com>
MIME-version: 1.0
X-Mailer: Microsoft Outlook 14.0
Content-type: text/plain; charset=us-ascii
Content-language: ja
Content-transfer-encoding: 7bit
Thread-index: Ac0HQ9tCu7clu1gVR+2GL0z/zkKTnA==
x-ccmail-original-to: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Mar 2012 09:20:46 -0000

Hi,

I support to allocate a codepoint to G.8113.1.

Best ragards,
Satoshi


From stephen.farrell@cs.tcd.ie  Wed Mar 21 02:33:15 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 BD50221E801A for <ietf@ietfa.amsl.com>; Wed, 21 Mar 2012 02:33:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.309
X-Spam-Level: 
X-Spam-Status: No, score=-102.309 tagged_above=-999 required=5 tests=[AWL=0.290, 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 ZoS3mV3Whyg9 for <ietf@ietfa.amsl.com>; Wed, 21 Mar 2012 02:33:15 -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 0DCFD21E8012 for <ietf@ietf.org>; Wed, 21 Mar 2012 02:33:13 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hermes.scss.tcd.ie (Postfix) with ESMTP id 593C2154416; Wed, 21 Mar 2012 09:33:12 +0000 (GMT)
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=1332322392; bh=+T+SQ7WPMSlOOU /lURscInaiGm/QOOiXx1dFqXlfGo4=; b=iqmFlHbBTDHoVpHELN4wb053zimoyI NHLH5QmsNqTDytwQqk+2o74OcWUHgNnCypZSUdvqyFnIM0sOoTSMSzNig07lmpav /RDWnlVGfQEpO42NAuoKdhwRkOdBrceMsGoeeZj5x6EbzhCTLQ8skASE7+IXzvDd LyjEqYWmQFPqCye/AWDZ0UWtAHhGYFVvqzg4FJJwq36BpcRl6qKxUcViqImNvxw6 a2+GSQa9skKB2ARd/uSYX0oQybM9TP6DYSSem0YKjysZjqgTNdMwi19zkItdezLx /plA3ZKAUu3TXp5iLjJw70oHcg8fS5RhPcRQ3vANvko287LDNZayIbXA==
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 bRte3aLr1vAD; Wed, 21 Mar 2012 09:33:12 +0000 (GMT)
Received: from [10.87.48.7] (unknown [86.44.79.158]) by smtp.scss.tcd.ie (Postfix) with ESMTPSA id F0B2A154382; Wed, 21 Mar 2012 09:33:09 +0000 (GMT)
Message-ID: <4F69A055.6040807@cs.tcd.ie>
Date: Wed, 21 Mar 2012 09:33:09 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: Satoshi UENO <satoshi.ueno@ntt.com>
Subject: Re: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt> (Allocation of an Associated Channel Code Point for Use by ITU-T Ethernet based OAM) to Informational RFC
References: <016001cd0743$df0f7d70$9d2e7850$@ntt.com>
In-Reply-To: <016001cd0743$df0f7d70$9d2e7850$@ntt.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Mar 2012 09:33:15 -0000

Hi,

On 03/21/2012 09:20 AM, Satoshi UENO wrote:
> Hi,
>
> I support to allocate a codepoint to G.8113.1.

Good for you. But just so you and other folks posting
similar mails know, this mail won't be helpful for me
as an AD when it comes to evaluating this topic, since
I've no clue as to the personalities involved here and
the mail itself doesn't say why you support this or why
its a good thing. Basically, mails like this aren't
meaningful to me, so I'll fall back to trusting the
other ADs who've been involved in this and can evaluate
whether this kind of mail carries any weight at all.

Mails with substantive content are much more useful.

Cheers,
S.

PS: Not picking on you, I've just noticed a few of
these mails and wondered if the senders know how
they are perceived.

>
> Best ragards,
> Satoshi
>
>

From lear@cisco.com  Wed Mar 21 04:06:28 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 E787521F8649 for <ietf@ietfa.amsl.com>; Wed, 21 Mar 2012 04:06:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.24
X-Spam-Level: 
X-Spam-Status: No, score=-110.24 tagged_above=-999 required=5 tests=[AWL=-0.242, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_15=0.6, 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 wjQIR6ZNUrVz for <ietf@ietfa.amsl.com>; Wed, 21 Mar 2012 04:06:27 -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 5B9EC21F863F for <ietf@ietf.org>; Wed, 21 Mar 2012 04:06:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=lear@cisco.com; l=4144; q=dns/txt; s=iport; t=1332327986; x=1333537586; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to; bh=ZGY321zfQkx2rHP1oFyipIsBLXoBhGYPUXW/7vo+OMw=; b=kePwdxLB7pt4qtX/aGlBkTyOdaWYvGu0nh77uoWumt7gU/fV7sp+S6uU ERYYwgC8G64deAynLnUBm8TpK0gkW/4byaMsIFg5SjP0e7mUaiG3sDedh BD0hOwHrtTUUN+AWd5aMqcFG2Cv8uOQOhS5BUE88WnhPYtUmKaXnWCWB5 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgEFAFK1aU+Q/khN/2dsb2JhbABEhUGxPIEHggkBAQEDARIBEFUBBQsLBBQJDAoEBwICCQMCAQIBRQYNAQcBARAHB4djBZhXjQWSHY1TghiBFgSVX44/gWiCaA
X-IronPort-AV: E=Sophos;i="4.73,623,1325462400"; d="scan'208,217";a="68979916"
Received: from ams-core-4.cisco.com ([144.254.72.77]) by ams-iport-2.cisco.com with ESMTP; 21 Mar 2012 11:06:25 +0000
Received: from dhcp-10-61-96-151.cisco.com (dhcp-10-61-96-151.cisco.com [10.61.96.151]) by ams-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id q2LB6On7016996; Wed, 21 Mar 2012 11:06:24 GMT
Message-ID: <4F69B630.9050909@cisco.com>
Date: Wed, 21 Mar 2012 12:06:24 +0100
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:11.0) Gecko/20120313 Thunderbird/11.0
MIME-Version: 1.0
To: "t.petch" <daedulus@btconnect.com>
Subject: Re: Last Call:<draft-betts-itu-oam-ach-code-point-03.txt>	(Allocation of anAssociated Channel Code Point for Use by	ITU-T Ethernet basedOAM) to Informational RFC
References: <20120222151252.32262.82157.idtracker@ietfa.amsl.com><03a301ccf174$ff953290$febf97b0$@olddog.co.uk><515703B08A3A064C9CC8C09ACCC710DC0631679E@XMB-RCD-103.cisco.com><C71DA9B1-A61F-4C5D-8DCE-3702271CBB6D@vigilsec.com><4F4FA70B.2030906@pi.nu><D0F60388-D852-4815-917A-B14BF40C64FB@vigilsec.com><BD60EA38ED03AF5A21868DF1@PST.JCK.COM> <4F4FC252.9010001@cisco.com> <C3E581FB44D46BF4128A2229@PST.JCK.COM> <029b01ccfb84$4e4e2220$4001a8c0@gateway.2wire.net> <4F55F92F.1020105@cisco.com> <005701ccfbad$5c6d9060$4001a8c0@gateway.2wire.net>
In-Reply-To: <005701ccfbad$5c6d9060$4001a8c0@gateway.2wire.net>
X-Enigmail-Version: 1.4
Content-Type: multipart/alternative; boundary="------------030508030104020008090500"
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, 21 Mar 2012 11:06:28 -0000

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

Tom,

I've let this sit a while, but wanted to respond on the following point:

On 3/6/12 4:25 PM, t.petch wrote:
> -ur responsibility is to ourselves first and foremost, and to see that
> our process is followed.  That process exists to, amongst other things,
> insure safe use and interoperable use of our own protocols.
> Which, Eliot, is where we part company.  Given the interest in and uptake
> of MPLS outside the original definition, we have a wider responsibility,
> as we have in, say, managing the IP address or domain name space.

If our process is broken, we should change it.  Our processes should
take into account that which *we* can control.  Making the best
recommendations for the use of our protocols on the Internet addresses
your point about the "wider community".  The IETF exists to serve that
wider community, but when others attempt to use our works in a way that
might harm our work, we equally have a responsibility to hold a line.  I
am NOT saying that in this instance, by the way, G.8113.1 harms IETF
work if a proper code point is assigned.  It would harm our work if a
code point was simply expropriated.



>   As
> with the last two, if we do not consider the needs of all parties, and not just
> ourselves, we may lose our influence in these matters.  Yes we must follow our
> processes but in the interests of a wider community than just ourselves.

Were this really true, then we must reject this request because of the
likelihood of fragmented solutions that do not interoperate.  Is that
what you are arguing?

Eliot

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

<html>
  <head>
    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    Tom,<br>
    <br>
    I've let this sit a while, but wanted to respond on the following
    point:<br>
    <br>
    On 3/6/12 4:25 PM, t.petch wrote:
    <blockquote
      cite="mid:005701ccfbad$5c6d9060$4001a8c0@gateway.2wire.net"
      type="cite">
      <pre wrap="">-ur responsibility is to ourselves first and foremost, and to see that
our process is followed.  That process exists to, amongst other things,
insure safe use and interoperable use of our own protocols.
</pre>
      <pre wrap="">
Which, Eliot, is where we part company.  Given the interest in and uptake
of MPLS outside the original definition, we have a wider responsibility,
as we have in, say, managing the IP address or domain name space.</pre>
    </blockquote>
    <br>
    If our process is broken, we should change it.  Our processes should
    take into account that which <b>we</b> can control.  Making the
    best recommendations for the use of our protocols on the Internet
    addresses your point about the "wider community".  The IETF exists
    to serve that wider community, but when others attempt to use our
    works in a way that might harm our work, we equally have a
    responsibility to hold a line.  I am NOT saying that in this
    instance, by the way, G.8113.1 harms IETF work if a proper code
    point is assigned.  It would harm our work if a code point was
    simply expropriated.<br>
    <br>
    <br>
    <br>
    <blockquote
      cite="mid:005701ccfbad$5c6d9060$4001a8c0@gateway.2wire.net"
      type="cite">
      <pre wrap="">  As
with the last two, if we do not consider the needs of all parties, and not just
ourselves, we may lose our influence in these matters.  Yes we must follow our
processes but in the interests of a wider community than just ourselves.</pre>
    </blockquote>
    <br>
    Were this really true, then we must reject this request because of
    the likelihood of fragmented solutions that do not interoperate.  Is
    that what you are arguing?<br>
    <br>
    Eliot<br>
  </body>
</html>

--------------030508030104020008090500--

From c-sai@bx.jp.nec.com  Wed Mar 21 04:19:59 2012
Return-Path: <c-sai@bx.jp.nec.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 46B8921F85A1 for <ietf@ietfa.amsl.com>; Wed, 21 Mar 2012 04:19:59 -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 8jJz8m2AG-3F for <ietf@ietfa.amsl.com>; Wed, 21 Mar 2012 04:19:58 -0700 (PDT)
Received: from tyo202.gate.nec.co.jp (TYO202.gate.nec.co.jp [202.32.8.206]) by ietfa.amsl.com (Postfix) with ESMTP id 45D0621F85A2 for <ietf@ietf.org>; Wed, 21 Mar 2012 04:19:58 -0700 (PDT)
Received: from mailgate3.nec.co.jp ([10.7.69.160]) by tyo202.gate.nec.co.jp (8.13.8/8.13.4) with ESMTP id q2LBJuSO023056;  Wed, 21 Mar 2012 20:19:56 +0900 (JST)
Received: (from root@localhost) by mailgate3.nec.co.jp (8.11.7/3.7W-MAILGATE-NEC) id q2LBJuI13308; Wed, 21 Mar 2012 20:19:56 +0900 (JST)
Received: from mail01b.kamome.nec.co.jp (mail01b.kamome.nec.co.jp [10.25.43.2]) by mailsv4.nec.co.jp (8.13.8/8.13.4) with ESMTP id q2LBJuKS010649; Wed, 21 Mar 2012 20:19:56 +0900 (JST)
Received: from togyo.jp.nec.com ([10.26.220.4] [10.26.220.4]) by mail01b.kamome.nec.co.jp with ESMTP id BT-MMP-213197; Wed, 21 Mar 2012 20:19:33 +0900
Received: from vpcja157 ([10.38.16.157] [10.38.16.157]) by mail.jp.nec.com with ESMTP; Wed, 21 Mar 2012 20:19:33 +0900
From: "Zhenlong Cui" <c-sai@bx.jp.nec.com>
To: "'Russ Housley'" <housley@vigilsec.com>
References: <20120222151252.32262.82157.idtracker@ietfa.amsl.com><03a301ccf174$ff953290$febf97b0$@olddog.co.uk><515703B08A3A064C9CC8C09ACCC710DC0631679E@XMB-RCD-103.cisco.com><C71DA9B1-A61F-4C5D-8DCE-3702271CBB6D@vigilsec.com><4F4FA70B.2030906@pi.nu><D0F60388-D852-4815-917A-B14BF40C64FB@vigilsec.com><BD60EA38ED03AF5A21868DF1@PST.JCK.COM><4F4FC252.9010001@cisco.com><444F9B86-84CD-4A21-BD02-067877052A0A@vigilsec.com><E4873516F3FC7547BCFE792C7D94039C015D125D@DEMUEXC013.nsn-intra.net> <28D09181-4EAF-4770-963F-A57073D77AE7@vigilsec.com>
Subject: RE: Last Call:<draft-betts-itu-oam-ach-code-point-03.txt>	(Allocationof anAssociated Channel Code Point for Use by	ITU-T EthernetbasedOAM) to Informational RFC
Date: Wed, 21 Mar 2012 20:19:33 +0900
Message-ID: <D146B4460F4446DBB393CE6D304668F1@nsl.ad.nec.co.jp>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
In-reply-to: <28D09181-4EAF-4770-963F-A57073D77AE7@vigilsec.com>
thread-index: Acz4BlU2IueJ2GojRNydBOlfsU8rYAPTH81g
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5931
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, 21 Mar 2012 11:19:59 -0000

I support the allocation of an ACH code point to G.8113.1, and I agree with Russ's comment.

In addition, to avoid the same argument after the ITU-T's decision, I suggest we should clearly conclude that a code point be
available if ITU-T will make consensus on G.8113.1, during this last call.
This conclusion should be immediately informed to ITU-T.

Best regards,
zhenlong

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of Russ Housley
> Sent: Friday, March 02, 2012 8:52 AM
> To: Sprecher, Nurit (NSN - IL/Hod HaSharon)
> Cc: IETF
> Subject: Re: Last Call:<draft-betts-itu-oam-ach-code-point-03.txt> (Allocationof anAssociated Channel Code Point for Use
> by ITU-T EthernetbasedOAM) to Informational RFC
> 
> Nurit:
> 
> Some people are using the lack of a code point as the reason that the cannot support the ITU-T document.  My approach tells
> the ITU-T that a code point is available to them IFF they are able to reach consensus.  The removes IETF from the discussion.
> This creates a situation where G.8113.1 succeeded or fails based on the ITU-T members actions, with no finger pointing at
> the IETF.  This is completely a Layer 9 consideration, and it has noting to do with the technical content of the document.
> 
> Russ
> 
> 
> On Mar 1, 2012, at 2:33 PM, Sprecher, Nurit (NSN - IL/Hod HaSharon) wrote:
> 
> > Russ,
> > I propose to simply re-discuss it when and IFF G.8113.1 is mature and
> > approved...
> > Best regards,
> > Nurit
> >
> >
> > -----Original Message-----
> > From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
> > ext Russ Housley
> > Sent: Thursday, March 01, 2012 9:12 PM
> > To: IETF
> > Subject: Re: Last Call:<draft-betts-itu-oam-ach-code-point-03.txt>
> > (Allocation of anAssociated Channel Code Point for Use by ITU-T Ethernet
> > basedOAM) to Informational RFC
> >
> >>>> Right now, there is no ITU-T approved document to reference.
> >>>> I am certainly not an expert on ITU-T process, but my
> >>>> understanding is that earliest that we could see an approved
> >>>> G.8113.1 is December 2012.  My point is that we don't want to
> >>>> assign a code point until the ITU-T approves their document.
> >>>> However, if we are willing to assign a code point to G.8113.1
> >>>> once it is approved, then this would be an approach where the
> >>>> code point assignment would block on the approval of the
> >>>> normative reference.
> >>>>
> >>>> I like this approach from the political point of view.  With
> >>>> this approach the IETF tells the ITU-T that if and only if
> >>>> they are able to achieve consensus on G.8113.1, then a code
> >>>> point will be assigned.
> >>> FWIW, this seems entirely appropriate to me.  If we do it this
> >>> way, I think it is important to note --for the benefit of those
> >>> more historically involved with the ITU and others-- that we
> >>> routinely block our own documents on normative references to
> >>> work that is still in progress and, usually, do not do related
> >>> code point allocations until the blocking referenced documents
> >>> are ready.  Once the present I-D is judged to be sufficiently
> >>> ready, this approach would therefore be IETF approval and a
> >>> formal guarantee to the ITU that a code point will be allocated
> >>> if an when G.8113.1 is approved and published, but not
> >>> assignment of that code point until the referenced base document
> >>> is finished.
> >>>
> >>> Completely normal procedurally.
> >>>
> >> To be clear John our normal requirement would be that the
> >> technical community achieved consensus that the base document
> >> was ready. I have never seen ITU-T consensus on the contents
> >> of G.8113.1 at any meeting that I have observed. What in your
> >> view is the criteria for determining that  G.8113.1 has achieved
> >> consensus?
> >
> >
> > This is not an IETF problem, and I do not think that the IETF ought to
> > be discussing the internal workings of the ITU-T process.  The point is
> > to come up with a mechanism that allows the code point to be assigned if
> > and only if the ITU-T does come to a consensus by whatever means is
> > allowed by their own process.
> >
> > Russ
> > _______________________________________________
> > Ietf mailing list
> > Ietf@ietf.org
> > https://www.ietf.org/mailman/listinfo/ietf
> 
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf


From alessandro.dalessandro@telecomitalia.it  Wed Mar 21 07:16:31 2012
Return-Path: <alessandro.dalessandro@telecomitalia.it>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5848721F86F5 for <ietf@ietfa.amsl.com>; Wed, 21 Mar 2012 07:16:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.919
X-Spam-Level: 
X-Spam-Status: No, score=-0.919 tagged_above=-999 required=5 tests=[AWL=0.201,  BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, J_CHICKENPOX_15=0.6, 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 Hf1ti5CFg8h5 for <ietf@ietfa.amsl.com>; Wed, 21 Mar 2012 07:16:30 -0700 (PDT)
Received: from GRFEDG702RM001.telecomitalia.it (grfedg702rm001.telecomitalia.it [217.169.121.21]) by ietfa.amsl.com (Postfix) with ESMTP id 353C321F86F3 for <ietf@ietf.org>; Wed, 21 Mar 2012 07:16:30 -0700 (PDT)
Received: from grfhub702rm001.griffon.local (10.19.3.9) by GRFEDG702RM001.telecomitalia.it (10.173.88.21) with Microsoft SMTP Server (TLS) id 8.2.254.0; Wed, 21 Mar 2012 15:16:28 +0100
Received: from GRFMBX702RM001.griffon.local ([10.19.3.20]) by grfhub702rm001.griffon.local ([10.19.9.235]) with mapi; Wed, 21 Mar 2012 15:15:26 +0100
From: D'Alessandro Alessandro Gerardo <alessandro.dalessandro@telecomitalia.it>
To: "ietf@ietf.org" <ietf@ietf.org>
Date: Wed, 21 Mar 2012 15:15:24 +0100
Subject: R: Last Call:<draft-betts-itu-oam-ach-code-point-03.txt> (Allocation	of anAssociated Channel Code Point for Use by	ITU-T Ethernet basedOAM) to Informational RFC
Thread-Topic: Last Call:<draft-betts-itu-oam-ach-code-point-03.txt> (Allocation	of anAssociated Channel Code Point for Use by	ITU-T Ethernet basedOAM) to Informational RFC
Thread-Index: Acz7oFecI8YJL68SRp2bt66DGRUiYQLtXgnA
Message-ID: <A1F769BC58A8B146B2EEA818EAE052A2097389D5FE@GRFMBX702RM001.griffon.local>
References: <20120222151252.32262.82157.idtracker@ietfa.amsl.com><03a301ccf174$ff953290$febf97b0$@olddog.co.uk><515703B08A3A064C9CC8C09ACCC710DC0631679E@XMB-RCD-103.cisco.com><C71DA9B1-A61F-4C5D-8DCE-3702271CBB6D@vigilsec.com><4F4FA70B.2030906@pi.nu><D0F60388-D852-4815-917A-B14BF40C64FB@vigilsec.com><BD60EA38ED03AF5A21868DF1@PST.JCK.COM> <4F4FC252.9010001@cisco.com> <C3E581FB44D46BF4128A2229@PST.JCK.COM> <029b01ccfb84$4e4e2220$4001a8c0@gateway.2wire.net>
In-Reply-To: <029b01ccfb84$4e4e2220$4001a8c0@gateway.2wire.net>
Accept-Language: en-US
Content-Language: it-IT
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
x-ti-disclaimer: Disclaimer1
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Mar 2012 14:16:31 -0000

I support the draft.
Multi-vendor interoperable implementations of the protocol the draft  is as=
king for the allocation of a code point  has been already tested and deploy=
ed and therefore I agree with Mr. Petch when he says  we should approve it =
now to facilitate the migration of the existing boxes to an approved soluti=
on.

Best regards,
Alessandro
------------------------------------------------------------------
Telecom Italia
Alessandro Gerardo D'Alessandro
Transport Innovation
Via Reiss Romoli, 274 - 10148 Torino
phone:  +39 011 228 5887
mobile: +39 335 766 9607
fax: +39 06 418 639 07


-----Messaggio originale-----
Da: t.petch [mailto:daedulus@btconnect.com]
Inviato: marted=EC 6 marzo 2012 11:32
A: John C Klensin; stbryant@cisco.com
Cc: ietf@ietf.org
Oggetto: Re: Last Call:<draft-betts-itu-oam-ach-code-point-03.txt> (Allocat=
ion of anAssociated Channel Code Point for Use by ITU-T Ethernet basedOAM) =
to Informational RFC

I am finding myself with some unfamiliar bedfellows on this issue, but yes,=
 it should be approved - see inline.

Tom Petch

----- Original Message -----
From: "John C Klensin" <john-ietf@jck.com>
To: <stbryant@cisco.com>
Cc: <ietf@ietf.org>
Sent: Friday, March 02, 2012 12:04 AM
Subject: Re: Last Call:<draft-betts-itu-oam-ach-code-point-03.txt> (Allocat=
ion of anAssociated Channel Code Point for Use by ITU-T Ethernet basedOAM) =
to Informational RFC


 <snip>

> (2) Whether it is reasonable or appropriate for the IETF to use our
> responsibility for code point assignments and consequent relationship
> with IANA to try to keep protocols that are not consistent with our
> design judgment and aesthetics --no matter how grounded in experience
> and good engineering-- off the Internet.  That is the "Internet
> gatekeeper" function about which, as you know, I've expressed concern
> in other contexts.  I think the answer has got to be "we can, should,
> and always will exercise quality control on stable specifications and
> normative references but, unless we can justify being sure of our own
> infallibility, we cannot and should not try to prevent another body
> from deploying a specification on the Internet by using our
> control of the registration model".   Telling people why we
> think their ideas are sub-optimal is fine, as is identifying any risks
> we see in appropriate and visible places, but telling another group
> what they can't do because the IETF doesn't like the idea isn't.

We claim ownership of the name space on behalf of all parties, all SDOs gov=
ernments, NGOs, anyone and anything, and this gives us a special responsibi=
lity to exercise that wisely.  We should beware of imposing our ideas of co=
rrectness of any kind on another SDO - that is up to  them to decide, not u=
s.

Of course, one open technical solution to a problem is best but the RFC Ser=
ies is suitable cluttered with instances of the IETF failing to achieve tha=
t so any argument based on those grounds is hypocritical.

A stable, approved reference is ideal, but we have been told of the widespr=
ead deployment of this approach using an experimental
code point so the running code very much exists.   If that is camping
on something that it would be better if it were not, then that is something=
 to fix, and something we can fix.

There is no reason not to approve the allocation of a code point and furthe=
rmore, I believe we should do it now, to facilitate the migration of the ex=
isting boxes to an approved solution.  If that leaves another SDO with an i=
ncompatability between what is working and what their documents say, well, =
the IETF has been there too; not a good place to be, but it is up to the SD=
O to resolve that, not the IETF.

Tom Petch

> And I think that distinction is entirely consistent with Russ's
> suggestion.
>
> best,
>    john
>
>
>
>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>
>



Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle per=
sone indicate. La diffusione, copia o qualsiasi altra azione derivante dall=
a conoscenza di queste informazioni sono rigorosamente vietate. Qualora abb=
iate ricevuto questo documento per errore siete cortesemente pregati di dar=
ne immediata comunicazione al mittente e di provvedere alla sua distruzione=
, Grazie.

This e-mail and any attachments is confidential and may contain privileged =
information intended for the addressee(s) only. Dissemination, copying, pri=
nting or use by anybody else is unauthorised. If you are not the intended r=
ecipient, please delete this message and any attachments and advise the sen=
der by return e-mail, Thanks.


Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle per=
sone indicate. La diffusione, copia o qualsiasi altra azione derivante dall=
a conoscenza di queste informazioni sono rigorosamente vietate. Qualora abb=
iate ricevuto questo documento per errore siete cortesemente pregati di dar=
ne immediata comunicazione al mittente e di provvedere alla sua distruzione=
, Grazie.

This e-mail and any attachments is confidential and may contain privileged =
information intended for the addressee(s) only. Dissemination, copying, pri=
nting or use by anybody else is unauthorised. If you are not the intended r=
ecipient, please delete this message and any attachments and advise the sen=
der by return e-mail, Thanks.


From alessandro.dalessandro@telecomitalia.it  Wed Mar 21 08:05:35 2012
Return-Path: <alessandro.dalessandro@telecomitalia.it>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E9F6F21F863F for <ietf@ietfa.amsl.com>; Wed, 21 Mar 2012 08:05:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.793
X-Spam-Level: 
X-Spam-Status: No, score=-0.793 tagged_above=-999 required=5 tests=[AWL=-0.126, BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, J_CHICKENPOX_15=0.6, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1, SARE_SUB_ENC_UTF8=0.152]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QXHSqyRFG0ui for <ietf@ietfa.amsl.com>; Wed, 21 Mar 2012 08:05:35 -0700 (PDT)
Received: from GRFEDG701RM001.telecomitalia.it (grfedg701rm001.telecomitalia.it [217.169.121.20]) by ietfa.amsl.com (Postfix) with ESMTP id 586BC21F8513 for <ietf@ietf.org>; Wed, 21 Mar 2012 08:05:34 -0700 (PDT)
Received: from grfhub702rm001.griffon.local (10.19.3.9) by GRFEDG701RM001.telecomitalia.it (10.173.88.20) with Microsoft SMTP Server (TLS) id 8.2.254.0; Wed, 21 Mar 2012 16:05:32 +0100
Received: from GRFMBX702RM001.griffon.local ([10.19.3.20]) by grfhub702rm001.griffon.local ([10.19.9.235]) with mapi; Wed, 21 Mar 2012 16:04:24 +0100
From: D'Alessandro Alessandro Gerardo <alessandro.dalessandro@telecomitalia.it>
To: "ietf@ietf.org" <ietf@ietf.org>
Date: Wed, 21 Mar 2012 16:04:23 +0100
Subject: =?utf-8?B?Ujog15TXoNeT15XXnzogUkU6IExhc3QgQ2FsbDo8ZHJhZnQtYmV0dHMtaXR1?= =?utf-8?B?LW9hbS1hY2gtY29kZS1wb2ludC0wMy50eHQ+KEFsbG9jYXRpb25vZglhbiA=?= =?utf-8?B?QXNzb2NpYXRlZCBDaGFubmVsIENvZGUgUG9pbnQgZm9yIFVzZSBieUlUVS0=?= =?utf-8?B?VCBFdGhlcm5ldGJhc2VkIE9BTSkgdG8JSW5mb3JtYXRpb25hbCBSRkM=?=
Thread-Topic: =?utf-8?B?15TXoNeT15XXnzogUkU6IExhc3QgQ2FsbDo8ZHJhZnQtYmV0dHMtaXR1LW9h?= =?utf-8?B?bS1hY2gtY29kZS1wb2ludC0wMy50eHQ+KEFsbG9jYXRpb25vZglhbiBBc3M=?= =?utf-8?B?b2NpYXRlZCBDaGFubmVsIENvZGUgUG9pbnQgZm9yIFVzZSBieUlUVS1UIEU=?= =?utf-8?B?dGhlcm5ldGJhc2VkIE9BTSkgdG8JSW5mb3JtYXRpb25hbCBSRkM=?=
Thread-Index: Ac0B6GB7EtwuABoGTP2UbPu0bPkjYgFiap0A
Message-ID: <A1F769BC58A8B146B2EEA818EAE052A2097389D69F@GRFMBX702RM001.griffon.local>
References: <8fab01cd014c$dea8f551$5e209f0a@nsnintra.net> <050401cd01d1$10aa47c0$4001a8c0@gateway.2wire.net>
In-Reply-To: <050401cd01d1$10aa47c0$4001a8c0@gateway.2wire.net>
Accept-Language: en-US
Content-Language: it-IT
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
x-ti-disclaimer: Disclaimer1
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: Wed, 21 Mar 2012 15:05:36 -0000

RGVhciBhbGwsDQpXcnQgZHJhZnQtYmV0dHMsIEkgYmVsaWV2ZSBpdCBpcyBhcHByb3ByaWF0ZSB0
byBhbGxvY2F0ZSBhIGNvZGUgcG9pbnQgZm9yIHRoZSByZWZlcmVuY2VkIHNwZWNpZmljYXRpb24g
d2l0aG91dCBhbnkgcmVzdHJpY3Rpb24gYWJvdXQgdGhlIHBvc3NpYmlsaXR5IHRvIGV2b2x2ZSBt
ZXNzYWdlcy9wcm90b2NvbHMgd2hlbiBjb21wYXRpYmlsaXR5IGlzIHByZXNlcnZlZC4gSXQgaXMg
bm90IG9ubHkgdW5uZWNlc3NhcnkgYnV0IGl0IGRvZXMgbm90IGhlbHAgaW4gaW1wcm92aW5nIHRo
ZSByZWxhdGlvbnNoaXAgYmV0d2VlbiB0aGUgdHdvIFNET3MuDQoNCkJlc3QgcmVnYXJkcywNCkFs
ZXNzYW5kcm8NCi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLQ0KVGVsZWNvbSBJdGFsaWENCkFsZXNzYW5kcm8gR2VyYXJkbyBE
J0FsZXNzYW5kcm8NClRyYW5zcG9ydCBJbm5vdmF0aW9uDQpWaWEgUmVpc3MgUm9tb2xpLCAyNzQg
LSAxMDE0OCBUb3Jpbm8NCnBob25lOiAgKzM5IDAxMSAyMjggNTg4Nw0KbW9iaWxlOiArMzkgMzM1
IDc2NiA5NjA3DQpmYXg6ICszOSAwNiA0MTggNjM5IDA3DQoNCg0KLS0tLS1NZXNzYWdnaW8gb3Jp
Z2luYWxlLS0tLS0NCkRhOiB0LnBldGNoIFttYWlsdG86ZGFlZHVsdXNAYnRjb25uZWN0LmNvbV0N
CkludmlhdG86IG1lcmNvbGVkw6wgMTQgbWFyem8gMjAxMiAxMTo1Ng0KQTogU3ByZWNoZXIsIE51
cml0IChOU04gLSBJTC9Ib2QgSGFTaGFyb24pOyBleHQgUm9zcyBDYWxsb24NCkNjOiBpZXRmQGll
dGYub3JnDQpPZ2dldHRvOiBSZTog15TXoNeT15XXnzogUkU6IExhc3QgQ2FsbDo8ZHJhZnQtYmV0
dHMtaXR1LW9hbS1hY2gtY29kZS1wb2ludC0wMy50eHQ+KEFsbG9jYXRpb25vZiBhbiBBc3NvY2lh
dGVkIENoYW5uZWwgQ29kZSBQb2ludCBmb3IgVXNlIGJ5SVRVLVQgRXRoZXJuZXRiYXNlZCBPQU0p
IHRvIEluZm9ybWF0aW9uYWwgUkZDDQoNCi0tLS0tIE9yaWdpbmFsIE1lc3NhZ2UgLS0tLS0NCkZy
b206ICJTcHJlY2hlciwgTnVyaXQgKE5TTiAtIElML0hvZCBIYVNoYXJvbikiIDxudXJpdC5zcHJl
Y2hlckBuc24uY29tPg0KVG86ICJBbmRyZXcgRy4gTWFsaXMiIDxhZ21hbGlzQGdtYWlsLmNvbT47
ICJleHQgUm9zcyBDYWxsb24iDQo8cmNhbGxvbkBqdW5pcGVyLm5ldD4NCkNjOiA8aWV0ZkBpZXRm
Lm9yZz4NClNlbnQ6IFR1ZXNkYXksIE1hcmNoIDEzLCAyMDEyIDg6MDkgUE0NClN1YmplY3Q6INeU
16DXk9eV1586IFJFOiBMYXN0DQpDYWxsOjxkcmFmdC1iZXR0cy1pdHUtb2FtLWFjaC1jb2RlLXBv
aW50LTAzLnR4dD4oQWxsb2NhdGlvbm9mIGFuIEFzc29jaWF0ZWQgQ2hhbm5lbCBDb2RlIFBvaW50
IGZvciBVc2UgYnlJVFUtVCBFdGhlcm5ldGJhc2VkIE9BTSkgdG8gSW5mb3JtYXRpb25hbCBSRkMN
Cg0KDQpSb3NzLA0KaSBhbSBhZnJhaWQgdGhhdCB5b3UgbWlzc2VkIHRoZSBwb2ludC4gVGhlcmUg
d2lsbCBub3QgYmUgYSBmaW5hbCB2ZXJzaW9uIHNpbmNlIGFzIHdyaXR0ZW4gaW4gZHJhZnQtYmV0
dHMsIGFsbCAgSVRVIHJlY29tbWVuZGF0aW9ucyBhcmUgc3ViamVjdCB0byByZXZpc2lvbnMsIGFu
ZCB0aGUgY29kZSBwb2ludCB3aWxsIGFsc28gYmUgdXNlZCBmb3IgZnV0dXJlIHJldmlzaW9ucyBv
ZiB0aGUgZG9jdW1lbnQuIE5ldyBtZXNzYWdlcy9wcm90b2NvbHMgY2FuIGJlIGRlZmluZWQgaW4g
ZnV0dXJlIHJldmlzaW9ucyBvZiB0aGUgcmVjb21tZW5kYXRpb24gYW5kIHRoZXkgd2lsbCB1c2Ug
dGhlIHNhbWUgY29kZSBwb2ludCB0aGF0IGlzIGFsbG9jYXRlZCBmb3IgdGhlIGZpcnN0IHZlcnNp
b24uDQpUaGlzIGlzIGEgcmVhbCBpc3N1ZS4NClJlZ2FyZHMsDQpOdXJpdA0KLS0tLS3XlNeV15PX
oteUINee16fXldeo15nXqi0tLS0tDQrXnteQ16o6IGV4dCBSb3NzIENhbGxvbg0K16DXqdec15c6
ICAxMy8wMy8yMDEyLCAxOToyNw0K15DXnDogQW5kcmV3IEcuIE1hbGlzOyBTcHJlY2hlciwgTnVy
aXQgKE5TTiAtIElML0hvZCBIYVNoYXJvbikNCtei15XXqtenOiBpZXRmQGlldGYub3JnDQrXoNeV
16nXkDogUkU6IExhc3QgQ2FsbDo8ZHJhZnQtYmV0dHMtaXR1LW9hbS1hY2gtY29kZS1wb2ludC0w
My50eHQ+KEFsbG9jYXRpb25vZiBhbiBBc3NvY2lhdGVkIENoYW5uZWwgQ29kZSBQb2ludCBmb3Ig
VXNlIGJ5SVRVLVQgRXRoZXJuZXRiYXNlZCBPQU0pIHRvIEluZm9ybWF0aW9uYWwgUkZDIEkgYWdy
ZWUgdGhhdCB0aGUgYWxsb2NhdGlvbiBvZiBhIGNvZGUgcG9pbnQgc2hvdWxkIGJlIHRvIGEgc3Bl
Y2lmaWMgdmVyc2lvbiBvZiA4MTEzLjEsDQoNCjx0cD4NCldoeT8NCg0KSSBjYW4gdW5kZXJzdGFu
ZCBhIG5ldyBjb2RlIHBvaW50IGJlaW5nIHJlcXVpcmVkIGlmIHRoZXJlIGlzIGEgbmV3IGFuZCBi
YWNrd2FyZHMgaW5jb21wYXRpYmxlIGZvcm1hdCBmb3IgdGhlIG1lc3NhZ2VzLCBidXQgaWYgdGhl
IG1lc3NhZ2VzIGFyZSBleHRlbmRlZCBpbiBhIGZvcndhcmRzIGNvbXBhdGlibGUgbWFubmVyLCBh
ZGRpbmcgbmV3IFRMViBmb3IgZXhhbXBsZSwgb3IgYSBuZXcgZm9ybWF0IG9mIElGX0lELCB0aGVu
IHdoeSBzaG91bGQgd2UgYnVybiBhIG5ldyBjb2RlIHBvaW50Pw0KDQpXb3VsZCB5b3Ugc2F5IHRo
YXQgd2Ugc2hvdWxkIGhhdmUgYSBkb3plbiBkaWZmZXJlbnQgcG9ydCBudW1iZXJzIGZvciBIVFRQ
IHRvIHJlZmxlY3QgaXRzIGV2b2x1dGlvbiBvdmVyIHRpbWU/ICBJZiBub3QsIHdoeSBub3Q/DQoN
CkRlbWFuZGluZyB0aGF0IHRoZSBJVFUtVCBjb21lIGJhY2sgdG8gdXMgZm9yIGEgbmV3IHJvdW5k
IG9mIG5lZ290aWF0aW9uIHdoZW4gaXQgaXMgdGVjaG5pY2FsbHkgdW5uZWNlc3Nhcnkgc2VlbXMg
dG8gYmUgcGxhY2luZyBhbiB1bm5lY2Vzc2FyeSBiYXJyaWVyIGJldHdlZW4gdGhlIHR3byBTRE9z
Lg0KDQpUb20gUGV0Y2gNCg0KYW5kIHNwZWNpZmljYWxseSBzaG91bGQgYmUgdG8gdGhlIGZpbmFs
IHZlcnNpb24gdGhhdCBpcyBhcHByb3ZlZCBieSB0aGUgSVRVLVQgKGFzc3VtaW5nIHRoYXQgYSBm
aW5hbCB2ZXJzaW9uIG9mIDgxMTMuMSB3aWxsIGJlIGFwcHJvdmVkIGJ5IHRoZSBJVFUtVCkuIFRo
aXMgd291bGQgaW1wbHkgdGhhdCBkcmFmdC1iZXR0cy1pdHUtb2FtLWFjaC1jb2RlLXBvaW50IHNo
b3VsZCBjb250YWluIGEgbm9ybWF0aXZlIHJlZmVyZW5jZSB0byB0aGUgZmluYWwgYXBwcm92ZWQg
dmVyc2lvbiBvZiA4MTEzLjEuDQoNCkdpdmVuIG5vcm1hbCBJRVRGIHByb2Nlc3NlcywgdGhpcyBp
bXBsaWVzIHRoYXQgdGhlIGZpbmFsIFJGQyByZXN1bHRpbmcgZnJvbSBkcmFmdC1iZXR0cy1pdHUt
b2FtLWFjaC1jb2RlLXBvaW50IGNvdWxkIGJlIHB1Ymxpc2hlZCBhcyBzb29uIGFzIHRoZSBmaW5h
bCB2ZXJzaW9uIG9mIDgxMTMuMSBpcyBhcHByb3ZlZCAod2l0aCB0aGUgdW5kZXJzdGFuZGluZyB0
aGF0IHRoZXJlIHdpbGwgYmUgYSBzbWFsbCBub3JtYWwgZGVsYXkgYmV0d2VlbiAiYXBwcm92ZWQi
IGFuZCAicHVibGlzaGVkIiB3aGljaCBnaXZlcyB0aW1lIGZvciBjb29yZGluYXRpb24pLiBHaXZl
biB0aGF0IHRoZSBmaW5hbCB2ZXJzaW9uIG9mIDgxMTMuMSBtaWdodCBuZWVkIHRvIHJlZmVyZW5j
ZSB0aGUgUkZDIHJlc3VsdGluZyBmcm9tIGRyYWZ0LWJldHRzLWl0dS1vYW0tYWNoLWNvZGUtcG9p
bnQsIGEgYml0IG9mIGNvb3BlcmF0aW9uIG1pZ2h0IGJlIG5lZWRlZCBiZXR3ZWVuIGVkaXRvcmlh
bCBzdGFmZiBhdCB0aGUgSVRVIGFuZCBSRkMgZWRpdG9yaWFsIHN0YWZmLCBidXQgSSBkb24ndCBz
ZWUgd2h5IHRoaXMgc2hvdWxkIGJlIGEgcHJvYmxlbSAoSSBhbSBzdXJlIHRoYXQgdGhleSBhbGwg
aGF2ZSBhY2Nlc3MgdG8gZW1haWwpLg0KDQpSb3NzDQoNCi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0t
LS0tDQpGcm9tOiBpZXRmLWJvdW5jZXNAaWV0Zi5vcmcgW21haWx0bzppZXRmLWJvdW5jZXNAaWV0
Zi5vcmddIE9uIEJlaGFsZiBPZiBBbmRyZXcgRy4gTWFsaXMNClNlbnQ6IE1vbmRheSwgTWFyY2gg
MDUsIDIwMTIgNjo1NCBQTQ0KVG86IFNwcmVjaGVyLCBOdXJpdCAoTlNOIC0gSUwvSG9kIEhhU2hh
cm9uKQ0KQ2M6IGlldGZAaWV0Zi5vcmcNClN1YmplY3Q6IFJlOiBMYXN0IENhbGw6IDxkcmFmdC1i
ZXR0cy1pdHUtb2FtLWFjaC1jb2RlLXBvaW50LTAzLnR4dD4oQWxsb2NhdGlvbm9mDQphbiBBc3Nv
Y2lhdGVkIENoYW5uZWwgQ29kZSBQb2ludCBmb3IgVXNlIGJ5SVRVLVQgRXRoZXJuZXRiYXNlZCBP
QU0pIHRvIEluZm9ybWF0aW9uYWwgUkZDDQoNCkkgd291bGQgbGlrZSB0byBzdXBwb3J0IE51cml0
J3MgY29tbWVudHMgYmVsb3cuIEluIHBhcnRpY3VsYXIsIGluIHRoZSBwYXN0IHRoZSBJVFUtVCBo
YXMgZXhwYW5kZWQgdXBvbiBvciBjaGFuZ2VkIHRoZSB1c2FnZSBvZiBJRVRGIGNvZGVwb2ludCBh
bGxvY2F0aW9ucywgaW4gc29tZSBjYXNlcyBpbmNvbXBhdGlibHkgd2l0aCBpdHMgb3JpZ2luYWwg
dXNhZ2Ugb3IgZGVmaW5pdGlvbi4gSW4gdGhlIGZ1dHVyZSwgYWxsIGNvZGVwb2ludCBhbGxvY2F0
aW9ucyB0byB0aGUgSVRVLVQgc2hvdWxkIGJlIHRpZWQgdG8gb25lIHNwZWNpZmljLCBkYXRlZCBy
ZXZpc2lvbiBvZiB0aGVpciBzcGVjaWZpY2F0aW9uIG9ubHkuIFRoaXMgaXMgc2ltaWxhciB0byB0
aGUgSVRVLVQncyBvd24gcHJvY2Vzc2VzLCBzdWNoIGFzIHNlY3Rpb24gMi4yLjEgb2YgUmVjLiBB
LjUsIHdoaWNoIHJlcXVpcmVzIGEgdmVyc2lvbiBudW1iZXIgYW5kL29yIGRhdGUgZm9yIHJlZmVy
ZW5jZWQgb3V0c2lkZSBkb2N1bWVudHMgaW4gSVRVLVQgcmVjb21tZW5kYXRpb25zLg0KDQpDaGVl
cnMsDQpBbmR5DQoNCk9uIFRodSwgTWFyIDEsIDIwMTIgYXQgNzoyMCBBTSwgU3ByZWNoZXIsIE51
cml0IChOU04gLSBJTC9Ib2QNCkhhU2hhcm9uKSA8bnVyaXQuc3ByZWNoZXJAbnNuLmNvbT4gd3Jv
dGU6DQo+IEhpLA0KPg0KPg0KPg0KPiBJIGNhbm5vdCBzdXBwb3J0IHRoZSBwdWJsaWNhdGlvbiBv
ZiB0aGUgZG9jdW1lbnQgaW4gaXRzIGN1cnJlbnQgdmVyc2lvbi4NCj4NCj4NCj4NCj4gSSBoYXZl
IHRoZSBmb2xsb3dpbmcgY29uY2VybnM6DQo+DQo+DQo+DQo+IC4gICAgICAgIEl0IGlzIGluZGlj
YXRlZCB0aGF0IHRoZSBjaGFubmVsIGlzIGludGVuZGVkIHRvIGJlIHVzZWQgdG8gY2FycnkNCj4g
RXRoZXJuZXQgYmFzZWQgT0FNIG1lc3NhZ2VzLiBJdCBpcyBub3QgY2xlYXIgd2h5IHRoZXJlIGlz
IGEgbmVlZCBmb3IgQUNILg0KPiBQV3MgY2FuIGJlIHVzZWQgdG8gdHJhbnNtaXQgRXRoZXJuZXQg
T0FNLg0KPg0KPiBJZiB0aGUgaW50ZW50aW9uIGlzIHRvIHVzZSB0aGUgY2hhbm5lbCBmb3IgT0FN
IG1lc3NhZ2VzIGZvciBvcGVyYXRpbmcNCj4gTVBMUy1UUCBiYXNlZCBuZXR3b3JrcywgdGhlIElF
VEYgKmFscmVhZHkqIGRlZmluZWQgYSBzb2x1dGlvbiBmb3INCj4gTVBMUy1UUCBPQU0gYW5kIEkg
ZXhwZWN0IHRvIHNlZSBmaXJzdCBhIHRlY2huaWNhbCAqanVzdGlmaWNhdGlvbiogd2h5DQo+IGEg
c2Vjb25kIHNvbHV0aW9uIGlzIG5lZWRlZC4gSW4gYWRkaXRpb24sIEkgd291bGQgZXhwZWN0IHRv
IHNlZQ0KPiAqcmVmZXJlbmNlcyB0byB0aGUNCj4gYXJndW1lbnRzKiByYWlzZWQgaW4gZHJhZnQt
c3ByZWNoZXItbXBscy10cC1vYW0tY29uc2lkZXJhdGlvbnMuDQo+DQo+DQo+DQo+IC4gICAgICAg
IEl0IGlzIG5vdCBjbGVhciB3aGF0IHRoZSBtYXR1cml0eSBzdGF0dXMgb2YgRy44MTEzLjEgaXMu
IEl0IHNlZW1zDQo+IHRoYXQgdGhlIGRvY3VtZW50IHdhcyBub3QgYXBwcm92ZWQgYnkgU0cxNSBh
bmQgdGhlIGRpc2N1c3Npb24gd2FzDQo+IGRlZmVycmVkIHRvIFdUU0EuIFRoaXMgaW5kaWNhdGVz
IHRoYXQgdGhlcmUgaXMgKm5vIGNvbnNlbnN1cyogZm9yIHRoZQ0KPiBhcHByb3ZhbCBvZiBHLjgx
MTMuMS4gQSBjb2RlIHBvaW50IHNob3VsZCBub3QgYmUgYWxsb2NhdGVkIGJlZm9yZSBhDQo+IGNv
bnNlbnN1cy9kZWNpc2lvbiBpcyByZWFjaGVkIGluIHRoZSBJVFUtVCBhbmQgYmVmb3JlIHRoZSBk
b2N1bWVudCBpcw0KPiBtYXR1cmUgYW5kIGFwcHJvdmVkLiBJIGRvIG5vdCB0aGluayBpdCBpcyBh
cHByb3ByaWF0ZSB0byBhbGxvY2F0ZSBhDQo+IGNvZGUgcG9pbnQgYW5kIHRyeSB0byBmb3JjZSBh
IHJlc29sdXRpb24gaW4gdGhlIElUVS1ULg0KPg0KPg0KPg0KPiAuICAgICAgICBJIGZpbmQgYSBj
b250cmFkaWN0aW9uIGluIHRoZSBkcmFmdC4gSW4gb25lIHBsYWNlIGl0IGlzIG1lbnRpb25lZDoN
Cj4gIlRoZXNlIEV0aGVybmV0IGJhc2VkIE9BTSBtZXNzYWdlcyBhbmQgcHJvY2VkdXJlcywgYWRk
cmVzcyB0aGUgT0FNDQo+IGZ1bmN0aW9uYWwgcmVxdWlyZW1lbnRzIGRlZmluZWQgaW4gW1JGQzU4
NjBdLiBPdGhlciBtZXNzYWdlIHR5cGVzDQo+IHNob3VsZCBub3QgYmUgY2FycmllZCBiZWhpbmQg
dGhpcyBjb2RlIHBvaW50LiIgSW4gYW5vdGhlciBwbGFjZSBpdCBpcw0KPiBtZW50aW9uZWQ6ICJh
bGwgSVRVLVQgUmVjb21tZW5kYXRpb25zIGFyZSBzdWJqZWN0IHRvIHJldmlzaW9uLg0KPiBUaGVy
ZWZvcmUsIHRoZSBjb2RlIHBvaW50IGFsbG9jYXRlZCBieSB0aGlzIGRvY3VtZW50IG1heSBiZSB1
c2VkIGZvciBmdXR1cmUgdmVyc2lvbnMgb2YgW0cuODExMy4xXS4iLg0KPiBUaGUgbGFzdCBzdGF0
ZW1lbnQgb3BlbnMgdGhlIGRvb3IgZm9yIHRoZSBkZWZpbml0aW9uIG9mIGFkZGl0aW9uYWwNCj4g
bWVzc2FnZXMgaW4gRy44MTEzLjEgaW4gdGhlIGZvbGxvd2luZyB2ZXJzaW9ucywgZm9yIGV4YW1w
bGUsIGZvciBBUFMNCj4gKHN1cHBvcnRpbmcgbGluZWFyIG9yIHJpbmcgcHJvdGVjdGlvbiBtZWNo
YW5pc21zKSBhbmQgYnkgdGhpcyBjcmVhdGVzDQo+IHR3byBzb2x1dGlvbnMgZm9yIG90aGVyIG1l
Y2hhbmlzbXMgYXMgd2VsbC4NCj4NCj4NCj4NCj4gVGhlIHVzZSBvZiB0aGUgY29kZSBwb2ludCBj
YW4gZ28gbXVjaCBiZXlvbmQgaXRzIG9yaWdpbmFsIHB1cnBvc2UgYW5kDQo+IGl0IHdpbGwgaGlk
ZSBvdGhlciBtZXNzYWdlcy4uLi5hIGNvZGUgcG9pbnQgc2hvdWxkIG5vdCBiZSBhbGxvY2F0ZWQg
YXQNCj4gdGhpcyBwb2ludCBhdCBhbGwsIGJ1dCBzcGVjaWZpY2FsbHkgbm90IGZvciB1bmtub3du
IHVzYWdlIHRoYXQgbWF5IGJlDQo+IGRlZmluZWQgaW4gZnV0dXJlIHZlcnNpb25zIG9mIEcuODEx
My4xLg0KPg0KPg0KPg0KPiBCZXN0IHJlZ2FyZHMsDQo+DQo+IE51cml0DQo+DQo+DQo+DQo+DQo+
DQo+DQo+DQo+PiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPg0KPj4gRnJvbTogaWV0Zi1h
bm5vdW5jZS1ib3VuY2VzQGlldGYub3JnIFttYWlsdG86aWV0Zi1hbm5vdW5jZS0NCj4NCj4+IGJv
dW5jZXNAaWV0Zi5vcmddIE9uIEJlaGFsZiBPZiBUaGUgSUVTRw0KPg0KPj4gU2VudDogMjIgRmVi
cnVhcnkgMjAxMiAxNToxMw0KPg0KPj4gVG86IElFVEYtQW5ub3VuY2UNCj4NCj4+IFN1YmplY3Q6
IExhc3QgQ2FsbDogPGRyYWZ0LWJldHRzLWl0dS1vYW0tYWNoLWNvZGUtcG9pbnQtMDMudHh0Pg0K
Pg0KPiAoQWxsb2NhdGlvbiBvZg0KPg0KPiBhbg0KPg0KPj4gQXNzb2NpYXRlZCBDaGFubmVsIENv
ZGUgUG9pbnQgZm9yIFVzZSBieSBJVFUtVCBFdGhlcm5ldCBiYXNlZCBPQU0pIHRvDQo+DQo+PiBJ
bmZvcm1hdGlvbmFsIFJGQw0KPg0KPj4NCj4NCj4+DQo+DQo+PiBUaGUgSUVTRyBoYXMgcmVjZWl2
ZWQgYSByZXF1ZXN0IGZyb20gYW4gaW5kaXZpZHVhbCBzdWJtaXR0ZXIgdG8NCj4NCj4gY29uc2lk
ZXINCj4NCj4+IHRoZSBmb2xsb3dpbmcgZG9jdW1lbnQ6DQo+DQo+PiAtICdBbGxvY2F0aW9uIG9m
IGFuIEFzc29jaWF0ZWQgQ2hhbm5lbCBDb2RlIFBvaW50IGZvciBVc2UgYnkgSVRVLVQNCj4NCj4+
ICAgIEV0aGVybmV0IGJhc2VkIE9BTScNCj4NCj4+ICAgPGRyYWZ0LWJldHRzLWl0dS1vYW0tYWNo
LWNvZGUtcG9pbnQtMDMudHh0PiBhcyBhbiBJbmZvcm1hdGlvbmFsIFJGQw0KPg0KPj4NCj4NCj4+
IFRoZSBJRVNHIHBsYW5zIHRvIG1ha2UgYSBkZWNpc2lvbiBpbiB0aGUgbmV4dCBmZXcgd2Vla3Ms
IGFuZCBzb2xpY2l0cw0KPg0KPj4gZmluYWwgY29tbWVudHMgb24gdGhpcyBhY3Rpb24uIFBsZWFz
ZSBzZW5kIHN1YnN0YW50aXZlIGNvbW1lbnRzIHRvDQo+PiB0aGUNCj4NCj4+IGlldGZAaWV0Zi5v
cmcgbWFpbGluZyBsaXN0cyBieSAyMDEyLTAzLTIxLiBFeGNlcHRpb25hbGx5LCBjb21tZW50cw0K
Pj4gbWF5DQo+DQo+IGJlDQo+DQo+PiBzZW50IHRvIGllc2dAaWV0Zi5vcmcgaW5zdGVhZC4gSW4g
ZWl0aGVyIGNhc2UsIHBsZWFzZSByZXRhaW4gdGhlDQo+DQo+PiBiZWdpbm5pbmcgb2YgdGhlIFN1
YmplY3QgbGluZSB0byBhbGxvdyBhdXRvbWF0ZWQgc29ydGluZy4NCj4NCj4+DQo+DQo+PiBBYnN0
cmFjdA0KPg0KPj4NCj4NCj4+ICAgIFRoaXMgZG9jdW1lbnQgYXNzaWducyBhbiBBc3NvY2lhdGVk
IENoYW5uZWwgVHlwZSBjb2RlIHBvaW50IGZvcg0KPg0KPj4gICAgY2FycnlpbmcgRXRoZXJuZXQg
YmFzZWQgT3BlcmF0aW9ucywgQWRtaW5pc3RyYXRpb24sIGFuZCBNYW5hZ2VtZW50DQo+DQo+PiAg
ICBtZXNzYWdlcyBpbiB0aGUgTVBMUyBHZW5lcmljIEFzc29jaWF0ZWQgQ2hhbm5lbCAoRy1BQ2gp
Lg0KPg0KPj4NCj4NCj4+IFRoZSBmaWxlIGNhbiBiZSBvYnRhaW5lZCB2aWENCj4NCj4+IGh0dHA6
Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9kb2MvZHJhZnQtYmV0dHMtaXR1LW9hbS1hY2gtY29kZS1w
b2ludC8NCj4NCj4+DQo+DQo+PiBJRVNHIGRpc2N1c3Npb24gY2FuIGJlIHRyYWNrZWQgdmlhDQo+
DQo+PiBodHRwOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0LWJldHRzLWl0dS1vYW0t
YWNoLWNvZGUtcG9pbnQvDQo+DQo+Pg0KPg0KPj4NCj4NCj4+IE5vIElQUiBkZWNsYXJhdGlvbnMg
aGF2ZSBiZWVuIHN1Ym1pdHRlZCBkaXJlY3RseSBvbiB0aGlzIEktRC4NCj4NCj4+IF9fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+DQo+PiBJRVRGLUFubm91
bmNlIG1haWxpbmcgbGlzdA0KPg0KPj4gSUVURi1Bbm5vdW5jZUBpZXRmLm9yZw0KPg0KPj4gaHR0
cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9pZXRmLWFubm91bmNlDQo+DQo+DQo+
DQo+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+DQo+
IG1wbHMgbWFpbGluZyBsaXN0DQo+DQo+IG1wbHNAaWV0Zi5vcmcNCj4NCj4gaHR0cHM6Ly93d3cu
aWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9tcGxzDQo+DQo+IF9fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+DQo+IElldGYgbWFpbGluZyBsaXN0DQo+DQo+
IElldGZAaWV0Zi5vcmcNCj4NCj4gaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5m
by9pZXRmDQo+DQo+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fDQo+DQo+IElldGYgbWFpbGluZyBsaXN0DQo+DQo+IElldGZAaWV0Zi5vcmcNCj4NCj4gaHR0
cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9pZXRmDQo+DQo+DQo+IF9fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+IElldGYgbWFpbGluZyBs
aXN0DQo+IElldGZAaWV0Zi5vcmcNCj4gaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0
aW5mby9pZXRmDQo+DQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fXw0KSWV0ZiBtYWlsaW5nIGxpc3QNCklldGZAaWV0Zi5vcmcNCmh0dHBzOi8vd3d3LmlldGYu
b3JnL21haWxtYW4vbGlzdGluZm8vaWV0Zg0KDQoNCg0KLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0N
Cg0KDQo+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+
IElldGYgbWFpbGluZyBsaXN0DQo+IElldGZAaWV0Zi5vcmcNCj4gaHR0cHM6Ly93d3cuaWV0Zi5v
cmcvbWFpbG1hbi9saXN0aW5mby9pZXRmDQo+DQoNCg0KDQpRdWVzdG8gbWVzc2FnZ2lvIGUgaSBz
dW9pIGFsbGVnYXRpIHNvbm8gaW5kaXJpenphdGkgZXNjbHVzaXZhbWVudGUgYWxsZSBwZXJzb25l
IGluZGljYXRlLiBMYSBkaWZmdXNpb25lLCBjb3BpYSBvIHF1YWxzaWFzaSBhbHRyYSBhemlvbmUg
ZGVyaXZhbnRlIGRhbGxhIGNvbm9zY2VuemEgZGkgcXVlc3RlIGluZm9ybWF6aW9uaSBzb25vIHJp
Z29yb3NhbWVudGUgdmlldGF0ZS4gUXVhbG9yYSBhYmJpYXRlIHJpY2V2dXRvIHF1ZXN0byBkb2N1
bWVudG8gcGVyIGVycm9yZSBzaWV0ZSBjb3J0ZXNlbWVudGUgcHJlZ2F0aSBkaSBkYXJuZSBpbW1l
ZGlhdGEgY29tdW5pY2F6aW9uZSBhbCBtaXR0ZW50ZSBlIGRpIHByb3Z2ZWRlcmUgYWxsYSBzdWEg
ZGlzdHJ1emlvbmUsIEdyYXppZS4NCg0KVGhpcyBlLW1haWwgYW5kIGFueSBhdHRhY2htZW50cyBp
cyBjb25maWRlbnRpYWwgYW5kIG1heSBjb250YWluIHByaXZpbGVnZWQgaW5mb3JtYXRpb24gaW50
ZW5kZWQgZm9yIHRoZSBhZGRyZXNzZWUocykgb25seS4gRGlzc2VtaW5hdGlvbiwgY29weWluZywg
cHJpbnRpbmcgb3IgdXNlIGJ5IGFueWJvZHkgZWxzZSBpcyB1bmF1dGhvcmlzZWQuIElmIHlvdSBh
cmUgbm90IHRoZSBpbnRlbmRlZCByZWNpcGllbnQsIHBsZWFzZSBkZWxldGUgdGhpcyBtZXNzYWdl
IGFuZCBhbnkgYXR0YWNobWVudHMgYW5kIGFkdmlzZSB0aGUgc2VuZGVyIGJ5IHJldHVybiBlLW1h
aWwsIFRoYW5rcy4NCg0K

From alessandro.dalessandro@telecomitalia.it  Wed Mar 21 08:13:23 2012
Return-Path: <alessandro.dalessandro@telecomitalia.it>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 56C8B21F872F for <ietf@ietfa.amsl.com>; Wed, 21 Mar 2012 08:13:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.977
X-Spam-Level: 
X-Spam-Status: No, score=-0.977 tagged_above=-999 required=5 tests=[AWL=0.142,  BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, J_CHICKENPOX_15=0.6, 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 8G4rWf1PCw6s for <ietf@ietfa.amsl.com>; Wed, 21 Mar 2012 08:13:22 -0700 (PDT)
Received: from GRFEDG701RM001.telecomitalia.it (grfedg701rm001.telecomitalia.it [217.169.121.20]) by ietfa.amsl.com (Postfix) with ESMTP id A833721F872B for <ietf@ietf.org>; Wed, 21 Mar 2012 08:13:21 -0700 (PDT)
Received: from grfhub701rm001.griffon.local (10.19.3.8) by GRFEDG701RM001.telecomitalia.it (10.173.88.20) with Microsoft SMTP Server (TLS) id 8.2.254.0; Wed, 21 Mar 2012 16:13:19 +0100
Received: from GRFMBX702RM001.griffon.local ([10.19.3.20]) by grfhub701rm001.griffon.local ([10.19.9.234]) with mapi; Wed, 21 Mar 2012 16:12:50 +0100
From: D'Alessandro Alessandro Gerardo <alessandro.dalessandro@telecomitalia.it>
To: "ietf@ietf.org" <ietf@ietf.org>
Date: Wed, 21 Mar 2012 16:11:49 +0100
Subject: RE: Last Call:<draft-betts-itu-oam-ach-code-point-03.txt>(Allocationof	an Associated Channel Code Point for Use byITU-T Ethernetbased OAM) to	Informational RFC
Thread-Topic: Last Call:<draft-betts-itu-oam-ach-code-point-03.txt>(Allocationof	an Associated Channel Code Point for Use byITU-T Ethernetbased OAM) to	Informational RFC
Thread-Index: Ac0HdLufGyIpL3HPTom7mYWDtDPeQA==
Message-ID: <A1F769BC58A8B146B2EEA818EAE052A2097389D6B7@GRFMBX702RM001.griffon.local>
Accept-Language: en-US, it-IT
Content-Language: it-IT
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, it-IT
x-ti-disclaimer: Disclaimer1
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: Wed, 21 Mar 2012 15:13:23 -0000

RGVhciBhbGwsDQpXcnQgZHJhZnQtYmV0dHMsIEkgYmVsaWV2ZSBpdCBpcyBhcHByb3ByaWF0ZSB0
byBhbGxvY2F0ZSBhIGNvZGUgcG9pbnQgZm9yIHRoZSByZWZlcmVuY2VkIHNwZWNpZmljYXRpb24g
d2l0aG91dCBhbnkgcmVzdHJpY3Rpb24gYWJvdXQgdGhlIHBvc3NpYmlsaXR5IHRvIGV2b2x2ZSBt
ZXNzYWdlcy9wcm90b2NvbHMgd2hlbiBjb21wYXRpYmlsaXR5IGlzIHByZXNlcnZlZC4gSXQgaXMg
bm90IG9ubHkgdW5uZWNlc3NhcnkgYnV0IGl0IGRvZXMgbm90IGhlbHAgaW4gaW1wcm92aW5nIHRo
ZSByZWxhdGlvbnNoaXAgYmV0d2VlbiB0aGUgdHdvIFNET3MuDQoNCkJlc3QgcmVnYXJkcywNCkFs
ZXNzYW5kcm8NCg0KUFMgUmVzZW50IGR1ZSB0byBtYWxmb3JtZWQgc3ViamVjdA0KLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
DQpUZWxlY29tIEl0YWxpYQ0KQWxlc3NhbmRybyBHZXJhcmRvIEQnQWxlc3NhbmRybw0KVHJhbnNw
b3J0IElubm92YXRpb24NClZpYSBSZWlzcyBSb21vbGksIDI3NCAtIDEwMTQ4IFRvcmlubw0KcGhv
bmU6ICArMzkgMDExIDIyOCA1ODg3DQptb2JpbGU6ICszOSAzMzUgNzY2IDk2MDcNCmZheDogKzM5
IDA2IDQxOCA2MzkgMDcNCg0KDQotLS0tLU1lc3NhZ2dpbyBvcmlnaW5hbGUtLS0tLQ0KRGE6IHQu
cGV0Y2ggW21haWx0bzpkYWVkdWx1c0BidGNvbm5lY3QuY29tXQ0KSW52aWF0bzogbWVyY29sZWTD
rCAxNCBtYXJ6byAyMDEyIDExOjU2DQpBOiBTcHJlY2hlciwgTnVyaXQgKE5TTiAtIElML0hvZCBI
YVNoYXJvbik7IGV4dCBSb3NzIENhbGxvbg0KQ2M6IGlldGZAaWV0Zi5vcmcNCk9nZ2V0dG86IFJl
OiDXlNeg15PXldefOiBSRTogTGFzdCBDYWxsOjxkcmFmdC1iZXR0cy1pdHUtb2FtLWFjaC1jb2Rl
LXBvaW50LTAzLnR4dD4oQWxsb2NhdGlvbm9mIGFuIEFzc29jaWF0ZWQgQ2hhbm5lbCBDb2RlIFBv
aW50IGZvciBVc2UgYnlJVFUtVCBFdGhlcm5ldGJhc2VkIE9BTSkgdG8gSW5mb3JtYXRpb25hbCBS
RkMNCg0KLS0tLS0gT3JpZ2luYWwgTWVzc2FnZSAtLS0tLQ0KRnJvbTogIlNwcmVjaGVyLCBOdXJp
dCAoTlNOIC0gSUwvSG9kIEhhU2hhcm9uKSIgPG51cml0LnNwcmVjaGVyQG5zbi5jb20+DQpUbzog
IkFuZHJldyBHLiBNYWxpcyIgPGFnbWFsaXNAZ21haWwuY29tPjsgImV4dCBSb3NzIENhbGxvbiIN
CjxyY2FsbG9uQGp1bmlwZXIubmV0Pg0KQ2M6IDxpZXRmQGlldGYub3JnPg0KU2VudDogVHVlc2Rh
eSwgTWFyY2ggMTMsIDIwMTIgODowOSBQTQ0KU3ViamVjdDog15TXoNeT15XXnzogUkU6IExhc3QN
CkNhbGw6PGRyYWZ0LWJldHRzLWl0dS1vYW0tYWNoLWNvZGUtcG9pbnQtMDMudHh0PihBbGxvY2F0
aW9ub2YgYW4gQXNzb2NpYXRlZCBDaGFubmVsIENvZGUgUG9pbnQgZm9yIFVzZSBieUlUVS1UIEV0
aGVybmV0YmFzZWQgT0FNKSB0byBJbmZvcm1hdGlvbmFsIFJGQw0KDQoNClJvc3MsDQppIGFtIGFm
cmFpZCB0aGF0IHlvdSBtaXNzZWQgdGhlIHBvaW50LiBUaGVyZSB3aWxsIG5vdCBiZSBhIGZpbmFs
IHZlcnNpb24gc2luY2UgYXMgd3JpdHRlbiBpbiBkcmFmdC1iZXR0cywgYWxsICBJVFUgcmVjb21t
ZW5kYXRpb25zIGFyZSBzdWJqZWN0IHRvIHJldmlzaW9ucywgYW5kIHRoZSBjb2RlIHBvaW50IHdp
bGwgYWxzbyBiZSB1c2VkIGZvciBmdXR1cmUgcmV2aXNpb25zIG9mIHRoZSBkb2N1bWVudC4gTmV3
IG1lc3NhZ2VzL3Byb3RvY29scyBjYW4gYmUgZGVmaW5lZCBpbiBmdXR1cmUgcmV2aXNpb25zIG9m
IHRoZSByZWNvbW1lbmRhdGlvbiBhbmQgdGhleSB3aWxsIHVzZSB0aGUgc2FtZSBjb2RlIHBvaW50
IHRoYXQgaXMgYWxsb2NhdGVkIGZvciB0aGUgZmlyc3QgdmVyc2lvbi4NClRoaXMgaXMgYSByZWFs
IGlzc3VlLg0KUmVnYXJkcywNCk51cml0DQotLS0tLdeU15XXk9ei15Qg157Xp9eV16jXmdeqLS0t
LS0NCtee15DXqjogZXh0IFJvc3MgQ2FsbG9uDQrXoNep15zXlzogIDEzLzAzLzIwMTIsIDE5OjI3
DQrXkNecOiBBbmRyZXcgRy4gTWFsaXM7IFNwcmVjaGVyLCBOdXJpdCAoTlNOIC0gSUwvSG9kIEhh
U2hhcm9uKQ0K16LXldeq16c6IGlldGZAaWV0Zi5vcmcNCteg15XXqdeQOiBSRTogTGFzdCBDYWxs
OjxkcmFmdC1iZXR0cy1pdHUtb2FtLWFjaC1jb2RlLXBvaW50LTAzLnR4dD4oQWxsb2NhdGlvbm9m
IGFuIEFzc29jaWF0ZWQgQ2hhbm5lbCBDb2RlIFBvaW50IGZvciBVc2UgYnlJVFUtVCBFdGhlcm5l
dGJhc2VkIE9BTSkgdG8gSW5mb3JtYXRpb25hbCBSRkMgSSBhZ3JlZSB0aGF0IHRoZSBhbGxvY2F0
aW9uIG9mIGEgY29kZSBwb2ludCBzaG91bGQgYmUgdG8gYSBzcGVjaWZpYyB2ZXJzaW9uIG9mIDgx
MTMuMSwNCg0KPHRwPg0KV2h5Pw0KDQpJIGNhbiB1bmRlcnN0YW5kIGEgbmV3IGNvZGUgcG9pbnQg
YmVpbmcgcmVxdWlyZWQgaWYgdGhlcmUgaXMgYSBuZXcgYW5kIGJhY2t3YXJkcyBpbmNvbXBhdGli
bGUgZm9ybWF0IGZvciB0aGUgbWVzc2FnZXMsIGJ1dCBpZiB0aGUgbWVzc2FnZXMgYXJlIGV4dGVu
ZGVkIGluIGEgZm9yd2FyZHMgY29tcGF0aWJsZSBtYW5uZXIsIGFkZGluZyBuZXcgVExWIGZvciBl
eGFtcGxlLCBvciBhIG5ldyBmb3JtYXQgb2YgSUZfSUQsIHRoZW4gd2h5IHNob3VsZCB3ZSBidXJu
IGEgbmV3IGNvZGUgcG9pbnQ/DQoNCldvdWxkIHlvdSBzYXkgdGhhdCB3ZSBzaG91bGQgaGF2ZSBh
IGRvemVuIGRpZmZlcmVudCBwb3J0IG51bWJlcnMgZm9yIEhUVFAgdG8gcmVmbGVjdCBpdHMgZXZv
bHV0aW9uIG92ZXIgdGltZT8gIElmIG5vdCwgd2h5IG5vdD8NCg0KRGVtYW5kaW5nIHRoYXQgdGhl
IElUVS1UIGNvbWUgYmFjayB0byB1cyBmb3IgYSBuZXcgcm91bmQgb2YgbmVnb3RpYXRpb24gd2hl
biBpdCBpcyB0ZWNobmljYWxseSB1bm5lY2Vzc2FyeSBzZWVtcyB0byBiZSBwbGFjaW5nIGFuIHVu
bmVjZXNzYXJ5IGJhcnJpZXIgYmV0d2VlbiB0aGUgdHdvIFNET3MuDQoNClRvbSBQZXRjaA0KDQph
bmQgc3BlY2lmaWNhbGx5IHNob3VsZCBiZSB0byB0aGUgZmluYWwgdmVyc2lvbiB0aGF0IGlzIGFw
cHJvdmVkIGJ5IHRoZSBJVFUtVCAoYXNzdW1pbmcgdGhhdCBhIGZpbmFsIHZlcnNpb24gb2YgODEx
My4xIHdpbGwgYmUgYXBwcm92ZWQgYnkgdGhlIElUVS1UKS4gVGhpcyB3b3VsZCBpbXBseSB0aGF0
IGRyYWZ0LWJldHRzLWl0dS1vYW0tYWNoLWNvZGUtcG9pbnQgc2hvdWxkIGNvbnRhaW4gYSBub3Jt
YXRpdmUgcmVmZXJlbmNlIHRvIHRoZSBmaW5hbCBhcHByb3ZlZCB2ZXJzaW9uIG9mIDgxMTMuMS4N
Cg0KR2l2ZW4gbm9ybWFsIElFVEYgcHJvY2Vzc2VzLCB0aGlzIGltcGxpZXMgdGhhdCB0aGUgZmlu
YWwgUkZDIHJlc3VsdGluZyBmcm9tIGRyYWZ0LWJldHRzLWl0dS1vYW0tYWNoLWNvZGUtcG9pbnQg
Y291bGQgYmUgcHVibGlzaGVkIGFzIHNvb24gYXMgdGhlIGZpbmFsIHZlcnNpb24gb2YgODExMy4x
IGlzIGFwcHJvdmVkICh3aXRoIHRoZSB1bmRlcnN0YW5kaW5nIHRoYXQgdGhlcmUgd2lsbCBiZSBh
IHNtYWxsIG5vcm1hbCBkZWxheSBiZXR3ZWVuICJhcHByb3ZlZCIgYW5kICJwdWJsaXNoZWQiIHdo
aWNoIGdpdmVzIHRpbWUgZm9yIGNvb3JkaW5hdGlvbikuIEdpdmVuIHRoYXQgdGhlIGZpbmFsIHZl
cnNpb24gb2YgODExMy4xIG1pZ2h0IG5lZWQgdG8gcmVmZXJlbmNlIHRoZSBSRkMgcmVzdWx0aW5n
IGZyb20gZHJhZnQtYmV0dHMtaXR1LW9hbS1hY2gtY29kZS1wb2ludCwgYSBiaXQgb2YgY29vcGVy
YXRpb24gbWlnaHQgYmUgbmVlZGVkIGJldHdlZW4gZWRpdG9yaWFsIHN0YWZmIGF0IHRoZSBJVFUg
YW5kIFJGQyBlZGl0b3JpYWwgc3RhZmYsIGJ1dCBJIGRvbid0IHNlZSB3aHkgdGhpcyBzaG91bGQg
YmUgYSBwcm9ibGVtIChJIGFtIHN1cmUgdGhhdCB0aGV5IGFsbCBoYXZlIGFjY2VzcyB0byBlbWFp
bCkuDQoNClJvc3MNCg0KLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCkZyb206IGlldGYtYm91
bmNlc0BpZXRmLm9yZyBbbWFpbHRvOmlldGYtYm91bmNlc0BpZXRmLm9yZ10gT24gQmVoYWxmIE9m
IEFuZHJldyBHLiBNYWxpcw0KU2VudDogTW9uZGF5LCBNYXJjaCAwNSwgMjAxMiA2OjU0IFBNDQpU
bzogU3ByZWNoZXIsIE51cml0IChOU04gLSBJTC9Ib2QgSGFTaGFyb24pDQpDYzogaWV0ZkBpZXRm
Lm9yZw0KU3ViamVjdDogUmU6IExhc3QgQ2FsbDogPGRyYWZ0LWJldHRzLWl0dS1vYW0tYWNoLWNv
ZGUtcG9pbnQtMDMudHh0PihBbGxvY2F0aW9ub2YNCmFuIEFzc29jaWF0ZWQgQ2hhbm5lbCBDb2Rl
IFBvaW50IGZvciBVc2UgYnlJVFUtVCBFdGhlcm5ldGJhc2VkIE9BTSkgdG8gSW5mb3JtYXRpb25h
bCBSRkMNCg0KSSB3b3VsZCBsaWtlIHRvIHN1cHBvcnQgTnVyaXQncyBjb21tZW50cyBiZWxvdy4g
SW4gcGFydGljdWxhciwgaW4gdGhlIHBhc3QgdGhlIElUVS1UIGhhcyBleHBhbmRlZCB1cG9uIG9y
IGNoYW5nZWQgdGhlIHVzYWdlIG9mIElFVEYgY29kZXBvaW50IGFsbG9jYXRpb25zLCBpbiBzb21l
IGNhc2VzIGluY29tcGF0aWJseSB3aXRoIGl0cyBvcmlnaW5hbCB1c2FnZSBvciBkZWZpbml0aW9u
LiBJbiB0aGUgZnV0dXJlLCBhbGwgY29kZXBvaW50IGFsbG9jYXRpb25zIHRvIHRoZSBJVFUtVCBz
aG91bGQgYmUgdGllZCB0byBvbmUgc3BlY2lmaWMsIGRhdGVkIHJldmlzaW9uIG9mIHRoZWlyIHNw
ZWNpZmljYXRpb24gb25seS4gVGhpcyBpcyBzaW1pbGFyIHRvIHRoZSBJVFUtVCdzIG93biBwcm9j
ZXNzZXMsIHN1Y2ggYXMgc2VjdGlvbiAyLjIuMSBvZiBSZWMuIEEuNSwgd2hpY2ggcmVxdWlyZXMg
YSB2ZXJzaW9uIG51bWJlciBhbmQvb3IgZGF0ZSBmb3IgcmVmZXJlbmNlZCBvdXRzaWRlIGRvY3Vt
ZW50cyBpbiBJVFUtVCByZWNvbW1lbmRhdGlvbnMuDQoNCkNoZWVycywNCkFuZHkNCg0KT24gVGh1
LCBNYXIgMSwgMjAxMiBhdCA3OjIwIEFNLCBTcHJlY2hlciwgTnVyaXQgKE5TTiAtIElML0hvZA0K
SGFTaGFyb24pIDxudXJpdC5zcHJlY2hlckBuc24uY29tPiB3cm90ZToNCj4gSGksDQo+DQo+DQo+
DQo+IEkgY2Fubm90IHN1cHBvcnQgdGhlIHB1YmxpY2F0aW9uIG9mIHRoZSBkb2N1bWVudCBpbiBp
dHMgY3VycmVudCB2ZXJzaW9uLg0KPg0KPg0KPg0KPiBJIGhhdmUgdGhlIGZvbGxvd2luZyBjb25j
ZXJuczoNCj4NCj4NCj4NCj4gLiAgICAgICAgSXQgaXMgaW5kaWNhdGVkIHRoYXQgdGhlIGNoYW5u
ZWwgaXMgaW50ZW5kZWQgdG8gYmUgdXNlZCB0byBjYXJyeQ0KPiBFdGhlcm5ldCBiYXNlZCBPQU0g
bWVzc2FnZXMuIEl0IGlzIG5vdCBjbGVhciB3aHkgdGhlcmUgaXMgYSBuZWVkIGZvciBBQ0guDQo+
IFBXcyBjYW4gYmUgdXNlZCB0byB0cmFuc21pdCBFdGhlcm5ldCBPQU0uDQo+DQo+IElmIHRoZSBp
bnRlbnRpb24gaXMgdG8gdXNlIHRoZSBjaGFubmVsIGZvciBPQU0gbWVzc2FnZXMgZm9yIG9wZXJh
dGluZw0KPiBNUExTLVRQIGJhc2VkIG5ldHdvcmtzLCB0aGUgSUVURiAqYWxyZWFkeSogZGVmaW5l
ZCBhIHNvbHV0aW9uIGZvcg0KPiBNUExTLVRQIE9BTSBhbmQgSSBleHBlY3QgdG8gc2VlIGZpcnN0
IGEgdGVjaG5pY2FsICpqdXN0aWZpY2F0aW9uKiB3aHkNCj4gYSBzZWNvbmQgc29sdXRpb24gaXMg
bmVlZGVkLiBJbiBhZGRpdGlvbiwgSSB3b3VsZCBleHBlY3QgdG8gc2VlDQo+ICpyZWZlcmVuY2Vz
IHRvIHRoZQ0KPiBhcmd1bWVudHMqIHJhaXNlZCBpbiBkcmFmdC1zcHJlY2hlci1tcGxzLXRwLW9h
bS1jb25zaWRlcmF0aW9ucy4NCj4NCj4NCj4NCj4gLiAgICAgICAgSXQgaXMgbm90IGNsZWFyIHdo
YXQgdGhlIG1hdHVyaXR5IHN0YXR1cyBvZiBHLjgxMTMuMSBpcy4gSXQgc2VlbXMNCj4gdGhhdCB0
aGUgZG9jdW1lbnQgd2FzIG5vdCBhcHByb3ZlZCBieSBTRzE1IGFuZCB0aGUgZGlzY3Vzc2lvbiB3
YXMNCj4gZGVmZXJyZWQgdG8gV1RTQS4gVGhpcyBpbmRpY2F0ZXMgdGhhdCB0aGVyZSBpcyAqbm8g
Y29uc2Vuc3VzKiBmb3IgdGhlDQo+IGFwcHJvdmFsIG9mIEcuODExMy4xLiBBIGNvZGUgcG9pbnQg
c2hvdWxkIG5vdCBiZSBhbGxvY2F0ZWQgYmVmb3JlIGENCj4gY29uc2Vuc3VzL2RlY2lzaW9uIGlz
IHJlYWNoZWQgaW4gdGhlIElUVS1UIGFuZCBiZWZvcmUgdGhlIGRvY3VtZW50IGlzDQo+IG1hdHVy
ZSBhbmQgYXBwcm92ZWQuIEkgZG8gbm90IHRoaW5rIGl0IGlzIGFwcHJvcHJpYXRlIHRvIGFsbG9j
YXRlIGENCj4gY29kZSBwb2ludCBhbmQgdHJ5IHRvIGZvcmNlIGEgcmVzb2x1dGlvbiBpbiB0aGUg
SVRVLVQuDQo+DQo+DQo+DQo+IC4gICAgICAgIEkgZmluZCBhIGNvbnRyYWRpY3Rpb24gaW4gdGhl
IGRyYWZ0LiBJbiBvbmUgcGxhY2UgaXQgaXMgbWVudGlvbmVkOg0KPiAiVGhlc2UgRXRoZXJuZXQg
YmFzZWQgT0FNIG1lc3NhZ2VzIGFuZCBwcm9jZWR1cmVzLCBhZGRyZXNzIHRoZSBPQU0NCj4gZnVu
Y3Rpb25hbCByZXF1aXJlbWVudHMgZGVmaW5lZCBpbiBbUkZDNTg2MF0uIE90aGVyIG1lc3NhZ2Ug
dHlwZXMNCj4gc2hvdWxkIG5vdCBiZSBjYXJyaWVkIGJlaGluZCB0aGlzIGNvZGUgcG9pbnQuIiBJ
biBhbm90aGVyIHBsYWNlIGl0IGlzDQo+IG1lbnRpb25lZDogImFsbCBJVFUtVCBSZWNvbW1lbmRh
dGlvbnMgYXJlIHN1YmplY3QgdG8gcmV2aXNpb24uDQo+IFRoZXJlZm9yZSwgdGhlIGNvZGUgcG9p
bnQgYWxsb2NhdGVkIGJ5IHRoaXMgZG9jdW1lbnQgbWF5IGJlIHVzZWQgZm9yIGZ1dHVyZSB2ZXJz
aW9ucyBvZiBbRy44MTEzLjFdLiIuDQo+IFRoZSBsYXN0IHN0YXRlbWVudCBvcGVucyB0aGUgZG9v
ciBmb3IgdGhlIGRlZmluaXRpb24gb2YgYWRkaXRpb25hbA0KPiBtZXNzYWdlcyBpbiBHLjgxMTMu
MSBpbiB0aGUgZm9sbG93aW5nIHZlcnNpb25zLCBmb3IgZXhhbXBsZSwgZm9yIEFQUw0KPiAoc3Vw
cG9ydGluZyBsaW5lYXIgb3IgcmluZyBwcm90ZWN0aW9uIG1lY2hhbmlzbXMpIGFuZCBieSB0aGlz
IGNyZWF0ZXMNCj4gdHdvIHNvbHV0aW9ucyBmb3Igb3RoZXIgbWVjaGFuaXNtcyBhcyB3ZWxsLg0K
Pg0KPg0KPg0KPiBUaGUgdXNlIG9mIHRoZSBjb2RlIHBvaW50IGNhbiBnbyBtdWNoIGJleW9uZCBp
dHMgb3JpZ2luYWwgcHVycG9zZSBhbmQNCj4gaXQgd2lsbCBoaWRlIG90aGVyIG1lc3NhZ2VzLi4u
LmEgY29kZSBwb2ludCBzaG91bGQgbm90IGJlIGFsbG9jYXRlZCBhdA0KPiB0aGlzIHBvaW50IGF0
IGFsbCwgYnV0IHNwZWNpZmljYWxseSBub3QgZm9yIHVua25vd24gdXNhZ2UgdGhhdCBtYXkgYmUN
Cj4gZGVmaW5lZCBpbiBmdXR1cmUgdmVyc2lvbnMgb2YgRy44MTEzLjEuDQo+DQo+DQo+DQo+IEJl
c3QgcmVnYXJkcywNCj4NCj4gTnVyaXQNCj4NCj4NCj4NCj4NCj4NCj4NCj4NCj4+IC0tLS0tT3Jp
Z2luYWwgTWVzc2FnZS0tLS0tDQo+DQo+PiBGcm9tOiBpZXRmLWFubm91bmNlLWJvdW5jZXNAaWV0
Zi5vcmcgW21haWx0bzppZXRmLWFubm91bmNlLQ0KPg0KPj4gYm91bmNlc0BpZXRmLm9yZ10gT24g
QmVoYWxmIE9mIFRoZSBJRVNHDQo+DQo+PiBTZW50OiAyMiBGZWJydWFyeSAyMDEyIDE1OjEzDQo+
DQo+PiBUbzogSUVURi1Bbm5vdW5jZQ0KPg0KPj4gU3ViamVjdDogTGFzdCBDYWxsOiA8ZHJhZnQt
YmV0dHMtaXR1LW9hbS1hY2gtY29kZS1wb2ludC0wMy50eHQ+DQo+DQo+IChBbGxvY2F0aW9uIG9m
DQo+DQo+IGFuDQo+DQo+PiBBc3NvY2lhdGVkIENoYW5uZWwgQ29kZSBQb2ludCBmb3IgVXNlIGJ5
IElUVS1UIEV0aGVybmV0IGJhc2VkIE9BTSkgdG8NCj4NCj4+IEluZm9ybWF0aW9uYWwgUkZDDQo+
DQo+Pg0KPg0KPj4NCj4NCj4+IFRoZSBJRVNHIGhhcyByZWNlaXZlZCBhIHJlcXVlc3QgZnJvbSBh
biBpbmRpdmlkdWFsIHN1Ym1pdHRlciB0bw0KPg0KPiBjb25zaWRlcg0KPg0KPj4gdGhlIGZvbGxv
d2luZyBkb2N1bWVudDoNCj4NCj4+IC0gJ0FsbG9jYXRpb24gb2YgYW4gQXNzb2NpYXRlZCBDaGFu
bmVsIENvZGUgUG9pbnQgZm9yIFVzZSBieSBJVFUtVA0KPg0KPj4gICAgRXRoZXJuZXQgYmFzZWQg
T0FNJw0KPg0KPj4gICA8ZHJhZnQtYmV0dHMtaXR1LW9hbS1hY2gtY29kZS1wb2ludC0wMy50eHQ+
IGFzIGFuIEluZm9ybWF0aW9uYWwgUkZDDQo+DQo+Pg0KPg0KPj4gVGhlIElFU0cgcGxhbnMgdG8g
bWFrZSBhIGRlY2lzaW9uIGluIHRoZSBuZXh0IGZldyB3ZWVrcywgYW5kIHNvbGljaXRzDQo+DQo+
PiBmaW5hbCBjb21tZW50cyBvbiB0aGlzIGFjdGlvbi4gUGxlYXNlIHNlbmQgc3Vic3RhbnRpdmUg
Y29tbWVudHMgdG8NCj4+IHRoZQ0KPg0KPj4gaWV0ZkBpZXRmLm9yZyBtYWlsaW5nIGxpc3RzIGJ5
IDIwMTItMDMtMjEuIEV4Y2VwdGlvbmFsbHksIGNvbW1lbnRzDQo+PiBtYXkNCj4NCj4gYmUNCj4N
Cj4+IHNlbnQgdG8gaWVzZ0BpZXRmLm9yZyBpbnN0ZWFkLiBJbiBlaXRoZXIgY2FzZSwgcGxlYXNl
IHJldGFpbiB0aGUNCj4NCj4+IGJlZ2lubmluZyBvZiB0aGUgU3ViamVjdCBsaW5lIHRvIGFsbG93
IGF1dG9tYXRlZCBzb3J0aW5nLg0KPg0KPj4NCj4NCj4+IEFic3RyYWN0DQo+DQo+Pg0KPg0KPj4g
ICAgVGhpcyBkb2N1bWVudCBhc3NpZ25zIGFuIEFzc29jaWF0ZWQgQ2hhbm5lbCBUeXBlIGNvZGUg
cG9pbnQgZm9yDQo+DQo+PiAgICBjYXJyeWluZyBFdGhlcm5ldCBiYXNlZCBPcGVyYXRpb25zLCBB
ZG1pbmlzdHJhdGlvbiwgYW5kIE1hbmFnZW1lbnQNCj4NCj4+ICAgIG1lc3NhZ2VzIGluIHRoZSBN
UExTIEdlbmVyaWMgQXNzb2NpYXRlZCBDaGFubmVsIChHLUFDaCkuDQo+DQo+Pg0KPg0KPj4gVGhl
IGZpbGUgY2FuIGJlIG9idGFpbmVkIHZpYQ0KPg0KPj4gaHR0cDovL2RhdGF0cmFja2VyLmlldGYu
b3JnL2RvYy9kcmFmdC1iZXR0cy1pdHUtb2FtLWFjaC1jb2RlLXBvaW50Lw0KPg0KPj4NCj4NCj4+
IElFU0cgZGlzY3Vzc2lvbiBjYW4gYmUgdHJhY2tlZCB2aWENCj4NCj4+IGh0dHA6Ly9kYXRhdHJh
Y2tlci5pZXRmLm9yZy9kb2MvZHJhZnQtYmV0dHMtaXR1LW9hbS1hY2gtY29kZS1wb2ludC8NCj4N
Cj4+DQo+DQo+Pg0KPg0KPj4gTm8gSVBSIGRlY2xhcmF0aW9ucyBoYXZlIGJlZW4gc3VibWl0dGVk
IGRpcmVjdGx5IG9uIHRoaXMgSS1ELg0KPg0KPj4gX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX18NCj4NCj4+IElFVEYtQW5ub3VuY2UgbWFpbGluZyBsaXN0DQo+
DQo+PiBJRVRGLUFubm91bmNlQGlldGYub3JnDQo+DQo+PiBodHRwczovL3d3dy5pZXRmLm9yZy9t
YWlsbWFuL2xpc3RpbmZvL2lldGYtYW5ub3VuY2UNCj4NCj4NCj4NCj4gX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCj4NCj4gbXBscyBtYWlsaW5nIGxpc3QN
Cj4NCj4gbXBsc0BpZXRmLm9yZw0KPg0KPiBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xp
c3RpbmZvL21wbHMNCj4NCj4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX18NCj4NCj4gSWV0ZiBtYWlsaW5nIGxpc3QNCj4NCj4gSWV0ZkBpZXRmLm9yZw0KPg0K
PiBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2lldGYNCj4NCj4gX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCj4NCj4gSWV0ZiBtYWls
aW5nIGxpc3QNCj4NCj4gSWV0ZkBpZXRmLm9yZw0KPg0KPiBodHRwczovL3d3dy5pZXRmLm9yZy9t
YWlsbWFuL2xpc3RpbmZvL2lldGYNCj4NCj4NCj4gX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX18NCj4gSWV0ZiBtYWlsaW5nIGxpc3QNCj4gSWV0ZkBpZXRmLm9y
Zw0KPiBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2lldGYNCj4NCl9fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQpJZXRmIG1haWxpbmcg
bGlzdA0KSWV0ZkBpZXRmLm9yZw0KaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5m
by9pZXRmDQoNCg0KDQotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KDQoNCj4gX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCj4gSWV0ZiBtYWlsaW5nIGxpc3QN
Cj4gSWV0ZkBpZXRmLm9yZw0KPiBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZv
L2lldGYNCj4NCg0KDQoNClF1ZXN0byBtZXNzYWdnaW8gZSBpIHN1b2kgYWxsZWdhdGkgc29ubyBp
bmRpcml6emF0aSBlc2NsdXNpdmFtZW50ZSBhbGxlIHBlcnNvbmUgaW5kaWNhdGUuIExhIGRpZmZ1
c2lvbmUsIGNvcGlhIG8gcXVhbHNpYXNpIGFsdHJhIGF6aW9uZSBkZXJpdmFudGUgZGFsbGEgY29u
b3NjZW56YSBkaSBxdWVzdGUgaW5mb3JtYXppb25pIHNvbm8gcmlnb3Jvc2FtZW50ZSB2aWV0YXRl
LiBRdWFsb3JhIGFiYmlhdGUgcmljZXZ1dG8gcXVlc3RvIGRvY3VtZW50byBwZXIgZXJyb3JlIHNp
ZXRlIGNvcnRlc2VtZW50ZSBwcmVnYXRpIGRpIGRhcm5lIGltbWVkaWF0YSBjb211bmljYXppb25l
IGFsIG1pdHRlbnRlIGUgZGkgcHJvdnZlZGVyZSBhbGxhIHN1YSBkaXN0cnV6aW9uZSwgR3Jhemll
Lg0KDQpUaGlzIGUtbWFpbCBhbmQgYW55IGF0dGFjaG1lbnRzIGlzIGNvbmZpZGVudGlhbCBhbmQg
bWF5IGNvbnRhaW4gcHJpdmlsZWdlZCBpbmZvcm1hdGlvbiBpbnRlbmRlZCBmb3IgdGhlIGFkZHJl
c3NlZShzKSBvbmx5LiBEaXNzZW1pbmF0aW9uLCBjb3B5aW5nLCBwcmludGluZyBvciB1c2UgYnkg
YW55Ym9keSBlbHNlIGlzIHVuYXV0aG9yaXNlZC4gSWYgeW91IGFyZSBub3QgdGhlIGludGVuZGVk
IHJlY2lwaWVudCwgcGxlYXNlIGRlbGV0ZSB0aGlzIG1lc3NhZ2UgYW5kIGFueSBhdHRhY2htZW50
cyBhbmQgYWR2aXNlIHRoZSBzZW5kZXIgYnkgcmV0dXJuIGUtbWFpbCwgVGhhbmtzLg0KDQo=

From akatlas@gmail.com  Wed Mar 21 08:29:48 2012
Return-Path: <akatlas@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7111A21F86F4 for <ietf@ietfa.amsl.com>; Wed, 21 Mar 2012 08:29:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.922
X-Spam-Level: 
X-Spam-Status: No, score=-2.922 tagged_above=-999 required=5 tests=[AWL=-0.375, BAYES_00=-2.599, J_CHICKENPOX_15=0.6, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1, SARE_SUB_ENC_UTF8=0.152]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kZcEC121N91J for <ietf@ietfa.amsl.com>; Wed, 21 Mar 2012 08:29:47 -0700 (PDT)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id 211BA21F86E5 for <ietf@ietf.org>; Wed, 21 Mar 2012 08:29:47 -0700 (PDT)
Received: by iazz13 with SMTP id z13so1998928iaz.31 for <ietf@ietf.org>; Wed, 21 Mar 2012 08:29: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:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=YsfaQJWVIlZKL2Kg9COmEl+SZ8ZE3S+PqAufXCGxJ/A=; b=kVAjW5rHjax6ZLot6JLLjuy6GBXHcFhQfKlRYnH8Br7XzwQZsPCkGcYkndm/bt5jA+ H6l061viqw80XxrIoGc+BBncXuWS5TJbNhyrjIxblQask3/tHkriAeIbr+5elZmxWC4l gUvoISVCjNNadqkNR0a9x/8OGxTtuQIJFiSO6OlWx9Bdbf0Ze5wX66B9fGrHGLE/l8I0 tW9wWic/+qzBRBDCsA7PMaakvjjYZ9CoQr0RQQqA4ihXyOa9KiuuOUshmO2lUS2tT0bI hssUasMergREt51GM2UV7sF4d+p2WK49CTtcUXy5NoVw07cE8QfHFyb4KDljxOzylUPn eIkg==
MIME-Version: 1.0
Received: by 10.50.181.194 with SMTP id dy2mr3033053igc.48.1332343786602; Wed, 21 Mar 2012 08:29:46 -0700 (PDT)
Received: by 10.50.1.209 with HTTP; Wed, 21 Mar 2012 08:29:46 -0700 (PDT)
In-Reply-To: <A1F769BC58A8B146B2EEA818EAE052A2097389D69F@GRFMBX702RM001.griffon.local>
References: <8fab01cd014c$dea8f551$5e209f0a@nsnintra.net> <050401cd01d1$10aa47c0$4001a8c0@gateway.2wire.net> <A1F769BC58A8B146B2EEA818EAE052A2097389D69F@GRFMBX702RM001.griffon.local>
Date: Wed, 21 Mar 2012 11:29:46 -0400
Message-ID: <CAG4d1retO38rCGSNawo3crtiwGm1NfaQg8CpUB3x42Ti+A00kQ@mail.gmail.com>
Subject: =?UTF-8?Q?Re=3A_=D7=94=D7=A0=D7=93=D7=95=D7=9F=3A_RE=3A_Last_Call=3A=3Cdraft=2Dbetts=2Ditu=2Doam=2Da?= =?UTF-8?Q?ch=2Dcode=2Dpoint=2D03=2Etxt=3E=28Allocationof_an_Associated_Channel_Cod?= =?UTF-8?Q?e_Point_for_Use_byITU=2DT_Ethernetbased_OAM=29_to_Informational_?= =?UTF-8?Q?RFC?=
From: Alia Atlas <akatlas@gmail.com>
To: "D'Alessandro Alessandro Gerardo" <alessandro.dalessandro@telecomitalia.it>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Mar 2012 15:29:48 -0000

Considering that the need for this code point is a result of the ITU
not fully complying with the IETF agreement, I cannot agree that we
should simply allocate a code point for whatever the ITU wants to do
in the future.

It seems the best of the options to allocate a code point (much better
than squatting) - but tie it to a stable reference.  If the ITU can't
provide a stable reference, then perhaps an RFC is the best way.
There are lots of folks with opinions on the best procedure, but I
certainly don't support the idea of not restricting the usage to what
is clearly defined.

Alia

On Wed, Mar 21, 2012 at 11:04 AM, D'Alessandro Alessandro Gerardo
<alessandro.dalessandro@telecomitalia.it> wrote:
> Dear all,
> Wrt draft-betts, I believe it is appropriate to allocate a code point for=
 the referenced specification without any restriction about the possibility=
 to evolve messages/protocols when compatibility is preserved. It is not on=
ly unnecessary but it does not help in improving the relationship between t=
he two SDOs.
>
> Best regards,
> Alessandro
> ------------------------------------------------------------------
> Telecom Italia
> Alessandro Gerardo D'Alessandro
> Transport Innovation
> Via Reiss Romoli, 274 - 10148 Torino
> phone: =C2=A0+39 011 228 5887
> mobile: +39 335 766 9607
> fax: +39 06 418 639 07
>
>
> -----Messaggio originale-----
> Da: t.petch [mailto:daedulus@btconnect.com]
> Inviato: mercoled=C3=AC 14 marzo 2012 11:56
> A: Sprecher, Nurit (NSN - IL/Hod HaSharon); ext Ross Callon
> Cc: ietf@ietf.org
> Oggetto: Re: =D7=94=D7=A0=D7=93=D7=95=D7=9F: RE: Last Call:<draft-betts-i=
tu-oam-ach-code-point-03.txt>(Allocationof an Associated Channel Code Point=
 for Use byITU-T Ethernetbased OAM) to Informational RFC
>
> ----- Original Message -----
> From: "Sprecher, Nurit (NSN - IL/Hod HaSharon)" <nurit.sprecher@nsn.com>
> To: "Andrew G. Malis" <agmalis@gmail.com>; "ext Ross Callon"
> <rcallon@juniper.net>
> Cc: <ietf@ietf.org>
> Sent: Tuesday, March 13, 2012 8:09 PM
> Subject: =D7=94=D7=A0=D7=93=D7=95=D7=9F: RE: Last
> Call:<draft-betts-itu-oam-ach-code-point-03.txt>(Allocationof an Associat=
ed Channel Code Point for Use byITU-T Ethernetbased OAM) to Informational R=
FC
>
>
> Ross,
> i am afraid that you missed the point. There will not be a final version =
since as written in draft-betts, all =C2=A0ITU recommendations are subject =
to revisions, and the code point will also be used for future revisions of =
the document. New messages/protocols can be defined in future revisions of =
the recommendation and they will use the same code point that is allocated =
for the first version.
> This is a real issue.
> Regards,
> Nurit
> -----=D7=94=D7=95=D7=93=D7=A2=D7=94 =D7=9E=D7=A7=D7=95=D7=A8=D7=99=D7=AA-=
----
> =D7=9E=D7=90=D7=AA: ext Ross Callon
> =D7=A0=D7=A9=D7=9C=D7=97: =C2=A013/03/2012, 19:27
> =D7=90=D7=9C: Andrew G. Malis; Sprecher, Nurit (NSN - IL/Hod HaSharon)
> =D7=A2=D7=95=D7=AA=D7=A7: ietf@ietf.org
> =D7=A0=D7=95=D7=A9=D7=90: RE: Last Call:<draft-betts-itu-oam-ach-code-poi=
nt-03.txt>(Allocationof an Associated Channel Code Point for Use byITU-T Et=
hernetbased OAM) to Informational RFC I agree that the allocation of a code=
 point should be to a specific version of 8113.1,
>
> <tp>
> Why?
>
> I can understand a new code point being required if there is a new and ba=
ckwards incompatible format for the messages, but if the messages are exten=
ded in a forwards compatible manner, adding new TLV for example, or a new f=
ormat of IF_ID, then why should we burn a new code point?
>
> Would you say that we should have a dozen different port numbers for HTTP=
 to reflect its evolution over time? =C2=A0If not, why not?
>
> Demanding that the ITU-T come back to us for a new round of negotiation w=
hen it is technically unnecessary seems to be placing an unnecessary barrie=
r between the two SDOs.
>
> Tom Petch
>
> and specifically should be to the final version that is approved by the I=
TU-T (assuming that a final version of 8113.1 will be approved by the ITU-T=
). This would imply that draft-betts-itu-oam-ach-code-point should contain =
a normative reference to the final approved version of 8113.1.
>
> Given normal IETF processes, this implies that the final RFC resulting fr=
om draft-betts-itu-oam-ach-code-point could be published as soon as the fin=
al version of 8113.1 is approved (with the understanding that there will be=
 a small normal delay between "approved" and "published" which gives time f=
or coordination). Given that the final version of 8113.1 might need to refe=
rence the RFC resulting from draft-betts-itu-oam-ach-code-point, a bit of c=
ooperation might be needed between editorial staff at the ITU and RFC edito=
rial staff, but I don't see why this should be a problem (I am sure that th=
ey all have access to email).
>
> Ross
>
> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of A=
ndrew G. Malis
> Sent: Monday, March 05, 2012 6:54 PM
> To: Sprecher, Nurit (NSN - IL/Hod HaSharon)
> Cc: ietf@ietf.org
> Subject: Re: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt>(Alloc=
ationof
> an Associated Channel Code Point for Use byITU-T Ethernetbased OAM) to In=
formational RFC
>
> I would like to support Nurit's comments below. In particular, in the pas=
t the ITU-T has expanded upon or changed the usage of IETF codepoint alloca=
tions, in some cases incompatibly with its original usage or definition. In=
 the future, all codepoint allocations to the ITU-T should be tied to one s=
pecific, dated revision of their specification only. This is similar to the=
 ITU-T's own processes, such as section 2.2.1 of Rec. A.5, which requires a=
 version number and/or date for referenced outside documents in ITU-T recom=
mendations.
>
> Cheers,
> Andy
>
> On Thu, Mar 1, 2012 at 7:20 AM, Sprecher, Nurit (NSN - IL/Hod
> HaSharon) <nurit.sprecher@nsn.com> wrote:
>> Hi,
>>
>>
>>
>> I cannot support the publication of the document in its current version.
>>
>>
>>
>> I have the following concerns:
>>
>>
>>
>> . =C2=A0 =C2=A0 =C2=A0 =C2=A0It is indicated that the channel is intende=
d to be used to carry
>> Ethernet based OAM messages. It is not clear why there is a need for ACH=
.
>> PWs can be used to transmit Ethernet OAM.
>>
>> If the intention is to use the channel for OAM messages for operating
>> MPLS-TP based networks, the IETF *already* defined a solution for
>> MPLS-TP OAM and I expect to see first a technical *justification* why
>> a second solution is needed. In addition, I would expect to see
>> *references to the
>> arguments* raised in draft-sprecher-mpls-tp-oam-considerations.
>>
>>
>>
>> . =C2=A0 =C2=A0 =C2=A0 =C2=A0It is not clear what the maturity status of=
 G.8113.1 is. It seems
>> that the document was not approved by SG15 and the discussion was
>> deferred to WTSA. This indicates that there is *no consensus* for the
>> approval of G.8113.1. A code point should not be allocated before a
>> consensus/decision is reached in the ITU-T and before the document is
>> mature and approved. I do not think it is appropriate to allocate a
>> code point and try to force a resolution in the ITU-T.
>>
>>
>>
>> . =C2=A0 =C2=A0 =C2=A0 =C2=A0I find a contradiction in the draft. In one=
 place it is mentioned:
>> "These Ethernet based OAM messages and procedures, address the OAM
>> functional requirements defined in [RFC5860]. Other message types
>> should not be carried behind this code point." In another place it is
>> mentioned: "all ITU-T Recommendations are subject to revision.
>> Therefore, the code point allocated by this document may be used for fut=
ure versions of [G.8113.1].".
>> The last statement opens the door for the definition of additional
>> messages in G.8113.1 in the following versions, for example, for APS
>> (supporting linear or ring protection mechanisms) and by this creates
>> two solutions for other mechanisms as well.
>>
>>
>>
>> The use of the code point can go much beyond its original purpose and
>> it will hide other messages....a code point should not be allocated at
>> this point at all, but specifically not for unknown usage that may be
>> defined in future versions of G.8113.1.
>>
>>
>>
>> Best regards,
>>
>> Nurit
>>
>>
>>
>>
>>
>>
>>
>>> -----Original Message-----
>>
>>> From: ietf-announce-bounces@ietf.org [mailto:ietf-announce-
>>
>>> bounces@ietf.org] On Behalf Of The IESG
>>
>>> Sent: 22 February 2012 15:13
>>
>>> To: IETF-Announce
>>
>>> Subject: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt>
>>
>> (Allocation of
>>
>> an
>>
>>> Associated Channel Code Point for Use by ITU-T Ethernet based OAM) to
>>
>>> Informational RFC
>>
>>>
>>
>>>
>>
>>> The IESG has received a request from an individual submitter to
>>
>> consider
>>
>>> the following document:
>>
>>> - 'Allocation of an Associated Channel Code Point for Use by ITU-T
>>
>>> =C2=A0 =C2=A0Ethernet based OAM'
>>
>>> =C2=A0 <draft-betts-itu-oam-ach-code-point-03.txt> as an 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-03-21. 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
>>
>>>
>>
>>> =C2=A0 =C2=A0This document assigns an Associated Channel Type code poin=
t for
>>
>>> =C2=A0 =C2=A0carrying Ethernet based Operations, Administration, and Ma=
nagement
>>
>>> =C2=A0 =C2=A0messages in the MPLS Generic Associated Channel (G-ACh).
>>
>>>
>>
>>> The file can be obtained via
>>
>>> http://datatracker.ietf.org/doc/draft-betts-itu-oam-ach-code-point/
>>
>>>
>>
>>> IESG discussion can be tracked via
>>
>>> http://datatracker.ietf.org/doc/draft-betts-itu-oam-ach-code-point/
>>
>>>
>>
>>>
>>
>>> No IPR declarations have been submitted directly on this I-D.
>>
>>> _______________________________________________
>>
>>> IETF-Announce mailing list
>>
>>> IETF-Announce@ietf.org
>>
>>> https://www.ietf.org/mailman/listinfo/ietf-announce
>>
>>
>>
>> _______________________________________________
>>
>> mpls mailing list
>>
>> mpls@ietf.org
>>
>> https://www.ietf.org/mailman/listinfo/mpls
>>
>> _______________________________________________
>>
>> Ietf mailing list
>>
>> Ietf@ietf.org
>>
>> https://www.ietf.org/mailman/listinfo/ietf
>>
>> _______________________________________________
>>
>> Ietf mailing list
>>
>> Ietf@ietf.org
>>
>> https://www.ietf.org/mailman/listinfo/ietf
>>
>>
>> _______________________________________________
>> Ietf mailing list
>> Ietf@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf
>>
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>
>
>
> -------------------------------------------------------------------------=
-------
>
>
>> _______________________________________________
>> Ietf mailing list
>> Ietf@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf
>>
>
>
>
> Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle p=
ersone indicate. La diffusione, copia o qualsiasi altra azione derivante da=
lla conoscenza di queste informazioni sono rigorosamente vietate. Qualora a=
bbiate ricevuto questo documento per errore siete cortesemente pregati di d=
arne immediata comunicazione al mittente e di provvedere alla sua distruzio=
ne, Grazie.
>
> This e-mail and any attachments is confidential and may contain privilege=
d information intended for the addressee(s) only. Dissemination, copying, p=
rinting or use by anybody else is unauthorised. If you are not the intended=
 recipient, please delete this message and any attachments and advise the s=
ender by return e-mail, Thanks.
>

From dworley@avaya.com  Wed Mar 21 10:49:02 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 C099A21E8039 for <ietf@ietfa.amsl.com>; Wed, 21 Mar 2012 10:49:02 -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.617, BAYES_00=-2.599, J_CHICKENPOX_54=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WsrvsVL5zVRA for <ietf@ietfa.amsl.com>; Wed, 21 Mar 2012 10:49:02 -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 3DEAF21E800E for <ietf@ietf.org>; Wed, 21 Mar 2012 10:49:02 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av4EAIYTak/GmAcF/2dsb2JhbAA6CrcFgQeCCQEBAQECARIoRAsCAQgNCCEQMiUBAQQBEggah2MFm3mcHIpYCYU9YwSbbooYgwOBQA
X-IronPort-AV: E=Sophos;i="4.73,624,1325480400";  d="scan'208";a="628279"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by p-us1-iereast-outbound.us1.avaya.com with ESMTP; 21 Mar 2012 13:49:01 -0400
Received: from unknown (HELO DC-US1HCEX3.global.avaya.com) ([135.11.52.22]) by co300216-co-erhwest-out.avaya.com with ESMTP; 21 Mar 2012 13:40:42 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.202]) by DC-US1HCEX3.global.avaya.com ([135.11.52.22]) with mapi; Wed, 21 Mar 2012 13:49:00 -0400
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: Sabahattin Gucukoglu <mail-dated-1334746550.15c4ac@sabahattin-gucukoglu.com>, "ietf@ietf.org" <ietf@ietf.org>
Date: Wed, 21 Mar 2012 13:44:31 -0400
Subject: RE: IPv6 Zone Identifiers Considered Hateful
Thread-Topic: IPv6 Zone Identifiers Considered Hateful
Thread-Index: Ac0Fvuc1JIMvQbEqTzy33A2Nyb2JmgBy146z
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B22726A0994@DC-US1MBEX4.global.avaya.com>
References: <82A794CE-B328-475F-9300-1B6BE628F7E3@sabahattin-gucukoglu.com>
In-Reply-To: <82A794CE-B328-475F-9300-1B6BE628F7E3@sabahattin-gucukoglu.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Mar 2012 17:49:02 -0000

> From: Sabahattin Gucukoglu [mail@sabahattin-gucukoglu.com]
>=20
> [...] when I ping one from the other using link-local-scoped
> addresses, I have to put in this zone identifier (%ifname on BSD and
> Linux).
> [...]
> Can't it figure it out itself?

OK, I know nothing about the subject, but when I do "ifconfig" I get:

    eth0      Link encap:Ethernet  HWaddr 00:16:35:AF:82:03 =20
	      inet addr:135.55.22.90  Bcast:135.55.22.255  Mask:255.255.255.0
	      inet6 addr: fe80::216:35ff:feaf:8203/64 Scope:Link
	      UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
	      [...]

Looking at the link-local address, it appears to be constructed from
the interface's MAC address, and basically nothing else.

This suggests that the link-local address of another system on an
attached network would contain that system's MAC address, but nothing
to identify which network, and thus, *this* system has no algorithmic
way to determine which interface goes to the proper network.

Dale

From snark17@gmail.com  Wed Mar 21 10:54:43 2012
Return-Path: <snark17@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D69EF21E8040 for <ietf@ietfa.amsl.com>; Wed, 21 Mar 2012 10:54:43 -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=[BAYES_00=-2.599, J_CHICKENPOX_54=0.6, 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 jtUDIbXAd4-z for <ietf@ietfa.amsl.com>; Wed, 21 Mar 2012 10:54:43 -0700 (PDT)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 37D2021E801A for <ietf@ietf.org>; Wed, 21 Mar 2012 10:54:43 -0700 (PDT)
Received: by vcbfk13 with SMTP id fk13so1535766vcb.31 for <ietf@ietf.org>; Wed, 21 Mar 2012 10:54: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:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=a7rd3nbA8FBOBAR0CbugJfkLfRiRTsRJ5pvDD3Q3pQU=; b=ZqCXm0kv83PuFAwi/K3J5uqAboCTqedMdWQRUg7EjgPxMq2FwJm552lgDZWajil2rM sdSpSsscb6ij19ZiyicNMSUbZoVT4teFd51id+te/6S7YEGTxIL+2Du5v13Z4Ab8y8MV UwuVAmIHqxBP3/H+Dd/DUyOdLmKWpWohQ59U+yXoIAAdnYZRcKeBkTBslalEvFV92NAq dkriNDOpXTfNaNzDbz1wXnIPEtW50p0OK1K8dHlvX1lqVFmc0Vr27x3GuaD/YGD2Qyl9 /2Z1CYL/KTvGEEJcw/fG7Gef1dgTuwX2xOtGVMnWJKZAKC+rjoMWcvkg5TGvCm2Od79r yr6Q==
MIME-Version: 1.0
Received: by 10.52.28.164 with SMTP id c4mr1860686vdh.130.1332352482749; Wed, 21 Mar 2012 10:54:42 -0700 (PDT)
Received: by 10.52.99.8 with HTTP; Wed, 21 Mar 2012 10:54:42 -0700 (PDT)
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B22726A0994@DC-US1MBEX4.global.avaya.com>
References: <82A794CE-B328-475F-9300-1B6BE628F7E3@sabahattin-gucukoglu.com> <CD5674C3CD99574EBA7432465FC13C1B22726A0994@DC-US1MBEX4.global.avaya.com>
Date: Wed, 21 Mar 2012 12:54:42 -0500
Message-ID: <CAGHVWBgnF49UYSaL3awXf4Y+wxvmUTFi9xYRVCZ8WL1nFZp1Aw@mail.gmail.com>
Subject: Re: IPv6 Zone Identifiers Considered Hateful
From: Craig Finseth <snark17@gmail.com>
To: "Worley, Dale R (Dale)" <dworley@avaya.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: Sabahattin Gucukoglu <mail-dated-1334746550.15c4ac@sabahattin-gucukoglu.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: Wed, 21 Mar 2012 17:54:43 -0000

On Wed, Mar 21, 2012 at 12:44 PM, Worley, Dale R (Dale)
<dworley@avaya.com> wrote:

> OK, I know nothing about the subject, but when I do "ifconfig" I get:
>
> =A0 =A0eth0 =A0 =A0 =A0Link encap:Ethernet =A0HWaddr 00:16:35:AF:82:03
> =A0 =A0 =A0 =A0 =A0 =A0 =A0inet addr:135.55.22.90 =A0Bcast:135.55.22.255 =
=A0Mask:255.255.255.0
> =A0 =A0 =A0 =A0 =A0 =A0 =A0inet6 addr: fe80::216:35ff:feaf:8203/64 Scope:=
Link
> =A0 =A0 =A0 =A0 =A0 =A0 =A0UP BROADCAST RUNNING MULTICAST =A0MTU:1500 =A0=
Metric:1
> =A0 =A0 =A0 =A0 =A0 =A0 =A0[...]
>
> Looking at the link-local address, it appears to be constructed from
> the interface's MAC address, and basically nothing else.
>
> This suggests that the link-local address of another system on an
> attached network would contain that system's MAC address, but nothing
> to identify which network, and thus, *this* system has no algorithmic
> way to determine which interface goes to the proper network.

You've just rediscovered what the "link local" part of the link-local
address means: the address is local to the link!  It is not globally
unique or even unique within a host, it is just unique within a link.
Thus, if a host has more than one interface (and most do: at least one
network interface + loopback, which is a separate interface), you need
to tell it which one you mean when you use link-local addresses.

--=20
Craig A. Finseth

From dworley@avaya.com  Wed Mar 21 11:00:22 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 A6BCF21E8095 for <ietf@ietfa.amsl.com>; Wed, 21 Mar 2012 11:00:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.404
X-Spam-Level: 
X-Spam-Status: No, score=-103.404 tagged_above=-999 required=5 tests=[AWL=0.195, 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 cTd04DlxKA-q for <ietf@ietfa.amsl.com>; Wed, 21 Mar 2012 11:00:21 -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 112F621F84D2 for <ietf@ietf.org>; Wed, 21 Mar 2012 11:00:20 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EALcWak/GmAcF/2dsb2JhbABDtxKBB4IJAQEBAQIBEig/BQsCAQgNAQchECERJQEBBA4FCBqHYwWiLZQ2iWyGMmMElAqHZIUfhHmDAw
X-IronPort-AV: E=Sophos;i="4.73,624,1325480400"; d="scan'208";a="298248551"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 21 Mar 2012 14:00:19 -0400
Received: from unknown (HELO DC-US1HCEX4.global.avaya.com) ([135.11.52.35]) by co300216-co-erhwest-out.avaya.com with ESMTP; 21 Mar 2012 13:51:59 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.202]) by DC-US1HCEX4.global.avaya.com ([135.11.52.35]) with mapi; Wed, 21 Mar 2012 14:00:15 -0400
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: Craig Finseth <snark17@gmail.com>
Date: Wed, 21 Mar 2012 13:57:24 -0400
Subject: RE: IPv6 Zone Identifiers Considered Hateful
Thread-Topic: IPv6 Zone Identifiers Considered Hateful
Thread-Index: Ac0Hi7Ku4NHSimV+S7GwckR3zU6vEQAAF8p/
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B22726A0996@DC-US1MBEX4.global.avaya.com>
References: <82A794CE-B328-475F-9300-1B6BE628F7E3@sabahattin-gucukoglu.com> <CD5674C3CD99574EBA7432465FC13C1B22726A0994@DC-US1MBEX4.global.avaya.com>, <CAGHVWBgnF49UYSaL3awXf4Y+wxvmUTFi9xYRVCZ8WL1nFZp1Aw@mail.gmail.com>
In-Reply-To: <CAGHVWBgnF49UYSaL3awXf4Y+wxvmUTFi9xYRVCZ8WL1nFZp1Aw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Sabahattin Gucukoglu <mail-dated-1334746550.15c4ac@sabahattin-gucukoglu.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: Wed, 21 Mar 2012 18:00:22 -0000

> From: Craig Finseth [snark17@gmail.com]
>=20
> You've just rediscovered what the "link local" part of the link-local
> address means: the address is local to the link!  It is not globally
> unique or even unique within a host, it is just unique within a link.

Actually, it's globally *unique*, because it contains the MAC address.
The problem is that it's not *routable*, even within the context of a
single host.  And unless you give an application on the host guidance,
it depends on host-context routing to get its output packets to the
correct wire.  It's hard to remain aware that host-context routing is
important, because it's almost always worked.

Dale

From stewe@stewe.org  Wed Mar 21 11:09:27 2012
Return-Path: <stewe@stewe.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 92EE021F847F; Wed, 21 Mar 2012 11:09:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.735
X-Spam-Level: 
X-Spam-Status: No, score=-3.735 tagged_above=-999 required=5 tests=[AWL=-0.136, 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 aj1hdzaxc4Qr; Wed, 21 Mar 2012 11:09:26 -0700 (PDT)
Received: from db3outboundpool.messaging.microsoft.com (db3ehsobe003.messaging.microsoft.com [213.199.154.141]) by ietfa.amsl.com (Postfix) with ESMTP id 1C16121F847E; Wed, 21 Mar 2012 11:09:25 -0700 (PDT)
Received: from mail101-db3-R.bigfish.com (10.3.81.238) by DB3EHSOBE005.bigfish.com (10.3.84.25) with Microsoft SMTP Server id 14.1.225.23; Wed, 21 Mar 2012 18:09:18 +0000
Received: from mail101-db3 (localhost [127.0.0.1])	by mail101-db3-R.bigfish.com (Postfix) with ESMTP id 91DC54A0357; Wed, 21 Mar 2012 18:09:17 +0000 (UTC)
X-SpamScore: -43
X-BigFish: PS-43(zz9371I1503M542M1432N98dK4015I1447Mzz1202h1082kzz1033IL8275bh8275dhz2fh2a8h668h839h944h)
X-Forefront-Antispam-Report: CIP:157.56.240.133; KIP:(null); UIP:(null); IPV:NLI; H:BL2PRD0710HT004.namprd07.prod.outlook.com; RD:none; EFVD:NLI
Received-SPF: pass (mail101-db3: domain of stewe.org designates 157.56.240.133 as permitted sender) client-ip=157.56.240.133; envelope-from=stewe@stewe.org; helo=BL2PRD0710HT004.namprd07.prod.outlook.com ; .outlook.com ; 
Received: from mail101-db3 (localhost.localdomain [127.0.0.1]) by mail101-db3 (MessageSwitch) id 1332353355317821_29063; Wed, 21 Mar 2012 18:09:15 +0000 (UTC)
Received: from DB3EHSMHS004.bigfish.com (unknown [10.3.81.238])	by mail101-db3.bigfish.com (Postfix) with ESMTP id 46568100049; Wed, 21 Mar 2012 18:09:15 +0000 (UTC)
Received: from BL2PRD0710HT004.namprd07.prod.outlook.com (157.56.240.133) by DB3EHSMHS004.bigfish.com (10.3.87.104) with Microsoft SMTP Server (TLS) id 14.1.225.23; Wed, 21 Mar 2012 18:09:14 +0000
Received: from BL2PRD0710MB349.namprd07.prod.outlook.com ([169.254.1.100]) by BL2PRD0710HT004.namprd07.prod.outlook.com ([10.255.102.39]) with mapi id 14.16.0135.002; Wed, 21 Mar 2012 18:09:09 +0000
From: Stephan Wenger <stewe@stewe.org>
To: Barry Leiba <barryleiba@computer.org>
Subject: Re: [AVTCORE] IPR requirements in document write-up
Thread-Topic: [AVTCORE] IPR requirements in document write-up
Thread-Index: AQHNB4223QfN1LwTdkiObOrmg6aoSw==
Date: Wed, 21 Mar 2012 18:09:09 +0000
Message-ID: <CB8FCF89.84B69%stewe@stewe.org>
In-Reply-To: <CALaySJJcP8ijZK6PyX8+3zpDSL3q47woWX0e__mcDtA=nD438w@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.255.102.4]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <C2920CD07DB8674697AE80EC2660AC12@namprd07.prod.outlook.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: stewe.org
Cc: "ipr@ietf.org" <ipr@ietf.org>, IETF <ietf@ietf.org>, "avt@ietf.org" <avt@ietf.org>, "payload@ietf.org" <payload@ietf.org>, "iesg@ietf.org" <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Mar 2012 18:09:27 -0000

Hi Barry,

Adding the IPRWG and ietf@ietf.

For the benefit if "new" readers: This is about an updated proto shepherd
writeup template, asking two questions about IPR that, IMO may not be in
compliance with the IETF's IPR policy.

I was not aware that the proto template had IESG blessing.  Still, I
believe that the template text does not ask the right question, or, more
specifically, is a suggestive question in that it appears (at least to me)
to interpret the IETF's patent policy in a considerably more strict way
than it is set out in the policy RFCs.
I believe the IESG should reconsider the proto writeup.
A few more comments inline

On 3.21.2012 17:03 , "Barry Leiba" <barryleiba@computer.org> wrote:

>> Thanks for the text, I will use it.
>>
>> Roni
>
>I recommend you do not, for a few reasons:
>
>1. You may not rewrite the PROTO template; that belongs to the IESG.

Agreed (now that I'm aware of that this is an IESG-sanctioned template).

>2. The question was worded as it is for a reason, and it should be
>left that way.  The IESG wants to know whether there are any known IPR
>claims, whether declarations have been made to and considered by the
>working group, and whether formal IPR statements have been filed in
>the system.  The middle one is as important as the last.

Also agreed (with caveats, see below).

>
>3. Stephan is incorrect when he says this:
>> The reason is that disclosure is not
>> required in many cases; for example, when the IPR in question is not
>>owned
>> by them or their employers.
>
>If you are aware of IPR that you do not own, you may and you should
>make a third-party disclosure.

Barry, please read my language carefully.  Perhaps I should have
capitalized REQUIRED, but the text is clear and inline with yours.  It's
MAY and SHOULD for third party disclosures.  But you are NOT *required* to
do so by policy; there is no MUST.  There are many good and valid reasons
why there is no MUST (beyond that it's not in the policy docs).  And,
third party disclosures are not even a widely used current practice.  Just
look at the (comparatively low) number of third party disclosures.

Look, I do patent work as my day job.  I also do standards work  In my
current and previous job roles, I have looked at hundreds of patents of my
current or previous employers, as well as occasionally at third party
patents.  Now, with this background, let's look at the template text again
(numerals by me):

   (1) Are you aware of any IPR that applies to <insert document name>?
(2) If so,
   has this IPR been disclosed in compliance with IETF IPR rules (see RFCs
3979,=20
   4879, 3669 and 5378 for more details)?


For the majority of the documents I am working on, the answer to question
(1) would be yes.  The answer to question (2) would be quite often no.

Based on my interpretation of the policy RFCs, I am in full compliance
with language and spirit of the policy.  I'm not doing anything fishy.  I
just don't talk about third party IPR, which is my right under the IETF's
IPR policy.  However, by providing answers to questions (1) and (2), the
IESG would receive a signal that it is not entitled to receive (more
precisely: that I'm not required to send, and not willing to send
voluntarily, as it could get me personally into trouble), namely that
there may be patents related to a document which the discloser is not
willing, AND not obligated, to talk about.

This is a policy change through the backdoor.  Policy changes through the
backdoor are bad.

My suggestion was aimed to bring the template in compliance with what I
believe is language and spirit of the policy.

Thanks,
Stephan



>
>You may, of course, ask the question of your working group in any way
>you like.  But I suggest you ask it in a way that allows you to
>accurately answer the question asked in the PROTO template.
>
>Barry, incoming Applications AD
>
>> -------- Original Message --------
>> From: Stephan Wenger [mailto:stewe@stewe.org]
>> Sent: Sunday, March 18, 2012 7:03 PM
>> To: Roni Even; 'IETF AVTCore WG'; payload@ietf.org
>> Cc: 'Magnus Westerlund'
>> Subject: Re: [AVTCORE] (no subject)
>>
>> Hi,
>>
>> There are many cases, where the answer to the first question is Yes, the
>> answer to the second question is No, and people would still be in
>>compliance
>> with the assorted policy RFCs.  The reason is that disclosure is not
>> required in many cases; for example, when the IPR in question is not
>>owned
>> by them or their employers.
>>
>>
>>
>> Suggest that the second question should be something like:
>>
>> "
>>
>> If so,
>>
>> has this IPR been disclosed when so required for in compliance with IETF
>> IPR rules (see RFCs
>>
>> 3979, 4879, 3669 and 5378 for more details)?
>>
>> "
>>
>>
>>
>> Stephan
>>
>>
>>
>> From: Roni Even <ron.even.tlv@gmail.com>
>> Date: Sun, 18 Mar 2012 18:33:53 +0200
>> To: 'IETF AVTCore WG' <avt@ietf.org>, <payload@ietf.org>
>> Cc: 'Magnus Westerlund' <magnus.westerlund@ericsson.com>
>> Subject: [AVTCORE] (no subject)
>>
>>
>>
>> Hi,
>>
>>
>>
>> The document write-up template for sending documents to publication has
>> changed.  In particular, we need to poll authors on their compliance
>>with
>> IETF IPR rules prior to moving a document to the publication in the WG
>> process. See http://www.ietf.org/iesg/template/doc-writeup.html
>>question 7.
>>
>>
>>
>> We plan to send the following email when a WG document goes to WG last
>> call.
>>
>>
>>
>>
>>
>>
>>
>> Please let us know if you have any comments on this plan.
>>
>>
>>
>> Roni Even
>>
>> AVTCore and Payload co-chair
>>
>>
>>
>> -----------------------------------------------------------------
>>
>>
>>
>> To: <list all authors and contributors>
>>
>> Cc: AD; AVTcore/Payload WG
>>
>>
>>
>> Subject: Regarding IPR on <insert document name>
>>
>>
>>
>> Are you aware of any IPR that applies to <insert document name>? If so,
>>
>> has this IPR been disclosed in compliance with IETF IPR rules (see RFCs
>>
>> 3979, 4879, 3669 and 5378 for more details)?
>>
>>
>>
>> If you are listed as a document author or contributor please answer the
>>
>> above by responding to this email regardless of whether or not you are
>>
>> aware of any relevant IPR.  This document will not advance to the next
>>
>> stage until a response has been received from each author and listed
>>
>> contributor.
>>
>>
>>
>> If you are on the AVTcore/payload WG email list but are not listed as an
>> author or contributor, we remind you of your obligations under the IETF
>>IPR
>> rules which encourages you to notify the IETF if you are aware of IPR of
>> others on an IETF contribution, or to refrain from participating in any
>> contribution or discussion related to your undisclosed IPR.  For more
>> information, please see the RFCs listed above and
>>
>> http://trac.tools.ietf.org/group/iesg/trac/wiki/IntellectualProperty.
>>
>>
>>
>>
>>
>> _______________________________________________ Audio/Video Transport
>>Core
>> Maintenance avt@ietf.org https://www.ietf.org/mailman/listinfo/avt
>



From barryleiba@gmail.com  Wed Mar 21 11:42:41 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 979C421F8615; Wed, 21 Mar 2012 11:42:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.99
X-Spam-Level: 
X-Spam-Status: No, score=-102.99 tagged_above=-999 required=5 tests=[AWL=-0.013, 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 cjSL1CSZYhzm; Wed, 21 Mar 2012 11:42:40 -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 4735C21F8603; Wed, 21 Mar 2012 11:42:40 -0700 (PDT)
Received: by obbtb4 with SMTP id tb4so1014350obb.31 for <multiple recipients>; Wed, 21 Mar 2012 11:42:39 -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 :content-transfer-encoding; bh=UrpwMOQ+pqit3EsiBfhk2mWQl27fOAzRwXxct8BRIgc=; b=Cs9B+BwfsrULbR5d6qitBJdcnJ9CSctcstjdqGfoIlAIl5nr/bLkWA82udSOjTrZLa Qj857hIsFDnHhOgs0cw3xLXYWArLQB+Z8DXQd0iE8JWHQrhCTKzoRf2jC6bSl5X7IBtb PLjaGtFBqDjrujopiAs3l+52UT0UMZ0t+aVWXM8diCk8ME2jOlOuB6HA0d7WCQcd0SPU 1qXTrz2+RDJWipURUib1URFIkBLfUSFp3AuWwLDQUTD5eTgoDhh35AbR/r/+gyoyQEtE R7MBpDxjLWd96jJ31u0QuJHsQ7ihUl5c4ApwdQQBv/xI9CWhucDx0UWNRgBLlUm4ll5J r4kg==
MIME-Version: 1.0
Received: by 10.182.1.1 with SMTP id 1mr6058959obi.32.1332355359857; Wed, 21 Mar 2012 11:42:39 -0700 (PDT)
Sender: barryleiba@gmail.com
Received: by 10.60.165.72 with HTTP; Wed, 21 Mar 2012 11:42:39 -0700 (PDT)
In-Reply-To: <CB8FCF89.84B69%stewe@stewe.org>
References: <CALaySJJcP8ijZK6PyX8+3zpDSL3q47woWX0e__mcDtA=nD438w@mail.gmail.com> <CB8FCF89.84B69%stewe@stewe.org>
Date: Wed, 21 Mar 2012 14:42:39 -0400
X-Google-Sender-Auth: SCP7ELHnhbS0EgYui7f82OfNzlI
Message-ID: <CALaySJJXRnRPGk6Fc_q9V3x4h=4Vzm83Nj1bLqk-qfKN=_4w8A@mail.gmail.com>
Subject: Re: [AVTCORE] IPR requirements in document write-up
From: Barry Leiba <barryleiba@computer.org>
To: Stephan Wenger <stewe@stewe.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "ipr@ietf.org" <ipr@ietf.org>, "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: Wed, 21 Mar 2012 18:42:41 -0000

[I am removing the avt and payload WG lists from this, so they can
keep at their work; feel free to direct people from those lists to the
IETF discussion list.  And thanks for moving this to the right lists.]

Hi, Stephan.
I think we're mostly in agreement, then, judging from what you say.
The gap may be a misunderstanding of what the PROTO writeup is for; it
has two purposes:

1. To provide information to the IESG, which might be important for
the IESG to consider as it reviews the document.

2. To make sure the document shepherd (usually, but not always, one of
the working group chairs) has reviewed and considered certain things.

That means that the writeup is NOT meant to set or enforce policy, and
there aren't any "right" or "wrong" answers, except that "Oh, gee, I
never thought about that," is probably never right, and the response
to it should be to go think about it.

Note in particular that BCPs 78 & 79 and Note Well have legal
blessing, the PROTO template does not, and the writeup is not there to
be a legal document.

For reference, the writeup templates live here:
https://www.ietf.org/iesg/ (see the links at the bottom of the
right-hand column).  The two questions we're talking about are these:

   (7) Has each author confirmed that any and all appropriate IPR
   disclosures required for full conformance with the provisions of BCP 78
   and BCP 79 have already been filed. If not, explain why.

   (8) Has an IPR disclosure been filed that references this document?
   If so, summarize any WG discussion and conclusion regarding the IPR
   disclosures.

...and there was discussion of the wording of those questions within
the IESG and with the WG chairs before finalizing it.  For the record,
not all the chairs liked the wording that's there.

What the IESG wants in response to these questions is not just "Yes"
or "No", but (where appropriate) an explanation of what IPR-related
things happened with respect to the document the writeup is for.  If
there are no IPR issues, the writeup should say that: "There are no
known IPR issues with this document, and the shepherd has re-confirmed
that with the editors and the working group," or some such.

But t also could say something like this: "Shortly after the document
was adopted by the working group, participant Herkermer Biffelwogg
said that he was aware of some IPR that might cover the document.  The
working group decided to continue working on the document, no IPR
disclosure was ever filed, and Mr Biffelwogg says he has no further
information about any IPR claims."  Or perhaps this: "The Frobozz
Magic AVT Company filed an IPR disclosure on the -06 version of the
document."  Concerned about the timing of the disclosure, the working
group fought bitterly for a few weeks about it, but ultimately came to
rough consensus to accept the Frobozz terms and continue.  The
discussion resulted in some changes to the language in the draft, and
a few participants remain unhappy with the result.  No one has said
they intend to appeal the decision."

See what I'm getting at?  Information for the IESG, and making sure
that the shepherd is on top of things.  No policy changes, subtle or
blatant.  And that's true in general with the PROTO writeup.  There
are many places where a yes/no answer could instead be done as an
explanation that really gives us an idea of what happened and how the
working group came to the result that it did.  That information can
really help when the IESG members do their reviews, and perhaps have
similar questions that were long ago answered.

Barry

On Wed, Mar 21, 2012 at 14:09, Stephan Wenger <stewe@stewe.org> wrote:
> Hi Barry,
>
> Adding the IPRWG and ietf@ietf.
>
> For the benefit if "new" readers: This is about an updated proto shepherd
> writeup template, asking two questions about IPR that, IMO may not be in
> compliance with the IETF's IPR policy.
>
> I was not aware that the proto template had IESG blessing. =A0Still, I
> believe that the template text does not ask the right question, or, more
> specifically, is a suggestive question in that it appears (at least to me=
)
> to interpret the IETF's patent policy in a considerably more strict way
> than it is set out in the policy RFCs.
> I believe the IESG should reconsider the proto writeup.
> A few more comments inline
>
> On 3.21.2012 17:03 , "Barry Leiba" <barryleiba@computer.org> wrote:
>
>>> Thanks for the text, I will use it.
>>>
>>> Roni
>>
>>I recommend you do not, for a few reasons:
>>
>>1. You may not rewrite the PROTO template; that belongs to the IESG.
>
> Agreed (now that I'm aware of that this is an IESG-sanctioned template).
>
>>2. The question was worded as it is for a reason, and it should be
>>left that way. =A0The IESG wants to know whether there are any known IPR
>>claims, whether declarations have been made to and considered by the
>>working group, and whether formal IPR statements have been filed in
>>the system. =A0The middle one is as important as the last.
>
> Also agreed (with caveats, see below).
>
>>
>>3. Stephan is incorrect when he says this:
>>> The reason is that disclosure is not
>>> required in many cases; for example, when the IPR in question is not
>>>owned
>>> by them or their employers.
>>
>>If you are aware of IPR that you do not own, you may and you should
>>make a third-party disclosure.
>
> Barry, please read my language carefully. =A0Perhaps I should have
> capitalized REQUIRED, but the text is clear and inline with yours. =A0It'=
s
> MAY and SHOULD for third party disclosures. =A0But you are NOT *required*=
 to
> do so by policy; there is no MUST. =A0There are many good and valid reaso=
ns
> why there is no MUST (beyond that it's not in the policy docs). =A0And,
> third party disclosures are not even a widely used current practice. =A0J=
ust
> look at the (comparatively low) number of third party disclosures.
>
> Look, I do patent work as my day job. =A0I also do standards work =A0In m=
y
> current and previous job roles, I have looked at hundreds of patents of m=
y
> current or previous employers, as well as occasionally at third party
> patents. =A0Now, with this background, let's look at the template text ag=
ain
> (numerals by me):
>
> =A0 (1) Are you aware of any IPR that applies to <insert document name>?
> (2) If so,
> =A0 has this IPR been disclosed in compliance with IETF IPR rules (see RF=
Cs
> 3979,
> =A0 4879, 3669 and 5378 for more details)?
>
>
> For the majority of the documents I am working on, the answer to question
> (1) would be yes. =A0The answer to question (2) would be quite often no.
>
> Based on my interpretation of the policy RFCs, I am in full compliance
> with language and spirit of the policy. =A0I'm not doing anything fishy. =
=A0I
> just don't talk about third party IPR, which is my right under the IETF's
> IPR policy. =A0However, by providing answers to questions (1) and (2), th=
e
> IESG would receive a signal that it is not entitled to receive (more
> precisely: that I'm not required to send, and not willing to send
> voluntarily, as it could get me personally into trouble), namely that
> there may be patents related to a document which the discloser is not
> willing, AND not obligated, to talk about.
>
> This is a policy change through the backdoor. =A0Policy changes through t=
he
> backdoor are bad.
>
> My suggestion was aimed to bring the template in compliance with what I
> believe is language and spirit of the policy.
>
> Thanks,
> Stephan
>
>
>
>>
>>You may, of course, ask the question of your working group in any way
>>you like. =A0But I suggest you ask it in a way that allows you to
>>accurately answer the question asked in the PROTO template.
>>
>>Barry, incoming Applications AD
>>
>>> -------- Original Message --------
>>> From: Stephan Wenger [mailto:stewe@stewe.org]
>>> Sent: Sunday, March 18, 2012 7:03 PM
>>> To: Roni Even; 'IETF AVTCore WG'; payload@ietf.org
>>> Cc: 'Magnus Westerlund'
>>> Subject: Re: [AVTCORE] (no subject)
>>>
>>> Hi,
>>>
>>> There are many cases, where the answer to the first question is Yes, th=
e
>>> answer to the second question is No, and people would still be in
>>>compliance
>>> with the assorted policy RFCs. =A0The reason is that disclosure is not
>>> required in many cases; for example, when the IPR in question is not
>>>owned
>>> by them or their employers.
>>>
>>>
>>>
>>> Suggest that the second question should be something like:
>>>
>>> "
>>>
>>> If so,
>>>
>>> has this IPR been disclosed when so required for in compliance with IET=
F
>>> IPR rules (see RFCs
>>>
>>> 3979, 4879, 3669 and 5378 for more details)?
>>>
>>> "
>>>
>>>
>>>
>>> Stephan
>>>
>>>
>>>
>>> From: Roni Even <ron.even.tlv@gmail.com>
>>> Date: Sun, 18 Mar 2012 18:33:53 +0200
>>> To: 'IETF AVTCore WG' <avt@ietf.org>, <payload@ietf.org>
>>> Cc: 'Magnus Westerlund' <magnus.westerlund@ericsson.com>
>>> Subject: [AVTCORE] (no subject)
>>>
>>>
>>>
>>> Hi,
>>>
>>>
>>>
>>> The document write-up template for sending documents to publication has
>>> changed. =A0In particular, we need to poll authors on their compliance
>>>with
>>> IETF IPR rules prior to moving a document to the publication in the WG
>>> process. See http://www.ietf.org/iesg/template/doc-writeup.html
>>>question 7.
>>>
>>>
>>>
>>> We plan to send the following email when a WG document goes to WG last
>>> call.
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> Please let us know if you have any comments on this plan.
>>>
>>>
>>>
>>> Roni Even
>>>
>>> AVTCore and Payload co-chair
>>>
>>>
>>>
>>> -----------------------------------------------------------------
>>>
>>>
>>>
>>> To: <list all authors and contributors>
>>>
>>> Cc: AD; AVTcore/Payload WG
>>>
>>>
>>>
>>> Subject: Regarding IPR on <insert document name>
>>>
>>>
>>>
>>> Are you aware of any IPR that applies to <insert document name>? If so,
>>>
>>> has this IPR been disclosed in compliance with IETF IPR rules (see RFCs
>>>
>>> 3979, 4879, 3669 and 5378 for more details)?
>>>
>>>
>>>
>>> If you are listed as a document author or contributor please answer the
>>>
>>> above by responding to this email regardless of whether or not you are
>>>
>>> aware of any relevant IPR. =A0This document will not advance to the nex=
t
>>>
>>> stage until a response has been received from each author and listed
>>>
>>> contributor.
>>>
>>>
>>>
>>> If you are on the AVTcore/payload WG email list but are not listed as a=
n
>>> author or contributor, we remind you of your obligations under the IETF
>>>IPR
>>> rules which encourages you to notify the IETF if you are aware of IPR o=
f
>>> others on an IETF contribution, or to refrain from participating in any
>>> contribution or discussion related to your undisclosed IPR. =A0For more
>>> information, please see the RFCs listed above and
>>>
>>> http://trac.tools.ietf.org/group/iesg/trac/wiki/IntellectualProperty.
>>>
>>>
>>>
>>>
>>>
>>> _______________________________________________ Audio/Video Transport
>>>Core
>>> Maintenance avt@ietf.org https://www.ietf.org/mailman/listinfo/avt

From simon@josefsson.org  Wed Mar 21 11:59:59 2012
Return-Path: <simon@josefsson.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B190821F8564; Wed, 21 Mar 2012 11:59:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.9
X-Spam-Level: 
X-Spam-Status: No, score=-102.9 tagged_above=-999 required=5 tests=[AWL=-0.991, BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, GB_I_LETTER=-2, HELO_MISMATCH_COM=0.553, HOST_EQ_STATICB=1.372, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id On8Y+BGwvQxg; Wed, 21 Mar 2012 11:59:59 -0700 (PDT)
Received: from yxa-v.extundo.com (static-213-115-179-173.sme.bredbandsbolaget.se [213.115.179.173]) by ietfa.amsl.com (Postfix) with ESMTP id D34DD21F8555; Wed, 21 Mar 2012 11:59:57 -0700 (PDT)
Received: from latte.josefsson.org (static-213-115-179-130.sme.bredbandsbolaget.se [213.115.179.130]) (authenticated bits=0) by yxa-v.extundo.com (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id q2LIxDpc006028 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Wed, 21 Mar 2012 19:59:14 +0100
From: Simon Josefsson <simon@josefsson.org>
To: Stephan Wenger <stewe@stewe.org>
Subject: Re: [AVTCORE] IPR requirements in document write-up
References: <CALaySJJcP8ijZK6PyX8+3zpDSL3q47woWX0e__mcDtA=nD438w@mail.gmail.com> <CB8FCF89.84B69%stewe@stewe.org>
OpenPGP: id=B565716F; url=http://josefsson.org/key.txt
X-Hashcash: 1:22:120321:stewe@stewe.org::Vzbh9oFczpoonGjO:JlV
X-Hashcash: 1:22:120321:iesg@ietf.org::1t4rL2u8gTq2lgYm:2+Gr
X-Hashcash: 1:22:120321:ipr@ietf.org::25ffxsWrf5VX2wtv:A4+6
X-Hashcash: 1:22:120321:barryleiba@computer.org::1OqKn1j+wkJ0m70i:G+/I
X-Hashcash: 1:22:120321:payload@ietf.org::e5Jf6SPh3OYwi0qT:ZhLs
X-Hashcash: 1:22:120321:avt@ietf.org::xxWzSK0ZStnqfbZt:qVwu
X-Hashcash: 1:22:120321:ietf@ietf.org::wz6szIOpPs/uFY/j:sE4R
Date: Wed, 21 Mar 2012 19:59:13 +0100
In-Reply-To: <CB8FCF89.84B69%stewe@stewe.org> (Stephan Wenger's message of "Wed, 21 Mar 2012 18:09:09 +0000")
Message-ID: <87wr6dye4e.fsf@latte.josefsson.org>
User-Agent: Gnus/5.130004 (Ma Gnus v0.4) Emacs/24.0.94 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
X-Virus-Scanned: clamav-milter 0.97.3 at yxa-v
X-Virus-Status: Clean
Cc: "ipr@ietf.org" <ipr@ietf.org>, "avt@ietf.org" <avt@ietf.org>, "payload@ietf.org" <payload@ietf.org>, "iesg@ietf.org" <iesg@ietf.org>, Barry Leiba <barryleiba@computer.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Mar 2012 18:59:59 -0000

Stephan Wenger <stewe@stewe.org> writes:

>    (1) Are you aware of any IPR that applies to <insert document name>?
> (2) If so,
>    has this IPR been disclosed in compliance with IETF IPR rules (see RFCs
> 3979, 
>    4879, 3669 and 5378 for more details)?
>
>
> For the majority of the documents I am working on, the answer to question
> (1) would be yes.  The answer to question (2) would be quite often no.
>
> Based on my interpretation of the policy RFCs, I am in full compliance
> with language and spirit of the policy.  I'm not doing anything fishy.  I
> just don't talk about third party IPR, which is my right under the IETF's
> IPR policy.

RFC 3669 section 5.7:

https://tools.ietf.org/html/rfc3669#section-5.7

says for example

   It is good to notify the IETF of relevant IPR claims even when they
   are not one's own, and [6] says to do so "as soon as possible".

My interpretation has always been that partcipants are strongly
encouraged to notify about third party patents.  Withholding such
information seems contrary to the spirit even if not the letter of the
guidelines.

There are additional advice given here:

https://tools.ietf.org/html/rfc3669#section-5.7.1

/Simon

From ron.even.tlv@gmail.com  Wed Mar 21 12:29:18 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 7E57921F8600; Wed, 21 Mar 2012 12:29:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.354
X-Spam-Level: 
X-Spam-Status: No, score=-3.354 tagged_above=-999 required=5 tests=[AWL=0.245,  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 op4ID3xon62c; Wed, 21 Mar 2012 12:29:17 -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 69A0A21F85EE; Wed, 21 Mar 2012 12:29:16 -0700 (PDT)
Received: by werb10 with SMTP id b10so1470041wer.31 for <multiple recipients>; Wed, 21 Mar 2012 12:29:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-type:content-transfer-encoding:x-mailer :thread-index:content-language; bh=8M06T1LDd/TPgdH2RA279fMO1ThA85Iswd6mLkeQ78I=; b=XaatEiUixT/R7R2wPOlTtIKKbE09BQbD+im7xdMTTDSKxwDprAShHlfzbivNhtQBGa 7SGL4ARTw4Dul8pt9qORwqf77EdF+d4Lo4yUX99AewP5i33LX2hfSWFRpu74PLve8amV 16U9H7EZePWpncIOS+i6odYUuF7kVl+goRkDX3LHdpUdU60b48gQkkSqffqI7snlICGW QVF8V2ddFhNWcDaV179eT/rhw11lE+uoIz0IqNn3MZlRwzyrU71uEkimSNxih6I9yJMH 7jRvWmCXtID0Yvo8rrAPoIXgNJXmkKc/5Od1bwoxjRV7WGBq74i9f2TvhXfHPZ5iy2pG RlYA==
Received: by 10.180.104.230 with SMTP id gh6mr11615308wib.22.1332358155089; Wed, 21 Mar 2012 12:29:15 -0700 (PDT)
Received: from windows8d787f9 (bzq-79-179-219-130.red.bezeqint.net. [79.179.219.130]) by mx.google.com with ESMTPS id e6sm6788219wix.8.2012.03.21.12.29.12 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 21 Mar 2012 12:29:14 -0700 (PDT)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: "'Barry Leiba'" <barryleiba@computer.org>, "'Stephan Wenger'" <stewe@stewe.org>
References: <CALaySJJcP8ijZK6PyX8+3zpDSL3q47woWX0e__mcDtA=nD438w@mail.gmail.com>	<CB8FCF89.84B69%stewe@stewe.org> <CALaySJJXRnRPGk6Fc_q9V3x4h=4Vzm83Nj1bLqk-qfKN=_4w8A@mail.gmail.com>
In-Reply-To: <CALaySJJXRnRPGk6Fc_q9V3x4h=4Vzm83Nj1bLqk-qfKN=_4w8A@mail.gmail.com>
Subject: RE: [AVTCORE] IPR requirements in document write-up
Date: Wed, 21 Mar 2012 21:28:10 +0200
Message-ID: <4f6a2c0a.e64eb40a.3ae6.74cb@mx.google.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="windows-1255"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac0HknMFu7EYWSO0R8CWDuWHSdO+9gABV1GQ
Content-Language: en-us
Cc: 'IETF' <ietf@ietf.org>, ipr@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: Wed, 21 Mar 2012 19:29:18 -0000

Hi Barry,
I read your response and it is OK as long as the Shephard has to respond =
to
question 8 and inform what happened in the WG. My reading of question 7 =
is
that the document shepherd have to ask the authors to confirm  the IPR
status to their knowledge which is different than just reporting what =
was
discussed in the WG and which IP statements were submitted. Did I
mis-understand question 7.
This is why I was trying to draft the question to ask the documents =
authors
in order to be able to reply to question 7. I was not trying to change =
the
proto itself.
Thanks
Roni

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf =
Of
> Barry Leiba
> Sent: Wednesday, March 21, 2012 8:43 PM
> To: Stephan Wenger
> Cc: ipr@ietf.org; iesg@ietf.org; IETF
> Subject: Re: [AVTCORE] IPR requirements in document write-up
>=20
> [I am removing the avt and payload WG lists from this, so they can =
keep
> at their work; feel free to direct people from those lists to the IETF
> discussion list.  And thanks for moving this to the right lists.]
>=20
> Hi, Stephan.
> I think we're mostly in agreement, then, judging from what you say.
> The gap may be a misunderstanding of what the PROTO writeup is for; it
> has two purposes:
>=20
> 1. To provide information to the IESG, which might be important for =
the
> IESG to consider as it reviews the document.
>=20
> 2. To make sure the document shepherd (usually, but not always, one of
> the working group chairs) has reviewed and considered certain things.
>=20
> That means that the writeup is NOT meant to set or enforce policy, and
> there aren't any "right" or "wrong" answers, except that "Oh, gee, I
> never thought about that," is probably never right, and the response =
to
> it should be to go think about it.
>=20
> Note in particular that BCPs 78 & 79 and Note Well have legal =
blessing,
> the PROTO template does not, and the writeup is not there to be a =
legal
> document.
>=20
> For reference, the writeup templates live here:
> https://www.ietf.org/iesg/ (see the links at the bottom of the right-
> hand column).  The two questions we're talking about are these:
>=20
>    (7) Has each author confirmed that any and all appropriate IPR
>    disclosures required for full conformance with the provisions of =
BCP
> 78
>    and BCP 79 have already been filed. If not, explain why.
>=20
>    (8) Has an IPR disclosure been filed that references this document?
>    If so, summarize any WG discussion and conclusion regarding the IPR
>    disclosures.
>=20
> ...and there was discussion of the wording of those questions within
> the IESG and with the WG chairs before finalizing it.  For the record,
> not all the chairs liked the wording that's there.
>=20
> What the IESG wants in response to these questions is not just "Yes"
> or "No", but (where appropriate) an explanation of what IPR-related
> things happened with respect to the document the writeup is for.  If
> there are no IPR issues, the writeup should say that: "There are no
> known IPR issues with this document, and the shepherd has re-confirmed
> that with the editors and the working group," or some such.
>=20
> But t also could say something like this: "Shortly after the document
> was adopted by the working group, participant Herkermer Biffelwogg =
said
> that he was aware of some IPR that might cover the document.  The
> working group decided to continue working on the document, no IPR
> disclosure was ever filed, and Mr Biffelwogg says he has no further
> information about any IPR claims."  Or perhaps this: "The Frobozz =
Magic
> AVT Company filed an IPR disclosure on the -06 version of the
> document."  Concerned about the timing of the disclosure, the working
> group fought bitterly for a few weeks about it, but ultimately came to
> rough consensus to accept the Frobozz terms and continue.  The
> discussion resulted in some changes to the language in the draft, and =
a
> few participants remain unhappy with the result.  No one has said they
> intend to appeal the decision."
>=20
> See what I'm getting at?  Information for the IESG, and making sure
> that the shepherd is on top of things.  No policy changes, subtle or
> blatant.  And that's true in general with the PROTO writeup.  There =
are
> many places where a yes/no answer could instead be done as an
> explanation that really gives us an idea of what happened and how the
> working group came to the result that it did.  That information can
> really help when the IESG members do their reviews, and perhaps have
> similar questions that were long ago answered.
>=20
> Barry
>=20
> On Wed, Mar 21, 2012 at 14:09, Stephan Wenger <stewe@stewe.org> wrote:
> > Hi Barry,
> >
> > Adding the IPRWG and ietf@ietf.
> >
> > For the benefit if "new" readers: This is about an updated proto
> > shepherd writeup template, asking two questions about IPR that, IMO
> > may not be in compliance with the IETF's IPR policy.
> >
> > I was not aware that the proto template had IESG blessing. =A0Still, =
I
> > believe that the template text does not ask the right question, or,
> > more specifically, is a suggestive question in that it appears (at
> > least to me) to interpret the IETF's patent policy in a considerably
> > more strict way than it is set out in the policy RFCs.
> > I believe the IESG should reconsider the proto writeup.
> > A few more comments inline
> >
> > On 3.21.2012 17:03 , "Barry Leiba" <barryleiba@computer.org> wrote:
> >
> >>> Thanks for the text, I will use it.
> >>>
> >>> Roni
> >>
> >>I recommend you do not, for a few reasons:
> >>
> >>1. You may not rewrite the PROTO template; that belongs to the IESG.
> >
> > Agreed (now that I'm aware of that this is an IESG-sanctioned
> template).
> >
> >>2. The question was worded as it is for a reason, and it should be
> >>left that way. =A0The IESG wants to know whether there are any known
> IPR
> >>claims, whether declarations have been made to and considered by the
> >>working group, and whether formal IPR statements have been filed in
> >>the system. =A0The middle one is as important as the last.
> >
> > Also agreed (with caveats, see below).
> >
> >>
> >>3. Stephan is incorrect when he says this:
> >>> The reason is that disclosure is not  required in many cases; for
> >>>example, when the IPR in question is not owned  by them or their
> >>>employers.
> >>
> >>If you are aware of IPR that you do not own, you may and you should
> >>make a third-party disclosure.
> >
> > Barry, please read my language carefully. =A0Perhaps I should have
> > capitalized REQUIRED, but the text is clear and inline with yours.
> > It's MAY and SHOULD for third party disclosures. =A0But you are NOT
> > *required* to do so by policy; there is no MUST. =A0There are many =
good
> > and valid reasons why there is no MUST (beyond that it's not in the
> > policy docs). =A0And, third party disclosures are not even a widely
> used
> > current practice. =A0Just look at the (comparatively low) number of
> third party disclosures.
> >
> > Look, I do patent work as my day job. =A0I also do standards work =
=A0In
> my
> > current and previous job roles, I have looked at hundreds of patents
> > of my current or previous employers, as well as occasionally at =
third
> > party patents. =A0Now, with this background, let's look at the =
template
> > text again (numerals by me):
> >
> > =A0 (1) Are you aware of any IPR that applies to <insert document
> name>?
> > (2) If so,
> > =A0 has this IPR been disclosed in compliance with IETF IPR rules =
(see
> > RFCs 3979,
> > =A0 4879, 3669 and 5378 for more details)?
> >
> >
> > For the majority of the documents I am working on, the answer to
> > question
> > (1) would be yes. =A0The answer to question (2) would be quite often
> no.
> >
> > Based on my interpretation of the policy RFCs, I am in full
> compliance
> > with language and spirit of the policy. =A0I'm not doing anything
> fishy.
> > I just don't talk about third party IPR, which is my right under the
> > IETF's IPR policy. =A0However, by providing answers to questions (1)
> and
> > (2), the IESG would receive a signal that it is not entitled to
> > receive (more
> > precisely: that I'm not required to send, and not willing to send
> > voluntarily, as it could get me personally into trouble), namely =
that
> > there may be patents related to a document which the discloser is =
not
> > willing, AND not obligated, to talk about.
> >
> > This is a policy change through the backdoor. =A0Policy changes =
through
> > the backdoor are bad.
> >
> > My suggestion was aimed to bring the template in compliance with =
what
> > I believe is language and spirit of the policy.
> >
> > Thanks,
> > Stephan
> >
> >
> >
> >>
> >>You may, of course, ask the question of your working group in any =
way
> >>you like. =A0But I suggest you ask it in a way that allows you to
> >>accurately answer the question asked in the PROTO template.
> >>
> >>Barry, incoming Applications AD
> >>
> >>> -------- Original Message --------
> >>> From: Stephan Wenger [mailto:stewe@stewe.org]
> >>> Sent: Sunday, March 18, 2012 7:03 PM
> >>> To: Roni Even; 'IETF AVTCore WG'; payload@ietf.org
> >>> Cc: 'Magnus Westerlund'
> >>> Subject: Re: [AVTCORE] (no subject)
> >>>
> >>> Hi,
> >>>
> >>> There are many cases, where the answer to the first question is
> Yes,
> >>>the  answer to the second question is No, and people would still be
> >>>in compliance  with the assorted policy RFCs. =A0The reason is that
> >>>disclosure is not  required in many cases; for example, when the =
IPR
> >>>in question is not owned  by them or their employers.
> >>>
> >>>
> >>>
> >>> Suggest that the second question should be something like:
> >>>
> >>> "
> >>>
> >>> If so,
> >>>
> >>> has this IPR been disclosed when so required for in compliance =
with
> >>> IETF IPR rules (see RFCs
> >>>
> >>> 3979, 4879, 3669 and 5378 for more details)?
> >>>
> >>> "
> >>>
> >>>
> >>>
> >>> Stephan
> >>>
> >>>
> >>>
> >>> From: Roni Even <ron.even.tlv@gmail.com>
> >>> Date: Sun, 18 Mar 2012 18:33:53 +0200
> >>> To: 'IETF AVTCore WG' <avt@ietf.org>, <payload@ietf.org>
> >>> Cc: 'Magnus Westerlund' <magnus.westerlund@ericsson.com>
> >>> Subject: [AVTCORE] (no subject)
> >>>
> >>>
> >>>
> >>> Hi,
> >>>
> >>>
> >>>
> >>> The document write-up template for sending documents to =
publication
> >>>has  changed. =A0In particular, we need to poll authors on their
> >>>compliance with  IETF IPR rules prior to moving a document to the
> >>>publication in the WG  process. See
> >>>http://www.ietf.org/iesg/template/doc-writeup.html
> >>>question 7.
> >>>
> >>>
> >>>
> >>> We plan to send the following email when a WG document goes to WG
> >>> last call.
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>> Please let us know if you have any comments on this plan.
> >>>
> >>>
> >>>
> >>> Roni Even
> >>>
> >>> AVTCore and Payload co-chair
> >>>
> >>>
> >>>
> >>> -----------------------------------------------------------------
> >>>
> >>>
> >>>
> >>> To: <list all authors and contributors>
> >>>
> >>> Cc: AD; AVTcore/Payload WG
> >>>
> >>>
> >>>
> >>> Subject: Regarding IPR on <insert document name>
> >>>
> >>>
> >>>
> >>> Are you aware of any IPR that applies to <insert document name>? =
If
> >>> so,
> >>>
> >>> has this IPR been disclosed in compliance with IETF IPR rules (see
> >>> RFCs
> >>>
> >>> 3979, 4879, 3669 and 5378 for more details)?
> >>>
> >>>
> >>>
> >>> If you are listed as a document author or contributor please =
answer
> >>> the
> >>>
> >>> above by responding to this email regardless of whether or not you
> >>> are
> >>>
> >>> aware of any relevant IPR. =A0This document will not advance to =
the
> >>> next
> >>>
> >>> stage until a response has been received from each author and
> listed
> >>>
> >>> contributor.
> >>>
> >>>
> >>>
> >>> If you are on the AVTcore/payload WG email list but are not listed
> >>>as an  author or contributor, we remind you of your obligations
> under
> >>>the IETF IPR  rules which encourages you to notify the IETF if you
> >>>are aware of IPR of  others on an IETF contribution, or to refrain
> >>>from participating in any  contribution or discussion related to
> your
> >>>undisclosed IPR. =A0For more  information, please see the RFCs =
listed
> >>>above and
> >>>
> >>>
> http://trac.tools.ietf.org/group/iesg/trac/wiki/IntellectualProperty.
> >>>
> >>>
> >>>
> >>>
> >>>
> >>> _______________________________________________ Audio/Video
> >>>Transport Core  Maintenance avt@ietf.org
> >>>https://www.ietf.org/mailman/listinfo/avt


From barryleiba@gmail.com  Wed Mar 21 12:50: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 821ED21E8083; Wed, 21 Mar 2012 12:50:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.99
X-Spam-Level: 
X-Spam-Status: No, score=-102.99 tagged_above=-999 required=5 tests=[AWL=-0.013, 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 vcmfE3+0ZKZw; Wed, 21 Mar 2012 12:50:41 -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 A455421E80BD; Wed, 21 Mar 2012 12:50:41 -0700 (PDT)
Received: by obbtb4 with SMTP id tb4so1056552obb.31 for <multiple recipients>; Wed, 21 Mar 2012 12:50:41 -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 :content-transfer-encoding; bh=kmsNYOy4akkiCeTxsBK5u/BAmtoEqNZAg0GpIlXXtVk=; b=LBzpWwztzpVY9DxKgiLHTcvNa2lLxW4dks7tYoicrRtelE4g2iPg0gfwG/b6BTVKzk GetVHNC+YaFQfd8emqmOrKySwjEcs6AYsVhx1dkyMF/J0bSqgt07nsEkPIfckT4eHCaK CC56CXpGtceCZpzGFAi0H/T9JX2qf/TMvjj/L8ULyrLYJSjZx7k/Z2JIrCPk4+Ib+QPG 4CfMxIvOQ0pSx3QqrVxRJpGYKFJT2f7vnI+lLw0W84vIvk8wKB8pv1GJFnaAx/ku8OxS gsCcUB5baJAKn8SqbjCk2gLuEIIeZaqqQUmS20buqe8NkUYp7qx82hT2zrtTU95oKs5O oUdA==
MIME-Version: 1.0
Received: by 10.182.231.41 with SMTP id td9mr6336433obc.22.1332359441131; Wed, 21 Mar 2012 12:50:41 -0700 (PDT)
Sender: barryleiba@gmail.com
Received: by 10.60.165.72 with HTTP; Wed, 21 Mar 2012 12:50:41 -0700 (PDT)
In-Reply-To: <4f6a2c0a.e64eb40a.3ae6.74cb@mx.google.com>
References: <CALaySJJcP8ijZK6PyX8+3zpDSL3q47woWX0e__mcDtA=nD438w@mail.gmail.com> <CB8FCF89.84B69%stewe@stewe.org> <CALaySJJXRnRPGk6Fc_q9V3x4h=4Vzm83Nj1bLqk-qfKN=_4w8A@mail.gmail.com> <4f6a2c0a.e64eb40a.3ae6.74cb@mx.google.com>
Date: Wed, 21 Mar 2012 15:50:41 -0400
X-Google-Sender-Auth: v8sjayxTzIJW0LT6ZV8AHYLoLfw
Message-ID: <CALaySJJa0TL4uF5DXm_psQ-QwrrCCRgDbDOt7fkO4k8LpcsCiw@mail.gmail.com>
Subject: Re: [AVTCORE] IPR requirements in document write-up
From: Barry Leiba <barryleiba@computer.org>
To: Roni Even <ron.even.tlv@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: IETF <ietf@ietf.org>, ipr@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: Wed, 21 Mar 2012 19:50:45 -0000

> My reading of question 7 is
> that the document shepherd have to ask the authors to confirm =A0the IPR
> status to their knowledge which is different than just reporting what was
> discussed in the WG and which IP statements were submitted. Did I
> mis-understand question 7.

You're correct: question 7 is asking you to confirm with the document
editors, to make sure nothing's been forgotten.

> This is why I was trying to draft the question to ask the documents autho=
rs
> in order to be able to reply to question 7. I was not trying to change th=
e
> proto itself.

I understand that you weren't trying to change the PROTO template; I
thought Stephan was, and, as he's said, he's now aware of where it
comes from.  (And, by the way, it's always possible to make
suggestions to the IESG about changes to the writeup.)

As I said in my first note, you're welcome to ask the question in any
manner you like, as long as you can comfortably complete the PROTO
writeup.

The way I've handled it since the change was to ask openly on the WG
mailing list.  I've asked the editors *and* the participants, but only
expected explicit replies (off list) from the editors.  This way, all
participants were reminded to let the working group know about IPR
they're aware of ["reasonably and personally known to the participant"
is the specific text from BCP 79, in case you want to use that].

How you, as a chair, do it, is up to you.  And I suggest that "Yes,"
is a reasonable answer to question 7, and question 8 is the one that
wants more words.

Barry

From snark17@gmail.com  Wed Mar 21 13:15:28 2012
Return-Path: <snark17@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6A25521F8714 for <ietf@ietfa.amsl.com>; Wed, 21 Mar 2012 13:15:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.299
X-Spam-Level: 
X-Spam-Status: No, score=-3.299 tagged_above=-999 required=5 tests=[AWL=0.300,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PZ85TCHkXyEW for <ietf@ietfa.amsl.com>; Wed, 21 Mar 2012 13:15:28 -0700 (PDT)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id CB6A821F8710 for <ietf@ietf.org>; Wed, 21 Mar 2012 13:15:27 -0700 (PDT)
Received: by vcbfk13 with SMTP id fk13so1676947vcb.31 for <ietf@ietf.org>; Wed, 21 Mar 2012 13:15:27 -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=wUyshvhE4tpaC/a+gy5GS6R2krk7MlxNus+9iOg5aRM=; b=L4ff9tmwuM4Gehqgg7ZkMMdEcmNI/xNjZpf2euB+GC3yzYTZu6Nte0jIA58VEuXZtr q/gaMCb06yqYLYDTan9JEELCDf2i2dAvOpVq6p8uHayQPlV02UqwH6AOW/mOz2e5o+8k HgsUcLgIIuHlfoea+tZX5B+yk8RDPXcpgt6vL3Sonaeahqrda5kxXoVdEasgIA9+d9Wr 6r1yc4MGn2zIDU08DX4Io2CZdF/arVoZk11n4zhLWiVTcBzy3sMDvrbjA+HTA+swhyHo hlb8KwFdzADWnQR+ne2W3YvX76lgOrVrqfHkG4vmRKph7Q0XdEvE1QDPRnh76nG0ofme Nxwg==
MIME-Version: 1.0
Received: by 10.52.240.232 with SMTP id wd8mr2080547vdc.96.1332360927179; Wed, 21 Mar 2012 13:15:27 -0700 (PDT)
Received: by 10.52.99.8 with HTTP; Wed, 21 Mar 2012 13:15:27 -0700 (PDT)
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B22726A0996@DC-US1MBEX4.global.avaya.com>
References: <82A794CE-B328-475F-9300-1B6BE628F7E3@sabahattin-gucukoglu.com> <CD5674C3CD99574EBA7432465FC13C1B22726A0994@DC-US1MBEX4.global.avaya.com> <CAGHVWBgnF49UYSaL3awXf4Y+wxvmUTFi9xYRVCZ8WL1nFZp1Aw@mail.gmail.com> <CD5674C3CD99574EBA7432465FC13C1B22726A0996@DC-US1MBEX4.global.avaya.com>
Date: Wed, 21 Mar 2012 15:15:27 -0500
Message-ID: <CAGHVWBh=vKnc343ux6YFRkL=G+rH8Up2fGKDNiDSPbxMwyQvtA@mail.gmail.com>
Subject: Re: IPv6 Zone Identifiers Considered Hateful
From: Craig Finseth <snark17@gmail.com>
To: "Worley, Dale R (Dale)" <dworley@avaya.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: Sabahattin Gucukoglu <mail-dated-1334746550.15c4ac@sabahattin-gucukoglu.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: Wed, 21 Mar 2012 20:15:28 -0000

On Wed, Mar 21, 2012 at 12:57 PM, Worley, Dale R (Dale)
<dworley@avaya.com> wrote:
>> From: Craig Finseth [snark17@gmail.com]
>>
>> You've just rediscovered what the "link local" part of the link-local
>> address means: the address is local to the link! =A0It is not globally
>> unique or even unique within a host, it is just unique within a link.
>
> Actually, it's globally *unique*, because it contains the MAC address.
> The problem is that it's not *routable*, even within the context of a
> single host. =A0And unless you give an application on the host guidance,
> it depends on host-context routing to get its output packets to the
> correct wire. =A0It's hard to remain aware that host-context routing is
> important, because it's almost always work.

Well, it's globally unique to a host, not to an interface: the host
(in general) uses the same link-local address on all interfaces.
Thus, you can't tell from the address which interface it refers to.

--
Craig A. Finseth

From malcolm.betts@zte.com.cn  Wed Mar 21 13:33:31 2012
Return-Path: <malcolm.betts@zte.com.cn>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4400821F8603; Wed, 21 Mar 2012 13:33:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.838
X-Spam-Level: 
X-Spam-Status: No, score=-101.838 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_DOUBLE_IP_LOOSE=0.76,  USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WYWzFnsVI9cL; Wed, 21 Mar 2012 13:33:29 -0700 (PDT)
Received: from mx5.zte.com.cn (mx6.zte.com.cn [95.130.199.165]) by ietfa.amsl.com (Postfix) with ESMTP id DF4B821F8601; Wed, 21 Mar 2012 13:33:28 -0700 (PDT)
Received: from [10.30.17.100] by mx5.zte.com.cn with surfront esmtp id 12280301151118; Thu, 22 Mar 2012 03:59:13 +0800 (CST)
Received: from [10.30.3.21] by [192.168.168.16] with StormMail ESMTP id 33120.675403240; Thu, 22 Mar 2012 04:33:06 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse02.zte.com.cn with ESMTP id q2LKXBuw058348; Thu, 22 Mar 2012 04:33:11 +0800 (GMT-8) (envelope-from Malcolm.BETTS@zte.com.cn)
In-Reply-To: <4F5DB46F.10009@pi.nu>
References: <20120222151252.32262.82157.idtracker@ietfa.amsl.com>	<039f01ccf174$fe79d780$fb6d8680$@olddog.co.uk> <44F4E579A764584EA9BDFD07D0CA0813075C936F@tlvmail1>	<4F4B7EA2.7070305@cisco.com> <4F4B8A75.6000207@pi.nu> <4F5DB46F.10009@pi.nu>
To: Loa Andersson <loa@pi.nu>
Subject: Re: [PWE3] FW: Last Call:	<draft-betts-itu-oam-ach-code-point-03.txt>(Allocation of	an Associated Channel Code Point for Use byITU-T Ethernet	based OAM)	to Informational RFC
MIME-Version: 1.0
X-KeepSent: E57A943C:CA873F89-852579C8:006D6B01; type=4; name=$KeepSent
X-Mailer: Lotus Notes Release 8.5.1 September 28, 2009
Message-ID: <OFE57A943C.CA873F89-ON852579C8.006D6B01-852579C8.0070E507@zte.com.cn>
From: Malcolm.BETTS@zte.com.cn
Date: Wed, 21 Mar 2012 15:33:03 -0500
X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 8.5.1FP4|July 25, 2010) at 2012-03-22 04:33:11, Serialize complete at 2012-03-22 04:33:11
Content-Type: multipart/alternative; boundary="=_alternative 0070E506852579C8_="
X-MAIL: mse02.zte.com.cn q2LKXBuw058348
Cc: ietf-bounces@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Mar 2012 20:33:31 -0000

This is a multipart message in MIME format.
--=_alternative 0070E506852579C8_=
Content-Type: text/plain; charset="US-ASCII"

Loa,

Thank you for your comments and suggestions, please see in line below.

Regards,

Malcolm


ietf-bounces@ietf.org wrote on 12/03/2012 04:31:43 AM:

> Loa Andersson <loa@pi.nu> 
> Sent by: ietf-bounces@ietf.org
> 
> 12/03/2012 04:31 AM
> 
> To
> 
> ietf@ietf.org
> 
> cc
> 
> Subject
> 
> Re: [PWE3] FW: Last Call: <draft-betts-itu-oam-ach-code-
> point-03.txt>(Allocation of an Associated Channel Code Point for Use
> byITU-T Ethernet based OAM) to Informational RFC
> 
> All,
> 
> I've been asked to clarify thee comments in this mail, I done
> so by proposing new text to draft-betts-.
> 
> I hope this helps.
> 
> 
> Title
> =====
> 
> Comment: We want to assign a Associated Channel Type. The registry
> that it  will be assigned from is "Pseudowire Associated Channel
> Types"; however RFC 5586, makes the Channel Types generic and I
> think the title should be changed as follows:
> 
> OLD:
> Allocation of an Associated Channel Code Point for Use by ITU-T
> Ethernet based OAM
> 
> NEW:
> Allocation of an Generic Associated Channel Type for ITU-T
> MPLS-TP OAM
> 
> Note: Neither MPLS-TP or OAM are in the RFC Editors list of wellknown
> acronyms, therfore the title probably should be:
> 
> NEW:
> Allocation of an Generic Associated Channel Type for ITU-T
> MPLS Transport Profile Operation, Maintenance and Administration.
> 

MB: No objection to this change

> 
> Introduction - first paragraph
> ==============================
> 
> In the first paragraph of the introduction, there seems to be an
> oddity in the description of the role of the ietf-tp-oam-analysis
> document.  Instead of:
> 
> OLD
> "tools defined by the IETF [I-D.ietf-mpls-tp-oam-analysis], that
> are intended to meet the OAM functional requirements defined in
> [RFC5860]."
> 
> NEW:
> "tools described by the IETF [I-D.ietf-mpls-tp-oam-analysis], which
> are used to meet the OAM functional requirements defined
> in [RFC5860]."

MB: No objection to this change

> 
> Intrduction - second paragraph
> ==============================
> 
> The next paragraph in describing G.8113.1, stumbles over the current
> vs anticipated future state of G.8113.1 and its relationship to
> its antecedents.  I'm a bit un-certain about the correct terminology,
> but I think the following change would improve the document.
> 
> OLD:
> 
> The ITU-T has documented, in draft new Recommendation [G.8113.1], the
> use of Ethernet based OAM mechanisms, originally defined in [Y.1731],
> carried in the MPLS Generic Associated Channel (G-ACh). This approach
> requires the allocation of an ACH Type from the registry of ACH types
> maintained by IANA in order that the messages that will be described
> in [G.8113.1] can be identified by an implementation.
> 
> NEW:
> 
> "The ITU-T has Draft Recommendation [G.8113.1] documented MPLS OAM
> which as of this writing is undergoing the ITU-T Traditional
> Approval Process (TAP). This Recommendation builds upon Ethernet
> OAM as documented in [Y.1731]. The messages in [G.8113.1] are defined
> to be carried in a new Associated Channel Type in the MPLS Generaic
>   Associated Channel (G-Ach).  In order to carry these messages in an
> interoperable fashion, an Associated Channel Type from the IANA
> maintained registry "Pseudowire Associated Channel Types is to be
> used."

MB: Since the draft will not be published as an RFC until after G.8113.1 
is approved we can directly reference the approved Recommendation and I 
suggest that we modify paragraph to:


ITU-T Recommendation [G.8113.1] documents MPLS OAM. This Recommendation 
builds upon Ethernet OAM as documented in [Y.1731]. The messages in 
[G.8113.1] are defined to be carried in a new Associated Channel Type in 
the MPLS Generaic Associated Channel (G-Ach).  In order to carry these 
messages in an interoperable fashion, an Associated Channel Type from the 
IANA maintained registry "Pseudowire Associated Channel Types is to be 
used."


> 
> Note there are confusion around some of the Associated Channel
> acronyms that are refledted in this document.
> 
> ACh is Associated Channel
> ACH is Associated Chamnnel Header
> G-ACh is Generic Associated Channel
> 
> "ACH Type" is not used anywhere in IETF documents; we talk about
> Associated Channel Type or Generic Associated Channel Type
> (G-ACh Type).

MB: Thank you, I will fix this.

> 
> Introduction - third paragraph
> ==============================
> 
> In the third paragraph, there seems to be an unnecessary reference
> to experimental types.  When asking for a code point for a standard,
> it is not helped to bring up experimental code space.  Can we remove
> the text reading:
> 
> OLD:
> "without continuing to resorting to the use of an experimental
> ACH Type,"
> 
> NEW
> -

MB: I do not agree with the deletion of this text, these existing 
deployments, and the desire to migrate to an allocated code point, are 
part of the rational for requesting the code point.

> 
> 
> Section 2 - first paragraph
> ===========================
> 
> 
> 
> In section 2, the first sentence refers to Ethernet based OAM
> messages. As far as I know, the messages in G.8113.1 are either
> MPLS-TP OAM messages, or they are simply the OAM messages defined
> in G.8113.1.  The simplest path to clarity would seem to be to
> replace "Ethernet based OAM messages" in that sentence with
> "messages".
> 
> The second sentence of that paragraph does not seem to say anything
> we need to say.  Can we remove it?
> 
> OLD:
> 
>     The code point allocated by this document is intended to be used 
only
>     for Ethernet based OAM messages, defined in the ITU-T Recommendation
>     [G.8113.1], carried in the G-ACh . These Ethernet based OAM messages
>     and procedures, address the OAM functional requirements defined in
>     [RFC5860]. Other message types should not be carried behind this 
code
>     point.
> 
> NEW:
> 
>     The code point allocated by this document is intended to be used
>     only for OAM messages, defined in the ITU-T Recommendation
>     [G.8113.1], carried in the G-ACh . Other message types should not
>     be carried behind this Associated Channel Type.


MB: I do not agree with this proposed change. Other comments request that 
the restriction on the applicability of the code point is strengthened so 
I propose the following:

The code point allocated by this document should only be used for OAM 
messages, defined in the ITU-T Recommendation [G.8113.1], carried in the 
G-ACh. The messages and procedures carried behind this code point, are 
restricted to only those that the address the OAM functional requirements 
defined in [RFC5860]. Other message types should not be carried behind 
this code point.


> 
> Section 2 - second paragraph
> ============================
> 
> A matter of some clarity, can we change this paragrap like this:
> 
> OLD:
>     This code point may be used on any transport construct that uses
>     the G-ACh, e.g., MPLS-TP Sections, MPLS-TP LSPs or PWs.
> 
> NEW:
> 
>     The Generic Associated Channel Type assigned by this
>     document may be used on any transport construct that uses the
>     G-ACh, e.g., MPLS-TP Sections, MPLS-TP LSPs or PWs as specified
>     by G.8113.1.

MB: No objection to this change.

> 
> 
> Section 2 - third paragraph
> ===========================
> 
> With regard to revisions, which is what I think the third paragraph
> is about, I am not clear what you are trying to say.  A code point
> allocation must point to a stable referent.  If the desired referent
> changes, then process needs to be followed to make sure that the IANA
> is updated in accordance with IETF procedures.  Hence, I am left to
> the conclusion that the third paragraph is actually asking for
> something we can not do.  Can we remove that?
> 
> OLD:
>     All ITU-T Recommendations are subject to revisions. Therefore, the
>     code point allocated by this document may be used for future 
versions
>     of [G.8113.1].
> 
> NEW:
>     -
> 
> 

MB: I do not agree with the removal of this text:

The intention of this statement is to bring to the attention of the IETF 
the normal practice in the ITU of developing amendments to Recommendations 
to fully meet the functional requirements (e.g. adding pro-active loss 
measurement).  Normally any reference to ITU-T Rec G.8113.1 will 
automatically be directed to the current version (including any 
amendments). 

Only those interfaces that support G.8113.1 OAM will act on these OAM 
messages, any interface that does not support this G-ACh type will discard 
these OAM messages as defined in RFC5586.

Restricting the application of the code point to a specific version of 
Recommendation G.8113.1 would require the ITU to deviate from its normal 
process for enhancing Recommendations and would put the IETF back into the 
discussion for approval.



>---------------snip


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

--=_alternative 0070E506852579C8_=
Content-Type: text/html; charset="US-ASCII"

<font size=2 face="sans-serif">Loa,</font>
<br>
<br><font size=2 face="sans-serif">Thank you for your comments and suggestions,
please see in line below.</font>
<br>
<br><font size=2 face="sans-serif">Regards,</font>
<br>
<br><font size=2 face="sans-serif">Malcolm</font>
<br>
<br>
<br><tt><font size=2>ietf-bounces@ietf.org wrote on 12/03/2012 04:31:43
AM:<br>
<br>
&gt; Loa Andersson &lt;loa@pi.nu&gt; </font></tt>
<br><tt><font size=2>&gt; Sent by: ietf-bounces@ietf.org<br>
&gt; </font></tt>
<br><tt><font size=2>&gt; 12/03/2012 04:31 AM</font></tt>
<br><tt><font size=2>&gt; <br>
&gt; To</font></tt>
<br><tt><font size=2>&gt; <br>
&gt; ietf@ietf.org</font></tt>
<br><tt><font size=2>&gt; <br>
&gt; cc</font></tt>
<br><tt><font size=2>&gt; <br>
&gt; Subject</font></tt>
<br><tt><font size=2>&gt; <br>
&gt; Re: [PWE3] FW: Last Call: &lt;draft-betts-itu-oam-ach-code-<br>
&gt; point-03.txt&gt;(Allocation of an Associated Channel Code Point for
Use<br>
&gt; byITU-T Ethernet based OAM) to Informational RFC</font></tt>
<br><tt><font size=2>&gt; <br>
&gt; All,<br>
&gt; <br>
&gt; I've been asked to clarify thee comments in this mail, I done<br>
&gt; so by proposing new text to draft-betts-.<br>
&gt; <br>
&gt; I hope this helps.<br>
&gt; <br>
&gt; <br>
&gt; Title<br>
&gt; =====<br>
&gt; <br>
&gt; Comment: We want to assign a Associated Channel Type. The registry<br>
&gt; that it &nbsp;will be assigned from is &quot;Pseudowire Associated
Channel<br>
&gt; Types&quot;; however RFC 5586, makes the Channel Types generic and
I<br>
&gt; think the title should be changed as follows:<br>
&gt; <br>
&gt; OLD:<br>
&gt; Allocation of an Associated Channel Code Point for Use by ITU-T<br>
&gt; Ethernet based OAM<br>
&gt; <br>
&gt; NEW:<br>
&gt; Allocation of an Generic Associated Channel Type for ITU-T<br>
&gt; MPLS-TP OAM<br>
&gt; <br>
&gt; Note: Neither MPLS-TP or OAM are in the RFC Editors list of wellknown<br>
&gt; acronyms, therfore the title probably should be:<br>
&gt; <br>
&gt; NEW:<br>
&gt; Allocation of an Generic Associated Channel Type for ITU-T<br>
&gt; MPLS Transport Profile Operation, Maintenance and Administration.<br>
&gt; <br>
</font></tt>
<br><tt><font size=2>MB: No objection to this change</font></tt>
<br>
<br><tt><font size=2>&gt; <br>
&gt; Introduction - first paragraph<br>
&gt; ==============================<br>
&gt; <br>
&gt; In the first paragraph of the introduction, there seems to be an<br>
&gt; oddity in the description of the role of the ietf-tp-oam-analysis<br>
&gt; document. &nbsp;Instead of:<br>
&gt; <br>
&gt; OLD<br>
&gt; &quot;tools defined by the IETF [I-D.ietf-mpls-tp-oam-analysis], that<br>
&gt; are intended to meet the OAM functional requirements defined in<br>
&gt; [RFC5860].&quot;<br>
&gt; <br>
&gt; NEW:<br>
&gt; &quot;tools described by the IETF [I-D.ietf-mpls-tp-oam-analysis],
which<br>
&gt; are used to meet the OAM functional requirements defined<br>
&gt; in [RFC5860].&quot;<br>
</font></tt>
<br><tt><font size=2>MB: No objection to this change</font></tt>
<br>
<br><tt><font size=2>&gt; <br>
&gt; Intrduction - second paragraph<br>
&gt; ==============================<br>
&gt; <br>
&gt; The next paragraph in describing G.8113.1, stumbles over the current<br>
&gt; vs anticipated future state of G.8113.1 and its relationship to<br>
&gt; its antecedents. &nbsp;I'm a bit un-certain about the correct terminology,<br>
&gt; but I think the following change would improve the document.<br>
&gt; <br>
&gt; OLD:<br>
&gt; <br>
&gt; The ITU-T has documented, in draft new Recommendation [G.8113.1],
the<br>
&gt; use of Ethernet based OAM mechanisms, originally defined in [Y.1731],<br>
&gt; carried in the MPLS Generic Associated Channel (G-ACh). This approach<br>
&gt; requires the allocation of an ACH Type from the registry of ACH types<br>
&gt; maintained by IANA in order that the messages that will be described<br>
&gt; in [G.8113.1] can be identified by an implementation.<br>
&gt; <br>
&gt; NEW:<br>
&gt; <br>
&gt; &quot;The ITU-T has Draft Recommendation [G.8113.1] documented MPLS
OAM<br>
&gt; which as of this writing is undergoing the ITU-T Traditional<br>
&gt; Approval Process (TAP). This Recommendation builds upon Ethernet<br>
&gt; OAM as documented in [Y.1731]. The messages in [G.8113.1] are defined<br>
&gt; to be carried in a new Associated Channel Type in the MPLS Generaic<br>
&gt; &nbsp; Associated Channel (G-Ach). &nbsp;In order to carry these messages
in an<br>
&gt; interoperable fashion, an Associated Channel Type from the IANA<br>
&gt; maintained registry &quot;Pseudowire Associated Channel Types is to
be<br>
&gt; used.&quot;<br>
</font></tt>
<br><tt><font size=2>MB: Since the draft will not be published as an RFC
until after G.8113.1 is approved we can directly reference the approved
Recommendation and I suggest that we modify paragraph to:</font></tt>
<br>
<br>
<br><tt><font size=2>ITU-T Recommendation [G.8113.1] documents MPLS OAM.
This Recommendation builds upon Ethernet OAM as documented in [Y.1731].
The messages in [G.8113.1] are defined to be carried in a new Associated
Channel Type in the MPLS Generaic Associated Channel (G-Ach). &nbsp;In
order to carry these messages in an interoperable fashion, an Associated
Channel Type from the IANA maintained registry &quot;Pseudowire Associated
Channel Types is to be used.&quot;</font></tt>
<br>
<br>
<br><tt><font size=2>&gt; <br>
&gt; Note there are confusion around some of the Associated Channel<br>
&gt; acronyms that are refledted in this document.<br>
&gt; <br>
&gt; ACh is Associated Channel<br>
&gt; ACH is Associated Chamnnel Header<br>
&gt; G-ACh is Generic Associated Channel<br>
&gt; <br>
&gt; &quot;ACH Type&quot; is not used anywhere in IETF documents; we talk
about<br>
&gt; Associated Channel Type or Generic Associated Channel Type<br>
&gt; (G-ACh Type).<br>
</font></tt>
<br><tt><font size=2>MB: Thank you, I will fix this.</font></tt>
<br>
<br><tt><font size=2>&gt; <br>
&gt; Introduction - third paragraph<br>
&gt; ==============================<br>
&gt; <br>
&gt; In the third paragraph, there seems to be an unnecessary reference<br>
&gt; to experimental types. &nbsp;When asking for a code point for a standard,<br>
&gt; it is not helped to bring up experimental code space. &nbsp;Can we
remove<br>
&gt; the text reading:<br>
&gt; <br>
&gt; OLD:<br>
&gt; &quot;without continuing to resorting to the use of an experimental<br>
&gt; ACH Type,&quot;<br>
&gt; <br>
&gt; NEW<br>
&gt; -<br>
</font></tt>
<br><tt><font size=2>MB: I do not agree with the deletion of this text,
these existing deployments, and the desire to migrate to an allocated code
point, are part of the rational for requesting the code point.</font></tt>
<br>
<br><tt><font size=2>&gt; <br>
&gt; <br>
&gt; Section 2 - first paragraph<br>
&gt; ===========================<br>
&gt; <br>
&gt; <br>
&gt; <br>
&gt; In section 2, the first sentence refers to Ethernet based OAM<br>
&gt; messages. As far as I know, the messages in G.8113.1 are either<br>
&gt; MPLS-TP OAM messages, or they are simply the OAM messages defined<br>
&gt; in G.8113.1. &nbsp;The simplest path to clarity would seem to be to<br>
&gt; replace &quot;Ethernet based OAM messages&quot; in that sentence with<br>
&gt; &quot;messages&quot;.<br>
&gt; <br>
&gt; The second sentence of that paragraph does not seem to say anything<br>
&gt; we need to say. &nbsp;Can we remove it?<br>
&gt; <br>
&gt; OLD:<br>
&gt; <br>
&gt; &nbsp; &nbsp; The code point allocated by this document is intended
to be used only<br>
&gt; &nbsp; &nbsp; for Ethernet based OAM messages, defined in the ITU-T
Recommendation<br>
&gt; &nbsp; &nbsp; [G.8113.1], carried in the G-ACh . These Ethernet based
OAM messages<br>
&gt; &nbsp; &nbsp; and procedures, address the OAM functional requirements
defined in<br>
&gt; &nbsp; &nbsp; [RFC5860]. Other message types should not be carried
behind this code<br>
&gt; &nbsp; &nbsp; point.<br>
&gt; <br>
&gt; NEW:<br>
&gt; <br>
&gt; &nbsp; &nbsp; The code point allocated by this document is intended
to be used<br>
&gt; &nbsp; &nbsp; only for OAM messages, defined in the ITU-T Recommendation<br>
&gt; &nbsp; &nbsp; [G.8113.1], carried in the G-ACh . Other message types
should not<br>
&gt; &nbsp; &nbsp; be carried behind this Associated Channel Type.<br>
</font></tt>
<br>
<br><tt><font size=2>MB: I do not agree with this proposed change. Other
comments request that the restriction on the applicability of the code
point is strengthened so I propose the following:</font></tt>
<br>
<br><tt><font size=2>The code point allocated by this document should only
be used for OAM messages, defined in the ITU-T Recommendation [G.8113.1],
carried in the G-ACh. The messages and procedures carried behind this code
point, are restricted to only those that the address the OAM functional
requirements defined in [RFC5860]. Other message types should not be carried
behind this code point.</font></tt>
<br>
<br>
<br><tt><font size=2>&gt; <br>
&gt; Section 2 - second paragraph<br>
&gt; ============================<br>
&gt; <br>
&gt; A matter of some clarity, can we change this paragrap like this:<br>
&gt; <br>
&gt; OLD:<br>
&gt; &nbsp; &nbsp; This code point may be used on any transport construct
that uses<br>
&gt; &nbsp; &nbsp; the G-ACh, e.g., MPLS-TP Sections, MPLS-TP LSPs or PWs.<br>
&gt; <br>
&gt; NEW:<br>
&gt; <br>
&gt; &nbsp; &nbsp; The Generic Associated Channel Type assigned by this<br>
&gt; &nbsp; &nbsp; document may be used on any transport construct that
uses the<br>
&gt; &nbsp; &nbsp; G-ACh, e.g., MPLS-TP Sections, MPLS-TP LSPs or PWs as
specified<br>
&gt; &nbsp; &nbsp; by G.8113.1.<br>
</font></tt>
<br><tt><font size=2>MB: No objection to this change.</font></tt>
<br>
<br><tt><font size=2>&gt; <br>
&gt; <br>
&gt; Section 2 - third paragraph<br>
&gt; ===========================<br>
&gt; <br>
&gt; With regard to revisions, which is what I think the third paragraph<br>
&gt; is about, I am not clear what you are trying to say. &nbsp;A code
point<br>
&gt; allocation must point to a stable referent. &nbsp;If the desired referent<br>
&gt; changes, then process needs to be followed to make sure that the IANA<br>
&gt; is updated in accordance with IETF procedures. &nbsp;Hence, I am left
to<br>
&gt; the conclusion that the third paragraph is actually asking for<br>
&gt; something we can not do. &nbsp;Can we remove that?<br>
&gt; <br>
&gt; OLD:<br>
&gt; &nbsp; &nbsp; All ITU-T Recommendations are subject to revisions.
Therefore, the<br>
&gt; &nbsp; &nbsp; code point allocated by this document may be used for
future versions<br>
&gt; &nbsp; &nbsp; of [G.8113.1].<br>
&gt; <br>
&gt; NEW:<br>
&gt; &nbsp; &nbsp; -<br>
&gt; <br>
&gt; <br>
</font></tt>
<br><tt><font size=2>MB: I do not agree with the removal of this text:</font></tt>
<br>
<br><tt><font size=2>The intention of this statement is to bring to the
attention of the IETF the normal practice in the ITU of developing amendments
to Recommendations to fully meet the functional requirements (e.g. adding
pro-active loss measurement). &nbsp;Normally any reference to ITU-T Rec
G.8113.1 will automatically be directed to the current version (including
any amendments). </font></tt>
<br>
<br><tt><font size=2>Only those interfaces that support G.8113.1 OAM will
act on these OAM messages, any interface that does not support this G-ACh
type will discard these OAM messages as defined in RFC5586.</font></tt>
<br>
<br><tt><font size=2>Restricting the application of the code point to a
specific version of Recommendation G.8113.1 would require the ITU to deviate
from its normal process for enhancing Recommendations and would put the
IETF back into the discussion for approval.</font></tt>
<br>
<br>
<br>
<br><tt><font size=2>&gt;---------------snip</font></tt>
<br>
<br><tt><font size=2><br>
&gt; <br>
&gt; Loa Andersson &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; email: loa.andersson@ericsson.com<br>
&gt; Sr Strategy and Standards Manager &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp;loa@pi.nu<br>
&gt; Ericsson Inc &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;phone: +46 10 717 52 13<br>
&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; +46 767 72 92 13<br>
&gt; _______________________________________________<br>
&gt; Ietf mailing list<br>
&gt; Ietf@ietf.org<br>
&gt; </font></tt><a href=https://www.ietf.org/mailman/listinfo/ietf><tt><font size=2>https://www.ietf.org/mailman/listinfo/ietf</font></tt></a><tt><font size=2><br>
&gt; <br>
</font></tt>
--=_alternative 0070E506852579C8_=--


From malcolm.betts@zte.com.cn  Wed Mar 21 13:34:17 2012
Return-Path: <malcolm.betts@zte.com.cn>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0413521E8121 for <ietf@ietfa.amsl.com>; Wed, 21 Mar 2012 13:34:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.488
X-Spam-Level: 
X-Spam-Status: No, score=-100.488 tagged_above=-999 required=5 tests=[AWL=-1.350, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, MIME_BASE64_TEXT=1.753, RCVD_DOUBLE_IP_LOOSE=0.76, SARE_SUB_ENC_WIN1255=0.647, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id k-rJ4WTPw9o2 for <ietf@ietfa.amsl.com>; Wed, 21 Mar 2012 13:34:15 -0700 (PDT)
Received: from mx5.zte.com.cn (mx6.zte.com.cn [95.130.199.165]) by ietfa.amsl.com (Postfix) with ESMTP id 948DE21F8629 for <ietf@ietf.org>; Wed, 21 Mar 2012 13:34:14 -0700 (PDT)
Received: from [10.30.17.100] by mx5.zte.com.cn with surfront esmtp id 1228011182326; Thu, 22 Mar 2012 04:00:06 +0800 (CST)
Received: from [10.30.3.20] by [192.168.168.16] with StormMail ESMTP id 33120.11182326; Thu, 22 Mar 2012 04:33:58 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse01.zte.com.cn with ESMTP id q2LKY6dN067056 for <ietf@ietf.org>; Thu, 22 Mar 2012 04:34:06 +0800 (GMT-8) (envelope-from Malcolm.BETTS@zte.com.cn)
In-Reply-To: <8fab01cd014c$dea8f551$5e209f0a@nsnintra.net>
References: <8fab01cd014c$dea8f551$5e209f0a@nsnintra.net>
To: ietf@ietf.org
Subject: =?windows-1255?B?UmU6IOTw4+XvOiBSRTogTGFzdCBDYWxsOjxkcmFmdC1iZXR0cy1pdHUt?= =?windows-1255?B?b2FtLWFjaC1jb2RlLXBvaW50LTAzLnR4dD4oQWxsb2NhdGlvbm9mCWFu?= =?windows-1255?B?IEFzc29jaWF0ZWQgQ2hhbm5lbCBDb2RlIFBvaW50IGZvciBVc2U=?= =?windows-1255?B?IGJ5SVRVLVQgRXRoZXJuZXRiYXNlZCBPQU0pIHRv?= =?windows-1255?B?CUluZm9ybWF0aW9uYWwgUkZD?=
MIME-Version: 1.0
X-KeepSent: 937CA1AC:2B9543C2-852579C8:006E853F; type=4; name=$KeepSent
X-Mailer: Lotus Notes Release 8.5.1 September 28, 2009
Message-ID: <OF937CA1AC.2B9543C2-ON852579C8.006E853F-852579C8.0070FA65@zte.com.cn>
From: Malcolm.BETTS@zte.com.cn
Date: Wed, 21 Mar 2012 15:33:58 -0500
X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 8.5.1FP4|July 25, 2010) at 2012-03-22 04:34:06, Serialize complete at 2012-03-22 04:34:06
Content-Type: multipart/alternative; boundary="=_alternative 0070FA63852579C8_="
X-MAIL: mse01.zte.com.cn q2LKY6dN067056
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Mar 2012 20:34:17 -0000

This is a multipart message in MIME format.
--=_alternative 0070FA63852579C8_=
Content-Type: text/plain; charset="windows-1255"
Content-Transfer-Encoding: base64

QWxsLA0KDQpUd28gcG9pbnRzIHRvIGNvbnNpZGVyOg0KDQoxKSBCZWxvdyBpdCBpcyBzdGF0ZWQ6
DQoNCiJJbiB0aGUgZnV0dXJlLCBhbGwgY29kZXBvaW50IGFsbG9jYXRpb25zIHRvIHRoZSBJVFUt
VCBzaG91bGQgYmUgdGllZCB0byANCm9uZSBzcGVjaWZpYywgZGF0ZWQgcmV2aXNpb24gb2YgdGhl
aXIgc3BlY2lmaWNhdGlvbiBvbmx5LiBUaGlzIGlzIHNpbWlsYXIgDQp0byB0aGUgSVRVLVQncyBv
d24gcHJvY2Vzc2VzLCBzdWNoIGFzIHNlY3Rpb24gMi4yLjEgb2YgUmVjLiBBLjUsIHdoaWNoIA0K
cmVxdWlyZXMgYSB2ZXJzaW9uIG51bWJlciBhbmQvb3IgZGF0ZSBmb3IgcmVmZXJlbmNlZCBvdXRz
aWRlIGRvY3VtZW50cyBpbiANCklUVS1UIHJlY29tbWVuZGF0aW9ucy4iDQoNCkhvd2V2ZXIsIHRo
aXMgaXMgbm90IHRoZSBjb21wbGV0ZSBwaWN0dXJlIG9mIHRoZSBJVFUgcHJvY2Vzcy4gU2VjdGlv
biAyLjIgDQpvZiBSZWNvbW1lbmRhdGlvbiBBLjUgZGVmaW5lcyB0aGUgaW5mb3JtYXRpb24gdGhh
dCBtdXN0IGJlIHByb3ZpZGVkIHdoZW4gDQp0aGUgaW5jbHVzaW9uIG9mIGEgbm9ybWF0aXZlIHJl
ZmVyZW5jZSBpcyB1bmRlciBjb25zaWRlcmF0aW9uLiBUaGUgQXV0aG9ycyANCmd1aWRlIHJlcXVp
cmVzIHRoYXQgdGhlIGZvbGxvd2luZyB0ZXh0IGlzIGluc2VydGVkIGludG8gdGhlIFJlZmVyZW5j
ZXMgDQpzZWN0aW9uIG9mIGFsbCBJVFUtVCBSZWNvbW1lbmRhdGlvbnM6DQoNCiJUaGUgZm9sbG93
aW5nIElUVS1UIFJlY29tbWVuZGF0aW9ucyBhbmQgb3RoZXIgcmVmZXJlbmNlcyBjb250YWluIA0K
cHJvdmlzaW9ucyB3aGljaCwgdGhyb3VnaCByZWZlcmVuY2UgaW4gdGhpcyB0ZXh0LCBjb25zdGl0
dXRlIHByb3Zpc2lvbnMgb2YgDQp0aGlzIFJlY29tbWVuZGF0aW9uLiBBdCB0aGUgdGltZSBvZiBw
dWJsaWNhdGlvbiwgdGhlIGVkaXRpb25zIGluZGljYXRlZCANCndlcmUgdmFsaWQuIEFsbCBSZWNv
bW1lbmRhdGlvbnMgYW5kIG90aGVyIHJlZmVyZW5jZXMgYXJlIHN1YmplY3QgdG8gDQpyZXZpc2lv
bjsgdXNlcnMgb2YgdGhpcyBSZWNvbW1lbmRhdGlvbiBhcmUgdGhlcmVmb3JlIGVuY291cmFnZWQg
dG8gDQppbnZlc3RpZ2F0ZSB0aGUgcG9zc2liaWxpdHkgb2YgYXBwbHlpbmcgdGhlIG1vc3QgcmVj
ZW50IGVkaXRpb24gb2YgdGhlIA0KUmVjb21tZW5kYXRpb25zIGFuZCBvdGhlciByZWZlcmVuY2Vz
IGxpc3RlZCBiZWxvdy4iDQoNClRodXMgaW4gdGhlIElUVSB0aGUgbGF0ZXN0IHZlcnNpb24gb2Yg
YSByZWZlcmVuY2VkIGRvY3VtZW50IGlzIGFsd2F5cyANCmNvbnNpZGVyZWQuDQoNCg0KMikgU2Vj
dGlvbiAyIG9mIGRyYWZ0LWJldHRzIJNTY29wZSBvZiB0aGUgRXRoZXJuZXQgYmFzZWQgT0FNIEFD
SCBUeXBllCANCnJlc3RyaWN0cyB0aGUgdXNlIG9mIHRoZSBjb2RlIHBvaW50IHRvIHRoZSBPQU0g
bWVzc2FnZXMgbmVjZXNzYXJ5IHRvIG1lZXQgDQp0aGUgZnVuY3Rpb25hbCByZXF1aXJlbWVudHMg
b2YgUkZDIDU4NjA6DQoNCpNUaGUgY29kZSBwb2ludCBhbGxvY2F0ZWQgYnkgdGhpcyBkb2N1bWVu
dCBpcyBpbnRlbmRlZCB0byBiZSB1c2VkIG9ubHkgZm9yIA0KRXRoZXJuZXQgYmFzZWQgT0FNIG1l
c3NhZ2VzLCBkZWZpbmVkIGluIHRoZSBJVFUtVCBSZWNvbW1lbmRhdGlvbiANCltHLjgxMTMuMV0s
IGNhcnJpZWQgaW4gdGhlIEctQUNoIC4gVGhlc2UgRXRoZXJuZXQgYmFzZWQgT0FNIG1lc3NhZ2Vz
IGFuZCANCnByb2NlZHVyZXMsIGFkZHJlc3MgdGhlIE9BTSBmdW5jdGlvbmFsIHJlcXVpcmVtZW50
cyBkZWZpbmVkIGluIFtSRkM1ODYwXS4gDQpPdGhlciBtZXNzYWdlIHR5cGVzIHNob3VsZCBub3Qg
YmUgY2FycmllZCBiZWhpbmQgdGhpcyBjb2RlIHBvaW50LpQNCg0KRnVydGhlciBvbmx5IGludGVy
ZmFjZXMgdGhhdCBzdXBwb3J0IEcuODExMy4xIE9BTSB3aWxsIGFjdCBvbiB0aGVzZSBPQU0gDQpt
ZXNzYWdlcywgYW55IGludGVyZmFjZSB0aGF0IGRvZXMgbm90IHN1cHBvcnQgdGhpcyBHLUFDaCB0
eXBlICB3aWxsIA0KZGlzY2FyZCB0aGVzZSBPQU0gbWVzc2FnZXMgYXMgZGVmaW5lZCBpbiBSRkM1
NTg2Lg0KDQpBbHNvIGFzIHN0YXRlZCBpbiB0aGUgbGFzdCBwYXJhZ3JhcGggb2Ygc2VjdGlvbiAy
Og0KDQqTQWxsIElUVS1UIFJlY29tbWVuZGF0aW9ucyBhcmUgc3ViamVjdCB0byByZXZpc2lvbnMu
IFRoZXJlZm9yZSwgdGhlIGNvZGUgDQpwb2ludCBhbGxvY2F0ZWQgYnkgdGhpcyBkb2N1bWVudCBt
YXkgYmUgdXNlZCBmb3IgZnV0dXJlIHZlcnNpb25zIG9mIA0KW0cuODExMy4xXS6UDQoNClRoZSBp
bnRlbnRpb24gb2YgdGhpcyBzdGF0ZW1lbnQgaXMgdG8gYnJpbmcgdG8gdGhlIGF0dGVudGlvbiBv
ZiB0aGUgSUVURiANCnRoZSBub3JtYWwgcHJhY3RpY2UgaW4gdGhlIElUVSBvZiBkZXZlbG9waW5n
IGFtZW5kbWVudHMgdG8gUmVjb21tZW5kYXRpb25zIA0KdG8gZnVsbHkgbWVldCB0aGUgZnVuY3Rp
b25hbCByZXF1aXJlbWVudHMgKGUuZy4gYWRkaW5nIHByby1hY3RpdmUgbG9zcyANCm1lYXN1cmVt
ZW50KS4gIE5vcm1hbGx5IGFueSByZWZlcmVuY2UgdG8gSVRVLVQgUmVjIEcuODExMy4xIHdpbGwg
DQphdXRvbWF0aWNhbGx5IGJlIGRpcmVjdGVkIHRvIHRoZSBjdXJyZW50IHZlcnNpb24gKGluY2x1
ZGluZyBhbnkgDQphbWVuZG1lbnRzKS4NCg0KUnVzcyBzdGF0ZWQgaW4gDQpodHRwczovL3d3dy5p
ZXRmLm9yZy9pYmluL2M1aT9taWQ9NiZyaWQ9NDkmZ2lkPTAmazE9OTMzJmsyPTYyMTg1JnRpZD0x
MzMxNjQ4NjY0DQo6DQoNCpNTb21lIHBlb3BsZSBhcmUgdXNpbmcgdGhlIGxhY2sgb2YgYSBjb2Rl
IHBvaW50IGFzIHRoZSByZWFzb24gdGhhdCB0aGUgDQpjYW5ub3Qgc3VwcG9ydCB0aGUgSVRVLVQg
ZG9jdW1lbnQuIE15IGFwcHJvYWNoIHRlbGxzIHRoZSBJVFUtVCB0aGF0IGEgY29kZSANCnBvaW50
IGlzIGF2YWlsYWJsZSB0byB0aGVtIElGRiB0aGV5IGFyZSBhYmxlIHRvIHJlYWNoIGNvbnNlbnN1
cy4gVGhlIA0KcmVtb3ZlcyBJRVRGIGZyb20gdGhlIGRpc2N1c3Npb24uIFRoaXMgY3JlYXRlcyBh
IHNpdHVhdGlvbiB3aGVyZSBHLjgxMTMuMSANCnN1Y2NlZWRlZCBvciBmYWlscyBiYXNlZCBvbiB0
aGUgSVRVLVQgbWVtYmVycyBhY3Rpb25zLCB3aXRoIG5vIGZpbmdlciANCnBvaW50aW5nIGF0IHRo
ZSBJRVRGLiBUaGlzIGlzIGNvbXBsZXRlbHkgYSBMYXllciA5IGNvbnNpZGVyYXRpb24sIGFuZCBp
dCANCmhhcyBub3RpbmcgdG8gZG8gd2l0aCB0aGUgdGVjaG5pY2FsIGNvbnRlbnQgb2YgdGhlIGRv
Y3VtZW50LpQNCg0KUmVzdHJpY3RpbmcgdGhlIGFwcGxpY2F0aW9uIG9mIHRoZSBjb2RlIHBvaW50
IHRvIGEgc3BlY2lmaWMgdmVyc2lvbiBvZiANClJlY29tbWVuZGF0aW9uIEcuODExMy4xIHdvdWxk
IHJlcXVpcmUgdGhlIElUVSB0byBkZXZpYXRlIGZyb20gaXRzIG5vcm1hbCANCnByb2Nlc3MgZm9y
IGVuaGFuY2luZyBSZWNvbW1lbmRhdGlvbnMgYW5kIHdvdWxkIHB1dCB0aGUgSUVURiBiYWNrIGlu
dG8gdGhlIA0KZGlzY3Vzc2lvbiBmb3IgYXBwcm92YWwuDQoNClJlZ2FyZHMsDQoNCk1hbGNvbG0N
Cg0KDQoNCg0KIlNwcmVjaGVyLCBOdXJpdCAoTlNOIC0gSUwvSG9kIEhhU2hhcm9uKSIgPG51cml0
LnNwcmVjaGVyQG5zbi5jb20+IA0KU2VudCBieTogaWV0Zi1ib3VuY2VzQGlldGYub3JnDQoxMy8w
My8yMDEyIDAzOjA5IFBNDQoNClRvDQoiQW5kcmV3IEcuIE1hbGlzIiA8YWdtYWxpc0BnbWFpbC5j
b20+LCAiZXh0IFJvc3MgQ2FsbG9uIiANCjxyY2FsbG9uQGp1bmlwZXIubmV0Pg0KY2MNCmlldGZA
aWV0Zi5vcmcNClN1YmplY3QNCuTw4+XvOiBSRTogTGFzdCANCkNhbGw6PGRyYWZ0LWJldHRzLWl0
dS1vYW0tYWNoLWNvZGUtcG9pbnQtMDMudHh0PihBbGxvY2F0aW9ub2YgICBhbiANCkFzc29jaWF0
ZWQgQ2hhbm5lbCBDb2RlIFBvaW50IGZvciBVc2UgYnlJVFUtVCBFdGhlcm5ldGJhc2VkIE9BTSkg
dG8gDQpJbmZvcm1hdGlvbmFsIFJGQw0KDQoNCg0KDQoNCg0KUm9zcywNCmkgYW0gYWZyYWlkIHRo
YXQgeW91IG1pc3NlZCB0aGUgcG9pbnQuIFRoZXJlIHdpbGwgbm90IGJlIGEgZmluYWwgdmVyc2lv
biANCnNpbmNlIGFzIHdyaXR0ZW4gaW4gZHJhZnQtYmV0dHMsIGFsbCAgSVRVIHJlY29tbWVuZGF0
aW9ucyBhcmUgc3ViamVjdCB0byANCnJldmlzaW9ucywgYW5kIHRoZSBjb2RlIHBvaW50IHdpbGwg
YWxzbyBiZSB1c2VkIGZvciBmdXR1cmUgcmV2aXNpb25zIG9mIA0KdGhlIGRvY3VtZW50LiBOZXcg
bWVzc2FnZXMvcHJvdG9jb2xzIGNhbiBiZSBkZWZpbmVkIGluIGZ1dHVyZSByZXZpc2lvbnMgb2Yg
DQp0aGUgcmVjb21tZW5kYXRpb24gYW5kIHRoZXkgd2lsbCB1c2UgdGhlIHNhbWUgY29kZSBwb2lu
dCB0aGF0IGlzIGFsbG9jYXRlZCANCmZvciB0aGUgZmlyc3QgdmVyc2lvbi4NClRoaXMgaXMgYSBy
ZWFsIGlzc3VlLg0KUmVnYXJkcywNCk51cml0IA0KLS0tLS3k5ePy5CDu9+X46fotLS0tLQ0K7uD6
OiBleHQgUm9zcyBDYWxsb24NCvD57Oc6ICAxMy8wMy8yMDEyLCAxOToyNyANCuDsOiBBbmRyZXcg
Ry4gTWFsaXM7IFNwcmVjaGVyLCBOdXJpdCAoTlNOIC0gSUwvSG9kIEhhU2hhcm9uKQ0K8uX69zog
aWV0ZkBpZXRmLm9yZw0K8OX54DogUkU6IExhc3QgDQpDYWxsOjxkcmFmdC1iZXR0cy1pdHUtb2Ft
LWFjaC1jb2RlLXBvaW50LTAzLnR4dD4oQWxsb2NhdGlvbm9mIGFuIA0KQXNzb2NpYXRlZCBDaGFu
bmVsIENvZGUgUG9pbnQgZm9yIFVzZSBieUlUVS1UIEV0aGVybmV0YmFzZWQgT0FNKSB0byAgDQpJ
bmZvcm1hdGlvbmFsIFJGQw0KSSBhZ3JlZSB0aGF0IHRoZSBhbGxvY2F0aW9uIG9mIGEgY29kZSBw
b2ludCBzaG91bGQgYmUgdG8gYSBzcGVjaWZpYyANCnZlcnNpb24gb2YgODExMy4xLCBhbmQgc3Bl
Y2lmaWNhbGx5IHNob3VsZCBiZSB0byB0aGUgZmluYWwgdmVyc2lvbiB0aGF0IGlzIA0KYXBwcm92
ZWQgYnkgdGhlIElUVS1UIChhc3N1bWluZyB0aGF0IGEgZmluYWwgdmVyc2lvbiBvZiA4MTEzLjEg
d2lsbCBiZSANCmFwcHJvdmVkIGJ5IHRoZSBJVFUtVCkuIFRoaXMgd291bGQgaW1wbHkgdGhhdCAN
CmRyYWZ0LWJldHRzLWl0dS1vYW0tYWNoLWNvZGUtcG9pbnQgc2hvdWxkIGNvbnRhaW4gYSBub3Jt
YXRpdmUgcmVmZXJlbmNlIHRvIA0KdGhlIGZpbmFsIGFwcHJvdmVkIHZlcnNpb24gb2YgODExMy4x
LiANCg0KR2l2ZW4gbm9ybWFsIElFVEYgcHJvY2Vzc2VzLCB0aGlzIGltcGxpZXMgdGhhdCB0aGUg
ZmluYWwgUkZDIHJlc3VsdGluZyANCmZyb20gZHJhZnQtYmV0dHMtaXR1LW9hbS1hY2gtY29kZS1w
b2ludCBjb3VsZCBiZSBwdWJsaXNoZWQgYXMgc29vbiBhcyB0aGUgDQpmaW5hbCB2ZXJzaW9uIG9m
IDgxMTMuMSBpcyBhcHByb3ZlZCAod2l0aCB0aGUgdW5kZXJzdGFuZGluZyB0aGF0IHRoZXJlIA0K
d2lsbCBiZSBhIHNtYWxsIG5vcm1hbCBkZWxheSBiZXR3ZWVuICJhcHByb3ZlZCIgYW5kICJwdWJs
aXNoZWQiIHdoaWNoIA0KZ2l2ZXMgdGltZSBmb3IgY29vcmRpbmF0aW9uKS4gR2l2ZW4gdGhhdCB0
aGUgZmluYWwgdmVyc2lvbiBvZiA4MTEzLjEgbWlnaHQgDQpuZWVkIHRvIHJlZmVyZW5jZSB0aGUg
UkZDIHJlc3VsdGluZyBmcm9tIA0KZHJhZnQtYmV0dHMtaXR1LW9hbS1hY2gtY29kZS1wb2ludCwg
YSBiaXQgb2YgY29vcGVyYXRpb24gbWlnaHQgYmUgbmVlZGVkIA0KYmV0d2VlbiBlZGl0b3JpYWwg
c3RhZmYgYXQgdGhlIElUVSBhbmQgUkZDIGVkaXRvcmlhbCBzdGFmZiwgYnV0IEkgZG9uJ3QgDQpz
ZWUgd2h5IHRoaXMgc2hvdWxkIGJlIGEgcHJvYmxlbSAoSSBhbSBzdXJlIHRoYXQgdGhleSBhbGwg
aGF2ZSBhY2Nlc3MgdG8gDQplbWFpbCkuIA0KDQpSb3NzDQoNCi0tLS0tT3JpZ2luYWwgTWVzc2Fn
ZS0tLS0tDQpGcm9tOiBpZXRmLWJvdW5jZXNAaWV0Zi5vcmcgW21haWx0bzppZXRmLWJvdW5jZXNA
aWV0Zi5vcmddIE9uIEJlaGFsZiBPZiANCkFuZHJldyBHLiBNYWxpcw0KU2VudDogTW9uZGF5LCBN
YXJjaCAwNSwgMjAxMiA2OjU0IFBNDQpUbzogU3ByZWNoZXIsIE51cml0IChOU04gLSBJTC9Ib2Qg
SGFTaGFyb24pDQpDYzogaWV0ZkBpZXRmLm9yZw0KU3ViamVjdDogUmU6IExhc3QgQ2FsbDogDQo8
ZHJhZnQtYmV0dHMtaXR1LW9hbS1hY2gtY29kZS1wb2ludC0wMy50eHQ+KEFsbG9jYXRpb25vZiBh
biBBc3NvY2lhdGVkIA0KQ2hhbm5lbCBDb2RlIFBvaW50IGZvciBVc2UgYnlJVFUtVCBFdGhlcm5l
dGJhc2VkIE9BTSkgdG8gSW5mb3JtYXRpb25hbCBSRkMNCg0KSSB3b3VsZCBsaWtlIHRvIHN1cHBv
cnQgTnVyaXQncyBjb21tZW50cyBiZWxvdy4gSW4gcGFydGljdWxhciwgaW4gdGhlDQpwYXN0IHRo
ZSBJVFUtVCBoYXMgZXhwYW5kZWQgdXBvbiBvciBjaGFuZ2VkIHRoZSB1c2FnZSBvZiBJRVRGDQpj
b2RlcG9pbnQgYWxsb2NhdGlvbnMsIGluIHNvbWUgY2FzZXMgaW5jb21wYXRpYmx5IHdpdGggaXRz
IG9yaWdpbmFsDQp1c2FnZSBvciBkZWZpbml0aW9uLiBJbiB0aGUgZnV0dXJlLCBhbGwgY29kZXBv
aW50IGFsbG9jYXRpb25zIHRvIHRoZQ0KSVRVLVQgc2hvdWxkIGJlIHRpZWQgdG8gb25lIHNwZWNp
ZmljLCBkYXRlZCByZXZpc2lvbiBvZiB0aGVpcg0Kc3BlY2lmaWNhdGlvbiBvbmx5LiBUaGlzIGlz
IHNpbWlsYXIgdG8gdGhlIElUVS1UJ3Mgb3duIHByb2Nlc3Nlcywgc3VjaA0KYXMgc2VjdGlvbiAy
LjIuMSBvZiBSZWMuIEEuNSwgd2hpY2ggcmVxdWlyZXMgYSB2ZXJzaW9uIG51bWJlciBhbmQvb3IN
CmRhdGUgZm9yIHJlZmVyZW5jZWQgb3V0c2lkZSBkb2N1bWVudHMgaW4gSVRVLVQgcmVjb21tZW5k
YXRpb25zLg0KDQpDaGVlcnMsDQpBbmR5DQoNCj4tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
U25pcA0KDQoNCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
DQpJZXRmIG1haWxpbmcgbGlzdA0KSWV0ZkBpZXRmLm9yZw0KaHR0cHM6Ly93d3cuaWV0Zi5vcmcv
bWFpbG1hbi9saXN0aW5mby9pZXRmDQoNCg0K
--=_alternative 0070FA63852579C8_=
Content-Type: text/html; charset="windows-1255"
Content-Transfer-Encoding: base64

PGZvbnQgc2l6ZT0yIGZhY2U9IkFyaWFsIj5BbGwsPC9mb250Pg0KPGJyPg0KPGJyPjxmb250IHNp
emU9MiBmYWNlPSJBcmlhbCI+VHdvIHBvaW50cyB0byBjb25zaWRlcjo8L2ZvbnQ+DQo8YnI+DQo8
YnI+PGZvbnQgc2l6ZT0yIGZhY2U9IkFyaWFsIj4xKSBCZWxvdyBpdCBpcyBzdGF0ZWQ6PC9mb250
Pg0KPGJyPg0KPGJyPjxmb250IHNpemU9MiBmYWNlPSJBcmlhbCI+JnF1b3Q7SW4gdGhlIGZ1dHVy
ZSwgYWxsIGNvZGVwb2ludCBhbGxvY2F0aW9ucw0KdG8gdGhlIElUVS1UIHNob3VsZCBiZSB0aWVk
IHRvIG9uZSBzcGVjaWZpYywgZGF0ZWQgcmV2aXNpb24gb2YgdGhlaXIgc3BlY2lmaWNhdGlvbg0K
b25seS4gVGhpcyBpcyBzaW1pbGFyIHRvIHRoZSBJVFUtVCdzIG93biBwcm9jZXNzZXMsIHN1Y2gg
YXMgc2VjdGlvbiAyLjIuMQ0Kb2YgUmVjLiBBLjUsIHdoaWNoIHJlcXVpcmVzIGEgdmVyc2lvbiBu
dW1iZXIgYW5kL29yIGRhdGUgZm9yIHJlZmVyZW5jZWQNCm91dHNpZGUgZG9jdW1lbnRzIGluIElU
VS1UIHJlY29tbWVuZGF0aW9ucy4mcXVvdDs8L2ZvbnQ+DQo8YnI+DQo8YnI+PGZvbnQgc2l6ZT0y
IGZhY2U9IkFyaWFsIj5Ib3dldmVyLCB0aGlzIGlzIG5vdCB0aGUgY29tcGxldGUgcGljdHVyZQ0K
b2YgdGhlIElUVSBwcm9jZXNzLiBTZWN0aW9uIDIuMiBvZiBSZWNvbW1lbmRhdGlvbiBBLjUgZGVm
aW5lcyB0aGUgaW5mb3JtYXRpb24NCnRoYXQgbXVzdCBiZSBwcm92aWRlZCB3aGVuIHRoZSBpbmNs
dXNpb24gb2YgYSBub3JtYXRpdmUgcmVmZXJlbmNlIGlzIHVuZGVyDQpjb25zaWRlcmF0aW9uLiBU
aGUgQXV0aG9ycyBndWlkZSByZXF1aXJlcyB0aGF0IHRoZSBmb2xsb3dpbmcgdGV4dCBpcyBpbnNl
cnRlZA0KaW50byB0aGUgUmVmZXJlbmNlcyBzZWN0aW9uIG9mIGFsbCBJVFUtVCBSZWNvbW1lbmRh
dGlvbnM6PC9mb250Pg0KPGJyPg0KPGJyPjxmb250IHNpemU9MiBmYWNlPSJBcmlhbCI+JnF1b3Q7
VGhlIGZvbGxvd2luZyBJVFUtVCBSZWNvbW1lbmRhdGlvbnMNCmFuZCBvdGhlciByZWZlcmVuY2Vz
IGNvbnRhaW4gcHJvdmlzaW9ucyB3aGljaCwgdGhyb3VnaCByZWZlcmVuY2UgaW4gdGhpcw0KdGV4
dCwgY29uc3RpdHV0ZSBwcm92aXNpb25zIG9mIHRoaXMgUmVjb21tZW5kYXRpb24uIEF0IHRoZSB0
aW1lIG9mIHB1YmxpY2F0aW9uLA0KdGhlIGVkaXRpb25zIGluZGljYXRlZCB3ZXJlIHZhbGlkLiBB
bGwgUmVjb21tZW5kYXRpb25zIGFuZCBvdGhlciByZWZlcmVuY2VzDQphcmUgc3ViamVjdCB0byBy
ZXZpc2lvbjsgdXNlcnMgb2YgdGhpcyBSZWNvbW1lbmRhdGlvbiBhcmUgdGhlcmVmb3JlIGVuY291
cmFnZWQNCnRvIGludmVzdGlnYXRlIHRoZSBwb3NzaWJpbGl0eSBvZiBhcHBseWluZyB0aGUgbW9z
dCByZWNlbnQgZWRpdGlvbiBvZiB0aGUNClJlY29tbWVuZGF0aW9ucyBhbmQgb3RoZXIgcmVmZXJl
bmNlcyBsaXN0ZWQgYmVsb3cuJnF1b3Q7PC9mb250Pg0KPGJyPg0KPGJyPjxmb250IHNpemU9MiBm
YWNlPSJBcmlhbCI+VGh1cyBpbiB0aGUgSVRVIHRoZSBsYXRlc3QgdmVyc2lvbiBvZiBhIHJlZmVy
ZW5jZWQNCmRvY3VtZW50IGlzIGFsd2F5cyBjb25zaWRlcmVkLjwvZm9udD4NCjxicj4NCjxicj4N
Cjxicj48Zm9udCBzaXplPTIgZmFjZT0iQXJpYWwiPjIpIFNlY3Rpb24gMiBvZiBkcmFmdC1iZXR0
cyCTU2NvcGUgb2YgdGhlDQpFdGhlcm5ldCBiYXNlZCBPQU0gQUNIIFR5cGWUIHJlc3RyaWN0cyB0
aGUgdXNlIG9mIHRoZSBjb2RlIHBvaW50IHRvIHRoZQ0KT0FNIG1lc3NhZ2VzIG5lY2Vzc2FyeSB0
byBtZWV0IHRoZSBmdW5jdGlvbmFsIHJlcXVpcmVtZW50cyBvZiBSRkMgNTg2MDo8L2ZvbnQ+DQo8
YnI+DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9IkFyaWFsIj6TVGhlIGNvZGUgcG9pbnQgYWxsb2Nh
dGVkIGJ5IHRoaXMgZG9jdW1lbnQNCmlzIGludGVuZGVkIHRvIGJlIHVzZWQgb25seSBmb3IgRXRo
ZXJuZXQgYmFzZWQgT0FNIG1lc3NhZ2VzLCBkZWZpbmVkIGluDQp0aGUgSVRVLVQgUmVjb21tZW5k
YXRpb24gW0cuODExMy4xXSwgY2FycmllZCBpbiB0aGUgRy1BQ2ggLiBUaGVzZSBFdGhlcm5ldA0K
YmFzZWQgT0FNIG1lc3NhZ2VzIGFuZCBwcm9jZWR1cmVzLCBhZGRyZXNzIHRoZSBPQU0gZnVuY3Rp
b25hbCByZXF1aXJlbWVudHMNCmRlZmluZWQgaW4gW1JGQzU4NjBdLiBPdGhlciBtZXNzYWdlIHR5
cGVzIHNob3VsZCBub3QgYmUgY2FycmllZCBiZWhpbmQNCnRoaXMgY29kZSBwb2ludC6UPC9mb250
Pg0KPGJyPg0KPGJyPjxmb250IHNpemU9MiBmYWNlPSJBcmlhbCI+RnVydGhlciBvbmx5IGludGVy
ZmFjZXMgdGhhdCBzdXBwb3J0IEcuODExMy4xDQpPQU0gd2lsbCBhY3Qgb24gdGhlc2UgT0FNIG1l
c3NhZ2VzLCBhbnkgaW50ZXJmYWNlIHRoYXQgZG9lcyBub3Qgc3VwcG9ydA0KdGhpcyBHLUFDaCB0
eXBlICZuYnNwO3dpbGwgZGlzY2FyZCB0aGVzZSBPQU0gbWVzc2FnZXMgYXMgZGVmaW5lZCBpbiBS
RkM1NTg2LjwvZm9udD4NCjxicj4NCjxicj48Zm9udCBzaXplPTIgZmFjZT0iQXJpYWwiPkFsc28g
YXMgc3RhdGVkIGluIHRoZSBsYXN0IHBhcmFncmFwaCBvZiBzZWN0aW9uDQoyOjwvZm9udD4NCjxi
cj4NCjxicj48Zm9udCBzaXplPTIgZmFjZT0iQXJpYWwiPpNBbGwgSVRVLVQgUmVjb21tZW5kYXRp
b25zIGFyZSBzdWJqZWN0IHRvDQpyZXZpc2lvbnMuIFRoZXJlZm9yZSwgdGhlIGNvZGUgcG9pbnQg
YWxsb2NhdGVkIGJ5IHRoaXMgZG9jdW1lbnQgbWF5IGJlDQp1c2VkIGZvciBmdXR1cmUgdmVyc2lv
bnMgb2YgW0cuODExMy4xXS6UPC9mb250Pg0KPGJyPg0KPGJyPjxmb250IHNpemU9MiBmYWNlPSJB
cmlhbCI+VGhlIGludGVudGlvbiBvZiB0aGlzIHN0YXRlbWVudCBpcyB0byBicmluZw0KdG8gdGhl
IGF0dGVudGlvbiBvZiB0aGUgSUVURiB0aGUgbm9ybWFsIHByYWN0aWNlIGluIHRoZSBJVFUgb2Yg
ZGV2ZWxvcGluZw0KYW1lbmRtZW50cyB0byBSZWNvbW1lbmRhdGlvbnMgdG8gZnVsbHkgbWVldCB0
aGUgZnVuY3Rpb25hbCByZXF1aXJlbWVudHMNCihlLmcuIGFkZGluZyBwcm8tYWN0aXZlIGxvc3Mg
bWVhc3VyZW1lbnQpLiAmbmJzcDtOb3JtYWxseSBhbnkgcmVmZXJlbmNlDQp0byBJVFUtVCBSZWMg
Ry44MTEzLjEgd2lsbCBhdXRvbWF0aWNhbGx5IGJlIGRpcmVjdGVkIHRvIHRoZSBjdXJyZW50IHZl
cnNpb24NCihpbmNsdWRpbmcgYW55IGFtZW5kbWVudHMpLjwvZm9udD4NCjxicj4NCjxicj48Zm9u
dCBzaXplPTIgZmFjZT0iQXJpYWwiPlJ1c3Mgc3RhdGVkIGluIDwvZm9udD48YSBocmVmPSJodHRw
czovL3d3dy5pZXRmLm9yZy9pYmluL2M1aT9taWQ9NiZhbXA7cmlkPTQ5JmFtcDtnaWQ9MCZhbXA7
azE9OTMzJmFtcDtrMj02MjE4NSZhbXA7dGlkPTEzMzE2NDg2NjQiPjxmb250IHNpemU9MiBjb2xv
cj1ibHVlIGZhY2U9IkFyaWFsIj48dT5odHRwczovL3d3dy5pZXRmLm9yZy9pYmluL2M1aT9taWQ9
NiZhbXA7cmlkPTQ5JmFtcDtnaWQ9MCZhbXA7azE9OTMzJmFtcDtrMj02MjE4NSZhbXA7dGlkPTEz
MzE2NDg2NjQ8L3U+PC9mb250PjwvYT48Zm9udCBzaXplPTIgZmFjZT0iQXJpYWwiPjo8L2ZvbnQ+
DQo8YnI+DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9IkFyaWFsIj6TU29tZSBwZW9wbGUgYXJlIHVz
aW5nIHRoZSBsYWNrIG9mIGEgY29kZQ0KcG9pbnQgYXMgdGhlIHJlYXNvbiB0aGF0IHRoZSBjYW5u
b3Qgc3VwcG9ydCB0aGUgSVRVLVQgZG9jdW1lbnQuIE15IGFwcHJvYWNoDQp0ZWxscyB0aGUgSVRV
LVQgdGhhdCBhIGNvZGUgcG9pbnQgaXMgYXZhaWxhYmxlIHRvIHRoZW0gSUZGIHRoZXkgYXJlIGFi
bGUNCnRvIHJlYWNoIGNvbnNlbnN1cy4gVGhlIHJlbW92ZXMgSUVURiBmcm9tIHRoZSBkaXNjdXNz
aW9uLiBUaGlzIGNyZWF0ZXMNCmEgc2l0dWF0aW9uIHdoZXJlIEcuODExMy4xIHN1Y2NlZWRlZCBv
ciBmYWlscyBiYXNlZCBvbiB0aGUgSVRVLVQgbWVtYmVycw0KYWN0aW9ucywgd2l0aCBubyBmaW5n
ZXIgcG9pbnRpbmcgYXQgdGhlIElFVEYuIFRoaXMgaXMgY29tcGxldGVseSBhIExheWVyDQo5IGNv
bnNpZGVyYXRpb24sIGFuZCBpdCBoYXMgbm90aW5nIHRvIGRvIHdpdGggdGhlIHRlY2huaWNhbCBj
b250ZW50IG9mDQp0aGUgZG9jdW1lbnQulDwvZm9udD4NCjxicj4NCjxicj48Zm9udCBzaXplPTIg
ZmFjZT0iQXJpYWwiPlJlc3RyaWN0aW5nIHRoZSBhcHBsaWNhdGlvbiBvZiB0aGUgY29kZSBwb2lu
dA0KdG8gYSBzcGVjaWZpYyB2ZXJzaW9uIG9mIFJlY29tbWVuZGF0aW9uIEcuODExMy4xIHdvdWxk
IHJlcXVpcmUgdGhlIElUVQ0KdG8gZGV2aWF0ZSBmcm9tIGl0cyBub3JtYWwgcHJvY2VzcyBmb3Ig
ZW5oYW5jaW5nIFJlY29tbWVuZGF0aW9ucyBhbmQgd291bGQNCnB1dCB0aGUgSUVURiBiYWNrIGlu
dG8gdGhlIGRpc2N1c3Npb24gZm9yIGFwcHJvdmFsLjwvZm9udD4NCjxicj4NCjxicj48Zm9udCBz
aXplPTIgZmFjZT0iQXJpYWwiPlJlZ2FyZHMsPC9mb250Pg0KPGJyPg0KPGJyPjxmb250IHNpemU9
MiBmYWNlPSJBcmlhbCI+TWFsY29sbTwvZm9udD4NCjxicj4NCjxicj4NCjxicj4NCjxicj4NCjx0
YWJsZSB3aWR0aD0xMDAlPg0KPHRyIHZhbGlnbj10b3A+DQo8dGQgd2lkdGg9MzYlPjxmb250IHNp
emU9MSBmYWNlPSJzYW5zLXNlcmlmIj48Yj4mcXVvdDtTcHJlY2hlciwgTnVyaXQgKE5TTg0KLSBJ
TC9Ib2QgSGFTaGFyb24pJnF1b3Q7ICZsdDtudXJpdC5zcHJlY2hlckBuc24uY29tJmd0OzwvYj4g
PC9mb250Pg0KPGJyPjxmb250IHNpemU9MSBmYWNlPSJzYW5zLXNlcmlmIj5TZW50IGJ5OiBpZXRm
LWJvdW5jZXNAaWV0Zi5vcmc8L2ZvbnQ+DQo8cD48Zm9udCBzaXplPTEgZmFjZT0ic2Fucy1zZXJp
ZiI+MTMvMDMvMjAxMiAwMzowOSBQTTwvZm9udD4NCjx0ZCB3aWR0aD02MyU+DQo8dGFibGUgd2lk
dGg9MTAwJT4NCjx0ciB2YWxpZ249dG9wPg0KPHRkPg0KPGRpdiBhbGlnbj1yaWdodD48Zm9udCBz
aXplPTEgZmFjZT0ic2Fucy1zZXJpZiI+VG88L2ZvbnQ+PC9kaXY+DQo8dGQ+PGZvbnQgc2l6ZT0x
IGZhY2U9InNhbnMtc2VyaWYiPiZxdW90O0FuZHJldyBHLiBNYWxpcyZxdW90OyAmbHQ7YWdtYWxp
c0BnbWFpbC5jb20mZ3Q7LA0KJnF1b3Q7ZXh0IFJvc3MgQ2FsbG9uJnF1b3Q7ICZsdDtyY2FsbG9u
QGp1bmlwZXIubmV0Jmd0OzwvZm9udD4NCjx0ciB2YWxpZ249dG9wPg0KPHRkPg0KPGRpdiBhbGln
bj1yaWdodD48Zm9udCBzaXplPTEgZmFjZT0ic2Fucy1zZXJpZiI+Y2M8L2ZvbnQ+PC9kaXY+DQo8
dGQ+PGZvbnQgc2l6ZT0xIGZhY2U9InNhbnMtc2VyaWYiPmlldGZAaWV0Zi5vcmc8L2ZvbnQ+DQo8
dHIgdmFsaWduPXRvcD4NCjx0ZD4NCjxkaXYgYWxpZ249cmlnaHQ+PGZvbnQgc2l6ZT0xIGZhY2U9
InNhbnMtc2VyaWYiPlN1YmplY3Q8L2ZvbnQ+PC9kaXY+DQo8dGQ+PGZvbnQgc2l6ZT0xIGZhY2U9
InNhbnMtc2VyaWYiPuTw4+XvOiBSRTogTGFzdCBDYWxsOiZsdDtkcmFmdC1iZXR0cy1pdHUtb2Ft
LWFjaC1jb2RlLXBvaW50LTAzLnR4dCZndDsoQWxsb2NhdGlvbm9mDQombmJzcDsgJm5ic3A7ICZu
YnNwOyAmbmJzcDthbiBBc3NvY2lhdGVkIENoYW5uZWwgQ29kZSBQb2ludCBmb3INClVzZSBieUlU
VS1UIEV0aGVybmV0YmFzZWQgT0FNKSB0byAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDtJbmZv
cm1hdGlvbmFsDQpSRkM8L2ZvbnQ+PC90YWJsZT4NCjxicj4NCjx0YWJsZT4NCjx0ciB2YWxpZ249
dG9wPg0KPHRkPg0KPHRkPjwvdGFibGU+DQo8YnI+PC90YWJsZT4NCjxicj4NCjxicj4NCjxicj48
dHQ+PGZvbnQgc2l6ZT0yPlJvc3MsPGJyPg0KaSBhbSBhZnJhaWQgdGhhdCB5b3UgbWlzc2VkIHRo
ZSBwb2ludC4gVGhlcmUgd2lsbCBub3QgYmUgYSBmaW5hbCB2ZXJzaW9uDQpzaW5jZSBhcyB3cml0
dGVuIGluIGRyYWZ0LWJldHRzLCBhbGwgJm5ic3A7SVRVIHJlY29tbWVuZGF0aW9ucyBhcmUgc3Vi
amVjdA0KdG8gcmV2aXNpb25zLCBhbmQgdGhlIGNvZGUgcG9pbnQgd2lsbCBhbHNvIGJlIHVzZWQg
Zm9yIGZ1dHVyZSByZXZpc2lvbnMNCm9mIHRoZSBkb2N1bWVudC4gTmV3IG1lc3NhZ2VzL3Byb3Rv
Y29scyBjYW4gYmUgZGVmaW5lZCBpbiBmdXR1cmUgcmV2aXNpb25zDQpvZiB0aGUgcmVjb21tZW5k
YXRpb24gYW5kIHRoZXkgd2lsbCB1c2UgdGhlIHNhbWUgY29kZSBwb2ludCB0aGF0IGlzIGFsbG9j
YXRlZA0KZm9yIHRoZSBmaXJzdCB2ZXJzaW9uLjxicj4NClRoaXMgaXMgYSByZWFsIGlzc3VlLjxi
cj4NClJlZ2FyZHMsPGJyPg0KTnVyaXQgPGJyPg0KLS0tLS3k5ePy5CDu9+X46fotLS0tLTxicj4N
Cu7g+jogZXh0IFJvc3MgQ2FsbG9uPGJyPg0K8Pns5zogJm5ic3A7MTMvMDMvMjAxMiwgMTk6Mjcg
PGJyPg0K4Ow6IEFuZHJldyBHLiBNYWxpczsgU3ByZWNoZXIsIE51cml0IChOU04gLSBJTC9Ib2Qg
SGFTaGFyb24pPGJyPg0K8uX69zogaWV0ZkBpZXRmLm9yZzxicj4NCvDl+eA6IFJFOiBMYXN0IENh
bGw6Jmx0O2RyYWZ0LWJldHRzLWl0dS1vYW0tYWNoLWNvZGUtcG9pbnQtMDMudHh0Jmd0OyhBbGxv
Y2F0aW9ub2YNCiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNw
OyAmbmJzcDsNCmFuIEFzc29jaWF0ZWQgQ2hhbm5lbCBDb2RlIFBvaW50IGZvciBVc2UgYnlJVFUt
VCBFdGhlcm5ldGJhc2VkIE9BTSkgdG8NCiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJz
cDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsNCkluZm9ybWF0aW9uYWwgUkZDPGJyPg0KSSBhZ3JlZSB0
aGF0IHRoZSBhbGxvY2F0aW9uIG9mIGEgY29kZSBwb2ludCBzaG91bGQgYmUgdG8gYSBzcGVjaWZp
YyB2ZXJzaW9uDQpvZiA4MTEzLjEsIGFuZCBzcGVjaWZpY2FsbHkgc2hvdWxkIGJlIHRvIHRoZSBm
aW5hbCB2ZXJzaW9uIHRoYXQgaXMgYXBwcm92ZWQNCmJ5IHRoZSBJVFUtVCAoYXNzdW1pbmcgdGhh
dCBhIGZpbmFsIHZlcnNpb24gb2YgODExMy4xIHdpbGwgYmUgYXBwcm92ZWQNCmJ5IHRoZSBJVFUt
VCkuIFRoaXMgd291bGQgaW1wbHkgdGhhdCBkcmFmdC1iZXR0cy1pdHUtb2FtLWFjaC1jb2RlLXBv
aW50DQpzaG91bGQgY29udGFpbiBhIG5vcm1hdGl2ZSByZWZlcmVuY2UgdG8gdGhlIGZpbmFsIGFw
cHJvdmVkIHZlcnNpb24gb2YgODExMy4xLg0KPGJyPg0KPGJyPg0KR2l2ZW4gbm9ybWFsIElFVEYg
cHJvY2Vzc2VzLCB0aGlzIGltcGxpZXMgdGhhdCB0aGUgZmluYWwgUkZDIHJlc3VsdGluZw0KZnJv
bSBkcmFmdC1iZXR0cy1pdHUtb2FtLWFjaC1jb2RlLXBvaW50IGNvdWxkIGJlIHB1Ymxpc2hlZCBh
cyBzb29uIGFzIHRoZQ0KZmluYWwgdmVyc2lvbiBvZiA4MTEzLjEgaXMgYXBwcm92ZWQgKHdpdGgg
dGhlIHVuZGVyc3RhbmRpbmcgdGhhdCB0aGVyZQ0Kd2lsbCBiZSBhIHNtYWxsIG5vcm1hbCBkZWxh
eSBiZXR3ZWVuICZxdW90O2FwcHJvdmVkJnF1b3Q7IGFuZCAmcXVvdDtwdWJsaXNoZWQmcXVvdDsN
CndoaWNoIGdpdmVzIHRpbWUgZm9yIGNvb3JkaW5hdGlvbikuIEdpdmVuIHRoYXQgdGhlIGZpbmFs
IHZlcnNpb24gb2YgODExMy4xDQptaWdodCBuZWVkIHRvIHJlZmVyZW5jZSB0aGUgUkZDIHJlc3Vs
dGluZyBmcm9tIGRyYWZ0LWJldHRzLWl0dS1vYW0tYWNoLWNvZGUtcG9pbnQsDQphIGJpdCBvZiBj
b29wZXJhdGlvbiBtaWdodCBiZSBuZWVkZWQgYmV0d2VlbiBlZGl0b3JpYWwgc3RhZmYgYXQgdGhl
IElUVQ0KYW5kIFJGQyBlZGl0b3JpYWwgc3RhZmYsIGJ1dCBJIGRvbid0IHNlZSB3aHkgdGhpcyBz
aG91bGQgYmUgYSBwcm9ibGVtIChJDQphbSBzdXJlIHRoYXQgdGhleSBhbGwgaGF2ZSBhY2Nlc3Mg
dG8gZW1haWwpLiA8YnI+DQo8YnI+DQpSb3NzPGJyPg0KPGJyPg0KLS0tLS1PcmlnaW5hbCBNZXNz
YWdlLS0tLS08YnI+DQpGcm9tOiBpZXRmLWJvdW5jZXNAaWV0Zi5vcmcgWzwvZm9udD48L3R0Pjxh
IGhyZWY9Im1haWx0bzppZXRmLWJvdW5jZXNAaWV0Zi5vcmciPjx0dD48Zm9udCBzaXplPTI+bWFp
bHRvOmlldGYtYm91bmNlc0BpZXRmLm9yZzwvZm9udD48L3R0PjwvYT48dHQ+PGZvbnQgc2l6ZT0y
Pl0NCk9uIEJlaGFsZiBPZiBBbmRyZXcgRy4gTWFsaXM8YnI+DQpTZW50OiBNb25kYXksIE1hcmNo
IDA1LCAyMDEyIDY6NTQgUE08YnI+DQpUbzogU3ByZWNoZXIsIE51cml0IChOU04gLSBJTC9Ib2Qg
SGFTaGFyb24pPGJyPg0KQ2M6IGlldGZAaWV0Zi5vcmc8YnI+DQpTdWJqZWN0OiBSZTogTGFzdCBD
YWxsOiAmbHQ7ZHJhZnQtYmV0dHMtaXR1LW9hbS1hY2gtY29kZS1wb2ludC0wMy50eHQmZ3Q7KEFs
bG9jYXRpb25vZg0KYW4gQXNzb2NpYXRlZCBDaGFubmVsIENvZGUgUG9pbnQgZm9yIFVzZSBieUlU
VS1UIEV0aGVybmV0YmFzZWQgT0FNKSB0bw0KSW5mb3JtYXRpb25hbCBSRkM8YnI+DQo8YnI+DQpJ
IHdvdWxkIGxpa2UgdG8gc3VwcG9ydCBOdXJpdCdzIGNvbW1lbnRzIGJlbG93LiBJbiBwYXJ0aWN1
bGFyLCBpbiB0aGU8YnI+DQpwYXN0IHRoZSBJVFUtVCBoYXMgZXhwYW5kZWQgdXBvbiBvciBjaGFu
Z2VkIHRoZSB1c2FnZSBvZiBJRVRGPGJyPg0KY29kZXBvaW50IGFsbG9jYXRpb25zLCBpbiBzb21l
IGNhc2VzIGluY29tcGF0aWJseSB3aXRoIGl0cyBvcmlnaW5hbDxicj4NCnVzYWdlIG9yIGRlZmlu
aXRpb24uIEluIHRoZSBmdXR1cmUsIGFsbCBjb2RlcG9pbnQgYWxsb2NhdGlvbnMgdG8gdGhlPGJy
Pg0KSVRVLVQgc2hvdWxkIGJlIHRpZWQgdG8gb25lIHNwZWNpZmljLCBkYXRlZCByZXZpc2lvbiBv
ZiB0aGVpcjxicj4NCnNwZWNpZmljYXRpb24gb25seS4gVGhpcyBpcyBzaW1pbGFyIHRvIHRoZSBJ
VFUtVCdzIG93biBwcm9jZXNzZXMsIHN1Y2g8YnI+DQphcyBzZWN0aW9uIDIuMi4xIG9mIFJlYy4g
QS41LCB3aGljaCByZXF1aXJlcyBhIHZlcnNpb24gbnVtYmVyIGFuZC9vcjxicj4NCmRhdGUgZm9y
IHJlZmVyZW5jZWQgb3V0c2lkZSBkb2N1bWVudHMgaW4gSVRVLVQgcmVjb21tZW5kYXRpb25zLjxi
cj4NCjxicj4NCkNoZWVycyw8YnI+DQpBbmR5PGJyPg0KPGJyPg0KJmd0Oy0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS1TbmlwPC9mb250PjwvdHQ+DQo8YnI+DQo8YnI+PHR0Pjxmb250IHNpemU9
Mj48YnI+DQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXzxi
cj4NCklldGYgbWFpbGluZyBsaXN0PGJyPg0KSWV0ZkBpZXRmLm9yZzxicj4NCjwvZm9udD48L3R0
PjxhIGhyZWY9aHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9pZXRmPjx0dD48
Zm9udCBzaXplPTI+aHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9pZXRmPC9m
b250PjwvdHQ+PC9hPjx0dD48Zm9udCBzaXplPTI+PGJyPg0KPC9mb250PjwvdHQ+DQo8YnI+DQo=
--=_alternative 0070FA63852579C8_=--


From malcolm.betts@zte.com.cn  Wed Mar 21 13:35:01 2012
Return-Path: <malcolm.betts@zte.com.cn>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 638EA21E812A for <ietf@ietfa.amsl.com>; Wed, 21 Mar 2012 13:35:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.218
X-Spam-Level: 
X-Spam-Status: No, score=-100.218 tagged_above=-999 required=5 tests=[AWL=-1.080, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, MIME_BASE64_TEXT=1.753, RCVD_DOUBLE_IP_LOOSE=0.76, SARE_SUB_ENC_WIN1255=0.647, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ot0611mGcvun for <ietf@ietfa.amsl.com>; Wed, 21 Mar 2012 13:35:00 -0700 (PDT)
Received: from mx5.zte.com.cn (mx6.zte.com.cn [95.130.199.165]) by ietfa.amsl.com (Postfix) with ESMTP id 3A69021E8102 for <ietf@ietf.org>; Wed, 21 Mar 2012 13:35:00 -0700 (PDT)
Received: from [10.30.17.99] by mx5.zte.com.cn with surfront esmtp id 1228011182326; Thu, 22 Mar 2012 04:00:52 +0800 (CST)
Received: from [10.30.3.20] by [192.168.168.15] with StormMail ESMTP id 84000.1346409004; Thu, 22 Mar 2012 04:34:53 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse01.zte.com.cn with ESMTP id q2LKYsdQ067183; Thu, 22 Mar 2012 04:34:54 +0800 (GMT-8) (envelope-from Malcolm.BETTS@zte.com.cn)
In-Reply-To: <E4873516F3FC7547BCFE792C7D94039C016F6EE0@DEMUEXC013.nsn-intra.net>
References: <8fab01cd014c$dea8f551$5e209f0a@nsnintra.net> <E4873516F3FC7547BCFE792C7D94039C016F6EE0@DEMUEXC013.nsn-intra.net>
To: "Sprecher, Nurit (NSN - IL/Hod HaSharon)" <nurit.sprecher@nsn.com>
Subject: =?windows-1255?B?UkU6IOTw4+XvOiBSRTogTGFzdCBDYWxsOjxkcmFmdC1iZXR0cy1pdHUt?= =?windows-1255?B?b2FtLWFjaC1jb2RlLXBvaW50LTAzLnR4dD4oQWxsb2NhdGlvbm9mCWFu?= =?windows-1255?B?IEFzc29jaWF0ZWQgQ2hhbm5lbCBDb2RlIFBvaW50IGZvciBVc2U=?= =?windows-1255?B?IGJ5SVRVLVQgRXRoZXJuZXRiYXNlZCBPQU0pIHRv?= =?windows-1255?B?CUluZm9ybWF0aW9uYWwgUkZD?=
MIME-Version: 1.0
X-KeepSent: 64E69521:55EAB63F-852579C8:006EE6A1; type=4; name=$KeepSent
X-Mailer: Lotus Notes Release 8.5.1 September 28, 2009
Message-ID: <OF64E69521.55EAB63F-ON852579C8.006EE6A1-852579C8.00710D12@zte.com.cn>
From: Malcolm.BETTS@zte.com.cn
Date: Wed, 21 Mar 2012 15:34:46 -0500
X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 8.5.1FP4|July 25, 2010) at 2012-03-22 04:34:53, Serialize complete at 2012-03-22 04:34:53
Content-Type: multipart/alternative; boundary="=_alternative 00710D11852579C8_="
X-MAIL: mse01.zte.com.cn q2LKYsdQ067183
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, 21 Mar 2012 20:35:01 -0000

This is a multipart message in MIME format.
--=_alternative 00710D11852579C8_=
Content-Type: text/plain; charset="windows-1255"
Content-Transfer-Encoding: base64

TnVyaXQsDQoNClNlY3Rpb24gMiCTU2NvcGUgb2YgdGhlIEV0aGVybmV0IGJhc2VkIE9BTSBBQ0gg
VHlwZZQgY29udGFpbnMgdGhlIA0KZm9sbG93aW5nIHRleHQ6DQoNCiJUaGUgY29kZSBwb2ludCBh
bGxvY2F0ZWQgYnkgdGhpcyBkb2N1bWVudCBpcyBpbnRlbmRlZCB0byBiZSB1c2VkIG9ubHkgZm9y
IA0KRXRoZXJuZXQgYmFzZWQgT0FNIG1lc3NhZ2VzLCBkZWZpbmVkIGluIHRoZSBJVFUtVCBSZWNv
bW1lbmRhdGlvbiANCltHLjgxMTMuMV0sIGNhcnJpZWQgaW4gdGhlIEctQUNoIC4gVGhlc2UgRXRo
ZXJuZXQgYmFzZWQgT0FNIG1lc3NhZ2VzIGFuZCANCnByb2NlZHVyZXMsIGFkZHJlc3MgdGhlIE9B
TSBmdW5jdGlvbmFsIHJlcXVpcmVtZW50cyBkZWZpbmVkIGluIFtSRkM1ODYwXS4gDQpPdGhlciBt
ZXNzYWdlIHR5cGVzIHNob3VsZCBub3QgYmUgY2FycmllZCBiZWhpbmQgdGhpcyBjb2RlIHBvaW50
LiINCg0KVGhlIHJlc3RyaWN0aW9ucyBvbiB0aGUgZnV0dXJlIHVzZSBvZiB0aGUgY29kZSBwb2lu
dCBjb3VsZCBiZSBtYWRlIG1vcmUgDQpleHBsaWNpdCBieSBtb2RpZnlpbmcgdGhlIHRleHQgYXMg
Zm9sbG93czoNCg0KVGhlIGNvZGUgcG9pbnQgYWxsb2NhdGVkIGJ5IHRoaXMgZG9jdW1lbnQgc2hv
dWxkIG9ubHkgYmUgdXNlZCBmb3IgRXRoZXJuZXQgDQpiYXNlZCBPQU0gbWVzc2FnZXMsIGRlZmlu
ZWQgaW4gdGhlIElUVS1UIFJlY29tbWVuZGF0aW9uIFtHLjgxMTMuMV0sIA0KY2FycmllZCBpbiB0
aGUgRy1BQ2guIFRoZSBtZXNzYWdlcyBhbmQgcHJvY2VkdXJlcyBjYXJyaWVkIGJlaGluZCB0aGlz
IGNvZGUgDQpwb2ludCwgYXJlIHJlc3RyaWN0ZWQgdG8gb25seSB0aG9zZSB0aGF0IHRoZSBhZGRy
ZXNzIHRoZSBPQU0gZnVuY3Rpb25hbCANCnJlcXVpcmVtZW50cyBkZWZpbmVkIGluIFtSRkM1ODYw
XS4gT3RoZXIgbWVzc2FnZSB0eXBlcyBzaG91bGQgbm90IGJlIA0KY2FycmllZCBiZWhpbmQgdGhp
cyBjb2RlIHBvaW50Lg0KDQpJIGhvcGUgdGhhdCB0aGlzIGFkZHJlc3NlcyB5b3VyIGNvbmNlcm4u
DQoNClJlZ2FyZHMsDQoNCk1hbGNvbG0NCg0KDQoNCg0KIlNwcmVjaGVyLCBOdXJpdCAoTlNOIC0g
SUwvSG9kIEhhU2hhcm9uKSIgPG51cml0LnNwcmVjaGVyQG5zbi5jb20+IA0KMTQvMDMvMjAxMiAw
Njo0MyBBTQ0KDQpUbw0KIlNwcmVjaGVyLCBOdXJpdCAoTlNOIC0gSUwvSG9kIEhhU2hhcm9uKSIg
PG51cml0LnNwcmVjaGVyQG5zbi5jb20+LCANCiJBbmRyZXcgRy4gTWFsaXMiIDxhZ21hbGlzQGdt
YWlsLmNvbT4sICJleHQgUm9zcyBDYWxsb24iIA0KPHJjYWxsb25AanVuaXBlci5uZXQ+LCA8bWFs
Y29sbS5iZXR0c0B6dGUuY29tLmNuPg0KY2MNCjxpZXRmQGlldGYub3JnPg0KU3ViamVjdA0KUkU6
IOTw4+XvOiBSRTogTGFzdCANCkNhbGw6PGRyYWZ0LWJldHRzLWl0dS1vYW0tYWNoLWNvZGUtcG9p
bnQtMDMudHh0PihBbGxvY2F0aW9ub2YgICBhbiANCkFzc29jaWF0ZWQgQ2hhbm5lbCBDb2RlIFBv
aW50IGZvciBVc2UgYnlJVFUtVCBFdGhlcm5ldGJhc2VkIE9BTSkgdG8gDQpJbmZvcm1hdGlvbmFs
IFJGQw0KDQoNCg0KDQoNCg0KTWFsY29sbSwNCkFzIG1lbnRpb25lZCBiZWZvcmUsIEkgY2Fubm90
IHN1cHBvcnQgdGhlIHB1YmxpY2F0aW9uIG9mIHRoZSBjdXJyZW50IA0KdmVyc2lvbiBvZiBkcmFm
dC1iZXR0cy4uLml0IG11c3QgYmUgcmV2aXNlZCBmaXJzdCB0byBhZGRyZXNzIHRoZSBjb25jZXJu
cyANCkkgYW5kIG90aGVycyByYWlzZWQgb24gdGhlIGxpc3QuIA0KTWF5YmUgeW91IGNvdWxkIGNs
YXJpZnkgaG93IHRoZSB0ZXh0IGluIHlvdXIgZHJhZnQgY2FuIGJlIGltcHJvdmVkIHRvIA0KcHJv
dGVjdCB0aGUgdXNlIG9mIHRoZSBjb2RlIHBvaW50IGZyb20gZnV0dXJlIGV4dGVuc2lvbnMgYmV5
b25kIHRoZSANCnB1cnBvc2Ugb2YgdGhlIGNvZGUgcG9pbnQgYWxsb2NhdGlvbj8NCkJlc3QgcmVn
YXJkcywNCk51cml0IA0KDQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KDQoNCj4t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tc25pcA0KX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX18NCklldGYgbWFpbGluZyBsaXN0DQpJZXRmQGlldGYub3JnDQpo
dHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2lldGYNCg0KDQoNCg0KDQo=
--=_alternative 00710D11852579C8_=
Content-Type: text/html; charset="windows-1255"
Content-Transfer-Encoding: base64

PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2VyaWYiPk51cml0LDwvZm9udD4NCjxicj4NCjxicj48
Zm9udCBzaXplPTIgZmFjZT0ic2Fucy1zZXJpZiI+U2VjdGlvbiAyIJNTY29wZSBvZiB0aGUgRXRo
ZXJuZXQgYmFzZWQNCk9BTSBBQ0ggVHlwZZQgY29udGFpbnMgdGhlIGZvbGxvd2luZyB0ZXh0Ojwv
Zm9udD4NCjxicj4NCjxicj48Zm9udCBzaXplPTIgZmFjZT0ic2Fucy1zZXJpZiI+JnF1b3Q7VGhl
IGNvZGUgcG9pbnQgYWxsb2NhdGVkIGJ5IHRoaXMNCmRvY3VtZW50IGlzIGludGVuZGVkIHRvIGJl
IHVzZWQgb25seSBmb3IgRXRoZXJuZXQgYmFzZWQgT0FNIG1lc3NhZ2VzLCBkZWZpbmVkDQppbiB0
aGUgSVRVLVQgUmVjb21tZW5kYXRpb24gW0cuODExMy4xXSwgY2FycmllZCBpbiB0aGUgRy1BQ2gg
LiBUaGVzZSBFdGhlcm5ldA0KYmFzZWQgT0FNIG1lc3NhZ2VzIGFuZCBwcm9jZWR1cmVzLCBhZGRy
ZXNzIHRoZSBPQU0gZnVuY3Rpb25hbCByZXF1aXJlbWVudHMNCmRlZmluZWQgaW4gW1JGQzU4NjBd
LiBPdGhlciBtZXNzYWdlIHR5cGVzIHNob3VsZCBub3QgYmUgY2FycmllZCBiZWhpbmQNCnRoaXMg
Y29kZSBwb2ludC4mcXVvdDs8L2ZvbnQ+DQo8YnI+DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9InNh
bnMtc2VyaWYiPlRoZSByZXN0cmljdGlvbnMgb24gdGhlIGZ1dHVyZSB1c2Ugb2YNCnRoZSBjb2Rl
IHBvaW50IGNvdWxkIGJlIG1hZGUgbW9yZSBleHBsaWNpdCBieSBtb2RpZnlpbmcgdGhlIHRleHQg
YXMgZm9sbG93czo8L2ZvbnQ+DQo8YnI+DQo8YnI+PGZvbnQgc2l6ZT0yIGZhY2U9InNhbnMtc2Vy
aWYiPlRoZSBjb2RlIHBvaW50IGFsbG9jYXRlZCBieSB0aGlzIGRvY3VtZW50DQpzaG91bGQgb25s
eSBiZSB1c2VkIGZvciBFdGhlcm5ldCBiYXNlZCBPQU0gbWVzc2FnZXMsIGRlZmluZWQgaW4gdGhl
IElUVS1UDQpSZWNvbW1lbmRhdGlvbiBbRy44MTEzLjFdLCBjYXJyaWVkIGluIHRoZSBHLUFDaC4g
VGhlIG1lc3NhZ2VzIGFuZCBwcm9jZWR1cmVzDQpjYXJyaWVkIGJlaGluZCB0aGlzIGNvZGUgcG9p
bnQsIGFyZSByZXN0cmljdGVkIHRvIG9ubHkgdGhvc2UgdGhhdCB0aGUgYWRkcmVzcw0KdGhlIE9B
TSBmdW5jdGlvbmFsIHJlcXVpcmVtZW50cyBkZWZpbmVkIGluIFtSRkM1ODYwXS4gT3RoZXIgbWVz
c2FnZSB0eXBlcw0Kc2hvdWxkIG5vdCBiZSBjYXJyaWVkIGJlaGluZCB0aGlzIGNvZGUgcG9pbnQu
PC9mb250Pg0KPGJyPg0KPGJyPjxmb250IHNpemU9MiBmYWNlPSJBcmlhbCI+SSBob3BlIHRoYXQg
dGhpcyBhZGRyZXNzZXMgeW91ciBjb25jZXJuLjwvZm9udD4NCjxicj4NCjxicj48Zm9udCBzaXpl
PTIgZmFjZT0iQXJpYWwiPlJlZ2FyZHMsPC9mb250Pg0KPGJyPg0KPGJyPjxmb250IHNpemU9MiBm
YWNlPSJBcmlhbCI+TWFsY29sbTwvZm9udD4NCjxicj4NCjxicj4NCjxicj4NCjxicj4NCjx0YWJs
ZSB3aWR0aD0xMDAlPg0KPHRyIHZhbGlnbj10b3A+DQo8dGQgd2lkdGg9MzYlPjxmb250IHNpemU9
MSBmYWNlPSJzYW5zLXNlcmlmIj48Yj4mcXVvdDtTcHJlY2hlciwgTnVyaXQgKE5TTg0KLSBJTC9I
b2QgSGFTaGFyb24pJnF1b3Q7ICZsdDtudXJpdC5zcHJlY2hlckBuc24uY29tJmd0OzwvYj4gPC9m
b250Pg0KPHA+PGZvbnQgc2l6ZT0xIGZhY2U9InNhbnMtc2VyaWYiPjE0LzAzLzIwMTIgMDY6NDMg
QU08L2ZvbnQ+DQo8dGQgd2lkdGg9NjMlPg0KPHRhYmxlIHdpZHRoPTEwMCU+DQo8dHIgdmFsaWdu
PXRvcD4NCjx0ZD4NCjxkaXYgYWxpZ249cmlnaHQ+PGZvbnQgc2l6ZT0xIGZhY2U9InNhbnMtc2Vy
aWYiPlRvPC9mb250PjwvZGl2Pg0KPHRkPjxmb250IHNpemU9MSBmYWNlPSJzYW5zLXNlcmlmIj4m
cXVvdDtTcHJlY2hlciwgTnVyaXQgKE5TTiAtIElML0hvZA0KSGFTaGFyb24pJnF1b3Q7ICZsdDtu
dXJpdC5zcHJlY2hlckBuc24uY29tJmd0OywgJnF1b3Q7QW5kcmV3IEcuIE1hbGlzJnF1b3Q7DQom
bHQ7YWdtYWxpc0BnbWFpbC5jb20mZ3Q7LCAmcXVvdDtleHQgUm9zcyBDYWxsb24mcXVvdDsgJmx0
O3JjYWxsb25AanVuaXBlci5uZXQmZ3Q7LA0KJmx0O21hbGNvbG0uYmV0dHNAenRlLmNvbS5jbiZn
dDs8L2ZvbnQ+DQo8dHIgdmFsaWduPXRvcD4NCjx0ZD4NCjxkaXYgYWxpZ249cmlnaHQ+PGZvbnQg
c2l6ZT0xIGZhY2U9InNhbnMtc2VyaWYiPmNjPC9mb250PjwvZGl2Pg0KPHRkPjxmb250IHNpemU9
MSBmYWNlPSJzYW5zLXNlcmlmIj4mbHQ7aWV0ZkBpZXRmLm9yZyZndDs8L2ZvbnQ+DQo8dHIgdmFs
aWduPXRvcD4NCjx0ZD4NCjxkaXYgYWxpZ249cmlnaHQ+PGZvbnQgc2l6ZT0xIGZhY2U9InNhbnMt
c2VyaWYiPlN1YmplY3Q8L2ZvbnQ+PC9kaXY+DQo8dGQ+PGZvbnQgc2l6ZT0xIGZhY2U9InNhbnMt
c2VyaWYiPlJFOiDk8OPl7zogUkU6IExhc3QgQ2FsbDombHQ7ZHJhZnQtYmV0dHMtaXR1LW9hbS1h
Y2gtY29kZS1wb2ludC0wMy50eHQmZ3Q7KEFsbG9jYXRpb25vZg0KJm5ic3A7ICZuYnNwOyAmbmJz
cDsgJm5ic3A7YW4gQXNzb2NpYXRlZCBDaGFubmVsIENvZGUgUG9pbnQgZm9yDQpVc2UgYnlJVFUt
VCBFdGhlcm5ldGJhc2VkIE9BTSkgdG8gJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7SW5mb3Jt
YXRpb25hbA0KUkZDPC9mb250PjwvdGFibGU+DQo8YnI+DQo8dGFibGU+DQo8dHIgdmFsaWduPXRv
cD4NCjx0ZD4NCjx0ZD48L3RhYmxlPg0KPGJyPjwvdGFibGU+DQo8YnI+DQo8YnI+DQo8YnI+PHR0
Pjxmb250IHNpemU9Mj5NYWxjb2xtLDxicj4NCkFzIG1lbnRpb25lZCBiZWZvcmUsIEkgY2Fubm90
IHN1cHBvcnQgdGhlIHB1YmxpY2F0aW9uIG9mIHRoZSBjdXJyZW50IHZlcnNpb24NCm9mIGRyYWZ0
LWJldHRzLi4uaXQgbXVzdCBiZSByZXZpc2VkIGZpcnN0IHRvIGFkZHJlc3MgdGhlIGNvbmNlcm5z
IEkgYW5kDQpvdGhlcnMgcmFpc2VkIG9uIHRoZSBsaXN0LiA8YnI+DQpNYXliZSB5b3UgY291bGQg
Y2xhcmlmeSBob3cgdGhlIHRleHQgaW4geW91ciBkcmFmdCBjYW4gYmUgaW1wcm92ZWQgdG8gcHJv
dGVjdA0KdGhlIHVzZSBvZiB0aGUgY29kZSBwb2ludCBmcm9tIGZ1dHVyZSBleHRlbnNpb25zIGJl
eW9uZCB0aGUgcHVycG9zZSBvZg0KdGhlIGNvZGUgcG9pbnQgYWxsb2NhdGlvbj88YnI+DQpCZXN0
IHJlZ2FyZHMsPGJyPg0KTnVyaXQgPGJyPg0KPGJyPg0KX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX188YnI+DQo8L2ZvbnQ+PC90dD4NCjxicj48dHQ+PGZvbnQgc2l6ZT0yPjxicj4NCiZn
dDstLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tc25pcDxicj4NCl9fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fPGJyPg0KSWV0ZiBtYWlsaW5nIGxpc3Q8YnI+DQpJ
ZXRmQGlldGYub3JnPGJyPg0KPC9mb250PjwvdHQ+PGEgaHJlZj1odHRwczovL3d3dy5pZXRmLm9y
Zy9tYWlsbWFuL2xpc3RpbmZvL2lldGY+PHR0Pjxmb250IHNpemU9Mj5odHRwczovL3d3dy5pZXRm
Lm9yZy9tYWlsbWFuL2xpc3RpbmZvL2lldGY8L2ZvbnQ+PC90dD48L2E+PHR0Pjxmb250IHNpemU9
Mj48YnI+DQo8YnI+DQo8YnI+DQo8YnI+DQo8L2ZvbnQ+PC90dD4NCjxicj4NCg==
--=_alternative 00710D11852579C8_=--


From fred@cisco.com  Wed Mar 21 13:44:08 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 2075D21F8649 for <ietf@ietfa.amsl.com>; Wed, 21 Mar 2012 13:44:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.367
X-Spam-Level: 
X-Spam-Status: No, score=-110.367 tagged_above=-999 required=5 tests=[AWL=0.232, 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 IIiqx6uRyWzc for <ietf@ietfa.amsl.com>; Wed, 21 Mar 2012 13:44:07 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by ietfa.amsl.com (Postfix) with ESMTP id E13AC21F8646 for <ietf@ietf.org>; Wed, 21 Mar 2012 13:44:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fred@cisco.com; l=1748; q=dns/txt; s=iport; t=1332362647; x=1333572247; h=subject:mime-version:from:in-reply-to:date:cc:message-id: references:to:content-transfer-encoding; bh=UMd2kkJxqnQyymTUJGm6YYDZnT7lu6I5G4OkexJrNq0=; b=BAOa3/mfOUKCLkySiP2o+j/0WYO6+oPuuHj6I8iU30oB1vY6ArQFWK+o oSPQ9IdhB6u+9UU4RSRkrpaZjyNaWJF6X49Thh1GbuOjJZZElCYM61KgC oq1BG6LsHfPC9RvhBJto8g0Fr7O/nTKMOG+fw8TaM+XPVW67inXsPqahU k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAIw8ak+Q/khM/2dsb2JhbABEtwmBB4IJAQEBAwESASc/BQsLRlcGNYdjBZkOnwOQHmMElV+FbYhSgWiCaA
X-IronPort-AV: E=Sophos;i="4.73,624,1325462400"; d="scan'208";a="132990954"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-1.cisco.com with ESMTP; 21 Mar 2012 20:44:05 +0000
Received: from Freds-Computer.local (dhcp-10-55-81-147.cisco.com [10.55.81.147]) by ams-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id q2LKi5rF027286; Wed, 21 Mar 2012 20:44:05 GMT
Received: from [127.0.0.1] by Freds-Computer.local (PGP Universal service); Wed, 21 Mar 2012 21:44:05 +0100
X-PGP-Universal: processed; by Freds-Computer.local on Wed, 21 Mar 2012 21:44:05 +0100
Subject: Re: IPv6 Zone Identifiers Considered Hateful
Mime-Version: 1.0 (Apple Message framework v1084)
From: Fred Baker <fred@cisco.com>
In-Reply-To: <82A794CE-B328-475F-9300-1B6BE628F7E3@sabahattin-gucukoglu.com>
Date: Wed, 21 Mar 2012 21:43:53 +0100
Message-Id: <C1BCE1FC-B35C-4D11-B6E7-AA8A6264A289@cisco.com>
References: <82A794CE-B328-475F-9300-1B6BE628F7E3@sabahattin-gucukoglu.com>
To: Sabahattin Gucukoglu <mail-dated-1334746550.15c4ac@sabahattin-gucukoglu.com>
X-Mailer: Apple Mail (2.1084)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Mar 2012 20:44:08 -0000

On Mar 19, 2012, at 11:55 AM, Sabahattin Gucukoglu wrote:

> I've obviously not been doing all my homework, and RFC 4007 slipped my =
attention.  Worse, for all the communication my IPv6 nodes are doing =
amongst themselves using link-local addresses, it's never really been =
much more than a hastily-justified curiosity why, when I ping one from =
the other using link-local-scoped addresses, I have to put in this zone =
identifier (%ifname on BSD and Linux).

To be honest, I'm still not sure I understand the argument for a zone =
identifier.

=46rom MIF's perspective, if the same prefix is placed on multiple =
interfaces, the system might see peers using a given address on multiple =
interfaces, and at least some devices might be expected to route between =
the interfaces. Architecturally, this can be easy to solve or hard. We =
have any number of cases (think about PPP for example) in which we =
bundle multiple interfaces under a common super-interface and "do =
something". In PPP Multilink, we might segment messages into smaller =
frames, distribute them across a number of interfaces to the same place, =
and reconstitute the original message on the other side. In this case, =
it seems that we want IP to use two layers of interfaces, a virtual one =
instantiated by multiple lower layer interfaces, and place the prefix on =
the virtual interface. When we are wondering what MAC address should be =
associated with a given IP address, we ask each of the lower layer =
interfaces, and if we get a result on one of them we know where we're =
going. The big issue will be routing among the physical interfaces - =
something required for it to be seamless and yet not as trivial as it =
might sound.

From koike.yoshinori@lab.ntt.co.jp  Wed Mar 21 14:01:36 2012
Return-Path: <koike.yoshinori@lab.ntt.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 DC2B721E80AF for <ietf@ietfa.amsl.com>; Wed, 21 Mar 2012 14:01:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.06
X-Spam-Level: 
X-Spam-Status: No, score=0.06 tagged_above=-999 required=5 tests=[AWL=0.150, 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 BOshI8Xp71hM for <ietf@ietfa.amsl.com>; Wed, 21 Mar 2012 14:01:36 -0700 (PDT)
Received: from tama50.ecl.ntt.co.jp (tama50.ecl.ntt.co.jp [129.60.39.147]) by ietfa.amsl.com (Postfix) with ESMTP id 118C621E80A8 for <ietf@ietf.org>; Wed, 21 Mar 2012 14:01:34 -0700 (PDT)
Received: from mfs6.rdh.ecl.ntt.co.jp (mfs6.rdh.ecl.ntt.co.jp [129.60.39.149]) by tama50.ecl.ntt.co.jp (8.13.8/8.13.8) with ESMTP id q2LL1XKb014659 for <ietf@ietf.org>; Thu, 22 Mar 2012 06:01:33 +0900
Received: from mfs6.rdh.ecl.ntt.co.jp (localhost [127.0.0.1]) by mfs6.rdh.ecl.ntt.co.jp (Postfix) with ESMTP id A03E765F1 for <ietf@ietf.org>; Thu, 22 Mar 2012 06:01:33 +0900 (JST)
Received: from imail3.m.ecl.ntt.co.jp (imail3.m.ecl.ntt.co.jp [129.60.5.248]) by mfs6.rdh.ecl.ntt.co.jp (Postfix) with ESMTP id 931BC65EB for <ietf@ietf.org>; Thu, 22 Mar 2012 06:01:33 +0900 (JST)
Received: from [129.60.11.43] (koike-pc.nslab.ecl.ntt.co.jp [129.60.11.43]) by imail3.m.ecl.ntt.co.jp (8.13.8/8.13.8) with ESMTP id q2LL1XAL021842;  Thu, 22 Mar 2012 06:01:33 +0900
Message-ID: <4F6A426B.2040806@lab.ntt.co.jp>
Date: Thu, 22 Mar 2012 06:04:43 +0900
From: Yoshinori Koike <koike.yoshinori@lab.ntt.co.jp>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt>(Allocation of an Associated Channel Code Point for Use byITU-T Ethernet	based OAM) to Informational RFC
References: <20120222151252.32262.82157.idtracker@ietfa.amsl.com> <039f01ccf174$fe79d780$fb6d8680$@olddog.co.uk> <44F4E579A764584EA9BDFD07D0CA0813075C936F@tlvmail1>
In-Reply-To: <44F4E579A764584EA9BDFD07D0CA0813075C936F@tlvmail1>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Mar 2012 21:01:37 -0000

Yes/Support.

I also support the following comment from Mr.Tom Petch.

"There is no reason not to approve the allocation of a code point
and furthermore, I believe we should do it now, to facilitate the 
migration of the existing boxes to an approved solution."

It is very difficult for me to find the reason that a Generic Associated 
Channel Type for ITU-T MPLS-TP OAM cannot be allocated, considering the 
following points.

-Request from ITU-T(LS370 - Current status of Recommendation ITU-T 
G.8113.1/Y.1372.1, Operations, Administration and Maintenance mechanism 
for MPLS-TP in Packet Transport Network (PTN)) which I think reflects a 
strong demand for G.8113.1 in transport networks which sustain Internet 
all over the world.
-Necessity to continue cooperation and collaboration with ITU-T
-Expected difficulties to progress G.8113.1 OAM protocol based on Rough 
Consensus in IETF

IMHO, this is the case that the IETF leverages standards that are 
defined and maintained by other organizations; we continue to work with 
those organizations on their standards and do not attempt to take them over.

Best regards,

Yoshinori

 > -----Original Message-----
 > From: ietf-announce-bounces@ietf.org [mailto:ietf-announce-
 > bounces@ietf.org] On Behalf Of The IESG
 > Sent: 22 February 2012 15:13
 > To: IETF-Announce
 > Subject: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt>
(Allocation of
an
 > Associated Channel Code Point for Use by ITU-T Ethernet based OAM) to
 > Informational RFC
 >
 >
 > The IESG has received a request from an individual submitter to
consider
 > the following document:
 > - 'Allocation of an Associated Channel Code Point for Use by ITU-T
 >    Ethernet based OAM'
 >   <draft-betts-itu-oam-ach-code-point-03.txt> as an 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-03-21. 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 assigns an Associated Channel Type code point for
 >    carrying Ethernet based Operations, Administration, and Management
 >    messages in the MPLS Generic Associated Channel (G-ACh).
 >
 > The file can be obtained via
 > http://datatracker.ietf.org/doc/draft-betts-itu-oam-ach-code-point/
 >
 > IESG discussion can be tracked via
 > http://datatracker.ietf.org/doc/draft-betts-itu-oam-ach-code-point/
 >
 >
 > No IPR declarations have been submitted directly on this I-D.
 > _______________________________________________
 > IETF-Announce mailing list
 > IETF-Announce@ietf.org
 > https://www.ietf.org/mailman/listinfo/ietf-announce



-- 
Yoshinori Koike
koike.yoshinori@lab.ntt.co.jp


From brian.e.carpenter@gmail.com  Wed Mar 21 14:51:49 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 ABA9C21F8688 for <ietf@ietfa.amsl.com>; Wed, 21 Mar 2012 14:51:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.497
X-Spam-Level: 
X-Spam-Status: No, score=-103.497 tagged_above=-999 required=5 tests=[AWL=0.102, 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 7UtPiQJQZzDt for <ietf@ietfa.amsl.com>; Wed, 21 Mar 2012 14:51:48 -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 8A57921F866D for <ietf@ietf.org>; Wed, 21 Mar 2012 14:51:48 -0700 (PDT)
Received: by eeke51 with SMTP id e51so501215eek.31 for <ietf@ietf.org>; Wed, 21 Mar 2012 14:51:47 -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=LwLuLEfR1SYbsYGfZKny1PN3TAVwG6usQmZgsZXIg9g=; b=G7mQG1sWVe5Qp6SLDozQfT/QyQKp/Jo32FMph+ZcPHtDEo1cDYPbLZtXpONlUgai/8 4MMD/w8tuaEhUle0515WbRWePuhEGnNxDS3QbiQvr3hqJtF7FstdbN4zaf4NXTKt1Pa+ IA6eKVkVGyKTwJ08YOA5UpvlALynLM82p5XeAc+INfAymzNSpMQI2nBqoTDvjti6edaZ i2NEh3fpyxXDn30mTfgS6dEodIV3gIp0L0NeHQleIPffkU1FisJLHQcIDjEIXGeoN1cE arGt8HNyCDHuMn9oq84XLWLD2k39Ko+pJ+myxL4361F3ZMEfGoL4f9zfpGpGwSTXgKbU NOQA==
Received: by 10.213.21.20 with SMTP id h20mr429897ebb.185.1332366707684; Wed, 21 Mar 2012 14:51:47 -0700 (PDT)
Received: from [10.1.1.4] ([121.98.251.219]) by mx.google.com with ESMTPS id z47sm10225804een.5.2012.03.21.14.51.44 (version=SSLv3 cipher=OTHER); Wed, 21 Mar 2012 14:51:46 -0700 (PDT)
Message-ID: <4F6A4D68.10905@gmail.com>
Date: Thu, 22 Mar 2012 10:51:36 +1300
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@cisco.com>
Subject: Re: IPv6 Zone Identifiers Considered Hateful
References: <82A794CE-B328-475F-9300-1B6BE628F7E3@sabahattin-gucukoglu.com> <C1BCE1FC-B35C-4D11-B6E7-AA8A6264A289@cisco.com>
In-Reply-To: <C1BCE1FC-B35C-4D11-B6E7-AA8A6264A289@cisco.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Mar 2012 21:51:49 -0000

On 2012-03-22 09:43, Fred Baker wrote:
> On Mar 19, 2012, at 11:55 AM, Sabahattin Gucukoglu wrote:
> 
>> I've obviously not been doing all my homework, and RFC 4007 slipped my attention.  Worse, for all the communication my IPv6 nodes are doing amongst themselves using link-local addresses, it's never really been much more than a hastily-justified curiosity why, when I ping one from the other using link-local-scoped addresses, I have to put in this zone identifier (%ifname on BSD and Linux).
> 
> To be honest, I'm still not sure I understand the argument for a zone identifier.

I've always viewed them as a fault diagnosis tool, mainly.
But the first paragraph of section 6 of RFC 4007 makes a stack
implementation argument:

>> 6.  Zone Indices
>> 
>>    Because the same non-global address may be in use in more than one
>>    zone of the same scope (e.g., the use of link-local address fe80::1
>>    in two separate physical links) and a node may have interfaces
>>    attached to different zones of the same scope (e.g., a router
>>    normally has multiple interfaces attached to different links), a node
>>    requires an internal means to identify to which zone a non-global
>>    address belongs.  This is accomplished by assigning, within the node,
>>    a distinct "zone index" to each zone of the same scope to which that
>>    node is attached, and by allowing all internal uses of an address to
>>    be qualified by a zone index.

In other words if the IETF doesn't define the zone index, every
implementor will have to do so anyway. Also, read the last clause
carefully: it says the stack MUST allow OPTIONAL use of the zone
index internally.

> From MIF's perspective, if the same prefix is placed on multiple interfaces, 

The prefix fe80::/10 is automatically on every interface. That's the
only case where I'm certain we need a zone index in practice, but the
definition isn't limited to that case.

   Brian

> the system might see peers using a given address on multiple interfaces, and at least some devices might be expected to route between the interfaces. Architecturally, this can be easy to solve or hard. We have any number of cases (think about PPP for example) in which we bundle multiple interfaces under a common super-interface and "do something". In PPP Multilink, we might segment messages into smaller frames, distribute them across a number of interfaces to the same place, and reconstitute the original message on the other side. In this case, it seems that we want IP to use two layers of interfaces, a virtual one instantiated by multiple lower layer interfaces, and place the prefix on the virtual interface. When we are wondering what MAC address should be associated with a given IP address, we ask each of the lower layer interfaces, and if we get a result on one of them we know where we're going. The big issue will be routing among the physical interfaces - something req
uired for it to be seamless and yet not as trivial as it might sound.
> 

From erminio.ottone_69@libero.it  Wed Mar 21 15:42:50 2012
Return-Path: <erminio.ottone_69@libero.it>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4A17D21E8148 for <ietf@ietfa.amsl.com>; Wed, 21 Mar 2012 15:42:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.719
X-Spam-Level: 
X-Spam-Status: No, score=-0.719 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UxjhscMwSPIP for <ietf@ietfa.amsl.com>; Wed, 21 Mar 2012 15:42:49 -0700 (PDT)
Received: from outrelay03.libero.it (outrelay03.libero.it [212.52.84.103]) by ietfa.amsl.com (Postfix) with ESMTP id 7E0A421E805A for <ietf@ietf.org>; Wed, 21 Mar 2012 15:42:49 -0700 (PDT)
X-CTCH-Spam: Unknown
X-CTCH-RefID: str=0001.0A0B020D.4F6A5968.0040,ss=1,re=0.000,fgs=0
X-libjamoibt: 1821
Received: from wmail32 (172.31.0.220) by outrelay03.libero.it (8.5.140) id 4F59EB9E01AEF495 for ietf@ietf.org; Wed, 21 Mar 2012 23:42:48 +0100
Message-ID: <6385413.260911332369768124.JavaMail.defaultUser@defaultHost>
Date: Wed, 21 Mar 2012 23:42:48 +0100 (CET)
From: "erminio.ottone_69@libero.it" <erminio.ottone_69@libero.it>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: R: RE: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt> (Allocation of	an Associated Channel Code Point for Use by	ITU-T	Ethernet based OAM) to Informational RFC
MIME-Version: 1.0
Content-Type: text/plain;charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-SenderIP: 87.9.60.18
X-libjamv: vOHg+jRI00Q=
X-libjamsun: mOWeDn5N/mrGYqwayZWpj/aUpWO5gziTADkMjMTNlgc=
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: "erminio.ottone_69@libero.it" <erminio.ottone_69@libero.it>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Mar 2012 22:42:50 -0000

I support the allocation of an ACH codepoint to G.8113.1, not precluding the 
ITU-T to progress refinements to the protocol following its own process.

As indicated by Russ, this approach "creates a situation where G.8113.1 
succeeded or fails based on the ITU-T members actions, with no finger pointing 
at the IETF" which, in my opinion, will help the two SDOs to improve their 
cooperation on a fair and reciprocal basis.

>-------- Original Message --------
>From: The IESG <iesg-secretary@ietf.org>
>Sent: Wed, 22 Feb 2012 07:12:52 -0800
>To: IETF-Announce <ietf-announce@ietf.org>
>Subject: Last Call: <draft-betts-itu-oam-ach-code-point-03.txt> (Allocation 
of	an Associated Channel Code Point for Use by ITU-T Ethernet	based OAM) to 
Informational RFC
>
>The IESG has received a request from an individual submitter to consider the 
following document:
>- 'Allocation of an Associated Channel Code Point for Use by ITU-T
>    Ethernet based OAM'
>   <draft-betts-itu-oam-ach-code-point-03.txt> as an 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-03-21. 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 assigns an Associated Channel Type code point for
>    carrying Ethernet based Operations, Administration, and Management
>    messages in the MPLS Generic Associated Channel (G-ACh).
>
>The file can be obtained via
>http://datatracker.ietf.org/doc/draft-betts-itu-oam-ach-code-point/
>
>IESG discussion can be tracked via
>http://datatracker.ietf.org/doc/draft-betts-itu-oam-ach-code-point/
>
>
>No IPR declarations have been submitted directly on this I-D.
>_______________________________________________
>IETF-Announce mailing list
>IETF-Announce@ietf.org
>https://www.ietf.org/mailman/listinfo/ietf-announce	
>
>



From huubatwork@gmail.com  Wed Mar 21 15:49:04 2012
Return-Path: <huubatwork@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 366C521E800E for <ietf@ietfa.amsl.com>; Wed, 21 Mar 2012 15:49:04 -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 Xp-Bs8JcLk+f for <ietf@ietfa.amsl.com>; Wed, 21 Mar 2012 15:49:03 -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 6119F21F8569 for <ietf@ietf.org>; Wed, 21 Mar 2012 15:49:03 -0700 (PDT)
Received: by wibhj6 with SMTP id hj6so19025wib.13 for <ietf@ietf.org>; Wed, 21 Mar 2012 15:49:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:disposition-notification-to:date:from:reply-to :user-agent:mime-version:to:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=8Y090b09jkBkDiFa19ImwwpTYnFB0LKuUnoxf7PHHvk=; b=iYbuHZcdbyo3ylFi8z5BjRC2gk7DtbQs7g2o6xldRsi4UzU4/pGygc+GLjSnhHFF6l qfRkbbaus2DNbUddzG4Xwl9SdylnS3uNoHm01k5LMP+qTbjhTbw62PtrhbLUhIJvsSQn UyFg61EZGt5HwqI7cMXNknhgZKutADAIu9Ic4p8IriqsMdRr+7QA1Gp0tPsdX4Y32sVT puOYQmZC0GpOC9xisx9A4gYHUAvfs/yoXYfg2fjxdmUgjMQmbRIzdM+zRBFe9DmS+C9t uC4qbt1HYPAg9rdc5vp6CU9ZT4xJBY/jq3MgtTVU38YHXcEvlY18BEby2DWl/K+L9ado FyKA==
Received: by 10.180.106.9 with SMTP id gq9mr12802128wib.17.1332370142585; Wed, 21 Mar 2012 15:49:02 -0700 (PDT)
Received: from McAsterix.local ([31.216.236.133]) by mx.google.com with ESMTPS id gp8sm301680wib.5.2012.03.21.15.49.01 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 21 Mar 2012 15:49:01 -0700 (PDT)
Message-ID: <4F6A5ADB.2090002@gmail.com>
Date: Wed, 21 Mar 2012 23:48:59 +0100
From: Huub van Helvoort <huubatwork@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Last Call: <draft-ietf-mpls-tp-oam-analysis-08.txt> (An Overview of the OAM Tool Set for MPLS based Transport Networks) to Informational RFC
References: <20120309205157.8304.55419.idtracker@ietfa.amsl.com>
In-Reply-To: <20120309205157.8304.55419.idtracker@ietfa.amsl.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: huubatwork@gmail.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Mar 2012 22:49:04 -0000

IESG,

I do *NOT* support this draft unless the following changes are made:

The first paragraph of section 8 Acknowledgements has to be removed:
It is an attempt to capture history, but lacks accuracy.
Removal does not impact the technical information in the draft;
the tools have evolved significantly from the strawman tools proposed
in Stockholm; some members of the MEAD team (I am one of them) do not
consider that an agreement on this proposal was reached.

I also request the removal of my name from this acknowledgements section
since I do not support this tool set, neither as an individual nor as
ITU-T Q10 rapporteur. The latter is implied by mentioning my name in
the same sentence as a WG chair and ADs.

Regards, Huub.

=============
> The IESG has received a request from the Multiprotocol Label Switching WG
> (mpls) to consider the following document:
> - 'An Overview of the OAM Tool Set for MPLS based Transport Networks'
>    <draft-ietf-mpls-tp-oam-analysis-08.txt>  as an 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-03-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 provides an overview of the OAM toolset for MPLS based
>     Transport Networks.  The toolset consists of a comprehensive set of
>     fault management and performance monitoring capabilities (operating
>     in the data-plane) which are appropriate for transport networks as
>     required in RFC 5860 and support the network and services at
>     different nested levels.  This overview includes a brief recap of
>     MPLS-TP OAM requirements and functions, and of generic mechanisms
>     created in the MPLS data plane to allow the OAM packets run in-band
>     and share their fate with data packets.  The protocol definitions for
>     each of the MPLS-TP OAM tools are defined in separate documents (RFCs
>     or Working Group drafts) which are referenced by this document.
>
>
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-oam-analysis/
>
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-oam-analysis/ballot/
>
>
> No IPR declarations have been submitted directly on this I-D.
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-announce

From ole@cisco.com  Wed Mar 21 16:33:39 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 8601C21E80F4; Wed, 21 Mar 2012 16:33:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.397
X-Spam-Level: 
X-Spam-Status: No, score=-109.397 tagged_above=-999 required=5 tests=[AWL=1.202, 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 JYOj9Xyq9fKm; Wed, 21 Mar 2012 16:33:39 -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 10B1621E80A2; Wed, 21 Mar 2012 16:33:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=ole@cisco.com; l=1923; q=dns/txt; s=iport; t=1332372818; x=1333582418; h=date:from:reply-to:to:cc:subject:message-id:mime-version; bh=XhgmlH/wTA0O3/7Mql6vs58nOnJP/F5JCq2xmcg4fJo=; b=RQ+OCRcvLXCGmdOO0d3/tpdYtzTEV/GN4tfyXy2JwDVMRZ7R1b2QDN/D K6yUdeXdnT6d2iwqytWmdaLFVbRBdB01qgp6lrsL6l4rapPz4K0WXtClo yNWIJ9eOPbyVdHms8ru3nvwJRkbY76RJ9AUYriDA0gxAkK6ydkvT9KrA3 M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AtoGAC5kak+rRDoJ/2dsb2JhbABEgxGzfoEHgiIBAiUtBA6BPhMJGYdnDJkEgzwQgU6ZZ5BiBIhWknaFRIMOgQJmgwc
X-IronPort-AV: E=Sophos;i="4.73,626,1325462400"; d="scan'208";a="34031862"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by mtv-iport-1.cisco.com with ESMTP; 21 Mar 2012 23:33:38 +0000
Received: from [10.86.255.229] ([10.86.255.229]) by mtv-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id q2LNXbYC000750; Wed, 21 Mar 2012 23:33:38 GMT
Date: Wed, 21 Mar 2012 16:33:36 -0700 (PDT)
From: Ole Jacobsen <ole@cisco.com>, Matthew Ford <ford@isoc.org>
To: The IETF <ietf@ietf.org>
Subject: Journals at the IETF - calling all contributors!
Message-ID: <alpine.OSX.2.01.1203211629110.28243@rabdullah.local>
User-Agent: Alpine 2.01 (OSX 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: IETF 83 Attendees <83attendees@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Ole Jacobsen <ole@cisco.com>, Matthew Ford <ford@isoc.org>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Mar 2012 23:33:39 -0000

If you have attended any IETF meetings in the last several years you
will have noticed two publications available from the registration
desk or literature table:
 
* The IETF Journal, published by the Internet Society
 http://www.internetsociety.org/ietfjournal
 
 and
 
* The Internet Protocol Journal (IPJ), published by Cisco Systems
 http://www.cisco.com/ipj
 
The IETF Journal delivers information about the work of the IETF to a 
worldwide audience of technical developers and decision makers. It 
provides an easy-to-understand and comprehensive overview of IETF 
technical and organisational developments. Each issue highlights some 
of the hot issues being discussed at and around the IETF meetings and 
may also feature articles covering other IETF-related topics.
 
The Internet Protocol Journal is intended to serve as an informational 
and educational resource for engineering professionals involved in the 
design, development, and operation of public and private internets and 
intranets. The IP Journal carries tutorial articles as well as 
implementation/operation articles and technology and standardization 
updates for all levels of the protocol stack.
 
These two journals cover similar ground, but the former is more 
focused specifically on the work of the IETF whereas the latter 
carries articles that aren't necessarily always directly related to 
the IETF. In some cases, the same article has appeared in both 
journals.
 
Both publications rely heavily on the contributions of volunteers in 
the IETF and elsewhere, technical experts who can clearly explain 
networking technology. If you are interested in contributing an 
article to either of these journals, please contact:
 
Mat Ford, Managing Editor of the IETF Journal <ford@isoc.org>
 
and
 
Ole Jacobsen, Editor and Publisher of IPJ  <ole@cisco.com>

We look forward to seeing you in Paris!


From fred@cisco.com  Wed Mar 21 17:30:43 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 D710121E8042 for <ietf@ietfa.amsl.com>; Wed, 21 Mar 2012 17:30:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.425
X-Spam-Level: 
X-Spam-Status: No, score=-110.425 tagged_above=-999 required=5 tests=[AWL=0.174, 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 1z3RrGm-nELY for <ietf@ietfa.amsl.com>; Wed, 21 Mar 2012 17:30:43 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by ietfa.amsl.com (Postfix) with ESMTP id E89C721E8015 for <ietf@ietf.org>; Wed, 21 Mar 2012 17:30:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fred@cisco.com; l=1000; q=dns/txt; s=iport; t=1332376243; x=1333585843; h=subject:mime-version:from:in-reply-to:date:cc:message-id: references:to:content-transfer-encoding; bh=nF2r+tERk5RzKlkmCm6wqrOinizqefv9/b+fsYeBv00=; b=bG9cUGmkBrPurk31bs8SuY+rO8bEwpd1s3LwE6hB03l8Xq5KOR2mKHM0 tc/W6UyUYY5SVZzMT3PW+Wzcclq8hJyFbXd9Pykuu4MCyBDkMshFhX/T5 DeH5Oob/dGuUO0VjCpBtJD9RZyn890CRKr0+smFin34wmC8HW+Tu+2Z+L A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAFZxak+Q/khL/2dsb2JhbABDtxqBB4IJAQEBAwESASc/EAsYLlcGNYdjBZ8/lyiKXIUjYwSVX4VtiFKBaIJogVM
X-IronPort-AV: E=Sophos;i="4.73,626,1325462400"; d="scan'208";a="133002089"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by ams-iport-1.cisco.com with ESMTP; 22 Mar 2012 00:30:41 +0000
Received: from Freds-Computer.local (dhcp-10-55-81-147.cisco.com [10.55.81.147]) by ams-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id q2M0Uf0b020831; Thu, 22 Mar 2012 00:30:41 GMT
Received: from [127.0.0.1] by Freds-Computer.local (PGP Universal service); Thu, 22 Mar 2012 01:30:41 +0100
X-PGP-Universal: processed; by Freds-Computer.local on Thu, 22 Mar 2012 01:30:41 +0100
Subject: Re: IPv6 Zone Identifiers Considered Hateful
Mime-Version: 1.0 (Apple Message framework v1084)
From: Fred Baker <fred@cisco.com>
In-Reply-To: <4F6A4D68.10905@gmail.com>
Date: Thu, 22 Mar 2012 01:29:56 +0100
Message-Id: <CA9F71F7-350D-4265-B469-0CA150D39FCE@cisco.com>
References: <82A794CE-B328-475F-9300-1B6BE628F7E3@sabahattin-gucukoglu.com> <C1BCE1FC-B35C-4D11-B6E7-AA8A6264A289@cisco.com> <4F6A4D68.10905@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1084)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Mar 2012 00:30:43 -0000

On Mar 21, 2012, at 10:51 PM, Brian E Carpenter wrote:
> In other words if the IETF doesn't define the zone index, every
> implementor will have to do so anyway. Also, read the last clause
> carefully: it says the stack MUST allow OPTIONAL use of the zone
> index internally.

Implementors generally *do* have some internal form of a zone index, and =
it doesn't look at all like what the RFC describes. It is a machine =
address or a lookup index of some kind for a table that is associated =
with an interface. Sometimes, part of it is a card identifier.

>> =46rom MIF's perspective, if the same prefix is placed on multiple =
interfaces,=20
>=20
> The prefix fe80::/10 is automatically on every interface. That's the
> only case where I'm certain we need a zone index in practice, but the
> definition isn't limited to that case.

The use of something to get me to the interface table in question isn't =
what I am questioning. It's the use of that particular something...=

From twalsh@juniper.net  Wed Mar 21 17:38:55 2012
Return-Path: <twalsh@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 A927221E8015 for <ietf@ietfa.amsl.com>; Wed, 21 Mar 2012 17:38:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.425
X-Spam-Level: 
X-Spam-Status: No, score=-106.425 tagged_above=-999 required=5 tests=[AWL=0.173, 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 pIxQs1je+TCg for <ietf@ietfa.amsl.com>; Wed, 21 Mar 2012 17:38:55 -0700 (PDT)
Received: from exprod7og123.obsmtp.com (exprod7og123.obsmtp.com [64.18.2.24]) by ietfa.amsl.com (Postfix) with ESMTP id 6F0E221E8017 for <ietf@ietf.org>; Wed, 21 Mar 2012 17:38:54 -0700 (PDT)
Received: from P-EMHUB01-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob123.postini.com ([64.18.6.12]) with SMTP ID DSNKT2p0nTcTzvkhBEqgU1UKUElC9/KKuVnL@postini.com; Wed, 21 Mar 2012 17:38:54 PDT
Received: from p-emfe01-wf.jnpr.net (172.28.145.24) by P-EMHUB01-HQ.jnpr.net (172.24.192.35) with Microsoft SMTP Server (TLS) id 8.3.213.0; Wed, 21 Mar 2012 17:37:31 -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, 21 Mar 2012 20:37:30 -0400
From: Thomas Walsh <twalsh@juniper.net>
To: "ietf@ietf.org" <ietf@ietf.org>
Date: Wed, 21 Mar 2012 20:37:26 -0400
Subject: RE: Last Call:<draft-betts-itu-oam-ach-code-point-03.txt> (Allocation	of anAssociated Channel Code Point for Use by	ITU-T Ethernet basedOAM) to Informational RFC
Thread-Topic: Last Call:<draft-betts-itu-oam-ach-code-point-03.txt> (Allocation	of anAssociated Channel Code Point for Use by	ITU-T Ethernet basedOAM) to Informational RFC
Thread-Index: Ac0HUrBsWwoVKD7YRFOl58v5OZ6i5AAZ2WWg
Message-ID: <A4C6A166C36F5F40A5767E6F66358FC0BB89D828EE@EMBX01-WF.jnpr.net>
References: <20120222151252.32262.82157.idtracker@ietfa.amsl.com><03a301ccf174$ff953290$febf97b0$@olddog.co.uk><515703B08A3A064C9CC8C09ACCC710DC0631679E@XMB-RCD-103.cisco.com><C71DA9B1-A61F-4C5D-8DCE-3702271CBB6D@vigilsec.com><4F4FA70B.2030906@pi.nu><D0F60388-D852-4815-917A-B14BF40C64FB@vigilsec.com><BD60EA38ED03AF5A21868DF1@PST.JCK.COM> <4F4FC252.9010001@cisco.com> <C3E581FB44D46BF4128A2229@PST.JCK.COM> <029b01ccfb84$4e4e2220$4001a8c0@gateway.2wire.net> <4F55F92F.1020105@cisco.com> <005701ccfbad$5c6d9060$4001a8c0@gateway.2wire.net> <4F69B630.9050909@cisco.com>
In-Reply-To: <4F69B630.9050909@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_A4C6A166C36F5F40A5767E6F66358FC0BB89D828EEEMBX01WFjnprn_"
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, 22 Mar 2012 00:38:55 -0000

--_000_A4C6A166C36F5F40A5767E6F66358FC0BB89D828EEEMBX01WFjnprn_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

SSBkb27igJl0IHNlZSBhIHByb2JsZW0gd2l0aCB0aGUgIElFVEYgcHJvY2Vzcy4gV2Ugc2hvdWxk
IGhvd2V2ZXIgdW5kZXJzdGFuZCB3aHkgdGhlIElUVS1UIHByb2Nlc3MgZmFpbGVkIHRvIHJlYWNo
IGEgY29uc2Vuc3VzIG9yIGFwcHJvdmFsLg0KDQpEcmFmdC1iZXR0cyBzdGF0ZXMgIOKAnEEgbnVt
YmVyIG9mIGV4cGVydHMgaW4gdGhlIElFVEYgZG8gbm90IGNvbnNpZGVyIHRoYXQgdGhlIGRldmVs
b3BtZW50IG9yIGRlcGxveW1lbnQgb2YgYSBzZWNvbmQgcHJvdG9jb2wgc29sdXRpb24gd2l0aGlu
IHRoZSBzYW1lIGFyY2hpdGVjdHVyYWwgcHJvYmxlbSBzcGFjZSBpcyBuZWNlc3Nhcnkgb3IgYWR2
aXNhYmxl4oCdLiAgVGhpcyBzdGF0ZW1lbnQgZnJvbSBkcmFmdC1iZXR0cyBpc27igJl0IHdoeSBJ
VFUtVCBTRyAxNSBmYWlsZWQgdG8gYXBwcm92ZSBHLjgxMTMuMS4gIENvbnNlbnN1cyBvciBhcHBy
b3ZhbCBpbiBJVFUtVCBpcyBkZWNpZGVkIG9ubHkgYnkgc2VjdG9yIG1lbWJlcnMgYW5kIG1lbWJl
ciBzdGF0ZXMuDQoNCg0KVGhlIHJlZmVyZW5jZWQgbGlhaXNvbiBpbiBkcmFmdC1iZXR0cyBtZW50
aW9ucyDigJxPbmUgb2YgdGhlIGlzc3VlcyB0aGF0IHByZXZlbnRlZCB0aGUgYXBwcm92YWwgaW4g
U0cgMTUgd2FzIHRoZSBsYWNrIG9mIGFuIEFDaCBjb2RlIHBvaW50IHRvIHN1cHBvcnQgdGhpcyBS
ZWNvbW1lbmRhdGlvbi7igJ0gICBPbmUgb2YgdGhlIHJlYXNvbnM/ICBJIHJlYWQgdGhhdCB0byBt
ZWFuIHRoZXJlIHdlcmUgb3RoZXIgcmVhc29ucyBhcyB3ZWxsLg0KDQoNCklFVEYgY291bGQgYXNr
IFNHIDE1LCB2aWEgbGlhaXNvbiwgIGZvciBtb3JlIGluZm9ybWF0aW9uIGFzIHRvIHRoZSDigJxv
dGhlciByZWFzb25z4oCdIHdoeSB0aGUgIElUVS1UIHByb2Nlc3MgZmFpbGVkIHRvIGFjaGlldmUg
dG8gYWNoaWV2ZSBhIGNvbnNlbnN1cyBhcm91bmQgRy44MTEzLjEuDQoNCg0KDQpTRyAxNSwgYWRt
aXR0aW5nIHRoZXkgZmFpbGVkIGluIHRoZWlyIHByb2Nlc3MgdG8gcmVhY2ggYXBwcm92YWwgb24g
Ry44MTEzLjEsIHN0YXRlcyBpbiB0aGUgcmVmZXJlbmNlZCBsaWFpc29uICDigJxVbmZvcnR1bmF0
ZWx5IHRoZSBTdHVkeSBHcm91cCBjb3VsZCBub3QgYXBwcm92ZSB0aGlzIFJlY29tbWVuZGF0aW9u
IHNvIGl0IHdhcyBmb3J3YXJkZWQgdG8gdGhlIFdUU0EgKDIwLTI5IE5vdmVtYmVyIDIwMTIpIGZv
ciBhcHByb3ZhbC7igJ0NCg0KDQoNCldUU0EgaXMgZGlmZmVyZW50IGZyb20gU0cgMTUuICBJIGRv
buKAmXQga25vdyB3aGF0IHdpbGwgaGFwcGVuIHRoZXJlLCBhbmQgd2hldGhlciBhcHByb3ZhbCB3
aWxsIHJlc3VsdC4gIEFzIG9mIG5vdywgY29uc2Vuc3VzL2FwcHJvdmFsIHdhcyBub3QgYWNoaWV2
ZWQgd2l0aGluIHRoZSBJVFUtVCBwcm9jZXNzLg0KDQoNCg0KTXkgdmlldyBpcyBJRVRGIHNob3Vs
ZCB3YWl0IGF0IGxlYXN0IHVudGlsIHRoZXJlIGlzIGFuIGFwcHJvdmVkIFJlY29tbWVuZGF0aW9u
Lg0KDQpUb20gV2Fsc2gNCg0K

--_000_A4C6A166C36F5F40A5767E6F66358FC0BB89D828EEEMBX01WFjnprn_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+PGhlYWQ+PG1ldGEgaHR0cC1lcXVpdj1Db250ZW50LVR5cGUgY29udGVu
dD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij48bWV0YSBuYW1lPUdlbmVyYXRvciBjb250ZW50
PSJNaWNyb3NvZnQgV29yZCAxMiAoZmlsdGVyZWQgbWVkaXVtKSI+PHN0eWxlPjwhLS0NCi8qIEZv
bnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Q2FsaWJyaTsNCglw
YW5vc2UtMToyIDE1IDUgMiAyIDIgNCAzIDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5
OkNvbnNvbGFzOw0KCXBhbm9zZS0xOjIgMTEgNiA5IDIgMiA0IDMgMiA0O30NCi8qIFN0eWxlIERl
ZmluaXRpb25zICovDQpwLk1zb05vcm1hbCwgbGkuTXNvTm9ybWFsLCBkaXYuTXNvTm9ybWFsDQoJ
e21hcmdpbjowaW47DQoJbWFyZ2luLWJvdHRvbTouMDAwMXB0Ow0KCWZvbnQtc2l6ZToxMi4wcHQ7
DQoJZm9udC1mYW1pbHk6IlRpbWVzIE5ldyBSb21hbiIsInNlcmlmIjsNCgljb2xvcjpibGFjazt9
DQphOmxpbmssIHNwYW4uTXNvSHlwZXJsaW5rDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCglj
b2xvcjpibHVlOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0KYTp2aXNpdGVkLCBzcGFu
Lk1zb0h5cGVybGlua0ZvbGxvd2VkDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjpw
dXJwbGU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQpwcmUNCgl7bXNvLXN0eWxlLXBy
aW9yaXR5Ojk5Ow0KCW1zby1zdHlsZS1saW5rOiJIVE1MIFByZWZvcm1hdHRlZCBDaGFyIjsNCglt
YXJnaW46MGluOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNpemU6MTAuMHB0Ow0K
CWZvbnQtZmFtaWx5OiJDb3VyaWVyIE5ldyI7DQoJY29sb3I6YmxhY2s7fQ0Kc3Bhbi5IVE1MUHJl
Zm9ybWF0dGVkQ2hhcg0KCXttc28tc3R5bGUtbmFtZToiSFRNTCBQcmVmb3JtYXR0ZWQgQ2hhciI7
DQoJbXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCW1zby1zdHlsZS1saW5rOiJIVE1MIFByZWZvcm1h
dHRlZCI7DQoJZm9udC1mYW1pbHk6Q29uc29sYXM7DQoJY29sb3I6YmxhY2s7fQ0Kc3Bhbi5FbWFp
bFN0eWxlMTkNCgl7bXNvLXN0eWxlLXR5cGU6cGVyc29uYWwtcmVwbHk7DQoJZm9udC1mYW1pbHk6
IkNhbGlicmkiLCJzYW5zLXNlcmlmIjsNCgljb2xvcjojMUY0OTdEO30NCi5Nc29DaHBEZWZhdWx0
DQoJe21zby1zdHlsZS10eXBlOmV4cG9ydC1vbmx5Ow0KCWZvbnQtc2l6ZToxMC4wcHQ7fQ0KQHBh
Z2UgV29yZFNlY3Rpb24xDQoJe3NpemU6OC41aW4gMTEuMGluOw0KCW1hcmdpbjoxLjBpbiAxLjBp
biAxLjBpbiAxLjBpbjt9DQpkaXYuV29yZFNlY3Rpb24xDQoJe3BhZ2U6V29yZFNlY3Rpb24xO30N
Ci0tPjwvc3R5bGU+PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWRlZmF1bHRzIHY6
ZXh0PSJlZGl0IiBzcGlkbWF4PSIxMDI2IiAvPg0KPC94bWw+PCFbZW5kaWZdLS0+PCEtLVtpZiBn
dGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWxheW91dCB2OmV4dD0iZWRpdCI+DQo8bzppZG1hcCB2
OmV4dD0iZWRpdCIgZGF0YT0iMSIgLz4NCjwvbzpzaGFwZWxheW91dD48L3htbD48IVtlbmRpZl0t
LT48L2hlYWQ+PGJvZHkgYmdjb2xvcj13aGl0ZSBsYW5nPUVOLVVTIGxpbms9Ymx1ZSB2bGluaz1w
dXJwbGU+PGRpdiBjbGFzcz1Xb3JkU2VjdGlvbjE+PHAgY2xhc3M9TXNvTm9ybWFsPjxzcGFuIHN0
eWxlPSdmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7
Y29sb3I6IzFGNDk3RCc+SSBkb27igJl0IHNlZSBhIHByb2JsZW0gd2l0aCB0aGUgwqBJRVRGIHBy
b2Nlc3MuIFdlIHNob3VsZCBob3dldmVyIHVuZGVyc3RhbmQgd2h5IHRoZSBJVFUtVCBwcm9jZXNz
IGZhaWxlZCB0byByZWFjaCBhIGNvbnNlbnN1cyBvciBhcHByb3ZhbC4gwqA8bzpwPjwvbzpwPjwv
c3Bhbj48L3A+PHAgY2xhc3M9TXNvTm9ybWFsPjxzcGFuIHN0eWxlPSdmb250LXNpemU6MTEuMHB0
O2ZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7Y29sb3I6IzFGNDk3RCc+PG86cD4m
bmJzcDs8L286cD48L3NwYW4+PC9wPjxwIGNsYXNzPU1zb05vcm1hbCBzdHlsZT0nbGluZS1oZWln
aHQ6MTQuNHB0O2JhY2tncm91bmQ6d2hpdGUnPjxzcGFuIHN0eWxlPSdmb250LXNpemU6MTEuMHB0
O2ZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7Y29sb3I6IzFGNDk3RCc+RHJhZnQt
YmV0dHMgc3RhdGVzIMKg4oCcPC9zcGFuPjxzcGFuIHN0eWxlPSdmb250LXNpemU6MTAuMHB0O2Zv
bnQtZmFtaWx5OiJDb3VyaWVyIE5ldyI7Y29sb3I6d2luZG93dGV4dCc+QSBudW1iZXIgb2YgZXhw
ZXJ0cyBpbiB0aGUgSUVURiBkbyBub3QgY29uc2lkZXIgdGhhdCB0aGUgZGV2ZWxvcG1lbnQgb3Ig
ZGVwbG95bWVudCBvZiBhIHNlY29uZCBwcm90b2NvbCBzb2x1dGlvbiB3aXRoaW4gdGhlIHNhbWUg
YXJjaGl0ZWN0dXJhbCBwcm9ibGVtIHNwYWNlIGlzIG5lY2Vzc2FyeSBvciBhZHZpc2FibGXigJ0u
wqAgVGhpcyBzdGF0ZW1lbnQgZnJvbSBkcmFmdC1iZXR0cyBpc27igJl0IHdoeSBJVFUtVCBTRyAx
NSBmYWlsZWQgdG8gYXBwcm92ZSBHLjgxMTMuMS7CoCBDb25zZW5zdXMgb3IgYXBwcm92YWwgaW4g
SVRVLVQgaXMgZGVjaWRlZCBvbmx5IGJ5IHNlY3RvciBtZW1iZXJzIGFuZCBtZW1iZXIgc3RhdGVz
LsKgIMKgwqA8bzpwPjwvbzpwPjwvc3Bhbj48L3A+PHAgY2xhc3M9TXNvTm9ybWFsIHN0eWxlPSds
aW5lLWhlaWdodDoxNC40cHQ7YmFja2dyb3VuZDp3aGl0ZSc+PHNwYW4gc3R5bGU9J2ZvbnQtc2l6
ZToxMC4wcHQ7Zm9udC1mYW1pbHk6IkNvdXJpZXIgTmV3Ijtjb2xvcjp3aW5kb3d0ZXh0Jz48bzpw
PiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+PHByZT48c3BhbiBzdHlsZT0nY29sb3I6d2luZG93dGV4
dCc+VGhlIHJlZmVyZW5jZWQgbGlhaXNvbiBpbiBkcmFmdC1iZXR0cyBtZW50aW9ucyDigJxPbmUg
b2YgdGhlIGlzc3VlcyB0aGF0IHByZXZlbnRlZCB0aGUgYXBwcm92YWwgaW4gU0cgMTUgd2FzIHRo
ZSBsYWNrIG9mIGFuIEFDaCBjb2RlIHBvaW50IHRvIHN1cHBvcnQgdGhpcyBSZWNvbW1lbmRhdGlv
bi7igJ0gwqDCoE9uZSBvZiB0aGUgcmVhc29ucz/CoCBJIHJlYWQgdGhhdCB0byBtZWFuIHRoZXJl
IHdlcmUgb3RoZXIgcmVhc29ucyBhcyB3ZWxsLiA8bzpwPjwvbzpwPjwvc3Bhbj48L3ByZT48cHJl
PjxzcGFuIHN0eWxlPSdjb2xvcjp3aW5kb3d0ZXh0Jz48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48
L3ByZT48cCBjbGFzcz1Nc29Ob3JtYWw+PHNwYW4gc3R5bGU9J2ZvbnQtc2l6ZToxMS4wcHQ7Zm9u
dC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjtjb2xvcjojMUY0OTdEJz5JRVRGIGNvdWxk
IGFzayBTRyAxNSwgdmlhIGxpYWlzb24sIMKgZm9yIG1vcmUgaW5mb3JtYXRpb24gYXMgdG8gdGhl
IOKAnG90aGVyIHJlYXNvbnPigJ0gd2h5IHRoZSDCoElUVS1UIHByb2Nlc3MgZmFpbGVkIHRvIGFj
aGlldmUgdG8gYWNoaWV2ZSBhIGNvbnNlbnN1cyBhcm91bmQgRy44MTEzLjEuwqAgwqDCoDxvOnA+
PC9vOnA+PC9zcGFuPjwvcD48cHJlPjxzcGFuIHN0eWxlPSdjb2xvcjp3aW5kb3d0ZXh0Jz48bzpw
PiZuYnNwOzwvbzpwPjwvc3Bhbj48L3ByZT48cHJlPjxzcGFuIHN0eWxlPSdjb2xvcjp3aW5kb3d0
ZXh0Jz5TRyAxNSwgYWRtaXR0aW5nIHRoZXkgZmFpbGVkIGluIHRoZWlyIHByb2Nlc3MgdG8gcmVh
Y2ggYXBwcm92YWwgb24gRy44MTEzLjEsIHN0YXRlcyBpbiB0aGUgcmVmZXJlbmNlZCBsaWFpc29u
IDwvc3Bhbj48c3BhbiBzdHlsZT0nZm9udC1zaXplOjEyLjBwdDtmb250LWZhbWlseToiVGltZXMg
TmV3IFJvbWFuIiwic2VyaWYiO2NvbG9yOndpbmRvd3RleHQnPsKg4oCcPC9zcGFuPjxzcGFuIHN0
eWxlPSdjb2xvcjp3aW5kb3d0ZXh0Jz5VbmZvcnR1bmF0ZWx5IHRoZSBTdHVkeSBHcm91cCBjb3Vs
ZCBub3QgYXBwcm92ZSB0aGlzIFJlY29tbWVuZGF0aW9uIHNvIDwvc3Bhbj48c3BhbiBzdHlsZT0n
Zm9udC1zaXplOjEyLjBwdDtmb250LWZhbWlseToiVGltZXMgTmV3IFJvbWFuIiwic2VyaWYiO2Nv
bG9yOndpbmRvd3RleHQnPml0IHdhcyBmb3J3YXJkZWQgdG8gdGhlIFdUU0EgKDIwLTI5IE5vdmVt
YmVyIDIwMTIpIGZvciBhcHByb3ZhbC7igJ08L3NwYW4+PHNwYW4gc3R5bGU9J2NvbG9yOndpbmRv
d3RleHQnPjxvOnA+PC9vOnA+PC9zcGFuPjwvcHJlPjxwcmU+PHNwYW4gc3R5bGU9J2NvbG9yOndp
bmRvd3RleHQnPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcHJlPjxwcmU+PHNwYW4gc3R5bGU9
J2NvbG9yOndpbmRvd3RleHQnPldUU0EgaXMgZGlmZmVyZW50IGZyb20gU0cgMTUuIMKgSSBkb27i
gJl0IGtub3cgd2hhdCB3aWxsIGhhcHBlbiB0aGVyZSwgYW5kIHdoZXRoZXIgYXBwcm92YWwgd2ls
bCByZXN1bHQuwqAgQXMgb2Ygbm93LCBjb25zZW5zdXMvYXBwcm92YWwgd2FzIG5vdCBhY2hpZXZl
ZCB3aXRoaW4gdGhlIElUVS1UIHByb2Nlc3MuIDxvOnA+PC9vOnA+PC9zcGFuPjwvcHJlPjxwcmU+
PHNwYW4gc3R5bGU9J2NvbG9yOndpbmRvd3RleHQnPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwv
cHJlPjxwcmU+PHNwYW4gc3R5bGU9J2NvbG9yOndpbmRvd3RleHQnPk15IHZpZXcgaXMgSUVURiBz
aG91bGQgd2FpdCBhdCBsZWFzdCB1bnRpbCB0aGVyZSBpcyBhbiBhcHByb3ZlZCBSZWNvbW1lbmRh
dGlvbi7CoCA8bzpwPjwvbzpwPjwvc3Bhbj48L3ByZT48cCBjbGFzcz1Nc29Ob3JtYWwgc3R5bGU9
J2xpbmUtaGVpZ2h0OjE0LjRwdDtiYWNrZ3JvdW5kOndoaXRlJz48c3BhbiBzdHlsZT0nZm9udC1z
aXplOjEwLjBwdDtmb250LWZhbWlseToiQ291cmllciBOZXciO2NvbG9yOndpbmRvd3RleHQnPjxv
OnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD48cCBjbGFzcz1Nc29Ob3JtYWw+PHNwYW4gc3R5bGU9
J2ZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjtjb2xv
cjojMUY0OTdEJz5Ub20gV2Fsc2g8bzpwPjwvbzpwPjwvc3Bhbj48L3A+PHAgY2xhc3M9TXNvTm9y
bWFsIHN0eWxlPSdsaW5lLWhlaWdodDoxNC40cHQ7YmFja2dyb3VuZDp3aGl0ZSc+PHNwYW4gc3R5
bGU9J2ZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6IkNvdXJpZXIgTmV3Ijtjb2xvcjp3aW5k
b3d0ZXh0Jz48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+PC9kaXY+PC9ib2R5PjwvaHRtbD4=

--_000_A4C6A166C36F5F40A5767E6F66358FC0BB89D828EEEMBX01WFjnprn_--

From denghui02@gmail.com  Wed Mar 21 18:49:54 2012
Return-Path: <denghui02@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 359B821E8015; Wed, 21 Mar 2012 18:49:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.37
X-Spam-Level: 
X-Spam-Status: No, score=-103.37 tagged_above=-999 required=5 tests=[AWL=0.228, 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 LeuIIPQTwqCg; Wed, 21 Mar 2012 18:49:53 -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 6ACBC21E800C; Wed, 21 Mar 2012 18:49:53 -0700 (PDT)
Received: by yenm5 with SMTP id m5so1618625yen.31 for <multiple recipients>; Wed, 21 Mar 2012 18:49:53 -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=j5dWFsWs95m5VbEDQPgAQLeC7hO7tS6sD+ItVuJ8w8c=; b=pTRphpzZk8lS55R1Ur6dn+CQKFpClkKzYKAx3NZA1n+q9iaErblLsfpVTAu5+G8U77 fE7Lq7kPs+EnwbXwcD1Pfi/e8C3smgepYuUbzhRD1r9Z5/hcxMuRvWCX4+iWGtVdV9vm x2i2DP3yTIKU5CHeG59QmiScDeKnUz2WXJb90ITlXHRdGXK+tmctg3EdSMblzj+y/trn j9G+YnXVYyVwECvJStHcrRyF7ecnoLZMyDw2uK74OvHzCwS9RZCGpR76+LFUuDJ5EDYy rAeabZPuoy63lVEM7/fFmLzYR3VdPnSPLQsE+FUS+T+XrvQEQZqBC0SXRSh7Zepeebqx IZUg==
MIME-Version: 1.0
Received: by 10.101.128.14 with SMTP id f14mr1886430ann.21.1332380992977; Wed, 21 Mar 2012 18:49:52 -0700 (PDT)
Received: by 10.147.112.1 with HTTP; Wed, 21 Mar 2012 18:49:52 -0700 (PDT)
Date: Thu, 22 Mar 2012 09:49:52 +0800
Message-ID: <CANF0JMCw1DZCc1dHoEYidYrKA19skLXYZz69iHyWNuG=NQWjtg@mail.gmail.com>
Subject: OMA IETF MIF API Workshop
From: Hui Deng <denghui02@gmail.com>
To: MIF Mailing List <mif@ietf.org>, IETF Discussion <ietf@ietf.org>, Internet Area <int-area@ietf.org>
Content-Type: multipart/alternative; boundary=001636c597a3cabbcb04bbcb1f26
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Mar 2012 01:49:54 -0000

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

OMA IETF MIF API Workshop

Time: Tuesday: 18:10-20:00
Location: TBD

1) Program
1.1) OMA OpenCMAPI activity (Thierry)
1.2) IETF MIF API Design (Ted Lemon)
1.3) IETF API related work (TBD)
1.4) OMA API Program (OMA Member)
1.5) Vendor's today implementation (Maybe)
1.6) Next step between IETF and OMA (Thierry and Hui)

2) Purpose
2.1) From IETF, this workshop would help to explain the API related topic,
and clarify what is recommended and not recommended to do and standardized,
if possible, either publish a information document or adding word into the
current MIF api draft about how to use those MIF API for Internet developer=
.
and some current practices information how today smart terminal is doing.

2.2) From OMA perspective, to socialize OMA=92s published specifications an=
d
current ongoing standards activities in the area of APIs. To make sure that
the standards landscape for APIs is coordinated and harmonized. To solicit
feedback about OMA=92s specification for Authorization4APIs, which is built
on IETF OAuth as well as OpenCMAPI.

3) Outcomes:
3.1) Future work about how to use those MIF API in an IETF information
 document or inside current MIF API documentfor Internet developers.

3.2) Outcomes OMA: Improved understanding of each others=92 activities,
 and a coordinated approach going forward

3.3) Better mutual understanding of the work of both organizations,
 and how to cooperate in the future.

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

OMA IETF MIF API Workshop<br>=A0<br>Time: Tuesday: 18:10-20:00<br>Location:=
 TBD <br>=A0<br>1) Program<br>1.1) OMA OpenCMAPI activity (Thierry) <br>1.2=
) IETF MIF API Design (Ted Lemon)<br>1.3) IETF API related work (TBD) <br>1=
.4) OMA API Program (OMA Member) <br>
1.5) Vendor&#39;s today implementation (Maybe)<br>1.6) Next step between IE=
TF and OMA (Thierry and Hui)<br>=A0<br>2) Purpose<br>2.1) From IETF, this w=
orkshop would help to explain the API related topic,<br>and clarify what is=
 recommended and not recommended to do and standardized, <br>
if possible, either publish a information document or adding word into the =
<br>current MIF api draft about how to use those MIF API for Internet devel=
oper.<br>and some current practices information how today smart terminal is=
 doing. <br>
=A0<br>2.2) From OMA perspective, to socialize OMA=92s published specificat=
ions and <br>current ongoing standards activities in the area of APIs. To m=
ake sure that <br>the standards landscape for APIs is coordinated and harmo=
nized. To solicit <br>
feedback about OMA=92s specification for Authorization4APIs, which is built=
 <br>on IETF OAuth as well as OpenCMAPI.<br>=A0<br>3) Outcomes:<br>3.1) Fut=
ure work about how to use those MIF API in an IETF information <br>=A0docum=
ent or inside current MIF API documentfor Internet developers.<br>
<br>3.2) Outcomes OMA: Improved understanding of each others=92 activities,=
<br>=A0and a coordinated approach going forward<br><br>3.3) Better mutual u=
nderstanding of the work of both organizations, <br>=A0and how to cooperate=
 in the future.

--001636c597a3cabbcb04bbcb1f26--

From brian.e.carpenter@gmail.com  Wed Mar 21 20:49: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 43ED721E80EB for <ietf@ietfa.amsl.com>; Wed, 21 Mar 2012 20:49:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.498
X-Spam-Level: 
X-Spam-Status: No, score=-103.498 tagged_above=-999 required=5 tests=[AWL=0.101, 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 5XwAYHchlki5 for <ietf@ietfa.amsl.com>; Wed, 21 Mar 2012 20:49:46 -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 87B1721E804B for <ietf@ietf.org>; Wed, 21 Mar 2012 20:49:46 -0700 (PDT)
Received: by eaaq11 with SMTP id q11so522894eaa.31 for <ietf@ietf.org>; Wed, 21 Mar 2012 20:49:45 -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=yGHStWiAjwpcF5OPueodOncPNwleSITTeo6CAH3dHcY=; b=UdnUlcmDIA760vxPKRALgOTRVQ+2rdbJWO9u30bwvYoiIGWWw6VW40c5/Y+lQUfu5d Iffsk1X//zJlmGKfz9YwQzBy8qUHvmDXrNkLVvckcdSzr4IKllrv1b8SNfrmO/JGOroh PCZ1iPiQskUFeNH6AEcNIM26NoPjkRVD3s/cN+1P4aG0xai7TMaX+RSpwU5Oer+ngU9i KsLv5TbFo0fVaGsKuZT01lWAWsV1JXBoLMwlgQLCWRbyIQGcJpE2JQ4SkOS6NM4zBxF/ ofdl9agI8rZQXxjE+X5UFN1LmIADRv8MFCqGcppBNFloua5cSCtTxmPwssepT6e/TQUm HS8A==
Received: by 10.14.186.12 with SMTP id v12mr869574eem.31.1332388185724; Wed, 21 Mar 2012 20:49:45 -0700 (PDT)
Received: from [10.1.1.4] ([121.98.251.219]) by mx.google.com with ESMTPS id d54sm12575129eei.9.2012.03.21.20.49.42 (version=SSLv3 cipher=OTHER); Wed, 21 Mar 2012 20:49:44 -0700 (PDT)
Message-ID: <4F6AA14E.4040204@gmail.com>
Date: Thu, 22 Mar 2012 16:49:34 +1300
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@cisco.com>
Subject: Re: IPv6 Zone Identifiers Considered Hateful
References: <82A794CE-B328-475F-9300-1B6BE628F7E3@sabahattin-gucukoglu.com> <C1BCE1FC-B35C-4D11-B6E7-AA8A6264A289@cisco.com> <4F6A4D68.10905@gmail.com> <CA9F71F7-350D-4265-B469-0CA150D39FCE@cisco.com>
In-Reply-To: <CA9F71F7-350D-4265-B469-0CA150D39FCE@cisco.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Mar 2012 03:49:47 -0000

Fred,

On 2012-03-22 13:29, Fred Baker wrote:
> On Mar 21, 2012, at 10:51 PM, Brian E Carpenter wrote:
>> In other words if the IETF doesn't define the zone index, every
>> implementor will have to do so anyway. Also, read the last clause
>> carefully: it says the stack MUST allow OPTIONAL use of the zone
>> index internally.
> 
> Implementors generally *do* have some internal form of a zone index, and it doesn't look at all like what the RFC describes. It is a machine address or a lookup index of some kind for a table that is associated with an interface. Sometimes, part of it is a card identifier.

Yes, someone recently cited fe-0/0/1 as a real-world example of an
interface identifier (in practice equivalent to a zone identifier)
RFC 4007 says nothing about the syntax of the identifier. Clearly
the mapping to a 32 bit integer is a local matter in the node; look
at RFC 4007 and the socket API together.

>>> From MIF's perspective, if the same prefix is placed on multiple interfaces, 
>> The prefix fe80::/10 is automatically on every interface. That's the
>> only case where I'm certain we need a zone index in practice, but the
>> definition isn't limited to that case.
> 
> The use of something to get me to the interface table in question isn't what I am questioning. It's the use of that particular something...

IMHO it is very limited, mainly for diagnostic use. We need to get
it right but it has no mainstream value that I can see.

    Brian

From nurit.sprecher@nsn.com  Thu Mar 22 03:52:15 2012
Return-Path: <nurit.sprecher@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 9FC2B21F869A for <ietf@ietfa.amsl.com>; Thu, 22 Mar 2012 03:52:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.493
X-Spam-Level: 
X-Spam-Status: No, score=-6.493 tagged_above=-999 required=5 tests=[AWL=0.105,  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 bwgAHum0JOJa for <ietf@ietfa.amsl.com>; Thu, 22 Mar 2012 03:52:09 -0700 (PDT)
Received: from demumfd001.nsn-inter.net (demumfd001.nsn-inter.net [93.183.12.32]) by ietfa.amsl.com (Postfix) with ESMTP id 6187A21F868A for <ietf@ietf.org>; Thu, 22 Mar 2012 03:52:08 -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 q2MAq4ah013761 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 22 Mar 2012 11:52:04 +0100
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 q2MAq4SG029866; Thu, 22 Mar 2012 11:52:04 +0100
Received: from DEMUEXC013.nsn-intra.net ([10.150.128.24]) by demuexc023.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 22 Mar 2012 11:51:57 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----_=_NextPart_001_01CD0819.CCB6A7A8"
Subject: RE: Last Call: <draft-ietf-mpls-tp-oam-analysis-08.txt> (An Overviewof the OAM Tool Set for MPLS based Transport Networks) toInformational RFC
Date: Thu, 22 Mar 2012 11:51:54 +0100
Message-ID: <E4873516F3FC7547BCFE792C7D94039C0179AE70@DEMUEXC013.nsn-intra.net>
In-Reply-To: <4F6A5ADB.2090002@gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Last Call: <draft-ietf-mpls-tp-oam-analysis-08.txt> (An Overviewof the OAM Tool Set for MPLS based Transport Networks) toInformational RFC
Thread-Index: Ac0HtNfKAyIL5jroRyKuN6xWHpPmlQAYWYxw
References: <20120309205157.8304.55419.idtracker@ietfa.amsl.com> <4F6A5ADB.2090002@gmail.com>
From: "Sprecher, Nurit (NSN - IL/Hod HaSharon)" <nurit.sprecher@nsn.com>
To: <huubatwork@gmail.com>, <ietf@ietf.org>
X-OriginalArrivalTime: 22 Mar 2012 10:51:57.0120 (UTC) FILETIME=[CD101400:01CD0819]
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: 20495
X-purgate-ID: 151667::1332413524-00003570-2F2B5019/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: Thu, 22 Mar 2012 10:52:15 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CD0819.CCB6A7A8
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_002_01CD0819.CCB6A7A8"


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

Huub hi,

Thanks for your comments to IESG...

We can easily remove your name from the acknowledgement section. We put
you there upon your request!=20

I am sorry that I am going to share on the list a private mail from you
to me but I can see no other choice with the mail you have just sent to
the list.=20

As you recall you were an editor of the draft and on June 2010 (when the
document was already an IETF document for a while), you have asked to
remove your name from the list of editors. See=20
http://www.ietf.org/mail-archive/web/mpls-tp/current/msg04118.html. the
main reason was as you said:=20

"It was my intention to be editor as an IETF member, however there are
people that interpret my name/role differently. They see it as being
editor as an ITU-T member and recently even as being editor as an ITU-T
Q10 rapporteur.".

In a private mail you sent me later (attached) you proposed to include
you in the acknowledgement section:

" Yes, remove my name as editor. As Adrian suggested, you could mention
me in the acknowledgements section."

It is a pity that you did not inform us that you changed your mind since
then, but it can easily be fixed!

Best regards,

Nurit

=20

=20

=20

-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
ext Huub van Helvoort
Sent: Thursday, March 22, 2012 12:49 AM
To: ietf@ietf.org
Subject: Re: Last Call: <draft-ietf-mpls-tp-oam-analysis-08.txt> (An
Overviewof the OAM Tool Set for MPLS based Transport Networks)
toInformational RFC

=20

IESG,

=20

I do *NOT* support this draft unless the following changes are made:

=20

The first paragraph of section 8 Acknowledgements has to be removed:

It is an attempt to capture history, but lacks accuracy.

Removal does not impact the technical information in the draft;

the tools have evolved significantly from the strawman tools proposed

in Stockholm; some members of the MEAD team (I am one of them) do not

consider that an agreement on this proposal was reached.

=20

I also request the removal of my name from this acknowledgements section

since I do not support this tool set, neither as an individual nor as

ITU-T Q10 rapporteur. The latter is implied by mentioning my name in

the same sentence as a WG chair and ADs.

=20

Regards, Huub.

=20

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

> The IESG has received a request from the Multiprotocol Label Switching
WG

> (mpls) to consider the following document:

> - 'An Overview of the OAM Tool Set for MPLS based Transport Networks'

>    <draft-ietf-mpls-tp-oam-analysis-08.txt>  as an Informational RFC

>=20

> The IESG plans to make a decision in the next few weeks, and solicits

> final comments on this action. Please send substantive comments to the

> ietf@ietf.org <mailto:ietf@ietf.org>  mailing lists by 2012-03-23.
Exceptionally, comments may be

> sent to iesg@ietf.org <mailto:iesg@ietf.org>  instead. In either case,
please retain the

> beginning of the Subject line to allow automated sorting.

>=20

> Abstract

>=20

>     This document provides an overview of the OAM toolset for MPLS
based

>     Transport Networks.  The toolset consists of a comprehensive set
of

>     fault management and performance monitoring capabilities
(operating

>     in the data-plane) which are appropriate for transport networks as

>     required in RFC 5860 and support the network and services at

>     different nested levels.  This overview includes a brief recap of

>     MPLS-TP OAM requirements and functions, and of generic mechanisms

>     created in the MPLS data plane to allow the OAM packets run
in-band

>     and share their fate with data packets.  The protocol definitions
for

>     each of the MPLS-TP OAM tools are defined in separate documents
(RFCs

>     or Working Group drafts) which are referenced by this document.

>=20

>=20

> The file can be obtained via

> http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-oam-analysis/
<http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-oam-analysis/>=20

>=20

> IESG discussion can be tracked via

>=20
http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-oam-analysis/ballot/
<http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-oam-analysis/ballot/
>=20

>=20

>=20

> No IPR declarations have been submitted directly on this I-D.

> _______________________________________________

> IETF-Announce mailing list

> IETF-Announce@ietf.org <mailto:IETF-Announce@ietf.org>=20

> https://www.ietf.org/mailman/listinfo/ietf-announce
<https://www.ietf.org/mailman/listinfo/ietf-announce>=20


------_=_NextPart_002_01CD0819.CCB6A7A8
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:Consolas;
	panose-1:2 11 6 9 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;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
.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=3DMsoPlainText>Huub =
hi,<o:p></o:p></p><p class=3DMsoPlainText>Thanks for your comments to =
IESG...<o:p></o:p></p><p class=3DMsoPlainText>We can easily remove your =
name from the acknowledgement section. We put you there upon your =
request! <o:p></o:p></p><p class=3DMsoPlainText>I am sorry that I am =
going to share on the list a private mail from you to me but I can see =
no other choice with the mail you have just sent to the list. =
<o:p></o:p></p><p class=3DMsoPlainText>As you recall you were an editor =
of the draft and on June 2010 (when the document was already an IETF =
document for a while), you have asked to remove your name from the list =
of editors. See <a =
href=3D"http://www.ietf.org/mail-archive/web/mpls-tp/current/msg04118.htm=
l">http://www.ietf.org/mail-archive/web/mpls-tp/current/msg04118.html</a>=
. the main reason was as you said: <o:p></o:p></p><p =
class=3DMsoPlainText style=3D'margin-left:.5in'>&quot;It was my =
intention to be editor as an IETF member, however there are people that =
interpret my name/role differently. They see it as being editor as an =
ITU-T member and recently even as being editor as an ITU-T Q10 =
rapporteur.&quot;.<o:p></o:p></p><p class=3DMsoPlainText>In a private =
mail you sent me later (attached) you proposed to include you in the =
acknowledgement section:<o:p></o:p></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in'>&quot; Yes, remove my name as editor. As =
Adrian suggested, <span =
style=3D'background:yellow;mso-highlight:yellow'>you could mention me in =
the acknowledgements section</span>.&quot;<o:p></o:p></p><p =
class=3DMsoPlainText>It is a pity that you did not inform us that you =
changed your mind since then, but it can easily be =
fixed!<o:p></o:p></p><p class=3DMsoPlainText>Best =
regards,<o:p></o:p></p><p class=3DMsoPlainText>Nurit<o:p></o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>-----Original Message-----<br>From: =
ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of ext =
Huub van Helvoort<br>Sent: Thursday, March 22, 2012 12:49 AM<br>To: =
ietf@ietf.org<br>Subject: Re: Last Call: =
&lt;draft-ietf-mpls-tp-oam-analysis-08.txt&gt; (An Overviewof the OAM =
Tool Set for MPLS based Transport Networks) toInformational =
RFC<o:p></o:p></p><p class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>IESG,<o:p></o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p class=3DMsoPlainText>I do =
*NOT* support this draft unless the following changes are =
made:<o:p></o:p></p><p class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>The first paragraph of section 8 Acknowledgements =
has to be removed:<o:p></o:p></p><p class=3DMsoPlainText>It is an =
attempt to capture history, but lacks accuracy.<o:p></o:p></p><p =
class=3DMsoPlainText>Removal does not impact the technical information =
in the draft;<o:p></o:p></p><p class=3DMsoPlainText>the tools have =
evolved significantly from the strawman tools proposed<o:p></o:p></p><p =
class=3DMsoPlainText>in Stockholm; some members of the MEAD team (I am =
one of them) do not<o:p></o:p></p><p class=3DMsoPlainText>consider that =
an agreement on this proposal was reached.<o:p></o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p class=3DMsoPlainText>I also =
request the removal of my name from this acknowledgements =
section<o:p></o:p></p><p class=3DMsoPlainText>since I do not support =
this tool set, neither as an individual nor as<o:p></o:p></p><p =
class=3DMsoPlainText>ITU-T Q10 rapporteur. The latter is implied by =
mentioning my name in<o:p></o:p></p><p class=3DMsoPlainText>the same =
sentence as a WG chair and ADs.<o:p></o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>Regards, Huub.<o:p></o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<o:p></o:p></=
p><p class=3DMsoPlainText>&gt; The IESG has received a request from the =
Multiprotocol Label Switching WG<o:p></o:p></p><p =
class=3DMsoPlainText>&gt; (mpls) to consider the following =
document:<o:p></o:p></p><p class=3DMsoPlainText>&gt; - 'An Overview of =
the OAM Tool Set for MPLS based Transport Networks'<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&nbsp;&nbsp;&nbsp; =
&lt;draft-ietf-mpls-tp-oam-analysis-08.txt&gt;&nbsp; as an Informational =
RFC<o:p></o:p></p><p class=3DMsoPlainText>&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt; The IESG plans to make a decision in the next =
few weeks, and solicits<o:p></o:p></p><p class=3DMsoPlainText>&gt; final =
comments on this action. Please send substantive comments to =
the<o:p></o:p></p><p class=3DMsoPlainText>&gt; <a =
href=3D"mailto:ietf@ietf.org"><span =
style=3D'color:windowtext;text-decoration:none'>ietf@ietf.org</span></a> =
mailing lists by 2012-03-23. Exceptionally, comments may =
be<o:p></o:p></p><p class=3DMsoPlainText>&gt; sent to <a =
href=3D"mailto:iesg@ietf.org"><span =
style=3D'color:windowtext;text-decoration:none'>iesg@ietf.org</span></a> =
instead. In either case, please retain the<o:p></o:p></p><p =
class=3DMsoPlainText>&gt; beginning of the Subject line to allow =
automated sorting.<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt; Abstract<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&nbsp;&nbsp;&nbsp;&nbsp; This document provides =
an overview of the OAM toolset for MPLS based<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&nbsp;&nbsp;&nbsp;&nbsp; Transport =
Networks.&nbsp; The toolset consists of a comprehensive set =
of<o:p></o:p></p><p class=3DMsoPlainText>&gt;&nbsp;&nbsp;&nbsp;&nbsp; =
fault management and performance monitoring capabilities =
(operating<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&nbsp;&nbsp;&nbsp;&nbsp; in the data-plane) =
which are appropriate for transport networks as<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&nbsp;&nbsp;&nbsp;&nbsp; required in RFC 5860 =
and support the network and services at<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&nbsp;&nbsp;&nbsp;&nbsp; different nested =
levels.&nbsp; This overview includes a brief recap of<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&nbsp;&nbsp;&nbsp;&nbsp; MPLS-TP OAM =
requirements and functions, and of generic mechanisms<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&nbsp;&nbsp;&nbsp;&nbsp; created in the MPLS =
data plane to allow the OAM packets run in-band<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&nbsp;&nbsp;&nbsp;&nbsp; and share their fate =
with data packets.&nbsp; The protocol definitions for<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&nbsp;&nbsp;&nbsp;&nbsp; each of the MPLS-TP =
OAM tools are defined in separate documents (RFCs<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&nbsp;&nbsp;&nbsp;&nbsp; or Working Group =
drafts) which are referenced by this document.<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt; The file can be obtained via<o:p></o:p></p><p =
class=3DMsoPlainText>&gt; <a =
href=3D"http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-oam-analysis/"=
><span =
style=3D'color:windowtext;text-decoration:none'>http://datatracker.ietf.o=
rg/doc/draft-ietf-mpls-tp-oam-analysis/</span></a><o:p></o:p></p><p =
class=3DMsoPlainText>&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt; IESG discussion can be tracked =
via<o:p></o:p></p><p class=3DMsoPlainText>&gt; <a =
href=3D"http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-oam-analysis/b=
allot/"><span =
style=3D'color:windowtext;text-decoration:none'>http://datatracker.ietf.o=
rg/doc/draft-ietf-mpls-tp-oam-analysis/ballot/</span></a><o:p></o:p></p><=
p class=3DMsoPlainText>&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt; No IPR declarations have been submitted =
directly on this I-D.<o:p></o:p></p><p class=3DMsoPlainText>&gt; =
_______________________________________________<o:p></o:p></p><p =
class=3DMsoPlainText>&gt; IETF-Announce mailing list<o:p></o:p></p><p =
class=3DMsoPlainText>&gt; <a =
href=3D"mailto:IETF-Announce@ietf.org"><span =
style=3D'color:windowtext;text-decoration:none'>IETF-Announce@ietf.org</s=
pan></a><o:p></o:p></p><p class=3DMsoPlainText>&gt; <a =
href=3D"https://www.ietf.org/mailman/listinfo/ietf-announce"><span =
style=3D'color:windowtext;text-decoration:none'>https://www.ietf.org/mail=
man/listinfo/ietf-announce</span></a><o:p></o:p></p></div></body></html>
------_=_NextPart_002_01CD0819.CCB6A7A8--

------_=_NextPart_001_01CD0819.CCB6A7A8
Content-Type: message/rfc822
Content-Transfer-Encoding: 7bit

X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: from demuexc025.nsn-intra.net ([10.159.32.12]) by DEMUEXC014.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.4675); Mon, 21 Jun 2010 10:38:28 +0200
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_003_01CB111D.1EE15A00"
Disposition-Notification-To: "Huub van Helvoort" <hhelvoort@chello.nl>
Received: from demuprx016.emea.nsn-intra.net ([10.150.129.55]) by demuexc025.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.4675); Mon, 21 Jun 2010 10:38:27 +0200
Received: from demumfd001.nsn-inter.net (DEMUMFD001 [93.183.12.32]) by demuprx016.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id o5L8cRlL022761 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <nurit.sprecher@nsn.com>; Mon, 21 Jun 2010 10:38:27 +0200
Received: from fep15.mx.upcmail.net (fep15.mx.upcmail.net [62.179.121.35]) by demumfd001.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id o5L8cRg7021256 for <nurit.sprecher@nsn.com>; Mon, 21 Jun 2010 10:38:27 +0200
Received: from edge03.upcmail.net ([192.168.13.238])          by viefep15-int.chello.at          (InterMail vM.8.01.02.02 201-2260-120-106-20100312) with ESMTP          id <20100621083827.FKDH21071.viefep15-int.chello.at@edge03.upcmail.net>          for <nurit.sprecher@nsn.com>; Mon, 21 Jun 2010 10:38:27 +0200
Received: from McAsterix.local ([77.250.51.60]) by edge03.upcmail.net with edge id YYeR1e0461Hw6VZ03YeSMg; Mon, 21 Jun 2010 10:38:26 +0200
Content-class: urn:content-classes:message
Subject: Re: MPLS-T OAM Analysis
Date: Mon, 21 Jun 2010 09:38:25 +0100
Message-ID: <4C1F2501.6040803@chello.nl>
In-Reply-To: <077E41CFFD002C4CAB7DFA4386A5326402425E5B@DEMUEXC014.nsn-intra.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: MPLS-T OAM Analysis
Thread-Index: AcsRHR9V9pajLQqGT72R4yUx7m9hPw==
References: <077E41CFFD002C4CAB7DFA4386A5326402425E5B@DEMUEXC014.nsn-intra.net>
From: "ext Huub van Helvoort" <hhelvoort@chello.nl>
To: "Sprecher, Nurit (NSN - IL/Hod HaSharon)" <nurit.sprecher@nsn.com>
Reply-To: <hhelvoort@chello.nl>

This is a multi-part message in MIME format.

------_=_NextPart_003_01CB111D.1EE15A00
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hello Nurit,

You wrote:

> We plan shortly to submit a new revision of
> draft-ietf-mpls-tp-oam-analysis.

Because I am not aware of this submission I assume
I am already not part of the "we" anymore.

> Can you please confirm to me whether you wish to have your
 > name removed from the document.

Yes, remove my name as editor.
As Adrian suggested, you could mention me in the
acknowledgements section.

Regards, Huub.

--=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=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Always remember that you are unique...just like everyone else...

------_=_NextPart_003_01CB111D.1EE15A00
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7654.12">
<TITLE>Re: MPLS-T OAM Analysis</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->

<P><FONT SIZE=3D2>Hello Nurit,<BR>
<BR>
You wrote:<BR>
<BR>
&gt; We plan shortly to submit a new revision of<BR>
&gt; draft-ietf-mpls-tp-oam-analysis.<BR>
<BR>
Because I am not aware of this submission I assume<BR>
I am already not part of the &quot;we&quot; anymore.<BR>
<BR>
&gt; Can you please confirm to me whether you wish to have your<BR>
&nbsp;&gt; name removed from the document.<BR>
<BR>
Yes, remove my name as editor.<BR>
As Adrian suggested, you could mention me in the<BR>
acknowledgements section.<BR>
<BR>
Regards, Huub.<BR>
<BR>
--<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=3D=3D=3D=3D=3D=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>
Always remember that you are unique...just like everyone else...<BR>
</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_003_01CB111D.1EE15A00--

------_=_NextPart_001_01CD0819.CCB6A7A8--

From fanf2@hermes.cam.ac.uk  Thu Mar 22 04:50:58 2012
Return-Path: <fanf2@hermes.cam.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C606F21F86A3 for <ietf@ietfa.amsl.com>; Thu, 22 Mar 2012 04:50:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.475
X-Spam-Level: 
X-Spam-Status: No, score=-6.475 tagged_above=-999 required=5 tests=[AWL=0.124,  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 m6RPjGclAykG for <ietf@ietfa.amsl.com>; Thu, 22 Mar 2012 04:50:57 -0700 (PDT)
Received: from ppsw-51.csi.cam.ac.uk (ppsw-51.csi.cam.ac.uk [131.111.8.151]) by ietfa.amsl.com (Postfix) with ESMTP id 9706721F86AB for <ietf@ietf.org>; Thu, 22 Mar 2012 04:50:57 -0700 (PDT)
X-Cam-AntiVirus: no malware found
X-Cam-SpamDetails: not scanned
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
Received: from hermes-2.csi.cam.ac.uk ([131.111.8.54]:36792) by ppsw-51.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.158]:25) with esmtpa (EXTERNAL:fanf2) id 1SAgXU-00042h-YB (Exim 4.72) (return-path <fanf2@hermes.cam.ac.uk>); Thu, 22 Mar 2012 11:50:44 +0000
Received: from fanf2 (helo=localhost) by hermes-2.csi.cam.ac.uk (hermes.cam.ac.uk) with local-esmtp id 1SAgXU-0006a2-I7 (Exim 4.67) (return-path <fanf2@hermes.cam.ac.uk>); Thu, 22 Mar 2012 11:50:44 +0000
Date: Thu, 22 Mar 2012 11:50:44 +0000
From: Tony Finch <dot@dotat.at>
X-X-Sender: fanf2@hermes-2.csi.cam.ac.uk
To: Craig Finseth <snark17@gmail.com>
Subject: Re: IPv6 Zone Identifiers Considered Hateful
In-Reply-To: <CAGHVWBh=vKnc343ux6YFRkL=G+rH8Up2fGKDNiDSPbxMwyQvtA@mail.gmail.com>
Message-ID: <alpine.LSU.2.00.1203221150100.24583@hermes-2.csi.cam.ac.uk>
References: <82A794CE-B328-475F-9300-1B6BE628F7E3@sabahattin-gucukoglu.com> <CD5674C3CD99574EBA7432465FC13C1B22726A0994@DC-US1MBEX4.global.avaya.com> <CAGHVWBgnF49UYSaL3awXf4Y+wxvmUTFi9xYRVCZ8WL1nFZp1Aw@mail.gmail.com> <CD5674C3CD99574EBA7432465FC13C1B22726A0996@DC-US1MBEX4.global.avaya.com> <CAGHVWBh=vKnc343ux6YFRkL=G+rH8Up2fGKDNiDSPbxMwyQvtA@mail.gmail.com>
User-Agent: Alpine 2.00 (LSU 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: Tony Finch <fanf2@hermes.cam.ac.uk>
Cc: Sabahattin Gucukoglu <mail-dated-1334746550.15c4ac@sabahattin-gucukoglu.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Mar 2012 11:50:59 -0000

Craig Finseth <snark17@gmail.com> wrote:
>
> Well, it's globally unique to a host, not to an interface: the host
> (in general) uses the same link-local address on all interfaces.
> Thus, you can't tell from the address which interface it refers to.

That kind of setup is pretty rare these days AFAIK.

Tony.
-- 
f.anthony.n.finch  <dot@dotat.at>  http://dotat.at/
Rockall: South or southeast 5 to 7, decreasing 4 at times. Rough or very
rough. Fair. Moderate or good.

From RCosta@ptinovacao.pt  Thu Mar 22 07:42:39 2012
Return-Path: <RCosta@ptinovacao.pt>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 36DF621F8630 for <ietf@ietfa.amsl.com>; Thu, 22 Mar 2012 07:42:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.336
X-Spam-Level: 
X-Spam-Status: No, score=-2.336 tagged_above=-999 required=5 tests=[AWL=0.263,  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 HTgI8gzSHGpm for <ietf@ietfa.amsl.com>; Thu, 22 Mar 2012 07:42:38 -0700 (PDT)
Received: from owa.ptinovacao.pt (mail6.ptinovacao.pt [194.65.138.99]) by ietfa.amsl.com (Postfix) with ESMTP id 5CDE121F8647 for <ietf@ietf.org>; Thu, 22 Mar 2012 07:42:37 -0700 (PDT)
Received: from INOAVREX11.ptin.corpPT.com ([10.112.15.122]) by inoavrcas01.ptin.corpPT.com ([10.112.15.99]) with mapi; Thu, 22 Mar 2012 14:42:35 +0000
From: Rui Costa <RCosta@ptinovacao.pt>
To: "ietf@ietf.org" <ietf@ietf.org>
Date: Thu, 22 Mar 2012 14:42:34 +0000
Subject: FW: Last Call:<draft-betts-itu-oam-ach-code-point-03.txt>(Allocationof	an	Associated Channel Code Point for Use byITU-T Ethernetbased OAM) to	Informational	RFC
Thread-Topic: Last Call:<draft-betts-itu-oam-ach-code-point-03.txt>(Allocationof	an	Associated Channel Code Point for Use byITU-T Ethernetbased OAM) to	Informational	RFC
Thread-Index: Ac0HdLufGyIpL3HPTom7mYWDtDPeQAABo+vg
Message-ID: <52981DB05D3C5247A12D0AEE309F3CC202444240C161@INOAVREX11.ptin.corpPT.com>
Accept-Language: pt-PT
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: pt-PT
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: Thu, 22 Mar 2012 14:42:39 -0000

SSBmYWlsIHRvIHVuZGVyc3RhbmQgdGhlIGlzc3VlIHVuZGVyIGRpc2N1c3Npb24uCQ0KDQpDYW4n
dCBpbWFnaW5lIElFRUUgZGVueWluZyB0byBncmFudCBFdGhlcnR5cGUgMHg4NkRELiBJZiwgaG93
ZXZlciwgZnJvbSBhYnN1cmQgdGhhdCBoYWQgaGFwcGVuZWQsIHdvdWxkIHRoZSB3b3JsZCBzdG9w
IG9yIHdvdWxkIHdlIHRha2UgdGhlIHNhbWUgaW5mb3JtYXRpb24gZnJvbSB0aGUgSVAgaGVhZGVy
IHZlcnNpb24gZmllbGQ/CQ0KDQpSZWdhcmRzLAkNClJ1aQkNCg0KDQotLS0tLU9yaWdpbmFsIE1l
c3NhZ2UtLS0tLQ0KRnJvbTogaWV0Zi1ib3VuY2VzQGlldGYub3JnIFttYWlsdG86aWV0Zi1ib3Vu
Y2VzQGlldGYub3JnXSBPbiBCZWhhbGYgT2YgQWxpYSBBdGxhcw0KU2VudDogcXVhcnRhLWZlaXJh
LCAyMSBkZSBNYXLDp28gZGUgMjAxMiAxNTozMA0KVG86IEQnQWxlc3NhbmRybyBBbGVzc2FuZHJv
IEdlcmFyZG8NCkNjOiBpZXRmQGlldGYub3JnDQpTdWJqZWN0OiBSZTog15TXoNeT15XXnzogUkU6
IExhc3QgQ2FsbDo8ZHJhZnQtYmV0dHMtaXR1LW9hbS1hY2gtY29kZS1wb2ludC0wMy50eHQ+KEFs
bG9jYXRpb25vZiBhbiBBc3NvY2lhdGVkIENoYW5uZWwgQ29kZSBQb2ludCBmb3IgVXNlIGJ5SVRV
LVQgRXRoZXJuZXRiYXNlZCBPQU0pIHRvIEluZm9ybWF0aW9uYWwgUkZDDQoNCkNvbnNpZGVyaW5n
IHRoYXQgdGhlIG5lZWQgZm9yIHRoaXMgY29kZSBwb2ludCBpcyBhIHJlc3VsdCBvZiB0aGUgSVRV
DQpub3QgZnVsbHkgY29tcGx5aW5nIHdpdGggdGhlIElFVEYgYWdyZWVtZW50LCBJIGNhbm5vdCBh
Z3JlZSB0aGF0IHdlDQpzaG91bGQgc2ltcGx5IGFsbG9jYXRlIGEgY29kZSBwb2ludCBmb3Igd2hh
dGV2ZXIgdGhlIElUVSB3YW50cyB0byBkbw0KaW4gdGhlIGZ1dHVyZS4NCg0KSXQgc2VlbXMgdGhl
IGJlc3Qgb2YgdGhlIG9wdGlvbnMgdG8gYWxsb2NhdGUgYSBjb2RlIHBvaW50IChtdWNoIGJldHRl
cg0KdGhhbiBzcXVhdHRpbmcpIC0gYnV0IHRpZSBpdCB0byBhIHN0YWJsZSByZWZlcmVuY2UuICBJ
ZiB0aGUgSVRVIGNhbid0DQpwcm92aWRlIGEgc3RhYmxlIHJlZmVyZW5jZSwgdGhlbiBwZXJoYXBz
IGFuIFJGQyBpcyB0aGUgYmVzdCB3YXkuDQpUaGVyZSBhcmUgbG90cyBvZiBmb2xrcyB3aXRoIG9w
aW5pb25zIG9uIHRoZSBiZXN0IHByb2NlZHVyZSwgYnV0IEkNCmNlcnRhaW5seSBkb24ndCBzdXBw
b3J0IHRoZSBpZGVhIG9mIG5vdCByZXN0cmljdGluZyB0aGUgdXNhZ2UgdG8gd2hhdA0KaXMgY2xl
YXJseSBkZWZpbmVkLg0KDQpBbGlhDQoNCi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQpGcm9t
OiBpZXRmLWJvdW5jZXNAaWV0Zi5vcmcgW21haWx0bzppZXRmLWJvdW5jZXNAaWV0Zi5vcmddIE9u
IEJlaGFsZiBPZiBTcHJlY2hlciwgTnVyaXQgKE5TTiAtIElML0hvZCBIYVNoYXJvbikNClNlbnQ6
IHF1YXJ0YS1mZWlyYSwgMjEgZGUgTWFyw6dvIGRlIDIwMTIgMDc6NDINClRvOiBodXViYXR3b3Jr
QGdtYWlsLmNvbTsgaWV0ZkBpZXRmLm9yZw0KU3ViamVjdDogUkU6IExhc3QgQ2FsbDogPGRyYWZ0
LWJldHRzLWl0dS1vYW0tYWNoLWNvZGUtcG9pbnQtMDMudHh0PiAoQWxsb2NhdGlvbm9mIGFuIEFz
c29jaWF0ZWQgQ2hhbm5lbCBDb2RlIFBvaW50IGZvciBVc2UgYnkgSVRVLVQgRXRoZXJuZXQgYmFz
ZWRPQU0pIHRvIEluZm9ybWF0aW9uYWwgUkZDDQoNCkhlbGxvLA0KSSBzdGlsbCBleHBlY3QgdGhl
IGF1dGhvciBvZiBkcmFmdC1iZXR0cyB0byBhbnN3ZXIgbXkgcXVlc3Rpb24uLi4NCgkiTWF5YmUg
eW91IGNvdWxkIGNsYXJpZnkgaG93IHRoZSB0ZXh0IGluIHlvdXIgZHJhZnQgY2FuIGJlIGltcHJv
dmVkIHRvIHByb3RlY3QgdGhlIHVzZSBvZiB0aGUgY29kZSBwb2ludCBmcm9tIGZ1dHVyZSBleHRl
bnNpb25zIGJleW9uZCB0aGUgcHVycG9zZSBvZiB0aGUgY29kZSBwb2ludCBhbGxvY2F0aW9uPyIN
CkkgYW0gYSBiaXQgZGlzYXBwb2ludGVkIHRvIHNlZSB0aGF0IHRoZSBhdXRob3Igc2ltcGx5IGRv
ZXMgbm90IHJlc3BvbmQgdG8gdGhlIHF1ZXN0aW9ucyBhbmQgcHJvcG9zZWQgbW9kaWZpY2F0aW9u
cyBoZSBnb3Qgb24gdGhlIGxpc3QuIA0KSWYgd2Ugd2FudCB0byBwcm9kdWN0aXZlbHkgbW92ZSBm
b3J3YXJkLCBpdCB3b3VsZCBiZSBnb29kIHRvIGhhdmUgdGhlIGF1dGhvciByZXNwb25kaW5nIHRv
IHRoZSBxdWVzdGlvbnMgYW5kIHByb3Bvc2Fscy4gDQpCZXN0IHJlZ2FyZHMsDQpOdXJpdA0KDQoN
Cg0KLS0tLS0gT3JpZ2luYWwgTWVzc2FnZSAtLS0tLQ0KRnJvbTogIlNwcmVjaGVyLCBOdXJpdCAo
TlNOIC0gSUwvSG9kIEhhU2hhcm9uKSIgPG51cml0LnNwcmVjaGVyQG5zbi5jb20+DQpUbzogIkFu
ZHJldyBHLiBNYWxpcyIgPGFnbWFsaXNAZ21haWwuY29tPjsgImV4dCBSb3NzIENhbGxvbiINCjxy
Y2FsbG9uQGp1bmlwZXIubmV0Pg0KQ2M6IDxpZXRmQGlldGYub3JnPg0KU2VudDogVHVlc2RheSwg
TWFyY2ggMTMsIDIwMTIgODowOSBQTQ0KU3ViamVjdDog15TXoNeT15XXnzogUkU6IExhc3QNCkNh
bGw6PGRyYWZ0LWJldHRzLWl0dS1vYW0tYWNoLWNvZGUtcG9pbnQtMDMudHh0PihBbGxvY2F0aW9u
b2YgYW4gQXNzb2NpYXRlZCBDaGFubmVsIENvZGUgUG9pbnQgZm9yIFVzZSBieUlUVS1UIEV0aGVy
bmV0YmFzZWQgT0FNKSB0byBJbmZvcm1hdGlvbmFsIFJGQw0KDQoNClJvc3MsDQppIGFtIGFmcmFp
ZCB0aGF0IHlvdSBtaXNzZWQgdGhlIHBvaW50LiBUaGVyZSB3aWxsIG5vdCBiZSBhIGZpbmFsIHZl
cnNpb24gc2luY2UgYXMgd3JpdHRlbiBpbiBkcmFmdC1iZXR0cywgYWxsICBJVFUgcmVjb21tZW5k
YXRpb25zIGFyZSBzdWJqZWN0IHRvIHJldmlzaW9ucywgYW5kIHRoZSBjb2RlIHBvaW50IHdpbGwg
YWxzbyBiZSB1c2VkIGZvciBmdXR1cmUgcmV2aXNpb25zIG9mIHRoZSBkb2N1bWVudC4gTmV3IG1l
c3NhZ2VzL3Byb3RvY29scyBjYW4gYmUgZGVmaW5lZCBpbiBmdXR1cmUgcmV2aXNpb25zIG9mIHRo
ZSByZWNvbW1lbmRhdGlvbiBhbmQgdGhleSB3aWxsIHVzZSB0aGUgc2FtZSBjb2RlIHBvaW50IHRo
YXQgaXMgYWxsb2NhdGVkIGZvciB0aGUgZmlyc3QgdmVyc2lvbi4NClRoaXMgaXMgYSByZWFsIGlz
c3VlLg0KUmVnYXJkcywNCk51cml0DQotLS0tLdeU15XXk9ei15Qg157Xp9eV16jXmdeqLS0tLS0N
Ctee15DXqjogZXh0IFJvc3MgQ2FsbG9uDQrXoNep15zXlzogIDEzLzAzLzIwMTIsIDE5OjI3DQrX
kNecOiBBbmRyZXcgRy4gTWFsaXM7IFNwcmVjaGVyLCBOdXJpdCAoTlNOIC0gSUwvSG9kIEhhU2hh
cm9uKQ0K16LXldeq16c6IGlldGZAaWV0Zi5vcmcNCteg15XXqdeQOiBSRTogTGFzdCBDYWxsOjxk
cmFmdC1iZXR0cy1pdHUtb2FtLWFjaC1jb2RlLXBvaW50LTAzLnR4dD4oQWxsb2NhdGlvbm9mIGFu
IEFzc29jaWF0ZWQgQ2hhbm5lbCBDb2RlIFBvaW50IGZvciBVc2UgYnlJVFUtVCBFdGhlcm5ldGJh
c2VkIE9BTSkgdG8gSW5mb3JtYXRpb25hbCBSRkMgSSBhZ3JlZSB0aGF0IHRoZSBhbGxvY2F0aW9u
IG9mIGEgY29kZSBwb2ludCBzaG91bGQgYmUgdG8gYSBzcGVjaWZpYyB2ZXJzaW9uIG9mIDgxMTMu
MSwNCg0KPHRwPg0KV2h5Pw0KDQpJIGNhbiB1bmRlcnN0YW5kIGEgbmV3IGNvZGUgcG9pbnQgYmVp
bmcgcmVxdWlyZWQgaWYgdGhlcmUgaXMgYSBuZXcgYW5kIGJhY2t3YXJkcyBpbmNvbXBhdGlibGUg
Zm9ybWF0IGZvciB0aGUgbWVzc2FnZXMsIGJ1dCBpZiB0aGUgbWVzc2FnZXMgYXJlIGV4dGVuZGVk
IGluIGEgZm9yd2FyZHMgY29tcGF0aWJsZSBtYW5uZXIsIGFkZGluZyBuZXcgVExWIGZvciBleGFt
cGxlLCBvciBhIG5ldyBmb3JtYXQgb2YgSUZfSUQsIHRoZW4gd2h5IHNob3VsZCB3ZSBidXJuIGEg
bmV3IGNvZGUgcG9pbnQ/DQoNCldvdWxkIHlvdSBzYXkgdGhhdCB3ZSBzaG91bGQgaGF2ZSBhIGRv
emVuIGRpZmZlcmVudCBwb3J0IG51bWJlcnMgZm9yIEhUVFAgdG8gcmVmbGVjdCBpdHMgZXZvbHV0
aW9uIG92ZXIgdGltZT8gIElmIG5vdCwgd2h5IG5vdD8NCg0KRGVtYW5kaW5nIHRoYXQgdGhlIElU
VS1UIGNvbWUgYmFjayB0byB1cyBmb3IgYSBuZXcgcm91bmQgb2YgbmVnb3RpYXRpb24gd2hlbiBp
dCBpcyB0ZWNobmljYWxseSB1bm5lY2Vzc2FyeSBzZWVtcyB0byBiZSBwbGFjaW5nIGFuIHVubmVj
ZXNzYXJ5IGJhcnJpZXIgYmV0d2VlbiB0aGUgdHdvIFNET3MuDQoNClRvbSBQZXRjaA0KDQphbmQg
c3BlY2lmaWNhbGx5IHNob3VsZCBiZSB0byB0aGUgZmluYWwgdmVyc2lvbiB0aGF0IGlzIGFwcHJv
dmVkIGJ5IHRoZSBJVFUtVCAoYXNzdW1pbmcgdGhhdCBhIGZpbmFsIHZlcnNpb24gb2YgODExMy4x
IHdpbGwgYmUgYXBwcm92ZWQgYnkgdGhlIElUVS1UKS4gVGhpcyB3b3VsZCBpbXBseSB0aGF0IGRy
YWZ0LWJldHRzLWl0dS1vYW0tYWNoLWNvZGUtcG9pbnQgc2hvdWxkIGNvbnRhaW4gYSBub3JtYXRp
dmUgcmVmZXJlbmNlIHRvIHRoZSBmaW5hbCBhcHByb3ZlZCB2ZXJzaW9uIG9mIDgxMTMuMS4NCg0K
R2l2ZW4gbm9ybWFsIElFVEYgcHJvY2Vzc2VzLCB0aGlzIGltcGxpZXMgdGhhdCB0aGUgZmluYWwg
UkZDIHJlc3VsdGluZyBmcm9tIGRyYWZ0LWJldHRzLWl0dS1vYW0tYWNoLWNvZGUtcG9pbnQgY291
bGQgYmUgcHVibGlzaGVkIGFzIHNvb24gYXMgdGhlIGZpbmFsIHZlcnNpb24gb2YgODExMy4xIGlz
IGFwcHJvdmVkICh3aXRoIHRoZSB1bmRlcnN0YW5kaW5nIHRoYXQgdGhlcmUgd2lsbCBiZSBhIHNt
YWxsIG5vcm1hbCBkZWxheSBiZXR3ZWVuICJhcHByb3ZlZCIgYW5kICJwdWJsaXNoZWQiIHdoaWNo
IGdpdmVzIHRpbWUgZm9yIGNvb3JkaW5hdGlvbikuIEdpdmVuIHRoYXQgdGhlIGZpbmFsIHZlcnNp
b24gb2YgODExMy4xIG1pZ2h0IG5lZWQgdG8gcmVmZXJlbmNlIHRoZSBSRkMgcmVzdWx0aW5nIGZy
b20gZHJhZnQtYmV0dHMtaXR1LW9hbS1hY2gtY29kZS1wb2ludCwgYSBiaXQgb2YgY29vcGVyYXRp
b24gbWlnaHQgYmUgbmVlZGVkIGJldHdlZW4gZWRpdG9yaWFsIHN0YWZmIGF0IHRoZSBJVFUgYW5k
IFJGQyBlZGl0b3JpYWwgc3RhZmYsIGJ1dCBJIGRvbid0IHNlZSB3aHkgdGhpcyBzaG91bGQgYmUg
YSBwcm9ibGVtIChJIGFtIHN1cmUgdGhhdCB0aGV5IGFsbCBoYXZlIGFjY2VzcyB0byBlbWFpbCku
DQoNClJvc3MNCg0KLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCkZyb206IGlldGYtYm91bmNl
c0BpZXRmLm9yZyBbbWFpbHRvOmlldGYtYm91bmNlc0BpZXRmLm9yZ10gT24gQmVoYWxmIE9mIEFu
ZHJldyBHLiBNYWxpcw0KU2VudDogTW9uZGF5LCBNYXJjaCAwNSwgMjAxMiA2OjU0IFBNDQpUbzog
U3ByZWNoZXIsIE51cml0IChOU04gLSBJTC9Ib2QgSGFTaGFyb24pDQpDYzogaWV0ZkBpZXRmLm9y
Zw0KU3ViamVjdDogUmU6IExhc3QgQ2FsbDogPGRyYWZ0LWJldHRzLWl0dS1vYW0tYWNoLWNvZGUt
cG9pbnQtMDMudHh0PihBbGxvY2F0aW9ub2YNCmFuIEFzc29jaWF0ZWQgQ2hhbm5lbCBDb2RlIFBv
aW50IGZvciBVc2UgYnlJVFUtVCBFdGhlcm5ldGJhc2VkIE9BTSkgdG8gSW5mb3JtYXRpb25hbCBS
RkMNCg0KSSB3b3VsZCBsaWtlIHRvIHN1cHBvcnQgTnVyaXQncyBjb21tZW50cyBiZWxvdy4gSW4g
cGFydGljdWxhciwgaW4gdGhlIHBhc3QgdGhlIElUVS1UIGhhcyBleHBhbmRlZCB1cG9uIG9yIGNo
YW5nZWQgdGhlIHVzYWdlIG9mIElFVEYgY29kZXBvaW50IGFsbG9jYXRpb25zLCBpbiBzb21lIGNh
c2VzIGluY29tcGF0aWJseSB3aXRoIGl0cyBvcmlnaW5hbCB1c2FnZSBvciBkZWZpbml0aW9uLiBJ
biB0aGUgZnV0dXJlLCBhbGwgY29kZXBvaW50IGFsbG9jYXRpb25zIHRvIHRoZSBJVFUtVCBzaG91
bGQgYmUgdGllZCB0byBvbmUgc3BlY2lmaWMsIGRhdGVkIHJldmlzaW9uIG9mIHRoZWlyIHNwZWNp
ZmljYXRpb24gb25seS4gVGhpcyBpcyBzaW1pbGFyIHRvIHRoZSBJVFUtVCdzIG93biBwcm9jZXNz
ZXMsIHN1Y2ggYXMgc2VjdGlvbiAyLjIuMSBvZiBSZWMuIEEuNSwgd2hpY2ggcmVxdWlyZXMgYSB2
ZXJzaW9uIG51bWJlciBhbmQvb3IgZGF0ZSBmb3IgcmVmZXJlbmNlZCBvdXRzaWRlIGRvY3VtZW50
cyBpbiBJVFUtVCByZWNvbW1lbmRhdGlvbnMuDQoNCkNoZWVycywNCkFuZHkNCg0KT24gVGh1LCBN
YXIgMSwgMjAxMiBhdCA3OjIwIEFNLCBTcHJlY2hlciwgTnVyaXQgKE5TTiAtIElML0hvZA0KSGFT
aGFyb24pIDxudXJpdC5zcHJlY2hlckBuc24uY29tPiB3cm90ZToNCj4gSGksDQo+DQo+DQo+DQo+
IEkgY2Fubm90IHN1cHBvcnQgdGhlIHB1YmxpY2F0aW9uIG9mIHRoZSBkb2N1bWVudCBpbiBpdHMg
Y3VycmVudCB2ZXJzaW9uLg0KPg0KPg0KPg0KPiBJIGhhdmUgdGhlIGZvbGxvd2luZyBjb25jZXJu
czoNCj4NCj4NCj4NCj4gLiAgICAgICAgSXQgaXMgaW5kaWNhdGVkIHRoYXQgdGhlIGNoYW5uZWwg
aXMgaW50ZW5kZWQgdG8gYmUgdXNlZCB0byBjYXJyeQ0KPiBFdGhlcm5ldCBiYXNlZCBPQU0gbWVz
c2FnZXMuIEl0IGlzIG5vdCBjbGVhciB3aHkgdGhlcmUgaXMgYSBuZWVkIGZvciBBQ0guDQo+IFBX
cyBjYW4gYmUgdXNlZCB0byB0cmFuc21pdCBFdGhlcm5ldCBPQU0uDQo+DQo+IElmIHRoZSBpbnRl
bnRpb24gaXMgdG8gdXNlIHRoZSBjaGFubmVsIGZvciBPQU0gbWVzc2FnZXMgZm9yIG9wZXJhdGlu
Zw0KPiBNUExTLVRQIGJhc2VkIG5ldHdvcmtzLCB0aGUgSUVURiAqYWxyZWFkeSogZGVmaW5lZCBh
IHNvbHV0aW9uIGZvcg0KPiBNUExTLVRQIE9BTSBhbmQgSSBleHBlY3QgdG8gc2VlIGZpcnN0IGEg
dGVjaG5pY2FsICpqdXN0aWZpY2F0aW9uKiB3aHkNCj4gYSBzZWNvbmQgc29sdXRpb24gaXMgbmVl
ZGVkLiBJbiBhZGRpdGlvbiwgSSB3b3VsZCBleHBlY3QgdG8gc2VlDQo+ICpyZWZlcmVuY2VzIHRv
IHRoZQ0KPiBhcmd1bWVudHMqIHJhaXNlZCBpbiBkcmFmdC1zcHJlY2hlci1tcGxzLXRwLW9hbS1j
b25zaWRlcmF0aW9ucy4NCj4NCj4NCj4NCj4gLiAgICAgICAgSXQgaXMgbm90IGNsZWFyIHdoYXQg
dGhlIG1hdHVyaXR5IHN0YXR1cyBvZiBHLjgxMTMuMSBpcy4gSXQgc2VlbXMNCj4gdGhhdCB0aGUg
ZG9jdW1lbnQgd2FzIG5vdCBhcHByb3ZlZCBieSBTRzE1IGFuZCB0aGUgZGlzY3Vzc2lvbiB3YXMN
Cj4gZGVmZXJyZWQgdG8gV1RTQS4gVGhpcyBpbmRpY2F0ZXMgdGhhdCB0aGVyZSBpcyAqbm8gY29u
c2Vuc3VzKiBmb3IgdGhlDQo+IGFwcHJvdmFsIG9mIEcuODExMy4xLiBBIGNvZGUgcG9pbnQgc2hv
dWxkIG5vdCBiZSBhbGxvY2F0ZWQgYmVmb3JlIGENCj4gY29uc2Vuc3VzL2RlY2lzaW9uIGlzIHJl
YWNoZWQgaW4gdGhlIElUVS1UIGFuZCBiZWZvcmUgdGhlIGRvY3VtZW50IGlzDQo+IG1hdHVyZSBh
bmQgYXBwcm92ZWQuIEkgZG8gbm90IHRoaW5rIGl0IGlzIGFwcHJvcHJpYXRlIHRvIGFsbG9jYXRl
IGENCj4gY29kZSBwb2ludCBhbmQgdHJ5IHRvIGZvcmNlIGEgcmVzb2x1dGlvbiBpbiB0aGUgSVRV
LVQuDQo+DQo+DQo+DQo+IC4gICAgICAgIEkgZmluZCBhIGNvbnRyYWRpY3Rpb24gaW4gdGhlIGRy
YWZ0LiBJbiBvbmUgcGxhY2UgaXQgaXMgbWVudGlvbmVkOg0KPiAiVGhlc2UgRXRoZXJuZXQgYmFz
ZWQgT0FNIG1lc3NhZ2VzIGFuZCBwcm9jZWR1cmVzLCBhZGRyZXNzIHRoZSBPQU0NCj4gZnVuY3Rp
b25hbCByZXF1aXJlbWVudHMgZGVmaW5lZCBpbiBbUkZDNTg2MF0uIE90aGVyIG1lc3NhZ2UgdHlw
ZXMNCj4gc2hvdWxkIG5vdCBiZSBjYXJyaWVkIGJlaGluZCB0aGlzIGNvZGUgcG9pbnQuIiBJbiBh
bm90aGVyIHBsYWNlIGl0IGlzDQo+IG1lbnRpb25lZDogImFsbCBJVFUtVCBSZWNvbW1lbmRhdGlv
bnMgYXJlIHN1YmplY3QgdG8gcmV2aXNpb24uDQo+IFRoZXJlZm9yZSwgdGhlIGNvZGUgcG9pbnQg
YWxsb2NhdGVkIGJ5IHRoaXMgZG9jdW1lbnQgbWF5IGJlIHVzZWQgZm9yIGZ1dHVyZSB2ZXJzaW9u
cyBvZiBbRy44MTEzLjFdLiIuDQo+IFRoZSBsYXN0IHN0YXRlbWVudCBvcGVucyB0aGUgZG9vciBm
b3IgdGhlIGRlZmluaXRpb24gb2YgYWRkaXRpb25hbA0KPiBtZXNzYWdlcyBpbiBHLjgxMTMuMSBp
biB0aGUgZm9sbG93aW5nIHZlcnNpb25zLCBmb3IgZXhhbXBsZSwgZm9yIEFQUw0KPiAoc3VwcG9y
dGluZyBsaW5lYXIgb3IgcmluZyBwcm90ZWN0aW9uIG1lY2hhbmlzbXMpIGFuZCBieSB0aGlzIGNy
ZWF0ZXMNCj4gdHdvIHNvbHV0aW9ucyBmb3Igb3RoZXIgbWVjaGFuaXNtcyBhcyB3ZWxsLg0KPg0K
Pg0KPg0KPiBUaGUgdXNlIG9mIHRoZSBjb2RlIHBvaW50IGNhbiBnbyBtdWNoIGJleW9uZCBpdHMg
b3JpZ2luYWwgcHVycG9zZSBhbmQNCj4gaXQgd2lsbCBoaWRlIG90aGVyIG1lc3NhZ2VzLi4uLmEg
Y29kZSBwb2ludCBzaG91bGQgbm90IGJlIGFsbG9jYXRlZCBhdA0KPiB0aGlzIHBvaW50IGF0IGFs
bCwgYnV0IHNwZWNpZmljYWxseSBub3QgZm9yIHVua25vd24gdXNhZ2UgdGhhdCBtYXkgYmUNCj4g
ZGVmaW5lZCBpbiBmdXR1cmUgdmVyc2lvbnMgb2YgRy44MTEzLjEuDQo+DQo+DQo+DQo+IEJlc3Qg
cmVnYXJkcywNCj4NCj4gTnVyaXQNCj4NCj4NCj4NCj4NCj4NCj4NCj4NCj4+IC0tLS0tT3JpZ2lu
YWwgTWVzc2FnZS0tLS0tDQo+DQo+PiBGcm9tOiBpZXRmLWFubm91bmNlLWJvdW5jZXNAaWV0Zi5v
cmcgW21haWx0bzppZXRmLWFubm91bmNlLQ0KPg0KPj4gYm91bmNlc0BpZXRmLm9yZ10gT24gQmVo
YWxmIE9mIFRoZSBJRVNHDQo+DQo+PiBTZW50OiAyMiBGZWJydWFyeSAyMDEyIDE1OjEzDQo+DQo+
PiBUbzogSUVURi1Bbm5vdW5jZQ0KPg0KPj4gU3ViamVjdDogTGFzdCBDYWxsOiA8ZHJhZnQtYmV0
dHMtaXR1LW9hbS1hY2gtY29kZS1wb2ludC0wMy50eHQ+DQo+DQo+IChBbGxvY2F0aW9uIG9mDQo+
DQo+IGFuDQo+DQo+PiBBc3NvY2lhdGVkIENoYW5uZWwgQ29kZSBQb2ludCBmb3IgVXNlIGJ5IElU
VS1UIEV0aGVybmV0IGJhc2VkIE9BTSkgdG8NCj4NCj4+IEluZm9ybWF0aW9uYWwgUkZDDQo+DQo+
Pg0KPg0KPj4NCj4NCj4+IFRoZSBJRVNHIGhhcyByZWNlaXZlZCBhIHJlcXVlc3QgZnJvbSBhbiBp
bmRpdmlkdWFsIHN1Ym1pdHRlciB0bw0KPg0KPiBjb25zaWRlcg0KPg0KPj4gdGhlIGZvbGxvd2lu
ZyBkb2N1bWVudDoNCj4NCj4+IC0gJ0FsbG9jYXRpb24gb2YgYW4gQXNzb2NpYXRlZCBDaGFubmVs
IENvZGUgUG9pbnQgZm9yIFVzZSBieSBJVFUtVA0KPg0KPj4gICAgRXRoZXJuZXQgYmFzZWQgT0FN
Jw0KPg0KPj4gICA8ZHJhZnQtYmV0dHMtaXR1LW9hbS1hY2gtY29kZS1wb2ludC0wMy50eHQ+IGFz
IGFuIEluZm9ybWF0aW9uYWwgUkZDDQo+DQo+Pg0KPg0KPj4gVGhlIElFU0cgcGxhbnMgdG8gbWFr
ZSBhIGRlY2lzaW9uIGluIHRoZSBuZXh0IGZldyB3ZWVrcywgYW5kIHNvbGljaXRzDQo+DQo+PiBm
aW5hbCBjb21tZW50cyBvbiB0aGlzIGFjdGlvbi4gUGxlYXNlIHNlbmQgc3Vic3RhbnRpdmUgY29t
bWVudHMgdG8NCj4+IHRoZQ0KPg0KPj4gaWV0ZkBpZXRmLm9yZyBtYWlsaW5nIGxpc3RzIGJ5IDIw
MTItMDMtMjEuIEV4Y2VwdGlvbmFsbHksIGNvbW1lbnRzDQo+PiBtYXkNCj4NCj4gYmUNCj4NCj4+
IHNlbnQgdG8gaWVzZ0BpZXRmLm9yZyBpbnN0ZWFkLiBJbiBlaXRoZXIgY2FzZSwgcGxlYXNlIHJl
dGFpbiB0aGUNCj4NCj4+IGJlZ2lubmluZyBvZiB0aGUgU3ViamVjdCBsaW5lIHRvIGFsbG93IGF1
dG9tYXRlZCBzb3J0aW5nLg0KPg0KPj4NCj4NCj4+IEFic3RyYWN0DQo+DQo+Pg0KPg0KPj4gICAg
VGhpcyBkb2N1bWVudCBhc3NpZ25zIGFuIEFzc29jaWF0ZWQgQ2hhbm5lbCBUeXBlIGNvZGUgcG9p
bnQgZm9yDQo+DQo+PiAgICBjYXJyeWluZyBFdGhlcm5ldCBiYXNlZCBPcGVyYXRpb25zLCBBZG1p
bmlzdHJhdGlvbiwgYW5kIE1hbmFnZW1lbnQNCj4NCj4+ICAgIG1lc3NhZ2VzIGluIHRoZSBNUExT
IEdlbmVyaWMgQXNzb2NpYXRlZCBDaGFubmVsIChHLUFDaCkuDQo+DQo+Pg0KPg0KPj4gVGhlIGZp
bGUgY2FuIGJlIG9idGFpbmVkIHZpYQ0KPg0KPj4gaHR0cDovL2RhdGF0cmFja2VyLmlldGYub3Jn
L2RvYy9kcmFmdC1iZXR0cy1pdHUtb2FtLWFjaC1jb2RlLXBvaW50Lw0KPg0KPj4NCj4NCj4+IElF
U0cgZGlzY3Vzc2lvbiBjYW4gYmUgdHJhY2tlZCB2aWENCj4NCj4+IGh0dHA6Ly9kYXRhdHJhY2tl
ci5pZXRmLm9yZy9kb2MvZHJhZnQtYmV0dHMtaXR1LW9hbS1hY2gtY29kZS1wb2ludC8NCj4NCj4+
DQo+DQo+Pg0KPg0KPj4gTm8gSVBSIGRlY2xhcmF0aW9ucyBoYXZlIGJlZW4gc3VibWl0dGVkIGRp
cmVjdGx5IG9uIHRoaXMgSS1ELg0KPg0KPj4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX18NCj4NCj4+IElFVEYtQW5ub3VuY2UgbWFpbGluZyBsaXN0DQo+DQo+
PiBJRVRGLUFubm91bmNlQGlldGYub3JnDQo+DQo+PiBodHRwczovL3d3dy5pZXRmLm9yZy9tYWls
bWFuL2xpc3RpbmZvL2lldGYtYW5ub3VuY2UNCj4NCj4NCj4NCj4gX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCj4NCj4gbXBscyBtYWlsaW5nIGxpc3QNCj4N
Cj4gbXBsc0BpZXRmLm9yZw0KPg0KPiBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3Rp
bmZvL21wbHMNCj4NCj4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX18NCj4NCj4gSWV0ZiBtYWlsaW5nIGxpc3QNCj4NCj4gSWV0ZkBpZXRmLm9yZw0KPg0KPiBo
dHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2lldGYNCj4NCj4gX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCj4NCj4gSWV0ZiBtYWlsaW5n
IGxpc3QNCj4NCj4gSWV0ZkBpZXRmLm9yZw0KPg0KPiBodHRwczovL3d3dy5pZXRmLm9yZy9tYWls
bWFuL2xpc3RpbmZvL2lldGYNCj4NCj4NCj4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX18NCj4gSWV0ZiBtYWlsaW5nIGxpc3QNCj4gSWV0ZkBpZXRmLm9yZw0K
PiBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2lldGYNCj4NCl9fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQpJZXRmIG1haWxpbmcgbGlz
dA0KSWV0ZkBpZXRmLm9yZw0KaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9p
ZXRmDQoNCg0KDQotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KDQoNCj4gX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCj4gSWV0ZiBtYWlsaW5nIGxpc3QNCj4g
SWV0ZkBpZXRmLm9yZw0KPiBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2ll
dGYNCj4NCg0KDQoNClF1ZXN0byBtZXNzYWdnaW8gZSBpIHN1b2kgYWxsZWdhdGkgc29ubyBpbmRp
cml6emF0aSBlc2NsdXNpdmFtZW50ZSBhbGxlIHBlcnNvbmUgaW5kaWNhdGUuIExhIGRpZmZ1c2lv
bmUsIGNvcGlhIG8gcXVhbHNpYXNpIGFsdHJhIGF6aW9uZSBkZXJpdmFudGUgZGFsbGEgY29ub3Nj
ZW56YSBkaSBxdWVzdGUgaW5mb3JtYXppb25pIHNvbm8gcmlnb3Jvc2FtZW50ZSB2aWV0YXRlLiBR
dWFsb3JhIGFiYmlhdGUgcmljZXZ1dG8gcXVlc3RvIGRvY3VtZW50byBwZXIgZXJyb3JlIHNpZXRl
IGNvcnRlc2VtZW50ZSBwcmVnYXRpIGRpIGRhcm5lIGltbWVkaWF0YSBjb211bmljYXppb25lIGFs
IG1pdHRlbnRlIGUgZGkgcHJvdnZlZGVyZSBhbGxhIHN1YSBkaXN0cnV6aW9uZSwgR3JhemllLg0K
DQpUaGlzIGUtbWFpbCBhbmQgYW55IGF0dGFjaG1lbnRzIGlzIGNvbmZpZGVudGlhbCBhbmQgbWF5
IGNvbnRhaW4gcHJpdmlsZWdlZCBpbmZvcm1hdGlvbiBpbnRlbmRlZCBmb3IgdGhlIGFkZHJlc3Nl
ZShzKSBvbmx5LiBEaXNzZW1pbmF0aW9uLCBjb3B5aW5nLCBwcmludGluZyBvciB1c2UgYnkgYW55
Ym9keSBlbHNlIGlzIHVuYXV0aG9yaXNlZC4gSWYgeW91IGFyZSBub3QgdGhlIGludGVuZGVkIHJl
Y2lwaWVudCwgcGxlYXNlIGRlbGV0ZSB0aGlzIG1lc3NhZ2UgYW5kIGFueSBhdHRhY2htZW50cyBh
bmQgYWR2aXNlIHRoZSBzZW5kZXIgYnkgcmV0dXJuIGUtbWFpbCwgVGhhbmtzLg0KDQo=

From RCosta@ptinovacao.pt  Thu Mar 22 07:44:50 2012
Return-Path: <RCosta@ptinovacao.pt>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8BA6821F85D3 for <ietf@ietfa.amsl.com>; Thu, 22 Mar 2012 07:44:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.356
X-Spam-Level: 
X-Spam-Status: No, score=-2.356 tagged_above=-999 required=5 tests=[AWL=0.243,  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 v+Mci1lqH1ut for <ietf@ietfa.amsl.com>; Thu, 22 Mar 2012 07:44:49 -0700 (PDT)
Received: from owa.ptinovacao.pt (mail6.ptinovacao.pt [194.65.138.99]) by ietfa.amsl.com (Postfix) with ESMTP id 865B821F85C6 for <ietf@ietf.org>; Thu, 22 Mar 2012 07:44:49 -0700 (PDT)
Received: from INOAVREX11.ptin.corpPT.com ([10.112.15.122]) by inoavrcas01.ptin.corpPT.com ([10.112.15.99]) with mapi; Thu, 22 Mar 2012 14:44:48 +0000
From: Rui Costa <RCosta@ptinovacao.pt>
To: "huubatwork@gmail.com" <huubatwork@gmail.com>, "ietf@ietf.org" <ietf@ietf.org>
Date: Thu, 22 Mar 2012 14:44:47 +0000
Subject: RE: Last Call: <draft-ietf-mpls-tp-oam-analysis-08.txt> (An Overview	of the OAM Tool Set for MPLS based Transport Networks) to Informational RFC
Thread-Topic: Last Call: <draft-ietf-mpls-tp-oam-analysis-08.txt> (An Overview	of the OAM Tool Set for MPLS based Transport Networks) to Informational RFC
Thread-Index: Ac0HtOWjpBgo4U97TvGMg40QqhM1igAaGAQQ
Message-ID: <52981DB05D3C5247A12D0AEE309F3CC202444240C162@INOAVREX11.ptin.corpPT.com>
References: <20120309205157.8304.55419.idtracker@ietfa.amsl.com> <4F6A5ADB.2090002@gmail.com>
In-Reply-To: <4F6A5ADB.2090002@gmail.com>
Accept-Language: pt-PT
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: pt-PT
Content-Type: text/plain; charset="iso-8859-1"
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, 22 Mar 2012 14:44:50 -0000

Hello,=09

i) I support this proposal.=09

Apart from the text section mentioned below, the different versions of the =
draft (at least the initial ones) have presented, from the available option=
s and IMHO, Y.1731 as the readiest/closest most to requirements. On the oth=
er hand, this section looks to want being a memorandum about decisions rega=
rding OAM, which didn't follow that option. So, it's important not to put I=
TU-T or MEAD in subject for that.=09


ii) " [RFC 6375]=09
      augments that set of identifiers to include identifier information=09
      in a format used by the ITU-T"=09
Is the intended reference [MPLS TP ITU Idents], draft-ietf-mpls-tp-itu-t-id=
entifiers? 6375's related to packet loss and delay measurements, not to ide=
ntifiers.=09

Regards,=09
Rui=09


-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of Huu=
b van Helvoort
Sent: quarta-feira, 21 de Mar=E7o de 2012 22:49
To: ietf@ietf.org
Subject: Re: Last Call: <draft-ietf-mpls-tp-oam-analysis-08.txt> (An Overvi=
ew of the OAM Tool Set for MPLS based Transport Networks) to Informational =
RFC

IESG,

I do *NOT* support this draft unless the following changes are made:

The first paragraph of section 8 Acknowledgements has to be removed:
It is an attempt to capture history, but lacks accuracy.
Removal does not impact the technical information in the draft; the tools h=
ave evolved significantly from the strawman tools proposed in Stockholm; so=
me members of the MEAD team (I am one of them) do not consider that an agre=
ement on this proposal was reached.

I also request the removal of my name from this acknowledgements section si=
nce I do not support this tool set, neither as an individual nor as ITU-T Q=
10 rapporteur. The latter is implied by mentioning my name in the same sent=
ence as a WG chair and ADs.

Regards, Huub.

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> The IESG has received a request from the Multiprotocol Label Switching=20
> WG
> (mpls) to consider the following document:
> - 'An Overview of the OAM Tool Set for MPLS based Transport Networks'
>    <draft-ietf-mpls-tp-oam-analysis-08.txt>  as an Informational RFC
>
> The IESG plans to make a decision in the next few weeks, and solicits=20
> final comments on this action. Please send substantive comments to the=20
> ietf@ietf.org mailing lists by 2012-03-23. Exceptionally, comments may=20
> be sent to iesg@ietf.org instead. In either case, please retain the=20
> beginning of the Subject line to allow automated sorting.
>
> Abstract
>
>     This document provides an overview of the OAM toolset for MPLS based
>     Transport Networks.  The toolset consists of a comprehensive set of
>     fault management and performance monitoring capabilities (operating
>     in the data-plane) which are appropriate for transport networks as
>     required in RFC 5860 and support the network and services at
>     different nested levels.  This overview includes a brief recap of
>     MPLS-TP OAM requirements and functions, and of generic mechanisms
>     created in the MPLS data plane to allow the OAM packets run in-band
>     and share their fate with data packets.  The protocol definitions for
>     each of the MPLS-TP OAM tools are defined in separate documents (RFCs
>     or Working Group drafts) which are referenced by this document.
>
>
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-oam-analysis/
>
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-oam-analysis/ballot
> /
>
>
> No IPR declarations have been submitted directly on this I-D.
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-announce

From joelja@bogus.com  Thu Mar 22 09:38:38 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 17AC121F860B; Thu, 22 Mar 2012 09:38:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.224
X-Spam-Level: 
X-Spam-Status: No, score=-102.224 tagged_above=-999 required=5 tests=[AWL=0.375, 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 4WmrykUsrPbH; Thu, 22 Mar 2012 09:38:37 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 90D5021F85EC; Thu, 22 Mar 2012 09:38:37 -0700 (PDT)
Received: from Joels-MacBook-Pro.local (174.sub-166-250-34.myvzw.com [166.250.34.174]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id q2MGcZUw018150 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Thu, 22 Mar 2012 16:38:36 GMT (envelope-from joelja@bogus.com)
Message-ID: <4F6B5586.5070308@bogus.com>
Date: Thu, 22 Mar 2012 09:38:30 -0700
From: Joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:11.0) Gecko/20120313 Thunderbird/11.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Last Call: <draft-ietf-krb-wg-des-die-die-die-04.txt> (Deprecate DES, RC4-HMAC-EXP, and other weak cryptographic algorithms in Kerberos) to Best Current Practice
References: <20120322152611.20184.76979.idtracker@ietfa.amsl.com>
In-Reply-To: <20120322152611.20184.76979.idtracker@ietfa.amsl.com>
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]); Thu, 22 Mar 2012 16:38:37 +0000 (UTC)
Cc: ietf-krb-wg@lists.anl.gov, The IESG <iesg-secretary@ietf.org>, IETF-Announce <ietf-announce@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Mar 2012 16:38:38 -0000

On 3/22/12 08:26 , The IESG wrote:
> 
> The IESG has received a request from the Kerberos WG (krb-wg) to consider
> the following document:
> - 'Deprecate DES, RC4-HMAC-EXP, and other weak cryptographic algorithms
>    in Kerberos'
>   <draft-ietf-krb-wg-des-die-die-die-04.txt> as a 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-04-05. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.

support, it's time.

joel

From dworley@avaya.com  Thu Mar 22 09:48:27 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 477C221F8629 for <ietf@ietfa.amsl.com>; Thu, 22 Mar 2012 09:48:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.908
X-Spam-Level: 
X-Spam-Status: No, score=-102.908 tagged_above=-999 required=5 tests=[AWL=-0.309, 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 vNB2ofcbD4z3 for <ietf@ietfa.amsl.com>; Thu, 22 Mar 2012 09:48:26 -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 B0C0921F8631 for <ietf@ietf.org>; Thu, 22 Mar 2012 09:48:26 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAC1Xa0+HCzI1/2dsb2JhbABEtzuBB4IJAQEBAQIBEig/BQsCAQgNAQchECERJQEBBA4FCBqHYwWcVpwyiW2GFGMElAqHZIUghHmDAw
X-IronPort-AV: E=Sophos;i="4.73,630,1325480400";  d="scan'208";a="824164"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by p-us1-iereast-outbound.us1.avaya.com with ESMTP; 22 Mar 2012 12:48:25 -0400
Received: from dc-us1hcex2.us1.avaya.com (HELO DC-US1HCEX2.global.avaya.com) ([135.11.52.21]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 22 Mar 2012 12:32:48 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.202]) by DC-US1HCEX2.global.avaya.com ([::1]) with mapi; Thu, 22 Mar 2012 12:48:25 -0400
From: "Worley, Dale R (Dale)" <dworley@avaya.com>
To: Craig Finseth <snark17@gmail.com>
Date: Thu, 22 Mar 2012 12:48:25 -0400
Subject: RE: IPv6 Zone Identifiers Considered Hateful
Thread-Topic: IPv6 Zone Identifiers Considered Hateful
Thread-Index: Ac0Hn2xTG52tqXhYR5G1ErCJrjO76AAqtKW9
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B22726A099F@DC-US1MBEX4.global.avaya.com>
References: <82A794CE-B328-475F-9300-1B6BE628F7E3@sabahattin-gucukoglu.com> <CD5674C3CD99574EBA7432465FC13C1B22726A0994@DC-US1MBEX4.global.avaya.com> <CAGHVWBgnF49UYSaL3awXf4Y+wxvmUTFi9xYRVCZ8WL1nFZp1Aw@mail.gmail.com> <CD5674C3CD99574EBA7432465FC13C1B22726A0996@DC-US1MBEX4.global.avaya.com>, <CAGHVWBh=vKnc343ux6YFRkL=G+rH8Up2fGKDNiDSPbxMwyQvtA@mail.gmail.com>
In-Reply-To: <CAGHVWBh=vKnc343ux6YFRkL=G+rH8Up2fGKDNiDSPbxMwyQvtA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Sabahattin Gucukoglu <mail-dated-1334746550.15c4ac@sabahattin-gucukoglu.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Mar 2012 16:48:27 -0000

> From: Craig Finseth [snark17@gmail.com]
>=20
> > Actually, it's globally *unique*, because it contains the MAC address.
> > The problem is that it's not *routable*, even within the context of a
> > single host.  And unless you give an application on the host guidance,
> > it depends on host-context routing to get its output packets to the
> > correct wire.  It's hard to remain aware that host-context routing is
> > important, because it's almost always work.
>=20
> Well, it's globally unique to a host, not to an interface: the host
> (in general) uses the same link-local address on all interfaces.
> Thus, you can't tell from the address which interface it refers to.

But remember we're talking about the address given to "ping" -- it's
not the address of *this* host, but the address of some host that is
on some network on which this host has an interface.  So the fact that
this host uses the same link-local address on all interfaces, while
true, is not important.  What's important is that given the link-local
address of *some other host*, there is no algorithmic way to determine
which of this host's interfaces is needed to access it.

In regard to URIs:

People have spoken about the annoyance of using "%" to introduce the
zone identifier, and the fact that "%" is special in URIs and would
need escaping, etc.  But (1) it's unlikely anyone will write URIs with
zone identifiers, since they'd only be usable on a single host, and
(2) the syntax of RFC 3986 ("Uniform Resource Identifier (URI):
Generic Syntax") does not provide for specifying zone identifers on
IPv6 addresses.  Indeed, it says "This syntax does not support IPv6
scoped addressing zone identifiers."

Dale

From akatlas@gmail.com  Thu Mar 22 14:07:34 2012
Return-Path: <akatlas@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E3E8821E8037 for <ietf@ietfa.amsl.com>; Thu, 22 Mar 2012 14:07:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.421
X-Spam-Level: 
X-Spam-Status: No, score=-3.421 tagged_above=-999 required=5 tests=[AWL=0.178,  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 BOyuzqPZmqZd for <ietf@ietfa.amsl.com>; Thu, 22 Mar 2012 14:07:34 -0700 (PDT)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id 4C3B721E8045 for <ietf@ietf.org>; Thu, 22 Mar 2012 14:07:34 -0700 (PDT)
Received: by ggmi1 with SMTP id i1so2473056ggm.31 for <ietf@ietf.org>; Thu, 22 Mar 2012 14:07: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:content-transfer-encoding; bh=qhcf27WZEDJtSRMsgxHH+KSW77SIRhWBqrdINyfYPz0=; b=NuCXMkBkyBhw3H2tp04WSu6qdZTSCDcKqzX+zVHFKwowJtNTE8yOqQSbcWacnx6A9k iz3ogRVvTdQfN0UFPBRWHJLmqFsI8MBfilFy7iRAL8clJLykJAa3P0o6HxzBkzgnWYPi iGPoL/Vs1JTPH/lMKkYQYtcXvHiwhZ3sYR/DEFa4gbDd9XGNWWjjqHOVEYEUirOyP8i3 3THxS+FEpDGRLhPKbvHU1mH5uX6HLiypYc717XvvYK1Zn2WbLhYwF4fgVaEDVGG0E+Ou Vn7t7tdfYsQRVyWh4Kf63vdL0q7TYXWuORv3+8shSWrfi07/Oq30vcNpAoB1gtMjiPU7 6G6A==
MIME-Version: 1.0
Received: by 10.50.202.105 with SMTP id kh9mr188560igc.68.1332450453687; Thu, 22 Mar 2012 14:07:33 -0700 (PDT)
Received: by 10.50.1.209 with HTTP; Thu, 22 Mar 2012 14:07:33 -0700 (PDT)
In-Reply-To: <52981DB05D3C5247A12D0AEE309F3CC202444240C161@INOAVREX11.ptin.corpPT.com>
References: <52981DB05D3C5247A12D0AEE309F3CC202444240C161@INOAVREX11.ptin.corpPT.com>
Date: Thu, 22 Mar 2012 17:07:33 -0400
Message-ID: <CAG4d1reb=bWp09uT-tOLyvSa7q-W5a-LnpGphngg-+KR1+TcKg@mail.gmail.com>
Subject: Re: FW: Last Call:<draft-betts-itu-oam-ach-code-point-03.txt>(Allocationof an Associated Channel Code Point for Use byITU-T Ethernetbased OAM) to Informational RFC
From: Alia Atlas <akatlas@gmail.com>
To: Rui Costa <RCosta@ptinovacao.pt>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Mar 2012 21:07:35 -0000

Rui,

Perhaps more familiarity with the related history over the last
several years would help?  I can recommend the MPLS list archives.
Otherwise, I find this remarkably disingenuous.

This is a case of a second solution that was clearly rejected by the
MPLS working group (despite in-person histrionics causing the ADs to
have to threaten to close down the WG meeting).  Then the solution was
taken to the ITU study group - where it could also not get enough
traction for their normal process.  It is still not approved as a
recommendation.

To imply that the IETF should simply trust the allocated ACH code
point to not be abused both seems optimistic and sets a dreadful
precedent.

Making an allocation available for an approved recommendation version
is a tolerable way of reducing the deliberate use of an experimental
value.   Handing the keys over for any conceivable use, or even just
the uses in the OAM RFC that have been adequately met by IETF
WG-consensus based technology, does not seem appropriate.

Alia



On Thu, Mar 22, 2012 at 10:42 AM, Rui Costa <RCosta@ptinovacao.pt> wrote:
> I fail to understand the issue under discussion.
>
> Can't imagine IEEE denying to grant Ethertype 0x86DD. If, however, from a=
bsurd that had happened, would the world stop or would we take the same inf=
ormation from the IP header version field?
>
> Regards,
> Rui
>
>
> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of A=
lia Atlas
> Sent: quarta-feira, 21 de Mar=C3=A7o de 2012 15:30
> To: D'Alessandro Alessandro Gerardo
> Cc: ietf@ietf.org
> Subject: Re: =D7=94=D7=A0=D7=93=D7=95=D7=9F: RE: Last Call:<draft-betts-i=
tu-oam-ach-code-point-03.txt>(Allocationof an Associated Channel Code Point=
 for Use byITU-T Ethernetbased OAM) to Informational RFC
>
> Considering that the need for this code point is a result of the ITU
> not fully complying with the IETF agreement, I cannot agree that we
> should simply allocate a code point for whatever the ITU wants to do
> in the future.
>
> It seems the best of the options to allocate a code point (much better
> than squatting) - but tie it to a stable reference. =C2=A0If the ITU can'=
t
> provide a stable reference, then perhaps an RFC is the best way.
> There are lots of folks with opinions on the best procedure, but I
> certainly don't support the idea of not restricting the usage to what
> is clearly defined.
>
> Alia

From brian.e.carpenter@gmail.com  Thu Mar 22 15:27:31 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 5CEE821E802B for <ietf@ietfa.amsl.com>; Thu, 22 Mar 2012 15:27:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.499
X-Spam-Level: 
X-Spam-Status: No, score=-103.499 tagged_above=-999 required=5 tests=[AWL=0.100, 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 FRolMUMOWvvF for <ietf@ietfa.amsl.com>; Thu, 22 Mar 2012 15:27:30 -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 3FB9021E8013 for <ietf@ietf.org>; Thu, 22 Mar 2012 15:27:30 -0700 (PDT)
Received: by eeke51 with SMTP id e51so862092eek.31 for <ietf@ietf.org>; Thu, 22 Mar 2012 15:27:29 -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=4bBlzuvAvdV2u7giKkbGzw9VD/0duaSVdl5vT9IxqH0=; b=KOIJM9cqTjVd8AHpPjNr9RPVcXNXxmNC4mIoJvdzxH9DZi7Qdhvs03Rk+czmwCz/Wo egEe3ePmG/AIb6hPwakoZmJokbjF7XX308A77uCIDaCnFVIa1trhOxLM2hlHAgdW4ya7 8gAomkeZs1hHOyGUQJ+ZrHP9lzMxMdC1EAnRhEcH9G+k5Qhbj9cFugyKRNGi4y2w4bZ4 mTpM73qpm8NW6S8T+t7hYX3Dyyiw4Limaf450m/0DtiPpe7eEfh4gJG0GaSuNvODlCHp w5Zn2bim4MB0fPOwy57T39i3BwSAYJx+FhkicrX3WRQyID7Pnl7OQQ2Y5W9EdS1ODRWR Vu4g==
Received: by 10.14.22.16 with SMTP id s16mr1381468ees.2.1332455249379; Thu, 22 Mar 2012 15:27:29 -0700 (PDT)
Received: from [10.1.1.4] ([121.98.251.219]) by mx.google.com with ESMTPS id r44sm21521134eef.2.2012.03.22.15.27.25 (version=SSLv3 cipher=OTHER); Thu, 22 Mar 2012 15:27:28 -0700 (PDT)
Message-ID: <4F6BA746.6030709@gmail.com>
Date: Fri, 23 Mar 2012 11:27:18 +1300
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: "Worley, Dale R (Dale)" <dworley@avaya.com>
Subject: Re: IPv6 Zone Identifiers Considered Hateful
References: <82A794CE-B328-475F-9300-1B6BE628F7E3@sabahattin-gucukoglu.com>	<CD5674C3CD99574EBA7432465FC13C1B22726A0994@DC-US1MBEX4.global.avaya.com>	<CAGHVWBgnF49UYSaL3awXf4Y+wxvmUTFi9xYRVCZ8WL1nFZp1Aw@mail.gmail.com>	<CD5674C3CD99574EBA7432465FC13C1B22726A0996@DC-US1MBEX4.global.avaya.com>, <CAGHVWBh=vKnc343ux6YFRkL=G+rH8Up2fGKDNiDSPbxMwyQvtA@mail.gmail.com> <CD5674C3CD99574EBA7432465FC13C1B22726A099F@DC-US1MBEX4.global.avaya.com>
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B22726A099F@DC-US1MBEX4.global.avaya.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Sabahattin Gucukoglu <mail-dated-1334746550.15c4ac@sabahattin-gucukoglu.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Mar 2012 22:27:31 -0000

On 2012-03-23 05:48, Worley, Dale R (Dale) wrote:
...

> In regard to URIs:
> 
> People have spoken about the annoyance of using "%" to introduce the
> zone identifier, and the fact that "%" is special in URIs and would
> need escaping, etc.  But (1) it's unlikely anyone will write URIs with
> zone identifiers, since they'd only be usable on a single host, and
> (2) the syntax of RFC 3986 ("Uniform Resource Identifier (URI):
> Generic Syntax") does not provide for specifying zone identifers on
> IPv6 addresses.  Indeed, it says "This syntax does not support IPv6
> scoped addressing zone identifiers."

This is a current topic in 6man so it may change.

   Brian

From huubatwork@gmail.com  Thu Mar 22 16:27:39 2012
Return-Path: <huubatwork@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5DA3021F84F8 for <ietf@ietfa.amsl.com>; Thu, 22 Mar 2012 16:27:39 -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 S-hBvHMXDYcN for <ietf@ietfa.amsl.com>; Thu, 22 Mar 2012 16:27:38 -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 142DC21F84F6 for <ietf@ietf.org>; Thu, 22 Mar 2012 16:27:37 -0700 (PDT)
Received: by wibhq7 with SMTP id hq7so1162909wib.13 for <ietf@ietf.org>; Thu, 22 Mar 2012 16:27:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:disposition-notification-to:date:from:reply-to :user-agent:mime-version:to:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=sI+HXhVWM+0hUV4y7ErI48QJCtYOGL3UPwg2PT3JQdc=; b=IEP6WcFD5kELYQXhy28xhLVselKQVyqNMgiiiVMjRLrwvJiYtgQ5wd5KZXYY2tSoXo 6HuLT7+gPYZSZaHUuhepG228aiGMbYCU1C8pyurT/bTCbA9Rwt00pUz39KrvcQp+HCNQ QDrBU8+fnso8T2ZfpMGgpk+OHIiDrSCpVDTo/wHOioBj58ysqrdL07/DsD25WkKnA21I I65xjBW8Bdl2uVsC8EgJKLlzJb2vubC4ZEr6LAct2AoSwDWvpmmsyM9rBwe+uMt0+mfq gg/wtN4D4yVLN4KlsBMfgIshjKXzF3ATH+VjcGJ0786spVB8zjLfTvaFcqEg97kz+oE/ ML5w==
Received: by 10.216.136.138 with SMTP id w10mr5742626wei.75.1332458856974; Thu, 22 Mar 2012 16:27:36 -0700 (PDT)
Received: from McAsterix.local ([31.216.236.133]) by mx.google.com with ESMTPS id bx13sm9046710wib.10.2012.03.22.16.27.35 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 22 Mar 2012 16:27:35 -0700 (PDT)
Message-ID: <4F6BB565.3010008@gmail.com>
Date: Fri, 23 Mar 2012 00:27:33 +0100
From: Huub van Helvoort <huubatwork@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Last Call: <draft-ietf-mpls-tp-oam-analysis-08.txt> (An Overviewof the OAM Tool Set for MPLS based Transport Networks) toInformational RFC
References: <20120309205157.8304.55419.idtracker@ietfa.amsl.com> <4F6A5ADB.2090002@gmail.com> <E4873516F3FC7547BCFE792C7D94039C0179AE70@DEMUEXC013.nsn-intra.net>
In-Reply-To: <E4873516F3FC7547BCFE792C7D94039C0179AE70@DEMUEXC013.nsn-intra.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: huubatwork@gmail.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Mar 2012 23:27:39 -0000

Hallo Nurit,

You replied:

> Thanks for your comments to IESG...

The IESG did send the message in order to make a decision, that
is why I addressed my comments to them.

> We can easily remove your name from the acknowledgement section.

Go ahead and do it.

> We put you there upon your request!

It is clear from your response that you did not understand my initial
explanation and request to be removed as editor.
When I wrote "you could mention me in the acknowledgements section" I
did *not* mean "make it more easy for the reader to mis-interpret the
acknowledgement for my role as Q10 rapporteur".
You did not even send me the text that you were going to include to
verify that this text would have taken away my concern.

> I am sorry that I am going to share on the list a private mail from you
> to me but I can see no other choice with the mail you have just sent to
> the list.

It just proves that you did not understand my initial explanation.

Regards, Huub.
==============
> As you recall you were an editor of the draft and on June 2010 (when the
> document was already an IETF document for a while), you have asked to
> remove your name from the list of editors. See
> http://www.ietf.org/mail-archive/web/mpls-tp/current/msg04118.html. the
> main reason was as you said:
>
> "It was my intention to be editor as an IETF member, however there are
> people that interpret my name/role differently. They see it as being
> editor as an ITU-T member and recently even as being editor as an ITU-T
> Q10 rapporteur.".
>
> In a private mail you sent me later (attached) you proposed to include
> you in the acknowledgement section:
>
> " Yes, remove my name as editor. As Adrian suggested, you could mention
> me in the acknowledgements section."
>
> It is a pity that you did not inform us that you changed your mind since
> then, but it can easily be fixed!
>
> Best regards,
>
> Nurit
>
> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
> ext Huub van Helvoort
> Sent: Thursday, March 22, 2012 12:49 AM
> To: ietf@ietf.org
> Subject: Re: Last Call: <draft-ietf-mpls-tp-oam-analysis-08.txt> (An
> Overviewof the OAM Tool Set for MPLS based Transport Networks)
> toInformational RFC
>
> IESG,
>
> I do *NOT* support this draft unless the following changes are made:
>
> The first paragraph of section 8 Acknowledgements has to be removed:
>
> It is an attempt to capture history, but lacks accuracy.
>
> Removal does not impact the technical information in the draft;
>
> the tools have evolved significantly from the strawman tools proposed
>
> in Stockholm; some members of the MEAD team (I am one of them) do not
>
> consider that an agreement on this proposal was reached.
>
> I also request the removal of my name from this acknowledgements section
>
> since I do not support this tool set, neither as an individual nor as
>
> ITU-T Q10 rapporteur. The latter is implied by mentioning my name in
>
> the same sentence as a WG chair and ADs.
>
> Regards, Huub.
>
> =============
>
>  > The IESG has received a request from the Multiprotocol Label Switching WG
>
>  > (mpls) to consider the following document:
>
>  > - 'An Overview of the OAM Tool Set for MPLS based Transport Networks'
>
>  > <draft-ietf-mpls-tp-oam-analysis-08.txt> as an 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 <mailto:ietf@ietf.org> mailing lists by 2012-03-23.
> Exceptionally, comments may be
>
>  > sent to iesg@ietf.org <mailto:iesg@ietf.org> instead. In either case,
> please retain the
>
>  > beginning of the Subject line to allow automated sorting.
>
>  >
>
>  > Abstract
>
>  >
>
>  > This document provides an overview of the OAM toolset for MPLS based
>
>  > Transport Networks. The toolset consists of a comprehensive set of
>
>  > fault management and performance monitoring capabilities (operating
>
>  > in the data-plane) which are appropriate for transport networks as
>
>  > required in RFC 5860 and support the network and services at
>
>  > different nested levels. This overview includes a brief recap of
>
>  > MPLS-TP OAM requirements and functions, and of generic mechanisms
>
>  > created in the MPLS data plane to allow the OAM packets run in-band
>
>  > and share their fate with data packets. The protocol definitions for
>
>  > each of the MPLS-TP OAM tools are defined in separate documents (RFCs
>
>  > or Working Group drafts) which are referenced by this document.
>  >
>  >
>  > The file can be obtained via
>  > http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-oam-analysis/
>  >
>  > IESG discussion can be tracked via
>  > http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-oam-analysis/ballot/
>  >
>  >
>  > No IPR declarations have been submitted directly on this I-D.
>  > _____________________________________________
>  > IETF-Announce mailing list
>  > IETF-Announce@ietf.org <mailto:IETF-Announce@ietf.org>
>  > https://www.ietf.org/mailman/listinfo/ietf-announce
>

From narten@us.ibm.com  Thu Mar 22 21:53:23 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 E591421E8045 for <ietf@ietfa.amsl.com>; Thu, 22 Mar 2012 21:53:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.718
X-Spam-Level: 
X-Spam-Status: No, score=-109.718 tagged_above=-999 required=5 tests=[AWL=0.881, 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 tSLr-vi+lTpz for <ietf@ietfa.amsl.com>; Thu, 22 Mar 2012 21:53:22 -0700 (PDT)
Received: from e39.co.us.ibm.com (e39.co.us.ibm.com [32.97.110.160]) by ietfa.amsl.com (Postfix) with ESMTP id 9483421E8017 for <ietf@ietf.org>; Thu, 22 Mar 2012 21:53:22 -0700 (PDT)
Received: from /spool/local by e39.co.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <ietf@ietf.org> from <narten@us.ibm.com>; Thu, 22 Mar 2012 22:53:21 -0600
Received: from d03dlp03.boulder.ibm.com (9.17.202.179) by e39.co.us.ibm.com (192.168.1.139) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Thu, 22 Mar 2012 22:53:04 -0600
Received: from d03relay01.boulder.ibm.com (d03relay01.boulder.ibm.com [9.17.195.226]) by d03dlp03.boulder.ibm.com (Postfix) with ESMTP id 76B8E19D804A for <ietf@ietf.org>; Thu, 22 Mar 2012 22:52:57 -0600 (MDT)
Received: from d03av01.boulder.ibm.com (d03av01.boulder.ibm.com [9.17.195.167]) by d03relay01.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id q2N4r4Yr201066 for <ietf@ietf.org>; Thu, 22 Mar 2012 22:53:04 -0600
Received: from d03av01.boulder.ibm.com (loopback [127.0.0.1]) by d03av01.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id q2N4r3VF028477 for <ietf@ietf.org>; Thu, 22 Mar 2012 22:53:03 -0600
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.27.192.143]) by d03av01.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id q2N4r3LL028421 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Thu, 22 Mar 2012 22:53:03 -0600
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [127.0.0.1]) by rotala.raleigh.ibm.com (8.14.4/8.12.5) with ESMTP id q2N4r23W029572 for <ietf@ietf.org>; Fri, 23 Mar 2012 00:53:02 -0400
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.4/8.14.4/Submit) id q2N4r2Dj029528 for ietf@ietf.org; Fri, 23 Mar 2012 00:53:02 -0400
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201203230453.q2N4r2Dj029528@rotala.raleigh.ibm.com>
Date: Fri, 23 Mar 2012 00:53:01 -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: 12032304-4242-0000-0000-00000121B7AC
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Mar 2012 04:53:24 -0000

Total of 113 messages in the last 7 days.
 
script run at: Fri Mar 23 00:53:01 EDT 2012
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
  5.31% |    6 |  4.91% |    54587 | daedulus@btconnect.com
  0.88% |    1 |  8.77% |    97484 | yaoguang.china@gmail.com
  2.65% |    3 |  6.17% |    68609 | malcolm.betts@zte.com.cn
  3.54% |    4 |  5.06% |    56265 | nurit.sprecher@nsn.com
  4.42% |    5 |  3.57% |    39722 | fred@cisco.com
  2.65% |    3 |  3.86% |    42878 | alessandro.dalessandro@telecomitalia.it
  3.54% |    4 |  2.82% |    31342 | brian.e.carpenter@gmail.com
  3.54% |    4 |  2.49% |    27660 | joelja@bogus.com
  3.54% |    4 |  2.46% |    27351 | john-ietf@jck.com
  3.54% |    4 |  2.33% |    25882 | dworley@avaya.com
  2.65% |    3 |  2.90% |    32259 | rcosta@ptinovacao.pt
  2.65% |    3 |  2.43% |    27017 | huubatwork@gmail.com
  2.65% |    3 |  2.11% |    23445 | sant9442@gmail.com
  2.65% |    3 |  2.01% |    22342 | julian.reschke@gmx.de
  2.65% |    3 |  1.46% |    16190 | dhc@dcrocker.net
  1.77% |    2 |  2.27% |    25231 | akatlas@gmail.com
  1.77% |    2 |  2.20% |    24425 | stbryant@cisco.com
  1.77% |    2 |  2.12% |    23590 | barryleiba@computer.org
  1.77% |    2 |  1.35% |    14971 | agmalis@gmail.com
  0.88% |    1 |  2.12% |    23530 | alexey.melnikov@isode.com
  1.77% |    2 |  1.22% |    13522 | snark17@gmail.com
  1.77% |    2 |  1.18% |    13073 | ole@cisco.com
  1.77% |    2 |  1.12% |    12461 | mcr@sandelman.ca
  1.77% |    2 |  1.07% |    11911 | kpfleming@digium.com
  1.77% |    2 |  1.02% |    11300 | dwm@xpasc.com
  0.88% |    1 |  1.64% |    18254 | ron.even.tlv@gmail.com
  0.88% |    1 |  1.42% |    15741 | eburger@standardstrack.com
  0.88% |    1 |  1.40% |    15516 | twalsh@juniper.net
  0.88% |    1 |  1.20% |    13374 | stewe@stewe.org
  0.88% |    1 |  1.06% |    11836 | edj.etc@gmail.com
  0.88% |    1 |  0.93% |    10332 | c-sai@bx.jp.nec.com
  0.88% |    1 |  0.91% |    10122 | lear@cisco.com
  0.88% |    1 |  0.90% |     9979 | eran@hueniverse.com
  0.88% |    1 |  0.88% |     9742 | narten@us.ibm.com
  0.88% |    1 |  0.85% |     9504 | dmm@1-4-5.net
  0.88% |    1 |  0.84% |     9342 | spromano@unina.it
  0.88% |    1 |  0.83% |     9193 | ben@nostrum.com
  0.88% |    1 |  0.82% |     9131 | jonne.soininen@renesasmobile.com
  0.88% |    1 |  0.81% |     8968 | richard@shockey.us
  0.88% |    1 |  0.80% |     8889 | loa@pi.nu
  0.88% |    1 |  0.77% |     8522 | framefritti@gmail.com
  0.88% |    1 |  0.76% |     8412 | wesley.george@twcable.com
  0.88% |    1 |  0.75% |     8318 | denghui02@gmail.com
  0.88% |    1 |  0.74% |     8215 | koike.yoshinori@lab.ntt.co.jp
  0.88% |    1 |  0.73% |     8081 | teemu.savolainen@nokia.com
  0.88% |    1 |  0.72% |     7998 | maarten.vissers@huawei.com
  0.88% |    1 |  0.72% |     7978 | frederick.knight@netapp.com
  0.88% |    1 |  0.70% |     7730 | ryoo@etri.re.kr
  0.88% |    1 |  0.69% |     7701 | stpeter@stpeter.im
  0.88% |    1 |  0.63% |     7021 | henk.uijterwaal@gmail.com
  0.88% |    1 |  0.61% |     6808 | housley@vigilsec.com
  0.88% |    1 |  0.61% |     6731 | erminio.ottone_69@libero.it
  0.88% |    1 |  0.60% |     6712 | simon@josefsson.org
  0.88% |    1 |  0.59% |     6577 | bob.hinden@gmail.com
  0.88% |    1 |  0.58% |     6491 | stephen.farrell@cs.tcd.ie
  0.88% |    1 |  0.58% |     6440 | mail@sabahattin-gucukoglu.com
  0.88% |    1 |  0.58% |     6437 | michael_oreirdan@cable.comcast.com
  0.88% |    1 |  0.56% |     6280 | melinda.shore@gmail.com
  0.88% |    1 |  0.55% |     6130 | andy@netconfcentral.org
  0.88% |    1 |  0.52% |     5801 | dot@dotat.at
  0.88% |    1 |  0.50% |     5555 | scott.brim@gmail.com
  0.88% |    1 |  0.48% |     5363 | hartmans-ietf@mit.edu
  0.88% |    1 |  0.47% |     5205 | johnl@iecc.com
  0.88% |    1 |  0.46% |     5104 | sm@resistor.net
  0.88% |    1 |  0.43% |     4799 | satoshi.ueno@ntt.com
  0.88% |    1 |  0.42% |     4645 | francis.dupont@fdupont.fr
--------+------+--------+----------+------------------------
100.00% |  113 |100.00% |  1112024 | Total


From nurit.sprecher@nsn.com  Fri Mar 23 00:11:29 2012
Return-Path: <nurit.sprecher@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 3EB8B21F84DC for <ietf@ietfa.amsl.com>; Fri, 23 Mar 2012 00:11:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.495
X-Spam-Level: 
X-Spam-Status: No, score=-6.495 tagged_above=-999 required=5 tests=[AWL=0.104,  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 DmtlGSSSh6v9 for <ietf@ietfa.amsl.com>; Fri, 23 Mar 2012 00:11:28 -0700 (PDT)
Received: from demumfd001.nsn-inter.net (demumfd001.nsn-inter.net [93.183.12.32]) by ietfa.amsl.com (Postfix) with ESMTP id AB80F21F84DF for <ietf@ietf.org>; Fri, 23 Mar 2012 00:11:26 -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 q2N7BLE5009404 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 23 Mar 2012 08:11:21 +0100
Received: from demuexc022.nsn-intra.net (demuexc022.nsn-intra.net [10.150.128.35]) by demuprx016.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id q2N7BL8b014584; Fri, 23 Mar 2012 08:11:21 +0100
Received: from DEMUEXC013.nsn-intra.net ([10.150.128.24]) by demuexc022.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.4675);  Fri, 23 Mar 2012 08:11:13 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Last Call: <draft-ietf-mpls-tp-oam-analysis-08.txt> (An Overviewofthe OAM Tool Set for MPLS based Transport Networks) toInformational RFC
Date: Fri, 23 Mar 2012 08:11:11 +0100
Message-ID: <E4873516F3FC7547BCFE792C7D94039C0179B254@DEMUEXC013.nsn-intra.net>
In-Reply-To: <4F6BB565.3010008@gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Last Call: <draft-ietf-mpls-tp-oam-analysis-08.txt> (An Overviewofthe OAM Tool Set for MPLS based Transport Networks) toInformational RFC
Thread-Index: Ac0Ig2XqQpTxz28jTWydM6ljxtYlKgAP3izA
References: <20120309205157.8304.55419.idtracker@ietfa.amsl.com><4F6A5ADB.2090002@gmail.com><E4873516F3FC7547BCFE792C7D94039C0179AE70@DEMUEXC013.nsn-intra.net> <4F6BB565.3010008@gmail.com>
From: "Sprecher, Nurit (NSN - IL/Hod HaSharon)" <nurit.sprecher@nsn.com>
To: <huubatwork@gmail.com>, <ietf@ietf.org>
X-OriginalArrivalTime: 23 Mar 2012 07:11:13.0138 (UTC) FILETIME=[21728D20:01CD08C4]
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: 6323
X-purgate-ID: 151667::1332486681-00003570-CBAE5D91/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: Fri, 23 Mar 2012 07:11:29 -0000

Huub hi,
The document went through two WG last calls...it is a pity you did not
use the opportunity to provide your useful comment then.=20
I am surprised that it took you almost two years and seven revisions of
the document before you actually realized you are not happy with the way
we acknowledged you upon your own request. Surely for a draft where the
removal of your name from the list of editors was driven by your
concerns that people might misread your involvement/position. I would
think that in two years you would get around to checking for you that
the new acknowledgement is satisfactory.=20
Best regards,
Nurit


-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
ext Huub van Helvoort
Sent: Friday, March 23, 2012 1:28 AM
To: ietf@ietf.org
Subject: Re: Last Call: <draft-ietf-mpls-tp-oam-analysis-08.txt> (An
Overviewofthe OAM Tool Set for MPLS based Transport Networks)
toInformational RFC

Hallo Nurit,

You replied:

> Thanks for your comments to IESG...

The IESG did send the message in order to make a decision, that
is why I addressed my comments to them.

> We can easily remove your name from the acknowledgement section.

Go ahead and do it.

> We put you there upon your request!

It is clear from your response that you did not understand my initial
explanation and request to be removed as editor.
When I wrote "you could mention me in the acknowledgements section" I
did *not* mean "make it more easy for the reader to mis-interpret the
acknowledgement for my role as Q10 rapporteur".
You did not even send me the text that you were going to include to
verify that this text would have taken away my concern.

> I am sorry that I am going to share on the list a private mail from
you
> to me but I can see no other choice with the mail you have just sent
to
> the list.

It just proves that you did not understand my initial explanation.

Regards, Huub.
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> As you recall you were an editor of the draft and on June 2010 (when
the
> document was already an IETF document for a while), you have asked to
> remove your name from the list of editors. See
> http://www.ietf.org/mail-archive/web/mpls-tp/current/msg04118.html.
the
> main reason was as you said:
>
> "It was my intention to be editor as an IETF member, however there are
> people that interpret my name/role differently. They see it as being
> editor as an ITU-T member and recently even as being editor as an
ITU-T
> Q10 rapporteur.".
>
> In a private mail you sent me later (attached) you proposed to include
> you in the acknowledgement section:
>
> " Yes, remove my name as editor. As Adrian suggested, you could
mention
> me in the acknowledgements section."
>
> It is a pity that you did not inform us that you changed your mind
since
> then, but it can easily be fixed!
>
> Best regards,
>
> Nurit
>
> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf
Of
> ext Huub van Helvoort
> Sent: Thursday, March 22, 2012 12:49 AM
> To: ietf@ietf.org
> Subject: Re: Last Call: <draft-ietf-mpls-tp-oam-analysis-08.txt> (An
> Overviewof the OAM Tool Set for MPLS based Transport Networks)
> toInformational RFC
>
> IESG,
>
> I do *NOT* support this draft unless the following changes are made:
>
> The first paragraph of section 8 Acknowledgements has to be removed:
>
> It is an attempt to capture history, but lacks accuracy.
>
> Removal does not impact the technical information in the draft;
>
> the tools have evolved significantly from the strawman tools proposed
>
> in Stockholm; some members of the MEAD team (I am one of them) do not
>
> consider that an agreement on this proposal was reached.
>
> I also request the removal of my name from this acknowledgements
section
>
> since I do not support this tool set, neither as an individual nor as
>
> ITU-T Q10 rapporteur. The latter is implied by mentioning my name in
>
> the same sentence as a WG chair and ADs.
>
> Regards, Huub.
>
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>
>  > The IESG has received a request from the Multiprotocol Label
Switching WG
>
>  > (mpls) to consider the following document:
>
>  > - 'An Overview of the OAM Tool Set for MPLS based Transport
Networks'
>
>  > <draft-ietf-mpls-tp-oam-analysis-08.txt> as an 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 <mailto:ietf@ietf.org> mailing lists by 2012-03-23.
> Exceptionally, comments may be
>
>  > sent to iesg@ietf.org <mailto:iesg@ietf.org> instead. In either
case,
> please retain the
>
>  > beginning of the Subject line to allow automated sorting.
>
>  >
>
>  > Abstract
>
>  >
>
>  > This document provides an overview of the OAM toolset for MPLS
based
>
>  > Transport Networks. The toolset consists of a comprehensive set of
>
>  > fault management and performance monitoring capabilities (operating
>
>  > in the data-plane) which are appropriate for transport networks as
>
>  > required in RFC 5860 and support the network and services at
>
>  > different nested levels. This overview includes a brief recap of
>
>  > MPLS-TP OAM requirements and functions, and of generic mechanisms
>
>  > created in the MPLS data plane to allow the OAM packets run in-band
>
>  > and share their fate with data packets. The protocol definitions
for
>
>  > each of the MPLS-TP OAM tools are defined in separate documents
(RFCs
>
>  > or Working Group drafts) which are referenced by this document.
>  >
>  >
>  > The file can be obtained via
>  > http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-oam-analysis/
>  >
>  > IESG discussion can be tracked via
>  >
http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-oam-analysis/ballot/
>  >
>  >
>  > No IPR declarations have been submitted directly on this I-D.
>  > _____________________________________________
>  > IETF-Announce mailing list
>  > IETF-Announce@ietf.org <mailto:IETF-Announce@ietf.org>
>  > https://www.ietf.org/mailman/listinfo/ietf-announce
>

From loa@pi.nu  Fri Mar 23 02:44:55 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 15D2621F849B for <ietf@ietfa.amsl.com>; Fri, 23 Mar 2012 02:44:55 -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 zcvdgnYyIlMs for <ietf@ietfa.amsl.com>; Fri, 23 Mar 2012 02:44:52 -0700 (PDT)
Received: from mail.pi.nu (mail.pi.nu [194.71.127.148]) by ietfa.amsl.com (Postfix) with ESMTP id 0E6A421F84BF for <ietf@ietf.org>; Fri, 23 Mar 2012 02:44:50 -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 882B32A8002; Fri, 23 Mar 2012 10:44:48 +0100 (CET)
Message-ID: <4F6C460F.4080007@pi.nu>
Date: Fri, 23 Mar 2012 10:44:47 +0100
From: Loa Andersson <loa@pi.nu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: Malcolm.BETTS@zte.com.cn
Subject: Re: [PWE3] FW: Last Call:	<draft-betts-itu-oam-ach-code-point-03.txt>(Allocation of	an Associated Channel Code Point for Use byITU-T Ethernet	based OAM)	to Informational RFC
References: <20120222151252.32262.82157.idtracker@ietfa.amsl.com>	<039f01ccf174$fe79d780$fb6d8680$@olddog.co.uk> <44F4E579A764584EA9BDFD07D0CA0813075C936F@tlvmail1>	<4F4B7EA2.7070305@cisco.com> <4F4B8A75.6000207@pi.nu> <4F5DB46F.10009@pi.nu> <OFE57A943C.CA873F89-ON852579C8.006D6B01-852579C8.0070E507@zte.com.cn>
In-Reply-To: <OFE57A943C.CA873F89-ON852579C8.006D6B01-852579C8.0070E507@zte.com.cn>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Mar 2012 09:44:55 -0000

Malcolm,

good that we are making some progress!

On the experimental code point
------------------------------

I doesn't seem appropriate to call out the fact that some commercial
products has been using an experimental code point in production
setting!

On the remain (key) disagreements
---------------------------------

I will let other people comment for now.


/Loa

On 2012-03-21 21:33, Malcolm.BETTS@zte.com.cn wrote:
> Loa,
>
> Thank you for your comments and suggestions, please see in line below.
>
> Regards,
>
> Malcolm
>
>
> ietf-bounces@ietf.org wrote on 12/03/2012 04:31:43 AM:
>
>  > Loa Andersson <loa@pi.nu>
>  > Sent by: ietf-bounces@ietf.org
>  >
>  > 12/03/2012 04:31 AM
>  >
>  > To
>  >
>  > ietf@ietf.org
>  >
>  > cc
>  >
>  > Subject
>  >
>  > Re: [PWE3] FW: Last Call: <draft-betts-itu-oam-ach-code-
>  > point-03.txt>(Allocation of an Associated Channel Code Point for Use
>  > byITU-T Ethernet based OAM) to Informational RFC
>  >
>  > All,
>  >
>  > I've been asked to clarify thee comments in this mail, I done
>  > so by proposing new text to draft-betts-.
>  >
>  > I hope this helps.
>  >
>  >
>  > Title
>  > =====
>  >
>  > Comment: We want to assign a Associated Channel Type. The registry
>  > that it will be assigned from is "Pseudowire Associated Channel
>  > Types"; however RFC 5586, makes the Channel Types generic and I
>  > think the title should be changed as follows:
>  >
>  > OLD:
>  > Allocation of an Associated Channel Code Point for Use by ITU-T
>  > Ethernet based OAM
>  >
>  > NEW:
>  > Allocation of an Generic Associated Channel Type for ITU-T
>  > MPLS-TP OAM
>  >
>  > Note: Neither MPLS-TP or OAM are in the RFC Editors list of wellknown
>  > acronyms, therfore the title probably should be:
>  >
>  > NEW:
>  > Allocation of an Generic Associated Channel Type for ITU-T
>  > MPLS Transport Profile Operation, Maintenance and Administration.
>  >
>
> MB: No objection to this change
>
>  >
>  > Introduction - first paragraph
>  > ==============================
>  >
>  > In the first paragraph of the introduction, there seems to be an
>  > oddity in the description of the role of the ietf-tp-oam-analysis
>  > document. Instead of:
>  >
>  > OLD
>  > "tools defined by the IETF [I-D.ietf-mpls-tp-oam-analysis], that
>  > are intended to meet the OAM functional requirements defined in
>  > [RFC5860]."
>  >
>  > NEW:
>  > "tools described by the IETF [I-D.ietf-mpls-tp-oam-analysis], which
>  > are used to meet the OAM functional requirements defined
>  > in [RFC5860]."
>
> MB: No objection to this change
>
>  >
>  > Intrduction - second paragraph
>  > ==============================
>  >
>  > The next paragraph in describing G.8113.1, stumbles over the current
>  > vs anticipated future state of G.8113.1 and its relationship to
>  > its antecedents. I'm a bit un-certain about the correct terminology,
>  > but I think the following change would improve the document.
>  >
>  > OLD:
>  >
>  > The ITU-T has documented, in draft new Recommendation [G.8113.1], the
>  > use of Ethernet based OAM mechanisms, originally defined in [Y.1731],
>  > carried in the MPLS Generic Associated Channel (G-ACh). This approach
>  > requires the allocation of an ACH Type from the registry of ACH types
>  > maintained by IANA in order that the messages that will be described
>  > in [G.8113.1] can be identified by an implementation.
>  >
>  > NEW:
>  >
>  > "The ITU-T has Draft Recommendation [G.8113.1] documented MPLS OAM
>  > which as of this writing is undergoing the ITU-T Traditional
>  > Approval Process (TAP). This Recommendation builds upon Ethernet
>  > OAM as documented in [Y.1731]. The messages in [G.8113.1] are defined
>  > to be carried in a new Associated Channel Type in the MPLS Generaic
>  > Associated Channel (G-Ach). In order to carry these messages in an
>  > interoperable fashion, an Associated Channel Type from the IANA
>  > maintained registry "Pseudowire Associated Channel Types is to be
>  > used."
>
> MB: Since the draft will not be published as an RFC until after G.8113.1
> is approved we can directly reference the approved Recommendation and I
> suggest that we modify paragraph to:
>
>
> ITU-T Recommendation [G.8113.1] documents MPLS OAM. This Recommendation
> builds upon Ethernet OAM as documented in [Y.1731]. The messages in
> [G.8113.1] are defined to be carried in a new Associated Channel Type in
> the MPLS Generaic Associated Channel (G-Ach). In order to carry these
> messages in an interoperable fashion, an Associated Channel Type from
> the IANA maintained registry "Pseudowire Associated Channel Types is to
> be used."
>
>
>  >
>  > Note there are confusion around some of the Associated Channel
>  > acronyms that are refledted in this document.
>  >
>  > ACh is Associated Channel
>  > ACH is Associated Chamnnel Header
>  > G-ACh is Generic Associated Channel
>  >
>  > "ACH Type" is not used anywhere in IETF documents; we talk about
>  > Associated Channel Type or Generic Associated Channel Type
>  > (G-ACh Type).
>
> MB: Thank you, I will fix this.
>
>  >
>  > Introduction - third paragraph
>  > ==============================
>  >
>  > In the third paragraph, there seems to be an unnecessary reference
>  > to experimental types. When asking for a code point for a standard,
>  > it is not helped to bring up experimental code space. Can we remove
>  > the text reading:
>  >
>  > OLD:
>  > "without continuing to resorting to the use of an experimental
>  > ACH Type,"
>  >
>  > NEW
>  > -
>
> MB: I do not agree with the deletion of this text, these existing
> deployments, and the desire to migrate to an allocated code point, are
> part of the rational for requesting the code point.
>
>  >
>  >
>  > Section 2 - first paragraph
>  > ===========================
>  >
>  >
>  >
>  > In section 2, the first sentence refers to Ethernet based OAM
>  > messages. As far as I know, the messages in G.8113.1 are either
>  > MPLS-TP OAM messages, or they are simply the OAM messages defined
>  > in G.8113.1. The simplest path to clarity would seem to be to
>  > replace "Ethernet based OAM messages" in that sentence with
>  > "messages".
>  >
>  > The second sentence of that paragraph does not seem to say anything
>  > we need to say. Can we remove it?
>  >
>  > OLD:
>  >
>  > The code point allocated by this document is intended to be used only
>  > for Ethernet based OAM messages, defined in the ITU-T Recommendation
>  > [G.8113.1], carried in the G-ACh . These Ethernet based OAM messages
>  > and procedures, address the OAM functional requirements defined in
>  > [RFC5860]. Other message types should not be carried behind this code
>  > point.
>  >
>  > NEW:
>  >
>  > The code point allocated by this document is intended to be used
>  > only for OAM messages, defined in the ITU-T Recommendation
>  > [G.8113.1], carried in the G-ACh . Other message types should not
>  > be carried behind this Associated Channel Type.
>
>
> MB: I do not agree with this proposed change. Other comments request
> that the restriction on the applicability of the code point is
> strengthened so I propose the following:
>
> The code point allocated by this document should only be used for OAM
> messages, defined in the ITU-T Recommendation [G.8113.1], carried in the
> G-ACh. The messages and procedures carried behind this code point, are
> restricted to only those that the address the OAM functional
> requirements defined in [RFC5860]. Other message types should not be
> carried behind this code point.
>
>
>  >
>  > Section 2 - second paragraph
>  > ============================
>  >
>  > A matter of some clarity, can we change this paragrap like this:
>  >
>  > OLD:
>  > This code point may be used on any transport construct that uses
>  > the G-ACh, e.g., MPLS-TP Sections, MPLS-TP LSPs or PWs.
>  >
>  > NEW:
>  >
>  > The Generic Associated Channel Type assigned by this
>  > document may be used on any transport construct that uses the
>  > G-ACh, e.g., MPLS-TP Sections, MPLS-TP LSPs or PWs as specified
>  > by G.8113.1.
>
> MB: No objection to this change.
>
>  >
>  >
>  > Section 2 - third paragraph
>  > ===========================
>  >
>  > With regard to revisions, which is what I think the third paragraph
>  > is about, I am not clear what you are trying to say. A code point
>  > allocation must point to a stable referent. If the desired referent
>  > changes, then process needs to be followed to make sure that the IANA
>  > is updated in accordance with IETF procedures. Hence, I am left to
>  > the conclusion that the third paragraph is actually asking for
>  > something we can not do. Can we remove that?
>  >
>  > OLD:
>  > All ITU-T Recommendations are subject to revisions. Therefore, the
>  > code point allocated by this document may be used for future versions
>  > of [G.8113.1].
>  >
>  > NEW:
>  > -
>  >
>  >
>
> MB: I do not agree with the removal of this text:
>
> The intention of this statement is to bring to the attention of the IETF
> the normal practice in the ITU of developing amendments to
> Recommendations to fully meet the functional requirements (e.g. adding
> pro-active loss measurement). Normally any reference to ITU-T Rec
> G.8113.1 will automatically be directed to the current version
> (including any amendments).
>
> Only those interfaces that support G.8113.1 OAM will act on these OAM
> messages, any interface that does not support this G-ACh type will
> discard these OAM messages as defined in RFC5586.
>
> Restricting the application of the code point to a specific version of
> Recommendation G.8113.1 would require the ITU to deviate from its normal
> process for enhancing Recommendations and would put the IETF back into
> the discussion for approval.
>
>
>
>  >---------------snip
>
>
>  >
>  > 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
>  > _______________________________________________
>  > Ietf mailing list
>  > Ietf@ietf.org
>  > https://www.ietf.org/mailman/listinfo/ietf
>  >

-- 


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 daedulus@btconnect.com  Fri Mar 23 03:37:25 2012
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ED2AD21F855F; Fri, 23 Mar 2012 03:37:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.775
X-Spam-Level: 
X-Spam-Status: No, score=-0.775 tagged_above=-999 required=5 tests=[AWL=0.335,  BAYES_05=-1.11]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id n7pk6wzGMMS1; Fri, 23 Mar 2012 03:37:25 -0700 (PDT)
Received: from mail.btconnect.com (c2beaomr09.btconnect.com [213.123.26.187]) by ietfa.amsl.com (Postfix) with ESMTP id D83E221F855B; Fri, 23 Mar 2012 03:37:24 -0700 (PDT)
Received: from host86-162-135-195.range86-162.btcentralplus.com (HELO pc6) ([86.162.135.195]) by c2beaomr09.btconnect.com with SMTP id GUH41682; Fri, 23 Mar 2012 10:37:21 +0000 (GMT)
Message-ID: <004601cd08d8$66d362e0$4001a8c0@gateway.2wire.net>
From: "t.petch" <daedulus@btconnect.com>
To: "Barry Leiba" <barryleiba@computer.org>
References: <CALaySJJcP8ijZK6PyX8+3zpDSL3q47woWX0e__mcDtA=nD438w@mail.gmail.com><CB8FCF89.84B69%stewe@stewe.org><CALaySJJXRnRPGk6Fc_q9V3x4h=4Vzm83Nj1bLqk-qfKN=_4w8A@mail.gmail.com><4f6a2c0a.e64eb40a.3ae6.74cb@mx.google.com> <CALaySJJa0TL4uF5DXm_psQ-QwrrCCRgDbDOt7fkO4k8LpcsCiw@mail.gmail.com>
Subject: Re: IPR requirements in document write-up
Date: Fri, 23 Mar 2012 10:36:14 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Mirapoint-IP-Reputation: reputation=Fair-1, source=Queried, refid=tid=0001.0A0B0301.4F6C5260.012F, actions=tag
X-Junkmail-Premium-Raw: score=8/50, refid=2.7.2:2012.3.23.95415:17:8.317, ip=86.162.135.195, rules=__HAS_MSGID, __OUTLOOK_MSGID_1, __SANE_MSGID, __TO_MALFORMED_2, __MULTIPLE_RCPTS_CC_X2, __BOUNCE_CHALLENGE_SUBJ, __BOUNCE_NDR_SUBJ_EXEMPT, __MIME_VERSION, __CT, CT_TP_8859_1, __CT_TEXT_PLAIN, __CTE, __HAS_X_PRIORITY, __HAS_MSMAIL_PRI, __HAS_X_MAILER, USER_AGENT_OE, __OUTLOOK_MUA_1, __USER_AGENT_MS_GENERIC, __ANY_URI, __FRAUD_BODY_WEBMAIL, __URI_NO_WWW, __URI_NO_PATH, __INT_PROD_COMP, BODYTEXTP_SIZE_3000_LESS, BODY_SIZE_2000_2999, __MIME_TEXT_ONLY, RDNS_GENERIC_POOLED, HTML_00_01, HTML_00_10, BODY_SIZE_5000_LESS, RDNS_SUSP_GENERIC, __OUTLOOK_MUA, MULTIPLE_RCPTS, RDNS_SUSP, __FRAUD_WEBMAIL, BODY_SIZE_7000_LESS
X-Junkmail-Status: score=10/50, host=c2beaomr09.btconnect.com
X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A0B020B.4F6C5261.025A,ss=1,re=0.000,fgs=0, ip=0.0.0.0, so=2011-07-25 19:15:43, dmn=2011-05-27 18:58:46, mode=multiengine
X-Junkmail-IWF: false
Cc: IETF <ietf@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, 23 Mar 2012 10:37:26 -0000

----- Original Message -----
From: "Barry Leiba" <barryleiba@computer.org>
To: "Roni Even" <ron.even.tlv@gmail.com>
Cc: "IETF" <ietf@ietf.org>; <ipr@ietf.org>; <iesg@ietf.org>
Sent: Wednesday, March 21, 2012 8:50 PM

> My reading of question 7 is
> that the document shepherd have to ask the authors to confirm the IPR
> status to their knowledge which is different than just reporting what was
> discussed in the WG and which IP statements were submitted. Did I
> mis-understand question 7.

<snip>

As I said in my first note, you're welcome to ask the question in any
manner you like, as long as you can comfortably complete the PROTO
writeup.

The way I've handled it since the change was to ask openly on the WG
mailing list.  I've asked the editors *and* the participants, but only
expected explicit replies (off list) from the editors.  This way, all
participants were reminded to let the working group know about IPR
they're aware of ["reasonably and personally known to the participant"
is the specific text from BCP 79, in case you want to use that].

<tp>
Barry

What might have improved this change to the process, it would have for me, would
have been to announce that the process has changed, so that it did not come as a
surprise.

I saw these open requests on more than one list, guessed that this was a
WG-Chair or IESG sponsored initiative, thought back to a recent unfortunate
situation that I presumed to be the cause of this process change, and then
wondered what should happen for non-WG submissions and what was happening on the
WG lists where I saw no public requests.

Life would have been simpler if this process change had been announced, ideally
on the IETF list as well as on individual WG lists - seeing it on some and not
on other WG lists makes one wonder what is going on, time that could be better
spent reading the I-Ds in question:-).

I was unaware of the link to the write-ups from the IESG page and had not a clue
what the status of the documents is - it could be worse, it could have been
ION:-(

Tom Petch
</tp>
How you, as a chair, do it, is up to you.  And I suggest that "Yes,"
is a reasonable answer to question 7, and question 8 is the one that
wants more words.

Barry



From daedulus@btconnect.com  Fri Mar 23 03:51:57 2012
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2ADFA21F8532 for <ietf@ietfa.amsl.com>; Fri, 23 Mar 2012 03:51:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.631
X-Spam-Level: 
X-Spam-Status: No, score=-1.631 tagged_above=-999 required=5 tests=[AWL=0.968,  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 huyVLS6u4Ucg for <ietf@ietfa.amsl.com>; Fri, 23 Mar 2012 03:51:53 -0700 (PDT)
Received: from mail.btconnect.com (c2beaomr10.btconnect.com [213.123.26.188]) by ietfa.amsl.com (Postfix) with ESMTP id 909E521F852D for <ietf@ietf.org>; Fri, 23 Mar 2012 03:51:50 -0700 (PDT)
Received: from host86-162-135-195.range86-162.btcentralplus.com (HELO pc6) ([86.162.135.195]) by c2beaomr10.btconnect.com with SMTP id GSV55409; Fri, 23 Mar 2012 10:51:43 +0000 (GMT)
Message-ID: <00b801cd08da$6885bbe0$4001a8c0@gateway.2wire.net>
From: "t.petch" <daedulus@btconnect.com>
To: "Loa Andersson" <loa@pi.nu>, <Malcolm.BETTS@zte.com.cn>
References: <20120222151252.32262.82157.idtracker@ietfa.amsl.com>	<039f01ccf174$fe79d780$fb6d8680$@olddog.co.uk><44F4E579A764584EA9BDFD07D0CA0813075C936F@tlvmail1>	<4F4B7EA2.7070305@cisco.com><4F4B8A75.6000207@pi.nu> <4F5DB46F.10009@pi.nu><OFE57A943C.CA873F89-ON852579C8.006D6B01-852579C8.0070E507@zte.com.cn> <4F6C460F.4080007@pi.nu>
Subject: Re: [PWE3] FW: LastCall:	<draft-betts-itu-oam-ach-code-point-03.txt>(Allocationof	an Associated Channel Code Point for Use byITU-T Ethernet	basedOAM)	to Informational RFC
Date: Fri, 23 Mar 2012 10:50:36 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Mirapoint-IP-Reputation: reputation=Fair-1, source=Queried, refid=tid=0001.0A0B0302.4F6C55BE.0127, actions=tag
X-Junkmail-Premium-Raw: score=9/50, refid=2.7.2:2012.3.23.95415:17:9.975, ip=86.162.135.195, rules=__HAS_MSGID, __OUTLOOK_MSGID_1, __SANE_MSGID, __TO_MALFORMED_2, __BOUNCE_CHALLENGE_SUBJ, __BOUNCE_NDR_SUBJ_EXEMPT, __SUBJ_ALPHA_END, __MIME_VERSION, __CT, CT_TP_8859_1, __CT_TEXT_PLAIN, __CTE, __HAS_X_PRIORITY, __HAS_MSMAIL_PRI, __HAS_X_MAILER, USER_AGENT_OE, __OUTLOOK_MUA_1, __USER_AGENT_MS_GENERIC, __ANY_URI, CN_TLD, __URI_NO_WWW, __URI_NO_PATH, __CP_NOT_1, BODY_SIZE_10000_PLUS, __MIME_TEXT_ONLY, RDNS_GENERIC_POOLED, HTML_00_01, HTML_00_10, RDNS_SUSP_GENERIC, __OUTLOOK_MUA, RDNS_SUSP
X-Junkmail-Status: score=10/50, host=c2beaomr10.btconnect.com
X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A0B0201.4F6C55BF.0135,ss=1,re=0.000,fgs=0, ip=0.0.0.0, so=2011-07-25 19:15:43, dmn=2011-05-27 18:58:46, mode=multiengine
X-Junkmail-IWF: false
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, 23 Mar 2012 10:51:57 -0000

Loa

The one point that jumps out at me is the proposed text
"Other message types should not be carried behind this code point."
or should that be
"Other message types SHOULD NOT be carried behind this code point."
which, in IETF-Land, is a bit different.

I prefer the latter.

Tom Petch


----- Original Message -----
From: "Loa Andersson" <loa@pi.nu>
To: <Malcolm.BETTS@zte.com.cn>
Cc: <ietf@ietf.org>
Sent: Friday, March 23, 2012 10:44 AM
Subject: Re: [PWE3] FW: LastCall:
<draft-betts-itu-oam-ach-code-point-03.txt>(Allocationof an Associated Channel
Code Point for Use byITU-T Ethernet basedOAM) to Informational RFC


> Malcolm,
>
> good that we are making some progress!
>
> On the experimental code point
> ------------------------------
>
> I doesn't seem appropriate to call out the fact that some commercial
> products has been using an experimental code point in production
> setting!
>
> On the remain (key) disagreements
> ---------------------------------
>
> I will let other people comment for now.
>
>
> /Loa
>
> On 2012-03-21 21:33, Malcolm.BETTS@zte.com.cn wrote:
> > Loa,
> >
> > Thank you for your comments and suggestions, please see in line below.
> >
> > Regards,
> >
> > Malcolm
> >
> >
> > ietf-bounces@ietf.org wrote on 12/03/2012 04:31:43 AM:
> >
> >  > Loa Andersson <loa@pi.nu>
> >  > Sent by: ietf-bounces@ietf.org
> >  >
> >  > 12/03/2012 04:31 AM
> >  >
> >  > To
> >  >
> >  > ietf@ietf.org
> >  >
> >  > cc
> >  >
> >  > Subject
> >  >
> >  > Re: [PWE3] FW: Last Call: <draft-betts-itu-oam-ach-code-
> >  > point-03.txt>(Allocation of an Associated Channel Code Point for Use
> >  > byITU-T Ethernet based OAM) to Informational RFC
> >  >
> >  > All,
> >  >
> >  > I've been asked to clarify thee comments in this mail, I done
> >  > so by proposing new text to draft-betts-.
> >  >
> >  > I hope this helps.
> >  >
> >  >
> >  > Title
> >  > =====
> >  >
> >  > Comment: We want to assign a Associated Channel Type. The registry
> >  > that it will be assigned from is "Pseudowire Associated Channel
> >  > Types"; however RFC 5586, makes the Channel Types generic and I
> >  > think the title should be changed as follows:
> >  >
> >  > OLD:
> >  > Allocation of an Associated Channel Code Point for Use by ITU-T
> >  > Ethernet based OAM
> >  >
> >  > NEW:
> >  > Allocation of an Generic Associated Channel Type for ITU-T
> >  > MPLS-TP OAM
> >  >
> >  > Note: Neither MPLS-TP or OAM are in the RFC Editors list of wellknown
> >  > acronyms, therfore the title probably should be:
> >  >
> >  > NEW:
> >  > Allocation of an Generic Associated Channel Type for ITU-T
> >  > MPLS Transport Profile Operation, Maintenance and Administration.
> >  >
> >
> > MB: No objection to this change
> >
> >  >
> >  > Introduction - first paragraph
> >  > ==============================
> >  >
> >  > In the first paragraph of the introduction, there seems to be an
> >  > oddity in the description of the role of the ietf-tp-oam-analysis
> >  > document. Instead of:
> >  >
> >  > OLD
> >  > "tools defined by the IETF [I-D.ietf-mpls-tp-oam-analysis], that
> >  > are intended to meet the OAM functional requirements defined in
> >  > [RFC5860]."
> >  >
> >  > NEW:
> >  > "tools described by the IETF [I-D.ietf-mpls-tp-oam-analysis], which
> >  > are used to meet the OAM functional requirements defined
> >  > in [RFC5860]."
> >
> > MB: No objection to this change
> >
> >  >
> >  > Intrduction - second paragraph
> >  > ==============================
> >  >
> >  > The next paragraph in describing G.8113.1, stumbles over the current
> >  > vs anticipated future state of G.8113.1 and its relationship to
> >  > its antecedents. I'm a bit un-certain about the correct terminology,
> >  > but I think the following change would improve the document.
> >  >
> >  > OLD:
> >  >
> >  > The ITU-T has documented, in draft new Recommendation [G.8113.1], the
> >  > use of Ethernet based OAM mechanisms, originally defined in [Y.1731],
> >  > carried in the MPLS Generic Associated Channel (G-ACh). This approach
> >  > requires the allocation of an ACH Type from the registry of ACH types
> >  > maintained by IANA in order that the messages that will be described
> >  > in [G.8113.1] can be identified by an implementation.
> >  >
> >  > NEW:
> >  >
> >  > "The ITU-T has Draft Recommendation [G.8113.1] documented MPLS OAM
> >  > which as of this writing is undergoing the ITU-T Traditional
> >  > Approval Process (TAP). This Recommendation builds upon Ethernet
> >  > OAM as documented in [Y.1731]. The messages in [G.8113.1] are defined
> >  > to be carried in a new Associated Channel Type in the MPLS Generaic
> >  > Associated Channel (G-Ach). In order to carry these messages in an
> >  > interoperable fashion, an Associated Channel Type from the IANA
> >  > maintained registry "Pseudowire Associated Channel Types is to be
> >  > used."
> >
> > MB: Since the draft will not be published as an RFC until after G.8113.1
> > is approved we can directly reference the approved Recommendation and I
> > suggest that we modify paragraph to:
> >
> >
> > ITU-T Recommendation [G.8113.1] documents MPLS OAM. This Recommendation
> > builds upon Ethernet OAM as documented in [Y.1731]. The messages in
> > [G.8113.1] are defined to be carried in a new Associated Channel Type in
> > the MPLS Generaic Associated Channel (G-Ach). In order to carry these
> > messages in an interoperable fashion, an Associated Channel Type from
> > the IANA maintained registry "Pseudowire Associated Channel Types is to
> > be used."
> >
> >
> >  >
> >  > Note there are confusion around some of the Associated Channel
> >  > acronyms that are refledted in this document.
> >  >
> >  > ACh is Associated Channel
> >  > ACH is Associated Chamnnel Header
> >  > G-ACh is Generic Associated Channel
> >  >
> >  > "ACH Type" is not used anywhere in IETF documents; we talk about
> >  > Associated Channel Type or Generic Associated Channel Type
> >  > (G-ACh Type).
> >
> > MB: Thank you, I will fix this.
> >
> >  >
> >  > Introduction - third paragraph
> >  > ==============================
> >  >
> >  > In the third paragraph, there seems to be an unnecessary reference
> >  > to experimental types. When asking for a code point for a standard,
> >  > it is not helped to bring up experimental code space. Can we remove
> >  > the text reading:
> >  >
> >  > OLD:
> >  > "without continuing to resorting to the use of an experimental
> >  > ACH Type,"
> >  >
> >  > NEW
> >  > -
> >
> > MB: I do not agree with the deletion of this text, these existing
> > deployments, and the desire to migrate to an allocated code point, are
> > part of the rational for requesting the code point.
> >
> >  >
> >  >
> >  > Section 2 - first paragraph
> >  > ===========================
> >  >
> >  >
> >  >
> >  > In section 2, the first sentence refers to Ethernet based OAM
> >  > messages. As far as I know, the messages in G.8113.1 are either
> >  > MPLS-TP OAM messages, or they are simply the OAM messages defined
> >  > in G.8113.1. The simplest path to clarity would seem to be to
> >  > replace "Ethernet based OAM messages" in that sentence with
> >  > "messages".
> >  >
> >  > The second sentence of that paragraph does not seem to say anything
> >  > we need to say. Can we remove it?
> >  >
> >  > OLD:
> >  >
> >  > The code point allocated by this document is intended to be used only
> >  > for Ethernet based OAM messages, defined in the ITU-T Recommendation
> >  > [G.8113.1], carried in the G-ACh . These Ethernet based OAM messages
> >  > and procedures, address the OAM functional requirements defined in
> >  > [RFC5860]. Other message types should not be carried behind this code
> >  > point.
> >  >
> >  > NEW:
> >  >
> >  > The code point allocated by this document is intended to be used
> >  > only for OAM messages, defined in the ITU-T Recommendation
> >  > [G.8113.1], carried in the G-ACh . Other message types should not
> >  > be carried behind this Associated Channel Type.
> >
> >
> > MB: I do not agree with this proposed change. Other comments request
> > that the restriction on the applicability of the code point is
> > strengthened so I propose the following:
> >
> > The code point allocated by this document should only be used for OAM
> > messages, defined in the ITU-T Recommendation [G.8113.1], carried in the
> > G-ACh. The messages and procedures carried behind this code point, are
> > restricted to only those that the address the OAM functional
> > requirements defined in [RFC5860]. Other message types should not be
> > carried behind this code point.
> >
> >
> >  >
> >  > Section 2 - second paragraph
> >  > ============================
> >  >
> >  > A matter of some clarity, can we change this paragrap like this:
> >  >
> >  > OLD:
> >  > This code point may be used on any transport construct that uses
> >  > the G-ACh, e.g., MPLS-TP Sections, MPLS-TP LSPs or PWs.
> >  >
> >  > NEW:
> >  >
> >  > The Generic Associated Channel Type assigned by this
> >  > document may be used on any transport construct that uses the
> >  > G-ACh, e.g., MPLS-TP Sections, MPLS-TP LSPs or PWs as specified
> >  > by G.8113.1.
> >
> > MB: No objection to this change.
> >
> >  >
> >  >
> >  > Section 2 - third paragraph
> >  > ===========================
> >  >
> >  > With regard to revisions, which is what I think the third paragraph
> >  > is about, I am not clear what you are trying to say. A code point
> >  > allocation must point to a stable referent. If the desired referent
> >  > changes, then process needs to be followed to make sure that the IANA
> >  > is updated in accordance with IETF procedures. Hence, I am left to
> >  > the conclusion that the third paragraph is actually asking for
> >  > something we can not do. Can we remove that?
> >  >
> >  > OLD:
> >  > All ITU-T Recommendations are subject to revisions. Therefore, the
> >  > code point allocated by this document may be used for future versions
> >  > of [G.8113.1].
> >  >
> >  > NEW:
> >  > -
> >  >
> >  >
> >
> > MB: I do not agree with the removal of this text:
> >
> > The intention of this statement is to bring to the attention of the IETF
> > the normal practice in the ITU of developing amendments to
> > Recommendations to fully meet the functional requirements (e.g. adding
> > pro-active loss measurement). Normally any reference to ITU-T Rec
> > G.8113.1 will automatically be directed to the current version
> > (including any amendments).
> >
> > Only those interfaces that support G.8113.1 OAM will act on these OAM
> > messages, any interface that does not support this G-ACh type will
> > discard these OAM messages as defined in RFC5586.
> >
> > Restricting the application of the code point to a specific version of
> > Recommendation G.8113.1 would require the ITU to deviate from its normal
> > process for enhancing Recommendations and would put the IETF back into
> > the discussion for approval.
> >
> >
> >
> >  >---------------snip
> >
> >
> >  >
> >  > 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
> >  > _______________________________________________
> >  > Ietf mailing list
> >  > Ietf@ietf.org
> >  > https://www.ietf.org/mailman/listinfo/ietf
> >  >
>
> --
>
>
> 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 daedulus@btconnect.com  Fri Mar 23 03:59:17 2012
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CDA6121F8526 for <ietf@ietfa.amsl.com>; Fri, 23 Mar 2012 03:59:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.873
X-Spam-Level: 
X-Spam-Status: No, score=-1.873 tagged_above=-999 required=5 tests=[AWL=0.726,  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 TOdW5cEJGIp9 for <ietf@ietfa.amsl.com>; Fri, 23 Mar 2012 03:59:16 -0700 (PDT)
Received: from mail.btconnect.com (c2beaomr06.btconnect.com [213.123.26.184]) by ietfa.amsl.com (Postfix) with ESMTP id 4A8E821F846C for <ietf@ietf.org>; Fri, 23 Mar 2012 03:59:15 -0700 (PDT)
Received: from host86-162-135-195.range86-162.btcentralplus.com (HELO pc6) ([86.162.135.195]) by c2beaomr06.btconnect.com with SMTP id GZI14492; Fri, 23 Mar 2012 10:59:10 +0000 (GMT)
Message-ID: <00c001cd08db$7323d2c0$4001a8c0@gateway.2wire.net>
From: "t.petch" <daedulus@btconnect.com>
To: "Alia Atlas" <akatlas@gmail.com>, "Rui Costa" <RCosta@ptinovacao.pt>
References: <52981DB05D3C5247A12D0AEE309F3CC202444240C161@INOAVREX11.ptin.corpPT.com> <CAG4d1reb=bWp09uT-tOLyvSa7q-W5a-LnpGphngg-+KR1+TcKg@mail.gmail.com>
Subject: Re: FW: LastCall:<draft-betts-itu-oam-ach-code-point-03.txt>(Allocationofan Associated Channel Code Point for Use byITU-T Ethernetbased OAM) toInformational RFC
Date: Fri, 23 Mar 2012 10:58:04 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Mirapoint-IP-Reputation: reputation=Fair-1, source=Queried, refid=tid=0001.0A0B0303.4F6C577E.00DC, actions=TAG
X-Junkmail-Premium-Raw: score=7/50, refid=2.7.2:2012.3.23.95415:17:7.944, ip=86.162.135.195, rules=__HAS_MSGID, __OUTLOOK_MSGID_1, __SANE_MSGID, __TO_MALFORMED_2, __BOUNCE_CHALLENGE_SUBJ, __BOUNCE_NDR_SUBJ_EXEMPT, __SUBJ_ALPHA_END, __MIME_VERSION, __CT, __CT_TEXT_PLAIN, __CTE, __HAS_X_PRIORITY, __HAS_MSMAIL_PRI, __HAS_X_MAILER, USER_AGENT_OE, __OUTLOOK_MUA_1, __USER_AGENT_MS_GENERIC, __ANY_URI, __FRAUD_BODY_WEBMAIL, __URI_NO_WWW, __URI_NO_PATH, __HIGHBITS, BODY_SIZE_3000_3999, __MIME_TEXT_ONLY, RDNS_GENERIC_POOLED, HTML_00_01, HTML_00_10, BODY_SIZE_5000_LESS, RDNS_SUSP_GENERIC, __OUTLOOK_MUA, RDNS_SUSP, __FRAUD_WEBMAIL, BODY_SIZE_7000_LESS
X-Junkmail-Status: score=10/50, host=c2beaomr06.btconnect.com
X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A0B0201.4F6C577E.01E4,ss=1,re=0.000,fgs=0, ip=0.0.0.0, so=2011-07-25 19:15:43, dmn=2011-05-27 18:58:46, mode=multiengine
X-Junkmail-IWF: false
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, 23 Mar 2012 10:59:17 -0000

----- Original Message -----
From: "Alia Atlas" <akatlas@gmail.com>
To: "Rui Costa" <RCosta@ptinovacao.pt>
Cc: <ietf@ietf.org>
Sent: Thursday, March 22, 2012 10:07 PM

Rui,

Perhaps more familiarity with the related history over the last
several years would help?  I can recommend the MPLS list archives.
Otherwise, I find this remarkably disingenuous.

This is a case of a second solution that was clearly rejected by the
MPLS working group (despite in-person histrionics causing the ADs to
have to threaten to close down the WG meeting).  Then the solution was
taken to the ITU study group - where it could also not get enough
traction for their normal process.  It is still not approved as a
recommendation.

<tp>
Alia

Were the roles reversed and the second solution be a product of the IETF that
the IETF were trying to get more widely approved, would the IETF allocate a code
point?

I think that it would.  We certainly have running code, widely deployed
(although my request on the MPLS list as to which manufacturers' boxes were
involved never did get answered:-(.

We have a rough consensus; not unanimity, and not enough of a consensus to
satisfy the processes of the ITU-T but I think enough to satisfy the
consensus-judgers of the IETF (as ever, we do not vote, a majority of e-mails
for one point of view may be discounted, it is the quality of the views
expressed that matters as much or more).

So applying the standards to which we work, I think this is another reason why
we should approve this I-D.

Tom Petch

</tp>
To imply that the IETF should simply trust the allocated ACH code
point to not be abused both seems optimistic and sets a dreadful
precedent.

Making an allocation available for an approved recommendation version
is a tolerable way of reducing the deliberate use of an experimental
value.   Handing the keys over for any conceivable use, or even just
the uses in the OAM RFC that have been adequately met by IETF
WG-consensus based technology, does not seem appropriate.

Alia



On Thu, Mar 22, 2012 at 10:42 AM, Rui Costa <RCosta@ptinovacao.pt> wrote:
> I fail to understand the issue under discussion.
>
> Can't imagine IEEE denying to grant Ethertype 0x86DD. If, however, from absurd
that had happened, would the world stop or would we take the same information
from the IP header version field?
>
> Regards,
> Rui
>
>
> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of Alia
Atlas
> Sent: quarta-feira, 21 de Março de 2012 15:30
> To: D'Alessandro Alessandro Gerardo
> Cc: ietf@ietf.org
> Subject: Re: הנדון: RE: Last
Call:<draft-betts-itu-oam-ach-code-point-03.txt>(Allocationof an Associated
Channel Code Point for Use byITU-T Ethernetbased OAM) to Informational RFC
>
> Considering that the need for this code point is a result of the ITU
> not fully complying with the IETF agreement, I cannot agree that we
> should simply allocate a code point for whatever the ITU wants to do
> in the future.
>
> It seems the best of the options to allocate a code point (much better
> than squatting) - but tie it to a stable reference. If the ITU can't
> provide a stable reference, then perhaps an RFC is the best way.
> There are lots of folks with opinions on the best procedure, but I
> certainly don't support the idea of not restricting the usage to what
> is clearly defined.
>
> Alia



From daedulus@btconnect.com  Fri Mar 23 04:31:31 2012
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0308121F8503 for <ietf@ietfa.amsl.com>; Fri, 23 Mar 2012 04:31:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.718
X-Spam-Level: 
X-Spam-Status: No, score=-1.718 tagged_above=-999 required=5 tests=[AWL=0.281,  BAYES_00=-2.599, J_CHICKENPOX_15=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3syNc3KyvEZc for <ietf@ietfa.amsl.com>; Fri, 23 Mar 2012 04:31:30 -0700 (PDT)
Received: from mail.btconnect.com (c2beaomr06.btconnect.com [213.123.26.184]) by ietfa.amsl.com (Postfix) with ESMTP id D3E2021F84D7 for <ietf@ietf.org>; Fri, 23 Mar 2012 04:31:28 -0700 (PDT)
Received: from host86-162-135-195.range86-162.btcentralplus.com (HELO pc6) ([86.162.135.195]) by c2beaomr06.btconnect.com with SMTP id GZI56816; Fri, 23 Mar 2012 11:31:26 +0000 (GMT)
Message-ID: <00f601cd08df$f4a389e0$4001a8c0@gateway.2wire.net>
From: "t.petch" <daedulus@btconnect.com>
To: "Eliot Lear" <lear@cisco.com>
References: <20120222151252.32262.82157.idtracker@ietfa.amsl.com><03a301ccf174$ff953290$febf97b0$@olddog.co.uk><515703B08A3A064C9CC8C09ACCC710DC0631679E@XMB-RCD-103.cisco.com><C71DA9B1-A61F-4C5D-8DCE-3702271CBB6D@vigilsec.com><4F4FA70B.2030906@pi.nu><D0F60388-D852-4815-917A-B14BF40C64FB@vigilsec.com><BD60EA38ED03AF5A21868DF1@PST.JCK.COM> <4F4FC252.9010001@cisco.com> <C3E581FB44D46BF4128A2229@PST.JCK.COM> <029b01ccfb84$4e4e2220$4001a8c0@gateway.2wire.net> <4F55F92F.1020105@cisco.com> <005701ccfbad$5c6d9060$4001a8c0@gateway.2wire.net> <4F69B630.9050909@cisco.com>
Subject: Re: Last Call:<draft-betts-itu-oam-ach-code-point-03.txt>	(Allocation of anAssociated Channel Code Point for Use by	ITU-T Ethernet basedOAM) to Informational RFC
Date: Fri, 23 Mar 2012 11:30:19 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Mirapoint-IP-Reputation: reputation=Fair-1, source=Queried, refid=tid=0001.0A0B0302.4F6C5F0D.00AF, actions=TAG
X-Junkmail-Premium-Raw: score=7/50, refid=2.7.2:2012.3.23.111516:17:7.944, ip=86.162.135.195, rules=__HAS_MSGID, __OUTLOOK_MSGID_1, __SANE_MSGID, __TO_MALFORMED_2, __BOUNCE_CHALLENGE_SUBJ, __BOUNCE_NDR_SUBJ_EXEMPT, __SUBJ_ALPHA_END, __MIME_VERSION, __CT, __CT_TEXT_PLAIN, __CTE, __HAS_X_PRIORITY, __HAS_MSMAIL_PRI, __HAS_X_MAILER, USER_AGENT_OE, __OUTLOOK_MUA_1, __USER_AGENT_MS_GENERIC, __ANY_URI, __URI_NO_WWW, __URI_NO_PATH, BODYTEXTP_SIZE_3000_LESS, BODY_SIZE_2000_2999, __MIME_TEXT_ONLY, RDNS_GENERIC_POOLED, HTML_00_01, HTML_00_10, BODY_SIZE_5000_LESS, RDNS_SUSP_GENERIC, __OUTLOOK_MUA, RDNS_SUSP, BODY_SIZE_7000_LESS
X-Junkmail-Status: score=10/50, host=c2beaomr06.btconnect.com
X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A0B0204.4F6C5F0E.0028,ss=1,re=0.000,fgs=0, ip=0.0.0.0, so=2011-07-25 19:15:43, dmn=2011-05-27 18:58:46, mode=multiengine
X-Junkmail-IWF: false
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, 23 Mar 2012 11:31:31 -0000

----- Original Message -----
From: "Eliot Lear" <lear@cisco.com>
To: "t.petch" <daedulus@btconnect.com>
Cc: <ietf@ietf.org>
Sent: Wednesday, March 21, 2012 12:06 PM
> Tom,
>
> I've let this sit a while, but wanted to respond on the following point:
>
> On 3/6/12 4:25 PM, t.petch wrote:
> > -ur responsibility is to ourselves first and foremost, and to see that
> > our process is followed.  That process exists to, amongst other things,
> > insure safe use and interoperable use of our own protocols.
> > Which, Eliot, is where we part company.  Given the interest in and uptake
> > of MPLS outside the original definition, we have a wider responsibility,
> > as we have in, say, managing the IP address or domain name space.
>
> If our process is broken, we should change it.  Our processes should
> take into account that which *we* can control.  Making the best
> recommendations for the use of our protocols on the Internet addresses
> your point about the "wider community".  The IETF exists to serve that
> wider community, but when others attempt to use our works in a way that
> might harm our work, we equally have a responsibility to hold a line.  I
> am NOT saying that in this instance, by the way, G.8113.1 harms IETF
> work if a proper code point is assigned.  It would harm our work if a
> code point was simply expropriated.

<tp>
Yes I agree.

> >   As
> > with the last two, if we do not consider the needs of all parties, and not
just
> > ourselves, we may lose our influence in these matters.  Yes we must follow
our
> > processes but in the interests of a wider community than just ourselves.
>
> Were this really true, then we must reject this request because of the
> likelihood of fragmented solutions that do not interoperate.  Is that
> what you are arguing?

Disagree here.  Where multiple solutions exist, then interoperability costs
more.  Ask anyone implementing ... well anything with IP in it, say, and
currently, they will be expected to have both IPv4 and IPv6, a dual stack in
some sense of the word, and the cost of this ripples up the stack to whereever
IP addresses cease to be visible, which is a long way up.

Ditto SNMP where there are three different flavours that a stack will support,
in many if not most cases.  And so on and so forth.

So having two different packet formats for the same OAM function is a pain and
will cost; but as long as the protocols are properly defined, as I believe they
are here, then the coexistence will have a cost but will not stop
interoperability, in the same way as we have IPv6 and IPv4 and a lot of
associated options, dual stack, gateway, encapsulation ......

Tom Petch

>
> Eliot
>


From akatlas@gmail.com  Fri Mar 23 07:12:04 2012
Return-Path: <akatlas@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 61EDC21F84CE for <ietf@ietfa.amsl.com>; Fri, 23 Mar 2012 07:12:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.133
X-Spam-Level: 
X-Spam-Status: No, score=-3.133 tagged_above=-999 required=5 tests=[AWL=-0.134, BAYES_00=-2.599, J_CHICKENPOX_15=0.6, 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 sZh1C0xiaEO3 for <ietf@ietfa.amsl.com>; Fri, 23 Mar 2012 07:12:03 -0700 (PDT)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id CDE8821F8470 for <ietf@ietf.org>; Fri, 23 Mar 2012 07:11:56 -0700 (PDT)
Received: by iazz13 with SMTP id z13so5549983iaz.31 for <ietf@ietf.org>; Fri, 23 Mar 2012 07:11: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:content-transfer-encoding; bh=uMkHh8OY2mYpj9iW6sQCizty4AdSAAP0hGu9lVRID9I=; b=SwBpbUWRM6zGHBEIMWrQfhBpvsNmv0u7487CfZvUUFJFH0obcCYfFVQvBx5oOeiyqG DWMGOZLX2qNDcYmg92hySoQwUe16MaLFYUMXVbmCrNS9s3edqgZDwTRR8jV5FJ7GOYEd lcbiSznJSjPjJSpX9dCjLHBvH3OCCFGmIrGBU2z4XEHsfDTQdz/msFU4trSDXt/iLjug WzO+Tx9aCyiXd0L193oEaqMj3Hvr6Bl2uxIBnbSVB8Mpmb33zd1aA+2ijPyAMzZP+Xl3 6R26Wn2YDgMAg7Bt5XwfTkji6xNU6ez2E6aMXuzzPTLLNOEiYl90+Ao25mKRHDkIsOzA o9ZQ==
MIME-Version: 1.0
Received: by 10.50.186.168 with SMTP id fl8mr2123419igc.68.1332511913076; Fri, 23 Mar 2012 07:11:53 -0700 (PDT)
Received: by 10.50.1.209 with HTTP; Fri, 23 Mar 2012 07:11:53 -0700 (PDT)
In-Reply-To: <00c001cd08db$7323d2c0$4001a8c0@gateway.2wire.net>
References: <52981DB05D3C5247A12D0AEE309F3CC202444240C161@INOAVREX11.ptin.corpPT.com> <CAG4d1reb=bWp09uT-tOLyvSa7q-W5a-LnpGphngg-+KR1+TcKg@mail.gmail.com> <00c001cd08db$7323d2c0$4001a8c0@gateway.2wire.net>
Date: Fri, 23 Mar 2012 10:11:53 -0400
Message-ID: <CAG4d1rc8EjOj1dn5NPAJx3s4Xg+-D=p0tjFNOmq611NGdActFA@mail.gmail.com>
Subject: Re: FW: LastCall:<draft-betts-itu-oam-ach-code-point-03.txt>(Allocationofan Associated Channel Code Point for Use byITU-T Ethernetbased OAM) toInformational RFC
From: Alia Atlas <akatlas@gmail.com>
To: "t.petch" <daedulus@btconnect.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Mar 2012 14:12:04 -0000

Tom,

Thank you for both judging consensus (the IESG's job) and instructing
me on how it is done in the IETF (quite useful to me as a WG chair).
Thanks also for cutting my email where I agreed that allocating a
code-point for this particular use was the most tolerable option (I
know the email thread had gotten long).

Here it is again:

> Making an allocation available for an approved recommendation version
> is a tolerable way of reducing the deliberate use of an experimental
> value.   Handing the keys over for any conceivable use, or even just
> the uses in the OAM RFC that have been adequately met by IETF
> WG-consensus based technology, does not seem appropriate.

There are 2 separate points on which discussion is occurring.

1)  Should an ACH code-point be allocated?
2)  If so, should it be
    (a) restricted to a particular approved version of the recommendation o=
r
    (b) available for whatever the ITU wants or
    (c) slightly restricted to uses to meet the relevant OAM RFC?

On the second question, the IETF doesn't do 2b - but rather ties
allocations to published RFCs.  Option 2a matches both IETF process
and avoids setting a dreadful precedent.

Alia

On Fri, Mar 23, 2012 at 5:58 AM, t.petch <daedulus@btconnect.com> wrote:
> ----- Original Message -----
> From: "Alia Atlas" <akatlas@gmail.com>
> To: "Rui Costa" <RCosta@ptinovacao.pt>
> Cc: <ietf@ietf.org>
> Sent: Thursday, March 22, 2012 10:07 PM
>
> Rui,
>
> Perhaps more familiarity with the related history over the last
> several years would help? =C2=A0I can recommend the MPLS list archives.
> Otherwise, I find this remarkably disingenuous.
>
> This is a case of a second solution that was clearly rejected by the
> MPLS working group (despite in-person histrionics causing the ADs to
> have to threaten to close down the WG meeting). =C2=A0Then the solution w=
as
> taken to the ITU study group - where it could also not get enough
> traction for their normal process. =C2=A0It is still not approved as a
> recommendation.
>
> <tp>
> Alia
>
> Were the roles reversed and the second solution be a product of the IETF =
that
> the IETF were trying to get more widely approved, would the IETF allocate=
 a code
> point?
>
> I think that it would. =C2=A0We certainly have running code, widely deplo=
yed
> (although my request on the MPLS list as to which manufacturers' boxes we=
re
> involved never did get answered:-(.
>
> We have a rough consensus; not unanimity, and not enough of a consensus t=
o
> satisfy the processes of the ITU-T but I think enough to satisfy the
> consensus-judgers of the IETF (as ever, we do not vote, a majority of e-m=
ails
> for one point of view may be discounted, it is the quality of the views
> expressed that matters as much or more).
>
> So applying the standards to which we work, I think this is another reaso=
n why
> we should approve this I-D.
>
> Tom Petch
>
> </tp>
> To imply that the IETF should simply trust the allocated ACH code
> point to not be abused both seems optimistic and sets a dreadful
> precedent.
>
> Making an allocation available for an approved recommendation version
> is a tolerable way of reducing the deliberate use of an experimental
> value. =C2=A0 Handing the keys over for any conceivable use, or even just
> the uses in the OAM RFC that have been adequately met by IETF
> WG-consensus based technology, does not seem appropriate.
>
> Alia
>
>
>
> On Thu, Mar 22, 2012 at 10:42 AM, Rui Costa <RCosta@ptinovacao.pt> wrote:
>> I fail to understand the issue under discussion.
>>
>> Can't imagine IEEE denying to grant Ethertype 0x86DD. If, however, from =
absurd
> that had happened, would the world stop or would we take the same informa=
tion
> from the IP header version field?
>>
>> Regards,
>> Rui
>>
>>
>> -----Original Message-----
>> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of =
Alia
> Atlas
>> Sent: quarta-feira, 21 de Mar=C3=A7o de 2012 15:30
>> To: D'Alessandro Alessandro Gerardo
>> Cc: ietf@ietf.org
>> Subject: Re: =D7=94=D7=A0=D7=93=D7=95=D7=9F: RE: Last
> Call:<draft-betts-itu-oam-ach-code-point-03.txt>(Allocationof an Associat=
ed
> Channel Code Point for Use byITU-T Ethernetbased OAM) to Informational RF=
C
>>
>> Considering that the need for this code point is a result of the ITU
>> not fully complying with the IETF agreement, I cannot agree that we
>> should simply allocate a code point for whatever the ITU wants to do
>> in the future.
>>
>> It seems the best of the options to allocate a code point (much better
>> than squatting) - but tie it to a stable reference. If the ITU can't
>> provide a stable reference, then perhaps an RFC is the best way.
>> There are lots of folks with opinions on the best procedure, but I
>> certainly don't support the idea of not restricting the usage to what
>> is clearly defined.
>>
>> Alia
>
>

From malcolm.betts@zte.com.cn  Fri Mar 23 08:39:57 2012
Return-Path: <malcolm.betts@zte.com.cn>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 884DE21F8531 for <ietf@ietfa.amsl.com>; Fri, 23 Mar 2012 08:39:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.388
X-Spam-Level: 
X-Spam-Status: No, score=-101.388 tagged_above=-999 required=5 tests=[AWL=0.450, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_DOUBLE_IP_LOOSE=0.76, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TxHEFzkryPpv for <ietf@ietfa.amsl.com>; Fri, 23 Mar 2012 08:39:53 -0700 (PDT)
Received: from mx5.zte.com.cn (mx6.zte.com.cn [95.130.199.165]) by ietfa.amsl.com (Postfix) with ESMTP id 7227C21F854E for <ietf@ietf.org>; Fri, 23 Mar 2012 08:39:52 -0700 (PDT)
Received: from [10.30.17.100] by mx5.zte.com.cn with surfront esmtp id 1228011182326; Fri, 23 Mar 2012 23:05:16 +0800 (CST)
Received: from [10.30.3.20] by [192.168.168.16] with StormMail ESMTP id 77675.518932364; Fri, 23 Mar 2012 23:39:22 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse01.zte.com.cn with ESMTP id q2NFdWKD061543; Fri, 23 Mar 2012 23:39:32 +0800 (GMT-8) (envelope-from Malcolm.BETTS@zte.com.cn)
In-Reply-To: <00b801cd08da$6885bbe0$4001a8c0@gateway.2wire.net>
References: <20120222151252.32262.82157.idtracker@ietfa.amsl.com>	<039f01ccf174$fe79d780$fb6d8680$@olddog.co.uk><44F4E579A764584EA9BDFD07D0CA0813075C936F@tlvmail1> <4F4B7EA2.7070305@cisco.com><4F4B8A75.6000207@pi.nu> <4F5DB46F.10009@pi.nu><OFE57A943C.CA873F89-ON852579C8.006D6B01-852579C8.0070E507@zte.com.cn> <4F6C460F.4080007@pi.nu> <00b801cd08da$6885bbe0$4001a8c0@gateway.2wire.net>
To: "t.petch" <daedulus@btconnect.com>
Subject: Re: [PWE3] FW: LastCall:	<draft-betts-itu-oam-ach-code-point-03.txt>(Allocationof an Associated Channel Code Point for Use byITU-T Ethernet	basedOAM)	to Informational RFC
MIME-Version: 1.0
X-KeepSent: FF023599:28F45CA8-852579CA:0055A56A; type=4; name=$KeepSent
X-Mailer: Lotus Notes Release 8.5.1 September 28, 2009
Message-ID: <OFFF023599.28F45CA8-ON852579CA.0055A56A-852579CA.00560272@zte.com.cn>
From: Malcolm.BETTS@zte.com.cn
Date: Fri, 23 Mar 2012 10:39:20 -0500
X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 8.5.1FP4|July 25, 2010) at 2012-03-23 23:39:34, Serialize complete at 2012-03-23 23:39:34
Content-Type: multipart/alternative; boundary="=_alternative 00560271852579CA_="
X-MAIL: mse01.zte.com.cn q2NFdWKD061543
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, 23 Mar 2012 15:39:57 -0000

This is a multipart message in MIME format.
--=_alternative 00560271852579CA_=
Content-Type: text/plain; charset="US-ASCII"

Tom,

I have no objections to using the RFC 2119 key words, I am not sure if 
that is appropriate in an informational track document, I expect that our 
AD will provide some guidance.

Regards,

Malcolm




"t.petch" <daedulus@btconnect.com> 
23/03/2012 05:50 AM

To
"Loa Andersson" <loa@pi.nu>, <Malcolm.BETTS@zte.com.cn>
cc
<ietf@ietf.org>
Subject
Re: [PWE3] FW: LastCall: 
<draft-betts-itu-oam-ach-code-point-03.txt>(Allocationof        an 
Associated Channel Code Point for Use byITU-T Ethernet  basedOAM)       to 
Informational RFC






Loa

The one point that jumps out at me is the proposed text
"Other message types should not be carried behind this code point."
or should that be
"Other message types SHOULD NOT be carried behind this code point."
which, in IETF-Land, is a bit different.

I prefer the latter.

Tom Petch


----- Original Message -----
From: "Loa Andersson" <loa@pi.nu>
To: <Malcolm.BETTS@zte.com.cn>
Cc: <ietf@ietf.org>
Sent: Friday, March 23, 2012 10:44 AM
Subject: Re: [PWE3] FW: LastCall:
<draft-betts-itu-oam-ach-code-point-03.txt>(Allocationof an Associated 
Channel
Code Point for Use byITU-T Ethernet basedOAM) to Informational RFC


> Malcolm,
>
> good that we are making some progress!
>
> On the experimental code point
> ------------------------------
>
> I doesn't seem appropriate to call out the fact that some commercial
> products has been using an experimental code point in production
> setting!
>
> On the remain (key) disagreements
> ---------------------------------
>
> I will let other people comment for now.
>
>
> /Loa
>
> On 2012-03-21 21:33, Malcolm.BETTS@zte.com.cn wrote:
> > Loa,
> >
> > Thank you for your comments and suggestions, please see in line below.
> >
> > Regards,
> >
> > Malcolm
> >
> >
> > ietf-bounces@ietf.org wrote on 12/03/2012 04:31:43 AM:
> >
> >  > Loa Andersson <loa@pi.nu>
> >  > Sent by: ietf-bounces@ietf.org
> >  >
> >  > 12/03/2012 04:31 AM
> >  >
> >  > To
> >  >
> >  > ietf@ietf.org
> >  >
> >  > cc
> >  >
> >  > Subject
> >  >
> >  > Re: [PWE3] FW: Last Call: <draft-betts-itu-oam-ach-code-
> >  > point-03.txt>(Allocation of an Associated Channel Code Point for 
Use
> >  > byITU-T Ethernet based OAM) to Informational RFC
> >  >
> >  > All,
> >  >
> >  > I've been asked to clarify thee comments in this mail, I done
> >  > so by proposing new text to draft-betts-.
> >  >
> >  > I hope this helps.
> >  >
> >  >
> >  > Title
> >  > =====
> >  >
> >  > Comment: We want to assign a Associated Channel Type. The registry
> >  > that it will be assigned from is "Pseudowire Associated Channel
> >  > Types"; however RFC 5586, makes the Channel Types generic and I
> >  > think the title should be changed as follows:
> >  >
> >  > OLD:
> >  > Allocation of an Associated Channel Code Point for Use by ITU-T
> >  > Ethernet based OAM
> >  >
> >  > NEW:
> >  > Allocation of an Generic Associated Channel Type for ITU-T
> >  > MPLS-TP OAM
> >  >
> >  > Note: Neither MPLS-TP or OAM are in the RFC Editors list of 
wellknown
> >  > acronyms, therfore the title probably should be:
> >  >
> >  > NEW:
> >  > Allocation of an Generic Associated Channel Type for ITU-T
> >  > MPLS Transport Profile Operation, Maintenance and Administration.
> >  >
> >
> > MB: No objection to this change
> >
> >  >
> >  > Introduction - first paragraph
> >  > ==============================
> >  >
> >  > In the first paragraph of the introduction, there seems to be an
> >  > oddity in the description of the role of the ietf-tp-oam-analysis
> >  > document. Instead of:
> >  >
> >  > OLD
> >  > "tools defined by the IETF [I-D.ietf-mpls-tp-oam-analysis], that
> >  > are intended to meet the OAM functional requirements defined in
> >  > [RFC5860]."
> >  >
> >  > NEW:
> >  > "tools described by the IETF [I-D.ietf-mpls-tp-oam-analysis], which
> >  > are used to meet the OAM functional requirements defined
> >  > in [RFC5860]."
> >
> > MB: No objection to this change
> >
> >  >
> >  > Intrduction - second paragraph
> >  > ==============================
> >  >
> >  > The next paragraph in describing G.8113.1, stumbles over the 
current
> >  > vs anticipated future state of G.8113.1 and its relationship to
> >  > its antecedents. I'm a bit un-certain about the correct 
terminology,
> >  > but I think the following change would improve the document.
> >  >
> >  > OLD:
> >  >
> >  > The ITU-T has documented, in draft new Recommendation [G.8113.1], 
the
> >  > use of Ethernet based OAM mechanisms, originally defined in 
[Y.1731],
> >  > carried in the MPLS Generic Associated Channel (G-ACh). This 
approach
> >  > requires the allocation of an ACH Type from the registry of ACH 
types
> >  > maintained by IANA in order that the messages that will be 
described
> >  > in [G.8113.1] can be identified by an implementation.
> >  >
> >  > NEW:
> >  >
> >  > "The ITU-T has Draft Recommendation [G.8113.1] documented MPLS OAM
> >  > which as of this writing is undergoing the ITU-T Traditional
> >  > Approval Process (TAP). This Recommendation builds upon Ethernet
> >  > OAM as documented in [Y.1731]. The messages in [G.8113.1] are 
defined
> >  > to be carried in a new Associated Channel Type in the MPLS Generaic
> >  > Associated Channel (G-Ach). In order to carry these messages in an
> >  > interoperable fashion, an Associated Channel Type from the IANA
> >  > maintained registry "Pseudowire Associated Channel Types is to be
> >  > used."
> >
> > MB: Since the draft will not be published as an RFC until after 
G.8113.1
> > is approved we can directly reference the approved Recommendation and 
I
> > suggest that we modify paragraph to:
> >
> >
> > ITU-T Recommendation [G.8113.1] documents MPLS OAM. This 
Recommendation
> > builds upon Ethernet OAM as documented in [Y.1731]. The messages in
> > [G.8113.1] are defined to be carried in a new Associated Channel Type 
in
> > the MPLS Generaic Associated Channel (G-Ach). In order to carry these
> > messages in an interoperable fashion, an Associated Channel Type from
> > the IANA maintained registry "Pseudowire Associated Channel Types is 
to
> > be used."
> >
> >
> >  >
> >  > Note there are confusion around some of the Associated Channel
> >  > acronyms that are refledted in this document.
> >  >
> >  > ACh is Associated Channel
> >  > ACH is Associated Chamnnel Header
> >  > G-ACh is Generic Associated Channel
> >  >
> >  > "ACH Type" is not used anywhere in IETF documents; we talk about
> >  > Associated Channel Type or Generic Associated Channel Type
> >  > (G-ACh Type).
> >
> > MB: Thank you, I will fix this.
> >
> >  >
> >  > Introduction - third paragraph
> >  > ==============================
> >  >
> >  > In the third paragraph, there seems to be an unnecessary reference
> >  > to experimental types. When asking for a code point for a standard,
> >  > it is not helped to bring up experimental code space. Can we remove
> >  > the text reading:
> >  >
> >  > OLD:
> >  > "without continuing to resorting to the use of an experimental
> >  > ACH Type,"
> >  >
> >  > NEW
> >  > -
> >
> > MB: I do not agree with the deletion of this text, these existing
> > deployments, and the desire to migrate to an allocated code point, are
> > part of the rational for requesting the code point.
> >
> >  >
> >  >
> >  > Section 2 - first paragraph
> >  > ===========================
> >  >
> >  >
> >  >
> >  > In section 2, the first sentence refers to Ethernet based OAM
> >  > messages. As far as I know, the messages in G.8113.1 are either
> >  > MPLS-TP OAM messages, or they are simply the OAM messages defined
> >  > in G.8113.1. The simplest path to clarity would seem to be to
> >  > replace "Ethernet based OAM messages" in that sentence with
> >  > "messages".
> >  >
> >  > The second sentence of that paragraph does not seem to say anything
> >  > we need to say. Can we remove it?
> >  >
> >  > OLD:
> >  >
> >  > The code point allocated by this document is intended to be used 
only
> >  > for Ethernet based OAM messages, defined in the ITU-T 
Recommendation
> >  > [G.8113.1], carried in the G-ACh . These Ethernet based OAM 
messages
> >  > and procedures, address the OAM functional requirements defined in
> >  > [RFC5860]. Other message types should not be carried behind this 
code
> >  > point.
> >  >
> >  > NEW:
> >  >
> >  > The code point allocated by this document is intended to be used
> >  > only for OAM messages, defined in the ITU-T Recommendation
> >  > [G.8113.1], carried in the G-ACh . Other message types should not
> >  > be carried behind this Associated Channel Type.
> >
> >
> > MB: I do not agree with this proposed change. Other comments request
> > that the restriction on the applicability of the code point is
> > strengthened so I propose the following:
> >
> > The code point allocated by this document should only be used for OAM
> > messages, defined in the ITU-T Recommendation [G.8113.1], carried in 
the
> > G-ACh. The messages and procedures carried behind this code point, are
> > restricted to only those that the address the OAM functional
> > requirements defined in [RFC5860]. Other message types should not be
> > carried behind this code point.
> >
> >
> >  >
> >  > Section 2 - second paragraph
> >  > ============================
> >  >
> >  > A matter of some clarity, can we change this paragrap like this:
> >  >
> >  > OLD:
> >  > This code point may be used on any transport construct that uses
> >  > the G-ACh, e.g., MPLS-TP Sections, MPLS-TP LSPs or PWs.
> >  >
> >  > NEW:
> >  >
> >  > The Generic Associated Channel Type assigned by this
> >  > document may be used on any transport construct that uses the
> >  > G-ACh, e.g., MPLS-TP Sections, MPLS-TP LSPs or PWs as specified
> >  > by G.8113.1.
> >
> > MB: No objection to this change.
> >
> >  >
> >  >
> >  > Section 2 - third paragraph
> >  > ===========================
> >  >
> >  > With regard to revisions, which is what I think the third paragraph
> >  > is about, I am not clear what you are trying to say. A code point
> >  > allocation must point to a stable referent. If the desired referent
> >  > changes, then process needs to be followed to make sure that the 
IANA
> >  > is updated in accordance with IETF procedures. Hence, I am left to
> >  > the conclusion that the third paragraph is actually asking for
> >  > something we can not do. Can we remove that?
> >  >
> >  > OLD:
> >  > All ITU-T Recommendations are subject to revisions. Therefore, the
> >  > code point allocated by this document may be used for future 
versions
> >  > of [G.8113.1].
> >  >
> >  > NEW:
> >  > -
> >  >
> >  >
> >
> > MB: I do not agree with the removal of this text:
> >
> > The intention of this statement is to bring to the attention of the 
IETF
> > the normal practice in the ITU of developing amendments to
> > Recommendations to fully meet the functional requirements (e.g. adding
> > pro-active loss measurement). Normally any reference to ITU-T Rec
> > G.8113.1 will automatically be directed to the current version
> > (including any amendments).
> >
> > Only those interfaces that support G.8113.1 OAM will act on these OAM
> > messages, any interface that does not support this G-ACh type will
> > discard these OAM messages as defined in RFC5586.
> >
> > Restricting the application of the code point to a specific version of
> > Recommendation G.8113.1 would require the ITU to deviate from its 
normal
> > process for enhancing Recommendations and would put the IETF back into
> > the discussion for approval.
> >
> >
> >
> >  >---------------snip
> >
> >
> >  >
> >  > 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
> >  > _______________________________________________
> >  > Ietf mailing list
> >  > Ietf@ietf.org
> >  > https://www.ietf.org/mailman/listinfo/ietf
> >  >
>
> --
>
>
> 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
>
>




--=_alternative 00560271852579CA_=
Content-Type: text/html; charset="US-ASCII"

<font size=2 face="sans-serif">Tom,</font>
<br>
<br><font size=2 face="sans-serif">I have no objections to using the RFC
2119 key words, I am not sure if that is appropriate in an informational
track document, I expect that our AD will provide some guidance.</font>
<br>
<br><font size=2 face="sans-serif">Regards,</font>
<br>
<br><font size=2 face="sans-serif">Malcolm</font>
<br>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=36%><font size=1 face="sans-serif"><b>&quot;t.petch&quot; &lt;daedulus@btconnect.com&gt;</b>
</font>
<p><font size=1 face="sans-serif">23/03/2012 05:50 AM</font>
<td width=63%>
<table width=100%>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">To</font></div>
<td><font size=1 face="sans-serif">&quot;Loa Andersson&quot; &lt;loa@pi.nu&gt;,
&lt;Malcolm.BETTS@zte.com.cn&gt;</font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td><font size=1 face="sans-serif">&lt;ietf@ietf.org&gt;</font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td><font size=1 face="sans-serif">Re: [PWE3] FW: LastCall: &nbsp; &nbsp;
&nbsp; &nbsp;&lt;draft-betts-itu-oam-ach-code-point-03.txt&gt;(Allocationof
&nbsp; &nbsp; &nbsp; &nbsp;an Associated Channel Code Point for
Use byITU-T Ethernet &nbsp; &nbsp; &nbsp; &nbsp;basedOAM) &nbsp;
&nbsp; &nbsp; &nbsp;to Informational RFC</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br><tt><font size=2>Loa<br>
<br>
The one point that jumps out at me is the proposed text<br>
&quot;Other message types should not be carried behind this code point.&quot;<br>
or should that be<br>
&quot;Other message types SHOULD NOT be carried behind this code point.&quot;<br>
which, in IETF-Land, is a bit different.<br>
<br>
I prefer the latter.<br>
<br>
Tom Petch<br>
<br>
<br>
----- Original Message -----<br>
From: &quot;Loa Andersson&quot; &lt;loa@pi.nu&gt;<br>
To: &lt;Malcolm.BETTS@zte.com.cn&gt;<br>
Cc: &lt;ietf@ietf.org&gt;<br>
Sent: Friday, March 23, 2012 10:44 AM<br>
Subject: Re: [PWE3] FW: LastCall:<br>
&lt;draft-betts-itu-oam-ach-code-point-03.txt&gt;(Allocationof an Associated
Channel<br>
Code Point for Use byITU-T Ethernet basedOAM) to Informational RFC<br>
<br>
<br>
&gt; Malcolm,<br>
&gt;<br>
&gt; good that we are making some progress!<br>
&gt;<br>
&gt; On the experimental code point<br>
&gt; ------------------------------<br>
&gt;<br>
&gt; I doesn't seem appropriate to call out the fact that some commercial<br>
&gt; products has been using an experimental code point in production<br>
&gt; setting!<br>
&gt;<br>
&gt; On the remain (key) disagreements<br>
&gt; ---------------------------------<br>
&gt;<br>
&gt; I will let other people comment for now.<br>
&gt;<br>
&gt;<br>
&gt; /Loa<br>
&gt;<br>
&gt; On 2012-03-21 21:33, Malcolm.BETTS@zte.com.cn wrote:<br>
&gt; &gt; Loa,<br>
&gt; &gt;<br>
&gt; &gt; Thank you for your comments and suggestions, please see in line
below.<br>
&gt; &gt;<br>
&gt; &gt; Regards,<br>
&gt; &gt;<br>
&gt; &gt; Malcolm<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; ietf-bounces@ietf.org wrote on 12/03/2012 04:31:43 AM:<br>
&gt; &gt;<br>
&gt; &gt; &nbsp;&gt; Loa Andersson &lt;loa@pi.nu&gt;<br>
&gt; &gt; &nbsp;&gt; Sent by: ietf-bounces@ietf.org<br>
&gt; &gt; &nbsp;&gt;<br>
&gt; &gt; &nbsp;&gt; 12/03/2012 04:31 AM<br>
&gt; &gt; &nbsp;&gt;<br>
&gt; &gt; &nbsp;&gt; To<br>
&gt; &gt; &nbsp;&gt;<br>
&gt; &gt; &nbsp;&gt; ietf@ietf.org<br>
&gt; &gt; &nbsp;&gt;<br>
&gt; &gt; &nbsp;&gt; cc<br>
&gt; &gt; &nbsp;&gt;<br>
&gt; &gt; &nbsp;&gt; Subject<br>
&gt; &gt; &nbsp;&gt;<br>
&gt; &gt; &nbsp;&gt; Re: [PWE3] FW: Last Call: &lt;draft-betts-itu-oam-ach-code-<br>
&gt; &gt; &nbsp;&gt; point-03.txt&gt;(Allocation of an Associated Channel
Code Point for Use<br>
&gt; &gt; &nbsp;&gt; byITU-T Ethernet based OAM) to Informational RFC<br>
&gt; &gt; &nbsp;&gt;<br>
&gt; &gt; &nbsp;&gt; All,<br>
&gt; &gt; &nbsp;&gt;<br>
&gt; &gt; &nbsp;&gt; I've been asked to clarify thee comments in this mail,
I done<br>
&gt; &gt; &nbsp;&gt; so by proposing new text to draft-betts-.<br>
&gt; &gt; &nbsp;&gt;<br>
&gt; &gt; &nbsp;&gt; I hope this helps.<br>
&gt; &gt; &nbsp;&gt;<br>
&gt; &gt; &nbsp;&gt;<br>
&gt; &gt; &nbsp;&gt; Title<br>
&gt; &gt; &nbsp;&gt; =====<br>
&gt; &gt; &nbsp;&gt;<br>
&gt; &gt; &nbsp;&gt; Comment: We want to assign a Associated Channel Type.
The registry<br>
&gt; &gt; &nbsp;&gt; that it will be assigned from is &quot;Pseudowire
Associated Channel<br>
&gt; &gt; &nbsp;&gt; Types&quot;; however RFC 5586, makes the Channel Types
generic and I<br>
&gt; &gt; &nbsp;&gt; think the title should be changed as follows:<br>
&gt; &gt; &nbsp;&gt;<br>
&gt; &gt; &nbsp;&gt; OLD:<br>
&gt; &gt; &nbsp;&gt; Allocation of an Associated Channel Code Point for
Use by ITU-T<br>
&gt; &gt; &nbsp;&gt; Ethernet based OAM<br>
&gt; &gt; &nbsp;&gt;<br>
&gt; &gt; &nbsp;&gt; NEW:<br>
&gt; &gt; &nbsp;&gt; Allocation of an Generic Associated Channel Type for
ITU-T<br>
&gt; &gt; &nbsp;&gt; MPLS-TP OAM<br>
&gt; &gt; &nbsp;&gt;<br>
&gt; &gt; &nbsp;&gt; Note: Neither MPLS-TP or OAM are in the RFC Editors
list of wellknown<br>
&gt; &gt; &nbsp;&gt; acronyms, therfore the title probably should be:<br>
&gt; &gt; &nbsp;&gt;<br>
&gt; &gt; &nbsp;&gt; NEW:<br>
&gt; &gt; &nbsp;&gt; Allocation of an Generic Associated Channel Type for
ITU-T<br>
&gt; &gt; &nbsp;&gt; MPLS Transport Profile Operation, Maintenance and
Administration.<br>
&gt; &gt; &nbsp;&gt;<br>
&gt; &gt;<br>
&gt; &gt; MB: No objection to this change<br>
&gt; &gt;<br>
&gt; &gt; &nbsp;&gt;<br>
&gt; &gt; &nbsp;&gt; Introduction - first paragraph<br>
&gt; &gt; &nbsp;&gt; ==============================<br>
&gt; &gt; &nbsp;&gt;<br>
&gt; &gt; &nbsp;&gt; In the first paragraph of the introduction, there
seems to be an<br>
&gt; &gt; &nbsp;&gt; oddity in the description of the role of the ietf-tp-oam-analysis<br>
&gt; &gt; &nbsp;&gt; document. Instead of:<br>
&gt; &gt; &nbsp;&gt;<br>
&gt; &gt; &nbsp;&gt; OLD<br>
&gt; &gt; &nbsp;&gt; &quot;tools defined by the IETF [I-D.ietf-mpls-tp-oam-analysis],
that<br>
&gt; &gt; &nbsp;&gt; are intended to meet the OAM functional requirements
defined in<br>
&gt; &gt; &nbsp;&gt; [RFC5860].&quot;<br>
&gt; &gt; &nbsp;&gt;<br>
&gt; &gt; &nbsp;&gt; NEW:<br>
&gt; &gt; &nbsp;&gt; &quot;tools described by the IETF [I-D.ietf-mpls-tp-oam-analysis],
which<br>
&gt; &gt; &nbsp;&gt; are used to meet the OAM functional requirements defined<br>
&gt; &gt; &nbsp;&gt; in [RFC5860].&quot;<br>
&gt; &gt;<br>
&gt; &gt; MB: No objection to this change<br>
&gt; &gt;<br>
&gt; &gt; &nbsp;&gt;<br>
&gt; &gt; &nbsp;&gt; Intrduction - second paragraph<br>
&gt; &gt; &nbsp;&gt; ==============================<br>
&gt; &gt; &nbsp;&gt;<br>
&gt; &gt; &nbsp;&gt; The next paragraph in describing G.8113.1, stumbles
over the current<br>
&gt; &gt; &nbsp;&gt; vs anticipated future state of G.8113.1 and its relationship
to<br>
&gt; &gt; &nbsp;&gt; its antecedents. I'm a bit un-certain about the correct
terminology,<br>
&gt; &gt; &nbsp;&gt; but I think the following change would improve the
document.<br>
&gt; &gt; &nbsp;&gt;<br>
&gt; &gt; &nbsp;&gt; OLD:<br>
&gt; &gt; &nbsp;&gt;<br>
&gt; &gt; &nbsp;&gt; The ITU-T has documented, in draft new Recommendation
[G.8113.1], the<br>
&gt; &gt; &nbsp;&gt; use of Ethernet based OAM mechanisms, originally defined
in [Y.1731],<br>
&gt; &gt; &nbsp;&gt; carried in the MPLS Generic Associated Channel (G-ACh).
This approach<br>
&gt; &gt; &nbsp;&gt; requires the allocation of an ACH Type from the registry
of ACH types<br>
&gt; &gt; &nbsp;&gt; maintained by IANA in order that the messages that
will be described<br>
&gt; &gt; &nbsp;&gt; in [G.8113.1] can be identified by an implementation.<br>
&gt; &gt; &nbsp;&gt;<br>
&gt; &gt; &nbsp;&gt; NEW:<br>
&gt; &gt; &nbsp;&gt;<br>
&gt; &gt; &nbsp;&gt; &quot;The ITU-T has Draft Recommendation [G.8113.1]
documented MPLS OAM<br>
&gt; &gt; &nbsp;&gt; which as of this writing is undergoing the ITU-T Traditional<br>
&gt; &gt; &nbsp;&gt; Approval Process (TAP). This Recommendation builds
upon Ethernet<br>
&gt; &gt; &nbsp;&gt; OAM as documented in [Y.1731]. The messages in [G.8113.1]
are defined<br>
&gt; &gt; &nbsp;&gt; to be carried in a new Associated Channel Type in
the MPLS Generaic<br>
&gt; &gt; &nbsp;&gt; Associated Channel (G-Ach). In order to carry these
messages in an<br>
&gt; &gt; &nbsp;&gt; interoperable fashion, an Associated Channel Type
from the IANA<br>
&gt; &gt; &nbsp;&gt; maintained registry &quot;Pseudowire Associated Channel
Types is to be<br>
&gt; &gt; &nbsp;&gt; used.&quot;<br>
&gt; &gt;<br>
&gt; &gt; MB: Since the draft will not be published as an RFC until after
G.8113.1<br>
&gt; &gt; is approved we can directly reference the approved Recommendation
and I<br>
&gt; &gt; suggest that we modify paragraph to:<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; ITU-T Recommendation [G.8113.1] documents MPLS OAM. This Recommendation<br>
&gt; &gt; builds upon Ethernet OAM as documented in [Y.1731]. The messages
in<br>
&gt; &gt; [G.8113.1] are defined to be carried in a new Associated Channel
Type in<br>
&gt; &gt; the MPLS Generaic Associated Channel (G-Ach). In order to carry
these<br>
&gt; &gt; messages in an interoperable fashion, an Associated Channel Type
from<br>
&gt; &gt; the IANA maintained registry &quot;Pseudowire Associated Channel
Types is to<br>
&gt; &gt; be used.&quot;<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; &nbsp;&gt;<br>
&gt; &gt; &nbsp;&gt; Note there are confusion around some of the Associated
Channel<br>
&gt; &gt; &nbsp;&gt; acronyms that are refledted in this document.<br>
&gt; &gt; &nbsp;&gt;<br>
&gt; &gt; &nbsp;&gt; ACh is Associated Channel<br>
&gt; &gt; &nbsp;&gt; ACH is Associated Chamnnel Header<br>
&gt; &gt; &nbsp;&gt; G-ACh is Generic Associated Channel<br>
&gt; &gt; &nbsp;&gt;<br>
&gt; &gt; &nbsp;&gt; &quot;ACH Type&quot; is not used anywhere in IETF
documents; we talk about<br>
&gt; &gt; &nbsp;&gt; Associated Channel Type or Generic Associated Channel
Type<br>
&gt; &gt; &nbsp;&gt; (G-ACh Type).<br>
&gt; &gt;<br>
&gt; &gt; MB: Thank you, I will fix this.<br>
&gt; &gt;<br>
&gt; &gt; &nbsp;&gt;<br>
&gt; &gt; &nbsp;&gt; Introduction - third paragraph<br>
&gt; &gt; &nbsp;&gt; ==============================<br>
&gt; &gt; &nbsp;&gt;<br>
&gt; &gt; &nbsp;&gt; In the third paragraph, there seems to be an unnecessary
reference<br>
&gt; &gt; &nbsp;&gt; to experimental types. When asking for a code point
for a standard,<br>
&gt; &gt; &nbsp;&gt; it is not helped to bring up experimental code space.
Can we remove<br>
&gt; &gt; &nbsp;&gt; the text reading:<br>
&gt; &gt; &nbsp;&gt;<br>
&gt; &gt; &nbsp;&gt; OLD:<br>
&gt; &gt; &nbsp;&gt; &quot;without continuing to resorting to the use of
an experimental<br>
&gt; &gt; &nbsp;&gt; ACH Type,&quot;<br>
&gt; &gt; &nbsp;&gt;<br>
&gt; &gt; &nbsp;&gt; NEW<br>
&gt; &gt; &nbsp;&gt; -<br>
&gt; &gt;<br>
&gt; &gt; MB: I do not agree with the deletion of this text, these existing<br>
&gt; &gt; deployments, and the desire to migrate to an allocated code point,
are<br>
&gt; &gt; part of the rational for requesting the code point.<br>
&gt; &gt;<br>
&gt; &gt; &nbsp;&gt;<br>
&gt; &gt; &nbsp;&gt;<br>
&gt; &gt; &nbsp;&gt; Section 2 - first paragraph<br>
&gt; &gt; &nbsp;&gt; ===========================<br>
&gt; &gt; &nbsp;&gt;<br>
&gt; &gt; &nbsp;&gt;<br>
&gt; &gt; &nbsp;&gt;<br>
&gt; &gt; &nbsp;&gt; In section 2, the first sentence refers to Ethernet
based OAM<br>
&gt; &gt; &nbsp;&gt; messages. As far as I know, the messages in G.8113.1
are either<br>
&gt; &gt; &nbsp;&gt; MPLS-TP OAM messages, or they are simply the OAM messages
defined<br>
&gt; &gt; &nbsp;&gt; in G.8113.1. The simplest path to clarity would seem
to be to<br>
&gt; &gt; &nbsp;&gt; replace &quot;Ethernet based OAM messages&quot; in
that sentence with<br>
&gt; &gt; &nbsp;&gt; &quot;messages&quot;.<br>
&gt; &gt; &nbsp;&gt;<br>
&gt; &gt; &nbsp;&gt; The second sentence of that paragraph does not seem
to say anything<br>
&gt; &gt; &nbsp;&gt; we need to say. Can we remove it?<br>
&gt; &gt; &nbsp;&gt;<br>
&gt; &gt; &nbsp;&gt; OLD:<br>
&gt; &gt; &nbsp;&gt;<br>
&gt; &gt; &nbsp;&gt; The code point allocated by this document is intended
to be used only<br>
&gt; &gt; &nbsp;&gt; for Ethernet based OAM messages, defined in the ITU-T
Recommendation<br>
&gt; &gt; &nbsp;&gt; [G.8113.1], carried in the G-ACh . These Ethernet
based OAM messages<br>
&gt; &gt; &nbsp;&gt; and procedures, address the OAM functional requirements
defined in<br>
&gt; &gt; &nbsp;&gt; [RFC5860]. Other message types should not be carried
behind this code<br>
&gt; &gt; &nbsp;&gt; point.<br>
&gt; &gt; &nbsp;&gt;<br>
&gt; &gt; &nbsp;&gt; NEW:<br>
&gt; &gt; &nbsp;&gt;<br>
&gt; &gt; &nbsp;&gt; The code point allocated by this document is intended
to be used<br>
&gt; &gt; &nbsp;&gt; only for OAM messages, defined in the ITU-T Recommendation<br>
&gt; &gt; &nbsp;&gt; [G.8113.1], carried in the G-ACh . Other message types
should not<br>
&gt; &gt; &nbsp;&gt; be carried behind this Associated Channel Type.<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; MB: I do not agree with this proposed change. Other comments
request<br>
&gt; &gt; that the restriction on the applicability of the code point is<br>
&gt; &gt; strengthened so I propose the following:<br>
&gt; &gt;<br>
&gt; &gt; The code point allocated by this document should only be used
for OAM<br>
&gt; &gt; messages, defined in the ITU-T Recommendation [G.8113.1], carried
in the<br>
&gt; &gt; G-ACh. The messages and procedures carried behind this code point,
are<br>
&gt; &gt; restricted to only those that the address the OAM functional<br>
&gt; &gt; requirements defined in [RFC5860]. Other message types should
not be<br>
&gt; &gt; carried behind this code point.<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; &nbsp;&gt;<br>
&gt; &gt; &nbsp;&gt; Section 2 - second paragraph<br>
&gt; &gt; &nbsp;&gt; ============================<br>
&gt; &gt; &nbsp;&gt;<br>
&gt; &gt; &nbsp;&gt; A matter of some clarity, can we change this paragrap
like this:<br>
&gt; &gt; &nbsp;&gt;<br>
&gt; &gt; &nbsp;&gt; OLD:<br>
&gt; &gt; &nbsp;&gt; This code point may be used on any transport construct
that uses<br>
&gt; &gt; &nbsp;&gt; the G-ACh, e.g., MPLS-TP Sections, MPLS-TP LSPs or
PWs.<br>
&gt; &gt; &nbsp;&gt;<br>
&gt; &gt; &nbsp;&gt; NEW:<br>
&gt; &gt; &nbsp;&gt;<br>
&gt; &gt; &nbsp;&gt; The Generic Associated Channel Type assigned by this<br>
&gt; &gt; &nbsp;&gt; document may be used on any transport construct that
uses the<br>
&gt; &gt; &nbsp;&gt; G-ACh, e.g., MPLS-TP Sections, MPLS-TP LSPs or PWs
as specified<br>
&gt; &gt; &nbsp;&gt; by G.8113.1.<br>
&gt; &gt;<br>
&gt; &gt; MB: No objection to this change.<br>
&gt; &gt;<br>
&gt; &gt; &nbsp;&gt;<br>
&gt; &gt; &nbsp;&gt;<br>
&gt; &gt; &nbsp;&gt; Section 2 - third paragraph<br>
&gt; &gt; &nbsp;&gt; ===========================<br>
&gt; &gt; &nbsp;&gt;<br>
&gt; &gt; &nbsp;&gt; With regard to revisions, which is what I think the
third paragraph<br>
&gt; &gt; &nbsp;&gt; is about, I am not clear what you are trying to say.
A code point<br>
&gt; &gt; &nbsp;&gt; allocation must point to a stable referent. If the
desired referent<br>
&gt; &gt; &nbsp;&gt; changes, then process needs to be followed to make
sure that the IANA<br>
&gt; &gt; &nbsp;&gt; is updated in accordance with IETF procedures. Hence,
I am left to<br>
&gt; &gt; &nbsp;&gt; the conclusion that the third paragraph is actually
asking for<br>
&gt; &gt; &nbsp;&gt; something we can not do. Can we remove that?<br>
&gt; &gt; &nbsp;&gt;<br>
&gt; &gt; &nbsp;&gt; OLD:<br>
&gt; &gt; &nbsp;&gt; All ITU-T Recommendations are subject to revisions.
Therefore, the<br>
&gt; &gt; &nbsp;&gt; code point allocated by this document may be used
for future versions<br>
&gt; &gt; &nbsp;&gt; of [G.8113.1].<br>
&gt; &gt; &nbsp;&gt;<br>
&gt; &gt; &nbsp;&gt; NEW:<br>
&gt; &gt; &nbsp;&gt; -<br>
&gt; &gt; &nbsp;&gt;<br>
&gt; &gt; &nbsp;&gt;<br>
&gt; &gt;<br>
&gt; &gt; MB: I do not agree with the removal of this text:<br>
&gt; &gt;<br>
&gt; &gt; The intention of this statement is to bring to the attention
of the IETF<br>
&gt; &gt; the normal practice in the ITU of developing amendments to<br>
&gt; &gt; Recommendations to fully meet the functional requirements (e.g.
adding<br>
&gt; &gt; pro-active loss measurement). Normally any reference to ITU-T
Rec<br>
&gt; &gt; G.8113.1 will automatically be directed to the current version<br>
&gt; &gt; (including any amendments).<br>
&gt; &gt;<br>
&gt; &gt; Only those interfaces that support G.8113.1 OAM will act on these
OAM<br>
&gt; &gt; messages, any interface that does not support this G-ACh type
will<br>
&gt; &gt; discard these OAM messages as defined in RFC5586.<br>
&gt; &gt;<br>
&gt; &gt; Restricting the application of the code point to a specific version
of<br>
&gt; &gt; Recommendation G.8113.1 would require the ITU to deviate from
its normal<br>
&gt; &gt; process for enhancing Recommendations and would put the IETF
back into<br>
&gt; &gt; the discussion for approval.<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; &nbsp;&gt;---------------snip<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; &nbsp;&gt;<br>
&gt; &gt; &nbsp;&gt; Loa Andersson email: loa.andersson@ericsson.com<br>
&gt; &gt; &nbsp;&gt; Sr Strategy and Standards Manager loa@pi.nu<br>
&gt; &gt; &nbsp;&gt; Ericsson Inc phone: +46 10 717 52 13<br>
&gt; &gt; &nbsp;&gt; +46 767 72 92 13<br>
&gt; &gt; &nbsp;&gt; _______________________________________________<br>
&gt; &gt; &nbsp;&gt; Ietf mailing list<br>
&gt; &gt; &nbsp;&gt; Ietf@ietf.org<br>
&gt; &gt; &nbsp;&gt; </font></tt><a href=https://www.ietf.org/mailman/listinfo/ietf><tt><font size=2>https://www.ietf.org/mailman/listinfo/ietf</font></tt></a><tt><font size=2><br>
&gt; &gt; &nbsp;&gt;<br>
&gt;<br>
&gt; --<br>
&gt;<br>
&gt;<br>
&gt; Loa Andersson &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; email: loa.andersson@ericsson.com<br>
&gt; Sr Strategy and Standards Manager &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp;loa@pi.nu<br>
&gt; Ericsson Inc &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;phone: +46 10 717 52 13<br>
&gt; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; +46 767 72 92 13<br>
&gt;<br>
&gt;<br>
<br>
<br>
</font></tt>
<br>
--=_alternative 00560271852579CA_=--


From rcallon@juniper.net  Fri Mar 23 08:47:04 2012
Return-Path: <rcallon@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 04C8021F8597 for <ietf@ietfa.amsl.com>; Fri, 23 Mar 2012 08:47:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.282
X-Spam-Level: 
X-Spam-Status: No, score=-106.282 tagged_above=-999 required=5 tests=[AWL=-0.284, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_15=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 R4QOQlZv74kj for <ietf@ietfa.amsl.com>; Fri, 23 Mar 2012 08:46:59 -0700 (PDT)
Received: from exprod7og107.obsmtp.com (exprod7og107.obsmtp.com [64.18.2.167]) by ietfa.amsl.com (Postfix) with ESMTP id 3FD8B21F858A for <ietf@ietf.org>; Fri, 23 Mar 2012 08:46:55 -0700 (PDT)
Received: from P-EMHUB02-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob107.postini.com ([64.18.6.12]) with SMTP ID DSNKT2ya7jIYvh+MikS5tu/hcJby3KrXPBru@postini.com; Fri, 23 Mar 2012 08:46:59 PDT
Received: from p-emfe02-wf.jnpr.net (172.28.145.25) by P-EMHUB02-HQ.jnpr.net (172.24.192.36) with Microsoft SMTP Server (TLS) id 8.3.213.0; Fri, 23 Mar 2012 08:46:28 -0700
Received: from EMBX01-WF.jnpr.net ([fe80::1914:3299:33d9:e43b]) by p-emfe02-wf.jnpr.net ([fe80::c126:c633:d2dc:8090%11]) with mapi; Fri, 23 Mar 2012 11:46:28 -0400
From: Ross Callon <rcallon@juniper.net>
To: "Malcolm.BETTS@zte.com.cn" <Malcolm.BETTS@zte.com.cn>, t.petch <daedulus@btconnect.com>
Date: Fri, 23 Mar 2012 11:45:52 -0400
Subject: RE: [PWE3] FW:	LastCall: <draft-betts-itu-oam-ach-code-point-03.txt>(Allocationof	an Associated Channel Code Point for Use byITU-T Ethernet	basedOAM)	to	Informational RFC
Thread-Topic: [PWE3] FW:	LastCall: <draft-betts-itu-oam-ach-code-point-03.txt>(Allocationof	an Associated Channel Code Point for Use byITU-T Ethernet	basedOAM)	to	Informational RFC
Thread-Index: Ac0JCzjLdgmxPpxMT8q/F/y6xkQYzgAADkQQ
Message-ID: <DF7F294AF4153D498141CBEFADB17704C70D0DB7B1@EMBX01-WF.jnpr.net>
References: <20120222151252.32262.82157.idtracker@ietfa.amsl.com> <039f01ccf174$fe79d780$fb6d8680$@olddog.co.uk><44F4E579A764584EA9BDFD07D0CA0813075C936F@tlvmail1> <4F4B7EA2.7070305@cisco.com><4F4B8A75.6000207@pi.nu> <4F5DB46F.10009@pi.nu><OFE57A943C.CA873F89-ON852579C8.006D6B01-852579C8.0070E507@zte.com.cn> <4F6C460F.4080007@pi.nu>	<00b801cd08da$6885bbe0$4001a8c0@gateway.2wire.net> <OFFF023599.28F45CA8-ON852579CA.0055A56A-852579CA.00560272@zte.com.cn>
In-Reply-To: <OFFF023599.28F45CA8-ON852579CA.0055A56A-852579CA.00560272@zte.com.cn>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_DF7F294AF4153D498141CBEFADB17704C70D0DB7B1EMBX01WFjnprn_"
MIME-Version: 1.0
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Mar 2012 15:47:04 -0000

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

A current AD might take precedence over a past one, but back when I was on =
the IESG we twice had discussions of the use of RFC2119 keywords in informa=
tional track documents. Both times we fortunately came to the same conclusi=
on - that it is fine to use RFC2119 keywords in informational (or experimen=
tal) RFCs.

Ross

From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of Mal=
colm.BETTS@zte.com.cn
Sent: Friday, March 23, 2012 11:39 AM
To: t.petch
Cc: ietf@ietf.org
Subject: Re: [PWE3] FW: LastCall: <draft-betts-itu-oam-ach-code-point-03.tx=
t>(Allocationof an Associated Channel Code Point for Use byITU-T Ethernet b=
asedOAM) to Informational RFC

Tom,

I have no objections to using the RFC 2119 key words, I am not sure if that=
 is appropriate in an informational track document, I expect that our AD wi=
ll provide some guidance.

Regards,

Malcolm


"t.petch" <daedulus@btconnect.com>

23/03/2012 05:50 AM

To

"Loa Andersson" <loa@pi.nu>, <Malcolm.BETTS@zte.com.cn>

cc

<ietf@ietf.org>

Subject

Re: [PWE3] FW: LastCall:        <draft-betts-itu-oam-ach-code-point-03.txt>=
(Allocationof        an Associated Channel Code Point for Use byITU-T Ether=
net        basedOAM)        to Informational RFC







Loa

The one point that jumps out at me is the proposed text
"Other message types should not be carried behind this code point."
or should that be
"Other message types SHOULD NOT be carried behind this code point."
which, in IETF-Land, is a bit different.

I prefer the latter.

Tom Petch


----- Original Message -----
From: "Loa Andersson" <loa@pi.nu>
To: <Malcolm.BETTS@zte.com.cn>
Cc: <ietf@ietf.org>
Sent: Friday, March 23, 2012 10:44 AM
Subject: Re: [PWE3] FW: LastCall:
<draft-betts-itu-oam-ach-code-point-03.txt>(Allocationof an Associated Chan=
nel
Code Point for Use byITU-T Ethernet basedOAM) to Informational RFC


> Malcolm,
>
> good that we are making some progress!
>
> On the experimental code point
> ------------------------------
>
> I doesn't seem appropriate to call out the fact that some commercial
> products has been using an experimental code point in production
> setting!
>
> On the remain (key) disagreements
> ---------------------------------
>
> I will let other people comment for now.
>
>
> /Loa
>
> On 2012-03-21 21:33, Malcolm.BETTS@zte.com.cn wrote:
> > Loa,
> >
> > Thank you for your comments and suggestions, please see in line below.
> >
> > Regards,
> >
> > Malcolm
> >
> >
> > ietf-bounces@ietf.org wrote on 12/03/2012 04:31:43 AM:
> >
> >  > Loa Andersson <loa@pi.nu>
> >  > Sent by: ietf-bounces@ietf.org
> >  >
> >  > 12/03/2012 04:31 AM
> >  >
> >  > To
> >  >
> >  > ietf@ietf.org
> >  >
> >  > cc
> >  >
> >  > Subject
> >  >
> >  > Re: [PWE3] FW: Last Call: <draft-betts-itu-oam-ach-code-
> >  > point-03.txt>(Allocation of an Associated Channel Code Point for Use
> >  > byITU-T Ethernet based OAM) to Informational RFC
> >  >
> >  > All,
> >  >
> >  > I've been asked to clarify thee comments in this mail, I done
> >  > so by proposing new text to draft-betts-.
> >  >
> >  > I hope this helps.
> >  >
> >  >
> >  > Title
> >  > =3D=3D=3D=3D=3D
> >  >
> >  > Comment: We want to assign a Associated Channel Type. The registry
> >  > that it will be assigned from is "Pseudowire Associated Channel
> >  > Types"; however RFC 5586, makes the Channel Types generic and I
> >  > think the title should be changed as follows:
> >  >
> >  > OLD:
> >  > Allocation of an Associated Channel Code Point for Use by ITU-T
> >  > Ethernet based OAM
> >  >
> >  > NEW:
> >  > Allocation of an Generic Associated Channel Type for ITU-T
> >  > MPLS-TP OAM
> >  >
> >  > Note: Neither MPLS-TP or OAM are in the RFC Editors list of wellknow=
n
> >  > acronyms, therfore the title probably should be:
> >  >
> >  > NEW:
> >  > Allocation of an Generic Associated Channel Type for ITU-T
> >  > MPLS Transport Profile Operation, Maintenance and Administration.
> >  >
> >
> > MB: No objection to this change
> >
> >  >
> >  > Introduction - first paragraph
> >  > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D
> >  >
> >  > In the first paragraph of the introduction, there seems to be an
> >  > oddity in the description of the role of the ietf-tp-oam-analysis
> >  > document. Instead of:
> >  >
> >  > OLD
> >  > "tools defined by the IETF [I-D.ietf-mpls-tp-oam-analysis], that
> >  > are intended to meet the OAM functional requirements defined in
> >  > [RFC5860]."
> >  >
> >  > NEW:
> >  > "tools described by the IETF [I-D.ietf-mpls-tp-oam-analysis], which
> >  > are used to meet the OAM functional requirements defined
> >  > in [RFC5860]."
> >
> > MB: No objection to this change
> >
> >  >
> >  > Intrduction - second paragraph
> >  > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D
> >  >
> >  > The next paragraph in describing G.8113.1, stumbles over the current
> >  > vs anticipated future state of G.8113.1 and its relationship to
> >  > its antecedents. I'm a bit un-certain about the correct terminology,
> >  > but I think the following change would improve the document.
> >  >
> >  > OLD:
> >  >
> >  > The ITU-T has documented, in draft new Recommendation [G.8113.1], th=
e
> >  > use of Ethernet based OAM mechanisms, originally defined in [Y.1731]=
,
> >  > carried in the MPLS Generic Associated Channel (G-ACh). This approac=
h
> >  > requires the allocation of an ACH Type from the registry of ACH type=
s
> >  > maintained by IANA in order that the messages that will be described
> >  > in [G.8113.1] can be identified by an implementation.
> >  >
> >  > NEW:
> >  >
> >  > "The ITU-T has Draft Recommendation [G.8113.1] documented MPLS OAM
> >  > which as of this writing is undergoing the ITU-T Traditional
> >  > Approval Process (TAP). This Recommendation builds upon Ethernet
> >  > OAM as documented in [Y.1731]. The messages in [G.8113.1] are define=
d
> >  > to be carried in a new Associated Channel Type in the MPLS Generaic
> >  > Associated Channel (G-Ach). In order to carry these messages in an
> >  > interoperable fashion, an Associated Channel Type from the IANA
> >  > maintained registry "Pseudowire Associated Channel Types is to be
> >  > used."
> >
> > MB: Since the draft will not be published as an RFC until after G.8113.=
1
> > is approved we can directly reference the approved Recommendation and I
> > suggest that we modify paragraph to:
> >
> >
> > ITU-T Recommendation [G.8113.1] documents MPLS OAM. This Recommendation
> > builds upon Ethernet OAM as documented in [Y.1731]. The messages in
> > [G.8113.1] are defined to be carried in a new Associated Channel Type i=
n
> > the MPLS Generaic Associated Channel (G-Ach). In order to carry these
> > messages in an interoperable fashion, an Associated Channel Type from
> > the IANA maintained registry "Pseudowire Associated Channel Types is to
> > be used."
> >
> >
> >  >
> >  > Note there are confusion around some of the Associated Channel
> >  > acronyms that are refledted in this document.
> >  >
> >  > ACh is Associated Channel
> >  > ACH is Associated Chamnnel Header
> >  > G-ACh is Generic Associated Channel
> >  >
> >  > "ACH Type" is not used anywhere in IETF documents; we talk about
> >  > Associated Channel Type or Generic Associated Channel Type
> >  > (G-ACh Type).
> >
> > MB: Thank you, I will fix this.
> >
> >  >
> >  > Introduction - third paragraph
> >  > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D
> >  >
> >  > In the third paragraph, there seems to be an unnecessary reference
> >  > to experimental types. When asking for a code point for a standard,
> >  > it is not helped to bring up experimental code space. Can we remove
> >  > the text reading:
> >  >
> >  > OLD:
> >  > "without continuing to resorting to the use of an experimental
> >  > ACH Type,"
> >  >
> >  > NEW
> >  > -
> >
> > MB: I do not agree with the deletion of this text, these existing
> > deployments, and the desire to migrate to an allocated code point, are
> > part of the rational for requesting the code point.
> >
> >  >
> >  >
> >  > Section 2 - first paragraph
> >  > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D
> >  >
> >  >
> >  >
> >  > In section 2, the first sentence refers to Ethernet based OAM
> >  > messages. As far as I know, the messages in G.8113.1 are either
> >  > MPLS-TP OAM messages, or they are simply the OAM messages defined
> >  > in G.8113.1. The simplest path to clarity would seem to be to
> >  > replace "Ethernet based OAM messages" in that sentence with
> >  > "messages".
> >  >
> >  > The second sentence of that paragraph does not seem to say anything
> >  > we need to say. Can we remove it?
> >  >
> >  > OLD:
> >  >
> >  > The code point allocated by this document is intended to be used onl=
y
> >  > for Ethernet based OAM messages, defined in the ITU-T Recommendation
> >  > [G.8113.1], carried in the G-ACh . These Ethernet based OAM messages
> >  > and procedures, address the OAM functional requirements defined in
> >  > [RFC5860]. Other message types should not be carried behind this cod=
e
> >  > point.
> >  >
> >  > NEW:
> >  >
> >  > The code point allocated by this document is intended to be used
> >  > only for OAM messages, defined in the ITU-T Recommendation
> >  > [G.8113.1], carried in the G-ACh . Other message types should not
> >  > be carried behind this Associated Channel Type.
> >
> >
> > MB: I do not agree with this proposed change. Other comments request
> > that the restriction on the applicability of the code point is
> > strengthened so I propose the following:
> >
> > The code point allocated by this document should only be used for OAM
> > messages, defined in the ITU-T Recommendation [G.8113.1], carried in th=
e
> > G-ACh. The messages and procedures carried behind this code point, are
> > restricted to only those that the address the OAM functional
> > requirements defined in [RFC5860]. Other message types should not be
> > carried behind this code point.
> >
> >
> >  >
> >  > Section 2 - second paragraph
> >  > =3D=3D=3D=3D=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 matter of some clarity, can we change this paragrap like this:
> >  >
> >  > OLD:
> >  > This code point may be used on any transport construct that uses
> >  > the G-ACh, e.g., MPLS-TP Sections, MPLS-TP LSPs or PWs.
> >  >
> >  > NEW:
> >  >
> >  > The Generic Associated Channel Type assigned by this
> >  > document may be used on any transport construct that uses the
> >  > G-ACh, e.g., MPLS-TP Sections, MPLS-TP LSPs or PWs as specified
> >  > by G.8113.1.
> >
> > MB: No objection to this change.
> >
> >  >
> >  >
> >  > Section 2 - third paragraph
> >  > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D
> >  >
> >  > With regard to revisions, which is what I think the third paragraph
> >  > is about, I am not clear what you are trying to say. A code point
> >  > allocation must point to a stable referent. If the desired referent
> >  > changes, then process needs to be followed to make sure that the IAN=
A
> >  > is updated in accordance with IETF procedures. Hence, I am left to
> >  > the conclusion that the third paragraph is actually asking for
> >  > something we can not do. Can we remove that?
> >  >
> >  > OLD:
> >  > All ITU-T Recommendations are subject to revisions. Therefore, the
> >  > code point allocated by this document may be used for future version=
s
> >  > of [G.8113.1].
> >  >
> >  > NEW:
> >  > -
> >  >
> >  >
> >
> > MB: I do not agree with the removal of this text:
> >
> > The intention of this statement is to bring to the attention of the IET=
F
> > the normal practice in the ITU of developing amendments to
> > Recommendations to fully meet the functional requirements (e.g. adding
> > pro-active loss measurement). Normally any reference to ITU-T Rec
> > G.8113.1 will automatically be directed to the current version
> > (including any amendments).
> >
> > Only those interfaces that support G.8113.1 OAM will act on these OAM
> > messages, any interface that does not support this G-ACh type will
> > discard these OAM messages as defined in RFC5586.
> >
> > Restricting the application of the code point to a specific version of
> > Recommendation G.8113.1 would require the ITU to deviate from its norma=
l
> > process for enhancing Recommendations and would put the IETF back into
> > the discussion for approval.
> >
> >
> >
> >  >---------------snip
> >
> >
> >  >
> >  > 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
> >  > _______________________________________________
> >  > Ietf mailing list
> >  > Ietf@ietf.org
> >  > https://www.ietf.org/mailman/listinfo/ietf
> >  >
>
> --
>
>
> 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
>
>



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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40"><head><meta http-equiv=3DContent-Type content=
=3D"text/html; charset=3Dus-ascii"><meta name=3DGenerator content=3D"Micros=
oft Word 12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
tt
	{mso-style-priority:99;
	font-family:"Courier New";}
span.EmailStyle19
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.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 vli=
nk=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span style=3D'f=
ont-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>A current=
 AD might take precedence over a past one, but back when I was on the IESG =
we twice had discussions of the use of RFC2119 keywords in informational tr=
ack documents. Both times we fortunately came to the same conclusion &#8211=
; that it is fine to use RFC2119 keywords in informational (or experimental=
) RFCs. <o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size=
:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p>&nbsp;</o:p>=
</span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family=
:"Calibri","sans-serif";color:#1F497D'>Ross<o:p></o:p></span></p><p class=
=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri","sans-se=
rif";color:#1F497D'><o:p>&nbsp;</o:p></span></p><div style=3D'border:none;b=
order-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNorm=
al><b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>Fr=
om:</span></b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-se=
rif"'> ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] <b>On Behalf Of=
 </b>Malcolm.BETTS@zte.com.cn<br><b>Sent:</b> Friday, March 23, 2012 11:39 =
AM<br><b>To:</b> t.petch<br><b>Cc:</b> ietf@ietf.org<br><b>Subject:</b> Re:=
 [PWE3] FW: LastCall: &lt;draft-betts-itu-oam-ach-code-point-03.txt&gt;(All=
ocationof an Associated Channel Code Point for Use byITU-T Ethernet basedOA=
M) to Informational RFC<o:p></o:p></span></p></div><p class=3DMsoNormal><o:=
p>&nbsp;</o:p></p><p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><span=
 style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'>Tom,</span> <b=
r><br><span style=3D'font-size:10.0pt;font-family:"Arial","sans-serif"'>I h=
ave no objections to using the RFC 2119 key words, I am not sure if that is=
 appropriate in an informational track document, I expect that our AD will =
provide some guidance.</span> <br><br><span style=3D'font-size:10.0pt;font-=
family:"Arial","sans-serif"'>Regards,</span> <br><br><span style=3D'font-si=
ze:10.0pt;font-family:"Arial","sans-serif"'>Malcolm</span> <br><br><br><o:p=
></o:p></p><table class=3DMsoNormalTable border=3D0 cellpadding=3D0 width=
=3D"100%" style=3D'width:100.0%'><tr><td width=3D"36%" valign=3Dtop style=
=3D'width:36.0%;padding:.75pt .75pt .75pt .75pt'><p class=3DMsoNormal><b><s=
pan style=3D'font-size:7.5pt;font-family:"Arial","sans-serif"'>&quot;t.petc=
h&quot; &lt;daedulus@btconnect.com&gt;</span></b><span style=3D'font-size:7=
.5pt;font-family:"Arial","sans-serif"'> </span><o:p></o:p></p><p><span styl=
e=3D'font-size:7.5pt;font-family:"Arial","sans-serif"'>23/03/2012 05:50 AM<=
/span> <o:p></o:p></p></td><td width=3D"63%" valign=3Dtop style=3D'width:63=
.0%;padding:.75pt .75pt .75pt .75pt'><table class=3DMsoNormalTable border=
=3D0 cellpadding=3D0 width=3D"100%" style=3D'width:100.0%'><tr><td valign=
=3Dtop style=3D'padding:.75pt .75pt .75pt .75pt'><p class=3DMsoNormal align=
=3Dright style=3D'text-align:right'><span style=3D'font-size:7.5pt;font-fam=
ily:"Arial","sans-serif"'>To</span><o:p></o:p></p></td><td valign=3Dtop sty=
le=3D'padding:.75pt .75pt .75pt .75pt'><p class=3DMsoNormal><span style=3D'=
font-size:7.5pt;font-family:"Arial","sans-serif"'>&quot;Loa Andersson&quot;=
 &lt;loa@pi.nu&gt;, &lt;Malcolm.BETTS@zte.com.cn&gt;</span> <o:p></o:p></p>=
</td></tr><tr><td valign=3Dtop style=3D'padding:.75pt .75pt .75pt .75pt'><p=
 class=3DMsoNormal align=3Dright style=3D'text-align:right'><span style=3D'=
font-size:7.5pt;font-family:"Arial","sans-serif"'>cc</span><o:p></o:p></p><=
/td><td valign=3Dtop style=3D'padding:.75pt .75pt .75pt .75pt'><p class=3DM=
soNormal><span style=3D'font-size:7.5pt;font-family:"Arial","sans-serif"'>&=
lt;ietf@ietf.org&gt;</span> <o:p></o:p></p></td></tr><tr><td valign=3Dtop s=
tyle=3D'padding:.75pt .75pt .75pt .75pt'><p class=3DMsoNormal align=3Dright=
 style=3D'text-align:right'><span style=3D'font-size:7.5pt;font-family:"Ari=
al","sans-serif"'>Subject</span><o:p></o:p></p></td><td valign=3Dtop style=
=3D'padding:.75pt .75pt .75pt .75pt'><p class=3DMsoNormal><span style=3D'fo=
nt-size:7.5pt;font-family:"Arial","sans-serif"'>Re: [PWE3] FW: LastCall: &n=
bsp; &nbsp; &nbsp; &nbsp;&lt;draft-betts-itu-oam-ach-code-point-03.txt&gt;(=
Allocationof &nbsp; &nbsp; &nbsp; &nbsp;an Associated Channel Code Point fo=
r Use byITU-T Ethernet &nbsp; &nbsp; &nbsp; &nbsp;basedOAM) &nbsp; &nbsp; &=
nbsp; &nbsp;to Informational RFC</span><o:p></o:p></p></td></tr></table><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><table class=3DMsoNormalTable border=
=3D0 cellpadding=3D0><tr><td valign=3Dtop style=3D'padding:.75pt .75pt .75p=
t .75pt'></td><td valign=3Dtop style=3D'padding:.75pt .75pt .75pt .75pt'></=
td></tr></table></td></tr></table><p class=3DMsoNormal style=3D'margin-bott=
om:12.0pt'><br><br><br><tt><span style=3D'font-size:10.0pt'>Loa</span></tt>=
<span style=3D'font-size:10.0pt;font-family:"Courier New"'><br><br><tt>The =
one point that jumps out at me is the proposed text</tt><br><tt>&quot;Other=
 message types should not be carried behind this code point.&quot;</tt><br>=
<tt>or should that be</tt><br><tt>&quot;Other message types SHOULD NOT be c=
arried behind this code point.&quot;</tt><br><tt>which, in IETF-Land, is a =
bit different.</tt><br><br><tt>I prefer the latter.</tt><br><br><tt>Tom Pet=
ch</tt><br><br><br><tt>----- Original Message -----</tt><br><tt>From: &quot=
;Loa Andersson&quot; &lt;loa@pi.nu&gt;</tt><br><tt>To: &lt;Malcolm.BETTS@zt=
e.com.cn&gt;</tt><br><tt>Cc: &lt;ietf@ietf.org&gt;</tt><br><tt>Sent: Friday=
, March 23, 2012 10:44 AM</tt><br><tt>Subject: Re: [PWE3] FW: LastCall:</tt=
><br><tt>&lt;draft-betts-itu-oam-ach-code-point-03.txt&gt;(Allocationof an =
Associated Channel</tt><br><tt>Code Point for Use byITU-T Ethernet basedOAM=
) to Informational RFC</tt><br><br><br><tt>&gt; Malcolm,</tt><br><tt>&gt;</=
tt><br><tt>&gt; good that we are making some progress!</tt><br><tt>&gt;</tt=
><br><tt>&gt; On the experimental code point</tt><br><tt>&gt; -------------=
-----------------</tt><br><tt>&gt;</tt><br><tt>&gt; I doesn't seem appropri=
ate to call out the fact that some commercial</tt><br><tt>&gt; products has=
 been using an experimental code point in production</tt><br><tt>&gt; setti=
ng!</tt><br><tt>&gt;</tt><br><tt>&gt; On the remain (key) disagreements</tt=
><br><tt>&gt; ---------------------------------</tt><br><tt>&gt;</tt><br><t=
t>&gt; I will let other people comment for now.</tt><br><tt>&gt;</tt><br><t=
t>&gt;</tt><br><tt>&gt; /Loa</tt><br><tt>&gt;</tt><br><tt>&gt; On 2012-03-2=
1 21:33, Malcolm.BETTS@zte.com.cn wrote:</tt><br><tt>&gt; &gt; Loa,</tt><br=
><tt>&gt; &gt;</tt><br><tt>&gt; &gt; Thank you for your comments and sugges=
tions, please see in line below.</tt><br><tt>&gt; &gt;</tt><br><tt>&gt; &gt=
; Regards,</tt><br><tt>&gt; &gt;</tt><br><tt>&gt; &gt; Malcolm</tt><br><tt>=
&gt; &gt;</tt><br><tt>&gt; &gt;</tt><br><tt>&gt; &gt; ietf-bounces@ietf.org=
 wrote on 12/03/2012 04:31:43 AM:</tt><br><tt>&gt; &gt;</tt><br><tt>&gt; &g=
t; &nbsp;&gt; Loa Andersson &lt;loa@pi.nu&gt;</tt><br><tt>&gt; &gt; &nbsp;&=
gt; Sent by: ietf-bounces@ietf.org</tt><br><tt>&gt; &gt; &nbsp;&gt;</tt><br=
><tt>&gt; &gt; &nbsp;&gt; 12/03/2012 04:31 AM</tt><br><tt>&gt; &gt; &nbsp;&=
gt;</tt><br><tt>&gt; &gt; &nbsp;&gt; To</tt><br><tt>&gt; &gt; &nbsp;&gt;</t=
t><br><tt>&gt; &gt; &nbsp;&gt; ietf@ietf.org</tt><br><tt>&gt; &gt; &nbsp;&g=
t;</tt><br><tt>&gt; &gt; &nbsp;&gt; cc</tt><br><tt>&gt; &gt; &nbsp;&gt;</tt=
><br><tt>&gt; &gt; &nbsp;&gt; Subject</tt><br><tt>&gt; &gt; &nbsp;&gt;</tt>=
<br><tt>&gt; &gt; &nbsp;&gt; Re: [PWE3] FW: Last Call: &lt;draft-betts-itu-=
oam-ach-code-</tt><br><tt>&gt; &gt; &nbsp;&gt; point-03.txt&gt;(Allocation =
of an Associated Channel Code Point for Use</tt><br><tt>&gt; &gt; &nbsp;&gt=
; byITU-T Ethernet based OAM) to Informational RFC</tt><br><tt>&gt; &gt; &n=
bsp;&gt;</tt><br><tt>&gt; &gt; &nbsp;&gt; All,</tt><br><tt>&gt; &gt; &nbsp;=
&gt;</tt><br><tt>&gt; &gt; &nbsp;&gt; I've been asked to clarify thee comme=
nts in this mail, I done</tt><br><tt>&gt; &gt; &nbsp;&gt; so by proposing n=
ew text to draft-betts-.</tt><br><tt>&gt; &gt; &nbsp;&gt;</tt><br><tt>&gt; =
&gt; &nbsp;&gt; I hope this helps.</tt><br><tt>&gt; &gt; &nbsp;&gt;</tt><br=
><tt>&gt; &gt; &nbsp;&gt;</tt><br><tt>&gt; &gt; &nbsp;&gt; Title</tt><br><t=
t>&gt; &gt; &nbsp;&gt; =3D=3D=3D=3D=3D</tt><br><tt>&gt; &gt; &nbsp;&gt;</tt=
><br><tt>&gt; &gt; &nbsp;&gt; Comment: We want to assign a Associated Chann=
el Type. The registry</tt><br><tt>&gt; &gt; &nbsp;&gt; that it will be assi=
gned from is &quot;Pseudowire Associated Channel</tt><br><tt>&gt; &gt; &nbs=
p;&gt; Types&quot;; however RFC 5586, makes the Channel Types generic and I=
</tt><br><tt>&gt; &gt; &nbsp;&gt; think the title should be changed as foll=
ows:</tt><br><tt>&gt; &gt; &nbsp;&gt;</tt><br><tt>&gt; &gt; &nbsp;&gt; OLD:=
</tt><br><tt>&gt; &gt; &nbsp;&gt; Allocation of an Associated Channel Code =
Point for Use by ITU-T</tt><br><tt>&gt; &gt; &nbsp;&gt; Ethernet based OAM<=
/tt><br><tt>&gt; &gt; &nbsp;&gt;</tt><br><tt>&gt; &gt; &nbsp;&gt; NEW:</tt>=
<br><tt>&gt; &gt; &nbsp;&gt; Allocation of an Generic Associated Channel Ty=
pe for ITU-T</tt><br><tt>&gt; &gt; &nbsp;&gt; MPLS-TP OAM</tt><br><tt>&gt; =
&gt; &nbsp;&gt;</tt><br><tt>&gt; &gt; &nbsp;&gt; Note: Neither MPLS-TP or O=
AM are in the RFC Editors list of wellknown</tt><br><tt>&gt; &gt; &nbsp;&gt=
; acronyms, therfore the title probably should be:</tt><br><tt>&gt; &gt; &n=
bsp;&gt;</tt><br><tt>&gt; &gt; &nbsp;&gt; NEW:</tt><br><tt>&gt; &gt; &nbsp;=
&gt; Allocation of an Generic Associated Channel Type for ITU-T</tt><br><tt=
>&gt; &gt; &nbsp;&gt; MPLS Transport Profile Operation, Maintenance and Adm=
inistration.</tt><br><tt>&gt; &gt; &nbsp;&gt;</tt><br><tt>&gt; &gt;</tt><br=
><tt>&gt; &gt; MB: No objection to this change</tt><br><tt>&gt; &gt;</tt><b=
r><tt>&gt; &gt; &nbsp;&gt;</tt><br><tt>&gt; &gt; &nbsp;&gt; Introduction - =
first paragraph</tt><br><tt>&gt; &gt; &nbsp;&gt; =3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D</tt><br>=
<tt>&gt; &gt; &nbsp;&gt;</tt><br><tt>&gt; &gt; &nbsp;&gt; In the first para=
graph of the introduction, there seems to be an</tt><br><tt>&gt; &gt; &nbsp=
;&gt; oddity in the description of the role of the ietf-tp-oam-analysis</tt=
><br><tt>&gt; &gt; &nbsp;&gt; document. Instead of:</tt><br><tt>&gt; &gt; &=
nbsp;&gt;</tt><br><tt>&gt; &gt; &nbsp;&gt; OLD</tt><br><tt>&gt; &gt; &nbsp;=
&gt; &quot;tools defined by the IETF [I-D.ietf-mpls-tp-oam-analysis], that<=
/tt><br><tt>&gt; &gt; &nbsp;&gt; are intended to meet the OAM functional re=
quirements defined in</tt><br><tt>&gt; &gt; &nbsp;&gt; [RFC5860].&quot;</tt=
><br><tt>&gt; &gt; &nbsp;&gt;</tt><br><tt>&gt; &gt; &nbsp;&gt; NEW:</tt><br=
><tt>&gt; &gt; &nbsp;&gt; &quot;tools described by the IETF [I-D.ietf-mpls-=
tp-oam-analysis], which</tt><br><tt>&gt; &gt; &nbsp;&gt; are used to meet t=
he OAM functional requirements defined</tt><br><tt>&gt; &gt; &nbsp;&gt; in =
[RFC5860].&quot;</tt><br><tt>&gt; &gt;</tt><br><tt>&gt; &gt; MB: No objecti=
on to this change</tt><br><tt>&gt; &gt;</tt><br><tt>&gt; &gt; &nbsp;&gt;</t=
t><br><tt>&gt; &gt; &nbsp;&gt; Intrduction - second paragraph</tt><br><tt>&=
gt; &gt; &nbsp;&gt; =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D</tt><br><tt>&gt; &gt; &nbsp;&gt;</tt><=
br><tt>&gt; &gt; &nbsp;&gt; The next paragraph in describing G.8113.1, stum=
bles over the current</tt><br><tt>&gt; &gt; &nbsp;&gt; vs anticipated futur=
e state of G.8113.1 and its relationship to</tt><br><tt>&gt; &gt; &nbsp;&gt=
; its antecedents. I'm a bit un-certain about the correct terminology,</tt>=
<br><tt>&gt; &gt; &nbsp;&gt; but I think the following change would improve=
 the document.</tt><br><tt>&gt; &gt; &nbsp;&gt;</tt><br><tt>&gt; &gt; &nbsp=
;&gt; OLD:</tt><br><tt>&gt; &gt; &nbsp;&gt;</tt><br><tt>&gt; &gt; &nbsp;&gt=
; The ITU-T has documented, in draft new Recommendation [G.8113.1], the</tt=
><br><tt>&gt; &gt; &nbsp;&gt; use of Ethernet based OAM mechanisms, origina=
lly defined in [Y.1731],</tt><br><tt>&gt; &gt; &nbsp;&gt; carried in the MP=
LS Generic Associated Channel (G-ACh). This approach</tt><br><tt>&gt; &gt; =
&nbsp;&gt; requires the allocation of an ACH Type from the registry of ACH =
types</tt><br><tt>&gt; &gt; &nbsp;&gt; maintained by IANA in order that the=
 messages that will be described</tt><br><tt>&gt; &gt; &nbsp;&gt; in [G.811=
3.1] can be identified by an implementation.</tt><br><tt>&gt; &gt; &nbsp;&g=
t;</tt><br><tt>&gt; &gt; &nbsp;&gt; NEW:</tt><br><tt>&gt; &gt; &nbsp;&gt;</=
tt><br><tt>&gt; &gt; &nbsp;&gt; &quot;The ITU-T has Draft Recommendation [G=
.8113.1] documented MPLS OAM</tt><br><tt>&gt; &gt; &nbsp;&gt; which as of t=
his writing is undergoing the ITU-T Traditional</tt><br><tt>&gt; &gt; &nbsp=
;&gt; Approval Process (TAP). This Recommendation builds upon Ethernet</tt>=
<br><tt>&gt; &gt; &nbsp;&gt; OAM as documented in [Y.1731]. The messages in=
 [G.8113.1] are defined</tt><br><tt>&gt; &gt; &nbsp;&gt; to be carried in a=
 new Associated Channel Type in the MPLS Generaic</tt><br><tt>&gt; &gt; &nb=
sp;&gt; Associated Channel (G-Ach). In order to carry these messages in an<=
/tt><br><tt>&gt; &gt; &nbsp;&gt; interoperable fashion, an Associated Chann=
el Type from the IANA</tt><br><tt>&gt; &gt; &nbsp;&gt; maintained registry =
&quot;Pseudowire Associated Channel Types is to be</tt><br><tt>&gt; &gt; &n=
bsp;&gt; used.&quot;</tt><br><tt>&gt; &gt;</tt><br><tt>&gt; &gt; MB: Since =
the draft will not be published as an RFC until after G.8113.1</tt><br><tt>=
&gt; &gt; is approved we can directly reference the approved Recommendation=
 and I</tt><br><tt>&gt; &gt; suggest that we modify paragraph to:</tt><br><=
tt>&gt; &gt;</tt><br><tt>&gt; &gt;</tt><br><tt>&gt; &gt; ITU-T Recommendati=
on [G.8113.1] documents MPLS OAM. This Recommendation</tt><br><tt>&gt; &gt;=
 builds upon Ethernet OAM as documented in [Y.1731]. The messages in</tt><b=
r><tt>&gt; &gt; [G.8113.1] are defined to be carried in a new Associated Ch=
annel Type in</tt><br><tt>&gt; &gt; the MPLS Generaic Associated Channel (G=
-Ach). In order to carry these</tt><br><tt>&gt; &gt; messages in an interop=
erable fashion, an Associated Channel Type from</tt><br><tt>&gt; &gt; the I=
ANA maintained registry &quot;Pseudowire Associated Channel Types is to</tt=
><br><tt>&gt; &gt; be used.&quot;</tt><br><tt>&gt; &gt;</tt><br><tt>&gt; &g=
t;</tt><br><tt>&gt; &gt; &nbsp;&gt;</tt><br><tt>&gt; &gt; &nbsp;&gt; Note t=
here are confusion around some of the Associated Channel</tt><br><tt>&gt; &=
gt; &nbsp;&gt; acronyms that are refledted in this document.</tt><br><tt>&g=
t; &gt; &nbsp;&gt;</tt><br><tt>&gt; &gt; &nbsp;&gt; ACh is Associated Chann=
el</tt><br><tt>&gt; &gt; &nbsp;&gt; ACH is Associated Chamnnel Header</tt><=
br><tt>&gt; &gt; &nbsp;&gt; G-ACh is Generic Associated Channel</tt><br><tt=
>&gt; &gt; &nbsp;&gt;</tt><br><tt>&gt; &gt; &nbsp;&gt; &quot;ACH Type&quot;=
 is not used anywhere in IETF documents; we talk about</tt><br><tt>&gt; &gt=
; &nbsp;&gt; Associated Channel Type or Generic Associated Channel Type</tt=
><br><tt>&gt; &gt; &nbsp;&gt; (G-ACh Type).</tt><br><tt>&gt; &gt;</tt><br><=
tt>&gt; &gt; MB: Thank you, I will fix this.</tt><br><tt>&gt; &gt;</tt><br>=
<tt>&gt; &gt; &nbsp;&gt;</tt><br><tt>&gt; &gt; &nbsp;&gt; Introduction - th=
ird paragraph</tt><br><tt>&gt; &gt; &nbsp;&gt; =3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D</tt><br><tt=
>&gt; &gt; &nbsp;&gt;</tt><br><tt>&gt; &gt; &nbsp;&gt; In the third paragra=
ph, there seems to be an unnecessary reference</tt><br><tt>&gt; &gt; &nbsp;=
&gt; to experimental types. When asking for a code point for a standard,</t=
t><br><tt>&gt; &gt; &nbsp;&gt; it is not helped to bring up experimental co=
de space. Can we remove</tt><br><tt>&gt; &gt; &nbsp;&gt; the text reading:<=
/tt><br><tt>&gt; &gt; &nbsp;&gt;</tt><br><tt>&gt; &gt; &nbsp;&gt; OLD:</tt>=
<br><tt>&gt; &gt; &nbsp;&gt; &quot;without continuing to resorting to the u=
se of an experimental</tt><br><tt>&gt; &gt; &nbsp;&gt; ACH Type,&quot;</tt>=
<br><tt>&gt; &gt; &nbsp;&gt;</tt><br><tt>&gt; &gt; &nbsp;&gt; NEW</tt><br><=
tt>&gt; &gt; &nbsp;&gt; -</tt><br><tt>&gt; &gt;</tt><br><tt>&gt; &gt; MB: I=
 do not agree with the deletion of this text, these existing</tt><br><tt>&g=
t; &gt; deployments, and the desire to migrate to an allocated code point, =
are</tt><br><tt>&gt; &gt; part of the rational for requesting the code poin=
t.</tt><br><tt>&gt; &gt;</tt><br><tt>&gt; &gt; &nbsp;&gt;</tt><br><tt>&gt; =
&gt; &nbsp;&gt;</tt><br><tt>&gt; &gt; &nbsp;&gt; Section 2 - first paragrap=
h</tt><br><tt>&gt; &gt; &nbsp;&gt; =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D</tt><br><tt>&gt; &gt; &nbsp;&gt;=
</tt><br><tt>&gt; &gt; &nbsp;&gt;</tt><br><tt>&gt; &gt; &nbsp;&gt;</tt><br>=
<tt>&gt; &gt; &nbsp;&gt; In section 2, the first sentence refers to Etherne=
t based OAM</tt><br><tt>&gt; &gt; &nbsp;&gt; messages. As far as I know, th=
e messages in G.8113.1 are either</tt><br><tt>&gt; &gt; &nbsp;&gt; MPLS-TP =
OAM messages, or they are simply the OAM messages defined</tt><br><tt>&gt; =
&gt; &nbsp;&gt; in G.8113.1. The simplest path to clarity would seem to be =
to</tt><br><tt>&gt; &gt; &nbsp;&gt; replace &quot;Ethernet based OAM messag=
es&quot; in that sentence with</tt><br><tt>&gt; &gt; &nbsp;&gt; &quot;messa=
ges&quot;.</tt><br><tt>&gt; &gt; &nbsp;&gt;</tt><br><tt>&gt; &gt; &nbsp;&gt=
; The second sentence of that paragraph does not seem to say anything</tt><=
br><tt>&gt; &gt; &nbsp;&gt; we need to say. Can we remove it?</tt><br><tt>&=
gt; &gt; &nbsp;&gt;</tt><br><tt>&gt; &gt; &nbsp;&gt; OLD:</tt><br><tt>&gt; =
&gt; &nbsp;&gt;</tt><br><tt>&gt; &gt; &nbsp;&gt; The code point allocated b=
y this document is intended to be used only</tt><br><tt>&gt; &gt; &nbsp;&gt=
; for Ethernet based OAM messages, defined in the ITU-T Recommendation</tt>=
<br><tt>&gt; &gt; &nbsp;&gt; [G.8113.1], carried in the G-ACh . These Ether=
net based OAM messages</tt><br><tt>&gt; &gt; &nbsp;&gt; and procedures, add=
ress the OAM functional requirements defined in</tt><br><tt>&gt; &gt; &nbsp=
;&gt; [RFC5860]. Other message types should not be carried behind this code=
</tt><br><tt>&gt; &gt; &nbsp;&gt; point.</tt><br><tt>&gt; &gt; &nbsp;&gt;</=
tt><br><tt>&gt; &gt; &nbsp;&gt; NEW:</tt><br><tt>&gt; &gt; &nbsp;&gt;</tt><=
br><tt>&gt; &gt; &nbsp;&gt; The code point allocated by this document is in=
tended to be used</tt><br><tt>&gt; &gt; &nbsp;&gt; only for OAM messages, d=
efined in the ITU-T Recommendation</tt><br><tt>&gt; &gt; &nbsp;&gt; [G.8113=
.1], carried in the G-ACh . Other message types should not</tt><br><tt>&gt;=
 &gt; &nbsp;&gt; be carried behind this Associated Channel Type.</tt><br><t=
t>&gt; &gt;</tt><br><tt>&gt; &gt;</tt><br><tt>&gt; &gt; MB: I do not agree =
with this proposed change. Other comments request</tt><br><tt>&gt; &gt; tha=
t the restriction on the applicability of the code point is</tt><br><tt>&gt=
; &gt; strengthened so I propose the following:</tt><br><tt>&gt; &gt;</tt><=
br><tt>&gt; &gt; The code point allocated by this document should only be u=
sed for OAM</tt><br><tt>&gt; &gt; messages, defined in the ITU-T Recommenda=
tion [G.8113.1], carried in the</tt><br><tt>&gt; &gt; G-ACh. The messages a=
nd procedures carried behind this code point, are</tt><br><tt>&gt; &gt; res=
tricted to only those that the address the OAM functional</tt><br><tt>&gt; =
&gt; requirements defined in [RFC5860]. Other message types should not be</=
tt><br><tt>&gt; &gt; carried behind this code point.</tt><br><tt>&gt; &gt;<=
/tt><br><tt>&gt; &gt;</tt><br><tt>&gt; &gt; &nbsp;&gt;</tt><br><tt>&gt; &gt=
; &nbsp;&gt; Section 2 - second paragraph</tt><br><tt>&gt; &gt; &nbsp;&gt; =
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D</tt><br><tt>&gt; &gt; &nbsp;&gt;</tt><br><tt>&gt; &gt; &nbsp;&gt;=
 A matter of some clarity, can we change this paragrap like this:</tt><br><=
tt>&gt; &gt; &nbsp;&gt;</tt><br><tt>&gt; &gt; &nbsp;&gt; OLD:</tt><br><tt>&=
gt; &gt; &nbsp;&gt; This code point may be used on any transport construct =
that uses</tt><br><tt>&gt; &gt; &nbsp;&gt; the G-ACh, e.g., MPLS-TP Section=
s, MPLS-TP LSPs or PWs.</tt><br><tt>&gt; &gt; &nbsp;&gt;</tt><br><tt>&gt; &=
gt; &nbsp;&gt; NEW:</tt><br><tt>&gt; &gt; &nbsp;&gt;</tt><br><tt>&gt; &gt; =
&nbsp;&gt; The Generic Associated Channel Type assigned by this</tt><br><tt=
>&gt; &gt; &nbsp;&gt; document may be used on any transport construct that =
uses the</tt><br><tt>&gt; &gt; &nbsp;&gt; G-ACh, e.g., MPLS-TP Sections, MP=
LS-TP LSPs or PWs as specified</tt><br><tt>&gt; &gt; &nbsp;&gt; by G.8113.1=
.</tt><br><tt>&gt; &gt;</tt><br><tt>&gt; &gt; MB: No objection to this chan=
ge.</tt><br><tt>&gt; &gt;</tt><br><tt>&gt; &gt; &nbsp;&gt;</tt><br><tt>&gt;=
 &gt; &nbsp;&gt;</tt><br><tt>&gt; &gt; &nbsp;&gt; Section 2 - third paragra=
ph</tt><br><tt>&gt; &gt; &nbsp;&gt; =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D</tt><br><tt>&gt; &gt; &nbsp;&gt;=
</tt><br><tt>&gt; &gt; &nbsp;&gt; With regard to revisions, which is what I=
 think the third paragraph</tt><br><tt>&gt; &gt; &nbsp;&gt; is about, I am =
not clear what you are trying to say. A code point</tt><br><tt>&gt; &gt; &n=
bsp;&gt; allocation must point to a stable referent. If the desired referen=
t</tt><br><tt>&gt; &gt; &nbsp;&gt; changes, then process needs to be follow=
ed to make sure that the IANA</tt><br><tt>&gt; &gt; &nbsp;&gt; is updated i=
n accordance with IETF procedures. Hence, I am left to</tt><br><tt>&gt; &gt=
; &nbsp;&gt; the conclusion that the third paragraph is actually asking for=
</tt><br><tt>&gt; &gt; &nbsp;&gt; something we can not do. Can we remove th=
at?</tt><br><tt>&gt; &gt; &nbsp;&gt;</tt><br><tt>&gt; &gt; &nbsp;&gt; OLD:<=
/tt><br><tt>&gt; &gt; &nbsp;&gt; All ITU-T Recommendations are subject to r=
evisions. Therefore, the</tt><br><tt>&gt; &gt; &nbsp;&gt; code point alloca=
ted by this document may be used for future versions</tt><br><tt>&gt; &gt; =
&nbsp;&gt; of [G.8113.1].</tt><br><tt>&gt; &gt; &nbsp;&gt;</tt><br><tt>&gt;=
 &gt; &nbsp;&gt; NEW:</tt><br><tt>&gt; &gt; &nbsp;&gt; -</tt><br><tt>&gt; &=
gt; &nbsp;&gt;</tt><br><tt>&gt; &gt; &nbsp;&gt;</tt><br><tt>&gt; &gt;</tt><=
br><tt>&gt; &gt; MB: I do not agree with the removal of this text:</tt><br>=
<tt>&gt; &gt;</tt><br><tt>&gt; &gt; The intention of this statement is to b=
ring to the attention of the IETF</tt><br><tt>&gt; &gt; the normal practice=
 in the ITU of developing amendments to</tt><br><tt>&gt; &gt; Recommendatio=
ns to fully meet the functional requirements (e.g. adding</tt><br><tt>&gt; =
&gt; pro-active loss measurement). Normally any reference to ITU-T Rec</tt>=
<br><tt>&gt; &gt; G.8113.1 will automatically be directed to the current ve=
rsion</tt><br><tt>&gt; &gt; (including any amendments).</tt><br><tt>&gt; &g=
t;</tt><br><tt>&gt; &gt; Only those interfaces that support G.8113.1 OAM wi=
ll act on these OAM</tt><br><tt>&gt; &gt; messages, any interface that does=
 not support this G-ACh type will</tt><br><tt>&gt; &gt; discard these OAM m=
essages as defined in RFC5586.</tt><br><tt>&gt; &gt;</tt><br><tt>&gt; &gt; =
Restricting the application of the code point to a specific version of</tt>=
<br><tt>&gt; &gt; Recommendation G.8113.1 would require the ITU to deviate =
from its normal</tt><br><tt>&gt; &gt; process for enhancing Recommendations=
 and would put the IETF back into</tt><br><tt>&gt; &gt; the discussion for =
approval.</tt><br><tt>&gt; &gt;</tt><br><tt>&gt; &gt;</tt><br><tt>&gt; &gt;=
</tt><br><tt>&gt; &gt; &nbsp;&gt;---------------snip</tt><br><tt>&gt; &gt;<=
/tt><br><tt>&gt; &gt;</tt><br><tt>&gt; &gt; &nbsp;&gt;</tt><br><tt>&gt; &gt=
; &nbsp;&gt; Loa Andersson email: loa.andersson@ericsson.com</tt><br><tt>&g=
t; &gt; &nbsp;&gt; Sr Strategy and Standards Manager loa@pi.nu</tt><br><tt>=
&gt; &gt; &nbsp;&gt; Ericsson Inc phone: +46 10 717 52 13</tt><br><tt>&gt; =
&gt; &nbsp;&gt; +46 767 72 92 13</tt><br><tt>&gt; &gt; &nbsp;&gt; _________=
______________________________________</tt><br><tt>&gt; &gt; &nbsp;&gt; Iet=
f mailing list</tt><br><tt>&gt; &gt; &nbsp;&gt; Ietf@ietf.org</tt><br><tt>&=
gt; &gt; &nbsp;&gt; </tt></span><a href=3D"https://www.ietf.org/mailman/lis=
tinfo/ietf"><tt><span style=3D'font-size:10.0pt'>https://www.ietf.org/mailm=
an/listinfo/ietf</span></tt></a><span style=3D'font-size:10.0pt;font-family=
:"Courier New"'><br><tt>&gt; &gt; &nbsp;&gt;</tt><br><tt>&gt;</tt><br><tt>&=
gt; --</tt><br><tt>&gt;</tt><br><tt>&gt;</tt><br><tt>&gt; Loa Andersson &nb=
sp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &=
nbsp; email: loa.andersson@ericsson.com</tt><br><tt>&gt; Sr Strategy and St=
andards Manager &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;loa@pi.nu</tt><br>=
<tt>&gt; Ericsson Inc &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbs=
p; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;phone: +46 10 717 52 13</tt><br><tt>&g=
t; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &n=
bsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; +46 767 72 92 13</tt><br><tt>&gt;</tt><br><tt>&gt;</tt><br><b=
r><br></span><o:p></o:p></p></div></body></html>=

--_000_DF7F294AF4153D498141CBEFADB17704C70D0DB7B1EMBX01WFjnprn_--

From mustapha.aissaoui@alcatel-lucent.com  Thu Mar 22 08:59:47 2012
Return-Path: <mustapha.aissaoui@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 1171921F85CC; Thu, 22 Mar 2012 08:59:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.239
X-Spam-Level: 
X-Spam-Status: No, score=-9.239 tagged_above=-999 required=5 tests=[AWL=1.359,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lQ2A6y3+ul4N; Thu, 22 Mar 2012 08:59:45 -0700 (PDT)
Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33]) by ietfa.amsl.com (Postfix) with ESMTP id 6939A21F85A8; Thu, 22 Mar 2012 08:59:45 -0700 (PDT)
Received: from usnavsmail2.ndc.alcatel-lucent.com (usnavsmail2.ndc.alcatel-lucent.com [135.3.39.10]) by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id q2MFxg9j006229 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 22 Mar 2012 10:59:42 -0500 (CDT)
Received: from USNAVSXCHHUB01.ndc.alcatel-lucent.com (usnavsxchhub01.ndc.alcatel-lucent.com [135.3.39.110]) by usnavsmail2.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id q2MFxdYt009698 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Thu, 22 Mar 2012 10:59:39 -0500
Received: from USNAVSXCHMBSC2.ndc.alcatel-lucent.com ([135.3.39.147]) by USNAVSXCHHUB01.ndc.alcatel-lucent.com ([135.3.39.110]) with mapi; Thu, 22 Mar 2012 10:59:26 -0500
From: "Aissaoui, Mustapha (Mustapha)" <mustapha.aissaoui@alcatel-lucent.com>
To: "'pwe3@ietf.org'" <pwe3@ietf.org>, Daniel Cohn <DanielC@orckit.com>
Date: Thu, 22 Mar 2012 10:59:24 -0500
Subject: RE: [PWE3] Last Call: <draft-ietf-pwe3-redundancy-bit-06.txt> (Pseudowire Preferential Forwarding Status Bit) to Proposed Standard
Thread-Topic: [PWE3] Last Call: <draft-ietf-pwe3-redundancy-bit-06.txt> (Pseudowire Preferential Forwarding Status Bit) to Proposed Standard
Thread-Index: Acz8izeZXI9/dkIbSZqtuo9E9fuJLwAADwawAsQxoaA=
Message-ID: <5DF53972F7E9134782DCE51624466FE50AD59605CD@USNAVSXCHMBSC2.ndc.alcatel-lucent.com>
References: <20120307170032.20594.20281.idtracker@ietfa.amsl.com> <4F579F33.7050508@cisco.com> <5DF53972F7E9134782DCE51624466FE50AD5811DAC@USNAVSXCHMBSC2.ndc.alcatel-lucent.com> <CAK+d4xsS9GVrM1u2QPhsfXXK6xhzmQzGDDaVNhqay8VM_eQbaQ@mail.gmail.com> <F3C4EFDF82867245BE6619978090E9A40AF5FEDC6B@USNAVSXCHMBSC2.ndc.alcatel-lucent.com>
In-Reply-To: <F3C4EFDF82867245BE6619978090E9A40AF5FEDC6B@USNAVSXCHMBSC2.ndc.alcatel-lucent.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_5DF53972F7E9134782DCE51624466FE50AD59605CDUSNAVSXCHMBSC_"
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.10
X-Mailman-Approved-At: Fri, 23 Mar 2012 10:02:02 -0700
Cc: "'draft-ietf-pwe3-redundancy-bit@tools.ietf.org'" <draft-ietf-pwe3-redundancy-bit@tools.ietf.org>, "'Andrew G. Malis'" <amalis@gmail.com>, "'ietf@ietf.org'" <ietf@ietf.org>, "'stbryant@cisco.com'" <stbryant@cisco.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Mar 2012 15:59:47 -0000

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

Dear all,
I received comments from Daniel regarding the intended use of the optional =
active PW selection mechanism in section 5.1. I pasted below the correspond=
ing paragraph of Section 5.1 with the changes we agreed to underlined.

He also asked if the default active PW selection mechanism should be refere=
nced in Section 5.2 with the Master/Slave mode of operation. Although, it i=
s not stricly required for interoperability, implementations would benefit =
from a consistent behaviour. I used SHOULD in that case. The text is also p=
asted below with the changes underlined.

Let me know if you have any comments on this.

Regards,
Mustapha.

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
I. Changes to Section 5.1 - 3rd paragraph:
"
If more than one PW qualifies for the Active state, each PW endpoint MUST i=
mplement a common mechanism to choose the PW for forwarding. The default me=
chanism MUST be supported by all implementations and operates as follows:
1.     For FEC128 PW, the PW with the lowest pw-id value is selected.
2.     For FEC129 PW, each PW in a redundant set is uniquely identified at =
each PE using the following triplet: AGI::SAII::TAII. The unsigned integer =
form of the concatenated word can be used in the comparison. However, the S=
AII and TAII values as seen on a PE node are the mirror values of what the =
peer PE node sees. To have both PE nodes compare the same value we propose =
that the PE with the lowest system IP address use the unsigned integer form=
 of AGI::SAII::TAII while the PE with the highest system IP address use the=
 unsigned integer form of AGI::TAII::SAII. This way, both PEs will compare =
the same values. The PW which corresponds to the minimum of the compared va=
lues across all PWs in the redundant is selected.
Note 1: in the case where the system IP address is not known, it is recomme=
nded to implement the optional active PW selection mechanism described next=
.
Note 2: in the case of segmented PW, the operator needs to make sure that t=
he pw-id or AGI::SAII::TAII of the redundant PWs within the first and last =
segment are ordered consistently such that the same end-to-end MS-PW gets s=
elected. Otherwise, it is recommended to implement the optional active PW s=
election mechanism described next.
The PW endpoints MAY also implement the following optional active PW select=
ion mechanism.
1.     If the PW endpoint is configured with the precedence parameter on ea=
ch PW in the redundant set, it must select the PW with the lowest configure=
d precedence value.
2.     If the PW endpoint is configured with one PW as primary and one or m=
ore PWs as secondary, it must select the primary PW in preference to all se=
condary PWs. If a primary PW is not available, it must use the secondary PW=
 with the lowest precedence value. If the primary PW becomes available, a P=
W endpoint must revert to it immediately or after the expiration of a confi=
gurable delay.
3.     This active PW selection mechanism assumes the precedence parameter =
values are configured consistently at both PW endpoints and that unique val=
ues are assigned to the PWs in the same redundancy set to achieve tie-break=
ing using this mechanism.
"

II. Changes to Section 5.2 - 5th paragraph:
"
If more than one PW qualify for the Active state, the Master PW endpoint no=
de selects one. There is no requirement to specify a default active PW sele=
ction mechanism in this case but for consistency across implementations, th=
e Master PW endpoint SHOULD implement the default active PW selection mecha=
nism described in Section 5.1.
If the Master PW endpoint implements the optional active PW selection mecha=
nism based on primay/secondary and precedence parameters, it MUST follow th=
e following behaviour:
1.     If the PW endpoint is configured with the precedence parameter on ea=
ch PW in the redundant set, it must select the PW with the lowest configure=
d precedence value.
2.     If the PW endpoint is configured with one PW as primary and one or m=
ore PWs as secondary, it must select the primary PW in preference to all se=
condary PWs. If a primary PW is not available, it must use the secondary PW=
 with the lowest precedence value. If the primary PW becomes available, a P=
W endpoint must revert to it immediately or after the expiration of a confi=
gurable delay.
"
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

________________________________
From: Aissaoui, Mustapha (Mustapha)
Sent: Wednesday, March 07, 2012 12:56 PM
To: Andrew G. Malis
Cc: stbryant@cisco.com; draft-ietf-pwe3-redundancy-bit@tools.ietf.org; pwe3=
@ietf.org; ietf@ietf.org
Subject: RE: [PWE3] Last Call: <draft-ietf-pwe3-redundancy-bit-06.txt> (Pse=
udowire Preferential Forwarding Status Bit) to Proposed Standard

makes sense Andy.

Thanks,
Mustapha.

________________________________
From: Andrew G. Malis [mailto:amalis@gmail.com]
Sent: Wednesday, March 07, 2012 12:53 PM
To: Aissaoui, Mustapha (Mustapha)
Cc: stbryant@cisco.com; draft-ietf-pwe3-redundancy-bit@tools.ietf.org; pwe3=
@ietf.org; ietf@ietf.org
Subject: Re: [PWE3] Last Call: <draft-ietf-pwe3-redundancy-bit-06.txt> (Pse=
udowire Preferential Forwarding Status Bit) to Proposed Standard

Mustapha,

You might want to wait for any other LC comments before updating.

Thanks,
Andy

On Wed, Mar 7, 2012 at 9:49 AM, Aissaoui, Mustapha (Mustapha) <mustapha.ais=
saoui@alcatel-lucent.com<mailto:mustapha.aissaoui@alcatel-lucent.com>> wrot=
e:
Ooops. Thank you for pointing this out Stewart. I will make the update and =
publish a new revision.

Mustapha.

-----Original Message-----
From: Stewart Bryant [mailto:stbryant@cisco.com<mailto:stbryant@cisco.com>]
Sent: Wednesday, March 07, 2012 12:48 PM
To: draft-ietf-pwe3-redundancy-bit@tools.ietf.org<mailto:draft-ietf-pwe3-re=
dundancy-bit@tools.ietf.org>
Cc: ietf@ietf.org<mailto:ietf@ietf.org>; pwe3@ietf.org<mailto:pwe3@ietf.org=
>
Subject: Re: Last Call: <draft-ietf-pwe3-redundancy-bit-06.txt> (Pseudowire=
 Preferential Forwarding Status Bit) to Proposed Standard


Authors

There was on point that I notice that you did not address from the AD revie=
w and so I am picking it up as a LC comment:

In section 10 you say:

   "This document makes the following update to the PwOperStatusTC
   textual convention in RFC5542 [8]: "

This update should be recorded in the metadata (top left front page) and it=
 is usual to put a one line note in the abstract.

Stewart



On 07/03/2012 17:00, The IESG wrote:
> The IESG has received a request from the Pseudowire Emulation Edge to
> Edge WG (pwe3) to consider the following document:
> - 'Pseudowire Preferential Forwarding Status Bit'
>    <draft-ietf-pwe3-redundancy-bit-06.txt>  as a Proposed Standard
>
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org<mailto:ietf@ietf.org> mailing lists by 2012-03-21. Exceptio=
nally, comments may
> be sent to iesg@ietf.org<mailto:iesg@ietf.org> instead. In either case, p=
lease retain the
> beginning of the Subject line to allow automated sorting.
>
> Abstract
>
>
>     This document describes a mechanism for standby status signaling of
>     redundant pseudowires (PWs) between their termination points. A set
>     of redundant PWs is configured between provider edge (PE) nodes in
>     single-segment pseudowire (SS-PW) applications, or between
>     terminating provider edge (T-PE) nodes in multi-segment pseudowire
>     (MS-PW) applications.
>
>     In order for the PE/T-PE nodes to indicate the preferred PW to use
>     for forwarding PW packets to one another, a new status bit is needed
>     to indicate a preferential forwarding status of Active or Standby for
>     each PW in a redundant set.
>
>     In addition, a second status bit is defined to allow peer PE nodes to
>     coordinate a switchover operation of the PW.
>
>
>
>
>
>
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-pwe3-redundancy-bit/
>
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-pwe3-redundancy-bit/ballot/
>
>
> No IPR declarations have been submitted directly on this I-D.
>
>
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org<mailto:IETF-Announce@ietf.org>
> https://www.ietf.org/mailman/listinfo/ietf-announce
>


--
For corporate legal information go to:

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


_______________________________________________
pwe3 mailing list
pwe3@ietf.org<mailto:pwe3@ietf.org>
https://www.ietf.org/mailman/listinfo/pwe3


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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns:o =3D "urn:schemas-microsoft-com:office:office"><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" http-equiv=3DContent-Type=
>
<META name=3DGENERATOR content=3D"MSHTML 8.00.6001.19190"></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><FONT size=3D2 face=3DArial><SPAN=20
class=3D765035319-21032012>Dear all,</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT size=3D2 face=3DArial><SPAN class=3D76503=
5319-21032012>I=20
received comments from Daniel regarding the intended use of the optional ac=
tive=20
PW selection mechanism in section 5.1. I&nbsp;pasted below the correspondin=
g=20
paragraph of Section 5.1 with the changes we agreed to underlined.&nbsp;=20
</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT size=3D2 face=3DArial><SPAN=20
class=3D765035319-21032012></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT size=3D2 face=3DArial><SPAN=20
class=3D765035319-21032012>He also asked if the default active PW selection=
=20
mechanism should be referenced in Section 5.2 with the Master/Slave mode of=
=20
operation. Although, it is not stricly required for interoperability,=20
implementations would benefit from a consistent behaviour. I used SHOULD in=
 that=20
case. The text is also pasted below with the changes=20
underlined.</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT size=3D2 face=3DArial><SPAN=20
class=3D765035319-21032012></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT size=3D2 face=3DArial><SPAN=20
class=3D765035319-21032012>Let me know if you have any comments on=20
this.</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT size=3D2 face=3DArial><SPAN=20
class=3D765035319-21032012></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT size=3D2 face=3DArial><SPAN=20
class=3D765035319-21032012>Regards,</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT size=3D2 face=3DArial><SPAN=20
class=3D765035319-21032012>Mustapha.</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT size=3D2 face=3DArial><SPAN=20
class=3D765035319-21032012></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT size=3D2 face=3DArial><SPAN=20
class=3D765035319-21032012>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D</SPAN></FON=
T></DIV>
<DIV dir=3Dltr align=3Dleft><FONT size=3D2 face=3DArial><SPAN=20
class=3D765035319-21032012>I. Changes to Section 5.1 - 3rd=20
paragraph:</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT size=3D2 face=3DArial><SPAN=20
class=3D765035319-21032012>"</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial><SPAN class=3D765035319-2103=
2012>
<P style=3D"MARGIN: 0in 0in 12pt 0.3in" class=3DMsoNormal><FONT=20
face=3D"Courier New"><FONT size=3D2>If more than one PW qualifies for the A=
ctive=20
state, each PW endpoint MUST implement a common mechanism to choose the PW =
for=20
forwarding. The default mechanism MUST be supported by all implementations =
and=20
operates as follows:<o:p></o:p></FONT></FONT></P>
<P=20
style=3D"TEXT-INDENT: -21.75pt; MARGIN: 0in 0in 12pt 43.35pt; tab-stops: .3=
in list 43.35pt left .9in 1.2in 1.5in 1.8in 2.1in 2.4in 2.7in 3.0in 3.3in 3=
.6in 3.9in 4.2in 4.5in 4.8in 5.1in 5.4in 5.7in 6.0in 6.3in 6.6in 6.9in; mso=
-list: l0 level1 lfo1"=20
class=3DMsoNormal><FONT size=3D2><SPAN=20
style=3D"mso-fareast-font-family: 'Courier New'"><SPAN=20
style=3D"mso-list: Ignore"><FONT face=3D"Courier New">1.</FONT><SPAN=20
style=3D"FONT: 7pt 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;=20
</SPAN></SPAN></SPAN><FONT face=3D"Courier New">For FEC128 PW, the PW with =
the=20
lowest pw-id value is selected.<o:p></o:p></FONT></FONT></P>
<P=20
style=3D"TEXT-INDENT: -21.75pt; MARGIN: 0in 0in 12pt 43.35pt; tab-stops: .3=
in list 43.35pt left .9in 1.2in 1.5in 1.8in 2.1in 2.4in 2.7in 3.0in 3.3in 3=
.6in 3.9in 4.2in 4.5in 4.8in 5.1in 5.4in 5.7in 6.0in 6.3in 6.6in 6.9in; mso=
-list: l0 level1 lfo1"=20
class=3DMsoNormal><FONT size=3D2><SPAN=20
style=3D"mso-fareast-font-family: 'Courier New'"><SPAN=20
style=3D"mso-list: Ignore"><FONT face=3D"Courier New">2.</FONT><SPAN=20
style=3D"FONT: 7pt 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;=20
</SPAN></SPAN></SPAN><FONT face=3D"Courier New">For FEC129 PW, each PW in a=
=20
redundant set is uniquely identified at each PE using the following triplet=
:=20
AGI::SAII::TAII. The unsigned integer form of the concatenated word can be =
used=20
in the comparison. However, the SAII and TAII values as seen on a PE node a=
re=20
the mirror values of what the peer PE node sees. To have both PE nodes comp=
are=20
the same value we propose that the PE with the lowest system IP address use=
 the=20
unsigned integer form of AGI::SAII::TAII while the PE with the highest syst=
em IP=20
address use the unsigned integer form of AGI::TAII::SAII. This way, both PE=
s=20
will compare the same values. The PW which corresponds to the minimum of th=
e=20
compared values across all PWs in the redundant is=20
selected.<o:p></o:p></FONT></FONT></P>
<P style=3D"MARGIN: 0in 0in 12pt 0.6in" class=3DMsoNormal><FONT=20
face=3D"Courier New"><FONT size=3D2>Note 1: in the case where the system IP=
 address=20
is not known, it is recommended to implement the optional <U>active PW=20
selection</U> mechanism described next.<o:p></o:p></FONT></FONT></P>
<P style=3D"MARGIN: 0in 0in 12pt 0.6in" class=3DMsoNormal><FONT=20
face=3D"Courier New"><FONT size=3D2>Note 2: in the case of segmented PW, th=
e=20
operator needs to make sure that the pw-id or AGI::SAII::TAII of the redund=
ant=20
PWs within the first and last segment are ordered consistently such that th=
e=20
same end-to-end MS-PW gets selected. Otherwise, it is recommended to implem=
ent=20
the optional <U>active PW selection</U> mechanism described=20
next.<o:p></o:p></FONT></FONT></P>
<P style=3D"MARGIN: 0in 0in 12pt 0.3in" class=3DMsoNormal><FONT=20
face=3D"Courier New"><FONT size=3D2>The PW endpoints MAY also implement the=
=20
following optional <U>active PW selection</U> mechanism.=20
<o:p></o:p></FONT></FONT></P>
<P=20
style=3D"TEXT-INDENT: -21.75pt; MARGIN: 0in 0in 12pt 43.35pt; tab-stops: .3=
in list 43.35pt left .9in 1.2in 1.5in 1.8in 2.1in 2.4in 2.7in 3.0in 3.3in 3=
.6in 3.9in 4.2in 4.5in 4.8in 5.1in 5.4in 5.7in 6.0in 6.3in 6.6in 6.9in; mso=
-list: l1 level1 lfo2"=20
class=3DMsoNormal><FONT size=3D2><SPAN=20
style=3D"mso-fareast-font-family: 'Courier New'"><SPAN=20
style=3D"mso-list: Ignore"><FONT face=3D"Courier New">1.</FONT><SPAN=20
style=3D"FONT: 7pt 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;=20
</SPAN></SPAN></SPAN><FONT face=3D"Courier New">If the PW endpoint is confi=
gured=20
with the precedence parameter on each PW in the redundant set, it must sele=
ct=20
the PW with the lowest configured precedence value.=20
<o:p></o:p></FONT></FONT></P>
<P=20
style=3D"TEXT-INDENT: -21.75pt; MARGIN: 0in 0in 12pt 43.35pt; tab-stops: .3=
in list 43.35pt left .9in 1.2in 1.5in 1.8in 2.1in 2.4in 2.7in 3.0in 3.3in 3=
.6in 3.9in 4.2in 4.5in 4.8in 5.1in 5.4in 5.7in 6.0in 6.3in 6.6in 6.9in; mso=
-list: l1 level1 lfo2"=20
class=3DMsoNormal><FONT size=3D2><SPAN=20
style=3D"mso-fareast-font-family: 'Courier New'"><SPAN=20
style=3D"mso-list: Ignore"><FONT face=3D"Courier New">2.</FONT><SPAN=20
style=3D"FONT: 7pt 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;=20
</SPAN></SPAN></SPAN><FONT face=3D"Courier New">If the PW endpoint is confi=
gured=20
with one PW as primary and one or more PWs as secondary, it must select the=
=20
primary PW in preference to all secondary PWs. If a primary PW is not avail=
able,=20
it must use the secondary PW with the lowest precedence value. If the prima=
ry PW=20
becomes available, a PW endpoint must revert to it immediately or after the=
=20
expiration of a configurable delay.<o:p></o:p></FONT></FONT></P>
<P=20
style=3D"TEXT-INDENT: -21.75pt; MARGIN: 0in 0in 12pt 43.35pt; tab-stops: .3=
in list 43.35pt left .9in 1.2in 1.5in 1.8in 2.1in 2.4in 2.7in 3.0in 3.3in 3=
.6in 3.9in 4.2in 4.5in 4.8in 5.1in 5.4in 5.7in 6.0in 6.3in 6.6in 6.9in; mso=
-list: l1 level1 lfo2"=20
class=3DMsoNormal><FONT size=3D2><SPAN=20
style=3D"mso-fareast-font-family: 'Courier New'"><SPAN=20
style=3D"mso-list: Ignore"><FONT face=3D"Courier New">3.</FONT><SPAN=20
style=3D"FONT: 7pt 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;=20
</SPAN></SPAN></SPAN><U><FONT face=3D"Courier New">This active PW selection=
=20
mechanism assumes the precedence parameter values are configured consistent=
ly at=20
both PW endpoints and that unique values are assigned to the PWs in the sam=
e=20
redundancy set to achieve tie-breaking using this=20
mechanism.<o:p></o:p></FONT></U></FONT></P></SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT size=3D2 face=3DArial><SPAN=20
class=3D765035319-21032012>"</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT size=3D2 face=3DArial><SPAN=20
class=3D765035319-21032012></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT size=3D2 face=3DArial><SPAN=20
class=3D765035319-21032012>II. <FONT size=3D2 face=3DArial><SPAN=20
class=3D765035319-21032012>Changes to Section 5.2 - 5th=20
paragraph:</SPAN></FONT></SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT size=3D2 face=3DArial><SPAN=20
class=3D765035319-21032012><FONT size=3D2 face=3DArial><SPAN=20
class=3D765035319-21032012>"</SPAN></FONT></SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial><SPAN class=3D765035319-2103=
2012><FONT=20
face=3DArial><SPAN class=3D765035319-21032012>
<P style=3D"MARGIN: 0in 0in 12pt 0.3in" class=3DMsoNormal><FONT=20
face=3D"Courier New"><FONT size=3D2>If more than one PW qualify for the Act=
ive=20
state, <U>the Master PW endpoint node selects one. There is no requirement =
to=20
specify a default active PW selection mechanism in this case but for consis=
tency=20
across implementations, the Master PW endpoint SHOULD implement the default=
=20
active PW selection mechanism described in Section 5.1.=20
<o:p></o:p></U></FONT></FONT></P>
<P style=3D"MARGIN: 0in 0in 12pt 0.3in" class=3DMsoNormal><U><FONT=20
face=3D"Courier New"><FONT size=3D2>If the Master PW endpoint implements th=
e=20
optional active PW selection mechanism based on primay/secondary and preced=
ence=20
parameters, it MUST follow the following behaviour:=20
<o:p></o:p></FONT></FONT></U></P>
<P=20
style=3D"TEXT-INDENT: -21.75pt; MARGIN: 0in 0in 12pt 43.35pt; tab-stops: .3=
in list 43.35pt left .9in 1.2in 1.5in 1.8in 2.1in 2.4in 2.7in 3.0in 3.3in 3=
.6in 3.9in 4.2in 4.5in 4.8in 5.1in 5.4in 5.7in 6.0in 6.3in 6.6in 6.9in; mso=
-list: l0 level1 lfo1"=20
class=3DMsoNormal><FONT size=3D2><SPAN=20
style=3D"mso-fareast-font-family: 'Courier New'"><SPAN=20
style=3D"mso-list: Ignore"><FONT face=3D"Courier New">1.</FONT><SPAN=20
style=3D"FONT: 7pt 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;=20
</SPAN></SPAN></SPAN><U><FONT face=3D"Courier New">If the PW endpoint is=20
configured with the precedence parameter on&nbsp;each PW in the redundant s=
et,=20
it must select the PW with the&nbsp;lowest configured precedence=20
value.<o:p></o:p></FONT></U></FONT></P>
<P=20
style=3D"TEXT-INDENT: -21.75pt; MARGIN: 0in 0in 12pt 43.35pt; tab-stops: .3=
in list 43.35pt left .9in 1.2in 1.5in 1.8in 2.1in 2.4in 2.7in 3.0in 3.3in 3=
.6in 3.9in 4.2in 4.5in 4.8in 5.1in 5.4in 5.7in 6.0in 6.3in 6.6in 6.9in; mso=
-list: l0 level1 lfo1"=20
class=3DMsoNormal><FONT size=3D2><SPAN=20
style=3D"mso-fareast-font-family: 'Courier New'"><SPAN=20
style=3D"mso-list: Ignore"><FONT face=3D"Courier New">2.</FONT><SPAN=20
style=3D"FONT: 7pt 'Times New Roman'">&nbsp;&nbsp;&nbsp;&nbsp;=20
</SPAN></SPAN></SPAN><U><FONT face=3D"Courier New">If the PW endpoint is=20
configured with one PW as primary and one&nbsp;or more PWs as secondary, it=
 must=20
select the primary PW in&nbsp;preference to all secondary PWs. If a primary=
 PW=20
is not available, it must use the secondary PW with the lowest&nbsp;precede=
nce=20
value. If the primary PW becomes available, a PW&nbsp;endpoint must revert =
to it=20
immediately or after the expiration of&nbsp;a configurable=20
delay.<o:p></o:p></FONT></U></FONT></P></SPAN></FONT></SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT size=3D2 face=3DArial><SPAN=20
class=3D765035319-21032012><FONT size=3D2 face=3DArial><SPAN=20
class=3D765035319-21032012>"</SPAN></FONT></SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT size=3D2 face=3DArial><SPAN=20
class=3D765035319-21032012>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D</SPAN></FON=
T></DIV><BR>
<DIV dir=3Dltr lang=3Den-us class=3DOutlookMessageHeader align=3Dleft>
<HR tabIndex=3D-1>
<FONT size=3D2 face=3DTahoma><B>From:</B> Aissaoui, Mustapha (Mustapha)=20
<BR><B>Sent:</B> Wednesday, March 07, 2012 12:56 PM<BR><B>To:</B> Andrew G.=
=20
Malis<BR><B>Cc:</B> stbryant@cisco.com;=20
draft-ietf-pwe3-redundancy-bit@tools.ietf.org; pwe3@ietf.org;=20
ietf@ietf.org<BR><B>Subject:</B> RE: [PWE3] Last Call:=20
&lt;draft-ietf-pwe3-redundancy-bit-06.txt&gt; (Pseudowire Preferential=20
Forwarding Status Bit) to Proposed Standard<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D954155517-07032012><FONT size=3D2=
=20
face=3DArial>makes sense Andy. </FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D954155517-07032012><FONT size=3D2=
=20
face=3DArial></FONT></SPAN>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D954155517-07032012><FONT size=3D2=
=20
face=3DArial>Thanks,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D954155517-07032012><FONT size=3D2=
=20
face=3DArial>Mustapha.</FONT></SPAN></DIV><BR>
<DIV dir=3Dltr lang=3Den-us class=3DOutlookMessageHeader align=3Dleft>
<HR tabIndex=3D-1>
<FONT size=3D2 face=3DTahoma><B>From:</B> Andrew G. Malis [mailto:amalis@gm=
ail.com]=20
<BR><B>Sent:</B> Wednesday, March 07, 2012 12:53 PM<BR><B>To:</B> Aissaoui,=
=20
Mustapha (Mustapha)<BR><B>Cc:</B> stbryant@cisco.com;=20
draft-ietf-pwe3-redundancy-bit@tools.ietf.org; pwe3@ietf.org;=20
ietf@ietf.org<BR><B>Subject:</B> Re: [PWE3] Last Call:=20
&lt;draft-ietf-pwe3-redundancy-bit-06.txt&gt; (Pseudowire Preferential=20
Forwarding Status Bit) to Proposed Standard<BR></FONT><BR></DIV>
<DIV></DIV>Mustapha,<BR><BR>You might want to wait for any other LC comment=
s=20
before updating.<BR><BR>Thanks,<BR>Andy<BR><BR>
<DIV class=3Dgmail_quote>On Wed, Mar 7, 2012 at 9:49 AM, Aissaoui, Mustapha=
=20
(Mustapha) <SPAN dir=3Dltr>&lt;<A=20
href=3D"mailto:mustapha.aissaoui@alcatel-lucent.com">mustapha.aissaoui@alca=
tel-lucent.com</A>&gt;</SPAN>=20
wrote:<BR>
<BLOCKQUOTE=20
style=3D"BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LE=
FT: 1ex"=20
class=3Dgmail_quote>Ooops. Thank you for pointing this out Stewart. I will =
make=20
  the update and publish a new revision.<BR><SPAN class=3DHOEnZb><FONT=20
  color=3D#888888><BR>Mustapha.<BR></FONT></SPAN>
  <DIV class=3DHOEnZb>
  <DIV class=3Dh5><BR>-----Original Message-----<BR>From: Stewart Bryant=20
  [mailto:<A href=3D"mailto:stbryant@cisco.com">stbryant@cisco.com</A>]<BR>=
Sent:=20
  Wednesday, March 07, 2012 12:48 PM<BR>To: <A=20
  href=3D"mailto:draft-ietf-pwe3-redundancy-bit@tools.ietf.org">draft-ietf-=
pwe3-redundancy-bit@tools.ietf.org</A><BR>Cc:=20
  <A href=3D"mailto:ietf@ietf.org">ietf@ietf.org</A>; <A=20
  href=3D"mailto:pwe3@ietf.org">pwe3@ietf.org</A><BR>Subject: Re: Last Call=
:=20
  &lt;draft-ietf-pwe3-redundancy-bit-06.txt&gt; (Pseudowire Preferential=20
  Forwarding Status Bit) to Proposed Standard<BR><BR><BR>Authors<BR><BR>The=
re=20
  was on point that I notice that you did not address from the AD review an=
d so=20
  I am picking it up as a LC comment:<BR><BR>In section 10 you=20
  say:<BR><BR>&nbsp; &nbsp;"This document makes the following update to the=
=20
  PwOperStatusTC<BR>&nbsp; &nbsp;textual convention in RFC5542 [8]:=20
  "<BR><BR>This update should be recorded in the metadata (top left front p=
age)=20
  and it is usual to put a one line note in the=20
  abstract.<BR><BR>Stewart<BR><BR><BR><BR>On 07/03/2012 17:00, The IESG=20
  wrote:<BR>&gt; The IESG has received a request from the Pseudowire Emulat=
ion=20
  Edge to<BR>&gt; Edge WG (pwe3) to consider the following document:<BR>&gt=
; -=20
  'Pseudowire Preferential Forwarding Status Bit'<BR>&gt; &nbsp;=20
  &nbsp;&lt;draft-ietf-pwe3-redundancy-bit-06.txt&gt; &nbsp;as a Proposed=20
  Standard<BR>&gt;<BR>&gt; The IESG plans to make a decision in the next fe=
w=20
  weeks, and solicits<BR>&gt; final comments on this action. Please send=20
  substantive comments to the<BR>&gt; <A=20
  href=3D"mailto:ietf@ietf.org">ietf@ietf.org</A> mailing lists by 2012-03-=
21.=20
  Exceptionally, comments may<BR>&gt; be sent to <A=20
  href=3D"mailto:iesg@ietf.org">iesg@ietf.org</A> instead. In either case, =
please=20
  retain the<BR>&gt; beginning of the Subject line to allow automated=20
  sorting.<BR>&gt;<BR>&gt; Abstract<BR>&gt;<BR>&gt;<BR>&gt; &nbsp; &nbsp; T=
his=20
  document describes a mechanism for standby status signaling of<BR>&gt; &n=
bsp;=20
  &nbsp; redundant pseudowires (PWs) between their termination points. A=20
  set<BR>&gt; &nbsp; &nbsp; of redundant PWs is configured between provider=
 edge=20
  (PE) nodes in<BR>&gt; &nbsp; &nbsp; single-segment pseudowire (SS-PW)=20
  applications, or between<BR>&gt; &nbsp; &nbsp; terminating provider edge=
=20
  (T-PE) nodes in multi-segment pseudowire<BR>&gt; &nbsp; &nbsp; (MS-PW)=20
  applications.<BR>&gt;<BR>&gt; &nbsp; &nbsp; In order for the PE/T-PE node=
s to=20
  indicate the preferred PW to use<BR>&gt; &nbsp; &nbsp; for forwarding PW=
=20
  packets to one another, a new status bit is needed<BR>&gt; &nbsp; &nbsp; =
to=20
  indicate a preferential forwarding status of Active or Standby for<BR>&gt=
;=20
  &nbsp; &nbsp; each PW in a redundant set.<BR>&gt;<BR>&gt; &nbsp; &nbsp; I=
n=20
  addition, a second status bit is defined to allow peer PE nodes to<BR>&gt=
;=20
  &nbsp; &nbsp; coordinate a switchover operation of the=20
  PW.<BR>&gt;<BR>&gt;<BR>&gt;<BR>&gt;<BR>&gt;<BR>&gt;<BR>&gt; The file can =
be=20
  obtained via<BR>&gt; <A=20
  href=3D"http://datatracker.ietf.org/doc/draft-ietf-pwe3-redundancy-bit/"=
=20
  target=3D_blank>http://datatracker.ietf.org/doc/draft-ietf-pwe3-redundanc=
y-bit/</A><BR>&gt;<BR>&gt;=20
  IESG discussion can be tracked via<BR>&gt; <A=20
  href=3D"http://datatracker.ietf.org/doc/draft-ietf-pwe3-redundancy-bit/ba=
llot/"=20
  target=3D_blank>http://datatracker.ietf.org/doc/draft-ietf-pwe3-redundanc=
y-bit/ballot/</A><BR>&gt;<BR>&gt;<BR>&gt;=20
  No IPR declarations have been submitted directly on this=20
  I-D.<BR>&gt;<BR>&gt;<BR>&gt;=20
  _______________________________________________<BR>&gt; IETF-Announce mai=
ling=20
  list<BR>&gt; <A=20
  href=3D"mailto:IETF-Announce@ietf.org">IETF-Announce@ietf.org</A><BR>&gt;=
 <A=20
  href=3D"https://www.ietf.org/mailman/listinfo/ietf-announce"=20
  target=3D_blank>https://www.ietf.org/mailman/listinfo/ietf-announce</A><B=
R>&gt;<BR><BR><BR>--<BR>For=20
  corporate legal information go to:<BR><BR><A=20
  href=3D"http://www.cisco.com/web/about/doing_business/legal/cri/index.htm=
l"=20
  target=3D_blank>http://www.cisco.com/web/about/doing_business/legal/cri/i=
ndex.html</A><BR><BR><BR>_______________________________________________<BR=
>pwe3=20
  mailing list<BR><A href=3D"mailto:pwe3@ietf.org">pwe3@ietf.org</A><BR><A=
=20
  href=3D"https://www.ietf.org/mailman/listinfo/pwe3"=20
  target=3D_blank>https://www.ietf.org/mailman/listinfo/pwe3</A><BR></DIV><=
/DIV></BLOCKQUOTE></DIV><BR></BODY></HTML>

--_000_5DF53972F7E9134782DCE51624466FE50AD59605CDUSNAVSXCHMBSC_--

From huubatwork@gmail.com  Fri Mar 23 14:12:08 2012
Return-Path: <huubatwork@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A083A21F8627 for <ietf@ietfa.amsl.com>; Fri, 23 Mar 2012 14:12:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iVrsRBrGO93e for <ietf@ietfa.amsl.com>; Fri, 23 Mar 2012 14:12:07 -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 430BC21F8623 for <ietf@ietf.org>; Fri, 23 Mar 2012 14:12:07 -0700 (PDT)
Received: by eeke51 with SMTP id e51so1127927eek.31 for <ietf@ietf.org>; Fri, 23 Mar 2012 14:12:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:disposition-notification-to:date:from:reply-to :user-agent:mime-version:to:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=FDlPdt2fo1S5zhMM7wS/hCV4SfjdYLZbVTOcRgY7DxA=; b=YJnNifC4bomaiv1vhECJCgI1xJqmMZoDtEbp57k7VT+ZvlVaOPQhO+yl1Z7YnRZogI SJsJUXeXJalXtSl8dItFFQKmyTaNaxvCQeWrzG8U67OPDxSG25SoM2jPD6uceqhJ9nVi urDtRTS7k8VFF6X3PScn17eE7XjM2n5nZeAV0GlZRAG2pHxwhyaTJLSnNAB6NGE8ilde JPPJdRMZKAm2I9U7AmwcKNsWL6k6Lxs7y6HdKtaKiMiQyRMeIGaA2OGwEVtuAOvQvnZ9 8tajKUweWXHTbWSEtraYK7o+5UFTHIjTmPfi0qx5IJU5imdoJgSsEG+8VUWge0QamqyU Gmqw==
Received: by 10.213.2.83 with SMTP id 19mr975106ebi.241.1332537126250; Fri, 23 Mar 2012 14:12:06 -0700 (PDT)
Received: from mcasterix.lan (ip56521a36.adsl-surfen.hetnet.nl. [86.82.26.54]) by mx.google.com with ESMTPS id y11sm31822435eem.3.2012.03.23.14.12.03 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 23 Mar 2012 14:12:04 -0700 (PDT)
Message-ID: <4F6CE71F.7050003@gmail.com>
Date: Fri, 23 Mar 2012 22:11:59 +0100
From: Huub van Helvoort <huubatwork@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Last Call: <draft-ietf-mpls-tp-oam-analysis-08.txt> (An Overviewofthe OAM Tool Set for MPLS based Transport Networks) toInformational RFC
References: <20120309205157.8304.55419.idtracker@ietfa.amsl.com><4F6A5ADB.2090002@gmail.com><E4873516F3FC7547BCFE792C7D94039C0179AE70@DEMUEXC013.nsn-intra.net> <4F6BB565.3010008@gmail.com> <E4873516F3FC7547BCFE792C7D94039C0179B254@DEMUEXC013.nsn-intra.net>
In-Reply-To: <E4873516F3FC7547BCFE792C7D94039C0179B254@DEMUEXC013.nsn-intra.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: huubatwork@gmail.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Mar 2012 21:12:08 -0000

Hallo Nurit,

I will *not* change my mind.
So it is useless to continue this thread.

Just make the changes I requested.

Regards, Huub.
==============

On 23-03-12 08:11, Sprecher, Nurit (NSN - IL/Hod HaSharon) wrote:
> Huub hi,
> The document went through two WG last calls...it is a pity you did not
> use the opportunity to provide your useful comment then.
> I am surprised that it took you almost two years and seven revisions of
> the document before you actually realized you are not happy with the way
> we acknowledged you upon your own request. Surely for a draft where the
> removal of your name from the list of editors was driven by your
> concerns that people might misread your involvement/position. I would
> think that in two years you would get around to checking for you that
> the new acknowledgement is satisfactory.
> Best regards,
> Nurit
>
>
> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
> ext Huub van Helvoort
> Sent: Friday, March 23, 2012 1:28 AM
> To: ietf@ietf.org
> Subject: Re: Last Call:<draft-ietf-mpls-tp-oam-analysis-08.txt>  (An
> Overviewofthe OAM Tool Set for MPLS based Transport Networks)
> toInformational RFC
>
> Hallo Nurit,
>
> You replied:
>
>> Thanks for your comments to IESG...
>
> The IESG did send the message in order to make a decision, that
> is why I addressed my comments to them.
>
>> We can easily remove your name from the acknowledgement section.
>
> Go ahead and do it.
>
>> We put you there upon your request!
>
> It is clear from your response that you did not understand my initial
> explanation and request to be removed as editor.
> When I wrote "you could mention me in the acknowledgements section" I
> did *not* mean "make it more easy for the reader to mis-interpret the
> acknowledgement for my role as Q10 rapporteur".
> You did not even send me the text that you were going to include to
> verify that this text would have taken away my concern.
>
>> I am sorry that I am going to share on the list a private mail from
> you
>> to me but I can see no other choice with the mail you have just sent
> to
>> the list.
>
> It just proves that you did not understand my initial explanation.
>
> Regards, Huub.
> ==============
>> As you recall you were an editor of the draft and on June 2010 (when
> the
>> document was already an IETF document for a while), you have asked to
>> remove your name from the list of editors. See
>> http://www.ietf.org/mail-archive/web/mpls-tp/current/msg04118.html.
> the
>> main reason was as you said:
>>
>> "It was my intention to be editor as an IETF member, however there are
>> people that interpret my name/role differently. They see it as being
>> editor as an ITU-T member and recently even as being editor as an
> ITU-T
>> Q10 rapporteur.".
>>
>> In a private mail you sent me later (attached) you proposed to include
>> you in the acknowledgement section:
>>
>> " Yes, remove my name as editor. As Adrian suggested, you could
> mention
>> me in the acknowledgements section."
>>
>> It is a pity that you did not inform us that you changed your mind
> since
>> then, but it can easily be fixed!
>>
>> Best regards,
>>
>> Nurit
>>
>> -----Original Message-----
>> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf
> Of
>> ext Huub van Helvoort
>> Sent: Thursday, March 22, 2012 12:49 AM
>> To: ietf@ietf.org
>> Subject: Re: Last Call:<draft-ietf-mpls-tp-oam-analysis-08.txt>  (An
>> Overviewof the OAM Tool Set for MPLS based Transport Networks)
>> toInformational RFC
>>
>> IESG,
>>
>> I do *NOT* support this draft unless the following changes are made:
>>
>> The first paragraph of section 8 Acknowledgements has to be removed:
>>
>> It is an attempt to capture history, but lacks accuracy.
>>
>> Removal does not impact the technical information in the draft;
>>
>> the tools have evolved significantly from the strawman tools proposed
>>
>> in Stockholm; some members of the MEAD team (I am one of them) do not
>>
>> consider that an agreement on this proposal was reached.
>>
>> I also request the removal of my name from this acknowledgements
> section
>>
>> since I do not support this tool set, neither as an individual nor as
>>
>> ITU-T Q10 rapporteur. The latter is implied by mentioning my name in
>>
>> the same sentence as a WG chair and ADs.
>>
>> Regards, Huub.
>>
>> =============
>>
>>   >  The IESG has received a request from the Multiprotocol Label
> Switching WG
>>
>>   >  (mpls) to consider the following document:
>>
>>   >  - 'An Overview of the OAM Tool Set for MPLS based Transport
> Networks'
>>
>>   >  <draft-ietf-mpls-tp-oam-analysis-08.txt>  as an 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<mailto:ietf@ietf.org>  mailing lists by 2012-03-23.
>> Exceptionally, comments may be
>>
>>   >  sent to iesg@ietf.org<mailto:iesg@ietf.org>  instead. In either
> case,
>> please retain the
>>
>>   >  beginning of the Subject line to allow automated sorting.
>>
>>   >
>>
>>   >  Abstract
>>
>>   >
>>
>>   >  This document provides an overview of the OAM toolset for MPLS
> based
>>
>>   >  Transport Networks. The toolset consists of a comprehensive set of
>>
>>   >  fault management and performance monitoring capabilities (operating
>>
>>   >  in the data-plane) which are appropriate for transport networks as
>>
>>   >  required in RFC 5860 and support the network and services at
>>
>>   >  different nested levels. This overview includes a brief recap of
>>
>>   >  MPLS-TP OAM requirements and functions, and of generic mechanisms
>>
>>   >  created in the MPLS data plane to allow the OAM packets run in-band
>>
>>   >  and share their fate with data packets. The protocol definitions
> for
>>
>>   >  each of the MPLS-TP OAM tools are defined in separate documents
> (RFCs
>>
>>   >  or Working Group drafts) which are referenced by this document.
>>   >
>>   >
>>   >  The file can be obtained via
>>   >  http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-oam-analysis/
>>   >
>>   >  IESG discussion can be tracked via
>>   >
> http://datatracker.ietf.org/doc/draft-ietf-mpls-tp-oam-analysis/ballot/
>>   >
>>   >
>>   >  No IPR declarations have been submitted directly on this I-D.
>>   >  _____________________________________________
>>   >  IETF-Announce mailing list
>>   >  IETF-Announce@ietf.org<mailto:IETF-Announce@ietf.org>
>>   >  https://www.ietf.org/mailman/listinfo/ietf-announce
>>


-- 
*****************************************************************
                          我爱外点一七三一

From hartmans@mit.edu  Sat Mar 24 00:42:37 2012
Return-Path: <hartmans@mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 210F421F8688; Sat, 24 Mar 2012 00:42:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.265
X-Spam-Level: 
X-Spam-Status: No, score=-102.265 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id myxTIldQ6qJD; Sat, 24 Mar 2012 00:42:36 -0700 (PDT)
Received: from permutation-city.suchdamage.org (permutation-city.suchdamage.org [69.25.196.28]) by ietfa.amsl.com (Postfix) with ESMTP id 4892A21F869F; Sat, 24 Mar 2012 00:42:34 -0700 (PDT)
Received: from carter-zimmerman.suchdamage.org (dhcp-40ae.meeting.ietf.org [130.129.64.174]) (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 F34C820244; Sat, 24 Mar 2012 03:41:52 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id D9B314767; Sat, 24 Mar 2012 03:42:29 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: ietf@ietf.org
Subject: Re: [Ietf-krb-wg] Last Call: <draft-ietf-krb-wg-des-die-die-die-04.txt> (Deprecate DES, RC4-HMAC-EXP, and other weak cryptographic algorithms in Kerberos) to Best Current Practice
References: <20120322152611.20184.76979.idtracker@ietfa.amsl.com>
Date: Sat, 24 Mar 2012 03:42:29 -0400
In-Reply-To: <20120322152611.20184.76979.idtracker@ietfa.amsl.com> (The IESG's message of "Thu, 22 Mar 2012 08:26:11 -0700")
Message-ID: <tslr4wizbq2.fsf@mit.edu>
User-Agent: Gnus/5.110009 (No Gnus v0.9) Emacs/22.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: ietf-krb-wg@anl.gov, iesg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 24 Mar 2012 07:42:37 -0000

Hi.

In the writeup I asked Stephen to include a note that there is a
normative downreference to RFC 4757. RFC 4757 is informational.
This document recommends that implementations not implement some of the
algorithms in RFC 4757, thus creating a normative down-ref.
My opinion and that of the WG is that permitting this normative
down-reference is the appropriate course of action. 

From A.Hoenes@TR-Sys.de  Fri Mar 23 13:59:00 2012
Return-Path: <A.Hoenes@TR-Sys.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 9483C21F844D; Fri, 23 Mar 2012 13:59:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.6
X-Spam-Level: 
X-Spam-Status: No, score=-98.6 tagged_above=-999 required=5 tests=[AWL=0.149,  BAYES_00=-2.599, CHARSET_FARAWAY_HEADER=3.2, HELO_EQ_DE=0.35, 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 PWHXp5HhD6Ah; Fri, 23 Mar 2012 13:59:00 -0700 (PDT)
Received: from TR-Sys.de (gateway.tr-sys.de [213.178.172.147]) by ietfa.amsl.com (Postfix) with ESMTP id 85DF121F8444; Fri, 23 Mar 2012 13:58:58 -0700 (PDT)
Received: from ZEUS.TR-Sys.de by w. with ESMTP ($Revision: 1.37.109.26 $/16.3.2) id AA246666270; Fri, 23 Mar 2012 21:57:50 +0100
Received: (from ah@localhost) by z.TR-Sys.de (8.9.3 (PHNE_25183)/8.7.3) id VAA08984; Fri, 23 Mar 2012 21:57:48 +0100 (MEZ)
From: Alfred =?hp-roman8?B?SM5uZXM=?= <ah@TR-Sys.de>
Message-Id: <201203232057.VAA08984@TR-Sys.de>
Subject: Re: Last Call: <draft-ietf-dnsext-rfc2671bis-edns0-08.txt> ... to Full Standard
To: joao@isc.org, mgraff@isc.org, vixie@isc.org
Date: Fri, 23 Mar 2012 21:57:48 +0100 (MEZ)
X-Mailer: ELM [$Revision: 1.17.214.3 $]
Mime-Version: 1.0
Content-Type: text/plain; charset=hp-roman8
Content-Transfer-Encoding: 8bit
X-Mailman-Approved-At: Sat, 24 Mar 2012 08:28:23 -0700
Cc: ietf@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: Fri, 23 Mar 2012 20:59:00 -0000

I have reviewed draft-ietf-dnsext-rfc2671bis-edns0-08
and would like to submit a few LC comments.

Summary:
=======

The draft is almost ready for publication as a
(Full) Internet Standard RFC.

(Note: Shouldn't the Last Call template now be aligned with the
RFC 6410 maturity level designations and use "Internet Standard"
in place of "Full Standard" -- both in the headline and in the body?)

The technical content is sound and stable and supported by consensus
in the DNS community, including all major DNS implementers; it is also
well aligned with other recent documents / documents in the pipeline.
AFAICT, the document fulfills the criteria posed in Section 2.2 of
RFC 6410 for "Internet Standard".

I only found a few minor textual issues (see below) and a couple of
editorial nits (being communicated to a smaller distribution list)
that all could be easily addressed during final processing stages.


Minor textual issues:
====================

a)  Section 3, last line

I suspect that "... generalized use of TCP for DNS transport."
is not what the authors had in mind, it likely should be
"... general use of TCP for DNS transport."

(or s/general/more frequent/)


b)  Section 6.1.2 -- procedural clarification

I suggest to slightly amend the very last sentence of s6.1.2 :

OLD:
                                           [...].  For example, an
   option specification might say that if a responder sees option XYZ,
   it MUST include option XYZ in its response.

NEW:
                                           [...].  For example, an
   option specification might say that if a responder sees and
   understands option XYZ, it MUST include option XYZ in its response.

(or add "and supports" in place of "and understands")


c)  Section 6.2.2 -- terminological clarification

Since EDNS is -- at least in principle -- designed to be a versioned
family of DNS protocol extensions based on the OPT RR, and such
versions are expected to be upward compatible, the second mention
of "ENDS0" in that paragraph should better say "EDNS" (without the
version '0', see below) or (less preferably) "EDNS(0)".

OLD:
   If a requestor detects that the remote end does not support EDNS0, it
   MAY issue queries without an OPT record.  It MAY cache this knowledge
   for a brief time in order to avoid fallback delays in the future.
   However, if DNSSEC or any future option using EDNS is required, no
|  fallback should be performed as they are only signaled through EDNS0.
   If an implementation detects that some servers for the zone support
   EDNS(0) while others would force the use of TCP to fetch all data,
   preference SHOULD be given to those support EDNS(0).

NEW:
   If a requestor detects that the remote end does not support EDNS0, it
   MAY issue queries without an OPT record.  It MAY cache this knowledge
   for a brief time in order to avoid fallback delays in the future.
   However, if DNSSEC or any future option using EDNS is required, no
|  fallback should be performed as they are only signaled through EDNS.
   If an implementation detects that some servers for the zone support
   EDNS(0) while others would force the use of TCP to fetch all data,
   preference SHOULD be given to those support EDNS(0).


d)  Section 7 -- terminology and additional Reference

I suggest to capitalize the RFC 5226 term used here and add a ref. to
RFC 5226.
Further in terminology: with regard to IANA, "allocation" usually
indicates handing out a block of codepoints -- for instance for
assigment of code points contained within that block to specific
purposes by the entity that seeks the allocation (e.g.: IP addresses)
-- whereas "assignment" refers to the assignment of specific code
points; therfore, I suggest to switch the terms used.

OLD:

 7.  OPT Option Code Allocation Procedure

   Allocations are assigned by expert review.

   Assignment of Option Codes should be liberal, but duplicate
   functionality is to be avoided.

NEW:

|7.  OPT Option Code Assignment Procedure

|  OPT Option Codes are assigned by Expert Review [RFC5226].

   Assignment of Option Codes should be liberal, but duplicate
   functionality is to be avoided.


e)  Section 10 (IANA Considerations)

Because the two sentences contained in it are related to two different
namespaces managed by IANA, for uniformity of the presentation in this
section, I suggest to split the last paragraph of that section into
two:

OLD:

   IETF Standards Action is required to create new entries in the EDNS
   Version Number registry.  Expert Review is required for allocation of
   an EDNS Option Code.

NEW:

   IETF Standards Action is required to create new entries in the EDNS
|  Version Number registry.
|
   Expert Review is required for allocation of an EDNS Option Code.



Kind regards,
  Alfred HÎnes.

-- 

+------------------------+--------------------------------------------+
| TR-Sys Alfred Hoenes   |  Alfred Hoenes   Dipl.-Math., Dipl.-Phys.  |
| Gerlinger Strasse 12   |  Phone: (+49)7156/9635-0, Fax: -18         |
| D-71254  Ditzingen     |  E-Mail:  ah@TR-Sys.de                     |
+------------------------+--------------------------------------------+


From nurit.sprecher@nsn.com  Sat Mar 24 23:51:12 2012
Return-Path: <nurit.sprecher@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 4363B21F85A4 for <ietf@ietfa.amsl.com>; Sat, 24 Mar 2012 23:51:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.498
X-Spam-Level: 
X-Spam-Status: No, score=-6.498 tagged_above=-999 required=5 tests=[AWL=0.101,  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 VfxXHzdezkZQ for <ietf@ietfa.amsl.com>; Sat, 24 Mar 2012 23:51:11 -0700 (PDT)
Received: from demumfd002.nsn-inter.net (demumfd002.nsn-inter.net [93.183.12.31]) by ietfa.amsl.com (Postfix) with ESMTP id C4E4B21F859A for <ietf@ietf.org>; Sat, 24 Mar 2012 23:51:09 -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 q2P6oxP1030633 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sun, 25 Mar 2012 08:50:59 +0200
Received: from DEMUEXC048.nsn-intra.net ([10.159.32.94]) by demuprx017.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id q2P6ovps008560; Sun, 25 Mar 2012 08:50:59 +0200
Received: from DEMUEXC013.nsn-intra.net ([10.150.128.24]) by DEMUEXC048.nsn-intra.net with Microsoft SMTPSVC(6.0.3790.4675);  Sun, 25 Mar 2012 08:50:47 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Subject: RE: Last Call: <draft-ietf-mpls-tp-oam-analysis-08.txt> (AnOverviewoftheOAM Tool Set for MPLS based Transport Networks) toInformational RFC
Date: Sun, 25 Mar 2012 08:50:48 +0200
Message-ID: <E4873516F3FC7547BCFE792C7D94039C0179B7D4@DEMUEXC013.nsn-intra.net>
In-Reply-To: <4F6CE71F.7050003@gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Last Call: <draft-ietf-mpls-tp-oam-analysis-08.txt> (AnOverviewoftheOAM Tool Set for MPLS based Transport Networks) toInformational RFC
Thread-Index: Ac0JOaSk1v50YP43RwCRzaE+gKvsQwBGe2nA
References: <20120309205157.8304.55419.idtracker@ietfa.amsl.com><4F6A5ADB.2090002@gmail.com><E4873516F3FC7547BCFE792C7D94039C0179AE70@DEMUEXC013.nsn-intra.net><4F6BB565.3010008@gmail.com><E4873516F3FC7547BCFE792C7D94039C0179B254@DEMUEXC013.nsn-intra.net> <4F6CE71F.7050003@gmail.com>
From: "Sprecher, Nurit (NSN - IL/Hod HaSharon)" <nurit.sprecher@nsn.com>
To: <huubatwork@gmail.com>, <ietf@ietf.org>
X-OriginalArrivalTime: 25 Mar 2012 06:50:47.0807 (UTC) FILETIME=[9BEB60F0:01CD0A53]
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: 10014
X-purgate-ID: 151667::1332658263-00007415-DFCE82B8/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, 25 Mar 2012 06:51:12 -0000

Tm8gb25lIGhhcyBhc2tlZCB5b3UgdG8gY2hhbmdlIHlvdXIgbWluZCENCg0KLS0tLS1PcmlnaW5h
bCBNZXNzYWdlLS0tLS0NCkZyb206IGlldGYtYm91bmNlc0BpZXRmLm9yZyBbbWFpbHRvOmlldGYt
Ym91bmNlc0BpZXRmLm9yZ10gT24gQmVoYWxmIE9mIGV4dCBIdXViIHZhbiBIZWx2b29ydA0KU2Vu
dDogRnJpZGF5LCBNYXJjaCAyMywgMjAxMiAxMToxMiBQTQ0KVG86IGlldGZAaWV0Zi5vcmcNClN1
YmplY3Q6IFJlOiBMYXN0IENhbGw6IDxkcmFmdC1pZXRmLW1wbHMtdHAtb2FtLWFuYWx5c2lzLTA4
LnR4dD4gKEFuT3ZlcnZpZXdvZnRoZU9BTSBUb29sIFNldCBmb3IgTVBMUyBiYXNlZCBUcmFuc3Bv
cnQgTmV0d29ya3MpIHRvSW5mb3JtYXRpb25hbCBSRkMNCg0KSGFsbG8gTnVyaXQsDQoNCkkgd2ls
bCAqbm90KiBjaGFuZ2UgbXkgbWluZC4NClNvIGl0IGlzIHVzZWxlc3MgdG8gY29udGludWUgdGhp
cyB0aHJlYWQuDQoNCkp1c3QgbWFrZSB0aGUgY2hhbmdlcyBJIHJlcXVlc3RlZC4NCg0KUmVnYXJk
cywgSHV1Yi4NCj09PT09PT09PT09PT09DQoNCk9uIDIzLTAzLTEyIDA4OjExLCBTcHJlY2hlciwg
TnVyaXQgKE5TTiAtIElML0hvZCBIYVNoYXJvbikgd3JvdGU6DQo+IEh1dWIgaGksDQo+IFRoZSBk
b2N1bWVudCB3ZW50IHRocm91Z2ggdHdvIFdHIGxhc3QgY2FsbHMuLi5pdCBpcyBhIHBpdHkgeW91
IGRpZCBub3QNCj4gdXNlIHRoZSBvcHBvcnR1bml0eSB0byBwcm92aWRlIHlvdXIgdXNlZnVsIGNv
bW1lbnQgdGhlbi4NCj4gSSBhbSBzdXJwcmlzZWQgdGhhdCBpdCB0b29rIHlvdSBhbG1vc3QgdHdv
IHllYXJzIGFuZCBzZXZlbiByZXZpc2lvbnMgb2YNCj4gdGhlIGRvY3VtZW50IGJlZm9yZSB5b3Ug
YWN0dWFsbHkgcmVhbGl6ZWQgeW91IGFyZSBub3QgaGFwcHkgd2l0aCB0aGUgd2F5DQo+IHdlIGFj
a25vd2xlZGdlZCB5b3UgdXBvbiB5b3VyIG93biByZXF1ZXN0LiBTdXJlbHkgZm9yIGEgZHJhZnQg
d2hlcmUgdGhlDQo+IHJlbW92YWwgb2YgeW91ciBuYW1lIGZyb20gdGhlIGxpc3Qgb2YgZWRpdG9y
cyB3YXMgZHJpdmVuIGJ5IHlvdXINCj4gY29uY2VybnMgdGhhdCBwZW9wbGUgbWlnaHQgbWlzcmVh
ZCB5b3VyIGludm9sdmVtZW50L3Bvc2l0aW9uLiBJIHdvdWxkDQo+IHRoaW5rIHRoYXQgaW4gdHdv
IHllYXJzIHlvdSB3b3VsZCBnZXQgYXJvdW5kIHRvIGNoZWNraW5nIGZvciB5b3UgdGhhdA0KPiB0
aGUgbmV3IGFja25vd2xlZGdlbWVudCBpcyBzYXRpc2ZhY3RvcnkuDQo+IEJlc3QgcmVnYXJkcywN
Cj4gTnVyaXQNCj4NCj4NCj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4gRnJvbTogaWV0
Zi1ib3VuY2VzQGlldGYub3JnIFttYWlsdG86aWV0Zi1ib3VuY2VzQGlldGYub3JnXSBPbiBCZWhh
bGYgT2YNCj4gZXh0IEh1dWIgdmFuIEhlbHZvb3J0DQo+IFNlbnQ6IEZyaWRheSwgTWFyY2ggMjMs
IDIwMTIgMToyOCBBTQ0KPiBUbzogaWV0ZkBpZXRmLm9yZw0KPiBTdWJqZWN0OiBSZTogTGFzdCBD
YWxsOjxkcmFmdC1pZXRmLW1wbHMtdHAtb2FtLWFuYWx5c2lzLTA4LnR4dD4gIChBbg0KPiBPdmVy
dmlld29mdGhlIE9BTSBUb29sIFNldCBmb3IgTVBMUyBiYXNlZCBUcmFuc3BvcnQgTmV0d29ya3Mp
DQo+IHRvSW5mb3JtYXRpb25hbCBSRkMNCj4NCj4gSGFsbG8gTnVyaXQsDQo+DQo+IFlvdSByZXBs
aWVkOg0KPg0KPj4gVGhhbmtzIGZvciB5b3VyIGNvbW1lbnRzIHRvIElFU0cuLi4NCj4NCj4gVGhl
IElFU0cgZGlkIHNlbmQgdGhlIG1lc3NhZ2UgaW4gb3JkZXIgdG8gbWFrZSBhIGRlY2lzaW9uLCB0
aGF0DQo+IGlzIHdoeSBJIGFkZHJlc3NlZCBteSBjb21tZW50cyB0byB0aGVtLg0KPg0KPj4gV2Ug
Y2FuIGVhc2lseSByZW1vdmUgeW91ciBuYW1lIGZyb20gdGhlIGFja25vd2xlZGdlbWVudCBzZWN0
aW9uLg0KPg0KPiBHbyBhaGVhZCBhbmQgZG8gaXQuDQo+DQo+PiBXZSBwdXQgeW91IHRoZXJlIHVw
b24geW91ciByZXF1ZXN0IQ0KPg0KPiBJdCBpcyBjbGVhciBmcm9tIHlvdXIgcmVzcG9uc2UgdGhh
dCB5b3UgZGlkIG5vdCB1bmRlcnN0YW5kIG15IGluaXRpYWwNCj4gZXhwbGFuYXRpb24gYW5kIHJl
cXVlc3QgdG8gYmUgcmVtb3ZlZCBhcyBlZGl0b3IuDQo+IFdoZW4gSSB3cm90ZSAieW91IGNvdWxk
IG1lbnRpb24gbWUgaW4gdGhlIGFja25vd2xlZGdlbWVudHMgc2VjdGlvbiIgSQ0KPiBkaWQgKm5v
dCogbWVhbiAibWFrZSBpdCBtb3JlIGVhc3kgZm9yIHRoZSByZWFkZXIgdG8gbWlzLWludGVycHJl
dCB0aGUNCj4gYWNrbm93bGVkZ2VtZW50IGZvciBteSByb2xlIGFzIFExMCByYXBwb3J0ZXVyIi4N
Cj4gWW91IGRpZCBub3QgZXZlbiBzZW5kIG1lIHRoZSB0ZXh0IHRoYXQgeW91IHdlcmUgZ29pbmcg
dG8gaW5jbHVkZSB0bw0KPiB2ZXJpZnkgdGhhdCB0aGlzIHRleHQgd291bGQgaGF2ZSB0YWtlbiBh
d2F5IG15IGNvbmNlcm4uDQo+DQo+PiBJIGFtIHNvcnJ5IHRoYXQgSSBhbSBnb2luZyB0byBzaGFy
ZSBvbiB0aGUgbGlzdCBhIHByaXZhdGUgbWFpbCBmcm9tDQo+IHlvdQ0KPj4gdG8gbWUgYnV0IEkg
Y2FuIHNlZSBubyBvdGhlciBjaG9pY2Ugd2l0aCB0aGUgbWFpbCB5b3UgaGF2ZSBqdXN0IHNlbnQN
Cj4gdG8NCj4+IHRoZSBsaXN0Lg0KPg0KPiBJdCBqdXN0IHByb3ZlcyB0aGF0IHlvdSBkaWQgbm90
IHVuZGVyc3RhbmQgbXkgaW5pdGlhbCBleHBsYW5hdGlvbi4NCj4NCj4gUmVnYXJkcywgSHV1Yi4N
Cj4gPT09PT09PT09PT09PT0NCj4+IEFzIHlvdSByZWNhbGwgeW91IHdlcmUgYW4gZWRpdG9yIG9m
IHRoZSBkcmFmdCBhbmQgb24gSnVuZSAyMDEwICh3aGVuDQo+IHRoZQ0KPj4gZG9jdW1lbnQgd2Fz
IGFscmVhZHkgYW4gSUVURiBkb2N1bWVudCBmb3IgYSB3aGlsZSksIHlvdSBoYXZlIGFza2VkIHRv
DQo+PiByZW1vdmUgeW91ciBuYW1lIGZyb20gdGhlIGxpc3Qgb2YgZWRpdG9ycy4gU2VlDQo+PiBo
dHRwOi8vd3d3LmlldGYub3JnL21haWwtYXJjaGl2ZS93ZWIvbXBscy10cC9jdXJyZW50L21zZzA0
MTE4Lmh0bWwuDQo+IHRoZQ0KPj4gbWFpbiByZWFzb24gd2FzIGFzIHlvdSBzYWlkOg0KPj4NCj4+
ICJJdCB3YXMgbXkgaW50ZW50aW9uIHRvIGJlIGVkaXRvciBhcyBhbiBJRVRGIG1lbWJlciwgaG93
ZXZlciB0aGVyZSBhcmUNCj4+IHBlb3BsZSB0aGF0IGludGVycHJldCBteSBuYW1lL3JvbGUgZGlm
ZmVyZW50bHkuIFRoZXkgc2VlIGl0IGFzIGJlaW5nDQo+PiBlZGl0b3IgYXMgYW4gSVRVLVQgbWVt
YmVyIGFuZCByZWNlbnRseSBldmVuIGFzIGJlaW5nIGVkaXRvciBhcyBhbg0KPiBJVFUtVA0KPj4g
UTEwIHJhcHBvcnRldXIuIi4NCj4+DQo+PiBJbiBhIHByaXZhdGUgbWFpbCB5b3Ugc2VudCBtZSBs
YXRlciAoYXR0YWNoZWQpIHlvdSBwcm9wb3NlZCB0byBpbmNsdWRlDQo+PiB5b3UgaW4gdGhlIGFj
a25vd2xlZGdlbWVudCBzZWN0aW9uOg0KPj4NCj4+ICIgWWVzLCByZW1vdmUgbXkgbmFtZSBhcyBl
ZGl0b3IuIEFzIEFkcmlhbiBzdWdnZXN0ZWQsIHlvdSBjb3VsZA0KPiBtZW50aW9uDQo+PiBtZSBp
biB0aGUgYWNrbm93bGVkZ2VtZW50cyBzZWN0aW9uLiINCj4+DQo+PiBJdCBpcyBhIHBpdHkgdGhh
dCB5b3UgZGlkIG5vdCBpbmZvcm0gdXMgdGhhdCB5b3UgY2hhbmdlZCB5b3VyIG1pbmQNCj4gc2lu
Y2UNCj4+IHRoZW4sIGJ1dCBpdCBjYW4gZWFzaWx5IGJlIGZpeGVkIQ0KPj4NCj4+IEJlc3QgcmVn
YXJkcywNCj4+DQo+PiBOdXJpdA0KPj4NCj4+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+
PiBGcm9tOiBpZXRmLWJvdW5jZXNAaWV0Zi5vcmcgW21haWx0bzppZXRmLWJvdW5jZXNAaWV0Zi5v
cmddIE9uIEJlaGFsZg0KPiBPZg0KPj4gZXh0IEh1dWIgdmFuIEhlbHZvb3J0DQo+PiBTZW50OiBU
aHVyc2RheSwgTWFyY2ggMjIsIDIwMTIgMTI6NDkgQU0NCj4+IFRvOiBpZXRmQGlldGYub3JnDQo+
PiBTdWJqZWN0OiBSZTogTGFzdCBDYWxsOjxkcmFmdC1pZXRmLW1wbHMtdHAtb2FtLWFuYWx5c2lz
LTA4LnR4dD4gIChBbg0KPj4gT3ZlcnZpZXdvZiB0aGUgT0FNIFRvb2wgU2V0IGZvciBNUExTIGJh
c2VkIFRyYW5zcG9ydCBOZXR3b3JrcykNCj4+IHRvSW5mb3JtYXRpb25hbCBSRkMNCj4+DQo+PiBJ
RVNHLA0KPj4NCj4+IEkgZG8gKk5PVCogc3VwcG9ydCB0aGlzIGRyYWZ0IHVubGVzcyB0aGUgZm9s
bG93aW5nIGNoYW5nZXMgYXJlIG1hZGU6DQo+Pg0KPj4gVGhlIGZpcnN0IHBhcmFncmFwaCBvZiBz
ZWN0aW9uIDggQWNrbm93bGVkZ2VtZW50cyBoYXMgdG8gYmUgcmVtb3ZlZDoNCj4+DQo+PiBJdCBp
cyBhbiBhdHRlbXB0IHRvIGNhcHR1cmUgaGlzdG9yeSwgYnV0IGxhY2tzIGFjY3VyYWN5Lg0KPj4N
Cj4+IFJlbW92YWwgZG9lcyBub3QgaW1wYWN0IHRoZSB0ZWNobmljYWwgaW5mb3JtYXRpb24gaW4g
dGhlIGRyYWZ0Ow0KPj4NCj4+IHRoZSB0b29scyBoYXZlIGV2b2x2ZWQgc2lnbmlmaWNhbnRseSBm
cm9tIHRoZSBzdHJhd21hbiB0b29scyBwcm9wb3NlZA0KPj4NCj4+IGluIFN0b2NraG9sbTsgc29t
ZSBtZW1iZXJzIG9mIHRoZSBNRUFEIHRlYW0gKEkgYW0gb25lIG9mIHRoZW0pIGRvIG5vdA0KPj4N
Cj4+IGNvbnNpZGVyIHRoYXQgYW4gYWdyZWVtZW50IG9uIHRoaXMgcHJvcG9zYWwgd2FzIHJlYWNo
ZWQuDQo+Pg0KPj4gSSBhbHNvIHJlcXVlc3QgdGhlIHJlbW92YWwgb2YgbXkgbmFtZSBmcm9tIHRo
aXMgYWNrbm93bGVkZ2VtZW50cw0KPiBzZWN0aW9uDQo+Pg0KPj4gc2luY2UgSSBkbyBub3Qgc3Vw
cG9ydCB0aGlzIHRvb2wgc2V0LCBuZWl0aGVyIGFzIGFuIGluZGl2aWR1YWwgbm9yIGFzDQo+Pg0K
Pj4gSVRVLVQgUTEwIHJhcHBvcnRldXIuIFRoZSBsYXR0ZXIgaXMgaW1wbGllZCBieSBtZW50aW9u
aW5nIG15IG5hbWUgaW4NCj4+DQo+PiB0aGUgc2FtZSBzZW50ZW5jZSBhcyBhIFdHIGNoYWlyIGFu
ZCBBRHMuDQo+Pg0KPj4gUmVnYXJkcywgSHV1Yi4NCj4+DQo+PiA9PT09PT09PT09PT09DQo+Pg0K
Pj4gICA+ICBUaGUgSUVTRyBoYXMgcmVjZWl2ZWQgYSByZXF1ZXN0IGZyb20gdGhlIE11bHRpcHJv
dG9jb2wgTGFiZWwNCj4gU3dpdGNoaW5nIFdHDQo+Pg0KPj4gICA+ICAobXBscykgdG8gY29uc2lk
ZXIgdGhlIGZvbGxvd2luZyBkb2N1bWVudDoNCj4+DQo+PiAgID4gIC0gJ0FuIE92ZXJ2aWV3IG9m
IHRoZSBPQU0gVG9vbCBTZXQgZm9yIE1QTFMgYmFzZWQgVHJhbnNwb3J0DQo+IE5ldHdvcmtzJw0K
Pj4NCj4+ICAgPiAgPGRyYWZ0LWlldGYtbXBscy10cC1vYW0tYW5hbHlzaXMtMDgudHh0PiAgYXMg
YW4gSW5mb3JtYXRpb25hbCBSRkMNCj4+DQo+PiAgID4NCj4+DQo+PiAgID4gIFRoZSBJRVNHIHBs
YW5zIHRvIG1ha2UgYSBkZWNpc2lvbiBpbiB0aGUgbmV4dCBmZXcgd2Vla3MsIGFuZA0KPiBzb2xp
Y2l0cw0KPj4NCj4+ICAgPiAgZmluYWwgY29tbWVudHMgb24gdGhpcyBhY3Rpb24uIFBsZWFzZSBz
ZW5kIHN1YnN0YW50aXZlIGNvbW1lbnRzIHRvDQo+IHRoZQ0KPj4NCj4+ICAgPiAgaWV0ZkBpZXRm
Lm9yZzxtYWlsdG86aWV0ZkBpZXRmLm9yZz4gIG1haWxpbmcgbGlzdHMgYnkgMjAxMi0wMy0yMy4N
Cj4+IEV4Y2VwdGlvbmFsbHksIGNvbW1lbnRzIG1heSBiZQ0KPj4NCj4+ICAgPiAgc2VudCB0byBp
ZXNnQGlldGYub3JnPG1haWx0bzppZXNnQGlldGYub3JnPiAgaW5zdGVhZC4gSW4gZWl0aGVyDQo+
IGNhc2UsDQo+PiBwbGVhc2UgcmV0YWluIHRoZQ0KPj4NCj4+ICAgPiAgYmVnaW5uaW5nIG9mIHRo
ZSBTdWJqZWN0IGxpbmUgdG8gYWxsb3cgYXV0b21hdGVkIHNvcnRpbmcuDQo+Pg0KPj4gICA+DQo+
Pg0KPj4gICA+ICBBYnN0cmFjdA0KPj4NCj4+ICAgPg0KPj4NCj4+ICAgPiAgVGhpcyBkb2N1bWVu
dCBwcm92aWRlcyBhbiBvdmVydmlldyBvZiB0aGUgT0FNIHRvb2xzZXQgZm9yIE1QTFMNCj4gYmFz
ZWQNCj4+DQo+PiAgID4gIFRyYW5zcG9ydCBOZXR3b3Jrcy4gVGhlIHRvb2xzZXQgY29uc2lzdHMg
b2YgYSBjb21wcmVoZW5zaXZlIHNldCBvZg0KPj4NCj4+ICAgPiAgZmF1bHQgbWFuYWdlbWVudCBh
bmQgcGVyZm9ybWFuY2UgbW9uaXRvcmluZyBjYXBhYmlsaXRpZXMgKG9wZXJhdGluZw0KPj4NCj4+
ICAgPiAgaW4gdGhlIGRhdGEtcGxhbmUpIHdoaWNoIGFyZSBhcHByb3ByaWF0ZSBmb3IgdHJhbnNw
b3J0IG5ldHdvcmtzIGFzDQo+Pg0KPj4gICA+ICByZXF1aXJlZCBpbiBSRkMgNTg2MCBhbmQgc3Vw
cG9ydCB0aGUgbmV0d29yayBhbmQgc2VydmljZXMgYXQNCj4+DQo+PiAgID4gIGRpZmZlcmVudCBu
ZXN0ZWQgbGV2ZWxzLiBUaGlzIG92ZXJ2aWV3IGluY2x1ZGVzIGEgYnJpZWYgcmVjYXAgb2YNCj4+
DQo+PiAgID4gIE1QTFMtVFAgT0FNIHJlcXVpcmVtZW50cyBhbmQgZnVuY3Rpb25zLCBhbmQgb2Yg
Z2VuZXJpYyBtZWNoYW5pc21zDQo+Pg0KPj4gICA+ICBjcmVhdGVkIGluIHRoZSBNUExTIGRhdGEg
cGxhbmUgdG8gYWxsb3cgdGhlIE9BTSBwYWNrZXRzIHJ1biBpbi1iYW5kDQo+Pg0KPj4gICA+ICBh
bmQgc2hhcmUgdGhlaXIgZmF0ZSB3aXRoIGRhdGEgcGFja2V0cy4gVGhlIHByb3RvY29sIGRlZmlu
aXRpb25zDQo+IGZvcg0KPj4NCj4+ICAgPiAgZWFjaCBvZiB0aGUgTVBMUy1UUCBPQU0gdG9vbHMg
YXJlIGRlZmluZWQgaW4gc2VwYXJhdGUgZG9jdW1lbnRzDQo+IChSRkNzDQo+Pg0KPj4gICA+ICBv
ciBXb3JraW5nIEdyb3VwIGRyYWZ0cykgd2hpY2ggYXJlIHJlZmVyZW5jZWQgYnkgdGhpcyBkb2N1
bWVudC4NCj4+ICAgPg0KPj4gICA+DQo+PiAgID4gIFRoZSBmaWxlIGNhbiBiZSBvYnRhaW5lZCB2
aWENCj4+ICAgPiAgaHR0cDovL2RhdGF0cmFja2VyLmlldGYub3JnL2RvYy9kcmFmdC1pZXRmLW1w
bHMtdHAtb2FtLWFuYWx5c2lzLw0KPj4gICA+DQo+PiAgID4gIElFU0cgZGlzY3Vzc2lvbiBjYW4g
YmUgdHJhY2tlZCB2aWENCj4+ICAgPg0KPiBodHRwOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9j
L2RyYWZ0LWlldGYtbXBscy10cC1vYW0tYW5hbHlzaXMvYmFsbG90Lw0KPj4gICA+DQo+PiAgID4N
Cj4+ICAgPiAgTm8gSVBSIGRlY2xhcmF0aW9ucyBoYXZlIGJlZW4gc3VibWl0dGVkIGRpcmVjdGx5
IG9uIHRoaXMgSS1ELg0KPj4gICA+ICBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX18NCj4+ICAgPiAgSUVURi1Bbm5vdW5jZSBtYWlsaW5nIGxpc3QNCj4+ICAgPiAg
SUVURi1Bbm5vdW5jZUBpZXRmLm9yZzxtYWlsdG86SUVURi1Bbm5vdW5jZUBpZXRmLm9yZz4NCj4+
ICAgPiAgaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9pZXRmLWFubm91bmNl
DQo+Pg0KDQoNCi0tIA0KKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioq
KioqKioqKioqKioqKioqKioqKioqKioNCiAgICAgICAgICAgICAgICAgICAgICAgICAg5oiR54ix
5aSW54K55LiA5LiD5LiJ5LiADQo=

From RCosta@ptinovacao.pt  Sun Mar 25 04:11:53 2012
Return-Path: <RCosta@ptinovacao.pt>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9A2A321F856F for <ietf@ietfa.amsl.com>; Sun, 25 Mar 2012 04:11:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.074
X-Spam-Level: 
X-Spam-Status: No, score=-2.074 tagged_above=-999 required=5 tests=[AWL=-0.075, BAYES_00=-2.599, J_CHICKENPOX_15=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cKiEZM8mhyTj for <ietf@ietfa.amsl.com>; Sun, 25 Mar 2012 04:11:52 -0700 (PDT)
Received: from owa.ptinovacao.pt (webmail.ptinovacao.pt [194.65.138.99]) by ietfa.amsl.com (Postfix) with ESMTP id 2240621F84F4 for <ietf@ietf.org>; Sun, 25 Mar 2012 04:11:51 -0700 (PDT)
Received: from INOAVREX11.ptin.corpPT.com ([10.112.15.122]) by inoavrcas01.ptin.corpPT.com ([10.112.15.99]) with mapi; Sun, 25 Mar 2012 12:11:50 +0100
From: Rui Costa <RCosta@ptinovacao.pt>
To: t.petch <daedulus@btconnect.com>
Date: Sun, 25 Mar 2012 12:11:48 +0100
Subject: RE: FW: LastCall:<draft-betts-itu-oam-ach-code-point-03.txt>(Allocationofan Associated Channel Code Point for Use byITU-T Ethernetbased OAM) toInformational RFC
Thread-Topic: FW: LastCall:<draft-betts-itu-oam-ach-code-point-03.txt>(Allocationofan Associated Channel Code Point for Use byITU-T Ethernetbased OAM) toInformational RFC
Thread-Index: Ac0I5HAPwtuKOzcbSwu0/24/jmYahABklgsg
Message-ID: <52981DB05D3C5247A12D0AEE309F3CC202444240C386@INOAVREX11.ptin.corpPT.com>
References: <52981DB05D3C5247A12D0AEE309F3CC202444240C161@INOAVREX11.ptin.corpPT.com> <CAG4d1reb=bWp09uT-tOLyvSa7q-W5a-LnpGphngg-+KR1+TcKg@mail.gmail.com> <00c001cd08db$7323d2c0$4001a8c0@gateway.2wire.net>
In-Reply-To: <00c001cd08db$7323d2c0$4001a8c0@gateway.2wire.net>
Accept-Language: pt-PT
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: pt-PT
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: Sun, 25 Mar 2012 11:11:53 -0000

IldlIGNlcnRhaW5seSBoYXZlIHJ1bm5pbmcgY29kZSwgd2lkZWx5IGRlcGxveWVkIChhbHRob3Vn
aCBteSByZXF1ZXN0IG9uIHRoZSBNUExTIGxpc3QgYXMgdG8gd2hpY2ggbWFudWZhY3R1cmVycycg
Ym94ZXMgd2VyZSBpbnZvbHZlZCBuZXZlciBkaWQgZ2V0IGFuc3dlcmVkOi0oIgkNCkhvcGUgdGhl
c2UgaGVscDoJDQpodHRwOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1mYW5nLW1wbHMtdHAt
b2FtLWNvbnNpZGVyYXRpb25zCQ0KaHR0cDovL3d3dy5lYW50Yy5jb20vZmlsZWFkbWluL2VhbnRj
L2Rvd25sb2Fkcy9ldmVudHMvMjAwNy0yMDEwL0NFV0MwOS9FQU5UQy1DRVdDMjAwOS1XaGl0ZVBh
cGVyLXYxXzIucGRmCQ0KDQpSZWdhcmRzLAkNClJ1aQ0KDQotLS0tLU9yaWdpbmFsIE1lc3NhZ2Ut
LS0tLQ0KRnJvbTogdC5wZXRjaCBbbWFpbHRvOmRhZWR1bHVzQGJ0Y29ubmVjdC5jb21dIA0KU2Vu
dDogc2V4dGEtZmVpcmEsIDIzIGRlIE1hcsOnbyBkZSAyMDEyIDA5OjU4DQpUbzogQWxpYSBBdGxh
czsgUnVpIENvc3RhDQpDYzogaWV0ZkBpZXRmLm9yZw0KU3ViamVjdDogUmU6IEZXOiBMYXN0Q2Fs
bDo8ZHJhZnQtYmV0dHMtaXR1LW9hbS1hY2gtY29kZS1wb2ludC0wMy50eHQ+KEFsbG9jYXRpb25v
ZmFuIEFzc29jaWF0ZWQgQ2hhbm5lbCBDb2RlIFBvaW50IGZvciBVc2UgYnlJVFUtVCBFdGhlcm5l
dGJhc2VkIE9BTSkgdG9JbmZvcm1hdGlvbmFsIFJGQw0KDQotLS0tLSBPcmlnaW5hbCBNZXNzYWdl
IC0tLS0tDQpGcm9tOiAiQWxpYSBBdGxhcyIgPGFrYXRsYXNAZ21haWwuY29tPg0KVG86ICJSdWkg
Q29zdGEiIDxSQ29zdGFAcHRpbm92YWNhby5wdD4NCkNjOiA8aWV0ZkBpZXRmLm9yZz4NClNlbnQ6
IFRodXJzZGF5LCBNYXJjaCAyMiwgMjAxMiAxMDowNyBQTQ0KDQpSdWksDQoNClBlcmhhcHMgbW9y
ZSBmYW1pbGlhcml0eSB3aXRoIHRoZSByZWxhdGVkIGhpc3Rvcnkgb3ZlciB0aGUgbGFzdCBzZXZl
cmFsIHllYXJzIHdvdWxkIGhlbHA/ICBJIGNhbiByZWNvbW1lbmQgdGhlIE1QTFMgbGlzdCBhcmNo
aXZlcy4NCk90aGVyd2lzZSwgSSBmaW5kIHRoaXMgcmVtYXJrYWJseSBkaXNpbmdlbnVvdXMuDQoN
ClRoaXMgaXMgYSBjYXNlIG9mIGEgc2Vjb25kIHNvbHV0aW9uIHRoYXQgd2FzIGNsZWFybHkgcmVq
ZWN0ZWQgYnkgdGhlIE1QTFMgd29ya2luZyBncm91cCAoZGVzcGl0ZSBpbi1wZXJzb24gaGlzdHJp
b25pY3MgY2F1c2luZyB0aGUgQURzIHRvIGhhdmUgdG8gdGhyZWF0ZW4gdG8gY2xvc2UgZG93biB0
aGUgV0cgbWVldGluZykuICBUaGVuIHRoZSBzb2x1dGlvbiB3YXMgdGFrZW4gdG8gdGhlIElUVSBz
dHVkeSBncm91cCAtIHdoZXJlIGl0IGNvdWxkIGFsc28gbm90IGdldCBlbm91Z2ggdHJhY3Rpb24g
Zm9yIHRoZWlyIG5vcm1hbCBwcm9jZXNzLiAgSXQgaXMgc3RpbGwgbm90IGFwcHJvdmVkIGFzIGEg
cmVjb21tZW5kYXRpb24uDQoNCjx0cD4NCkFsaWENCg0KV2VyZSB0aGUgcm9sZXMgcmV2ZXJzZWQg
YW5kIHRoZSBzZWNvbmQgc29sdXRpb24gYmUgYSBwcm9kdWN0IG9mIHRoZSBJRVRGIHRoYXQgdGhl
IElFVEYgd2VyZSB0cnlpbmcgdG8gZ2V0IG1vcmUgd2lkZWx5IGFwcHJvdmVkLCB3b3VsZCB0aGUg
SUVURiBhbGxvY2F0ZSBhIGNvZGUgcG9pbnQ/DQoNCkkgdGhpbmsgdGhhdCBpdCB3b3VsZC4gIFdl
IGNlcnRhaW5seSBoYXZlIHJ1bm5pbmcgY29kZSwgd2lkZWx5IGRlcGxveWVkIChhbHRob3VnaCBt
eSByZXF1ZXN0IG9uIHRoZSBNUExTIGxpc3QgYXMgdG8gd2hpY2ggbWFudWZhY3R1cmVycycgYm94
ZXMgd2VyZSBpbnZvbHZlZCBuZXZlciBkaWQgZ2V0IGFuc3dlcmVkOi0oLg0KDQpXZSBoYXZlIGEg
cm91Z2ggY29uc2Vuc3VzOyBub3QgdW5hbmltaXR5LCBhbmQgbm90IGVub3VnaCBvZiBhIGNvbnNl
bnN1cyB0byBzYXRpc2Z5IHRoZSBwcm9jZXNzZXMgb2YgdGhlIElUVS1UIGJ1dCBJIHRoaW5rIGVu
b3VnaCB0byBzYXRpc2Z5IHRoZSBjb25zZW5zdXMtanVkZ2VycyBvZiB0aGUgSUVURiAoYXMgZXZl
ciwgd2UgZG8gbm90IHZvdGUsIGEgbWFqb3JpdHkgb2YgZS1tYWlscyBmb3Igb25lIHBvaW50IG9m
IHZpZXcgbWF5IGJlIGRpc2NvdW50ZWQsIGl0IGlzIHRoZSBxdWFsaXR5IG9mIHRoZSB2aWV3cyBl
eHByZXNzZWQgdGhhdCBtYXR0ZXJzIGFzIG11Y2ggb3IgbW9yZSkuDQoNClNvIGFwcGx5aW5nIHRo
ZSBzdGFuZGFyZHMgdG8gd2hpY2ggd2Ugd29yaywgSSB0aGluayB0aGlzIGlzIGFub3RoZXIgcmVh
c29uIHdoeSB3ZSBzaG91bGQgYXBwcm92ZSB0aGlzIEktRC4NCg0KVG9tIFBldGNoDQoNCjwvdHA+
DQpUbyBpbXBseSB0aGF0IHRoZSBJRVRGIHNob3VsZCBzaW1wbHkgdHJ1c3QgdGhlIGFsbG9jYXRl
ZCBBQ0ggY29kZSBwb2ludCB0byBub3QgYmUgYWJ1c2VkIGJvdGggc2VlbXMgb3B0aW1pc3RpYyBh
bmQgc2V0cyBhIGRyZWFkZnVsIHByZWNlZGVudC4NCg0KTWFraW5nIGFuIGFsbG9jYXRpb24gYXZh
aWxhYmxlIGZvciBhbiBhcHByb3ZlZCByZWNvbW1lbmRhdGlvbiB2ZXJzaW9uIGlzIGEgdG9sZXJh
YmxlIHdheSBvZiByZWR1Y2luZyB0aGUgZGVsaWJlcmF0ZSB1c2Ugb2YgYW4gZXhwZXJpbWVudGFs
DQp2YWx1ZS4gICBIYW5kaW5nIHRoZSBrZXlzIG92ZXIgZm9yIGFueSBjb25jZWl2YWJsZSB1c2Us
IG9yIGV2ZW4ganVzdA0KdGhlIHVzZXMgaW4gdGhlIE9BTSBSRkMgdGhhdCBoYXZlIGJlZW4gYWRl
cXVhdGVseSBtZXQgYnkgSUVURiBXRy1jb25zZW5zdXMgYmFzZWQgdGVjaG5vbG9neSwgZG9lcyBu
b3Qgc2VlbSBhcHByb3ByaWF0ZS4NCg0KQWxpYQ0KDQoNCg0KT24gVGh1LCBNYXIgMjIsIDIwMTIg
YXQgMTA6NDIgQU0sIFJ1aSBDb3N0YSA8UkNvc3RhQHB0aW5vdmFjYW8ucHQ+IHdyb3RlOg0KPiBJ
IGZhaWwgdG8gdW5kZXJzdGFuZCB0aGUgaXNzdWUgdW5kZXIgZGlzY3Vzc2lvbi4NCj4NCj4gQ2Fu
J3QgaW1hZ2luZSBJRUVFIGRlbnlpbmcgdG8gZ3JhbnQgRXRoZXJ0eXBlIDB4ODZERC4gSWYsIGhv
d2V2ZXIsIA0KPiBmcm9tIGFic3VyZA0KdGhhdCBoYWQgaGFwcGVuZWQsIHdvdWxkIHRoZSB3b3Js
ZCBzdG9wIG9yIHdvdWxkIHdlIHRha2UgdGhlIHNhbWUgaW5mb3JtYXRpb24gZnJvbSB0aGUgSVAg
aGVhZGVyIHZlcnNpb24gZmllbGQ/DQo+DQo+IFJlZ2FyZHMsDQo+IFJ1aQ0KPg0KPg0KPiAtLS0t
LU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPiBGcm9tOiBpZXRmLWJvdW5jZXNAaWV0Zi5vcmcgW21h
aWx0bzppZXRmLWJvdW5jZXNAaWV0Zi5vcmddIE9uIEJlaGFsZiANCj4gT2YgQWxpYQ0KQXRsYXMN
Cj4gU2VudDogcXVhcnRhLWZlaXJhLCAyMSBkZSBNYXLDp28gZGUgMjAxMiAxNTozMA0KPiBUbzog
RCdBbGVzc2FuZHJvIEFsZXNzYW5kcm8gR2VyYXJkbw0KPiBDYzogaWV0ZkBpZXRmLm9yZw0KPiBT
dWJqZWN0OiBSZTog15TXoNeT15XXnzogUkU6IExhc3QNCkNhbGw6PGRyYWZ0LWJldHRzLWl0dS1v
YW0tYWNoLWNvZGUtcG9pbnQtMDMudHh0PihBbGxvY2F0aW9ub2YgYW4gQXNzb2NpYXRlZCBDaGFu
bmVsIENvZGUgUG9pbnQgZm9yIFVzZSBieUlUVS1UIEV0aGVybmV0YmFzZWQgT0FNKSB0byBJbmZv
cm1hdGlvbmFsIFJGQw0KPg0KPiBDb25zaWRlcmluZyB0aGF0IHRoZSBuZWVkIGZvciB0aGlzIGNv
ZGUgcG9pbnQgaXMgYSByZXN1bHQgb2YgdGhlIElUVSANCj4gbm90IGZ1bGx5IGNvbXBseWluZyB3
aXRoIHRoZSBJRVRGIGFncmVlbWVudCwgSSBjYW5ub3QgYWdyZWUgdGhhdCB3ZSANCj4gc2hvdWxk
IHNpbXBseSBhbGxvY2F0ZSBhIGNvZGUgcG9pbnQgZm9yIHdoYXRldmVyIHRoZSBJVFUgd2FudHMg
dG8gZG8gDQo+IGluIHRoZSBmdXR1cmUuDQo+DQo+IEl0IHNlZW1zIHRoZSBiZXN0IG9mIHRoZSBv
cHRpb25zIHRvIGFsbG9jYXRlIGEgY29kZSBwb2ludCAobXVjaCBiZXR0ZXIgDQo+IHRoYW4gc3F1
YXR0aW5nKSAtIGJ1dCB0aWUgaXQgdG8gYSBzdGFibGUgcmVmZXJlbmNlLiBJZiB0aGUgSVRVIGNh
bid0IA0KPiBwcm92aWRlIGEgc3RhYmxlIHJlZmVyZW5jZSwgdGhlbiBwZXJoYXBzIGFuIFJGQyBp
cyB0aGUgYmVzdCB3YXkuDQo+IFRoZXJlIGFyZSBsb3RzIG9mIGZvbGtzIHdpdGggb3BpbmlvbnMg
b24gdGhlIGJlc3QgcHJvY2VkdXJlLCBidXQgSSANCj4gY2VydGFpbmx5IGRvbid0IHN1cHBvcnQg
dGhlIGlkZWEgb2Ygbm90IHJlc3RyaWN0aW5nIHRoZSB1c2FnZSB0byB3aGF0IA0KPiBpcyBjbGVh
cmx5IGRlZmluZWQuDQo+DQo+IEFsaWENCg0KDQo=

From ietf.fact.check@gmail.com  Sun Mar 25 06:36:39 2012
Return-Path: <ietf.fact.check@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 23DCC21F84B4 for <ietf@ietfa.amsl.com>; Sun, 25 Mar 2012 06:36:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.11
X-Spam-Level: 
X-Spam-Status: No, score=-1.11 tagged_above=-999 required=5 tests=[BAYES_20=-0.74, RCVD_IN_DNSWL_LOW=-1, US_DOLLARS_3=0.63]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0PoKKIctlJoJ for <ietf@ietfa.amsl.com>; Sun, 25 Mar 2012 06:36:38 -0700 (PDT)
Received: from mail-iy0-f194.google.com (mail-iy0-f194.google.com [209.85.210.194]) by ietfa.amsl.com (Postfix) with ESMTP id 640AA21F84AF for <ietf@ietf.org>; Sun, 25 Mar 2012 06:36:38 -0700 (PDT)
Received: by iabz21 with SMTP id z21so3031543iab.1 for <ietf@ietf.org>; Sun, 25 Mar 2012 06:36:38 -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 :content-transfer-encoding; bh=eILEjjvf/RwkGoTG74W2m4FR4/uNyr3044JgjdyqYX0=; b=qulqpzDeMs42CJqV9xd7ITu5ibSc1XFPrtQtqdkTKr1Z0tSXGMbMg0NKEeqJlW/hYO UvWnl4Jo2rvkDQ6mj+lD55X2tB1c2ud0geP6ts+eUABSxPodQdWfpqlSZghVa3eLipA9 Sdt1tvw83TRqKD5t6fCUaBjD6/nrhqLVj86QzJL9I0VNlIVJGiJl53AkqaCwwYp3+T/R Ft4O0EeV6BfcxdUy0p1MeHUiCKi9/hm/XP3bpsqnwwtY/ZL4hh5LzXkodw/woFLyeorm J31LcJr6+MkaNfArPEzWkyacxzq9Qkj4WhkKanDua4Lc9O8hlCK5Wtq0WKRdLaV5/qE1 xq4A==
MIME-Version: 1.0
Received: by 10.50.149.131 with SMTP id ua3mr3362547igb.41.1332682598101; Sun, 25 Mar 2012 06:36:38 -0700 (PDT)
Received: by 10.50.171.38 with HTTP; Sun, 25 Mar 2012 06:36:38 -0700 (PDT)
Date: Sun, 25 Mar 2012 08:36:38 -0500
Message-ID: <CANwOnkGRwokhAC44g10xRaOgQxrkfm=gxJRDhszSXyv-x4-Ziw@mail.gmail.com>
Subject: Fact.Check IETF Meeting - 1460 registrations:
From: Jim Fleming <ietf.fact.check@gmail.com>
To: ietf@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 25 Mar 2012 13:37:38 -0000

IETF Meeting Registration System
Attendance List
IETF 83
Paris, France
March 25-30, 2012
Last updated Sunday, March 25, 2012 at 06:24:32 PDT
1460 registrations:
https://www.ietf.org/registration/ietf83/attendance.py

Is the ISOC annual buget now $34,000,000 ?

What is the ICANN annual budget ?

How many $600,000 per year non-profit public benefit employees are now
in The.Community?

Kruse	Megan	Internet Society	US	Yes 	YES
Minton	Graham	Internet Society	CH	No =09
Hoyt	Scott	Internet Society	US	No =09
O'Donoghue	Karen	Internet Society	US	Yes =09
St Amour	Lynn 	Internet Society	US	No 	YES
York	Dan	Internet Society	US	Yes 	YES
Daigle	Leslie	Internet Society	US	Yes =09
Roseman	Walda	Internet Society	US	No =09
Robachevsky	Andrei	Internet Society	NL	No =09
Lynch	Lucy	Internet Society	US	Yes =09
Conte	Steve	Internet Society	US	Yes =09
Sebuck	Kathy	Internet Society	US	No 	YES
Kummer	Markus	Internet Society	CH	Yes =09
Craemer	Kevin	Internet Society	US	Yes =09
Seidler	Nicolas	Internet Society	CH	Yes =09
Runnegar	Christine	Internet Society	CH	Yes =09
Cowieson	Toral	Internet Society	US	No =09
Dvorshak	Andrew	Internet Society	US	No =09
Brigner	Paul	Internet Society	US	No 	YES
Greenspan	Robin	Internet Society	US	No =09
Ford	Mat	Internet Society (ISOC)	US	No =09

Abley	Joseph	ICANN	CA	Yes =09
Manderson	Terry	ICANN	AU	Yes =09
liang	pearl	ICANN	US	Yes =09
Okubo	Tomofumi	ICANN	US	Yes =09
Sheng	Steve	ICANN	US	Yes =09
Arias	Francisco	ICANN	US	Yes 	YES
Raveh	Simon	ICANN	US	No =09
Bird Gerich	Elise	ICANN	US	Yes =09
Lee	Xiaodong	ICANN	US	No =09
Bachollet	Sebastien	ICANN	US	Yes =09
Sadowsky	George	ICANN	US	No 	YES
Cotton	Michelle	ICANN - IANA	US	No =09

Huston	Geoff	APNIC	AU	Yes =09
Ellacott	Byron	APNIC	AU	No
Newton	Andrew	ARIN	US	Yes 	YES
Kosters	Mark	ARIN	US	No =09
Aronson	Cathy	ARIN Advisory Council	US	Yes =09
Servin	Arturo	LACNIC	UY	No 	YES
Bruijnzeels	Tim	RIPE NCC	NL	No =09
Juhasz	Miklos	RIPE NCC	NL	No =09
Wijnen	Bert	RIPE NCC	NL	Yes =09
Buddhdev	Anand	RIPE NCC	NL	No =09
Kuehne	Mirjam	RIPE NCC	NL	No
AKPLOGAN	ADIEL AYODELE	AfriNIC	MU	No =09
AINA	Alain PATRICK	AfriNIC Ltd	TG	Yes

Dupont	Francis	ISC	FR	Yes =09
Damas	Jo=E3o	ISC	ES	Yes =09
kaeo	merike	ISC	US	No =09
Morris	Stephen	ISC	GB	Yes 	YES
Selkirk	Paul	ISC	US	No =09
Woolf	Suzanne	ISC	US	Yes =09
Kerr	Shane	ISC (Internet Systems Consortium)	NL	Yes =09
Woodman	AListair	ISC.org	US	Yes 	YES
Mrugalski	Tomek	ISC/Gdansk University of Technology	PL	Yes

From prvs=1431553845=jordi.palet@consulintel.es  Sun Mar 25 07:27:38 2012
Return-Path: <prvs=1431553845=jordi.palet@consulintel.es>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 091AB21F84D1 for <ietf@ietfa.amsl.com>; Sun, 25 Mar 2012 07:27:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.969
X-Spam-Level: 
X-Spam-Status: No, score=-105.969 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100, US_DOLLARS_3=0.63]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pfPC1cZWRi5c for <ietf@ietfa.amsl.com>; Sun, 25 Mar 2012 07:27:37 -0700 (PDT)
Received: from consulintel.es (mail.consulintel.es [213.172.48.142]) by ietfa.amsl.com (Postfix) with ESMTP id 5B8C321F84A5 for <ietf@ietf.org>; Sun, 25 Mar 2012 07:27:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1332685482; x=1333290282; q=dns/txt; h=DomainKey-Signature: Received:User-Agent:Date:Subject:From:To:Message-ID:Thread-Topic: In-Reply-To:Mime-version:Content-type:Content-transfer-encoding: Reply-To; bh=KGC5W/KJLfkLzGJDXEj9FGKvSWiHV+wxRlhvn3ittGo=; b=Kvb LhpaAES09hnX3mJWUkXgkvKaC045ooGDjKKPnCb+bbm8f7cnkETY2b90JXXhCVrf jerX7a4n1t7eNHHe9b+LTmwzGe+BJK7rXVgOhxkdbb6NZXJhMjNUyWb9AyGFsPzn FcU9waI6rFNuLnMRAJV3At//OUfySBcWGlPel/K4=
DomainKey-Signature: a=rsa-sha1; s=MDaemon; d=consulintel.es; c=simple; q=dns; h=from:message-id; b=qLNIHC/asDrOrEaC7zX3QVpY42ZZ0FF3KJWUcMfASqcX0vQGNV9TIIfq2/W1 mg7NklVtrXCTiEAQUCXxCATeVaK1dlA7E+YM/rOni/4bEK6kEg5YrT0EW +Y7JSshGVvlVcHkYcUOb7GoGqS8+VAWp8/ff+NfbBzTfU0t07/RiEQ=;
X-MDAV-Processed: consulintel.es, Sun, 25 Mar 2012 16:24:42 +0200
Received: from [10.0.0.105] by consulintel.es (MDaemon PRO v11.0.3) with ESMTP id md50004130959.msg for <ietf@ietf.org>; Sun, 25 Mar 2012 16:24:42 +0200
X-Spam-Processed: consulintel.es, Sun, 25 Mar 2012 16:24:42 +0200 (not processed: message from trusted or authenticated source)
X-Authenticated-Sender: jordi.palet@consulintel.es
X-HashCash: 1:20:120325:md50004130959::2SwFmhrbQG5znnB1:00003jRv
X-Return-Path: prvs=1431553845=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ietf@ietf.org
User-Agent: Microsoft-MacOutlook/14.14.0.111121
Date: Sun, 25 Mar 2012 16:27:21 +0200
Subject: Re: Fact.Check IETF Meeting - 1460 registrations:
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: <ietf.fact.check@gmail.com>, <ietf@ietf.org>
Message-ID: <CB94F6A8.6B3E8%jordi.palet@consulintel.es>
Thread-Topic: Fact.Check IETF Meeting - 1460 registrations:
In-Reply-To: <CANwOnkGRwokhAC44g10xRaOgQxrkfm=gxJRDhszSXyv-x4-Ziw@mail.gmail.com>
Mime-version: 1.0
Content-type: text/plain; charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: jordi.palet@consulintel.es
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 25 Mar 2012 14:27:38 -0000

Hi Jim,

I don't think your questions are relevant to this IETF list.

You can try in ISOC or ICANN exploders.

Regards,
Jordi Palet
(speaking as IETF Seargeant-at-arms)







-----Mensaje original-----
De: Jim Fleming <ietf.fact.check@gmail.com>
Responder a: <ietf.fact.check@gmail.com>
Fecha: Sun, 25 Mar 2012 08:36:38 -0500
Para: <ietf@ietf.org>
Asunto: Fact.Check IETF Meeting - 1460 registrations:

>IETF Meeting Registration System
>Attendance List
>IETF 83
>Paris, France
>March 25-30, 2012
>Last updated Sunday, March 25, 2012 at 06:24:32 PDT
>1460 registrations:
>https://www.ietf.org/registration/ietf83/attendance.py
>
>Is the ISOC annual buget now $34,000,000 ?
>
>What is the ICANN annual budget ?
>
>How many $600,000 per year non-profit public benefit employees are now
>in The.Community?
>
>Kruse	Megan	Internet Society	US	Yes 	YES
>Minton	Graham	Internet Society	CH	No =09
>Hoyt	Scott	Internet Society	US	No =09
>O'Donoghue	Karen	Internet Society	US	Yes =09
>St Amour	Lynn 	Internet Society	US	No 	YES
>York	Dan	Internet Society	US	Yes 	YES
>Daigle	Leslie	Internet Society	US	Yes =09
>Roseman	Walda	Internet Society	US	No =09
>Robachevsky	Andrei	Internet Society	NL	No =09
>Lynch	Lucy	Internet Society	US	Yes =09
>Conte	Steve	Internet Society	US	Yes =09
>Sebuck	Kathy	Internet Society	US	No 	YES
>Kummer	Markus	Internet Society	CH	Yes =09
>Craemer	Kevin	Internet Society	US	Yes =09
>Seidler	Nicolas	Internet Society	CH	Yes =09
>Runnegar	Christine	Internet Society	CH	Yes =09
>Cowieson	Toral	Internet Society	US	No =09
>Dvorshak	Andrew	Internet Society	US	No =09
>Brigner	Paul	Internet Society	US	No 	YES
>Greenspan	Robin	Internet Society	US	No =09
>Ford	Mat	Internet Society (ISOC)	US	No =09
>
>Abley	Joseph	ICANN	CA	Yes =09
>Manderson	Terry	ICANN	AU	Yes =09
>liang	pearl	ICANN	US	Yes =09
>Okubo	Tomofumi	ICANN	US	Yes =09
>Sheng	Steve	ICANN	US	Yes =09
>Arias	Francisco	ICANN	US	Yes 	YES
>Raveh	Simon	ICANN	US	No =09
>Bird Gerich	Elise	ICANN	US	Yes =09
>Lee	Xiaodong	ICANN	US	No =09
>Bachollet	Sebastien	ICANN	US	Yes =09
>Sadowsky	George	ICANN	US	No 	YES
>Cotton	Michelle	ICANN - IANA	US	No =09
>
>Huston	Geoff	APNIC	AU	Yes =09
>Ellacott	Byron	APNIC	AU	No
>Newton	Andrew	ARIN	US	Yes 	YES
>Kosters	Mark	ARIN	US	No =09
>Aronson	Cathy	ARIN Advisory Council	US	Yes =09
>Servin	Arturo	LACNIC	UY	No 	YES
>Bruijnzeels	Tim	RIPE NCC	NL	No =09
>Juhasz	Miklos	RIPE NCC	NL	No =09
>Wijnen	Bert	RIPE NCC	NL	Yes =09
>Buddhdev	Anand	RIPE NCC	NL	No =09
>Kuehne	Mirjam	RIPE NCC	NL	No
>AKPLOGAN	ADIEL AYODELE	AfriNIC	MU	No =09
>AINA	Alain PATRICK	AfriNIC Ltd	TG	Yes
>
>Dupont	Francis	ISC	FR	Yes =09
>Damas	Jo=E3o	ISC	ES	Yes =09
>kaeo	merike	ISC	US	No =09
>Morris	Stephen	ISC	GB	Yes 	YES
>Selkirk	Paul	ISC	US	No =09
>Woolf	Suzanne	ISC	US	Yes =09
>Kerr	Shane	ISC (Internet Systems Consortium)	NL	Yes =09
>Woodman	AListair	ISC.org	US	Yes 	YES
>Mrugalski	Tomek	ISC/Gdansk University of Technology	PL	Yes



**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.consulintel.es
The IPv6 Company

This electronic message contains information which may be privileged or con=
fidential. The information is intended to be for the use of the individual(=
s) named above. If you are not the intended recipient be aware that any dis=
closure, copying, distribution or use of the contents of this information, =
including attached files, is prohibited.




From ietf.fact.check@gmail.com  Sun Mar 25 08:20:47 2012
Return-Path: <ietf.fact.check@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8D3F521F84B4 for <ietf@ietfa.amsl.com>; Sun, 25 Mar 2012 08:20:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.105
X-Spam-Level: 
X-Spam-Status: No, score=-3.105 tagged_above=-999 required=5 tests=[AWL=0.494,  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 TIE+qygipCua for <ietf@ietfa.amsl.com>; Sun, 25 Mar 2012 08:20:47 -0700 (PDT)
Received: from mail-iy0-f194.google.com (mail-iy0-f194.google.com [209.85.210.194]) by ietfa.amsl.com (Postfix) with ESMTP id E5B2521F84AA for <ietf@ietf.org>; Sun, 25 Mar 2012 08:20:46 -0700 (PDT)
Received: by iabz21 with SMTP id z21so3069553iab.1 for <ietf@ietf.org>; Sun, 25 Mar 2012 08:20:43 -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=uGpO9gHKet6AiHiZB+xafjXzmNiuwRMZGwF6OjAfiXk=; b=aI3UQdj0xO3UMfPTBo28bu9BLfjIj9ibaDOGV4sUOsl5mLrQGppeDxTnX6dbb12V7B 9aFsLrGMMz9fiMJFt7JvAvB61la0wWkjuh/AKtBmhFxvbt9A4O/ZU2d0jRjOIw8yJzI0 R8cYICneD7nomE6vkBh/4JD08FRoSCM1350FpetOkYh/HGXSkoz8I7y6RaQ2Kep0BvFG fUk199w2jK1DGVSAljC2GJc49uAHHUQmHmaaTUMpoO3mcjdQ5dhJGTMo85JAMOjgeHXd UU00ajPs3mCBPi0ihbudogibHUVe5qRzKG3I96XBKgVzuKOdhZxmXLkHlab55ulRrLu+ PUHg==
MIME-Version: 1.0
Received: by 10.50.212.101 with SMTP id nj5mr3514825igc.41.1332688843787; Sun, 25 Mar 2012 08:20:43 -0700 (PDT)
Received: by 10.50.171.38 with HTTP; Sun, 25 Mar 2012 08:20:43 -0700 (PDT)
Date: Sun, 25 Mar 2012 10:20:43 -0500
Message-ID: <CANwOnkF3VWUFzh4UadBujZEM+0i6VEdteJ8TH5YXCyc8==zunQ@mail.gmail.com>
Subject: Fact.Check IETF Meeting - Paris, France - Internet Engineering
From: Jim Fleming <ietf.fact.check@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: Sun, 25 Mar 2012 15:20:47 -0000

IETF Meeting Registration System
Attendance List
IETF 83
Paris, France
March 25-30, 2012
https://www.ietf.org/registration/ietf83/attendance.py

What (current) Internet Engineering protocols, software, etc. are the
following people working on ?

What are the RFCs they are authoring ?

St Amour	Lynn 	Internet Society	
Daigle	Leslie	Internet Society	
Lynch	Lucy	Internet Society	
Kummer	Markus	Internet Society
Bradner	Scott	Harvard University (ARIN?)
Crocker	Steve	Shinkuro, Inc.(ICANN?)
Roessler	Thomas	W3C (ICANN?)
Seltzer	Wendy	W3C (ICANN?)

What are the new Top Level Domains these people are discussing at IETF ?

Abley	Joseph	ICANN
Manderson	Terry	ICANN
liang	pearl	ICANN
Okubo	Tomofumi	ICANN
Sheng	Steve	ICANN
Arias	Francisco	ICANN
Raveh	Simon	ICANN
Bird Gerich	Elise	ICANN
Lee	Xiaodong	ICANN
Bachollet	Sebastien	ICANN
Sadowsky	George	ICANN
Cotton	Michelle	ICANN

From christopher.morrow@gmail.com  Sun Mar 25 08:26:16 2012
Return-Path: <christopher.morrow@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 19F0D21F84C2 for <ietf@ietfa.amsl.com>; Sun, 25 Mar 2012 08:26:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.544
X-Spam-Level: 
X-Spam-Status: No, score=-103.544 tagged_above=-999 required=5 tests=[AWL=0.055, 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 jM46LmQbUBiE for <ietf@ietfa.amsl.com>; Sun, 25 Mar 2012 08:26:15 -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 8B4D221F84BF for <ietf@ietf.org>; Sun, 25 Mar 2012 08:26:15 -0700 (PDT)
Received: by obbtb4 with SMTP id tb4so4904219obb.31 for <ietf@ietf.org>; Sun, 25 Mar 2012 08:26:14 -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 :content-transfer-encoding; bh=a6kcPp+EB9B7cdQwNYY4qI2bE2gp0F1DE77HN9YoUhQ=; b=z9bHfALLIDPkuDr4PvWOGECguoodqk2kDIUanQDWVAaBr3Tyy/M13MfHIIEMYcT1ue ss3HD5h+EgC71kdKboJ9rjIWg/DKsS4IO+O3U5ONcb/Jv3QFQfTR8HolpstqnN3T3WCp ZdlJ4OFx926Wq1K4OpbpAll2/pQpzNeXy8flC4JNGTGOidy16Y0MiWexsTe2QOzRydup sC/9Xk31vkABHyBbwgCJweCVPToW5xQIkoNYYl+l7k8C90AQzhQGGMP4K+whcrowY2Yj rqg3YwkGDp5GuNvw+xQcbfIvJTidgQ0iJp1HJMpf3BnBGVkivTlmQdCl1yGZeroNeIKS eEgQ==
MIME-Version: 1.0
Received: by 10.60.24.164 with SMTP id v4mr19801222oef.51.1332689174886; Sun, 25 Mar 2012 08:26:14 -0700 (PDT)
Sender: christopher.morrow@gmail.com
Received: by 10.182.80.137 with HTTP; Sun, 25 Mar 2012 08:26:14 -0700 (PDT)
In-Reply-To: <CANwOnkF3VWUFzh4UadBujZEM+0i6VEdteJ8TH5YXCyc8==zunQ@mail.gmail.com>
References: <CANwOnkF3VWUFzh4UadBujZEM+0i6VEdteJ8TH5YXCyc8==zunQ@mail.gmail.com>
Date: Sun, 25 Mar 2012 11:26:14 -0400
X-Google-Sender-Auth: Wt9mkzyR2lQyFjLn8QBajnP6WpI
Message-ID: <CAL9jLaYSk+RU=+Q+h_g_BFOBNvNo7MQ6=bnYTauN3z4sDnf_XQ@mail.gmail.com>
Subject: Re: Fact.Check IETF Meeting - Paris, France - Internet Engineering
From: Christopher Morrow <morrowc.lists@gmail.com>
To: Jim Fleming <ietf.fact.check@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 25 Mar 2012 15:26:16 -0000

congrats on the database and select/group queries, please to move to a
list that cares.

On Sun, Mar 25, 2012 at 11:20 AM, Jim Fleming <ietf.fact.check@gmail.com> w=
rote:
> IETF Meeting Registration System
> Attendance List
> IETF 83
> Paris, France
> March 25-30, 2012
> https://www.ietf.org/registration/ietf83/attendance.py
>
> What (current) Internet Engineering protocols, software, etc. are the
> following people working on ?
>
> What are the RFCs they are authoring ?
>
> St Amour =A0 =A0 =A0 =A0Lynn =A0 =A0Internet Society
> Daigle =A0Leslie =A0Internet Society
> Lynch =A0 Lucy =A0 =A0Internet Society
> Kummer =A0Markus =A0Internet Society
> Bradner Scott =A0 Harvard University (ARIN?)
> Crocker Steve =A0 Shinkuro, Inc.(ICANN?)
> Roessler =A0 =A0 =A0 =A0Thomas =A0W3C (ICANN?)
> Seltzer Wendy =A0 W3C (ICANN?)
>
> What are the new Top Level Domains these people are discussing at IETF ?
>
> Abley =A0 Joseph =A0ICANN
> Manderson =A0 =A0 =A0 Terry =A0 ICANN
> liang =A0 pearl =A0 ICANN
> Okubo =A0 Tomofumi =A0 =A0 =A0 =A0ICANN
> Sheng =A0 Steve =A0 ICANN
> Arias =A0 Francisco =A0 =A0 =A0 ICANN
> Raveh =A0 Simon =A0 ICANN
> Bird Gerich =A0 =A0 Elise =A0 ICANN
> Lee =A0 =A0 Xiaodong =A0 =A0 =A0 =A0ICANN
> Bachollet =A0 =A0 =A0 Sebastien =A0 =A0 =A0 ICANN
> Sadowsky =A0 =A0 =A0 =A0George =A0ICANN
> Cotton =A0Michelle =A0 =A0 =A0 =A0ICANN

From Francis.Dupont@fdupont.fr  Sun Mar 25 15:12:54 2012
Return-Path: <Francis.Dupont@fdupont.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 B17E821E8025 for <ietf@ietfa.amsl.com>; Sun, 25 Mar 2012 15:12:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.537
X-Spam-Level: 
X-Spam-Status: No, score=-2.537 tagged_above=-999 required=5 tests=[AWL=0.062,  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 MTlbFlykVjE7 for <ietf@ietfa.amsl.com>; Sun, 25 Mar 2012 15:12:54 -0700 (PDT)
Received: from givry.fdupont.fr (givry.fdupont.fr [IPv6:2001:41d0:1:6d55:211:5bff:fe98:d51e]) by ietfa.amsl.com (Postfix) with ESMTP id DF6DC21E800C for <ietf@ietf.org>; Sun, 25 Mar 2012 15:12:53 -0700 (PDT)
Received: from givry.fdupont.fr (localhost [127.0.0.1]) by givry.fdupont.fr (8.14.3/8.14.3) with ESMTP id q2PMCqCr074537; Mon, 26 Mar 2012 00:12:52 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201203252212.q2PMCqCr074537@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: Jim Fleming <ietf.fact.check@gmail.com>
Subject: Re: Fact.Check IETF Meeting - 1460 registrations: 
In-reply-to: Your message of Sun, 25 Mar 2012 08:36:38 CDT. <CANwOnkGRwokhAC44g10xRaOgQxrkfm=gxJRDhszSXyv-x4-Ziw@mail.gmail.com> 
Date: Mon, 26 Mar 2012 00:12:52 +0200
Sender: Francis.Dupont@fdupont.fr
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, 25 Mar 2012 22:12:54 -0000

Randy (oops, Jim), what is the meaning of the YES/NO?
BTW most NICs (AFNIC for instance) are also not-profit public benefit.
And you can add the few persons who pay themselves the registration,
Remi Despres, etc.

Regards

Francis.Dupont@fdupont.fr (also fdupont@isc.org)

From ietf.fact.check@gmail.com  Mon Mar 26 06:19:18 2012
Return-Path: <ietf.fact.check@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E41E21F866E for <ietf@ietfa.amsl.com>; Mon, 26 Mar 2012 06:19:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.187
X-Spam-Level: 
X-Spam-Status: No, score=-3.187 tagged_above=-999 required=5 tests=[AWL=0.412,  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 GCjl-etzZ49o for <ietf@ietfa.amsl.com>; Mon, 26 Mar 2012 06:19:17 -0700 (PDT)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id 833B221F8664 for <ietf@ietf.org>; Mon, 26 Mar 2012 06:19:17 -0700 (PDT)
Received: by iazz13 with SMTP id z13so9761859iaz.31 for <ietf@ietf.org>; Mon, 26 Mar 2012 06:19:17 -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=v86hVQ2IE/LM3TYyFe1sWeu8LC7YiKad6puZhhlcWno=; b=DWgmkCNpElJhhrBMVONoq50//XnrTUn0mfT0zjlRcTCBrgH3sb7EkeYWd880qzOMMj cLCzreKssyVVHvx8InJOzbLRfmMh6jsWhYrvvbQOwNcFFw9s2Ejptsvee/5e9x7cAGZx /q1gNtcTy/CJWcZk2/Lt8BiZgunQiIatWW3dubktSG2md9aZnGGa6ZjCW0ADbdqXLgJ2 6rUhMFz2gflkObajRMqFfTQa0rjvm8CFB7dU5Gy0PB8KDk71tSjSzmt+ji6eiei4eKei qqJxNrki+ScpKwi+w7h8sPpZqGlEUFX4Vbf98+KEbzSNRiLSbtE9tZyeuYO3RJnIIP5Q ysmw==
MIME-Version: 1.0
Received: by 10.50.42.132 with SMTP id o4mr759590igl.41.1332767957016; Mon, 26 Mar 2012 06:19:17 -0700 (PDT)
Received: by 10.50.171.38 with HTTP; Mon, 26 Mar 2012 06:19:16 -0700 (PDT)
Date: Mon, 26 Mar 2012 08:19:16 -0500
Message-ID: <CANwOnkExpmm6L6+Fw+PerJmf2uVGa6dgN5D+TTc8jGS_HeK1NA@mail.gmail.com>
Subject: Fact.Check IETF Meeting - Paris, France - 100/8 IANA
From: Jim Fleming <ietf.fact.check@gmail.com>
To: ietf <ietf@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Mar 2012 13:19:18 -0000

Fact.Check IETF Meeting - Paris, France - 100/8 IANA

Fact Check:

http://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.txt

Was the decision to cut into the (in-use) 100/8 IPv4 Address Spectrum
made because of the consumer human factors of using 10/8 on their
VPNs?

Were existing users in 100/8 advised that they will not be routable
with that change ?

Was the U.S. FCC consulted about the 100/8 Address Spectrum usage ?

http://www.fcc.gov/encyclopedia/communications-security-reliability-and-interoperability-council-iii
Council Meetings
3/22/12
Steve Crocker (ISOC ICANN)

http://www.fcc.gov/encyclopedia/technological-advisory-council
Vinton Cerf (ISOC ICANN ARIN)

March 20, 2012 - FCC Announces the next Technological Advisory
Committee Meeting on March 28, 2012

8 Days Notice ?

From rpelletier@isoc.org  Mon Mar 26 07:04:47 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 7928E21F874C for <ietf@ietfa.amsl.com>; Mon, 26 Mar 2012 07:04:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.222
X-Spam-Level: 
X-Spam-Status: No, score=-103.222 tagged_above=-999 required=5 tests=[AWL=0.377, 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 kqHoHV2h4VFZ for <ietf@ietfa.amsl.com>; Mon, 26 Mar 2012 07:04:46 -0700 (PDT)
Received: from smtp127.iad.emailsrvr.com (smtp127.iad.emailsrvr.com [207.97.245.127]) by ietfa.amsl.com (Postfix) with ESMTP id 8DB8821F8749 for <ietf@ietf.org>; Mon, 26 Mar 2012 07:04:46 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp42.relay.iad1a.emailsrvr.com (SMTP Server) with ESMTP id 26BB6148616; Mon, 26 Mar 2012 10:04:46 -0400 (EDT)
X-Virus-Scanned: OK
Received: by smtp42.relay.iad1a.emailsrvr.com (Authenticated sender: rpelletier-AT-isoc.org) with ESMTPSA id AF37714841F;  Mon, 26 Mar 2012 10:04:45 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1084)
Subject: Technical Plenary Captioned
From: Ray Pelletier <rpelletier@isoc.org>
Date: Mon, 26 Mar 2012 10:04:44 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <3D796CBB-5FCF-4E1A-8092-F4EF88FAF945@isoc.org>
To: 83all@ietf.org
X-Mailer: Apple Mail (2.1084)
Cc: Discussion IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Mar 2012 14:04:47 -0000

All

The Technical Plenary will be transcribed real time and presented in the =
Plenary on a screen and also distributed online at:

http://www.streamtext.net/player?event=3Dietf=20

Ray
IETF Administrative Director


From christopher.morrow@gmail.com  Mon Mar 26 07:09:10 2012
Return-Path: <christopher.morrow@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E657A21F8752 for <ietf@ietfa.amsl.com>; Mon, 26 Mar 2012 07:09:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.546
X-Spam-Level: 
X-Spam-Status: No, score=-103.546 tagged_above=-999 required=5 tests=[AWL=0.053, 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 8SYdwbO+cLZ3 for <ietf@ietfa.amsl.com>; Mon, 26 Mar 2012 07:09:09 -0700 (PDT)
Received: from mail-gy0-f172.google.com (mail-gy0-f172.google.com [209.85.160.172]) by ietfa.amsl.com (Postfix) with ESMTP id 17D6521F875D for <ietf@ietf.org>; Mon, 26 Mar 2012 07:09:09 -0700 (PDT)
Received: by ghbg16 with SMTP id g16so4233771ghb.31 for <ietf@ietf.org>; Mon, 26 Mar 2012 07:09:08 -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=dg29Vnz21fb20ZGQlGXRagjVUoGkdfc8g/ZeQUsXnXY=; b=jvLm9O0Tu/fdlF2wvxBKiSwJfwYz7h9UdW2oRjrxVjty610l1+IcMNW/3BDwqgHjY4 uALzjp/5Ic/Hel1bdKRTC36UZivQA+YFhuDOzlEiIP6S6G1DQ2c+WRf3naLPGYRZfZhM Lxxk+aQxiqRiKCceknPCPVVhvsFnkUyFUqUhnwVvsGNEhO2TNTF8hAiZaTSuPgSswL4y axVQle/NP7ChUoXJHlTvdMOwUNecSuKzZF+yPeCZfS09/axnplxWMo9Cydu28+ha3a3y CtA/T8H9ZTpVTljdmiybsmKrRKSO3I3XLL8Vd5FZwLYgvutMoEyjF2JR7zrvjnnEyja4 oZ1g==
MIME-Version: 1.0
Received: by 10.60.8.103 with SMTP id q7mr26568761oea.61.1332770948085; Mon, 26 Mar 2012 07:09:08 -0700 (PDT)
Sender: christopher.morrow@gmail.com
Received: by 10.182.80.137 with HTTP; Mon, 26 Mar 2012 07:09:08 -0700 (PDT)
In-Reply-To: <CANwOnkExpmm6L6+Fw+PerJmf2uVGa6dgN5D+TTc8jGS_HeK1NA@mail.gmail.com>
References: <CANwOnkExpmm6L6+Fw+PerJmf2uVGa6dgN5D+TTc8jGS_HeK1NA@mail.gmail.com>
Date: Mon, 26 Mar 2012 10:09:08 -0400
X-Google-Sender-Auth: -j70iDX-1EbASXkYAxdHVt2PYR4
Message-ID: <CAL9jLaZHTky5vEuBMR3r_B9rd2uL11Pgbn87j96py9VWyCYPKw@mail.gmail.com>
Subject: Re: Fact.Check IETF Meeting - Paris, France - 100/8 IANA
From: Christopher Morrow <morrowc.lists@gmail.com>
To: Jim Fleming <ietf.fact.check@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Mar 2012 14:09:10 -0000

On Mon, Mar 26, 2012 at 9:19 AM, Jim Fleming <ietf.fact.check@gmail.com> wrote:
> Was the U.S. FCC consulted about the 100/8 Address Spectrum usage ?

spectrum?

From dave@cridland.net  Mon Mar 26 07:11:57 2012
Return-Path: <dave@cridland.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A860A21F8783 for <ietf@ietfa.amsl.com>; Mon, 26 Mar 2012 07:11:57 -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 9q986y65iMvy for <ietf@ietfa.amsl.com>; Mon, 26 Mar 2012 07:11:56 -0700 (PDT)
Received: from peirce.dave.cridland.net (peirce.dave.cridland.net [IPv6:2001:470:1f09:882:2e0:81ff:fe29:d16a]) by ietfa.amsl.com (Postfix) with ESMTP id 547A921F8782 for <ietf@ietf.org>; Mon, 26 Mar 2012 07:11:55 -0700 (PDT)
Received: from localhost (peirce.dave.cridland.net [127.0.0.1]) by peirce.dave.cridland.net (Postfix) with ESMTP id 622191168087; Mon, 26 Mar 2012 15:11:53 +0100 (BST)
X-Virus-Scanned: Debian amavisd-new at peirce.dave.cridland.net
Received: from peirce.dave.cridland.net ([127.0.0.1]) by localhost (peirce.dave.cridland.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H69-2JcnyKKE; Mon, 26 Mar 2012 15:11:47 +0100 (BST)
Received: from puncture (puncture.dave.cridland.net [IPv6:2001:470:1f09:882:221:85ff:fe3f:1696]) by peirce.dave.cridland.net (Postfix) with ESMTPA id 128651168067; Mon, 26 Mar 2012 15:11:47 +0100 (BST)
Subject: Re: Fact.Check IETF Meeting - Paris, France - 100/8 IANA
References: <CANwOnkExpmm6L6+Fw+PerJmf2uVGa6dgN5D+TTc8jGS_HeK1NA@mail.gmail.com> <CAL9jLaZHTky5vEuBMR3r_B9rd2uL11Pgbn87j96py9VWyCYPKw@mail.gmail.com>
In-Reply-To: <CAL9jLaZHTky5vEuBMR3r_B9rd2uL11Pgbn87j96py9VWyCYPKw@mail.gmail.com>
MIME-Version: 1.0
Message-Id: <20897.1332771107.067840@puncture>
Date: Mon, 26 Mar 2012 15:11:47 +0100
From: Dave Cridland <dave@cridland.net>
To: Christopher Morrow <morrowc.lists@gmail.com>, IETF-Discussion <ietf@ietf.org>, Jim Fleming <ietf.fact.check@gmail.com>
Content-Type: text/plain; delsp="yes"; charset="us-ascii"; format="flowed"
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Mar 2012 14:11:58 -0000

On Mon Mar 26 15:09:08 2012, Christopher Morrow wrote:
> On Mon, Mar 26, 2012 at 9:19 AM, Jim Fleming  
> <ietf.fact.check@gmail.com> wrote:
> > Was the U.S. FCC consulted about the 100/8 Address Spectrum usage  
> ?
> 
> spectrum?

Yes, 100/8 was reserved for use by the FCC for 1980's UK home  
computers. It's a fair cop, we should have involved them in the  
discussion.

Dave.
-- 
Dave Cridland - mailto:dave@cridland.net - xmpp:dwd@dave.cridland.net
  - acap://acap.dave.cridland.net/byowner/user/dwd/bookmarks/
  - http://dave.cridland.net/
Infotrope Polymer - ACAP, IMAP, ESMTP, and Lemonade

From sm@resistor.net  Mon Mar 26 07:17:00 2012
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 11C6821F8512 for <ietf@ietfa.amsl.com>; Mon, 26 Mar 2012 07:17:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.628
X-Spam-Level: 
X-Spam-Status: No, score=-102.628 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 DAyFxguEtif2 for <ietf@ietfa.amsl.com>; Mon, 26 Mar 2012 07:16:58 -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 D63FB21F8469 for <ietf@ietf.org>; Mon, 26 Mar 2012 07:16: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 q2QEGpsM008502; Mon, 26 Mar 2012 07:16:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1332771416; i=@resistor.net; bh=eTi/FRtogtH+2pt8H5VYgfrBps4iuQbhMwVa21AAtMM=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=2p0bxe5SCiuFykGXU9+WvMYqYIlIDp67FubBmhUcp2m8/OGT35b60G/ARkFxyhGHC BjmwkyE9rf9/V0v8ULLHkHs+cVAK28cNUtOkhcUhze+6zHsACNKgs+VSnnAYwgfNSl WMC6/u2Ul0mIszpmAixpADxZHtJLtHbbg6Xpj2Vo=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1332771416; i=@resistor.net; bh=eTi/FRtogtH+2pt8H5VYgfrBps4iuQbhMwVa21AAtMM=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=3vQ2B/WSq5oqd8024jDmknQIx1zzq5W0v3gYuPhhv/rNiaOVqCW+SnoGwq9D983F9 H5n6XtTxHl/CcAeqf5QJFvpLyEKuT/uv62gu30OjtJ0mxvBcSlmLbijFPiZfRJVZwl 3zvIEA0E4Jrcw+rvOs3pv/xJnc9apZgzaLLctM7M=
Message-Id: <6.2.5.6.2.20120326071440.0ba41668@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 26 Mar 2012 07:16:34 -0700
To: Ray Pelletier <rpelletier@isoc.org>
From: SM <sm@resistor.net>
Subject: Re: Technical Plenary Captioned
In-Reply-To: <3D796CBB-5FCF-4E1A-8092-F4EF88FAF945@isoc.org>
References: <3D796CBB-5FCF-4E1A-8092-F4EF88FAF945@isoc.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: Discussion IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Mar 2012 14:17:00 -0000

Hi Ray,
At 07:04 26-03-2012, Ray Pelletier wrote:
>The Technical Plenary will be transcribed real time and presented in 
>the Plenary on a screen and also distributed online at:

Is the audio channel http://ietf83streaming.dnsalias.net/ietf/ietf839.m3u ?

Regards,
-sm 


From rpelletier@isoc.org  Mon Mar 26 07:32:24 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 1B24621E80AB for <ietf@ietfa.amsl.com>; Mon, 26 Mar 2012 07:32:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.227
X-Spam-Level: 
X-Spam-Status: No, score=-103.227 tagged_above=-999 required=5 tests=[AWL=0.372, 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 ITtyh8NS8gHA for <ietf@ietfa.amsl.com>; Mon, 26 Mar 2012 07:32:23 -0700 (PDT)
Received: from smtp127.iad.emailsrvr.com (smtp127.iad.emailsrvr.com [207.97.245.127]) by ietfa.amsl.com (Postfix) with ESMTP id 3779621E80AA for <ietf@ietf.org>; Mon, 26 Mar 2012 07:32:23 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp42.relay.iad1a.emailsrvr.com (SMTP Server) with ESMTP id BAD431487BD; Mon, 26 Mar 2012 10:32:22 -0400 (EDT)
X-Virus-Scanned: OK
Received: by smtp42.relay.iad1a.emailsrvr.com (Authenticated sender: rpelletier-AT-isoc.org) with ESMTPSA id 668A4148469;  Mon, 26 Mar 2012 10:32:22 -0400 (EDT)
Subject: Re: Technical Plenary Captioned
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Ray Pelletier <rpelletier@isoc.org>
In-Reply-To: <6.2.5.6.2.20120326071440.0ba41668@resistor.net>
Date: Mon, 26 Mar 2012 10:32:22 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <58E56881-8CCC-4B54-83C5-D3046EB845B1@isoc.org>
References: <3D796CBB-5FCF-4E1A-8092-F4EF88FAF945@isoc.org> <6.2.5.6.2.20120326071440.0ba41668@resistor.net>
To: SM <sm@resistor.net>
X-Mailer: Apple Mail (2.1084)
Cc: Discussion IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Mar 2012 14:32:24 -0000

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


On Mar 26, 2012, at 10:16 AM, SM wrote:

> Hi Ray,
> At 07:04 26-03-2012, Ray Pelletier wrote:
>> The Technical Plenary will be transcribed real time and presented in =
the Plenary on a screen and also distributed online at:
>=20
> Is the audio channel =
http://ietf83streaming.dnsalias.net/ietf/ietf839.m3u ?
>=20
> Regards,
> -sm=20


From sm@resistor.net  Mon Mar 26 07:39:14 2012
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ED1DA21E80AB for <ietf@ietfa.amsl.com>; Mon, 26 Mar 2012 07:39:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.628
X-Spam-Level: 
X-Spam-Status: No, score=-102.628 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 cdST17rLfZGZ for <ietf@ietfa.amsl.com>; Mon, 26 Mar 2012 07:39:12 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 1C8BA21E809C for <ietf@ietf.org>; Mon, 26 Mar 2012 07:39:12 -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 q2QEd539007973; Mon, 26 Mar 2012 07:39:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1332772751; i=@resistor.net; bh=r/BskSvO2JnMVGbGGixT32MV4qTDYVykXRZr22TNRdY=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=qVIeul/7LpaJ369Pr+fxTZl853pUJVTKV5mliOYkvLHOZVe+C0E2hN9WT8tZhHqb0 PpGkUC/8a2bVibxD4kFiePT+xkdne26A0ADNXBbauH7eN41YR1bh8wjzdxOurScfRH 4dXNlGlSC4FbSP8lOaD9TdE5vDcFEXvvpQt9sa+c=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1332772751; i=@resistor.net; bh=r/BskSvO2JnMVGbGGixT32MV4qTDYVykXRZr22TNRdY=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=CHTaz/kaJ+GmDmWJjCE+6gCsY10NeddD4f30kUFmefq0nCzdTk3xt08sVtWOw1+6G 7EFV+sf8m5XwPPm1/96OR7FkiUqucrVAAP3+uvsK6b6jv6ntT6NLqF/U/yISLW2Ds5 VgbYsc9rSTveghFh/gVaIZ6ehAtXu8uE3lzHdIBs=
Message-Id: <6.2.5.6.2.20120326073716.0b6e1818@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 26 Mar 2012 07:37:59 -0700
To: Ray Pelletier <rpelletier@isoc.org>
From: SM <sm@resistor.net>
Subject: Re: Technical Plenary Captioned
In-Reply-To: <58E56881-8CCC-4B54-83C5-D3046EB845B1@isoc.org>
References: <3D796CBB-5FCF-4E1A-8092-F4EF88FAF945@isoc.org> <6.2.5.6.2.20120326071440.0ba41668@resistor.net> <58E56881-8CCC-4B54-83C5-D3046EB845B1@isoc.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: Discussion IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Mar 2012 14:39:15 -0000

Hi Ray,
At 07:32 26-03-2012, Ray Pelletier wrote:
>http://www.ietf.org/meeting/83/remote-participation.html

I read that.  The channel is TBD and there's no sound.

Regards,
-sm  


From joelja@bogus.com  Mon Mar 26 07:46:06 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 C954D21E80C3 for <ietf@ietfa.amsl.com>; Mon, 26 Mar 2012 07:46: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=[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 KFykgjYrGww1 for <ietf@ietfa.amsl.com>; Mon, 26 Mar 2012 07:46:06 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 4D85E21E80BD for <ietf@ietf.org>; Mon, 26 Mar 2012 07:46:06 -0700 (PDT)
Received: from dhcp-5710.meeting.ietf.org (dhcp-5710.meeting.ietf.org [130.129.87.16]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id q2QEk3KM023077 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Mon, 26 Mar 2012 14:46:05 GMT (envelope-from joelja@bogus.com)
Message-ID: <4F708129.5070303@bogus.com>
Date: Mon, 26 Mar 2012 16:46:01 +0200
From: Joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:11.0) Gecko/20120313 Thunderbird/11.0
MIME-Version: 1.0
To: SM <sm@resistor.net>
Subject: Re: Technical Plenary Captioned
References: <3D796CBB-5FCF-4E1A-8092-F4EF88FAF945@isoc.org> <6.2.5.6.2.20120326071440.0ba41668@resistor.net> <58E56881-8CCC-4B54-83C5-D3046EB845B1@isoc.org> <6.2.5.6.2.20120326073716.0b6e1818@resistor.net>
In-Reply-To: <6.2.5.6.2.20120326073716.0b6e1818@resistor.net>
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]); Mon, 26 Mar 2012 14:46:06 +0000 (UTC)
Cc: Discussion IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Mar 2012 14:46:06 -0000

it is supposed to be channel-9 yes

On 3/26/12 16:37 , SM wrote:
> Hi Ray,
> At 07:32 26-03-2012, Ray Pelletier wrote:
>> http://www.ietf.org/meeting/83/remote-participation.html
> 
> I read that.  The channel is TBD and there's no sound.
> 
> Regards,
> -sm 


From marshall.eubanks@gmail.com  Mon Mar 26 08:10:21 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 E3A2921F8608 for <ietf@ietfa.amsl.com>; Mon, 26 Mar 2012 08:10:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.526
X-Spam-Level: 
X-Spam-Status: No, score=-103.526 tagged_above=-999 required=5 tests=[AWL=0.073, 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 7pR+pA0Eb14M for <ietf@ietfa.amsl.com>; Mon, 26 Mar 2012 08:10:15 -0700 (PDT)
Received: from mail-lpp01m010-f44.google.com (mail-lpp01m010-f44.google.com [209.85.215.44]) by ietfa.amsl.com (Postfix) with ESMTP id 4A0ED21F8613 for <ietf@ietf.org>; Mon, 26 Mar 2012 08:10:14 -0700 (PDT)
Received: by lagj5 with SMTP id j5so4438043lag.31 for <ietf@ietf.org>; Mon, 26 Mar 2012 08:10:13 -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=c+EeZBiaPllIcCaIJd3LHYkPw2uLNQbcAIt+rFM0Xo8=; b=XlWeMxF+p2HCOWVLFXNHuz9+mOtIggo6z/K7ccaPFsssPnJ1UkWtkXuHW4hGQOgre/ tFak3oSpKWcHOGCByG/yzq96IJfJkkf8OEV8tkLqdRXrkluBTSt3QbQPkbs5p6D/9xXH zJaOaOEAbDIuZmprZIqdwiz1yJHJ8VBS9hNBD54qWgCayoM0NZC5xIuB9aLic5WWEG5Y fm9IMOSdF/TuhefqDcPJqVPdeSdT+Dd0NmUDfRJUdcE/LNQN2vpXQO189HB/DMNpTBIH YwieNX6uR5Ze5cTOfsU0FCzhQInq9nQusAbn6mYNV6IOCks4hgnrfBOplOFfgSZA8E4s CcYw==
MIME-Version: 1.0
Received: by 10.112.26.37 with SMTP id i5mr8286768lbg.6.1332774613238; Mon, 26 Mar 2012 08:10:13 -0700 (PDT)
Received: by 10.112.115.98 with HTTP; Mon, 26 Mar 2012 08:10:13 -0700 (PDT)
Date: Mon, 26 Mar 2012 11:10:13 -0400
Message-ID: <CAJNg7VJ4FuoGhMbnjSHY+n3-WvwQcue=JZjBk2s4TAzTmy-s8Q@mail.gmail.com>
Subject: Anti-Trust Policy BOF tomorrow
From: Marshall Eubanks <marshall.eubanks@gmail.com>
To: ietf <ietf@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Mar 2012 15:10:21 -0000

Hello All;

I just wanted to remind people of our BOF tomorrow, Room 243 in
Morning Session I at 9:00 AM,
which is intended to explore the need for
an Anti-Trust Policy for the IETF. John Levine and I will be chairing this;
we will start with presentations from Jorge Contreras and
Scott Bradner (see Agenda, below), and will then move into an open
discussion. The presentations are intended to describe, in a neutral
fashion, the
issues, risks and opportunities of having (or not
having) an Anti-Trust Policy to provide information and encourage discussion.
I would like to encourage anyone interested to come and make their
opinions known.

Regards
Marshall Eubanks

-----

Does the IETF Need an Anti-Trust Policy BOF?

General Area

TUESDAY, March 27, 2012

Room 252A

Chairs : Marshall Eubanks <marshall.eubanks@gmail.com>
John Levine  <johnl@iecc.com>

Agenda

Jorge Contreras : Legal risks/benefits of Anti-Trust Policy Options (30 minutes)

Scott Bradner : Operational risks/benefits of Anti-Trust Policy
Options (30 minutes)

General Discussion

From amorris@amsl.com  Mon Mar 26 08:10:23 2012
Return-Path: <amorris@amsl.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BFC2121F84FE; Mon, 26 Mar 2012 08:10:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 i1-oIuTV5k0q; Mon, 26 Mar 2012 08:10:21 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:123a::1:14]) by ietfa.amsl.com (Postfix) with ESMTP id CD85621F8504; Mon, 26 Mar 2012 08:10:20 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 841EC12BBB9; Mon, 26 Mar 2012 08:10:18 -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 2bUTe3+YKb70; Mon, 26 Mar 2012 08:10:18 -0700 (PDT)
Received: from dhcp-67aa.meeting.ietf.org (dhcp-67aa.meeting.ietf.org [130.129.103.170]) by c8a.amsl.com (Postfix) with ESMTPSA id 8FB8412BBB8; Mon, 26 Mar 2012 08:10:17 -0700 (PDT)
Subject: Re: Technical Plenary Captioned
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Alexa Morris <amorris@amsl.com>
In-Reply-To: <4F708129.5070303@bogus.com>
Date: Mon, 26 Mar 2012 17:10:14 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <C8946AAD-E1D5-4DA8-A9C3-59271C4F7397@amsl.com>
References: <3D796CBB-5FCF-4E1A-8092-F4EF88FAF945@isoc.org> <6.2.5.6.2.20120326071440.0ba41668@resistor.net> <58E56881-8CCC-4B54-83C5-D3046EB845B1@isoc.org> <6.2.5.6.2.20120326073716.0b6e1818@resistor.net> <4F708129.5070303@bogus.com>
To: Joel jaeggli <joelja@bogus.com>
X-Mailer: Apple Mail (2.1084)
Cc: SM <sm@resistor.net>, 83attendees@ietf.org, Discussion IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Mar 2012 15:10:23 -0000

There are some issues with the audio in the plenary and VeriLAN is =
working to address them right now.=20

Alexa

On Mar 26, 2012, at 4:46 PM, Joel jaeggli wrote:

> it is supposed to be channel-9 yes
>=20
> On 3/26/12 16:37 , SM wrote:
>> Hi Ray,
>> At 07:32 26-03-2012, Ray Pelletier wrote:
>>> http://www.ietf.org/meeting/83/remote-participation.html
>>=20
>> I read that.  The channel is TBD and there's no sound.
>>=20
>> Regards,
>> -sm=20
>=20

----------
Alexa Morris / Executive Director / IETF
48377 Fremont Blvd., Suite 117, Fremont, CA  94538
Phone: +1.510.492.4089 / Fax: +1.510.492.4001
Email: amorris@amsl.com

Managed by Association Management Solutions (AMS)
Forum Management, Meeting and Event Planning
www.amsl.com <http://www.amsl.com/>


From sm@resistor.net  Mon Mar 26 08:21:35 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 4CD1C21E80A6; Mon, 26 Mar 2012 08:21:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.628
X-Spam-Level: 
X-Spam-Status: No, score=-102.628 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 u6D3izIC8pk3; Mon, 26 Mar 2012 08:21: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 A051421E8097; Mon, 26 Mar 2012 08:21:33 -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 q2QFLLZN025672; Mon, 26 Mar 2012 08:21:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1332775290; i=@resistor.net; bh=xUOsRm3XasE3KC8VLyk4U99ZEma1IqtxVKsETNqD/no=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=0cNNTn+V5+FVAt80S2OQhfl4mSzGAlcAIUhRzwK/CcyZPebzlJsrUuRc1E/7rjFtZ UHSFfnwDF+le6Gpb5eBrz+PK6m7T1cr4rY2Bui/Trxp9gMLDUQNAQtMPY7J60s7JyK 8U5jNbQs92WxaC+kWFMkdP12fmCWZTj/Gqu+UJoc=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1332775290; i=@resistor.net; bh=xUOsRm3XasE3KC8VLyk4U99ZEma1IqtxVKsETNqD/no=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=UeLiycacqVoo5exeHk5M8M02olbBegN4ldibTo2Kt+4PRbTxOV2j6HNNamw5JbsaY XebYT9XW1tX9VmyWieYWAa77Mw4m9zLUcWqIzeL6HNmRsec0QmrBoOP8aPCQXqjHJ8 2PkpSVhBwUWn4zHzGqu1Q8b3ZmFKs6UZNzg1tAog=
Message-Id: <6.2.5.6.2.20120326082042.0c156018@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 26 Mar 2012 08:21:22 -0700
To: Alexa Morris <amorris@amsl.com>
From: SM <sm@resistor.net>
Subject: Re: Technical Plenary Captioned
In-Reply-To: <C8946AAD-E1D5-4DA8-A9C3-59271C4F7397@amsl.com>
References: <3D796CBB-5FCF-4E1A-8092-F4EF88FAF945@isoc.org> <6.2.5.6.2.20120326071440.0ba41668@resistor.net> <58E56881-8CCC-4B54-83C5-D3046EB845B1@isoc.org> <6.2.5.6.2.20120326073716.0b6e1818@resistor.net> <4F708129.5070303@bogus.com> <C8946AAD-E1D5-4DA8-A9C3-59271C4F7397@amsl.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: 83attendees@ietf.org, Discussion IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Mar 2012 15:21:35 -0000

Hi Alexa,
At 08:10 26-03-2012, Alexa Morris wrote:
>There are some issues with the audio in the plenary and VeriLAN is 
>working to address them right now.

Thanks, audio is working now.

Regards,
-sm 


From drc@virtualized.org  Mon Mar 26 08:57:10 2012
Return-Path: <drc@virtualized.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7BC8121E80DF for <ietf@ietfa.amsl.com>; Mon, 26 Mar 2012 08:57:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.586
X-Spam-Level: 
X-Spam-Status: No, score=-2.586 tagged_above=-999 required=5 tests=[AWL=0.013,  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 sGT2o1dnwh83 for <ietf@ietfa.amsl.com>; Mon, 26 Mar 2012 08:57:10 -0700 (PDT)
Received: from trantor.virtualized.org (trantor.virtualized.org [199.48.134.42]) by ietfa.amsl.com (Postfix) with ESMTP id F0B5A21E80DE for <ietf@ietf.org>; Mon, 26 Mar 2012 08:57:09 -0700 (PDT)
Received: from [192.168.2.143] (unknown [173.245.57.22]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: drc) by trantor.virtualized.org (Postfix) with ESMTPSA id 9BA911705F; Mon, 26 Mar 2012 15:57:08 +0000 (UTC)
Subject: Re: Fact.Check IETF Meeting - Paris, France - 100/8 IANA
Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=iso-8859-1
From: David Conrad <drc@virtualized.org>
In-Reply-To: <CAL9jLaZHTky5vEuBMR3r_B9rd2uL11Pgbn87j96py9VWyCYPKw@mail.gmail.com>
Date: Mon, 26 Mar 2012 08:35:31 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <812C9A14-AD0F-4CE5-A94D-2F26379079C6@virtualized.org>
References: <CANwOnkExpmm6L6+Fw+PerJmf2uVGa6dgN5D+TTc8jGS_HeK1NA@mail.gmail.com> <CAL9jLaZHTky5vEuBMR3r_B9rd2uL11Pgbn87j96py9VWyCYPKw@mail.gmail.com>
To: Christopher Morrow <morrowc.lists@gmail.com>
X-Mailer: Apple Mail (2.1257)
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, 26 Mar 2012 15:57:10 -0000

Please don't feed the loons.  All they do is poop all over everything.

Regards,
-drc

On Mar 26, 2012, at 7:09 AM, Christopher Morrow wrote:
> On Mon, Mar 26, 2012 at 9:19 AM, Jim Fleming =
<ietf.fact.check@gmail.com> wrote:
>> Was the U.S. FCC consulted about the 100/8 Address Spectrum usage ?
>=20
> spectrum?


From marshall.eubanks@gmail.com  Mon Mar 26 09:04:38 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 D424F21E80E9; Mon, 26 Mar 2012 09:04:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.527
X-Spam-Level: 
X-Spam-Status: No, score=-103.527 tagged_above=-999 required=5 tests=[AWL=0.072, 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 UZmdRzO4NPCH; Mon, 26 Mar 2012 09:04: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 96C3D21E80A3; Mon, 26 Mar 2012 09:04:37 -0700 (PDT)
Received: by lbol12 with SMTP id l12so4489062lbo.31 for <multiple recipients>; Mon, 26 Mar 2012 09:04:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=yMo/f8vAOG6k5k/Gcc1eXuyqByzrOtCo6FOoC6w6iLs=; b=tGXaNciZW4xvAZg1e4L/4NM6vNEGqKN14Cfwss9sAFcjBNfn/2kQUFXALUXLyFD2YF VJC55WW7lf6nCNSt3F/Rmi7sBiUp7L26UHBWEoR7+F6jc7GxTNnu/YJYUQkvLbFlawyg d8ff9b+UWb7tVkod/GbUrD27bWYVvEZ73rD9W/VNCQ3aRxOdcCX3CQjSaVJjiw5CDw96 P/vOYtadEzIZVD1uYs2F0g16fHLWoB3bx9OuQajd4ja8cZUbHuDhuE0ucdwxzrZdQ/Ou FTBhx5hZJxuJhqcDyRp0P1v1Uu7Ay5CTuHU/xRrHlQtDhIeUXAEnOWOZrAGf6Fma+B8L 3bag==
MIME-Version: 1.0
Received: by 10.112.82.37 with SMTP id f5mr8571905lby.48.1332777876535; Mon, 26 Mar 2012 09:04:36 -0700 (PDT)
Received: by 10.112.115.98 with HTTP; Mon, 26 Mar 2012 09:04:36 -0700 (PDT)
In-Reply-To: <CAJNg7VJKipyQFnkYbquW0PkbVEQi2Fp_Uj9bL14ZivbVjdUc1A@mail.gmail.com>
References: <CAJNg7VJKipyQFnkYbquW0PkbVEQi2Fp_Uj9bL14ZivbVjdUc1A@mail.gmail.com>
Date: Mon, 26 Mar 2012 12:04:36 -0400
Message-ID: <CAJNg7V+6e2P2+8OsJNMZ69+kLdjJrZ_7WYk84Jc1HWt7V=5JQw@mail.gmail.com>
Subject: Re: Anti-Trust Policy BOF tomorrow
From: Marshall Eubanks <marshall.eubanks@gmail.com>
To: antitrust-policy@ietf.org, 83attendees@ietf.org,  "John R. Levine" <johnl@iecc.com>, ietf <ietf@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Mar 2012 16:04:39 -0000

On Mon, Mar 26, 2012 at 11:05 AM, Marshall Eubanks
<marshall.eubanks@gmail.com> wrote:
> Hello All;
>
> I just wanted to remind people of our BOF tomorrow, Room 243 in

Sorry, the correct room is 252A.

Regards
Marshall

> Morning Session I at 9:00 AM,
> which is intended to explore the need for
> an Anti-Trust Policy for the IETF. John Levine and I will be chairing thi=
s;
> we will start with presentations from Jorge Contreras and
> Scott Bradner (see Agenda, below), and will then move into an open
> discussion. The
> presentations are intended to describe, in a neutral fashion, the
> issues, risks and opportunities of having (or not
> having) an Anti-Trust Policy to provide information and encourage discuss=
ion.
> I would like to encourage anyone interested to come and make their
> opinions known.
>
> Regards
> Marshall Eubanks
>
> -----
>
> Does the IETF Need an Anti-Trust Policy BOF?
>
> General Area
>
> TUESDAY, March 27, 2012
>
> Room 252A
>
> Chairs : Marshall Eubanks <marshall.eubanks@gmail.com>
> John Levine =A0<johnl@iecc.com>
>
> Agenda
>
> Jorge Contreras : Legal risks/benefits of Anti-Trust Policy Options (30 m=
inutes)
>
> Scott Bradner : Operational risks/benefits of Anti-Trust Policy
> Options (30 minutes)
>
> General Discussion

From denghui02@gmail.com  Mon Mar 26 10:28:52 2012
Return-Path: <denghui02@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 512C221E80BC; Mon, 26 Mar 2012 10:28:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.381
X-Spam-Level: 
X-Spam-Status: No, score=-103.381 tagged_above=-999 required=5 tests=[AWL=0.217, 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 H3zeu6uB39Xu; Mon, 26 Mar 2012 10:28:51 -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 E40DD21E80E5; Mon, 26 Mar 2012 10:28:50 -0700 (PDT)
Received: by yenm5 with SMTP id m5so4465469yen.31 for <multiple recipients>; Mon, 26 Mar 2012 10:28:50 -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=E/RzDaHuekNZWCc1VMUlQY/8x40p/ArRb4iArllNmIg=; b=Pp5LSlX2DP7rIwDrKzJx6/xdoWrR6XGneLrVVavgd1/WWDtucQpp7KgITFlERkMQBd Vsx0BGRcPcXOrEBE/J90mkcAt+gWBPJik+ubUAXTpMSEi1xOROO3WJkiJUkFuENRzvN+ 1KAwUQncqfvlVYxyp6kMvY6ojvd7fpX0mVkSFJmN2LZShoPbYEkn4bvF2nz3dSmuTV4a 4n3heGZDa8XSky7OBhu9WrNhCt/I3PfRa34H1/5T+HXBcf7rd7cQGA+FJYdAxYuVSdqN 2EwDaOjHexvLgN/1ZlpGrfeNLh0MikvnRyYCQxITTBFIA0HP98Gb29bnqHXnpL7GzdD/ xM8w==
MIME-Version: 1.0
Received: by 10.236.46.232 with SMTP id r68mr23062351yhb.80.1332782930398; Mon, 26 Mar 2012 10:28:50 -0700 (PDT)
Received: by 10.146.20.14 with HTTP; Mon, 26 Mar 2012 10:28:50 -0700 (PDT)
Date: Mon, 26 Mar 2012 19:28:50 +0200
Message-ID: <CANF0JMBijns_ks33Qfie55GUo2cQtENBkdjdRYmYjGAsVfxzAA@mail.gmail.com>
Subject: OMA IETF MIF API Workshop - Room info
From: Hui Deng <denghui02@gmail.com>
To: MIF Mailing List <mif@ietf.org>, Internet Area <int-area@ietf.org>, IETF Discussion <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=20cf303bfe24210f7f04bc28b539
Cc: thierry.berisot@telekom.de, jerry.shih@att.com, liliana.dinale@ericsson.com, Ralph Droms <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: Mon, 26 Mar 2012 17:28:52 -0000

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

OMA IETF MIF API Workshop

Time: Tuesday: 18:10-20:00
Location: room 212/213

1) Program
1.1) OMA OpenCMAPI activity (Thierry Berisot, OMA)
1.2) IETF MIF API Design (Ted Lemon, IETF)
1.3) IETF API related consideration (TBD)
1.4) OMA API Program (Liliana Dinale, OMA)
1.5) Vendor's today implementation (Maybe)
1.6) Next step between IETF and OMA (Thierry, Margaret, and Hui)

2) Purpose
2.1) From IETF, this workshop would help to explain the API related topic,
and clarify what is recommended and not recommended to do and standardized,
if possible, either publish a information document or adding word into the
current MIF api draft about how to use those MIF API for Internet developer=
.
and some current practices information how today smart terminal is doing.

2.2) From OMA perspective, to socialize OMA=92s published specifications an=
d
current ongoing standards activities in the area of APIs. To make sure that
the standards landscape for APIs is coordinated and harmonized. To solicit
feedback about OMA=92s specification for Authorization4APIs, which is built
on IETF OAuth as well as OpenCMAPI.

3) Outcomes:
3.1) Future work about how to use those MIF API in an IETF information
 document or inside current MIF API documentfor Internet developers.

3.2) Outcomes OMA: Improved understanding of each others=92 activities,
 and a coordinated approach going forward

3.3) Better mutual understanding of the work of both organizations,
 and how to cooperate in the future.

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

<p>OMA IETF MIF API Workshop<br>=A0<br>Time: Tuesday: 18:10-20:00<br>Locati=
on: room 212/213<br>=A0<br>1) Program<br>1.1) OMA OpenCMAPI activity (Thier=
ry Berisot, OMA) <br>1.2) IETF MIF API Design (Ted Lemon, IETF)<br>1.3) IET=
F API related consideration (TBD) <br>
1.4) OMA API Program (Liliana Dinale, OMA) <br>1.5) Vendor&#39;s today impl=
ementation (Maybe)<br>1.6) Next step between IETF and OMA (Thierry, Margare=
t, and Hui)<br>=A0<br>2) Purpose<br>2.1) From IETF, this workshop would hel=
p to explain the API related topic,<br>
and clarify what is recommended and not recommended to do and standardized,=
 <br>if possible, either publish a information document or adding word into=
 the <br>current MIF api draft about how to use those MIF API for Internet =
developer.<br>
and some current practices information how today smart terminal is doing. <=
br>=A0<br>2.2) From OMA perspective, to socialize OMA=92s published specifi=
cations and <br>current ongoing standards activities in the area of APIs. T=
o make sure that <br>
the standards landscape for APIs is coordinated and harmonized. To solicit =
<br>feedback about OMA=92s specification for Authorization4APIs, which is b=
uilt <br>on IETF OAuth as well as OpenCMAPI.<br>=A0<br>3) Outcomes:<br>3.1)=
 Future work about how to use those MIF API in an IETF information <br>
=A0document or inside current MIF API documentfor Internet developers.</p>
<p>3.2) Outcomes OMA: Improved understanding of each others=92 activities,<=
br>=A0and a coordinated approach going forward</p>
<p>3.3) Better mutual understanding of the work of both organizations, <br>=
=A0and how to cooperate in the future.<br></p>

--20cf303bfe24210f7f04bc28b539--

From john@jck.com  Mon Mar 26 07:43:44 2012
Return-Path: <john@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 81A6021E80C1 for <ietf@ietfa.amsl.com>; Mon, 26 Mar 2012 07:43:44 -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 WX3oW8lVQDsK; Mon, 26 Mar 2012 07:43:43 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id C597621E80C2; Mon, 26 Mar 2012 07:43:43 -0700 (PDT)
Received: from [198.252.137.7] (helo=PST.JCK.COM) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john@jck.com>) id 1SCB4L-0004hN-7B; Mon, 26 Mar 2012 10:38:49 -0400
Date: Mon, 26 Mar 2012 10:43:33 -0400
From: John C Klensin <john@jck.com>
To: SM <sm@resistor.net>, Ray Pelletier <rpelletier@isoc.org>, ietf-streaming@verilan.com, noc@ietf.org, mtg@ietf.org
Subject: Re: Technical Plenary Captioned
Message-ID: <61F18DFFA34487E4121F2114@PST.JCK.COM>
In-Reply-To: <6.2.5.6.2.20120326073716.0b6e1818@resistor.net>
References: <3D796CBB-5FCF-4E1A-8092-F4EF88FAF945@isoc.org> <6.2.5.6.2.20120326071440.0ba41668@resistor.net> <58E56881-8CCC-4B54-83C5-D3046EB845B1@isoc.org> <6.2.5.6.2.20120326073716.0b6e1818@resistor.net>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Mailman-Approved-At: Mon, 26 Mar 2012 12:15:01 -0700
Cc: Discussion IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Mar 2012 14:43:44 -0000

--On Monday, March 26, 2012 07:37 -0700 SM <sm@resistor.net>
wrote:

> Hi Ray,
> At 07:32 26-03-2012, Ray Pelletier wrote:
>> http://www.ietf.org/meeting/83/remote-participation.html
> 
> I read that.  The channel is TBD and there's no sound.

SM, I got the link/file this time (unlike URNBIS, where there
was no file either), but no sound here either


From vinayakh@gmail.com  Mon Mar 26 22:52:21 2012
Return-Path: <vinayakh@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E0B2021F8454; Mon, 26 Mar 2012 22:52:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W9mJBk+mhXFY; Mon, 26 Mar 2012 22:52:21 -0700 (PDT)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id E614A21F84AF; Mon, 26 Mar 2012 22:52:20 -0700 (PDT)
Received: by vcbfk13 with SMTP id fk13so5882437vcb.31 for <multiple recipients>; Mon, 26 Mar 2012 22:52: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=YpMJNmE7brSruuIJR9fp27LMrLrF9QZZWtx+0K+iVxU=; b=hs9PGJyLfD8bCyBtApRKMMqyE4WpiuFgKGLknalK77ncheBJCtlYzIojBcDbSmGdie 27J+r4gjiHhpJXHG3k+tlpcU55zfyD8kCEGIOZMr7Y7I4kb4FFN0ryNBl6qHv8RYzDtQ moW8uyl6LgiqHauOy+SJCJNIdzBRc0soIB3JfM7FGO5xSVT/MKAJNJ4slE3AsaRSAlJe 4cVY5KOsWEg4fKm3vVmXKT/Jug2/YjG+l2FmQkinhW7ke/ueHFxqe/tFOo8ycyoFvB2j qvjM6NbduPLW8KbfOFQ9Mx+xU074tJGKHcSkhxeCaLrwZNtZpSh8m0xeetFl85RycPUz 10LQ==
MIME-Version: 1.0
Received: by 10.52.99.169 with SMTP id er9mr9386973vdb.126.1332827538115; Mon, 26 Mar 2012 22:52:18 -0700 (PDT)
Received: by 10.52.36.148 with HTTP; Mon, 26 Mar 2012 22:52:18 -0700 (PDT)
In-Reply-To: <3D796CBB-5FCF-4E1A-8092-F4EF88FAF945@isoc.org>
References: <3D796CBB-5FCF-4E1A-8092-F4EF88FAF945@isoc.org>
Date: Tue, 27 Mar 2012 11:22:18 +0530
Message-ID: <CAKe6YvOdQUquBJ8qEgB1eyhxmFkk1tL6QJL8Dq8r4PoCUaX5ZA@mail.gmail.com>
Subject: Re: Technical Plenary Captioned
From: Vinayak Hegde <vinayakh@gmail.com>
To: Ray Pelletier <rpelletier@isoc.org>
Content-Type: text/plain; charset=ISO-8859-1
Cc: 83all@ietf.org, Discussion IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Mar 2012 05:52:22 -0000

Is this archived ? Is so, please provide the location.

Thanks
Vinayak

On Mon, Mar 26, 2012 at 7:34 PM, Ray Pelletier <rpelletier@isoc.org> wrote:
> All
>
> The Technical Plenary will be transcribed real time and presented in the Plenary on a screen and also distributed online at:
>
> http://www.streamtext.net/player?event=ietf
>
> Ray
> IETF Administrative Director
>

From ietf.fact.check@gmail.com  Tue Mar 27 16:17:07 2012
Return-Path: <ietf.fact.check@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 46B0821E803C for <ietf@ietfa.amsl.com>; Tue, 27 Mar 2012 16:17:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.781
X-Spam-Level: 
X-Spam-Status: No, score=-2.781 tagged_above=-999 required=5 tests=[AWL=-0.112, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1, US_DOLLARS_3=0.63]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i5Qs4nbFPkf6 for <ietf@ietfa.amsl.com>; Tue, 27 Mar 2012 16:17:06 -0700 (PDT)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id A318621E802C for <Ietf@ietf.org>; Tue, 27 Mar 2012 16:17:06 -0700 (PDT)
Received: by iazz13 with SMTP id z13so595484iaz.31 for <Ietf@ietf.org>; Tue, 27 Mar 2012 16:17:06 -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 :content-transfer-encoding; bh=r5kjSkiiQaonZEpa+KMH8fY5xfq6384DAsLuR7vVIOc=; b=Tlg7LhRJNmxGt7aF+UflTFbEa3SkR5ZEip4oWDK8s7xsr4H6bAhyBpM930npACnOpz 646Rlzb8jy02G1VJv6NFPhuGlkX7gwY7HGQaA8btlZN0yJfCJ+x9U7d+zxBWnnVSyaYw NDnqIa9DBOjLN522Y6Tjms2Ro7i9MQLGA8TQkk20XqTmi1dzMncti7ATl4YaV0zgSCFf aU/6kkeWBZJzShXxOGZ3dUZ4G34afX3KmfYCKMJsbVw+yIbk/94bDFBBPDuoQFbgbabZ g5oYd6pyPoGU49wIQOWBexDcYcvmYVf1qXn6fDpNovS9EFRER/yhyGErFU+U8SOeblUL 9vkQ==
MIME-Version: 1.0
Received: by 10.50.188.138 with SMTP id ga10mr578955igc.51.1332890226211; Tue, 27 Mar 2012 16:17:06 -0700 (PDT)
Received: by 10.50.171.38 with HTTP; Tue, 27 Mar 2012 16:17:06 -0700 (PDT)
Date: Tue, 27 Mar 2012 18:17:06 -0500
Message-ID: <CANwOnkHkBqKXmHxCVRjogj1sHfGuRmcOCLrzCUmxUnkwEz1UUw@mail.gmail.com>
Subject: =?windows-1252?Q?IAB_responds_to_ICANN_questions_concerning_=93The_In?= =?windows-1252?Q?terpretation_of_Rules_in_the_ICANN_gTLD_Guidebook=94?=
From: Jim Fleming <ietf.fact.check@gmail.com>
To: Ietf@ietf.org
Content-Type: text/plain; charset=windows-1252
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: Tue, 27 Mar 2012 23:17:07 -0000

http://www.iab.org/2012/03/27/iab-responds-to-icann-questions-concerning-th=
e-interpretation-of-rules-in-the-icann-gtld-guidebook/

IAB responds to ICANN questions concerning =93The Interpretation of
Rules in the ICANN gTLD Guidebook=94

"The IAB statement could be interpreted as a recommendation to ICANN to
revise the Applicant Guidebook, or as a warning to be cautious when
evaluating applied-for strings with certain properties."
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

http://blog.icann.org/2012/03/ten-million-dns-resolvers-on-the-internet/com=
ment-page-1/#comment-26813

600 Applicants with 50 TLDs at $185,000 each is $5,550,000,000 - that
could pay for a lot of travel and parties

From Francis.Dupont@fdupont.fr  Wed Mar 28 01:13:59 2012
Return-Path: <Francis.Dupont@fdupont.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 6822B21F87C4 for <ietf@ietfa.amsl.com>; Wed, 28 Mar 2012 01:13:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.562
X-Spam-Level: 
X-Spam-Status: No, score=-2.562 tagged_above=-999 required=5 tests=[AWL=0.037,  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 2tyI00duNbhi for <ietf@ietfa.amsl.com>; Wed, 28 Mar 2012 01:13:58 -0700 (PDT)
Received: from givry.fdupont.fr (givry.fdupont.fr [IPv6:2001:41d0:1:6d55:211:5bff:fe98:d51e]) by ietfa.amsl.com (Postfix) with ESMTP id 79AD021F87C5 for <ietf@ietf.org>; Wed, 28 Mar 2012 01:13:57 -0700 (PDT)
Received: from givry.fdupont.fr (localhost [127.0.0.1]) by givry.fdupont.fr (8.14.3/8.14.3) with ESMTP id q2S8Dro1093082; Wed, 28 Mar 2012 10:13:53 +0200 (CEST) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201203280813.q2S8Dro1093082@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: "Worley, Dale R (Dale)" <dworley@avaya.com>
Subject: Re: IPv6 Zone Identifiers Considered Hateful 
In-reply-to: Your message of Wed, 21 Mar 2012 13:44:31 -0400. <CD5674C3CD99574EBA7432465FC13C1B22726A0994@DC-US1MBEX4.global.avaya.com>
Date: Wed, 28 Mar 2012 10:13:53 +0200
Sender: Francis.Dupont@fdupont.fr
Cc: Sabahattin Gucukoglu <mail-dated-1334746550.15c4ac@sabahattin-gucukoglu.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: Wed, 28 Mar 2012 08:14:00 -0000

 In your previous mail you wrote:

>  Looking at the link-local address, it appears to be constructed from
>  the interface's MAC address, and basically nothing else.
       ^^^^^^^^^^^

=> note the IEEE spec says device MAC address and if the common
interpretation is device == NIC there is at least one vendor where
device == machine, i.e., you get the same MAC address so same link-local
address on all the 10 interfaces of a 10 interface box!

Regards

Francis.Dupont@fdupont.fr

PS: I maintain my opinion: zone identifiers don't suck, link-local
addresses used where they should not definitely suck.

From thierry.moreau@connotech.com  Wed Mar 28 07:22:13 2012
Return-Path: <thierry.moreau@connotech.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9ADCA21F8730 for <ietf@ietfa.amsl.com>; Wed, 28 Mar 2012 07:22:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.495
X-Spam-Level: 
X-Spam-Status: No, score=-0.495 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aEyV9PObWQk4 for <ietf@ietfa.amsl.com>; Wed, 28 Mar 2012 07:22:12 -0700 (PDT)
Received: from mail.connotech.com (unknown [76.10.176.241]) by ietfa.amsl.com (Postfix) with ESMTP id 84F6421F8711 for <ietf@ietf.org>; Wed, 28 Mar 2012 07:22:12 -0700 (PDT)
Received: from [192.168.1.200] (unknown [192.168.1.200]) by mail.connotech.com (Postfix) with ESMTPA id 480B5308AA; Wed, 28 Mar 2012 15:40:51 -0400 (EDT)
Message-ID: <4F731FD7.8060704@connotech.com>
Date: Wed, 28 Mar 2012 10:27:35 -0400
From: Thierry Moreau <thierry.moreau@connotech.com>
User-Agent: Thunderbird 2.0.0.17 (X11/20090608)
MIME-Version: 1.0
To: Francis Dupont <Francis.Dupont@fdupont.fr>
Subject: Re: IPv6 Zone Identifiers Considered Hateful
References: <201203280813.q2S8Dro1093082@givry.fdupont.fr>
In-Reply-To: <201203280813.q2S8Dro1093082@givry.fdupont.fr>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Sabahattin Gucukoglu <mail-dated-1334746550.15c4ac@sabahattin-gucukoglu.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: Wed, 28 Mar 2012 14:22:13 -0000

Francis Dupont wrote:
>  In your previous mail you wrote:
> 
>>  Looking at the link-local address, it appears to be constructed from
>>  the interface's MAC address, and basically nothing else.
>        ^^^^^^^^^^^
> 
> => note the IEEE spec says device MAC address and if the common
> interpretation is device == NIC there is at least one vendor where
> device == machine, i.e., you get the same MAC address so same link-local
> address on all the 10 interfaces of a 10 interface box!
> 
> Regards
> 
> Francis.Dupont@fdupont.fr
> 
> PS: I maintain my opinion: zone identifiers don't suck, link-local
> addresses used where they should not definitely suck.
> 

Maybe link local addresses are erroneously used where one should use 
RFC4193 (Unique Local IPv6 Unicast Addresses) with L=1? (I mean where 
link local addresses are inconvenient but not necessary.)

I.e. something like FDxx:yyyy:zzzz:nnnn:id
where xx:yyyy:zzzz is 40 random bits that you pick-up as you wish,
nnnn is a subnet id for your (local) routing scheme
id is the 64 bits interface ID ...

It's a suggestion.

I guess the trouble of assigning addresses in this way is much smaller 
than tracking link local addresses derived from hardware serial numbers. 
The interface ID assignment strategy/tools with RFC4193 is deemed to be 
close to the strategy/tools useful for globally routable addresses.

Is this well explained in the IPv6 tutorials?

Regards,

-- 
- Thierry Moreau


From ietf@meetecho.com  Wed Mar 28 07:38:34 2012
Return-Path: <ietf@meetecho.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9794921E81FD for <ietf@ietfa.amsl.com>; Wed, 28 Mar 2012 07:38:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.954
X-Spam-Level: 
X-Spam-Status: No, score=-0.954 tagged_above=-999 required=5 tests=[AWL=-0.235, BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id STECwqCsNMwV for <ietf@ietfa.amsl.com>; Wed, 28 Mar 2012 07:38:33 -0700 (PDT)
Received: from smtplq04.aruba.it (smtplqs-out26.aruba.it [62.149.158.66]) by ietfa.amsl.com (Postfix) with SMTP id D962721E818A for <ietf@ietf.org>; Wed, 28 Mar 2012 07:38:32 -0700 (PDT)
Received: (qmail 13672 invoked by uid 89); 28 Mar 2012 14:38:25 -0000
Received: from unknown (HELO smtp1.aruba.it) (62.149.158.221) by smtplq04.aruba.it with SMTP; 28 Mar 2012 14:38:25 -0000
Received: (qmail 28494 invoked by uid 89); 28 Mar 2012 14:38:25 -0000
Received: from unknown (HELO ?130.129.21.177?) (ietf@meetecho.com@130.129.21.177) by smtp1.ad.aruba.it with SMTP; 28 Mar 2012 14:38:25 -0000
Message-ID: <4F73225A.6010204@meetecho.com>
Date: Wed, 28 Mar 2012 16:38:18 +0200
From: Meetecho IETF support <ietf@meetecho.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:11.0) Gecko/20120312 Thunderbird/11.0
MIME-Version: 1.0
To: ietf@ietf.org, vmeet@ietf.org
Subject: Meetecho support fot Plenary session
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Rating: smtp1.ad.aruba.it 1.6.2 0/1000/N
X-Spam-Rating: smtplq04.aruba.it 1.6.2 0/1000/N
Cc: Team Meetecho <team@meetecho.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, 28 Mar 2012 14:38:35 -0000

Hi all,

we made a last minute arrangement and we're supporting the Operations 
and Administrations Plenary through Meetecho!

To participate:
http://srv137.conf.meetecho.com/WebLite/login.jsp?ietf=plenary

Regards,
the Meetecho team

-- 
Meetecho s.r.l.
Web Conferencing and Collaboration Tools
www.meetecho.com

From dwm@xpasc.com  Wed Mar 28 11:17:05 2012
Return-Path: <dwm@xpasc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0397221E8113 for <ietf@ietfa.amsl.com>; Wed, 28 Mar 2012 11:17:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.273
X-Spam-Level: 
X-Spam-Status: No, score=-4.273 tagged_above=-999 required=5 tests=[AWL=-1.674, 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 SibW0GoukFK7 for <ietf@ietfa.amsl.com>; Wed, 28 Mar 2012 11:17:04 -0700 (PDT)
Received: from c2w3p-2.abacamail.com (c2w3p-2.abacamail.com [209.133.53.32]) by ietfa.amsl.com (Postfix) with ESMTP id 9F99421E817B for <ietf@ietf.org>; Wed, 28 Mar 2012 11:17:04 -0700 (PDT)
Received: from xpasc.com (unknown [68.164.244.188]) by c2w3p-2.abacamail.com (Postfix) with ESMTP id 3FA3A4057E; Wed, 28 Mar 2012 18:16:58 +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 q2SIGr2r021813; Wed, 28 Mar 2012 11:16:55 -0700
Date: Wed, 28 Mar 2012 11:16:53 -0700 (PDT)
From: David Morris <dwm@xpasc.com>
To: IAB Chair <iab-chair@iab.org>, webmaster@iab.org
Subject: Re: IAB responds to ICANN questions concerning "The interpretation of rules in the ICANN gTLD applicant guidelines"
In-Reply-To: <99EF8C10-307B-4E3F-8A0F-99D8D3200251@iab.org>
Message-ID: <alpine.LRH.2.01.1203281114270.16047@egate.xpasc.com>
References: <99EF8C10-307B-4E3F-8A0F-99D8D3200251@iab.org>
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.24-gef8a08a
X-CLX-ID: a120AD3GD2zQ1vr-2S1116w
X-CLX-Spam: false
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, 28 Mar 2012 18:17:05 -0000

Please be advised that this page does not print correctly using IE8 on 
XP/SP3 ... this is the sort of thing I reserve for study when I'm not 
online or trying to give my eyes a break.

On Wed, 28 Mar 2012, IAB Chair wrote:

> The IAB has responded to ICANN questions concerning "The interpretation of rules in the ICANN gTLD applicant guidebook":
> 
> https://www.iab.org/documents/correspondence-reports-documents/2012-2/response-to-icann-questions-concerning-the-interpretation-of-rules-in-the-icann-gtld-applicant-guidebook/
> 

From dcrocker@gmail.com  Wed Mar 28 00:34:26 2012
Return-Path: <dcrocker@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A1CE121F863D for <ietf@ietfa.amsl.com>; Wed, 28 Mar 2012 00:34: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 MHxxIBs+XrTM for <ietf@ietfa.amsl.com>; Wed, 28 Mar 2012 00:34:26 -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 9F2DC21F876A for <ietf@ietf.org>; Wed, 28 Mar 2012 00:34:25 -0700 (PDT)
Received: by eaaq11 with SMTP id q11so171629eaa.31 for <ietf@ietf.org>; Wed, 28 Mar 2012 00:34:24 -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:content-type:content-transfer-encoding; bh=3jEBYBA+eZU6rpkjR1LpAULDnWaEK8fbFwT4ru9ZwU4=; b=Sg6Bzye21dXdeNt6T+H+kPgV6j1QFmUkbI/LctzmHvSfy2Qbdqa+YXCHOZlsIY5TBl lxgN8RWKPSp4DtHSmXKCXdzAk4v/2gUml5eVX5YcfaNT8i0MHgCKMFLU6WVhMVsRZKOo 618G5eqeRzwJdg3XC+Y+fM0T249maSvfTmeGaDXMnCIQwnx6zMdPzVBU0JOK5UUivvfx jf2POtC/37ReXXZxyEwsbk+NQ/J5JdQqx3N+cjX84cx88+I9h9UAvhKzueL7XEqtfWRP 7LtXeeDFSzZ3mmmVAJlQ709J80zTYXs1NlhCTJl0aIK55bpDehZIb58llIoeMCiU3cV2 oHfw==
Received: by 10.213.35.135 with SMTP id p7mr2074113ebd.61.1332920064819; Wed, 28 Mar 2012 00:34:24 -0700 (PDT)
Received: from ?IPv6:2001:df8:0:80:3cef:ffe2:96cb:45cf? ([2001:df8:0:80:3cef:ffe2:96cb:45cf]) by mx.google.com with ESMTPS id n55sm7445081eef.6.2012.03.28.00.34.23 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 28 Mar 2012 00:34:24 -0700 (PDT)
Message-ID: <4F72BEFC.1000806@gmail.com>
Date: Wed, 28 Mar 2012 09:34:20 +0200
From: Dave Crocker <dcrocker@gmail.com>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:11.0) Gecko/20120312 Thunderbird/11.0
MIME-Version: 1.0
To: IETF Discussion <ietf@ietf.org>
Subject: response set assertions and extensions
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Wed, 28 Mar 2012 11:26:36 -0700
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Mar 2012 07:34:26 -0000

> 3.1.  Assertions
>
>    The "email-id" reputation application recognizes the following
>    assertions:
...
> 3.2.  Vocabulary Extensions
>
>    The "email-id" reputation application recognizes the following
>    OPTIONAL extensions to the basic vocabulary defined in
>    [I-D.REPUTE-MODEL]:


Reflecting on these two sections and especially the reference to vocabulary 
(response set) in -model:

    Somehow I didn't find a base response set (vocabulary) or base assertions in 
the model document.  I'd expected to have found a core set of information types 
that would be common across all uses of Repute.

    Did I miss what is actually in -model?  If not, shouldn't there be a base 
response set (and maybe assertions)?

d/

ps. i hope it's obvious i'm not wearing a hat, but i'm also just asking questions...
-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

From ietf.fact.check@gmail.com  Wed Mar 28 12:21:55 2012
Return-Path: <ietf.fact.check@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 60FF021E80A1 for <ietf@ietfa.amsl.com>; Wed, 28 Mar 2012 12:21:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.71
X-Spam-Level: 
X-Spam-Status: No, score=-1.71 tagged_above=-999 required=5 tests=[AWL=-1.155,  BAYES_40=-0.185, RCVD_IN_DNSWL_LOW=-1, US_DOLLARS_3=0.63]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m9rY61QQuoMT for <ietf@ietfa.amsl.com>; Wed, 28 Mar 2012 12:21:54 -0700 (PDT)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id 52CF921E80D5 for <ietf@ietf.org>; Wed, 28 Mar 2012 12:21:53 -0700 (PDT)
Received: by iazz13 with SMTP id z13so2171979iaz.31 for <ietf@ietf.org>; Wed, 28 Mar 2012 12:21:49 -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=EOtUrEzvIZ5DjVly3mkeciw6v7EZFMzHWGwTMNYA2Gw=; b=DSdgb4pFlCoZwcQ2RkqMwhVQKseWV4Vp2Eb2AoFsBVymW8JKhu8LNFMTumhGZU8MGS zWI3hSEVKYN/rOn8cgMBb21AOOam+f17v0UwPZUMQaJeebaAOp1p7xuvflj7uAMGEGou bG0wGjzyYfyx/FEOJ8sIkmimU3CFjxuzSF0tlmO3vb+pqGhZZikFjLA8uI1LkTzXKnqe 5eVc+8Mkd+l1iettkavCzqIY7dSWmvFemKGQfP/viFK6+rFf8aE+BEV2hwbnLsWPlJVr 4/RC3mj3Z32n7KhOyeh56j0mrGCHQN1nEaT1aDoptx6jJe3O8saKeft821+nqvP7GS/Y u0rA==
MIME-Version: 1.0
Received: by 10.50.187.231 with SMTP id fv7mr200023igc.51.1332962509059; Wed, 28 Mar 2012 12:21:49 -0700 (PDT)
Received: by 10.50.171.38 with HTTP; Wed, 28 Mar 2012 12:21:48 -0700 (PDT)
Date: Wed, 28 Mar 2012 14:21:48 -0500
Message-ID: <CANwOnkE_4goApO-q0mUGj91rmUsCAYDP7-KDbYyaBg4rWj2Z8Q@mail.gmail.com>
Subject: IETF.Fact.Check - .COM .NET .ORG Legacy DNS vs Peer-2-Peer DNS
From: Jim Fleming <ietf.fact.check@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, 28 Mar 2012 19:21:55 -0000

ZOOM://IETF.Fact.Check

IETF.Fact.Check - .COM .NET .ORG Legacy DNS vs Peer-2-Peer DNS

1. The .COM .NET .ORG ICANN (IANA) U.S. Department of Commerce
contracts are coming up for renewal.[1]

2. The Legacy Client-Server DNS is OUT-DATED and highly monetized for
Meat.Space.Mammals

3. Netizens clearly prefer True.Internet.Technology with a Peer-2-Peer
Architecture

4. Peer-2-Peer DNS and Virtual Currency are finally gaining
market-share with BitCoin and NameCoin using Bit.Throttles.[2]

5. Migration of existing .COM and .NET owners to Peer-2-Peer DNS
negates the need for .COM and .NET contract renewals.

6. Migration of existing .ORG owners to Peer-2-Peer DNS appears to be
a waste of time.****

7. Peer-2-Peer DNS begins with Digital.Wallets and many companies are
working on variations and services.[3]


ZOOM://IETF.Fact.Check - It does not appear that the IETF has any
current interest in Peer-2-Peer DNS

**** ZOOM://IETF.Fact.Check - The .ORG contract renewal could impact
the ISOC (IETF) and a $34,000,000 annual donation from the PIR (set up
by the ISOC). People with $600,000 annual non-profit compensation
packages may oppose any changes.


SEARCH://BITCOIN
http://bitcoin.org/
SEARCH://NAMECOIN
https://en.bitcoin.it/wiki/Namecoin


[1] http://www.icann.org/en/news/announcements/announcement-27mar12-en.htm

[2] http://bittco.yolasite.com

[3] http://code.google.com/p/bitcoin-wallet/

From nick@inex.ie  Wed Mar 28 12:57:10 2012
Return-Path: <nick@inex.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 169A821F8555 for <ietf@ietfa.amsl.com>; Wed, 28 Mar 2012 12:57:10 -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 qAgtwBLRSZgo for <ietf@ietfa.amsl.com>; Wed, 28 Mar 2012 12:57:09 -0700 (PDT)
Received: from mail.acquirer.com (mail.acquirer.com [IPv6:2a03:8900:0:100::5]) by ietfa.amsl.com (Postfix) with ESMTP id C6C1621F84DE for <ietf@ietf.org>; Wed, 28 Mar 2012 12:57:07 -0700 (PDT)
X-Envelope-To: <ietf@ietf.org>
Received: from crumpet.foobar.org ([IPv6:2001:4d68:2002:100:48f0:bbda:fe47:2d4e]) (authenticated bits=0) by mail.acquirer.com (8.14.4/8.14.4) with ESMTP id q2SJv9C3072129 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Wed, 28 Mar 2012 20:57:15 +0100 (IST) (envelope-from nick@inex.ie)
Message-ID: <4F736D0B.1070009@inex.ie>
Date: Wed, 28 Mar 2012 20:56:59 +0100
From: Nick Hilliard <nick@inex.ie>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:11.0) Gecko/20120313 Thunderbird/11.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: IETF.Fact.Check - .COM .NET .ORG Legacy DNS vs Peer-2-Peer DNS
References: <CANwOnkE_4goApO-q0mUGj91rmUsCAYDP7-KDbYyaBg4rWj2Z8Q@mail.gmail.com>
In-Reply-To: <CANwOnkE_4goApO-q0mUGj91rmUsCAYDP7-KDbYyaBg4rWj2Z8Q@mail.gmail.com>
X-Enigmail-Version: 1.4
X-Company-Info-1: Internet Neutral Exchange Association Limited. Registered in Ireland No. 253804
X-Company-Info-2: Registered Offices: 1-2, Marino Mart, Fairview, Dublin 3
X-Company-Info-3: Internet Neutral Exchange Association Limited is limited by guarantee
X-Company-Info-4: Offices: 4027 Kingswood Road, Citywest, Dublin 24.
Content-Type: text/plain; charset=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: Wed, 28 Mar 2012 19:57:10 -0000

On 28/03/2012 20:21, Jim Fleming wrote:
> ZOOM://IETF.Fact.Check

What I'd like to know is whether the ZOOM:// protocol is IPv8 compatible.

Nick

From ietf.fact.check@gmail.com  Wed Mar 28 13:51:32 2012
Return-Path: <ietf.fact.check@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 45D7F21E808A for <ietf@ietfa.amsl.com>; Wed, 28 Mar 2012 13:51:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.837
X-Spam-Level: 
X-Spam-Status: No, score=-3.837 tagged_above=-999 required=5 tests=[AWL=1.162,  BAYES_00=-2.599, GB_I_LETTER=-2, J_CHICKENPOX_53=0.6, 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 w6PHav4vu6Ai for <ietf@ietfa.amsl.com>; Wed, 28 Mar 2012 13:51:31 -0700 (PDT)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id 359BC21E8089 for <ietf@ietf.org>; Wed, 28 Mar 2012 13:51:31 -0700 (PDT)
Received: by iazz13 with SMTP id z13so2278614iaz.31 for <ietf@ietf.org>; Wed, 28 Mar 2012 13:51:30 -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=rohd5q7kGEmBAhyFLtK8fkC8/gAOwNnBuQK8rCycGDc=; b=gVseg9hVoFm9je54I5LEYckTinzJxqTAOa8/godarGaq1uvZfS30+Su7eYb+72WyVq qE4u8wrV77abj/78BuQf3yEc3/MAT5ng8yDMNpKtirngblR/DaDH9uO0KeEo52CfJlXS 99bMdY9vC4nkGhTeJNEHdgnDeuHXLJYKbio16S7BH0P2HLRx2vX8lh/t80gzkxH+Hork TAoMBY1lGYJ10Oul7C2VWLG04MAd74tTRvsaf46jeeXByrLtshP8gsUfQofs56JuW+5/ iDkH0ZWyqGZkANThcuN8Z7ayoHRZDlMaaePMUMWfvVm15bkHRzhtyuxT7MJuUDbNDi8D QGug==
MIME-Version: 1.0
Received: by 10.50.149.131 with SMTP id ua3mr421841igb.41.1332967890806; Wed, 28 Mar 2012 13:51:30 -0700 (PDT)
Received: by 10.50.171.38 with HTTP; Wed, 28 Mar 2012 13:51:30 -0700 (PDT)
Date: Wed, 28 Mar 2012 15:51:30 -0500
Message-ID: <CANwOnkGJsSouGSLkRpaTgz3Oopsv2VAjyAK52YNMV=mvXZhY7w@mail.gmail.com>
Subject: IETF.Fact.Check on the ZOOM:// Scheme and ZOOM://BOX Architecture and the Inter.NOT
From: Jim Fleming <ietf.fact.check@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, 28 Mar 2012 20:51:32 -0000

ZOOM://IETF.Fact.Check

IETF.Fact.Check on the ZOOM:// Scheme and ZOOM://BOX Architecture

ZOOM:// is a Scheme not a Protocol

The ZOOM://BOX Architecture as No Back-Haul connection to the Legacy Inter.NET

When you deploy your free open-source ZOOM://BOX and invite wireless
users they connect to the Inter.NOT

NOTE: the .NOT Top.Level.Domain is "Confusingly Similar" to the .NET
Top.Level.Domain so you are banned from using it

The ZOOM://BOX Architecture uses modern Peer-2-Peer and MULE
Technology (aka Sneaker.Net)

Users are the MULES and they carry Objects from place to place

ZOOM=15.3.3.13 or 0xF33D = P2P Port 62,269

The Official ZOOM://DNS 4-bit Alphabet
"ETAO^NRIS^HDLF^CMUZ"
"0123^4567^89AB^CDEF"

Note: The Letter "Z" is a WildCard (.-X*)
Use ZNZ for .NZ or ZOOM://NZ

ZOOM=15.3.3.13 or 0xF33D = P2P Port 62,269

ZOOM://DNS on Port 62,269

COM=12.3.13 or 0xC3D = P2P Port 3133

NET=4.0.1 or 0x401 = P2P Port 1025

ZNZ=15.4.15 or 0xF4F = P2P Port 3919

There is no "G" for .ORG or "B" for .BIZ

NO $$.IANA.$$ is needed to hand-select Ports

EXPLORE://BLOCK0
http://blockexplorer.com/b/0

=======================

10/100 Ethernet

10/8
100/8
http://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.txt

There are 10 kinds of people in the world those that understand binary
and those that do not
There are 100 kinds of people in the world those that see 100 as 4 and 99 others

Migrating to Binary prefixes with IPv4 addresses can be interesting.
10.9.8.7.6 it takes 2 bits to store 10
How many bits does it take to store 100 ?

From ietf.fact.check@gmail.com  Wed Mar 28 14:16:58 2012
Return-Path: <ietf.fact.check@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C86B21E8105 for <ietf@ietfa.amsl.com>; Wed, 28 Mar 2012 14:16:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.233
X-Spam-Level: 
X-Spam-Status: No, score=-3.233 tagged_above=-999 required=5 tests=[AWL=0.366,  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 jguuvOibM7Vx for <ietf@ietfa.amsl.com>; Wed, 28 Mar 2012 14:16:57 -0700 (PDT)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id F1E5F21E8040 for <ietf@ietf.org>; Wed, 28 Mar 2012 14:16:56 -0700 (PDT)
Received: by iazz13 with SMTP id z13so2308477iaz.31 for <ietf@ietf.org>; Wed, 28 Mar 2012 14:16:56 -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 :content-transfer-encoding; bh=o80AMF/hqeVy7+qQ8qOmz81R5bP+lJ0G9zI9O9G9WSU=; b=HlLA6fy39LB5cYe3YXjUcFFJP9kA9XKb7NcVGbXAeZ8m2AYlmbmIlTuOfxATmtXou8 cXcb+GE8HOeU3xqLoxA3sJjiN9U0i9y2zWmSDwXt08ye6e7LMHdHSVGDUmfyFcc1vQCN rO/WDeywlOjy7ezC6qjt52Bg0418aVFr5JlmBfuG21x1FeYuzofHFlfoIlUKSXjyirhn Ev+0ntQEUtKqd55zDmhKnsXda0ZMqUpwO71qzncwuV76utYEA4wuj/cMn1Mr5evGNZJZ Sk+tjqlqtKW07G12STX1mymFZC21FLwvUJTMY1ib+uGrOtzX6N4PaZT8I/t5mv5ZnBCg T9DQ==
MIME-Version: 1.0
Received: by 10.50.188.138 with SMTP id ga10mr458918igc.51.1332969416654; Wed, 28 Mar 2012 14:16:56 -0700 (PDT)
Received: by 10.50.171.38 with HTTP; Wed, 28 Mar 2012 14:16:56 -0700 (PDT)
Date: Wed, 28 Mar 2012 16:16:56 -0500
Message-ID: <CANwOnkEA78qG-O-rD-Z_hYW0rx1tQizs4BTXfUWn_RoePjMtqw@mail.gmail.com>
Subject: IETF.Fact.Check on the ZOOM://BOX Protocol(s)
From: Jim Fleming <ietf.fact.check@gmail.com>
To: ietf <ietf@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Mar 2012 21:16:58 -0000

IETF.Fact.Check on the ZOOM://BOX Protocol(s)

ZOOM://Protocols

There are two dominant header sizes 160-bits and 320-bits

It takes three 160-bit headers to form a 480-bit DHT*** Key or a
160-bit header and a 320-bit header

The first 4 bits of the 160-bit header are SDSD for Source and
Destination Addressing
A VVRR view is also used for Version and Ring
A legacy value of 0100 is Version 01 and Ring 0 to Ring 0 - Source 0
Destination 0
a value of 0011 is Version 00 and Ring 1 to Ring 1 - Source 1
Destination 1 - used behind the first 10/100 firewall 100/8
...other values of the 4 bits are left as an exercise for the reader...

Your stand-alone ZOOM://BOX has all the details and documentation and
NO back-haul connection - Mules carry the messages - sometimes very
slowly and long distances...
http://WheresGeorge.com

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

***DHT - Distributed Hash Table

"The Network IS the Registry"

A Virtual Disk Drive with 480-bit Sector Addresses (KEY)

1024 Byte DATA Blocks

4 Bitt TIME Setting

(Day | Week | Month | Year)


Two Simple Operations

PUT(KEY,DATA,TIME)=A2=A2=A2=A2

GET(KEY)=A2=A2=A2=A2


The global network stores the DATA via the KEY for the period of TIME.
The DATA is returned when the proper KEY is provided via GET(KEY).
ACID - Atomic, Coherent, Isolated & Durable apply.

It all just works, like magic. Replication of DATA, KEY management,
etc. is handled via the Peer-2-Peer Network of Nodes. THERE IS NO
CLOUD. FOG would be a better description. Each user contributes part
of their server and power capacity.

The maximum TIME is one Year + one Month + one Week + one Day (1111).
A TIME of (0000) specifies the default BIT Throttle - Genesis BITT
Block Chain.

Applications build on top of the DHT to provide other virtual
services, such as the DNS - Domain Name System. The 480-bit KEY can be
encoded via an 80 Symbol ZOOM.NAME. Three 160-bit BITT Addresses can
be combined to form a unique 480-bit KEY.


Operations are THROTTLED by BITTs =A2=A2=A2=A2

(and Peer-2-Peer Stooges)

From ietf.fact.check@gmail.com  Wed Mar 28 16:10:56 2012
Return-Path: <ietf.fact.check@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BC0E921E8153 for <ietf@ietfa.amsl.com>; Wed, 28 Mar 2012 16:10:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.962
X-Spam-Level: 
X-Spam-Status: No, score=-2.962 tagged_above=-999 required=5 tests=[AWL=0.038,  BAYES_00=-2.599, J_CHICKENPOX_53=0.6, 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 E9PCa9TBHwDB for <ietf@ietfa.amsl.com>; Wed, 28 Mar 2012 16:10:49 -0700 (PDT)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id 0F25221E80B3 for <ietf@ietf.org>; Wed, 28 Mar 2012 16:10:49 -0700 (PDT)
Received: by iazz13 with SMTP id z13so2447577iaz.31 for <ietf@ietf.org>; Wed, 28 Mar 2012 16:10:48 -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=Dm+gFGNmZnCCAlphaEsAYhsyoSBaqa4VHcIqRaTvkWA=; b=ofYhBMqWb/3y6viSGjqBs4DfyAs+kzTGlwSZaKmcYmocWk2BUowaDcid6YIxFNCgCh 2ksRSiBkiqzY8+ocsk2ri9FMUV112iNen/4kJcbrG8I2RRjqAzJQzgVTF0w6/M20YhmI ZoD0TsaB5lZf48GYMY762snfwp8posplX3jqWZnbeX1bEt0ST6QBZlLC0RBy+iMWu38l 8EKTiF1urT7mcrUcmvYlG0hb2W9vm1ITyKxpt/JJpvZVGYC8OQABRgkVQsSRe8X5rCXQ uBaq+oimT4ltKEbNs1aebYtXHgHhtBgsItNrj24XB4OSu8NlcVPNXMULMmU9RE9DJ0C0 FxmA==
MIME-Version: 1.0
Received: by 10.50.207.5 with SMTP id ls5mr658088igc.51.1332976248676; Wed, 28 Mar 2012 16:10:48 -0700 (PDT)
Received: by 10.50.171.38 with HTTP; Wed, 28 Mar 2012 16:10:48 -0700 (PDT)
Date: Wed, 28 Mar 2012 18:10:48 -0500
Message-ID: <CANwOnkHQFsm=L=J_N2+z_ZOStaCLt2jSFsiJGxncrkjQVKx_pw@mail.gmail.com>
Subject: IETF.FACT.CHECK ....839 new Top Level Domains or more...plus the DIRTY.BIT
From: Jim Fleming <ietf.fact.check@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, 28 Mar 2012 23:10:56 -0000

ZOOM://IETF.Fact.Check

The Latest Number of TLD Application System Registrants

"As of 25 March 2012 the number of registered users in the online TLD
Application System (TAS) stands at 839. However, this number does not
necessarily represent the total number of applications since each
registrant can apply for up to 50 new generic Top-Level Domains."

http://newgtlds.icann.org/en/program-status/statistics

Only the TOP 4096 TLDs will be carried in the new DNS
http://archive.icann.org/en/comments-mail/icann-current/msg00342.html

That used to be called Best.of.Breed.

Check out the TLDs leaked on the screens in this video from
Music.Night and the DIRTY.BIT** (aka the Evil.Bit)
http://www.youtube.com/watch?v=vpTEtM_SXrU&feature=player_embedded

Domainers have much better parties than the ISOC and IETF - and
Domainers have 3D and Avatars and web-cams and Peer-2-Peer

http://ZOOM.NAME

The DIRTY.BIT is set in the packet header after the Source and
Destination fields change places as the One-Way packet routes the
second half of the 60-bit path.

ZOOM://IETF.Fact.Check

From ietf@meetecho.com  Wed Mar 28 16:41:06 2012
Return-Path: <ietf@meetecho.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D66DF21E8160 for <ietf@ietfa.amsl.com>; Wed, 28 Mar 2012 16:41:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.719
X-Spam-Level: 
X-Spam-Status: No, score=-0.719 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SZ8tJPKTMbft for <ietf@ietfa.amsl.com>; Wed, 28 Mar 2012 16:41:06 -0700 (PDT)
Received: from smtplq01.aruba.it (smtplqs-out27.aruba.it [62.149.158.67]) by ietfa.amsl.com (Postfix) with SMTP id BBDD121E8024 for <ietf@ietf.org>; Wed, 28 Mar 2012 16:41:05 -0700 (PDT)
Received: (qmail 4468 invoked by uid 89); 28 Mar 2012 23:41:03 -0000
Received: from unknown (HELO smtp7.aruba.it) (62.149.158.227) by smtplq01.aruba.it with SMTP; 28 Mar 2012 23:41:03 -0000
Received: (qmail 24634 invoked by uid 89); 28 Mar 2012 23:41:03 -0000
Received: from unknown (HELO ?192.168.0.40?) (alex@meetecho.com@78.192.151.119) by smtp7.ad.aruba.it with ESMTPA; 28 Mar 2012 23:41:03 -0000
Message-ID: <4F73A188.5060203@meetecho.com>
Date: Thu, 29 Mar 2012 01:40:56 +0200
From: Meetecho IETF support <ietf@meetecho.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:11.0) Gecko/20120312 Thunderbird/11.0
MIME-Version: 1.0
To: ietf@ietf.org, vmeet@ietf.org
Subject: Re: Meetecho support fot Plenary session
References: <4F73225A.6010204@meetecho.com>
In-Reply-To: <4F73225A.6010204@meetecho.com>
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Rating: smtplq01.aruba.it 1.6.2 0/1000/N
Cc: Team Meetecho <team@meetecho.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, 28 Mar 2012 23:41:06 -0000

Hi again,

the full recording (synchronized video, audio, slides and jabber room)
of the Operations and Administration Plenary session at IETF-83 is 
available.

You can watch it by directly accessing the following URL:
http://ietf83.conf.meetecho.com/index.php/Recorded_Sessions#ADMIN_PLENARY_IETF83

For the chair(s): please feel free to put the link to the recording in 
the minutes, if you think this might be useful.

In case of problems with the playout, just drop an e-mail to
team@meetecho.com.

Cheers,
the Meetecho team

--
Meetecho s.r.l.
Web Conferencing and Collaboration Tools
www.meetecho.com

Il 28/03/2012 16:38, Meetecho IETF support ha scritto:
> Hi all,
>
> we made a last minute arrangement and we're supporting the Operations
> and Administrations Plenary through Meetecho!
>
> To participate:
> http://srv137.conf.meetecho.com/WebLite/login.jsp?ietf=plenary
>
> Regards,
> the Meetecho team
>

From ietf.fact.check@gmail.com  Wed Mar 28 16:53:57 2012
Return-Path: <ietf.fact.check@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DDF5D21E802C for <ietf@ietfa.amsl.com>; Wed, 28 Mar 2012 16:53:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.264
X-Spam-Level: 
X-Spam-Status: No, score=-3.264 tagged_above=-999 required=5 tests=[AWL=0.335,  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 hFnBiDFKjuUY for <ietf@ietfa.amsl.com>; Wed, 28 Mar 2012 16:53:57 -0700 (PDT)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id 14B2421E8024 for <ietf@ietf.org>; Wed, 28 Mar 2012 16:53:57 -0700 (PDT)
Received: by iazz13 with SMTP id z13so2497086iaz.31 for <ietf@ietf.org>; Wed, 28 Mar 2012 16:53:56 -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=wILkrNoHDAgoXbnBjYHmNb0b4xV+ghesveeJswdj6Qw=; b=yRr0a63x27rmb/SZim+CP+7Mo5EC3AbdUSKqgUgRKDOFurrxXMtooNAahorBziAV4/ o/Zo/LSX9p1tOaEAFc4KHGXEWebLbnkpaBbRJDrm2tx1HoxDwFaU6/CCSKME/5xF5Z7I POYUMbcZHCfBAeIlGtQAt5ofEsKnn2XlPBTE9R0gNBiEdiwJqOJkrOBUVw8DAddixs0E lAYAj9vR6jO69apTHnFP03QToHK1NfO932Xd/S6UyBq2hkH2QFnrhVvBs9sWgyK+EwtU SNO8kPtEfQtFDw30eZFCVl8tuh7DB6x0RWdeNUjHh5keIhXTDH8REZ7j/x2FNh9xSUil SWjg==
MIME-Version: 1.0
Received: by 10.50.149.131 with SMTP id ua3mr776750igb.41.1332978836785; Wed, 28 Mar 2012 16:53:56 -0700 (PDT)
Received: by 10.50.171.38 with HTTP; Wed, 28 Mar 2012 16:53:56 -0700 (PDT)
Date: Wed, 28 Mar 2012 18:53:56 -0500
Message-ID: <CANwOnkFUAMtBxJDpjPpq4ibGrUU7uEisa-LR+nf7=Er7oB+AUA@mail.gmail.com>
Subject: ZOOM://IETF.Fact.Check ? 2012 State of the Art according to the ISOC ?
From: Jim Fleming <ietf.fact.check@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, 28 Mar 2012 23:53:58 -0000

ZOOM://IETF.Fact.Check

? 2012 State of the Art according to the ISOC ?

http://www.internetsociety.org/events/internet-society-panel-openid-and-oauth-ietf-83

Internet Society Panel on OpenID and OAuth @ IETF 83
Date:
27 March 2012 - 11:45am
Location: Le Palais des Congres, Paris, France, Room 242B
Time: 11:45 - 12:45 local time

ZOOM://IETF.Fact.Check

From ietf.fact.check@gmail.com  Wed Mar 28 18:37:47 2012
Return-Path: <ietf.fact.check@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6506821E801C for <ietf@ietfa.amsl.com>; Wed, 28 Mar 2012 18:37:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.306
X-Spam-Level: 
X-Spam-Status: No, score=-3.306 tagged_above=-999 required=5 tests=[AWL=0.293,  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 RsKmYInugfvQ for <ietf@ietfa.amsl.com>; Wed, 28 Mar 2012 18:37:46 -0700 (PDT)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id 7ABD821E800F for <ietf@ietf.org>; Wed, 28 Mar 2012 18:37:46 -0700 (PDT)
Received: by iazz13 with SMTP id z13so2622848iaz.31 for <ietf@ietf.org>; Wed, 28 Mar 2012 18:37:46 -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=uaerHGAPkQXq8PHAh7a4rediYDi0wHWC9RUWFy07j5w=; b=weokc/Utbt1t8TBjxe+lj4ryVGQtgsR/TR2LHBMrOglSFmmpSM5vKWPSTlowwWPLnP 3x9Yg39GOXV6mARrUtLr1a5Xfj2V6vcw8F4JaZFQfzkx8cg1xgU8dQSWpVE0iScqBw0s D10pQAaJt7AwBCkMz8oWdYikL00DSHGdplShh8GgHd7zvvsAon8j6Dm2UDta0l0pHx4f Iy3/OpkiH3+pK3zZff9BwFx9m5c0iSlS/EOArUUVdzgTDnFXR4radVu8QhZScDj5j+XN 0sXQDsYcueUXM+/SjbGEYzcD1KxXl42EGo+0BIqWvzfPZhpcC+Pi8W1JKeCUNZSEVqka K6Jw==
MIME-Version: 1.0
Received: by 10.50.212.101 with SMTP id nj5mr132549igc.41.1332985066213; Wed, 28 Mar 2012 18:37:46 -0700 (PDT)
Received: by 10.50.171.38 with HTTP; Wed, 28 Mar 2012 18:37:46 -0700 (PDT)
Date: Wed, 28 Mar 2012 20:37:46 -0500
Message-ID: <CANwOnkF5Lt98-Drx_i4-A6fpwUz4RhVUK1BR-Nmqn9PC_qomxw@mail.gmail.com>
Subject: ZOOM://IETF.Fact.Check "Improving HTTP starts with speed."
From: Jim Fleming <ietf.fact.check@gmail.com>
To: ietf <ietf@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Mar 2012 01:37:47 -0000

ZOOM://IETF.Fact.Check

http://tools.ietf.org/html/draft-montenegro-httpbis-speed-mobility-00

"Improving HTTP starts with speed."

Improving the Inter.NET starts with speed.

"HTTP Speed+Mobility,"

Locator-ID Separation ?
Locator (60) + ID (68)
60-bit Symmetric Addressing in the IPv4 160-bit Header
68-bit Symmetric Addressing in the IPv16 320-bit Header with Data
AAAA DNS ~ 60+68 ~ VRHL+000.T1.111+PORT12+ASN30+FRAG6 + LAN4+60+CPE4

"The proposal starts from both the Google SPDY protocol and the work
the IETF has done around WebSockets."
If you start with a HAMMER everything may look like a NAIL.

Improving the Inter.NET starts with speed.
A Comprehensive (Modern) Architecture may be better than the old
Hammer and Nails?

Removing TCP may help.
Re-Tooling UDP for Peer-2-Peer may help.
[The 12-bit Port value also rides in the old Identification Field in
the IP Header - are three copies needed?]
2 Protocol Bits frees up 6 bits for addressing
4 TTL Bits encourages less hops and frees up addressing bits
Less.is.More may result in Speed

IPv6 is not built for Speed - Yet people sure are trying to sell it -
Do consumers want it ?

They may prefer a Net.Work as opposed to a Not.Work

ZOOM://IETF.Fact.Check "Improving HTTP starts with speed."

From hannes.tschofenig@gmx.net  Thu Mar 29 00:10:16 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 D7E8021E810E for <ietf@ietfa.amsl.com>; Thu, 29 Mar 2012 00:10:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.512
X-Spam-Level: 
X-Spam-Status: No, score=-102.512 tagged_above=-999 required=5 tests=[AWL=0.087, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WT2cgSX3R0jA for <ietf@ietfa.amsl.com>; Thu, 29 Mar 2012 00:10:12 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by ietfa.amsl.com (Postfix) with SMTP id 123FB21E8102 for <ietf@ietf.org>; Thu, 29 Mar 2012 00:10:11 -0700 (PDT)
Received: (qmail invoked by alias); 29 Mar 2012 07:10:10 -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 Mar 2012 09:10:10 +0200
X-Authenticated: #29516787
X-Provags-ID: V01U2FsdGVkX1+MaAcCWQaMVNx0amhpVzslBJLeYsSFoCp/27v5YA kn+pyVlpRSYwLA
Subject: Re: ZOOM://IETF.Fact.Check "Improving HTTP starts with speed."
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: <CANwOnkF5Lt98-Drx_i4-A6fpwUz4RhVUK1BR-Nmqn9PC_qomxw@mail.gmail.com>
Date: Thu, 29 Mar 2012 09:55:32 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <01F141DB-1887-41A6-9A89-0C0524C3811E@gmx.net>
References: <CANwOnkF5Lt98-Drx_i4-A6fpwUz4RhVUK1BR-Nmqn9PC_qomxw@mail.gmail.com>
To: Jim Fleming <ietf.fact.check@gmail.com>
X-Mailer: Apple Mail (2.1084)
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: Thu, 29 Mar 2012 07:10:17 -0000

Hi Jim,=20

it is tempting to write a short mail with some random thoughts about =
various protocols design aspects. Everyone can do that.=20
That will not get you anywhere.=20

If you want to be understood by others then you have to=20
* write a draft with a consistent story, and
* convince others that it is a good idea.=20

=46rom the way you have posted your messages so far it seems likely that =
you do not able to develop a consistent story.

Sorry to say that.=20

Ciao
Hannes

On Mar 29, 2012, at 4:37 AM, Jim Fleming wrote:

> ZOOM://IETF.Fact.Check
>=20
> http://tools.ietf.org/html/draft-montenegro-httpbis-speed-mobility-00
>=20
> "Improving HTTP starts with speed."
>=20
> Improving the Inter.NET starts with speed.
>=20
> "HTTP Speed+Mobility,"
>=20
> Locator-ID Separation ?
> Locator (60) + ID (68)
> 60-bit Symmetric Addressing in the IPv4 160-bit Header
> 68-bit Symmetric Addressing in the IPv16 320-bit Header with Data
> AAAA DNS ~ 60+68 ~ VRHL+000.T1.111+PORT12+ASN30+FRAG6 + LAN4+60+CPE4
>=20
> "The proposal starts from both the Google SPDY protocol and the work
> the IETF has done around WebSockets."
> If you start with a HAMMER everything may look like a NAIL.
>=20
> Improving the Inter.NET starts with speed.
> A Comprehensive (Modern) Architecture may be better than the old
> Hammer and Nails?
>=20
> Removing TCP may help.
> Re-Tooling UDP for Peer-2-Peer may help.
> [The 12-bit Port value also rides in the old Identification Field in
> the IP Header - are three copies needed?]
> 2 Protocol Bits frees up 6 bits for addressing
> 4 TTL Bits encourages less hops and frees up addressing bits
> Less.is.More may result in Speed
>=20
> IPv6 is not built for Speed - Yet people sure are trying to sell it -
> Do consumers want it ?
>=20
> They may prefer a Net.Work as opposed to a Not.Work
>=20
> ZOOM://IETF.Fact.Check "Improving HTTP starts with speed."


From fred@cisco.com  Thu Mar 29 00:28:28 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 C72D021F85F9 for <ietf@ietfa.amsl.com>; Thu, 29 Mar 2012 00:28:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.539
X-Spam-Level: 
X-Spam-Status: No, score=-110.539 tagged_above=-999 required=5 tests=[AWL=0.060, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ld-K95JbyEBT for <ietf@ietfa.amsl.com>; Thu, 29 Mar 2012 00:28:28 -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 E1A1921F85F4 for <ietf@ietf.org>; Thu, 29 Mar 2012 00:28:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fred@cisco.com; l=218; q=dns/txt; s=iport; t=1333006107; x=1334215707; h=subject:mime-version:from:in-reply-to:date:cc:message-id: references:to:content-transfer-encoding; bh=yJK83Zw7I27Z2egki0ODh3qgGa+d201nFvAwXxbwyes=; b=nLLSAvDH8crJQWKveA7GcOR7bkxIJK58b3/4v+HpMQfSIj8AF3aciEgz DYetU1L35bU5cPhBZzm/JuA9UlwOKco9ZwfblcB8TsDHZW6z5a8YDLaIq y9JWZ9AVoQR/kKRXjrKxzYHfytoRbju4jL0DH50xe50Q8GzdsnGA+9OuF I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAOoNdE+Q/khM/2dsb2JhbABFuQqBB4IJAQEBAwESASc/BQsLRlcGNYdjBZtMnxeQPGMElWGFb4hWgWiCaQ
X-IronPort-AV: E=Sophos;i="4.73,665,1325462400"; d="scan'208";a="69613934"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-2.cisco.com with ESMTP; 29 Mar 2012 07:28:26 +0000
Received: from dhcp-478d.meeting.ietf.org (dhcp-10-55-88-165.cisco.com [10.55.88.165]) by ams-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id q2T7SQmm030051; Thu, 29 Mar 2012 07:28:26 GMT
Received: from [127.0.0.1] by dhcp-478d.meeting.ietf.org (PGP Universal service); Thu, 29 Mar 2012 09:28:26 +0200
X-PGP-Universal: processed; by dhcp-478d.meeting.ietf.org on Thu, 29 Mar 2012 09:28:26 +0200
Subject: Re: ZOOM://IETF.Fact.Check "Improving HTTP starts with speed."
Mime-Version: 1.0 (Apple Message framework v1084)
From: Fred Baker <fred@cisco.com>
In-Reply-To: <01F141DB-1887-41A6-9A89-0C0524C3811E@gmx.net>
Date: Thu, 29 Mar 2012 09:28:14 +0200
Message-Id: <AE229C36-9DD1-4975-8D09-2AD1CBFEFFB8@cisco.com>
References: <CANwOnkF5Lt98-Drx_i4-A6fpwUz4RhVUK1BR-Nmqn9PC_qomxw@mail.gmail.com> <01F141DB-1887-41A6-9A89-0C0524C3811E@gmx.net>
To: Hannes Tschofenig <hannes.tschofenig@gmx.net>
X-Mailer: Apple Mail (2.1084)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Mar 2012 07:28:28 -0000

On Mar 29, 2012, at 8:55 AM, Hannes Tschofenig wrote:

> =46rom the way you have posted your messages so far it seems likely =
that you do not able to develop a consistent story.

Please don't feed the troll.=

From hannes.tschofenig@gmx.net  Thu Mar 29 00:34:47 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 08B6D21F87BF for <ietf@ietfa.amsl.com>; Thu, 29 Mar 2012 00:34:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.523
X-Spam-Level: 
X-Spam-Status: No, score=-102.523 tagged_above=-999 required=5 tests=[AWL=0.076, 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 3mBS6NwOs7+U for <ietf@ietfa.amsl.com>; Thu, 29 Mar 2012 00:34:45 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by ietfa.amsl.com (Postfix) with SMTP id 2CB7C21F87B7 for <ietf@ietf.org>; Thu, 29 Mar 2012 00:34:43 -0700 (PDT)
Received: (qmail invoked by alias); 29 Mar 2012 07:34:42 -0000
Received: from dhcp-172b.meeting.ietf.org (EHLO dhcp-172b.meeting.ietf.org) [130.129.23.43] by mail.gmx.net (mp037) with SMTP; 29 Mar 2012 09:34:42 +0200
X-Authenticated: #29516787
X-Provags-ID: V01U2FsdGVkX1+JSzNGGReJJ0vbw1OHe4f5Eh73ILEDGV1k7l8nIV VLzR5greSAY4Ia
Subject: Re: ZOOM://IETF.Fact.Check "Improving HTTP starts with speed."
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: <AE229C36-9DD1-4975-8D09-2AD1CBFEFFB8@cisco.com>
Date: Thu, 29 Mar 2012 10:34:39 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <50D5D1ED-0636-4183-8BCD-E7A80179A5F2@gmx.net>
References: <CANwOnkF5Lt98-Drx_i4-A6fpwUz4RhVUK1BR-Nmqn9PC_qomxw@mail.gmail.com> <01F141DB-1887-41A6-9A89-0C0524C3811E@gmx.net> <AE229C36-9DD1-4975-8D09-2AD1CBFEFFB8@cisco.com>
To: Fred Baker <fred@cisco.com>
X-Mailer: Apple Mail (2.1084)
X-Y-GMX-Trusted: 0
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Mar 2012 07:34:47 -0000

Ack.=20

On Mar 29, 2012, at 10:28 AM, Fred Baker wrote:

>=20
> On Mar 29, 2012, at 8:55 AM, Hannes Tschofenig wrote:
>=20
>> =46rom the way you have posted your messages so far it seems likely =
that you do not able to develop a consistent story.
>=20
> Please don't feed the troll.


From ietf.fact.check@gmail.com  Thu Mar 29 05:09:52 2012
Return-Path: <ietf.fact.check@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C1D5921F88DC for <ietf@ietfa.amsl.com>; Thu, 29 Mar 2012 05:09:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.074
X-Spam-Level: 
X-Spam-Status: No, score=-0.074 tagged_above=-999 required=5 tests=[AWL=-2.974, BAYES_50=0.001, FS_COSTARICA=2.899, J_CHICKENPOX_32=0.6, RCVD_IN_DNSWL_LOW=-1, SARE_BAYES_6x6=0.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 SPyyjpLUk+Zp for <ietf@ietfa.amsl.com>; Thu, 29 Mar 2012 05:09:51 -0700 (PDT)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id E809E21F8986 for <ietf@ietf.org>; Thu, 29 Mar 2012 05:09:50 -0700 (PDT)
Received: by ggmi1 with SMTP id i1so1512544ggm.31 for <ietf@ietf.org>; Thu, 29 Mar 2012 05:09:50 -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 :content-transfer-encoding; bh=Y8CMQzqtj63p2MMtKu560TeEpYpkziMHVARq6zQeHEk=; b=fQdhp53g55UnirBOAKTJsyZwY8f13/hoO8mnFqo2ohrTW7uu80r5MWTw9MNcSY7ilB SFW5n8lBaWuoc3hFlZ4amjdLUUJcEfc3wKgg4h0Ru/kwHzaW3uCzCQEnn8dXel7vRRNB jEDKXhW66zclYjCMyKY0wTLUHuq7QD0hdDLr0da9DdZXlogyO8m0RlyWz7zmoS/hCMGd PwSuXF7EOCzOi3Ze5+7L26vNSwx60vtBvmXvA5WMUVNdTjShbab4KBojkXBT4CQynHbR /W68koCOrnGJsjR5gSFTtbS5i1/Xp90ltu1Ma/L2zAzpBgL3iQQzJeT6wozpY3HxfT6X KDNA==
MIME-Version: 1.0
Received: by 10.50.207.5 with SMTP id ls5mr1233518igc.51.1333022990163; Thu, 29 Mar 2012 05:09:50 -0700 (PDT)
Received: by 10.50.171.38 with HTTP; Thu, 29 Mar 2012 05:09:50 -0700 (PDT)
Date: Thu, 29 Mar 2012 07:09:50 -0500
Message-ID: <CANwOnkHm5cFVLOf=Yy6MpBvydPMVf2EPu=kFwQmcf-1bxpRa_w@mail.gmail.com>
Subject: IETF.Fact.Check IETF Participants that were also at ICANN Costa Rica Meeting ?
From: Jim Fleming <ietf.fact.check@gmail.com>
To: ietf <ietf@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Mar 2012 12:09:53 -0000

IETF.Fact.Check IETF Participants that were also at ICANN Costa Rica Meetin=
g ?

https://www.ietf.org/registration/ietf83/attendance.py

http://www.registration123.com/ICANN/CR43/

Registration list as of: 03/29/2012
NAME 	AFFILIATION 	COUNTRY
AARON STEWART 	CLOUD VINE 	United States
Aar=F3n Quesada M=E9ndez 	Ice 	Costa Rica
Abdoul-Akim Adjibola 	Benin Telecoms 	BENIN
Abel Brenes 	University of Cosra Rica 	Costa Rica
ABELARDO FONSECA 	LA NACI=D2N 	Costa Rica
Abiodun Olawale 	Reboot& Associates Ltd =09
Abraham Araya 	MMSoluciones Seguridad en Informatica 	Costa Rica
Abraham Djekou 	Atci 	Cote d''Ivoire
Abraham Rodriguez 	Agencia Datsun Nissan 	Costa Rica
Acc Va Cac 	Ac Ac 	CR
Adalberto L=F3pez 	NIC Costa Rica =09
Adam Eisner 	Tucows Inc. =09
Adam Peake 	Glocom 	Japan
Adaobi Okeke 	Nigerian Communications Commission 	Nigeria
Adebiyi Oladipo 	Nigeria Internet Registration Association (NIRA) 	Nigeria
Adebunmi Akinbo 	Young Internet Professionals (YiPS)/(NiRA) dotNG 	Nigeria
Adela Elena Danciu 	Fellowship 	Romania
Adrian Carballo 	South School On Internet Governance 	Argentina
Adrian Garcia 	ISOC Costa Rica Chapter 	Costa Rica
Adrian Kinderis 	ARI Registry Services 	Australia
Adri=E1n P=E9rez 	Ccss 	Costa Rica
Adri=E1n Quesada Rodr=EDguez 		Costa Rica
Adri=E1n Solano 	Acoprot 	Costa Rica
ADRIANA DIAZ 	ICANN 	Costa Rica
Adriana Gonz=E1lez 	Sul=E1 Bats=FA 	Costa Rica
Adriana Rivero 	Lacnic 	Uruguay
Adriana Ulate 		COSTA RICA
AGARWAL SWAPNA 	.INDIA 	India
Ague Alain 	Ministry of agriculture 	B=E9nin
Ahsan Fahmi 		Pakistan
Aimee Deziel 	Mad =09
Akewushola Adisa 	Sanbak Communications Commission 	Nigeria
Akinori Maemura 	JPNIC 	Japan
Alain Artero 	European Broadcasting Union 	France
Alain Berranger 	Centre d'=E9tude et de coop=E9ration internationale 	Canad=
a
Alain Bidron 	France Telecom/ETNO 	France
Alain Patrick Aina 	AFRIMIC 	B=E9nin
Alan Barrett 	AfriNIC / ASO-AC 	South Africa
Alan Fern=E1ndez Mar=EDn 	Universidad de Costa Rica 	Costa Rica
Alan Fern=E1ndez Mar=EDn 	Universidad de Costa Rica 	Costa Rica
Alan Greenberg 	Alac/gnso 	Canada
Alan Gutierrez 	Att 	Bolivia
Alberto Gomez 	Red.es 	Espa=F1a
Alberto Medrano C=E1ceres 	Universidad Nacional 	Costa Rica
Alejandra Castro 	Arias & Mu=F1oz 	Costa Rica
Alejandra Fern=E1ndez Bonilla 	TV Channel 15, University of Costa Rica 	Cos=
ta Rica
Alejandra Reynoso 	Fellowship 	Guatemala
Alejandro Berrocal Valverde 	Viceministrerio Telecomunicaciones MINAET
	Costa Rica
Alejandro Cruz 	Ministro de CIencia y Tecnologia 	Costa Rica
Alejandro Esquivel Rodriguez 	Cisco Systems 	Costa Rica
Alejandro Guzman 	ASO AC - LACNIC - Google 	Colombia
Alejandro Jimenez 	Ice 	Costa Rica
Alejandro Liz 	Nic Do 	Dominican Republic
Alejandro Moscol 	Fellow 	PER=DA
Alejandro Pisanty 	ISOC Mexico 	Mexico
Alejandro Portilla Navarro 	Radio Universidad de Costa Rica 	Costa Rica
Alejandro Rivera 	ICE 	Costa Rica
Alejandro Solis 	Unimer 	Costa Rica
Alex Blowers 	Nominet 	United Kingdom
Alex Mwangangi 	Municipal Council Of Mavoko 	KENYA
Alex Siffrin 	Key-Systems GmbH =09
Alex Stamos 	iSEC Partners 	United States
Alexa Raad 	Architelos 	United States
Alexander Al=ED 		Costa Rica
Alexander Flores 	Universidad de Costa Rica 	Costa Rica
Alexander Mora 	CAMTIC 	Costa Rica
Alexander Mora 	Universidad de Costa Rica 	Costa Rica
Alexander Ot=E1rola 	Omd 	Costa Rica
Alexander Panov 	Ru-Center 	Russia
Alexander Rojas 	Coral Technologies 	Costa Rica
Alexander Salas Arce 	Oficina Digital - CentroAmerica Hosting 	Costa Rica
Alexander Schubert 	dotgay LLC 	USA
Alexander Schwertner 	EPAG Domainservices GmbH 	Germany
Alexander Seger 	Council of Europe 	France
Alexis Coto 	Colegio Agropecuario 	Costa Rica
Alexis Sandoval 	Ice 	Costa Rica
Alfredo Lopez Hernandez 	Enredo 	Colombia
Alfredo Pinochet 	LatinTLD, Inc. 	Chile
Ali Asghar 	Ministry of I.C.T information technology organizat 	Indonesia
Alice Huang 	Net-Chinese Co., Ltd. 	Taiwan
Alice Jansen 	Icann 	Belgium
Alice Munyua 	Ministry of Information and Communications 	Kenya
Alicia Avenda=F1o 	Digital Government, Costa Rica 	Costa Rica
Alicia Paz 	Rds-Hn 	HONDURAS
Alina Syunkova 	Icann 	USA
Aline Valerie Assako 	NATIONAL AGENCY FOR ICT's 	CAMEROON
Alissa Sekulic 	TANGO Registry Services =AE 	Germany
Allan Berm=FAdez Carvajal 	Ice 	Costa Rica
Allan Campos Gallo 	Universidad de Costa Rica 	Costa Rica
Allan Perez 	colegio de abogados CR 	Costa Rica
Alvaro Araya 	Lightmaster Dev 	Costa Rica
Alvaro Hernandez 	Sistemas Inform=E1ticos de Centroam=E9rica =09
Amanda Cimaglia 	McCormick ICT 	USA
Amanda Fessenden 	Internet Pro APC 	United States
Am=E9d=E9e Dossou 	Ministere de la Communication et des TIC 	B=E9nin
Aminata Sy 	Fellowship 	Senegal
Amitabh Singhal 	Public Interest Registry 	India
Amy Repp 	CentralNic 	United Kingdom
Ana Arias 	Racsa 	Costa Rica
Ana Castro 	NIC Costa Rica =09
Ana Herrera 	Ucr 	COSTA RICA
Ana Neves 	Foundation for Science and Technology 	Portugal
Ana Ramos 	Internet Society of Puerto Rico 	Puerto Rico
ANA SANCHEZ 	ISOC ECUADOR 	Ecuador
Ana V=EDlchez 	Racsa 	Costa Rica
Ana Laura Echemendia 	Gobierno Digital 	Costa Rica
Ana Paula V=E1zquez Cisneros 	Sedo 	Germany
ANABEL RODRIGUEZ 	AGEIA DENSI ARGENTINA 	Argentina
Anahi Fajardo Torres 	Facultad de Derecho, Universidad de Costa Rica 	Costa=
 Rica
Anand Vora 	Public Interest Registry =09
Anders Gammelmark 	Larsen Data ApS 	Denmark
Anders Giversen 	TELE Greenland A/S 	Greenland
Anders Rafting 	Swedish Post and Telecom Authority 	Sweden
Andre Griffith 	Barbados ICT Professionals Association 	Barbados
Andre Hernandez 	Emd.co.cr 	Costa Rica
ANDREA BECCALLI 	(UNESCO) 	Italy
Andrea Glorioso 	European Commission 	Belgium
Andrea Rivera Alvarez 	Lanotec 	Costa Rica
Andrea Solano Ulloa 	Red de las Am=E8ricas 	costa rica
Andres Alfaro Quiros 	LQ Ingenieria 	Costa Rica
Andres Gonzalez 	Hewlett Packard 	Costa Rica
Andres Gonzalez Tenorio 	Itech Soluciones 	Costa Rica
Andres Guadamuz 	Innova Technology 	Costa Rica
Andres Morillo 	Metro Wireless 	Costa Rica
Andres Piazza 	Lacnic =09
Andres Rodriguez 	Promociones mercadeo y descuentos 	Costa Rica
Andres Ulate Jara 		Costa Rica
Andr=E9s Angulo Ram=EDrez 	Ice 	Costa Rica
Andr=E9s Cabezas 		Costa Rica
Andr=E9s Castillo G=F3mez 	Alojamiento Tico 	Costa Rica
Andr=E9s Garita 	Personal 	Costa Rica
Andrew Abrams 	Google 	United States
Andrew Barrett 	EnCirca 	US
Andrew Haije 	Ripe Ncc 	Netherlands
Andrew Mack 	AMGlobal Consulting 	USA
Andrew Merriam 	ICANNWiki 	USA
Andrew Robertson 	Edelman =09
Andrew Sullivan 	Dyn Inc 	Canada
Andrew Sullivan 	Dyn Inc 	Canada
Andrey Barrantes 	Ice 	Costa Rica
Andrey Kolesnikov 	Coordination center ccTLD .RU 	Russian Federation
Andrey Vorobyev 	Ru-Center 	Russian Federation
Andrii Paziuk 	Institute of International Relations Ukraine 	Ukraine
Andy Coombs 	International Anticounterfeiting Coalition 	United States
Angela Orozco 	Cac Porter Novelli 	COSTA RICA
Angie Graves 	Community DNS 	United States of America
Angie Morales Villalobos 	Universidad de Costa Rica 	Costa Rica
ANGIE OBANDO 	OIJ 	Costa Rica
Anjali Hansen 	Council of Better Business Bureaus 	USA
Annalisa Roger 	DotGreen 	United States
ANNE AIKMAN-SCALESE 	LEWIS AND ROCA 	United States
Anne LaPlante 	Gvsd 	USA
Anne-Rachel Inne 	Icann 	Niger
Annebeth Lange 	Uninett 	Norway
Anthony Arce 	Grupo ICE 	Costa Rica
ANTHONY BELTRAN 	101 DOMAIN 	United States
Anthony Beltran 	101Domain, Inc. 	United States
Anthony Harris 	Cabase =09
Anthony Lee 	Twnic 	Taiwan
Antonio Godinho 	Ciuem 	Mozambique
Antonio Medina 	Asociacion Colombiana de Usuarios de Internet 	Colombia
ANTONIO OSORIO 	DELL 	Costa Rica
Antonio Silva 	gwNIC official refistry SARL 	Guinea Bissau
Antonio Valverde-Mu=F1oz 	University of Costa Rica 	Costa Rica
Anwana Ima Obong 	International Foundation for African Children 	Nigeria
Arantxa Martinez 	Red.es 	Spain
Argery Campos 	Ice 	Costa Rica
Ariel Zu=F1iga Rojas 	=09
Armando Aguilar 	Ministerio de Ciencia y Tecnologia 	Costa Rica
Armando Jipsion 	NIC-Panama / PANNet / UTP =09
Arnold Yamukandu 	Centre De Promotion Et De Vulgarisation De L'Infor 	RDCon=
go
Arnoldo Muller-Molina 	simMachines 	Costa Rica
Art Reilly 	Public Interest Registry 	USA
Arturo Rojas Aubert 	ADN Solutions 	Costa Rica
Arturo Rojas Kruse 	Emagine de Centroamerica 	Costa Rica
Arturo Servin 	Lacnic 	Uruguay
Ashley Henning 	Web.com 	United States
Attila Ozgit 	nic.TR 	Turkey
Aura Bonilla 	AST Media 	Costa Rica
Austin Gonz=E1lez 	Ice 	Costa Rica
AVRI DORIA 	N/A 	United States
Axel Pawlik 	Ripe Ncc / Nro 	Netherlands
Axia Harrison 	ARI Registry Services 	Australia
AYESHA NASSAN 	INTERNATINAL CHAMBER OF COMMERCE 	France
Ayotunde Akande 	Bluemiles Global Concept Ltd. 	Nigeria
Azeez Jubril 	Jaaz Integrated Services Ltd 	Nigeria
Aziz Hilali 	Isoc Morocco 	MOROCCO
B Nath 	TEC, India 	India
Ba Oumar 	Agetic =09
Barbara Cabezas 	NameAction Domains Latinamerica =09
Barbara Clay 	Icann 	UNITED STATES
Bart Lieben 	Crowell & Moring 	Belgium
Basamba Drammeh 	Association of ICT And Mobile Phone Technicians 	Gambia
Bashir Ghellali 		Costa Rica
Baudouin Schombe 	Centre Africain D'Echange Culturel 	DEMOCRATIC
REPUBLIC OF CONGO
Bavafa Syamak 	Domaine.fr 	France
Beau Brendler 	chairman,naraco 	United States
Becky Burr 	Wilmer Hale 	United States
Ben Anderson 	Group NBT 	Denmark
Ben Crawford 	CentralNic 	UAE
BEN ROBERT MILAM 	MILAM LAW FIRM 	United States
Bence Kozma 	Ultimate Digital Technologies, LLC ; DOTTODAY, LLC =09
Benedetta Rossi 	Business Constituency - ICANN 	France
Benedict Addis 	SOCA UK 	United Kingdom
Benjamin Zu=F1iga 	Seventh Floor C&D 	Costa Rica
Bernal Cordero 	Ice 	Costa Rica
Bernal Rojas Chavarr=EDa 	Ice 	Costa Rica
Bernard Turcotte 	Icann 	Canada
Bernardo Rojas Alfaro 	Ice 	Costa Rica
Berry Cobb 	Icann 	United States
Bert Achten 	gwNIC Global Web Service Ltd. 	Germany
Bert Wijnen 	Ripe Ncc 	Netherlands
Bertrand de La Chapelle 	Icann 	France
Bertrand Louveau 	Afnic 	France
Betsy Paque 	=09
BETZABEN ARIAS 	ICANN 	Costa Rica
Bill Graham 	Icann 	Canada
BILL SMITH 	PAYPAL 	United States
Bill Tomon 	Fellowship 	Papua New Guinea
Bill Woodcock 	Packet Clearing House 	US
BILLY YARBROUGH 	DOTREGISTRY,ORG 	United States
BLAINE RIGLER 	IRON MOUNTAIN 	United States
BLANCA CASTRO 	ICE 	Costa Rica
Blanca Diaz Jipsion 	NIC-Panama / PANNet / UTP 	Panama
Bo Martinsson 	Swedish Post and Telecom Authority 	Sweden
Bob Mountain 	NameMedia, Inc. 	United States
Bob Wiegand 	Web.com =09
Bobe Poka 	Otrt =09
Bolivar Molina Quir=F3s 	Ice 	Costa Rica
Bolivar Zu=F1iga 	Llevatetuweb.com =09
Brad Lemire 	Sedo 	usa
Brad White 	Icann 	USA
Brandon Soto Oviedo 		Costa Rica
Brenda Nyanamba 	KeNIC 	Kenya
Brendan Doyle 	CTIC Foundation 	Spain
BRETT FASSET 	.JOBS 	United States
Brian Beckham 	WIPO 	Switzerland
Brian Cute 	Public Interest Registry 	USA
Brian Unruh 	Endurance International Group =09
Brian Jay Winterfeldt 	Steptoe + Johnson LLP 	United States
Bruce Tonkin 	Icann 	Australia

From prvs=1435221dd5=jordi.palet@consulintel.es  Thu Mar 29 05:27:04 2012
Return-Path: <prvs=1435221dd5=jordi.palet@consulintel.es>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4CA7621F8A98 for <ietf@ietfa.amsl.com>; Thu, 29 Mar 2012 05:27:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.266
X-Spam-Level: 
X-Spam-Status: No, score=-104.266 tagged_above=-999 required=5 tests=[AWL=-1.166, BAYES_00=-2.599, FS_COSTARICA=2.899, J_CHICKENPOX_32=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 R-BLIZyF5+10 for <ietf@ietfa.amsl.com>; Thu, 29 Mar 2012 05:27:02 -0700 (PDT)
Received: from consulintel.es (mail.consulintel.es [213.172.48.142]) by ietfa.amsl.com (Postfix) with ESMTP id 0C56021F86BB for <ietf@ietf.org>; Thu, 29 Mar 2012 05:27:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1333023847; x=1333628647; q=dns/txt; h=DomainKey-Signature: Received:User-Agent:Date:Subject:From:To:Message-ID:Thread-Topic: In-Reply-To:Mime-version:Content-type:Content-transfer-encoding: Reply-To; bh=2SNNsyP+fI7CyW7Q3lWffsJZzI4vquev3eJYCZj0eIo=; b=MwP luZlbsKT+tKIMThTVh0nkdrKbUv6FzNS3wei4y9sE8KI3wzFuC2hOIKzZ/EZthQw F2/Wnyk23uhqwzuHfpoj7oAUF02xra0I7886pssJQ1OA0y0eUklqwcMq3Is78WEf 4W2PzvnPr7cXC0shUdPDvK70L9cRlaepJP/6u/vo=
DomainKey-Signature: a=rsa-sha1; s=MDaemon; d=consulintel.es; c=simple; q=dns; h=from:message-id; b=J9IE2c6e2HNfaD2DP0u+yj6OaP/eh4N2+fg0eMv6gNGjBlY9YcIPNCrI5G3l htzlpgWIFoZsDNgTPskk2ow1GpcrjAOuwZgTaXYmPKwL/f8KlQbaj2Pdh jLJyPMNByWWAjcy4KUnT4Gpe3YW2U7WwpLtVB8M1mio/RFYly9V1Sw=;
X-MDAV-Processed: consulintel.es, Thu, 29 Mar 2012 14:24:07 +0200
Received: from [130.129.80.175] by consulintel.es (MDaemon PRO v11.0.3) with ESMTP id md50004135011.msg for <ietf@ietf.org>; Thu, 29 Mar 2012 14:24:06 +0200
X-Spam-Processed: consulintel.es, Thu, 29 Mar 2012 14:24:06 +0200 (not processed: message from trusted or authenticated source)
X-MDPtrLookup-Result: pass dns.ptr=dhcp-50af.meeting.ietf.org (ip=130.129.80.175) (consulintel.es)
X-Authenticated-Sender: jordi.palet@consulintel.es
X-HashCash: 1:20:120329:md50004135011::PSxf0N+uYA/MRTw6:0000010G
X-MDRemoteIP: 130.129.80.175
X-Return-Path: prvs=1435221dd5=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ietf@ietf.org
User-Agent: Microsoft-MacOutlook/14.14.0.111121
Date: Thu, 29 Mar 2012 14:26:51 +0200
Subject: Re: IETF.Fact.Check IETF Participants that were also at ICANN Costa Rica Meeting ?
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: <ietf.fact.check@gmail.com>, ietf <ietf@ietf.org>
Message-ID: <CB9A2149.6C8C0%jordi.palet@consulintel.es>
Thread-Topic: IETF.Fact.Check IETF Participants that were also at ICANN Costa Rica Meeting ?
In-Reply-To: <CANwOnkHm5cFVLOf=Yy6MpBvydPMVf2EPu=kFwQmcf-1bxpRa_w@mail.gmail.com>
Mime-version: 1.0
Content-type: text/plain; charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: jordi.palet@consulintel.es
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Mar 2012 12:27:04 -0000

Hi Jim,

This is my last message to you as IETF Sergeant-at-arms.

I've asked the Secretariat avoid your posts going thru the email exploder.

Regards,
Jordi






-----Mensaje original-----
De: Jim Fleming <ietf.fact.check@gmail.com>
Responder a: <ietf.fact.check@gmail.com>
Fecha: Thu, 29 Mar 2012 07:09:50 -0500
Para: ietf <ietf@ietf.org>
Asunto: IETF.Fact.Check IETF Participants that were also at ICANN Costa
Rica Meeting ?

>IETF.Fact.Check IETF Participants that were also at ICANN Costa Rica
>Meeting ?
>
>https://www.ietf.org/registration/ietf83/attendance.py
>
>http://www.registration123.com/ICANN/CR43/
>
>Registration list as of: 03/29/2012
>NAME 	AFFILIATION 	COUNTRY
>AARON STEWART 	CLOUD VINE 	United States
>Aar=F3n Quesada M=E9ndez 	Ice 	Costa Rica
>Abdoul-Akim Adjibola 	Benin Telecoms 	BENIN
>Abel Brenes 	University of Cosra Rica 	Costa Rica
>ABELARDO FONSECA 	LA NACI=D2N 	Costa Rica
>Abiodun Olawale 	Reboot& Associates Ltd =09
>Abraham Araya 	MMSoluciones Seguridad en Informatica 	Costa Rica
>Abraham Djekou 	Atci 	Cote d''Ivoire
>Abraham Rodriguez 	Agencia Datsun Nissan 	Costa Rica
>Acc Va Cac 	Ac Ac 	CR
>Adalberto L=F3pez 	NIC Costa Rica =09
>Adam Eisner 	Tucows Inc. =09
>Adam Peake 	Glocom 	Japan
>Adaobi Okeke 	Nigerian Communications Commission 	Nigeria
>Adebiyi Oladipo 	Nigeria Internet Registration Association (NIRA) 	Nigeria
>Adebunmi Akinbo 	Young Internet Professionals (YiPS)/(NiRA) dotNG 	Nigeria
>Adela Elena Danciu 	Fellowship 	Romania
>Adrian Carballo 	South School On Internet Governance 	Argentina
>Adrian Garcia 	ISOC Costa Rica Chapter 	Costa Rica
>Adrian Kinderis 	ARI Registry Services 	Australia
>Adri=E1n P=E9rez 	Ccss 	Costa Rica
>Adri=E1n Quesada Rodr=EDguez 		Costa Rica
>Adri=E1n Solano 	Acoprot 	Costa Rica
>ADRIANA DIAZ 	ICANN 	Costa Rica
>Adriana Gonz=E1lez 	Sul=E1 Bats=FA 	Costa Rica
>Adriana Rivero 	Lacnic 	Uruguay
>Adriana Ulate 		COSTA RICA
>AGARWAL SWAPNA 	.INDIA 	India
>Ague Alain 	Ministry of agriculture 	B=E9nin
>Ahsan Fahmi 		Pakistan
>Aimee Deziel 	Mad =09
>Akewushola Adisa 	Sanbak Communications Commission 	Nigeria
>Akinori Maemura 	JPNIC 	Japan
>Alain Artero 	European Broadcasting Union 	France
>Alain Berranger 	Centre d'=E9tude et de coop=E9ration internationale 	Cana=
da
>Alain Bidron 	France Telecom/ETNO 	France
>Alain Patrick Aina 	AFRIMIC 	B=E9nin
>Alan Barrett 	AfriNIC / ASO-AC 	South Africa
>Alan Fern=E1ndez Mar=EDn 	Universidad de Costa Rica 	Costa Rica
>Alan Fern=E1ndez Mar=EDn 	Universidad de Costa Rica 	Costa Rica
>Alan Greenberg 	Alac/gnso 	Canada
>Alan Gutierrez 	Att 	Bolivia
>Alberto Gomez 	Red.es 	Espa=F1a
>Alberto Medrano C=E1ceres 	Universidad Nacional 	Costa Rica
>Alejandra Castro 	Arias & Mu=F1oz 	Costa Rica
>Alejandra Fern=E1ndez Bonilla 	TV Channel 15, University of Costa Rica
>	Costa Rica
>Alejandra Reynoso 	Fellowship 	Guatemala
>Alejandro Berrocal Valverde 	Viceministrerio Telecomunicaciones MINAET
>	Costa Rica
>Alejandro Cruz 	Ministro de CIencia y Tecnologia 	Costa Rica
>Alejandro Esquivel Rodriguez 	Cisco Systems 	Costa Rica
>Alejandro Guzman 	ASO AC - LACNIC - Google 	Colombia
>Alejandro Jimenez 	Ice 	Costa Rica
>Alejandro Liz 	Nic Do 	Dominican Republic
>Alejandro Moscol 	Fellow 	PER=DA
>Alejandro Pisanty 	ISOC Mexico 	Mexico
>Alejandro Portilla Navarro 	Radio Universidad de Costa Rica 	Costa Rica
>Alejandro Rivera 	ICE 	Costa Rica
>Alejandro Solis 	Unimer 	Costa Rica
>Alex Blowers 	Nominet 	United Kingdom
>Alex Mwangangi 	Municipal Council Of Mavoko 	KENYA
>Alex Siffrin 	Key-Systems GmbH =09
>Alex Stamos 	iSEC Partners 	United States
>Alexa Raad 	Architelos 	United States
>Alexander Al=ED 		Costa Rica
>Alexander Flores 	Universidad de Costa Rica 	Costa Rica
>Alexander Mora 	CAMTIC 	Costa Rica
>Alexander Mora 	Universidad de Costa Rica 	Costa Rica
>Alexander Ot=E1rola 	Omd 	Costa Rica
>Alexander Panov 	Ru-Center 	Russia
>Alexander Rojas 	Coral Technologies 	Costa Rica
>Alexander Salas Arce 	Oficina Digital - CentroAmerica Hosting 	Costa Rica
>Alexander Schubert 	dotgay LLC 	USA
>Alexander Schwertner 	EPAG Domainservices GmbH 	Germany
>Alexander Seger 	Council of Europe 	France
>Alexis Coto 	Colegio Agropecuario 	Costa Rica
>Alexis Sandoval 	Ice 	Costa Rica
>Alfredo Lopez Hernandez 	Enredo 	Colombia
>Alfredo Pinochet 	LatinTLD, Inc. 	Chile
>Ali Asghar 	Ministry of I.C.T information technology organizat 	Indonesia
>Alice Huang 	Net-Chinese Co., Ltd. 	Taiwan
>Alice Jansen 	Icann 	Belgium
>Alice Munyua 	Ministry of Information and Communications 	Kenya
>Alicia Avenda=F1o 	Digital Government, Costa Rica 	Costa Rica
>Alicia Paz 	Rds-Hn 	HONDURAS
>Alina Syunkova 	Icann 	USA
>Aline Valerie Assako 	NATIONAL AGENCY FOR ICT's 	CAMEROON
>Alissa Sekulic 	TANGO Registry Services =AE 	Germany
>Allan Berm=FAdez Carvajal 	Ice 	Costa Rica
>Allan Campos Gallo 	Universidad de Costa Rica 	Costa Rica
>Allan Perez 	colegio de abogados CR 	Costa Rica
>Alvaro Araya 	Lightmaster Dev 	Costa Rica
>Alvaro Hernandez 	Sistemas Inform=E1ticos de Centroam=E9rica =09
>Amanda Cimaglia 	McCormick ICT 	USA
>Amanda Fessenden 	Internet Pro APC 	United States
>Am=E9d=E9e Dossou 	Ministere de la Communication et des TIC 	B=E9nin
>Aminata Sy 	Fellowship 	Senegal
>Amitabh Singhal 	Public Interest Registry 	India
>Amy Repp 	CentralNic 	United Kingdom
>Ana Arias 	Racsa 	Costa Rica
>Ana Castro 	NIC Costa Rica =09
>Ana Herrera 	Ucr 	COSTA RICA
>Ana Neves 	Foundation for Science and Technology 	Portugal
>Ana Ramos 	Internet Society of Puerto Rico 	Puerto Rico
>ANA SANCHEZ 	ISOC ECUADOR 	Ecuador
>Ana V=EDlchez 	Racsa 	Costa Rica
>Ana Laura Echemendia 	Gobierno Digital 	Costa Rica
>Ana Paula V=E1zquez Cisneros 	Sedo 	Germany
>ANABEL RODRIGUEZ 	AGEIA DENSI ARGENTINA 	Argentina
>Anahi Fajardo Torres 	Facultad de Derecho, Universidad de Costa Rica
>	Costa Rica
>Anand Vora 	Public Interest Registry =09
>Anders Gammelmark 	Larsen Data ApS 	Denmark
>Anders Giversen 	TELE Greenland A/S 	Greenland
>Anders Rafting 	Swedish Post and Telecom Authority 	Sweden
>Andre Griffith 	Barbados ICT Professionals Association 	Barbados
>Andre Hernandez 	Emd.co.cr 	Costa Rica
>ANDREA BECCALLI 	(UNESCO) 	Italy
>Andrea Glorioso 	European Commission 	Belgium
>Andrea Rivera Alvarez 	Lanotec 	Costa Rica
>Andrea Solano Ulloa 	Red de las Am=E8ricas 	costa rica
>Andres Alfaro Quiros 	LQ Ingenieria 	Costa Rica
>Andres Gonzalez 	Hewlett Packard 	Costa Rica
>Andres Gonzalez Tenorio 	Itech Soluciones 	Costa Rica
>Andres Guadamuz 	Innova Technology 	Costa Rica
>Andres Morillo 	Metro Wireless 	Costa Rica
>Andres Piazza 	Lacnic =09
>Andres Rodriguez 	Promociones mercadeo y descuentos 	Costa Rica
>Andres Ulate Jara 		Costa Rica
>Andr=E9s Angulo Ram=EDrez 	Ice 	Costa Rica
>Andr=E9s Cabezas 		Costa Rica
>Andr=E9s Castillo G=F3mez 	Alojamiento Tico 	Costa Rica
>Andr=E9s Garita 	Personal 	Costa Rica
>Andrew Abrams 	Google 	United States
>Andrew Barrett 	EnCirca 	US
>Andrew Haije 	Ripe Ncc 	Netherlands
>Andrew Mack 	AMGlobal Consulting 	USA
>Andrew Merriam 	ICANNWiki 	USA
>Andrew Robertson 	Edelman =09
>Andrew Sullivan 	Dyn Inc 	Canada
>Andrew Sullivan 	Dyn Inc 	Canada
>Andrey Barrantes 	Ice 	Costa Rica
>Andrey Kolesnikov 	Coordination center ccTLD .RU 	Russian Federation
>Andrey Vorobyev 	Ru-Center 	Russian Federation
>Andrii Paziuk 	Institute of International Relations Ukraine 	Ukraine
>Andy Coombs 	International Anticounterfeiting Coalition 	United States
>Angela Orozco 	Cac Porter Novelli 	COSTA RICA
>Angie Graves 	Community DNS 	United States of America
>Angie Morales Villalobos 	Universidad de Costa Rica 	Costa Rica
>ANGIE OBANDO 	OIJ 	Costa Rica
>Anjali Hansen 	Council of Better Business Bureaus 	USA
>Annalisa Roger 	DotGreen 	United States
>ANNE AIKMAN-SCALESE 	LEWIS AND ROCA 	United States
>Anne LaPlante 	Gvsd 	USA
>Anne-Rachel Inne 	Icann 	Niger
>Annebeth Lange 	Uninett 	Norway
>Anthony Arce 	Grupo ICE 	Costa Rica
>ANTHONY BELTRAN 	101 DOMAIN 	United States
>Anthony Beltran 	101Domain, Inc. 	United States
>Anthony Harris 	Cabase =09
>Anthony Lee 	Twnic 	Taiwan
>Antonio Godinho 	Ciuem 	Mozambique
>Antonio Medina 	Asociacion Colombiana de Usuarios de Internet 	Colombia
>ANTONIO OSORIO 	DELL 	Costa Rica
>Antonio Silva 	gwNIC official refistry SARL 	Guinea Bissau
>Antonio Valverde-Mu=F1oz 	University of Costa Rica 	Costa Rica
>Anwana Ima Obong 	International Foundation for African Children 	Nigeria
>Arantxa Martinez 	Red.es 	Spain
>Argery Campos 	Ice 	Costa Rica
>Ariel Zu=F1iga Rojas 	=09
>Armando Aguilar 	Ministerio de Ciencia y Tecnologia 	Costa Rica
>Armando Jipsion 	NIC-Panama / PANNet / UTP =09
>Arnold Yamukandu 	Centre De Promotion Et De Vulgarisation De L'Infor
>	RDCongo
>Arnoldo Muller-Molina 	simMachines 	Costa Rica
>Art Reilly 	Public Interest Registry 	USA
>Arturo Rojas Aubert 	ADN Solutions 	Costa Rica
>Arturo Rojas Kruse 	Emagine de Centroamerica 	Costa Rica
>Arturo Servin 	Lacnic 	Uruguay
>Ashley Henning 	Web.com 	United States
>Attila Ozgit 	nic.TR 	Turkey
>Aura Bonilla 	AST Media 	Costa Rica
>Austin Gonz=E1lez 	Ice 	Costa Rica
>AVRI DORIA 	N/A 	United States
>Axel Pawlik 	Ripe Ncc / Nro 	Netherlands
>Axia Harrison 	ARI Registry Services 	Australia
>AYESHA NASSAN 	INTERNATINAL CHAMBER OF COMMERCE 	France
>Ayotunde Akande 	Bluemiles Global Concept Ltd. 	Nigeria
>Azeez Jubril 	Jaaz Integrated Services Ltd 	Nigeria
>Aziz Hilali 	Isoc Morocco 	MOROCCO
>B Nath 	TEC, India 	India
>Ba Oumar 	Agetic =09
>Barbara Cabezas 	NameAction Domains Latinamerica =09
>Barbara Clay 	Icann 	UNITED STATES
>Bart Lieben 	Crowell & Moring 	Belgium
>Basamba Drammeh 	Association of ICT And Mobile Phone Technicians 	Gambia
>Bashir Ghellali 		Costa Rica
>Baudouin Schombe 	Centre Africain D'Echange Culturel 	DEMOCRATIC
>REPUBLIC OF CONGO
>Bavafa Syamak 	Domaine.fr 	France
>Beau Brendler 	chairman,naraco 	United States
>Becky Burr 	Wilmer Hale 	United States
>Ben Anderson 	Group NBT 	Denmark
>Ben Crawford 	CentralNic 	UAE
>BEN ROBERT MILAM 	MILAM LAW FIRM 	United States
>Bence Kozma 	Ultimate Digital Technologies, LLC ; DOTTODAY, LLC =09
>Benedetta Rossi 	Business Constituency - ICANN 	France
>Benedict Addis 	SOCA UK 	United Kingdom
>Benjamin Zu=F1iga 	Seventh Floor C&D 	Costa Rica
>Bernal Cordero 	Ice 	Costa Rica
>Bernal Rojas Chavarr=EDa 	Ice 	Costa Rica
>Bernard Turcotte 	Icann 	Canada
>Bernardo Rojas Alfaro 	Ice 	Costa Rica
>Berry Cobb 	Icann 	United States
>Bert Achten 	gwNIC Global Web Service Ltd. 	Germany
>Bert Wijnen 	Ripe Ncc 	Netherlands
>Bertrand de La Chapelle 	Icann 	France
>Bertrand Louveau 	Afnic 	France
>Betsy Paque 	=09
>BETZABEN ARIAS 	ICANN 	Costa Rica
>Bill Graham 	Icann 	Canada
>BILL SMITH 	PAYPAL 	United States
>Bill Tomon 	Fellowship 	Papua New Guinea
>Bill Woodcock 	Packet Clearing House 	US
>BILLY YARBROUGH 	DOTREGISTRY,ORG 	United States
>BLAINE RIGLER 	IRON MOUNTAIN 	United States
>BLANCA CASTRO 	ICE 	Costa Rica
>Blanca Diaz Jipsion 	NIC-Panama / PANNet / UTP 	Panama
>Bo Martinsson 	Swedish Post and Telecom Authority 	Sweden
>Bob Mountain 	NameMedia, Inc. 	United States
>Bob Wiegand 	Web.com =09
>Bobe Poka 	Otrt =09
>Bolivar Molina Quir=F3s 	Ice 	Costa Rica
>Bolivar Zu=F1iga 	Llevatetuweb.com =09
>Brad Lemire 	Sedo 	usa
>Brad White 	Icann 	USA
>Brandon Soto Oviedo 		Costa Rica
>Brenda Nyanamba 	KeNIC 	Kenya
>Brendan Doyle 	CTIC Foundation 	Spain
>BRETT FASSET 	.JOBS 	United States
>Brian Beckham 	WIPO 	Switzerland
>Brian Cute 	Public Interest Registry 	USA
>Brian Unruh 	Endurance International Group =09
>Brian Jay Winterfeldt 	Steptoe + Johnson LLP 	United States
>Bruce Tonkin 	Icann 	Australia



**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.consulintel.es
The IPv6 Company

This electronic message contains information which may be privileged or con=
fidential. The information is intended to be for the use of the individual(=
s) named above. If you are not the intended recipient be aware that any dis=
closure, copying, distribution or use of the contents of this information, =
including attached files, is prohibited.




From christopher.morrow@gmail.com  Thu Mar 29 09:11:35 2012
Return-Path: <christopher.morrow@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BE4EE21E8231; Thu, 29 Mar 2012 09:11:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.561
X-Spam-Level: 
X-Spam-Status: No, score=-103.561 tagged_above=-999 required=5 tests=[AWL=0.038, 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 0QH+awABvbAe; Thu, 29 Mar 2012 09:11:35 -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 E07BA21E8229; Thu, 29 Mar 2012 09:11:34 -0700 (PDT)
Received: by obbta17 with SMTP id ta17so841090obb.31 for <multiple recipients>; Thu, 29 Mar 2012 09:11:34 -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 :content-transfer-encoding; bh=2OsZJbLOAB3ydpvd7XWlvI+yciJvWhDtFjmz42SEc0A=; b=sVpy8Ldr8ne82exDSb633j22acWpz5KUx2via6SAZpnoIJ0KwUGLdgy25qbH5Zoc44 9qkZAQ4X3VJVYOSU05hNLu7IdxHwaZGOtEQ9ovX0BL+VWthk2Js/7DB/X7mLKDjykEei iH1SyRdF7lD9dIFF/u7og+h3Ec61FXRvGSIrDhgCrKH4bA/ykIw0+IW28OMG7TDEyQAP OZYAp8UgRER0xSlfwaVs5dOR60SJJJqFrfPX0Him4dMlAgeko7KBwdYqf+GSd/g4md4d 10ZGnS9fyfzPBF9QEFraZnPFR3fslXGQpeL4bOee5evICroBgAQuPiMwIDYi21ho15hg gSzA==
MIME-Version: 1.0
Received: by 10.182.85.39 with SMTP id e7mr43807279obz.51.1333037494489; Thu, 29 Mar 2012 09:11:34 -0700 (PDT)
Sender: christopher.morrow@gmail.com
Received: by 10.182.80.137 with HTTP; Thu, 29 Mar 2012 09:11:34 -0700 (PDT)
In-Reply-To: <20120329141002.22903.96428.idtracker@ietfa.amsl.com>
References: <20120329141002.22903.96428.idtracker@ietfa.amsl.com>
Date: Thu, 29 Mar 2012 12:11:34 -0400
X-Google-Sender-Auth: u1rScoPALWGBi6yogXzIAqA4EIE
Message-ID: <CAL9jLaZYt0kEWm4rHGZ4JMXraDjRsCP8t7DLKn_bRMZOTy9GTg@mail.gmail.com>
Subject: Re: [conex] Last Call: <draft-ietf-conex-concepts-uses-04.txt> (ConEx Concepts and Use Cases) to Informational RFC
From: Christopher Morrow <morrowc.lists@gmail.com>
To: ietf@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: IETF-Announce <ietf-announce@ietf.org>, conex@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Mar 2012 16:11:35 -0000

On Thu, Mar 29, 2012 at 10:10 AM, The IESG <iesg-secretary@ietf.org> wrote:
>
> The IESG has received a request from the Congestion Exposure WG (conex)
> to consider the following document:
> - 'ConEx Concepts and Use Cases'
> =A0<draft-ietf-conex-concepts-uses-04.txt> as an 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-04-12. 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
>
>
> =A0 This document provides the entry point to the set of documentation
> =A0 about the Congestion Exposure (ConEx) protocol. =A0It explains the
> =A0 motivation for including a ConEx marking at the IP layer: to expose
> =A0 information about congestion to network nodes. =A0Although such
> =A0 information may have a number of uses, this document focuses on how
> =A0 the information communicated by the ConEx marking can serve as the
> =A0 basis for significantly more efficient and effective traffic
> =A0 management than what exists on the Internet today.
>
>
>
>
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-conex-concepts-uses/
>
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-conex-concepts-uses/ballot/
>
>
> No IPR declarations have been submitted directly on this I-D.

Didn't Mr Briscoe just email that there was a BT IPR claim against
this ID, related to re-ECN work he did/does for BT?

> _______________________________________________
> conex mailing list
> conex@ietf.org
> https://www.ietf.org/mailman/listinfo/conex

From christopher.morrow@gmail.com  Thu Mar 29 09:12:42 2012
Return-Path: <christopher.morrow@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3625721F8735; Thu, 29 Mar 2012 09:12:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.562
X-Spam-Level: 
X-Spam-Status: No, score=-103.562 tagged_above=-999 required=5 tests=[AWL=0.037, 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 dGVi6oEWu3V1; Thu, 29 Mar 2012 09:12:41 -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 1868621F8718; Thu, 29 Mar 2012 09:12:41 -0700 (PDT)
Received: by obbta17 with SMTP id ta17so842217obb.31 for <multiple recipients>; Thu, 29 Mar 2012 09:12:40 -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 :content-transfer-encoding; bh=goocOdoos0EcpvmqV/NB8Yht2B9VdaqUvspMg/UCxBA=; b=k8M6FELH97sl7ihMQ7jy7DbHzgZ0ZgrbjTaIA0ntvTqKx2sH18KdnikPOLRqJfkWk+ UDCyFKgn74mAxfc0wYoDZeJAZxdj51hzCLFSZa32oeT1YWAbVet+kv4kV9Mh7ZST4CBl L0MNj/FjLD/Qw8O/mIRfkuTZ4FsPEGujm3gZIKAjulHZ6rVnGluMzEDc1v7DL3t92nqo 8AQExYGhOO3dq5Q+QZxKeq5QeXNp2BZVsj2f4qC9fRhkde91V/TMUIIZGQTAa7j+/53j wO6kNwEFcX55QmD2JWeSpQjEI8+NcNFzXzsghiGecQYY1Mbdeq6vlk7OBenh0TaTNakp yx4A==
MIME-Version: 1.0
Received: by 10.182.74.8 with SMTP id p8mr44706459obv.41.1333037560641; Thu, 29 Mar 2012 09:12:40 -0700 (PDT)
Sender: christopher.morrow@gmail.com
Received: by 10.182.80.137 with HTTP; Thu, 29 Mar 2012 09:12:40 -0700 (PDT)
In-Reply-To: <CAL9jLaZYt0kEWm4rHGZ4JMXraDjRsCP8t7DLKn_bRMZOTy9GTg@mail.gmail.com>
References: <20120329141002.22903.96428.idtracker@ietfa.amsl.com> <CAL9jLaZYt0kEWm4rHGZ4JMXraDjRsCP8t7DLKn_bRMZOTy9GTg@mail.gmail.com>
Date: Thu, 29 Mar 2012 12:12:40 -0400
X-Google-Sender-Auth: a2HANQ9mkgUIsGab7BqOq8RQTxQ
Message-ID: <CAL9jLabf2QSd+ydbxCOfinJNxV_gPxX7XLk_RiE7_oCptfv-TA@mail.gmail.com>
Subject: Re: [conex] Last Call: <draft-ietf-conex-concepts-uses-04.txt> (ConEx Concepts and Use Cases) to Informational RFC
From: Christopher Morrow <morrowc.lists@gmail.com>
To: ietf@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: IETF-Announce <ietf-announce@ietf.org>, conex@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Mar 2012 16:12:42 -0000

On Thu, Mar 29, 2012 at 12:11 PM, Christopher Morrow
<morrowc.lists@gmail.com> wrote:
> On Thu, Mar 29, 2012 at 10:10 AM, The IESG <iesg-secretary@ietf.org> wrot=
e:
>>
>> The IESG has received a request from the Congestion Exposure WG (conex)
>> to consider the following document:
>> - 'ConEx Concepts and Use Cases'
>> =A0<draft-ietf-conex-concepts-uses-04.txt> as an 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-04-12. Exceptionally, comments may b=
e
>> sent to iesg@ietf.org instead. In either case, please retain the
>> beginning of the Subject line to allow automated sorting.
>>
>> Abstract
>>
>>
>> =A0 This document provides the entry point to the set of documentation
>> =A0 about the Congestion Exposure (ConEx) protocol. =A0It explains the
>> =A0 motivation for including a ConEx marking at the IP layer: to expose
>> =A0 information about congestion to network nodes. =A0Although such
>> =A0 information may have a number of uses, this document focuses on how
>> =A0 the information communicated by the ConEx marking can serve as the
>> =A0 basis for significantly more efficient and effective traffic
>> =A0 management than what exists on the Internet today.
>>
>>
>>
>>
>> The file can be obtained via
>> http://datatracker.ietf.org/doc/draft-ietf-conex-concepts-uses/
>>
>> IESG discussion can be tracked via
>> http://datatracker.ietf.org/doc/draft-ietf-conex-concepts-uses/ballot/
>>
>>
>> No IPR declarations have been submitted directly on this I-D.
>
> Didn't Mr Briscoe just email that there was a BT IPR claim against
> this ID, related to re-ECN work he did/does for BT?

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

From housley@vigilsec.com  Thu Mar 29 14:28:28 2012
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EE87321E801F for <ietf@ietfa.amsl.com>; Thu, 29 Mar 2012 14:28:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.586
X-Spam-Level: 
X-Spam-Status: No, score=-103.586 tagged_above=-999 required=5 tests=[AWL=1.014, BAYES_00=-2.599, GB_I_LETTER=-2, 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 Cm6bQj0oR773 for <ietf@ietfa.amsl.com>; Thu, 29 Mar 2012 14:28:28 -0700 (PDT)
Received: from services-1.meeting.ietf.org (unknown [IPv6:2001:df8:0:5::6]) by ietfa.amsl.com (Postfix) with ESMTP id 9D96721E8036 for <ietf@ietf.org>; Thu, 29 Mar 2012 14:28:27 -0700 (PDT)
Received: from [IPv6:2001:df8::64:c62c:3ff:fe2c:c7b9] (unknown [IPv6:2001:df8:0:64:c62c:3ff:fe2c:c7b9]) by services-1.meeting.ietf.org (Postfix) with ESMTP id 00820688E3 for <ietf@ietf.org>; Thu, 29 Mar 2012 21:28:26 +0000 (UTC)
From: Russ Housley <housley@vigilsec.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Priority: 3
Subject: IETF attendees reengineer their hotel's Wi-Fi network
Date: Thu, 29 Mar 2012 17:28:26 -0400
To: IETF <ietf@ietf.org>
Message-Id: <72DBE72C-5AA8-41F8-A804-06FC598591AE@vigilsec.com>
Mime-Version: 1.0 (Apple Message framework v1084)
X-Mailer: Apple Mail (2.1084)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Mar 2012 21:28:29 -0000

Disgusted IETF attendees reengineer their Paris hotel's Wi-Fi network
What happens when a bunch of IETF super nerds show up in Paris for a major 
conference and discover their hotel's Wi-Fi network has imploded?

http://newsletters.networkworld.com/t/6464858/258923304/355639/0/ 


From robert@raszuk.net  Thu Mar 29 14:43:38 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 AFF8321E801F for <ietf@ietfa.amsl.com>; Thu, 29 Mar 2012 14:43:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.505
X-Spam-Level: 
X-Spam-Status: No, score=-3.505 tagged_above=-999 required=5 tests=[AWL=1.094,  BAYES_00=-2.599, GB_I_LETTER=-2]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qBIgU+cxARZY for <ietf@ietfa.amsl.com>; Thu, 29 Mar 2012 14:43:38 -0700 (PDT)
Received: from mail1310.opentransfer.com (mail1310.opentransfer.com [76.162.254.103]) by ietfa.amsl.com (Postfix) with ESMTP id C976E21E8019 for <ietf@ietf.org>; Thu, 29 Mar 2012 14:43:37 -0700 (PDT)
Received: (qmail 32643 invoked by uid 399); 29 Mar 2012 21:43:37 -0000
Received: from unknown (HELO ?10.0.1.4?) (pbs:robert@raszuk.net@79.141.15.165) by mail1310.opentransfer.com with ESMTPM; 29 Mar 2012 21:43:37 -0000
X-Originating-IP: 79.141.15.165
Message-ID: <4F74D78C.7020600@raszuk.net>
Date: Thu, 29 Mar 2012 23:43:40 +0200
From: Robert Raszuk <robert@raszuk.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:11.0) Gecko/20120312 Thunderbird/11.0
MIME-Version: 1.0
To: "George, Wesley" <wesley.george@twcable.com>
Subject: Fwd: IETF attendees reengineer their hotel's Wi-Fi network
References: <72DBE72C-5AA8-41F8-A804-06FC598591AE@vigilsec.com>
In-Reply-To: <72DBE72C-5AA8-41F8-A804-06FC598591AE@vigilsec.com>
X-Forwarded-Message-Id: <72DBE72C-5AA8-41F8-A804-06FC598591AE@vigilsec.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: robert@raszuk.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Mar 2012 21:43:38 -0000

Hi Wes,

Could we perhaps add a section to your draft 
(draft-george-travel-faq-05.txt) on how to fix wifi network in the hotel 
you are staying ?

Pointer to set of open source wifi troubleshooting tools would be 
welcome too ;)

Cheers,
R.

-------- Original Message --------
Subject: IETF attendees reengineer their hotel's Wi-Fi network
Date: Thu, 29 Mar 2012 17:28:26 -0400
From: Russ Housley <housley@vigilsec.com>
To: IETF <ietf@ietf.org>

Disgusted IETF attendees reengineer their Paris hotel's Wi-Fi network
What happens when a bunch of IETF super nerds show up in Paris for a 
major conference and discover their hotel's Wi-Fi network has imploded?

http://newsletters.networkworld.com/t/6464858/258923304/355639/0/




From eburger-l@standardstrack.com  Thu Mar 29 14:49:34 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 CAE6221E8047 for <ietf@ietfa.amsl.com>; Thu, 29 Mar 2012 14:49:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.9
X-Spam-Level: 
X-Spam-Status: No, score=0.9 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FS_COSTARICA=2.899, J_CHICKENPOX_32=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rbpFfP3k+mIz for <ietf@ietfa.amsl.com>; Thu, 29 Mar 2012 14:49:33 -0700 (PDT)
Received: from biz104.inmotionhosting.com (biz104.inmotionhosting.com [173.247.254.120]) by ietfa.amsl.com (Postfix) with ESMTP id 3440D21E8026 for <ietf@ietf.org>; Thu, 29 Mar 2012 14:48:55 -0700 (PDT)
Received: from dhcp-4456.meeting.ietf.org ([130.129.68.86]:57721) by biz104.inmotionhosting.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69) (envelope-from <eburger-l@standardstrack.com>) id 1SDND7-0002tW-U0; Thu, 29 Mar 2012 14:48:51 -0700
Subject: Re: IETF.Fact.Check IETF Participants that were also at ICANN Costa Rica Meeting ?
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=iso-8859-1
From: Eric Burger <eburger-l@standardstrack.com>
In-Reply-To: <CB9A2149.6C8C0%jordi.palet@consulintel.es>
Date: Thu, 29 Mar 2012 23:48:40 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <EDBC32D3-3D99-4291-A290-276031398015@standardstrack.com>
References: <CB9A2149.6C8C0%jordi.palet@consulintel.es>
To: jordi.palet@consulintel.es
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: 
Cc: IETF list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Mar 2012 21:49:34 -0000

I was about to say we are at a point for an RFC 4633 action. Thanks.

On Mar 29, 2012, at 2:26 PM, JORDI PALET MARTINEZ wrote:

> Hi Jim,
>=20
> This is my last message to you as IETF Sergeant-at-arms.
>=20
> I've asked the Secretariat avoid your posts going thru the email =
exploder.
>=20
> Regards,
> Jordi
>=20
>=20
>=20
>=20
>=20
>=20
> -----Mensaje original-----
> De: Jim Fleming <ietf.fact.check@gmail.com>
> Responder a: <ietf.fact.check@gmail.com>
> Fecha: Thu, 29 Mar 2012 07:09:50 -0500
> Para: ietf <ietf@ietf.org>
> Asunto: IETF.Fact.Check IETF Participants that were also at ICANN =
Costa
> Rica Meeting ?
>=20
>> IETF.Fact.Check IETF Participants that were also at ICANN Costa Rica
>> Meeting ?
>>=20
>> https://www.ietf.org/registration/ietf83/attendance.py
>>=20
>> http://www.registration123.com/ICANN/CR43/
>>=20
>> Registration list as of: 03/29/2012
>> NAME 	AFFILIATION 	COUNTRY
>> AARON STEWART 	CLOUD VINE 	United States
>> Aar=F3n Quesada M=E9ndez 	Ice 	Costa Rica
>> Abdoul-Akim Adjibola 	Benin Telecoms 	BENIN
>> Abel Brenes 	University of Cosra Rica 	Costa Rica
>> ABELARDO FONSECA 	LA NACI=D2N 	Costa Rica
>> Abiodun Olawale 	Reboot& Associates Ltd =09
>> Abraham Araya 	MMSoluciones Seguridad en Informatica 	Costa =
Rica
>> Abraham Djekou 	Atci 	Cote d''Ivoire
>> Abraham Rodriguez 	Agencia Datsun Nissan 	Costa Rica
>> Acc Va Cac 	Ac Ac 	CR
>> Adalberto L=F3pez 	NIC Costa Rica =09
>> Adam Eisner 	Tucows Inc. =09
>> Adam Peake 	Glocom 	Japan
>> Adaobi Okeke 	Nigerian Communications Commission 	Nigeria
>> Adebiyi Oladipo 	Nigeria Internet Registration Association (NIRA) =
	Nigeria
>> Adebunmi Akinbo 	Young Internet Professionals (YiPS)/(NiRA) dotNG =
	Nigeria
>> Adela Elena Danciu 	Fellowship 	Romania
>> Adrian Carballo 	South School On Internet Governance 	=
Argentina
>> Adrian Garcia 	ISOC Costa Rica Chapter 	Costa Rica
>> Adrian Kinderis 	ARI Registry Services 	Australia
>> Adri=E1n P=E9rez 	Ccss 	Costa Rica
>> Adri=E1n Quesada Rodr=EDguez 		Costa Rica
>> Adri=E1n Solano 	Acoprot 	Costa Rica
>> ADRIANA DIAZ 	ICANN 	Costa Rica
>> Adriana Gonz=E1lez 	Sul=E1 Bats=FA 	Costa Rica
>> Adriana Rivero 	Lacnic 	Uruguay
>> Adriana Ulate 		COSTA RICA
>> AGARWAL SWAPNA 	.INDIA 	India
>> Ague Alain 	Ministry of agriculture 	B=E9nin
>> Ahsan Fahmi 		Pakistan
>> Aimee Deziel 	Mad =09
>> Akewushola Adisa 	Sanbak Communications Commission 	Nigeria
>> Akinori Maemura 	JPNIC 	Japan
>> Alain Artero 	European Broadcasting Union 	France
>> Alain Berranger 	Centre d'=E9tude et de coop=E9ration =
internationale 	Canada
>> Alain Bidron 	France Telecom/ETNO 	France
>> Alain Patrick Aina 	AFRIMIC 	B=E9nin
>> Alan Barrett 	AfriNIC / ASO-AC 	South Africa
>> Alan Fern=E1ndez Mar=EDn 	Universidad de Costa Rica 	Costa =
Rica
>> Alan Fern=E1ndez Mar=EDn 	Universidad de Costa Rica 	Costa =
Rica
>> Alan Greenberg 	Alac/gnso 	Canada
>> Alan Gutierrez 	Att 	Bolivia
>> Alberto Gomez 	Red.es 	Espa=F1a
>> Alberto Medrano C=E1ceres 	Universidad Nacional 	Costa Rica
>> Alejandra Castro 	Arias & Mu=F1oz 	Costa Rica
>> Alejandra Fern=E1ndez Bonilla 	TV Channel 15, University of =
Costa Rica
>> 	Costa Rica
>> Alejandra Reynoso 	Fellowship 	Guatemala
>> Alejandro Berrocal Valverde 	Viceministrerio Telecomunicaciones =
MINAET
>> 	Costa Rica
>> Alejandro Cruz 	Ministro de CIencia y Tecnologia 	Costa =
Rica
>> Alejandro Esquivel Rodriguez 	Cisco Systems 	Costa Rica
>> Alejandro Guzman 	ASO AC - LACNIC - Google 	Colombia
>> Alejandro Jimenez 	Ice 	Costa Rica
>> Alejandro Liz 	Nic Do 	Dominican Republic
>> Alejandro Moscol 	Fellow 	PER=DA
>> Alejandro Pisanty 	ISOC Mexico 	Mexico
>> Alejandro Portilla Navarro 	Radio Universidad de Costa Rica 	=
Costa Rica
>> Alejandro Rivera 	ICE 	Costa Rica
>> Alejandro Solis 	Unimer 	Costa Rica
>> Alex Blowers 	Nominet 	United Kingdom
>> Alex Mwangangi 	Municipal Council Of Mavoko 	KENYA
>> Alex Siffrin 	Key-Systems GmbH =09
>> Alex Stamos 	iSEC Partners 	United States
>> Alexa Raad 	Architelos 	United States
>> Alexander Al=ED 		Costa Rica
>> Alexander Flores 	Universidad de Costa Rica 	Costa Rica
>> Alexander Mora 	CAMTIC 	Costa Rica
>> Alexander Mora 	Universidad de Costa Rica 	Costa Rica
>> Alexander Ot=E1rola 	Omd 	Costa Rica
>> Alexander Panov 	Ru-Center 	Russia
>> Alexander Rojas 	Coral Technologies 	Costa Rica
>> Alexander Salas Arce 	Oficina Digital - CentroAmerica Hosting 	=
Costa Rica
>> Alexander Schubert 	dotgay LLC 	USA
>> Alexander Schwertner 	EPAG Domainservices GmbH 	Germany
>> Alexander Seger 	Council of Europe 	France
>> Alexis Coto 	Colegio Agropecuario 	Costa Rica
>> Alexis Sandoval 	Ice 	Costa Rica
>> Alfredo Lopez Hernandez 	Enredo 	Colombia
>> Alfredo Pinochet 	LatinTLD, Inc. 	Chile
>> Ali Asghar 	Ministry of I.C.T information technology organizat 	=
Indonesia
>> Alice Huang 	Net-Chinese Co., Ltd. 	Taiwan
>> Alice Jansen 	Icann 	Belgium
>> Alice Munyua 	Ministry of Information and Communications 	=
Kenya
>> Alicia Avenda=F1o 	Digital Government, Costa Rica 	Costa Rica
>> Alicia Paz 	Rds-Hn 	HONDURAS
>> Alina Syunkova 	Icann 	USA
>> Aline Valerie Assako 	NATIONAL AGENCY FOR ICT's 	CAMEROON
>> Alissa Sekulic 	TANGO Registry Services =AE 	Germany
>> Allan Berm=FAdez Carvajal 	Ice 	Costa Rica
>> Allan Campos Gallo 	Universidad de Costa Rica 	Costa Rica
>> Allan Perez 	colegio de abogados CR 	Costa Rica
>> Alvaro Araya 	Lightmaster Dev 	Costa Rica
>> Alvaro Hernandez 	Sistemas Inform=E1ticos de Centroam=E9rica =09
>> Amanda Cimaglia 	McCormick ICT 	USA
>> Amanda Fessenden 	Internet Pro APC 	United States
>> Am=E9d=E9e Dossou 	Ministere de la Communication et des TIC 	=
B=E9nin
>> Aminata Sy 	Fellowship 	Senegal
>> Amitabh Singhal 	Public Interest Registry 	India
>> Amy Repp 	CentralNic 	United Kingdom
>> Ana Arias 	Racsa 	Costa Rica
>> Ana Castro 	NIC Costa Rica =09
>> Ana Herrera 	Ucr 	COSTA RICA
>> Ana Neves 	Foundation for Science and Technology 	Portugal
>> Ana Ramos 	Internet Society of Puerto Rico 	Puerto Rico
>> ANA SANCHEZ 	ISOC ECUADOR 	Ecuador
>> Ana V=EDlchez 	Racsa 	Costa Rica
>> Ana Laura Echemendia 	Gobierno Digital 	Costa Rica
>> Ana Paula V=E1zquez Cisneros 	Sedo 	Germany
>> ANABEL RODRIGUEZ 	AGEIA DENSI ARGENTINA 	Argentina
>> Anahi Fajardo Torres 	Facultad de Derecho, Universidad de =
Costa Rica
>> 	Costa Rica
>> Anand Vora 	Public Interest Registry =09
>> Anders Gammelmark 	Larsen Data ApS 	Denmark
>> Anders Giversen 	TELE Greenland A/S 	Greenland
>> Anders Rafting 	Swedish Post and Telecom Authority 	Sweden
>> Andre Griffith 	Barbados ICT Professionals Association 	Barbados
>> Andre Hernandez 	Emd.co.cr 	Costa Rica
>> ANDREA BECCALLI 	(UNESCO) 	Italy
>> Andrea Glorioso 	European Commission 	Belgium
>> Andrea Rivera Alvarez 	Lanotec 	Costa Rica
>> Andrea Solano Ulloa 	Red de las Am=E8ricas 	costa rica
>> Andres Alfaro Quiros 	LQ Ingenieria 	Costa Rica
>> Andres Gonzalez 	Hewlett Packard 	Costa Rica
>> Andres Gonzalez Tenorio 	Itech Soluciones 	Costa Rica
>> Andres Guadamuz 	Innova Technology 	Costa Rica
>> Andres Morillo 	Metro Wireless 	Costa Rica
>> Andres Piazza 	Lacnic =09
>> Andres Rodriguez 	Promociones mercadeo y descuentos 	Costa =
Rica
>> Andres Ulate Jara 		Costa Rica
>> Andr=E9s Angulo Ram=EDrez 	Ice 	Costa Rica
>> Andr=E9s Cabezas 		Costa Rica
>> Andr=E9s Castillo G=F3mez 	Alojamiento Tico 	Costa Rica
>> Andr=E9s Garita 	Personal 	Costa Rica
>> Andrew Abrams 	Google 	United States
>> Andrew Barrett 	EnCirca 	US
>> Andrew Haije 	Ripe Ncc 	Netherlands
>> Andrew Mack 	AMGlobal Consulting 	USA
>> Andrew Merriam 	ICANNWiki 	USA
>> Andrew Robertson 	Edelman =09
>> Andrew Sullivan 	Dyn Inc 	Canada
>> Andrew Sullivan 	Dyn Inc 	Canada
>> Andrey Barrantes 	Ice 	Costa Rica
>> Andrey Kolesnikov 	Coordination center ccTLD .RU 	Russian =
Federation
>> Andrey Vorobyev 	Ru-Center 	Russian Federation
>> Andrii Paziuk 	Institute of International Relations Ukraine 	=
Ukraine
>> Andy Coombs 	International Anticounterfeiting Coalition 	United =
States
>> Angela Orozco 	Cac Porter Novelli 	COSTA RICA
>> Angie Graves 	Community DNS 	United States of America
>> Angie Morales Villalobos 	Universidad de Costa Rica 	Costa =
Rica
>> ANGIE OBANDO 	OIJ 	Costa Rica
>> Anjali Hansen 	Council of Better Business Bureaus 	USA
>> Annalisa Roger 	DotGreen 	United States
>> ANNE AIKMAN-SCALESE 	LEWIS AND ROCA 	United States
>> Anne LaPlante 	Gvsd 	USA
>> Anne-Rachel Inne 	Icann 	Niger
>> Annebeth Lange 	Uninett 	Norway
>> Anthony Arce 	Grupo ICE 	Costa Rica
>> ANTHONY BELTRAN 	101 DOMAIN 	United States
>> Anthony Beltran 	101Domain, Inc. 	United States
>> Anthony Harris 	Cabase =09
>> Anthony Lee 	Twnic 	Taiwan
>> Antonio Godinho 	Ciuem 	Mozambique
>> Antonio Medina 	Asociacion Colombiana de Usuarios de Internet 	=
Colombia
>> ANTONIO OSORIO 	DELL 	Costa Rica
>> Antonio Silva 	gwNIC official refistry SARL 	Guinea Bissau
>> Antonio Valverde-Mu=F1oz 	University of Costa Rica 	Costa =
Rica
>> Anwana Ima Obong 	International Foundation for African Children 	=
Nigeria
>> Arantxa Martinez 	Red.es 	Spain
>> Argery Campos 	Ice 	Costa Rica
>> Ariel Zu=F1iga Rojas 	=09
>> Armando Aguilar 	Ministerio de Ciencia y Tecnologia 	Costa =
Rica
>> Armando Jipsion 	NIC-Panama / PANNet / UTP =09
>> Arnold Yamukandu 	Centre De Promotion Et De Vulgarisation De =
L'Infor
>> 	RDCongo
>> Arnoldo Muller-Molina 	simMachines 	Costa Rica
>> Art Reilly 	Public Interest Registry 	USA
>> Arturo Rojas Aubert 	ADN Solutions 	Costa Rica
>> Arturo Rojas Kruse 	Emagine de Centroamerica 	Costa Rica
>> Arturo Servin 	Lacnic 	Uruguay
>> Ashley Henning 	Web.com 	United States
>> Attila Ozgit 	nic.TR 	Turkey
>> Aura Bonilla 	AST Media 	Costa Rica
>> Austin Gonz=E1lez 	Ice 	Costa Rica
>> AVRI DORIA 	N/A 	United States
>> Axel Pawlik 	Ripe Ncc / Nro 	Netherlands
>> Axia Harrison 	ARI Registry Services 	Australia
>> AYESHA NASSAN 	INTERNATINAL CHAMBER OF COMMERCE 	France
>> Ayotunde Akande 	Bluemiles Global Concept Ltd. 	Nigeria
>> Azeez Jubril 	Jaaz Integrated Services Ltd 	Nigeria
>> Aziz Hilali 	Isoc Morocco 	MOROCCO
>> B Nath 	TEC, India 	India
>> Ba Oumar 	Agetic =09
>> Barbara Cabezas 	NameAction Domains Latinamerica =09
>> Barbara Clay 	Icann 	UNITED STATES
>> Bart Lieben 	Crowell & Moring 	Belgium
>> Basamba Drammeh 	Association of ICT And Mobile Phone Technicians 	=
Gambia
>> Bashir Ghellali 		Costa Rica
>> Baudouin Schombe 	Centre Africain D'Echange Culturel 	=
DEMOCRATIC
>> REPUBLIC OF CONGO
>> Bavafa Syamak 	Domaine.fr 	France
>> Beau Brendler 	chairman,naraco 	United States
>> Becky Burr 	Wilmer Hale 	United States
>> Ben Anderson 	Group NBT 	Denmark
>> Ben Crawford 	CentralNic 	UAE
>> BEN ROBERT MILAM 	MILAM LAW FIRM 	United States
>> Bence Kozma 	Ultimate Digital Technologies, LLC ; DOTTODAY, LLC =09
>> Benedetta Rossi 	Business Constituency - ICANN 	France
>> Benedict Addis 	SOCA UK 	United Kingdom
>> Benjamin Zu=F1iga 	Seventh Floor C&D 	Costa Rica
>> Bernal Cordero 	Ice 	Costa Rica
>> Bernal Rojas Chavarr=EDa 	Ice 	Costa Rica
>> Bernard Turcotte 	Icann 	Canada
>> Bernardo Rojas Alfaro 	Ice 	Costa Rica
>> Berry Cobb 	Icann 	United States
>> Bert Achten 	gwNIC Global Web Service Ltd. 	Germany
>> Bert Wijnen 	Ripe Ncc 	Netherlands
>> Bertrand de La Chapelle 	Icann 	France
>> Bertrand Louveau 	Afnic 	France
>> Betsy Paque 	=09
>> BETZABEN ARIAS 	ICANN 	Costa Rica
>> Bill Graham 	Icann 	Canada
>> BILL SMITH 	PAYPAL 	United States
>> Bill Tomon 	Fellowship 	Papua New Guinea
>> Bill Woodcock 	Packet Clearing House 	US
>> BILLY YARBROUGH 	DOTREGISTRY,ORG 	United States
>> BLAINE RIGLER 	IRON MOUNTAIN 	United States
>> BLANCA CASTRO 	ICE 	Costa Rica
>> Blanca Diaz Jipsion 	NIC-Panama / PANNet / UTP 	Panama
>> Bo Martinsson 	Swedish Post and Telecom Authority 	Sweden
>> Bob Mountain 	NameMedia, Inc. 	United States
>> Bob Wiegand 	Web.com =09
>> Bobe Poka 	Otrt =09
>> Bolivar Molina Quir=F3s 	Ice 	Costa Rica
>> Bolivar Zu=F1iga 	Llevatetuweb.com =09
>> Brad Lemire 	Sedo 	usa
>> Brad White 	Icann 	USA
>> Brandon Soto Oviedo 		Costa Rica
>> Brenda Nyanamba 	KeNIC 	Kenya
>> Brendan Doyle 	CTIC Foundation 	Spain
>> BRETT FASSET 	.JOBS 	United States
>> Brian Beckham 	WIPO 	Switzerland
>> Brian Cute 	Public Interest Registry 	USA
>> Brian Unruh 	Endurance International Group =09
>> Brian Jay Winterfeldt 	Steptoe + Johnson LLP 	United States
>> Bruce Tonkin 	Icann 	Australia
>=20
>=20
>=20
> **********************************************
> IPv4 is over
> Are you ready for the new Internet ?
> http://www.consulintel.es
> The IPv6 Company
>=20
> This electronic message contains information which may be privileged =
or confidential. The information is intended to be for the use of the =
individual(s) named above. If you are not the intended recipient be =
aware that any disclosure, copying, distribution or use of the contents =
of this information, including attached files, is prohibited.
>=20
>=20
>=20


From ynir@checkpoint.com  Thu Mar 29 15:01:07 2012
Return-Path: <ynir@checkpoint.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AEC5321E8064 for <ietf@ietfa.amsl.com>; Thu, 29 Mar 2012 15:01:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.757
X-Spam-Level: 
X-Spam-Status: No, score=-8.757 tagged_above=-999 required=5 tests=[AWL=-1.657, BAYES_00=-2.599, FS_COSTARICA=2.899, J_CHICKENPOX_32=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 LGOxAvH1SjVL for <ietf@ietfa.amsl.com>; Thu, 29 Mar 2012 15:01:06 -0700 (PDT)
Received: from michael.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id 5901821E8019 for <ietf@ietf.org>; Thu, 29 Mar 2012 15:01:05 -0700 (PDT)
Received: from il-ex01.ad.checkpoint.com (il-ex01.ad.checkpoint.com [194.29.34.26]) by michael.checkpoint.com (8.13.8/8.13.8) with ESMTP id q2TM13R0026407;  Fri, 30 Mar 2012 00:01:03 +0200
X-CheckPoint: {4F74DAA2-1-1B221DC2-5FFFF}
Received: from il-ex01.ad.checkpoint.com ([126.0.0.2]) by il-ex01.ad.checkpoint.com ([126.0.0.2]) with mapi; Fri, 30 Mar 2012 00:01:02 +0200
From: Yoav Nir <ynir@checkpoint.com>
To: Eric Burger <eburger-l@standardstrack.com>
Date: Fri, 30 Mar 2012 00:01:02 +0200
Subject: Re: IETF.Fact.Check IETF Participants that were also at ICANN Costa Rica Meeting ?
Thread-Topic: IETF.Fact.Check IETF Participants that were also at ICANN Costa	Rica Meeting ?
Thread-Index: Ac0N926W9zAJxqr6QwKF5z7wCyrefw==
Message-ID: <CC4CC026-499B-4F77-A6A5-C83E696E5386@checkpoint.com>
References: <CB9A2149.6C8C0%jordi.palet@consulintel.es> <EDBC32D3-3D99-4291-A290-276031398015@standardstrack.com>
In-Reply-To: <EDBC32D3-3D99-4291-A290-276031398015@standardstrack.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: IETF list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Mar 2012 22:01:07 -0000

Oh, this guy pre-dates RFC 4633

http://www.google.com/search?q=3D%22jim%20fleming%22%20site:ietf.org

On Mar 29, 2012, at 11:48 PM, Eric Burger wrote:

> I was about to say we are at a point for an RFC 4633 action. Thanks.
>
> On Mar 29, 2012, at 2:26 PM, JORDI PALET MARTINEZ wrote:
>
>> Hi Jim,
>>
>> This is my last message to you as IETF Sergeant-at-arms.
>>
>> I've asked the Secretariat avoid your posts going thru the email explode=
r.
>>
>> Regards,
>> Jordi
>>
>>
>>
>>
>>
>>
>> -----Mensaje original-----
>> De: Jim Fleming <ietf.fact.check@gmail.com>
>> Responder a: <ietf.fact.check@gmail.com>
>> Fecha: Thu, 29 Mar 2012 07:09:50 -0500
>> Para: ietf <ietf@ietf.org>
>> Asunto: IETF.Fact.Check IETF Participants that were also at ICANN Costa
>> Rica Meeting ?
>>
>>> IETF.Fact.Check IETF Participants that were also at ICANN Costa Rica
>>> Meeting ?
>>>
>>> https://www.ietf.org/registration/ietf83/attendance.py
>>>
>>> http://www.registration123.com/ICANN/CR43/
>>>
>>> Registration list as of: 03/29/2012
>>> NAME         AFFILIATION     COUNTRY
>>> AARON STEWART        CLOUD VINE      United States
>>> Aar=F3n Quesada M=E9ndez         Ice     Costa Rica
>>> Abdoul-Akim Adjibola         Benin Telecoms  BENIN
>>> Abel Brenes  University of Cosra Rica        Costa Rica
>>> ABELARDO FONSECA     LA NACI=D2N       Costa Rica
>>> Abiodun Olawale      Reboot& Associates Ltd
>>> Abraham Araya        MMSoluciones Seguridad en Informatica   Costa Rica
>>> Abraham Djekou       Atci    Cote d''Ivoire
>>> Abraham Rodriguez    Agencia Datsun Nissan   Costa Rica
>>> Acc Va Cac   Ac Ac   CR
>>> Adalberto L=F3pez      NIC Costa Rica
>>> Adam Eisner  Tucows Inc.
>>> Adam Peake   Glocom  Japan
>>> Adaobi Okeke         Nigerian Communications Commission      Nigeria
>>> Adebiyi Oladipo      Nigeria Internet Registration Association (NIRA)  =
      Nigeria
>>> Adebunmi Akinbo      Young Internet Professionals (YiPS)/(NiRA) dotNG  =
      Nigeria
>>> Adela Elena Danciu   Fellowship      Romania
>>> Adrian Carballo      South School On Internet Governance     Argentina
>>> Adrian Garcia        ISOC Costa Rica Chapter         Costa Rica
>>> Adrian Kinderis      ARI Registry Services   Australia
>>> Adri=E1n P=E9rez         Ccss    Costa Rica
>>> Adri=E1n Quesada Rodr=EDguez             Costa Rica
>>> Adri=E1n Solano        Acoprot         Costa Rica
>>> ADRIANA DIAZ         ICANN   Costa Rica
>>> Adriana Gonz=E1lez     Sul=E1 Bats=FA      Costa Rica
>>> Adriana Rivero       Lacnic  Uruguay
>>> Adriana Ulate                COSTA RICA
>>> AGARWAL SWAPNA       .INDIA  India
>>> Ague Alain   Ministry of agriculture         B=E9nin
>>> Ahsan Fahmi          Pakistan
>>> Aimee Deziel         Mad
>>> Akewushola Adisa     Sanbak Communications Commission        Nigeria
>>> Akinori Maemura      JPNIC   Japan
>>> Alain Artero         European Broadcasting Union     France
>>> Alain Berranger      Centre d'=E9tude et de coop=E9ration international=
e         Canada
>>> Alain Bidron         France Telecom/ETNO     France
>>> Alain Patrick Aina   AFRIMIC         B=E9nin
>>> Alan Barrett         AfriNIC / ASO-AC        South Africa
>>> Alan Fern=E1ndez Mar=EDn         Universidad de Costa Rica       Costa =
Rica
>>> Alan Fern=E1ndez Mar=EDn         Universidad de Costa Rica       Costa =
Rica
>>> Alan Greenberg       Alac/gnso       Canada
>>> Alan Gutierrez       Att     Bolivia
>>> Alberto Gomez        Red.es  Espa=F1a
>>> Alberto Medrano C=E1ceres      Universidad Nacional    Costa Rica
>>> Alejandra Castro     Arias & Mu=F1oz   Costa Rica
>>> Alejandra Fern=E1ndez Bonilla  TV Channel 15, University of Costa Rica
>>>     Costa Rica
>>> Alejandra Reynoso    Fellowship      Guatemala
>>> Alejandro Berrocal Valverde  Viceministrerio Telecomunicaciones MINAET
>>>     Costa Rica
>>> Alejandro Cruz       Ministro de CIencia y Tecnologia        Costa Rica
>>> Alejandro Esquivel Rodriguez         Cisco Systems   Costa Rica
>>> Alejandro Guzman     ASO AC - LACNIC - Google        Colombia
>>> Alejandro Jimenez    Ice     Costa Rica
>>> Alejandro Liz        Nic Do  Dominican Republic
>>> Alejandro Moscol     Fellow  PER=DA
>>> Alejandro Pisanty    ISOC Mexico     Mexico
>>> Alejandro Portilla Navarro   Radio Universidad de Costa Rica         Co=
sta Rica
>>> Alejandro Rivera     ICE     Costa Rica
>>> Alejandro Solis      Unimer  Costa Rica
>>> Alex Blowers         Nominet         United Kingdom
>>> Alex Mwangangi       Municipal Council Of Mavoko     KENYA
>>> Alex Siffrin         Key-Systems GmbH
>>> Alex Stamos  iSEC Partners   United States
>>> Alexa Raad   Architelos      United States
>>> Alexander Al=ED                Costa Rica
>>> Alexander Flores     Universidad de Costa Rica       Costa Rica
>>> Alexander Mora       CAMTIC  Costa Rica
>>> Alexander Mora       Universidad de Costa Rica       Costa Rica
>>> Alexander Ot=E1rola    Omd     Costa Rica
>>> Alexander Panov      Ru-Center       Russia
>>> Alexander Rojas      Coral Technologies      Costa Rica
>>> Alexander Salas Arce         Oficina Digital - CentroAmerica Hosting   =
      Costa Rica
>>> Alexander Schubert   dotgay LLC      USA
>>> Alexander Schwertner         EPAG Domainservices GmbH        Germany
>>> Alexander Seger      Council of Europe       France
>>> Alexis Coto  Colegio Agropecuario    Costa Rica
>>> Alexis Sandoval      Ice     Costa Rica
>>> Alfredo Lopez Hernandez      Enredo  Colombia
>>> Alfredo Pinochet     LatinTLD, Inc.  Chile
>>> Ali Asghar   Ministry of I.C.T information technology organizat      In=
donesia
>>> Alice Huang  Net-Chinese Co., Ltd.   Taiwan
>>> Alice Jansen         Icann   Belgium
>>> Alice Munyua         Ministry of Information and Communications      Ke=
nya
>>> Alicia Avenda=F1o      Digital Government, Costa Rica  Costa Rica
>>> Alicia Paz   Rds-Hn  HONDURAS
>>> Alina Syunkova       Icann   USA
>>> Aline Valerie Assako         NATIONAL AGENCY FOR ICT's       CAMEROON
>>> Alissa Sekulic       TANGO Registry Services =AE       Germany
>>> Allan Berm=FAdez Carvajal      Ice     Costa Rica
>>> Allan Campos Gallo   Universidad de Costa Rica       Costa Rica
>>> Allan Perez  colegio de abogados CR  Costa Rica
>>> Alvaro Araya         Lightmaster Dev         Costa Rica
>>> Alvaro Hernandez     Sistemas Inform=E1ticos de Centroam=E9rica
>>> Amanda Cimaglia      McCormick ICT   USA
>>> Amanda Fessenden     Internet Pro APC        United States
>>> Am=E9d=E9e Dossou        Ministere de la Communication et des TIC      =
  B=E9nin
>>> Aminata Sy   Fellowship      Senegal
>>> Amitabh Singhal      Public Interest Registry        India
>>> Amy Repp     CentralNic      United Kingdom
>>> Ana Arias    Racsa   Costa Rica
>>> Ana Castro   NIC Costa Rica
>>> Ana Herrera  Ucr     COSTA RICA
>>> Ana Neves    Foundation for Science and Technology   Portugal
>>> Ana Ramos    Internet Society of Puerto Rico         Puerto Rico
>>> ANA SANCHEZ  ISOC ECUADOR    Ecuador
>>> Ana V=EDlchez  Racsa   Costa Rica
>>> Ana Laura Echemendia         Gobierno Digital        Costa Rica
>>> Ana Paula V=E1zquez Cisneros   Sedo    Germany
>>> ANABEL RODRIGUEZ     AGEIA DENSI ARGENTINA   Argentina
>>> Anahi Fajardo Torres         Facultad de Derecho, Universidad de Costa =
Rica
>>>     Costa Rica
>>> Anand Vora   Public Interest Registry
>>> Anders Gammelmark    Larsen Data ApS         Denmark
>>> Anders Giversen      TELE Greenland A/S      Greenland
>>> Anders Rafting       Swedish Post and Telecom Authority      Sweden
>>> Andre Griffith       Barbados ICT Professionals Association  Barbados
>>> Andre Hernandez      Emd.co.cr       Costa Rica
>>> ANDREA BECCALLI      (UNESCO)        Italy
>>> Andrea Glorioso      European Commission     Belgium
>>> Andrea Rivera Alvarez        Lanotec         Costa Rica
>>> Andrea Solano Ulloa  Red de las Am=E8ricas     costa rica
>>> Andres Alfaro Quiros         LQ Ingenieria   Costa Rica
>>> Andres Gonzalez      Hewlett Packard         Costa Rica
>>> Andres Gonzalez Tenorio      Itech Soluciones        Costa Rica
>>> Andres Guadamuz      Innova Technology       Costa Rica
>>> Andres Morillo       Metro Wireless  Costa Rica
>>> Andres Piazza        Lacnic
>>> Andres Rodriguez     Promociones mercadeo y descuentos       Costa Rica
>>> Andres Ulate Jara            Costa Rica
>>> Andr=E9s Angulo Ram=EDrez        Ice     Costa Rica
>>> Andr=E9s Cabezas               Costa Rica
>>> Andr=E9s Castillo G=F3mez        Alojamiento Tico        Costa Rica
>>> Andr=E9s Garita        Personal        Costa Rica
>>> Andrew Abrams        Google  United States
>>> Andrew Barrett       EnCirca         US
>>> Andrew Haije         Ripe Ncc        Netherlands
>>> Andrew Mack  AMGlobal Consulting     USA
>>> Andrew Merriam       ICANNWiki       USA
>>> Andrew Robertson     Edelman
>>> Andrew Sullivan      Dyn Inc         Canada
>>> Andrew Sullivan      Dyn Inc         Canada
>>> Andrey Barrantes     Ice     Costa Rica
>>> Andrey Kolesnikov    Coordination center ccTLD .RU   Russian Federation
>>> Andrey Vorobyev      Ru-Center       Russian Federation
>>> Andrii Paziuk        Institute of International Relations Ukraine    Uk=
raine
>>> Andy Coombs  International Anticounterfeiting Coalition      United Sta=
tes
>>> Angela Orozco        Cac Porter Novelli      COSTA RICA
>>> Angie Graves         Community DNS   United States of America
>>> Angie Morales Villalobos     Universidad de Costa Rica       Costa Rica
>>> ANGIE OBANDO         OIJ     Costa Rica
>>> Anjali Hansen        Council of Better Business Bureaus      USA
>>> Annalisa Roger       DotGreen        United States
>>> ANNE AIKMAN-SCALESE  LEWIS AND ROCA  United States
>>> Anne LaPlante        Gvsd    USA
>>> Anne-Rachel Inne     Icann   Niger
>>> Annebeth Lange       Uninett         Norway
>>> Anthony Arce         Grupo ICE       Costa Rica
>>> ANTHONY BELTRAN      101 DOMAIN      United States
>>> Anthony Beltran      101Domain, Inc.         United States
>>> Anthony Harris       Cabase
>>> Anthony Lee  Twnic   Taiwan
>>> Antonio Godinho      Ciuem   Mozambique
>>> Antonio Medina       Asociacion Colombiana de Usuarios de Internet   Co=
lombia
>>> ANTONIO OSORIO       DELL    Costa Rica
>>> Antonio Silva        gwNIC official refistry SARL    Guinea Bissau
>>> Antonio Valverde-Mu=F1oz       University of Costa Rica        Costa Ri=
ca
>>> Anwana Ima Obong     International Foundation for African Children   Ni=
geria
>>> Arantxa Martinez     Red.es  Spain
>>> Argery Campos        Ice     Costa Rica
>>> Ariel Zu=F1iga Rojas
>>> Armando Aguilar      Ministerio de Ciencia y Tecnologia      Costa Rica
>>> Armando Jipsion      NIC-Panama / PANNet / UTP
>>> Arnold Yamukandu     Centre De Promotion Et De Vulgarisation De L'Infor
>>>     RDCongo
>>> Arnoldo Muller-Molina        simMachines     Costa Rica
>>> Art Reilly   Public Interest Registry        USA
>>> Arturo Rojas Aubert  ADN Solutions   Costa Rica
>>> Arturo Rojas Kruse   Emagine de Centroamerica        Costa Rica
>>> Arturo Servin        Lacnic  Uruguay
>>> Ashley Henning       Web.com         United States
>>> Attila Ozgit         nic.TR  Turkey
>>> Aura Bonilla         AST Media       Costa Rica
>>> Austin Gonz=E1lez      Ice     Costa Rica
>>> AVRI DORIA   N/A     United States
>>> Axel Pawlik  Ripe Ncc / Nro  Netherlands
>>> Axia Harrison        ARI Registry Services   Australia
>>> AYESHA NASSAN        INTERNATINAL CHAMBER OF COMMERCE        France
>>> Ayotunde Akande      Bluemiles Global Concept Ltd.   Nigeria
>>> Azeez Jubril         Jaaz Integrated Services Ltd    Nigeria
>>> Aziz Hilali  Isoc Morocco    MOROCCO
>>> B Nath       TEC, India      India
>>> Ba Oumar     Agetic
>>> Barbara Cabezas      NameAction Domains Latinamerica
>>> Barbara Clay         Icann   UNITED STATES
>>> Bart Lieben  Crowell & Moring        Belgium
>>> Basamba Drammeh      Association of ICT And Mobile Phone Technicians   =
      Gambia
>>> Bashir Ghellali              Costa Rica
>>> Baudouin Schombe     Centre Africain D'Echange Culturel      DEMOCRATIC
>>> REPUBLIC OF CONGO
>>> Bavafa Syamak        Domaine.fr      France
>>> Beau Brendler        chairman,naraco         United States
>>> Becky Burr   Wilmer Hale     United States
>>> Ben Anderson         Group NBT       Denmark
>>> Ben Crawford         CentralNic      UAE
>>> BEN ROBERT MILAM     MILAM LAW FIRM  United States
>>> Bence Kozma  Ultimate Digital Technologies, LLC ; DOTTODAY, LLC
>>> Benedetta Rossi      Business Constituency - ICANN   France
>>> Benedict Addis       SOCA UK         United Kingdom
>>> Benjamin Zu=F1iga      Seventh Floor C&D       Costa Rica
>>> Bernal Cordero       Ice     Costa Rica
>>> Bernal Rojas Chavarr=EDa       Ice     Costa Rica
>>> Bernard Turcotte     Icann   Canada
>>> Bernardo Rojas Alfaro        Ice     Costa Rica
>>> Berry Cobb   Icann   United States
>>> Bert Achten  gwNIC Global Web Service Ltd.   Germany
>>> Bert Wijnen  Ripe Ncc        Netherlands
>>> Bertrand de La Chapelle      Icann   France
>>> Bertrand Louveau     Afnic   France
>>> Betsy Paque
>>> BETZABEN ARIAS       ICANN   Costa Rica
>>> Bill Graham  Icann   Canada
>>> BILL SMITH   PAYPAL  United States
>>> Bill Tomon   Fellowship      Papua New Guinea
>>> Bill Woodcock        Packet Clearing House   US
>>> BILLY YARBROUGH      DOTREGISTRY,ORG         United States
>>> BLAINE RIGLER        IRON MOUNTAIN   United States
>>> BLANCA CASTRO        ICE     Costa Rica
>>> Blanca Diaz Jipsion  NIC-Panama / PANNet / UTP       Panama
>>> Bo Martinsson        Swedish Post and Telecom Authority      Sweden
>>> Bob Mountain         NameMedia, Inc.         United States
>>> Bob Wiegand  Web.com
>>> Bobe Poka    Otrt
>>> Bolivar Molina Quir=F3s        Ice     Costa Rica
>>> Bolivar Zu=F1iga       Llevatetuweb.com
>>> Brad Lemire  Sedo    usa
>>> Brad White   Icann   USA
>>> Brandon Soto Oviedo          Costa Rica
>>> Brenda Nyanamba      KeNIC   Kenya
>>> Brendan Doyle        CTIC Foundation         Spain
>>> BRETT FASSET         .JOBS   United States
>>> Brian Beckham        WIPO    Switzerland
>>> Brian Cute   Public Interest Registry        USA
>>> Brian Unruh  Endurance International Group
>>> Brian Jay Winterfeldt        Steptoe + Johnson LLP   United States
>>> Bruce Tonkin         Icann   Australia
>>
>>
>>
>> **********************************************
>> IPv4 is over
>> Are you ready for the new Internet ?
>> http://www.consulintel.es
>> The IPv6 Company
>>
>> This electronic message contains information which may be privileged or =
confidential. The information is intended to be for the use of the individu=
al(s) named above. If you are not the intended recipient be aware that any =
disclosure, copying, distribution or use of the contents of this informatio=
n, including attached files, is prohibited.
>>
>>
>>
>
>
> Scanned by Check Point Total Security Gateway.


From narten@us.ibm.com  Thu Mar 29 21:54:07 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 7433B21F862F for <ietf@ietfa.amsl.com>; Thu, 29 Mar 2012 21:54:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -108.852
X-Spam-Level: 
X-Spam-Status: No, score=-108.852 tagged_above=-999 required=5 tests=[AWL=-0.112, BAYES_20=-0.74, 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 henW1M0aYefC for <ietf@ietfa.amsl.com>; Thu, 29 Mar 2012 21:54:05 -0700 (PDT)
Received: from e32.co.us.ibm.com (e32.co.us.ibm.com [32.97.110.150]) by ietfa.amsl.com (Postfix) with ESMTP id 8507A21F8629 for <ietf@ietf.org>; Thu, 29 Mar 2012 21:53:59 -0700 (PDT)
Received: from /spool/local by e32.co.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <ietf@ietf.org> from <narten@us.ibm.com>; Thu, 29 Mar 2012 22:53:58 -0600
Received: from d03dlp01.boulder.ibm.com (9.17.202.177) by e32.co.us.ibm.com (192.168.1.132) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Thu, 29 Mar 2012 22:53:04 -0600
Received: from d03relay04.boulder.ibm.com (d03relay04.boulder.ibm.com [9.17.195.106]) by d03dlp01.boulder.ibm.com (Postfix) with ESMTP id 70E2E1FF0048 for <ietf@ietf.org>; Thu, 29 Mar 2012 22:53:03 -0600 (MDT)
Received: from d03av03.boulder.ibm.com (d03av03.boulder.ibm.com [9.17.195.169]) by d03relay04.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id q2U4r3Vr163834 for <ietf@ietf.org>; Thu, 29 Mar 2012 22:53:03 -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 q2U4r3B0009300 for <ietf@ietf.org>; Thu, 29 Mar 2012 22:53:03 -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 q2U4r3A0009282 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Thu, 29 Mar 2012 22:53:03 -0600
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [127.0.0.1]) by rotala.raleigh.ibm.com (8.14.4/8.12.5) with ESMTP id q2U4r2M7013271 for <ietf@ietf.org>; Fri, 30 Mar 2012 00:53:02 -0400
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.4/8.14.4/Submit) id q2U4r1ND013227 for ietf@ietf.org; Fri, 30 Mar 2012 00:53:02 -0400
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201203300453.q2U4r1ND013227@rotala.raleigh.ibm.com>
Date: Fri, 30 Mar 2012 00:53:01 -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: 12033004-3270-0000-0000-0000052E5B03
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Mar 2012 04:54:07 -0000

Total of 62 messages in the last 7 days.
 
script run at: Fri Mar 30 00:53:01 EDT 2012
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
 17.74% |   11 | 13.46% |    78436 | ietf.fact.check@gmail.com
  6.45% |    4 |  7.50% |    43736 | daedulus@btconnect.com
  6.45% |    4 |  4.60% |    26804 | morrowc.lists@gmail.com
  1.61% |    1 |  8.03% |    46785 | rcallon@juniper.net
  3.23% |    2 |  4.68% |    27290 | jordi.palet@consulintel.es
  1.61% |    1 |  6.24% |    36393 | malcolm.betts@zte.com.cn
  4.84% |    3 |  2.88% |    16794 | sm@resistor.net
  1.61% |    1 |  6.10% |    35534 | mustapha.aissaoui@alcatel-lucent.com
  3.23% |    2 |  4.32% |    25192 | nurit.sprecher@nsn.com
  3.23% |    2 |  2.17% |    12636 | marshall.eubanks@gmail.com
  3.23% |    2 |  2.06% |    11998 | hannes.tschofenig@gmx.net
  3.23% |    2 |  1.85% |    10809 | ietf@meetecho.com
  1.61% |    1 |  3.43% |    19970 | ynir@checkpoint.com
  3.23% |    2 |  1.74% |    10155 | rpelletier@isoc.org
  3.23% |    2 |  1.67% |     9723 | francis.dupont@fdupont.fr
  1.61% |    1 |  3.04% |    17729 | eburger-l@standardstrack.com
  1.61% |    1 |  2.65% |    15461 | loa@pi.nu
  1.61% |    1 |  2.15% |    12509 | huubatwork@gmail.com
  1.61% |    1 |  1.78% |    10373 | akatlas@gmail.com
  1.61% |    1 |  1.72% |    10050 | narten@us.ibm.com
  1.61% |    1 |  1.66% |     9682 | ah@tr-sys.de
  1.61% |    1 |  1.59% |     9290 | rcosta@ptinovacao.pt
  1.61% |    1 |  1.47% |     8549 | denghui02@gmail.com
  1.61% |    1 |  1.07% |     6226 | dcrocker@gmail.com
  1.61% |    1 |  1.04% |     6063 | thierry.moreau@connotech.com
  1.61% |    1 |  1.04% |     6045 | fred@cisco.com
  1.61% |    1 |  1.00% |     5855 | amorris@amsl.com
  1.61% |    1 |  0.98% |     5696 | dave@cridland.net
  1.61% |    1 |  0.95% |     5536 | robert@raszuk.net
  1.61% |    1 |  0.94% |     5453 | vinayakh@gmail.com
  1.61% |    1 |  0.91% |     5302 | dwm@xpasc.com
  1.61% |    1 |  0.91% |     5296 | hartmans-ietf@mit.edu
  1.61% |    1 |  0.90% |     5257 | nick@inex.ie
  1.61% |    1 |  0.90% |     5254 | joelja@bogus.com
  1.61% |    1 |  0.88% |     5155 | drc@virtualized.org
  1.61% |    1 |  0.87% |     5086 | john@jck.com
  1.61% |    1 |  0.82% |     4792 | housley@vigilsec.com
--------+------+--------+----------+------------------------
100.00% |   62 |100.00% |   582914 | Total


From wesley.george@twcable.com  Thu Mar 29 22:33:56 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 A04A821F8667 for <ietf@ietfa.amsl.com>; Thu, 29 Mar 2012 22:33:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.561
X-Spam-Level: 
X-Spam-Status: No, score=-1.561 tagged_above=-999 required=5 tests=[AWL=0.902,  BAYES_00=-2.599, GB_I_LETTER=-2, 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 Ha6ZQHg8VJwt for <ietf@ietfa.amsl.com>; Thu, 29 Mar 2012 22:33:55 -0700 (PDT)
Received: from cdpipgw02.twcable.com (cdpipgw02.twcable.com [165.237.59.23]) by ietfa.amsl.com (Postfix) with ESMTP id 202D421F8668 for <ietf@ietf.org>; Thu, 29 Mar 2012 22:33:54 -0700 (PDT)
X-SENDER-IP: 10.136.163.14
X-SENDER-REPUTATION: None
X-IronPort-AV: E=Sophos;i="4.75,340,1330923600"; d="scan'208";a="344726308"
Received: from unknown (HELO PRVPEXHUB05.corp.twcable.com) ([10.136.163.14]) by cdpipgw02.twcable.com with ESMTP/TLS/RC4-MD5; 30 Mar 2012 01:33:02 -0400
Received: from PRVPEXVS03.corp.twcable.com ([10.136.163.27]) by PRVPEXHUB05.corp.twcable.com ([10.136.163.14]) with mapi; Fri, 30 Mar 2012 01:33:54 -0400
From: "George, Wes" <wesley.george@twcable.com>
To: "robert@raszuk.net" <robert@raszuk.net>
Date: Fri, 30 Mar 2012 01:33:51 -0400
Subject: RE: IETF attendees reengineer their hotel's Wi-Fi network
Thread-Topic: IETF attendees reengineer their hotel's Wi-Fi network
Thread-Index: Ac0N9RCDoqLe6GL5S7+W4GV1gVlpdAAQCvPQ
Message-ID: <DCC302FAA9FE5F4BBA4DCAD465693779173D5FA410@PRVPEXVS03.corp.twcable.com>
References: <72DBE72C-5AA8-41F8-A804-06FC598591AE@vigilsec.com> <4F74D78C.7020600@raszuk.net>
In-Reply-To: <4F74D78C.7020600@raszuk.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 Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Mar 2012 05:33:56 -0000

I had recommended separately on the attendees list that perhaps Chelliot an=
d his merry band of "supernerds" need to write an informational or BCP draf=
t, accompanied by a round of *NOG presentations to share the wealth, as doc=
umentation in this area appears a bit sparse -- I've been to plenty of othe=
r conferences where the wireless network melted down in the hotel, conferen=
ce itself or both. In response, Joel Jaeggli pointed to a NANOG presentatio=
n that is so old that it's still talking about 802.11G (and A) as a future =
thing, and the network in question was probably dealing with half or less o=
f the devices that a modern one must do (no wi-fi phones, tablets, etc). So=
 while the fundamentals of dealing with RF frequency overlap and power prob=
ably haven't changed much, I think that perhaps we're due for an update on =
the experience of managing and optimizing large-scale conference/hotel WiFi=
 networks, especially the part about the tools that you use that enable you=
 to re-engineer a network of that size on the fly (aside from "pure awesome=
" and "lack of sleep", that is). :-)

Thanks,

Wes


> -----Original Message-----
> From: Robert Raszuk [mailto:robert@raszuk.net]
> Sent: Thursday, March 29, 2012 5:44 PM
> To: George, Wes
> Cc: IETF Discussion
> Subject: Fwd: IETF attendees reengineer their hotel's Wi-Fi network
>
> Hi Wes,
>
> Could we perhaps add a section to your draft
> (draft-george-travel-faq-05.txt) on how to fix wifi network in the hotel
> you are staying ?
>
> Pointer to set of open source wifi troubleshooting tools would be
> welcome too ;)
>
> Cheers,
> R.
>
> -------- Original Message --------
> Subject: IETF attendees reengineer their hotel's Wi-Fi network
> Date: Thu, 29 Mar 2012 17:28:26 -0400
> From: Russ Housley <housley@vigilsec.com>
> To: IETF <ietf@ietf.org>
>
> Disgusted IETF attendees reengineer their Paris hotel's Wi-Fi network
> What happens when a bunch of IETF super nerds show up in Paris for a
> major conference and discover their hotel's Wi-Fi network has imploded?
>
> http://newsletters.networkworld.com/t/6464858/258923304/355639/0/
>
>


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 wesley.george@twcable.com  Thu Mar 29 22:44:28 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 C541521F86D3 for <ietf@ietfa.amsl.com>; Thu, 29 Mar 2012 22:44:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.377
X-Spam-Level: 
X-Spam-Status: No, score=0.377 tagged_above=-999 required=5 tests=[AWL=-1.059,  BAYES_00=-2.599, FS_COSTARICA=2.899, 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 0hz78Hyxoj9v for <ietf@ietfa.amsl.com>; Thu, 29 Mar 2012 22:44:28 -0700 (PDT)
Received: from cdpipgw01.twcable.com (cdpipgw01.twcable.com [165.237.59.22]) by ietfa.amsl.com (Postfix) with ESMTP id CCAF521F86D1 for <ietf@ietf.org>; Thu, 29 Mar 2012 22:44:27 -0700 (PDT)
X-SENDER-IP: 10.136.163.15
X-SENDER-REPUTATION: None
X-IronPort-AV: E=Sophos;i="4.75,341,1330923600"; d="scan'208";a="361170118"
Received: from unknown (HELO PRVPEXHUB06.corp.twcable.com) ([10.136.163.15]) by cdpipgw01.twcable.com with ESMTP/TLS/RC4-MD5; 30 Mar 2012 01:43:25 -0400
Received: from PRVPEXVS03.corp.twcable.com ([10.136.163.27]) by PRVPEXHUB06.corp.twcable.com ([10.136.163.15]) with mapi; Fri, 30 Mar 2012 01:44:27 -0400
From: "George, Wes" <wesley.george@twcable.com>
To: Yoav Nir <ynir@checkpoint.com>, Eric Burger <eburger-l@standardstrack.com>
Date: Fri, 30 Mar 2012 01:44:25 -0400
Subject: RE: IETF.Fact.Check IETF Participants that were also at ICANN Costa Rica Meeting ?
Thread-Topic: IETF.Fact.Check IETF Participants that were also at ICANN Costa	Rica Meeting ?
Thread-Index: Ac0N926W9zAJxqr6QwKF5z7wCyrefwAP1R+g
Message-ID: <DCC302FAA9FE5F4BBA4DCAD465693779173D5FA413@PRVPEXVS03.corp.twcable.com>
References: <CB9A2149.6C8C0%jordi.palet@consulintel.es> <EDBC32D3-3D99-4291-A290-276031398015@standardstrack.com> <CC4CC026-499B-4F77-A6A5-C83E696E5386@checkpoint.com>
In-Reply-To: <CC4CC026-499B-4F77-A6A5-C83E696E5386@checkpoint.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: IETF list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Mar 2012 05:44:28 -0000

Which is why I'm wondering why it took us that long to punt him? Our rules =
shouldn't treat people like this as a first-time poster if it's the same no=
nsense that got them banned before, but from a new email address.

Mr. Fleming had stopped trolling lists for the last 6-9 months, but prior t=
o that he was hitting every list he could find plus Twitter (hashtag spammi=
ng), and it appears that it's about to start again, so I'd ask that the adm=
ins be a bit more aggressive in this regard.

Thanks
Wes George


> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of Y=
oav
> Nir
> Sent: Thursday, March 29, 2012 6:01 PM
> To: Eric Burger
> Cc: IETF list
> Subject: Re: IETF.Fact.Check IETF Participants that were also at ICANN Co=
sta
> Rica Meeting ?
>
> Oh, this guy pre-dates RFC 4633
>
> http://www.google.com/search?q=3D%22jim%20fleming%22%20site:ietf.org
>
> On Mar 29, 2012, at 11:48 PM, Eric Burger wrote:
>
> > I was about to say we are at a point for an RFC 4633 action. Thanks.
> >
> > On Mar 29, 2012, at 2:26 PM, JORDI PALET MARTINEZ wrote:
> >
> >> Hi Jim,
> >>
> >> This is my last message to you as IETF Sergeant-at-arms.
> >>
> >> I've asked the Secretariat avoid your posts going thru the email explo=
der.
> >>
> >> Regards,
> >> Jordi
>


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 prvs=14368fa829=jordi.palet@consulintel.es  Fri Mar 30 00:10:09 2012
Return-Path: <prvs=14368fa829=jordi.palet@consulintel.es>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 298B521F8704 for <ietf@ietfa.amsl.com>; Fri, 30 Mar 2012 00:10:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.275
X-Spam-Level: 
X-Spam-Status: No, score=-104.275 tagged_above=-999 required=5 tests=[AWL=-0.575, BAYES_00=-2.599, FS_COSTARICA=2.899, 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 6rVLQa-FZgnz for <ietf@ietfa.amsl.com>; Fri, 30 Mar 2012 00:10:08 -0700 (PDT)
Received: from consulintel.es (mail.consulintel.es [213.172.48.142]) by ietfa.amsl.com (Postfix) with ESMTP id 45F8C21F8707 for <ietf@ietf.org>; Fri, 30 Mar 2012 00:10:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1333091229; x=1333696029; q=dns/txt; h=DomainKey-Signature: Received:User-Agent:Date:Subject:From:To:Message-ID:Thread-Topic: In-Reply-To:Mime-version:Content-type:Content-transfer-encoding: Reply-To; bh=+Gu1RM4Jwa43SuGjXlzdscGEaCRJzb1ORQ7sh/VwcbI=; b=oaF 0Ci18cDdaHuxJjqIpbIPlbW5tEnbU0fFOJK2B6ch+xa9cPHIT2TQGQubsZqnX+un sjPuB7BzYkNciE8RTrkIOWUsYtaz1M1C0bn7MHWH9Kq5AyCYAbFaiH3U2bihxpxz essMcIbKuOe1tB1ntPtPTrW7nqKzG2iW97oTNCog=
DomainKey-Signature: a=rsa-sha1; s=MDaemon; d=consulintel.es; c=simple; q=dns; h=from:message-id; b=TrwDX+8Nzu7q+dwvhYF9MGe9DCuaZR/VUfeLINn0E60wvJJQaOgW+kkfxaZB i+UiQVGuCF8YA7Qs3nCdDFk/ExkHashMePPi8/IteWwHGSyhMXsXbJlGs tmcVGK29xdyOJnDhVOUYA3JUGbCng3CKt9azVusw6baZ8FmPA0NloQ=;
X-MDAV-Processed: consulintel.es, Fri, 30 Mar 2012 09:07:09 +0200
Received: from [130.129.80.175] by consulintel.es (MDaemon PRO v11.0.3) with ESMTP id md50004135652.msg for <ietf@ietf.org>; Fri, 30 Mar 2012 09:07:08 +0200
X-Spam-Processed: consulintel.es, Fri, 30 Mar 2012 09:07:08 +0200 (not processed: message from trusted or authenticated source)
X-MDPtrLookup-Result: pass dns.ptr=dhcp-50af.meeting.ietf.org (ip=130.129.80.175) (consulintel.es)
X-Authenticated-Sender: jordi.palet@consulintel.es
X-HashCash: 1:20:120330:md50004135652::MiZQyB8J6k7Bz48z:00008+b3
X-MDRemoteIP: 130.129.80.175
X-Return-Path: prvs=14368fa829=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ietf@ietf.org
User-Agent: Microsoft-MacOutlook/14.14.0.111121
Date: Fri, 30 Mar 2012 08:51:18 +0200
Subject: Re: IETF.Fact.Check IETF Participants that were also at ICANN Costa Rica Meeting ?
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: IETF list <ietf@ietf.org>
Message-ID: <CB9B2456.6CB26%jordi.palet@consulintel.es>
Thread-Topic: IETF.Fact.Check IETF Participants that were also at ICANN Costa Rica Meeting ?
In-Reply-To: <DCC302FAA9FE5F4BBA4DCAD465693779173D5FA413@PRVPEXVS03.corp.twcable.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: jordi.palet@consulintel.es
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Mar 2012 07:10:09 -0000

I guess this is due to the way IETF Secretariat filter and the possibility
of some one to use a new email each time they want ...

Regards,
Jordi






-----Mensaje original-----
De: "George, Wes" <wesley.george@twcable.com>
Responder a: <wesley.george@twcable.com>
Fecha: Fri, 30 Mar 2012 01:44:25 -0400
Para: Yoav Nir <ynir@checkpoint.com>, Eric Burger
<eburger-l@standardstrack.com>
CC: IETF list <ietf@ietf.org>
Asunto: RE: IETF.Fact.Check IETF Participants that were also at ICANN
Costa Rica Meeting ?

>Which is why I'm wondering why it took us that long to punt him? Our
>rules shouldn't treat people like this as a first-time poster if it's the
>same nonsense that got them banned before, but from a new email address.
>
>Mr. Fleming had stopped trolling lists for the last 6-9 months, but prior
>to that he was hitting every list he could find plus Twitter (hashtag
>spamming), and it appears that it's about to start again, so I'd ask that
>the admins be a bit more aggressive in this regard.
>
>Thanks
>Wes George
>
>
>> -----Original Message-----
>> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
>>Yoav
>> Nir
>> Sent: Thursday, March 29, 2012 6:01 PM
>> To: Eric Burger
>> Cc: IETF list
>> Subject: Re: IETF.Fact.Check IETF Participants that were also at ICANN
>>Costa
>> Rica Meeting ?
>>
>> Oh, this guy pre-dates RFC 4633
>>
>> http://www.google.com/search?q=%22jim%20fleming%22%20site:ietf.org
>>
>> On Mar 29, 2012, at 11:48 PM, Eric Burger wrote:
>>
>> > I was about to say we are at a point for an RFC 4633 action. Thanks.
>> >
>> > On Mar 29, 2012, at 2:26 PM, JORDI PALET MARTINEZ wrote:
>> >
>> >> Hi Jim,
>> >>
>> >> This is my last message to you as IETF Sergeant-at-arms.
>> >>
>> >> I've asked the Secretariat avoid your posts going thru the email
>>exploder.
>> >>
>> >> Regards,
>> >> Jordi
>>
>
>
>This E-mail and any of its attachments may contain Time Warner Cable
>proprietary information, which is privileged, confidential, or subject to
>copyright belonging to Time Warner Cable. This E-mail is intended solely
>for the use of the individual or entity to which it is addressed. If you
>are not the intended recipient of this E-mail, you are hereby notified
>that any dissemination, distribution, copying, or action taken in
>relation to the contents of and attachments to this E-mail is strictly
>prohibited and may be unlawful. If you have received this E-mail in
>error, please notify the sender immediately and permanently delete the
>original and any copy of this E-mail and any printout.



**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.consulintel.es
The IPv6 Company

This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.




From mcr@sandelman.ca  Fri Mar 30 01:12:27 2012
Return-Path: <mcr@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5BB1E21F86C8 for <ietf@ietfa.amsl.com>; Fri, 30 Mar 2012 01:12:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.624
X-Spam-Level: 
X-Spam-Status: No, score=-1.624 tagged_above=-999 required=5 tests=[AWL=0.330,  BAYES_00=-2.599, HOST_MISMATCH_NET=0.311, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UsCMCogKJxls for <ietf@ietfa.amsl.com>; Fri, 30 Mar 2012 01:12:25 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [67.23.6.41]) by ietfa.amsl.com (Postfix) with ESMTP id 9EC0121F852B for <ietf@ietf.org>; Fri, 30 Mar 2012 01:12:14 -0700 (PDT)
Received: from marajade.sandelman.ca (dhcp-50ed.meeting.ietf.org [130.129.80.237]) by relay.sandelman.ca (Postfix) with ESMTPS id 013C3344FB for <ietf@ietf.org>; Fri, 30 Mar 2012 04:09:26 -0400 (EDT)
Received: by marajade.sandelman.ca (Postfix, from userid 179) id 7ECAF98AAE; Fri, 30 Mar 2012 10:12:10 +0200 (CEST)
Received: from marajade.sandelman.ca (localhost [127.0.0.1]) by marajade.sandelman.ca (Postfix) with ESMTP id 7D39998281 for <ietf@ietf.org>; Fri, 30 Mar 2012 10:12:10 +0200 (CEST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: IETF Discussion <ietf@ietf.org>
Subject: Re: IETF attendees reengineer their hotel's Wi-Fi network
In-Reply-To: <DCC302FAA9FE5F4BBA4DCAD465693779173D5FA410@PRVPEXVS03.corp.twcable.com>
References: <72DBE72C-5AA8-41F8-A804-06FC598591AE@vigilsec.com> <4F74D78C.7020600@raszuk.net> <DCC302FAA9FE5F4BBA4DCAD465693779173D5FA410@PRVPEXVS03.corp.twcable.com>
X-Mailer: MH-E 8.3; nmh 1.3-dev; XEmacs 21.4 (patch 22)
Date: Fri, 30 Mar 2012 10:12:10 +0200
Message-ID: <24480.1333095130@marajade.sandelman.ca>
Sender: mcr@sandelman.ca
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Mar 2012 08:12:28 -0000

>>>>> "Wes" == Wes George <George> writes:
    Wes> I had recommended separately on the attendees list that perhaps
    Wes> Chelliot and his merry band of "supernerds" need to write an
    Wes> informational or BCP draft, accompanied by a round of *NOG
    Wes> presentations to share the wealth, as documentation in this
    Wes> area appears a bit sparse -- I've been to plenty of other
    Wes> conferences where the wireless network melted down in the
    Wes> hotel, conference itself or both. In response, Joel Jaeggli
    Wes> pointed to a NANOG presentation that is so old that it's still

It's a lot of work for someone who isn't getting paid for it.

I'd like to see some hotel chains commission this.


-- 
]       He who is tired of Weird Al is tired of life!           |  firewalls  [
]   Michael Richardson, Sandelman Software Works, Ottawa, ON    |net architect[
] mcr@sandelman.ottawa.on.ca http://www.sandelman.ottawa.on.ca/ |device driver[
   Kyoto Plus: watch the video <http://www.youtube.com/watch?v=kzx1ycLXQSE>
	               then sign the petition. 

From marcelo@it.uc3m.es  Fri Mar 30 02:56:03 2012
Return-Path: <marcelo@it.uc3m.es>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2D86A21F894F; Fri, 30 Mar 2012 02:56: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 KK-lIpjD8Z-1; Fri, 30 Mar 2012 02:56:02 -0700 (PDT)
Received: from smtp03.uc3m.es (smtp03.uc3m.es [163.117.176.133]) by ietfa.amsl.com (Postfix) with ESMTP id 5587521F8926; Fri, 30 Mar 2012 02:56:01 -0700 (PDT)
X-uc3m-safe: yes
Received: from dhcp-117d.meeting.ietf.org (dhcp-117d.meeting.ietf.org [130.129.17.125]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp03.uc3m.es (Postfix) with ESMTP id 9B0FA9C63A0; Fri, 30 Mar 2012 11:56:00 +0200 (CEST)
Message-ID: <4F758327.3000104@it.uc3m.es>
Date: Fri, 30 Mar 2012 11:55:51 +0200
From: marcelo bagnulo braun <marcelo@it.uc3m.es>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: Christopher Morrow <morrowc.lists@gmail.com>
Subject: Re: [conex] Last Call: <draft-ietf-conex-concepts-uses-04.txt> (ConEx Concepts and Use Cases) to Informational RFC
References: <20120329141002.22903.96428.idtracker@ietfa.amsl.com> <CAL9jLaZYt0kEWm4rHGZ4JMXraDjRsCP8t7DLKn_bRMZOTy9GTg@mail.gmail.com>
In-Reply-To: <CAL9jLaZYt0kEWm4rHGZ4JMXraDjRsCP8t7DLKn_bRMZOTy9GTg@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-TM-AS-Product-Ver: IMSS-7.0.0.3116-6.8.0.1017-18806.006
Cc: ietf@ietf.org, IETF-Announce <ietf-announce@ietf.org>, conex@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Mar 2012 09:56:03 -0000

Hi,

Bob's email specifically said specifications and mechanisms would be 
likely to be tagged with the IPR. This particular document is neither a 
specification nor a mechanism as it describes the use cases for conex. 
When the drafts describing the conex spec are sent to the IESG, the IPR 
claim will be propely pointed out.

I hope this clarifies the issue.

Regards, marcelo


El 29/03/12 18:11, Christopher Morrow escribió:
> On Thu, Mar 29, 2012 at 10:10 AM, The IESG<iesg-secretary@ietf.org>  wrote:
>> The IESG has received a request from the Congestion Exposure WG (conex)
>> to consider the following document:
>> - 'ConEx Concepts and Use Cases'
>>   <draft-ietf-conex-concepts-uses-04.txt>  as an 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-04-12. 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 provides the entry point to the set of documentation
>>    about the Congestion Exposure (ConEx) protocol.  It explains the
>>    motivation for including a ConEx marking at the IP layer: to expose
>>    information about congestion to network nodes.  Although such
>>    information may have a number of uses, this document focuses on how
>>    the information communicated by the ConEx marking can serve as the
>>    basis for significantly more efficient and effective traffic
>>    management than what exists on the Internet today.
>>
>>
>>
>>
>> The file can be obtained via
>> http://datatracker.ietf.org/doc/draft-ietf-conex-concepts-uses/
>>
>> IESG discussion can be tracked via
>> http://datatracker.ietf.org/doc/draft-ietf-conex-concepts-uses/ballot/
>>
>>
>> No IPR declarations have been submitted directly on this I-D.
> Didn't Mr Briscoe just email that there was a BT IPR claim against
> this ID, related to re-ECN work he did/does for BT?
>
>> _______________________________________________
>> conex mailing list
>> conex@ietf.org
>> https://www.ietf.org/mailman/listinfo/conex
> _______________________________________________
> conex mailing list
> conex@ietf.org
> https://www.ietf.org/mailman/listinfo/conex
>

