
From bortzmeyer@nic.fr  Mon Oct  1 12:43:11 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 4491621F8B98 for <ietf@ietfa.amsl.com>; Mon,  1 Oct 2012 12:43:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.393
X-Spam-Level: 
X-Spam-Status: No, score=-101.393 tagged_above=-999 required=5 tests=[AWL=1.207, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1ltIueRvD330 for <ietf@ietfa.amsl.com>; Mon,  1 Oct 2012 12:43:10 -0700 (PDT)
Received: from mail.bortzmeyer.org (aetius.bortzmeyer.org [IPv6:2001:4b98:dc0:41:216:3eff:fece:1902]) by ietfa.amsl.com (Postfix) with ESMTP id 78B3221F8B96 for <ietf@ietf.org>; Mon,  1 Oct 2012 12:43:10 -0700 (PDT)
Received: by mail.bortzmeyer.org (Postfix, from userid 10) id 231263B46B; Mon,  1 Oct 2012 19:43:07 +0000 (UTC)
Received: by mail.sources.org (Postfix, from userid 1000) id 7100C190DAA; Mon,  1 Oct 2012 21:40:48 +0200 (CEST)
Date: Mon, 1 Oct 2012 21:40:48 +0200
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: iab@iab.org
Subject: Re: Call for Comment: <draft-iab-modern-paradigm-01.txt> (Affirmation of 	the Modern Paradigm for Standards) to Informational RFC
Message-ID: <20121001194048.GA31574@sources.org>
References: <027201cd9fe5$b4189710$1c49c530$@iab.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <027201cd9fe5$b4189710$1c49c530$@iab.org>
X-Transport: UUCP rules
X-Operating-System: Debian GNU/Linux 6.0.5
User-Agent: Mutt/1.5.20 (2009-06-14)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Oct 2012 19:43:11 -0000

On Mon, Oct 01, 2012 at 08:01:54AM -0700,
 IAB Chair <iab-chair@iab.org> wrote 
 a message of 157 lines which said:

> This is an IETF-wide Call for Comment on 'Affirmation of the Modern Paradigm
> for Standards'. 

As mentioned by others, it is quite late since the text is already
signed. 

Also, what could be the outcome of this Last Call? There have been
already a call for comments two months ago and the filed comments do
not seem to have been addressed (see for instance #193)


From john-ietf@jck.com  Mon Oct  1 12:48:54 2012
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 66BA721F843A; Mon,  1 Oct 2012 12:48:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.584
X-Spam-Level: 
X-Spam-Status: No, score=-102.584 tagged_above=-999 required=5 tests=[AWL=0.015, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pbb0J3jnz4et; Mon,  1 Oct 2012 12:48:53 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 41A5621F852C; Mon,  1 Oct 2012 12:48:37 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1TIlym-0006ce-EW; Mon, 01 Oct 2012 15:48:36 -0400
Date: Mon, 01 Oct 2012 15:48:31 -0400
From: John C Klensin <john-ietf@jck.com>
To: ietf@ietf.org
Subject: Re: Last Call: <draft-ietf-dnsext-rfc2671bis-edns0-09.txt> (Extension	Mechanisms for DNS (EDNS(0))) to Internet Standard
Message-ID: <56DB6FE506A144D1183B93A8@JcK-HP8200.jck.com>
In-Reply-To: <20120930145325.21053.67854.idtracker@ietfa.amsl.com>
References: <20120930145325.21053.67854.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: dnsext@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Oct 2012 19:48:54 -0000

--On Sunday, September 30, 2012 07:53 -0700 The IESG
<iesg-secretary@ietf.org> wrote:

> 
> The IESG has received a request from the DNS Extensions WG
> (dnsext) to consider the following document:
> - 'Extension Mechanisms for DNS (EDNS(0))'
>   <draft-ietf-dnsext-rfc2671bis-edns0-09.txt> as Internet
> Standard
> 
> The IESG plans to make a decision in the next few weeks, and
> solicits final comments on this action. Please send
> substantive comments to the ietf@ietf.org mailing lists by
> 2012-10-29. Exceptionally, comments may be sent to
> iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
> 
> Abstract
> 
> 
>    The Domain Name System's wire protocol includes a number of
> fixed    fields whose range has been or soon will be exhausted
> and does not    allow requestors to advertise their
> capabilities to responders.  This    document describes
> backward compatible mechanisms for allowing the    protocol to
> grow.
> 
>    This document updates the EDNS(0) specification (and
> obsoletes RFC    2671) based on feedback from deployment
> experience in several    implementations.  It also closes the
> IANA registry for extended    labels created as part of RFC
> 2671 and obsoletes RFC 2673 ("Binary    Labels in the Domain
> Name System") which depends on the existence of    extended
> labels.
>...

Hi.  Apologies for not noticing this earlier, but this
specification's deprecation of label types raises an issue that
the document doesn't seem to address.

Deprecating RFC 2673 is one thing.  Given deployment and
operational experience, I don't know of anyone who would offer a
strong defense of binary labels today.   However, the document
doesn't offer a strong justification for deprecating label types
entirely other than, it seems, that there has been only one
example of their use and that failed.   If that were the only
motivation, it would be a rather weak one, especially since
having a capability that we don't use (but conceivably might in
the future) would not appear to cause any harm.

With the understanding that this is an example, not a proposal,
it may be useful to review some of the history and context for
IDNs.  IDNA represents community consensus as to the right way
to proceed, but that consensus includes both people who believe
it is a good permanent strategy and people who believe it is a
good temporary/transition strategy until a better plan can be
developed and deployed.   In particular, some of that latter
group were painfully aware of the rate at which EDNS0 was
deploying in the first half of the last decade, making them more
receptive to IDNA (or other strategies that did not depend on
changes to DNS servers or resolvers).

So suppose the community really does decide that it wants
DNS-based IDNs and that it wants to see if they can be developed
and deployed within the existing DNS rather than moving to what
some have called DNSng.  It is reasonably clear that what would
be called "just send 8" in the email community would not be
acceptable if only because there are DNS uses outside the public
network that use UTF-8 directly and others that use ISO 8859-1
or other character coding and repertoires (RFC 6055 discusses
some related issues).  The proposal/thought piece I produced in
2001-2002 (with urging from some DNS-expert colleagues) to
transition to a new, i18n-sensitive, Class might be part of the
solution, but it is now clear that it would not be sufficient
(at least without considerable special-casing that would violate
both 1034/1035 and current trends).  A different label type that
would permit specialized interpretations of the labels might be
an important part of the puzzle.

Would that be a good idea?  I don't know.  Personally, I believe
that some of the expectations of and demand for IDNs cannot be
met in the current DNS and that we should not try to go much
further than IDNA: if more is really needed, then it should be
accomplished either in an "above DNS" solution or by designing
and deploying DNS2.  But I think it would be terribly unwise to
eliminate a facility that might be useful for i18n simply
because someone tried to use it for something entirely different
and that effort did not succeed.

Therefore:
(1)  Did the WG consider i18n and other issues and possibilities
before deciding to deprecate extended label types entirely?  If
so, why aren't those considerations described in the document?
We don't have a lot of codes left in the RFC 1035 space on which
other label type models might be constructed.

(2) Is there strong justification for deprecating extended label
types, e.g., evidence that they would cause harm?

(3) If the answer to either of both of the above questions is
"no", wouldn't it be wiser to simply deprecate the use of binary
labels, urge great caution in allocating and using other label
types, and then move on rather than eliminating the facility?

thanks,
    john



From marka@isc.org  Mon Oct  1 19:22: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 A3B331F0D67; Mon,  1 Oct 2012 19:22:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VuU+4jVur2UA; Mon,  1 Oct 2012 19:22:33 -0700 (PDT)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [IPv6:2001:500:60::65]) by ietfa.amsl.com (Postfix) with ESMTP id 73C5F1F0D44; Mon,  1 Oct 2012 19:22:33 -0700 (PDT)
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mail.isc.org", Issuer "RapidSSL CA" (not verified)) by mx.ams1.isc.org (Postfix) with ESMTPS id 7062F5F9954; Tue,  2 Oct 2012 02:22:21 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (unknown [IPv6:2001:470:1f00:820:1c89:b24e:dc8f:2933]) (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 0DC06216C3B; Tue,  2 Oct 2012 02:22: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 D7B2A282EC28; Tue,  2 Oct 2012 12:22:12 +1000 (EST)
To: John C Klensin <john-ietf@jck.com>
From: Mark Andrews <marka@isc.org>
References: <20120930145325.21053.67854.idtracker@ietfa.amsl.com> <56DB6FE506A144D1183B93A8@JcK-HP8200.jck.com>
Subject: Re: [dnsext] Last Call: <draft-ietf-dnsext-rfc2671bis-edns0-09.txt> (Extension Mechanisms for DNS (EDNS(0))) to Internet Standard
In-reply-to: Your message of "Mon, 01 Oct 2012 15:48:31 -0400." <56DB6FE506A144D1183B93A8@JcK-HP8200.jck.com>
Date: Tue, 02 Oct 2012 12:22:12 +1000
Message-Id: <20121002022212.D7B2A282EC28@drugs.dv.isc.org>
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: Tue, 02 Oct 2012 02:22:34 -0000

In message <56DB6FE506A144D1183B93A8@JcK-HP8200.jck.com>, John C Klensin writes
:
> 
> 
> --On Sunday, September 30, 2012 07:53 -0700 The IESG
> <iesg-secretary@ietf.org> wrote:
> 
> > 
> > The IESG has received a request from the DNS Extensions WG
> > (dnsext) to consider the following document:
> > - 'Extension Mechanisms for DNS (EDNS(0))'
> >   <draft-ietf-dnsext-rfc2671bis-edns0-09.txt> as Internet
> > Standard
> > 
> > The IESG plans to make a decision in the next few weeks, and
> > solicits final comments on this action. Please send
> > substantive comments to the ietf@ietf.org mailing lists by
> > 2012-10-29. Exceptionally, comments may be sent to
> > iesg@ietf.org instead. In either case, please retain the
> > beginning of the Subject line to allow automated sorting.
> > 
> > Abstract
> > 
> > 
> >    The Domain Name System's wire protocol includes a number of
> > fixed    fields whose range has been or soon will be exhausted
> > and does not    allow requestors to advertise their
> > capabilities to responders.  This    document describes
> > backward compatible mechanisms for allowing the    protocol to
> > grow.
> > 
> >    This document updates the EDNS(0) specification (and
> > obsoletes RFC    2671) based on feedback from deployment
> > experience in several    implementations.  It also closes the
> > IANA registry for extended    labels created as part of RFC
> > 2671 and obsoletes RFC 2673 ("Binary    Labels in the Domain
> > Name System") which depends on the existence of    extended
> > labels.
> >...
> 
> Hi.  Apologies for not noticing this earlier, but this
> specification's deprecation of label types raises an issue that
> the document doesn't seem to address.
> 
> Deprecating RFC 2673 is one thing.  Given deployment and
> operational experience, I don't know of anyone who would offer a
> strong defense of binary labels today.   However, the document
> doesn't offer a strong justification for deprecating label types
> entirely other than, it seems, that there has been only one
> example of their use and that failed.   If that were the only
> motivation, it would be a rather weak one, especially since
> having a capability that we don't use (but conceivably might in
> the future) would not appear to cause any harm.
> 
> With the understanding that this is an example, not a proposal,
> it may be useful to review some of the history and context for
> IDNs.  IDNA represents community consensus as to the right way
> to proceed, but that consensus includes both people who believe
> it is a good permanent strategy and people who believe it is a
> good temporary/transition strategy until a better plan can be
> developed and deployed.   In particular, some of that latter
> group were painfully aware of the rate at which EDNS0 was
> deploying in the first half of the last decade, making them more
> receptive to IDNA (or other strategies that did not depend on
> changes to DNS servers or resolvers).
> 
> So suppose the community really does decide that it wants
> DNS-based IDNs and that it wants to see if they can be developed
> and deployed within the existing DNS rather than moving to what
> some have called DNSng.  It is reasonably clear that what would
> be called "just send 8" in the email community would not be
> acceptable if only because there are DNS uses outside the public
> network that use UTF-8 directly and others that use ISO 8859-1
> or other character coding and repertoires (RFC 6055 discusses
> some related issues).  The proposal/thought piece I produced in
> 2001-2002 (with urging from some DNS-expert colleagues) to
> transition to a new, i18n-sensitive, Class might be part of the
> solution, but it is now clear that it would not be sufficient
> (at least without considerable special-casing that would violate
> both 1034/1035 and current trends).  A different label type that
> would permit specialized interpretations of the labels might be
> an important part of the puzzle.
> 
> Would that be a good idea?  I don't know.  Personally, I believe
> that some of the expectations of and demand for IDNs cannot be
> met in the current DNS and that we should not try to go much
> further than IDNA: if more is really needed, then it should be
> accomplished either in an "above DNS" solution or by designing
> and deploying DNS2.  But I think it would be terribly unwise to
> eliminate a facility that might be useful for i18n simply
> because someone tried to use it for something entirely different
> and that effort did not succeed.
> 
> Therefore:
> (1)  Did the WG consider i18n and other issues and possibilities
> before deciding to deprecate extended label types entirely?  If
> so, why aren't those considerations described in the document?
> We don't have a lot of codes left in the RFC 1035 space on which
> other label type models might be constructed.
> 
> (2) Is there strong justification for deprecating extended label
> types, e.g., evidence that they would cause harm?
> 
> (3) If the answer to either of both of the above questions is
> "no", wouldn't it be wiser to simply deprecate the use of binary
> labels, urge great caution in allocating and using other label
> types, and then move on rather than eliminating the facility?
> 
> thanks,
>     john

I don't think we need to do this in label types.  An EDNS option
would be sufficient to specify alternate normalisation rules should
be applied to the QNAME when looking for data and when normalising
the owner names when performing DNSSEC validation.

> _______________________________________________
> dnsext mailing list
> dnsext@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsext
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org

From john-ietf@jck.com  Mon Oct  1 19:57: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 A3BA421F8A2D; Mon,  1 Oct 2012 19:57:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.584
X-Spam-Level: 
X-Spam-Status: No, score=-102.584 tagged_above=-999 required=5 tests=[AWL=0.015, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1tAq4cgmFo5C; Mon,  1 Oct 2012 19:57:06 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 266A121F8A2B; Mon,  1 Oct 2012 19:57:06 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1TIsfR-00070V-5X; Mon, 01 Oct 2012 22:57:05 -0400
Date: Mon, 01 Oct 2012 22:56:59 -0400
From: John C Klensin <john-ietf@jck.com>
To: Mark Andrews <marka@isc.org>
Subject: Re: [dnsext] Last Call: <draft-ietf-dnsext-rfc2671bis-edns0-09.txt> (Extension Mechanisms for DNS (EDNS(0))) to Internet Standard
Message-ID: <818904DB9902CFA1AB4DCB8F@JcK-HP8200.jck.com>
In-Reply-To: <20121002022212.D7B2A282EC28@drugs.dv.isc.org>
References: <20120930145325.21053.67854.idtracker@ietfa.amsl.com> <56DB6FE506A144D1183B93A8@JcK-HP8200.jck.com> <20121002022212.D7B2A282EC28@drugs.dv.isc.org>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: ietf@ietf.org, 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: Tue, 02 Oct 2012 02:57:06 -0000

--On Tuesday, October 02, 2012 12:22 +1000 Mark Andrews
<marka@isc.org> wrote:

>> Therefore:
>> (1)  Did the WG consider i18n and other issues and
>> possibilities before deciding to deprecate extended label
>> types entirely?  If so, why aren't those considerations
>> described in the document? We don't have a lot of codes left
>> in the RFC 1035 space on which other label type models might
>> be constructed.
>> 
>> (2) Is there strong justification for deprecating extended
>> label types, e.g., evidence that they would cause harm?
>> 
>> (3) If the answer to either of both of the above questions is
>> "no", wouldn't it be wiser to simply deprecate the use of
>> binary labels, urge great caution in allocating and using
>> other label types, and then move on rather than eliminating
>> the facility?
>...
> I don't think we need to do this in label types.  An EDNS
> option would be sufficient to specify alternate normalisation
> rules should be applied to the QNAME when looking for data and
> when normalising the owner names when performing DNSSEC
> validation.

Mark,

First, it was just an example.   As I thought I made clear, my
main concern is about completely eliminating a facility because
one instance of trying to use it had not turned out to be as
useful as expected.  Absent demonstration that all possible uses
of the facility are actually useless or that the facility is
harmful, I don't think the case has been made for deprecating
it.   As far as that example is concerned, I don't think this is
the right place to review everything we've learned about i18n,
identifiers, and comparisons in the last couple of decades, but
normalization is just not a very large fraction of the problem.

    john


From marka@isc.org  Mon Oct  1 20:33:15 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 89E0E1F0D5B; Mon,  1 Oct 2012 20:33:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.301
X-Spam-Level: 
X-Spam-Status: No, score=-2.301 tagged_above=-999 required=5 tests=[AWL=0.298,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IfiSC5tRDJIT; Mon,  1 Oct 2012 20:33:15 -0700 (PDT)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [IPv6:2001:500:60::65]) by ietfa.amsl.com (Postfix) with ESMTP id 17F591F0D64; Mon,  1 Oct 2012 20:33:14 -0700 (PDT)
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mail.isc.org", Issuer "RapidSSL CA" (not verified)) by mx.ams1.isc.org (Postfix) with ESMTPS id 862615F989F; Tue,  2 Oct 2012 03:33:01 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (c211-30-172-21.carlnfd1.nsw.optusnet.com.au [211.30.172.21]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by bikeshed.isc.org (Postfix) with ESMTPSA id 88377216C3B; Tue,  2 Oct 2012 03:32:59 +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 AA10F283536B; Tue,  2 Oct 2012 13:32:53 +1000 (EST)
To: John C Klensin <john-ietf@jck.com>
From: Mark Andrews <marka@isc.org>
References: <20120930145325.21053.67854.idtracker@ietfa.amsl.com> <56DB6FE506A144D1183B93A8@JcK-HP8200.jck.com> <20121002022212.D7B2A282EC28@drugs.dv.isc.org> <818904DB9902CFA1AB4DCB8F@JcK-HP8200.jck.com>
Subject: Re: [dnsext] Last Call: <draft-ietf-dnsext-rfc2671bis-edns0-09.txt> (Extension Mechanisms for DNS (EDNS(0))) to Internet Standard
In-reply-to: Your message of "Mon, 01 Oct 2012 22:56:59 -0400." <818904DB9902CFA1AB4DCB8F@JcK-HP8200.jck.com>
Date: Tue, 02 Oct 2012 13:32:52 +1000
Message-Id: <20121002033253.AA10F283536B@drugs.dv.isc.org>
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: Tue, 02 Oct 2012 03:33:15 -0000

Closing the registry is not irreversable if it needs to be reversed.
It's not like we can forget that there were assigned code points
and anything that attempted to use those code points would have to
consider the fact that they were used at one time.

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

From john-ietf@jck.com  Tue Oct  2 08:09:34 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 D718021F84A0; Tue,  2 Oct 2012 08:09:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.585
X-Spam-Level: 
X-Spam-Status: No, score=-102.585 tagged_above=-999 required=5 tests=[AWL=0.014, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Gpj77GrGRO99; Tue,  2 Oct 2012 08:09:33 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 115A921F8471; Tue,  2 Oct 2012 08:09:33 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1TJ46G-0009Ze-21; Tue, 02 Oct 2012 11:09:32 -0400
Date: Tue, 02 Oct 2012 11:09:25 -0400
From: John C Klensin <john-ietf@jck.com>
To: Mark Andrews <marka@isc.org>
Subject: Re: [dnsext] Last Call: <draft-ietf-dnsext-rfc2671bis-edns0-09.txt> (Extension Mechanisms for DNS (EDNS(0))) to Internet Standard
Message-ID: <352FF2F3A9C6DE5B0203ABDD@JcK-HP8200.jck.com>
In-Reply-To: <20121002033253.AA10F283536B@drugs.dv.isc.org>
References: <20120930145325.21053.67854.idtracker@ietfa.amsl.com> <56DB6FE506A144D1183B93A8@JcK-HP8200.jck.com> <20121002022212.D7B2A282EC28@drugs.dv.isc.org> <818904DB9902CFA1AB4DCB8F@JcK-HP8200.jck.com> <20121002033253.AA10F283536B@drugs.dv.isc.org>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: ietf@ietf.org, 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: Tue, 02 Oct 2012 15:09:34 -0000

--On Tuesday, October 02, 2012 13:32 +1000 Mark Andrews
<marka@isc.org> wrote:

> Closing the registry is not irreversable if it needs to be
> reversed. It's not like we can forget that there were assigned
> code points and anything that attempted to use those code
> points would have to consider the fact that they were used at
> one time.

Actually, Mark, we very rarely close registries if there is any
possibility of reopening them.  We may raise the threshold for
registration, etc. (in this case, new types already require
standards action, which should make it adequately easy to head
off bad or frivolous ideas), but closing is a big step.  Telling
implementers that they don't need to pay attention to the
relevant codes and fields (and might even be able to use them
for a different, even if private, purpose) is an even more
serious step.

But I'd like to ask that this discussion move up a level.  My
question was about what the WG considered and whether, in the
light of those discussions, there was really justification to
take the serious step of abandoning a facility and consensus on
that justification.  It seems to me that your responses have
addressed different questions entirely: your opinion about
alternate approaches in the earlier note and a suggestion about
the possibility of reopening registries in this one. 

Because the questions I asked are tightly connected to what the
WG discussed and on what basis the presumably-consensus decision
was made, I would hope that I (and, more important, the IESG and
the community) would hear from the WG Chairs and other
participants, not only from someone who, coincidentally or not,
is part of the same organization as the three authors of the
draft (a draft that does not indicate the active participation
of any other people or organizations by the presence of an
Acknowledgments section).

best regards,
   john





From mccap@petoni.org  Mon Oct  1 15:56:23 2012
Return-Path: <mccap@petoni.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 D9D201F0D1D for <ietf@ietfa.amsl.com>; Mon,  1 Oct 2012 15:56:23 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XX3uutldchyy for <ietf@ietfa.amsl.com>; Mon,  1 Oct 2012 15:56:23 -0700 (PDT)
Received: from mail-gh0-f172.google.com (mail-gh0-f172.google.com [209.85.160.172]) by ietfa.amsl.com (Postfix) with ESMTP id 243F71F0CC4 for <ietf@ietf.org>; Mon,  1 Oct 2012 15:56:23 -0700 (PDT)
Received: by ghbg10 with SMTP id g10so1597438ghb.31 for <ietf@ietf.org>; Mon, 01 Oct 2012 15:56:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=petoni.org; s=google; h=mime-version:x-originating-ip:date:message-id:subject:from:to :content-type; bh=UFE5LyCFKB0mY8p57lA8WWS7RYArBq9NwAFBfODZkH0=; b=HJqkeustr/w0YuMYB8yXWf00WBSt09sau/gTVkoWIN5p0XptghA+aHfx8JWUire9h5 eeUXL31+i/wNoF19h4XTotYrD3MsLa8TciT673YKtr4sRK84MoIiCwXq/K7V6Cim5wmB IiS9XiBtB5ePJSzjEk+RB83a3FCIif8zlHA1o=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:date:message-id:subject:from:to :content-type:x-gm-message-state; bh=UFE5LyCFKB0mY8p57lA8WWS7RYArBq9NwAFBfODZkH0=; b=hgQYzhY1lTjuayvyiZr6kcgW7xm8glAgGGfDGIl1+uyzicVblRrUVBev4GnUSyOwLW VGEXOW1Xm7+R57klZEGaeXDTmpbfLR7VsqhEdJCxR+fBIV4jAamXZjJgm++pwSJM6PSN /fK5t2seMZ9i6XdBkMpUCO/dnqgms5Vak+6W2qVpuDZ3Hj5JAuiPyRVVIHWkfMskxDq9 6wAp6wNTKnmTavz6nb5Cl0nUYQakQpsYR4ThbZv34+1v7r3L7C8hDBISsaqofDjGhCLA 2yo+lQZkJj9jDSwzp06YxjPKKmzoySf7rOO7SIhbk5GJ8b2ZmzzLBbcCFGEpPNpDUiPO l7Rw==
MIME-Version: 1.0
Received: by 10.236.125.133 with SMTP id z5mr17039442yhh.121.1349132179501; Mon, 01 Oct 2012 15:56:19 -0700 (PDT)
Received: by 10.101.89.7 with HTTP; Mon, 1 Oct 2012 15:56:19 -0700 (PDT)
X-Originating-IP: [68.45.157.93]
Date: Mon, 1 Oct 2012 18:56:19 -0400
Message-ID: <CACvMsLG97q4Zvo-xQ=L_u6C_YCTAiTuOujFoyUsM1P+NY-prmA@mail.gmail.com>
Subject: Gen-ART Last Call Review of draft-ietf-sidr-pfx-validate-09
From: Pete McCann <mccap@petoni.org>
To: gen-art@ietf.org, draft-ietf-sidr-pfx-validate.all@tools.ietf.org,  ietf@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
X-Gm-Message-State: ALoCoQmZvyW78BEK3awlWqJgxxzKR+YibCSefAswgnNVE/r8eKK+6wQMxSLHGf6/td5Fc+lYVOno
X-Mailman-Approved-At: Tue, 02 Oct 2012 09:09:29 -0700
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Oct 2012 22:56:24 -0000

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at

<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

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

Document:  draft-ietf-sidr-pfx-validate-09
Reviewer:  Peter McCann
Review Date:  2012-10-01
IETF LC End Date:  2012-10-01
IESG Telechat date: unknown

Summary: Ready

Major issues: None

Minor issues:

Section 4:
    An "affected prefix" is any prefix that
   was matched by a deleted or updated mapping, or could be matched by
   an added mapping.
SHOULD BE:
   An "affected prefix" is any prefix that
   was matched by a deleted or updated mapping, or could be matched by
   an added or updated mapping.

Nits/editorial comments:

Abstract:
   monkey-in-the-middle
That's a game of keep-away.  Did you mean man-in-the-middle?  Perhaps
this is a technical term that has been discussed on the mailing list.

From sm@resistor.net  Tue Oct  2 10:37:21 2012
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 800B521F851E for <ietf@ietfa.amsl.com>; Tue,  2 Oct 2012 10:37:20 -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.006, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 50ccgb9BGAhn for <ietf@ietfa.amsl.com>; Tue,  2 Oct 2012 10:37:20 -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 D580621F84F1 for <ietf@ietf.org>; Tue,  2 Oct 2012 10:37:19 -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 q92HbDKl029665; Tue, 2 Oct 2012 10:37:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1349199438; bh=N81Xgd9QOVwYozfvdEPRqUpovD29Xo80OhO5TY58I3k=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=ia/CbwvpE/R5qwSJ4fnQu+o5yT21vVfhNJzv6wovK3ymRU5yEPtl7T4xLqPtL3DOH KgcJG7pcIODQ20h1/N1mBRHzNX8tKv2CBqMfIe+Vm0NFYu1O9XXkhBcgOzDbpPobPK /QubvqNxz7cneXCcWlEY4Cwf7MnFGv/GXcaTgEUo=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1349199438; i=@resistor.net; bh=N81Xgd9QOVwYozfvdEPRqUpovD29Xo80OhO5TY58I3k=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=2Zq66Jhe/4k3/8QXycP8rhbit5goasydAcJlVP1aJfC5VpxUMreqV0/AruEOX6XEO KeMiMCh+gsJFPnvRNIxsgTCn5J8dcPj+g7f9Uh5clNc3D5Ks8OgwHvL4uOQYId/J2g MoxS3nIKQ7HHCeGtF1rFb+v9mdJ1GzeIagNLJBvs=
Message-Id: <6.2.5.6.2.20121002085424.0a887e48@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 02 Oct 2012 10:31:47 -0700
To: ietf@ietf.org
From: SM <sm@resistor.net>
Subject: Re: [dnsext] Last Call: <draft-ietf-dnsext-rfc2671bis-edns0-09.txt> (Extension Mechanisms for DNS (EDNS(0))) to Internet Standard
In-Reply-To: <352FF2F3A9C6DE5B0203ABDD@JcK-HP8200.jck.com>
References: <20120930145325.21053.67854.idtracker@ietfa.amsl.com> <56DB6FE506A144D1183B93A8@JcK-HP8200.jck.com> <20121002022212.D7B2A282EC28@drugs.dv.isc.org> <818904DB9902CFA1AB4DCB8F@JcK-HP8200.jck.com> <20121002033253.AA10F283536B@drugs.dv.isc.org> <352FF2F3A9C6DE5B0203ABDD@JcK-HP8200.jck.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: John C Klensin <john-ietf@jck.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Oct 2012 17:37:21 -0000

At 08:09 02-10-2012, John C Klensin wrote:
>off bad or frivolous ideas), but closing is a big step.  Telling
>implementers that they don't need to pay attention to the
>relevant codes and fields (and might even be able to use them
>for a different, even if private, purpose) is an even more
>serious step.

Yes.

In Section 6.1.2:

   "OPTION-CODE
          Assigned by the Expert Review process as defined by the dnsext
          working group and the IESG."

It's odd to keep this defined by a working group which is being 
closed.  Section 9.1 does not provide much information.  One 
significant change in the draft is the inclusion of requirements for 
"middleboxes".  It's not mentioned under in Appendix A.2.

BTW, the RFC 2119 reference could be normative.

Regards,
-sm 


From ogud@ogud.com  Tue Oct  2 15:34:24 2012
Return-Path: <ogud@ogud.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 613FC21F85D5 for <ietf@ietfa.amsl.com>; Tue,  2 Oct 2012 15:34:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KUCYHXdJ0FfY for <ietf@ietfa.amsl.com>; Tue,  2 Oct 2012 15:34:18 -0700 (PDT)
Received: from smtp147.iad.emailsrvr.com (smtp147.iad.emailsrvr.com [207.97.245.147]) by ietfa.amsl.com (Postfix) with ESMTP id 9EA7F21F855A for <ietf@ietf.org>; Tue,  2 Oct 2012 15:34:18 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp24.relay.iad1a.emailsrvr.com (SMTP Server) with ESMTP id 10AC31A0411; Tue,  2 Oct 2012 18:34:18 -0400 (EDT)
X-Virus-Scanned: OK
Received: by smtp24.relay.iad1a.emailsrvr.com (Authenticated sender: ogud-AT-ogud.com) with ESMTPSA id A613E1A0480;  Tue,  2 Oct 2012 18:34:17 -0400 (EDT)
Message-ID: <506B6BE9.2000805@ogud.com>
Date: Tue, 02 Oct 2012 18:34:17 -0400
From: Olafur Gudmundsson <ogud@ogud.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120907 Thunderbird/15.0.1
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
Subject: Re: [dnsext] Last Call: <draft-ietf-dnsext-rfc2671bis-edns0-09.txt> (Extension	Mechanisms for DNS (EDNS(0))) to Internet Standard
References: <20120930145325.21053.67854.idtracker@ietfa.amsl.com> <56DB6FE506A144D1183B93A8@JcK-HP8200.jck.com> <506B01D1.9080708@ogud.com> <8F3DCBA9A3AF566810CD1061@JcK-HP8200.jck.com>
In-Reply-To: <8F3DCBA9A3AF566810CD1061@JcK-HP8200.jck.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: dnsext@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, 02 Oct 2012 22:34:24 -0000

My original message was not copied to ietf mailing list.

John quoted all of my text so I'm sending this follow-up to ietf as well 
as dnsext
mailing lists.


On 02/10/2012 12:38, John C Klensin wrote:
>
> --On Tuesday, October 02, 2012 11:01 -0400 Olafur Gudmundsson
> <ogud@ogud.com> wrote:
>
>> ...
>>>> The IESG has received a request from the DNS Extensions WG
>>>> (dnsext) to consider the following document: - 'Extension
>>>> Mechanisms for DNS (EDNS(0))'
>>>> <draft-ietf-dnsext-rfc2671bis-edns0-09.txt> as Internet
>>>> Standard
>> ...
>> John,
>> <no-hat>
>> We learned two main things from binary labels:
>> a) the specification of them caused expensive processing, and
>> the
>>      utility of binary labels w/o A6 record was none.
> Huh?  While I certainly agree that the binary label experiment
> failed, RFC 2673 didn't seem to me to have anything to do with
> A6 records and a quick review just now doesn't convince me
> otherwise.  As I recall, it came out of the period in which we
> were evolving to classless IPv4 addresses (with prefix
> lengths/netmasks on arbitrary bit boundaries) and was intended
> to permit address delegation entities to easily delegate ranges
> of reverse-mapping records to the appropriate address-holding
> entities for management.  The failure of that idea (for the
> reasons you outline) contributed, IMO, to PTR records being much
> less useful today than they were pre-CIDR.
>
> Conversely, if a significant reason for getting rid of binary
> labels was the link to A6 records, why doesn't the document just
> say "these existed solely to support A6 records, A6 records have
> been deprecated, therefore these are too".  All of us could be
> spared the discussion of why they failed relative to deployment
> issues, etc.  But the question of whether it is appropriate to
> get rid of label types would remain.
>
>> b) In order to introduce a new label type: All DNS
>> infrastructure
>>      needs to understand the new label type before it is can be
>>      reliability used. Lots of DNS processing elements barf at
>> labels that
>>      they do not expect. For example number of firewalls drop
>> answers
>>      if the name of the first answer record is not compressed (a
>>      protocol violation)
> Understood.  Of course, some of the same things could be said
> about EDNS0 itself.
>
>> Based on this experience the DNSEXT felt that the best message
>> to send
>> out is new label types do not work, in the current Internet.
>> Deploying a new label type requires an effort similar to what
>> we are
>> going through right now with DNSSEC, upgrade all DNS protocol
>> processing elements, plus systems and processes that feed and
>> operate the DNS systems.
> But, coming back to my example, this is exactly the problem with
> internationalization.  If one is willing to settle for keeping
> ASCII primary and applying a hack to accommodate non-ASCII
> characters, then one can avoid that very long and expensive
> transition effort.  We have such a solution in IDNA.  Some parts
> of the external community (including, albeit largely for
> historical reasons, a couple of very significant vendors) do not
> believe that is a satisfactory solution and that it would be
> better to have all characters that are considered valid treated
> equally.
>
> That puts your DNSSEC comparison into an interesting light.  I
> believe that, when the DNSSEC effort started, the community
> would have been appalled at how long deployment would take and
> how painful it would be (with or without allowances were made
> for reduced expectations).  But, as far as I know, we didn't
> have a good alternative way to do the job even in retrospect,
> so, presumably, the community decided that the pain and slow
> deployment associated with DNSSEC was (and is) worth it. Is a
> clean i18n model on a par with that?  I don't know (and I'm
> personally willing to live with IDNA forever if we have to).
> But I'm sure that some people would be willing to make the case
> that such an i18n model is at least as important as DNSSEC and
> worth whatever effort it would take.
>
> As I've tried to say to Mark, based on the experience with
> binary labels, I would have no problem if the document
> deprecated binary labels, noted that deployment of different
> label types is horrendously difficult and/or very slow and hence
> not recommended unless the requirement is really important and
> there are no plausible alternatives, and then just moved on.
> There just doesn't seem to be nearly enough documented support
> for moving beyond "we had a bad experience" to "completely
> discard the feature/ capability".
>
> I also note that part of what you said is "...do not work, in
> the current Internet".  I'm not sure what that means.  If it
> means that the WG has reached the conclusion that there are some
> set of possible extensions that are sufficiently problematic
> (including different label interpretation models) that they are
> simply incompatible with the current DNS, i.e., that those who
> want them should be working on a plausible strategy for what is
> variously called DNSng or DNS2, I think that would be great and
> an extremely useful contribution, especially as expectations for
> things that DNS should do/support that lie well outside the
> original design assumptions continue to increase... but the
> document doesn't say that, much less describe that boundary.

Well as if DNS has reached some limits to extensibility this document 
points out the
label types. Talking about other limitations is outside the documents 
scope.


>> Personally at the time of introduction of the label registry I
>> thought
>> it was a good idea, but operational realities demonstrated
>> that its time
>> had passed, i.e. if we had defined more label types in
>> RFC1034/5 then
>> there might have been a chance. But given how many
>> implementations are
>> based on coding against what that implementor sees in traffic
>> dumps
>> rather than what is in the RFC's makes extending DNS much
>> harder than it should be, upgrading the installed base takes
>> decades.
> Absolutely.  But those same comments couple be an argument for
> closing EDS down entirely except for the facilities needed to
> support DNSSEC and maybe DNAME, i.e., "closing the registries"
> as far as new options, header flags, etc., are concerned.   What
> you've said is a strong argument for caution, but I'm trying to
> understand what makes label types so special as to require this
> special treatment and to either get that understanding into the
> document or to back away from the drastic measure.

Labels only work when all the severs for a zone that has a new label type,
in ADDITION sufficient fraction servers in all zones above that zone 
MUST understand the new
label type.
in ADDITION all resolvers uses MUST understand the label type or treat 
it as unknown
label type.

This is even harder problem than DNSSEC as it was possible to fetch data 
via most resolvers
and configure local trust anchors or use TAR/DLV to create islands of 
trust.

Olafur


>> <dnsext-chair-hat=on>
>> <document-shepard-hat=on>
>>
>> If you think the text in the document does not reflect the
>> lessons
>> learned strongly enough I will be happy work with you on
>> putting better text in the document.


From marka@isc.org  Tue Oct  2 18:16: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 DF23821F8588; Tue,  2 Oct 2012 18:16:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pIdXdKasC812; Tue,  2 Oct 2012 18:16:13 -0700 (PDT)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [IPv6:2001:500:60::65]) by ietfa.amsl.com (Postfix) with ESMTP id 609E321F8574; Tue,  2 Oct 2012 18:16:13 -0700 (PDT)
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mail.isc.org", Issuer "RapidSSL CA" (not verified)) by mx.ams1.isc.org (Postfix) with ESMTPS id 4D39C5F99EB; Wed,  3 Oct 2012 01:16:02 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (unknown [IPv6:2001:470:1f00:820:a001:3387:3ce7:5925]) (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 74A37216C59; Wed,  3 Oct 2012 01:16: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 526A82873A5E; Wed,  3 Oct 2012 11:15:56 +1000 (EST)
To: Olafur Gudmundsson <ogud@ogud.com>
From: Mark Andrews <marka@isc.org>
References: <20120930145325.21053.67854.idtracker@ietfa.amsl.com> <56DB6FE506A144D1183B93A8@JcK-HP8200.jck.com> <506B01D1.9080708@ogud.com> <8F3DCBA9A3AF566810CD1061@JcK-HP8200.jck.com> <506B6BE9.2000805@ogud.com>
Subject: Re: [dnsext] Last Call: <draft-ietf-dnsext-rfc2671bis-edns0-09.txt> (Extension Mechanisms for DNS (EDNS(0))) to Internet Standard
In-reply-to: Your message of "Tue, 02 Oct 2012 18:34:17 -0400." <506B6BE9.2000805@ogud.com>
Date: Wed, 03 Oct 2012 11:15:56 +1000
Message-Id: <20121003011556.526A82873A5E@drugs.dv.isc.org>
Cc: John C Klensin <john-ietf@jck.com>, dnsext@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, 03 Oct 2012 01:16:14 -0000

> Labels only work when all the severs for a zone that has a new label type,
> in ADDITION sufficient fraction servers in all zones above that zone 
> MUST understand the new
> label type.

Not true. Binary labels could have been made to work by removing
the left hand label until the remaining suffix consisted of only
RFC 1035 labels, looking up the servers for that domain, then
resuming query processing using those servers similar to what we
do with DS lookups.

Such processing would be required for any new label type used in a
QNAME and would be a significant change to the standard query logic.

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

From sm@resistor.net  Wed Oct  3 00:16:15 2012
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9D31A21F86AB for <ietf@ietfa.amsl.com>; Wed,  3 Oct 2012 00:16:15 -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.006, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Rt-mKyVoV+ht for <ietf@ietfa.amsl.com>; Wed,  3 Oct 2012 00:16:14 -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 9817021F865B for <ietf@ietf.org>; Wed,  3 Oct 2012 00:16:14 -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 q937G9NG008447 for <ietf@ietf.org>; Wed, 3 Oct 2012 00:16:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1349248573; bh=+pf//ijI++OP+WXf/kxVw34/eupUbXQpV7WHiJ2nKso=; h=Date:To:From:Subject:In-Reply-To:References:Cc; b=fBvHSweNEapeWd2ccKIAZv9Bwq6URlb19r28l+zkJhj8RUtPRql0sJIrsfc2CZnhZ 1OWIe5N56CuH4OwrB7cJb7hmiV5Jk9meyvkqpE/yz5yiJajpW1fLU0kKxXwptzT3GZ YWytXON0OEVCuNE1kwWl8YFZFsBAOHf/aJbgwN7g=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1349248573; i=@resistor.net; bh=+pf//ijI++OP+WXf/kxVw34/eupUbXQpV7WHiJ2nKso=; h=Date:To:From:Subject:In-Reply-To:References:Cc; b=yhWhoO9vXYABOwuEspv9/GIOSLsLb1tm36mqUnpAXkHWgObcnaYgoBJ3EKG/pk6Ts LW91RFccTQkl5KwUxokg+ev4ZMB83Mo3L0NGqC3knWPq/XI4hiI40fT6nRltpdXPsv 5rzIaFgry6Kt8g8NMjEw6+ogdoAiAJIV3+sDULGg=
Message-Id: <6.2.5.6.2.20121002215133.0a563910@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 02 Oct 2012 23:39:20 -0700
To: ietf@ietf.org
From: SM <sm@resistor.net>
Subject: Re: [dnsext] Last Call: <draft-ietf-dnsext-rfc2671bis-edns0-09.txt> (Extension	Mechanisms for DNS (EDNS(0))) to Internet Standard
In-Reply-To: <506B6BE9.2000805@ogud.com>
References: <20120930145325.21053.67854.idtracker@ietfa.amsl.com> <56DB6FE506A144D1183B93A8@JcK-HP8200.jck.com> <506B01D1.9080708@ogud.com> <8F3DCBA9A3AF566810CD1061@JcK-HP8200.jck.com> <506B6BE9.2000805@ogud.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Oct 2012 07:16:15 -0000

 From Section 7 of the draft:

  "Responders which choose not to implement the protocol extensions
   defined in this document MUST respond with a return code (RCODE) of
   FORMERR to messages containing an OPT RR in the additional section
   and MUST NOT include an OPT record in the response."

That looks like a change [1] to STD 13.  Responders which respond 
with a return code of 4 would not be compliant.

On publication of draft-ietf-dnsext-rfc2671bis-edns0-09, will it be 
part of STD 13?

 From RFC 3225:

   "In the event a server returns a NOTIMP, FORMERR or SERVFAIL response
    to a query that has the DO bit set, the resolver SHOULD NOT expect
    DNSSEC security RRs and SHOULD retry the query without EDNS0 in
    accordance with section 5.3 of [RFC2671]."

There's a normative reference [2] to that RFC in this draft.

In Section 1:

  "This document deprecates Extended Labels, and therefore Binary Labels,
    obsoleting [RFC2673]."

draft-ietf-dnsext-rfc6195bis-04 mentions that:

  "The Binary label type is Historic [RFC2671bis]."

The IETF might wish to consider whether it is necessary to align the 
text in the two drafts.

Regards,
-sm

1. Whether it is a change or not depends upon how one reads RFC 
6410.  The write-up mentions that there are no unused features in the 
specification that greatly increase implementation complexity.  It is 
unclear whether this document is a minor revision of RFC 2671.

2. http://www.ietf.org/mail-archive/web/weirds/current/msg01668.html


From john-ietf@jck.com  Wed Oct  3 05:10:52 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 8748021F86B8; Wed,  3 Oct 2012 05:10:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.421
X-Spam-Level: 
X-Spam-Status: No, score=-102.421 tagged_above=-999 required=5 tests=[AWL=-0.122, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MhrJEpS+SHWX; Wed,  3 Oct 2012 05:10:51 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id BA31F21F86BD; Wed,  3 Oct 2012 05:10:51 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1TJNmo-000C7p-Dh; Wed, 03 Oct 2012 08:10:46 -0400
Date: Wed, 03 Oct 2012 08:10:41 -0400
From: John C Klensin <john-ietf@jck.com>
To: =?UTF-8?Q?Jo=C3=A3o_Damas?= <joao@bondis.org>, Mark Andrews <marka@isc.org>
Subject: Re: [dnsext] Last Call: <draft-ietf-dnsext-rfc2671bis-edns0-09.txt> (Extension Mechanisms for DNS (EDNS(0))) to Internet Standard
Message-ID: <396CFDC14B6FEF29A37A2FFF@JcK-HP8200.jck.com>
In-Reply-To: <84187E41-0CEC-4CA2-801D-5AB1171FFF9B@bondis.org>
References: <20120930145325.21053.67854.idtracker@ietfa.amsl.com> <56DB6FE506A144D1183B93A8@JcK-HP8200.jck.com> <506B01D1.9080708@ogud.com> <8F3DCBA9A3AF566810CD1061@JcK-HP8200.jck.com> <506B6BE9.2000805@ogud.com> <20121003011556.526A82873A5E@drugs.dv.isc.org> <84187E41-0CEC-4CA2-801D-5AB1171FFF9B@bondis.org>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Cc: dnsext@ietf.org, Olafur Gudmundsson <ogud@ogud.com>, 'IETF-Discussion list' <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Oct 2012 12:10:52 -0000

--On Wednesday, October 03, 2012 10:43 +0200 Jo=C3=A3o Damas
<joao@bondis.org> wrote:

> I believe you are saying the same things when you are both
> saying that for this to work there may be more than one way to
> do it but all options require completely new functionality in
> implementations (either by implementing support for new labels
> types or by implementing new fall back behavior). The
> conclusion is still the same.

Hmm.  I'm not completely sure who "you" was intended to include,
but my conclusion from the above is that there is no substantial
justification for eliminating, at this time, a capability that
might prove better on balance when and if new capabilities are
considered and tradeoffs evaluated.

To summarize my perspective on this as of now:

(1) No one is making a case for retaining binary labels

(2) The case has not been made, at least in the document, for
eliminating label types.  An argument that there are other ways
to do a particular type of label is not persuasive unless there
is a comprehensive and written analysis of what other labels
might be considered and what the tradeoffs among approaches
would be.  And an argument that almost any significant added
functionality would be very slow and costly to deploy may be an
argument for not approving such functionality, but it is not an
argument for eliminating one, but not all, of the underlying
capabilities.

IMO, this discussion has turned up two ways in which the case
for eliminating the possibility of additional label types could
be made:

(2.1) Demonstrating that simply having the capability defined
and available in principle is somehow harmful.

(2.2) The WG has consensus on a bright line that defines the
nature of proposals that would require going to DNSng rather
than EDNSx-type extensions to the current model, has concluded
that any extensions or alterations to the label definition of
1034/1035 would require crossing that line, and is prepared to
document that line and get IETF consensus on it (either as part
of this document or one normatively referenced from it).

best,
    john


From john-ietf@jck.com  Wed Oct  3 05:17:22 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 3275521F86C4 for <ietf@ietfa.amsl.com>; Wed,  3 Oct 2012 05:17:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.569
X-Spam-Level: 
X-Spam-Status: No, score=-102.569 tagged_above=-999 required=5 tests=[AWL=0.030, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6ETY9fJyidkX for <ietf@ietfa.amsl.com>; Wed,  3 Oct 2012 05:17:21 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 93A6E21F8652 for <ietf@ietf.org>; Wed,  3 Oct 2012 05:17:21 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1TJNt9-000C8m-7u; Wed, 03 Oct 2012 08:17:19 -0400
Date: Wed, 03 Oct 2012 08:17:13 -0400
From: John C Klensin <john-ietf@jck.com>
To: SM <sm@resistor.net>
Subject: Re: [dnsext] Last Call:	<draft-ietf-dnsext-rfc2671bis-edns0-09.txt> (Extension	Mechanisms for	DNS (EDNS(0))) to Internet Standard
Message-ID: <4A0451148D607972CC7ADE24@JcK-HP8200.jck.com>
In-Reply-To: <6.2.5.6.2.20121002215133.0a563910@resistor.net>
References: <20120930145325.21053.67854.idtracker@ietfa.amsl.com> <56DB6FE506A144D1183B93A8@JcK-HP8200.jck.com> <506B01D1.9080708@ogud.com> <8F3DCBA9A3AF566810CD1061@JcK-HP8200.jck.com> <506B6BE9.2000805@ogud.com> <6.2.5.6.2.20121002215133.0a563910@resistor.net>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Oct 2012 12:17:22 -0000

--On Tuesday, October 02, 2012 23:39 -0700 SM <sm@resistor.net>
wrote:

>  From Section 7 of the draft:
> 
>   "Responders which choose not to implement the protocol
> extensions
>    defined in this document MUST respond with a return code
> (RCODE) of
>    FORMERR to messages containing an OPT RR in the additional
> section
>    and MUST NOT include an OPT record in the response."
> 
> That looks like a change [1] to STD 13.  Responders which
> respond with a return code of 4 would not be compliant.
>...
> The IETF might wish to consider whether it is necessary to
> align the text in the two drafts.
>...

One observation on this part of the thread...

While I'm much more concerned about the substantive impact of
deprecating a possibly-useful (even if painful to use) feature
without adequate justification and documentation, I believe that
documents being processed for classification as Internet
Standard should be held to a very high standard for editorial
quality and clarity and consistency of relationships to other
specifications.  If others agree with that belief, SM's analysis
appears to represent a strong case that the current version of
this draft (and possibly draft-ietf-dnsext-rfc6195bis-04) are
not ready for prime time.

   best,
    john



From peter@akayla.com  Tue Oct  2 16:49:39 2012
Return-Path: <peter@akayla.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BB54C21F860B; Tue,  2 Oct 2012 16:49:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KWb+dGoseKBF; Tue,  2 Oct 2012 16:49:39 -0700 (PDT)
Received: from p3plsmtpa06-05.prod.phx3.secureserver.net (p3plsmtpa06-05.prod.phx3.secureserver.net [173.201.192.106]) by ietfa.amsl.com (Postfix) with ESMTP id 1BC9321F8608; Tue,  2 Oct 2012 16:49:39 -0700 (PDT)
Received: from spectre ([173.8.184.78]) by p3plsmtpa06-05.prod.phx3.secureserver.net with  id 6Ppd1k00G1huGat01PpeKF; Tue, 02 Oct 2012 16:49:38 -0700
From: "Peter Yee" <peter@akayla.com>
To: <draft-ietf-6man-udpchecksums.all@tools.ietf.org>
Subject: Gen-ART review of draft-ietf-6man-udpchecksums-04
Date: Tue, 2 Oct 2012 16:49:43 -0700
Message-ID: <002e01cda0f8$98f8d3f0$caea7bd0$@akayla.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac2g8orrJo+0BFndRS2G2P+THDWYgQ==
Content-Language: en-us
X-Mailman-Approved-At: Wed, 03 Oct 2012 08:33:30 -0700
Cc: gen-art@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Oct 2012 23:49:39 -0000

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>

Document: draft-ietf-6man-udpchecksums-04
Reviewer: Peter Yee
Review Date: Sep-30-2012
IETF LC End Date: Oct-2-2012
IESG Telechat date: Oct-11-2012

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

Presuming the assumptions in I-D.ietf-6man-udpzero are valid and agreed to
by the community, this document
provides an update to 2460 to allow the use of zero checksum UDP packets
over IPv6 in certain cases involving
protocols tunneled inside of UDP packets.

Nits:

General: references throughout the document to various Internet Drafts will,
of course, need to be cleaned up.

General: a comma after "e.g." is preferred in American English.

Abstract, last sentence: "defines" -> "define"

Section 3, first sentence: "tunnelled" -> "tunneled"
	Change the comma after "checksum" to a period to split the sentence,
capitalizing the following "there".
	Then change "compute" -> "computing" and "check" -> "checking" for
parseability.

Section 3, last sentence: "cost, " -> "cost".

Section 4, 4th paragraph: "The below" -> "The points below"
	Also: "an UDP" -> "a UDP"

Section 4, 1st bullet item, last sentence: "reception UDP" -> "reception of
UDP"

Section 4, 4th bullet item, 1st sentence: "port, destination" -> "port, and
destination"
	Also: "fields :" -> "fields:" (eliminate a superfluous space
character)

Section 5, paragraph 5 (the replacement text), last sentence: you refer to
RFC 2460.  That
would seem to read oddly when the replacement text is actually inserted into
RFC 2460.
I think it would be preferable to put in a specific cross-reference to where
in 2460 the
existing method resides instead of the document itself.

Section 5, item 2, last sentence: "call," -> "call"

Section 5, item 5, 1st sentence: "UDP Tunnels" -> "UDP tunnels" for
consistency.

Section 5, item 6, 2 occurrences: "Non-IP" -> "non-IP"

Section 5, item 8, parenthetical: " Necessary" -> "necessary".  Note the
leading space before
"Necessary" that is omitted in the replacement.

Section 8 includes one incredibly long run-on sentence.  I would suggest
splitting it as follows:

However, this does not lead to any significant new vulnerabilities as
checksums are not a
security measure and can be easily generated by any attacker. Properly
configured tunnels
should check the validity of the inner packet and perform any needed
security checks
regardless of the checksum status. Most attacks are generated from
compromised hosts
which automatically create checksummed packets (in other words, it would
generally be
more, not less, effort for most attackers to generate zero UDP checksums on
the host).

Authors' Addresses:
Unused Fax and URI fields may be omitted.
Phone numbers  should be presented in international dialing format to
facilitate use, e.g.,
+1 703 501 4376 and +46 10 714 82 87.





From Malcolm.BETTS@zte.com.cn  Wed Oct  3 13:01:38 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 EE54821F8440 for <ietf@ietfa.amsl.com>; Wed,  3 Oct 2012 13:01:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.178
X-Spam-Level: 
X-Spam-Status: No, score=-102.178 tagged_above=-999 required=5 tests=[AWL=0.421, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6Tf1y+MqMCfA for <ietf@ietfa.amsl.com>; Wed,  3 Oct 2012 13:01:37 -0700 (PDT)
Received: from zte.com.cn (mx5.zte.com.cn [63.217.80.70]) by ietfa.amsl.com (Postfix) with ESMTP id 6504321F8447 for <ietf@ietf.org>; Wed,  3 Oct 2012 13:01:37 -0700 (PDT)
Received: from mse01.zte.com.cn (unknown [10.30.3.20]) by Websense Email Security Gateway with ESMTPS id 091A112699B4 for <ietf@ietf.org>; Thu,  4 Oct 2012 03:54:30 +0800 (CST)
Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse01.zte.com.cn with ESMTP id q93K1L73028669 for <ietf@ietf.org>; Thu, 4 Oct 2012 04:01:21 +0800 (GMT-8) (envelope-from Malcolm.BETTS@zte.com.cn)
Subject: MalcolmBETTS90013533 is out of the office.
Auto-Submitted: auto-generated
From: Malcolm.BETTS@zte.com.cn
To: ietf@ietf.org
Message-ID: <OFC5D16B34.AFBF6411-ON48257A8C.006DFB17-48257A8C.006DFB17@zte.com.cn>
Date: Thu, 4 Oct 2012 04:01:17 +0800
X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 8.5.3FP1 HF212|May 23, 2012) at 2012-10-04 04:01:18
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
X-MAIL: mse01.zte.com.cn q93K1L73028669
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Oct 2012 20:01:38 -0000

I will be out of the office starting  03/10/2012 and will not return until
22/10/2012.

I will not have access to email, I will respond to your message when I
return on October 22nd.


From rbarnes@bbn.com  Wed Oct  3 14:11:48 2012
Return-Path: <rbarnes@bbn.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 04F431F0C49; Wed,  3 Oct 2012 14:11:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.504
X-Spam-Level: 
X-Spam-Status: No, score=-106.504 tagged_above=-999 required=5 tests=[AWL=0.095, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uq5jF8Evpyw4; Wed,  3 Oct 2012 14:11:42 -0700 (PDT)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.0.80]) by ietfa.amsl.com (Postfix) with ESMTP id 2E6191F0421; Wed,  3 Oct 2012 14:11:42 -0700 (PDT)
Received: from ros-dhcp192-1-51-103.bbn.com ([192.1.51.103]:60631) by smtp.bbn.com with esmtps (TLSv1:AES128-SHA:128) (Exim 4.77 (FreeBSD)) (envelope-from <rbarnes@bbn.com>) id 1TJWE6-000Fjh-MP; Wed, 03 Oct 2012 17:11:30 -0400
From: Richard Barnes <rbarnes@bbn.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: secdir review of draft-ietf-abfab-gss-eap-naming-05
Date: Wed, 3 Oct 2012 17:11:30 -0400
Message-Id: <65E7D30E-A5B2-4980-BB9F-9784AF7FF89F@bbn.com>
To: SECDIR <secdir@ietf.org>, IESG IESG <iesg@ietf.org>, IETF discussion list <ietf@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1283)
X-Mailer: Apple Mail (2.1283)
Cc: draft-ietf-abfab-gss-eap-naming@tools.ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Oct 2012 21:11:48 -0000

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

This document defines a method for assigning names to information from =
RADIUS and GSS-EAP, in particular SAML attributes received via the =
latter.

The security considerations in this document are difficult to evaluate =
because the general architecture is unclear to me, e.g., who attaches =
these names to things and who reads them.  (The naming scheme itself =
seems well defined.)  The text that causes me concern is the following:
"
These names MUST NOT be used for attributes issued by a party other than =
one closely associated with the source of credentials unless the source =
of credentials is re-asserting these attributes.
"
The use of "MUST NOT" here implies that the intent is for the =
application reading attributes to have assurance that they are "closely =
associated with the source".  However, the application has no way of =
verifying whether this MUST NOT has been adhered to, so the entity =
setting names is trusted in this regard.  The document should note this, =
and the corresponding risk that the namer will break this MUST NOT.  =
This risk is hard for the reader to evaluate because (AFAICT) the =
document doesn't specify who sets names in this system.  (Passive voice =
considered harmful.) =20

If the names did not have this implied security semantic, then the =
identity of the namer wouldn't be an issue.  Then this document could =
just define the format of the names and move on.

This is a nonsense MUST: "a service MUST make a policy decision"

Editorial:
Page 7: "thatwe know"
Page 8: "MAy be absent" (or is this an update to RFC 2119?  :) )
Page 11: "mechansisms are permitted"
Page 13: "Sam hartman"




From hartmans@mit.edu  Wed Oct  3 14:45:53 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 D61DC1F0C4C; Wed,  3 Oct 2012 14:45:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -96.875
X-Spam-Level: 
X-Spam-Status: No, score=-96.875 tagged_above=-999 required=5 tests=[AWL=-1.163, BAYES_00=-2.599, FH_HELO_EQ_D_D_D_D=1.597, FH_HOST_EQ_D_D_D_D=0.765, FM_DDDD_TIMES_2=1.999, HELO_DYNAMIC_IPADDR=2.426, RDNS_DYNAMIC=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id T8tr1FBVp4Zf; Wed,  3 Oct 2012 14:45:53 -0700 (PDT)
Received: from ec2-23-21-227-93.compute-1.amazonaws.com (ec2-23-21-227-93.compute-1.amazonaws.com [23.21.227.93]) by ietfa.amsl.com (Postfix) with ESMTP id 58ED81F0421; Wed,  3 Oct 2012 14:45:52 -0700 (PDT)
Received: from carter-zimmerman.suchdamage.org (c-98-217-126-210.hsd1.ma.comcast.net [98.217.126.210]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.suchdamage.org (Postfix) with ESMTPS id 6783720183; Wed,  3 Oct 2012 17:45:39 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 2F644414A; Wed,  3 Oct 2012 17:45:42 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: Richard Barnes <rbarnes@bbn.com>
Subject: Re: secdir review of draft-ietf-abfab-gss-eap-naming-05
References: <65E7D30E-A5B2-4980-BB9F-9784AF7FF89F@bbn.com>
Date: Wed, 03 Oct 2012 17:45:42 -0400
In-Reply-To: <65E7D30E-A5B2-4980-BB9F-9784AF7FF89F@bbn.com> (Richard Barnes's message of "Wed, 3 Oct 2012 17:11:30 -0400")
Message-ID: <tsld30zjkl5.fsf@mit.edu>
User-Agent: Gnus/5.110009 (No Gnus v0.9) Emacs/22.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: IETF discussion list <ietf@ietf.org>, IESG IESG <iesg@ietf.org>, draft-ietf-abfab-gss-eap-naming@tools.ietf.org, SECDIR <secdir@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Oct 2012 21:45:54 -0000

>>>>> "Richard" == Richard Barnes <rbarnes@bbn.com> writes:

    Richard> I have reviewed this document as part of the security
    Richard> directorate's ongoing effort to review all IETF documents
    Richard> being processed by the IESG.  These comments were written
    Richard> primarily for the benefit of the security area directors.
    Richard> Document editors and WG chairs should treat these comments
    Richard> just like any other last call comments.
    Richard> text that causes me concern is the following: " These names
    Richard> MUST NOT be used for attributes issued by a party other
    Richard> than one closely associated with the source of credentials
    Richard> unless the source of credentials is re-asserting these
    Richard> attributes.  " The use of "MUST NOT" here implies that the
    Richard> intent is for the application reading attributes to have
    Richard> assurance that they are "closely associated with the
    Richard> source".  However, the application has no way of verifying
    Richard> whether this MUST NOT has been adhered to, so the entity
    Richard> setting names is trusted in this regard.  The document
    Richard> should note this, and the corresponding risk that the namer
    Richard> will break this MUST NOT.  This risk is hard for the reader
    Richard> to evaluate because (AFAICT) the document doesn't specify
    Richard> who sets names in this system.  (Passive voice considered
    Richard> harmful.)

Yeah, we need more clarity around that as everyone who reads the
document brings up this issue.  I think it's OK because enforcing that
MUST NOT is a spec design issue in draft-ietf-abfab-aaa-saml, and a
couple of drafts in kitten.  I.E. if the IETF does its job, then
applications can depend on that MUST NOT being enforced.  We need to
make it more clear and we need to be careful when reviewing those other
specs.

So, I'll work on proposing text for this, but I think this is a clarity
issue rather than a security problem.

From ogud@ogud.com  Thu Oct  4 09:51:43 2012
Return-Path: <ogud@ogud.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F11FD21F86F4 for <ietf@ietfa.amsl.com>; Thu,  4 Oct 2012 09:51:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NHHZMLCY7hP8 for <ietf@ietfa.amsl.com>; Thu,  4 Oct 2012 09:51:42 -0700 (PDT)
Received: from smtp117.iad.emailsrvr.com (smtp117.iad.emailsrvr.com [207.97.245.117]) by ietfa.amsl.com (Postfix) with ESMTP id 6EC2321F84F9 for <ietf@ietf.org>; Thu,  4 Oct 2012 09:51:42 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp51.relay.iad1a.emailsrvr.com (SMTP Server) with ESMTP id CC0FF200B1; Thu,  4 Oct 2012 12:51:41 -0400 (EDT)
X-Virus-Scanned: OK
Received: by smtp51.relay.iad1a.emailsrvr.com (Authenticated sender: ogud-AT-ogud.com) with ESMTPSA id A116C20118;  Thu,  4 Oct 2012 12:51:40 -0400 (EDT)
Message-ID: <506DBE9B.3070209@ogud.com>
Date: Thu, 04 Oct 2012 12:51:39 -0400
From: Olafur Gudmundsson <ogud@ogud.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120907 Thunderbird/15.0.1
MIME-Version: 1.0
To: Mark Andrews <marka@isc.org>
Subject: Re: [dnsext] Last Call: <draft-ietf-dnsext-rfc2671bis-edns0-09.txt> (Extension Mechanisms for DNS (EDNS(0))) to Internet Standard
References: <20120930145325.21053.67854.idtracker@ietfa.amsl.com> <56DB6FE506A144D1183B93A8@JcK-HP8200.jck.com> <506B01D1.9080708@ogud.com> <8F3DCBA9A3AF566810CD1061@JcK-HP8200.jck.com> <506B6BE9.2000805@ogud.com> <20121003011556.526A82873A5E@drugs.dv.isc.org>
In-Reply-To: <20121003011556.526A82873A5E@drugs.dv.isc.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: John C Klensin <john-ietf@jck.com>, dnsext@ietf.org, 'IETF-Discussion list' <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Oct 2012 16:51:43 -0000

On 02/10/2012 21:15, Mark Andrews wrote:
>> Labels only work when all the severs for a zone that has a new label type,
>> in ADDITION sufficient fraction servers in all zones above that zone
>> MUST understand the new
>> label type.
>
> Not true. Binary labels could have been made to work by removing
> the left hand label until the remaining suffix consisted of only
> RFC 1035 labels, looking up the servers for that domain, then
> resuming query processing using those servers similar to what we
> do with DS lookups.
>
> Such processing would be required for any new label type used in a
> QNAME and would be a significant change to the standard query logic.
>
> Mark
>

Mark,

This will only work if all the recursive resolvers that "consumers" for
this new label types have been updated AND the new label type is the 
left most label(s) in the name.


Olafur


From hartmans@mit.edu  Thu Oct  4 14:06: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 8C45311E80A3; Thu,  4 Oct 2012 14:06:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -96.832
X-Spam-Level: 
X-Spam-Status: No, score=-96.832 tagged_above=-999 required=5 tests=[AWL=-1.120, BAYES_00=-2.599, FH_HELO_EQ_D_D_D_D=1.597, FH_HOST_EQ_D_D_D_D=0.765, FM_DDDD_TIMES_2=1.999, HELO_DYNAMIC_IPADDR=2.426, RDNS_DYNAMIC=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 85GFcdWQyoJz; Thu,  4 Oct 2012 14:06:32 -0700 (PDT)
Received: from ec2-23-21-227-93.compute-1.amazonaws.com (ec2-23-21-227-93.compute-1.amazonaws.com [23.21.227.93]) by ietfa.amsl.com (Postfix) with ESMTP id EAD7611E809A; Thu,  4 Oct 2012 14:06:31 -0700 (PDT)
Received: from carter-zimmerman.suchdamage.org (c-98-217-126-210.hsd1.ma.comcast.net [98.217.126.210]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.suchdamage.org (Postfix) with ESMTPS id 55FED2010F; Thu,  4 Oct 2012 17:06:18 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 19ECE414A; Thu,  4 Oct 2012 17:06:19 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: Richard Barnes <rbarnes@bbn.com>
Subject: Re: secdir review of draft-ietf-abfab-gss-eap-naming-05
References: <65E7D30E-A5B2-4980-BB9F-9784AF7FF89F@bbn.com>
Date: Thu, 04 Oct 2012 17:06:19 -0400
In-Reply-To: <65E7D30E-A5B2-4980-BB9F-9784AF7FF89F@bbn.com> (Richard Barnes's message of "Wed, 3 Oct 2012 17:11:30 -0400")
Message-ID: <tslr4pec5h0.fsf@mit.edu>
User-Agent: Gnus/5.110009 (No Gnus v0.9) Emacs/22.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: IETF discussion list <ietf@ietf.org>, IESG IESG <iesg@ietf.org>, draft-ietf-abfab-gss-eap-naming@tools.ietf.org, SECDIR <secdir@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Oct 2012 21:06:35 -0000

>>>>> "Richard" == Richard Barnes <rbarnes@bbn.com> writes:

    Richard> The security considerations in this document are difficult
    Richard> to evaluate because the general architecture is unclear to
    Richard> me, e.g., who attaches these names to things and who reads
    Richard> them.  (The naming scheme itself seems well defined.)  The
    Richard> text that causes me concern is the following: " These names
    Richard> MUST NOT be used for attributes issued by a party other
    Richard> than one closely associated with the source of credentials
    Richard> unless the source of credentials is re-asserting these
    Richard> attributes.  " The use of "MUST NOT" here implies that the
    Richard> intent is for the application reading attributes to have
    Richard> assurance that they are "closely associated with the
    Richard> source".  However, the application has no way of verifying
    Richard> whether this MUST NOT has been adhered to, so the entity
    Richard> setting names is trusted in this regard.  The document
    Richard> should note this, and the corresponding risk that the namer
    Richard> will break this MUST NOT.  This risk is hard for the reader
    Richard> to evaluate because (AFAICT) the document doesn't specify
    Richard> who sets names in this system.  (Passive voice considered
    Richard> harmful.)

I'd like to push back on this.
Text was adding in 05 making it clear that  in designing mechanisms
specifications we need to enforce that MUST not.
The full paragraph in question is as follows:

   These names MUST NOT be used for attributes issued by a party other
   than one closely associated with the source of credentials unless the
   source of credentials is re-asserting the attributes.  For example, a
   source of credentials can consult whatever sources of attributes it
   chooses, but acceptors can assume attributes in the federated context
   are from the source of credentials.  This requirement is typically


   enforced in mechanism specifications.  For example
   [I-D.ietf-abfab-aaa-saml] provides enough information thatwe know the
   attributes it carries today are in the federated context.  Similarly,
   we know that the requirements of this paragraph are met by SAML
   mechanisms where the assertion is the means of authentication.


I actually think that's reasonably easy to analyze and that we're in the
process of doing the analysis for draft-ietf-abfab-aaa-saml and have
done the analysis for other mechanisms.

From marka@isc.org  Thu Oct  4 16:38:47 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 5E50B21F84D8; Thu,  4 Oct 2012 16:38:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.341
X-Spam-Level: 
X-Spam-Status: No, score=-2.341 tagged_above=-999 required=5 tests=[AWL=0.258,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dxEGEvo34SwC; Thu,  4 Oct 2012 16:38:47 -0700 (PDT)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) by ietfa.amsl.com (Postfix) with ESMTP id CFDEF21F84C4; Thu,  4 Oct 2012 16:38:46 -0700 (PDT)
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mail.isc.org", Issuer "RapidSSL CA" (not verified)) by mx.pao1.isc.org (Postfix) with ESMTPS id AB707C95C0; Thu,  4 Oct 2012 23:38:39 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (c211-30-172-21.carlnfd1.nsw.optusnet.com.au [211.30.172.21]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by bikeshed.isc.org (Postfix) with ESMTPSA id 6E468216C80; Thu,  4 Oct 2012 23:38: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 2BE952896B88; Fri,  5 Oct 2012 09:38:37 +1000 (EST)
To: Olafur Gudmundsson <ogud@ogud.com>
From: Mark Andrews <marka@isc.org>
References: <20120930145325.21053.67854.idtracker@ietfa.amsl.com> <56DB6FE506A144D1183B93A8@JcK-HP8200.jck.com> <506B01D1.9080708@ogud.com> <8F3DCBA9A3AF566810CD1061@JcK-HP8200.jck.com> <506B6BE9.2000805@ogud.com> <20121003011556.526A82873A5E@drugs.dv.isc.org> <506DBE9B.3070209@ogud.com>
Subject: Re: [dnsext] Last Call: <draft-ietf-dnsext-rfc2671bis-edns0-09.txt> (Extension Mechanisms for DNS (EDNS(0))) to Internet Standard
In-reply-to: Your message of "Thu, 04 Oct 2012 12:51:39 -0400." <506DBE9B.3070209@ogud.com>
Date: Fri, 05 Oct 2012 09:38:37 +1000
Message-Id: <20121004233837.2BE952896B88@drugs.dv.isc.org>
Cc: John C Klensin <john-ietf@jck.com>, dnsext@ietf.org, 'IETF-Discussion list' <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Oct 2012 23:38:47 -0000

In message <506DBE9B.3070209@ogud.com>, Olafur Gudmundsson writes:
> On 02/10/2012 21:15, Mark Andrews wrote:
> >> Labels only work when all the severs for a zone that has a new label type,
> >> in ADDITION sufficient fraction servers in all zones above that zone
> >> MUST understand the new
> >> label type.
> >
> > Not true. Binary labels could have been made to work by removing
> > the left hand label until the remaining suffix consisted of only
> > RFC 1035 labels, looking up the servers for that domain, then
> > resuming query processing using those servers similar to what we
> > do with DS lookups.
> >
> > Such processing would be required for any new label type used in a
> > QNAME and would be a significant change to the standard query logic.
> >
> > Mark
> >
> 
> Mark,
> 
> This will only work if all the recursive resolvers that "consumers" for
> this new label types have been updated AND the new label type is the 
> left most label(s) in the name.

This works regardless of the position of the label.  If a TLD label
is a binary label then you strip back the labels until you reach
the root.

Resolvers involved in the lookup need to be updated and I didn't
dispute that.

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

From narten@us.ibm.com  Thu Oct  4 21:53:26 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 E124E21F845F for <ietf@ietfa.amsl.com>; Thu,  4 Oct 2012 21:53:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.312
X-Spam-Level: 
X-Spam-Status: No, score=-110.312 tagged_above=-999 required=5 tests=[AWL=0.288, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pthq4-HYKRQW for <ietf@ietfa.amsl.com>; Thu,  4 Oct 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 13AE421F845C for <ietf@ietf.org>; Thu,  4 Oct 2012 21:53:25 -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, 4 Oct 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, 4 Oct 2012 22:53:09 -0600
Received: from d03relay02.boulder.ibm.com (d03relay02.boulder.ibm.com [9.17.195.227]) by d03dlp01.boulder.ibm.com (Postfix) with ESMTP id C4B901FF003C for <ietf@ietf.org>; Thu,  4 Oct 2012 22:52:59 -0600 (MDT)
Received: from d03av05.boulder.ibm.com (d03av05.boulder.ibm.com [9.17.195.85]) by d03relay02.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id q954r47T257818 for <ietf@ietf.org>; Thu, 4 Oct 2012 22:53:04 -0600
Received: from d03av05.boulder.ibm.com (loopback [127.0.0.1]) by d03av05.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id q954r4qW007706 for <ietf@ietf.org>; Thu, 4 Oct 2012 22:53:04 -0600
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.44.115.148]) by d03av05.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id q954r3EU007687 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Thu, 4 Oct 2012 22:53:04 -0600
Received: from rotala.raleigh.ibm.com (localhost.localdomain [127.0.0.1]) by rotala.raleigh.ibm.com (8.14.5/8.12.5) with ESMTP id q954r2uk021300 for <ietf@ietf.org>; Fri, 5 Oct 2012 00:53:03 -0400
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.5/8.14.5/Submit) id q954r26M021275 for ietf@ietf.org; Fri, 5 Oct 2012 00:53:02 -0400
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201210050453.q954r26M021275@rotala.raleigh.ibm.com>
Date: Fri, 05 Oct 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: 12100504-2876-0000-0000-000000BEB86F
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Oct 2012 04:53:27 -0000

Total of 27 messages in the last 7 days.
 
script run at: Fri Oct  5 00:53:02 EDT 2012
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
 18.52% |    5 | 18.08% |    35445 | john-ietf@jck.com
 14.81% |    4 | 14.64% |    28710 | marka@isc.org
 11.11% |    3 | 10.93% |    21421 | sm@resistor.net
  7.41% |    2 |  9.30% |    18237 | ogud@ogud.com
  7.41% |    2 |  7.34% |    14395 | hartmans-ietf@mit.edu
  7.41% |    2 |  5.35% |    10488 | bortzmeyer@nic.fr
  3.70% |    1 |  4.79% |     9399 | tglassey@earthlink.net
  3.70% |    1 |  4.33% |     8495 | john@jlc.net
  3.70% |    1 |  4.22% |     8277 | narten@us.ibm.com
  3.70% |    1 |  4.22% |     8271 | joelja@bogus.com
  3.70% |    1 |  4.04% |     7926 | vesely@tana.it
  3.70% |    1 |  3.76% |     7369 | peter@akayla.com
  3.70% |    1 |  3.32% |     6501 | mccap@petoni.org
  3.70% |    1 |  3.27% |     6411 | rbarnes@bbn.com
  3.70% |    1 |  2.40% |     4701 | malcolm.betts@zte.com.cn
--------+------+--------+----------+------------------------
100.00% |   27 |100.00% |   196046 | Total


From joao@bondis.org  Fri Oct  5 03:59:18 2012
Return-Path: <joao@bondis.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 C8F3121F861E for <ietf@ietfa.amsl.com>; Fri,  5 Oct 2012 03:59:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0bZj4CTWcNYX for <ietf@ietfa.amsl.com>; Fri,  5 Oct 2012 03:59:18 -0700 (PDT)
Received: from smtp1.bondis.org (unknown [IPv6:2001:ac0:1003::1]) by ietfa.amsl.com (Postfix) with ESMTP id 33F4821F861D for <ietf@ietf.org>; Fri,  5 Oct 2012 03:59:18 -0700 (PDT)
Received: from core.c-l-i.net (187.red-80-29-62.adsl.static.ccgg.telefonica.net [80.29.62.187]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: joao) by smtp1.bondis.org (Postfix) with ESMTPSA id A5D276200AB; Tue,  2 Oct 2012 22:23:31 +0200 (CEST)
Subject: Re: [dnsext] Last Call: <draft-ietf-dnsext-rfc2671bis-edns0-09.txt> (Extension Mechanisms for DNS (EDNS(0))) to Internet Standard
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=us-ascii
From: =?iso-8859-1?Q?Jo=E3o_Damas?= <joao@bondis.org>
In-Reply-To: <6.2.5.6.2.20121002085424.0a887e48@resistor.net>
Date: Tue, 2 Oct 2012 22:23:34 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <14015F72-B1DD-4F15-8084-4B433A869A59@bondis.org>
References: <20120930145325.21053.67854.idtracker@ietfa.amsl.com> <56DB6FE506A144D1183B93A8@JcK-HP8200.jck.com> <20121002022212.D7B2A282EC28@drugs.dv.isc.org> <818904DB9902CFA1AB4DCB8F@JcK-HP8200.jck.com> <20121002033253.AA10F283536B@drugs.dv.isc.org> <352FF2F3A9C6DE5B0203ABDD@JcK-HP8200.jck.com> <6.2.5.6.2.20121002085424.0a887e48@resistor.net>
To: SM <sm@resistor.net>
X-Mailer: Apple Mail (2.1283)
Cc: John C Klensin <john-ietf@jck.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Oct 2012 10:59:19 -0000

On 2 Oct 2012, at 19:31, SM wrote:

> At 08:09 02-10-2012, John C Klensin wrote:
>> off bad or frivolous ideas), but closing is a big step.  Telling
>> implementers that they don't need to pay attention to the
>> relevant codes and fields (and might even be able to use them
>> for a different, even if private, purpose) is an even more
>> serious step.
>=20
> Yes.
>=20
> In Section 6.1.2:
>=20
>  "OPTION-CODE
>         Assigned by the Expert Review process as defined by the dnsext
>         working group and the IESG."
>=20
> It's odd to keep this defined by a working group which is being =
closed.

The process is (has been) defined by the wg. The assignment is done by =
the Expert Review process, not the wg.

>  Section 9.1 does not provide much information.  One significant =
change in the draft is the inclusion of requirements for "middleboxes".  =
It's not mentioned under in Appendix A.2.

OK, can add mention in there, no problem.

>=20
> BTW, the RFC 2119 reference could be normative.
>=20
> Regards,
> -sm=20


From joao@bondis.org  Fri Oct  5 03:59:18 2012
Return-Path: <joao@bondis.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 CC3F121F8620; Fri,  5 Oct 2012 03:59:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 85W5HHKIsoxi; Fri,  5 Oct 2012 03:59:18 -0700 (PDT)
Received: from smtp1.bondis.org (unknown [IPv6:2001:ac0:1003::1]) by ietfa.amsl.com (Postfix) with ESMTP id D642F21F8609; Fri,  5 Oct 2012 03:59:17 -0700 (PDT)
Received: from core.c-l-i.net (187.red-80-29-62.adsl.static.ccgg.telefonica.net [80.29.62.187]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: joao) by smtp1.bondis.org (Postfix) with ESMTPSA id 3887D6202F1; Fri,  5 Oct 2012 10:29:48 +0200 (CEST)
Subject: Re: [dnsext] Last Call: <draft-ietf-dnsext-rfc2671bis-edns0-09.txt> (Extension Mechanisms for DNS (EDNS(0))) to Internet Standard
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=iso-8859-1
From: =?iso-8859-1?Q?Jo=E3o_Damas?= <joao@bondis.org>
In-Reply-To: <396CFDC14B6FEF29A37A2FFF@JcK-HP8200.jck.com>
Date: Fri, 5 Oct 2012 10:29:52 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <DC14BFC8-601F-4E38-B1C8-3A5112033ECA@bondis.org>
References: <20120930145325.21053.67854.idtracker@ietfa.amsl.com> <56DB6FE506A144D1183B93A8@JcK-HP8200.jck.com> <506B01D1.9080708@ogud.com> <8F3DCBA9A3AF566810CD1061@JcK-HP8200.jck.com> <506B6BE9.2000805@ogud.com> <20121003011556.526A82873A5E@drugs.dv.isc.org> <84187E41-0CEC-4CA2-801D-5AB1171FFF9B@bondis.org> <396CFDC14B6FEF29A37A2FFF@JcK-HP8200.jck.com>
To: John C Klensin <john-ietf@jck.com>
X-Mailer: Apple Mail (2.1283)
Cc: 'IETF-Discussion list' <ietf@ietf.org>, Olafur Gudmundsson <ogud@ogud.com>, 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, 05 Oct 2012 10:59:19 -0000

On 3 Oct 2012, at 14:10, John C Klensin wrote:

>=20
>=20
> --On Wednesday, October 03, 2012 10:43 +0200 Jo=E3o Damas
> <joao@bondis.org> wrote:
>=20
>> I believe you are saying the same things when you are both
>> saying that for this to work there may be more than one way to
>> do it but all options require completely new functionality in
>> implementations (either by implementing support for new labels
>> types or by implementing new fall back behavior). The
>> conclusion is still the same.
>=20
> Hmm.  I'm not completely sure who "you" was intended to include,

Yourself and Olafur

> but my conclusion from the above is that there is no substantial
> justification for eliminating, at this time, a capability that
> might prove better on balance when and if new capabilities are
> considered and tradeoffs evaluated.
>=20
> To summarize my perspective on this as of now:
>=20
> (1) No one is making a case for retaining binary labels
>=20
> (2) The case has not been made, at least in the document, for
> eliminating label types.  An argument that there are other ways
> to do a particular type of label is not persuasive unless there
> is a comprehensive and written analysis of what other labels
> might be considered and what the tradeoffs among approaches
> would be.  And an argument that almost any significant added
> functionality would be very slow and costly to deploy may be an
> argument for not approving such functionality, but it is not an
> argument for eliminating one, but not all, of the underlying
> capabilities.

fair enough. The groups consensus over the last years and after the =
experience with binary labels has been that new label types are =
basically undeployable because they require a complete renewal of all =
deployed resolvers.
On the other hand the use of EDNS extension mechanisms can be =
incrementally deployed (e.g. see some of DNSSEC features that leverage =
EDNS)

> IMO, this discussion has turned up two ways in which the case
> for eliminating the possibility of additional label types could
> be made:
>=20
> (2.1) Demonstrating that simply having the capability defined
> and available in principle is somehow harmful.
>=20

People here can correct me, as my memory is fuzzy, but binary labels did =
cause harm to several deployed implementations. Don't know if this is =
just case in favour of natural selection.

> (2.2) The WG has consensus on a bright line that defines the
> nature of proposals that would require going to DNSng rather
> than EDNSx-type extensions to the current model, has concluded
> that any extensions or alterations to the label definition of
> 1034/1035 would require crossing that line, and is prepared to
> document that line and get IETF consensus on it (either as part
> of this document or one normatively referenced from it).

Pretty much, that is my understanding. It is quite possible that this =
has been a position reached over many iterations of discussions and is =
not actually documented anywhere.

Joao=

From joao@bondis.org  Fri Oct  5 03:59:19 2012
Return-Path: <joao@bondis.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 B5DBF21F8609; Fri,  5 Oct 2012 03:59:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ue7lLs880BB6; Fri,  5 Oct 2012 03:59:19 -0700 (PDT)
Received: from smtp1.bondis.org (unknown [IPv6:2001:ac0:1003::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0141521F860B; Fri,  5 Oct 2012 03:59:19 -0700 (PDT)
Received: from core.c-l-i.net (187.red-80-29-62.adsl.static.ccgg.telefonica.net [80.29.62.187]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: joao) by smtp1.bondis.org (Postfix) with ESMTPSA id 9A9BE6203CA; Wed,  3 Oct 2012 10:43:03 +0200 (CEST)
Subject: Re: [dnsext] Last Call: <draft-ietf-dnsext-rfc2671bis-edns0-09.txt> (Extension Mechanisms for DNS (EDNS(0))) to Internet Standard
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=us-ascii
From: =?iso-8859-1?Q?Jo=E3o_Damas?= <joao@bondis.org>
In-Reply-To: <20121003011556.526A82873A5E@drugs.dv.isc.org>
Date: Wed, 3 Oct 2012 10:43:06 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <84187E41-0CEC-4CA2-801D-5AB1171FFF9B@bondis.org>
References: <20120930145325.21053.67854.idtracker@ietfa.amsl.com> <56DB6FE506A144D1183B93A8@JcK-HP8200.jck.com> <506B01D1.9080708@ogud.com> <8F3DCBA9A3AF566810CD1061@JcK-HP8200.jck.com> <506B6BE9.2000805@ogud.com> <20121003011556.526A82873A5E@drugs.dv.isc.org>
To: Mark Andrews <marka@isc.org>
X-Mailer: Apple Mail (2.1283)
Cc: John C Klensin <john-ietf@jck.com>, dnsext@ietf.org, Olafur Gudmundsson <ogud@ogud.com>, 'IETF-Discussion list' <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Oct 2012 10:59:19 -0000

I believe you are saying the same things when you are both saying that =
for this to work there may be more than one way to do it but all options =
require completely new functionality in implementations (either by =
implementing support for new labels types or by implementing new fall =
back behavior). The conclusion is still the same.

Joao

On 3 Oct 2012, at 03:15, Mark Andrews wrote:

>=20
>> Labels only work when all the severs for a zone that has a new label =
type,
>> in ADDITION sufficient fraction servers in all zones above that zone=20=

>> MUST understand the new
>> label type.
>=20
> Not true. Binary labels could have been made to work by removing
> the left hand label until the remaining suffix consisted of only
> RFC 1035 labels, looking up the servers for that domain, then
> resuming query processing using those servers similar to what we
> do with DS lookups.
>=20
> Such processing would be required for any new label type used in a
> QNAME and would be a significant change to the standard query logic.
>=20
> Mark
> --=20
> Mark Andrews, ISC
> 1 Seymour St., Dundas Valley, NSW 2117, Australia
> PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org


From lars@netapp.com  Fri Oct  5 06:06:54 2012
Return-Path: <lars@netapp.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2BEA921F8718 for <ietf@ietfa.amsl.com>; Fri,  5 Oct 2012 06:06:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.547
X-Spam-Level: 
X-Spam-Status: No, score=-10.547 tagged_above=-999 required=5 tests=[AWL=0.052, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WNfmTMpY03-h for <ietf@ietfa.amsl.com>; Fri,  5 Oct 2012 06:06:52 -0700 (PDT)
Received: from mx2.netapp.com (mx2.netapp.com [216.240.18.37]) by ietfa.amsl.com (Postfix) with ESMTP id 9AA2821F8673 for <ietf@ietf.org>; Fri,  5 Oct 2012 06:06:52 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.80,541,1344236400";  d="p7s'?scan'208";a="697668964"
Received: from smtp2.corp.netapp.com ([10.57.159.114]) by mx2-out.netapp.com with ESMTP; 05 Oct 2012 06:06:52 -0700
Received: from vmwexceht05-prd.hq.netapp.com (exchsmtp.hq.netapp.com [10.106.77.35]) by smtp2.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id q95D6p0J026545 for <ietf@ietf.org>; Fri, 5 Oct 2012 06:06:52 -0700 (PDT)
Received: from SACEXCMBX01-PRD.hq.netapp.com ([169.254.2.46]) by vmwexceht05-prd.hq.netapp.com ([10.106.77.35]) with mapi id 14.02.0309.002; Fri, 5 Oct 2012 06:06:51 -0700
From: "Eggert, Lars" <lars@netapp.com>
To: "<ietf@ietf.org>" <ietf@ietf.org>
Subject: Re: Last Call: <draft-gont-intarea-obsolete-eid-option-01.txt> (Obsoleting the Endpoint Identifier (EID) Option) to Proposed Standard
Thread-Topic: Last Call: <draft-gont-intarea-obsolete-eid-option-01.txt> (Obsoleting the Endpoint Identifier (EID) Option) to Proposed Standard
Thread-Index: AQHNol14vOGu/RwsD0SZ2JSaS6ZfWperJS4A
Date: Fri, 5 Oct 2012 13:06:51 +0000
Message-ID: <D4D47BCFFE5A004F95D707546AC0D7E9068D415C@SACEXCMBX01-PRD.hq.netapp.com>
References: <20121004182351.13598.41485.idtracker@ietfa.amsl.com>
In-Reply-To: <20121004182351.13598.41485.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.104.60.115]
Content-Type: multipart/signed; boundary="Apple-Mail=_E71566AD-71DF-46E2-9568-F0E3F2FA07F1"; protocol="application/pkcs7-signature"; micalg=sha1
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, 05 Oct 2012 13:06:54 -0000

--Apple-Mail=_E71566AD-71DF-46E2-9568-F0E3F2FA07F1
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On Oct 4, 2012, at 20:23, The IESG <iesg-secretary@ietf.org> wrote:
> The IESG has received a request from an individual submitter to =
consider
> the following document:
> - 'Obsoleting the Endpoint Identifier (EID) Option'
>  <draft-gont-intarea-obsolete-eid-option-01.txt> as Proposed Standard

Have the original authors been contacted? Also, I see no reason why this =
RFC would need to be standards track.

Lars



--Apple-Mail=_E71566AD-71DF-46E2-9568-F0E3F2FA07F1
Content-Disposition: attachment; filename="smime.p7s"
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIMQDCCBUow
ggQyoAMCAQICEFcfSRTG0jNknqb9LV9GuFkwDQYJKoZIhvcNAQEFBQAwgd0xCzAJBgNVBAYTAlVT
MRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29y
azE7MDkGA1UECxMyVGVybXMgb2YgdXNlIGF0IGh0dHBzOi8vd3d3LnZlcmlzaWduLmNvbS9ycGEg
KGMpMDkxHjAcBgNVBAsTFVBlcnNvbmEgTm90IFZhbGlkYXRlZDE3MDUGA1UEAxMuVmVyaVNpZ24g
Q2xhc3MgMSBJbmRpdmlkdWFsIFN1YnNjcmliZXIgQ0EgLSBHMzAeFw0xMTEyMTAwMDAwMDBaFw0x
MjEyMDkyMzU5NTlaMIIBDTEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlT
aWduIFRydXN0IE5ldHdvcmsxRjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9S
UEEgSW5jb3JwLiBieSBSZWYuLExJQUIuTFREKGMpOTgxHjAcBgNVBAsTFVBlcnNvbmEgTm90IFZh
bGlkYXRlZDEzMDEGA1UECxMqRGlnaXRhbCBJRCBDbGFzcyAxIC0gTmV0c2NhcGUgRnVsbCBTZXJ2
aWNlMRQwEgYDVQQDFAtMYXJzIEVnZ2VydDEeMBwGCSqGSIb3DQEJARYPbGFyc0BuZXRhcHAuY29t
MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAokrhJTcXt6J/VEpZOicLoguBlYTjXP9v
Ze4HuuhXnURUS8YouAfgaqA0zYbt5yd6fh4PBMdAaEWr5yJyHuFykXlrCumjUWSpLuqTS2A+pt4q
cZaAQk9iLDN/UVd3SpkUuvWbxXlqzG7/BSqa3VNObBzCmyh+V7aXxri+30CT//DSsNRC4VFy6sn6
dMgSaFenXLwe/FBwY0qTMfICT1PrrX6Sw1S8OfH9rykLlZXbmfkFExxQngp1DJH9xMHeODHGbCv/
ty5gdxMOrLe+vENxFEcy1YQWBZd1kNL4UObugF8A/jE/s+Oa3H1VFH8ghqZTdqGDysVxmtKHuNFx
6jIBSQIDAQABo4HSMIHPMAkGA1UdEwQCMAAwRAYDVR0gBD0wOzA5BgtghkgBhvhFAQcXATAqMCgG
CCsGAQUFBwIBFhxodHRwczovL3d3dy52ZXJpc2lnbi5jb20vcnBhMAsGA1UdDwQEAwIFoDAdBgNV
HSUEFjAUBggrBgEFBQcDBAYIKwYBBQUHAwIwUAYDVR0fBEkwRzBFoEOgQYY/aHR0cDovL2luZGMx
ZGlnaXRhbGlkLWczLWNybC52ZXJpc2lnbi5jb20vSW5kQzFEaWdpdGFsSUQtRzMuY3JsMA0GCSqG
SIb3DQEBBQUAA4IBAQBA7q6tR92qpd7xo7VBsrOfGCWzoxIVfTc7t0RhB/Oz/+c3lnhYnNScIuKN
JmyZvznmVxqB9BJ72+NkvmdB/hnILSBTRawL2tyLo9PkBtN0nRt4gS6wjpWnD8G83hlJLE7r25jk
7HkRev61dTIXsANFpJKF02C4XSoDfEzNV6MpuEvHvcgHCqMrlwWwfKc7+NoDnE8PBuRzwSXvlD5L
mswCY2iiOsd7ImNO4OzTCxETvKTDu92+FTIbRJJpYjVNv1UF7e3w9Kq65BkZJErUH19beUeQl0Wh
2BJQE6/15rQyCnP0iJ/Nmx2/kI6M0PWunEsI6FMs0MbosreaWGHlQmomMIIG7jCCBdagAwIBAgIQ
cRVmBUrkkSFN6bxE+azT3DANBgkqhkiG9w0BAQUFADCByjELMAkGA1UEBhMCVVMxFzAVBgNVBAoT
DlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTowOAYDVQQL
EzEoYykgMTk5OSBWZXJpU2lnbiwgSW5jLiAtIEZvciBhdXRob3JpemVkIHVzZSBvbmx5MUUwQwYD
VQQDEzxWZXJpU2lnbiBDbGFzcyAxIFB1YmxpYyBQcmltYXJ5IENlcnRpZmljYXRpb24gQXV0aG9y
aXR5IC0gRzMwHhcNMDkwNTAxMDAwMDAwWhcNMTkwNDMwMjM1OTU5WjCB3TELMAkGA1UEBhMCVVMx
FzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3Jr
MTswOQYDVQQLEzJUZXJtcyBvZiB1c2UgYXQgaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAo
YykwOTEeMBwGA1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTcwNQYDVQQDEy5WZXJpU2lnbiBD
bGFzcyAxIEluZGl2aWR1YWwgU3Vic2NyaWJlciBDQSAtIEczMIIBIjANBgkqhkiG9w0BAQEFAAOC
AQ8AMIIBCgKCAQEA7cRH3yooHXwGa7vXITLJbBOP6bGNQU4099oL42r6ZYggCxET6ZvgSU6Lb9UB
0F8NR5GKWkx0Pj/GkQm7TDSejW6hglFi92l2WJYHr54UGAdPWr2f0jGyVBlzRmoZQhHsEnMhjfXc
MM3l2VYKMcU2bSkUl70t2olHGYjYSwQ967Y8Zx50ABMN0Ibak2f4MwOuGjxraXj2wCyO4YM/d/mZ
//6fUlrCtIcK2GypR8FUKWVDPkrAlh/Brfd3r2yxBF6+wbaULZeQLSfSux7pg2qE9sSyriMGZSal
J1grByK0b6ZiSBp38tVQJ5op05b7KPW6JHZi44xZ6/tu1ULEvkHH9QIDAQABo4ICuTCCArUwNAYI
KwYBBQUHAQEEKDAmMCQGCCsGAQUFBzABhhhodHRwOi8vb2NzcC52ZXJpc2lnbi5jb20wEgYDVR0T
AQH/BAgwBgEB/wIBADBwBgNVHSAEaTBnMGUGC2CGSAGG+EUBBxcBMFYwKAYIKwYBBQUHAgEWHGh0
dHBzOi8vd3d3LnZlcmlzaWduLmNvbS9jcHMwKgYIKwYBBQUHAgIwHhocaHR0cHM6Ly93d3cudmVy
aXNpZ24uY29tL3JwYTA0BgNVHR8ELTArMCmgJ6AlhiNodHRwOi8vY3JsLnZlcmlzaWduLmNvbS9w
Y2ExLWczLmNybDAOBgNVHQ8BAf8EBAMCAQYwbgYIKwYBBQUHAQwEYjBgoV6gXDBaMFgwVhYJaW1h
Z2UvZ2lmMCEwHzAHBgUrDgMCGgQUS2u5KJYGDLvQUjibKaxLB4shBRgwJhYkaHR0cDovL2xvZ28u
dmVyaXNpZ24uY29tL3ZzbG9nbzEuZ2lmMC4GA1UdEQQnMCWkIzAhMR8wHQYDVQQDExZQcml2YXRl
TGFiZWw0LTIwNDgtMTE4MB0GA1UdDgQWBBR5R2EIQf04BKJL57XM9UP2SSsR+DCB8QYDVR0jBIHp
MIHmoYHQpIHNMIHKMQswCQYDVQQGEwJVUzEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNV
BAsTFlZlcmlTaWduIFRydXN0IE5ldHdvcmsxOjA4BgNVBAsTMShjKSAxOTk5IFZlcmlTaWduLCBJ
bmMuIC0gRm9yIGF1dGhvcml6ZWQgdXNlIG9ubHkxRTBDBgNVBAMTPFZlcmlTaWduIENsYXNzIDEg
UHVibGljIFByaW1hcnkgQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkgLSBHM4IRAItbdVaEVIULAM+v
OEjOsaQwDQYJKoZIhvcNAQEFBQADggEBADlNz0GZgbWpBbVSOOk5hIls5DSoWufYbAlMJBq6WaSH
O3Mh8ZOBz79oY1pn/jWFK6HDXaNKwjoZ3TDWzE3v8dKBl8pUWkO/N4t6jhmND0OojPKvYLMVirOV
nDzgnrMnmKQ1chfl/Cpdh9OKDcLRRSr4wPSsKpM61a4ScAjr+zvid+zoK2Q1ds262uDRyxTWcVib
vtU+fbbZ6CTFJGZMXZEfdrMXPn8NxiGJL7M3uKH/XLJtSd5lUkL7DojS7Uodv0vj+Mxy+kgOZY5J
yNb4mZg7t5Q+MXEGh/psWVMu198r7V9jAKwV7QO4VRaMxmgD5yKocwuxvKDaUljdCg5/wYIxggSL
MIIEhwIBATCB8jCB3TELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYD
VQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTswOQYDVQQLEzJUZXJtcyBvZiB1c2UgYXQgaHR0
cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAoYykwOTEeMBwGA1UECxMVUGVyc29uYSBOb3QgVmFs
aWRhdGVkMTcwNQYDVQQDEy5WZXJpU2lnbiBDbGFzcyAxIEluZGl2aWR1YWwgU3Vic2NyaWJlciBD
QSAtIEczAhBXH0kUxtIzZJ6m/S1fRrhZMAkGBSsOAwIaBQCgggJtMBgGCSqGSIb3DQEJAzELBgkq
hkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTEyMTAwNTEzMDY1MVowIwYJKoZIhvcNAQkEMRYEFMkZ
Q1MiHwP/lmJZSuBFiG0Q3hS8MIIBAwYJKwYBBAGCNxAEMYH1MIHyMIHdMQswCQYDVQQGEwJVUzEX
MBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5ldHdvcmsx
OzA5BgNVBAsTMlRlcm1zIG9mIHVzZSBhdCBodHRwczovL3d3dy52ZXJpc2lnbi5jb20vcnBhIChj
KTA5MR4wHAYDVQQLExVQZXJzb25hIE5vdCBWYWxpZGF0ZWQxNzA1BgNVBAMTLlZlcmlTaWduIENs
YXNzIDEgSW5kaXZpZHVhbCBTdWJzY3JpYmVyIENBIC0gRzMCEFcfSRTG0jNknqb9LV9GuFkwggEF
BgsqhkiG9w0BCRACCzGB9aCB8jCB3TELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJ
bmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTswOQYDVQQLEzJUZXJtcyBvZiB1
c2UgYXQgaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAoYykwOTEeMBwGA1UECxMVUGVyc29u
YSBOb3QgVmFsaWRhdGVkMTcwNQYDVQQDEy5WZXJpU2lnbiBDbGFzcyAxIEluZGl2aWR1YWwgU3Vi
c2NyaWJlciBDQSAtIEczAhBXH0kUxtIzZJ6m/S1fRrhZMA0GCSqGSIb3DQEBAQUABIIBAAqKkfEF
SvsBHlVLBw2uJqgJHpcpigoGgkIuCVI4XS4FrxAS+MqxiVdEm+jV8zhx0hTrgHv9zhDyCqHtAeqU
uQ0JJK6YXolbenlwrVp2D9zCiLZOKpjZMC6H+7zYErMRRf6sZZckka7Q6vm5eI9kyvOM4O4asFnw
X2FRMEGu1PD6fSeULSH/Fqt8jb4Yaw1o1gTp5CXNzEpbLBrFdNNpEH8cXGc8Friyb5tlUSPEm5Ao
9xP8qlj2Og9eXHf6dT5fGPblFAZ/c1ZThkzhqrFXSIzx3DoOtHuXFbpuWjzYXStxT7oSgQYxcs6R
4wgc/fvcfvdLGnXpoBiskTpt5TbdfBYAAAAAAAA=

--Apple-Mail=_E71566AD-71DF-46E2-9568-F0E3F2FA07F1--

From jnc@mercury.lcs.mit.edu  Fri Oct  5 06:58:31 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 4FC2521F8584 for <ietf@ietfa.amsl.com>; Fri,  5 Oct 2012 06:58:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.413
X-Spam-Level: 
X-Spam-Status: No, score=-6.413 tagged_above=-999 required=5 tests=[AWL=0.186,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KfpZ7kpiu1Jb for <ietf@ietfa.amsl.com>; Fri,  5 Oct 2012 06:58:30 -0700 (PDT)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id 9965F21F8530 for <ietf@ietf.org>; Fri,  5 Oct 2012 06:58:30 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 825FE18C137; Fri,  5 Oct 2012 09:58:29 -0400 (EDT)
To: ietf@ietf.org
Subject: Re: Last Call: <draft-gont-intarea-obsolete-eid-option-01.txt> (Obsoleting the Endpoint Identifier (EID) Option) to Proposed Standard
Message-Id: <20121005135829.825FE18C137@mercury.lcs.mit.edu>
Date: Fri,  5 Oct 2012 09:58:29 -0400 (EDT)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: jnc@mercury.lcs.mit.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Oct 2012 13:58:31 -0000

    > From: "Eggert, Lars" <lars@netapp.com>

    >> The IESG has received a request from an individual submitter to
    >> consider the following document:
    >> - 'Obsoleting the Endpoint Identifier (EID) Option'
    >>  <draft-gont-intarea-obsolete-eid-option-01.txt> as Proposed Standard

    > Have the original authors [sic - JNC] been contacted? 

Alas, the author of the ID which defines this option, Charlie Lynn, is no
longer with us:

  http://www.postel.org/pipermail/end2end-interest/2004-June/004195.html

I can probably give as good a judgement on it as anyone, though.


Looking at the ID defining the option:

  http://ana-3.lcs.mit.edu/~jnc/nimrod/eidoption.txt

(dunno why the obsoletion ID doesn't give a URL for it), the obsoletion ID is
slightly inaccurate: it wasn't just "meant to be used with the Nimrod routing
architecture", but rather the endpoint name format supported by that option
is totally general, allowing any endpoint name format to be used.

(In fact, one large faction of the Namespace Research Group wanted to use a
format for endpoint names which would have made use of the 'variable length'
capability of this option, but I digress..)

I don't see any particular reason to not obsolete this option, though; no
recent proposal uses a separate header option for endpoint identification in
IPv6. Recent work on adding endpoint names has either i) used part of the
IPv6 address as an EID (e.g. ILNP), or interpreted the existing IPvN address
as an EID (e.g. LISP).

And, in any event, if we decide we need it, we can always bring it back
(according to the obsoletion ID, it's merely to be marked "obsolete",
not re-assigned).

	Noel

From tglassey@earthlink.net  Fri Oct  5 07:22:54 2012
Return-Path: <tglassey@earthlink.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5A6E021F86D1; Fri,  5 Oct 2012 07:22:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.644
X-Spam-Level: 
X-Spam-Status: No, score=-2.644 tagged_above=-999 required=5 tests=[AWL=-0.045, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lxI+hGsR4dpA; Fri,  5 Oct 2012 07:22:53 -0700 (PDT)
Received: from elasmtp-kukur.atl.sa.earthlink.net (elasmtp-kukur.atl.sa.earthlink.net [209.86.89.65]) by ietfa.amsl.com (Postfix) with ESMTP id 4BD5421F86CA; Fri,  5 Oct 2012 07:22:53 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=Mbcu0Q/rb6i1XVvkLg7zVa3jgm8BZCR/s1DFVErc7E1YnulO6C5430+vUrcAlf/3; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [67.180.133.21] (helo=[192.168.15.2]) by elasmtp-kukur.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from <tglassey@earthlink.net>) id 1TK8nk-0002e1-HK; Fri, 05 Oct 2012 10:22:52 -0400
Message-ID: <506EED36.1080700@earthlink.net>
Date: Fri, 05 Oct 2012 07:22:46 -0700
From: tglassey <tglassey@earthlink.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: Stephen Hanna <shanna@juniper.net>
Subject: Proposed BCP addition - No-Late-Patent-Filing Rights - contract provision for BCP/NoteWell - Re: [Nea] IPR Disclosure: Cisco's Statement of IPR Related to draft-ietf-nea-pt-tls-07
References: <20121004214451.3466.22760.idtracker@ietfa.amsl.com> <AC6674AB7BC78549BB231821ABF7A9AEB917F59A71@EMBX01-WF.jnpr.net>
In-Reply-To: <AC6674AB7BC78549BB231821ABF7A9AEB917F59A71@EMBX01-WF.jnpr.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 01b7a7e171bdf5911aa676d7e74259b7b3291a7d08dfec791b3cd1ea37db7340ce84c3cf4e18a5e7350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 67.180.133.21
Cc: "nea@ietf.org" <nea@ietf.org>, ietf <ietf@ietf.org>, IPR@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Oct 2012 14:22:55 -0000

On 10/4/2012 9:23 PM, Stephen Hanna wrote:
> IETF Secretariat wrote:
>> An IPR disclosure that pertains to your Internet-Draft entitled
>> "PT-TLS: A TCP-based Posture Transport (PT) Protocol"
>> (draft-ietf-nea-pt-tls) was submitted to the IETF Secretariat
>> on 2012-10-04
> Well, that's a pain in the neck!
Actually its much more than that. Its why full disclosure at the start 
of a process of who the parties legally represent and what their 
interests in the standard process are so that full disclosure is there.

But fixing this process is actually VERY SIMPLE... Just a 'component of 
an updated BCP which contractually commits that IETF members and their 
sponsors may not engage in submarining' its actually pretty simple to 
stop this... you folks just have to want to.

The propose text could look something like:

   " Whereas - all parties working in the IETF have an open 
collaboration agreement, it is agreed that any Intellectual Properties 
developed by a commercial sponsor to the IETF will have full disclosure 
of their licensing provisions prior to any development taking place in 
the IETF and that those rights must be properly disclosed to all parties 
in the interest of open collaboration and global standards development."

     "Further any party formally participating or supplying IP to these 
initiative waves any rights to change those access rights and disclosure 
requirements by participating in the process after the development 
commences on any initiative".

Todd
> I'm not happy to see these
> IPR disclosures come in so late in the process. PT-TLS is
> already with the IESG and PT-EAP has passed two WGLCs and
> is almost ready to go to the IESG. This IPR should have
> been disclosed much earlier, if at all possible.
>
> At this time, I would encourage nea participants to read
> (or re-read) RFC 3979, which describes how we handle IPR
> disclosures in IETF. Also read the IPR disclosures to see
> what's included in the patents in question and what IPR
> licensing terms are being offered.
>
> I would ask Cisco to please provide a link to the actual
> patent application (since I guess there is no patent yet
> and I can't find the patent application) so that we can
> see what technology is claimed to be covered.
>
> Thanks,
>
> Steve
>
>> -----Original Message-----
>> From: nea-bounces@ietf.org [mailto:nea-bounces@ietf.org] On Behalf Of
>> IETF Secretariat
>> Sent: Thursday, October 04, 2012 5:45 PM
>> To: Paul_Sangster@symantec.com; ncamwing@cisco.com; jsalowey@cisco.com
>> Cc: nea@ietf.org; turners@ieca.com; ipr-announce@ietf.org
>> Subject: [Nea] IPR Disclosure: Cisco's Statement of IPR Related to
>> draft-ietf-nea-pt-tls-07
>>
>>
>> Dear Paul Sangster, Nancy Cam-Winget, Joseph A. Salowey:
>>
>>   An IPR disclosure that pertains to your Internet-Draft entitled "PT-
>> TLS: A TCP-
>> based Posture Transport (PT) Protocol" (draft-ietf-nea-pt-tls) was
>> submitted to
>> the IETF Secretariat on 2012-10-04 and has been posted on the "IETF
>> Page of
>> Intellectual Property Rights Disclosures"
>> (https://datatracker.ietf.org/ipr/1890/). The title of the IPR
>> disclosure is
>> "Cisco's Statement of IPR Related to draft-ietf-nea-pt-tls-07."");
>>
>> The IETF Secretariat
>>
>> _______________________________________________
>> Nea mailing list
>> Nea@ietf.org
>> https://www.ietf.org/mailman/listinfo/nea
> _______________________________________________
> Nea mailing list
> Nea@ietf.org
> https://www.ietf.org/mailman/listinfo/nea
>
>
> -----
> No virus found in this message.
> Checked by AVG - www.avg.com
> Version: 2013.0.2677 / Virus Database: 2591/5808 - Release Date: 10/03/12
>
>


-- 
Regards TSG
"Ex-Cruce-Leo"

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


From jnc@mercury.lcs.mit.edu  Fri Oct  5 08:00:42 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 0FE6721F8718; Fri,  5 Oct 2012 08:00:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.434
X-Spam-Level: 
X-Spam-Status: No, score=-6.434 tagged_above=-999 required=5 tests=[AWL=0.165,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L943r41kuM37; Fri,  5 Oct 2012 08:00:41 -0700 (PDT)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id 84CCB21F86CA; Fri,  5 Oct 2012 08:00:41 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id BCCED18C136; Fri,  5 Oct 2012 11:00:40 -0400 (EDT)
To: ietf@ietf.org
Subject: Re: Last Call: RFC 5011 (Automated Updates of DNS Security (DNSSEC) Trust Anchors) to Internet Standard
Message-Id: <20121005150040.BCCED18C136@mercury.lcs.mit.edu>
Date: Fri,  5 Oct 2012 11:00:40 -0400 (EDT)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: dnsext@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Oct 2012 15:00:42 -0000

    > The IESG has received a request from the author to consider the
    > following document:
    > 'Automated Updates of DNS Security (DNSSEC) Trust Anchors,' RFC 5011
    > as an Internet Standard.
    > ...
    > The IESG plans to make a decision in the next few weeks, and solicits
    > final comments on this action.

I strongly support this requested action. This specification is both i) well
designed (not to mention very clever :-), and ii) fulfils a real, major need.

	Noel

From hartmans@painless-security.com  Thu Oct  4 13:59:06 2012
Return-Path: <hartmans@painless-security.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CD05621F85A4; Thu,  4 Oct 2012 13:59:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 4.351
X-Spam-Level: ****
X-Spam-Status: No, score=4.351 tagged_above=-999 required=5 tests=[AWL=0.063,  BAYES_00=-2.599, FH_HELO_EQ_D_D_D_D=1.597, FH_HOST_EQ_D_D_D_D=0.765,  FM_DDDD_TIMES_2=1.999, HELO_DYNAMIC_IPADDR=2.426, RDNS_DYNAMIC=0.1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uO6OSmQUSTtL; Thu,  4 Oct 2012 13:59:06 -0700 (PDT)
Received: from ec2-23-21-227-93.compute-1.amazonaws.com (ec2-23-21-227-93.compute-1.amazonaws.com [23.21.227.93]) by ietfa.amsl.com (Postfix) with ESMTP id 65B2B21F85A1; Thu,  4 Oct 2012 13:59:05 -0700 (PDT)
Received: from carter-zimmerman.suchdamage.org (c-98-217-126-210.hsd1.ma.comcast.net [98.217.126.210]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.suchdamage.org (Postfix) with ESMTPS id 777D62010F; Thu,  4 Oct 2012 16:58:52 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id E8F9B414A; Thu,  4 Oct 2012 16:58:53 -0400 (EDT)
From: Sam Hartman <hartmans@painless-security.com>
To: Simon Josefsson <simon@josefsson.org>
Subject: Re: [abfab] Last Call: <draft-ietf-abfab-gss-eap-naming-05.txt> (Name Attributes	for the GSS-API EAP mechanism) to Proposed Standard
References: <20120920141717.4821.29598.idtracker@ietfa.amsl.com> <87fw6c9w97.fsf@latte.josefsson.org>
Date: Thu, 04 Oct 2012 16:58:53 -0400
In-Reply-To: <87fw6c9w97.fsf@latte.josefsson.org> (Simon Josefsson's message of "Fri, 21 Sep 2012 00:15:16 +0200")
Message-ID: <tslwqz6c5te.fsf@mit.edu>
User-Agent: Gnus/5.110009 (No Gnus v0.9) Emacs/22.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailman-Approved-At: Fri, 05 Oct 2012 08:03:31 -0700
Cc: abfab@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Oct 2012 20:59:06 -0000

Any advice from the SAML community on responding to the following
comment from Simon:


   If the value is not simple or is empty, then the raw value(s) of the
   GSS name attribute MUST be the well-formed serialization of the
   <saml:AttributeValue> element(s) encoded as UTF-8.  The "display"
   values are implementation-defined.

Question: what serialization is intended here?  An example here would
make this more clear.


From cantor.2@osu.edu  Thu Oct  4 17:15:39 2012
Return-Path: <cantor.2@osu.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 3C04F1F0425; Thu,  4 Oct 2012 17:15: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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id naS0oeuhxclw; Thu,  4 Oct 2012 17:15:38 -0700 (PDT)
Received: from ch1outboundpool.messaging.microsoft.com (ch1ehsobe006.messaging.microsoft.com [216.32.181.186]) by ietfa.amsl.com (Postfix) with ESMTP id 6E0C11F041F; Thu,  4 Oct 2012 17:15:38 -0700 (PDT)
Received: from mail114-ch1-R.bigfish.com (10.43.68.252) by CH1EHSOBE009.bigfish.com (10.43.70.59) with Microsoft SMTP Server id 14.1.225.23; Fri, 5 Oct 2012 00:15:35 +0000
Received: from mail114-ch1 (localhost [127.0.0.1])	by mail114-ch1-R.bigfish.com (Postfix) with ESMTP id C59C86017D; Fri,  5 Oct 2012 00:15:35 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:164.107.81.40; KIP:(null); UIP:(null); IPV:NLI; H:CIO-KRC-HT02.osuad.osu.edu; RD:cio-krc-ht02.osuad.osu.edu; EFVD:NLI
X-SpamScore: -4
X-BigFish: PS-4(z551bizbb2dI98dI9371I1432I1418Izz1d77h1202h1d1ah1d2ahzz8275bh8275dhz2fh2a8h668h839h944hd25hf0ah107ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1155h)
Received-SPF: pass (mail114-ch1: domain of osu.edu designates 164.107.81.40 as permitted sender) client-ip=164.107.81.40; envelope-from=cantor.2@osu.edu; helo=CIO-KRC-HT02.osuad.osu.edu ; suad.osu.edu ; 
Received: from mail114-ch1 (localhost.localdomain [127.0.0.1]) by mail114-ch1 (MessageSwitch) id 1349396133713527_13936; Fri,  5 Oct 2012 00:15:33 +0000 (UTC)
Received: from CH1EHSMHS011.bigfish.com (snatpool2.int.messaging.microsoft.com [10.43.68.234])	by mail114-ch1.bigfish.com (Postfix) with ESMTP id A1C3C4000E4;	Fri,  5 Oct 2012 00:15:33 +0000 (UTC)
Received: from CIO-KRC-HT02.osuad.osu.edu (164.107.81.40) by CH1EHSMHS011.bigfish.com (10.43.70.11) with Microsoft SMTP Server (TLS) id 14.1.225.23; Fri, 5 Oct 2012 00:15:33 +0000
Received: from CIO-KRC-D1MBX01.osuad.osu.edu ([fe80::450b:35e6:80f4:f3e0]) by CIO-KRC-HT02.osuad.osu.edu ([fe80::8554:1787:2a7:72c9%12]) with mapi id 14.02.0309.002; Thu, 4 Oct 2012 20:15:32 -0400
From: "Cantor, Scott" <cantor.2@osu.edu>
To: Sam Hartman <hartmans@painless-security.com>, Simon Josefsson <simon@josefsson.org>
Subject: Re: [abfab] Last Call: <draft-ietf-abfab-gss-eap-naming-05.txt> (Name Attributes for the GSS-API EAP mechanism) to Proposed Standard
Thread-Topic: [abfab] Last Call: <draft-ietf-abfab-gss-eap-naming-05.txt> (Name Attributes for the GSS-API EAP mechanism) to Proposed Standard
Thread-Index: AQHNoo6IhaenKMaBu0KVsTWqbAugXQ==
Date: Fri, 5 Oct 2012 00:15:32 +0000
Message-ID: <BA63CEAE152A7742B854C678D949138339A52F3E@CIO-KRC-D1MBX01.osuad.osu.edu>
In-Reply-To: <tslwqz6c5te.fsf@mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [216.27.107.146]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <B3B2A4C0E4775046838108E2A7B6A2D7@osu.edu>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: osu.edu
X-Mailman-Approved-At: Fri, 05 Oct 2012 08:03:31 -0700
Cc: "abfab@ietf.org" <abfab@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Oct 2012 00:15:39 -0000

On 10/4/12 4:58 PM, "Sam Hartman" <hartmans@painless-security.com> wrote:

>Any advice from the SAML community on responding to the following
>comment from Simon:
>
>   If the value is not simple or is empty, then the raw value(s) of the
>   GSS name attribute MUST be the well-formed serialization of the
>   <saml:AttributeValue> element(s) encoded as UTF-8.  The "display"
>   values are implementation-defined.
>
>Question: what serialization is intended here?  An example here would
>make this more clear.

I think that was my text, possibly. I just meant that it's the XML
representation of the element, but well-formed, meaning that you have to
make sure any namespaces are declared, etc. so that if a parser were to
parse that serialization, it would be well-formed XML.

Like, say, this:

<saml2:Attribute xmlns:saml2=3D"urn:oasis:names:tc:SAML:2.0:assertion"
	NameFormat=3D"urn:oasis:names:tc:SAML:2.0:attrname-format:uri"
	Name=3D"urn:oid:1.3.6.1.4.1.5923.1.1.1.10"
	FriendlyName=3D"eduPersonTargetedID">
  <saml2:AttributeValue>
    <saml2:NameID=20
Format=3D"urn:oasis:names:tc:SAML:2.0:nameid-format:persistent"
		NameQualifier=3D"https://idp.example.org/idp/shibboleth"
 		SPNameQualifier=3D"https://sp.example.org/shibboleth">
	84e411ea-7daa-4a57-bbf6-b5cc52981b73
    </saml2:NameID>
  </saml2:AttributeValue>
</saml2:Attribute>

That's not a simple XML content model. So one such serialization is:

<saml2:AttributeValue xmlns:saml2=3D"urn:oasis:names:tc:SAML:2.0:assertion"=
>
    <saml2:NameID=20
Format=3D"urn:oasis:names:tc:SAML:2.0:nameid-format:persistent"
		NameQualifier=3D"https://idp.example.org/idp/shibboleth"
 		SPNameQualifier=3D"https://sp.example.org/shibboleth">
	84e411ea-7daa-4a57-bbf6-b5cc52981b73
    </saml2:NameID>
  </saml2:AttributeValue>

This is NOT the same as canonicalization of course. It's just well-formed
and is one of many possible serializations that would meet the requirement.



I suspect an example for the spec might be simpler. I just didn't have an
example of a complex value to hand, other than that case.

-- Scott



From julian.reschke@gmx.de  Fri Oct  5 08:13:03 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 90C8F21F875A for <ietf@ietfa.amsl.com>; Fri,  5 Oct 2012 08:13:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.299
X-Spam-Level: 
X-Spam-Status: No, score=-103.299 tagged_above=-999 required=5 tests=[AWL=-0.700, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fXfK4sGw9EfS for <ietf@ietfa.amsl.com>; Fri,  5 Oct 2012 08:13:02 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by ietfa.amsl.com (Postfix) with SMTP id E4C3921F84D5 for <ietf@ietf.org>; Fri,  5 Oct 2012 08:13:01 -0700 (PDT)
Received: (qmail invoked by alias); 05 Oct 2012 15:13:00 -0000
Received: from mail.greenbytes.de (EHLO [192.168.1.140]) [217.91.35.233] by mail.gmx.net (mp037) with SMTP; 05 Oct 2012 17:13:00 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX19ff0pgC0Jfl44CV45XesOiWNuW6nK0BU4I/vdp7Y XlMSQlnXDiKz6G
Message-ID: <506EF8FA.1030100@gmx.de>
Date: Fri, 05 Oct 2012 17:12:58 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120907 Thunderbird/15.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Last Call: <draft-snell-http-prefer-14.txt> (Prefer Header for HTTP) to Proposed Standard
References: <20120914184457.16683.33382.idtracker@ietfa.amsl.com> <6.2.5.6.2.20120914153648.09f87700@resistor.net>
In-Reply-To: <6.2.5.6.2.20120914153648.09f87700@resistor.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: SM <sm@resistor.net>, James M Snell <jasnell@gmail.com>, HTTP Working Group <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: Fri, 05 Oct 2012 15:13:03 -0000

Hi James,

see below for my (mostly editorial) feedback:

Multiple times: s/header/header field/

1.  Introduction

    Within the course of processing an HTTP request there are typically a
    range of required and optional behaviors that a server or
    intermediary can employ.  These often manifest is a variety of subtle
    and not-so-subtle ways within the response.

s/is/in/

    For example, when using the HTTP PUT method to modify a resource --
    similar to that defined for the Atom Publishing Protocol [RFC 5023]

reference to RFC 5023 is missing

    The rigid, must-understand semantics of the Expect header, therefore,

    make it a poor choice for the general expression of optional
    preferences that may be specific to an individual application and are
    therefore unknown to an intermediary or are otherwise irrelevant to
    the intermediaries successful handling of the request and response.

    Another option available to clients is to utilize Request URI query-
    string parameters to express preferences.  Doing so, however, results
    in a variety of issues affecting the cacheability of responses.

Comment: not according to the spec; but there are other issues with it, 
such as overloading the URI namespace.

    As an alternative, this specification defines a new HTTP request
    header field that can be used by clients to request that optional
    behaviors be applied by a server during the processing the request.
    Additionally, a handful of initial preference tokens for use with the
    new header are defined.

    In this document, the key words "MUST", "MUST NOT", "REQUIRED",
    "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY",
    and "OPTIONAL" are to be interpreted as described in [RFC2119].

ID-Nits complained it couldn't find this note. It probably needs some 
adjustment.

1.1.  Syntax Notation

    This specification uses the Augmented Backus-Naur Form (ABNF)
    notation of [RFC5234] and includes, by reference, the "token",
    "word", "OWS", "BWS" rules and the #rule extension as defined within
    Sections 1.2 and 3.2.4 of [I-D.ietf-httpbis-p1-messaging].

Note: need to re-check the section numbers, they might have moved.

2.  The Prefer Request Header Field

    The Prefer request-header field is used to indicate that particular
    server behaviors are preferred by the client, but not required for
    successful completion of the request.  Prefer is similar in nature to
    the Expect header field defined by Section 9.3 of
    [I-D.ietf-httpbis-p2-semantics] with the exception that servers are

Ditto.

    If a particular preference token or parameter is specified multiple
    times, repeated occurrences MUST be ignored without signaling an
    error or otherwise altering the processing of the request.

That means: first wins, right? The repeated occurrences might have 
different parameters...

    The Prefer request header field is end-to-end and MUST be forwarded
    by a proxy if the request is forwarded.

That's something *this* spec can not require; it should follow from 
HTTPbis, right?

s/header/header field/

    No significance is given to the order in which preference tokens
    appear within a request.

Really? What if a token is repeated with different parameters?

2.1.  Content Negotiation and Cache Considerations

    Note that while the Prefer header field is not intended to be used as
    content negotiation mechanism, the application of a preference
    potentially could affect the caching characteristics of a response.
    Specifically, if a server supports the optional application of a
    preference that could even just potentially result in a variance to a
    cache's handling of a response entity, a Vary header field MUST be
    included with the response listing the Prefer header field regardless
    of whether the client actually used Prefer in the request.

    Because of the inherent complexities involved with properly
    implementing server-driven content negotiation, effective caching,
    and the application of optional preferences, implementors must

...avoid lowercase RFC2119 keywords...

    exercise caution when utilizing preferences in such a way as to
    impact the caching of a response and SHOULD NOT use the Prefer header
    mechanism for content negotiation.

2.2.  Examples

    The following examples illustrate the use of various preferences
    defined by this specification, as well as undefined extensions for
    strictly illustrative purposes:

    1.  Return a "202 Accepted" response for asynchronous processing if
    the response cannot be processed within 10 seconds.  An undefined
    "priority" preference is also specified:

      Prefer: return-asynch, wait=10;
      Prefer: priority=5;

Shouldn't that be:

      Prefer: return-asynch; wait=10
      Prefer: priority=5

???

3.  Preference Definitions

    The following subsections define an initial set of preferences.
    Additional preferences can be registered for convenience and/or to
    promote reuse by other applications.  This specification establishes
    an IANA registry of such relation types (see Section 4.1).

    Registered preference names MUST conform to the token rule, and MUST
    be compared character-by-character in a case-insensitive fashion.
    They SHOULD be appropriate to the specificity of the preference;
    i.e., if the semantics are highly specific to a particular
    application, the name should reflect that, so that more general names
    remain available for less specific use.

    Registered preferences MUST NOT constrain servers, clients or any
    intermediaries involved in the exchange and processing of a request
    to any behavior required for successful processing.  The use and
    application of a preference within a given request MUST be optional
    on the part of all participants.

3.1.  The "return-asynch" Preference

    The "return-asynch" preference indicates that the client prefers the
    server to respond asynchronously to a response.  For instance, in the
    case when the length of time it takes to generate a response will
    exceed some arbitrary threshold established by the server, the server
    can honor the return-asynch preference by returning either a "202
    Accepted" or "303 See Other" response.

...would be good to explain when to use what (not sure about when 303 
would be right).

3.4.  The "wait" Preference

    The "wait" preference can be used to establish an upper bound on the
    length of time, in seconds, the client is willing to wait for a
    response, after which the client might choose to abandon the request.
    In the case generating a response will take longer than the time
    specified, the server, or proxy, MAY choose to utilize an
    asynchronous processing model by returning, for example, "202
    Accepted" or "303 See Other" responses.

    ABNF:

      wait = "wait" BWS "=" BWS delta-seconds

    Clients specifying the "wait" preference SHOULD also use the Date
    header field, as specified in Section 9.2 of
    [I-D.ietf-httpbis-p2-semantics], within the request to establish the
    time at which the client began waiting for the completion of the
    request.  Failing to include a Date header field in the request would
    require the server to use the instant it received or began processing
    the request as the baseline for determining how long the client has
    been waiting which could yield unintended results.

I'm not totally convinced that taking the Date request header field into 
account is necessary given the additional complexity; what do others 
think?

3.5.  The "strict" and "lenient" Processing Preferences

Editorial: why are "strict" and "lenient" described in a single section, 
while "return-representation" and "return-minimal" are not?

    An example request specifying the "strict" preference:

      POST /collection HTTP/1.1
      Host: example.org
      Content-Type: text/plain
      Prefer: strict

    An example request specifying the "lenient" preference:

      POST /collection HTTP/1.1
      Host: example.org
      Content-Type: text/plain
      Prefer: lenient

I like examples, but too much is too much :-)


4.  IANA Considerations

    The 'Prefer' header field should be added to the Permanent Message
    Header Fields registry defined in [RFC3864]
    (http://www.iana.org/assignments/message-headers/perm-headers.html).

       Header field name: Prefer
       Applicable Protocol: HTTP
       Status:

"standard", right?


5.  Security Considerations

    Specific preferences requested by a client can introduce security
    considerations and concerns beyond those discussed in HTTP/1.1 Parts
    1 [I-D.ietf-httpbis-p1-messaging], 2 [I-D.ietf-httpbis-p2-semantics],
    3 [I-D.ietf-httpbis-p3-payload], 4 [I-D.ietf-httpbis-p4-conditional],

There is no spoon^h^h^h^h^hPart 3.

    5 [I-D.ietf-httpbis-p5-range], 6 [I-D.ietf-httpbis-p6-cache], and 7
    [I-D.ietf-httpbis-p7-auth].  Implementors must refer to the
    specifications and descriptions of each preference to determine the
    security considerations relevant to each.



Best regards, Julian

From sm@resistor.net  Fri Oct  5 08:53:02 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 425F121F8783 for <ietf@ietfa.amsl.com>; Fri,  5 Oct 2012 08:53:02 -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.006, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id McHnFPCkygyO for <ietf@ietfa.amsl.com>; Fri,  5 Oct 2012 08:53:01 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 9BECD21F8768 for <ietf@ietf.org>; Fri,  5 Oct 2012 08:53:01 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id q95FqtaG002816 for <ietf@ietf.org>; Fri, 5 Oct 2012 08:52:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1349452379; bh=JfM257/X+2HfGz2wBcnhckfRQA9QYO40V3i6/lzGkA0=; h=Date:To:From:Subject:In-Reply-To:References:Cc; b=qudyOMwQbfdZFzVg+KRqBCKwemwweW9Y1wHf3mUCk4HqPOlER3rYJJR0QRoiYHPF1 unAJfxD0t+gF5PKHxZDQ+3Nr7J49C5ammMMcUX74iIoFgy/meLku2J6UdveJxpmyK4 Ih4+cZIhHAkEZrWDjbXV1D9+7Ry8U5O0WIzacBPo=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1349452379; i=@resistor.net; bh=JfM257/X+2HfGz2wBcnhckfRQA9QYO40V3i6/lzGkA0=; h=Date:To:From:Subject:In-Reply-To:References:Cc; b=Yy70+QUDaZoB1JT4fH/5jTfnllN3Ktc+92KjN5F911Gq2ijrOe4ntsQYDeVp8P3Pn U/5GDs2KUsV1urs44EdOuE7SMjUFG3YPhvKxfMOyxcKXyOz339IezzGzBDb0z3RKBX GmZvo5M2iea270NnDj2dEBLSZOdiL4PYgV7EJhL4=
Message-Id: <6.2.5.6.2.20121005080940.09edb488@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 05 Oct 2012 08:38:53 -0700
To: ietf@ietf.org
From: SM <sm@resistor.net>
Subject: Re: Last Call: RFC 5011 (Automated Updates of DNS Security (DNSSEC) Trust Anchors) to Internet Standard
In-Reply-To: <20121005144802.1972.16798.idtracker@ietfa.amsl.com>
References: <20121005144802.1972.16798.idtracker@ietfa.amsl.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Oct 2012 15:53:02 -0000

At 07:48 05-10-2012, IESG Secretary wrote:
>    (2) There are no errata against the specification that would cause a
>        new implementation to fail to interoperate with deployed ones.

I commend the author for writing a specification without any 
mistakes.  That's a lost art in the IETF.

>Note that RFC 5011 does include normative references to RFC 3755, RFC
>4033, RFC 4034 and RFC 4035 that will become down-refs if RFC 5011 is
>reclassified as "Internet Standard."  These down-refs do not preclude
>reclassification of RFC 5011 under the criteria of RFC 6410.

draft-ietf-dnsext-dnssec-bis-updates-20 updates RFC 4033, RFC 4034 
and RFC 4035.  The normative references in RFC 5011 might have to be 
updated accordingly.

Regards,
-sm 


From sm@elandsys.com  Fri Oct  5 09:27:43 2012
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C19AC21F8687 for <ietf@ietfa.amsl.com>; Fri,  5 Oct 2012 09:27:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.58
X-Spam-Level: 
X-Spam-Status: No, score=-102.58 tagged_above=-999 required=5 tests=[AWL=0.019, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xhrfDtoaFo98 for <ietf@ietfa.amsl.com>; Fri,  5 Oct 2012 09:27:43 -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 F3F6E21F85C3 for <ietf@ietf.org>; Fri,  5 Oct 2012 09:27:42 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([41.136.236.145]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id q95GRURW017013 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 5 Oct 2012 09:27:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1349454461; bh=Fab5T6jky3vVwEBHg24UuFBK1mK/i9PX8WZ3l+NynO8=; h=Date:To:From:Subject:Cc; b=4Xok8mmKZ70E+aVSW3mlMPqb3x/5p/Ca57fS1lbPshn1Yc4FNI77lCERZtqmWasdZ KvH8jFvtDpZrsww5AverHYQ2oXOZ+u4uPjPBLB1wFojPE4dMddgR3Gk88skbHc85TN fnuP9k1wl5QlvRrg49alZlMKTInH0zFfUUbFZ42M=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1349454461; i=@elandsys.com; bh=Fab5T6jky3vVwEBHg24UuFBK1mK/i9PX8WZ3l+NynO8=; h=Date:To:From:Subject:Cc; b=deAOnaGmqjY7Gn7enxH6xCrcy/2iqgbuTr8M602JZEvdVptfCJolSYysQOa9sS04m 2IoWMH/LfzlgBeZyNa1uoTes6cwCI7w9axAeXCqf2e3+v3aBHe/Q5Ai8VrLMX2Q7wH phAaXdp94Neeyu/YYPelYLt+dv9h/rC1vvRcu/94=
Message-Id: <6.2.5.6.2.20121005090223.0b4074d0@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 05 Oct 2012 09:26:08 -0700
To: verizon-services@verizon.com
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Commercial email from the Verizon Online Marketing Team
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, 05 Oct 2012 16:27:43 -0000

Dear Verizon,

I received a commercial email from the Verizon Online Marketing 
Team.  The message is DKIM-signed by netsender1.com.  Is Verizon 
collecting email addresses from IETF mailing lists or IETF Contributions?

Regards,
S. Moonesamy


From tglassey@earthlink.net  Fri Oct  5 10:17:20 2012
Return-Path: <tglassey@earthlink.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 08ADA21F87C7 for <ietf@ietfa.amsl.com>; Fri,  5 Oct 2012 10:17:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.642
X-Spam-Level: 
X-Spam-Status: No, score=-2.642 tagged_above=-999 required=5 tests=[AWL=-0.043, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id b8LhbkWCt4IY for <ietf@ietfa.amsl.com>; Fri,  5 Oct 2012 10:17:19 -0700 (PDT)
Received: from elasmtp-kukur.atl.sa.earthlink.net (elasmtp-kukur.atl.sa.earthlink.net [209.86.89.65]) by ietfa.amsl.com (Postfix) with ESMTP id 358A921F87C1 for <ietf@ietf.org>; Fri,  5 Oct 2012 10:17:19 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=dR7+2JXIzJYoHn6fvkIxgMUjmHgxIqsKnAirkWS/VFzZ+vM9wTvoTAVFxFYtd4qb; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [67.180.133.21] (helo=[192.168.15.2]) by elasmtp-kukur.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from <tglassey@earthlink.net>) id 1TKBWY-0001bK-HJ; Fri, 05 Oct 2012 13:17:18 -0400
Message-ID: <506F1618.60800@earthlink.net>
Date: Fri, 05 Oct 2012 10:17:12 -0700
From: tglassey <tglassey@earthlink.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: "Dale R. Worley" <worley@ariadne.com>
Subject: Re: Proposed BCP addition - No-Late-Patent-Filing Rights - contract provision for BCP/NoteWell - Re: [Nea] IPR Disclosure: Cisco's Statement of IPR Related to draft-ietf-nea-pt-tls-07
References: <201210051603.q95G3PAX010579@freeze.ariadne.com>
In-Reply-To: <201210051603.q95G3PAX010579@freeze.ariadne.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 01b7a7e171bdf5911aa676d7e74259b7b3291a7d08dfec79691e73a7b22afd932e9857286b6ee453350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 67.180.133.21
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Oct 2012 17:17:20 -0000

On 10/5/2012 9:03 AM, Dale R. Worley wrote:
>> From: tglassey <tglassey@earthlink.net>
>>
>> But fixing this process is actually VERY SIMPLE... Just a 'component of
>> an updated BCP which contractually commits that IETF members and their
>> sponsors may not engage in submarining' its actually pretty simple to
>> stop this... you folks just have to want to.
> Unless someone has already constructed contracts to do this in some
> similar circumstance and time has shown that the contracts work as
> intended, I wouldn't assert that it is known to be simple.
Dale -
The contracts are airtight and supported through items like the Federal 
and State Courts ruling about the contractual strength of NDA agreements 
in rulings like Grail Semi v Mitsubishi. In this case the contract is 
the exact opposite of a NDA it is a guaranteed disclosure agreement - a 
no secrets here variant so this is in fact a no-brainer to solve.

Yes - the Jury may have screwed up the damage calculation but not the 
issue of whether the NDA controlled relationship was enforceable and 
that is the key. It is ...

Again - to fix this issue all you have to do is want to...

Todd
> Certainly
> there are many times in protocol design where conceptually simple
> goals prove to be remarkably difficult to achieve in practice.  There
> is no reason that believe that similar problems don't show up in the
> legal field.
>
> That's not to say that this proposal is a bad idea.  But let's not
> assume that it will take little work to achieve.
>
> Dale
>
>
> -----
> No virus found in this message.
> Checked by AVG - www.avg.com
> Version: 2013.0.2677 / Virus Database: 2591/5810 - Release Date: 10/04/12
>
>


-- 
Regards TSG
"Ex-Cruce-Leo"

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


From martin.thomson@gmail.com  Fri Oct  5 10:22:07 2012
Return-Path: <martin.thomson@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 382DF21F87C1 for <ietf@ietfa.amsl.com>; Fri,  5 Oct 2012 10:22:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.688
X-Spam-Level: 
X-Spam-Status: No, score=-3.688 tagged_above=-999 required=5 tests=[AWL=-0.089, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L4rx78ewHZCH for <ietf@ietfa.amsl.com>; Fri,  5 Oct 2012 10:22:06 -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 D279121F87BE for <ietf@ietf.org>; Fri,  5 Oct 2012 10:22:04 -0700 (PDT)
Received: by mail-lb0-f172.google.com with SMTP id k13so1708291lbo.31 for <ietf@ietf.org>; Fri, 05 Oct 2012 10:22:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=6QvENKP1GqaKXdbyoIX/kpMYA0pzDKdDzLz4AU8xkI0=; b=fYDS7XSfwOaRryyTb7aVP7VeXVXUkW1HUQHkBp9KIIPsSWOIxmmh2NHP7qNlm1wynF bBMGap57dhLkLqP1cN3ta/bUgorvwbULeG40Oc+weHPbWSqDRVN+j0ofHlMP7i1XQjqN kDs7A+agicVtUELmS7SJE5k6Ba/mKCwTkwiHFepBqENDhVTQwlTthS9YPfiKK5Ah5vs1 1jZ+7TwG6fDaDaUfW4t36vviC2bkuxZfH0dD7IwyUXj2Ge0ZCe6kKit7Qx2C2kPUcK+i rIED+5ePdFB1kcO20g7zI1YfKwQgJojMdUPaxVC3gmzRpUd2PwKg3vHwJIhBMw5W2aia lAog==
MIME-Version: 1.0
Received: by 10.112.25.34 with SMTP id z2mr16352lbf.21.1349457723747; Fri, 05 Oct 2012 10:22:03 -0700 (PDT)
Received: by 10.112.83.2 with HTTP; Fri, 5 Oct 2012 10:22:03 -0700 (PDT)
In-Reply-To: <506EF8FA.1030100@gmx.de>
References: <20120914184457.16683.33382.idtracker@ietfa.amsl.com> <6.2.5.6.2.20120914153648.09f87700@resistor.net> <506EF8FA.1030100@gmx.de>
Date: Fri, 5 Oct 2012 10:22:03 -0700
Message-ID: <CABkgnnXkHdVcK4fa0p2MPox7RTruOQCWVa7UCuPNLy-b4yUiVg@mail.gmail.com>
Subject: Re: Last Call: <draft-snell-http-prefer-14.txt> (Prefer Header for HTTP) to Proposed Standard
From: Martin Thomson <martin.thomson@gmail.com>
To: Julian Reschke <julian.reschke@gmx.de>
Content-Type: text/plain; charset=UTF-8
Cc: SM <sm@resistor.net>, James M Snell <jasnell@gmail.com>, ietf@ietf.org, HTTP Working Group <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: Fri, 05 Oct 2012 17:22:07 -0000

On 5 October 2012 08:12, Julian Reschke <julian.reschke@gmx.de> wrote:
> 3.4.  The "wait" Preference
> I'm not totally convinced that taking the Date request header field into
> account is necessary given the additional complexity; what do others think?

I said as much in my GenART review:
http://www.ietf.org/mail-archive/web/gen-art/current/msg07790.html

Having had experience implementing this exact feature, relying on Date
isn't going to work.

From john-ietf@jck.com  Fri Oct  5 11:06: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 2C7FC21F87E4; Fri,  5 Oct 2012 11:06:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.404
X-Spam-Level: 
X-Spam-Status: No, score=-102.404 tagged_above=-999 required=5 tests=[AWL=-0.105, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DFLzYmXv1Dfm; Fri,  5 Oct 2012 11:06:43 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 5F32721F87DC; Fri,  5 Oct 2012 11:06:43 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1TKCIF-000IeJ-Rs; Fri, 05 Oct 2012 14:06:35 -0400
Date: Fri, 05 Oct 2012 14:06:26 -0400
From: John C Klensin <john-ietf@jck.com>
To: =?UTF-8?Q?Jo=C3=A3o_Damas?= <joao@bondis.org>
Subject: Re: [dnsext] Last Call: <draft-ietf-dnsext-rfc2671bis-edns0-09.txt> (Extension Mechanisms for DNS (EDNS(0))) to Internet Standard
Message-ID: <1E32ACCB0F8FA9E01D3DCB5B@JcK-HP8200.jck.com>
In-Reply-To: <DC14BFC8-601F-4E38-B1C8-3A5112033ECA@bondis.org>
References: <20120930145325.21053.67854.idtracker@ietfa.amsl.com> <56DB6FE506A144D1183B93A8@JcK-HP8200.jck.com> <506B01D1.9080708@ogud.com> <8F3DCBA9A3AF566810CD1061@JcK-HP8200.jck.com> <506B6BE9.2000805@ogud.com> <20121003011556.526A82873A5E@drugs.dv.isc.org> <84187E41-0CEC-4CA2-801D-5AB1171FFF9B@bondis.org> <396CFDC14B6FEF29A37A2FFF@JcK-HP8200.jck.com> <DC14BFC8-601F-4E38-B1C8-3A5112033ECA@bondis.org>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Cc: 'IETF-Discussion list' <ietf@ietf.org>, Olafur Gudmundsson <ogud@ogud.com>, 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, 05 Oct 2012 18:06:44 -0000

--On Friday, October 05, 2012 10:29 +0200 Jo=C3=A3o Damas
<joao@bondis.org> wrote:

>...
>> IMO, this discussion has turned up two ways in which the case
>> for eliminating the possibility of additional label types
>> could be made:
>>=20
>> (2.1) Demonstrating that simply having the capability defined
>> and available in principle is somehow harmful.

> People here can correct me, as my memory is fuzzy, but binary
> labels did cause harm to several deployed implementations.
> Don't know if this is just case in favour of natural =
selection.

Again, I'm not defending binary labels.  Many people thought
they were a good idea at the time.  But, just as "binary labels
failed" is a good argument for deprecating binary labels but not
a good argument for deprecating label types generally, "binary
labels caused harm" (assuming that is the case) would not be a
basis for inferring that all labels types would cause harm, much
less that retaining the capability for using extended label
types would be harmful.

Just as "some cows are brown and all cows are animals" doesn't
tell you a thing about the color of all animals, "binary labels
were a bad idea and binary labels are an instance of extended
label types" doesn't constitute an argument for deprecating
label types.

>> (2.2) The WG has consensus on a bright line that defines the
>> nature of proposals that would require going to DNSng rather
>> than EDNSx-type extensions to the current model, has =
concluded
>> that any extensions or alterations to the label definition of
>> 1034/1035 would require crossing that line, and is prepared =
to
>> document that line and get IETF consensus on it (either as
>> part of this document or one normatively referenced from it).
=20
> Pretty much, that is my understanding. It is quite possible
> that this has been a position reached over many iterations of
> discussions and is not actually documented anywhere.

If there is a bright line, it would definitely benefit the
broader community to be able to see a description and discuss
it.  If there is only a general feeling in the WG... well, that
doesn't count for much, especially given the history of
disagreements about what the base DNS specifications say and
what assorted terminology means.

   john


From martin.thomson@gmail.com  Fri Oct  5 11:12:28 2012
Return-Path: <martin.thomson@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B24D021F87FE for <ietf@ietfa.amsl.com>; Fri,  5 Oct 2012 11:12:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.776
X-Spam-Level: 
X-Spam-Status: No, score=-3.776 tagged_above=-999 required=5 tests=[AWL=-0.177, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bFqm-FxIgy1C for <ietf@ietfa.amsl.com>; Fri,  5 Oct 2012 11:12:28 -0700 (PDT)
Received: from mail-la0-f44.google.com (mail-la0-f44.google.com [209.85.215.44]) by ietfa.amsl.com (Postfix) with ESMTP id E576D21F87F9 for <ietf@ietf.org>; Fri,  5 Oct 2012 11:12:27 -0700 (PDT)
Received: by mail-la0-f44.google.com with SMTP id b11so1173354lam.31 for <ietf@ietf.org>; Fri, 05 Oct 2012 11:12: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; bh=dKZwRNDsoV1UmWWElBZ+VYzDkgcZ/WnfiUexxL4kp1s=; b=EnqPxo/vqS9ta2Wv7LYHiuziTH7kkO6plyRHb1Azm53fe5Wf0Ds/kii/lWYHc7BGYZ Wo9NUTluLM7u6qu/hJi1O5fZnNCv1ugM0p5HGCkD+gRJG3+w9Mxj5i8EjNYjYpsoaCE2 o6O2hGwTV/GVt5Nc6HUcYx8+XPaHs4D7tp9AsXB/nB4+83We8tTgTVtCLnvp/EOza/bA 60cyo4Ne/Mjr9IfwXKg+G+NFjFSFGu8uxdoiPMfIP8lqKnw7ykyFdXoeFeTfwh01jPCM 6qv0LFfWp1S/XolQW4+gqfhf7TZcon8oEYtjilbjiAADgBQUODI/fA3/2PWp87n/CML8 kB1w==
MIME-Version: 1.0
Received: by 10.112.100.197 with SMTP id fa5mr4122122lbb.59.1349460746934; Fri, 05 Oct 2012 11:12:26 -0700 (PDT)
Received: by 10.112.83.2 with HTTP; Fri, 5 Oct 2012 11:12:26 -0700 (PDT)
In-Reply-To: <CABP7Rbc81Yo+Xp4QdJKH=Kq=v8F1==gAnhGjaKASvVfKis_fRw@mail.gmail.com>
References: <20120914184457.16683.33382.idtracker@ietfa.amsl.com> <6.2.5.6.2.20120914153648.09f87700@resistor.net> <506EF8FA.1030100@gmx.de> <CABkgnnXkHdVcK4fa0p2MPox7RTruOQCWVa7UCuPNLy-b4yUiVg@mail.gmail.com> <CABP7Rbc81Yo+Xp4QdJKH=Kq=v8F1==gAnhGjaKASvVfKis_fRw@mail.gmail.com>
Date: Fri, 5 Oct 2012 11:12:26 -0700
Message-ID: <CABkgnnWvbjkmXe_orAKwLuq8J7LJ2uCgcW7Ry=mhBj=gOTgYHA@mail.gmail.com>
Subject: Re: Last Call: <draft-snell-http-prefer-14.txt> (Prefer Header for HTTP) to Proposed Standard
From: Martin Thomson <martin.thomson@gmail.com>
To: James M Snell <jasnell@gmail.com>
Content-Type: text/plain; charset=UTF-8
Cc: Julian Reschke <julian.reschke@gmx.de>, SM <sm@resistor.net>, ietf@ietf.org, HTTP Working Group <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: Fri, 05 Oct 2012 18:12:28 -0000

On 5 October 2012 10:42, James M Snell <jasnell@gmail.com> wrote:
> I could drop the Date header recommendation altogether and stress in the
> text that good clock synchronization and predictable latency is required for
> the wait preference to be used effectively.

The feature is useful, I agree.  The problem is that - as defined -
the server needs to guess something about the times on the client in
order to implement this reliably.

Relying on clock synchronization is not realistic.  Even in controlled
environments, errors are commonplace.

Even the simple case shows a problem:
  a: client sends request
  b: server receives request
  c: time passes
  d: server responds to request
  e: client receives response

You require that the time be a measure of a->e.  The server has no way
to determine what that time is.

An alternative would be to make the requirement apply to b->d.  That
is something that the server has direct control over.  The client then
gains a little extra work, but at least they are in a position to
measure a->b + d->e.  In any case, with low or predictable latency, I
doubt that the addition of a->b + d->e will have any significant
impact on whether the information is useful to the client.  Especially
given that times are expressed in seconds, not microseconds.

From jgs@juniper.net  Fri Oct  5 13:32:52 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 8ED1C21F858F; Fri,  5 Oct 2012 13:32:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.352
X-Spam-Level: 
X-Spam-Status: No, score=-3.352 tagged_above=-999 required=5 tests=[AWL=-1.886, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, SARE_RAND_6=2, UNRESOLVED_TEMPLATE=3.132]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 53OXHBAxspQF; Fri,  5 Oct 2012 13:32:51 -0700 (PDT)
Received: from exprod7og103.obsmtp.com (exprod7og103.obsmtp.com [64.18.2.159]) by ietfa.amsl.com (Postfix) with ESMTP id 5B7CB21F8582; Fri,  5 Oct 2012 13:32:51 -0700 (PDT)
Received: from P-EMHUB03-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob103.postini.com ([64.18.6.12]) with SMTP ID DSNKUG9D86hz7B3wH9Hw5CAmqOKjwvH8jglB@postini.com; Fri, 05 Oct 2012 13:32:51 PDT
Received: from P-CLDFE02-HQ.jnpr.net (172.24.192.60) by P-EMHUB03-HQ.jnpr.net (172.24.192.37) with Microsoft SMTP Server (TLS) id 8.3.213.0; Fri, 5 Oct 2012 13:31:15 -0700
Received: from o365mail.juniper.net (207.17.137.149) by o365mail.juniper.net (172.24.192.60) with Microsoft SMTP Server id 14.1.355.2; Fri, 5 Oct 2012 13:31:14 -0700
Received: from tx2outboundpool.messaging.microsoft.com (65.55.88.14) by o365mail.juniper.net (207.17.137.149) with Microsoft SMTP Server (TLS) id 14.1.355.2; Fri, 5 Oct 2012 13:33:02 -0700
Received: from mail170-tx2-R.bigfish.com (10.9.14.248) by TX2EHSOBE003.bigfish.com (10.9.40.23) with Microsoft SMTP Server id 14.1.225.23; Fri, 5 Oct 2012 20:31:10 +0000
Received: from mail170-tx2 (localhost [127.0.0.1])	by mail170-tx2-R.bigfish.com (Postfix) with ESMTP id BFD42600DD; Fri,  5 Oct 2012 20:31:10 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.240.101; KIP:(null); UIP:(null); (null); H:BL2PRD0510HT002.namprd05.prod.outlook.com; R:internal; EFV:INT
X-SpamScore: -21
X-BigFish: PS-21(zz98dI9371Id6eah936eIc85dh1432Izz1202h1d1ah1d2ah1082kzz1033IL17326ah8275dhz2dh2a8h668h839hd25he5bhf0ah107ah1288h12a5h12bdh137ah139eh1441h1155h)
Received: from mail170-tx2 (localhost.localdomain [127.0.0.1]) by mail170-tx2 (MessageSwitch) id 1349469068666404_6305; Fri,  5 Oct 2012 20:31:08 +0000 (UTC)
Received: from TX2EHSMHS024.bigfish.com (unknown [10.9.14.249])	by mail170-tx2.bigfish.com (Postfix) with ESMTP id 9B4AB34007A; Fri,  5 Oct 2012 20:31:08 +0000 (UTC)
Received: from BL2PRD0510HT002.namprd05.prod.outlook.com (157.56.240.101) by TX2EHSMHS024.bigfish.com (10.9.99.124) with Microsoft SMTP Server (TLS) id 14.1.225.23; Fri, 5 Oct 2012 20:31:07 +0000
Received: from jgs-sslvpn-nc.jnpr.net (66.129.224.52) by pod51010.outlook.com (10.255.100.37) with Microsoft SMTP Server (TLS) id 14.16.207.9; Fri, 5 Oct 2012 20:31:05 +0000
Content-Type: multipart/alternative; boundary="Apple-Mail=_A23C14FB-A124-4C57-AA7C-9360D38C41D6"
MIME-Version: 1.0 (Mac OS X Mail 6.1 \(1498\))
Subject: Re: Gen-ART Last Call Review of draft-ietf-sidr-pfx-validate-09
From: John Scudder <jgs@juniper.net>
In-Reply-To: <CACvMsLG97q4Zvo-xQ=L_u6C_YCTAiTuOujFoyUsM1P+NY-prmA@mail.gmail.com>
Date: Fri, 5 Oct 2012 16:30:54 -0400
Message-ID: <2DEE274C-EDC7-4353-B8E7-A4CCEAF1A80E@juniper.net>
References: <CACvMsLG97q4Zvo-xQ=L_u6C_YCTAiTuOujFoyUsM1P+NY-prmA@mail.gmail.com>
To: Pete McCann <mccap@petoni.org>, Randy Bush <randy@psg.com>
X-Mailer: Apple Mail (2.1498)
X-Originating-IP: [66.129.224.52]
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
X-FOPE-CONNECTOR: Id%12219$Dn%TOOLS.IETF.ORG$RO%2$TLS%5$FQDN%onpremiseedge-1018244.customer.frontbridge.com$TlsDn%o365mail.juniper.net
X-FOPE-CONNECTOR: Id%12219$Dn%IETF.ORG$RO%2$TLS%5$FQDN%onpremiseedge-1018244.customer.frontbridge.com$TlsDn%o365mail.juniper.net
X-FOPE-CONNECTOR: Id%12219$Dn%PETONI.ORG$RO%2$TLS%5$FQDN%onpremiseedge-1018244.customer.frontbridge.com$TlsDn%o365mail.juniper.net
X-FOPE-CONNECTOR: Id%12219$Dn%PSG.COM$RO%2$TLS%5$FQDN%onpremiseedge-1018244.customer.frontbridge.com$TlsDn%o365mail.juniper.net
Cc: gen-art@ietf.org, draft-ietf-sidr-pfx-validate.all@tools.ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Oct 2012 20:32:52 -0000

--Apple-Mail=_A23C14FB-A124-4C57-AA7C-9360D38C41D6
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"

Pete,

Your Section 4 change looks fine to me, thanks.

The "monkey-in-the-middle" terminology is Randy's and I will defer to =
him. (I've added him to the To:)

--John

On Oct 1, 2012, at 6:56 PM, Pete McCann <mccap@petoni.org> wrote:

> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
>=20
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>=20
> Please resolve these comments along with any other Last Call comments
> you may receive.
>=20
> Document:  draft-ietf-sidr-pfx-validate-09
> Reviewer:  Peter McCann
> Review Date:  2012-10-01
> IETF LC End Date:  2012-10-01
> IESG Telechat date: unknown
>=20
> Summary: Ready
>=20
> Major issues: None
>=20
> Minor issues:
>=20
> Section 4:
>    An "affected prefix" is any prefix that
>   was matched by a deleted or updated mapping, or could be matched by
>   an added mapping.
> SHOULD BE:
>   An "affected prefix" is any prefix that
>   was matched by a deleted or updated mapping, or could be matched by
>   an added or updated mapping.
>=20
> Nits/editorial comments:
>=20
> Abstract:
>   monkey-in-the-middle
> That's a game of keep-away.  Did you mean man-in-the-middle?  Perhaps
> this is a technical term that has been discussed on the mailing list.
>=20


--Apple-Mail=_A23C14FB-A124-4C57-AA7C-9360D38C41D6
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html; charset="iso-8859-1"

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Diso-8859-1"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
">Pete,<div><br></div><div>Your Section 4 change looks fine to me, =
thanks.</div><div><br></div><div>The "monkey-in-the-middle" terminology =
is Randy's and I will defer to him. (I've added him to the =
To:)</div><div><br></div><div>--John</div><div><br><div><div>On Oct 1, =
2012, at 6:56 PM, Pete McCann &lt;<a =
href=3D"mailto:mccap@petoni.org">mccap@petoni.org</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite">I am the assigned Gen-ART reviewer for this draft. For =
background on<br>Gen-ART, please see the FAQ at<br><br>&lt;<a =
href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq">http://wi=
ki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq</a>&gt;.<br><br>Please =
resolve these comments along with any other Last Call comments<br>you =
may receive.<br><br>Document: =
&nbsp;draft-ietf-sidr-pfx-validate-09<br>Reviewer: &nbsp;Peter =
McCann<br>Review Date: &nbsp;2012-10-01<br>IETF LC End Date: =
&nbsp;2012-10-01<br>IESG Telechat date: unknown<br><br>Summary: =
Ready<br><br>Major issues: None<br><br>Minor issues:<br><br>Section =
4:<br> &nbsp;&nbsp;&nbsp;An "affected prefix" is any prefix that<br> =
&nbsp;&nbsp;was matched by a deleted or updated mapping, or could be =
matched by<br> &nbsp;&nbsp;an added mapping.<br>SHOULD BE:<br> =
&nbsp;&nbsp;An "affected prefix" is any prefix that<br> &nbsp;&nbsp;was =
matched by a deleted or updated mapping, or could be matched by<br> =
&nbsp;&nbsp;an added or updated mapping.<br><br>Nits/editorial =
comments:<br><br>Abstract:<br> =
&nbsp;&nbsp;monkey-in-the-middle<br>That's a game of keep-away. =
&nbsp;Did you mean man-in-the-middle? &nbsp;Perhaps<br>this is a =
technical term that has been discussed on the mailing =
list.<br><br></blockquote></div><br></div></body></html>=

--Apple-Mail=_A23C14FB-A124-4C57-AA7C-9360D38C41D6--

From martin.thomson@gmail.com  Fri Oct  5 14:18:41 2012
Return-Path: <martin.thomson@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 38CBA21F8532 for <ietf@ietfa.amsl.com>; Fri,  5 Oct 2012 14:18:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.854
X-Spam-Level: 
X-Spam-Status: No, score=-3.854 tagged_above=-999 required=5 tests=[AWL=-0.255, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hnzfj0QNUDy6 for <ietf@ietfa.amsl.com>; Fri,  5 Oct 2012 14:18:40 -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 1558F21F84FD for <ietf@ietf.org>; Fri,  5 Oct 2012 14:18:39 -0700 (PDT)
Received: by mail-lb0-f172.google.com with SMTP id k13so1872634lbo.31 for <ietf@ietf.org>; Fri, 05 Oct 2012 14:18:39 -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=9H/afNv82bheda1SUJVlEkBFwCpPtbcYi20R/CfqPYg=; b=A3S/3cEaPR0M+KPILcTppafnpFtDbEsymuCcHeRamXeZjzQvpcHBUG68XYAE9oXZwy ggL8+1g+2o/5BdTR/Xd+d1Iq3C5OTXCTfTxAdbj/leez4E8S66MqbierxqaMgIESEVb0 odxwfioLvD0W9AqPYBsZIau6iB60uqNdaHG2w4dAX3pj/1sI9wXqHQXn0+8fgSuNvZja CMBgxRauqSlOe6zrMW26mrxP1z+zP0X/+I5YfUvHJWZIc1tLnVERX03M5cUmNZ9eBDBo mnSkfzUB9zHogE3U09JjB6xhaRtaqpEBJLSrWM0XgPpjR3RLGGtzZ8T9HzzEopLlUgXF /J5w==
MIME-Version: 1.0
Received: by 10.152.113.165 with SMTP id iz5mr7739935lab.48.1349471918772; Fri, 05 Oct 2012 14:18:38 -0700 (PDT)
Received: by 10.112.83.2 with HTTP; Fri, 5 Oct 2012 14:18:38 -0700 (PDT)
In-Reply-To: <CABP7RbeTd=43Pq56raCXOVO6NZhOX3yKb1_LL--EqroUEXiCzw@mail.gmail.com>
References: <20120914184457.16683.33382.idtracker@ietfa.amsl.com> <6.2.5.6.2.20120914153648.09f87700@resistor.net> <506EF8FA.1030100@gmx.de> <CABkgnnXkHdVcK4fa0p2MPox7RTruOQCWVa7UCuPNLy-b4yUiVg@mail.gmail.com> <CABP7Rbc81Yo+Xp4QdJKH=Kq=v8F1==gAnhGjaKASvVfKis_fRw@mail.gmail.com> <CABkgnnWvbjkmXe_orAKwLuq8J7LJ2uCgcW7Ry=mhBj=gOTgYHA@mail.gmail.com> <CABP7RbeTd=43Pq56raCXOVO6NZhOX3yKb1_LL--EqroUEXiCzw@mail.gmail.com>
Date: Fri, 5 Oct 2012 14:18:38 -0700
Message-ID: <CABkgnnWXRVeUDAfmJgfyJZyCYzn-Ktn+=ZbgRc5jKMBYJzGRew@mail.gmail.com>
Subject: Re: Last Call: <draft-snell-http-prefer-14.txt> (Prefer Header for HTTP) to Proposed Standard
From: Martin Thomson <martin.thomson@gmail.com>
To: James M Snell <jasnell@gmail.com>
Content-Type: text/plain; charset=UTF-8
Cc: Julian Reschke <julian.reschke@gmx.de>, SM <sm@resistor.net>, ietf@ietf.org, HTTP Working Group <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: Fri, 05 Oct 2012 21:18:41 -0000

An improvement.  Though the following doesn't read quite right to me:

  It is important to consider that there are many -- largely
  unpredictable -- factors that can influence the amount of time it
  takes a server to process a request. The period of time specified
  is not intended to be treated as a strictly defined "hard limit"
  but rather as a hint about the client's expectation.

I'm not sure that it's "mysterious forces" at the server that are the
issue in this design.  Nor is it the case that this would ever be a
hard limit.  As a preference, it's always option.  How about:

  Messages spend some time traversing the network and being
  processed by intermediaries.  This increases the time that a
  client awaits a response in addition to any time spent at a
  server.  A client that has strict timing requirements can estimate
  these factors and adjust the wait value accordingly.

Note that "intermediaries" could include the HTTP stack in both client
and server.

And maybe:

  As with other preferences, the wait preference could be ignored.
  Clients can abandon requests that take longer than they are
  prepared to wait.

--Martin

On 5 October 2012 11:28, James M Snell <jasnell@gmail.com> wrote:
> How about the following change:
>
> <snip>
>
>   The "wait" preference can be used to establish an upper bound on the
>   length of time, in seconds, the client expects it will take the server
>   to process the request once it has been received. In the case that
>   generating a response will take longer than the time specified,
>   the server, or proxy, can choose to utilize an asynchronous processing
>   model by returning -- for example -- a "202 Accepted" response.
>
>   ABNF:
>     wait = "wait" BWS "=" BWS delta-seconds
>
>   It is important to consider that there are many -- largely
>   unpredictable -- factors that can influence the amount of time it
>   takes a server to process a request. The period of time specified
>   is not intended to be treated as a strictly defined "hard limit"
>   but rather as a hint about the client's expectation.
>
>   For example, a server receiving the following request might choose
>   to respond asynchronously if processing the request will take longer
>   than 10 seconds:
>
>     POST /collection HTTP/1.1
>     Host: example.org
>     Content-Type: text/plain
>     Prefer: return-asynch, wait=10
>
>     {Data}
>
> </snip>
>
> On Fri, Oct 5, 2012 at 11:12 AM, Martin Thomson <martin.thomson@gmail.com>
> wrote:
>>
>> On 5 October 2012 10:42, James M Snell <jasnell@gmail.com> wrote:
>> > I could drop the Date header recommendation altogether and stress in the
>> > text that good clock synchronization and predictable latency is required
>> > for
>> > the wait preference to be used effectively.
>>
>> The feature is useful, I agree.  The problem is that - as defined -
>> the server needs to guess something about the times on the client in
>> order to implement this reliably.
>>
>> Relying on clock synchronization is not realistic.  Even in controlled
>> environments, errors are commonplace.
>>
>> Even the simple case shows a problem:
>>   a: client sends request
>>   b: server receives request
>>   c: time passes
>>   d: server responds to request
>>   e: client receives response
>>
>> You require that the time be a measure of a->e.  The server has no way
>> to determine what that time is.
>>
>> An alternative would be to make the requirement apply to b->d.  That
>> is something that the server has direct control over.  The client then
>> gains a little extra work, but at least they are in a position to
>> measure a->b + d->e.  In any case, with low or predictable latency, I
>> doubt that the addition of a->b + d->e will have any significant
>> impact on whether the information is useful to the client.  Especially
>> given that times are expressed in seconds, not microseconds.
>
>

From simon@josefsson.org  Sat Oct  6 09:50:40 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 4F06421F84F2; Sat,  6 Oct 2012 09:50:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.875
X-Spam-Level: 
X-Spam-Status: No, score=-99.875 tagged_above=-999 required=5 tests=[AWL=0.034, BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, HELO_MISMATCH_COM=0.553, HOST_EQ_STATICB=1.372, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id si9E7xZwVn5g; Sat,  6 Oct 2012 09:50:39 -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 4FD9621F850D; Sat,  6 Oct 2012 09:50:37 -0700 (PDT)
Received: from latte (static-213-115-179-130.sme.bredbandsbolaget.se [213.115.179.130]) (authenticated bits=0) by yxa-v.extundo.com (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id q96GoSMw032734 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Sat, 6 Oct 2012 18:50:29 +0200
From: Simon Josefsson <simon@josefsson.org>
To: "Cantor\, Scott" <cantor.2@osu.edu>
Subject: Re: Last Call: <draft-ietf-abfab-gss-eap-naming-05.txt> (Name Attributes for the GSS-API EAP mechanism) to Proposed Standard
References: <tslwqz6c5te.fsf@mit.edu> <BA63CEAE152A7742B854C678D949138339A52F3E@CIO-KRC-D1MBX01.osuad.osu.edu>
OpenPGP: id=B565716F; url=http://josefsson.org/key.txt
X-Hashcash: 1:22:121006:abfab@ietf.org::yKaWn1UdwdRMBQmw:4uVp
X-Hashcash: 1:22:121006:cantor.2@osu.edu::3uLuMcHIs5R6i2I/:7iXS
X-Hashcash: 1:22:121006:ietf@ietf.org::U+m/2Hhh3eh2mMbK:H+7h
X-Hashcash: 1:22:121006:hartmans@painless-security.com::yoNXcnAALj76nF8a:PoJG
Date: Sat, 06 Oct 2012 18:50:27 +0200
In-Reply-To: <BA63CEAE152A7742B854C678D949138339A52F3E@CIO-KRC-D1MBX01.osuad.osu.edu> (Scott Cantor's message of "Fri, 5 Oct 2012 00:15:32 +0000")
Message-ID: <874nm7v92k.fsf@latte.josefsson.org>
User-Agent: Gnus/5.130006 (Ma Gnus v0.6) Emacs/23.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
X-Virus-Scanned: clamav-milter 0.97.3 at yxa-v
X-Virus-Status: Clean
Cc: Sam Hartman <hartmans@painless-security.com>, "abfab@ietf.org" <abfab@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 06 Oct 2012 16:50:40 -0000

"Cantor, Scott" <cantor.2@osu.edu> writes:

> On 10/4/12 4:58 PM, "Sam Hartman" <hartmans@painless-security.com> wrote:
>
>>Any advice from the SAML community on responding to the following
>>comment from Simon:
>>
>>   If the value is not simple or is empty, then the raw value(s) of the
>>   GSS name attribute MUST be the well-formed serialization of the
>>   <saml:AttributeValue> element(s) encoded as UTF-8.  The "display"
>>   values are implementation-defined.
>>
>>Question: what serialization is intended here?  An example here would
>>make this more clear.
>
> I think that was my text, possibly. I just meant that it's the XML
> representation of the element, but well-formed, meaning that you have to
> make sure any namespaces are declared, etc. so that if a parser were to
> parse that serialization, it would be well-formed XML.

Thanks, now I understand better.  I would feel more comfortable if there
were a precise reference to what "well-formed serialization" means,
especially since there is a MUST here.  It ought to be possible to
determine algorithmically whether something conforms or not.  Sometimes
I get the impression that "well-formed" just refers to syntactical
correctness, whereas namespace considerations are more semantic.
Perhaps the text would be improved by adding a sentence between the two
sentences above like this:

  This means, for example, that the XML code includes all necessary
  namespace declarations, so that a parser is able to parse and
  understand the meaning of the raw value.

If there is a suitable reference to some XML standard, that is probably
better.

/Simon

From glenzorn@gmail.com  Sun Oct  7 00:28:20 2012
Return-Path: <glenzorn@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 859F921F84EC; Sun,  7 Oct 2012 00:28:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.949
X-Spam-Level: 
X-Spam-Status: No, score=-3.949 tagged_above=-999 required=5 tests=[AWL=-0.350, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QJeOIyN2wjX8; Sun,  7 Oct 2012 00:28:19 -0700 (PDT)
Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id 38A9F21F84EA; Sun,  7 Oct 2012 00:28:19 -0700 (PDT)
Received: by mail-pb0-f44.google.com with SMTP id ro8so3203714pbb.31 for <multiple recipients>; Sun, 07 Oct 2012 00:28: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=Xa6g5o0xcjFHO82Ht242m0ngBDIZSArp/jH6CIuiQ6A=; b=WQYq2mEvCOMWxbDQO3asOtatYVP9P3lw6+8kbX6o064bJzsDjVqQZZNXnEkKazhXKH i7ifP2wxhaK1wErNv3SV5xxpRB6QVsvHgrSMCfAKipZiEs0ww9ogmEZnMcdGXuavobpQ q4FrgiuL7FkqXq6Hc126Ro7tOiVsIU2jGPQTJRp81EOkP1RVDSvZjUw36Q4YE9aMzOQM tEREvFP/ZquvStaBwOaSM9XXmV3PwOiFxJrrxHFT/5sXcSLRi+Xs6oz/ymekMXSCWpEm urdxlG1jEOB++nm6OXkeBHd9tgRFqz47iAJamydyfJaBQIXQNehyETOtWaGIkva4iMBA 2kqg==
Received: by 10.68.234.7 with SMTP id ua7mr44345460pbc.91.1349594898753; Sun, 07 Oct 2012 00:28:18 -0700 (PDT)
Received: from [192.168.0.102] (ppp-115-87-90-243.revip4.asianet.co.th. [115.87.90.243]) by mx.google.com with ESMTPS id oi2sm7531203pbb.62.2012.10.07.00.28.15 (version=SSLv3 cipher=OTHER); Sun, 07 Oct 2012 00:28:18 -0700 (PDT)
Message-ID: <50712F0A.1050309@gmail.com>
Date: Sun, 07 Oct 2012 14:28:10 +0700
From: Glen Zorn <glenzorn@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120914 Thunderbird/15.0.1
MIME-Version: 1.0
To: "Black, David" <david.black@emc.com>
Subject: Re: Gen-ART review of draft-ietf-dime-rfc4005bis-11
References: <8D3D17ACE214DC429325B2B98F3AE7120DCD17FD@MX15A.corp.emc.com>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE7120DCD17FD@MX15A.corp.emc.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-dime-rfc4005bis@tools.ietf.org" <draft-ietf-dime-rfc4005bis@tools.ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, "lionel.morand@orange.com" <lionel.morand@orange.com>, "dime@ietf.org" <dime@ietf.org>, "dime-chairs@tools.ietf.org" <dime-chairs@tools.ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 07 Oct 2012 07:28:20 -0000

On 09/18/2012 06:53 AM, Black, David wrote:

> I am the assigned Gen-ART  reviewer for this draft. For background on
 > Gen-ART, please see the FAQ at
 > <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
 >
 > Please resolve these comments along with any other Last Call
 > comments you may receive.
 >
 > Document: draft-ietf-dime-rfc4005bis-11 Reviewer: David L. Black
 > Review Date: September 17, 2012 IETF LC End Date: September 18, 2012
 > IESG Telechat date: (if known)
 >
 > Summary:
 >
 > This draft is on the right track but has open issues, described in
 > the review.
 >
 > This draft is part of a set of drafts that updates the DIAMETER
 > protocol; this draft specifies the application of DIAMETER to AAA for
 > network access. The draft is heavily based on RFC 4005, which it
 > obsoletes, and requires significant DIAMETER familiarity (including
 > familiarity with its companion drafts, starting with the rfc3588bis
 > draft) for complete understanding.
 >
 > The draft is in good shape and reads well. I found one major open
 > issue, a few minor issues, and several nits.
 >
 > Major issues:
 >
 > This draft makes significant use of UTF-8 in its formats (some
 > subsections of sections 4.2, 4.4 and 4.5) for strings that are
 > intended to be compared for equality or processed by protocol
 > participants, but does not contain considerations for Unicode
 > processing that are sufficient to support this usage. Examples of
 > UTF-8 usage in this draft include:
 >
 > - 4.2.5 and 4.2.6: The NAS server may perform authorization based on
 > the Called-Station-Id and Calling-Station-Id AVPs under some
 > circumstances. - 4.4.3: The Callback-Id AVP is intended to be
 > interpreted by the NAS.
 >
 > All use of UTF-8 in this draft relies upon the specification of the
 > UTF8String format in the rfc3588bis draft. That specification is
 > insufficient to support the usage in the above examples, and there
 > are no Unicode considerations in this draft. Even binary comparison
 > of Unicode strings for equality generally requires specification of
 > string preparation (e.g., normalization) in order for string
 > comparison to work as expected.
 >
 > The variety of Unicode strings in this draft makes it important to
 > lay out the Unicode requirements and considerations for each AVP. I
 > see at least 5 classes of possible Unicode
 > requirements/considerations:
 >
 > 1) String preparation so that tests for equality work as expected.
 > This may suffice for the Called-Station-ID AVP (4.2.5) and
 > Calling-Station-ID AVP (4.2.6) if the internal structure of those
 > strings is not used in authorization.

Both those AVPs are specified to contain ASCII encoded as UTF-8.  Is 
string preparation necessary in that case?

> 2) Detailed string format for a
 > string that is processed by a protocol participant, e.g., the
 > Callback-ID AVP (4.4.3).

That format is unknown in this case.
...
> 5) Statement that the string  contains an FQDN, as stated for one case of
 > the Tunnel-Client-Endpoint AVP in 4.5.4. That specific statement is
 > incomplete, as it needs to be accompanied by a normative reference to
 > a document that specifies the format of internationalized domain
 > names, and probably needs to also state which types of labels (e.g.,
 > A-label, U-label) are allowed.
 >
 > Every use of UTF8String in this draft needs to be checked, and most
 > of them are likely to need some attention. The ongoing work in the
 > precis WG may help with some of this, and I would suggest talking to
 > the APP ADs, especially Pete Resnick (hi Pete) before embarking on
 > significant work in this area in order to avoid wasted or duplicated
 > efforts.

OK, this last one bothers me a lot: you /seem /to be suggesting that we 
hold up this draft to wait for the result of a WG which has yet to 
publish a problem statement.  I'm sure that that is not the case, but it 
sure sounds like it.

>
 > Minor Issues:
 >
 > [1] End of Section 2 on p.8:
 >
 > As a result, service cannot be started as a result of a response to
 > an authorization-only request without introducing a significant
 > security vulnerability.
 >
 > Please explain what to do about this - a simple rewrite with a
 > "SHOULD NOT" would suffice, e.g.:
 >
 > As a result, service SHOULD NOT be started as a result of a response
 > to an authorization-only request because that may introduce a
 > significant security vulnerability.

The text in question is descriptive, not prescriptive.at said, however, 
I think that it's not really clear.  I think that it should say 
something like "As a result, a new session cannot be started as a result 
of a response to an authorization-only request without introducing a 
significant security vulnerability."

>
 > This should also be noted in the Security Considerations section.
 >
 > [2] In the message formats in Section 3, QoS-Filter-Rule is
 > inconsistently capitalized.

OK, thanks.

> Also the use of QoSFilterRule  as the
 > format for the QoS-Filter-Rule AVP in Section 4.1.1 is potentially
 > confusing. Please add a sentence in 4.1.1 to say that QoSFilterRule
 > is the format for the QoS-Filter-Rule AVP.
 >
 > [3] Section 4.2.1. In this and the other AVP Flag Rules tables,
 > please explain what the values in the MUST and MUST NOT columns
 > mean.
 >
 > [4] Based on this text in 4.4.9:
 >
 > The use of this AVP is NOT RECOMMENDED; the AVPs defined by
 > Korhonen, et al. [RFC5777] SHOULD be used instead.
 >
 > I would have expected RFC5777 to be a Normative Reference, not an
 > Informative Reference.

I don't care particularly, but I don't think that it's really necessary 
to understand RFC 5777 to understand this document.

>
 > Nits/editorial comments:
 >
 > After the command table in Section 3 and other similar tables, please
 > add a sentence to say that the -Request and -Answer commands in each
 > similarly-named command pair are distinguished by the value of the
 > 'R' bit in the Command Flags field of the command. This is already
 > stated in the command definitions, but the sentence should be added
 > after the table for clarity because each command pair shares a
 > Command Code.
 >
 > idnits 2.12.13 found a few potential nits:
 >
 > == There are 7 instances of lines with non-RFC5735-compliant IPv4
 > addresses in the document. If these are example addresses, they
 > should be changed.
 >
 > That can probably be ignored, as these instances are likely generated
 > by text such as cross-references to Section 4.4.10.1
 >
 > == Missing Reference: 'BASE' is mentioned on line 219, but not
 > defined
 >
 > That's definitely a problem. Was [I-D.ietf-dime-rfc3588bis]
 > intended?

No.  The passage in question is a verbatim quote from RFC 4005.

>
 > -- Possible downref: Non-RFC (?) normative reference: ref.
 > 'ANITypes'
 >
 > That reference would be:
 >
 > [ANITypes] NANPA Number Resource Info, "ANI Assignments",
 > <http://www.nanpa.com/ number_resource_info/
 > ani_ii_assignments.html>.
 >
 > Is that reference sufficiently stable (e.g., IANA-class or better
 > management)?

Yes, I think so.

> My guess is that it is  sufficiently stable, but I'm not
 > the expert.
>
 > -- Obsolete informational reference (is this intentional?): RFC 1334
 > (Obsoleted by RFC 1994)
 >
 > That reference may be intentional,

Yes.

...

From cantor.2@osu.edu  Sun Oct  7 11:19:39 2012
Return-Path: <cantor.2@osu.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 03D0521F8714; Sun,  7 Oct 2012 11:19:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.099
X-Spam-Level: 
X-Spam-Status: No, score=-4.099 tagged_above=-999 required=5 tests=[AWL=-0.500, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id otZ18U5g9Uf8; Sun,  7 Oct 2012 11:19:38 -0700 (PDT)
Received: from va3outboundpool.messaging.microsoft.com (va3ehsobe005.messaging.microsoft.com [216.32.180.31]) by ietfa.amsl.com (Postfix) with ESMTP id 3CD6721F8711; Sun,  7 Oct 2012 11:19:37 -0700 (PDT)
Received: from mail98-va3-R.bigfish.com (10.7.14.240) by VA3EHSOBE004.bigfish.com (10.7.40.24) with Microsoft SMTP Server id 14.1.225.23; Sun, 7 Oct 2012 18:19:36 +0000
Received: from mail98-va3 (localhost [127.0.0.1])	by mail98-va3-R.bigfish.com (Postfix) with ESMTP id DEC953C0127; Sun,  7 Oct 2012 18:19:36 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:164.107.81.43; KIP:(null); UIP:(null); IPV:NLI; H:CIO-KRC-HT03.osuad.osu.edu; RD:cio-krc-ht03.osuad.osu.edu; EFVD:NLI
X-SpamScore: -4
X-BigFish: VPS-4(z551bizbb2dI98dI9371I1432I4015Izz1d77h1202h1d1ah1d2ahzz17326ah8275dhz2fh2a8h668h839h944hd25hf0ah107ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1155h)
Received-SPF: pass (mail98-va3: domain of osu.edu designates 164.107.81.43 as permitted sender) client-ip=164.107.81.43; envelope-from=cantor.2@osu.edu; helo=CIO-KRC-HT03.osuad.osu.edu ; suad.osu.edu ; 
Received: from mail98-va3 (localhost.localdomain [127.0.0.1]) by mail98-va3 (MessageSwitch) id 1349633975520260_11442; Sun,  7 Oct 2012 18:19:35 +0000 (UTC)
Received: from VA3EHSMHS031.bigfish.com (unknown [10.7.14.249])	by mail98-va3.bigfish.com (Postfix) with ESMTP id 7AC442A0044; Sun,  7 Oct 2012 18:19:35 +0000 (UTC)
Received: from CIO-KRC-HT03.osuad.osu.edu (164.107.81.43) by VA3EHSMHS031.bigfish.com (10.7.99.41) with Microsoft SMTP Server (TLS) id 14.1.225.23; Sun, 7 Oct 2012 18:19:35 +0000
Received: from CIO-KRC-D1MBX01.osuad.osu.edu ([fe80::450b:35e6:80f4:f3e0]) by CIO-KRC-HT03.osuad.osu.edu ([fe80::2572:c08d:8186:46a4%12]) with mapi id 14.02.0309.002; Sun, 7 Oct 2012 14:19:34 -0400
From: "Cantor, Scott" <cantor.2@osu.edu>
To: Simon Josefsson <simon@josefsson.org>
Subject: Re: Last Call: <draft-ietf-abfab-gss-eap-naming-05.txt> (Name Attributes for the GSS-API EAP mechanism) to Proposed Standard
Thread-Topic: Last Call: <draft-ietf-abfab-gss-eap-naming-05.txt> (Name Attributes for the GSS-API EAP mechanism) to Proposed Standard
Thread-Index: AQHNo+K8KYVCRSrcB0SaMmyLw5NQppeuKM0A
Date: Sun, 7 Oct 2012 18:19:34 +0000
Message-ID: <BA63CEAE152A7742B854C678D949138339A567CD@CIO-KRC-D1MBX01.osuad.osu.edu>
In-Reply-To: <874nm7v92k.fsf@latte.josefsson.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [128.146.178.47]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2C1BF4FA0905EB4E9D0980C5F6555BAF@osu.edu>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: osu.edu
Cc: Sam Hartman <hartmans@painless-security.com>, "abfab@ietf.org" <abfab@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 07 Oct 2012 18:19:39 -0000

On 10/6/12 12:50 PM, "Simon Josefsson" <simon@josefsson.org> wrote:
>
>Thanks, now I understand better.  I would feel more comfortable if there
>were a precise reference to what "well-formed serialization" means,
>especially since there is a MUST here.  It ought to be possible to
>determine algorithmically whether something conforms or not.  Sometimes
>I get the impression that "well-formed" just refers to syntactical
>correctness, whereas namespace considerations are more semantic.

Actually namespaces extend the notion of syntax in XML, so they're not
just semantic. When you parse while namespace-aware, there are normative
rules for that grammar that include having namespaces declared properly. I
think you probably want to reference the notion of "namespace
well-formed", so my suggested text could be adjusted to include that
instead of just "well-formed".

http://www.w3.org/TR/2009/REC-xml-names-20091208/#Conformance

>If there is a suitable reference to some XML standard, that is probably
>better.

See above.

-- Scott



From jasnell@gmail.com  Fri Oct  5 10:42:32 2012
Return-Path: <jasnell@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3154021F87B0 for <ietf@ietfa.amsl.com>; Fri,  5 Oct 2012 10:42:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.193
X-Spam-Level: 
X-Spam-Status: No, score=-4.193 tagged_above=-999 required=5 tests=[AWL=-0.595, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id x-lfrq78O3Zh for <ietf@ietfa.amsl.com>; Fri,  5 Oct 2012 10:42:31 -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 4F96E21F87B4 for <ietf@ietf.org>; Fri,  5 Oct 2012 10:42:31 -0700 (PDT)
Received: by mail-wi0-f172.google.com with SMTP id hq12so878609wib.13 for <ietf@ietf.org>; Fri, 05 Oct 2012 10:42:30 -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=v1xoBro0qWE4VsXuan+M9sU6VAg8x9PAAQhCMXgRMkA=; b=WeSODcIDbD4A9x+9tghgSaGVv4v7wnbZMDxGEyii9gYNxqhYG1L6R2SP/RmhYOPWwI HwD3YkRofXxT5YXHYiYVLLcJIWKZ+fTEJ2denwM5uTGZbPJpT1dPfB5BnxSVD24r5MU9 o2mFmqAGcGao4xwGFA4oL9vpFyfwD+SSuyhsnb9Vu+eZqbutN2oPSulww7oNPnM/sMD5 zuo08/cM1MrfVCmztFjOgwIPYE1ugFwJuOPRf0DYUNPpdhMK3nAK9TuW9anam2ec/GKu jYJjVcYXt1Jg6br0IyuS01UWAQLr02+CFclIYgB5gbZ0F7Ph3TB0k4mUvSgmgXkHoVsU U8DQ==
Received: by 10.216.243.74 with SMTP id j52mr5323323wer.108.1349458950426; Fri, 05 Oct 2012 10:42:30 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.182.4 with HTTP; Fri, 5 Oct 2012 10:42:10 -0700 (PDT)
In-Reply-To: <CABkgnnXkHdVcK4fa0p2MPox7RTruOQCWVa7UCuPNLy-b4yUiVg@mail.gmail.com>
References: <20120914184457.16683.33382.idtracker@ietfa.amsl.com> <6.2.5.6.2.20120914153648.09f87700@resistor.net> <506EF8FA.1030100@gmx.de> <CABkgnnXkHdVcK4fa0p2MPox7RTruOQCWVa7UCuPNLy-b4yUiVg@mail.gmail.com>
From: James M Snell <jasnell@gmail.com>
Date: Fri, 5 Oct 2012 10:42:10 -0700
Message-ID: <CABP7Rbc81Yo+Xp4QdJKH=Kq=v8F1==gAnhGjaKASvVfKis_fRw@mail.gmail.com>
Subject: Re: Last Call: <draft-snell-http-prefer-14.txt> (Prefer Header for HTTP) to Proposed Standard
To: Martin Thomson <martin.thomson@gmail.com>
Content-Type: multipart/alternative; boundary=e0cb4e43cf1f61119d04cb536591
X-Mailman-Approved-At: Mon, 08 Oct 2012 08:32:01 -0700
Cc: Julian Reschke <julian.reschke@gmx.de>, SM <sm@resistor.net>, ietf@ietf.org, HTTP Working Group <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: Fri, 05 Oct 2012 17:42:32 -0000

--e0cb4e43cf1f61119d04cb536591
Content-Type: text/plain; charset=UTF-8

I am certainly open to alternatives on this particular point. The wait
preference has proven to be quite useful in environments where the latency
is low and predicable and there is good clock synchronization between the
client and server. Such conditions can be easily achieved when the
deployment environment is well managed. It does not work so well,
obviously, for arbitrary web clients running on mobile devices talking to
arbitrary servers. I never really intended wait to be used within such
environments, however.

I could drop the Date header recommendation altogether and stress in the
text that good clock synchronization and predictable latency is required
for the wait preference to be used effectively.

- James

On Fri, Oct 5, 2012 at 10:22 AM, Martin Thomson <martin.thomson@gmail.com>wrote:

> On 5 October 2012 08:12, Julian Reschke <julian.reschke@gmx.de> wrote:
> > 3.4.  The "wait" Preference
> > I'm not totally convinced that taking the Date request header field into
> > account is necessary given the additional complexity; what do others
> think?
>
> I said as much in my GenART review:
> http://www.ietf.org/mail-archive/web/gen-art/current/msg07790.html
>
> Having had experience implementing this exact feature, relying on Date
> isn't going to work.
>

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

<font face=3D"courier new,monospace">I am certainly open to alternatives on=
 this particular point. The wait preference has proven to be quite useful i=
n environments where the latency is low and predicable and there is good cl=
ock synchronization between the client and server. Such conditions can be e=
asily achieved when the deployment environment is well managed. It does not=
 work so well, obviously, for arbitrary web clients running on mobile devic=
es talking to arbitrary servers. I never really intended wait to be used wi=
thin such environments, however.</font><div>

<font face=3D"courier new,monospace"><br></font></div><div><font face=3D"co=
urier new,monospace">I could drop the Date header recommendation altogether=
 and stress in the text that good clock synchronization and predictable lat=
ency is required for the wait preference to be used effectively.=C2=A0</fon=
t></div>

<div><font face=3D"courier new,monospace"><br></font></div><div><font face=
=3D"courier new,monospace">- James<br></font><br><div class=3D"gmail_quote"=
>On Fri, Oct 5, 2012 at 10:22 AM, Martin Thomson <span dir=3D"ltr">&lt;<a h=
ref=3D"mailto:martin.thomson@gmail.com" target=3D"_blank">martin.thomson@gm=
ail.com</a>&gt;</span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">On 5 October 2012 08:12, Julian Reschke &lt;=
<a href=3D"mailto:julian.reschke@gmx.de">julian.reschke@gmx.de</a>&gt; wrot=
e:<br>


&gt; 3.4. =C2=A0The &quot;wait&quot; Preference<br>
<div class=3D"im">&gt; I&#39;m not totally convinced that taking the Date r=
equest header field into<br>
&gt; account is necessary given the additional complexity; what do others t=
hink?<br>
<br>
</div>I said as much in my GenART review:<br>
<a href=3D"http://www.ietf.org/mail-archive/web/gen-art/current/msg07790.ht=
ml" target=3D"_blank">http://www.ietf.org/mail-archive/web/gen-art/current/=
msg07790.html</a><br>
<br>
Having had experience implementing this exact feature, relying on Date<br>
isn&#39;t going to work.<br>
</blockquote></div><br></div>

--e0cb4e43cf1f61119d04cb536591--

From jasnell@gmail.com  Fri Oct  5 11:28:43 2012
Return-Path: <jasnell@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B2BE921F84F1 for <ietf@ietfa.amsl.com>; Fri,  5 Oct 2012 11:28:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.293
X-Spam-Level: 
X-Spam-Status: No, score=-4.293 tagged_above=-999 required=5 tests=[AWL=-0.695, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gBUy7CgJi1r2 for <ietf@ietfa.amsl.com>; Fri,  5 Oct 2012 11:28:43 -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 4068321F84F0 for <ietf@ietf.org>; Fri,  5 Oct 2012 11:28:42 -0700 (PDT)
Received: by mail-wi0-f172.google.com with SMTP id hq12so928556wib.13 for <ietf@ietf.org>; Fri, 05 Oct 2012 11:28:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=Us38iM5QCoNG2c/YbQmd5mA6YRnzNYWMCQ/lAWdZ/4c=; b=FOBQNJienhpqzk5rCOq33LFpf/mDJEHuVc2o9Y2/Uz/Lb3v637jMwo2zMFitnCE3TX 3E5DRWwVDbw1o/ZS7yL65AclaJqzdDZkilyFdmzA4c7EdvW6G2Vona2qt1UzrUZaXByP mwukTJjYxRB37v5g7NkqEEuVDfQ+yChnpUzA2HxtrkApIx+lFgKTMWQk7YOBhgDUyyNi DmZo2c8FsjmNQnadn1bW3PHTBjur0iKdSjf+6NXUo60hRPMwk0sd40eAfkACw6hbflXR 6eUDgVLLpSKlviRGJ/5dBHn/pwSLl5wmARrUyU0n4HSJ8bPWdQ11WcfQKc7TnbH6Z64l qtrQ==
Received: by 10.180.87.230 with SMTP id bb6mr5021413wib.6.1349461721383; Fri, 05 Oct 2012 11:28:41 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.182.4 with HTTP; Fri, 5 Oct 2012 11:28:21 -0700 (PDT)
In-Reply-To: <CABkgnnWvbjkmXe_orAKwLuq8J7LJ2uCgcW7Ry=mhBj=gOTgYHA@mail.gmail.com>
References: <20120914184457.16683.33382.idtracker@ietfa.amsl.com> <6.2.5.6.2.20120914153648.09f87700@resistor.net> <506EF8FA.1030100@gmx.de> <CABkgnnXkHdVcK4fa0p2MPox7RTruOQCWVa7UCuPNLy-b4yUiVg@mail.gmail.com> <CABP7Rbc81Yo+Xp4QdJKH=Kq=v8F1==gAnhGjaKASvVfKis_fRw@mail.gmail.com> <CABkgnnWvbjkmXe_orAKwLuq8J7LJ2uCgcW7Ry=mhBj=gOTgYHA@mail.gmail.com>
From: James M Snell <jasnell@gmail.com>
Date: Fri, 5 Oct 2012 11:28:21 -0700
Message-ID: <CABP7RbeTd=43Pq56raCXOVO6NZhOX3yKb1_LL--EqroUEXiCzw@mail.gmail.com>
Subject: Re: Last Call: <draft-snell-http-prefer-14.txt> (Prefer Header for HTTP) to Proposed Standard
To: Martin Thomson <martin.thomson@gmail.com>
Content-Type: multipart/alternative; boundary=f46d0444e97b8a816e04cb540a87
X-Mailman-Approved-At: Mon, 08 Oct 2012 08:32:01 -0700
Cc: Julian Reschke <julian.reschke@gmx.de>, SM <sm@resistor.net>, ietf@ietf.org, HTTP Working Group <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: Fri, 05 Oct 2012 18:28:43 -0000

--f46d0444e97b8a816e04cb540a87
Content-Type: text/plain; charset=UTF-8

How about the following change:

<snip>

  The "wait" preference can be used to establish an upper bound on the
  length of time, in seconds, the client expects it will take the server
  to process the request once it has been received. In the case that
  generating a response will take longer than the time specified,
  the server, or proxy, can choose to utilize an asynchronous processing
  model by returning -- for example -- a "202 Accepted" response.

  ABNF:
    wait = "wait" BWS "=" BWS delta-seconds

  It is important to consider that there are many -- largely
  unpredictable -- factors that can influence the amount of time it
  takes a server to process a request. The period of time specified
  is not intended to be treated as a strictly defined "hard limit"
  but rather as a hint about the client's expectation.

  For example, a server receiving the following request might choose
  to respond asynchronously if processing the request will take longer
  than 10 seconds:

    POST /collection HTTP/1.1
    Host: example.org
    Content-Type: text/plain
    Prefer: return-asynch, wait=10

    {Data}

</snip>

On Fri, Oct 5, 2012 at 11:12 AM, Martin Thomson <martin.thomson@gmail.com>wrote:

> On 5 October 2012 10:42, James M Snell <jasnell@gmail.com> wrote:
> > I could drop the Date header recommendation altogether and stress in the
> > text that good clock synchronization and predictable latency is required
> for
> > the wait preference to be used effectively.
>
> The feature is useful, I agree.  The problem is that - as defined -
> the server needs to guess something about the times on the client in
> order to implement this reliably.
>
> Relying on clock synchronization is not realistic.  Even in controlled
> environments, errors are commonplace.
>
> Even the simple case shows a problem:
>   a: client sends request
>   b: server receives request
>   c: time passes
>   d: server responds to request
>   e: client receives response
>
> You require that the time be a measure of a->e.  The server has no way
> to determine what that time is.
>
> An alternative would be to make the requirement apply to b->d.  That
> is something that the server has direct control over.  The client then
> gains a little extra work, but at least they are in a position to
> measure a->b + d->e.  In any case, with low or predictable latency, I
> doubt that the addition of a->b + d->e will have any significant
> impact on whether the information is useful to the client.  Especially
> given that times are expressed in seconds, not microseconds.
>

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

<font face=3D"courier new,monospace">How about the following change:</font>=
<div><font face=3D"courier new,monospace"><br></font></div><div><font face=
=3D"courier new,monospace">&lt;snip&gt;</font></div><div><font face=3D"cour=
ier new,monospace"><br>

</font></div><div><span style=3D"font-family:&#39;courier new&#39;,monospac=
e">=C2=A0 The &quot;wait&quot; preference can be used to establish an upper=
 bound on the=C2=A0</span></div><div><font face=3D"courier new,monospace"><=
div>=C2=A0 length of time, in seconds, the client expects it will take the =
server=C2=A0</div>

<div>=C2=A0 to process the request once it has been received. In the case t=
hat=C2=A0</div><div>=C2=A0 generating a response will take longer than the =
time specified,=C2=A0</div><div>=C2=A0 the server, or proxy, can choose to =
utilize an asynchronous processing=C2=A0</div>

<div>=C2=A0 model by returning -- for example -- a &quot;202 Accepted&quot;=
 response.</div><div><br></div><div>=C2=A0 ABNF:</div><div>=C2=A0 =C2=A0 wa=
it =3D &quot;wait&quot; BWS &quot;=3D&quot; BWS delta-seconds</div><div><br=
></div><div>=C2=A0 It is important to consider that there are many -- large=
ly=C2=A0</div>

<div>=C2=A0 unpredictable -- factors that can influence the amount of time =
it=C2=A0</div><div>=C2=A0 takes a server to process a request. The period o=
f time specified=C2=A0</div><div>=C2=A0 is not intended to be treated as a =
strictly defined &quot;hard limit&quot;=C2=A0</div>

<div>=C2=A0 but rather as a hint about the client&#39;s expectation.</div><=
div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0</div><div>=C2=A0 For ex=
ample, a server receiving the following=C2=A0request might choose=C2=A0</di=
v><div>=C2=A0 to respond asynchronously if processing the=C2=A0request will=
 take longer=C2=A0</div>

<div>=C2=A0 than 10 seconds:</div><div><br></div><div>=C2=A0 =C2=A0 POST /c=
ollection HTTP/1.1</div><div>=C2=A0 =C2=A0 Host: <a href=3D"http://example.=
org">example.org</a></div><div>=C2=A0 =C2=A0 Content-Type: text/plain</div>=
<div>=C2=A0 =C2=A0 Prefer: return-asynch, wait=3D10</div>

<div>=C2=A0=C2=A0</div><div>=C2=A0 =C2=A0 {Data}</div><div><br></div></font=
></div><div><font face=3D"courier new,monospace">&lt;/snip&gt;</font></div>=
<div><br><div class=3D"gmail_quote">On Fri, Oct 5, 2012 at 11:12 AM, Martin=
 Thomson <span dir=3D"ltr">&lt;<a href=3D"mailto:martin.thomson@gmail.com" =
target=3D"_blank">martin.thomson@gmail.com</a>&gt;</span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"im">On 5 October 2012 10:42, J=
ames M Snell &lt;<a href=3D"mailto:jasnell@gmail.com">jasnell@gmail.com</a>=
&gt; wrote:<br>


&gt; I could drop the Date header recommendation altogether and stress in t=
he<br>
&gt; text that good clock synchronization and predictable latency is requir=
ed for<br>
&gt; the wait preference to be used effectively.<br>
<br>
</div>The feature is useful, I agree. =C2=A0The problem is that - as define=
d -<br>
the server needs to guess something about the times on the client in<br>
order to implement this reliably.<br>
<br>
Relying on clock synchronization is not realistic. =C2=A0Even in controlled=
<br>
environments, errors are commonplace.<br>
<br>
Even the simple case shows a problem:<br>
=C2=A0 a: client sends request<br>
=C2=A0 b: server receives request<br>
=C2=A0 c: time passes<br>
=C2=A0 d: server responds to request<br>
=C2=A0 e: client receives response<br>
<br>
You require that the time be a measure of a-&gt;e. =C2=A0The server has no =
way<br>
to determine what that time is.<br>
<br>
An alternative would be to make the requirement apply to b-&gt;d. =C2=A0Tha=
t<br>
is something that the server has direct control over. =C2=A0The client then=
<br>
gains a little extra work, but at least they are in a position to<br>
measure a-&gt;b + d-&gt;e. =C2=A0In any case, with low or predictable laten=
cy, I<br>
doubt that the addition of a-&gt;b + d-&gt;e will have any significant<br>
impact on whether the information is useful to the client. =C2=A0Especially=
<br>
given that times are expressed in seconds, not microseconds.<br>
</blockquote></div><br></div>

--f46d0444e97b8a816e04cb540a87--

From jasnell@gmail.com  Fri Oct  5 14:26:39 2012
Return-Path: <jasnell@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 05E7F21F871A for <ietf@ietfa.amsl.com>; Fri,  5 Oct 2012 14:26:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.664
X-Spam-Level: 
X-Spam-Status: No, score=-3.664 tagged_above=-999 required=5 tests=[AWL=-0.066, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4HvPq4S6V45t for <ietf@ietfa.amsl.com>; Fri,  5 Oct 2012 14:26:38 -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 ADF6121F870A for <ietf@ietf.org>; Fri,  5 Oct 2012 14:26:37 -0700 (PDT)
Received: by mail-we0-f172.google.com with SMTP id u46so1457533wey.31 for <ietf@ietf.org>; Fri, 05 Oct 2012 14:26:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=JpcVTo7j21IwOvxHOy8B9DidDQ9dJ9wQMwKHZiF3gtw=; b=bMBEfp6T060Mg+rzidfddD2wiFNCHWjATSeB/jHgN/zfvWSHVP5WRL7IjqK4uFb1hS gsDkCdnRyPjd6sdTYakoYzUkdq6AHCxeMyYLuVenMaD86QFSEFstj0XrKooGaVDdVKK+ Dy5N65NY9SzmXvwQ4X4wtVXCIOMPuxgQNpwGseBiuaJ1wJE07ii/+KYDN7MkzBG4nuZw LuNhogw4I60olWZx9vlZ859TXZ9s6gRPnY+z0eXq4vMbcyC2WjZBg4csHASBsDFtgdTK iKPWWSBLd752DTL+RAv4vaq8cqb1Zl8JjywbwMxUYx2RwHaAbBjsNTBWspwmpv1S6xZx skQw==
MIME-Version: 1.0
Received: by 10.180.79.103 with SMTP id i7mr5782386wix.13.1349472396868; Fri, 05 Oct 2012 14:26:36 -0700 (PDT)
Received: by 10.223.182.4 with HTTP; Fri, 5 Oct 2012 14:26:36 -0700 (PDT)
Received: by 10.223.182.4 with HTTP; Fri, 5 Oct 2012 14:26:36 -0700 (PDT)
In-Reply-To: <CABkgnnWXRVeUDAfmJgfyJZyCYzn-Ktn+=ZbgRc5jKMBYJzGRew@mail.gmail.com>
References: <20120914184457.16683.33382.idtracker@ietfa.amsl.com> <6.2.5.6.2.20120914153648.09f87700@resistor.net> <506EF8FA.1030100@gmx.de> <CABkgnnXkHdVcK4fa0p2MPox7RTruOQCWVa7UCuPNLy-b4yUiVg@mail.gmail.com> <CABP7Rbc81Yo+Xp4QdJKH=Kq=v8F1==gAnhGjaKASvVfKis_fRw@mail.gmail.com> <CABkgnnWvbjkmXe_orAKwLuq8J7LJ2uCgcW7Ry=mhBj=gOTgYHA@mail.gmail.com> <CABP7RbeTd=43Pq56raCXOVO6NZhOX3yKb1_LL--EqroUEXiCzw@mail.gmail.com> <CABkgnnWXRVeUDAfmJgfyJZyCYzn-Ktn+=ZbgRc5jKMBYJzGRew@mail.gmail.com>
Date: Fri, 5 Oct 2012 14:26:36 -0700
Message-ID: <CABP7RbfEUe-dHx0X-+ji5+GKQycOzHFUKg8fKJc2=xBfG0rEQg@mail.gmail.com>
Subject: Re: Last Call: <draft-snell-http-prefer-14.txt> (Prefer Header for HTTP) to Proposed Standard
From: James M Snell <jasnell@gmail.com>
To: Martin Thomson <martin.thomson@gmail.com>
Content-Type: multipart/alternative; boundary=f46d04182518d97d6704cb568645
X-Mailman-Approved-At: Mon, 08 Oct 2012 08:32:01 -0700
Cc: Julian Reschke <julian.reschke@gmx.de>, SM <sm@resistor.net>, ietf-http-wg@w3.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Oct 2012 21:26:39 -0000

--f46d04182518d97d6704cb568645
Content-Type: text/plain; charset=UTF-8

That works for me.
On Oct 5, 2012 2:18 PM, "Martin Thomson" <martin.thomson@gmail.com> wrote:

> An improvement.  Though the following doesn't read quite right to me:
>
>   It is important to consider that there are many -- largely
>   unpredictable -- factors that can influence the amount of time it
>   takes a server to process a request. The period of time specified
>   is not intended to be treated as a strictly defined "hard limit"
>   but rather as a hint about the client's expectation.
>
> I'm not sure that it's "mysterious forces" at the server that are the
> issue in this design.  Nor is it the case that this would ever be a
> hard limit.  As a preference, it's always option.  How about:
>
>   Messages spend some time traversing the network and being
>   processed by intermediaries.  This increases the time that a
>   client awaits a response in addition to any time spent at a
>   server.  A client that has strict timing requirements can estimate
>   these factors and adjust the wait value accordingly.
>
> Note that "intermediaries" could include the HTTP stack in both client
> and server.
>
> And maybe:
>
>   As with other preferences, the wait preference could be ignored.
>   Clients can abandon requests that take longer than they are
>   prepared to wait.
>
> --Martin
>
> On 5 October 2012 11:28, James M Snell <jasnell@gmail.com> wrote:
> > How about the following change:
> >
> > <snip>
> >
> >   The "wait" preference can be used to establish an upper bound on the
> >   length of time, in seconds, the client expects it will take the server
> >   to process the request once it has been received. In the case that
> >   generating a response will take longer than the time specified,
> >   the server, or proxy, can choose to utilize an asynchronous processing
> >   model by returning -- for example -- a "202 Accepted" response.
> >
> >   ABNF:
> >     wait = "wait" BWS "=" BWS delta-seconds
> >
> >   It is important to consider that there are many -- largely
> >   unpredictable -- factors that can influence the amount of time it
> >   takes a server to process a request. The period of time specified
> >   is not intended to be treated as a strictly defined "hard limit"
> >   but rather as a hint about the client's expectation.
> >
> >   For example, a server receiving the following request might choose
> >   to respond asynchronously if processing the request will take longer
> >   than 10 seconds:
> >
> >     POST /collection HTTP/1.1
> >     Host: example.org
> >     Content-Type: text/plain
> >     Prefer: return-asynch, wait=10
> >
> >     {Data}
> >
> > </snip>
> >
> > On Fri, Oct 5, 2012 at 11:12 AM, Martin Thomson <
> martin.thomson@gmail.com>
> > wrote:
> >>
> >> On 5 October 2012 10:42, James M Snell <jasnell@gmail.com> wrote:
> >> > I could drop the Date header recommendation altogether and stress in
> the
> >> > text that good clock synchronization and predictable latency is
> required
> >> > for
> >> > the wait preference to be used effectively.
> >>
> >> The feature is useful, I agree.  The problem is that - as defined -
> >> the server needs to guess something about the times on the client in
> >> order to implement this reliably.
> >>
> >> Relying on clock synchronization is not realistic.  Even in controlled
> >> environments, errors are commonplace.
> >>
> >> Even the simple case shows a problem:
> >>   a: client sends request
> >>   b: server receives request
> >>   c: time passes
> >>   d: server responds to request
> >>   e: client receives response
> >>
> >> You require that the time be a measure of a->e.  The server has no way
> >> to determine what that time is.
> >>
> >> An alternative would be to make the requirement apply to b->d.  That
> >> is something that the server has direct control over.  The client then
> >> gains a little extra work, but at least they are in a position to
> >> measure a->b + d->e.  In any case, with low or predictable latency, I
> >> doubt that the addition of a->b + d->e will have any significant
> >> impact on whether the information is useful to the client.  Especially
> >> given that times are expressed in seconds, not microseconds.
> >
> >
>

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

<p dir=3D"ltr">That works for me. </p>
<div class=3D"gmail_quote">On Oct 5, 2012 2:18 PM, &quot;Martin Thomson&quo=
t; &lt;<a href=3D"mailto:martin.thomson@gmail.com">martin.thomson@gmail.com=
</a>&gt; wrote:<br type=3D"attribution"><blockquote class=3D"gmail_quote" s=
tyle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
An improvement. =C2=A0Though the following doesn&#39;t read quite right to =
me:<br>
<br>
=C2=A0 It is important to consider that there are many -- largely<br>
=C2=A0 unpredictable -- factors that can influence the amount of time it<br=
>
=C2=A0 takes a server to process a request. The period of time specified<br=
>
=C2=A0 is not intended to be treated as a strictly defined &quot;hard limit=
&quot;<br>
=C2=A0 but rather as a hint about the client&#39;s expectation.<br>
<br>
I&#39;m not sure that it&#39;s &quot;mysterious forces&quot; at the server =
that are the<br>
issue in this design. =C2=A0Nor is it the case that this would ever be a<br=
>
hard limit. =C2=A0As a preference, it&#39;s always option. =C2=A0How about:=
<br>
<br>
=C2=A0 Messages spend some time traversing the network and being<br>
=C2=A0 processed by intermediaries. =C2=A0This increases the time that a<br=
>
=C2=A0 client awaits a response in addition to any time spent at a<br>
=C2=A0 server. =C2=A0A client that has strict timing requirements can estim=
ate<br>
=C2=A0 these factors and adjust the wait value accordingly.<br>
<br>
Note that &quot;intermediaries&quot; could include the HTTP stack in both c=
lient<br>
and server.<br>
<br>
And maybe:<br>
<br>
=C2=A0 As with other preferences, the wait preference could be ignored.<br>
=C2=A0 Clients can abandon requests that take longer than they are<br>
=C2=A0 prepared to wait.<br>
<br>
--Martin<br>
<br>
On 5 October 2012 11:28, James M Snell &lt;<a href=3D"mailto:jasnell@gmail.=
com">jasnell@gmail.com</a>&gt; wrote:<br>
&gt; How about the following change:<br>
&gt;<br>
&gt; &lt;snip&gt;<br>
&gt;<br>
&gt; =C2=A0 The &quot;wait&quot; preference can be used to establish an upp=
er bound on the<br>
&gt; =C2=A0 length of time, in seconds, the client expects it will take the=
 server<br>
&gt; =C2=A0 to process the request once it has been received. In the case t=
hat<br>
&gt; =C2=A0 generating a response will take longer than the time specified,=
<br>
&gt; =C2=A0 the server, or proxy, can choose to utilize an asynchronous pro=
cessing<br>
&gt; =C2=A0 model by returning -- for example -- a &quot;202 Accepted&quot;=
 response.<br>
&gt;<br>
&gt; =C2=A0 ABNF:<br>
&gt; =C2=A0 =C2=A0 wait =3D &quot;wait&quot; BWS &quot;=3D&quot; BWS delta-=
seconds<br>
&gt;<br>
&gt; =C2=A0 It is important to consider that there are many -- largely<br>
&gt; =C2=A0 unpredictable -- factors that can influence the amount of time =
it<br>
&gt; =C2=A0 takes a server to process a request. The period of time specifi=
ed<br>
&gt; =C2=A0 is not intended to be treated as a strictly defined &quot;hard =
limit&quot;<br>
&gt; =C2=A0 but rather as a hint about the client&#39;s expectation.<br>
&gt;<br>
&gt; =C2=A0 For example, a server receiving the following request might cho=
ose<br>
&gt; =C2=A0 to respond asynchronously if processing the request will take l=
onger<br>
&gt; =C2=A0 than 10 seconds:<br>
&gt;<br>
&gt; =C2=A0 =C2=A0 POST /collection HTTP/1.1<br>
&gt; =C2=A0 =C2=A0 Host: <a href=3D"http://example.org" target=3D"_blank">e=
xample.org</a><br>
&gt; =C2=A0 =C2=A0 Content-Type: text/plain<br>
&gt; =C2=A0 =C2=A0 Prefer: return-asynch, wait=3D10<br>
&gt;<br>
&gt; =C2=A0 =C2=A0 {Data}<br>
&gt;<br>
&gt; &lt;/snip&gt;<br>
&gt;<br>
&gt; On Fri, Oct 5, 2012 at 11:12 AM, Martin Thomson &lt;<a href=3D"mailto:=
martin.thomson@gmail.com">martin.thomson@gmail.com</a>&gt;<br>
&gt; wrote:<br>
&gt;&gt;<br>
&gt;&gt; On 5 October 2012 10:42, James M Snell &lt;<a href=3D"mailto:jasne=
ll@gmail.com">jasnell@gmail.com</a>&gt; wrote:<br>
&gt;&gt; &gt; I could drop the Date header recommendation altogether and st=
ress in the<br>
&gt;&gt; &gt; text that good clock synchronization and predictable latency =
is required<br>
&gt;&gt; &gt; for<br>
&gt;&gt; &gt; the wait preference to be used effectively.<br>
&gt;&gt;<br>
&gt;&gt; The feature is useful, I agree. =C2=A0The problem is that - as def=
ined -<br>
&gt;&gt; the server needs to guess something about the times on the client =
in<br>
&gt;&gt; order to implement this reliably.<br>
&gt;&gt;<br>
&gt;&gt; Relying on clock synchronization is not realistic. =C2=A0Even in c=
ontrolled<br>
&gt;&gt; environments, errors are commonplace.<br>
&gt;&gt;<br>
&gt;&gt; Even the simple case shows a problem:<br>
&gt;&gt; =C2=A0 a: client sends request<br>
&gt;&gt; =C2=A0 b: server receives request<br>
&gt;&gt; =C2=A0 c: time passes<br>
&gt;&gt; =C2=A0 d: server responds to request<br>
&gt;&gt; =C2=A0 e: client receives response<br>
&gt;&gt;<br>
&gt;&gt; You require that the time be a measure of a-&gt;e. =C2=A0The serve=
r has no way<br>
&gt;&gt; to determine what that time is.<br>
&gt;&gt;<br>
&gt;&gt; An alternative would be to make the requirement apply to b-&gt;d. =
=C2=A0That<br>
&gt;&gt; is something that the server has direct control over. =C2=A0The cl=
ient then<br>
&gt;&gt; gains a little extra work, but at least they are in a position to<=
br>
&gt;&gt; measure a-&gt;b + d-&gt;e. =C2=A0In any case, with low or predicta=
ble latency, I<br>
&gt;&gt; doubt that the addition of a-&gt;b + d-&gt;e will have any signifi=
cant<br>
&gt;&gt; impact on whether the information is useful to the client. =C2=A0E=
specially<br>
&gt;&gt; given that times are expressed in seconds, not microseconds.<br>
&gt;<br>
&gt;<br>
</blockquote></div>

--f46d04182518d97d6704cb568645--

From barryleiba.mailing.lists@gmail.com  Mon Oct  8 10:16:53 2012
Return-Path: <barryleiba.mailing.lists@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A95A221F87E8; Mon,  8 Oct 2012 10:16:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.1
X-Spam-Level: 
X-Spam-Status: No, score=-103.1 tagged_above=-999 required=5 tests=[AWL=-0.123, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AJAnkpc3SQYu; Mon,  8 Oct 2012 10:16:53 -0700 (PDT)
Received: from mail-la0-f44.google.com (mail-la0-f44.google.com [209.85.215.44]) by ietfa.amsl.com (Postfix) with ESMTP id 2F40321F87E4; Mon,  8 Oct 2012 10:16:52 -0700 (PDT)
Received: by mail-la0-f44.google.com with SMTP id b11so2672668lam.31 for <multiple recipients>; Mon, 08 Oct 2012 10:16:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=DvWnnNe9gwL58ZzSLvx2fDmeW+DHgNZyJ/zBR0qrcC4=; b=QrXTvh35QLhsYKEBrjTZh4RDJzid44fLvgjKFa34yj45VcCiCeXDkbuSUiFg2mLJCk OQ5GFGmeG4PScRu/C8O8eHvqmOPg/WgIbQtGZxiXCn2dao6DRu6RXM22WUE49aoS/3qK 3289cay5RWysjlh7EPRbWalnELv1VDJrauDsqIKCZzeqKkfDghrPkOVgHkXkNSlCs2bs 6FEXGo0piv0Ck4XFtmYrgpKaAwsMYpE0A2Qrc/v1LTQvkC/TceSp7xkfRowLT5ibibHp eGhux1LMDU3XPWQhE3OfOuRgzX52KESDck9k9ZuIuLasTNlMF1WVFp77/IyXzcw4SSKe mjTQ==
MIME-Version: 1.0
Received: by 10.112.101.133 with SMTP id fg5mr2771608lbb.3.1349716611100; Mon, 08 Oct 2012 10:16:51 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.112.150.194 with HTTP; Mon, 8 Oct 2012 10:16:50 -0700 (PDT)
In-Reply-To: <50712F0A.1050309@gmail.com>
References: <8D3D17ACE214DC429325B2B98F3AE7120DCD17FD@MX15A.corp.emc.com> <50712F0A.1050309@gmail.com>
Date: Mon, 8 Oct 2012 13:16:50 -0400
X-Google-Sender-Auth: kuSWlw21NSFpLbLwLkm8lk1x1sk
Message-ID: <CAC4RtVDDBo+kVJMpS+j1sCHy_qtn0FzLkrpzqysPZTaPTHpm1w@mail.gmail.com>
Subject: Re: Gen-ART review of draft-ietf-dime-rfc4005bis-11
From: Barry Leiba <barryleiba@computer.org>
To: Glen Zorn <glenzorn@gmail.com>, precis-chairs@tools.ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Cc: "ietf@ietf.org" <ietf@ietf.org>, "lionel.morand@orange.com" <lionel.morand@orange.com>, "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-dime-rfc4005bis@tools.ietf.org" <draft-ietf-dime-rfc4005bis@tools.ietf.org>, "dime@ietf.org" <dime@ietf.org>, "Black, David" <david.black@emc.com>, "dime-chairs@tools.ietf.org" <dime-chairs@tools.ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Oct 2012 17:16:53 -0000

>> 5) Statement that the string  contains an FQDN, as stated for one case of
>> the Tunnel-Client-Endpoint AVP in 4.5.4. That specific statement is
>> incomplete, as it needs to be accompanied by a normative reference to
>> a document that specifies the format of internationalized domain
>> names, and probably needs to also state which types of labels (e.g.,
>> A-label, U-label) are allowed.
>>
>> Every use of UTF8String in this draft needs to be checked, and most
>> of them are likely to need some attention. The ongoing work in the
>> precis WG may help with some of this, and I would suggest talking to
>> the APP ADs, especially Pete Resnick (hi Pete) before embarking on
>> significant work in this area in order to avoid wasted or duplicated
>> efforts.
>
> OK, this last one bothers me a lot: you /seem /to be suggesting that we hold
> up this draft to wait for the result of a WG which has yet to publish a
> problem statement.  I'm sure that that is not the case, but it sure sounds
> like it.

David can clarify if I'm wrong, but that's not what it sounds like to
me.  What it sounds like he's suggesting is that you talk with the
precis people to see if things are OK, or if there's anything you
should be doing differently.  I'm adding the precis chairs to this
message, and asking them to respond to this point.


A tangential point, while I'm here:

>> [4] Based on this text in 4.4.9:
>> The use of this AVP is NOT RECOMMENDED; the AVPs defined by
>> Korhonen, et al. [RFC5777] SHOULD be used instead.
>>
>> I would have expected RFC5777 to be a Normative Reference, not an
>> Informative Reference.
>
> I don't care particularly, but I don't think that it's really necessary to
> understand RFC 5777 to understand this document.

It would seem odd, in general, if something that's a "MUST implement"
or "SHOULD implement" weren't a normative reference.  But I haven't
(yet) looked at this particular case to see.

Barry

From rbarnes@bbn.com  Mon Oct  8 11:17:05 2012
Return-Path: <rbarnes@bbn.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 796F21F041C; Mon,  8 Oct 2012 11:17:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.424
X-Spam-Level: 
X-Spam-Status: No, score=-106.424 tagged_above=-999 required=5 tests=[AWL=-0.084, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_SUB_OBFU_Z=0.259, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2wqGELZS1zUv; Mon,  8 Oct 2012 11:17:04 -0700 (PDT)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.1.81]) by ietfa.amsl.com (Postfix) with ESMTP id 977E71F0381; Mon,  8 Oct 2012 11:17:04 -0700 (PDT)
Received: from [128.89.253.160] (port=60951) by smtp.bbn.com with esmtps (TLSv1:AES128-SHA:128) (Exim 4.77 (FreeBSD)) (envelope-from <rbarnes@bbn.com>) id 1TLHst-000Da3-Vl; Mon, 08 Oct 2012 14:16:56 -0400
From: Richard Barnes <rbarnes@bbn.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Gen-ART telechat review of draft-ietf-6man-udpzero-06
Date: Mon, 8 Oct 2012 14:16:55 -0400
Message-Id: <AFA53290-369B-43EA-93B5-D14273B8A9A7@bbn.com>
To: IETF discussion list <ietf@ietf.org>, IESG IESG <iesg@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1283)
X-Mailer: Apple Mail (2.1283)
Cc: gen-art@ietf.org, draft-ietf-6man-udpzero@tools.ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Oct 2012 18:17:05 -0000

I have been selected as the General Area Review Team (Gen-ART) reviewer =
for this draft (for background on Gen-ART, please see =
http://www.alvestrand.no/ietf/gen/art/gen-art-FAQ.html).

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

Document: draft-ietf-6man-udpzero-06
Reviewer: Richard Barnes
Review Date: 2012-10-08
IETF LC End Date: 2012-10-02
IESG Telechat date: 2012-10-11

Summary:  Ready

Comment:

In general, the document is well-written and seems to cover the relevant =
considerations well.  I agree with Barry's DISCUSS that the restrictions =
in Section 5.1 should be general to all usages of UDP zero checksums, =
and not specific to tunnels.=

From fernando@gont.com.ar  Mon Oct  8 16:39:57 2012
Return-Path: <fernando@gont.com.ar>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 22AA611E80E3 for <ietf@ietfa.amsl.com>; Mon,  8 Oct 2012 16:39: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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id En-avIUScAdA for <ietf@ietfa.amsl.com>; Mon,  8 Oct 2012 16:39:56 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:d10:2000:e::3]) by ietfa.amsl.com (Postfix) with ESMTP id 6346111E80CC for <ietf@ietf.org>; Mon,  8 Oct 2012 16:39:56 -0700 (PDT)
Received: from cust-174-146-109-94.dyn.as47377.net ([94.109.146.174] helo=[192.168.1.119]) by web01.jbserver.net with esmtpsa (TLSv1:CAMELLIA256-SHA:256) (Exim 4.76) (envelope-from <fernando@gont.com.ar>) id 1TLMvQ-0002Iq-63; Tue, 09 Oct 2012 01:39:52 +0200
Message-ID: <50736447.8050508@gont.com.ar>
Date: Tue, 09 Oct 2012 01:39:51 +0200
From: Fernando Gont <fernando@gont.com.ar>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120912 Thunderbird/15.0.1
MIME-Version: 1.0
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Subject: Re: Last Call: <draft-gont-intarea-obsolete-eid-option-01.txt> (Obsoleting the Endpoint Identifier (EID) Option) to Proposed Standard
References: <20121005135829.825FE18C137@mercury.lcs.mit.edu>
In-Reply-To: <20121005135829.825FE18C137@mercury.lcs.mit.edu>
X-Enigmail-Version: 1.4.4
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Oct 2012 23:39:57 -0000

On 10/05/2012 03:58 PM, Noel Chiappa wrote:
>     > Have the original authors [sic - JNC] been contacted? 
> 
> Alas, the author of the ID which defines this option, Charlie Lynn, is no
> longer with us:
> 
>   http://www.postel.org/pipermail/end2end-interest/2004-June/004195.html
> 
> I can probably give as good a judgement on it as anyone, though.

FWIW, being unaware of this, I tried to contact Charles Lynn a couple of
years ago when I was going through each of the then-currently-specified
IPv6 options. I seem to recall checking with Noel regarding whether EID
had ever been deployed (but my memory may certainly fail).


> Looking at the ID defining the option:
> 
>   http://ana-3.lcs.mit.edu/~jnc/nimrod/eidoption.txt
> 
> (dunno why the obsoletion ID doesn't give a URL for it),

Yep, it should. -- for some reason the I-D is referencing only
<http://ana-3.lcs.mit.edu/~jnc/nimrod/> but not the specific I-D that
specified the option. -- I will add a specific reference in the next rev
of the I-D - thanks!



> the obsoletion ID is
> slightly inaccurate: it wasn't just "meant to be used with the Nimrod routing
> architecture", but rather the endpoint name format supported by that option
> is totally general, allowing any endpoint name format to be used.

Please let me know if you have any suggestions on how to tweak the text
to improve this.

Thanks!

Best regards,
-- 
Fernando Gont
e-mail: fernando@gont.com.ar || fgont@si6networks.com
PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1




From mohta@necom830.hpcl.titech.ac.jp  Mon Oct  8 23:13:58 2012
Return-Path: <mohta@necom830.hpcl.titech.ac.jp>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DE80421F873B for <ietf@ietfa.amsl.com>; Mon,  8 Oct 2012 23:13:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.64
X-Spam-Level: 
X-Spam-Status: No, score=0.64 tagged_above=-999 required=5 tests=[AWL=0.471, BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, SARE_SUB_OBFU_Z=0.259]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1WhqbfHvby2c for <ietf@ietfa.amsl.com>; Mon,  8 Oct 2012 23:13:58 -0700 (PDT)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by ietfa.amsl.com (Postfix) with SMTP id 8010A21F8493 for <ietf@ietf.org>; Mon,  8 Oct 2012 23:13:54 -0700 (PDT)
Received: (qmail 5246 invoked from network); 9 Oct 2012 06:28:22 -0000
Received: from necom830.hpcl.titech.ac.jp (HELO ?127.0.0.1?) (131.112.32.132) by necom830.hpcl.titech.ac.jp with SMTP; 9 Oct 2012 06:28:22 -0000
Message-ID: <5073C064.3060900@necom830.hpcl.titech.ac.jp>
Date: Tue, 09 Oct 2012 15:12:52 +0900
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:15.0) Gecko/20120907 Thunderbird/15.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Gen-ART telechat review of draft-ietf-6man-udpzero-06
References: <AFA53290-369B-43EA-93B5-D14273B8A9A7@bbn.com>
In-Reply-To: <AFA53290-369B-43EA-93B5-D14273B8A9A7@bbn.com>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Oct 2012 06:13:59 -0000

Richard Barnes wrote:

> Document: draft-ietf-6man-udpzero-06

It's interesting that the draft denies the following statements
in RFC2765:

   Fragmented IPv4 UDP packets that do not contain a UDP checksum (i.e.
   the UDP checksum field is zero) are not of significant use over
   wide-areas in the Internet and will not be translated by the
   translator.

While the draft considers only tunnels and states:

   IPv6 middlebox
   deployment is not yet as prolific as it is in IPv4. Thus, relatively
   few current middleboxes may actually block IPv6 UDP with a zero
   checksum.

interactions between the draft and existing implementations
of RFC2765 will be quite exciting.

The following statement of the draft:

      The computed checksum
      value may be cached (before adding the Length field) for each flow
      /destination and subsequently combined with the Length of each
      packet to minimise per-packet processing.

is bogus, because searching cache means a lot more effort than
recomputing checksum.

							Masataka Ohta


From ron.even.tlv@gmail.com  Tue Oct  9 08:34:19 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 3F97011E8122; Tue,  9 Oct 2012 08:34:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5NtyCo0kLeGl; Tue,  9 Oct 2012 08:34:17 -0700 (PDT)
Received: from mail-wg0-f44.google.com (mail-wg0-f44.google.com [74.125.82.44]) by ietfa.amsl.com (Postfix) with ESMTP id EF06311E811B; Tue,  9 Oct 2012 08:34:14 -0700 (PDT)
Received: by mail-wg0-f44.google.com with SMTP id dr13so3201699wgb.13 for <multiple recipients>; Tue, 09 Oct 2012 08:34:14 -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:x-mailer:thread-index:content-language; bh=0qVn/xc+rCq0iNf6yObispYPcD2cGMa2Hx5zaY+uFsU=; b=xrvcPi3JCSGRf0p8poYyCU2RVwiccYrG/xYGbcFSs7HYSG9ufpiOLjElfKEwS8eAv3 Q+ojDa06vjyVIoQ9sYIAf5y4UewzVzMVHgHkbqfVirsqpwfaDAD1wcTB2c3jW6aNdW1V 5XGwjxkB/lwzGc3RR/QBmU/Rt0s7oNa6xFEVdO85Z2s9iz9uq3WakZgSyhbuc1UWz5uq xcc5sWrDWwX5JOej/uiHtVL6Ip85ueys7B3gWQ017OfjEJU6AVjdqYeLr09jwkSgIkS/ dFXVpWY85+wGmF+u/3rA2kzGMqzRlbrGpuTv981imYN+me7uSCKT7o1MWudrkxcJq4Uq abRA==
Received: by 10.216.205.166 with SMTP id j38mr12921619weo.186.1349796854115; Tue, 09 Oct 2012 08:34:14 -0700 (PDT)
Received: from RoniE (bzq-79-176-243-9.red.bezeqint.net. [79.176.243.9]) by mx.google.com with ESMTPS id f1sm25382469wiy.2.2012.10.09.08.34.11 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 09 Oct 2012 08:34:13 -0700 (PDT)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: "'Malis, Andrew G \(Andy\)'" <andrew.g.malis@verizon.com>, <draft-ietf-ccamp-rfc5787bis.all@tools.ietf.org>
References: <002101cd7997$a5204330$ef60c990$@gmail.com> <CC98C05A.2FC85%andrew.g.malis@one.verizon.com>
In-Reply-To: <CC98C05A.2FC85%andrew.g.malis@one.verizon.com>
Subject: RE: Gen-ART LC review of draft-ietf-ccamp-rfc5787bis-05
Date: Tue, 9 Oct 2012 17:32:17 +0200
Message-ID: <011a01cda633$45b69930$d123cb90$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_011B_01CDA644.0940EFD0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQKvrrCCYTySHJIE6oYZ/BaFSZDU3pXtCQqA
Content-Language: en-us
Cc: gen-art@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Oct 2012 15:34:19 -0000

This is a multipart message in MIME format.

------=_NextPart_000_011B_01CDA644.0940EFD0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Andy,

Thanks,

I am OK

Roni

 

From: Malis, Andrew G (Andy) [mailto:andrew.g.malis@verizon.com] 
Sent: 09 October, 2012 2:55 AM
To: Roni Even; draft-ietf-ccamp-rfc5787bis.all@tools.ietf.org
Cc: ietf@ietf.org; gen-art@ietf.org; Malis, Andrew G (Andy)
Subject: Re: Gen-ART LC review of draft-ietf-ccamp-rfc5787bis-05

 

Roni,

 

Thanks for your review, and sorry for the delay on the response, but we've
also been working on incorporating other changes to the draft as well. 

 

To answer your question on section 6.1, that was a good catch. That should
have said "other than the first", rather than "preceding the first". This
will be corrected.

 

To answer your question on section 10, the text is repeated in the
subsections to make life easier for IANA, since they would probably have
replicated it themselves anyway in the three registry listings.

 

On your last comment, we agree with you that the more familiar reader will
not have a problem.

 

Thanks again,

Andy

 

From: Roni Even <ron.even.tlv@gmail.com>
Date: Monday, August 13, 2012 14:07 
To: "draft-ietf-ccamp-rfc5787bis.all@tools.ietf.org"
<draft-ietf-ccamp-rfc5787bis.all@tools.ietf.org>
Cc: "ietf@ietf.org" <ietf@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>
Subject: Gen-ART LC review of draft-ietf-ccamp-rfc5787bis-05
Resent-To: <acee.lindem@ericsson.com>, Adrian Farrell <adrian@olddog.co.uk>,
Andrew Malis <andrew.g.malis@verizon.com>, <dbrungard@att.com>,
<dimitri.papadimitriou@alcatel-lucent.com>, <lberger@labn.net>

 

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-ccamp-rfc5787bis-05.

Reviewer: Roni Even

Review Date:2012-8-12

IETF LC End Date: 2012-8-17

IESG Telechat date:

 

Summary: This draft is almost ready for publication as a standard track RFC.

 

 

Major issues:

 

Minor issues:

In section 6.1 " If specified more than once, instances preceding the first
will be ignored and condition SHOULD be logged for possible action by the
network operator."  I am not sure what is meant by preceding the first.

 

 

Nits/editorial comments:

 

1.	The following note appears in section 10.1, 10.2 and 10.3. "Note
that the same values for the Inter-RA Export Upward sub-TLV and the Inter-RA
Export Downward Sub-TLV MUST be used when they appear in the Link TLV, Node
Attribute TLV, and Router Address TLV." - why not have it in section 10
before section 10.1.
2.	I saw in appendix  B that one of the changes from RFC 5787 was to
clarify the terminology before defining extensions, I would have found it
easier to read if the ASON hierarchy and the relation to OSPF in section 2
were presented in figures. This was more an issue to me as a reader not
familiar with the terminology and I would like to think that the more
familiar reader will not have problem.

 


------=_NextPart_000_011B_01CDA644.0940EFD0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><META =
HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family: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;}
@font-face
	{font-family:Verdana;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin-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;}
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.EmailStyle19
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle22
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:337274288;
	mso-list-template-ids:-764756284;}
@list l1
	{mso-list-id:715087181;
	mso-list-type:hybrid;
	mso-list-template-ids:-1205706658 -1668626108 67698713 67698715 =
67698703 67698713 67698715 67698703 67698713 67698715;}
@list l1:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-bidi-font-family:Calibri;}
@list l1:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l1:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l1:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>Andy,<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'>Thanks,<o:p></o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:#1F497D'>I am =
OK<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>Roni<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div><div =
style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in'><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><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"'> =
Malis, Andrew G (Andy) [mailto:andrew.g.malis@verizon.com] =
<br><b>Sent:</b> 09 October, 2012 2:55 AM<br><b>To:</b> Roni Even; =
draft-ietf-ccamp-rfc5787bis.all@tools.ietf.org<br><b>Cc:</b> =
ietf@ietf.org; gen-art@ietf.org; Malis, Andrew G =
(Andy)<br><b>Subject:</b> Re: Gen-ART LC review of =
draft-ietf-ccamp-rfc5787bis-05<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><p class=3DMsoNormal><span =
style=3D'font-size:10.5pt;line-height:115%;font-family:"Verdana","sans-se=
rif";color:#08003F'>Roni,<o:p></o:p></span></p></div><div><p =
class=3DMsoNormal><span =
style=3D'font-size:10.5pt;line-height:115%;font-family:"Verdana","sans-se=
rif";color:#08003F'><o:p>&nbsp;</o:p></span></p></div><div><div><p =
class=3DMsoNormal><span =
style=3D'font-size:10.5pt;line-height:115%;font-family:"Verdana","sans-se=
rif";color:#08003F'>Thanks for your review, and sorry for the delay on =
the response, but we've&nbsp;also been working on incorporating other =
changes to the draft as =
well.&nbsp;<o:p></o:p></span></p></div></div><div><p =
class=3DMsoNormal><span =
style=3D'font-size:10.5pt;line-height:115%;font-family:"Verdana","sans-se=
rif";color:#08003F'><o:p>&nbsp;</o:p></span></p></div><div><p =
class=3DMsoNormal><span =
style=3D'font-size:10.5pt;line-height:115%;font-family:"Verdana","sans-se=
rif";color:#08003F'>To answer your question on section 6.1, that was a =
good catch. That should have said &quot;other than the first&quot;, =
rather than &quot;preceding the first&quot;. This will be =
corrected.<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:10.5pt;line-height:115%;font-family:"Verdana","sans-se=
rif";color:#08003F'><o:p>&nbsp;</o:p></span></p></div><div><p =
class=3DMsoNormal><span =
style=3D'font-size:10.5pt;line-height:115%;font-family:"Verdana","sans-se=
rif";color:#08003F'>To answer your question on section 10, the text is =
repeated in the subsections to make life easier for IANA, since they =
would probably have replicated it themselves anyway in the three =
registry listings.<o:p></o:p></span></p></div><div><p =
class=3DMsoNormal><span =
style=3D'font-size:10.5pt;line-height:115%;font-family:"Verdana","sans-se=
rif";color:#08003F'><o:p>&nbsp;</o:p></span></p></div><div><p =
class=3DMsoNormal><span =
style=3D'font-size:10.5pt;line-height:115%;font-family:"Verdana","sans-se=
rif";color:#08003F'>On your last comment, we agree with you that the =
more familiar reader will not have a =
problem.<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:10.5pt;line-height:115%;font-family:"Verdana","sans-se=
rif";color:#08003F'><o:p>&nbsp;</o:p></span></p></div><div><p =
class=3DMsoNormal><span =
style=3D'font-size:10.5pt;line-height:115%;font-family:"Verdana","sans-se=
rif";color:#08003F'>Thanks again,<o:p></o:p></span></p></div><div><p =
class=3DMsoNormal><span =
style=3D'font-size:10.5pt;line-height:115%;font-family:"Verdana","sans-se=
rif";color:#08003F'>Andy<o:p></o:p></span></p></div><div><p =
class=3DMsoNormal><span =
style=3D'font-size:10.5pt;line-height:115%;font-family:"Verdana","sans-se=
rif";color:#08003F'><o:p>&nbsp;</o:p></span></p></div><div =
style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;line-height:115%;font-family:"Tahoma","sans-ser=
if";color:black'>From: </span></b><span =
style=3D'font-size:10.0pt;line-height:115%;font-family:"Tahoma","sans-ser=
if";color:black'>Roni Even &lt;<a =
href=3D"mailto:ron.even.tlv@gmail.com">ron.even.tlv@gmail.com</a>&gt;<br>=
<b>Date: </b>Monday, August 13, 2012 14:07 <br><b>To: </b>&quot;<a =
href=3D"mailto:draft-ietf-ccamp-rfc5787bis.all@tools.ietf.org">draft-ietf=
-ccamp-rfc5787bis.all@tools.ietf.org</a>&quot; &lt;<a =
href=3D"mailto:draft-ietf-ccamp-rfc5787bis.all@tools.ietf.org">draft-ietf=
-ccamp-rfc5787bis.all@tools.ietf.org</a>&gt;<br><b>Cc: </b>&quot;<a =
href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a>&quot; &lt;<a =
href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a>&gt;, &quot;<a =
href=3D"mailto:gen-art@ietf.org">gen-art@ietf.org</a>&quot; &lt;<a =
href=3D"mailto:gen-art@ietf.org">gen-art@ietf.org</a>&gt;<br><b>Subject: =
</b>Gen-ART LC review of draft-ietf-ccamp-rfc5787bis-05<br><b>Resent-To: =
</b>&lt;<a =
href=3D"mailto:acee.lindem@ericsson.com">acee.lindem@ericsson.com</a>&gt;=
, Adrian Farrell &lt;<a =
href=3D"mailto:adrian@olddog.co.uk">adrian@olddog.co.uk</a>&gt;, Andrew =
Malis &lt;<a =
href=3D"mailto:andrew.g.malis@verizon.com">andrew.g.malis@verizon.com</a>=
&gt;, &lt;<a =
href=3D"mailto:dbrungard@att.com">dbrungard@att.com</a>&gt;, &lt;<a =
href=3D"mailto:dimitri.papadimitriou@alcatel-lucent.com">dimitri.papadimi=
triou@alcatel-lucent.com</a>&gt;, &lt;<a =
href=3D"mailto:lberger@labn.net">lberger@labn.net</a>&gt;<o:p></o:p></spa=
n></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:10.5pt;line-height:115%;font-family:"Verdana","sans-se=
rif";color:#08003F'><o:p>&nbsp;</o:p></span></p></div><div><div><p =
class=3DMsoNormal><span style=3D'color:#08003F'>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></span></p><p class=3DMsoNormal><span =
style=3D'color:#08003F'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:#08003F'>Please resolve these =
comments along with any other Last Call comments you may =
receive.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#08003=
F'>&nbsp;</span><span style=3D'color:#08003F'><o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#08003=
F'>Document: </span><span =
style=3D'color:#08003F'>draft-ietf-ccamp-rfc5787bis-05.<o:p></o:p></span>=
</p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#08003=
F'>Reviewer: Roni Even</span><span =
style=3D'color:#08003F'><o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#08003=
F'>Review Date:2012&#8211;8&#8211;12</span><span =
style=3D'color:#08003F'><o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#08003=
F'>IETF LC End Date: 2012&#8211;8&#8211;17</span><span =
style=3D'color:#08003F'><o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#08003=
F'>IESG Telechat date:</span><span =
style=3D'color:#08003F'><o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#08003=
F'>&nbsp;</span><span style=3D'color:#08003F'><o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#08003=
F'>Summary: This draft is almost ready for publication as a standard =
track RFC.</span><span style=3D'color:#08003F'><o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#08003=
F'>&nbsp;</span><span style=3D'color:#08003F'><o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#08003=
F'>&nbsp;</span><span style=3D'color:#08003F'><o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#08003=
F'>Major issues:</span><span =
style=3D'color:#08003F'><o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#08003=
F'>&nbsp;</span><span style=3D'color:#08003F'><o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#08003=
F'>Minor issues:</span><span =
style=3D'color:#08003F'><o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#08003F'>In section 6.1 &#8220; If specified more than =
once, instances preceding the first will be ignored and condition SHOULD =
be logged for possible action by the network operator.&#8221;&nbsp; I am =
not sure what is meant by preceding the first.<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#08003F'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#08003=
F'>&nbsp;</span><span style=3D'color:#08003F'><o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#08003=
F'>Nits/editorial comments:</span><span =
style=3D'color:#08003F'><o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#08003=
F'>&nbsp;</span><span style=3D'color:#08003F'><o:p></o:p></span></p><ol =
style=3D'margin-top:0in' start=3D1 type=3D1><li class=3DMsoNormal =
style=3D'color:#08003F;mso-list:l1 level1 lfo3'>The following note =
appears in section 10.1, 10.2 and 10.3. &#8220;Note that the same values =
for the Inter-RA Export Upward sub-TLV and the Inter-RA Export Downward =
Sub-TLV MUST be used when they appear in the Link TLV, Node Attribute =
TLV, and Router Address TLV.&#8221; &#8211; why not have it in section =
10 before section 10.1.<o:p></o:p></li><li class=3DMsoNormal =
style=3D'color:#08003F;mso-list:l1 level1 lfo3'>I saw in appendix&nbsp; =
B that one of the changes from RFC 5787 was to clarify the terminology =
before defining extensions, I would have found it easier to read if the =
ASON hierarchy and the relation to OSPF in section 2 were presented in =
figures. This was more an issue to me as a reader not familiar with the =
terminology and I would like to think that the more familiar reader will =
not have problem.<o:p></o:p></li></ol><p class=3DMsoNormal><span =
style=3D'color:#08003F'>&nbsp;<o:p></o:p></span></p></div></div></div></b=
ody></html>
------=_NextPart_000_011B_01CDA644.0940EFD0--


From david.black@emc.com  Mon Oct  8 13:11:56 2012
Return-Path: <david.black@emc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A918E21F87F9; Mon,  8 Oct 2012 13:11:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id x26clcZ4oPbd; Mon,  8 Oct 2012 13:11:56 -0700 (PDT)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id BA61821F8702; Mon,  8 Oct 2012 13:11:55 -0700 (PDT)
Received: from hop04-l1d11-si04.isus.emc.com (HOP04-L1D11-SI04.isus.emc.com [10.254.111.24]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q98KBlHj021251 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 8 Oct 2012 16:11:48 -0400
Received: from mailhub.lss.emc.com (mailhub.lss.emc.com [10.254.221.145]) by hop04-l1d11-si04.isus.emc.com (RSA Interceptor); Mon, 8 Oct 2012 16:11:43 -0400
Received: from mxhub24.corp.emc.com (mxhub24.corp.emc.com [128.222.70.136]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q98KBeoH030012; Mon, 8 Oct 2012 16:11:41 -0400
Received: from mx15a.corp.emc.com ([169.254.1.83]) by mxhub24.corp.emc.com ([128.222.70.136]) with mapi; Mon, 8 Oct 2012 16:11:41 -0400
From: "Black, David" <david.black@emc.com>
To: Barry Leiba <barryleiba@computer.org>, Glen Zorn <glenzorn@gmail.com>, "precis-chairs@tools.ietf.org" <precis-chairs@tools.ietf.org>
Date: Mon, 8 Oct 2012 16:11:39 -0400
Subject: RE: Gen-ART review of draft-ietf-dime-rfc4005bis-11
Thread-Topic: Gen-ART review of draft-ietf-dime-rfc4005bis-11
Thread-Index: Ac2leMQ+3QDh/2XtR/iDfUkrQqimgwAFfE4Q
Message-ID: <8D3D17ACE214DC429325B2B98F3AE7120DF11C12@MX15A.corp.emc.com>
References: <8D3D17ACE214DC429325B2B98F3AE7120DCD17FD@MX15A.corp.emc.com> <50712F0A.1050309@gmail.com> <CAC4RtVDDBo+kVJMpS+j1sCHy_qtn0FzLkrpzqysPZTaPTHpm1w@mail.gmail.com>
In-Reply-To: <CAC4RtVDDBo+kVJMpS+j1sCHy_qtn0FzLkrpzqysPZTaPTHpm1w@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-EMM-MHVC: 1
X-Mailman-Approved-At: Tue, 09 Oct 2012 08:47:46 -0700
Cc: "dime-chairs@tools.ietf.org" <dime-chairs@tools.ietf.org>, "lionel.morand@orange.com" <lionel.morand@orange.com>, "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-dime-rfc4005bis@tools.ietf.org" <draft-ietf-dime-rfc4005bis@tools.ietf.org>, "dime@ietf.org" <dime@ietf.org>, "Black, David" <david.black@emc.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Oct 2012 20:11:56 -0000

Barry,

> >> 5) Statement that the string contains an FQDN, as stated for one case =
of
> >> the Tunnel-Client-Endpoint AVP in 4.5.4. That specific statement is
> >> incomplete, as it needs to be accompanied by a normative reference to
> >> a document that specifies the format of internationalized domain
> >> names, and probably needs to also state which types of labels (e.g.,
> >> A-label, U-label) are allowed.
> >>
> >> Every use of UTF8String in this draft needs to be checked, and most
> >> of them are likely to need some attention. The ongoing work in the
> >> precis WG may help with some of this, and I would suggest talking to
> >> the APP ADs, especially Pete Resnick (hi Pete) before embarking on
> >> significant work in this area in order to avoid wasted or duplicated
> >> efforts.
> >
> > OK, this last one bothers me a lot: you /seem /to be suggesting that we=
 hold
> > up this draft to wait for the result of a WG which has yet to publish a
> > problem statement.  I'm sure that that is not the case, but it sure sou=
nds
> > like it.
>=20
> David can clarify if I'm wrong, but that's not what it sounds like to
> me.  What it sounds like he's suggesting is that you talk with the
> precis people to see if things are OK, or if there's anything you
> should be doing differently.  I'm adding the precis chairs to this
> message, and asking them to respond to this point.

It's somewhere in between, as things are definitely *not* OK at the moment,
but my reason for suggesting a discussion with the pr=E9cis folks is to tak=
e
advantage of their insights and work to date.  If I thought this draft need=
ed
to wait for the output of the pr=E9cis WG, I would have indicated which pr=
=E9cis
draft ought to be a normative reference (and I did not do that).  Whether
that's a good idea will only be clear after every use of UTF8String is chec=
ked.

FWIW, the FQDN situation is worked out, start with a normative reference to
RFC 5890, which includes the specification of the various label types.

> A tangential point, while I'm here:
>=20
> >> [4] Based on this text in 4.4.9:
> >> The use of this AVP is NOT RECOMMENDED; the AVPs defined by
> >> Korhonen, et al. [RFC5777] SHOULD be used instead.
> >>
> >> I would have expected RFC5777 to be a Normative Reference, not an
> >> Informative Reference.
> >
> > I don't care particularly, but I don't think that it's really necessary=
 to
> > understand RFC 5777 to understand this document.
>=20
> It would seem odd, in general, if something that's a "MUST implement"
> or "SHOULD implement" weren't a normative reference.  But I haven't
> (yet) looked at this particular case to see.

My expectation is the same - if [RFCxxxx] is specified as "MUST implement"
or "SHOULD implement", then I usually expect that RFC to be a normative
reference.

Thanks,
--David
----------------------------------------------------
David L. Black, Distinguished Engineer
EMC Corporation, 176 South St., Hopkinton, MA=A0 01748
+1 (508) 293-7953=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 FAX: +1 (508) 293-778=
6
david.black@emc.com=A0=A0=A0=A0=A0=A0=A0 Mobile: +1 (978) 394-7754
----------------------------------------------------




From david.black@emc.com  Mon Oct  8 13:53:17 2012
Return-Path: <david.black@emc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EBEA011E80F1; Mon,  8 Oct 2012 13:53:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cPELdoa54pNm; Mon,  8 Oct 2012 13:53:16 -0700 (PDT)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id AF71A11E80F0; Mon,  8 Oct 2012 13:53:16 -0700 (PDT)
Received: from hop04-l1d11-si01.isus.emc.com (HOP04-L1D11-SI01.isus.emc.com [10.254.111.54]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q98KrEHS006683 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 8 Oct 2012 16:53:14 -0400
Received: from mailhub.lss.emc.com (mailhub.lss.emc.com [10.254.222.130]) by hop04-l1d11-si01.isus.emc.com (RSA Interceptor); Mon, 8 Oct 2012 16:52:59 -0400
Received: from mxhub16.corp.emc.com (mxhub16.corp.emc.com [128.222.70.237]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q98KqwFY017595; Mon, 8 Oct 2012 16:52:58 -0400
Received: from mx15a.corp.emc.com ([169.254.1.83]) by mxhub16.corp.emc.com ([128.222.70.237]) with mapi; Mon, 8 Oct 2012 16:52:58 -0400
From: "Black, David" <david.black@emc.com>
To: Glen Zorn <glenzorn@gmail.com>
Date: Mon, 8 Oct 2012 16:52:56 -0400
Subject: RE: Gen-ART review of draft-ietf-dime-rfc4005bis-11
Thread-Topic: Gen-ART review of draft-ietf-dime-rfc4005bis-11
Thread-Index: Ac2kXoeQSUAX8En/RPGw5bTX7IkshwBMzE7Q
Message-ID: <8D3D17ACE214DC429325B2B98F3AE7120DF11C25@MX15A.corp.emc.com>
References: <8D3D17ACE214DC429325B2B98F3AE7120DCD17FD@MX15A.corp.emc.com> <50712F0A.1050309@gmail.com>
In-Reply-To: <50712F0A.1050309@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-EMM-MHVC: 1
X-Mailman-Approved-At: Tue, 09 Oct 2012 08:47:46 -0700
Cc: "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-dime-rfc4005bis@tools.ietf.org" <draft-ietf-dime-rfc4005bis@tools.ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, "lionel.morand@orange.com" <lionel.morand@orange.com>, "dime@ietf.org" <dime@ietf.org>, "Black, David" <david.black@emc.com>, "dime-chairs@tools.ietf.org" <dime-chairs@tools.ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Oct 2012 20:53:18 -0000

Glen,

Picking up the topics that weren't in Barry's email ...

>  > 1) String preparation so that tests for equality work as expected.
>  > This may suffice for the Called-Station-ID AVP (4.2.5) and
>  > Calling-Station-ID AVP (4.2.6) if the internal structure of those
>  > strings is not used in authorization.
>=20
> Both those AVPs are specified to contain ASCII encoded as UTF-8.  Is
> string preparation necessary in that case?

Not in the full glory that is needed for serious usage of UTF-8, but
it looks like the language in the draft should be tightened.  At a
minimum, a "MUST" is in order to require use of 7-bit ASCII encoded
as UTF-8.  Among the reasons for such a requirement is to prohibit the
various ISO/IEC 8859-* character sets (a/k/a Latin-*), which are
8-bit ASCII and not distinguishable from each other on the wire
without an additional character set tag of some form.

I would also suggest forbidding control characters (e.g., require
displayable 7-bit ASCII characters) and saying something about case
handling, starting with whether the strings are case sensitive or case
insensitive.  Case sensitivity is simpler to specify, but may not yield
intuitive and/or expected results.  If the strings are case insensitive,
text should be added to say whether the strings are case-normalized on
the wire and/or whether the recipient is expected to implement case-
insensitive string comparison.

> > 2) Detailed string format for a
>  > string that is processed by a protocol participant, e.g., the
>  > Callback-ID AVP (4.4.3).
>=20
> That format is unknown in this case.

Please explain how that's supposed to result in interoperable processing
by the "protocol participant".

>  > [1] End of Section 2 on p.8:
>  >
>  > As a result, service cannot be started as a result of a response to
>  > an authorization-only request without introducing a significant
>  > security vulnerability.
>  >
>  > Please explain what to do about this - a simple rewrite with a
>  > "SHOULD NOT" would suffice, e.g.:
>  >
>  > As a result, service SHOULD NOT be started as a result of a response
>  > to an authorization-only request because that may introduce a
>  > significant security vulnerability.
>=20
> The text in question is descriptive, not prescriptive. That said, however=
,
> I think that it's not really clear.  I think that it should say
> something like "As a result, a new session cannot be started as a result
> of a response to an authorization-only request without introducing a
> significant security vulnerability."
>=20
> >
>  > This should also be noted in the Security Considerations section.

The rewrite helps, and make sure to add text about this in the Security
Considerations section.

>  > =3D=3D Missing Reference: 'BASE' is mentioned on line 219, but not
>  > defined
>  >
>  > That's definitely a problem. Was [I-D.ietf-dime-rfc3588bis]
>  > intended?
>=20
> No.  The passage in question is a verbatim quote from RFC 4005.

Ok, just fix this so idnits can find something else to complain about :-).

Thanks,
--David

> -----Original Message-----
> From: Glen Zorn [mailto:glenzorn@gmail.com]
> Sent: Sunday, October 07, 2012 3:28 AM
> To: Black, David
> Cc: glenzorn@gmail.com; lionel.morand@orange.com; gen-art@ietf.org; dime-
> chairs@tools.ietf.org; draft-ietf-dime-rfc4005bis@tools.ietf.org;
> ietf@ietf.org; dime@ietf.org; Benoit Claise
> Subject: Re: Gen-ART review of draft-ietf-dime-rfc4005bis-11
>=20
> On 09/18/2012 06:53 AM, Black, David wrote:
>=20
> > I am the assigned Gen-ART  reviewer for this draft. For background on
>  > Gen-ART, please see the FAQ at
>  > <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>  >
>  > Please resolve these comments along with any other Last Call
>  > comments you may receive.
>  >
>  > Document: draft-ietf-dime-rfc4005bis-11 Reviewer: David L. Black
>  > Review Date: September 17, 2012 IETF LC End Date: September 18, 2012
>  > IESG Telechat date: (if known)
>  >
>  > Summary:
>  >
>  > This draft is on the right track but has open issues, described in
>  > the review.
>  >
>  > This draft is part of a set of drafts that updates the DIAMETER
>  > protocol; this draft specifies the application of DIAMETER to AAA for
>  > network access. The draft is heavily based on RFC 4005, which it
>  > obsoletes, and requires significant DIAMETER familiarity (including
>  > familiarity with its companion drafts, starting with the rfc3588bis
>  > draft) for complete understanding.
>  >
>  > The draft is in good shape and reads well. I found one major open
>  > issue, a few minor issues, and several nits.
>  >
>  > Major issues:
>  >
>  > This draft makes significant use of UTF-8 in its formats (some
>  > subsections of sections 4.2, 4.4 and 4.5) for strings that are
>  > intended to be compared for equality or processed by protocol
>  > participants, but does not contain considerations for Unicode
>  > processing that are sufficient to support this usage. Examples of
>  > UTF-8 usage in this draft include:
>  >
>  > - 4.2.5 and 4.2.6: The NAS server may perform authorization based on
>  > the Called-Station-Id and Calling-Station-Id AVPs under some
>  > circumstances. - 4.4.3: The Callback-Id AVP is intended to be
>  > interpreted by the NAS.
>  >
>  > All use of UTF-8 in this draft relies upon the specification of the
>  > UTF8String format in the rfc3588bis draft. That specification is
>  > insufficient to support the usage in the above examples, and there
>  > are no Unicode considerations in this draft. Even binary comparison
>  > of Unicode strings for equality generally requires specification of
>  > string preparation (e.g., normalization) in order for string
>  > comparison to work as expected.
>  >
>  > The variety of Unicode strings in this draft makes it important to
>  > lay out the Unicode requirements and considerations for each AVP. I
>  > see at least 5 classes of possible Unicode
>  > requirements/considerations:
>  >
>  > 1) String preparation so that tests for equality work as expected.
>  > This may suffice for the Called-Station-ID AVP (4.2.5) and
>  > Calling-Station-ID AVP (4.2.6) if the internal structure of those
>  > strings is not used in authorization.
>=20
> Both those AVPs are specified to contain ASCII encoded as UTF-8.  Is
> string preparation necessary in that case?
>=20
> > 2) Detailed string format for a
>  > string that is processed by a protocol participant, e.g., the
>  > Callback-ID AVP (4.4.3).
>=20
> That format is unknown in this case.
> ...
> > 5) Statement that the string  contains an FQDN, as stated for one case =
of
>  > the Tunnel-Client-Endpoint AVP in 4.5.4. That specific statement is
>  > incomplete, as it needs to be accompanied by a normative reference to
>  > a document that specifies the format of internationalized domain
>  > names, and probably needs to also state which types of labels (e.g.,
>  > A-label, U-label) are allowed.
>  >
>  > Every use of UTF8String in this draft needs to be checked, and most
>  > of them are likely to need some attention. The ongoing work in the
>  > precis WG may help with some of this, and I would suggest talking to
>  > the APP ADs, especially Pete Resnick (hi Pete) before embarking on
>  > significant work in this area in order to avoid wasted or duplicated
>  > efforts.
>=20
> OK, this last one bothers me a lot: you /seem /to be suggesting that we
> hold up this draft to wait for the result of a WG which has yet to
> publish a problem statement.  I'm sure that that is not the case, but it
> sure sounds like it.
>=20
> >
>  > Minor Issues:
>  >
>  > [1] End of Section 2 on p.8:
>  >
>  > As a result, service cannot be started as a result of a response to
>  > an authorization-only request without introducing a significant
>  > security vulnerability.
>  >
>  > Please explain what to do about this - a simple rewrite with a
>  > "SHOULD NOT" would suffice, e.g.:
>  >
>  > As a result, service SHOULD NOT be started as a result of a response
>  > to an authorization-only request because that may introduce a
>  > significant security vulnerability.
>=20
> The text in question is descriptive, not prescriptive.at said, however,
> I think that it's not really clear.  I think that it should say
> something like "As a result, a new session cannot be started as a result
> of a response to an authorization-only request without introducing a
> significant security vulnerability."
>=20
> >
>  > This should also be noted in the Security Considerations section.
>  >
>  > [2] In the message formats in Section 3, QoS-Filter-Rule is
>  > inconsistently capitalized.
>=20
> OK, thanks.
>=20
> > Also the use of QoSFilterRule  as the
>  > format for the QoS-Filter-Rule AVP in Section 4.1.1 is potentially
>  > confusing. Please add a sentence in 4.1.1 to say that QoSFilterRule
>  > is the format for the QoS-Filter-Rule AVP.
>  >
>  > [3] Section 4.2.1. In this and the other AVP Flag Rules tables,
>  > please explain what the values in the MUST and MUST NOT columns
>  > mean.
>  >
>  > [4] Based on this text in 4.4.9:
>  >
>  > The use of this AVP is NOT RECOMMENDED; the AVPs defined by
>  > Korhonen, et al. [RFC5777] SHOULD be used instead.
>  >
>  > I would have expected RFC5777 to be a Normative Reference, not an
>  > Informative Reference.
>=20
> I don't care particularly, but I don't think that it's really necessary
> to understand RFC 5777 to understand this document.
>=20
> >
>  > Nits/editorial comments:
>  >
>  > After the command table in Section 3 and other similar tables, please
>  > add a sentence to say that the -Request and -Answer commands in each
>  > similarly-named command pair are distinguished by the value of the
>  > 'R' bit in the Command Flags field of the command. This is already
>  > stated in the command definitions, but the sentence should be added
>  > after the table for clarity because each command pair shares a
>  > Command Code.
>  >
>  > idnits 2.12.13 found a few potential nits:
>  >
>  > =3D=3D There are 7 instances of lines with non-RFC5735-compliant IPv4
>  > addresses in the document. If these are example addresses, they
>  > should be changed.
>  >
>  > That can probably be ignored, as these instances are likely generated
>  > by text such as cross-references to Section 4.4.10.1
>  >
>  > =3D=3D Missing Reference: 'BASE' is mentioned on line 219, but not
>  > defined
>  >
>  > That's definitely a problem. Was [I-D.ietf-dime-rfc3588bis]
>  > intended?
>=20
> No.  The passage in question is a verbatim quote from RFC 4005.
>=20
> >
>  > -- Possible downref: Non-RFC (?) normative reference: ref.
>  > 'ANITypes'
>  >
>  > That reference would be:
>  >
>  > [ANITypes] NANPA Number Resource Info, "ANI Assignments",
>  > <http://www.nanpa.com/ number_resource_info/
>  > ani_ii_assignments.html>.
>  >
>  > Is that reference sufficiently stable (e.g., IANA-class or better
>  > management)?
>=20
> Yes, I think so.
>=20
> > My guess is that it is  sufficiently stable, but I'm not
>  > the expert.
> >
>  > -- Obsolete informational reference (is this intentional?): RFC 1334
>  > (Obsoleted by RFC 1994)
>  >
>  > That reference may be intentional,
>=20
> Yes.
>=20
> ...


From andrew.g.malis@verizon.com  Mon Oct  8 17:55:31 2012
Return-Path: <andrew.g.malis@verizon.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D4C1811E80F5; Mon,  8 Oct 2012 17:55:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.561
X-Spam-Level: 
X-Spam-Status: No, score=-3.561 tagged_above=-999 required=5 tests=[AWL=0.037,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rfzCBo+0yet1; Mon,  8 Oct 2012 17:55:31 -0700 (PDT)
Received: from fldsmtpe02.verizon.com (fldsmtpe02.verizon.com [140.108.26.141]) by ietfa.amsl.com (Postfix) with ESMTP id 9529111E80DF; Mon,  8 Oct 2012 17:55:30 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: false
Received: from unknown (HELO fldsmtpi03.verizon.com) ([166.68.71.145]) by fldsmtpe02.verizon.com with ESMTP; 09 Oct 2012 00:55:13 +0000
From: "Malis, Andrew G \(Andy\)" <andrew.g.malis@verizon.com>
X-IronPort-AV: E=Sophos;i="4.80,556,1344211200";  d="scan'208,217";a="342506104"
Received: from fhdp1lumxc7hb02.verizon.com (HELO FHDP1LUMXC7HB02.us.one.verizon.com) ([166.68.59.189]) by fldsmtpi03.verizon.com with ESMTP; 09 Oct 2012 00:55:13 +0000
Received: from fhdp1lumxc7v22.us.one.verizon.com ([166.68.59.158]) by FHDP1LUMXC7HB02.us.one.verizon.com ([166.68.59.189]) with mapi; Mon, 8 Oct 2012 20:55:13 -0400
To: Roni Even <ron.even.tlv@gmail.com>, "draft-ietf-ccamp-rfc5787bis.all@tools.ietf.org" <draft-ietf-ccamp-rfc5787bis.all@tools.ietf.org>
Date: Mon, 8 Oct 2012 20:55:12 -0400
Subject: Re: Gen-ART LC review of draft-ietf-ccamp-rfc5787bis-05
Thread-Topic: Gen-ART LC review of draft-ietf-ccamp-rfc5787bis-05
Thread-Index: Ac2luLyUqlVszi5WS+u1neT2y/FIkQ==
Message-ID: <CC98C05A.2FC85%andrew.g.malis@one.verizon.com>
In-Reply-To: <002101cd7997$a5204330$ef60c990$@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.2.4.120824
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_CC98C05A2FC85andrewgmalisoneverizoncom_"
MIME-Version: 1.0
X-Mailman-Approved-At: Tue, 09 Oct 2012 08:47:46 -0700
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "Malis, Andrew G \(Andy\)" <andrew.g.malis@verizon.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Oct 2012 00:55:32 -0000

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

Roni,

Thanks for your review, and sorry for the delay on the response, but we've =
also been working on incorporating other changes to the draft as well.

To answer your question on section 6.1, that was a good catch. That should =
have said "other than the first", rather than "preceding the first". This w=
ill be corrected.

To answer your question on section 10, the text is repeated in the subsecti=
ons to make life easier for IANA, since they would probably have replicated=
 it themselves anyway in the three registry listings.

On your last comment, we agree with you that the more familiar reader will =
not have a problem.

Thanks again,
Andy

From: Roni Even <ron.even.tlv@gmail.com<mailto:ron.even.tlv@gmail.com>>
Date: Monday, August 13, 2012 14:07
To: "draft-ietf-ccamp-rfc5787bis.all@tools.ietf.org<mailto:draft-ietf-ccamp=
-rfc5787bis.all@tools.ietf.org>" <draft-ietf-ccamp-rfc5787bis.all@tools.iet=
f.org<mailto:draft-ietf-ccamp-rfc5787bis.all@tools.ietf.org>>
Cc: "ietf@ietf.org<mailto:ietf@ietf.org>" <ietf@ietf.org<mailto:ietf@ietf.o=
rg>>, "gen-art@ietf.org<mailto:gen-art@ietf.org>" <gen-art@ietf.org<mailto:=
gen-art@ietf.org>>
Subject: Gen-ART LC review of draft-ietf-ccamp-rfc5787bis-05
Resent-To: <acee.lindem@ericsson.com<mailto:acee.lindem@ericsson.com>>, Adr=
ian Farrell <adrian@olddog.co.uk<mailto:adrian@olddog.co.uk>>, Andrew Malis=
 <andrew.g.malis@verizon.com<mailto:andrew.g.malis@verizon.com>>, <dbrungar=
d@att.com<mailto:dbrungard@att.com>>, <dimitri.papadimitriou@alcatel-lucent=
.com<mailto:dimitri.papadimitriou@alcatel-lucent.com>>, <lberger@labn.net<m=
ailto:lberger@labn.net>>

I am the assigned Gen-ART reviewer for this draft. For background on Gen-AR=
T, please see the FAQ at <http://wiki.tools.ietf.org/area/gen/trac/wiki/Gen=
Artfaq>.

Please resolve these comments along with any other Last Call comments you m=
ay receive.



Document: draft-ietf-ccamp-rfc5787bis-05.

Reviewer: Roni Even

Review Date:2012=968=9612

IETF LC End Date: 2012=968=9617

IESG Telechat date:



Summary: This draft is almost ready for publication as a standard track RFC=
.





Major issues:



Minor issues:
In section 6.1 =93 If specified more than once, instances preceding the fir=
st will be ignored and condition SHOULD be logged for possible action by th=
e network operator.=94  I am not sure what is meant by preceding the first.




Nits/editorial comments:



 1.  The following note appears in section 10.1, 10.2 and 10.3. =93Note tha=
t the same values for the Inter-RA Export Upward sub-TLV and the Inter-RA E=
xport Downward Sub-TLV MUST be used when they appear in the Link TLV, Node =
Attribute TLV, and Router Address TLV.=94 =96 why not have it in section 10=
 before section 10.1.
 2.  I saw in appendix  B that one of the changes from RFC 5787 was to clar=
ify the terminology before defining extensions, I would have found it easie=
r to read if the ASON hierarchy and the relation to OSPF in section 2 were =
presented in figures. This was more an issue to me as a reader not familiar=
 with the terminology and I would like to think that the more familiar read=
er will not have problem.


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

<html><head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252"></head><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space;=
 -webkit-line-break: after-white-space; color: rgb(8, 0, 63); font-size: 14=
px; font-family: Verdana, sans-serif; "><div>Roni,</div><div><br></div><div=
><div>Thanks for your review, and sorry for the delay on the response, but =
we've&nbsp;also been working on incorporating other changes to the draft as=
 well.&nbsp;</div></div><div><br></div><div>To answer your question on sect=
ion 6.1, that was a good catch. That should have said &quot;other than the =
first&quot;, rather than &quot;preceding the first&quot;. This will be corr=
ected.</div><div><br></div><div>To answer your question on section 10, the =
text is repeated in the subsections to make life easier for IANA, since the=
y would probably have replicated it themselves anyway in the three registry=
 listings.</div><div><br></div><div>On your last comment, we agree with you=
 that the more familiar reader will not have a problem.</div><div><br></div=
><div>Thanks again,</div><div>Andy</div><div><br></div><span id=3D"OLK_SRC_=
BODY_SECTION"><div style=3D"font-family:Tahoma; font-size:10pt; text-align:=
left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PA=
DDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4=
df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt"><span style=3D"f=
ont-weight:bold">From: </span> Roni Even &lt;<a href=3D"mailto:ron.even.tlv=
@gmail.com">ron.even.tlv@gmail.com</a>&gt;<br><span style=3D"font-weight:bo=
ld">Date: </span> Monday, August 13, 2012 14:07 <br><span style=3D"font-wei=
ght:bold">To: </span> &quot;<a href=3D"mailto:draft-ietf-ccamp-rfc5787bis.a=
ll@tools.ietf.org">draft-ietf-ccamp-rfc5787bis.all@tools.ietf.org</a>&quot;=
 &lt;<a href=3D"mailto:draft-ietf-ccamp-rfc5787bis.all@tools.ietf.org">draf=
t-ietf-ccamp-rfc5787bis.all@tools.ietf.org</a>&gt;<br><span style=3D"font-w=
eight:bold">Cc: </span> &quot;<a href=3D"mailto:ietf@ietf.org">ietf@ietf.or=
g</a>&quot; &lt;<a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a>&gt;, &qu=
ot;<a href=3D"mailto:gen-art@ietf.org">gen-art@ietf.org</a>&quot; &lt;<a hr=
ef=3D"mailto:gen-art@ietf.org">gen-art@ietf.org</a>&gt;<br><span style=3D"f=
ont-weight:bold">Subject: </span> Gen-ART LC review of draft-ietf-ccamp-rfc=
5787bis-05<br><span style=3D"font-weight:bold">Resent-To: </span> &lt;<a hr=
ef=3D"mailto:acee.lindem@ericsson.com">acee.lindem@ericsson.com</a>&gt;, Ad=
rian Farrell &lt;<a href=3D"mailto:adrian@olddog.co.uk">adrian@olddog.co.uk=
</a>&gt;, Andrew Malis &lt;<a href=3D"mailto:andrew.g.malis@verizon.com">an=
drew.g.malis@verizon.com</a>&gt;, &lt;<a href=3D"mailto:dbrungard@att.com">=
dbrungard@att.com</a>&gt;, &lt;<a href=3D"mailto:dimitri.papadimitriou@alca=
tel-lucent.com">dimitri.papadimitriou@alcatel-lucent.com</a>&gt;, &lt;<a hr=
ef=3D"mailto:lberger@labn.net">lberger@labn.net</a>&gt;<br></div><div><br><=
/div><div 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:wo=
rd" xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"h=
ttp://www.w3.org/TR/REC-html40"><meta name=3D"Generator" content=3D"Microso=
ft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:10.0pt;
	margin-left:0in;
	line-height:115%;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:715087181;
	mso-list-type:hybrid;
	mso-list-template-ids:-1205706658 -1668626108 67698713 67698715 67698703 6=
7698713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-bidi-font-family:Calibri;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--><div lang=3D"EN-US" link=3D"blue" vlink=
=3D"purple"><div class=3D"WordSection1"><p class=3D"MsoNormal">I am the ass=
igned Gen-ART reviewer for this draft. For background on Gen-ART, please se=
e the FAQ at &lt;<a href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/G=
enArtfaq" target=3D"_blank">http://wiki.tools.ietf.org/area/gen/trac/wiki/G=
enArtfaq</a>&gt;.<o:p></o:p></p><p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p=
><p class=3D"MsoNormal">Please resolve these comments along with any other =
Last Call comments you may receive.<o:p></o:p></p><p class=3D"MsoPlainText"=
><span style=3D"font-size: 11pt; font-family: Calibri, sans-serif; "><o:p>&=
nbsp;</o:p></span></p><p class=3D"MsoPlainText"><span style=3D"font-size: 1=
1pt; font-family: Calibri, sans-serif; ">Document:
</span>draft-ietf-ccamp-rfc5787bis-05.<span style=3D"font-size: 11pt; font-=
family: Calibri, sans-serif; "><o:p></o:p></span></p><p class=3D"MsoPlainTe=
xt"><span style=3D"font-size: 11pt; font-family: Calibri, sans-serif; ">Rev=
iewer: Roni Even<o:p></o:p></span></p><p class=3D"MsoPlainText"><span style=
=3D"font-size: 11pt; font-family: Calibri, sans-serif; ">Review Date:2012=
=968=9612<o:p></o:p></span></p><p class=3D"MsoPlainText"><span style=3D"fon=
t-size: 11pt; font-family: Calibri, sans-serif; ">IETF LC End Date: 2012=96=
8=9617<o:p></o:p></span></p><p class=3D"MsoPlainText"><span style=3D"font-s=
ize: 11pt; font-family: Calibri, sans-serif; ">IESG Telechat date:<o:p></o:=
p></span></p><p class=3D"MsoPlainText"><span style=3D"font-size: 11pt; font=
-family: Calibri, sans-serif; "><o:p>&nbsp;</o:p></span></p><p class=3D"Mso=
PlainText"><span style=3D"font-size: 11pt; font-family: Calibri, sans-serif=
; ">Summary: This draft is almost ready for publication as</span><span styl=
e=3D"font-size: 11pt; font-family: Calibri, sans-serif; "> a standard track
</span><span style=3D"font-size: 11pt; font-family: Calibri, sans-serif; ">=
RFC</span><span style=3D"font-size: 11pt; font-family: Calibri, sans-serif;=
 ">.<o:p></o:p></span></p><p class=3D"MsoPlainText"><span style=3D"font-siz=
e: 11pt; font-family: Calibri, sans-serif; "><o:p>&nbsp;</o:p></span></p><p=
 class=3D"MsoPlainText"><span style=3D"font-size: 11pt; font-family: Calibr=
i, sans-serif; "><o:p>&nbsp;</o:p></span></p><p class=3D"MsoPlainText"><spa=
n style=3D"font-size: 11pt; font-family: Calibri, sans-serif; ">Major issue=
s:<o:p></o:p></span></p><p class=3D"MsoPlainText"><span style=3D"font-size:=
 11pt; font-family: Calibri, sans-serif; "><o:p>&nbsp;</o:p></span></p><p c=
lass=3D"MsoPlainText"><span style=3D"font-size: 11pt; font-family: Calibri,=
 sans-serif; ">Minor issues:<o:p></o:p></span></p><p class=3D"MsoNormal">In=
 section 6.1 =93 If specified more than once, instances preceding the first=
 will be ignored and condition SHOULD be logged for possible action by the =
network operator.=94&nbsp; I am not sure what is meant by preceding the fir=
st.<o:p></o:p></p><p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p><p class=3D"M=
soPlainText"><span style=3D"font-size: 11pt; font-family: Calibri, sans-ser=
if; "><o:p>&nbsp;</o:p></span></p><p class=3D"MsoPlainText"><span style=3D"=
font-size: 11pt; font-family: Calibri, sans-serif; ">Nits/editorial comment=
s:<o:p></o:p></span></p><p class=3D"MsoPlainText"><span style=3D"font-size:=
 11pt; font-family: Calibri, sans-serif; "><o:p>&nbsp;</o:p></span></p><ol =
style=3D"margin-top:0in" start=3D"1" type=3D"1"><li class=3D"MsoNormal" sty=
le=3D"mso-list:l0 level1 lfo1">The following note appears in section 10.1, =
10.2 and 10.3. =93Note that the same values for the Inter-RA Export Upward =
sub-TLV and the Inter-RA Export Downward Sub-TLV MUST be used when they app=
ear in the
 Link TLV, Node Attribute TLV, and Router Address TLV.=94 =96 why not have =
it in section 10 before section 10.1.<o:p></o:p></li><li class=3D"MsoNormal=
" style=3D"mso-list:l0 level1 lfo1">I saw in appendix&nbsp; B that one of t=
he changes from RFC 5787 was to clarify the terminology before defining ext=
ensions, I would have found it easier to read if the ASON hierarchy and the=
 relation to OSPF in
 section 2 were presented in figures. This was more an issue to me as a rea=
der not familiar with the terminology and I would like to think that the mo=
re familiar reader will not have problem.<o:p></o:p></li></ol><p class=3D"M=
soPlainText"><span style=3D"font-size: 11pt; font-family: Calibri, sans-ser=
if; "><o:p></o:p></span></p><p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p></d=
iv></div></div></span></body></html>

--_000_CC98C05A2FC85andrewgmalisoneverizoncom_--

From sm@resistor.net  Tue Oct  9 09:07:20 2012
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B39AC1F0C94 for <ietf@ietfa.amsl.com>; Tue,  9 Oct 2012 09:07:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.594
X-Spam-Level: 
X-Spam-Status: No, score=-102.594 tagged_above=-999 required=5 tests=[AWL=0.005, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 99kRdvH6btkl for <ietf@ietfa.amsl.com>; Tue,  9 Oct 2012 09:07:20 -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 343931F0C8C for <ietf@ietf.org>; Tue,  9 Oct 2012 09:07:20 -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 q99G7DD9010689 for <ietf@ietf.org>; Tue, 9 Oct 2012 09:07:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1349798837; bh=JgE/E2fL86+Bsa0mhagYIrChgULh5Xg4FUPr6Zvq5ho=; h=Date:To:From:Subject:In-Reply-To:References:Cc; b=WwVZR+RXeM99SidG303gkuT7pjrWR7Qr1vJetigP5XtR56cv50Iy9r1bUxezl6Let BUjJvI+nh2CbGC/iLWsD9SdhA4fK77ydwYYzpCHwBsrxSnzWFlrV3A52ft96WgMqtl QYBGiIeVkeHErmsk4xURroCsTUELVFH4PFl2PDXA=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1349798837; i=@resistor.net; bh=JgE/E2fL86+Bsa0mhagYIrChgULh5Xg4FUPr6Zvq5ho=; h=Date:To:From:Subject:In-Reply-To:References:Cc; b=0Ttys8V5J9Cxb8+Faz+V2u51PBpkvYymwjm0hpT+Klm5GIyc+vvvnSq5NeTaRohdE JNvYgy3UKmzyhzlYe3AsgFa6HM8amRAxdulorI6sMDMpDbVUF4btxs/kMYNgPZpgMv BUgr2ptE5ZLYhCGsBcPZNVIc0HKubLaTJAiyvqqo=
Message-Id: <6.2.5.6.2.20121009070956.0ac31c90@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 09 Oct 2012 08:25:06 -0700
To: ietf@ietf.org
From: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-ietf-precis-problem-statement-08.txt> (Stringprep Revision and PRECIS Problem Statement) to Informational RFC
In-Reply-To: <20121009134458.18784.49285.idtracker@ietfa.amsl.com>
References: <20121009134458.18784.49285.idtracker@ietfa.amsl.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Oct 2012 16:07:20 -0000

At 06:44 09-10-2012, The IESG wrote:
>The IESG has received a request from the Preparation and Comparison of
>Internationalized Strings WG (precis) to consider the following document:
>- 'Stringprep Revision and PRECIS Problem Statement'
>   <draft-ietf-precis-problem-statement-08.txt> as Informational RFC
>
>The IESG plans to make a decision in the next few weeks, and solicits
>final comments on this action. Please send substantive comments to the
>ietf@ietf.org mailing lists by 2012-10-23. Exceptionally, comments may be

Section 2 could be dropped as it isn't that important to have RFC 
2119 in a problem statement.  In Section 4:

   "For example, Stringprep is based on and profiles may
    use NFKC [UAX15], while IDNA2008 mostly uses NFC [UAX15]."

I suggest reviewing the references to see what background information 
is required for the reader to understand "NFKC".

In Section 6:

   "The above suggests the following guidance for replacing Stringprep:
    o  A stringprep replacement should be defined."

That sounds obvious.

The appendix is more informative than the rest of the draft.  The 
text in the Appendix B comes out as rough notes though.

In Section 5.3.3.2:

   "It is important to identify the willingness of the protocol-using
    community to accept backwards-incompatible changes."

The "tolerance for change" for several "protocol-using communities" 
is rated as "not sure".  I understand that it is difficult to get 
definitive answers for these questions.  It's doubtful that people 
will choose "better support for different linguistic environments 
against the potential side effects of backward incompatibility".  It 
seems that the WG has taken on an intractable problem.

Regards,
-sm 


From stpeter@stpeter.im  Tue Oct  9 09:25: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 2A4A621F87BC; Tue,  9 Oct 2012 09:25:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.535
X-Spam-Level: 
X-Spam-Status: No, score=-102.535 tagged_above=-999 required=5 tests=[AWL=0.064, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3opR9aSkCBjx; Tue,  9 Oct 2012 09:25:15 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id B7E3021F87B9; Tue,  9 Oct 2012 09:25:13 -0700 (PDT)
Received: from [192.168.1.2] (unknown [71.237.13.154]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id B3F80400F9; Tue,  9 Oct 2012 10:27:24 -0600 (MDT)
Message-ID: <50745001.9080308@stpeter.im>
Date: Tue, 09 Oct 2012 10:25:37 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:15.0) Gecko/20120907 Thunderbird/15.0.1
MIME-Version: 1.0
To: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-ietf-precis-problem-statement-08.txt> (Stringprep Revision and PRECIS Problem Statement) to Informational RFC
References: <20121009134458.18784.49285.idtracker@ietfa.amsl.com> <6.2.5.6.2.20121009070956.0ac31c90@resistor.net>
In-Reply-To: <6.2.5.6.2.20121009070956.0ac31c90@resistor.net>
X-Enigmail-Version: 1.4.4
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org, "precis@ietf.org" <precis@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Oct 2012 16:25:16 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 10/9/12 9:25 AM, SM wrote:
> At 06:44 09-10-2012, The IESG wrote:
>> The IESG has received a request from the Preparation and
>> Comparison of Internationalized Strings WG (precis) to consider
>> the following document: - 'Stringprep Revision and PRECIS Problem
>> Statement' <draft-ietf-precis-problem-statement-08.txt> as
>> Informational RFC
>> 
>> The IESG plans to make a decision in the next few weeks, and
>> solicits final comments on this action. Please send substantive
>> comments to the ietf@ietf.org mailing lists by 2012-10-23.
>> Exceptionally, comments may be
> 
> Section 2 could be dropped as it isn't that important to have RFC
> 2119 in a problem statement.  In Section 4:
> 
> "For example, Stringprep is based on and profiles may use NFKC
> [UAX15], while IDNA2008 mostly uses NFC [UAX15]."
> 
> I suggest reviewing the references to see what background
> information is required for the reader to understand "NFKC".

At the least, spelling out these acronyms on first use would be
helpful (e.g., "Unicode Normalization Form KC").

> In Section 6:
> 
> "The above suggests the following guidance for replacing
> Stringprep: o  A stringprep replacement should be defined."
> 
> That sounds obvious.
> 
> The appendix is more informative than the rest of the draft.  The
> text in the Appendix B comes out as rough notes though.

Indeed, that appendix consists of notes copied from a wiki page that
the PRECIS WG used to collect the information.

> In Section 5.3.3.2:
> 
> "It is important to identify the willingness of the protocol-using 
> community to accept backwards-incompatible changes."
> 
> The "tolerance for change" for several "protocol-using communities"
> is rated as "not sure".  I understand that it is difficult to get 
> definitive answers for these questions.  It's doubtful that people
> will choose "better support for different linguistic environments
> against the potential side effects of backward incompatibility".
> It seems that the WG has taken on an intractable problem.

Your conclusion does not follow. Yes, it is true that we're not sure
how willing some developer communities are to upgrade from Stringprep
(based on Unicode 3.2) to PRECIS (version-agile, currently Unicode
6.1). However, we know that some developer communities are in fact
willing to upgrade, and they have been more involved in the PRECIS WG.
Furthermore, in general applications don't have a choice about what
Unicode version is installed on the underlying system, so as time goes
by Stringprep will become more and more problematic. There was strong
agreement at the NEWPREP BoF to work on a common solution that all
Stringprep-using protocols could re-use. The approach taken in the
PRECIS framework specification is closely modelled on IDNA2008 and
follows the recommendations from RFC 4690. If you are going to
maintain that the PRECIS WG has taken on an intractable problem, then
I think you're also arguing that the IDNABIS WG took on an intractable
problem and that IDNA2008 failed to provide a viable solution to the
shortcomings of IDNA2003 and the Nameprep profile of Stringprep.

Peter

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


-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.18 (Darwin)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/

iEYEARECAAYFAlB0UAEACgkQNL8k5A2w/vwxggCfY5oXnRgP3UhOkZY3cu+1A/QX
gK4AoN5kxFk+5T19loPFsXup5YhzimWy
=LRQY
-----END PGP SIGNATURE-----

From sm@resistor.net  Tue Oct  9 13:28:41 2012
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D525121F8587; Tue,  9 Oct 2012 13:28:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.594
X-Spam-Level: 
X-Spam-Status: No, score=-102.594 tagged_above=-999 required=5 tests=[AWL=0.005, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id G45-gB4oJBt9; Tue,  9 Oct 2012 13:28:41 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 078A721F853E; Tue,  9 Oct 2012 13:28: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 q99KSPEV018461; Tue, 9 Oct 2012 13:28:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1349814512; bh=gk4POarhZqMgri8OaaE5niIm6KZtNsah0VPVgkB1grc=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=igMorl0HugmFHzRZiPSAz93Sw37hm+vgLuCrX3GxrgVzjiHjv8Ogz+N0wvXxDs+RH MTRhWi7ULWd0cmrTrbtYJCwhks8j53yUQzDDpebFjZ5tBN8YJquBe2hDR4+yPXbL0A A8LrWb+c7shEU8RpP6qpLqiY8ahc58nxin0DSzFc=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1349814512; i=@resistor.net; bh=gk4POarhZqMgri8OaaE5niIm6KZtNsah0VPVgkB1grc=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=3/VnMiNXJoZYwge2pIbqxiNRhW/FnhkLnppwK5ZVFNmhRiVYICFe9KJKBT08cxFLJ 0v5oYV3iuQoAh96HqcMpA3JZLpDEBMHi45cnnPennLkOJ47QW6cCZBVchhoaqgJYnj ctGKdMxsPEeEffWxVGs0LFVMvx+9AhR5B94QmtRc=
Message-Id: <6.2.5.6.2.20121009103254.0ac57808@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 09 Oct 2012 13:16:03 -0700
To: Peter Saint-Andre <stpeter@stpeter.im>
From: SM <sm@resistor.net>
Subject: Re: Last Call: <draft-ietf-precis-problem-statement-08.txt> (Stringprep Revision and PRECIS Problem Statement) to Informational RFC
In-Reply-To: <50745001.9080308@stpeter.im>
References: <20121009134458.18784.49285.idtracker@ietfa.amsl.com> <6.2.5.6.2.20121009070956.0ac31c90@resistor.net> <50745001.9080308@stpeter.im>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf@ietf.org, precis@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Oct 2012 20:28:42 -0000

Hi Peter,
At 09:25 09-10-2012, Peter Saint-Andre wrote:
>At the least, spelling out these acronyms on first use would be
>helpful (e.g., "Unicode Normalization Form KC").

Yes.

>Indeed, that appendix consists of notes copied from a wiki page that
>the PRECIS WG used to collect the information.

Ok.

>follows the recommendations from RFC 4690. If you are going to
>maintain that the PRECIS WG has taken on an intractable problem, then
>I think you're also arguing that the IDNABIS WG took on an intractable
>problem and that IDNA2008 failed to provide a viable solution to the
>shortcomings of IDNA2003 and the Nameprep profile of Stringprep.

My view is that the IDNABIS took on a difficult and 
politically-sensitive problem.  There's an open source implementation 
of the specification .  IDNABIS had the advantage of being related to 
domain names.  I'll take back the comment as you did a good write-up. :-)

Regards,
-sm 


From simon@josefsson.org  Wed Oct 10 15:14:04 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 70CD321F86B5; Wed, 10 Oct 2012 15:14:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.909
X-Spam-Level: 
X-Spam-Status: No, score=-99.909 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, HELO_MISMATCH_COM=0.553, HOST_EQ_STATICB=1.372, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sjthuRmgwYpi; Wed, 10 Oct 2012 15:14:04 -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 7858421F86BA; Wed, 10 Oct 2012 15:14:02 -0700 (PDT)
Received: from latte (host-95-193-1-90.mobileonline.telia.com [95.193.1.90]) (authenticated bits=0) by yxa-v.extundo.com (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id q9AMDObv021255 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Thu, 11 Oct 2012 00:13:34 +0200
From: Simon Josefsson <simon@josefsson.org>
To: "Cantor\, Scott" <cantor.2@osu.edu>
Subject: Re: Last Call: <draft-ietf-abfab-gss-eap-naming-05.txt> (Name Attributes for the GSS-API EAP mechanism) to Proposed Standard
References: <874nm7v92k.fsf@latte.josefsson.org> <BA63CEAE152A7742B854C678D949138339A567CD@CIO-KRC-D1MBX01.osuad.osu.edu>
OpenPGP: id=B565716F; url=http://josefsson.org/key.txt
X-Hashcash: 1:22:121010:cantor.2@osu.edu::mNWUgTgx06C4taci:1n52
X-Hashcash: 1:22:121010:abfab@ietf.org::U4vxsnPFNIPtaOvE:6zNH
X-Hashcash: 1:22:121010:ietf@ietf.org::NSULhYFmJXvyQLrl:K75X
Date: Thu, 11 Oct 2012 00:13:16 +0200
In-Reply-To: <BA63CEAE152A7742B854C678D949138339A567CD@CIO-KRC-D1MBX01.osuad.osu.edu> (Scott Cantor's message of "Sun, 7 Oct 2012 18:19:34 +0000")
Message-ID: <87wqyyf01v.fsf@latte.josefsson.org>
User-Agent: Gnus/5.130006 (Ma Gnus v0.6) Emacs/24.2 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
X-Virus-Scanned: clamav-milter 0.97.3 at yxa-v
X-Virus-Status: Clean
Cc: "abfab@ietf.org" <abfab@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Oct 2012 22:14:04 -0000

"Cantor, Scott" <cantor.2@osu.edu> writes:

> On 10/6/12 12:50 PM, "Simon Josefsson" <simon@josefsson.org> wrote:
>>
>>Thanks, now I understand better.  I would feel more comfortable if there
>>were a precise reference to what "well-formed serialization" means,
>>especially since there is a MUST here.  It ought to be possible to
>>determine algorithmically whether something conforms or not.  Sometimes
>>I get the impression that "well-formed" just refers to syntactical
>>correctness, whereas namespace considerations are more semantic.
>
> Actually namespaces extend the notion of syntax in XML, so they're not
> just semantic. When you parse while namespace-aware, there are normative
> rules for that grammar that include having namespaces declared properly. I
> think you probably want to reference the notion of "namespace
> well-formed", so my suggested text could be adjusted to include that
> instead of just "well-formed".
>
> http://www.w3.org/TR/2009/REC-xml-names-20091208/#Conformance

If the document use the term "namespace well-formed" and/or include the
reference that would resolve the issue for me.  Thanks for clarifying
this.

/Simon

From cheshire@apple.com  Wed Oct 10 15:53:36 2012
Return-Path: <cheshire@apple.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 29B1021F847A for <ietf@ietfa.amsl.com>; Wed, 10 Oct 2012 15:53:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XDd2fb0SL8hM for <ietf@ietfa.amsl.com>; Wed, 10 Oct 2012 15:53:33 -0700 (PDT)
Received: from mail-out.apple.com (mail-out.apple.com [17.151.62.51]) by ietfa.amsl.com (Postfix) with ESMTP id 753CE21F847B for <ietf@ietf.org>; Wed, 10 Oct 2012 15:53:33 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; CHARSET=US-ASCII
Received: from relay14.apple.com ([17.128.113.52]) by mail-out.apple.com (Oracle Communications Messaging Server 7u4-23.01 (7.0.4.23.0) 64bit (built Aug 10 2011)) with ESMTPS id <0MBP00H8Q8VS5TU2@mail-out.apple.com> for ietf@ietf.org; Wed, 10 Oct 2012 15:53:32 -0700 (PDT)
X-AuditID: 11807134-b7fb76d0000005cd-4f-5075fc6c67d8
Received: from jimbu (jimbu.apple.com [17.151.62.37]) (using TLS with cipher RC4-MD5 (RC4-MD5/128 bits)) (Client did not present a certificate)	by relay14.apple.com (Apple SCV relay) with SMTP id 65.07.01485.C6CF5705; Wed, 10 Oct 2012 15:53:32 -0700 (PDT)
Received: from [10.143.192.103] (unknown [217.39.5.120]) by jimbu.apple.com (Oracle Communications Messaging Server 7u4-24.01 (7.0.4.24.0) 64bit (built Nov 17 2011)) with ESMTPSA id <0MBP00G1A8X66UB0@jimbu.apple.com> for ietf@ietf.org; Wed, 10 Oct 2012 15:53:32 -0700 (PDT)
From: Stuart Cheshire <cheshire@apple.com>
Subject: New mailing list for DNS-SD/mDNS Extensions
Date: Wed, 10 Oct 2012 15:53:30 -0700
Message-id: <D15E357A-6213-4DFA-95B7-DA12010FB2EB@apple.com>
To: IETF Discussion <ietf@ietf.org>
X-Mailer: Apple Mail (2.1085)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmpiluLIzCtJLcpLzFFi42IRnG6nqpvzpzTA4HennsWzjfNZHBg9liz5 yRTAGMVlk5Kak1mWWqRvl8CVsXLNGeaCLzIVpz9sY21gPCvexcjBISFgInH1Tn4XIyeQKSZx 4d56ti5GLg4hgVYmicMP/jNBODOZJA5cP8kMUsUmoCXx4vMVNhCbGchev/M4E4StLfHk3QVW EFsYaOimFX/YQWwWAVWJXx92gPXyCthITD2+FKxGREBZ4tHU82wQcUOJJde3sENcISux885p lgmMvLOQrJiFZMUsJC0LGJlXMQoWpeYkVhqa6CUWFOSk6iXn525iBIVMQ6HJDsaDP/kPMQpw MCrx8L5YXRogxJpYVlyZe4hRgoNZSYQ38SFQiDclsbIqtSg/vqg0J7X4EKM0B4uSOK//8pIA IYH0xJLU7NTUgtQimCwTB6dUA2N5u+GNy3cfrrt6mq3eYIGpx5aDcQ9SCqbt+zNVhmkdz6Yd 4mdsxOtia5xzHOdM3tAhI3glwjCq7DNj10OTvd9fq0q1nUuO0+efN8lGd5NAs/Ov7JSVaqxK /jsaTeZ5c3+NfjXpcPzFCU3ioqHWc75MW/h5R+2Zlw21Lw+81dw1g9WXf/GCSlYlluKMREMt 5qLiRACCsMIgFQIAAA==
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Oct 2012 22:53:36 -0000

A new IETF mailing list has been created for discussions regarding DNS-SD/mDNS Extensions:

<https://www.ietf.org/mailman/listinfo/mdnsext>

This is in response to recent events in the industry and marketplace.

In August, EDUCAUSE delivered a petition to Apple asking for improvements to Bonjour (aka DNS-SD/mDNS) to allow discovery of services beyond the local link.

<http://www.networkworld.com/news/2012/080312-bonjour-petition-261390.html>
<https://www.change.org/petitions/from-educause-higher-ed-wireless-networking-admin-group>
<http://listserv.educause.edu/cgi-bin/wa.exe?A2=ind1208&L=WIRELESS-LAN&O=D&P=31656>

In principle DNS-SD can already be used in conjunction with conventional unicast DNS to enable wide-area service discovery, but in practice this capability is not widely used. This disconnect between customer needs and current practice suggests that we need to revisit how to solve this problem.

In response to this customer demand, Aerohive, Aruba, Cisco, and Xirrus have all recently announced "Bonjour gateway" products which allow service discovery beyond the local link. However, these were brought to market rapidly, and it's unclear whether they represent a desirable long-term direction for service discovery protocol development. Other companies are also reported to be developing their own "Bonjour gateway" products, not yet announced.

It would be beneficial for the end users, network operators, these vendors, and for the long-term health of the Internet to bring this work into the IETF where all interested parties can collaborate on it.

Proposed Scope of Work:

The MDNSEXT mailing list discussions will focus on service discovery solutions suitable for:

1. Enterprise networks
2. Academic/Educational/University networks
3. Multi-link home networks, such as that envisaged by HOMENET*
4. Mesh networks, such as SE2.0/ZigBee/6lowpan-style networks

* It is hoped that MDNSEXT can develop a solution that is suitable for all four network environments, including the HOMENET case. Of course the HOMENET WG is free to evalulate for itself whether it wishes to adopt the MDNSEXT solution, or develop something different.

Proposed Goals:

1. Enable discovery of services across multiple links.

2. Zero configuration operation possible, but not mandatory.
   - i.e. Zero configuration operation is supported by the protocols,
   but administrative control is also available on networks where that
   is desired.

3. Scalability, in terms of:
   - Network traffic
   - CPU and memory requirements on network entities
   - User interface (huge flat list is not user friendly)
   - Having a smooth continuum of operation from local link to site to
     global, rather than wildly different incompatible modes of
     operation at different network scales
   - Granularity of services available on a server (extend the notion of service?)

4. Suitable for both local (zero-config) and global (configured) use
   - i.e. Suitable out-of-the box defaults should enable zero-
     configuration use on many small- to medium-sized networks, while still
     allowing for administrative control in networks where that's desired.

5. Incremental deployability
   - Identify what changes to existing network elements will be
     required, and attempt to minimize those changes.
   - Don't break existing DNS-SD/mDNS functionality and devices

A BoF session is tentatively planned for 1520-1650 Tuesday 6th November 2012, subject there being enough interest to warrant moving ahead to that stage.

Stuart Cheshire


From chair@ietf.org  Wed Oct 10 20:41:28 2012
Return-Path: <chair@ietf.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B184821F861E for <ietf@ietfa.amsl.com>; Wed, 10 Oct 2012 20:41:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a2iIh9kjIQl3 for <ietf@ietfa.amsl.com>; Wed, 10 Oct 2012 20:41:28 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:123a::1:14]) by ietfa.amsl.com (Postfix) with ESMTP id DF02021F861F for <ietf@ietf.org>; Wed, 10 Oct 2012 20:41:27 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 7B3A412CDF5; Wed, 10 Oct 2012 20:41:22 -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 i6P-6QELerFJ; Wed, 10 Oct 2012 20:41:22 -0700 (PDT)
Received: from [172.17.197.177] (adsl-76-208-210-2.dsl.pltn13.sbcglobal.net [76.208.210.2]) by c8a.amsl.com (Postfix) with ESMTPSA id 1C4CD12CDF4; Wed, 10 Oct 2012 20:41:22 -0700 (PDT)
From: IETF Chair <chair@ietf.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Antitrust FAQ
Date: Wed, 10 Oct 2012 23:41:21 -0400
Message-Id: <AFB9BEA6-579B-4E26-A512-BE271D234F85@ietf.org>
To: IETF <ietf@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1085)
X-Mailer: Apple Mail (2.1085)
Cc: Jorge Contreras <contreraslegal@att.net>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Oct 2012 03:41:28 -0000

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

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

Thanks,
  Russ=

From dhc@dcrocker.net  Wed Oct 10 21:02:11 2012
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ED4AC1F0C55; Wed, 10 Oct 2012 21:02:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.449
X-Spam-Level: 
X-Spam-Status: No, score=-6.449 tagged_above=-999 required=5 tests=[AWL=0.150,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id btDQjjSz78yA; Wed, 10 Oct 2012 21:02:10 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 6CE751F041C; Wed, 10 Oct 2012 21:01:58 -0700 (PDT)
Received: from [192.168.1.6] (adsl-67-127-59-48.dsl.pltn13.pacbell.net [67.127.59.48]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q9B41vqF015162 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 10 Oct 2012 21:01:57 -0700
Message-ID: <507644AF.8040700@dcrocker.net>
Date: Wed, 10 Oct 2012 21:01:51 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121005 Thunderbird/16.0
MIME-Version: 1.0
To: IETF Chair <chair@ietf.org>
Subject: Re: Antitrust FAQ
References: <AFB9BEA6-579B-4E26-A512-BE271D234F85@ietf.org>
In-Reply-To: <AFB9BEA6-579B-4E26-A512-BE271D234F85@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Wed, 10 Oct 2012 21:01:57 -0700 (PDT)
Cc: IETF <ietf@ietf.org>, Jorge Contreras <contreraslegal@att.net>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Oct 2012 04:02:11 -0000

On 10/10/2012 8:41 PM, IETF Chair wrote:
> The IETF does not have a formal antitrust policy.  In fact, the ANTITRUST BOF concluded that a formal policy was not needed.  However, educational material is needed so that all IETF participants are aware of the the law.  The first draft of a FAQ to fill this need has been developed.  Please review the FAQ, and if you discover any issues raise them in response to this message.
>
> http://www.ietf.org/playground/antitrust-faq.html


In its current form, the plain language:

> 6) In order to avoid antitrust issues, what topics should not be discussed at IETF meeting?
>
> IETF participants should avoid any of the topics listed in questions 2 and 3, above.

directs two people who are at an IETF meeting to refrain from one having 
a sales discussion with the other in private.

Since this sort of discussion is probably quite common and entirely 
acceptable, it would help to have the stricture defined in terms of more 
specifically unacceptable context.

The current language merely specifies presence at an IETF meeting as the 
sole criterion.   The FAQ is necessarily quite basic, but since it is 
cast in a manner that assumes no prior knowledge of the topic by the 
reader, it's important to be a bit more detailed in specifying the 
relevant conditions under which the problematic exchanges should not occur.


d/

-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From johnl@iecc.com  Wed Oct 10 21:42:08 2012
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CB97C21F8516 for <ietf@ietfa.amsl.com>; Wed, 10 Oct 2012 21:42:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -111.664
X-Spam-Level: 
X-Spam-Status: No, score=-111.664 tagged_above=-999 required=5 tests=[AWL=0.535, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QMnJcHiMhhCI for <ietf@ietfa.amsl.com>; Wed, 10 Oct 2012 21:42:07 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id A857121F84FC for <ietf@ietf.org>; Wed, 10 Oct 2012 21:42:06 -0700 (PDT)
Received: (qmail 36842 invoked from network); 11 Oct 2012 04:42:03 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 11 Oct 2012 04:42:03 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=50764e1b.xn--hew.k1208; i=johnl@user.iecc.com; bh=NcsFbSdgc+fWbFpgu8/60LgtNeurWqV2VVrtKPQ1Uj0=; b=e3ZFaq74PjCPhmV1MHwy5zIzkg8NhaexQfskT8FBGnxkvhr6SOreXBP/Shg5tzPxkaZSZJfaFMk+3/1DVHZ4BespnIkNiEJrMQMIT8VWt2M9sa0LWlu2bkUxPO3eR1XgIoGQvpJdO6vLaw9iZtOLcN8LsOmRCIri+8m6hpB9B6Y=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=50764e1b.xn--hew.k1208; olt=johnl@user.iecc.com; bh=NcsFbSdgc+fWbFpgu8/60LgtNeurWqV2VVrtKPQ1Uj0=; b=XYM4P+NThWZ8+r4CKC4pWtpXTomjaBxsyOdMuy8Mc/prN97N+yd+CPaKpdhAa+LHbs81ONyu57uO77NYz+U4rB1/tjHrcsm4SMcyKwzCkiFNg2oTAUtuJt5HxSfSaoi/SbO/ypv6eqUP8WAI91wmosbMwTLLpvHsQwC6WHuGfBg=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 11 Oct 2012 04:41:41 -0000
Message-ID: <20121011044141.26679.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: Antitrust FAQ
In-Reply-To: <507644AF.8040700@dcrocker.net>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
Cc: dcrocker@bbiw.net
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Oct 2012 04:42:08 -0000

>directs two people who are at an IETF meeting to refrain from one having 
>a sales discussion with the other in private.

Um, could you identify which item under 2 or 3 would describe a
sales discussion?

R's,
John

From brian.e.carpenter@gmail.com  Thu Oct 11 00:34:38 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 A83C721F85F4; Thu, 11 Oct 2012 00:34:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.652
X-Spam-Level: 
X-Spam-Status: No, score=-101.652 tagged_above=-999 required=5 tests=[AWL=0.039, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Rg0rdp3X2oe6; Thu, 11 Oct 2012 00:34:37 -0700 (PDT)
Received: from mail-ea0-f172.google.com (mail-ea0-f172.google.com [209.85.215.172]) by ietfa.amsl.com (Postfix) with ESMTP id 6DA9E21F8585; Thu, 11 Oct 2012 00:34:37 -0700 (PDT)
Received: by mail-ea0-f172.google.com with SMTP id k13so259594eaa.31 for <multiple recipients>; Thu, 11 Oct 2012 00:34:36 -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=kUbNjKwcX2cLSa7rd33yaOrn8rYoD1lzQ17isniqpEE=; b=ZBM5NO5XSM5xIOqS8icXaJvcEi42J8RVU8R3WUCActLYU/bgAE1yQoVft7BR7iLJ+F dfdDybuxqegOPU9UmRkadClrx7It54XsXTehVwgvS1kGOzqXlqWdO4p2839YdUzPNuX0 t2T5B10Z3DsfgpYYcGBWRJrnmIk9FXHwWmn9qKbjIqVpTqesWx5Bb3qBUKhv2yA3PCWe k6OsOGlJanDmgoq2vK2JpCJHW+E+CE3Df4jiIaakcA0d03AjhLishRhR4G+OhWBN1LsH W75r/eOSwg9QiHCsj6kDAdiA1iHXpcZSl1lmxO4DPjQl1bPD+IZUbmTnoObckXVSqjOY Z2vA==
Received: by 10.14.198.133 with SMTP id v5mr50445een.7.1349940876616; Thu, 11 Oct 2012 00:34:36 -0700 (PDT)
Received: from [192.168.1.65] (host-2-102-217-30.as13285.net. [2.102.217.30]) by mx.google.com with ESMTPS id 7sm5463779eeg.5.2012.10.11.00.34.34 (version=SSLv3 cipher=OTHER); Thu, 11 Oct 2012 00:34:34 -0700 (PDT)
Message-ID: <5076768D.9020207@gmail.com>
Date: Thu, 11 Oct 2012 08:34:37 +0100
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: dcrocker@bbiw.net
Subject: Re: Antitrust FAQ
References: <AFB9BEA6-579B-4E26-A512-BE271D234F85@ietf.org> <507644AF.8040700@dcrocker.net>
In-Reply-To: <507644AF.8040700@dcrocker.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: IETF Chair <chair@ietf.org>, IETF <ietf@ietf.org>, Jorge Contreras <contreraslegal@att.net>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Oct 2012 07:34:38 -0000

On 11/10/2012 05:01, Dave Crocker wrote:
...
> The current language merely specifies presence at an IETF meeting as the
> sole criterion.   

It's behaviour at an IETF meeting that we are concerned about. Whether
it occurs in a session, in a corridor, in a private room, or electronically,
it would still violate anti-trust law afaik (ianal).

What is perhaps missing is a qualification like "except in private conversation
with fellow employees", in case that isn't obvious.

   Brian

From dhc@dcrocker.net  Thu Oct 11 05:34:42 2012
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 320C421F8620 for <ietf@ietfa.amsl.com>; Thu, 11 Oct 2012 05:34:42 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QhMnhS7mo9GT for <ietf@ietfa.amsl.com>; Thu, 11 Oct 2012 05:34:41 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 5E8D921F8616 for <ietf@ietf.org>; Thu, 11 Oct 2012 05:34:41 -0700 (PDT)
Received: from [192.168.1.6] (adsl-67-127-59-48.dsl.pltn13.pacbell.net [67.127.59.48]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q9BCYepv021998 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 11 Oct 2012 05:34:40 -0700
Message-ID: <5076BCDA.1090308@dcrocker.net>
Date: Thu, 11 Oct 2012 05:34:34 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121005 Thunderbird/16.0
MIME-Version: 1.0
To: John Levine <johnl@taugh.com>
Subject: Re: Antitrust FAQ
References: <20121011044141.26679.qmail@joyce.lan>
In-Reply-To: <20121011044141.26679.qmail@joyce.lan>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Thu, 11 Oct 2012 05:34:41 -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, 11 Oct 2012 12:34:42 -0000

On 10/10/2012 9:41 PM, John Levine wrote:
>> directs two people who are at an IETF meeting to refrain from one having
>> a sales discussion with the other in private.
>
> Um, could you identify which item under 2 or 3 would describe a
> sales discussion?


     Saleguy:  "Buy my product.  I'll sell it to you for US$xxx."

     Potential customer: "OK, but only if you guarantee me that that's 
your best price to any customer for the next 6 moths."

     Salesguy:  "OK."

By way of offering a single example, I'm only choosing the first bullet 
of #2.  Getting this sort of "price fixing" guarantee isn't actually all 
that unusual for critical sales contracts.

d/
-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From tglassey@earthlink.net  Thu Oct 11 05:47:31 2012
Return-Path: <tglassey@earthlink.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2FFD021F8743 for <ietf@ietfa.amsl.com>; Thu, 11 Oct 2012 05:47:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.624
X-Spam-Level: 
X-Spam-Status: No, score=-2.624 tagged_above=-999 required=5 tests=[AWL=-0.025, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TD6vhkOd9i8f for <ietf@ietfa.amsl.com>; Thu, 11 Oct 2012 05:47:30 -0700 (PDT)
Received: from elasmtp-masked.atl.sa.earthlink.net (elasmtp-masked.atl.sa.earthlink.net [209.86.89.68]) by ietfa.amsl.com (Postfix) with ESMTP id 4915C21F873B for <ietf@ietf.org>; Thu, 11 Oct 2012 05:47:30 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=tESo7th796CBxkOwmlMIsUURWD2aqJo5vucx0qQ+trwfjLtXpnvHUOscUmPrv9WU; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [67.180.133.21] (helo=[192.168.15.2]) by elasmtp-masked.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from <tglassey@earthlink.net>) id 1TMIAj-0000oV-Kd for ietf@ietf.org; Thu, 11 Oct 2012 08:47:29 -0400
Message-ID: <5076BFE0.7060000@earthlink.net>
Date: Thu, 11 Oct 2012 05:47:28 -0700
From: tglassey <tglassey@earthlink.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Antitrust FAQ
References: <AFB9BEA6-579B-4E26-A512-BE271D234F85@ietf.org>
In-Reply-To: <AFB9BEA6-579B-4E26-A512-BE271D234F85@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 01b7a7e171bdf5911aa676d7e74259b7b3291a7d08dfec7918f41e86298c480f954841e920229ade350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 67.180.133.21
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Oct 2012 12:47:31 -0000

On 10/10/2012 8:41 PM, IETF Chair wrote:
> The IETF does not have a formal antitrust policy.  In fact, the ANTITRUST BOF concluded that a formal policy was not needed.
Of course they did - the IETF and its membership seems to want autonomy 
and judicial immunity for its actions here... something so far from 
possible only the complexity and other issues - like government focusing 
on other issues like the economy but all of that is about to come to an end.
> Of course they did -  However, educational material is needed so that all IETF participants are aware of the the law.
More importantly declaring yourself innocent only works when you 
actually are... and that is far from the case here.
> The first draft of a FAQ to fill this need has been developed.  Please review the FAQ, and if you discover any issues raise them in response to this message.
Look its time for the IETF to admit several things - the first is that 
in its change from a trailing-edge to leading-edge GSO it needs formal 
IP controls in place because it is driving that envelope rather than 
working to create interoperable implementations from existing technologies.

In instances where IP is developed there are specific rights and 
responsibilities, especially for organizations with their own 
Transparency programs who are public entities.

Todd
> http://www.ietf.org/playground/antitrust-faq.html
>
> Thanks,
>    Russ
>
> -----
> No virus found in this message.
> Checked by AVG - www.avg.com
> Version: 2013.0.2677 / Virus Database: 2591/5822 - Release Date: 10/10/12
>
>
>


-- 
Regards TSG
"Ex-Cruce-Leo"

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


From johnl@taugh.com  Thu Oct 11 05:53:33 2012
Return-Path: <johnl@taugh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7B68F21F84D8 for <ietf@ietfa.amsl.com>; Thu, 11 Oct 2012 05:53:33 -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.078,  BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kLt2XD6izQCr for <ietf@ietfa.amsl.com>; Thu, 11 Oct 2012 05:53:32 -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 CD89C21F84A7 for <ietf@ietf.org>; Thu, 11 Oct 2012 05:53:31 -0700 (PDT)
Received: (qmail 35248 invoked from network); 11 Oct 2012 12:53: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=89aa.5076c143.k1210; bh=FDE50ei5SoCHHd/e+HX0FgfWggDthjhRr1mvdmoLIPA=; b=DV0fPjZl3597LGetSoSOFMrEgRkfA6gMfij7cPwqLe+mGE2ufrbewuSbCAp9C0SHyQR2dKAcs2ud7oZ/0RkRQTQI+Au33ggkgGGSmUVTQF7K6/iRjW1lcUY+Jr9quZmi0BCz3Qbel6bVi2KVIz6InhGZMw2UJtu6BzecDLwqaXQ=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:vbr-info:user-agent:cleverness; s=89aa.5076c143.k1210; bh=FDE50ei5SoCHHd/e+HX0FgfWggDthjhRr1mvdmoLIPA=; b=YWYnOoq1zqAaP4nIUaMH9vNa0dA2Ik5XVaGmTTYtOZ0H45gomeoO84BvnBQWox4HcSWVYn/VvZ9cgwUh+c8NlBM63sEPvQXG1giJQDmNsO+KnJg/f1CFB9G+CrEL4DgTkD2KiDjL/a6y/W1GNedGNFv8R5+pTNMIofVvy/rT44A=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Received: (ofmipd 127.0.0.1); 11 Oct 2012 12:53:01 -0000
Date: 11 Oct 2012 08:53:23 -0400
Message-ID: <alpine.BSF.2.00.1210110852270.46922@joyce.lan>
From: "John R Levine" <johnl@taugh.com>
To: dcrocker@bbiw.net
Subject: Re: Antitrust FAQ
In-Reply-To: <5076BCDA.1090308@dcrocker.net>
References: <20121011044141.26679.qmail@joyce.lan> <5076BCDA.1090308@dcrocker.net>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
Cleverness: None detected
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: John Levine <johnl@taugh.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Oct 2012 12:53:34 -0000

>    Saleguy:  "Buy my product.  I'll sell it to you for US$xxx."
>
>    Potential customer: "OK, but only if you guarantee me that that's your 
> best price to any customer for the next 6 moths."
>
>    Salesguy:  "OK."

It's only price fixing if it's a discussion between vendors, but I suppose 
I see how people who didn't understand the issues could misunderstand it.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
"I dropped the toothpaste", said Tom, crestfallenly.

From dcrocker@bbiw.net  Thu Oct 11 06:00:24 2012
Return-Path: <dcrocker@bbiw.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C848321F86DE for <ietf@ietfa.amsl.com>; Thu, 11 Oct 2012 06:00:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TOzKr0ZY8oq7 for <ietf@ietfa.amsl.com>; Thu, 11 Oct 2012 06:00:22 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 4CCF521F86C3 for <ietf@ietf.org>; Thu, 11 Oct 2012 06:00:22 -0700 (PDT)
Received: from [192.168.1.6] (adsl-67-127-59-48.dsl.pltn13.pacbell.net [67.127.59.48]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q9BD0LKv022544 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 11 Oct 2012 06:00:21 -0700
Message-ID: <5076C2DF.4080707@bbiw.net>
Date: Thu, 11 Oct 2012 06:00:15 -0700
From: Dave Crocker <dcrocker@bbiw.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121005 Thunderbird/16.0
MIME-Version: 1.0
To: John R Levine <johnl@taugh.com>
Subject: Re: Antitrust FAQ
References: <20121011044141.26679.qmail@joyce.lan> <5076BCDA.1090308@dcrocker.net> <alpine.BSF.2.00.1210110852270.46922@joyce.lan>
In-Reply-To: <alpine.BSF.2.00.1210110852270.46922@joyce.lan>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Thu, 11 Oct 2012 06:00:22 -0700 (PDT)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Oct 2012 13:00:24 -0000

On 10/11/2012 5:53 AM, John R Levine wrote:
> It's only price fixing if it's a discussion between vendors, but I
> suppose I see how people who didn't understand the issues could
> misunderstand it.


Exactly.  And this FAQ is, presumably, for people who do not already 
understand the issues.

Hence the request for more precision in specifying contextual constraints.

d/

-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From bob.hinden@gmail.com  Thu Oct 11 07:04:34 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 26C5F21F86C3 for <ietf@ietfa.amsl.com>; Thu, 11 Oct 2012 07:04:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.566
X-Spam-Level: 
X-Spam-Status: No, score=-103.566 tagged_above=-999 required=5 tests=[AWL=0.033, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id x4TsdVX1wSj8 for <ietf@ietfa.amsl.com>; Thu, 11 Oct 2012 07:04:33 -0700 (PDT)
Received: from mail-bk0-f44.google.com (mail-bk0-f44.google.com [209.85.214.44]) by ietfa.amsl.com (Postfix) with ESMTP id BE6D221F859B for <ietf@ietf.org>; Thu, 11 Oct 2012 07:04:32 -0700 (PDT)
Received: by mail-bk0-f44.google.com with SMTP id jc3so988986bkc.31 for <ietf@ietf.org>; Thu, 11 Oct 2012 07:04:31 -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=xzv/GVkx1GGJCZO2FuSlRkPoLnAXEXx7uvuSRuyF/vI=; b=vaClLQgfGzOr/UbsSZWTuDrI2fBj+/QyQ6ENvjVnVKupGl80lI/e571GHqnc8QDNlI EzsNp0oLpOv4DjVoot593VOeNMSn42D7GwALRZP75E4nW3IppmAKO+LFiHkQx5NnWj5H bYbknOHGwBltZ8Mwdg4f3uZpj1Vy/P/YJSDRZEyK28SUHUzxyao1wWfAJ32P+cj6vx6m Cmuq4qci5sgl/hxE8DFSzmEHQt5VatjJwlU1G5Ud8uY1VG8fwwVRQQo+X0eX6T81LW18 mOVQnl4h85REhFrgWHb7mczMbAlngNDcdqNOXeY4xCNpa0syLOz0FC1RsJwjx37weNpW UYnQ==
Received: by 10.204.11.141 with SMTP id t13mr361964bkt.65.1349964271775; Thu, 11 Oct 2012 07:04:31 -0700 (PDT)
Received: from [10.0.0.38] (c-24-130-151-138.hsd1.ca.comcast.net. [24.130.151.138]) by mx.google.com with ESMTPS id v14sm3802638bkv.10.2012.10.11.07.04.25 (version=SSLv3 cipher=OTHER); Thu, 11 Oct 2012 07:04:27 -0700 (PDT)
Subject: Re: New mailing list for DNS-SD/mDNS Extensions
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=us-ascii
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <D15E357A-6213-4DFA-95B7-DA12010FB2EB@apple.com>
Date: Thu, 11 Oct 2012 07:04:22 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <36380B37-2E0D-4B43-A747-1949E53BA4B3@gmail.com>
References: <D15E357A-6213-4DFA-95B7-DA12010FB2EB@apple.com>
To: Stuart Cheshire <cheshire@apple.com>
X-Mailer: Apple Mail (2.1283)
Cc: Bob Hinden <bob.hinden@gmail.com>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Oct 2012 14:04:34 -0000

Stuart,

Looks very interesting.  I will try to attend the BOF.

Bob

On Oct 10, 2012, at 3:53 PM, Stuart Cheshire wrote:

> A new IETF mailing list has been created for discussions regarding =
DNS-SD/mDNS Extensions:
>=20
> <https://www.ietf.org/mailman/listinfo/mdnsext>
>=20
> This is in response to recent events in the industry and marketplace.
>=20
> In August, EDUCAUSE delivered a petition to Apple asking for =
improvements to Bonjour (aka DNS-SD/mDNS) to allow discovery of services =
beyond the local link.
>=20
> =
<http://www.networkworld.com/news/2012/080312-bonjour-petition-261390.html=
>
> =
<https://www.change.org/petitions/from-educause-higher-ed-wireless-network=
ing-admin-group>
> =
<http://listserv.educause.edu/cgi-bin/wa.exe?A2=3Dind1208&L=3DWIRELESS-LAN=
&O=3DD&P=3D31656>
>=20
> In principle DNS-SD can already be used in conjunction with =
conventional unicast DNS to enable wide-area service discovery, but in =
practice this capability is not widely used. This disconnect between =
customer needs and current practice suggests that we need to revisit how =
to solve this problem.
>=20
> In response to this customer demand, Aerohive, Aruba, Cisco, and =
Xirrus have all recently announced "Bonjour gateway" products which =
allow service discovery beyond the local link. However, these were =
brought to market rapidly, and it's unclear whether they represent a =
desirable long-term direction for service discovery protocol =
development. Other companies are also reported to be developing their =
own "Bonjour gateway" products, not yet announced.
>=20
> It would be beneficial for the end users, network operators, these =
vendors, and for the long-term health of the Internet to bring this work =
into the IETF where all interested parties can collaborate on it.
>=20
> Proposed Scope of Work:
>=20
> The MDNSEXT mailing list discussions will focus on service discovery =
solutions suitable for:
>=20
> 1. Enterprise networks
> 2. Academic/Educational/University networks
> 3. Multi-link home networks, such as that envisaged by HOMENET*
> 4. Mesh networks, such as SE2.0/ZigBee/6lowpan-style networks
>=20
> * It is hoped that MDNSEXT can develop a solution that is suitable for =
all four network environments, including the HOMENET case. Of course the =
HOMENET WG is free to evalulate for itself whether it wishes to adopt =
the MDNSEXT solution, or develop something different.
>=20
> Proposed Goals:
>=20
> 1. Enable discovery of services across multiple links.
>=20
> 2. Zero configuration operation possible, but not mandatory.
>   - i.e. Zero configuration operation is supported by the protocols,
>   but administrative control is also available on networks where that
>   is desired.
>=20
> 3. Scalability, in terms of:
>   - Network traffic
>   - CPU and memory requirements on network entities
>   - User interface (huge flat list is not user friendly)
>   - Having a smooth continuum of operation from local link to site to
>     global, rather than wildly different incompatible modes of
>     operation at different network scales
>   - Granularity of services available on a server (extend the notion =
of service?)
>=20
> 4. Suitable for both local (zero-config) and global (configured) use
>   - i.e. Suitable out-of-the box defaults should enable zero-
>     configuration use on many small- to medium-sized networks, while =
still
>     allowing for administrative control in networks where that's =
desired.
>=20
> 5. Incremental deployability
>   - Identify what changes to existing network elements will be
>     required, and attempt to minimize those changes.
>   - Don't break existing DNS-SD/mDNS functionality and devices
>=20
> A BoF session is tentatively planned for 1520-1650 Tuesday 6th =
November 2012, subject there being enough interest to warrant moving =
ahead to that stage.
>=20
> Stuart Cheshire
>=20


From tglassey@earthlink.net  Thu Oct 11 07:10:08 2012
Return-Path: <tglassey@earthlink.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5F77F21F867C for <ietf@ietfa.amsl.com>; Thu, 11 Oct 2012 07:10:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.623
X-Spam-Level: 
X-Spam-Status: No, score=-2.623 tagged_above=-999 required=5 tests=[AWL=-0.024, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RMV0qFC8wudW for <ietf@ietfa.amsl.com>; Thu, 11 Oct 2012 07:10:07 -0700 (PDT)
Received: from elasmtp-spurfowl.atl.sa.earthlink.net (elasmtp-spurfowl.atl.sa.earthlink.net [209.86.89.66]) by ietfa.amsl.com (Postfix) with ESMTP id 49B6521F872A for <ietf@ietf.org>; Thu, 11 Oct 2012 07:09:59 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=NFUlLZbtV4pEKrXiUqI56F1b4K4suG7ixfbJLy52Gg3b/ziEfPpeA/6UoFqbWEvk; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [67.180.133.21] (helo=[192.168.15.2]) by elasmtp-spurfowl.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from <tglassey@earthlink.net>) id 1TMJSY-0007M6-Ms for ietf@ietf.org; Thu, 11 Oct 2012 10:09:58 -0400
Message-ID: <5076D335.4030801@earthlink.net>
Date: Thu, 11 Oct 2012 07:09:57 -0700
From: tglassey <tglassey@earthlink.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Antitrust FAQ
References: <AFB9BEA6-579B-4E26-A512-BE271D234F85@ietf.org> <507644AF.8040700@dcrocker.net> <5076768D.9020207@gmail.com>
In-Reply-To: <5076768D.9020207@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 01b7a7e171bdf5911aa676d7e74259b7b3291a7d08dfec79f5912a11e9f3ccc15bbab66c767fd371350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 67.180.133.21
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Oct 2012 14:10:08 -0000

On 10/11/2012 12:34 AM, Brian E Carpenter wrote:
> On 11/10/2012 05:01, Dave Crocker wrote:
> ...
>> The current language merely specifies presence at an IETF meeting as the
>> sole criterion.
> It's behaviour at an IETF meeting that we are concerned about. Whether
> it occurs in a session, in a corridor, in a private room, or electronically,
> it would still violate anti-trust law afaik (ianal).
>
> What is perhaps missing is a qualification like "except in private conversation
> with fellow employees", in case that isn't obvious.
>
>     Brian
And that would mean "any act or communication in furtherance of an IETF 
initiative". The problem you have here is the definition of a conspiracy 
under US Law - the left hand doesnt have to be in direct communication 
with the right hand here to be a quantifiable conspiracy.

http://www.justice.gov/usao/eousa/foia_reading_room/usam/title9/crm00923.htm

The fun part is that the obvious use of the US Copyright act to create a 
monopoly on the IETF IP brand is clearly the first step in documenting 
the "conspiracy" here. The issue then is one of disclosure to prevent 
antitrust - meaning everyone needs to fess up with regard to who's 
power-of-attorney as required by the BCPs they represent here before the 
IETF.

Todd  Glassey
>
> -----
> No virus found in this message.
> Checked by AVG - www.avg.com
> Version: 2013.0.2677 / Virus Database: 2591/5823 - Release Date: 10/10/12
>
>


-- 
Regards TSG
"Ex-Cruce-Leo"

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


From tglassey@earthlink.net  Thu Oct 11 08:20:35 2012
Return-Path: <tglassey@earthlink.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 528D621F86E0 for <ietf@ietfa.amsl.com>; Thu, 11 Oct 2012 08:20:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.622
X-Spam-Level: 
X-Spam-Status: No, score=-2.622 tagged_above=-999 required=5 tests=[AWL=-0.023, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ob+LV2tVJXB7 for <ietf@ietfa.amsl.com>; Thu, 11 Oct 2012 08:20:34 -0700 (PDT)
Received: from elasmtp-masked.atl.sa.earthlink.net (elasmtp-masked.atl.sa.earthlink.net [209.86.89.68]) by ietfa.amsl.com (Postfix) with ESMTP id 8B0D921F86C6 for <ietf@ietf.org>; Thu, 11 Oct 2012 08:20:34 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=aLKcW5avBpzIYuN/YSfc3bRXupH3NHYt7PinGio9rAZoXcOY6pLmU48XQ2d8OqEp; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [67.180.133.21] (helo=[192.168.15.2]) by elasmtp-masked.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from <tglassey@earthlink.net>) id 1TMKYr-0001mS-W6 for ietf@ietf.org; Thu, 11 Oct 2012 11:20:34 -0400
Message-ID: <5076E3C0.5050205@earthlink.net>
Date: Thu, 11 Oct 2012 08:20:32 -0700
From: tglassey <tglassey@earthlink.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Antitrust FAQ - Sherman Act
References: <20121011044141.26679.qmail@joyce.lan> <5076BCDA.1090308@dcrocker.net> <alpine.BSF.2.00.1210110852270.46922@joyce.lan> <5076C2DF.4080707@bbiw.net>
In-Reply-To: <5076C2DF.4080707@bbiw.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 01b7a7e171bdf5911aa676d7e74259b7b3291a7d08dfec79c8714c8d6f989c6e08386bf38b2a7867350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 67.180.133.21
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Oct 2012 15:20:35 -0000

On 10/11/2012 6:00 AM, Dave Crocker wrote:
>
> On 10/11/2012 5:53 AM, John R Levine wrote:
>> It's only price fixing if it's a discussion between vendors, but I
>> suppose I see how people who didn't understand the issues could
>> misunderstand it.
>
>
> Exactly.  And this FAQ is, presumably, for people who do not already 
> understand the issues.
>
> Hence the request for more precision in specifying contextual 
> constraints.
So the Sherman act in the US prevents any corporate entity from 
monopolizing the power of the US Government. Since the power of the IETF 
is tied to the ISOC and the ICANN/IANA operating practices which the 
IETF is the source of controls - the sole source of controls for... this 
is an issue. The NTIA MOU is the hanger so to speak...

Which means that the use of the IETF - an arguably Government Sponsored 
entity - since there are many Governments including the US with 
representatives in the IETF, this clearly becomes an antitrust issue 
with regard to the Sherman Act.

http://en.wikipedia.org/wiki/Sherman_Antitrust_Act

Todd//
>
> d/
>


-- 
Regards TSG
"Ex-Cruce-Leo"

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


From ted.ietf@gmail.com  Thu Oct 11 09:39:41 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 399BC21F8528; Thu, 11 Oct 2012 09:39:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.506
X-Spam-Level: 
X-Spam-Status: No, score=-3.506 tagged_above=-999 required=5 tests=[AWL=0.093,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H1kh5FuISnSk; Thu, 11 Oct 2012 09:39:40 -0700 (PDT)
Received: from mail-vc0-f172.google.com (mail-vc0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 5329A21F8525; Thu, 11 Oct 2012 09:39:40 -0700 (PDT)
Received: by mail-vc0-f172.google.com with SMTP id fl11so2710545vcb.31 for <multiple recipients>; Thu, 11 Oct 2012 09:39:39 -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=z7jM12Jd7YDYovqswpTNsw4R6UMyiJTcJOHuw+GycCc=; b=F0cY3DvIPj172mOn0FfxKtf7mLgEkyK1nUyFUr8K57b6rRB69/juKlWhdMRy2nNfpd Sobq/CwRUUbhJxO4tzDkS8bAEOmnQApfcN64mfwY1eZEb1vO6U2gJU/+VIDN2ENvr6uY 38h2NqxSckfrtdj3/E8SUn9j/jnCIdP9J9fhI61Fs7qbDue71KHMqPtrKogGxTGvOE2b JI95prDPQ9RJf5fOgyDzjPh/bfqoxhYdHuxio+i7kQ1CUjoHIl0E2d7aOQbu7vo5AjEq p/UluielPmmDAg8FffjqMGq6AlPbkQH8phHnzfCp/94oe0evGg6ZgaykkdiYO+azENoS lCEw==
MIME-Version: 1.0
Received: by 10.52.37.103 with SMTP id x7mr670421vdj.61.1349973579740; Thu, 11 Oct 2012 09:39:39 -0700 (PDT)
Received: by 10.58.245.39 with HTTP; Thu, 11 Oct 2012 09:39:39 -0700 (PDT)
In-Reply-To: <AFB9BEA6-579B-4E26-A512-BE271D234F85@ietf.org>
References: <AFB9BEA6-579B-4E26-A512-BE271D234F85@ietf.org>
Date: Thu, 11 Oct 2012 09:39:39 -0700
Message-ID: <CA+9kkMBaME6DgeLNQm3-YGhpAa+SDKJpbMuUb+odxYyCJidJDQ@mail.gmail.com>
Subject: Re: Antitrust FAQ
From: Ted Hardie <ted.ietf@gmail.com>
To: IETF Chair <chair@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: IETF <ietf@ietf.org>, Jorge Contreras <contreraslegal@att.net>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Oct 2012 16:39:41 -0000

On Wed, Oct 10, 2012 at 8:41 PM, IETF Chair <chair@ietf.org> wrote:
> The IETF does not have a formal antitrust policy.  In fact, the ANTITRUST=
 BOF concluded that a formal policy was not needed.  However, educational m=
aterial is needed so that all IETF participants are aware of the the law.  =
The first draft of a FAQ to fill this need has been developed.  Please revi=
ew the FAQ, and if you discover any issues raise them in response to this m=
essage.
>
> http://www.ietf.org/playground/antitrust-faq.html
>
> Thanks,
>   Russ

Hi Russ,

The language in section 4 of the proposed FAQ seems to me a bit
convoluted, which may make it difficult to understand.  I've suggested
a potential re-write,  but I think the main feedback is that this
needs work.

Current text:

"4) Why is the IETF concerned with antitrust law?

The IETF work on standards so that implementations (whether
traditional products, or open-source) of those standards from
different sources interoperate well. That means that by our very
nature, we bring together people, some of whom are competitors in
industry, to communicate about work they do, and that increases the
possibility that some of those communications might run afoul of
antitrust law. Any claim that the IETF takes part in anticompetitive
practices could be detrimental to the IETF Standards Process and
ultimately the Internet. To that end, this document is to remind all
IETF participants of their responsibilities regarding antitrust law so
that they can avoid engaging in anticompetitive behavior in
conjunction with their IETF activities."

Proposed text:

"4) Why should IETF participants be aware of antitrust laws?

The IETF brings together individuals whose corporate sponsors may be
competitors in specific markets.  Participants' efforts are focused on
creating specifications that allow different implementations to
interoperate, which enables a robust, competitive environment.
Because potential competitors are gathered, though, there can be
concerns that some discussions held in IETF contexts may be
inappropriate.  Such claims would be damaging to individuals, their
sponsors, and to the IETF process.  The IETF reminds all IETF
participants of their responsibilities so that they can avoid
discussions which might be understood to be collusion or otherwise
anti-competitive."

regards,

Ted Hardie

From dwm@xpasc.com  Thu Oct 11 13:11:22 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 860DD21F8596 for <ietf@ietfa.amsl.com>; Thu, 11 Oct 2012 13:11: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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zNMmyWqhSWzs for <ietf@ietfa.amsl.com>; Thu, 11 Oct 2012 13:11:21 -0700 (PDT)
Received: from c2w3p-2.abacamail.com (c2w3p-2.abacamail.com [209.133.53.32]) by ietfa.amsl.com (Postfix) with ESMTP id B9E5C21F8594 for <ietf@ietf.org>; Thu, 11 Oct 2012 13:11:21 -0700 (PDT)
Received: from xpasc.com (unknown [68.164.244.188]) by c2w3p-2.abacamail.com (Postfix) with ESMTP id 180A140520 for <ietf@ietf.org>; Thu, 11 Oct 2012 20:11:21 +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 q9BKBKHk029169 for <ietf@ietf.org>; Thu, 11 Oct 2012 13:11:20 -0700
Date: Thu, 11 Oct 2012 13:11:20 -0700 (PDT)
From: David Morris <dwm@xpasc.com>
To: ietf@ietf.org
Subject: Re: Antitrust FAQ
In-Reply-To: <5076BCDA.1090308@dcrocker.net>
Message-ID: <alpine.LRH.2.01.1210111305590.27778@egate.xpasc.com>
References: <20121011044141.26679.qmail@joyce.lan> <5076BCDA.1090308@dcrocker.net>
User-Agent: Alpine 2.01 (LRH 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Milter-Version: master.1+13-gbab1945
X-AV-Type: clean
X-AV-Accuracy: exact
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: ietf@ietf.org
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Oct 2012 20:11:22 -0000

On Thu, 11 Oct 2012, Dave Crocker wrote:

> 
> On 10/10/2012 9:41 PM, John Levine wrote:
> > > directs two people who are at an IETF meeting to refrain from one having
> > > a sales discussion with the other in private.
> > 
> > Um, could you identify which item under 2 or 3 would describe a
> > sales discussion?
> 
> 
>     Saleguy:  "Buy my product.  I'll sell it to you for US$xxx."
> 
>     Potential customer: "OK, but only if you guarantee me that that's your
> best price to any customer for the next 6 moths."
> 
>     Salesguy:  "OK."
> 
> By way of offering a single example, I'm only choosing the first bullet of #2.
> Getting this sort of "price fixing" guarantee isn't actually all that unusual
> for critical sales contracts.

What would be unusual would be to not have an escape clause that allowed 
the sales guy to offer a lower price to someone else if he also refunded
the different to the customer.

And it isn't an anti-trust violation ... an anti trust violation is where
two competators agree to maintain pricing and not compete, at least on
price.


From hartmans@mit.edu  Thu Oct 11 13:32:06 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 36EC221F862B; Thu, 11 Oct 2012 13:32:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -96.72
X-Spam-Level: 
X-Spam-Status: No, score=-96.72 tagged_above=-999 required=5 tests=[AWL=-1.008, BAYES_00=-2.599, FH_HELO_EQ_D_D_D_D=1.597, FH_HOST_EQ_D_D_D_D=0.765, FM_DDDD_TIMES_2=1.999, HELO_DYNAMIC_IPADDR=2.426, RDNS_DYNAMIC=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FbTqP-PsRvJh; Thu, 11 Oct 2012 13:32:05 -0700 (PDT)
Received: from ec2-23-21-227-93.compute-1.amazonaws.com (ec2-23-21-227-93.compute-1.amazonaws.com [23.21.227.93]) by ietfa.amsl.com (Postfix) with ESMTP id C0FC121F8628; Thu, 11 Oct 2012 13:32:05 -0700 (PDT)
Received: from carter-zimmerman.suchdamage.org (c-98-217-126-210.hsd1.ma.comcast.net [98.217.126.210]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.suchdamage.org (Postfix) with ESMTPS id 7B36E2021E; Thu, 11 Oct 2012 16:31:50 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 9734E4AD5; Thu, 11 Oct 2012 16:32:03 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: IETF Chair <chair@ietf.org>
Subject: Re: Antitrust FAQ
References: <AFB9BEA6-579B-4E26-A512-BE271D234F85@ietf.org>
Date: Thu, 11 Oct 2012 16:32:03 -0400
In-Reply-To: <AFB9BEA6-579B-4E26-A512-BE271D234F85@ietf.org> (IETF Chair's message of "Wed, 10 Oct 2012 23:41:21 -0400")
Message-ID: <tslobk8oim4.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>, Jorge Contreras <contreraslegal@att.net>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Oct 2012 20:32:06 -0000

Hi, Russ.

In question 2,
I don't understand what several terms are and whether they have any
relation to the standards process.

The one most confusing is "agreements to restrict output"

Also, more detail on what an anticompetitive reason to restrict someone
from the standards process could help.

I'd also expect to see:

7) What should be considered when evaluating the composition of design
teams to avoid antitrust concerns?

8) What responsibilities do chairs have in avoiding antitrust concerns
within their WGs.


9) What should chairs, editors or other participants do if they have
concerns about something they observe in the IETF process?


These are not hypothetical concerns.  In all three cases I've had the
question with regard to specific events and not been sure what to do.

From narten@us.ibm.com  Thu Oct 11 21:53:12 2012
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3250D21F8453 for <ietf@ietfa.amsl.com>; Thu, 11 Oct 2012 21:53:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.369
X-Spam-Level: 
X-Spam-Status: No, score=-110.369 tagged_above=-999 required=5 tests=[AWL=0.230, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id h7ELeVMRoNO7 for <ietf@ietfa.amsl.com>; Thu, 11 Oct 2012 21:53:11 -0700 (PDT)
Received: from e38.co.us.ibm.com (e38.co.us.ibm.com [32.97.110.159]) by ietfa.amsl.com (Postfix) with ESMTP id 16F2521F8458 for <ietf@ietf.org>; Thu, 11 Oct 2012 21:53:10 -0700 (PDT)
Received: from /spool/local by e38.co.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <ietf@ietf.org> from <narten@us.ibm.com>; Thu, 11 Oct 2012 22:53:10 -0600
Received: from d03dlp03.boulder.ibm.com (9.17.202.179) by e38.co.us.ibm.com (192.168.1.138) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Thu, 11 Oct 2012 22:53:07 -0600
Received: from d03relay05.boulder.ibm.com (d03relay05.boulder.ibm.com [9.17.195.107]) by d03dlp03.boulder.ibm.com (Postfix) with ESMTP id 3F4D119D803C for <ietf@ietf.org>; Thu, 11 Oct 2012 22:53:07 -0600 (MDT)
Received: from d03av04.boulder.ibm.com (d03av04.boulder.ibm.com [9.17.195.170]) by d03relay05.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id q9C4r54N268086 for <ietf@ietf.org>; Thu, 11 Oct 2012 22:53:05 -0600
Received: from d03av04.boulder.ibm.com (loopback [127.0.0.1]) by d03av04.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id q9C4r59V009254 for <ietf@ietf.org>; Thu, 11 Oct 2012 22:53:05 -0600
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.44.115.148]) by d03av04.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id q9C4r3lv009192 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Thu, 11 Oct 2012 22:53:04 -0600
Received: from rotala.raleigh.ibm.com (localhost.localdomain [127.0.0.1]) by rotala.raleigh.ibm.com (8.14.5/8.12.5) with ESMTP id q9C4r3fQ021872 for <ietf@ietf.org>; Fri, 12 Oct 2012 00:53:03 -0400
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.5/8.14.5/Submit) id q9C4r2Tv021827 for ietf@ietf.org; Fri, 12 Oct 2012 00:53:03 -0400
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201210120453.q9C4r2Tv021827@rotala.raleigh.ibm.com>
Date: Fri, 12 Oct 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: 12101204-5518-0000-0000-000008640160
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Oct 2012 04:53:12 -0000

Total of 52 messages in the last 7 days.
 
script run at: Fri Oct 12 00:53:02 EDT 2012
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
  9.62% |    5 |  8.32% |    35545 | tglassey@earthlink.net
  5.77% |    3 |  8.83% |    37719 | jasnell@gmail.com
  5.77% |    3 |  5.16% |    22062 | martin.thomson@gmail.com
  5.77% |    3 |  4.76% |    20356 | joao@bondis.org
  5.77% |    3 |  4.48% |    19133 | sm@resistor.net
  3.85% |    2 |  6.06% |    25880 | david.black@emc.com
  3.85% |    2 |  3.73% |    15931 | cantor.2@osu.edu
  1.92% |    1 |  5.57% |    23774 | ron.even.tlv@gmail.com
  3.85% |    2 |  3.06% |    13083 | simon@josefsson.org
  3.85% |    2 |  2.74% |    11704 | dhc@dcrocker.net
  3.85% |    2 |  2.65% |    11320 | johnl@taugh.com
  1.92% |    1 |  4.57% |    19512 | andrew.g.malis@verizon.com
  3.85% |    2 |  2.41% |    10307 | jnc@mercury.lcs.mit.edu
  1.92% |    1 |  3.28% |    14032 | julian.reschke@gmx.de
  1.92% |    1 |  3.05% |    13038 | glenzorn@gmail.com
  1.92% |    1 |  2.80% |    11970 | lars@netapp.com
  1.92% |    1 |  2.51% |    10742 | jgs@juniper.net
  1.92% |    1 |  2.17% |     9288 | bob.hinden@gmail.com
  1.92% |    1 |  2.15% |     9175 | cheshire@apple.com
  1.92% |    1 |  1.89% |     8078 | stpeter@stpeter.im
  1.92% |    1 |  1.76% |     7529 | ted.ietf@gmail.com
  1.92% |    1 |  1.75% |     7489 | barryleiba@computer.org
  1.92% |    1 |  1.70% |     7283 | john-ietf@jck.com
  1.92% |    1 |  1.63% |     6953 | narten@us.ibm.com
  1.92% |    1 |  1.45% |     6185 | fernando@gont.com.ar
  1.92% |    1 |  1.39% |     5920 | brian.e.carpenter@gmail.com
  1.92% |    1 |  1.33% |     5662 | dwm@xpasc.com
  1.92% |    1 |  1.31% |     5577 | hartmans-ietf@mit.edu
  1.92% |    1 |  1.31% |     5575 | mohta@necom830.hpcl.titech.ac.jp
  1.92% |    1 |  1.27% |     5423 | hartmans@painless-security.com
  1.92% |    1 |  1.24% |     5288 | sm+ietf@elandsys.com
  1.92% |    1 |  1.24% |     5282 | dcrocker@bbiw.net
  1.92% |    1 |  1.22% |     5218 | chair@ietf.org
  1.92% |    1 |  1.21% |     5169 | rbarnes@bbn.com
--------+------+--------+----------+------------------------
100.00% |   52 |100.00% |   427202 | Total


From abdussalambaryun@gmail.com  Fri Oct 12 02:18:43 2012
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B4E1321F8438; Fri, 12 Oct 2012 02:18:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.529
X-Spam-Level: 
X-Spam-Status: No, score=-3.529 tagged_above=-999 required=5 tests=[AWL=0.070,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U6v1c7BIBJTt; Fri, 12 Oct 2012 02:18:43 -0700 (PDT)
Received: from mail-vc0-f172.google.com (mail-vc0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id C4F6E21F8425; Fri, 12 Oct 2012 02:18:42 -0700 (PDT)
Received: by mail-vc0-f172.google.com with SMTP id fl11so3604659vcb.31 for <multiple recipients>; Fri, 12 Oct 2012 02:18: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; bh=Ol9oyGtd/xLv/5tBgAadVRckVmkSJmsPJCzxlkvnsaw=; b=hyTRW9OlQbZFQRKtxQZLfwbXj2KasMpVvjI+CNUJUGqrqSdS3Yv2YB7R+UdBz93lOq mDpmfpUEWYxj8bPuepxfhyLOTLmLVlPJ0xy/+60LJEfQAgNEG0+kXEV8psgpbWDxU+e8 zltR63iFuQ8rtjRRPr+esZSePHmKhUf+eG5gQbG/pfPr3bvA8e+KZeIgFvdKzbD65IOi i5atDv8mDpiAoaGs9SkWx9TuI2OTfzi7E7eTpyGkmVy+PrfU8uw8j5lQ6jqp52OQoN4b RGdURhzOInPssntEdyNa56hsk3QIYccydu43SvjsNqMmASHtTfnmqEwaCEMFrVF3ThDV nYsA==
MIME-Version: 1.0
Received: by 10.58.218.97 with SMTP id pf1mr2307072vec.20.1350033521973; Fri, 12 Oct 2012 02:18:41 -0700 (PDT)
Received: by 10.220.204.9 with HTTP; Fri, 12 Oct 2012 02:18:41 -0700 (PDT)
In-Reply-To: <CADnDZ8_OGGWVDAFiBUMDO5WA6xueJZcHtdqj8hB6jqV-d4u6dA@mail.gmail.com>
References: <CADnDZ8_OGGWVDAFiBUMDO5WA6xueJZcHtdqj8hB6jqV-d4u6dA@mail.gmail.com>
Date: Fri, 12 Oct 2012 11:18:41 +0200
Message-ID: <CADnDZ8-dBuqcY4gH0K7ZMrVTkW+zBP_YHyPNFhuGDFs4nnETig@mail.gmail.com>
Subject: Re: Antitrust FAQ
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: ietf <ietf@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Cc: chair@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Oct 2012 09:18:43 -0000

I support the reminder, however, would like to add considerations,
suggestions and my questions.
---------------------------------------------------------------------------------------------------------

I see that it only includes information related to antitrust

The *reminder-document* should be for both Companies (i.e.
managers/owners/share-holders) and IETF-participants, so we including
companies as well, there should not be any antitrust agreement against
a participant individual as well (i.e. All IETF input and output
decisions are from individual participants not companies).

AB>Amend> Antitrust law prohibits agreements that unreasonably
restrain trust, and business.

The word *trade* is more for companies, but *business* will include
participant individuals. The main issue is *trust* so should be in the
document.

AB>suggest> Q2:  *Competitive information includes:* I recommend to
put some exclude examples to clarify the answer. The last line in the
answer is not enough.

AB> My Questions: (as I still don't understand clearly from the document):
Qa) Is an information of technology advantages over another
competitive one prohibited?

Qb) Is an information of a standard advantages over another standard prohibited?
(e.g. many companies may hide technology analysis results from the market)

Qc) Do we as IETFers separate the product technology from the business
provider or we mix them? or does the customer/market-channels mix
between the two? I think we (i.e. participating in volunteering
standardising for the Internet Community) do that perfectly, maybe
companies (i.e. market profit makers, owner of percentage of market
share) don't understand that, and they MAY need reminder too.

Finally IMHO, The Qa and Qb questions are not understood from the
Antitrust FAQ doc. Participants on discussion lists always like to
argue/find-out technical advantages and disadvantages, and make clear
*HOW / WHEN* to use/not-use such technology/standard. I suggest to
include some information explaining Qc.

AB

>
> The IETF does not have a formal antitrust policy.  In fact, the
> ANTITRUST BOF concluded that a formal policy was not needed.  However,
> educational material is needed so that all IETF participants are aware
> of the the law.  The first draft of a FAQ to fill this need has been
> developed.  Please review the FAQ, and if you discover any issues
> raise them in response to this message.
>
> http://www.ietf.org/playground/antitrust-faq.html
>
> Thanks,
>   Russ
>

From hartmans@mit.edu  Fri Oct 12 03:52: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 22AB321F8562; Fri, 12 Oct 2012 03:52:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -95.727
X-Spam-Level: 
X-Spam-Status: No, score=-95.727 tagged_above=-999 required=5 tests=[AWL=-1.874, BAYES_20=-0.74, FH_HELO_EQ_D_D_D_D=1.597, FH_HOST_EQ_D_D_D_D=0.765, FM_DDDD_TIMES_2=1.999, HELO_DYNAMIC_IPADDR=2.426, RDNS_DYNAMIC=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dGkP7tPAVqcY; Fri, 12 Oct 2012 03:52:34 -0700 (PDT)
Received: from ec2-23-21-227-93.compute-1.amazonaws.com (ec2-23-21-227-93.compute-1.amazonaws.com [23.21.227.93]) by ietfa.amsl.com (Postfix) with ESMTP id CB83121F8510; Fri, 12 Oct 2012 03:52:25 -0700 (PDT)
Received: from carter-zimmerman.suchdamage.org (c-98-217-126-210.hsd1.ma.comcast.net [98.217.126.210]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.suchdamage.org (Postfix) with ESMTPS id 246DC2027D; Fri, 12 Oct 2012 06:42:43 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 051174AD5; Fri, 12 Oct 2012 06:42:55 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: Jorge Contreras <contreraslegal@att.net>
Subject: Re: Antitrust FAQ
References: <CC9CC662.B626%contreraslegal@att.net>
Date: Fri, 12 Oct 2012 06:42:54 -0400
In-Reply-To: <CC9CC662.B626%contreraslegal@att.net> (Jorge Contreras's message of "Thu, 11 Oct 2012 19:00:11 -0500")
Message-ID: <tslhaq0j7ip.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 Chair <chair@ietf.org>, Sam Hartman <hartmans-ietf@mit.edu>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Oct 2012 10:52:35 -0000

Thanks.  These are great responses, and I believe the FAQ would be
significantly improved by working these in.

From chair@ietf.org  Fri Oct 12 08:43:12 2012
Return-Path: <chair@ietf.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E3EC521F8699 for <ietf@ietfa.amsl.com>; Fri, 12 Oct 2012 08:43:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0zCrKIMe4H0v for <ietf@ietfa.amsl.com>; Fri, 12 Oct 2012 08:43:12 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:123a::1:14]) by ietfa.amsl.com (Postfix) with ESMTP id 4F7A921F8697 for <ietf@ietf.org>; Fri, 12 Oct 2012 08:43:12 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id BFB9512D02B for <ietf@ietf.org>; Fri, 12 Oct 2012 08:43:12 -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 S-5jKlJN6upK for <ietf@ietf.org>; Fri, 12 Oct 2012 08:43:12 -0700 (PDT)
Received: from [192.168.2.105] (pool-96-255-37-162.washdc.fios.verizon.net [96.255.37.162]) by c8a.amsl.com (Postfix) with ESMTPSA id 435FF12D016 for <ietf@ietf.org>; Fri, 12 Oct 2012 08:43:12 -0700 (PDT)
From: IETF Chair <chair@ietf.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Revised Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
Date: Fri, 12 Oct 2012 11:43:10 -0400
Message-Id: <41C64DEE-7E32-4198-B4D2-C5848F5A9426@ietf.org>
To: IETF <ietf@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1085)
X-Mailer: Apple Mail (2.1085)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Oct 2012 15:43:13 -0000

The IESG has updated the draft IESG Statement based on the many comments =
that have been received.  This revised text shows the linkage to RFC =
2026 in a much more explicit manner, and it preserves the ability of the =
IESG to remove an Internet-Draft from the Public I-D Archive without a =
court order.  That said, the IESG firmly believes that the collection of =
I-Ds provide important historical records for the open and transparent =
operation of the IETF.  Therefore, removal of a I-D from the  Public I-D =
Archive should teated as a significant event.  As a result, this =
statement requires IESG consensus is needed to remove an I-D from the =
Public I-D Archive.

Comments from the community are solicited on the revised draft IESG =
statement.

On behalf of the IESG,
Russ

--- DRAFT IESG STATEMENT ---

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

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

Internet-Drafts (I-Ds) are working documents of the IETF.  RFC 2026,
BCP 9, describes the purpose of I-Ds, and it also provides some policies
that govern the I-D Repository.  RFC 2026 says:

   During the development of a specification, draft versions of the
   document are made available for informal review and comment by
   placing them in the IETF's "Internet-Drafts" directory, which is
   replicated on a number of Internet hosts.  This makes an evolving
   working document readily available to a wide audience, facilitating
   the process of review and revision.

   An Internet-Draft that is published as an RFC, or that has remained
   unchanged in the Internet-Drafts directory for more than six months
   without being recommended by the IESG for publication as an RFC, is
   simply removed from the Internet-Drafts directory.  At any time, an
   Internet-Draft may be replaced by a more recent version of the same
   specification, restarting the six-month timeout period.

   An Internet-Draft is NOT a means of "publishing" a specification;
   specifications are published through the RFC mechanism described in
   the previous section.  Internet-Drafts have no formal status, and are
   subject to change or removal at any time.

I-Ds provide important historical records for the open and transparent
operation of the IETF.  It should be noted that individuals and groups,
including the IAB and IRTF Research Groups, have chosen to distribute
working documents as I-Ds.

I-Ds are stored in two places on the IETF web site.  First, current I-Ds
are stored in the I-D Repository.  Second, current and past I-Ds are
stored in a Public I-D Archive.

The policies associated with I-D Repository are discussed in RFC 2026,
and this IESG statement offers no additional policies regarding the
I-D Repository.

As RFC 2026 says, the entries in the I-D Repository are subject to
change or removal at any time; however, I-Ds generally remain in the
Public I-D Archive to support easy comparison with previous versions.
This availability facilitates review, comment, and revision.

An I-D will only be removed from the Public I-D Archive under unusual
circumstances with consensus of the IESG.  If you are aware of abuse or
misuse that warrants removal of an I-D from the Public I-D Archive,
please write to iesg@ietf.org and explain the situation.  At its
discretion, the IESG may consult counsel or the IETF community before
taking any action on such requests.  If circumstances permit, a removed
I-D will be replaced with a tombstone file that describes the reason =
that
the I-D was removed from the Public I-D Archive.

When an I-D is removed from the Public I-D Archive, a copy will be kept
in a location accessible by the IETF Secretariat.  This private location
is described in RFC 2026 as follows:

  ... Internet-Drafts that
  have been removed (for any reason) from the Internet-Drafts
  directories shall be archived by the IETF Secretariat for the sole
  purpose of preserving an historical record of Internet standards
  activity and thus are not retrievable except in special
  circumstances.
 =20
The IESG, IAB, IAOC, or the Internet Society Board of Trustees can
request the IETF Secretariat to search this private location in
support of responses to appeals, responses to subpoenas, or other
handling of legal matters.  The IETF Secretariat is expected to make
the results of searches of the private location available as needed to
appropriately respond such matters.


From chair@ietf.org  Fri Oct 12 08:57:19 2012
Return-Path: <chair@ietf.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9798221F86C2; Fri, 12 Oct 2012 08:57: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=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pCmfs4v378MA; Fri, 12 Oct 2012 08:57:19 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:123a::1:14]) by ietfa.amsl.com (Postfix) with ESMTP id 3FA6F21F8690; Fri, 12 Oct 2012 08:57:16 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id A63E812D02D; Fri, 12 Oct 2012 08:57:16 -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 lMHWGgq5X4FE; Fri, 12 Oct 2012 08:57:16 -0700 (PDT)
Received: from [192.168.2.105] (pool-96-255-37-162.washdc.fios.verizon.net [96.255.37.162]) by c8a.amsl.com (Postfix) with ESMTPSA id 33B7F12D016; Fri, 12 Oct 2012 08:57:16 -0700 (PDT)
From: IETF Chair <chair@ietf.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Bits-N-Bites Event in Atlanta
Date: Fri, 12 Oct 2012 11:57:14 -0400
Message-Id: <041870AD-B14A-49EB-AB0B-87104D6E95F0@ietf.org>
To: IETF Announce <ietf-announce@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1085)
X-Mailer: Apple Mail (2.1085)
Cc: 85all@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, 12 Oct 2012 15:57:19 -0000

We are pleased to announce Bits-N-Bites, the community networking =
experimental event that will take place for the second time at IETF 85 =
in Atlanta. =20

This event will bring together IETF participants, with exhibitors, =
product vendors, and service providers to share information, and =
showcase products and services in a social setting with food and drink.

Bits-N-Bites will be held Thursday evening, November 8th, from 7:00 - =
9:00 PM.

The Sponsors for this event include IPSO Alliance, Huawei, China =
Telecom, Tsinghua University, ICANN, and the Internet Society.  =
Sponsorship tables are still available! For more information see =
<https://www.ietf.org/meeting/85/bits-n-bites.html> and contact Drew =
Dvorshak at dvorshak@isoc.org.

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

Russ Housley
IETF Chair

Bob Hinden
IAOC Chair=

From luby@qti.qualcomm.com  Thu Oct 11 10:30:48 2012
Return-Path: <luby@qti.qualcomm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A11F921F86D4; Thu, 11 Oct 2012 10:30:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7q+8rmdzHsa7; Thu, 11 Oct 2012 10:30:48 -0700 (PDT)
Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) by ietfa.amsl.com (Postfix) with ESMTP id 0252821F8672; Thu, 11 Oct 2012 10:30:47 -0700 (PDT)
X-IronPort-AV: E=McAfee;i="5400,1158,6861"; a="246521777"
Received: from ironmsg02-r.qualcomm.com ([172.30.46.16]) by wolverine02.qualcomm.com with ESMTP; 11 Oct 2012 10:30:32 -0700
X-IronPort-AV: E=Sophos;i="4.80,573,1344236400"; d="scan'208";a="163223601"
Received: from nasanexhc11.na.qualcomm.com ([172.30.39.6]) by ironmsg02-R.qualcomm.com with ESMTP/TLS/RC4-SHA; 11 Oct 2012 10:30:32 -0700
Received: from NASANEXD02C.na.qualcomm.com ([169.254.6.73]) by nasanexhc11.na.qualcomm.com ([172.30.39.6]) with mapi id 14.02.0318.001; Thu, 11 Oct 2012 10:31:16 -0700
From: "Luby, Michael" <luby@qti.qualcomm.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: [Fecframe] Last Call: <draft-ietf-fecframe-simple-rs-04.txt> (Simple Reed-Solomon Forward Error Correction (FEC) Scheme for FECFRAME) to Proposed Standard
Thread-Topic: [Fecframe] Last Call: <draft-ietf-fecframe-simple-rs-04.txt> (Simple Reed-Solomon Forward Error Correction (FEC) Scheme for FECFRAME) to Proposed Standard
Thread-Index: AQHNp9YdUfC0inC8OUqNHjk/tyaiOA==
Date: Thu, 11 Oct 2012 17:30:31 +0000
Message-ID: <BAE0CC0CAB9C9C4AAE57C71E55C451D820BC037D@NASANEXD02C.na.qualcomm.com>
In-Reply-To: <20121008141129.10923.33854.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.2.4.120824
x-originating-ip: [10.45.230.6]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <4ABA1EE5DE627D48B8798BA805C3CCCD@qualcomm.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Fri, 12 Oct 2012 09:59:54 -0700
Cc: "Luby, Michael" <luby@qti.qualcomm.com>, "fecframe@ietf.org" <fecframe@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Oct 2012 17:32:56 -0000

Some quick comments.

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

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

Thanks, Mike

On 10/8/12 7:11 AM, "The IESG" <iesg-secretary@ietf.org> wrote:

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


From contreraslegal@att.net  Thu Oct 11 17:00:20 2012
Return-Path: <contreraslegal@att.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 542F721F859E for <ietf@ietfa.amsl.com>; Thu, 11 Oct 2012 17:00:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.306
X-Spam-Level: 
X-Spam-Status: No, score=-1.306 tagged_above=-999 required=5 tests=[AWL=1.294,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Q2CCS1u0XVHm for <ietf@ietfa.amsl.com>; Thu, 11 Oct 2012 17:00:20 -0700 (PDT)
Received: from nm29-vm2.bullet.mail.ne1.yahoo.com (nm29-vm2.bullet.mail.ne1.yahoo.com [98.138.91.129]) by ietfa.amsl.com (Postfix) with ESMTP id 1CE0D21F8594 for <ietf@ietf.org>; Thu, 11 Oct 2012 17:00:19 -0700 (PDT)
Received: from [98.138.90.55] by nm29.bullet.mail.ne1.yahoo.com with NNFMP; 12 Oct 2012 00:00:16 -0000
Received: from [66.94.237.120] by tm8.bullet.mail.ne1.yahoo.com with NNFMP; 12 Oct 2012 00:00:16 -0000
Received: from [127.0.0.1] by omp1025.access.mail.mud.yahoo.com with NNFMP; 12 Oct 2012 00:00:16 -0000
X-Yahoo-Newman-Id: 123838.25407.bm@omp1025.access.mail.mud.yahoo.com
Received: (qmail 25792 invoked from network); 12 Oct 2012 00:00:15 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=att.net; s=s1024; t=1350000015; bh=2UICsX7IxpPnnEIRaMZzWpYAcp+b2nj8TBQglr0oPtE=; h=X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:Received:User-Agent:Date:Subject:From:To:CC:Message-ID:Thread-Topic:In-Reply-To:Mime-version:Content-type:Content-transfer-encoding; b=oN9uYvGPL0vczq2z9xmt43qUu+B5YBlZN3CK1wP/EM1+mEtuqKWeV2NZIsWXjdDSslgKq518qu1TGqJX4iTcmw7c8kQXuagnBXmIS7j8eF9+VMkU8jQ/+Dg/tF+evsrbLxDNguyuXaJo0PIdsYZPLmhgRq/qXurCl1j0DcOAge8=
X-Yahoo-Newman-Property: ymail-3
X-YMail-OSG: rmQOcC8VM1lBmyt.fC.lZUXBlTeGfh.KWYamY1Yh_q6cL7M asWNmncKpt4L2pgKkn_orvW3S5QrECW1gm8gmQX7Tk_bNNaj5bTQ.DxnNc4S 9hhQht97Z7AEGxHwFYwINjvGBCeUS1e2g9mqetLKGFkIVEtTRO8XiE7rljd5 RgH6bAztCTESNmwOorAQ5JBppdavVSwVmVJIHLvvYqtuccvwlvCNNz6DmGU2 2p5m4eAoJClNa1XsO5PLDIZ7wX3p1wFFz4ZZdXZrxRJ6Es_6AEdaNkf2WNhp Eg7q.qh6EPIgR7vjWQpD8ufLBMHqZvrTqcnGsioyP4xIWaeFlSn175Zfe2Pz 6yANqTfctlODNrsnTqS7ID7gmDlsx85d5JyfuSylKRg24ofn.QPqHnRH9Z8i Vi7cnkwj7k1sF74R6vjLMnoCxsRto_2R3bDiJF.KLht6YNfcDzgvq_w--
X-Yahoo-SMTP: Tpws8J2swBD0AYsI15QnGStUj39kEOzzvCQVFA_jngKSSYU-
Received: from [192.168.1.2] (contreraslegal@198.228.196.121 with login) by smtp106.sbc.mail.ne1.yahoo.com with SMTP; 11 Oct 2012 17:00:15 -0700 PDT
User-Agent: Microsoft-MacOutlook/14.2.4.120824
Date: Thu, 11 Oct 2012 19:00:11 -0500
Subject: Re: Antitrust FAQ
From: Jorge Contreras <contreraslegal@att.net>
To: Sam Hartman <hartmans-ietf@mit.edu>, IETF Chair <chair@ietf.org>
Message-ID: <CC9CC662.B626%contreraslegal@att.net>
Thread-Topic: Antitrust FAQ
In-Reply-To: <tslobk8oim4.fsf@mit.edu>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-Mailman-Approved-At: Fri, 12 Oct 2012 09:59:54 -0700
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Oct 2012 00:00:20 -0000

Sam,

Here are some responses for your consideration.

Jorge

On 10/11/12 3:32 PM, "Sam Hartman" <hartmans-ietf@mit.edu> wrote:

>Hi, Russ.
>
>In question 2,
>I don't understand what several terms are and whether they have any
>relation to the standards process.
>
>The one most confusing is "agreements to restrict output"

This is when companies agree to reduce their production in order to
increase demand/prices.  For example, a group of ISPs get together at an
IETF meeting and agree that they will each only offer a limited quantity
of high-bandwitdh Internet access.

>
>Also, more detail on what an anticompetitive reason to restrict someone
>from the standards process could help.

For example 3 old-line manufacturers get together and decide that they
don't want a particular up-and-coming competitor to be part of a WG
because they would prefer to stick with their current technology
architecture.

>
>I'd also expect to see:
>
>7) What should be considered when evaluating the composition of design
>teams to avoid antitrust concerns?

Technical expertise, balance of interests (per the discussion in the join
IEEE/IAB/IETF document that was recently released), and no dominance by
any particular company.

>
>8) What responsibilities do chairs have in avoiding antitrust concerns
>within their WGs.

Without a formal Antitrust policy, I don't think there are any official
responsibilities.  However, the prudent chair will try to dissuade
anticompetitive conduct in his/her WG, and will report suspected
anticompetitive activity to the IESG.

>
>
>9) What should chairs, editors or other participants do if they have
>concerns about something they observe in the IETF process?


See above

>
>
>These are not hypothetical concerns.  In all three cases I've had the
>question with regard to specific events and not been sure what to do.



From craemer@isoc.org  Fri Oct 12 09:36:49 2012
Return-Path: <craemer@isoc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B53AB21F871A for <ietf@ietfa.amsl.com>; Fri, 12 Oct 2012 09:36:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.264
X-Spam-Level: 
X-Spam-Status: No, score=-103.264 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ky4i6f1ogbYn for <ietf@ietfa.amsl.com>; Fri, 12 Oct 2012 09:36:48 -0700 (PDT)
Received: from smtp207.dfw.emailsrvr.com (smtp207.dfw.emailsrvr.com [67.192.241.207]) by ietfa.amsl.com (Postfix) with ESMTP id CA08E21F8713 for <ietf@ietf.org>; Fri, 12 Oct 2012 09:36:48 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp10.relay.dfw1a.emailsrvr.com (SMTP Server) with ESMTP id 5D13F1B815F for <ietf@ietf.org>; Fri, 12 Oct 2012 12:36:48 -0400 (EDT)
X-Virus-Scanned: OK
Received: by smtp10.relay.dfw1a.emailsrvr.com (Authenticated sender: craemer-AT-isoc.org) with ESMTPSA id 2072E1B80ED for <ietf@ietf.org>; Fri, 12 Oct 2012 12:36:48 -0400 (EDT)
From: Kevin Craemer <craemer@isoc.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: ISOC@IETF 85 Briefing Panel - Internet Untethered?
Date: Fri, 12 Oct 2012 12:36:47 -0400
Message-Id: <DA154A4D-F91B-41DF-92CC-7DD53A4CB698@isoc.org>
To: ietf@ietf.org
Mime-Version: 1.0 (Apple Message framework v1085)
X-Mailer: Apple Mail (2.1085)
X-Mailman-Approved-At: Fri, 12 Oct 2012 09:59:54 -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, 12 Oct 2012 16:36:49 -0000

The Internet Society is organizing a briefing panel on Tuesday, 6 =
November, from 11:45am to 12:45pm, at IETF 85 in Atlanta.  This is to =
provide information on the topic and on registration for the panel.

	Internet Untethered?

The mobile data network world has changed significantly in the course of =
the last 4 years as game-changing smartphones have come online, tablets =
are hitting the scene.  Users have taken up these devices with =
enthusiasm, and put them to uses not ever envisioned by their creators =
or the operators of the networks that support them.  And with increasing =
speed and power (of devices and mobile data networks), users are =
expecting broadband Internet experience while on the move.  This panel =
will explore the evolution of the mobile data network reality through =
key questions:

How have these new devices impacted the evolution of mobile data =
services  and offerings of mobile Internet, especially in terms of =
bandwidth management?

What are the key factors in evolving from a mobile data service to =
mobile Internet?

Many ubiquitous web-based services (Wikipedia, Facebook, Twitter) are =
increasingly accessed through dedicated applications on the smartphone. =
What are the drivers for this and where is it taking the Internet user's =
reality?

Information on the briefing panelists will be posted at:
http://www.internetsociety.org/internet-society-panel-ietf-85

Due to high demand for limited seating at Internet Society panel events, =
we are providing you with advance information about registration. Online =
registration will open in two time blocks to account for the broad range =
of home timezones of IETF participants.  Half of the available seats =
will be open for registration at 09:00 UTC on Wednesday, 17 October, and =
the other half will be made available at 21:00 UTC.  Look for a =
registration form link at the webpage above at these times.

For those unable to attend, we plan to provide a live (and archived) =
audiocast, information on which will also be available at the above =
webpage.

Kevin Craemer
Senior Events Manager
Internet Society
craemer@isoc.org


From presnick@qti.qualcomm.com  Fri Oct 12 10:27:14 2012
Return-Path: <presnick@qti.qualcomm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 91A2C21F87B7; Fri, 12 Oct 2012 10:27:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.583
X-Spam-Level: 
X-Spam-Status: No, score=-106.583 tagged_above=-999 required=5 tests=[AWL=0.016, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Oz4MkvSzMYxN; Fri, 12 Oct 2012 10:27:13 -0700 (PDT)
Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) by ietfa.amsl.com (Postfix) with ESMTP id E151221F87A8; Fri, 12 Oct 2012 10:27:13 -0700 (PDT)
X-IronPort-AV: E=McAfee;i="5400,1158,6863"; a="247391568"
Received: from ironmsg02-r.qualcomm.com ([172.30.46.16]) by wolverine02.qualcomm.com with ESMTP; 12 Oct 2012 10:27:13 -0700
X-IronPort-AV: E=Sophos;i="4.80,577,1344236400"; d="scan'208";a="163443388"
Received: from nasanexhc08.na.qualcomm.com ([172.30.39.7]) by ironmsg02-R.qualcomm.com with ESMTP/TLS/RC4-SHA; 12 Oct 2012 10:27:13 -0700
Received: from presnick-mac.local (172.30.39.5) by qcmail1.qualcomm.com (172.30.39.7) with Microsoft SMTP Server (TLS) id 14.2.318.1; Fri, 12 Oct 2012 10:27:13 -0700
Message-ID: <507852EF.1000703@qti.qualcomm.com>
Date: Fri, 12 Oct 2012 12:27:11 -0500
From: Pete Resnick <presnick@qti.qualcomm.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.7; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4
MIME-Version: 1.0
To: Jorge Contreras <contreraslegal@att.net>
Subject: Re: Antitrust FAQ
References: <CC9CC662.B626%contreraslegal@att.net>
In-Reply-To: <CC9CC662.B626%contreraslegal@att.net>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.39.5]
Cc: IETF Chair <chair@ietf.org>, Sam Hartman <hartmans-ietf@mit.edu>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Oct 2012 17:27:14 -0000

On 10/11/12 7:00 PM, Jorge Contreras wrote:
>> 7) What should be considered when evaluating the composition of design
>> teams to avoid antitrust concerns?
>>      
> Technical expertise, balance of interests (per the discussion in the join
> IEEE/IAB/IETF document that was recently released), and no dominance by
> any particular company.
>    

Indeed, I'd expect chairs to follow the above advice even if it didn't 
affect antitrust concerns. In fact, I'd say following the rest of our 
process appropriately *requires* that you follow the above advice. 
That's why I think it's unnecessary to say this in the antitrust FAQ: If 
chairs don't know that they need to have appropriate representation of 
technical expertise and viewpoints on a design team, we need to fix that 
at a higher level.

>> 8) What responsibilities do chairs have in avoiding antitrust concerns
>> within their WGs.
>>      
> Without a formal Antitrust policy, I don't think there are any official
> responsibilities.  However, the prudent chair will try to dissuade
> anticompetitive conduct in his/her WG, and will report suspected
> anticompetitive activity to the IESG.
>    

Again, most anti-competitive behavior is also going to be a violation of 
other IETF procedures: In Jorge's example above, if folks from a group 
of old guard companies try to push the technology of an up-and-coming 
competitor out of a WG because they'd prefer to stick with their current 
technology and the chair allows the technology to be pushed out even 
though the new guy has some small amount of support and has answered all 
of the technical objections of the old fogies, that's not a proper 
consensus call. "There's 20 of us and only 2 of them" does not mean that 
there's rough consensus if the 2 have strong technical arguments for 
going in a different direction that go unanswered by the larger group.

One of the reasons that some of us wanted simply an FAQ and not a new 
antitrust policy is because sticking tightly to proper IETF procedures 
will almost always avoid a chair getting themselves into antitrust hot 
water.

pr

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


From dhc@dcrocker.net  Fri Oct 12 10:35:10 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 A56DD21F872E; Fri, 12 Oct 2012 10:35:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D5yM2dacFiGk; Fri, 12 Oct 2012 10:35:09 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id B95C021F871A; Fri, 12 Oct 2012 10:35:09 -0700 (PDT)
Received: from [192.168.10.220] (guest-wifi.isc.org [149.20.53.98]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q9CHZ6HS016988 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 12 Oct 2012 10:35:07 -0700
Message-ID: <507854C2.9090007@dcrocker.net>
Date: Fri, 12 Oct 2012 10:34:58 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121005 Thunderbird/16.0
MIME-Version: 1.0
To: Pete Resnick <presnick@qti.qualcomm.com>
Subject: Re: Antitrust FAQ
References: <CC9CC662.B626%contreraslegal@att.net> <507852EF.1000703@qti.qualcomm.com>
In-Reply-To: <507852EF.1000703@qti.qualcomm.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Fri, 12 Oct 2012 10:35:07 -0700 (PDT)
Cc: IETF Chair <chair@ietf.org>, Sam Hartman <hartmans-ietf@mit.edu>, IETF <ietf@ietf.org>, Jorge Contreras <contreraslegal@att.net>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Oct 2012 17:35:10 -0000

On 10/12/2012 10:27 AM, Pete Resnick wrote:
> On 10/11/12 7:00 PM, Jorge Contreras wrote:
> One of the reasons that some of us wanted simply an FAQ and not a new
> antitrust policy is because sticking tightly to proper IETF procedures
> will almost always avoid a chair getting themselves into antitrust hot
> water.


A statement of this sort in the FAQ, and an explanation for its basis, 
would be helpful.

d/

-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From johnl@iecc.com  Fri Oct 12 13:07: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 2D65A21F87B7 for <ietf@ietfa.amsl.com>; Fri, 12 Oct 2012 13:07:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -111.684
X-Spam-Level: 
X-Spam-Status: No, score=-111.684 tagged_above=-999 required=5 tests=[AWL=0.515, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 32rSG6UTWnzH for <ietf@ietfa.amsl.com>; Fri, 12 Oct 2012 13:07:42 -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 0550121F8748 for <ietf@ietf.org>; Fri, 12 Oct 2012 13:07:41 -0700 (PDT)
Received: (qmail 59067 invoked from network); 12 Oct 2012 20:07:37 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 12 Oct 2012 20:07:37 -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=50787889.xn--9vv.k1208; i=johnl@user.iecc.com; bh=Qtup+SAD5qWeY7rba5+IIzkXBGOzfWWtICrDKFQT48c=; b=u+VpSxFJb0dbhW2Lr3Q3upTTGig19xp8CVvlWU7sczEgT2T+y9rdIEl6S0EiO8NU5N8zdcP2gjneR6wtQCLEDrVYNQog7GqpwIEq/zr6pMY4r2lXgnykH0IaD0v8ie0ZrKwLfKwfMTzzNgPeMKcXwGd0ZB4T7qi9IrSGlmvcBME=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=50787889.xn--9vv.k1208; olt=johnl@user.iecc.com; bh=Qtup+SAD5qWeY7rba5+IIzkXBGOzfWWtICrDKFQT48c=; b=VMT0ZaRrVaZH+qPoMus9tSmEeu1Vk28vVVZVcG5X2ih+KxBWQT7Fb/g47VwyPfrWr/M74AY3xBZZbZXTEpKOVsa0ao6gIVcnz4b+tEAITkXZY8r9JBfC83tLV62JdACS1ARPAjrzHhHwcpMnSYEW8nsbvELmFvWzWciSRELiUPE=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 12 Oct 2012 20:07:15 -0000
Message-ID: <20121012200715.12201.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: Revised Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
In-Reply-To: <41C64DEE-7E32-4198-B4D2-C5848F5A9426@ietf.org>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
Cc: chair@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Oct 2012 20:07:43 -0000

>An I-D will only be removed from the Public I-D Archive under unusual
>circumstances with consensus of the IESG. ...

> If circumstances permit, a removed
> I-D will be replaced with a tombstone file that describes the reason that
> the I-D was removed from the Public I-D Archive.

That seems much more realistic and practical.  Ship it.

R's,
John

From mahmutbulut0@gmail.com  Sun Oct 14 05:36:04 2012
Return-Path: <mahmutbulut0@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3A19221F850D for <ietf@ietfa.amsl.com>; Sun, 14 Oct 2012 05:36:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.739
X-Spam-Level: 
X-Spam-Status: No, score=-1.739 tagged_above=-999 required=5 tests=[BAYES_20=-0.74, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ta-GqqQQFZAO for <ietf@ietfa.amsl.com>; Sun, 14 Oct 2012 05:36:03 -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 B2AE321F8504 for <ietf@ietf.org>; Sun, 14 Oct 2012 05:36:03 -0700 (PDT)
Received: by mail-ob0-f172.google.com with SMTP id v19so5019581obq.31 for <ietf@ietf.org>; Sun, 14 Oct 2012 05:36:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=tFvV3+nfFXMx7IizxVQj9hHpBZDyXVZsn5SJG7EJaak=; b=CBDs6/L+PeKggS1tyKQUaJimS2803fZBeVJzj0WXS//Nf9HUccPF4il8rGRnP4tLdi Hd52mdr+/e9eW7Oxy7a7CdTWKqPtd0S4IWVm5Zx/ctAv+rPNOcGdxUbQ+pNhzI65ijd5 CWpCGf1z3v0DZaXJpHTuSK+/wsRfMfkaXcQ4SJl97wfi7InELZRjBBgp97xrU98/BJwJ zwTvoQNuO/4E9FgLVM2mZoAIMPb6LAthuSV48ldGpazaFQLtkrDwAX1vy/UrdJEET5Sd +GUoZ/59PhJJERZJvfzvG13PZDDgOYgeYe4bG+07+3mjGLhSLn7Y/L1M0Mqhgwfqdy99 OFfA==
MIME-Version: 1.0
Received: by 10.182.192.74 with SMTP id he10mr7410180obc.87.1350218163297; Sun, 14 Oct 2012 05:36:03 -0700 (PDT)
Received: by 10.76.116.196 with HTTP; Sun, 14 Oct 2012 05:36:03 -0700 (PDT)
Date: Sun, 14 Oct 2012 15:36:03 +0300
Message-ID: <CANM99gzX-TidrZUp-mn8x26+TO5=i6deb0Nu+YF4LtYJ6+g0Cg@mail.gmail.com>
Subject: Newcomer from a student
From: Mahmut Bulut <mahmutbulut0@gmail.com>
To: ietf@ietf.org
Content-Type: multipart/alternative; boundary=14dae9399da7fe1e0d04cc042914
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 14 Oct 2012 12:36:04 -0000

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

Dear group members;
I'm a student from Turkey and interested in multicast research and I want
to participate in SAM researches. I have neither any background on this
research area nor any mentor ( academic ). I want to participate in an
universal project which is my reason to mail here. Would you mind to accept
me to an ongoing research?
Thanks in advance.

Best Regards

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

Dear group members;<br>
I&#39;m a student from Turkey and interested in multicast research and I 
want to participate in SAM researches. I have neither any background on 
this research area nor any mentor ( academic ). I want to participate in
 an universal project which is my reason to mail here. Would you mind to
 accept me to an ongoing research?<br>
Thanks in advance.<br>
<br>
Best Regards

--14dae9399da7fe1e0d04cc042914--

From hartmans@mit.edu  Mon Oct 15 05:53:13 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 1A7AE21F875A; Mon, 15 Oct 2012 05:53:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -95.393
X-Spam-Level: 
X-Spam-Status: No, score=-95.393 tagged_above=-999 required=5 tests=[AWL=-2.095, BAYES_40=-0.185, FH_HELO_EQ_D_D_D_D=1.597, FH_HOST_EQ_D_D_D_D=0.765, FM_DDDD_TIMES_2=1.999, HELO_DYNAMIC_IPADDR=2.426, RDNS_DYNAMIC=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yErGcPY66qKN; Mon, 15 Oct 2012 05:53:12 -0700 (PDT)
Received: from ec2-23-21-227-93.compute-1.amazonaws.com (ec2-23-21-227-93.compute-1.amazonaws.com [23.21.227.93]) by ietfa.amsl.com (Postfix) with ESMTP id A59A621F8758; Mon, 15 Oct 2012 05:53:12 -0700 (PDT)
Received: from carter-zimmerman.suchdamage.org (c-98-217-126-210.hsd1.ma.comcast.net [98.217.126.210]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.suchdamage.org (Postfix) with ESMTPS id EFB6220146; Mon, 15 Oct 2012 08:52:56 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id E85D24AD5; Mon, 15 Oct 2012 08:53:05 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: Pete Resnick <presnick@qti.qualcomm.com>
Subject: Re:  Re: Antitrust FAQ
References: <CC9CC662.B626%contreraslegal@att.net> <507852EF.1000703@qti.qualcomm.com>
Date: Mon, 15 Oct 2012 08:53:05 -0400
In-Reply-To: <507852EF.1000703@qti.qualcomm.com> (Pete Resnick's message of "Fri, 12 Oct 2012 12:27:11 -0500")
Message-ID: <tsld30jdhhq.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 Chair <chair@ietf.org>, Sam Hartman <hartmans-ietf@mit.edu>, IETF <ietf@ietf.org>, Jorge Contreras <contreraslegal@att.net>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Oct 2012 12:53:13 -0000

Pete, I have not been so frustrated and disappointed reading an IETF
message at any time earlier this year.
I'm disappointed because I'd like to work in an IETf climate where
antitrust and related concerns are taken seriously. 
I need to believe that the IESG will take these issues seriously, will
give chairs and others the tools they need to do a good job and will
seriously consider concers that arise.

I can recall a number of instances when I've raised concerns about not
having the appropriate tools or clarity of process in this regard. I can
also recall two instances where I've raised specific concerns about
anti-competitive practices.
In all these instances, including this one, I received pushback from an
area director working for a large company--Cisco, Ericson, Qualcomm,
etc.

Would you be willing to consider the following questions?

1) What harm is done by writing down common information in a FAQ where
chairs will be able to find it when trying to confirm they are doing the
right thing or double check what they should be considering?



2) How messages like yours will affect chairs and others willingness to
bring concerns to you in your role of area director.

Thanks for your consideration,

--Sam

From presnick@qti.qualcomm.com  Mon Oct 15 07:15:45 2012
Return-Path: <presnick@qti.qualcomm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0F29221F8750; Mon, 15 Oct 2012 07:15:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.583
X-Spam-Level: 
X-Spam-Status: No, score=-106.583 tagged_above=-999 required=5 tests=[AWL=0.016, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id icgf0Wc7YGS8; Mon, 15 Oct 2012 07:15:44 -0700 (PDT)
Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) by ietfa.amsl.com (Postfix) with ESMTP id DD93E21F85BB; Mon, 15 Oct 2012 07:15:43 -0700 (PDT)
X-IronPort-AV: E=McAfee;i="5400,1158,6865"; a="248812661"
Received: from ironmsg03-r.qualcomm.com ([172.30.46.17]) by wolverine02.qualcomm.com with ESMTP; 15 Oct 2012 07:14:56 -0700
X-IronPort-AV: E=Sophos;i="4.80,587,1344236400"; d="scan'208";a="351408293"
Received: from nasanexhc04.na.qualcomm.com ([172.30.48.17]) by Ironmsg03-R.qualcomm.com with ESMTP/TLS/RC4-SHA; 15 Oct 2012 07:14:55 -0700
Received: from presnick-mac.local (172.30.48.1) by qcmail1.qualcomm.com (172.30.48.17) with Microsoft SMTP Server (TLS) id 14.2.318.1; Mon, 15 Oct 2012 07:14:55 -0700
Message-ID: <507C1A5C.6000207@qti.qualcomm.com>
Date: Mon, 15 Oct 2012 09:14:52 -0500
From: Pete Resnick <presnick@qti.qualcomm.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.7; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4
MIME-Version: 1.0
To: Sam Hartman <hartmans-ietf@mit.edu>
Subject: Re: Antitrust FAQ
References: <CC9CC662.B626%contreraslegal@att.net>	<507852EF.1000703@qti.qualcomm.com> <tsld30jdhhq.fsf_-_@mit.edu>
In-Reply-To: <tsld30jdhhq.fsf_-_@mit.edu>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.48.1]
Cc: IETF Chair <chair@ietf.org>, IETF <ietf@ietf.org>, Jorge Contreras <contreraslegal@att.net>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Oct 2012 14:15:45 -0000

On 10/15/12 7:53 AM, Sam Hartman wrote:
> Pete, I have not been so frustrated and disappointed reading an IETF
> message at any time earlier this year.
> I'm disappointed because I'd like to work in an IETf climate where
> antitrust and related concerns are taken seriously.
> I need to believe that the IESG will take these issues seriously, will
> give chairs and others the tools they need to do a good job and will
> seriously consider concers that arise.
>    

Sam, I'm actually quite surprised at your reaction. The intention of my 
message (which obviously did not get across) was to say that I *do* take 
antitrust issues seriously, and to allay your concerns about the last 
two issues (the ones you labeled 7 and 8) because I think they are 
covered in other parts of our procedures having nothing to do with 
antitrust. I thought Jorge's answers were spot on, and followed up by 
saying, "If you stick to other IETF procedures, you should have smooth 
sailing." I'm at a loss for why you think this means I don't take these 
issues seriously, and if what I said seemed dismissive of your needs as 
a chair, please know that I'm intent on getting you the tools and 
support you need. I feel terrible that you aren't getting that support 
now, and I publicly commit to changing that. However, I do need to 
understand what I dismissed and what needs to change.

> I can recall a number of instances when I've raised concerns about not
> having the appropriate tools or clarity of process in this regard. I can
> also recall two instances where I've raised specific concerns about
> anti-competitive practices.
> In all these instances, including this one, I received pushback from an
> area director working for a large company--Cisco, Ericson, Qualcomm,
> etc.
>    

I hope that you did not get pushback from me prior to this (I'm the only 
Qualcomm AD at the moment), and if you did, I hope you'll tell me when 
that happened. That said, I do find it interesting that the pushback 
you've received is from people in large companies. I can tell you from 
my experience that one person I've talked to in Qualcomm legal about 
this topic would *prefer* the IETF to have not just a more elaborate 
FAQ, but an explicit antitrust policy, and I have pushed back against 
that. I can't speak for others, but I know that my position on this 
topic is probably one of the least affected by my company affiliation.

In any event, I want to hear more about concerns you've raised where you 
haven't gotten the tools or clarity of process you need, and I want to 
make sure that gets fixed.

> Would you be willing to consider the following questions?
>    

Of course.

> 1) What harm is done by writing down common information in a FAQ where
> chairs will be able to find it when trying to confirm they are doing the
> right thing or double check what they should be considering?
>    

Writing down helpful information is not at all a problem, and I do like 
Dave Crocker's suggestion to add the bits about, "Sticking to these 
other IETF procedures will keep you out of antitrust problems." My 
concern (along with many other folks) only kicks in when the collection 
of this information starts to look like a formal antitrust *policy*. I'm 
afraid that having an antitrust policy starts to lead us down the path 
of the IETF becoming a corporate-membership organization instead of a 
collection of individuals who do not represent particular companies. To 
date, we have little formal recognition of companies as participants in 
the IETF, and I for one would like to keep it that way. The real 
concerns that drive the desire for a formal antitrust policy are about 
corporations behaving in improper (and illegal) ways, not individuals. 
(There are ways for individuals to get themselves in antitrust trouble, 
but that's not the main motivation for having such a policy.) The closer 
we get to having such a policy, the closer we get to saying that we are 
going to make the concerns of corporations an important part of how we 
make decisions in the IETF. I think that would be a disaster.

If you see me pushing back against things in the antitrust FAQ, it's 
because of the above concerns. I'm not trying to dismiss the needs of 
folks like yourself in IETF leadership.

> 2) How messages like yours will affect chairs and others willingness to
> bring concerns to you in your role of area director.
>    

This one I'm not even sure how to start answering. As I said above, my 
intention in my message was to point out process and procedure you 
already have at your disposal to deal with antitrust issues. If I 
sounded like I didn't take your concerns seriously or was unwilling to 
hear concerns from chairs in the future, I will do everything I can to 
fix that. (And if other chairs felt the same way that Sam did but did 
not want to talk about it publicly, please drop me a private note; I 
need to make good on this.)

> Thanks for your consideration,
>    

You are absolutely welcome, and if this message does not fully address 
your concerns, please follow up. I'm also happy to talk, either by 
phone/VoIP or in a few weeks in Atlanta, with you or any chair who is 
not getting the support you need.

pr

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


From tglassey@earthlink.net  Mon Oct 15 07:33:38 2012
Return-Path: <tglassey@earthlink.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DC01F21F8713 for <ietf@ietfa.amsl.com>; Mon, 15 Oct 2012 07:33:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.622
X-Spam-Level: 
X-Spam-Status: No, score=-2.622 tagged_above=-999 required=5 tests=[AWL=-0.023, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xyFb1rTm5FM8 for <ietf@ietfa.amsl.com>; Mon, 15 Oct 2012 07:33:38 -0700 (PDT)
Received: from elasmtp-masked.atl.sa.earthlink.net (elasmtp-masked.atl.sa.earthlink.net [209.86.89.68]) by ietfa.amsl.com (Postfix) with ESMTP id EDD7821F8711 for <ietf@ietf.org>; Mon, 15 Oct 2012 07:33:37 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=Olk2UEtuiSvMqLM17PUBeBU0v0toqrr6e3C/mimXPlq1BrR/FcBzo0ByEOI6pRNz; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [67.180.133.21] (helo=[192.168.15.2]) by elasmtp-masked.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from <tglassey@earthlink.net>) id 1TNljc-0005Af-Tq for ietf@ietf.org; Mon, 15 Oct 2012 10:33:37 -0400
Message-ID: <507C1EC0.1000003@earthlink.net>
Date: Mon, 15 Oct 2012 07:33:36 -0700
From: tglassey <tglassey@earthlink.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Antitrust FAQ
References: <CC9CC662.B626%contreraslegal@att.net>	<507852EF.1000703@qti.qualcomm.com> <tsld30jdhhq.fsf_-_@mit.edu> <507C1A5C.6000207@qti.qualcomm.com>
In-Reply-To: <507C1A5C.6000207@qti.qualcomm.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 01b7a7e171bdf5911aa676d7e74259b7b3291a7d08dfec79e2e871b17f113a857426b503c4e3addc350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 67.180.133.21
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Oct 2012 14:33:39 -0000

On 10/15/2012 7:14 AM, Pete Resnick wrote:
> On 10/15/12 7:53 AM, Sam Hartman wrote:
>> Pete, I have not been so frustrated and disappointed reading an IETF
>> message at any time earlier this year.
>> I'm disappointed because I'd like to work in an IETf climate where
>> antitrust and related concerns are taken seriously.
>> I need to believe that the IESG will take these issues seriously, will
>> give chairs and others the tools they need to do a good job and will
>> seriously consider concers that arise.
>
> Sam, I'm actually quite surprised at your reaction. The intention of 
> my message (which obviously did not get across) was to say that I *do* 
> take antitrust issues seriously, and to allay your concerns about the 
> last two issues (the ones you labeled 7 and 8) because I think they 
> are covered in other parts of our procedures having nothing to do with 
> antitrust. I thought Jorge's answers were spot on, and followed up by 
> saying, "If you stick to other IETF procedures, you should have smooth 
> sailing." I'm at a loss for why you think this means I don't take 
> these issues seriously, and if what I said seemed dismissive of your 
> needs as a chair, please know that I'm intent on getting you the tools 
> and support you need. I feel terrible that you aren't getting that 
> support now, and I publicly commit to changing that. However, I do 
> need to understand what I dismissed and what needs to change.
>
>> I can recall a number of instances when I've raised concerns about not
>> having the appropriate tools or clarity of process in this regard. I can
>> also recall two instances where I've raised specific concerns about
>> anti-competitive practices.
>> In all these instances, including this one, I received pushback from an
>> area director working for a large company--Cisco, Ericson, Qualcomm,
>> etc.
>
> I hope that you did not get pushback from me prior to this (I'm the 
> only Qualcomm AD at the moment), and if you did, I hope you'll tell me 
> when that happened. That said, I do find it interesting that the 
> pushback you've received is from people in large companies. I can tell 
> you from my experience that one person I've talked to in Qualcomm 
> legal about this topic would *prefer* the IETF to have not just a more 
> elaborate FAQ, but an explicit antitrust policy, and I have pushed 
> back against that. I can't speak for others, but I know that my 
> position on this topic is probably one of the least affected by my 
> company affiliation.
>
> In any event, I want to hear more about concerns you've raised where 
> you haven't gotten the tools or clarity of process you need, and I 
> want to make sure that gets fixed.
>
>> Would you be willing to consider the following questions?
>
> Of course.
>
>> 1) What harm is done by writing down common information in a FAQ where
>> chairs will be able to find it when trying to confirm they are doing the
>> right thing or double check what they should be considering?
>
> Writing down helpful information is not at all a problem, and I do 
> like Dave Crocker's suggestion to add the bits about, "Sticking to 
> these other IETF procedures will keep you out of antitrust problems." 
> My concern (along with many other folks) only kicks in when the 
> collection of this information starts to look like a formal antitrust 
> *policy*. I'm afraid that having an antitrust policy starts to lead us 
> down the path of the IETF becoming a corporate-membership organization 
> instead of a collection of individuals who do not represent particular 
> companies. To date, we have little formal recognition of companies as 
> participants in the IETF, and I for one would like to keep it that 
> way. The real concerns that drive the desire for a formal antitrust 
> policy are about corporations behaving in improper (and illegal) ways, 
> not individuals. (There are ways for individuals to get themselves in 
> antitrust trouble, but that's not the main motivation for having such 
> a policy.) The closer we get to having such a policy, the closer we 
> get to saying that we are going to make the concerns of corporations 
> an important part of how we make decisions in the IETF. I think that 
> would be a disaster.
>
> If you see me pushing back against things in the antitrust FAQ, it's 
> because of the above concerns. I'm not trying to dismiss the needs of 
> folks like yourself in IETF leadership.
I am - I am saying the current models are useless, they get us to the 
point where NEA was being brought up before the IESG itself and we find 
one of the primary party's behind the process has an IPR disclosure.

As to Antitrust - well - it doesnt really matter what the IETF wants to 
claim is the law internally to the IETF - it simply is not a legal court 
system and has no authority other than ...

Todd
>
>> 2) How messages like yours will affect chairs and others willingness to
>> bring concerns to you in your role of area director.
>
> This one I'm not even sure how to start answering. As I said above, my 
> intention in my message was to point out process and procedure you 
> already have at your disposal to deal with antitrust issues. If I 
> sounded like I didn't take your concerns seriously or was unwilling to 
> hear concerns from chairs in the future, I will do everything I can to 
> fix that. (And if other chairs felt the same way that Sam did but did 
> not want to talk about it publicly, please drop me a private note; I 
> need to make good on this.)
>
>> Thanks for your consideration,
>
> You are absolutely welcome, and if this message does not fully address 
> your concerns, please follow up. I'm also happy to talk, either by 
> phone/VoIP or in a few weeks in Atlanta, with you or any chair who is 
> not getting the support you need.
>
> pr
>


-- 
Regards TSG
"Ex-Cruce-Leo"

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


From brian.e.carpenter@gmail.com  Mon Oct 15 08:22:55 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 84B4021F87AA; Mon, 15 Oct 2012 08:22:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.691
X-Spam-Level: 
X-Spam-Status: No, score=-101.691 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WFtYCDoYZqBM; Mon, 15 Oct 2012 08:22:54 -0700 (PDT)
Received: from mail-bk0-f44.google.com (mail-bk0-f44.google.com [209.85.214.44]) by ietfa.amsl.com (Postfix) with ESMTP id 3CF5121F87A8; Mon, 15 Oct 2012 08:22:54 -0700 (PDT)
Received: by mail-bk0-f44.google.com with SMTP id jc3so2397291bkc.31 for <multiple recipients>; Mon, 15 Oct 2012 08:22:53 -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=36B4pHEsjEqy+h+2WRHk9CZWchOdfI4HMvW4jzL7jw0=; b=dYdBudLYMKathiSTsf+CxYZ7LexQNop9JdqE/8cOy9E+YEP9iz+k5zYTUiUpj2w4se kbHsRI0J66mOECzoq7yOZZ+xS0XLvqPy5fMTurVcNM7EC6ushlbRpCoVmBMEacjDm9gB cZQM3dAhvmvSuO1nMthuzsQhYSZnl/+7qxwBszRKLOXXJR6AP9BFXWNLxWNVIczhrvyd MA0rBNdNnhKHVzNpkiNn4oW3BdZnPxnQJNnbC+urAm7VdDBDPLYNOId+U7dJ10uPwks/ qn8N5iZRQbcC+ELTQrjchOe+7fX/yRPhSxFf5LdqiTzGfuSBGyeaJ8Sfbay1dHzL/vKC muwA==
Received: by 10.204.7.88 with SMTP id c24mr3271530bkc.118.1350314573227; Mon, 15 Oct 2012 08:22:53 -0700 (PDT)
Received: from [192.168.1.65] (host-2-102-219-22.as13285.net. [2.102.219.22]) by mx.google.com with ESMTPS id fm5sm8831750bkc.5.2012.10.15.08.22.45 (version=SSLv3 cipher=OTHER); Mon, 15 Oct 2012 08:22:46 -0700 (PDT)
Message-ID: <507C2A45.9030602@gmail.com>
Date: Mon, 15 Oct 2012 16:22:45 +0100
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Pete Resnick <presnick@qti.qualcomm.com>
Subject: Re: Antitrust FAQ
References: <CC9CC662.B626%contreraslegal@att.net>	<507852EF.1000703@qti.qualcomm.com>	<tsld30jdhhq.fsf_-_@mit.edu> <507C1A5C.6000207@qti.qualcomm.com>
In-Reply-To: <507C1A5C.6000207@qti.qualcomm.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: IETF Chair <chair@ietf.org>, Sam Hartman <hartmans-ietf@mit.edu>, IETF <ietf@ietf.org>, Jorge Contreras <contreraslegal@att.net>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Oct 2012 15:22:55 -0000

On 15/10/2012 15:14, Pete Resnick wrote:
> On 10/15/12 7:53 AM, Sam Hartman wrote:
>> Pete, I have not been so frustrated and disappointed reading an IETF
>> message at any time earlier this year.
...
> Sam, I'm actually quite surprised at your reaction. 

In fairness to both of you, I can see why Sam might have interpreted Pete's
message the way he did - I also thought Pete was being a bit flippant until
I read it a second time.

I think the point is that when drafting RFC 2026 (and later RFC 2418), those
involved (including Jorge's predecessor as pro bono counsel) were very much
aware of anti-trust rules, and it was certainly in their minds that following
the RFC 2026 process would largely avoid anti-trust issues, without the need
to say so explicitly. Indeed BCP 9 describes what we *should* do (focus on
technical aspects, ensure openness and fairness, disclose IPR) but not what
we shouldn't do. Anti-trust advice tends to describe what we shouldn't do.
That's what the FAQ adds.

    Brian

From john-ietf@jck.com  Mon Oct 15 09:57: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 8CE2A11E80E6; Mon, 15 Oct 2012 09:57:41 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TC8AfnEexLMu; Mon, 15 Oct 2012 09:57:41 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id E57DF11E808D; Mon, 15 Oct 2012 09:57:40 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1TNnz1-000Kpm-I0; Mon, 15 Oct 2012 12:57:39 -0400
Date: Mon, 15 Oct 2012 12:57:33 -0400
From: John C Klensin <john-ietf@jck.com>
To: Pete Resnick <presnick@qti.qualcomm.com>
Subject: Re: Antitrust FAQ
Message-ID: <2B5B0F0036DD9FD9FBA556C2@JcK-HP8200.jck.com>
In-Reply-To: <507C1A5C.6000207@qti.qualcomm.com>
References: <CC9CC662.B626%contreraslegal@att.net> <507852EF.1000703@qti.qualcomm.com>	<tsld30jdhhq.fsf_-_@mit.edu> <507C1A5C.6000207@qti.qualcomm.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: IETF Chair <chair@ietf.org>, IETF <ietf@ietf.org>, Jorge Contreras <contreraslegal@att.net>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Oct 2012 16:57:41 -0000

--On Monday, October 15, 2012 09:14 -0500 Pete Resnick
<presnick@qti.qualcomm.com> wrote:

>  My concern (along with many other folks)
> only kicks in when the collection of this information starts
> to look like a formal antitrust *policy*. I'm afraid that
> having an antitrust policy starts to lead us down the path of
> the IETF becoming a corporate-membership organization instead
> of a collection of individuals who do not represent particular
> companies. To date, we have little formal recognition of
> companies as participants in the IETF, and I for one would
> like to keep it that way. The real concerns that drive the
> desire for a formal antitrust policy are about corporations
> behaving in improper (and illegal) ways, not individuals.
> (There are ways for individuals to get themselves in antitrust
> trouble, but that's not the main motivation for having such a
> policy.) The closer we get to having such a policy, the closer
> we get to saying that we are going to make the concerns of
> corporations an important part of how we make decisions in the
> IETF. I think that would be a disaster.

FWIW, I share these concerns (and said so during an earlier
round of discussions of antitrust policy).  We've spent a huge
amount of effort trying to ensure that IETF participation is by
individuals rather than on the basis of organizational
memberships or affiliations; it would be very unfortunate to
back into something that would undermine that rather basic
policy.  IANAL, much less one with the right specialized
expertise to advise on whether we could have an effective
antitrust policy without having to move to "membership" with
associated agreements and identified affiliations, but I've been
told it is hard or impossible.   

As Pete says, advice about what one should not do -- enhanced by
a reminder that following normal IETF procedures and
requirements for openness and conssnsus will avoid most or all
accidental problems -- is another thing and is probably useful
and certainly harmless.

Two suggestions about the document (I am _not_ suggesting
wording):

First, based on discussions at ANSI _many_ years ago, the
current point 6 says "...should not be discussed at IETF
meeting?".  Ignoring the small grammatical problem, the issue is
not limited to IETF meetings.  Anything that should not be
discussed at a meeting should not be discussed on a mailing
list, conference call, or context that might, for other reasons,
be subject to BCP 78 or 79.  Put differently, such discussions
should not occur in any IETF context.  They should probably also
not occur in any context that might have the effect of
influencing IETF decisions or actions without the advice of
counsel.

Second, as I understand things, it might be useful to enhance
point 4 to note that good practices wrt antitrust issues
protects participants and whomever might be supporting their
work as much or more than it protects the IETF.

best,
   john


From chair@ietf.org  Mon Oct 15 11:37:23 2012
Return-Path: <chair@ietf.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1A7D821F88B1 for <ietf@ietfa.amsl.com>; Mon, 15 Oct 2012 11:37:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BQtgrsBST9zA for <ietf@ietfa.amsl.com>; Mon, 15 Oct 2012 11:37:22 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:123a::1:14]) by ietfa.amsl.com (Postfix) with ESMTP id 83B1321F88AE for <ietf@ietf.org>; Mon, 15 Oct 2012 11:37:22 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c7a.amsl.com (Postfix) with ESMTP id 788241603F5 for <ietf@ietf.org>; Mon, 15 Oct 2012 11:37:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c7a.amsl.com ([127.0.0.1]) by localhost (c7a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pVbZ4ebMxTUb for <ietf@ietf.org>; Mon, 15 Oct 2012 11:37:22 -0700 (PDT)
Received: from [192.168.2.100] (pool-96-255-37-162.washdc.fios.verizon.net [96.255.37.162]) by c7a.amsl.com (Postfix) with ESMTPSA id 1A78B1603E9 for <ietf@ietf.org>; Mon, 15 Oct 2012 11:37:22 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1085)
Subject: Re: Draft IESG Statement on Ethertype Assignments for IETF Protocols
From: IETF Chair <chair@ietf.org>
In-Reply-To: <6B27DBC6-6335-45E9-95AE-99DE787AE1D7@ietf.org>
Date: Mon, 15 Oct 2012 14:37:20 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <1B737CC1-57AC-4D48-B6F5-FE3FBC9B9952@ietf.org>
References: <6B27DBC6-6335-45E9-95AE-99DE787AE1D7@ietf.org>
To: IETF <ietf@ietf.org>
X-Mailer: Apple Mail (2.1085)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Oct 2012 18:37:23 -0000

Based on the comments received from the IETF community and the IEEE RAC, =
the draft IESG statement has been updated.  Comments on the revised text =
are solicited.

On behalf of the IESG,
Russ


--- REVISED DRAFT IESG STATEMENT ---

SUBJECT: Ethertype Assignments for IETF Protocols

The IEEE Registration Authority (IEEE RA) assigns Ethertypes with
oversight from the IEEE Registration Authority Committee (IEEE RAC).
(See http://standards.ieee.org/develop/regauth/ethertype/.)  Some IETF
protocol specification make use of Ethertypes.  All Ethertype requests
are subject to review by a consultant to the IEEE RA followed by
IEEE RAC confirmation.=20

Since Ethertypes are a fairly scarce resource, the IEEE RAC has let us
know that they will not assign a new Ethertype to a new IETF protocol
specification until the IESG has approved the protocol specification for
publication as an RFC.  In exceptional cases, the IEEE RA is willing to
consider "early allocation" of an Ethertype for an IETF protocol that is
still under development as long as the request comes from and has been
vetted by the IESG.

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

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


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

From adrian@olddog.co.uk  Mon Oct 15 14:41:46 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 AD71721F8AB1 for <ietf@ietfa.amsl.com>; Mon, 15 Oct 2012 14:41:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[AWL=0.301,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id k0jA5yiL3mRD for <ietf@ietfa.amsl.com>; Mon, 15 Oct 2012 14:41:46 -0700 (PDT)
Received: from asmtp3.iomartmail.com (asmtp3.iomartmail.com [62.128.201.159]) by ietfa.amsl.com (Postfix) with ESMTP id E3CAB21F8AA7 for <ietf@ietf.org>; Mon, 15 Oct 2012 14:41:45 -0700 (PDT)
Received: from asmtp3.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id q9FLfh2H028692;  Mon, 15 Oct 2012 22:41:43 +0100
Received: from 950129200 (westford-nat.juniper.net [66.129.232.2]) (authenticated bits=0) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id q9FLfe1F028682 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 15 Oct 2012 22:41:42 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <jjaeggli@zynga.com>
Subject: Re: I-D Action: draft-jaeggli-interim-observations-00.txt
Date: Mon, 15 Oct 2012 22:41:41 +0100
Message-ID: <042001cdab1d$df26b6b0$9d742410$@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: Ac2rHZD5L/yBpc3hS/GxQrQ3C+mSoQ==
Content-Language: en-gb
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Oct 2012 21:41:46 -0000

Joel,

Thanks for this stake in the ground as a starting point for recording
observations on the LIM. As an AD who was not there, I believe it is really
important that we try to capture this experience to decide whether to repeat the
idea, and if so, how to improve it.

Cheers,
Adrian

> -----Original Message-----
> From: i-d-announce-bounces@ietf.org [mailto:i-d-announce-bounces@ietf.org]
> On Behalf Of internet-drafts@ietf.org
> Sent: 15 October 2012 22:28
> To: i-d-announce@ietf.org
> Subject: I-D Action: draft-jaeggli-interim-observations-00.txt
> 
> 
> A New Internet-Draft is available from the on-line Internet-Drafts
directories.
> 
> 
> 	Title           : Observations on the experience and nature of Large
Interim
> Meetings
> 	Author(s)       : Joel Jaeggli
> 	Filename        : draft-jaeggli-interim-observations-00.txt
> 	Pages           : 4
> 	Date            : 2012-10-15
> 
> Abstract:
>    Planning, particpipation and conclusions from the experience of
>    participating in the IETF LIM activity on september 29th 2012.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-jaeggli-interim-observations
> 
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-jaeggli-interim-observations-00
> 
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/i-d-announce
> Internet-Draft directories: http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


From randy@psg.com  Mon Oct 15 14:49:21 2012
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 90E3B21F8A1C for <ietf@ietfa.amsl.com>; Mon, 15 Oct 2012 14:49:21 -0700 (PDT)
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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7lVHVNVA4phk for <ietf@ietfa.amsl.com>; Mon, 15 Oct 2012 14:49:21 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 3FD5421F89CE for <ietf@ietf.org>; Mon, 15 Oct 2012 14:49:21 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=rair.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.80 (FreeBSD)) (envelope-from <randy@psg.com>) id 1TNsXG-000FdR-AZ; Mon, 15 Oct 2012 21:49:18 +0000
Date: Mon, 15 Oct 2012 11:49:17 -1000
Message-ID: <m21ugzjtia.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Adrian Farrel <adrian@olddog.co.uk>
Subject: Re: I-D Action: draft-jaeggli-interim-observations-00.txt
In-Reply-To: <042001cdab1d$df26b6b0$9d742410$@olddog.co.uk>
References: <042001cdab1d$df26b6b0$9d742410$@olddog.co.uk>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Cc: IETF Disgust <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Oct 2012 21:49:21 -0000

ok, i am lost.  the draft is only an outline and has zero content?  is
it a quiz?

imiho, the sidr meeting was useful and got work done which probably
would have taken a lot more time online and would have had the wonderful
email misunderstanding amplification.

randy

From adrian@olddog.co.uk  Mon Oct 15 14:53:12 2012
Return-Path: <adrian@olddog.co.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8EB6A21F8AD7 for <ietf@ietfa.amsl.com>; Mon, 15 Oct 2012 14:53:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level: 
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[AWL=0.150,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id narIEId4mzuC for <ietf@ietfa.amsl.com>; Mon, 15 Oct 2012 14:53:11 -0700 (PDT)
Received: from asmtp2.iomartmail.com (asmtp2.iomartmail.com [62.128.201.249]) by ietfa.amsl.com (Postfix) with ESMTP id E222321F8AD5 for <ietf@ietf.org>; Mon, 15 Oct 2012 14:53:10 -0700 (PDT)
Received: from asmtp2.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id q9FLr9Fx025578;  Mon, 15 Oct 2012 22:53:09 +0100
Received: from 950129200 (westford-nat.juniper.net [66.129.232.2]) (authenticated bits=0) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id q9FLr5o0025541 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 15 Oct 2012 22:53:07 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Randy Bush'" <randy@psg.com>
References: <042001cdab1d$df26b6b0$9d742410$@olddog.co.uk> <m21ugzjtia.wl%randy@psg.com>
In-Reply-To: <m21ugzjtia.wl%randy@psg.com>
Subject: RE: I-D Action: draft-jaeggli-interim-observations-00.txt
Date: Mon, 15 Oct 2012 22:53:07 +0100
Message-ID: <042501cdab1f$77f31e50$67d95af0$@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: AQGQ8uxwXwblegDWCOchl9n//24rKQKUvTE/mB+ypPA=
Content-Language: en-gb
Cc: 'IETF Disgust' <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Oct 2012 21:53:12 -0000

> ok, i am lost.  the draft is only an outline and has zero content?  is
> it a quiz?

Treat it like that and see if you can give Joel the right answers.

For me: Did it make any difference to you that it was a LIM rather than simply a
SIDR interim? Were logistics and resources worth the fee? Should we hold future
LIMs, or do the scheduling and other issues mean that normal interims are the
way forward?

cheers,
Adrian



From warren@kumari.net  Mon Oct 15 14:53:54 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 AFFDE21F8470 for <ietf@ietfa.amsl.com>; Mon, 15 Oct 2012 14:53: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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GY1-l6IRDKgz for <ietf@ietfa.amsl.com>; Mon, 15 Oct 2012 14:53:53 -0700 (PDT)
Received: from vimes.kumari.net (smtp1.kumari.net [204.194.22.1]) by ietfa.amsl.com (Postfix) with ESMTP id 87E4121F8469 for <ietf@ietf.org>; Mon, 15 Oct 2012 14:53:43 -0700 (PDT)
Received: from [10.196.196.235] (1-193.icannmeeting.org [199.91.193.1]) by vimes.kumari.net (Postfix) with ESMTPSA id BDDC01B40740; Mon, 15 Oct 2012 17:53:29 -0400 (EDT)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.1 \(1498\))
Subject: Re: [IETF] Re: I-D Action: draft-jaeggli-interim-observations-00.txt
From: Warren Kumari <warren@kumari.net>
In-Reply-To: <m21ugzjtia.wl%randy@psg.com>
Date: Mon, 15 Oct 2012 17:53:29 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <4B66B871-86B5-474F-AA36-A4F092EA40AA@kumari.net>
References: <042001cdab1d$df26b6b0$9d742410$@olddog.co.uk> <m21ugzjtia.wl%randy@psg.com>
To: Randy Bush <randy@psg.com>
X-Mailer: Apple Mail (2.1498)
Cc: Adrian Farrel <adrian@olddog.co.uk>, 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: Mon, 15 Oct 2012 21:53:55 -0000

On Oct 15, 2012, at 5:49 PM, Randy Bush <randy@psg.com> wrote:

> ok, i am lost.  the draft is only an outline and has zero content?  is
> it a quiz?

No, I believe that it is very subtle satire, reflecting Joel's view on =
the utility of the meeting :-P


>=20
> imiho, the sidr meeting was useful and got work done which probably
> would have taken a lot more time online and would have had the =
wonderful
> email misunderstanding amplification.

+lots.

Sad as it is, getting folk together in a room helps focus the discussion =
and provides many fewer opportunities for misunderstanding=85=20

>=20
> randy
>=20

--
I don't think the execution is relevant when it was obviously a bad idea =
in the first place.
This is like putting rabid weasels in your pants, and later expressing =
regret at having chosen those particular rabid weasels and that pair of =
pants.=20
   ---maf

Warren Kumari
warren@kumari.net



From randy@psg.com  Mon Oct 15 15:04: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 52BA421F8A03 for <ietf@ietfa.amsl.com>; Mon, 15 Oct 2012 15:04:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.492
X-Spam-Level: 
X-Spam-Status: No, score=-2.492 tagged_above=-999 required=5 tests=[AWL=0.107,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vCLKeiI8I1Pb for <ietf@ietfa.amsl.com>; Mon, 15 Oct 2012 15:04:10 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 922B021F89C6 for <ietf@ietf.org>; Mon, 15 Oct 2012 15:04:10 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=rair.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.80 (FreeBSD)) (envelope-from <randy@psg.com>) id 1TNsld-000FgW-V5; Mon, 15 Oct 2012 22:04:10 +0000
Date: Mon, 15 Oct 2012 12:04:09 -1000
Message-ID: <m2y5j7ie92.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Adrian Farrel <adrian@olddog.co.uk>
Subject: Re: I-D Action: draft-jaeggli-interim-observations-00.txt
In-Reply-To: <042501cdab1f$77f31e50$67d95af0$@olddog.co.uk>
References: <042001cdab1d$df26b6b0$9d742410$@olddog.co.uk> <m21ugzjtia.wl%randy@psg.com> <042501cdab1f$77f31e50$67d95af0$@olddog.co.uk>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Cc: IETF Disgust <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Oct 2012 22:04:11 -0000

[ i should know better than to get into this maelstrom, but .. ]

> For me: Did it make any difference to you that it was a LIM rather
> than simply a SIDR interim?

no.  face to face with the ability for remote participation is what
counts.

> Were logistics and resources worth the fee?

not really.  though i heard that meetecho was better than webex had been
at previous interims.

and i note that 'large' is a bit disingenuous, as 42 other wgs held
meetings elsewhere within a few weeks of that 'LIM'.

to me, the real logistics issue is the lack of viable two-way remote
voice, let alone video, participation.  heck, back when dinosaurs roamed
the ietf corridors (instead of circuitzilla), a remote participant used
to be able to speak and be heard.  the whole vmeet bs got so wraped
arount featuritis, control freakism, and the union of everyone's
fantasies that we are stalled having regressed more than a decade.

> Should we hold future LIMs, or do the scheduling and other issues mean
> that normal interims are the way forward?

for the logistics to be worth it, you would have to whack the other wgs
to conform.  if you whack, then how is this different from another
flavor of general meeting?

randy

From joelja@bogus.com  Mon Oct 15 15:08:51 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 8259C21F8A15 for <ietf@ietfa.amsl.com>; Mon, 15 Oct 2012 15:08:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.399
X-Spam-Level: 
X-Spam-Status: No, score=-102.399 tagged_above=-999 required=5 tests=[AWL=0.200, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ew0cwXN8NPj8 for <ietf@ietfa.amsl.com>; Mon, 15 Oct 2012 15:08:51 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id F0D0721F88D0 for <ietf@ietf.org>; Mon, 15 Oct 2012 15:08:46 -0700 (PDT)
Received: from joels-MacBook-Air.local (host-64-47-153-50.masergy.com [64.47.153.50]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id q9FM8kSG022356 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Mon, 15 Oct 2012 22:08:46 GMT (envelope-from joelja@bogus.com)
Message-ID: <507C8968.1010702@bogus.com>
Date: Mon, 15 Oct 2012 15:08:40 -0700
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:16.0) Gecko/20121002 Thunderbird/16.0
MIME-Version: 1.0
To: Warren Kumari <warren@kumari.net>
Subject: Re: [IETF] Re: I-D Action: draft-jaeggli-interim-observations-00.txt
References: <042001cdab1d$df26b6b0$9d742410$@olddog.co.uk> <m21ugzjtia.wl%randy@psg.com> <4B66B871-86B5-474F-AA36-A4F092EA40AA@kumari.net>
In-Reply-To: <4B66B871-86B5-474F-AA36-A4F092EA40AA@kumari.net>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Mon, 15 Oct 2012 22:08:46 +0000 (UTC)
Cc: Adrian Farrel <adrian@olddog.co.uk>, 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: Mon, 15 Oct 2012 22:08:51 -0000

On 10/15/12 2:53 PM, Warren Kumari wrote:
> On Oct 15, 2012, at 5:49 PM, Randy Bush <randy@psg.com> wrote:
>
>> ok, i am lost.  the draft is only an outline and has zero content?  is
>> it a quiz?
> No, I believe that it is very subtle satire, reflecting Joel's view on the utility of the meeting :-P
or it's unsubtle and I just needed a structure and a 00 before the 
deadline, because the text that exists now isn't cooked enough yet. that 
may be an sube of the process but if there's an 01 before 1700 pacifc 
I'll post it.
>> imiho, the sidr meeting was useful and got work done which probably
>> would have taken a lot more time online and would have had the wonderful
>> email misunderstanding amplification.
> +lots.
>
> Sad as it is, getting folk together in a room helps focus the discussion and provides many fewer opportunities for misunderstanding…
>
>> randy
>>
> --
> I don't think the execution is relevant when it was obviously a bad idea in the first place.
> This is like putting rabid weasels in your pants, and later expressing regret at having chosen those particular rabid weasels and that pair of pants.
>     ---maf
>
> Warren Kumari
> warren@kumari.net
>
>
>


From melinda.shore@gmail.com  Mon Oct 15 15:38:01 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 D68C621F8855 for <ietf@ietfa.amsl.com>; Mon, 15 Oct 2012 15:38:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.522
X-Spam-Level: 
X-Spam-Status: No, score=-3.522 tagged_above=-999 required=5 tests=[AWL=0.077,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PmBjfSIrrr-x for <ietf@ietfa.amsl.com>; Mon, 15 Oct 2012 15:38:01 -0700 (PDT)
Received: from mail-pa0-f44.google.com (mail-pa0-f44.google.com [209.85.220.44]) by ietfa.amsl.com (Postfix) with ESMTP id 6709621F884B for <ietf@ietf.org>; Mon, 15 Oct 2012 15:38:01 -0700 (PDT)
Received: by mail-pa0-f44.google.com with SMTP id fb11so5219659pad.31 for <ietf@ietf.org>; Mon, 15 Oct 2012 15:37:59 -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=aTqHP7q1OUZwYGMhvmYmMJGw9pP9WL9nYuiOlK090Gw=; b=eSVXESON+zU3z9vwuJIw0lOoftOtXb7+e+80INhZQb0OMYOUKURDcHEuwtTWTAoAdf N5BZRdByNcPSS2j+FZW/7iLnwZ+g7FvBERiqNMXRTb63wniVmUyxeGwdar/Ghtf5Gn8B z061Wa07fAm3OvAQdGW9p+C8HxlvYtgBmF8TS4vuJisCVdWyEG9zfRkQ3OhtDMa1xUpd LrpFmIyHnKxALmoj9718ztbbM7Q5MgMbesgko4nTjmxrLF8iTH95tE21EYnPi3UCHKtm z5iFGcmG248tefkuSb2WaQF2/UZRj7TsjKLL1c5Su7zZ8Yrauwj7K1lJd1BQRtSWubGA UXaw==
Received: by 10.68.202.6 with SMTP id ke6mr40717350pbc.82.1350340679855; Mon, 15 Oct 2012 15:37:59 -0700 (PDT)
Received: from spandex.local (66-230-86-185-rb1.fai.dsl.dynamic.acsalaska.net. [66.230.86.185]) by mx.google.com with ESMTPS id o5sm9704617paz.32.2012.10.15.15.37.44 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 15 Oct 2012 15:37:45 -0700 (PDT)
Message-ID: <507C9036.7020902@gmail.com>
Date: Mon, 15 Oct 2012 14:37:42 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: Warren Kumari <warren@kumari.net>
Subject: Re: [IETF] Re: I-D Action: draft-jaeggli-interim-observations-00.txt
References: <042001cdab1d$df26b6b0$9d742410$@olddog.co.uk> <m21ugzjtia.wl%randy@psg.com> <4B66B871-86B5-474F-AA36-A4F092EA40AA@kumari.net>
In-Reply-To: <4B66B871-86B5-474F-AA36-A4F092EA40AA@kumari.net>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
Cc: Adrian Farrel <adrian@olddog.co.uk>, 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: Mon, 15 Oct 2012 22:38:02 -0000

On 10/15/12 1:53 PM, Warren Kumari wrote:
> Sad as it is, getting folk together in a room helps focus the
> discussion and provides many fewer opportunities for
> misunderstanding…

I don't like interim meetings, but unfortunately the IETF seems
increasingly meeting-deadline driven so more deadlines is probably
the best way to keep work moving forward.  They've also been very
effective in helping to transition the IETF to an organization
that's far friendlier to large companies with big travel budgets
than it is to smaller companies with more constraints.  I also
wonder if some companies think they're IETF contributors by
putting bodies in chairs at meetings instead of focusing on
contributing to the work.  But hey, it's all good.

Melinda

From harald@alvestrand.no  Tue Oct 16 01:45:28 2012
Return-Path: <harald@alvestrand.no>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 36FBC21F8887 for <ietf@ietfa.amsl.com>; Tue, 16 Oct 2012 01:45:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.378
X-Spam-Level: 
X-Spam-Status: No, score=-110.378 tagged_above=-999 required=5 tests=[AWL=0.221, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LMiq0B9J7zxN for <ietf@ietfa.amsl.com>; Tue, 16 Oct 2012 01:45:27 -0700 (PDT)
Received: from eikenes.alvestrand.no (eikenes.alvestrand.no [158.38.152.233]) by ietfa.amsl.com (Postfix) with ESMTP id 8E2C621F8885 for <ietf@ietf.org>; Tue, 16 Oct 2012 01:45:27 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id D5C5539E197 for <ietf@ietf.org>; Tue, 16 Oct 2012 10:45:25 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at eikenes.alvestrand.no
Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eEr7T1xsxDIY for <ietf@ietf.org>; Tue, 16 Oct 2012 10:45:25 +0200 (CEST)
Received: from hta-dell.lul.corp.google.com (unknown [IPv6:2620:0:1043:1:be30:5bff:fede:bcdc]) by eikenes.alvestrand.no (Postfix) with ESMTPSA id 2FDA539E029 for <ietf@ietf.org>; Tue, 16 Oct 2012 10:45:24 +0200 (CEST)
Message-ID: <507D1EA3.9030102@alvestrand.no>
Date: Tue, 16 Oct 2012 10:45:23 +0200
From: Harald Alvestrand <harald@alvestrand.no>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20121011 Thunderbird/16.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Revised Draft IESG Statement on Removal of an Internet-Draft from the IETF Web Site
References: <41C64DEE-7E32-4198-B4D2-C5848F5A9426@ietf.org>
In-Reply-To: <41C64DEE-7E32-4198-B4D2-C5848F5A9426@ietf.org>
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, 16 Oct 2012 08:45:28 -0000

I like this.

Nit: There's a missing "to" in the last line.


From jari.arkko@piuha.net  Tue Oct 16 08:17:37 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 7EF2121F8973 for <ietf@ietfa.amsl.com>; Tue, 16 Oct 2012 08:17:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -94.119
X-Spam-Level: 
X-Spam-Status: No, score=-94.119 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FB_WORD1_END_DOLLAR=3.294, FB_WORD2_END_DOLLAR=3.294, J_CHICKENPOX_13=0.6, MISSING_HEADERS=1.292,  USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oN4AwRpvvFbw for <ietf@ietfa.amsl.com>; Tue, 16 Oct 2012 08:17:36 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by ietfa.amsl.com (Postfix) with ESMTP id 15A8721F896B for <ietf@ietf.org>; Tue, 16 Oct 2012 08:17:36 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id D4B452CF37; Tue, 16 Oct 2012 18:17:33 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Q-SmBFQoC5XP; Tue, 16 Oct 2012 18:17:33 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id D3D392CC56; Tue, 16 Oct 2012 18:17:32 +0300 (EEST)
Message-ID: <507D7A8C.1090201@piuha.net>
Date: Tue, 16 Oct 2012 18:17:32 +0300
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20121011 Thunderbird/16.0.1
MIME-Version: 1.0
Subject: Re: I-D Action: draft-jaeggli-interim-observations-00.txt
References: <042001cdab1d$df26b6b0$9d742410$@olddog.co.uk>
In-Reply-To: <042001cdab1d$df26b6b0$9d742410$@olddog.co.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
Cc: jjaeggli@zynga.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, 16 Oct 2012 15:17:37 -0000

Joel,

Thanks for writing this. I have some detailed comments, but perhaps I sho=
uld first start with my own perception of the meeting.

I traveled to this meeting as a part my trip to attend RIPE a few days, a=
nd to catch a few different people in the hallways on separate topics. On=
e datapoint: I would probably not have made the trip just for RIPE this t=
ime (although I usually do travel to them), nor would I have attended jus=
t for the LIM itself.

I was quite surprised by the small attendance, what I heard from the secr=
etariat was 30+ people registered for the interim. From a pure financial =
perspective this meeting did not seem to make a lot of sense for the IETF=
, 30 x 100$ for a lot of secretariat effort/travel, and presumably money =
for room fees and other costs. Most previous interim meetings have operat=
ed on a hosting/sponsoring model, or run in zero cost environments. I'd s=
ay that anything under hundred persons is probably easier to deal with in=
 that way than attempt to use an official organization for it.

But money is really a side issue, so lets not focus on the above too much=
=2E What matters if we can progress the IETF's work:

The various meeting had a big difference between them. The SIDR meeting w=
as clearly a close group of people with an intent to solve a design probl=
em, going over an issue after another issue, involving people who would n=
ot have traveled to the IETF, and at least from my perspective the meetin=
g was making quite a lot of progress in some issues that had been divisiv=
e earlier. This reminded me of some earlier SOFTWIRE meetings, for instan=
ce, where the designers and implementors met and made a lot of progress. =
An excellent meeting!

FWIW, in the IETF I would not have had time to go to SIDR, and I would no=
t have traveled anywhere to go to a SIDR meeting. But I'm glad I went to =
this one because it allowed me to learn more about this technology, and s=
ome of the layer nine implications at the IAB force me to try to understa=
nd its state.

I did not attend OPSEC, but I attended V6OPS. All discussions were useful=
, but topics seemed somewhat disconnected, and they did not cover the who=
le range of usual V6OPS work. It was clear that the room did not have the=
 full set of key contributors in the WG. I had prepared comments on a rec=
ent topic in the mailing list, but the relevant people were not there to =
receive my comments. Nevertheless, the V6OPS meeting did have a fair numb=
er of the usual experts in this topic, as well as a couple of extra peopl=
e from the European routing community. I was able to have a high-bandwidt=
h discussion on several topics with the people present; albeit that was i=
n the hallways and after the meeting. We started one new draft for V6OPS =
based on this interim, and another (yet to be completed) work item for th=
e HOMENET WG. In the latter case I would not have had the necessary peopl=
e present in the IETF, so for me this was quite positive.

It is hard to tell why there was no more attendance in V6OPS. Wrong time =
and place? Or true lack of interest to invest in some of the topics that =
we are just not seeing it in the IETF because everyone comes there anyway=
?

Conclusions? Maybe we need more discussion on this, but here are some obv=
ious ones:

o  Interim meetings can be extremely productive in the right situation. O=
r completely unnecessary in others. It is difficult to find a situation w=
here the planets are properly aligned such that several working groups ar=
e in the right phase to have an interim meeting, and that the co-location=
 with some event makes sense for all of those working groups. In other wo=
rds, the success of a LIM seems somewhat unlikely, though there may be su=
ccess for individual WG interims.

o  Co-location with RIPE appeared useful. I agree with you Joel that tigh=
ter packing would have made a difference. I met some people who noted the=
y will not attend, but probably would have attended if it was during the =
week. Co-locating individual WG interims with RIPEs and NANOGs seems like=
 a useful concept to consider in the future.

o  LIMs will not create a new big funding source for the IETF. We should =
also right-size our organization for the task at hand. 30, 50, or even 10=
0 people could probably be handled as part of the RIPE meeting, and might=
 have been something that the RIPE registration system and agenda could h=
ave accommodated, or have someone sponsor a room and leave the rest to pa=
rticipants.

o  As usual, hallways matter more than the official meetings. Put the rig=
ht people in the same building, and I'll attend, even if the topic would =
be International Charactersets for EBCDIC-based FTP.

o  Saturday is not a good day.

Detailed comments:

>     The LIM was the attempt that I am aware of an interim meeting
>     scheduled by IETF management for the purposes of accumulating inter=
im

Does not parse. Did you mean to say that LIM was the only attempt of its =
kind? A couple of years ago we also had the Malta proposal which failed (=
possibly due to the downturn, or possibly due to the same issues that mad=
e the Amsterdam event surprisingly small).

>     meetings in a common location rather that scheduled by working-grou=
p
>     participants, chairs nad coordinating ADs.

s/and/nad

>     It is, my understanding that discussion of the possbility of a LIM
>     style meeting occured early2011 if not before.

s/possbility/possibility/
s/early2011/early 2011/

There has been discussions of something like this over the years. FWIW I =
am not aware of the exact details of when and how this LIM discussion sta=
rted. Maybe Ron or someone else from the current IESG could explain it.


> The stated rational for targeting v6ops
>     involvement in a large interim was the volume of work that we proce=
ss
>     during and between meetings.

Interestingly, the amount of work in the interim meeting itself did not s=
eem match this as well as I would have expected. We can speculate about t=
he causes.

I came prepared to talk about certain topics, but the draft authors in qu=
estion were not present. Perhaps an isolated case, but had the impression=
 that you guys dealt with only a subset of the work that v6ops meetings i=
n IETF deal with. Do you agree?

> Superficially only a fraction of the v6ops attendees are
>     represented by the interested segment however when the numbers are
>     mapped against active participants and draft authors, interested
>     participants in the interim represent a bigger purportion of that
>     group

Missing ".".

I think we have a participant list. It would be useful to have an underst=
anding of how many % of the people who presented or made mike line commen=
ts in IETF-84 were present in the interim.

>     One osbervation that I would make about the interim submission
>

observation

>     V6ops attendance at an IETF meeting is typically in excess of 200
>     attendees.  An interim meeting that attracts 25 of those and
>     minuscule remote participation is necessarily exclusionary by defau=
lt
>     if not deliberately.  If useful work that advances drafts, gets don=
e,
>     is that exclusivity a bad thing?  It's not useful for measuring
>     meaningful consensus.

They are different meetings. And for sure the interim meetings do not hel=
p in measuring consensus. However, at their best they are meetings where =
closely knit groups of core developers can progress their work in a high-=
bandwidth collaboration environment. I have yet to see an interim meeting=
 that would actually represent any meaningful consensus measurement point=
 (to the extent any physical meeting can; the list is what counts). Or pe=
rhaps the Montreal IPv6 transition meeting was one, attended by close to =
a hundred persons. In any case, this does not necesssarily render the int=
erim meetings useless, just that you have to use them as a different tool=
=2E Progress work. Move forward in design. Write specs. But far less cons=
ensus measurement, far less various experts from different domains, etc. =
Useful early in the work, not so useful later when finetuning something.

>     Area director's were rather well represent at the LIM, While the
>     attendance of both of our Directors was appreciated I'm not sure th=
at
>     it's a good use of their time.  In particular if the frequency of
>     these events were fixed as some rate in the future, this represents=

>     an additional workload for which huge benfits due not appear liekly=

>     to ensue

There were also (at least) two IAB members, both of whom were present on =
site for other reasons as well.

Jari



From joelja@bogus.com  Tue Oct 16 08:39:41 2012
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1D69921F8875 for <ietf@ietfa.amsl.com>; Tue, 16 Oct 2012 08:39:41 -0700 (PDT)
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, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id glkhDYQdL8vE for <ietf@ietfa.amsl.com>; Tue, 16 Oct 2012 08:39:40 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 61DC021F8848 for <ietf@ietf.org>; Tue, 16 Oct 2012 08:39:40 -0700 (PDT)
Received: from joels-MacBook-Air.local (host-64-47-153-50.masergy.com [64.47.153.50]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id q9GFddns036068 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Tue, 16 Oct 2012 15:39:40 GMT (envelope-from joelja@bogus.com)
Message-ID: <507D7FB6.4050105@bogus.com>
Date: Tue, 16 Oct 2012 08:39:34 -0700
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:16.0) Gecko/20121002 Thunderbird/16.0
MIME-Version: 1.0
To: adrian@olddog.co.uk
Subject: Re: I-D Action: draft-jaeggli-interim-observations-00.txt
References: <042001cdab1d$df26b6b0$9d742410$@olddog.co.uk> <m21ugzjtia.wl%randy@psg.com> <042501cdab1f$77f31e50$67d95af0$@olddog.co.uk>
In-Reply-To: <042501cdab1f$77f31e50$67d95af0$@olddog.co.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Tue, 16 Oct 2012 15:39:40 +0000 (UTC)
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: Tue, 16 Oct 2012 15:39:41 -0000

On 10/15/12 2:53 PM, Adrian Farrel wrote:
>> ok, i am lost.  the draft is only an outline and has zero content?  is
>> it a quiz?
> Treat it like that and see if you can give Joel the right answers.
01 is available. I imagine the SIDR experience was a bit different, 
having been to another SIDR interim, I tried to call that out, but I 
wasn't in the room.

http://tools.ietf.org/html/draft-jaeggli-interim-observations-01
> For me: Did it make any difference to you that it was a LIM rather than simply a
> SIDR interim? Were logistics and resources worth the fee? Should we hold future
> LIMs, or do the scheduling and other issues mean that normal interims are the
> way forward?
>
> cheers,
> Adrian
>
>


From david.black@emc.com  Mon Oct 15 16:10:49 2012
Return-Path: <david.black@emc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1556D1F0381; Mon, 15 Oct 2012 16:10:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.56
X-Spam-Level: 
X-Spam-Status: No, score=-102.56 tagged_above=-999 required=5 tests=[AWL=0.039, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fZUtUaVgLuuL; Mon, 15 Oct 2012 16:10:48 -0700 (PDT)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id E87021F042A; Mon, 15 Oct 2012 16:10:47 -0700 (PDT)
Received: from hop04-l1d11-si02.isus.emc.com (HOP04-L1D11-SI02.isus.emc.com [10.254.111.55]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q9FNAi2T011614 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 15 Oct 2012 19:10:44 -0400
Received: from mailhub.lss.emc.com (mailhub.lss.emc.com [10.254.222.129]) by hop04-l1d11-si02.isus.emc.com (RSA Interceptor); Mon, 15 Oct 2012 19:10:30 -0400
Received: from mxhub36.corp.emc.com (mxhub36.corp.emc.com [10.254.93.84]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q9FNASNs008636; Mon, 15 Oct 2012 19:10:28 -0400
Received: from mx15a.corp.emc.com ([169.254.1.83]) by mxhub36.corp.emc.com ([::1]) with mapi; Mon, 15 Oct 2012 19:10:28 -0400
From: "Black, David" <david.black@emc.com>
To: "yiu_lee@cable.comcast.com" <yiu_lee@cable.comcast.com>, "roberta.maglione@telecomitalia.it" <roberta.maglione@telecomitalia.it>, "carlw@mcsr-labs.org" <carlw@mcsr-labs.org>, "christian.jacquenet@orange.com" <christian.jacquenet@orange.com>, "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>, "gen-art@ietf.org" <gen-art@ietf.org>
Date: Mon, 15 Oct 2012 19:10:27 -0400
Subject: Gen-ART review of draft-ietf-softwire-dslite-deployment-06
Thread-Topic: Gen-ART review of draft-ietf-softwire-dslite-deployment-06
Thread-Index: Ac2rKkPgDErjXyHISiSTlQ/jGKFZIg==
Message-ID: <8D3D17ACE214DC429325B2B98F3AE7120DFAEF29@MX15A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
X-Mailman-Approved-At: Tue, 16 Oct 2012 08:52:20 -0700
Cc: "softwires@ietf.org" <softwires@ietf.org>, "Black, David" <david.black@emc.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Oct 2012 23:10:49 -0000

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

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

Document: draft-ietf-softwire-dslite-deployment-06
Reviewer: David L. Black
Review Date: October 15, 2012
IETF LC End Date: October 16, 2012
IESG Telechat Date: October 25, 2012

Summary:

This draft is on the right track but has open issues, described in the revi=
ew.

This is a generally well-written draft that expands considerably on the bri=
ef
deployment considerations for DS-Lite in Appendix A of RFC 6333.  The draft
is clear and reasonably well-written, and a significant improvement on that
RFC 6333 Appendix, although an understanding of RFC 6333 is necessary to
understand this draft, which seems completely reasonable.

The B4 and AFTR acronyms are clever - kudos to whomever came up with those.

I found five open issues, all of which are minor.

Minor Issues:

[1] Ironically, the first issue is that something should be said about
the relationship of this draft to Appendix A of RFC 6333.  It probably
suffices to say that this draft expands on the material in that Appendix,
as I see no need to specify that this draft updates RFC 6333 solely to
change non-normative material in an Appendix.

[2] The MTU increase technique in Section 2.2 is a "may", which is
consistent with Section 5.3 of RFC 6333.  OTOH, Section 2.2 of this
draft should also discuss the AFTR resource exhaustion concern that
described in Section 6.3 of RFC 6333, as that is a potential
operational reason for an ISP to increase MTU size (e.g., if customer
sourcing of large IPv4 packets is not sufficiently rare).

[3] Section 2.7 refers to "the AFTR's internal interface".  There may be
two internal interfaces, the physical IPv6 interface (outer header) and
the tunnel's IPv4 interface (inner header).  The text should be clarified
to indicate which interface is involved - it appears that the AFTR's
physical IPv6 interface is intended in this section.

[4] Section 2.7 cites RFC 6333 for use of DHCPv6 with DS-Lite.  RFC 6334
should be cited - either in addition to or instead of RFC 6333.

[5] Section 2.8 discusses IPv4 accounting at the AFTR, but notes that
"the AFTR does not have detailed customer identity information."  Does
that create a theft of service possibility?  If so, that possibility
should be mentioned as a security consideration.  Also, Section 2.8
ought to be expanded with a sentence or two explaining why the AFTR
does not have that identity information, and in particular to explain
whether and why it is unreasonable in some or all cases to expect
that customer identity information be provided to the AFTR as part
of provisioning each customer's softwire.

Nits:

Section 2.3 on MTU Considerations could usefully mention MTU discovery
techniques, as possibilities for customer IPv4 traffic to adapt to a
smaller IPv4 MTU.  If this is done, it would be useful to mention
RFC 4821 in addition to the mention of RFC 1191 in RFC 6333.

Section 2.4 should define "lawful intercept".  It would be helpful to
cite a reference for this concept if something appropriate can be found.

Section 2.5:
- Are one or both types of logging recommended?
- Last paragraph on p.4, "timestamped log" is not a good verb phrase.
	"maintain a timestamped log of" would be a better replacement.
- Last paragraph in section, where is the batch file sent?

In Section 2.7, I'm having a hard time understanding which traffic is
intended to be subject to the Outgoing Policies and the Incoming Policies.
Expanding each of those two bullets to explain what traffic is subject
to each class of policies would help.

Section 3.2.2.2 uses 192.0.0.2/32 as an example IP address for the
B4.  That section should also cross-reference Section 5.7 on RFC 6333
on IP address assignment to B4s, as other IP addresses may be used.

idnits 2.12.13 found a tiny nit - draft-ietf-pcp-base is now at
version 28.

Thanks,
--David
----------------------------------------------------
David L. Black, Distinguished Engineer
EMC Corporation, 176 South St., Hopkinton, MA=A0 01748
+1 (508) 293-7953=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 FAX: +1 (508) 293-778=
6
david.black@emc.com=A0=A0=A0=A0=A0=A0=A0 Mobile: +1 (978) 394-7754
----------------------------------------------------



From randy@qti.qualcomm.com  Mon Oct 15 19:50:53 2012
Return-Path: <randy@qti.qualcomm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DDDBB1F0C93 for <ietf@ietfa.amsl.com>; Mon, 15 Oct 2012 19:50:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cS4wak++8M6s for <ietf@ietfa.amsl.com>; Mon, 15 Oct 2012 19:50:46 -0700 (PDT)
Received: from wolverine01.qualcomm.com (wolverine01.qualcomm.com [199.106.114.254]) by ietfa.amsl.com (Postfix) with ESMTP id 11F261F0C92 for <ietf@ietf.org>; Mon, 15 Oct 2012 19:50:46 -0700 (PDT)
X-IronPort-AV: E=McAfee;i="5400,1158,6866"; a="251501071"
Received: from ironmsg02-l.qualcomm.com ([172.30.48.16]) by wolverine01.qualcomm.com with ESMTP; 15 Oct 2012 19:50:30 -0700
X-IronPort-AV: E=Sophos;i="4.80,593,1344236400"; d="scan'208";a="125177394"
Received: from nasanexhc08.na.qualcomm.com ([172.30.39.7]) by ironmsg02-L.qualcomm.com with ESMTP/TLS/RC4-SHA; 15 Oct 2012 19:50:30 -0700
Received: from [99.111.97.136] (172.30.39.5) by qcmail1.qualcomm.com (172.30.39.7) with Microsoft SMTP Server (TLS) id 14.2.318.1; Mon, 15 Oct 2012 19:50:28 -0700
Message-ID: <p06240628cca279fdf657@[99.111.97.136]>
In-Reply-To: <94279462-0f48-41ec-933a-a7ac22ba204a@email.android.com>
References: <94279462-0f48-41ec-933a-a7ac22ba204a@email.android.com>
X-Mailer: Eudora for Mac OS X
Date: Mon, 15 Oct 2012 19:46:36 -0700
To: Michael Richardson {quigon} <mcr@sandelman.ca>, <ietf@ietf.org>
From: Randall Gellens <randy@qti.qualcomm.com>
Subject: Format=flowed quoting (was "Re: IETF...the unconference of SDOs")
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]
X-Mailman-Approved-At: Tue, 16 Oct 2012 08:52:20 -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: Tue, 16 Oct 2012 05:15:02 -0000

At 9:12 AM -0400 9/5/12, Michael Richardson {quigon} wrote:

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

I just noticed this assertion, which is quite false.  Format=flowed 
protects and preserved quoting.  It's the only way to avoid ludicrous 
and impossible to read quoting (which happens after quoted passages 
get line-wrapped at odd points).  Also, as far as I know, Exchange 
does not support format=flowed at all.  My understanding is that it 
insists on HTML quoting, which is entirely different.

-- 
Randall Gellens
Opinions are personal;    facts are suspect;    I speak for myself only
-------------- Randomly selected tag: ---------------
Once a job is fouled up, anything done to improve it only makes
it worse.

From david.black@emc.com  Tue Oct 16 06:35:10 2012
Return-Path: <david.black@emc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 20A1B21F8862; Tue, 16 Oct 2012 06:35:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.677
X-Spam-Level: 
X-Spam-Status: No, score=-102.677 tagged_above=-999 required=5 tests=[AWL=-0.078, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jsO32EAr7XPK; Tue, 16 Oct 2012 06:35:09 -0700 (PDT)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id BE3AC21F8843; Tue, 16 Oct 2012 06:35:08 -0700 (PDT)
Received: from hop04-l1d11-si02.isus.emc.com (HOP04-L1D11-SI02.isus.emc.com [10.254.111.55]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q9GDZ7Cb006594 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 16 Oct 2012 09:35:07 -0400
Received: from mailhub.lss.emc.com (mailhubhoprd02.lss.emc.com [10.254.221.253]) by hop04-l1d11-si02.isus.emc.com (RSA Interceptor); Tue, 16 Oct 2012 09:34:53 -0400
Received: from mxhub29.corp.emc.com (mxhub29.corp.emc.com [128.222.70.169]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q9GDYrPc027947; Tue, 16 Oct 2012 09:34:53 -0400
Received: from mx15a.corp.emc.com ([169.254.1.83]) by mxhub29.corp.emc.com ([128.222.70.169]) with mapi; Tue, 16 Oct 2012 09:34:53 -0400
From: "Black, David" <david.black@emc.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Date: Tue, 16 Oct 2012 09:34:51 -0400
Subject: RE: Last Call: <draft-ietf-storm-iser-12.txt> (iSCSI Extensions for RDMA	Specification) to Proposed Standard
Thread-Topic: Last Call: <draft-ietf-storm-iser-12.txt> (iSCSI Extensions for RDMA	Specification) to Proposed Standard
Thread-Index: Ac2lX31I32J7Gj+hT5yYefxwCndKkwGQw7UQ
Message-ID: <8D3D17ACE214DC429325B2B98F3AE7120DFAEFE5@MX15A.corp.emc.com>
References: <20121008141321.3098.10116.idtracker@ietfa.amsl.com>
In-Reply-To: <20121008141321.3098.10116.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
X-Mailman-Approved-At: Tue, 16 Oct 2012 08:52:20 -0700
Cc: "Black, David" <david.black@emc.com>, "storm@ietf.org" <storm@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Oct 2012 13:35:10 -0000

For those interested in what has changed in this draft by comparison
to the specification of iSER in RFC 5046, here's a reasonably readable
diff that shows the text changes:

http://www.stiemerling.org/ietf/storm-review/diff-rfc5046-to-iser.html

and the edited version of RFC 5046 on which this was based

http://www.stiemerling.org/ietf/storm-review/rfc5046-edited.txt

All of the content of RFC 5046 is preserved in that version, but the
changes to improve the diff include swapping the order of sections 1
and 2 in order to match the storm-iser draft, and taking out page
gutters that confuse the IETF diff tool.

And many thanks to our AD (Martin Stiemerling) for hosting this on his
web site.

FYI,
--David

> -----Original Message-----
> From: ietf-announce-bounces@ietf.org [mailto:ietf-announce-bounces@ietf.o=
rg]
> On Behalf Of The IESG
> Sent: Monday, October 08, 2012 10:13 AM
> To: IETF-Announce
> Cc: storm@ietf.org
> Subject: Last Call: <draft-ietf-storm-iser-12.txt> (iSCSI Extensions for =
RDMA
> Specification) to Proposed Standard
>=20
>=20
> The IESG has received a request from the STORage Maintenance WG (storm)
> to consider the following document:
> - 'iSCSI Extensions for RDMA Specification'
>   <draft-ietf-storm-iser-12.txt> as Proposed Standard
>=20
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2012-10-22. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
>=20
> Abstract
>=20
>=20
>    iSCSI Extensions for RDMA provides the RDMA data transfer capability
>    to iSCSI by layering iSCSI on top of an RDMA-Capable Protocol.  An
>    RDMA-Capable Protocol provides RDMA Read and Write services, which
>    enable data to be transferred directly into SCSI I/O Buffers without
>    intermediate data copies.  This document describes the extensions to
>    the iSCSI protocol to support RDMA services as provided by an RDMA-
>    Capable Protocol.
>=20
>    This document obsoletes RFC 5046.
>=20
>=20
>=20
>=20
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-storm-iser/
>=20
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-storm-iser/ballot/
>=20
>=20
> No IPR declarations have been submitted directly on this I-D.
>=20
>=20


From randy@psg.com  Tue Oct 16 10:20:36 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 0B3D921F89E1 for <ietf@ietfa.amsl.com>; Tue, 16 Oct 2012 10:20:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.192
X-Spam-Level: 
X-Spam-Status: No, score=-1.192 tagged_above=-999 required=5 tests=[AWL=-1.193, BAYES_50=0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4DKHP9A3XKXm for <ietf@ietfa.amsl.com>; Tue, 16 Oct 2012 10:20:35 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id ACD3A21F89DF for <ietf@ietf.org>; Tue, 16 Oct 2012 10:19:59 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=rair.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.80 (FreeBSD)) (envelope-from <randy@psg.com>) id 1TOAo9-000J2Y-Ns; Tue, 16 Oct 2012 17:19:58 +0000
Date: Tue, 16 Oct 2012 07:19:56 -1000
Message-ID: <m2fw5egwqr.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Jari Arkko <jari.arkko@piuha.net>
Subject: Re: I-D Action: draft-jaeggli-interim-observations-00.txt
In-Reply-To: <507D7A8C.1090201@piuha.net>
References: <042001cdab1d$df26b6b0$9d742410$@olddog.co.uk> <507D7A8C.1090201@piuha.net>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Cc: IETF 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: Tue, 16 Oct 2012 17:20:36 -0000

> o Co-location with RIPE appeared useful. I agree with you Joel that
>   tighter packing would have made a difference. I met some people who
>   noted they will not attend, but probably would have attended if it
>   was during the week. Co-locating individual WG interims with RIPEs
>   and NANOGs seems like a useful concept to consider in the future.

ripe/foonog would not appreciate a meeting in schedule conflict.  would
ietf appreciate a foonog meeting scheduled in conflict with and at the
same venue as an ietf meeting?

fwiw, sidr has met adjacent to a few foonogs and it was quite worthwhile
to have the extra ops that brought in.  i wonder if it would be good to
have a sidr meeting adjacent to a security meeting.  oops, we did that
too i think.

> o LIMs will not create a new big funding source for the IETF. We
>   should also right-size our organization for the task at hand. 30,
>   50, or even 100 people could probably be handled as part of the
>   RIPE meeting, and might have been something that the RIPE
>   registration system and agenda could have accommodated, or have
>   someone sponsor a room and leave the rest to participants.

foonog meeting coordination folk are generally very accommodating and
generous.  but beware that, often due to association with organizations
which have a monopoly on scarce intergers and thus pre-crash budget
contraints, foonogs often meet at expensive venues.

randy

From jari.arkko@piuha.net  Tue Oct 16 11:04:27 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 440D321F8747 for <ietf@ietfa.amsl.com>; Tue, 16 Oct 2012 11:04:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.359
X-Spam-Level: 
X-Spam-Status: No, score=-98.359 tagged_above=-999 required=5 tests=[AWL=4.240, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Swuwg9MCsBmO for <ietf@ietfa.amsl.com>; Tue, 16 Oct 2012 11:04:26 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by ietfa.amsl.com (Postfix) with ESMTP id 431EC21F8740 for <ietf@ietf.org>; Tue, 16 Oct 2012 11:04:26 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 8D1A82CF37; Tue, 16 Oct 2012 21:04:25 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DBLYXidb5P6Z; Tue, 16 Oct 2012 21:04:25 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id E2B3D2CC56; Tue, 16 Oct 2012 21:04:24 +0300 (EEST)
Message-ID: <507DA1A8.5000502@piuha.net>
Date: Tue, 16 Oct 2012 21:04:24 +0300
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20121011 Thunderbird/16.0.1
MIME-Version: 1.0
To: Randy Bush <randy@psg.com>
Subject: Re: I-D Action: draft-jaeggli-interim-observations-00.txt
References: <042001cdab1d$df26b6b0$9d742410$@olddog.co.uk> <507D7A8C.1090201@piuha.net> <m2fw5egwqr.wl%randy@psg.com>
In-Reply-To: <m2fw5egwqr.wl%randy@psg.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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: Tue, 16 Oct 2012 18:04:27 -0000

Randy,

> ripe/foonog would not appreciate a meeting in schedule conflict.  would
> ietf appreciate a foonog meeting scheduled in conflict with and at the
> same venue as an ietf meeting?
>

Agreed. But here's at least one idea on how to avoid that. Arrange an interim on a RIPE Friday afternoon, after the meetings have ended. Say, 2pm - 8pm. Long day and somewhat shorter WG time. But probably more doable for participants than a full Saturday. Other meetings may have similar scheduling opportunities.

Jari


From warren@kumari.net  Tue Oct 16 12:06:42 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 4A39A21F8A41 for <ietf@ietfa.amsl.com>; Tue, 16 Oct 2012 12:06:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.199
X-Spam-Level: 
X-Spam-Status: No, score=-102.199 tagged_above=-999 required=5 tests=[AWL=-0.200, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id um8cXT59M2YU for <ietf@ietfa.amsl.com>; Tue, 16 Oct 2012 12:06:39 -0700 (PDT)
Received: from vimes.kumari.net (smtp1.kumari.net [204.194.22.1]) by ietfa.amsl.com (Postfix) with ESMTP id 68C8711E808A for <ietf@ietf.org>; Tue, 16 Oct 2012 12:06:39 -0700 (PDT)
Received: from [10.196.196.235] (1-193.icannmeeting.org [199.91.193.1]) by vimes.kumari.net (Postfix) with ESMTPSA id 242B61B40038; Tue, 16 Oct 2012 15:06:36 -0400 (EDT)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.1 \(1498\))
Subject: Re: [IETF] I-D Action: draft-jaeggli-interim-observations-00.txt
From: Warren Kumari <warren@kumari.net>
In-Reply-To: <042501cdab1f$77f31e50$67d95af0$@olddog.co.uk>
Date: Tue, 16 Oct 2012 14:40:28 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <93145A39-4881-481F-A541-5C90EE73F30E@kumari.net>
References: <042001cdab1d$df26b6b0$9d742410$@olddog.co.uk> <m21ugzjtia.wl%randy@psg.com> <042501cdab1f$77f31e50$67d95af0$@olddog.co.uk>
To: adrian@olddog.co.uk
X-Mailer: Apple Mail (2.1498)
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: Tue, 16 Oct 2012 19:06:42 -0000

On Oct 15, 2012, at 5:53 PM, Adrian Farrel <adrian@olddog.co.uk> wrote:

>> ok, i am lost.  the draft is only an outline and has zero content?  =
is
>> it a quiz?
>=20
> Treat it like that and see if you can give Joel the right answers.
>=20
> For me: Did it make any difference to you that it was a LIM rather =
than simply a
> SIDR interim?

Yes -- because it was LIM multiple WGs met at the same time. This meant =
that OpSec and V6Ops conflicted with SIDR, and so I missed the SIDR =
meeting.

> Were logistics and resources worth the fee?

Personally I think so -- I have been involved in multiple interims, and =
the quality of the remote participation was (IMO) much better at the =
LIM. Having someone else (Meetecho) handle the audio / video was great=85

We (OpSec) were hoping to get more of the RIPE attendees (aka, =
operators) to show up and participate, but:
A: there was a gap between RIPE and the LIM,
B: the existence of the LIM was not announced far enough in advance for =
most RIPE attendees to change their plans
C: we (OpSec) did a poor job of announcing the fact that we would be =
meeting, and asking for operators to come participate.


> Should we hold future
> LIMs, or do the scheduling and other issues mean that normal interims =
are the
> way forward?

Sorry, but figuring this sort of thing out is what we pay *you* for=85

(aka, I don't know, to close to call).
W


>=20
> cheers,
> Adrian
>=20
>=20

--
What our ancestors would really be thinking, if they were alive today, =
is: "Why is it so dark in here?"

    -- (Terry Pratchett, Pyramids)



From sm@resistor.net  Tue Oct 16 14:50:11 2012
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 506611F0CA0 for <ietf@ietfa.amsl.com>; Tue, 16 Oct 2012 14:50:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.586
X-Spam-Level: 
X-Spam-Status: No, score=-102.586 tagged_above=-999 required=5 tests=[AWL=0.013, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FlBxlRtaYAw9 for <ietf@ietfa.amsl.com>; Tue, 16 Oct 2012 14:50:10 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id CD7751F0424 for <ietf@ietf.org>; Tue, 16 Oct 2012 14:50:10 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id q9GLo3dJ022829; Tue, 16 Oct 2012 14:50:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1350424209; bh=3EFl1Guh4yRGDtVSMOtmtWdjydxaNf81Qx8LT0fiG6Y=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=0wWvmc40qAbVlMAFjcFAeODH31Desm7hFSfS25LMnTjXHvcFAv/dR1hOa1Pq7Tl5c sS6xC5pRPX6zjq/LxXgFhCd8REydm+ZmL+TunBHGdQE942FlAI5n32jefI8b9Ps0AQ HEtMiulX9UZk9gWyykrvQj1rGI5UqdziL9provr8=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1350424209; i=@resistor.net; bh=3EFl1Guh4yRGDtVSMOtmtWdjydxaNf81Qx8LT0fiG6Y=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=VFfJ+XTBHUg0R6vKqxAGh1+5MRVIhyZJQExWAHLa0Dr6/PAyR+Lgeye3lo8OVxn/n EhlZaV6l7a9wiiVN1DkEYZnVNhCPCfhwEwjHgNeMSlg+JWZAlE9r4FAGjIoO2APKYP nAMwObiXlywDqrmXetYIBZfxGmASHwbQurn6Pl9Y=
Message-Id: <6.2.5.6.2.20121016143029.09ff45b0@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 16 Oct 2012 14:43:56 -0700
To: Olafur Gudmundsson <ogud@ogud.com>
From: SM <sm@resistor.net>
Subject: Re: [dnsext] Last Call: <draft-ietf-dnsext-rfc2671bis-edns0-09.txt> (Extension Mechanisms for DNS (EDNS(0))) to Internet Standard
In-Reply-To: <506DBE9B.3070209@ogud.com>
References: <20120930145325.21053.67854.idtracker@ietfa.amsl.com> <56DB6FE506A144D1183B93A8@JcK-HP8200.jck.com> <506B01D1.9080708@ogud.com> <8F3DCBA9A3AF566810CD1061@JcK-HP8200.jck.com> <506B6BE9.2000805@ogud.com> <20121003011556.526A82873A5E@drugs.dv.isc.org> <506DBE9B.3070209@ogud.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: draft-ietf-dnsext-rfc2671bis-edns0.all@tools.ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Oct 2012 21:50:11 -0000

Hi Olafur,

I posted the following question about the draft about two weeks ago [1]:

   "On publication of draft-ietf-dnsext-rfc2671bis-edns0-09, will it be
    part of STD 13?"

I did not see any comments from the WG about that.  I had an off-list 
exchange with the RFC Series Editor about STDs.  The question seems 
like an IETF matter.  Has this question been discussed by the WG, and 
if so, what was the conclusion?

Regards,
-sm

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


From ogud@ogud.com  Tue Oct 16 18:13:39 2012
Return-Path: <ogud@ogud.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 76F9621F84D9 for <ietf@ietfa.amsl.com>; Tue, 16 Oct 2012 18:13:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0bT6ZuH5ltkg for <ietf@ietfa.amsl.com>; Tue, 16 Oct 2012 18:13:34 -0700 (PDT)
Received: from smtp142.ord.emailsrvr.com (smtp142.ord.emailsrvr.com [173.203.6.142]) by ietfa.amsl.com (Postfix) with ESMTP id 57E3B21F85F4 for <ietf@ietf.org>; Tue, 16 Oct 2012 18:13:34 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp14.relay.ord1a.emailsrvr.com (SMTP Server) with ESMTP id B461931809F; Tue, 16 Oct 2012 21:13:33 -0400 (EDT)
X-Virus-Scanned: OK
Received: by smtp14.relay.ord1a.emailsrvr.com (Authenticated sender: ogud-AT-ogud.com) with ESMTPSA id 2286B31809C;  Tue, 16 Oct 2012 21:13:31 -0400 (EDT)
Message-ID: <507E063A.1020304@ogud.com>
Date: Tue, 16 Oct 2012 21:13:30 -0400
From: Olafur Gudmundsson <ogud@ogud.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120907 Thunderbird/15.0.1
MIME-Version: 1.0
To: SM <sm@resistor.net>
Subject: Re: [dnsext] Last Call: <draft-ietf-dnsext-rfc2671bis-edns0-09.txt> (Extension Mechanisms for DNS (EDNS(0))) to Internet Standard
References: <20120930145325.21053.67854.idtracker@ietfa.amsl.com> <56DB6FE506A144D1183B93A8@JcK-HP8200.jck.com> <506B01D1.9080708@ogud.com> <8F3DCBA9A3AF566810CD1061@JcK-HP8200.jck.com> <506B6BE9.2000805@ogud.com> <20121003011556.526A82873A5E@drugs.dv.isc.org> <506DBE9B.3070209@ogud.com> <6.2.5.6.2.20121016143029.09ff45b0@resistor.net>
In-Reply-To: <6.2.5.6.2.20121016143029.09ff45b0@resistor.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: draft-ietf-dnsext-rfc2671bis-edns0.all@tools.ietf.org, ietf@ietf.org, Olafur Gudmundsson <ogud@ogud.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Oct 2012 01:13:39 -0000

On 16/10/2012 17:43, SM wrote:
> Hi Olafur,
>
> I posted the following question about the draft about two weeks ago [1]:
>
>   "On publication of draft-ietf-dnsext-rfc2671bis-edns0-09, will it be
>    part of STD 13?"
>
> I did not see any comments from the WG about that.  I had an off-list 
> exchange with the RFC Series Editor about STDs.  The question seems 
> like an IETF matter.  Has this question been discussed by the WG, and 
> if so, what was the conclusion?
>

It was not explicitly discussed.

     Olafur


> Regards,
> -sm
>
> 1. http://www.ietf.org/mail-archive/web/ietf/current/msg75156.html
>


From fred@cisco.com  Tue Oct 16 20:31:17 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 96E8421F8589 for <ietf@ietfa.amsl.com>; Tue, 16 Oct 2012 20:31:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.333
X-Spam-Level: 
X-Spam-Status: No, score=-110.333 tagged_above=-999 required=5 tests=[AWL=0.266, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vR+ymTHdWdXc for <ietf@ietfa.amsl.com>; Tue, 16 Oct 2012 20:31:17 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) by ietfa.amsl.com (Postfix) with ESMTP id E8A3F21F8587 for <ietf@ietf.org>; Tue, 16 Oct 2012 20:31:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=924; q=dns/txt; s=iport; t=1350444677; x=1351654277; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=7F0QywXqP4LficiqtY4IlDyuMj6DhqvvNTa0Zf2zVdE=; b=OFhG39LY/dDmCt3tr7Asl8wrHlWkcICRlEcQcvINXXhinwDasUoBFuEq kqqg+Sv7LgnTk9Zk0kxL1/0d4dzEN7FJM231lRh1VrFRPN22UE88t1JPu JwYQRGu8wWB+yPnrva4GLchujMsz/VghPXE1RyfZbPPIcrz8gApJqDDIy 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av4EAEQmflCtJV2a/2dsb2JhbABFwCaBCIIgAQEBAwESASc/EAIBCCIUEDIlAQEEDg0ah1wGmy6RbI4vi0+FYGADpDKBa4JgDYIX
X-IronPort-AV: E=Sophos;i="4.80,597,1344211200"; d="scan'208";a="132165598"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by rcdn-iport-1.cisco.com with ESMTP; 17 Oct 2012 03:31:08 +0000
Received: from xhc-rcd-x09.cisco.com (xhc-rcd-x09.cisco.com [173.37.183.83]) by rcdn-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id q9H3V8Fb018187 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 17 Oct 2012 03:31:08 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.68]) by xhc-rcd-x09.cisco.com ([173.37.183.83]) with mapi id 14.02.0318.001; Tue, 16 Oct 2012 22:31:08 -0500
From: "Fred Baker (fred)" <fred@cisco.com>
To: Randy Bush <randy@psg.com>
Subject: Re: I-D Action: draft-jaeggli-interim-observations-00.txt
Thread-Topic: I-D Action: draft-jaeggli-interim-observations-00.txt
Thread-Index: Ac2rHZD5/kD+Gd//IkWmURuL51Vd1gAvbTEAAARGWAAAFVfPgA==
Date: Wed, 17 Oct 2012 03:31:08 +0000
Message-ID: <8C48B86A895913448548E6D15DA7553B17C734@xmb-rcd-x09.cisco.com>
References: <042001cdab1d$df26b6b0$9d742410$@olddog.co.uk> <507D7A8C.1090201@piuha.net> <m2fw5egwqr.wl%randy@psg.com>
In-Reply-To: <m2fw5egwqr.wl%randy@psg.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.66.255.140]
x-tm-as-product-ver: SMEX-10.2.0.1135-7.000.1014-19276.004
x-tm-as-result: No--33.202100-8.000000-31
x-tm-as-user-approved-sender: No
x-tm-as-user-blocked-sender: No
Content-Type: text/plain; charset="us-ascii"
Content-ID: <A311293E479FFF47BA0B62595B02BE8D@cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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, 17 Oct 2012 03:31:18 -0000

On Oct 17, 2012, at 4:19 AM, Randy Bush wrote:

>> o Co-location with RIPE appeared useful. I agree with you Joel that
>>  tighter packing would have made a difference. I met some people who
>>  noted they will not attend, but probably would have attended if it
>>  was during the week. Co-locating individual WG interims with RIPEs
>>  and NANOGs seems like a useful concept to consider in the future.
>=20
> ripe/foonog would not appreciate a meeting in schedule conflict.  would i=
etf appreciate a foonog meeting scheduled in conflict with and at the same =
venue as an ietf meeting?

One hopes he was looking for constructive engagement, such as IETF and IRTF=
 do during an IETF meeting. The interspersed meeting is on the same agenda =
as all of the other meetings, and not on a separate track. The IETF doesn't=
 promise IRTF meeting slots, but if slots are available, it makes them avai=
lable.=

From sm@resistor.net  Tue Oct 16 23:49:52 2012
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2A24021F875B; Tue, 16 Oct 2012 23:49:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.586
X-Spam-Level: 
X-Spam-Status: No, score=-102.586 tagged_above=-999 required=5 tests=[AWL=0.013, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0tWCEb5eOqwv; Tue, 16 Oct 2012 23:49:51 -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 419F921F8759; Tue, 16 Oct 2012 23:49:51 -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 q9H6njW4003886; Tue, 16 Oct 2012 23:49:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1350456589; bh=B5KpwFVLvIZw7t6eb86g1o2dQ0bqbV//sR1QstoAQHw=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=P9AIUhC0Go6rtLRUEfc6JPXkz1xoJ9x4UCGJ0OEtvhACIQrjtqFj09YjgfGwiZCwu go5hYHfLupnHJXzcSBgEtvfUQTXdVA9tTIz/w9HzB4RuMeo6SJnjoyrvIPrgtf9Fn7 ZaJRAUx/yYQNknyBPQ1+26T2Y6U65FVvbAupPfF8=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1350456589; i=@resistor.net; bh=B5KpwFVLvIZw7t6eb86g1o2dQ0bqbV//sR1QstoAQHw=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=4AwnAgHfmzhKWaMaTFyb0OBZbGKrXQlYwv+D0VgM62lLp74GonBFmrnUNb2RaTGBh bInKXf5lCLJFNdo0ZBuhEb990NQGuM8NQv/Bo+5S84Csu/XJQu9ysWlKA1WceUvZdM opEyi3c2bLdK08l4UKU68XRBMfQ8oU4krzWrdmtM=
Message-Id: <6.2.5.6.2.20121016223423.09e46058@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 16 Oct 2012 23:48:18 -0700
To: iesg@ietf.org, rsoc@iab.org
From: SM <sm@resistor.net>
Subject: Re: [dnsext] Last Call: <draft-ietf-dnsext-rfc2671bis-edns0-09.txt> (Extension Mechanisms for DNS (EDNS(0))) to Internet Standard
In-Reply-To: <507E063A.1020304@ogud.com>
References: <20120930145325.21053.67854.idtracker@ietfa.amsl.com> <56DB6FE506A144D1183B93A8@JcK-HP8200.jck.com> <506B01D1.9080708@ogud.com> <8F3DCBA9A3AF566810CD1061@JcK-HP8200.jck.com> <506B6BE9.2000805@ogud.com> <20121003011556.526A82873A5E@drugs.dv.isc.org> <506DBE9B.3070209@ogud.com> <6.2.5.6.2.20121016143029.09ff45b0@resistor.net> <507E063A.1020304@ogud.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Oct 2012 06:49:52 -0000

Hello,
At 18:13 16-10-2012, Olafur Gudmundsson wrote:
>It was not explicitly discussed.

The IESG received a request from the DNSEXT WG to create an Internet 
Standard [1].  The IESG solicited comments.  As this is the second 
last Call I presume that someone might know whether that Internet 
Standard will be STD 13 or something else.  Could the  information be shared?

Are there any guidelines about the publication of Internet Standards, 
i.e. how are STDs assigned and who does the assignment?

Regards,
-sm

P.S. According to mx.ams1.isc.org mgraff@isc.org is not a valid email address.

1. http://www.ietf.org/mail-archive/web/ietf-announce/current/msg10742.html  


From ron.even.tlv@gmail.com  Wed Oct 17 02:59:38 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 C43CC21F87E8; Wed, 17 Oct 2012 02:59:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GU8HNmB6G-HD; Wed, 17 Oct 2012 02:59:37 -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 35B8A21F87B8; Wed, 17 Oct 2012 02:59:37 -0700 (PDT)
Received: by mail-wi0-f178.google.com with SMTP id hr7so345936wib.13 for <multiple recipients>; Wed, 17 Oct 2012 02:59:36 -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=lv3+m4lyJZ+XxnK3cbQ+l0HL+WVvDL7cbZq4IJ+ZdNA=; b=j0OEdNZbYF5ZMR/65mS0FuHlBaG2WB9eS6xNtIpgzCJu4hxuANSaKST8P9G38nmhum sSUkM/SzI3vjzAgR6Szocd/3rOXqlrnMJFQ2qOxzOB9iyGInV1Tj+BKJ9CneMeEvlm5g djVF/eiYuuXhX+VrDip/doqojITF4S6N5xV2z0Sx1MjaV7toSet4mu7PlGhL4CJt+6O5 +3cse2nPaWEd6fu3xCFCblJzPw2wEOaxCWnd+ZDUqK1dwDojolz1QpdkXeN6rZqNSLZ2 jUgwv+x6tIj+WjMhqRgfLQcAQB8Y2avZmi4PWTfqq8qM0AiakT6VtXgdnROXxydA2yRB asTA==
Received: by 10.180.84.41 with SMTP id v9mr2987398wiy.8.1350467976392; Wed, 17 Oct 2012 02:59:36 -0700 (PDT)
Received: from RoniE (bzq-79-176-243-9.red.bezeqint.net. [79.176.243.9]) by mx.google.com with ESMTPS id cl8sm23567588wib.10.2012.10.17.02.59.33 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 17 Oct 2012 02:59:35 -0700 (PDT)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: <draft-leiba-5322upd-from-group.all@tools.ietf.org>
Subject: Gen-ART LC review of draft-leiba-5322upd-from-group-06
Date: Wed, 17 Oct 2012 11:57:22 +0200
Message-ID: <010301cdac4d$cfa70060$6ef50120$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0104_01CDAC5E.93306CA0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac2sTc0q0twAdGB/TEqBQ74s7zgemw==
Content-Language: en-us
Cc: gen-art@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Oct 2012 09:59:38 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0104_01CDAC5E.93306CA0
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-leiba-5322upd-from-group-06

Reviewer: Roni Even

Review Date:2012-10-17

IETF LC End Date: 2012-11-6

IESG Telechat date:

 

Summary: This draft is almost ready for publication as a standard track RFC.

 

 

Major issues:

 

Minor issues:

1.	It is not clear from the draft what the use case for using the group
construct is.  Section 3 talks about the issues with using the group
construct and recommend limited use, but this is the only information.
2.	Section 2.1 says "If the sender field uses group syntax, the group
MUST NOT contains more than one mailbox."  Why use a group name for a single
mailbox?

 

Nits/editorial comments:

 


------=_NextPart_000_0104_01CDAC5E.93306CA0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><META =
HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:10.0pt;
	margin-left:0in;
	line-height:115%;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:37364675;
	mso-list-type:hybrid;
	mso-list-template-ids:-1149338328 67698703 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><a =
name=3D"OLE_LINK1"></a><a name=3D"OLE_LINK2">I am the assigned Gen-ART =
reviewer for this draft. For background on Gen-ART, please see the FAQ =
at &lt;</a><a =
href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq" =
target=3D"_blank">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq=
</a>&gt;.<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>Please resolve these comments along with any other =
Last Call comments you may receive.<o:p></o:p></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Document: =
</span><span style=3D'font-family:"Courier =
New"'>draft-leiba-5322upd-from-group-06</span><o:p></o:p></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Reviewer: =
Roni Even<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Review =
Date:2012&#8211;10&#8211;17<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;11&#8211;6<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</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'> a =
standard track </span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>RFC</span><=
span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>.<o:p></o:p=
></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Major =
issues:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Minor =
issues:<o:p></o:p></span></p><ol style=3D'margin-top:0in' start=3D1 =
type=3D1><li class=3DMsoNormal style=3D'mso-list:l0 level1 lfo1'>It is =
not clear from the draft what the use case for using the group construct =
is.&nbsp; Section 3 talks about the issues with using the group =
construct and recommend limited use, but this is the only =
information.<o:p></o:p></li><li class=3DMsoNormal style=3D'mso-list:l0 =
level1 lfo1'>Section 2.1 says &#8220;If the sender field uses group =
syntax, the group MUST NOT contains more than one mailbox.&#8221;&nbsp; =
Why use a group name for a single mailbox?<o:p></o:p></li></ol><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoNormal>Nits/editorial =
comments:<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_0104_01CDAC5E.93306CA0--


From ron.even.tlv@gmail.com  Wed Oct 17 03:03:21 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 4706D21F881E; Wed, 17 Oct 2012 03:03:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qzawPmXt0Cof; Wed, 17 Oct 2012 03:03:19 -0700 (PDT)
Received: from mail-wi0-f172.google.com (mail-wi0-f172.google.com [209.85.212.172]) by ietfa.amsl.com (Postfix) with ESMTP id A730921F87F1; Wed, 17 Oct 2012 03:03:18 -0700 (PDT)
Received: by mail-wi0-f172.google.com with SMTP id hq12so365189wib.13 for <multiple recipients>; Wed, 17 Oct 2012 03:03:17 -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:x-mailer:thread-index:content-language; bh=GcglzIWPqoOBssYYsj9+9qoqKYSCCSxp1o4dBNg5cZU=; b=oWyVIW9cfsnlTEtZTSSNQdIooWBmwJ2N7H+f2iB3/Ud1Asmo+eDXAF9f2h6cqRbFZH YpWksz41EZ+474gYhlOhJeFcZafRVDiLKioU1XKU1euJziBwzanswwjL7harDBgWcu/1 ph0qvVAKQC80MWyO1dWQSbtB04mMOXEGYX6/mTHZq/ZABsMLPHGKBNzJU7gTp20egIu5 knsu9AKMAJEZhavcgC83aFZ+QZzZu5XNmLo13yFmEcwnxh8o4xUjQAK8Bs4SXHcgKtcr 5FtVz0G9OCc73SBZtGPHsnQdwsNpItGJQKCFHOg+tAEGyF01iBD42JbZT19PFoqlNADM RdHg==
Received: by 10.180.19.71 with SMTP id c7mr3036359wie.2.1350468197685; Wed, 17 Oct 2012 03:03:17 -0700 (PDT)
Received: from RoniE (bzq-79-176-243-9.red.bezeqint.net. [79.176.243.9]) by mx.google.com with ESMTPS id dm3sm26767231wib.3.2012.10.17.03.03.14 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 17 Oct 2012 03:03:16 -0700 (PDT)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: "'Malis, Andrew G \(Andy\)'" <andrew.g.malis@verizon.com>, <draft-ietf-ccamp-rfc5787bis.all@tools.ietf.org>
References: <002101cd7997$a5204330$ef60c990$@gmail.com> <CC98C05A.2FC85%andrew.g.malis@one.verizon.com>
In-Reply-To: <CC98C05A.2FC85%andrew.g.malis@one.verizon.com>
Subject: RE: Gen-ART LC review of draft-ietf-ccamp-rfc5787bis-05
Date: Wed, 17 Oct 2012 12:01:03 +0200
Message-ID: <010801cdac4e$5328ecf0$f97ac6d0$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0109_01CDAC5F.16B34390"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQKvrrCCYTySHJIE6oYZ/BaFSZDU3pX5PyvA
Content-Language: en-us
Cc: gen-art@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Oct 2012 10:03:21 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0109_01CDAC5F.16B34390
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Andy,

Thanks

Roni

 

From: Malis, Andrew G (Andy) [mailto:andrew.g.malis@verizon.com] 
Sent: 09 October, 2012 2:55 AM
To: Roni Even; draft-ietf-ccamp-rfc5787bis.all@tools.ietf.org
Cc: ietf@ietf.org; gen-art@ietf.org; Malis, Andrew G (Andy)
Subject: Re: Gen-ART LC review of draft-ietf-ccamp-rfc5787bis-05

 

Roni,

 

Thanks for your review, and sorry for the delay on the response, but we've
also been working on incorporating other changes to the draft as well. 

 

To answer your question on section 6.1, that was a good catch. That should
have said "other than the first", rather than "preceding the first". This
will be corrected.

 

To answer your question on section 10, the text is repeated in the
subsections to make life easier for IANA, since they would probably have
replicated it themselves anyway in the three registry listings.

 

On your last comment, we agree with you that the more familiar reader will
not have a problem.

 

Thanks again,

Andy

 

From: Roni Even <ron.even.tlv@gmail.com>
Date: Monday, August 13, 2012 14:07 
To: "draft-ietf-ccamp-rfc5787bis.all@tools.ietf.org"
<draft-ietf-ccamp-rfc5787bis.all@tools.ietf.org>
Cc: "ietf@ietf.org" <ietf@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>
Subject: Gen-ART LC review of draft-ietf-ccamp-rfc5787bis-05
Resent-To: <acee.lindem@ericsson.com>, Adrian Farrell <adrian@olddog.co.uk>,
Andrew Malis <andrew.g.malis@verizon.com>, <dbrungard@att.com>,
<dimitri.papadimitriou@alcatel-lucent.com>, <lberger@labn.net>

 

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-ccamp-rfc5787bis-05.

Reviewer: Roni Even

Review Date:2012-8-12

IETF LC End Date: 2012-8-17

IESG Telechat date:

 

Summary: This draft is almost ready for publication as a standard track RFC.

 

 

Major issues:

 

Minor issues:

In section 6.1 " If specified more than once, instances preceding the first
will be ignored and condition SHOULD be logged for possible action by the
network operator."  I am not sure what is meant by preceding the first.

 

 

Nits/editorial comments:

 

1.	The following note appears in section 10.1, 10.2 and 10.3. "Note
that the same values for the Inter-RA Export Upward sub-TLV and the Inter-RA
Export Downward Sub-TLV MUST be used when they appear in the Link TLV, Node
Attribute TLV, and Router Address TLV." - why not have it in section 10
before section 10.1.
2.	I saw in appendix  B that one of the changes from RFC 5787 was to
clarify the terminology before defining extensions, I would have found it
easier to read if the ASON hierarchy and the relation to OSPF in section 2
were presented in figures. This was more an issue to me as a reader not
familiar with the terminology and I would like to think that the more
familiar reader will not have problem.

 


------=_NextPart_000_0109_01CDAC5F.16B34390
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><META =
HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family: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;}
@font-face
	{font-family:Verdana;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin-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;}
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.EmailStyle19
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle22
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:229272229;
	mso-list-template-ids:-65088188;}
@list l1
	{mso-list-id:715087181;
	mso-list-type:hybrid;
	mso-list-template-ids:-1205706658 -1668626108 67698713 67698715 =
67698703 67698713 67698715 67698703 67698713 67698715;}
@list l1:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-bidi-font-family:Calibri;}
@list l1:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l1:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l1:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
style=3D'color:#1F497D'>Andy,<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'>Thanks<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'>Roni<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#1F497D'><o:p>&nbsp;</o:p></span></p><div><div =
style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in'><p class=3DMsoNormal =
style=3D'margin-bottom:0in;margin-bottom:.0001pt;line-height:normal'><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"'> =
Malis, Andrew G (Andy) [mailto:andrew.g.malis@verizon.com] =
<br><b>Sent:</b> 09 October, 2012 2:55 AM<br><b>To:</b> Roni Even; =
draft-ietf-ccamp-rfc5787bis.all@tools.ietf.org<br><b>Cc:</b> =
ietf@ietf.org; gen-art@ietf.org; Malis, Andrew G =
(Andy)<br><b>Subject:</b> Re: Gen-ART LC review of =
draft-ietf-ccamp-rfc5787bis-05<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div><p class=3DMsoNormal><span =
style=3D'font-size:10.5pt;line-height:115%;font-family:"Verdana","sans-se=
rif";color:#08003F'>Roni,<o:p></o:p></span></p></div><div><p =
class=3DMsoNormal><span =
style=3D'font-size:10.5pt;line-height:115%;font-family:"Verdana","sans-se=
rif";color:#08003F'><o:p>&nbsp;</o:p></span></p></div><div><div><p =
class=3DMsoNormal><span =
style=3D'font-size:10.5pt;line-height:115%;font-family:"Verdana","sans-se=
rif";color:#08003F'>Thanks for your review, and sorry for the delay on =
the response, but we've&nbsp;also been working on incorporating other =
changes to the draft as =
well.&nbsp;<o:p></o:p></span></p></div></div><div><p =
class=3DMsoNormal><span =
style=3D'font-size:10.5pt;line-height:115%;font-family:"Verdana","sans-se=
rif";color:#08003F'><o:p>&nbsp;</o:p></span></p></div><div><p =
class=3DMsoNormal><span =
style=3D'font-size:10.5pt;line-height:115%;font-family:"Verdana","sans-se=
rif";color:#08003F'>To answer your question on section 6.1, that was a =
good catch. That should have said &quot;other than the first&quot;, =
rather than &quot;preceding the first&quot;. This will be =
corrected.<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:10.5pt;line-height:115%;font-family:"Verdana","sans-se=
rif";color:#08003F'><o:p>&nbsp;</o:p></span></p></div><div><p =
class=3DMsoNormal><span =
style=3D'font-size:10.5pt;line-height:115%;font-family:"Verdana","sans-se=
rif";color:#08003F'>To answer your question on section 10, the text is =
repeated in the subsections to make life easier for IANA, since they =
would probably have replicated it themselves anyway in the three =
registry listings.<o:p></o:p></span></p></div><div><p =
class=3DMsoNormal><span =
style=3D'font-size:10.5pt;line-height:115%;font-family:"Verdana","sans-se=
rif";color:#08003F'><o:p>&nbsp;</o:p></span></p></div><div><p =
class=3DMsoNormal><span =
style=3D'font-size:10.5pt;line-height:115%;font-family:"Verdana","sans-se=
rif";color:#08003F'>On your last comment, we agree with you that the =
more familiar reader will not have a =
problem.<o:p></o:p></span></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:10.5pt;line-height:115%;font-family:"Verdana","sans-se=
rif";color:#08003F'><o:p>&nbsp;</o:p></span></p></div><div><p =
class=3DMsoNormal><span =
style=3D'font-size:10.5pt;line-height:115%;font-family:"Verdana","sans-se=
rif";color:#08003F'>Thanks again,<o:p></o:p></span></p></div><div><p =
class=3DMsoNormal><span =
style=3D'font-size:10.5pt;line-height:115%;font-family:"Verdana","sans-se=
rif";color:#08003F'>Andy<o:p></o:p></span></p></div><div><p =
class=3DMsoNormal><span =
style=3D'font-size:10.5pt;line-height:115%;font-family:"Verdana","sans-se=
rif";color:#08003F'><o:p>&nbsp;</o:p></span></p></div><div =
style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in'><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;line-height:115%;font-family:"Tahoma","sans-ser=
if";color:black'>From: </span></b><span =
style=3D'font-size:10.0pt;line-height:115%;font-family:"Tahoma","sans-ser=
if";color:black'>Roni Even &lt;<a =
href=3D"mailto:ron.even.tlv@gmail.com">ron.even.tlv@gmail.com</a>&gt;<br>=
<b>Date: </b>Monday, August 13, 2012 14:07 <br><b>To: </b>&quot;<a =
href=3D"mailto:draft-ietf-ccamp-rfc5787bis.all@tools.ietf.org">draft-ietf=
-ccamp-rfc5787bis.all@tools.ietf.org</a>&quot; &lt;<a =
href=3D"mailto:draft-ietf-ccamp-rfc5787bis.all@tools.ietf.org">draft-ietf=
-ccamp-rfc5787bis.all@tools.ietf.org</a>&gt;<br><b>Cc: </b>&quot;<a =
href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a>&quot; &lt;<a =
href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a>&gt;, &quot;<a =
href=3D"mailto:gen-art@ietf.org">gen-art@ietf.org</a>&quot; &lt;<a =
href=3D"mailto:gen-art@ietf.org">gen-art@ietf.org</a>&gt;<br><b>Subject: =
</b>Gen-ART LC review of draft-ietf-ccamp-rfc5787bis-05<br><b>Resent-To: =
</b>&lt;<a =
href=3D"mailto:acee.lindem@ericsson.com">acee.lindem@ericsson.com</a>&gt;=
, Adrian Farrell &lt;<a =
href=3D"mailto:adrian@olddog.co.uk">adrian@olddog.co.uk</a>&gt;, Andrew =
Malis &lt;<a =
href=3D"mailto:andrew.g.malis@verizon.com">andrew.g.malis@verizon.com</a>=
&gt;, &lt;<a =
href=3D"mailto:dbrungard@att.com">dbrungard@att.com</a>&gt;, &lt;<a =
href=3D"mailto:dimitri.papadimitriou@alcatel-lucent.com">dimitri.papadimi=
triou@alcatel-lucent.com</a>&gt;, &lt;<a =
href=3D"mailto:lberger@labn.net">lberger@labn.net</a>&gt;<o:p></o:p></spa=
n></p></div><div><p class=3DMsoNormal><span =
style=3D'font-size:10.5pt;line-height:115%;font-family:"Verdana","sans-se=
rif";color:#08003F'><o:p>&nbsp;</o:p></span></p></div><div><div><p =
class=3DMsoNormal><span style=3D'color:#08003F'>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></span></p><p class=3DMsoNormal><span =
style=3D'color:#08003F'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoNormal><span style=3D'color:#08003F'>Please resolve these =
comments along with any other Last Call comments you may =
receive.<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#08003=
F'>&nbsp;</span><span style=3D'color:#08003F'><o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#08003=
F'>Document: </span><span =
style=3D'color:#08003F'>draft-ietf-ccamp-rfc5787bis-05.<o:p></o:p></span>=
</p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#08003=
F'>Reviewer: Roni Even</span><span =
style=3D'color:#08003F'><o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#08003=
F'>Review Date:2012&#8211;8&#8211;12</span><span =
style=3D'color:#08003F'><o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#08003=
F'>IETF LC End Date: 2012&#8211;8&#8211;17</span><span =
style=3D'color:#08003F'><o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#08003=
F'>IESG Telechat date:</span><span =
style=3D'color:#08003F'><o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#08003=
F'>&nbsp;</span><span style=3D'color:#08003F'><o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#08003=
F'>Summary: This draft is almost ready for publication as a standard =
track RFC.</span><span style=3D'color:#08003F'><o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#08003=
F'>&nbsp;</span><span style=3D'color:#08003F'><o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#08003=
F'>&nbsp;</span><span style=3D'color:#08003F'><o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#08003=
F'>Major issues:</span><span =
style=3D'color:#08003F'><o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#08003=
F'>&nbsp;</span><span style=3D'color:#08003F'><o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#08003=
F'>Minor issues:</span><span =
style=3D'color:#08003F'><o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'color:#08003F'>In section 6.1 &#8220; If specified more than =
once, instances preceding the first will be ignored and condition SHOULD =
be logged for possible action by the network operator.&#8221;&nbsp; I am =
not sure what is meant by preceding the first.<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'color:#08003F'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#08003=
F'>&nbsp;</span><span style=3D'color:#08003F'><o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#08003=
F'>Nits/editorial comments:</span><span =
style=3D'color:#08003F'><o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#08003=
F'>&nbsp;</span><span style=3D'color:#08003F'><o:p></o:p></span></p><ol =
style=3D'margin-top:0in' start=3D1 type=3D1><li class=3DMsoNormal =
style=3D'color:#08003F;mso-list:l1 level1 lfo3'>The following note =
appears in section 10.1, 10.2 and 10.3. &#8220;Note that the same values =
for the Inter-RA Export Upward sub-TLV and the Inter-RA Export Downward =
Sub-TLV MUST be used when they appear in the Link TLV, Node Attribute =
TLV, and Router Address TLV.&#8221; &#8211; why not have it in section =
10 before section 10.1.<o:p></o:p></li><li class=3DMsoNormal =
style=3D'color:#08003F;mso-list:l1 level1 lfo3'>I saw in appendix&nbsp; =
B that one of the changes from RFC 5787 was to clarify the terminology =
before defining extensions, I would have found it easier to read if the =
ASON hierarchy and the relation to OSPF in section 2 were presented in =
figures. This was more an issue to me as a reader not familiar with the =
terminology and I would like to think that the more familiar reader will =
not have problem.<o:p></o:p></li></ol><p class=3DMsoNormal><span =
style=3D'color:#08003F'>&nbsp;<o:p></o:p></span></p></div></div></div></b=
ody></html>
------=_NextPart_000_0109_01CDAC5F.16B34390--


From ned+ietf@mauve.mrochek.com  Wed Oct 17 11:19:18 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 31ABD21F85F4 for <ietf@ietfa.amsl.com>; Wed, 17 Oct 2012 11:19:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 77bGfkebmUzU for <ietf@ietfa.amsl.com>; Wed, 17 Oct 2012 11:19:17 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id AA03D21F860E for <ietf@ietf.org>; Wed, 17 Oct 2012 11:19:17 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OLIW8X82EO0008V7@mauve.mrochek.com> for ietf@ietf.org; Wed, 17 Oct 2012 11:14:15 -0700 (PDT)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OLDMMCPN8G00008S@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Wed, 17 Oct 2012 11:14:13 -0700 (PDT)
From: ned+ietf@mauve.mrochek.com
Message-id: <01OLIW8VNVCU00008S@mauve.mrochek.com>
Date: Wed, 17 Oct 2012 10:49:55 -0700 (PDT)
Subject: Re: Gen-ART LC review of draft-leiba-5322upd-from-group-06
In-reply-to: "Your message dated Wed, 17 Oct 2012 11:57:22 +0200" <010301cdac4d$cfa70060$6ef50120$@gmail.com>
MIME-version: 1.0
Content-type: TEXT/PLAIN
References: <010301cdac4d$cfa70060$6ef50120$@gmail.com>
To: Roni Even <ron.even.tlv@gmail.com>
Cc: gen-art@ietf.org, draft-leiba-5322upd-from-group.all@tools.ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Oct 2012 18:19:18 -0000

> Minor issues:

> 1.	It is not clear from the draft what the use case for using the group
> construct is.  Section 3 talks about the issues with using the group
> construct and recommend limited use, but this is the only information.

The main driver for this work is to add support for EAI downgrade mechanisms,
although a good case can also be made that the present restrictions on group
usage are silly, limiting and unnecessary. (The silliness arises from the
observation that these restrictions enforced by most agents in the field.)

It is far from clear that it makes sense to clutter up this very clean and
crisp specification with a bunch of EAI use case scenarios, especially since
this is an update to RFC 5322 that could in theory be merged into the main
document in the future. A decision taken long ago for both RFC 5321 and 5322
was to keep them as free of entanglements with technology that's layered on top
of them (e.g., MIME, various SMTP extensions) as possible.

In any case, the decision of the group was not to do this.

> 2.	Section 2.1 says "If the sender field uses group syntax, the group
> MUST NOT contains more than one mailbox."  Why use a group name for a single
> mailbox?

Why not? I'm sorry, but this question makes no sense. A group is a
characteristic attached to a collection of zero or more addresses. A group
containing a single member is every bit as valid as a construct as a group
containing 20 members. Or zero, for that matter.

				Ned

From dhc@dcrocker.net  Wed Oct 17 11:30:59 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 17DE421F8668; Wed, 17 Oct 2012 11:30:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.524
X-Spam-Level: 
X-Spam-Status: No, score=-6.524 tagged_above=-999 required=5 tests=[AWL=0.075,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9he2Gf80wuv6; Wed, 17 Oct 2012 11:30:58 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 7570D21F865D; Wed, 17 Oct 2012 11:30:58 -0700 (PDT)
Received: from [192.168.1.6] (adsl-67-127-59-48.dsl.pltn13.pacbell.net [67.127.59.48]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q9HIUrpt021073 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 17 Oct 2012 11:30:54 -0700
Message-ID: <507EF95D.5090007@dcrocker.net>
Date: Wed, 17 Oct 2012 11:30:53 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121005 Thunderbird/16.0
MIME-Version: 1.0
To: ned+ietf@mauve.mrochek.com
Subject: Re: Gen-ART LC review of draft-leiba-5322upd-from-group-06
References: <010301cdac4d$cfa70060$6ef50120$@gmail.com> <01OLIW8VNVCU00008S@mauve.mrochek.com>
In-Reply-To: <01OLIW8VNVCU00008S@mauve.mrochek.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Wed, 17 Oct 2012 11:30:56 -0700 (PDT)
Cc: gen-art@ietf.org, draft-leiba-5322upd-from-group.all@tools.ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Oct 2012 18:30:59 -0000

On 10/17/2012 10:49 AM, ned+ietf@mauve.mrochek.com wrote:
>> Minor issues:
>
>> 1.	It is not clear from the draft what the use case for using the group
>> construct is.  Section 3 talks about the issues with using the group
>> construct and recommend limited use, but this is the only information.
>
> The main driver for this work is to add support for EAI downgrade mechanisms,


Although the Intro text cites this, it doesn't explain how the change 
will help.  Nor is this explained elsewhere in the document.

A single sentence summarizing what benefit is achieved with the change, 
along with a couple of usage examples, would go a long way towards 
showing how this update helps in practical ways.

d/

-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From ned+ietf@mauve.mrochek.com  Wed Oct 17 12:06: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 410F621F8658 for <ietf@ietfa.amsl.com>; Wed, 17 Oct 2012 12:06:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.525
X-Spam-Level: 
X-Spam-Status: No, score=-2.525 tagged_above=-999 required=5 tests=[AWL=0.074,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RHC+xJVcJZfM for <ietf@ietfa.amsl.com>; Wed, 17 Oct 2012 12:06:15 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id DFDA721F8650 for <ietf@ietf.org>; Wed, 17 Oct 2012 12:06:14 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OLIXV4JS6O000637@mauve.mrochek.com> for ietf@ietf.org; Wed, 17 Oct 2012 12:01:11 -0700 (PDT)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OLDMMCPN8G00008S@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Wed, 17 Oct 2012 12:01:08 -0700 (PDT)
From: ned+ietf@mauve.mrochek.com
Message-id: <01OLIXV2SU4O00008S@mauve.mrochek.com>
Date: Wed, 17 Oct 2012 12:00:05 -0700 (PDT)
Subject: Re: Gen-ART LC review of draft-leiba-5322upd-from-group-06
In-reply-to: "Your message dated Wed, 17 Oct 2012 11:30:53 -0700" <507EF95D.5090007@dcrocker.net>
MIME-version: 1.0
Content-type: TEXT/PLAIN; format=flowed
References: <010301cdac4d$cfa70060$6ef50120$@gmail.com> <01OLIW8VNVCU00008S@mauve.mrochek.com> <507EF95D.5090007@dcrocker.net>
To: Dave Crocker <dhc@dcrocker.net>
Cc: ned+ietf@mauve.mrochek.com, gen-art@ietf.org, draft-leiba-5322upd-from-group.all@tools.ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Oct 2012 19:06:15 -0000

> On 10/17/2012 10:49 AM, ned+ietf@mauve.mrochek.com wrote:
> >> Minor issues:
> >
> >> 1.	It is not clear from the draft what the use case for using the group
> >> construct is.  Section 3 talks about the issues with using the group
> >> construct and recommend limited use, but this is the only information.
> >
> > The main driver for this work is to add support for EAI downgrade mechanisms,


> Although the Intro text cites this, it doesn't explain how the change
> will help.  Nor is this explained elsewhere in the document.

> A single sentence summarizing what benefit is achieved with the change,
> along with a couple of usage examples, would go a long way towards
> showing how this update helps in practical ways.

I could live with a single sentence, but I strongly object to the inclusion
of examples, for the reasons I gave in my original response.

				Ned

From john-ietf@jck.com  Wed Oct 17 12:23:48 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 D5AB421F84EB; Wed, 17 Oct 2012 12:23:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.524
X-Spam-Level: 
X-Spam-Status: No, score=-102.524 tagged_above=-999 required=5 tests=[AWL=0.075, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8G9lg-ViaoXF; Wed, 17 Oct 2012 12:23:48 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 39D9F21F84DF; Wed, 17 Oct 2012 12:23:46 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1TOZDT-000PJf-TW; Wed, 17 Oct 2012 15:23:43 -0400
Date: Wed, 17 Oct 2012 15:23:39 -0400
From: John C Klensin <john-ietf@jck.com>
To: IETF <ietf@ietf.org>
Subject: Re: Antitrust FAQ
Message-ID: <38C9C715CA5F2EDA0E9DBE1C@JcK-HP8200.jck.com>
In-Reply-To: <2B5B0F0036DD9FD9FBA556C2@JcK-HP8200.jck.com>
References: <CC9CC662.B626%contreraslegal@att.net> <507852EF.1000703@qti.qualcomm.com>	<tsld30jdhhq.fsf_-_@mit.edu> <507C1A5C.6000207@qti.qualcomm.com> <2B5B0F0036DD9FD9FBA556C2@JcK-HP8200.jck.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: IETF Chair <chair@ietf.org>, Jorge Contreras <contreraslegal@att.net>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Oct 2012 19:23:49 -0000

Hi.

A separate conversation stirred up memories of the ones at ANSI
from long ago and suggests something else that should be added
to the list:

* A protocol specification that has the appearance of being
solely the product of a single vendor or other organization is
inherently dangerous and dangerous to the IETF, not just the
particants. Problems can arise if a standards body rubber-stamps
a one-organization specification, especially if that
organization gains an advantage from standardization of its
technology.  First-to-implement or other market dominance
factors may be as important in that regard as, e.g., licensing
restrictions.    WGs or others evaluating such a specification
should be extra-careful to make sure that it has broad support
from unaffiliated people  and that the support is documented for
the record in minutes, shepherd's reports, or through other
mechanisms.

Several of the terms above are wildly subjective, but this can
be an area in which, if one wishes to avoid trouble, the
appearance may be more important than hair-splitting about the
realities.

Just something to be considered.
best,
   john


From john-ietf@jck.com  Wed Oct 17 12:27: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 7254F21F86A4; Wed, 17 Oct 2012 12:27:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.525
X-Spam-Level: 
X-Spam-Status: No, score=-102.525 tagged_above=-999 required=5 tests=[AWL=0.074, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WHR1gGIlXrqU; Wed, 17 Oct 2012 12:27:44 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id ECD8F21F86B0; Wed, 17 Oct 2012 12:27:43 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1TOZHE-000PK0-5O; Wed, 17 Oct 2012 15:27:36 -0400
Date: Wed, 17 Oct 2012 15:27:31 -0400
From: John C Klensin <john-ietf@jck.com>
To: ned+ietf@mauve.mrochek.com, Dave Crocker <dhc@dcrocker.net>
Subject: Re: Gen-ART LC review of draft-leiba-5322upd-from-group-06
Message-ID: <5B0F81787945877A5CC3794B@JcK-HP8200.jck.com>
In-Reply-To: <01OLIXV2SU4O00008S@mauve.mrochek.com>
References: <010301cdac4d$cfa70060$6ef50120$@gmail.com> <01OLIW8VNVCU00008S@mauve.mrochek.com> <507EF95D.5090007@dcrocker.net> <01OLIXV2SU4O00008S@mauve.mrochek.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: gen-art@ietf.org, draft-leiba-5322upd-from-group.all@tools.ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Oct 2012 19:27:44 -0000

--On Wednesday, October 17, 2012 12:00 -0700
ned+ietf@mauve.mrochek.com wrote:

>> A single sentence summarizing what benefit is achieved with
>> the change, along with a couple of usage examples, would go a
>> long way towards showing how this update helps in practical
>> ways.
> 
> I could live with a single sentence, but I strongly object to
> the inclusion
> of examples, for the reasons I gave in my original response.

Would a possible middle ground be to include a single
well-crafted sentence with an informative citation of
draft-ietf-eai-popimap-downgrade?  That document does contain
examples and an explanation of that particular use case.

I'd prefer to avoid that entirely for the same reasons Ned
cites, but it would, IMO, be good to get on with this rather
than quibbling for days or weeks.

    john



From gtw@gtwassociates.com  Wed Oct 17 12:42:17 2012
Return-Path: <gtw@gtwassociates.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F168021F865B; Wed, 17 Oct 2012 12:42:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.739
X-Spam-Level: 
X-Spam-Status: No, score=-0.739 tagged_above=-999 required=5 tests=[BAYES_20=-0.74, STOX_REPLY_TYPE=0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eh64feePciSG; Wed, 17 Oct 2012 12:42:16 -0700 (PDT)
Received: from mail9.primary.net (mail9.primary.net [216.87.38.215]) by ietfa.amsl.com (Postfix) with ESMTP id 2869C21F8628; Wed, 17 Oct 2012 12:42:16 -0700 (PDT)
Received: from pool-71-191-174-95.washdc.fios.verizon.net ([71.191.174.95]:1952 helo=gtwassociates) by mail9.primary.net with esmtpa (Exim 4.63) (envelope-from <gtw@gtwassociates.com>) id 1TOZVJ-0002LI-G4; Wed, 17 Oct 2012 14:42:14 -0500
Message-ID: <BF6C8AC3360548F88D102ABD8E3C1195@gtwassociates>
From: "George Willingmyre" <gtw@gtwassociates.com>
To: "John C Klensin" <john-ietf@jck.com>, "IETF" <ietf@ietf.org>
References: <CC9CC662.B626%contreraslegal@att.net><507852EF.1000703@qti.qualcomm.com>	<tsld30jdhhq.fsf_-_@mit.edu><507C1A5C.6000207@qti.qualcomm.com><2B5B0F0036DD9FD9FBA556C2@JcK-HP8200.jck.com> <38C9C715CA5F2EDA0E9DBE1C@JcK-HP8200.jck.com>
Subject: Re: Antitrust FAQ
Date: Wed, 17 Oct 2012 15:42:52 -0400
Organization: GTW Associates
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157
X-ACL-Warn: X-The email account used to send this email was: gtw@gtwassociates.com
Cc: IETF Chair <chair@ietf.org>, Jorge Contreras <contreraslegal@att.net>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: George Willingmyre <gtw@gtwassociates.com>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Oct 2012 19:42:17 -0000

Hello John ... it would help me better understand your proposal in an 
antitrust context  if you elaborated to what you are referring at ANSI.

Could it be the text about use of trademarks in standards in the 2008

ANSI Guidelines on Embedded Trademark 
http://publicaa.ansi.org/sites/apdl/Documents/Standards%20Activities/American%20National%20Standards/Procedures,%20Guides,%20and%20Forms/ANSI%20Guidelines%20on%20Embedded%20Trademark.pdf

clip



The primary concern relating to the use of a mark in a standard is whether 
it would appear

as if the standard is endorsing one particular proprietary product or 
service over competing

ones.

B. General Guidance

As a general rule, standards should provide a description of features from 
which

competing and interoperable implementations can be developed. The appearance 
that a

standard endorses any particular products, services or companies should be 
avoided.

Therefore, proper names, trademarks, service marks or certification marks of 
specific

companies, products or services should not be included in the text of a 
standard or in an

appendix (or the equivalent) if it appears that they might cause this 
effect.


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


----- Original Message ----- 
From: "John C Klensin" <john-ietf@jck.com>
To: "IETF" <ietf@ietf.org>
Cc: "IETF Chair" <chair@ietf.org>; "Jorge Contreras" 
<contreraslegal@att.net>
Sent: Wednesday, October 17, 2012 3:23 PM
Subject: Re: Antitrust FAQ


> Hi.
>
> A separate conversation stirred up memories of the ones at ANSI
> from long ago and suggests something else that should be added
> to the list:
>
> * A protocol specification that has the appearance of being
> solely the product of a single vendor or other organization is
> inherently dangerous and dangerous to the IETF, not just the
> particants. Problems can arise if a standards body rubber-stamps
> a one-organization specification, especially if that
> organization gains an advantage from standardization of its
> technology.  First-to-implement or other market dominance
> factors may be as important in that regard as, e.g., licensing
> restrictions.    WGs or others evaluating such a specification
> should be extra-careful to make sure that it has broad support
> from unaffiliated people  and that the support is documented for
> the record in minutes, shepherd's reports, or through other
> mechanisms.
>
> Several of the terms above are wildly subjective, but this can
> be an area in which, if one wishes to avoid trouble, the
> appearance may be more important than hair-splitting about the
> realities.
>
> Just something to be considered.
> best,
>   john
>
> 


From dhc@dcrocker.net  Wed Oct 17 13:07:13 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 7C7F221F86D5; Wed, 17 Oct 2012 13:07:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.539
X-Spam-Level: 
X-Spam-Status: No, score=-6.539 tagged_above=-999 required=5 tests=[AWL=0.060,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LdPBLQvNJo0h; Wed, 17 Oct 2012 13:07:01 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id D869421F86CF; Wed, 17 Oct 2012 13:06:59 -0700 (PDT)
Received: from [192.168.1.6] (adsl-67-127-59-48.dsl.pltn13.pacbell.net [67.127.59.48]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q9HK6w9J023026 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 17 Oct 2012 13:06:59 -0700
Message-ID: <507F0FE2.2000606@dcrocker.net>
Date: Wed, 17 Oct 2012 13:06:58 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121005 Thunderbird/16.0
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
Subject: Re: Antitrust FAQ
References: <CC9CC662.B626%contreraslegal@att.net> <507852EF.1000703@qti.qualcomm.com>	<tsld30jdhhq.fsf_-_@mit.edu> <507C1A5C.6000207@qti.qualcomm.com> <2B5B0F0036DD9FD9FBA556C2@JcK-HP8200.jck.com> <38C9C715CA5F2EDA0E9DBE1C@JcK-HP8200.jck.com>
In-Reply-To: <38C9C715CA5F2EDA0E9DBE1C@JcK-HP8200.jck.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Wed, 17 Oct 2012 13:06:59 -0700 (PDT)
Cc: IETF Chair <chair@ietf.org>, IETF <ietf@ietf.org>, Jorge Contreras <contreraslegal@att.net>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Oct 2012 20:07:13 -0000

On 10/17/2012 12:23 PM, John C Klensin wrote:

> * A protocol specification that has the appearance of being
> solely the product of a single vendor or other organization is
> inherently dangerous and dangerous to the IETF, not just the
> particants. Problems can arise if a standards body rubber-stamps
> a one-organization specification, especially if that
> organization gains an advantage from standardization of its
> technology.  First-to-implement or other market dominance
> factors may be as important in that regard as, e.g., licensing
> restrictions.    WGs or others evaluating such a specification
> should be extra-careful to make sure that it has broad support
> from unaffiliated people  and that the support is documented for
> the record in minutes, shepherd's reports, or through other
> mechanisms.


If a spec has broad support, it doesn't matter where it came from.  If a 
spec does not have broad support, it doesn't matter where it came from.

The essential concern is reviewing initial and continuing support.  It's 
an issue for many different possible IETF activities, not just those 
with an initial specification coming from a single source.

d/

-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From dhc@dcrocker.net  Wed Oct 17 13:26:33 2012
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0636521F86DD; Wed, 17 Oct 2012 13:26:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.549
X-Spam-Level: 
X-Spam-Status: No, score=-6.549 tagged_above=-999 required=5 tests=[AWL=0.050,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bFPrgbbxK2VE; Wed, 17 Oct 2012 13:26:32 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 8681021F86C7; Wed, 17 Oct 2012 13:26:32 -0700 (PDT)
Received: from [192.168.1.6] (adsl-67-127-59-48.dsl.pltn13.pacbell.net [67.127.59.48]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q9HKQVsx023358 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 17 Oct 2012 13:26:31 -0700
Message-ID: <507F1477.1050905@dcrocker.net>
Date: Wed, 17 Oct 2012 13:26:31 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121005 Thunderbird/16.0
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
Subject: Re: Gen-ART LC review of draft-leiba-5322upd-from-group-06
References: <010301cdac4d$cfa70060$6ef50120$@gmail.com> <01OLIW8VNVCU00008S@mauve.mrochek.com> <507EF95D.5090007@dcrocker.net> <01OLIXV2SU4O00008S@mauve.mrochek.com> <5B0F81787945877A5CC3794B@JcK-HP8200.jck.com>
In-Reply-To: <5B0F81787945877A5CC3794B@JcK-HP8200.jck.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Wed, 17 Oct 2012 13:26:32 -0700 (PDT)
Cc: ned+ietf@mauve.mrochek.com, gen-art@ietf.org, draft-leiba-5322upd-from-group.all@tools.ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Oct 2012 20:26:33 -0000

On 10/17/2012 12:27 PM, John C Klensin wrote:
>
>
> --On Wednesday, October 17, 2012 12:00 -0700
> ned+ietf@mauve.mrochek.com wrote:
>
>>> A single sentence summarizing what benefit is achieved with
>>> the change, along with a couple of usage examples, would go a
>>> long way towards showing how this update helps in practical
>>> ways.
>>
>> I could live with a single sentence, but I strongly object to
>> the inclusion
>> of examples, for the reasons I gave in my original response.
>
> Would a possible middle ground be to include a single
> well-crafted sentence with an informative citation of
> draft-ietf-eai-popimap-downgrade?  That document does contain
> examples and an explanation of that particular use case.


I thought Ned's goal was -- quite reasonably, IMO -- to not be dependent 
upon EAI for this general-purpose enhancement.

d/
-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From john-ietf@jck.com  Wed Oct 17 14:16:43 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 543D621F86B0; Wed, 17 Oct 2012 14:16:43 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ReqJ4TiyGILP; Wed, 17 Oct 2012 14:16:42 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id C159E21F86A4; Wed, 17 Oct 2012 14:16:42 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1TOayh-000PRO-KN; Wed, 17 Oct 2012 17:16:35 -0400
Date: Wed, 17 Oct 2012 17:16:31 -0400
From: John C Klensin <john-ietf@jck.com>
To: dcrocker@bbiw.net
Subject: Re: Gen-ART LC review of draft-leiba-5322upd-from-group-06
Message-ID: <4C905CA81E1237976A78C364@JcK-HP8200.jck.com>
In-Reply-To: <507F1477.1050905@dcrocker.net>
References: <010301cdac4d$cfa70060$6ef50120$@gmail.com> <01OLIW8VNVCU00008S@mauve.mrochek.com> <507EF95D.5090007@dcrocker.net> <01OLIXV2SU4O00008S@mauve.mrochek.com> <5B0F81787945877A5CC3794B@JcK-HP8200.jck.com> <507F1477.1050905@dcrocker.net>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: ned+ietf@mauve.mrochek.com, gen-art@ietf.org, draft-leiba-5322upd-from-group.all@tools.ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Oct 2012 21:16:43 -0000

--On Wednesday, October 17, 2012 13:26 -0700 Dave Crocker
<dhc@dcrocker.net> wrote:

>...
>>>> A single sentence summarizing what benefit is achieved with
>>>> the change, along with a couple of usage examples, would go
>>>> a long way towards showing how this update helps in
>>>> practical ways.
>>> 
>>> I could live with a single sentence, but I strongly object to
>>> the inclusion
>>> of examples, for the reasons I gave in my original response.
>> 
>> Would a possible middle ground be to include a single
>> well-crafted sentence with an informative citation of
>> draft-ietf-eai-popimap-downgrade?  That document does contain
>> examples and an explanation of that particular use case.
> 
> I thought Ned's goal was -- quite reasonably, IMO -- to not be
> dependent upon EAI for this general-purpose enhancement.

The problem is that all of the practical (i.e., not constructed
just for the document) examples we have, especially with the
advice to not use these group addresses except under special
circumstances, are associated with EAI.  So, as soon as one says
something equivalent to "summarize the benefit and provide use
cases" one either becomes dependent on EAI for examples (which
is not what we usually mean by "dependent") or is constructing
works of fancy or speculation.

The other approach --and the one I think Ned is advocating
although he can speak for himself-- is to make this change
primarily because embedding the prohibition on using groups in
backward-pointing addresses in the syntax has outlived its
usefulness if, indeed, it was ever wise.  Instead, we end up
with the syntax restriction eliminated and rather general
use/applicability advice.  It seems to me that ought to be
sufficient.

    best,
    john



From ned+ietf@mauve.mrochek.com  Wed Oct 17 14:40:13 2012
Return-Path: <ned+ietf@mauve.mrochek.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2681421F8711 for <ietf@ietfa.amsl.com>; Wed, 17 Oct 2012 14:40:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id j3XqrNqGkrU8 for <ietf@ietfa.amsl.com>; Wed, 17 Oct 2012 14:40:12 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id AC9F221F8713 for <ietf@ietf.org>; Wed, 17 Oct 2012 14:40:12 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OLJ390L4ZK00097O@mauve.mrochek.com> for ietf@ietf.org; Wed, 17 Oct 2012 14:35:10 -0700 (PDT)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OLDMMCPN8G00008S@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Wed, 17 Oct 2012 14:35:06 -0700 (PDT)
From: ned+ietf@mauve.mrochek.com
Message-id: <01OLJ38YAL9600008S@mauve.mrochek.com>
Date: Wed, 17 Oct 2012 14:32:29 -0700 (PDT)
Subject: Re: Gen-ART LC review of draft-leiba-5322upd-from-group-06
In-reply-to: "Your message dated Wed, 17 Oct 2012 15:27:31 -0400" <5B0F81787945877A5CC3794B@JcK-HP8200.jck.com>
MIME-version: 1.0
Content-type: TEXT/PLAIN
References: <010301cdac4d$cfa70060$6ef50120$@gmail.com> <01OLIW8VNVCU00008S@mauve.mrochek.com> <507EF95D.5090007@dcrocker.net> <01OLIXV2SU4O00008S@mauve.mrochek.com> <5B0F81787945877A5CC3794B@JcK-HP8200.jck.com>
To: John C Klensin <john-ietf@jck.com>
Cc: ned+ietf@mauve.mrochek.com, gen-art@ietf.org, draft-leiba-5322upd-from-group.all@tools.ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Oct 2012 21:40:13 -0000

> --On Wednesday, October 17, 2012 12:00 -0700
> ned+ietf@mauve.mrochek.com wrote:

> >> A single sentence summarizing what benefit is achieved with
> >> the change, along with a couple of usage examples, would go a
> >> long way towards showing how this update helps in practical
> >> ways.
> >
> > I could live with a single sentence, but I strongly object to
> > the inclusion
> > of examples, for the reasons I gave in my original response.

> Would a possible middle ground be to include a single
> well-crafted sentence with an informative citation of
> draft-ietf-eai-popimap-downgrade?  That document does contain
> examples and an explanation of that particular use case.

> I'd prefer to avoid that entirely for the same reasons Ned
> cites, but it would, IMO, be good to get on with this rather
> than quibbling for days or weeks.

Channeling my inner Maslow, I see the present text as best, an additional
sentence or two as next best, a sentence and a cite to the downgrade doc next
in line, and including actual EAI examples in this doc as the worst choice.

FWIW.

				Ned


From john-ietf@jck.com  Wed Oct 17 15:05:59 2012
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C643021F867E; Wed, 17 Oct 2012 15:05:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.528
X-Spam-Level: 
X-Spam-Status: No, score=-102.528 tagged_above=-999 required=5 tests=[AWL=0.071, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AyuxSlfIplFz; Wed, 17 Oct 2012 15:05:59 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id E956F21F863B; Wed, 17 Oct 2012 15:05:58 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1TObkT-000PUg-Rh; Wed, 17 Oct 2012 18:05:57 -0400
Date: Wed, 17 Oct 2012 18:05:53 -0400
From: John C Klensin <john-ietf@jck.com>
To: dcrocker@bbiw.net
Subject: Re: Antitrust FAQ
Message-ID: <EABAC0DCA56E41601E995877@JcK-HP8200.jck.com>
In-Reply-To: <507F0FE2.2000606@dcrocker.net>
References: <CC9CC662.B626%contreraslegal@att.net> <507852EF.1000703@qti.qualcomm.com>	<tsld30jdhhq.fsf_-_@mit.edu> <507C1A5C.6000207@qti.qualcomm.com> <2B5B0F0036DD9FD9FBA556C2@JcK-HP8200.jck.com> <38C9C715CA5F2EDA0E9DBE1C@JcK-HP8200.jck.com> <507F0FE2.2000606@dcrocker.net>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: IETF Chair <chair@ietf.org>, IETF <ietf@ietf.org>, Jorge Contreras <contreraslegal@att.net>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Oct 2012 22:05:59 -0000

--On Wednesday, October 17, 2012 13:06 -0700 Dave Crocker
<dhc@dcrocker.net> wrote:

> If a spec has broad support, it doesn't matter where it came
> from.  If a spec does not have broad support, it doesn't
> matter where it came from.
> 
> The essential concern is reviewing initial and continuing
> support.  It's an issue for many different possible IETF
> activities, not just those with an initial specification
> coming from a single source.

Dave,

As a fairly determined non-lawyer, I believe that careful
attention to IETF procedures and norms, including the principle
you identify above, is sufficient to keep us out of antitrust
problems and that this "FAQ" effort, like the "policy" effort
before it, is a waste of the community's time.

But perhaps I'm naive and there are things that are driving the
IESG (or the IAOC, but I presume you would know about that) to
want to do this.  _If_ it is worth doing (and, again, I have my
doubts) then it is probably worth noting the things that can set
off alarms.  I have some small reason to believe that a single
source specification that is not significantly altered by the WG
and that is largely pushed by the organization from which the
specification came can set off those alarms should someone later
claim to have been damaged by the spec.   That is quite
independent of your point and the observation that, to the best
of my knowledge, "reviewing initial and continuing support" is a
sufficient remedy for problems that might occur with a
single-source specification for which that level of review did
not occur.

   john



From stephen.farrell@cs.tcd.ie  Wed Oct 17 15:18:57 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 9460D21F85B8; Wed, 17 Oct 2012 15:18:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.449
X-Spam-Level: 
X-Spam-Status: No, score=-102.449 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, SARE_WEOFFER=0.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wuvSvfi6uotC; Wed, 17 Oct 2012 15:18:53 -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 5401F21F858E; Wed, 17 Oct 2012 15:18:52 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hermes.scss.tcd.ie (Postfix) with ESMTP id 46750103F51; Wed, 17 Oct 2012 23:18:51 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; h= content-transfer-encoding:content-type:in-reply-to:references :subject:mime-version:user-agent:from:date:message-id:received :received:x-virus-scanned; s=cs; t=1350512330; bh=jUpxbWq9zKw0xj c/B6K1+zJ00xVBwHuOIfEW6tn7y3E=; b=CLXKf9hsbuvHqE/l22BQxj65HIoTkE JxMk1RFFnbwf1dvjI89QhIyCN1r/rnbSNmqlt6Uyvn+0zBpWs0deHoCjEr4cdlOe L26jksu0qC3i/tnk9Rv+t0MAuDuVskSnJuQtVkD9MQA2RlegSoEiQoE49NNstcQk Ycfd/TexMwpxBpp5u6maWFogox/6XxanTbfY+vFOQpAPrKxj/lwEUKYq3yh8ahZ7 MgSHR6mmozqKCSmOqewUex5e1G8vGMqT5E29MgciqQDGF9GYKNIzU2xg5f56nwQ8 yKG2iwPlwREvDeME6d8MJzmd0x0d+1AdBbYuzvZU57le8NkeEB5SbVnw==
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 asP1T3a4peoj; Wed, 17 Oct 2012 23:18:50 +0100 (IST)
Received: from [10.87.48.4] (unknown [86.41.5.56]) by smtp.scss.tcd.ie (Postfix) with ESMTPSA id 9B456171486; Wed, 17 Oct 2012 23:18:48 +0100 (IST)
Message-ID: <507F2EC7.90405@cs.tcd.ie>
Date: Wed, 17 Oct 2012 23:18:47 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20121011 Thunderbird/16.0.1
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
Subject: Re: Antitrust FAQ
References: <CC9CC662.B626%contreraslegal@att.net> <507852EF.1000703@qti.qualcomm.com>	<tsld30jdhhq.fsf_-_@mit.edu> <507C1A5C.6000207@qti.qualcomm.com> <2B5B0F0036DD9FD9FBA556C2@JcK-HP8200.jck.com> <38C9C715CA5F2EDA0E9DBE1C@JcK-HP8200.jck.com>
In-Reply-To: <38C9C715CA5F2EDA0E9DBE1C@JcK-HP8200.jck.com>
X-Enigmail-Version: 1.4.5
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: IETF Chair <chair@ietf.org>, IETF <ietf@ietf.org>, Jorge Contreras <contreraslegal@att.net>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Oct 2012 22:18:57 -0000

On 10/17/2012 08:23 PM, John C Klensin wrote:
> * A protocol specification that has the appearance of being
> solely the product of a single vendor or other organization is
> inherently dangerous and dangerous to the IETF, not just the
> particants. Problems can arise if a standards body rubber-stamps
> a one-organization specification, especially if that
> organization gains an advantage from standardization of its
> technology.

I'm with Dave on this one. I don't believe we should
feel any need whatsoever to fiddle with, or to look like
we've fiddled with, something that's already good, nor
ought we offer guidance to that effect.

If I recall correctly, HMAC (rfc 2104) is a fine counterexample
to the need-to-fiddle claim. The Internet is better because
we adopted what looks like that one-vendor specification
and we shouldn't feel like that's a problem, when it just
isn't.

So I don't see a need for any such addition to the FAQ.

S.

From dhc@dcrocker.net  Wed Oct 17 16:19:09 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 2D42321F867E; Wed, 17 Oct 2012 16:19:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.556
X-Spam-Level: 
X-Spam-Status: No, score=-6.556 tagged_above=-999 required=5 tests=[AWL=0.043,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id e9bzxvVsy7UO; Wed, 17 Oct 2012 16:19:08 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 819C521F8540; Wed, 17 Oct 2012 16:19:08 -0700 (PDT)
Received: from [192.168.1.6] (adsl-67-127-59-48.dsl.pltn13.pacbell.net [67.127.59.48]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q9HNJ7Wk026837 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 17 Oct 2012 16:19:07 -0700
Message-ID: <507F3CEA.2010306@dcrocker.net>
Date: Wed, 17 Oct 2012 16:19:06 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121005 Thunderbird/16.0
MIME-Version: 1.0
To: Ned Freed <ned.freed@mrochek.com>
Subject: Re: Gen-ART LC review of draft-leiba-5322upd-from-group-06
References: <010301cdac4d$cfa70060$6ef50120$@gmail.com> <01OLIW8VNVCU00008S@mauve.mrochek.com> <507EF95D.5090007@dcrocker.net> <01OLIXV2SU4O00008S@mauve.mrochek.com> <5B0F81787945877A5CC3794B@JcK-HP8200.jck.com> <01OLJ38YAL9600008S@mauve.mrochek.com>
In-Reply-To: <01OLJ38YAL9600008S@mauve.mrochek.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Wed, 17 Oct 2012 16:19:08 -0700 (PDT)
Cc: John C Klensin <john-ietf@jck.com>, ned+ietf@mauve.mrochek.com, gen-art@ietf.org, draft-leiba-5322upd-from-group.all@tools.ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Oct 2012 23:19:09 -0000

On 10/17/2012 2:32 PM, Ned Freed wrote:
> Channeling my inner Maslow, I see the present text as best, an additional
> sentence or two as next best, a sentence and a cite to the downgrade doc next
> in line, and including actual EAI examples in this doc as the worst choice.


The problem I have with the current text is that it says 'what' 
motivated the change, but not how it is useful for the intended class of 
uses.  The reader is left entirely to guess.

Self-actualization among the inadequately-informed invites fantasy more 
than it invites utility.

d/

-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From barryleiba@gmail.com  Wed Oct 17 16:46: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 2DCF421F8621; Wed, 17 Oct 2012 16:46:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.065
X-Spam-Level: 
X-Spam-Status: No, score=-103.065 tagged_above=-999 required=5 tests=[AWL=-0.088, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6efpUFfizLOc; Wed, 17 Oct 2012 16:46:02 -0700 (PDT)
Received: from mail-vc0-f172.google.com (mail-vc0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 825B121F861F; Wed, 17 Oct 2012 16:45:59 -0700 (PDT)
Received: by mail-vc0-f172.google.com with SMTP id fl11so9597491vcb.31 for <multiple recipients>; Wed, 17 Oct 2012 16:45:58 -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=2TCoh3SaoQ/BJJeiPbkoKJY7hUHpilkLFBAjUbfhDck=; b=DNBr2dxaMV+2SPc5ZzURqKXPJIqXJmBuQo1a0pd8E120o5jH0PSA3WKDaPcGuASooC IwGnfqTR7ajGiWFqukgvHKHDwDJyWlM7yaGiIM7pAZE8GE762+T8MHDBlefk2+6A8vrD fIRVotjvZCFdip76IsfVe6mwmksICuDWFn88o7sOzZA0hem4oRvlDy2qFNZvkVC5qHfh hJ6lgSY7z5N8NkqWUfJmeZA5hONfxR6de+AZBmpWBlWjggOfPPEQX8ol7BxLlWePwSg7 Fym51z8XZzAh5FFgHi5r634HDWIWs+qr+Fc8yPFPBhOuP+c9WINe4LEUAdKB2aEMIp7y IvsQ==
MIME-Version: 1.0
Received: by 10.58.86.36 with SMTP id m4mr12550829vez.14.1350517558744; Wed, 17 Oct 2012 16:45:58 -0700 (PDT)
Sender: barryleiba@gmail.com
Received: by 10.58.28.231 with HTTP; Wed, 17 Oct 2012 16:45:58 -0700 (PDT)
In-Reply-To: <507F3CEA.2010306@dcrocker.net>
References: <010301cdac4d$cfa70060$6ef50120$@gmail.com> <01OLIW8VNVCU00008S@mauve.mrochek.com> <507EF95D.5090007@dcrocker.net> <01OLIXV2SU4O00008S@mauve.mrochek.com> <5B0F81787945877A5CC3794B@JcK-HP8200.jck.com> <01OLJ38YAL9600008S@mauve.mrochek.com> <507F3CEA.2010306@dcrocker.net>
Date: Wed, 17 Oct 2012 19:45:58 -0400
X-Google-Sender-Auth: zOjJ2SzgtHpYEv4w-ivH0d5WAYE
Message-ID: <CALaySJLex2ozmTMByO8=mRmu-fETX-TDRk7CdMedz5nDxjT6vA@mail.gmail.com>
Subject: Re: Gen-ART LC review of draft-leiba-5322upd-from-group-06
From: Barry Leiba <barryleiba@computer.org>
To: dcrocker@bbiw.net
Content-Type: text/plain; charset=ISO-8859-1
Cc: Ned Freed <ned.freed@mrochek.com>, draft-leiba-5322upd-from-group.all@tools.ietf.org, ned+ietf@mauve.mrochek.com, gen-art@ietf.org, John C Klensin <john-ietf@jck.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Oct 2012 23:46:03 -0000

>> Channeling my inner Maslow, I see the present text as best, an additional
>> sentence or two as next best, a sentence and a cite to the downgrade doc
>> next in line, and including actual EAI examples in this doc as the worst
>> choice.
>
> The problem I have with the current text is that it says 'what' motivated
> the change, but not how it is useful for the intended class of uses.  The
> reader is left entirely to guess.

So, is it better to put in a sentence about representing non-ASCII
text in the group name without including a replyable address?

Or is it better to remove the notation about the EAI use case, and
just say that it's stupid to have the restriction, so we're removing
it?

I'm ambivalent.

Barry

From ned+ietf@mauve.mrochek.com  Wed Oct 17 17:40: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 3348521F8625 for <ietf@ietfa.amsl.com>; Wed, 17 Oct 2012 17:40:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nROKzA7B+pZi for <ietf@ietfa.amsl.com>; Wed, 17 Oct 2012 17:40:38 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id 75E5321F8622 for <ietf@ietf.org>; Wed, 17 Oct 2012 17:40:38 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OLJ9JD42OW0005HX@mauve.mrochek.com> for ietf@ietf.org; Wed, 17 Oct 2012 17:35:20 -0700 (PDT)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OLDMMCPN8G00008S@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Wed, 17 Oct 2012 17:35:14 -0700 (PDT)
From: ned+ietf@mauve.mrochek.com
Message-id: <01OLJ9JAK8SQ00008S@mauve.mrochek.com>
Date: Wed, 17 Oct 2012 17:18:37 -0700 (PDT)
Subject: Re: Gen-ART LC review of draft-leiba-5322upd-from-group-06
In-reply-to: "Your message dated Wed, 17 Oct 2012 16:19:06 -0700" <507F3CEA.2010306@dcrocker.net>
MIME-version: 1.0
Content-type: TEXT/PLAIN; format=flowed
References: <010301cdac4d$cfa70060$6ef50120$@gmail.com> <01OLIW8VNVCU00008S@mauve.mrochek.com> <507EF95D.5090007@dcrocker.net> <01OLIXV2SU4O00008S@mauve.mrochek.com> <5B0F81787945877A5CC3794B@JcK-HP8200.jck.com> <01OLJ38YAL9600008S@mauve.mrochek.com> <507F3CEA.2010306@dcrocker.net>
To: Dave Crocker <dhc@dcrocker.net>
Cc: Ned Freed <ned.freed@mrochek.com>, draft-leiba-5322upd-from-group.all@tools.ietf.org, ned+ietf@mauve.mrochek.com, gen-art@ietf.org, John C Klensin <john-ietf@jck.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Oct 2012 00:40:39 -0000

> On 10/17/2012 2:32 PM, Ned Freed wrote:
> > Channeling my inner Maslow, I see the present text as best, an additional
> > sentence or two as next best, a sentence and a cite to the downgrade doc next
> > in line, and including actual EAI examples in this doc as the worst choice.


> The problem I have with the current text is that it says 'what'
> motivated the change, but not how it is useful for the intended class of
> uses.  The reader is left entirely to guess.

> Self-actualization among the inadequately-informed invites fantasy more
> than it invites utility.

That depends on both the utility and the desirability of repeating the existing
use case, doesn't it? The EAI use case of downgraded messages is one that only
exists because of a nasty confluence of restrictions and which we absolutely do
not want to see repeated in any other context.

If you really think this is important to explain why we're making this change
against the overall context of RFC 5322 - and I most certainly do not agree
that it is important to do so - then the best "use case" to add is the negative
one: The elimination of an unnecessary restriction that isn't followed in
practice.

I see no way to explain the narrow EAI use case in this context without either
dragging in a whole bunch of EAI that has no business being here or leaving
various things dangling. Either way the average reader looking at general
message usage isn't going to get it, and the more you try and waltz around this
the more likely you are to get exactly the outcome you fear: Someone is going
to see some sort of parallel with some problem they are trying to solve (some
sort of deliberate form of address obfuscation scheme immediately comes to
mind) and proceeds to make a mess of things.

				Ned

P.S. It really would be best if this could wait until there was an update
to RFC 5322. But that's not how the timing has worked out, so this is the
best alternative available.

From dhc@dcrocker.net  Wed Oct 17 17:50:20 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 06FFE21F8686; Wed, 17 Oct 2012 17:50:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.562
X-Spam-Level: 
X-Spam-Status: No, score=-6.562 tagged_above=-999 required=5 tests=[AWL=0.038,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1QI4PhiV2L-q; Wed, 17 Oct 2012 17:50:19 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 52BA821F866E; Wed, 17 Oct 2012 17:50:19 -0700 (PDT)
Received: from [192.168.1.6] (adsl-67-127-59-48.dsl.pltn13.pacbell.net [67.127.59.48]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q9I0oIPi029055 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 17 Oct 2012 17:50:18 -0700
Message-ID: <507F5249.2090507@dcrocker.net>
Date: Wed, 17 Oct 2012 17:50:17 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121005 Thunderbird/16.0
MIME-Version: 1.0
To: Ned Freed <ned.freed@mrochek.com>
Subject: Re: Gen-ART LC review of draft-leiba-5322upd-from-group-06
References: <010301cdac4d$cfa70060$6ef50120$@gmail.com> <01OLIW8VNVCU00008S@mauve.mrochek.com> <507EF95D.5090007@dcrocker.net> <01OLIXV2SU4O00008S@mauve.mrochek.com> <5B0F81787945877A5CC3794B@JcK-HP8200.jck.com> <01OLJ38YAL9600008S@mauve.mrochek.com> <507F3CEA.2010306@dcrocker.net> <01OLJ9JAK8SQ00008S@mauve.mrochek.com>
In-Reply-To: <01OLJ9JAK8SQ00008S@mauve.mrochek.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Wed, 17 Oct 2012 17:50:19 -0700 (PDT)
Cc: John C Klensin <john-ietf@jck.com>, ned+ietf@mauve.mrochek.com, gen-art@ietf.org, draft-leiba-5322upd-from-group.all@tools.ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Oct 2012 00:50:20 -0000

On 10/17/2012 5:18 PM, Ned Freed wrote:
> If you really think this is important to explain why we're making
> this change against the overall context of RFC 5322 - and I most
> certainly do not agree that it is important to do so - then the best
> "use case" to add is the negative one: The elimination of an
> unnecessary restriction that isn't followed in practice.
>
> I see no way to explain the narrow EAI use case in this context
> without either dragging in a whole bunch of EAI that has no business
> being here or leaving various things dangling.


ack. mumble.

So I'll suggest a bit of an amalgam, including a cross reference of the 
type I prefer to avoid:

    1. State that this removes a restriction that was never essential.

    2. State that the timing of this removal is to accomodate EAI and 
for its use of the now-available features, see [RFCxxxx].

d/


-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From ned+ietf@mauve.mrochek.com  Wed Oct 17 17:55:58 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 A45FF21F8623 for <ietf@ietfa.amsl.com>; Wed, 17 Oct 2012 17:55:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.529
X-Spam-Level: 
X-Spam-Status: No, score=-2.529 tagged_above=-999 required=5 tests=[AWL=0.070,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kD8Fsw2HNJuE for <ietf@ietfa.amsl.com>; Wed, 17 Oct 2012 17:55:58 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id 703C121F8625 for <ietf@ietf.org>; Wed, 17 Oct 2012 17:55:58 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OLJA3P9BRK0009K0@mauve.mrochek.com> for ietf@ietf.org; Wed, 17 Oct 2012 17:50:56 -0700 (PDT)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01OLDMMCPN8G00008S@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Wed, 17 Oct 2012 17:50:51 -0700 (PDT)
From: ned+ietf@mauve.mrochek.com
Message-id: <01OLJA3N74PA00008S@mauve.mrochek.com>
Date: Wed, 17 Oct 2012 17:50:08 -0700 (PDT)
Subject: Re: Gen-ART LC review of draft-leiba-5322upd-from-group-06
In-reply-to: "Your message dated Wed, 17 Oct 2012 19:45:58 -0400" <CALaySJLex2ozmTMByO8=mRmu-fETX-TDRk7CdMedz5nDxjT6vA@mail.gmail.com>
MIME-version: 1.0
Content-type: TEXT/PLAIN
References: <010301cdac4d$cfa70060$6ef50120$@gmail.com> <01OLIW8VNVCU00008S@mauve.mrochek.com> <507EF95D.5090007@dcrocker.net> <01OLIXV2SU4O00008S@mauve.mrochek.com> <5B0F81787945877A5CC3794B@JcK-HP8200.jck.com> <01OLJ38YAL9600008S@mauve.mrochek.com> <507F3CEA.2010306@dcrocker.net> <CALaySJLex2ozmTMByO8=mRmu-fETX-TDRk7CdMedz5nDxjT6vA@mail.gmail.com>
To: Barry Leiba <barryleiba@computer.org>
Cc: Ned Freed <ned.freed@mrochek.com>, draft-leiba-5322upd-from-group.all@tools.ietf.org, ned+ietf@mauve.mrochek.com, gen-art@ietf.org, dcrocker@bbiw.net, John C Klensin <john-ietf@jck.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Oct 2012 00:55:59 -0000

> >> Channeling my inner Maslow, I see the present text as best, an additional
> >> sentence or two as next best, a sentence and a cite to the downgrade doc
> >> next in line, and including actual EAI examples in this doc as the worst
> >> choice.
> >
> > The problem I have with the current text is that it says 'what' motivated
> > the change, but not how it is useful for the intended class of uses.  The
> > reader is left entirely to guess.

> So, is it better to put in a sentence about representing non-ASCII
> text in the group name without including a replyable address?

> Or is it better to remove the notation about the EAI use case, and
> just say that it's stupid to have the restriction, so we're removing
> it?

If the alternative is to dig into EAI in any depth at all, the latter is far
preferable.

				Ned

From ietf@meetecho.com  Thu Oct 18 01:31:02 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 DB5E221F857D for <ietf@ietfa.amsl.com>; Thu, 18 Oct 2012 01:31:02 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4bAjjvz1BNqX for <ietf@ietfa.amsl.com>; Thu, 18 Oct 2012 01:31:01 -0700 (PDT)
Received: from smtplq02.aruba.it (smtplqs-out31.aruba.it [62.149.158.71]) by ietfa.amsl.com (Postfix) with SMTP id 9392421F852A for <ietf@ietf.org>; Thu, 18 Oct 2012 01:31:00 -0700 (PDT)
Received: (qmail 22066 invoked by uid 89); 18 Oct 2012 08:30:57 -0000
Received: from unknown (HELO smtp5.aruba.it) (62.149.158.225) by smtplq02.aruba.it with SMTP; 18 Oct 2012 08:30:57 -0000
Received: (qmail 8729 invoked by uid 89); 18 Oct 2012 08:30:57 -0000
Received: from unknown (HELO ?10.10.10.160?) (alex@meetecho.com@81.208.32.83) by smtp5.ad.aruba.it with ESMTPA; 18 Oct 2012 08:30:57 -0000
Message-ID: <507FBE3D.8050109@meetecho.com>
Date: Thu, 18 Oct 2012 10:30:53 +0200
From: Meetecho IETF support <ietf@meetecho.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121010 Thunderbird/16.0.1
MIME-Version: 1.0
To: joel jaeggli <joelja@bogus.com>
Subject: Re: I-D Action: draft-jaeggli-interim-observations-00.txt
References: <042001cdab1d$df26b6b0$9d742410$@olddog.co.uk> <m21ugzjtia.wl%randy@psg.com> <042501cdab1f$77f31e50$67d95af0$@olddog.co.uk> <507D7FB6.4050105@bogus.com>
In-Reply-To: <507D7FB6.4050105@bogus.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Rating: smtplq02.aruba.it 1.6.2 0/1000/N
Cc: adrian@olddog.co.uk, 'IETF Disgust' <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Oct 2012 08:31:03 -0000

Hi Joel,

nice work! Just a quick note about Section 3.2, with my Meetecho 
volunteer hat on :-)

In the mentioned section you state:

>    Remote participation was supported by volunteers from meetecho using
>    their own application.  Hotel okura wireless infrastrucuture was used
>    to support the meeting.  An outage of the hotel network was observed
>    during the opsec meeting with the result that remote participation
>    would have been interupted for about 10 minutes had there been any to
>    speak of.

As a matter of fact, our streaming laptops were not attached to the 
Okura Wifi network, but we were provided with wired connectivity per our 
request, and as such remote participants were not affected by the 
outage. This was done exactly to cope with issues like the one you 
mentioned, and this is the very reason why we always insist on asking 
for a wired connection for the streaming laptops.

Cheers,
Alessandro

Il 16/10/2012 17:39, joel jaeggli ha scritto:
> On 10/15/12 2:53 PM, Adrian Farrel wrote:
>>> ok, i am lost.  the draft is only an outline and has zero content?  is
>>> it a quiz?
>> Treat it like that and see if you can give Joel the right answers.
> 01 is available. I imagine the SIDR experience was a bit different,
> having been to another SIDR interim, I tried to call that out, but I
> wasn't in the room.
>
> http://tools.ietf.org/html/draft-jaeggli-interim-observations-01
>> For me: Did it make any difference to you that it was a LIM rather
>> than simply a
>> SIDR interim? Were logistics and resources worth the fee? Should we
>> hold future
>> LIMs, or do the scheduling and other issues mean that normal interims
>> are the
>> way forward?
>>
>> cheers,
>> Adrian
>>
>>
>

From johnl@iecc.com  Thu Oct 18 03:29:08 2012
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D4E2521F8618 for <ietf@ietfa.amsl.com>; Thu, 18 Oct 2012 03:29:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -111.693
X-Spam-Level: 
X-Spam-Status: No, score=-111.693 tagged_above=-999 required=5 tests=[AWL=0.506, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hlgu49Xd5s-U for <ietf@ietfa.amsl.com>; Thu, 18 Oct 2012 03:29:07 -0700 (PDT)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id AD64B21F85F7 for <ietf@ietf.org>; Thu, 18 Oct 2012 03:29:06 -0700 (PDT)
Received: (qmail 11823 invoked from network); 18 Oct 2012 10:29:05 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 18 Oct 2012 10:29:05 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=507fd9f1.xn--i8sz2z.k1208; i=johnl@user.iecc.com; bh=O7JWDA6TPx2wwjyiSCmJpAcigqj1YwWc1/UxRuavKSo=; b=VTwSXz1qu39lzdPakfBoAkcWlluYsB+wp4wAwoMGzimfYm7bAAiovgIWvK8sKszOhCU7rRbCofzF1mI4MP8H1WlXG3ployVv0dqYPcU6VaWXPwUsRFP4akDv0pUohX1niJF1DZS/mGfcIaZjPgmUUs2ycgubePufaKXUX9ZJPdM=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=507fd9f1.xn--i8sz2z.k1208; olt=johnl@user.iecc.com; bh=O7JWDA6TPx2wwjyiSCmJpAcigqj1YwWc1/UxRuavKSo=; b=zHR4SToItl8Xb6/c66f5/AGCCTGbawoLXmfYtoyFvScuOvCoWR4GOQuOhVDeYc9pB6q2n8elN8mZ60AJMpgJUlj6yFeCdT2aybIuUXL1wGceCEjvWp0lZ8xtd9jZ3Qe/ErwQ3IhZ8+m9qo9Uqjbk87fwQK1xRzWOgIla14tSslY=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 18 Oct 2012 10:28:42 -0000
Message-ID: <20121018102842.3183.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: Gen-ART LC review of draft-leiba-5322upd-from-group-06
In-Reply-To: <CALaySJLex2ozmTMByO8=mRmu-fETX-TDRk7CdMedz5nDxjT6vA@mail.gmail.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
Cc: barryleiba@computer.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Oct 2012 10:29:08 -0000

>So, is it better to put in a sentence about representing non-ASCII
>text in the group name without including a replyable address?

The main motivation is to provide a syntax for a non-replyable address
in From: and Sender: headers for cases where that is appropriate.  See
the EAI downgrade documents for a concrete example.

A secondary motivation is to remove an arcane restriction that has not
turned out to be useful in practice.

R's,
John

From barryleiba@gmail.com  Thu Oct 18 04:13:19 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 EC19D21F8688; Thu, 18 Oct 2012 04:13:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.094
X-Spam-Level: 
X-Spam-Status: No, score=-103.094 tagged_above=-999 required=5 tests=[AWL=-0.117, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fsoRT7XUQYD9; Thu, 18 Oct 2012 04:13:18 -0700 (PDT)
Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id 12A1A21F8685; Thu, 18 Oct 2012 04:13:15 -0700 (PDT)
Received: by mail-vb0-f44.google.com with SMTP id fc26so9552156vbb.31 for <multiple recipients>; Thu, 18 Oct 2012 04:13:15 -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=W/U2vijy17iOKl5oFvrgrbw60CdbhHBXVW+6pjwNehY=; b=ijRH4MbTkO93i+Ofz6sIQpxKcHeK2uyWww90Uckeqfqlj0TY4YwPk0Y6rw/ABC1iH7 o/MbT1xpHhPCFnaX7ATsurmhI4KgG1ILV5tSrwpNPkqEC7rzMRJB7Oz/Mro2VLiPMptl bVUMOlKEPt1AFgWb35UQCB5NBefN5Ufeeb/ZYxDb0NnNzCF2ljh777cPYBkp7ukS+aDo WPVG1e0vK/5JW9MZjTYS53ZvpfCm6gv7HRiwWRYDIvuk+n1Z1rmyGVsIeefBAbwPA0uz gYAV24WBXEhQ22Q/M1b625CSz26pgkvAeL4N4uxLK3beo8+Jdk8/AzHOpDCacWB/RuXZ y8Og==
MIME-Version: 1.0
Received: by 10.58.86.36 with SMTP id m4mr14950266vez.14.1350558795399; Thu, 18 Oct 2012 04:13:15 -0700 (PDT)
Sender: barryleiba@gmail.com
Received: by 10.58.28.231 with HTTP; Thu, 18 Oct 2012 04:13:15 -0700 (PDT)
In-Reply-To: <507F5249.2090507@dcrocker.net>
References: <010301cdac4d$cfa70060$6ef50120$@gmail.com> <01OLIW8VNVCU00008S@mauve.mrochek.com> <507EF95D.5090007@dcrocker.net> <01OLIXV2SU4O00008S@mauve.mrochek.com> <5B0F81787945877A5CC3794B@JcK-HP8200.jck.com> <01OLJ38YAL9600008S@mauve.mrochek.com> <507F3CEA.2010306@dcrocker.net> <01OLJ9JAK8SQ00008S@mauve.mrochek.com> <507F5249.2090507@dcrocker.net>
Date: Thu, 18 Oct 2012 07:13:15 -0400
X-Google-Sender-Auth: JuQ-vsnNQA2rdg_REp7--4tWNRU
Message-ID: <CALaySJKD+JbkOuZsC7wQtNNLHBP-4a_=DNfQ0XkQWoCq78-JGg@mail.gmail.com>
Subject: Re: Gen-ART LC review of draft-leiba-5322upd-from-group-06
From: Barry Leiba <barryleiba@computer.org>
To: dcrocker@bbiw.net
Content-Type: text/plain; charset=ISO-8859-1
Cc: Ned Freed <ned.freed@mrochek.com>, draft-leiba-5322upd-from-group.all@tools.ietf.org, ned+ietf@mauve.mrochek.com, gen-art@ietf.org, johnl@taugh.com, John C Klensin <john-ietf@jck.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Oct 2012 11:13:19 -0000

On Wed, Oct 17, 2012 at 8:50 PM, Dave Crocker <dhc@dcrocker.net> wrote:
>> I see no way to explain the narrow EAI use case in this context
>> without either dragging in a whole bunch of EAI that has no business
>> being here or leaving various things dangling.
>
> ack. mumble.
>
> So I'll suggest a bit of an amalgam, including a cross reference of the type
> I prefer to avoid:
>
>    1. State that this removes a restriction that was never essential.
>
>    2. State that the timing of this removal is to accomodate EAI and for its
> use of the now-available features, see [RFCxxxx].


On Thu, Oct 18, 2012 at 6:28 AM, John Levine <johnl@taugh.com> wrote
(with a large part of this distribution list removed):
>>So, is it better to put in a sentence about representing non-ASCII
>>text in the group name without including a replyable address?
>
> The main motivation is to provide a syntax for a non-replyable address
> in From: and Sender: headers for cases where that is appropriate.  See
> the EAI downgrade documents for a concrete example.
>
> A secondary motivation is to remove an arcane restriction that has not
> turned out to be useful in practice.

Dave and John (Levine) are both suggesting an informative reference
from this document to some piece of the EAI documents (which I guess
should be one or both of draft-ietf-eai-5738bis, Section 7, and
draft-ietf-eai-popimap-downgrade, Section 3.2.1).

Ned and John (Klensin), can you live with that (I know it's not your
preference).  All: which (or both) should the reference be to?

Barry

From dhc@dcrocker.net  Thu Oct 18 05:28:18 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 50C8421F8700 for <ietf@ietfa.amsl.com>; Thu, 18 Oct 2012 05:28:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.566
X-Spam-Level: 
X-Spam-Status: No, score=-6.566 tagged_above=-999 required=5 tests=[AWL=0.033,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id maxlEs3CW1tU for <ietf@ietfa.amsl.com>; Thu, 18 Oct 2012 05:28:17 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id C5DAC21F86F3 for <ietf@ietf.org>; Thu, 18 Oct 2012 05:28:16 -0700 (PDT)
Received: from [192.168.1.6] (adsl-67-127-59-48.dsl.pltn13.pacbell.net [67.127.59.48]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q9ICSC6K007625 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 18 Oct 2012 05:28:12 -0700
Message-ID: <507FF5DB.5030106@dcrocker.net>
Date: Thu, 18 Oct 2012 05:28:11 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121005 Thunderbird/16.0
MIME-Version: 1.0
To: John Levine <johnl@taugh.com>
Subject: Re: Gen-ART LC review of draft-leiba-5322upd-from-group-06
References: <20121018102842.3183.qmail@joyce.lan>
In-Reply-To: <20121018102842.3183.qmail@joyce.lan>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Thu, 18 Oct 2012 05:28:13 -0700 (PDT)
Cc: barryleiba@computer.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Oct 2012 12:28:18 -0000

small tweaks:

On 10/18/2012 3:28 AM, John Levine wrote:
>> So, is it better to put in a sentence about representing non-ASCII
>> text in the group name without including a replyable address?
>
> The main motivation is to provide a syntax for a non-replyable address
> in From: and Sender: headers for cases where that is appropriate.  See
> the EAI downgrade documents for a concrete example.

      The main motivation is to support an alternate address, such as 
one which might not be a valid reply address, in the From: and Sender: 
header fields, for cases where that is appropriate... example.


> A secondary motivation is to remove an arcane restriction that has not
> turned out to be useful in practice.


-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From john-ietf@jck.com  Thu Oct 18 06:46:02 2012
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6076221F8779; Thu, 18 Oct 2012 06:46:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.529
X-Spam-Level: 
X-Spam-Status: No, score=-102.529 tagged_above=-999 required=5 tests=[AWL=0.070, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BYU-HmWi9H6N; Thu, 18 Oct 2012 06:46:01 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 8275D21F8740; Thu, 18 Oct 2012 06:46:01 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1TOqPt-0000iR-HU; Thu, 18 Oct 2012 09:45:41 -0400
Date: Thu, 18 Oct 2012 09:45:35 -0400
From: John C Klensin <john-ietf@jck.com>
To: Barry Leiba <barryleiba@computer.org>, dcrocker@bbiw.net
Subject: Re: Gen-ART LC review of draft-leiba-5322upd-from-group-06
Message-ID: <E73A2748BBE3FA6E1EE3A2C3@JcK-HP8200.jck.com>
In-Reply-To: <CALaySJKD+JbkOuZsC7wQtNNLHBP-4a_=DNfQ0XkQWoCq78-JGg@mail.gmail.com>
References: <010301cdac4d$cfa70060$6ef50120$@gmail.com> <01OLIW8VNVCU00008S@mauve.mrochek.com> <507EF95D.5090007@dcrocker.net> <01OLIXV2SU4O00008S@mauve.mrochek.com> <5B0F81787945877A5CC3794B@JcK-HP8200.jck.com> <01OLJ38YAL9600008S@mauve.mrochek.com> <507F3CEA.2010306@dcrocker.net> <01OLJ9JAK8SQ00008S@mauve.mrochek.com> <507F5249.2090507@dcrocker.net> <CALaySJKD+JbkOuZsC7wQtNNLHBP-4a_=DNfQ0XkQWoCq78-JGg@mail.gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: Ned Freed <ned.freed@mrochek.com>, draft-leiba-5322upd-from-group.all@tools.ietf.org, ned+ietf@mauve.mrochek.com, gen-art@ietf.org, johnl@taugh.com, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Oct 2012 13:46:03 -0000

--On Thursday, October 18, 2012 07:13 -0400 Barry Leiba
<barryleiba@computer.org> wrote:

> On Wed, Oct 17, 2012 at 8:50 PM, Dave Crocker
> <dhc@dcrocker.net> wrote:
>>> I see no way to explain the narrow EAI use case in this
>>> context without either dragging in a whole bunch of EAI that
>>> has no business being here or leaving various things
>>> dangling.
>> 
>> ack. mumble.
>> 
>> So I'll suggest a bit of an amalgam, including a cross
>> reference of the type I prefer to avoid:
>> 
>>    1. State that this removes a restriction that was never
>>    essential.
>> 
>>    2. State that the timing of this removal is to accomodate
>>    EAI and for its use of the now-available features, see
>> [RFCxxxx].
> 
> 
> On Thu, Oct 18, 2012 at 6:28 AM, John Levine <johnl@taugh.com>
> wrote (with a large part of this distribution list removed):
>>> So, is it better to put in a sentence about representing
>>> non-ASCII text in the group name without including a
>>> replyable address?
>> 
>> The main motivation is to provide a syntax for a
>> non-replyable address in From: and Sender: headers for cases
>> where that is appropriate.  See the EAI downgrade documents
>> for a concrete example.
>> 
>> A secondary motivation is to remove an arcane restriction
>> that has not turned out to be useful in practice.
> 
> Dave and John (Levine) are both suggesting an informative
> reference from this document to some piece of the EAI
> documents (which I guess should be one or both of
> draft-ietf-eai-5738bis, Section 7, and
> draft-ietf-eai-popimap-downgrade, Section 3.2.1).
> 
> Ned and John (Klensin), can you live with that (I know it's
> not your preference). 

As I said earlier, I can live with almost anything if it is
correct and allows us to move forward.  I am, however, getting
more concerned about the consequences to the virtual 5322bis and
its future instantiation if we go down these paths.  I would
really not like to be the relevant AD (or Pete-bis) trying to
defend leaving the explanation and reference out of 5322bis
given that they were important enough to include in this
document and, if the explanation and reference go into 5322bis,
why a large series of other references and explanations should
not be included.  I'd be a tad happier if this explanatory stuff
when into an appendix rather than the text.  

Using a different part of the EAI work as an example, the idea
that it would take little work to get from 5322 to 5322bis goes
completely out the window if the explanation of the syntax of
header fields has to say, effectively, "restricted to ASCII
except when they are not" followed by an explanation and
references.

If you do decide to do this, I slightly prefer Dave's
formulation to John(Levine)'s and prefer my earlier formulation
to either.  Borrowing a bit from Ned, 

* this restriction is inappropriate given contemporary
	practice, 
* its incorporation as a syntax rule rather than an
	applicability restriction was a matter of convenience
	that turned out to be a mistake, so
* we are converting it to an applicability
	restriction with the main motivation being to permit an
	identifiable (or named) but non-replyable
	backward-pointing address where that is necessary and
	the special considerations associated with "<>" don't
	apply.**
 and, if necessary,
* here is a pointer to the application that motivated us
	to move forward at this particular time.

As evidence of how silly the syntax restriction is, 5322 syntax
allows a group, non-replyable, address in the one field whose
sole purpose is to provide an address to which one is supposed
to reply ("Reply-to:" of course), creating what might be a high
in silly states.

** Yeah, I know that 5322 doesn't permit "<>" except in
	a Return-path, but I've seen that restriction
	un-enforced many times too.  We could have decided to
	make "From:" and "Sender:" use "mailbox[-list] / path"
	instead of allowing groups, but the group preserves
	somewhat more information -- information that 
   popimap-downgrade very much needs.  I don't think 
   that explanation belongs in 5322 either.

>  All: which (or both) should the reference be to?

To the extent to which an explanation or examples are needed, it
has to be popimap-downgrade.  But that document is not
particularly well-suited for the purpose, it doesn't contain an
explanation of why empty groups were  chosen in preference to
"<>" and more Downgraded-* headers (and shouldn't unless we are
going to start documenting every discarded design alternative),
and we still hope that it turns out to be a moderately
short-term transition mechanism that can gradually fade away
into a historical footnote.

Mumble.
    john


From dcrocker@bbiw.net  Thu Oct 18 06:51:00 2012
Return-Path: <dcrocker@bbiw.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 68F5721F875A; Thu, 18 Oct 2012 06:51:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.413
X-Spam-Level: 
X-Spam-Status: No, score=-6.413 tagged_above=-999 required=5 tests=[AWL=0.186,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NDBn-7Tg62ub; Thu, 18 Oct 2012 06:50:59 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 79E7721F8758; Thu, 18 Oct 2012 06:50:59 -0700 (PDT)
Received: from [192.168.1.6] (adsl-67-127-59-48.dsl.pltn13.pacbell.net [67.127.59.48]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q9IDosbT008905 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 18 Oct 2012 06:50:55 -0700
Message-ID: <5080093D.2050406@bbiw.net>
Date: Thu, 18 Oct 2012 06:50:53 -0700
From: Dave Crocker <dcrocker@bbiw.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121005 Thunderbird/16.0
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
Subject: Re: Gen-ART LC review of draft-leiba-5322upd-from-group-06
References: <010301cdac4d$cfa70060$6ef50120$@gmail.com> <01OLIW8VNVCU00008S@mauve.mrochek.com> <507EF95D.5090007@dcrocker.net> <01OLIXV2SU4O00008S@mauve.mrochek.com> <5B0F81787945877A5CC3794B@JcK-HP8200.jck.com> <01OLJ38YAL9600008S@mauve.mrochek.com> <507F3CEA.2010306@dcrocker.net> <01OLJ9JAK8SQ00008S@mauve.mrochek.com> <507F5249.2090507@dcrocker.net> <CALaySJKD+JbkOuZsC7wQtNNLHBP-4a_=DNfQ0XkQWoCq78-JGg@mail.gmail.com> <E73A2748BBE3FA6E1EE3A2C3@JcK-HP8200.jck.com>
In-Reply-To: <E73A2748BBE3FA6E1EE3A2C3@JcK-HP8200.jck.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Thu, 18 Oct 2012 06:50:55 -0700 (PDT)
Cc: Ned Freed <ned.freed@mrochek.com>, draft-leiba-5322upd-from-group.all@tools.ietf.org, ned+ietf@mauve.mrochek.com, gen-art@ietf.org, johnl@taugh.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: Thu, 18 Oct 2012 13:51:00 -0000

On 10/18/2012 6:45 AM, John C Klensin wrote:
> As I said earlier, I can live with almost anything if it is
> correct and allows us to move forward.  I am, however, getting
> more concerned about the consequences to the virtual 5322bis and
> its future instantiation if we go down these paths.  I would
> really not like to be the relevant AD (or Pete-bis) trying to
> defend leaving the explanation and reference out of 5322bis
> given that they were important enough to include in this
> document and, if the explanation and reference go into 5322bis,
> why a large series of other references and explanations should
> not be included.  I'd be a tad happier if this explanatory stuff
> when into an appendix rather than the text.


The job of the current draft is to be sufficient to its purpose.  Its 
purpose is to augment a base document with a specific revision.

An update segment document does not typically have the purpose of 
including extensive annotations for possible later use, attempting to 
anticipate or hypothesize later editing efforts, to revise the base 
document.

d/
-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From yiu_lee@cable.comcast.com  Wed Oct 17 17:46:32 2012
Return-Path: <yiu_lee@cable.comcast.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AB97921F862B; Wed, 17 Oct 2012 17:46:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.798
X-Spam-Level: 
X-Spam-Status: No, score=-103.798 tagged_above=-999 required=5 tests=[AWL=1.433, BAYES_00=-2.599, HOST_EQ_MODEMCABLE=1.368, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QXk9iY44ZBJz; Wed, 17 Oct 2012 17:46:31 -0700 (PDT)
Received: from cable.comcast.com (copdcavout01.cable.comcast.com [76.96.32.253]) by ietfa.amsl.com (Postfix) with ESMTP id 9E46421F8623; Wed, 17 Oct 2012 17:46:31 -0700 (PDT)
Received: from ([24.40.56.115]) by copdcavout01.cable.comcast.com with ESMTP  id C7WM3M1.38137703; Wed, 17 Oct 2012 18:23:03 -0600
Received: from PACDCEXMB05.cable.comcast.com ([169.254.7.147]) by PACDCEXHUB02.cable.comcast.com ([fe80::492e:3fa1:c2ad:e04e%13]) with mapi id 14.02.0318.001; Wed, 17 Oct 2012 20:46:26 -0400
From: "Lee, Yiu" <Yiu_Lee@Cable.Comcast.com>
To: "Black, David" <david.black@emc.com>, "roberta.maglione@telecomitalia.it" <roberta.maglione@telecomitalia.it>, "carlw@mcsr-labs.org" <carlw@mcsr-labs.org>, "christian.jacquenet@orange.com" <christian.jacquenet@orange.com>, "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>, "gen-art@ietf.org" <gen-art@ietf.org>
Subject: Re: Gen-ART review of draft-ietf-softwire-dslite-deployment-06
Thread-Topic: Gen-ART review of draft-ietf-softwire-dslite-deployment-06
Thread-Index: AQHNrMoAT7CfnR/9yUSA1hDdxxOKmg==
Date: Thu, 18 Oct 2012 00:46:24 +0000
Message-ID: <E3FAB1F4F41F3A45B287E8D9C53522FD37A7EC79@PACDCEXMB05.cable.comcast.com>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE7120DFAEF29@MX15A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.2.4.120824
x-originating-ip: [24.40.55.70]
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="B_3433351583_493034"
MIME-Version: 1.0
X-Mailman-Approved-At: Thu, 18 Oct 2012 09:03:21 -0700
Cc: "softwires@ietf.org" <softwires@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Oct 2012 00:46:32 -0000

--B_3433351583_493034
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit

Hi David,

Thanks very much for review the draft. Comments inline.

Thanks,
Yiu

On 10/15/12 7:10 PM, "Black, David" <david.black@emc.com> wrote:

>I am the assigned Gen-ART reviewer for this draft. For background on
>Gen-ART, please see the FAQ at
><http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>
>Please resolve these comments along with any other Last Call comments
>you may receive.
>
>Document: draft-ietf-softwire-dslite-deployment-06
>Reviewer: David L. Black
>Review Date: October 15, 2012
>IETF LC End Date: October 16, 2012
>IESG Telechat Date: October 25, 2012
>
>Summary:
>
>This draft is on the right track but has open issues, described in the
>review.
>
>This is a generally well-written draft that expands considerably on the
>brief
>deployment considerations for DS-Lite in Appendix A of RFC 6333.  The
>draft
>is clear and reasonably well-written, and a significant improvement on
>that
>RFC 6333 Appendix, although an understanding of RFC 6333 is necessary to
>understand this draft, which seems completely reasonable.
>
>The B4 and AFTR acronyms are clever - kudos to whomever came up with
>those.
>
>I found five open issues, all of which are minor.
>
>Minor Issues:
>
>[1] Ironically, the first issue is that something should be said about
>the relationship of this draft to Appendix A of RFC 6333.  It probably
>suffices to say that this draft expands on the material in that Appendix,
>as I see no need to specify that this draft updates RFC 6333 solely to
>change non-normative material in an Appendix.

[YL] In "Overview", we will add:

"This document expands Appendix A of RFC6333 and discusses various
DS-Lite deployment considerations for operators."

>
>[2] The MTU increase technique in Section 2.2 is a "may", which is
>consistent with Section 5.3 of RFC 6333.  OTOH, Section 2.2 of this
>draft should also discuss the AFTR resource exhaustion concern that
>described in Section 6.3 of RFC 6333, as that is a potential
>operational reason for an ISP to increase MTU size (e.g., if customer
>sourcing of large IPv4 packets is not sufficiently rare).

[YL] In 2.2, we will add:

"Note that reassembly at Tunnel Exit-Point is resource
	intensive. A large number of B4 may terminate on the same AFTR. If many B4
	fragment the packets, it would increase sufficient load to the AFTR for
	reassembly. We recommend the operator should increase the MTU size of the
IPv6
	network between B4 and AFTR to avoid fragmentation."

>
>[3] Section 2.7 refers to "the AFTR's internal interface".  There may be
>two internal interfaces, the physical IPv6 interface (outer header) and
>the tunnel's IPv4 interface (inner header).  The text should be clarified
>to indicate which interface is involved - it appears that the AFTR's
>physical IPv6 interface is intended in this section.

[YL] We replace "internal" to "IPv6"

>
>[4] Section 2.7 cites RFC 6333 for use of DHCPv6 with DS-Lite.  RFC 6334
>should be cited - either in addition to or instead of RFC 6333.

[YL] Fixed

>
>[5] Section 2.8 discusses IPv4 accounting at the AFTR, but notes that
>"the AFTR does not have detailed customer identity information."  Does
>that create a theft of service possibility?  If so, that possibility
>should be mentioned as a security consideration.  Also, Section 2.8
>ought to be expanded with a sentence or two explaining why the AFTR
>does not have that identity information, and in particular to explain
>whether and why it is unreasonable in some or all cases to expect
>that customer identity information be provided to the AFTR as part
>of provisioning each customer's softwire.

[YL] Good catch. Actually I believe AFTR "does" have both IPv4 and IPv6 to
identify the customer. I suggest we remove

"but it will potentially introduce some additional complexity because
   the AFTR does not have detailed customer identity information."

>
>Nits:
>
>Section 2.3 on MTU Considerations could usefully mention MTU discovery
>techniques, as possibilities for customer IPv4 traffic to adapt to a
>smaller IPv4 MTU.  If this is done, it would be useful to mention
>RFC 4821 in addition to the mention of RFC 1191 in RFC 6333.

[YL] We would consider RFC 4821. However, the challenge is I don't have
information how many current OS support RFC 4821. Since DS-lite is a
transition technology, it would be unreasonable to ask the OS company to
implement RFC 4821 for DS-lite.

>
>Section 2.4 should define "lawful intercept".  It would be helpful to
>cite a reference for this concept if something appropriate can be found.

[YL] We will find whether there is any reference to this concept. If we
can't find any, we would add an explanation in the draft.

>
>Section 2.5:
>- Are one or both types of logging recommended?

[YL] We tempted to recommend source-specific log. However, some regulators
require to use both and the regulations vary country from country, this is
why we left it open and let the operators to decide.

>- Last paragraph on p.4, "timestamped log" is not a good verb phrase.
>	"maintain a timestamped log of" would be a better replacement.

[YL] Fixed

>- Last paragraph in section, where is the batch file sent?

[YL] We will add:

"The files may be compressed before transferring to a repository server
	to better utilize bandwidth and storage."


>
>In Section 2.7, I'm having a hard time understanding which traffic is
>intended to be subject to the Outgoing Policies and the Incoming Policies.
>Expanding each of those two bullets to explain what traffic is subject
>to each class of policies would help.

[YL] Does this help?

Outgoing Policies apply to packets originating from B4 to IPv4 network.
Incoming Policies apply to packets originating from IPv4 network to B4.



>
>Section 3.2.2.2 uses 192.0.0.2/32 as an example IP address for the
>B4.  That section should also cross-reference Section 5.7 on RFC 6333
>on IP address assignment to B4s, as other IP addresses may be used.

[YL] Added the cite.

>
>idnits 2.12.13 found a tiny nit - draft-ietf-pcp-base is now at
>version 28.

[YL] Fixed.

>
>Thanks,
>--David
>----------------------------------------------------
>David L. Black, Distinguished Engineer
>EMC Corporation, 176 South St., Hopkinton, MA  01748
>+1 (508) 293-7953             FAX: +1 (508) 293-7786
>david.black@emc.com        Mobile: +1 (978) 394-7754
>----------------------------------------------------
>
>

--B_3433351583_493034
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"

MIIVmQYJKoZIhvcNAQcCoIIVijCCFYYCAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC
EzEwggU0MIIEHKADAgECAhEAzuhISIgzOwSitfbc2LN4WDANBgkqhkiG9w0BAQUFADCBkzEL
MAkGA1UEBhMCR0IxGzAZBgNVBAgTEkdyZWF0ZXIgTWFuY2hlc3RlcjEQMA4GA1UEBxMHU2Fs
Zm9yZDEaMBgGA1UEChMRQ09NT0RPIENBIExpbWl0ZWQxOTA3BgNVBAMTMENPTU9ETyBDbGll
bnQgQXV0aGVudGljYXRpb24gYW5kIFNlY3VyZSBFbWFpbCBDQTAeFw0xMjA4MjgwMDAwMDBa
Fw0xMzA4MjgyMzU5NTlaMCoxKDAmBgkqhkiG9w0BCQEWGXlpdV9sZWVAY2FibGUuY29tY2Fz
dC5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCscOeu5/EoYRdja1jb6L4x
o0TIevelc17NsPuRHfr2z3BGUMbfsJY1p0uXO9+inBQoBXwb07ac3SbOjA/6Ef3NlMPItWdT
RGeFL6e/sMju9RgVyJURFnFgp7tc2tffnPOupnKZeeRehXeEFjun6+GC6teb1kSMu+WMMaCa
D7/XSK+Q+F0Udc2Av0/gUCkGfTDpNnYwutfctEMRnle6EYUqmJMN4C0crEfovmYdMFFgJLKs
Wa5Cdc+naFoIqzW8AcZB6+1XUDTzFbgjqgUbFFZFPzVZqNxLDFNy4tn8VlRSp2jBhgwQHtk1
ZA+spFENaeUuebp4tczj0IHG683FhhWjAgMBAAGjggHpMIIB5TAfBgNVHSMEGDAWgBR6E04A
dFvGeGNkJ8Ev4qBbvHnFezAdBgNVHQ4EFgQUz03csl7CmjwQY+spX9VWeGb5sVQwDgYDVR0P
AQH/BAQDAgWgMAwGA1UdEwEB/wQCMAAwIAYDVR0lBBkwFwYIKwYBBQUHAwQGCysGAQQBsjEB
AwUCMBEGCWCGSAGG+EIBAQQEAwIFIDBGBgNVHSAEPzA9MDsGDCsGAQQBsjEBAgEBATArMCkG
CCsGAQUFBwIBFh1odHRwczovL3NlY3VyZS5jb21vZG8ubmV0L0NQUzBXBgNVHR8EUDBOMEyg
SqBIhkZodHRwOi8vY3JsLmNvbW9kb2NhLmNvbS9DT01PRE9DbGllbnRBdXRoZW50aWNhdGlv
bmFuZFNlY3VyZUVtYWlsQ0EuY3JsMIGIBggrBgEFBQcBAQR8MHowUgYIKwYBBQUHMAKGRmh0
dHA6Ly9jcnQuY29tb2RvY2EuY29tL0NPTU9ET0NsaWVudEF1dGhlbnRpY2F0aW9uYW5kU2Vj
dXJlRW1haWxDQS5jcnQwJAYIKwYBBQUHMAGGGGh0dHA6Ly9vY3NwLmNvbW9kb2NhLmNvbTAk
BgNVHREEHTAbgRl5aXVfbGVlQGNhYmxlLmNvbWNhc3QuY29tMA0GCSqGSIb3DQEBBQUAA4IB
AQBG7LORtWcmzDlw0N/D5AwfsSLe93essAqKFhJ+nt7SmMVBsxGzFnSsZGQHMYQ4UXtiVq9A
NjtPk00F3DC3QGxe4mxdwF9LzeYHpHMpCHTzNyilSimKZolLNBO+MO/U0u79rdF2W+dOAwkB
dzroWBxK+yMhijJn2DCE/1pgxqBz+c9zbAtJYPVpgbeGNvvfIp6CA/JYsupQNqPX49a4MdJ3
L9yXLTiegSE8uPUlCB3sHZclQOXAttuMewpcKDoIC4wZgERKQqRH61PQO100GLKUO+VrTq+f
xNkjOAqA+dih6QO5Djbv3qcMTCcAChJQYK8BS7jved8XgEVa0Ihz7oWKMIIFGjCCBAKgAwIB
AgIQbRnqpxlPajMi5iIyeqpx3jANBgkqhkiG9w0BAQUFADCBrjELMAkGA1UEBhMCVVMxCzAJ
BgNVBAgTAlVUMRcwFQYDVQQHEw5TYWx0IExha2UgQ2l0eTEeMBwGA1UEChMVVGhlIFVTRVJU
UlVTVCBOZXR3b3JrMSEwHwYDVQQLExhodHRwOi8vd3d3LnVzZXJ0cnVzdC5jb20xNjA0BgNV
BAMTLVVUTi1VU0VSRmlyc3QtQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBFbWFpbDAeFw0x
MTA0MjgwMDAwMDBaFw0yMDA1MzAxMDQ4MzhaMIGTMQswCQYDVQQGEwJHQjEbMBkGA1UECBMS
R3JlYXRlciBNYW5jaGVzdGVyMRAwDgYDVQQHEwdTYWxmb3JkMRowGAYDVQQKExFDT01PRE8g
Q0EgTGltaXRlZDE5MDcGA1UEAxMwQ09NT0RPIENsaWVudCBBdXRoZW50aWNhdGlvbiBhbmQg
U2VjdXJlIEVtYWlsIENBMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAkoSEW0tX
mNReL4uk4UDIo1NYX2Zl8TJO958yfVXQeExVt0KU4PkncQfFxmmkuTLE8UAakMwnVmJ/F7Vx
aa7lIBvky2NeYMqiQfZq4aP/uN8fSG1lQ4wqLitjOHffsReswtqCAtbUMmrUZ28gE49cNfrl
VICv2HEKHTcKAlBTbJUdqRAUtJmVWRIx/wmi0kzcUtve4kABW0ho3cVKtODtJB86r3FfB+Os
vxQ7sCVxaD30D9YXWEYVgTxoi4uDD216IVfmNLDbMn7jSuGlUnJkJpFOpZIP/+CxYP0ab2hR
mWONGoulzEKbm30iY9OpoPzOnpDfRBn0XFs1uhbzp5v/wQIDAQABo4IBSzCCAUcwHwYDVR0j
BBgwFoAUiYJnfcSdJnAAS7RQSHzePa4Ebn0wHQYDVR0OBBYEFHoTTgB0W8Z4Y2QnwS/ioFu8
ecV7MA4GA1UdDwEB/wQEAwIBBjASBgNVHRMBAf8ECDAGAQH/AgEAMBEGA1UdIAQKMAgwBgYE
VR0gADBYBgNVHR8EUTBPME2gS6BJhkdodHRwOi8vY3JsLnVzZXJ0cnVzdC5jb20vVVROLVVT
RVJGaXJzdC1DbGllbnRBdXRoZW50aWNhdGlvbmFuZEVtYWlsLmNybDB0BggrBgEFBQcBAQRo
MGYwPQYIKwYBBQUHMAKGMWh0dHA6Ly9jcnQudXNlcnRydXN0LmNvbS9VVE5BZGRUcnVzdENs
aWVudF9DQS5jcnQwJQYIKwYBBQUHMAGGGWh0dHA6Ly9vY3NwLnVzZXJ0cnVzdC5jb20wDQYJ
KoZIhvcNAQEFBQADggEBAIXWvnhXVW0zf0RS/kLVBqgBA4CK+w2y/Uq/9q9BSfUbWsXSrRtz
bj7pJnzmTJjBMCjfy/tCPKElPgp11tA9OYZm0aGbtU2bb68obB2v5ep0WqjascDxdXovnrqT
ecr+4pEeVnSy+I3T4ENyG+2P/WA5IEf7i686ZUg8mD2lJb+972DgSeUWyOs/Q4Pw4O4NwdPN
M1+b0L1garM7/vrUyTo8H+2b/5tJM75CKTmD7jNpLoKdRU2oadqAGx490hpdfEeZpZsIbRKZ
htZdVwcbpzC+S0lEuJB+ytF5OOu0M/qgOl0mWJ5hVRi0IdWZ1eBDQEIwvuql55TSsP7zdfl/
bucwggSdMIIDhaADAgECAhA0PekrrCc0/4/LNJT7zHBUMA0GCSqGSIb3DQEBBQUAMG8xCzAJ
BgNVBAYTAlNFMRQwEgYDVQQKEwtBZGRUcnVzdCBBQjEmMCQGA1UECxMdQWRkVHJ1c3QgRXh0
ZXJuYWwgVFRQIE5ldHdvcmsxIjAgBgNVBAMTGUFkZFRydXN0IEV4dGVybmFsIENBIFJvb3Qw
HhcNMDUwNjA3MDgwOTEwWhcNMjAwNTMwMTA0ODM4WjCBrjELMAkGA1UEBhMCVVMxCzAJBgNV
BAgTAlVUMRcwFQYDVQQHEw5TYWx0IExha2UgQ2l0eTEeMBwGA1UEChMVVGhlIFVTRVJUUlVT
VCBOZXR3b3JrMSEwHwYDVQQLExhodHRwOi8vd3d3LnVzZXJ0cnVzdC5jb20xNjA0BgNVBAMT
LVVUTi1VU0VSRmlyc3QtQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBFbWFpbDCCASIwDQYJ
KoZIhvcNAQEBBQADggEPADCCAQoCggEBALI5haTyfatBO2JGN67NwWB1vDll+UoaR6K5zEjM
apjVTTUZuaRC5c5J4oovHnzSMQfHTrSDZJ0uKdWiZMSFvYVRNXmkTmiQexx6pJKoF/KYFfKT
zMmkMpW7DE8wvZigC4vlbhuiRvp4vKJvq1lepS/Pytptqi/rrKGzaqq3Lmc1i3nhHmmI4uZG
zaCl6r4LznY6eg6b6vzaJ1s9cx8i5khhxkzzabGoLhu21DEgLLyCio6kDqXXiUP8FlqvHXHX
EVnauocNr/rz4cLwpMVnjNbWVDreCqS6A3ezZcj9HtN0YqoYymiTHqGFfvVHZcv4TVcodNI0
/zC27vZiMBSMLOsCAwEAAaOB9DCB8TAfBgNVHSMEGDAWgBStvZh6NLQm9/rEJlTvA73gJMtU
GjAdBgNVHQ4EFgQUiYJnfcSdJnAAS7RQSHzePa4Ebn0wDgYDVR0PAQH/BAQDAgEGMA8GA1Ud
EwEB/wQFMAMBAf8wEQYDVR0gBAowCDAGBgRVHSAAMEQGA1UdHwQ9MDswOaA3oDWGM2h0dHA6
Ly9jcmwudXNlcnRydXN0LmNvbS9BZGRUcnVzdEV4dGVybmFsQ0FSb290LmNybDA1BggrBgEF
BQcBAQQpMCcwJQYIKwYBBQUHMAGGGWh0dHA6Ly9vY3NwLnVzZXJ0cnVzdC5jb20wDQYJKoZI
hvcNAQEFBQADggEBAAG8nONjKLDzMQHC33vdYqABnSMxD5ySc1NR6h9M+tafxMovZ354Mw90
FrmRh5H1iib6ZHAA2B75CwRiUIeTgdTa9SPbNLuFVrRwNG54gzcehRzFERWSX4cXvaxq/fHC
0cyJX7F88D5R8jXzfOxgmGs6K+Dv37N9huu1G/Vb7KJ8mBPXAFC50S1z3gN4dOEFhTFey5q5
nZTGuZQ3dXLcRPtn6PD6JR5Sp9ol6UfgoMc8oE6xCjb7d0if75eK+7T+45QUqIO8XC0/0mBx
YO7CcYIM6Yg249ogtKOgbKqWS7iAjnXKSQf2OxS639wF2Z/b4LLmTaB4JufnLW5/X8YeiBUw
ggQ2MIIDHqADAgECAgEBMA0GCSqGSIb3DQEBBQUAMG8xCzAJBgNVBAYTAlNFMRQwEgYDVQQK
EwtBZGRUcnVzdCBBQjEmMCQGA1UECxMdQWRkVHJ1c3QgRXh0ZXJuYWwgVFRQIE5ldHdvcmsx
IjAgBgNVBAMTGUFkZFRydXN0IEV4dGVybmFsIENBIFJvb3QwHhcNMDAwNTMwMTA0ODM4WhcN
MjAwNTMwMTA0ODM4WjBvMQswCQYDVQQGEwJTRTEUMBIGA1UEChMLQWRkVHJ1c3QgQUIxJjAk
BgNVBAsTHUFkZFRydXN0IEV4dGVybmFsIFRUUCBOZXR3b3JrMSIwIAYDVQQDExlBZGRUcnVz
dCBFeHRlcm5hbCBDQSBSb290MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAt/ca
M+byAAQtOeBOW+0fvGwPzbX6I7bO3psRM5ekKUx9k5+9SryT7QMa44/P5W1QWtaXKZRagLBJ
etsulf24yr83OC0ePpFBrXBWx/BPP+gynnTKyJBU6cZfD3idmkA8Dqxhql4Uj56HoWpQ3Nea
Tq8Fs6ZxlJxxs1BgCscTnTgHhgKo6ahpJhiQq0ywTyOrOk+E2N/On+Fpb7vXQtdrROTHre5t
QV9yWnEIN7N5ZaRZoJQ39wAvDcKSctrQOHLbFKhFxF0qfbe01sTurM0TRLfJK91DACX6Yblp
algjEbenM49WdVn1zSnXRrcKK2W200JvFbK4e/vv6V1T1TRaJwIDAQABo4HcMIHZMB0GA1Ud
DgQWBBStvZh6NLQm9/rEJlTvA73gJMtUGjALBgNVHQ8EBAMCAQYwDwYDVR0TAQH/BAUwAwEB
/zCBmQYDVR0jBIGRMIGOgBStvZh6NLQm9/rEJlTvA73gJMtUGqFzpHEwbzELMAkGA1UEBhMC
U0UxFDASBgNVBAoTC0FkZFRydXN0IEFCMSYwJAYDVQQLEx1BZGRUcnVzdCBFeHRlcm5hbCBU
VFAgTmV0d29yazEiMCAGA1UEAxMZQWRkVHJ1c3QgRXh0ZXJuYWwgQ0EgUm9vdIIBATANBgkq
hkiG9w0BAQUFAAOCAQEAsJvghSXC1iPiD5YGkp1BmJzZhHmB2R5bFAcjNmWPsNh3u6xBbEdg
g1Gw+TI95/z2JhPHgBalv1r8h894eYkhmuJMBwqGNbzy3lHE0pa33H5O7nD9HDnrDAJRFC2O
vRbgwd9Gdeckrez0QrSFk3AQZ7qdBjVKGNMresxRQqF6Y9Hmu6HFK8I2vhMN5r1jfnl7pwkN
QKtq3Y+Kw/b2jBpCBVHURfWfp2IhaBUgQzyZ53y9JNipkRdziD9WGzE4GLRxD5rNyA6eji4b
4YyYg8sfMfFETMYEc0l2YA/H+L0XgGsu6cxMDlqaeQ8gCi7VnmMmHlWSlNiCF1p70LzHj06G
BDGCAjAwggIsAgEBMIGpMIGTMQswCQYDVQQGEwJHQjEbMBkGA1UECBMSR3JlYXRlciBNYW5j
aGVzdGVyMRAwDgYDVQQHEwdTYWxmb3JkMRowGAYDVQQKExFDT01PRE8gQ0EgTGltaXRlZDE5
MDcGA1UEAxMwQ09NT0RPIENsaWVudCBBdXRoZW50aWNhdGlvbiBhbmQgU2VjdXJlIEVtYWls
IENBAhEAzuhISIgzOwSitfbc2LN4WDAJBgUrDgMCGgUAoF0wIwYJKoZIhvcNAQkEMRYEFMMH
sMOZ10JTh9owhxBX+FD1xKU7MBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcN
AQkFMQ8XDTEyMTAxODAwNDYyMlowDQYJKoZIhvcNAQEBBQAEggEAVXCxAZKhMeCjLddBOMAc
euaqgybURvaW20hpdAFWozQtHwiE4PuiVqDfyXb2yUkarjFljj7hCe5skRPcCVpfRzmjzXwy
+W5TQf1Slf431sNvR2xy5AW2NP57EnbGu1s7Mtvy5PC1eNBa68NS3Sxofveh1PJho7ca/E6m
dY+IsVuHgjgx3HpAhbehKLEhJ48pWXc9eygaYc94SUhjfWFKVPeY7h43LN4/hDsvOQVpFbcO
4Tv3UiBrr7XDuRHPEKnwMuh0RGP9JePzKB+/QSMfjzUf3J3UT0nZe2ZDQvCX0S51Jq9vies8
wLPlTa+1QYlkVcgQkJb7A5vTvhRgmBsF+A==

--B_3433351583_493034--

From david.black@emc.com  Wed Oct 17 18:12:19 2012
Return-Path: <david.black@emc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A294421F86AB; Wed, 17 Oct 2012 18:12:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.535
X-Spam-Level: 
X-Spam-Status: No, score=-102.535 tagged_above=-999 required=5 tests=[AWL=0.064, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Xd2PuNFkJr2t; Wed, 17 Oct 2012 18:12:17 -0700 (PDT)
Received: from mexforward.lss.emc.com (hop-nat-141.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id D936421F8622; Wed, 17 Oct 2012 18:12:16 -0700 (PDT)
Received: from hop04-l1d11-si03.isus.emc.com (HOP04-L1D11-SI03.isus.emc.com [10.254.111.23]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q9I1CCt5010771 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 17 Oct 2012 21:12:12 -0400
Received: from mailhub.lss.emc.com (mailhub.lss.emc.com [10.254.222.129]) by hop04-l1d11-si03.isus.emc.com (RSA Interceptor); Wed, 17 Oct 2012 21:11:54 -0400
Received: from mxhub20.corp.emc.com (mxhub20.corp.emc.com [10.254.93.49]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q9I1BrQc017300; Wed, 17 Oct 2012 21:11:53 -0400
Received: from mx15a.corp.emc.com ([169.254.1.83]) by mxhub20.corp.emc.com ([10.254.93.49]) with mapi; Wed, 17 Oct 2012 21:11:53 -0400
From: "Black, David" <david.black@emc.com>
To: "Lee, Yiu" <Yiu_Lee@cable.comcast.com>, "roberta.maglione@telecomitalia.it" <roberta.maglione@telecomitalia.it>, "carlw@mcsr-labs.org" <carlw@mcsr-labs.org>, "christian.jacquenet@orange.com" <christian.jacquenet@orange.com>, "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>, "gen-art@ietf.org" <gen-art@ietf.org>
Date: Wed, 17 Oct 2012 21:11:51 -0400
Subject: RE: Gen-ART review of draft-ietf-softwire-dslite-deployment-06
Thread-Topic: Gen-ART review of draft-ietf-softwire-dslite-deployment-06
Thread-Index: AQHNrMoAT7CfnR/9yUSA1hDdxxOKmpe+Pf7g
Message-ID: <8D3D17ACE214DC429325B2B98F3AE7120DFAF3B9@MX15A.corp.emc.com>
References: <8D3D17ACE214DC429325B2B98F3AE7120DFAEF29@MX15A.corp.emc.com> <E3FAB1F4F41F3A45B287E8D9C53522FD37A7EC79@PACDCEXMB05.cable.comcast.com>
In-Reply-To: <E3FAB1F4F41F3A45B287E8D9C53522FD37A7EC79@PACDCEXMB05.cable.comcast.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
X-Mailman-Approved-At: Thu, 18 Oct 2012 09:03:21 -0700
Cc: "softwires@ietf.org" <softwires@ietf.org>, "Black, David" <david.black@emc.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Oct 2012 01:12:19 -0000

Yiu,

Thank you for your responses - most of them look fine, and in=20
particular anything that I don't comment on here is acceptable to me.

> [YL] In 2.2, we will add:
>=20
> "Note that reassembly at Tunnel Exit-Point is resource
> 	intensive. A large number of B4 may terminate on the same AFTR. If many =
B4
> 	fragment the packets, it would increase sufficient load to the AFTR for
> 	reassembly. We recommend the operator should increase the MTU size of th=
e IPv6
> 	network between B4 and AFTR to avoid fragmentation."

I would change "is" to "may be" in the first line.

> >[5] Section 2.8 discusses IPv4 accounting at the AFTR, but notes that
> >"the AFTR does not have detailed customer identity information."  Does
> >that create a theft of service possibility?  If so, that possibility
> >should be mentioned as a security consideration.  Also, Section 2.8
> >ought to be expanded with a sentence or two explaining why the AFTR
> >does not have that identity information, and in particular to explain
> >whether and why it is unreasonable in some or all cases to expect
> >that customer identity information be provided to the AFTR as part
> >of provisioning each customer's softwire.
>=20
> [YL] Good catch. Actually I believe AFTR "does" have both IPv4 and IPv6 t=
o
> identify the customer. I suggest we remove
>=20
> "but it will potentially introduce some additional complexity because
>    the AFTR does not have detailed customer identity information."

That's definitely an easy way to address that issue, and it's fine with me.

> >Section 2.3 on MTU Considerations could usefully mention MTU discovery
> >techniques, as possibilities for customer IPv4 traffic to adapt to a
> >smaller IPv4 MTU.  If this is done, it would be useful to mention
> >RFC 4821 in addition to the mention of RFC 1191 in RFC 6333.
>=20
> [YL] We would consider RFC 4821. However, the challenge is I don't have
> information how many current OS support RFC 4821. Since DS-lite is a
> transition technology, it would be unreasonable to ask the OS company to
> implement RFC 4821 for DS-lite.

That's ok - this was a nit.

> >- Are one or both types of logging recommended?
>=20
> [YL] We tempted to recommend source-specific log. However, some regulator=
s
> require to use both and the regulations vary country from country, this i=
s
> why we left it open and let the operators to decide.

Please add a version of your explanation to the draft.

> >In Section 2.7, I'm having a hard time understanding which traffic is
> >intended to be subject to the Outgoing Policies and the Incoming Policie=
s.
> >Expanding each of those two bullets to explain what traffic is subject
> >to each class of policies would help.
>=20
> [YL] Does this help?
>=20
> Outgoing Policies apply to packets originating from B4 to IPv4 network.
> Incoming Policies apply to packets originating from IPv4 network to B4.

Yes, that's clearer, although the B4 is not the network endpoint for any
of that traffic.  I suggest:

Outgoing Policies apply to packets originating from behind the B4 with=20
a destination on the IPv4 network.

Incoming Policies apply to packets originating from the IPv4 network to
a destination behind the B4.

Thanks,
--David


> -----Original Message-----
> From: Lee, Yiu [mailto:Yiu_Lee@cable.comcast.com]
> Sent: Wednesday, October 17, 2012 8:46 PM
> To: Black, David; roberta.maglione@telecomitalia.it; carlw@mcsr-labs.org;
> christian.jacquenet@orange.com; mohamed.boucadair@orange.com; gen-art@iet=
f.org
> Cc: softwires@ietf.org; ietf@ietf.org; Ralph Droms
> Subject: Re: Gen-ART review of draft-ietf-softwire-dslite-deployment-06
>=20
> Hi David,
>=20
> Thanks very much for review the draft. Comments inline.
>=20
> Thanks,
> Yiu
>=20
> On 10/15/12 7:10 PM, "Black, David" <david.black@emc.com> wrote:
>=20
> >I am the assigned Gen-ART reviewer for this draft. For background on
> >Gen-ART, please see the FAQ at
> ><http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
> >
> >Please resolve these comments along with any other Last Call comments
> >you may receive.
> >
> >Document: draft-ietf-softwire-dslite-deployment-06
> >Reviewer: David L. Black
> >Review Date: October 15, 2012
> >IETF LC End Date: October 16, 2012
> >IESG Telechat Date: October 25, 2012
> >
> >Summary:
> >
> >This draft is on the right track but has open issues, described in the
> >review.
> >
> >This is a generally well-written draft that expands considerably on the =
brief
> >deployment considerations for DS-Lite in Appendix A of RFC 6333.  The dr=
aft
> >is clear and reasonably well-written, and a significant improvement on t=
hat
> >RFC 6333 Appendix, although an understanding of RFC 6333 is necessary to
> >understand this draft, which seems completely reasonable.
> >
> >The B4 and AFTR acronyms are clever - kudos to whomever came up with
> >those.
> >
> >I found five open issues, all of which are minor.
> >
> >Minor Issues:
> >
> >[1] Ironically, the first issue is that something should be said about
> >the relationship of this draft to Appendix A of RFC 6333.  It probably
> >suffices to say that this draft expands on the material in that Appendix=
,
> >as I see no need to specify that this draft updates RFC 6333 solely to
> >change non-normative material in an Appendix.
>=20
> [YL] In "Overview", we will add:
>=20
> "This document expands Appendix A of RFC6333 and discusses various
> DS-Lite deployment considerations for operators."
>=20
> >
> >[2] The MTU increase technique in Section 2.2 is a "may", which is
> >consistent with Section 5.3 of RFC 6333.  OTOH, Section 2.2 of this
> >draft should also discuss the AFTR resource exhaustion concern that
> >described in Section 6.3 of RFC 6333, as that is a potential
> >operational reason for an ISP to increase MTU size (e.g., if customer
> >sourcing of large IPv4 packets is not sufficiently rare).
>=20
> [YL] In 2.2, we will add:
>=20
> "Note that reassembly at Tunnel Exit-Point is resource
> 	intensive. A large number of B4 may terminate on the same AFTR. If many =
B4
> 	fragment the packets, it would increase sufficient load to the AFTR for
> 	reassembly. We recommend the operator should increase the MTU size of th=
e IPv6
> 	network between B4 and AFTR to avoid fragmentation."
>=20
> >
> >[3] Section 2.7 refers to "the AFTR's internal interface".  There may be
> >two internal interfaces, the physical IPv6 interface (outer header) and
> >the tunnel's IPv4 interface (inner header).  The text should be clarifie=
d
> >to indicate which interface is involved - it appears that the AFTR's
> >physical IPv6 interface is intended in this section.
>=20
> [YL] We replace "internal" to "IPv6"
>=20
> >
> >[4] Section 2.7 cites RFC 6333 for use of DHCPv6 with DS-Lite.  RFC 6334
> >should be cited - either in addition to or instead of RFC 6333.
>=20
> [YL] Fixed
>=20
> >
> >[5] Section 2.8 discusses IPv4 accounting at the AFTR, but notes that
> >"the AFTR does not have detailed customer identity information."  Does
> >that create a theft of service possibility?  If so, that possibility
> >should be mentioned as a security consideration.  Also, Section 2.8
> >ought to be expanded with a sentence or two explaining why the AFTR
> >does not have that identity information, and in particular to explain
> >whether and why it is unreasonable in some or all cases to expect
> >that customer identity information be provided to the AFTR as part
> >of provisioning each customer's softwire.
>=20
> [YL] Good catch. Actually I believe AFTR "does" have both IPv4 and IPv6 t=
o
> identify the customer. I suggest we remove
>=20
> "but it will potentially introduce some additional complexity because
>    the AFTR does not have detailed customer identity information."
>=20
> >
> >Nits:
> >
> >Section 2.3 on MTU Considerations could usefully mention MTU discovery
> >techniques, as possibilities for customer IPv4 traffic to adapt to a
> >smaller IPv4 MTU.  If this is done, it would be useful to mention
> >RFC 4821 in addition to the mention of RFC 1191 in RFC 6333.
>=20
> [YL] We would consider RFC 4821. However, the challenge is I don't have
> information how many current OS support RFC 4821. Since DS-lite is a
> transition technology, it would be unreasonable to ask the OS company to
> implement RFC 4821 for DS-lite.
>=20
> >
> >Section 2.4 should define "lawful intercept".  It would be helpful to
> >cite a reference for this concept if something appropriate can be found.
>=20
> [YL] We will find whether there is any reference to this concept. If we
> can't find any, we would add an explanation in the draft.
>=20
> >
> >Section 2.5:
> >- Are one or both types of logging recommended?
>=20
> [YL] We tempted to recommend source-specific log. However, some regulator=
s
> require to use both and the regulations vary country from country, this i=
s
> why we left it open and let the operators to decide.
>=20
> >- Last paragraph on p.4, "timestamped log" is not a good verb phrase.
> >	"maintain a timestamped log of" would be a better replacement.
>=20
> [YL] Fixed
>=20
> >- Last paragraph in section, where is the batch file sent?
>=20
> [YL] We will add:
>=20
> "The files may be compressed before transferring to a repository server
> 	to better utilize bandwidth and storage."
>=20
>=20
> >
> >In Section 2.7, I'm having a hard time understanding which traffic is
> >intended to be subject to the Outgoing Policies and the Incoming Policie=
s.
> >Expanding each of those two bullets to explain what traffic is subject
> >to each class of policies would help.
>=20
> [YL] Does this help?
>=20
> Outgoing Policies apply to packets originating from B4 to IPv4 network.
> Incoming Policies apply to packets originating from IPv4 network to B4.
>=20
>=20
>=20
> >
> >Section 3.2.2.2 uses 192.0.0.2/32 as an example IP address for the
> >B4.  That section should also cross-reference Section 5.7 on RFC 6333
> >on IP address assignment to B4s, as other IP addresses may be used.
>=20
> [YL] Added the cite.
>=20
> >
> >idnits 2.12.13 found a tiny nit - draft-ietf-pcp-base is now at
> >version 28.
>=20
> [YL] Fixed.
>=20
> >
> >Thanks,
> >--David
> >----------------------------------------------------
> >David L. Black, Distinguished Engineer
> >EMC Corporation, 176 South St., Hopkinton, MA  01748
> >+1 (508) 293-7953             FAX: +1 (508) 293-7786
> >david.black@emc.com        Mobile: +1 (978) 394-7754
> >----------------------------------------------------
> >
> >

From roberta.maglione@telecomitalia.it  Thu Oct 18 00:12:50 2012
Return-Path: <roberta.maglione@telecomitalia.it>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 24F4C21F85F7; Thu, 18 Oct 2012 00:12:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.487
X-Spam-Level: 
X-Spam-Status: No, score=-1.487 tagged_above=-999 required=5 tests=[AWL=0.232,  BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fvLH0GT6KgLz; Thu, 18 Oct 2012 00:12:49 -0700 (PDT)
Received: from GRFEDG701BA020.telecomitalia.it (grfedg701ba020.telecomitalia.it [156.54.233.200]) by ietfa.amsl.com (Postfix) with ESMTP id 6879E21F85A7; Thu, 18 Oct 2012 00:12:40 -0700 (PDT)
Received: from grfhub704ba020.griffon.local (10.188.101.117) by GRFEDG701BA020.telecomitalia.it (10.188.45.100) with Microsoft SMTP Server (TLS) id 8.3.279.5; Thu, 18 Oct 2012 09:12:31 +0200
Received: from GRFMBX704BA020.griffon.local ([10.188.101.15]) by grfhub704ba020.griffon.local ([10.188.101.117]) with mapi; Thu, 18 Oct 2012 09:12:29 +0200
From: Maglione Roberta <roberta.maglione@telecomitalia.it>
To: "'Black, David'" <david.black@emc.com>, "Lee, Yiu" <Yiu_Lee@cable.comcast.com>, "carlw@mcsr-labs.org" <carlw@mcsr-labs.org>, "christian.jacquenet@orange.com" <christian.jacquenet@orange.com>, "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>, "gen-art@ietf.org" <gen-art@ietf.org>
Date: Thu, 18 Oct 2012 09:12:29 +0200
Subject: RE: Gen-ART review of draft-ietf-softwire-dslite-deployment-06
Thread-Topic: Gen-ART review of draft-ietf-softwire-dslite-deployment-06
Thread-Index: AQHNrMoAT7CfnR/9yUSA1hDdxxOKmpe+Pf7ggABl0SA=
Message-ID: <282BBE8A501E1F4DA9C775F964BB21FE519702F258@GRFMBX704BA020.griffon.local>
References: <8D3D17ACE214DC429325B2B98F3AE7120DFAEF29@MX15A.corp.emc.com> <E3FAB1F4F41F3A45B287E8D9C53522FD37A7EC79@PACDCEXMB05.cable.comcast.com> <8D3D17ACE214DC429325B2B98F3AE7120DFAF3B9@MX15A.corp.emc.com>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE7120DFAF3B9@MX15A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
x-ti-disclaimer: Disclaimer1
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Thu, 18 Oct 2012 09:03:21 -0700
Cc: "softwires@ietf.org" <softwires@ietf.org>, Ullio Mario <mario.ullio@telecomitalia.it>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Oct 2012 07:12:50 -0000

Hello Yiu and David,
regarding point 5:

> [YL] Good catch. Actually I believe AFTR "does" have both IPv4 and IPv6 t=
o
> identify the customer. I suggest we remove
>
> "but it will potentially introduce some additional complexity because
>    the AFTR does not have detailed customer identity information."

The point related to the accounting is different: what I meant here with ac=
counting is RADIUS based accounting, commonly used in Broadband networks.

Today RADIUS accounting is done at the BNG level, the problem with the intr=
oduction of the AFTR is that the AFTR does not interact with AAA/RADIUS Ser=
ver for the initial authentication/authorization/accounting phase because t=
he authentication/authorization/accounting process happens between BNG and =
RADIUS Server when the session comes up.
The ATFR is not able to perform RADIUS accounting because as it does not in=
teract with the RADIUS Server it does not have " detailed customer identity=
 information" for example it does know the accounting session ID associated=
 to that session, that's why it cannot do detailed accounting for each sing=
le subscriber even if the ATFR can still correlated IPv6 and IPv4 traffic b=
elonging to the same user.

This is an important operational issue, I would suggest to keep this concep=
t. If you think is needed I can add some lines of text in order to clarify =
this point.

Thanks
Regards,
Roberta
-----Original Message-----
From: Black, David [mailto:david.black@emc.com]
Sent: Thursday, October 18, 2012 3:12 AM
To: Lee, Yiu; Maglione Roberta; carlw@mcsr-labs.org; christian.jacquenet@or=
ange.com; mohamed.boucadair@orange.com; gen-art@ietf.org
Cc: softwires@ietf.org; ietf@ietf.org; Ralph Droms; Black, David
Subject: RE: Gen-ART review of draft-ietf-softwire-dslite-deployment-06

Yiu,

Thank you for your responses - most of them look fine, and in
particular anything that I don't comment on here is acceptable to me.

> [YL] In 2.2, we will add:
>
> "Note that reassembly at Tunnel Exit-Point is resource
>       intensive. A large number of B4 may terminate on the same AFTR. If =
many B4
>       fragment the packets, it would increase sufficient load to the AFTR=
 for
>       reassembly. We recommend the operator should increase the MTU size =
of the IPv6
>       network between B4 and AFTR to avoid fragmentation."

I would change "is" to "may be" in the first line.

> >[5] Section 2.8 discusses IPv4 accounting at the AFTR, but notes that
> >"the AFTR does not have detailed customer identity information."  Does
> >that create a theft of service possibility?  If so, that possibility
> >should be mentioned as a security consideration.  Also, Section 2.8
> >ought to be expanded with a sentence or two explaining why the AFTR
> >does not have that identity information, and in particular to explain
> >whether and why it is unreasonable in some or all cases to expect
> >that customer identity information be provided to the AFTR as part
> >of provisioning each customer's softwire.
>
> [YL] Good catch. Actually I believe AFTR "does" have both IPv4 and IPv6 t=
o
> identify the customer. I suggest we remove
>
> "but it will potentially introduce some additional complexity because
>    the AFTR does not have detailed customer identity information."

That's definitely an easy way to address that issue, and it's fine with me.

> >Section 2.3 on MTU Considerations could usefully mention MTU discovery
> >techniques, as possibilities for customer IPv4 traffic to adapt to a
> >smaller IPv4 MTU.  If this is done, it would be useful to mention
> >RFC 4821 in addition to the mention of RFC 1191 in RFC 6333.
>
> [YL] We would consider RFC 4821. However, the challenge is I don't have
> information how many current OS support RFC 4821. Since DS-lite is a
> transition technology, it would be unreasonable to ask the OS company to
> implement RFC 4821 for DS-lite.

That's ok - this was a nit.

> >- Are one or both types of logging recommended?
>
> [YL] We tempted to recommend source-specific log. However, some regulator=
s
> require to use both and the regulations vary country from country, this i=
s
> why we left it open and let the operators to decide.

Please add a version of your explanation to the draft.

> >In Section 2.7, I'm having a hard time understanding which traffic is
> >intended to be subject to the Outgoing Policies and the Incoming Policie=
s.
> >Expanding each of those two bullets to explain what traffic is subject
> >to each class of policies would help.
>
> [YL] Does this help?
>
> Outgoing Policies apply to packets originating from B4 to IPv4 network.
> Incoming Policies apply to packets originating from IPv4 network to B4.

Yes, that's clearer, although the B4 is not the network endpoint for any
of that traffic.  I suggest:

Outgoing Policies apply to packets originating from behind the B4 with
a destination on the IPv4 network.

Incoming Policies apply to packets originating from the IPv4 network to
a destination behind the B4.

Thanks,
--David


> -----Original Message-----
> From: Lee, Yiu [mailto:Yiu_Lee@cable.comcast.com]
> Sent: Wednesday, October 17, 2012 8:46 PM
> To: Black, David; roberta.maglione@telecomitalia.it; carlw@mcsr-labs.org;
> christian.jacquenet@orange.com; mohamed.boucadair@orange.com; gen-art@iet=
f.org
> Cc: softwires@ietf.org; ietf@ietf.org; Ralph Droms
> Subject: Re: Gen-ART review of draft-ietf-softwire-dslite-deployment-06
>
> Hi David,
>
> Thanks very much for review the draft. Comments inline.
>
> Thanks,
> Yiu
>
> On 10/15/12 7:10 PM, "Black, David" <david.black@emc.com> wrote:
>
> >I am the assigned Gen-ART reviewer for this draft. For background on
> >Gen-ART, please see the FAQ at
> ><http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
> >
> >Please resolve these comments along with any other Last Call comments
> >you may receive.
> >
> >Document: draft-ietf-softwire-dslite-deployment-06
> >Reviewer: David L. Black
> >Review Date: October 15, 2012
> >IETF LC End Date: October 16, 2012
> >IESG Telechat Date: October 25, 2012
> >
> >Summary:
> >
> >This draft is on the right track but has open issues, described in the
> >review.
> >
> >This is a generally well-written draft that expands considerably on the =
brief
> >deployment considerations for DS-Lite in Appendix A of RFC 6333.  The dr=
aft
> >is clear and reasonably well-written, and a significant improvement on t=
hat
> >RFC 6333 Appendix, although an understanding of RFC 6333 is necessary to
> >understand this draft, which seems completely reasonable.
> >
> >The B4 and AFTR acronyms are clever - kudos to whomever came up with
> >those.
> >
> >I found five open issues, all of which are minor.
> >
> >Minor Issues:
> >
> >[1] Ironically, the first issue is that something should be said about
> >the relationship of this draft to Appendix A of RFC 6333.  It probably
> >suffices to say that this draft expands on the material in that Appendix=
,
> >as I see no need to specify that this draft updates RFC 6333 solely to
> >change non-normative material in an Appendix.
>
> [YL] In "Overview", we will add:
>
> "This document expands Appendix A of RFC6333 and discusses various
> DS-Lite deployment considerations for operators."
>
> >
> >[2] The MTU increase technique in Section 2.2 is a "may", which is
> >consistent with Section 5.3 of RFC 6333.  OTOH, Section 2.2 of this
> >draft should also discuss the AFTR resource exhaustion concern that
> >described in Section 6.3 of RFC 6333, as that is a potential
> >operational reason for an ISP to increase MTU size (e.g., if customer
> >sourcing of large IPv4 packets is not sufficiently rare).
>
> [YL] In 2.2, we will add:
>
> "Note that reassembly at Tunnel Exit-Point is resource
>       intensive. A large number of B4 may terminate on the same AFTR. If =
many B4
>       fragment the packets, it would increase sufficient load to the AFTR=
 for
>       reassembly. We recommend the operator should increase the MTU size =
of the IPv6
>       network between B4 and AFTR to avoid fragmentation."
>
> >
> >[3] Section 2.7 refers to "the AFTR's internal interface".  There may be
> >two internal interfaces, the physical IPv6 interface (outer header) and
> >the tunnel's IPv4 interface (inner header).  The text should be clarifie=
d
> >to indicate which interface is involved - it appears that the AFTR's
> >physical IPv6 interface is intended in this section.
>
> [YL] We replace "internal" to "IPv6"
>
> >
> >[4] Section 2.7 cites RFC 6333 for use of DHCPv6 with DS-Lite.  RFC 6334
> >should be cited - either in addition to or instead of RFC 6333.
>
> [YL] Fixed
>
> >
> >[5] Section 2.8 discusses IPv4 accounting at the AFTR, but notes that
> >"the AFTR does not have detailed customer identity information."  Does
> >that create a theft of service possibility?  If so, that possibility
> >should be mentioned as a security consideration.  Also, Section 2.8
> >ought to be expanded with a sentence or two explaining why the AFTR
> >does not have that identity information, and in particular to explain
> >whether and why it is unreasonable in some or all cases to expect
> >that customer identity information be provided to the AFTR as part
> >of provisioning each customer's softwire.
>
> [YL] Good catch. Actually I believe AFTR "does" have both IPv4 and IPv6 t=
o
> identify the customer. I suggest we remove
>
> "but it will potentially introduce some additional complexity because
>    the AFTR does not have detailed customer identity information."
>
> >
> >Nits:
> >
> >Section 2.3 on MTU Considerations could usefully mention MTU discovery
> >techniques, as possibilities for customer IPv4 traffic to adapt to a
> >smaller IPv4 MTU.  If this is done, it would be useful to mention
> >RFC 4821 in addition to the mention of RFC 1191 in RFC 6333.
>
> [YL] We would consider RFC 4821. However, the challenge is I don't have
> information how many current OS support RFC 4821. Since DS-lite is a
> transition technology, it would be unreasonable to ask the OS company to
> implement RFC 4821 for DS-lite.
>
> >
> >Section 2.4 should define "lawful intercept".  It would be helpful to
> >cite a reference for this concept if something appropriate can be found.
>
> [YL] We will find whether there is any reference to this concept. If we
> can't find any, we would add an explanation in the draft.
>
> >
> >Section 2.5:
> >- Are one or both types of logging recommended?
>
> [YL] We tempted to recommend source-specific log. However, some regulator=
s
> require to use both and the regulations vary country from country, this i=
s
> why we left it open and let the operators to decide.
>
> >- Last paragraph on p.4, "timestamped log" is not a good verb phrase.
> >     "maintain a timestamped log of" would be a better replacement.
>
> [YL] Fixed
>
> >- Last paragraph in section, where is the batch file sent?
>
> [YL] We will add:
>
> "The files may be compressed before transferring to a repository server
>       to better utilize bandwidth and storage."
>
>
> >
> >In Section 2.7, I'm having a hard time understanding which traffic is
> >intended to be subject to the Outgoing Policies and the Incoming Policie=
s.
> >Expanding each of those two bullets to explain what traffic is subject
> >to each class of policies would help.
>
> [YL] Does this help?
>
> Outgoing Policies apply to packets originating from B4 to IPv4 network.
> Incoming Policies apply to packets originating from IPv4 network to B4.
>
>
>
> >
> >Section 3.2.2.2 uses 192.0.0.2/32 as an example IP address for the
> >B4.  That section should also cross-reference Section 5.7 on RFC 6333
> >on IP address assignment to B4s, as other IP addresses may be used.
>
> [YL] Added the cite.
>
> >
> >idnits 2.12.13 found a tiny nit - draft-ietf-pcp-base is now at
> >version 28.
>
> [YL] Fixed.
>
> >
> >Thanks,
> >--David
> >----------------------------------------------------
> >David L. Black, Distinguished Engineer
> >EMC Corporation, 176 South St., Hopkinton, MA  01748
> >+1 (508) 293-7953             FAX: +1 (508) 293-7786
> >david.black@emc.com        Mobile: +1 (978) 394-7754
> >----------------------------------------------------
> >
> >

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 yiu_lee@cable.comcast.com  Thu Oct 18 05:29:16 2012
Return-Path: <yiu_lee@cable.comcast.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A0E1021F8618; Thu, 18 Oct 2012 05:29:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.109
X-Spam-Level: 
X-Spam-Status: No, score=-102.109 tagged_above=-999 required=5 tests=[AWL=-1.212, BAYES_00=-2.599, HOST_EQ_MODEMCABLE=1.368, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZTTy9bLOhn0U; Thu, 18 Oct 2012 05:29:15 -0700 (PDT)
Received: from cable.comcast.com (pacdcavout01.cable.comcast.com [69.241.43.119]) by ietfa.amsl.com (Postfix) with ESMTP id 2862221F85F4; Thu, 18 Oct 2012 05:29:15 -0700 (PDT)
Received: from ([24.40.56.115]) by pacdcavout01.cable.comcast.com with ESMTP  id 97wm3m1.30860935; Thu, 18 Oct 2012 08:22:04 -0400
Received: from PACDCEXMB05.cable.comcast.com ([169.254.7.147]) by PACDCEXHUB02.cable.comcast.com ([fe80::492e:3fa1:c2ad:e04e%13]) with mapi id 14.02.0318.001; Thu, 18 Oct 2012 08:29:10 -0400
From: "Lee, Yiu" <Yiu_Lee@Cable.Comcast.com>
To: "Black, David" <david.black@emc.com>, "roberta.maglione@telecomitalia.it" <roberta.maglione@telecomitalia.it>, "carlw@mcsr-labs.org" <carlw@mcsr-labs.org>, "christian.jacquenet@orange.com" <christian.jacquenet@orange.com>, "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>, "gen-art@ietf.org" <gen-art@ietf.org>
Subject: Re: Gen-ART review of draft-ietf-softwire-dslite-deployment-06
Thread-Topic: Gen-ART review of draft-ietf-softwire-dslite-deployment-06
Thread-Index: AQHNrSwstZEiPeUY0EatIphU3ATEWA==
Date: Thu, 18 Oct 2012 12:29:09 +0000
Message-ID: <E3FAB1F4F41F3A45B287E8D9C53522FD37A7F8BD@PACDCEXMB05.cable.comcast.com>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE7120DFAF3B9@MX15A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.2.4.120824
x-originating-ip: [24.40.55.70]
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="B_3433393748_19694"
MIME-Version: 1.0
X-Mailman-Approved-At: Thu, 18 Oct 2012 09:03:21 -0700
Cc: "softwires@ietf.org" <softwires@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Oct 2012 12:29:16 -0000

--B_3433393748_19694
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit

Thanks David! I will apply your changes to the next version.

On 10/17/12 9:11 PM, "Black, David" <david.black@emc.com> wrote:

>Yiu,
>
>Thank you for your responses - most of them look fine, and in
>particular anything that I don't comment on here is acceptable to me.
>
>> [YL] In 2.2, we will add:
>> 
>> "Note that reassembly at Tunnel Exit-Point is resource
>> 	intensive. A large number of B4 may terminate on the same AFTR. If
>>many B4
>> 	fragment the packets, it would increase sufficient load to the AFTR for
>> 	reassembly. We recommend the operator should increase the MTU size of
>>the IPv6
>> 	network between B4 and AFTR to avoid fragmentation."
>
>I would change "is" to "may be" in the first line.
>
>> >[5] Section 2.8 discusses IPv4 accounting at the AFTR, but notes that
>> >"the AFTR does not have detailed customer identity information."  Does
>> >that create a theft of service possibility?  If so, that possibility
>> >should be mentioned as a security consideration.  Also, Section 2.8
>> >ought to be expanded with a sentence or two explaining why the AFTR
>> >does not have that identity information, and in particular to explain
>> >whether and why it is unreasonable in some or all cases to expect
>> >that customer identity information be provided to the AFTR as part
>> >of provisioning each customer's softwire.
>> 
>> [YL] Good catch. Actually I believe AFTR "does" have both IPv4 and IPv6
>>to
>> identify the customer. I suggest we remove
>> 
>> "but it will potentially introduce some additional complexity because
>>    the AFTR does not have detailed customer identity information."
>
>That's definitely an easy way to address that issue, and it's fine with
>me.
>
>> >Section 2.3 on MTU Considerations could usefully mention MTU discovery
>> >techniques, as possibilities for customer IPv4 traffic to adapt to a
>> >smaller IPv4 MTU.  If this is done, it would be useful to mention
>> >RFC 4821 in addition to the mention of RFC 1191 in RFC 6333.
>> 
>> [YL] We would consider RFC 4821. However, the challenge is I don't have
>> information how many current OS support RFC 4821. Since DS-lite is a
>> transition technology, it would be unreasonable to ask the OS company to
>> implement RFC 4821 for DS-lite.
>
>That's ok - this was a nit.
>
>> >- Are one or both types of logging recommended?
>> 
>> [YL] We tempted to recommend source-specific log. However, some
>>regulators
>> require to use both and the regulations vary country from country, this
>>is
>> why we left it open and let the operators to decide.
>
>Please add a version of your explanation to the draft.
>
>> >In Section 2.7, I'm having a hard time understanding which traffic is
>> >intended to be subject to the Outgoing Policies and the Incoming
>>Policies.
>> >Expanding each of those two bullets to explain what traffic is subject
>> >to each class of policies would help.
>> 
>> [YL] Does this help?
>> 
>> Outgoing Policies apply to packets originating from B4 to IPv4 network.
>> Incoming Policies apply to packets originating from IPv4 network to B4.
>
>Yes, that's clearer, although the B4 is not the network endpoint for any
>of that traffic.  I suggest:
>
>Outgoing Policies apply to packets originating from behind the B4 with
>a destination on the IPv4 network.
>
>Incoming Policies apply to packets originating from the IPv4 network to
>a destination behind the B4.
>
>Thanks,
>--David
>
>
>> -----Original Message-----
>> From: Lee, Yiu [mailto:Yiu_Lee@cable.comcast.com]
>> Sent: Wednesday, October 17, 2012 8:46 PM
>> To: Black, David; roberta.maglione@telecomitalia.it;
>>carlw@mcsr-labs.org;
>> christian.jacquenet@orange.com; mohamed.boucadair@orange.com;
>>gen-art@ietf.org
>> Cc: softwires@ietf.org; ietf@ietf.org; Ralph Droms
>> Subject: Re: Gen-ART review of draft-ietf-softwire-dslite-deployment-06
>> 
>> Hi David,
>> 
>> Thanks very much for review the draft. Comments inline.
>> 
>> Thanks,
>> Yiu
>> 
>> On 10/15/12 7:10 PM, "Black, David" <david.black@emc.com> wrote:
>> 
>> >I am the assigned Gen-ART reviewer for this draft. For background on
>> >Gen-ART, please see the FAQ at
>> ><http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>> >
>> >Please resolve these comments along with any other Last Call comments
>> >you may receive.
>> >
>> >Document: draft-ietf-softwire-dslite-deployment-06
>> >Reviewer: David L. Black
>> >Review Date: October 15, 2012
>> >IETF LC End Date: October 16, 2012
>> >IESG Telechat Date: October 25, 2012
>> >
>> >Summary:
>> >
>> >This draft is on the right track but has open issues, described in the
>> >review.
>> >
>> >This is a generally well-written draft that expands considerably on
>>the brief
>> >deployment considerations for DS-Lite in Appendix A of RFC 6333.  The
>>draft
>> >is clear and reasonably well-written, and a significant improvement on
>>that
>> >RFC 6333 Appendix, although an understanding of RFC 6333 is necessary
>>to
>> >understand this draft, which seems completely reasonable.
>> >
>> >The B4 and AFTR acronyms are clever - kudos to whomever came up with
>> >those.
>> >
>> >I found five open issues, all of which are minor.
>> >
>> >Minor Issues:
>> >
>> >[1] Ironically, the first issue is that something should be said about
>> >the relationship of this draft to Appendix A of RFC 6333.  It probably
>> >suffices to say that this draft expands on the material in that
>>Appendix,
>> >as I see no need to specify that this draft updates RFC 6333 solely to
>> >change non-normative material in an Appendix.
>> 
>> [YL] In "Overview", we will add:
>> 
>> "This document expands Appendix A of RFC6333 and discusses various
>> DS-Lite deployment considerations for operators."
>> 
>> >
>> >[2] The MTU increase technique in Section 2.2 is a "may", which is
>> >consistent with Section 5.3 of RFC 6333.  OTOH, Section 2.2 of this
>> >draft should also discuss the AFTR resource exhaustion concern that
>> >described in Section 6.3 of RFC 6333, as that is a potential
>> >operational reason for an ISP to increase MTU size (e.g., if customer
>> >sourcing of large IPv4 packets is not sufficiently rare).
>> 
>> [YL] In 2.2, we will add:
>> 
>> "Note that reassembly at Tunnel Exit-Point is resource
>> 	intensive. A large number of B4 may terminate on the same AFTR. If
>>many B4
>> 	fragment the packets, it would increase sufficient load to the AFTR for
>> 	reassembly. We recommend the operator should increase the MTU size of
>>the IPv6
>> 	network between B4 and AFTR to avoid fragmentation."
>> 
>> >
>> >[3] Section 2.7 refers to "the AFTR's internal interface".  There may
>>be
>> >two internal interfaces, the physical IPv6 interface (outer header) and
>> >the tunnel's IPv4 interface (inner header).  The text should be
>>clarified
>> >to indicate which interface is involved - it appears that the AFTR's
>> >physical IPv6 interface is intended in this section.
>> 
>> [YL] We replace "internal" to "IPv6"
>> 
>> >
>> >[4] Section 2.7 cites RFC 6333 for use of DHCPv6 with DS-Lite.  RFC
>>6334
>> >should be cited - either in addition to or instead of RFC 6333.
>> 
>> [YL] Fixed
>> 
>> >
>> >[5] Section 2.8 discusses IPv4 accounting at the AFTR, but notes that
>> >"the AFTR does not have detailed customer identity information."  Does
>> >that create a theft of service possibility?  If so, that possibility
>> >should be mentioned as a security consideration.  Also, Section 2.8
>> >ought to be expanded with a sentence or two explaining why the AFTR
>> >does not have that identity information, and in particular to explain
>> >whether and why it is unreasonable in some or all cases to expect
>> >that customer identity information be provided to the AFTR as part
>> >of provisioning each customer's softwire.
>> 
>> [YL] Good catch. Actually I believe AFTR "does" have both IPv4 and IPv6
>>to
>> identify the customer. I suggest we remove
>> 
>> "but it will potentially introduce some additional complexity because
>>    the AFTR does not have detailed customer identity information."
>> 
>> >
>> >Nits:
>> >
>> >Section 2.3 on MTU Considerations could usefully mention MTU discovery
>> >techniques, as possibilities for customer IPv4 traffic to adapt to a
>> >smaller IPv4 MTU.  If this is done, it would be useful to mention
>> >RFC 4821 in addition to the mention of RFC 1191 in RFC 6333.
>> 
>> [YL] We would consider RFC 4821. However, the challenge is I don't have
>> information how many current OS support RFC 4821. Since DS-lite is a
>> transition technology, it would be unreasonable to ask the OS company to
>> implement RFC 4821 for DS-lite.
>> 
>> >
>> >Section 2.4 should define "lawful intercept".  It would be helpful to
>> >cite a reference for this concept if something appropriate can be
>>found.
>> 
>> [YL] We will find whether there is any reference to this concept. If we
>> can't find any, we would add an explanation in the draft.
>> 
>> >
>> >Section 2.5:
>> >- Are one or both types of logging recommended?
>> 
>> [YL] We tempted to recommend source-specific log. However, some
>>regulators
>> require to use both and the regulations vary country from country, this
>>is
>> why we left it open and let the operators to decide.
>> 
>> >- Last paragraph on p.4, "timestamped log" is not a good verb phrase.
>> >	"maintain a timestamped log of" would be a better replacement.
>> 
>> [YL] Fixed
>> 
>> >- Last paragraph in section, where is the batch file sent?
>> 
>> [YL] We will add:
>> 
>> "The files may be compressed before transferring to a repository server
>> 	to better utilize bandwidth and storage."
>> 
>> 
>> >
>> >In Section 2.7, I'm having a hard time understanding which traffic is
>> >intended to be subject to the Outgoing Policies and the Incoming
>>Policies.
>> >Expanding each of those two bullets to explain what traffic is subject
>> >to each class of policies would help.
>> 
>> [YL] Does this help?
>> 
>> Outgoing Policies apply to packets originating from B4 to IPv4 network.
>> Incoming Policies apply to packets originating from IPv4 network to B4.
>> 
>> 
>> 
>> >
>> >Section 3.2.2.2 uses 192.0.0.2/32 as an example IP address for the
>> >B4.  That section should also cross-reference Section 5.7 on RFC 6333
>> >on IP address assignment to B4s, as other IP addresses may be used.
>> 
>> [YL] Added the cite.
>> 
>> >
>> >idnits 2.12.13 found a tiny nit - draft-ietf-pcp-base is now at
>> >version 28.
>> 
>> [YL] Fixed.
>> 
>> >
>> >Thanks,
>> >--David
>> >----------------------------------------------------
>> >David L. Black, Distinguished Engineer
>> >EMC Corporation, 176 South St., Hopkinton, MA  01748
>> >+1 (508) 293-7953             FAX: +1 (508) 293-7786
>> >david.black@emc.com        Mobile: +1 (978) 394-7754
>> >----------------------------------------------------
>> >
>> >

--B_3433393748_19694
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"

MIIVmQYJKoZIhvcNAQcCoIIVijCCFYYCAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC
EzEwggU0MIIEHKADAgECAhEAzuhISIgzOwSitfbc2LN4WDANBgkqhkiG9w0BAQUFADCBkzEL
MAkGA1UEBhMCR0IxGzAZBgNVBAgTEkdyZWF0ZXIgTWFuY2hlc3RlcjEQMA4GA1UEBxMHU2Fs
Zm9yZDEaMBgGA1UEChMRQ09NT0RPIENBIExpbWl0ZWQxOTA3BgNVBAMTMENPTU9ETyBDbGll
bnQgQXV0aGVudGljYXRpb24gYW5kIFNlY3VyZSBFbWFpbCBDQTAeFw0xMjA4MjgwMDAwMDBa
Fw0xMzA4MjgyMzU5NTlaMCoxKDAmBgkqhkiG9w0BCQEWGXlpdV9sZWVAY2FibGUuY29tY2Fz
dC5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCscOeu5/EoYRdja1jb6L4x
o0TIevelc17NsPuRHfr2z3BGUMbfsJY1p0uXO9+inBQoBXwb07ac3SbOjA/6Ef3NlMPItWdT
RGeFL6e/sMju9RgVyJURFnFgp7tc2tffnPOupnKZeeRehXeEFjun6+GC6teb1kSMu+WMMaCa
D7/XSK+Q+F0Udc2Av0/gUCkGfTDpNnYwutfctEMRnle6EYUqmJMN4C0crEfovmYdMFFgJLKs
Wa5Cdc+naFoIqzW8AcZB6+1XUDTzFbgjqgUbFFZFPzVZqNxLDFNy4tn8VlRSp2jBhgwQHtk1
ZA+spFENaeUuebp4tczj0IHG683FhhWjAgMBAAGjggHpMIIB5TAfBgNVHSMEGDAWgBR6E04A
dFvGeGNkJ8Ev4qBbvHnFezAdBgNVHQ4EFgQUz03csl7CmjwQY+spX9VWeGb5sVQwDgYDVR0P
AQH/BAQDAgWgMAwGA1UdEwEB/wQCMAAwIAYDVR0lBBkwFwYIKwYBBQUHAwQGCysGAQQBsjEB
AwUCMBEGCWCGSAGG+EIBAQQEAwIFIDBGBgNVHSAEPzA9MDsGDCsGAQQBsjEBAgEBATArMCkG
CCsGAQUFBwIBFh1odHRwczovL3NlY3VyZS5jb21vZG8ubmV0L0NQUzBXBgNVHR8EUDBOMEyg
SqBIhkZodHRwOi8vY3JsLmNvbW9kb2NhLmNvbS9DT01PRE9DbGllbnRBdXRoZW50aWNhdGlv
bmFuZFNlY3VyZUVtYWlsQ0EuY3JsMIGIBggrBgEFBQcBAQR8MHowUgYIKwYBBQUHMAKGRmh0
dHA6Ly9jcnQuY29tb2RvY2EuY29tL0NPTU9ET0NsaWVudEF1dGhlbnRpY2F0aW9uYW5kU2Vj
dXJlRW1haWxDQS5jcnQwJAYIKwYBBQUHMAGGGGh0dHA6Ly9vY3NwLmNvbW9kb2NhLmNvbTAk
BgNVHREEHTAbgRl5aXVfbGVlQGNhYmxlLmNvbWNhc3QuY29tMA0GCSqGSIb3DQEBBQUAA4IB
AQBG7LORtWcmzDlw0N/D5AwfsSLe93essAqKFhJ+nt7SmMVBsxGzFnSsZGQHMYQ4UXtiVq9A
NjtPk00F3DC3QGxe4mxdwF9LzeYHpHMpCHTzNyilSimKZolLNBO+MO/U0u79rdF2W+dOAwkB
dzroWBxK+yMhijJn2DCE/1pgxqBz+c9zbAtJYPVpgbeGNvvfIp6CA/JYsupQNqPX49a4MdJ3
L9yXLTiegSE8uPUlCB3sHZclQOXAttuMewpcKDoIC4wZgERKQqRH61PQO100GLKUO+VrTq+f
xNkjOAqA+dih6QO5Djbv3qcMTCcAChJQYK8BS7jved8XgEVa0Ihz7oWKMIIFGjCCBAKgAwIB
AgIQbRnqpxlPajMi5iIyeqpx3jANBgkqhkiG9w0BAQUFADCBrjELMAkGA1UEBhMCVVMxCzAJ
BgNVBAgTAlVUMRcwFQYDVQQHEw5TYWx0IExha2UgQ2l0eTEeMBwGA1UEChMVVGhlIFVTRVJU
UlVTVCBOZXR3b3JrMSEwHwYDVQQLExhodHRwOi8vd3d3LnVzZXJ0cnVzdC5jb20xNjA0BgNV
BAMTLVVUTi1VU0VSRmlyc3QtQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBFbWFpbDAeFw0x
MTA0MjgwMDAwMDBaFw0yMDA1MzAxMDQ4MzhaMIGTMQswCQYDVQQGEwJHQjEbMBkGA1UECBMS
R3JlYXRlciBNYW5jaGVzdGVyMRAwDgYDVQQHEwdTYWxmb3JkMRowGAYDVQQKExFDT01PRE8g
Q0EgTGltaXRlZDE5MDcGA1UEAxMwQ09NT0RPIENsaWVudCBBdXRoZW50aWNhdGlvbiBhbmQg
U2VjdXJlIEVtYWlsIENBMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAkoSEW0tX
mNReL4uk4UDIo1NYX2Zl8TJO958yfVXQeExVt0KU4PkncQfFxmmkuTLE8UAakMwnVmJ/F7Vx
aa7lIBvky2NeYMqiQfZq4aP/uN8fSG1lQ4wqLitjOHffsReswtqCAtbUMmrUZ28gE49cNfrl
VICv2HEKHTcKAlBTbJUdqRAUtJmVWRIx/wmi0kzcUtve4kABW0ho3cVKtODtJB86r3FfB+Os
vxQ7sCVxaD30D9YXWEYVgTxoi4uDD216IVfmNLDbMn7jSuGlUnJkJpFOpZIP/+CxYP0ab2hR
mWONGoulzEKbm30iY9OpoPzOnpDfRBn0XFs1uhbzp5v/wQIDAQABo4IBSzCCAUcwHwYDVR0j
BBgwFoAUiYJnfcSdJnAAS7RQSHzePa4Ebn0wHQYDVR0OBBYEFHoTTgB0W8Z4Y2QnwS/ioFu8
ecV7MA4GA1UdDwEB/wQEAwIBBjASBgNVHRMBAf8ECDAGAQH/AgEAMBEGA1UdIAQKMAgwBgYE
VR0gADBYBgNVHR8EUTBPME2gS6BJhkdodHRwOi8vY3JsLnVzZXJ0cnVzdC5jb20vVVROLVVT
RVJGaXJzdC1DbGllbnRBdXRoZW50aWNhdGlvbmFuZEVtYWlsLmNybDB0BggrBgEFBQcBAQRo
MGYwPQYIKwYBBQUHMAKGMWh0dHA6Ly9jcnQudXNlcnRydXN0LmNvbS9VVE5BZGRUcnVzdENs
aWVudF9DQS5jcnQwJQYIKwYBBQUHMAGGGWh0dHA6Ly9vY3NwLnVzZXJ0cnVzdC5jb20wDQYJ
KoZIhvcNAQEFBQADggEBAIXWvnhXVW0zf0RS/kLVBqgBA4CK+w2y/Uq/9q9BSfUbWsXSrRtz
bj7pJnzmTJjBMCjfy/tCPKElPgp11tA9OYZm0aGbtU2bb68obB2v5ep0WqjascDxdXovnrqT
ecr+4pEeVnSy+I3T4ENyG+2P/WA5IEf7i686ZUg8mD2lJb+972DgSeUWyOs/Q4Pw4O4NwdPN
M1+b0L1garM7/vrUyTo8H+2b/5tJM75CKTmD7jNpLoKdRU2oadqAGx490hpdfEeZpZsIbRKZ
htZdVwcbpzC+S0lEuJB+ytF5OOu0M/qgOl0mWJ5hVRi0IdWZ1eBDQEIwvuql55TSsP7zdfl/
bucwggSdMIIDhaADAgECAhA0PekrrCc0/4/LNJT7zHBUMA0GCSqGSIb3DQEBBQUAMG8xCzAJ
BgNVBAYTAlNFMRQwEgYDVQQKEwtBZGRUcnVzdCBBQjEmMCQGA1UECxMdQWRkVHJ1c3QgRXh0
ZXJuYWwgVFRQIE5ldHdvcmsxIjAgBgNVBAMTGUFkZFRydXN0IEV4dGVybmFsIENBIFJvb3Qw
HhcNMDUwNjA3MDgwOTEwWhcNMjAwNTMwMTA0ODM4WjCBrjELMAkGA1UEBhMCVVMxCzAJBgNV
BAgTAlVUMRcwFQYDVQQHEw5TYWx0IExha2UgQ2l0eTEeMBwGA1UEChMVVGhlIFVTRVJUUlVT
VCBOZXR3b3JrMSEwHwYDVQQLExhodHRwOi8vd3d3LnVzZXJ0cnVzdC5jb20xNjA0BgNVBAMT
LVVUTi1VU0VSRmlyc3QtQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBFbWFpbDCCASIwDQYJ
KoZIhvcNAQEBBQADggEPADCCAQoCggEBALI5haTyfatBO2JGN67NwWB1vDll+UoaR6K5zEjM
apjVTTUZuaRC5c5J4oovHnzSMQfHTrSDZJ0uKdWiZMSFvYVRNXmkTmiQexx6pJKoF/KYFfKT
zMmkMpW7DE8wvZigC4vlbhuiRvp4vKJvq1lepS/Pytptqi/rrKGzaqq3Lmc1i3nhHmmI4uZG
zaCl6r4LznY6eg6b6vzaJ1s9cx8i5khhxkzzabGoLhu21DEgLLyCio6kDqXXiUP8FlqvHXHX
EVnauocNr/rz4cLwpMVnjNbWVDreCqS6A3ezZcj9HtN0YqoYymiTHqGFfvVHZcv4TVcodNI0
/zC27vZiMBSMLOsCAwEAAaOB9DCB8TAfBgNVHSMEGDAWgBStvZh6NLQm9/rEJlTvA73gJMtU
GjAdBgNVHQ4EFgQUiYJnfcSdJnAAS7RQSHzePa4Ebn0wDgYDVR0PAQH/BAQDAgEGMA8GA1Ud
EwEB/wQFMAMBAf8wEQYDVR0gBAowCDAGBgRVHSAAMEQGA1UdHwQ9MDswOaA3oDWGM2h0dHA6
Ly9jcmwudXNlcnRydXN0LmNvbS9BZGRUcnVzdEV4dGVybmFsQ0FSb290LmNybDA1BggrBgEF
BQcBAQQpMCcwJQYIKwYBBQUHMAGGGWh0dHA6Ly9vY3NwLnVzZXJ0cnVzdC5jb20wDQYJKoZI
hvcNAQEFBQADggEBAAG8nONjKLDzMQHC33vdYqABnSMxD5ySc1NR6h9M+tafxMovZ354Mw90
FrmRh5H1iib6ZHAA2B75CwRiUIeTgdTa9SPbNLuFVrRwNG54gzcehRzFERWSX4cXvaxq/fHC
0cyJX7F88D5R8jXzfOxgmGs6K+Dv37N9huu1G/Vb7KJ8mBPXAFC50S1z3gN4dOEFhTFey5q5
nZTGuZQ3dXLcRPtn6PD6JR5Sp9ol6UfgoMc8oE6xCjb7d0if75eK+7T+45QUqIO8XC0/0mBx
YO7CcYIM6Yg249ogtKOgbKqWS7iAjnXKSQf2OxS639wF2Z/b4LLmTaB4JufnLW5/X8YeiBUw
ggQ2MIIDHqADAgECAgEBMA0GCSqGSIb3DQEBBQUAMG8xCzAJBgNVBAYTAlNFMRQwEgYDVQQK
EwtBZGRUcnVzdCBBQjEmMCQGA1UECxMdQWRkVHJ1c3QgRXh0ZXJuYWwgVFRQIE5ldHdvcmsx
IjAgBgNVBAMTGUFkZFRydXN0IEV4dGVybmFsIENBIFJvb3QwHhcNMDAwNTMwMTA0ODM4WhcN
MjAwNTMwMTA0ODM4WjBvMQswCQYDVQQGEwJTRTEUMBIGA1UEChMLQWRkVHJ1c3QgQUIxJjAk
BgNVBAsTHUFkZFRydXN0IEV4dGVybmFsIFRUUCBOZXR3b3JrMSIwIAYDVQQDExlBZGRUcnVz
dCBFeHRlcm5hbCBDQSBSb290MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAt/ca
M+byAAQtOeBOW+0fvGwPzbX6I7bO3psRM5ekKUx9k5+9SryT7QMa44/P5W1QWtaXKZRagLBJ
etsulf24yr83OC0ePpFBrXBWx/BPP+gynnTKyJBU6cZfD3idmkA8Dqxhql4Uj56HoWpQ3Nea
Tq8Fs6ZxlJxxs1BgCscTnTgHhgKo6ahpJhiQq0ywTyOrOk+E2N/On+Fpb7vXQtdrROTHre5t
QV9yWnEIN7N5ZaRZoJQ39wAvDcKSctrQOHLbFKhFxF0qfbe01sTurM0TRLfJK91DACX6Yblp
algjEbenM49WdVn1zSnXRrcKK2W200JvFbK4e/vv6V1T1TRaJwIDAQABo4HcMIHZMB0GA1Ud
DgQWBBStvZh6NLQm9/rEJlTvA73gJMtUGjALBgNVHQ8EBAMCAQYwDwYDVR0TAQH/BAUwAwEB
/zCBmQYDVR0jBIGRMIGOgBStvZh6NLQm9/rEJlTvA73gJMtUGqFzpHEwbzELMAkGA1UEBhMC
U0UxFDASBgNVBAoTC0FkZFRydXN0IEFCMSYwJAYDVQQLEx1BZGRUcnVzdCBFeHRlcm5hbCBU
VFAgTmV0d29yazEiMCAGA1UEAxMZQWRkVHJ1c3QgRXh0ZXJuYWwgQ0EgUm9vdIIBATANBgkq
hkiG9w0BAQUFAAOCAQEAsJvghSXC1iPiD5YGkp1BmJzZhHmB2R5bFAcjNmWPsNh3u6xBbEdg
g1Gw+TI95/z2JhPHgBalv1r8h894eYkhmuJMBwqGNbzy3lHE0pa33H5O7nD9HDnrDAJRFC2O
vRbgwd9Gdeckrez0QrSFk3AQZ7qdBjVKGNMresxRQqF6Y9Hmu6HFK8I2vhMN5r1jfnl7pwkN
QKtq3Y+Kw/b2jBpCBVHURfWfp2IhaBUgQzyZ53y9JNipkRdziD9WGzE4GLRxD5rNyA6eji4b
4YyYg8sfMfFETMYEc0l2YA/H+L0XgGsu6cxMDlqaeQ8gCi7VnmMmHlWSlNiCF1p70LzHj06G
BDGCAjAwggIsAgEBMIGpMIGTMQswCQYDVQQGEwJHQjEbMBkGA1UECBMSR3JlYXRlciBNYW5j
aGVzdGVyMRAwDgYDVQQHEwdTYWxmb3JkMRowGAYDVQQKExFDT01PRE8gQ0EgTGltaXRlZDE5
MDcGA1UEAxMwQ09NT0RPIENsaWVudCBBdXRoZW50aWNhdGlvbiBhbmQgU2VjdXJlIEVtYWls
IENBAhEAzuhISIgzOwSitfbc2LN4WDAJBgUrDgMCGgUAoF0wIwYJKoZIhvcNAQkEMRYEFGkn
nJBZtnpog7FZj5U6Qx+BLJFVMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcN
AQkFMQ8XDTEyMTAxODEyMjkwN1owDQYJKoZIhvcNAQEBBQAEggEAhqU5Lp5+wPE+aK5lPOnX
UW8gQG+BDt7ck9adN8TNr6ZBxLONPEDZDtYes5TuMyLnXaPqPH/fx0KuhsQZz/iNUiuRiAv2
ijEn9Q74BRAftfmFwX5L71HJf3l/g04+GoTB8u5UM1IUVwiXhqExsgGsF7CNPN9g6aA9BBF9
he0ud9aEWFEEdlhhImS715fUmi2Tod5rzTT9+Es3kW1lHCliEsfzsmGbYdq18GFje7lDLlGB
z67zY/j3DzXInR5dnXWr2fdjkgOrOsj/zhckt6k9spUlI1e4SSO4UoaP5NQTRXYMz/A7R0RZ
PdFLnT1aKHCcmFQ7uL6/gPfjUyFNZTFrbw==

--B_3433393748_19694--

From ian@hixie.ch  Wed Oct 17 16:57:40 2012
Return-Path: <ian@hixie.ch>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 16DD221F8686 for <ietf@ietfa.amsl.com>; Wed, 17 Oct 2012 16:57:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CU7mVxgm79ls for <ietf@ietfa.amsl.com>; Wed, 17 Oct 2012 16:57:39 -0700 (PDT)
Received: from homiemail-a79.g.dreamhost.com (caibbdcaaaaf.dreamhost.com [208.113.200.5]) by ietfa.amsl.com (Postfix) with ESMTP id 6A68A21F8691 for <ietf@ietf.org>; Wed, 17 Oct 2012 16:57:39 -0700 (PDT)
Received: from homiemail-a79.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a79.g.dreamhost.com (Postfix) with ESMTP id 814E37D4070; Wed, 17 Oct 2012 16:57:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=hixie.ch; h=date:from:to :cc:subject:in-reply-to:message-id:references:mime-version: content-type; s=hixie.ch; bh=Gwt0D7KC8IQU85D05avTE0ABZnI=; b=akY RG8RGTLZk+B6dHIvdM6+BSjw2qcwN6PPcsYz8R6invZxiyANmQVNANJzvR/lSTRH SDjBipzNFBRUDhMfqgq1W5QB7aQATmUlRWqIbsKbQSRpoIWgbtDHfa4DJZv7m8Iq tByjFIX5yAL48kiwUznmYTL+VIcw8ELFWEucyznU=
Received: from ps20323.dreamhostps.com (ps20323.dreamhost.com [69.163.222.251]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: internal@index.hixie.ch) by homiemail-a79.g.dreamhost.com (Postfix) with ESMTPSA id 6DF037D406F;  Wed, 17 Oct 2012 16:57:35 -0700 (PDT)
Date: Wed, 17 Oct 2012 23:57:38 +0000 (UTC)
From: Ian Hickson <ian@hixie.ch>
To: Peter Saint-Andre <stpeter@stpeter.im>
Subject: Re: [whatwg] New URL Standard from Anne van Kesteren on 2012-09-24 (public-whatwg-archive@w3.org from September 2012)
In-Reply-To: <5060A964.5060001@stpeter.im>
Message-ID: <Pine.LNX.4.64.1210172354500.2478@ps20323.dreamhostps.com>
References: <50604C1A.7090901@gmx.de> <5060A964.5060001@stpeter.im>
Content-Language: en-GB-hixie
Content-Style-Type: text/css
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Mailman-Approved-At: Thu, 18 Oct 2012 09:04:06 -0700
Cc: Julian Reschke <julian.reschke@gmx.de>, URI <uri@w3.org>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Oct 2012 23:57:40 -0000

On Mon, 24 Sep 2012, Peter Saint-Andre wrote:
>
> It's also not clear to me what the WHATWG HTML Living Standard [1] 
> really means by "willful violation"
> http://www.whatwg.org/specs/web-apps/current-work/multipage/introduction.html#willful-violation

Can you elaborate on how the definition you cite there in the spec is 
unclear? I'm not sure how to make it clearer.


> e.g., is it just an allowance for APIs and browser software to not be 
> completely strict about processing some input for the sake of backward 
> compatibility with existing (messy) web content, or is it an active 
> attempt at redefining core protocols?

The spec seems pretty clear that it's the latter ("conflicting needs have 
led to this specification violating the requirements of these other 
specifications").


> However, it is interesting that the willful violations are not limited 
> to RFC 3986: the spec also mentions willful violations of RFC 2046, RFC 
> 2616, RFC 2781, RFC 5322, EcmaScript, XPath, XSLT, and Unicode. Quite a 
> list...

Yeah. Turns out we (the Web standards community) haven't been doing such a 
great job of making our specificatiosn match reality. :-(

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'

From nrm@arcanedomain.com  Wed Oct 17 18:24:19 2012
Return-Path: <nrm@arcanedomain.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9245921F8685 for <ietf@ietfa.amsl.com>; Wed, 17 Oct 2012 18:24:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CSZkysUMf4do for <ietf@ietfa.amsl.com>; Wed, 17 Oct 2012 18:24:19 -0700 (PDT)
Received: from homiemail-a5.g.dreamhost.com (caiajhbdcagg.dreamhost.com [208.97.132.66]) by ietfa.amsl.com (Postfix) with ESMTP id 15C5721F85AC for <ietf@ietf.org>; Wed, 17 Oct 2012 18:24:18 -0700 (PDT)
Received: from homiemail-a5.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a5.g.dreamhost.com (Postfix) with ESMTP id 82835704063; Wed, 17 Oct 2012 18:24:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=arcanedomain.com; h= message-id:date:from:mime-version:to:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; s= arcanedomain.com; bh=C3vxvIW4FJQU7y+j2ZgYJAZ2FuA=; b=BJZmRwcQJRT u3v6VRVaCXKRbHHD6ZVVYiYaYnq+MQfn22jFN2+hHyo43E8PrCloQ9LHHcO0Uaga taBLmmWMxn0otOwj82rwutwmHqtUPCzXltrowe2hIZFr4/eu4qgxi/WzLIBXxUvE 0dFS6YlbOMsXYppymhgkIQXQHEQ1d7Bo=
Received: from [192.168.1.70] (unknown [146.115.66.224]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: webmaster@arcanedomain.com) by homiemail-a5.g.dreamhost.com (Postfix) with ESMTPSA id DE31B70406E;  Wed, 17 Oct 2012 18:24:17 -0700 (PDT)
Message-ID: <507F5A7E.6040206@arcanedomain.com>
Date: Wed, 17 Oct 2012 21:25:18 -0400
From: Noah Mendelsohn <nrm@arcanedomain.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:16.0) Gecko/20121010 Thunderbird/16.0.1
MIME-Version: 1.0
To: Ian Hickson <ian@hixie.ch>
Subject: Re: [whatwg] New URL Standard from Anne van Kesteren on 2012-09-24 (public-whatwg-archive@w3.org from September 2012)
References: <50604C1A.7090901@gmx.de> <5060A964.5060001@stpeter.im> <Pine.LNX.4.64.1210172354500.2478@ps20323.dreamhostps.com>
In-Reply-To: <Pine.LNX.4.64.1210172354500.2478@ps20323.dreamhostps.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Thu, 18 Oct 2012 09:04:06 -0700
Cc: Julian Reschke <julian.reschke@gmx.de>, URI <uri@w3.org>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Oct 2012 01:24:19 -0000

On 10/17/2012 7:57 PM, Ian Hickson wrote:
> Yeah. Turns out we (the Web standards community) haven't been doing such a
> great job of making our specificatiosn match reality.:-(

Um, true... but it's also the case that the implementation community hasn't 
over the years been doing as much as might be best to make reality match 
the specifications. The new specs we're writing now would like have been a 
lot thinner and cleaner if they had.

Noah

From ian@hixie.ch  Wed Oct 17 18:29:14 2012
Return-Path: <ian@hixie.ch>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9D6BF1F0417 for <ietf@ietfa.amsl.com>; Wed, 17 Oct 2012 18:29:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id z6Nz2XE5gTLx for <ietf@ietfa.amsl.com>; Wed, 17 Oct 2012 18:29:14 -0700 (PDT)
Received: from homiemail-a51.g.dreamhost.com (caibbdcaaaaf.dreamhost.com [208.113.200.5]) by ietfa.amsl.com (Postfix) with ESMTP id 112801F041C for <ietf@ietf.org>; Wed, 17 Oct 2012 18:29:14 -0700 (PDT)
Received: from homiemail-a51.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a51.g.dreamhost.com (Postfix) with ESMTP id 0EC1E2E805C; Wed, 17 Oct 2012 18:29:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=hixie.ch; h=date:from:to :cc:subject:in-reply-to:message-id:references:mime-version: content-type; s=hixie.ch; bh=wtREkLkoU5A2SidSNdXFOOtiWAQ=; b=zNY 8/OUNsfo6IyMq/PZrO3FMHB2ySGIXlU7mvjY+hEIXcByMHvhJJstROor5BnNrHVL oM1GRchggFBht6JSHVi5EkZsqdyoy2nLHx2JDsXdCAqbuqn++lBBGcR4hBHwWgJ8 /sPeExNTrNo+7zhTLaPNr5b8h++K+423PH2Jyd2A=
Received: from ps20323.dreamhostps.com (ps20323.dreamhost.com [69.163.222.251]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: internal@index.hixie.ch) by homiemail-a51.g.dreamhost.com (Postfix) with ESMTPSA id 067BC2E8055;  Wed, 17 Oct 2012 18:29:24 -0700 (PDT)
Date: Thu, 18 Oct 2012 01:29:13 +0000 (UTC)
From: Ian Hickson <ian@hixie.ch>
To: Noah Mendelsohn <nrm@arcanedomain.com>
Subject: Re: [whatwg] New URL Standard from Anne van Kesteren on 2012-09-24 (public-whatwg-archive@w3.org from September 2012)
In-Reply-To: <507F5A7E.6040206@arcanedomain.com>
Message-ID: <Pine.LNX.4.64.1210180128020.2471@ps20323.dreamhostps.com>
References: <50604C1A.7090901@gmx.de> <5060A964.5060001@stpeter.im> <Pine.LNX.4.64.1210172354500.2478@ps20323.dreamhostps.com> <507F5A7E.6040206@arcanedomain.com>
Content-Language: en-GB-hixie
Content-Style-Type: text/css
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Mailman-Approved-At: Thu, 18 Oct 2012 09:04:06 -0700
Cc: Julian Reschke <julian.reschke@gmx.de>, URI <uri@w3.org>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Oct 2012 01:29:14 -0000

On Wed, 17 Oct 2012, Noah Mendelsohn wrote:
> On 10/17/2012 7:57 PM, Ian Hickson wrote:
> > Yeah. Turns out we (the Web standards community) haven't been doing 
> > such a great job of making our specificatiosn match reality.:-(
> 
> Um, true... but it's also the case that the implementation community 
> hasn't over the years been doing as much as might be best to make 
> reality match the specifications. The new specs we're writing now would 
> like have been a lot thinner and cleaner if they had.

At least on the browser front, having been on those front lines for much 
of my career, I don't really know what more we could have done.

But in any case, that's somewhat irrelevant now, since it's too late to 
ge back and change it.

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'

From McQuilWP@pobox.com  Thu Oct 18 17:51:37 2012
Return-Path: <McQuilWP@pobox.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2775221F8493; Thu, 18 Oct 2012 17:51:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2vBSNJSipSPN; Thu, 18 Oct 2012 17:51:33 -0700 (PDT)
Received: from smtp.pobox.com (b-pb-sasl-quonix.pobox.com [208.72.237.35]) by ietfa.amsl.com (Postfix) with ESMTP id 5063F21F849C; Thu, 18 Oct 2012 17:51:33 -0700 (PDT)
Received: from smtp.pobox.com (unknown [127.0.0.1]) by b-sasl-quonix.pobox.com (Postfix) with ESMTP id AD53881AB; Thu, 18 Oct 2012 20:51:31 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=pobox.com; h=date:from :message-id:to:cc:subject:in-reply-to:references:mime-version :content-type:content-transfer-encoding; s=sasl; bh=MgNqjWxq4ShP le4ZKFbqpRG15bA=; b=KbVMz4pVhqGhkUoowccZ+7wJ1l1D7URgT2KxO6Ur18OL 5nBTcVUPCo2NXZuTzqLWt7tgXgjG8yIezRQWKXyXTPjF8rmxpSt5hEzzWMrxIS7C eJ5iFq7NZHTE1E+umuWIwi6Bm/Ps14HKem0ny+fEkzkjnXu0LejNAEVISt2S1Oc=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=pobox.com; h=date:from :message-id:to:cc:subject:in-reply-to:references:mime-version :content-type:content-transfer-encoding; q=dns; s=sasl; b=nSrnTq X9+4+U6PY6JzXnt0diRhsBuPuFVO2Nk5HJ+oJAmZCkDjJOiY2qV/A17A9ZqJ6c+L sRwogS0Ib0B1o5XAHJURz3mVNT+e10MWRgxN9w8eUXO7MsRIcvw3hXVinX2bMM4o RDLD7WGsOUMPN3xn6G7+9TVC/8JVPHQJeJN9U=
Received: from b-pb-sasl-quonix.pobox.com (unknown [127.0.0.1]) by b-sasl-quonix.pobox.com (Postfix) with ESMTP id 9A17D81AA; Thu, 18 Oct 2012 20:51:31 -0400 (EDT)
Received: from BQ07NB (unknown [68.107.15.47]) by b-sasl-quonix.pobox.com (Postfix) with ESMTPA id E691E81A9; Thu, 18 Oct 2012 20:51:29 -0400 (EDT)
Date: Thu, 18 Oct 2012 17:51:28 -0700
From: Bill McQuillan <McQuilWP@pobox.com>
X-Priority: 3 (Normal)
Message-ID: <1475027170.20121018175128@pobox.com>
To: IETF Discussion <ietf@ietf.org>
Subject: Re: Gen-ART LC review of draft-leiba-5322upd-from-group-06
In-Reply-To: <E73A2748BBE3FA6E1EE3A2C3@JcK-HP8200.jck.com>
References: <010301cdac4d$cfa70060$6ef50120$@gmail.com> <01OLIW8VNVCU00008S@mauve.mrochek.com> <507EF95D.5090007@dcrocker.net> <01OLIXV2SU4O00008S@mauve.mrochek.com> <5B0F81787945877A5CC3794B@JcK-HP8200.jck.com> <01OLJ38YAL9600008S@mauve.mrochek.com> <507F3CEA.2010306@dcrocker.net> <01OLJ9JAK8SQ00008S@mauve.mrochek.com> <507F5249.2090507@dcrocker.net> <CALaySJKD+JbkOuZsC7wQtNNLHBP-4a_=DNfQ0XkQWoCq78-JGg@mail.gmail.com> <E73A2748BBE3FA6E1EE3A2C3@JcK-HP8200.jck.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Pobox-Relay-ID: 1F54F242-1987-11E2-90CF-9A8C2E706CDE-02871704!b-pb-sasl-quonix.pobox.com
Cc: Ned Freed <ned.freed@mrochek.com>, draft-leiba-5322upd-from-group.all@tools.ietf.org, ned+ietf@mauve.mrochek.com, gen-art@ietf.org, johnl@taugh.com, dcrocker@bbiw.net, John C Klensin <john-ietf@jck.com>, Barry Leiba <barryleiba@computer.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Oct 2012 00:51:37 -0000

On Thu, 2012-10-18, John C Klensin wrote:
<snip>

> As I said earlier, I can live with almost anything if it is
> correct and allows us to move forward.  I am, however, getting
> more concerned about the consequences to the virtual 5322bis and
> its future instantiation if we go down these paths.  I would
> really not like to be the relevant AD (or Pete-bis) trying to
> defend leaving the explanation and reference out of 5322bis
> given that they were important enough to include in this
> document and, if the explanation and reference go into 5322bis,
> why a large series of other references and explanations should
> not be included.  I'd be a tad happier if this explanatory stuff
> when into an appendix rather than the text.  

<serious value="false">
How about we put the explanation right next to the justification in 
5322 why <group> was not allowed in From: in the first place?
</serious>

I have wondered about that limitation for at least 15 years. I
have come up with possible explanations but without a shred of
evidence from the RFCs.

<snip>
-- 
Bill McQuillan <McQuilWP@pobox.com>


From dcrocker@bbiw.net  Thu Oct 18 18:25:38 2012
Return-Path: <dcrocker@bbiw.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AD79921F8528; Thu, 18 Oct 2012 18:25:38 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a78eHKqnYBvq; Thu, 18 Oct 2012 18:25:38 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 0C99821F84FF; Thu, 18 Oct 2012 18:25:38 -0700 (PDT)
Received: from [192.168.1.6] (adsl-67-127-59-48.dsl.pltn13.pacbell.net [67.127.59.48]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q9J1Pap2031753 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 18 Oct 2012 18:25:37 -0700
Message-ID: <5080AC0E.8080001@bbiw.net>
Date: Thu, 18 Oct 2012 18:25:34 -0700
From: Dave Crocker <dcrocker@bbiw.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121010 Thunderbird/16.0.1
MIME-Version: 1.0
To: Bill McQuillan <McQuilWP@pobox.com>
Subject: Re: Gen-ART LC review of draft-leiba-5322upd-from-group-06
References: <010301cdac4d$cfa70060$6ef50120$@gmail.com> <01OLIW8VNVCU00008S@mauve.mrochek.com> <507EF95D.5090007@dcrocker.net> <01OLIXV2SU4O00008S@mauve.mrochek.com> <5B0F81787945877A5CC3794B@JcK-HP8200.jck.com> <01OLJ38YAL9600008S@mauve.mrochek.com> <507F3CEA.2010306@dcrocker.net> <01OLJ9JAK8SQ00008S@mauve.mrochek.com> <507F5249.2090507@dcrocker.net> <CALaySJKD+JbkOuZsC7wQtNNLHBP-4a_=DNfQ0XkQWoCq78-JGg@mail.gmail.com> <E73A2748BBE3FA6E1EE3A2C3@JcK-HP8200.jck.com> <1475027170.20121018175128@pobox.com>
In-Reply-To: <1475027170.20121018175128@pobox.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, 18 Oct 2012 18:25:37 -0700 (PDT)
Cc: ned+ietf@mauve.mrochek.com, gen-art@ietf.org, johnl@taugh.com, IETF Discussion <ietf@ietf.org>, draft-leiba-5322upd-from-group.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, 19 Oct 2012 01:25:38 -0000

> I have wondered about that limitation for at least 15 years. I
> have come up with possible explanations but without a shred of
> evidence from the RFCs.


FWIW,

The construct of "group" is pretty much an assertion of an aggregate 
identity.  That is, an identity beyond that of the listed addressees, 
deriving from their, ummmm... grouping.

The purpose of From: and Sender: is to assign bits of essential 
responsibility.

Unlike the current trend towards declaring personhood for corporations, 
the design motivation behind using the group construct was to restrict 
assignment of responsibilities to individuals, rather than aggregations 
of them.

All very abstract, I admit.  From the vantage point of some decades, 
even quaint.

d/
-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From narten@us.ibm.com  Thu Oct 18 21:53:17 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 2852021F84F8 for <ietf@ietfa.amsl.com>; Thu, 18 Oct 2012 21:53:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.407
X-Spam-Level: 
X-Spam-Status: No, score=-110.407 tagged_above=-999 required=5 tests=[AWL=0.192, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2IlTb+MRDev1 for <ietf@ietfa.amsl.com>; Thu, 18 Oct 2012 21:53:16 -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 2725B21F84F3 for <ietf@ietf.org>; Thu, 18 Oct 2012 21:53:15 -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, 18 Oct 2012 22:53:14 -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, 18 Oct 2012 22:53:05 -0600
Received: from d03relay04.boulder.ibm.com (d03relay04.boulder.ibm.com [9.17.195.106]) by d03dlp01.boulder.ibm.com (Postfix) with ESMTP id 211F2C40001 for <ietf@ietf.org>; Thu, 18 Oct 2012 22:53:05 -0600 (MDT)
Received: from d03av01.boulder.ibm.com (d03av01.boulder.ibm.com [9.17.195.167]) by d03relay04.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id q9J4r55Z229216 for <ietf@ietf.org>; Thu, 18 Oct 2012 22:53:05 -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 q9J4r4vL005789 for <ietf@ietf.org>; Thu, 18 Oct 2012 22:53:04 -0600
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.44.115.148]) by d03av01.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id q9J4r4aX005770 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Thu, 18 Oct 2012 22:53:04 -0600
Received: from rotala.raleigh.ibm.com (localhost.localdomain [127.0.0.1]) by rotala.raleigh.ibm.com (8.14.5/8.12.5) with ESMTP id q9J4r3i6014330 for <ietf@ietf.org>; Fri, 19 Oct 2012 00:53:03 -0400
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.5/8.14.5/Submit) id q9J4r36T014291 for ietf@ietf.org; Fri, 19 Oct 2012 00:53:03 -0400
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201210190453.q9J4r36T014291@rotala.raleigh.ibm.com>
Date: Fri, 19 Oct 2012 00:53:03 -0400
To: ietf@ietf.org
Subject: Weekly posting summary for ietf@ietf.org
User-Agent: Heirloom mailx 12.5 7/5/10
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 12101904-5406-0000-0000-0000013EAE5D
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Oct 2012 04:53:17 -0000

Total of 72 messages in the last 7 days.
 
script run at: Fri Oct 19 00:53:02 EDT 2012
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
  9.72% |    7 |  7.32% |    40543 | dhc@dcrocker.net
  8.33% |    6 |  7.39% |    40922 | john-ietf@jck.com
  6.94% |    5 |  5.52% |    30553 | ned+ietf@mauve.mrochek.com
  2.78% |    2 |  7.82% |    43276 | yiu_lee@cable.comcast.com
  4.17% |    3 |  6.16% |    34126 | david.black@emc.com
  2.78% |    2 |  6.69% |    37019 | ron.even.tlv@gmail.com
  4.17% |    3 |  3.87% |    21402 | chair@ietf.org
  4.17% |    3 |  2.95% |    16322 | randy@psg.com
  2.78% |    2 |  3.42% |    18916 | jari.arkko@piuha.net
  2.78% |    2 |  3.15% |    17451 | presnick@qti.qualcomm.com
  2.78% |    2 |  2.43% |    13434 | barryleiba@computer.org
  2.78% |    2 |  2.36% |    13046 | ian@hixie.ch
  2.78% |    2 |  2.28% |    12597 | dcrocker@bbiw.net
  2.78% |    2 |  2.21% |    12228 | sm@resistor.net
  2.78% |    2 |  2.11% |    11706 | warren@kumari.net
  2.78% |    2 |  2.11% |    11693 | joelja@bogus.com
  2.78% |    2 |  2.10% |    11622 | johnl@taugh.com
  2.78% |    2 |  2.08% |    11501 | adrian@olddog.co.uk
  2.78% |    2 |  2.02% |    11180 | hartmans-ietf@mit.edu
  1.39% |    1 |  3.33% |    18428 | roberta.maglione@telecomitalia.it
  1.39% |    1 |  1.99% |    11017 | tglassey@earthlink.net
  1.39% |    1 |  1.46% |     8088 | narten@us.ibm.com
  1.39% |    1 |  1.45% |     8017 | luby@qti.qualcomm.com
  1.39% |    1 |  1.41% |     7793 | contreraslegal@att.net
  1.39% |    1 |  1.38% |     7645 | gtw@gtwassociates.com
  1.39% |    1 |  1.36% |     7531 | abdussalambaryun@gmail.com
  1.39% |    1 |  1.30% |     7222 | mcquilwp@pobox.com
  1.39% |    1 |  1.24% |     6870 | fred@cisco.com
  1.39% |    1 |  1.23% |     6799 | craemer@isoc.org
  1.39% |    1 |  1.20% |     6662 | ietf@meetecho.com
  1.39% |    1 |  1.20% |     6643 | stephen.farrell@cs.tcd.ie
  1.39% |    1 |  1.18% |     6535 | brian.e.carpenter@gmail.com
  1.39% |    1 |  1.14% |     6306 | melinda.shore@gmail.com
  1.39% |    1 |  1.08% |     5954 | nrm@arcanedomain.com
  1.39% |    1 |  1.06% |     5873 | randy@qti.qualcomm.com
  1.39% |    1 |  1.06% |     5865 | mahmutbulut0@gmail.com
  1.39% |    1 |  1.04% |     5771 | ogud@ogud.com
  1.39% |    1 |  0.91% |     5034 | harald@alvestrand.no
--------+------+--------+----------+------------------------
100.00% |   72 |100.00% |   553590 | Total


From listsebby@me.com  Fri Oct 19 03:42:09 2012
Return-Path: <listsebby@me.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 56EB621F8667 for <ietf@ietfa.amsl.com>; Fri, 19 Oct 2012 03:42:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.299
X-Spam-Level: 
X-Spam-Status: No, score=-4.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MANGLED_OFF=2.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tbf35RB2qJ8D for <ietf@ietfa.amsl.com>; Fri, 19 Oct 2012 03:42:08 -0700 (PDT)
Received: from nk11p04mm-asmtp001.mac.com (nk11p04mm-asmtpout001.mac.com [17.158.236.236]) by ietfa.amsl.com (Postfix) with ESMTP id 5A42C21F8675 for <ietf@ietf.org>; Fri, 19 Oct 2012 03:42:08 -0700 (PDT)
MIME-version: 1.0
Content-type: text/plain; charset=windows-1252
Received: from [192.168.1.5] (natbox.sabahattin-gucukoglu.com [213.123.192.30]) by nk11p04mm-asmtp001.mac.com (Oracle Communications Messaging Server 7u4-24.01(7.0.4.24.0) 64bit (built Jan 3 2012)) with ESMTPSA id <0MC400IN5Z24SS10@nk11p04mm-asmtp001.mac.com> for ietf@ietf.org; Fri, 19 Oct 2012 10:42:07 +0000 (GMT)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.7.7855,1.0.431,0.0.0000 definitions=2012-10-19_02:2012-10-19, 2012-10-19, 1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=5 spamscore=5 ipscore=0 suspectscore=0 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=6.0.2-1203120001 definitions=main-1210190072
Subject: Re: Format=flowed quoting (was "Re: IETF...the unconference of SDOs")
From: Sabahattin Gucukoglu <listsebby@me.com>
In-reply-to: <p06240628cca279fdf657@[99.111.97.136]>
Date: Fri, 19 Oct 2012 11:42:04 +0100
Content-transfer-encoding: quoted-printable
Message-id: <41CCF322-545D-49BD-AEC8-F7595AEE0222@me.com>
References: <94279462-0f48-41ec-933a-a7ac22ba204a@email.android.com> <p06240628cca279fdf657@[99.111.97.136]>
To: Randall Gellens <randy@qti.qualcomm.com>
X-Mailer: Apple Mail (2.1499)
Cc: Michael Richardson {quigon} <mcr@sandelman.ca>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Oct 2012 10:42:09 -0000

Warning: this message was generated by Apple Mail.  I just can't stop my =
insatiable appetite for shiny things.  :-( [1]

On 16 Oct 2012, at 03:46, Randall Gellens <randy@qti.qualcomm.com> =
wrote:

> At 9:12 AM -0400 9/5/12, Michael Richardson {quigon} wrote:
>=20
>> Maybe I'm also concerned because many in the former "elite" have =
moved to Apple Mail, and it seems that it is bug
>> compatible with Outlook in it's assumption that format=3Dflowed is =
the default, an act which destroys email quoting, and therefore =
discussion.
>=20
> I just noticed this assertion, which is quite false.  Format=3Dflowed =
protects and preserved quoting.  It's the only way to avoid ludicrous =
and impossible to read quoting (which happens after quoted passages get =
line-wrapped at odd points).  Also, as far as I know, Exchange does not =
support format=3Dflowed at all.  My understanding is that it insists on =
HTML quoting, which is entirely different.

You're right that this is the virtue of F/F, but that's not what Michael =
said.  Perhaps it was the context of the quoting, but the discussion =
refers to the fact that both LookOut and Apple Mail have (as you can =
see, by looking at this message) a nasty habit of *assuming* an F/F =
semantic by default.  In other words, they generate hugely long long =
long long long long long long long lines that only another equally =
broken client can interpret correctly, but dynamically reflowing those =
lines, by applying consistent quoting indicators to the lines of such =
reflowed lines, and so forth.  That, I believe, is a legitimate =
complaint, because it effectively creates an island between those who =
have support for Format/Flowed and those who do not.  At least Apple has =
the decency to use quoted-printable encoding to protect the actual =
transmitted lines, but it means nothing if competent MIME readers =
reconstitute the corruption at the other end, by reassembling long =
lines, and then failing to reflow them.  And it's worse yet if a news =
reader without MIME tries to quote the lines, complete with Q-P line =
terminators.  Or if a reply comes from somebody whose editor wraps the =
lines, but using soft line breaks which are never generated externally, =
resulting in whole paragraphs being quoted using a single quoting =
indicator.  And so on, and so on, and so on =85

I filed bug 7989556 (Mail uses quoted-printable indiscriminately) with =
Apple on 16 May 2010.  It was marked as duplicate of 7547565 on 25 May =
2010.  The system is closed; you can only see your own bug reports.  I =
therefore have no idea what's going on with that.  Meantime, I apologise =
for the inconvenience.  No, really. :-(

Cheers,
Sabahattin

[1] This isn't strictly true.  I'm blind, and Apple are the only guys =
who have stepped up to accessibility in anything approaching a serious =
manner, by including the screen reader in the OS and ensuring =
accessibility across their applications.  For better or worse, they're =
the only choice for a smartphone, and the only choice for a Windows =
convert (notwithstanding textmode Linux, of course, which I still enjoy =
in VMs for braille support).  I'm objective, so this could change, but =
on both Windows and Mac OS the only really accessible choices are the =
built-in MUAs (I used to use Pegasus Mail under Windows, when I had the =
screen reader support for it, although I now understand that Thunderbird =
has taken its place).


From denis.pinkas@bull.net  Fri Oct 19 03:41:17 2012
Return-Path: <denis.pinkas@bull.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 932D921F8669; Fri, 19 Oct 2012 03:41:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.863
X-Spam-Level: 
X-Spam-Status: No, score=-4.863 tagged_above=-999 required=5 tests=[AWL=1.385,  BAYES_00=-2.599, HELO_EQ_FR=0.35, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Idlytori-lvl; Fri, 19 Oct 2012 03:41:11 -0700 (PDT)
Received: from odin2.bull.net (odin2.bull.net [129.184.85.11]) by ietfa.amsl.com (Postfix) with ESMTP id A7BE821F8662; Fri, 19 Oct 2012 03:41:10 -0700 (PDT)
Received: from MSGC-007.bull.fr (unknown [129.184.87.136]) by odin2.bull.net (Bull S.A.) with ESMTP id 3AD8C4180F8; Fri, 19 Oct 2012 12:41:09 +0200 (CEST)
Received: from [127.0.0.1] ([129.184.39.15]) by MSGC-007.bull.fr (Lotus Domino Release 8.5.3FP1) with ESMTP id 2012101912410821-980 ; Fri, 19 Oct 2012 12:41:08 +0200 
Message-ID: <50812E3F.9070200@bull.net>
Date: Fri, 19 Oct 2012 12:41:03 +0200
From: Denis Pinkas <denis.pinkas@bull.net>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:15.0) Gecko/20120907 Thunderbird/15.0.1
MIME-Version: 1.0
To: iesg@ietf.org
Subject: RE: [pkix] Last Call: <draft-ietf-pkix-rfc5280-clarifications-08.txt>
References: <20121015023425.27492.34330.idtracker@ietfa.amsl.com> <507DEDD4.5070409@ieca.com>
In-Reply-To: <507DEDD4.5070409@ieca.com>
X-MIMETrack: Itemize by SMTP Server on MSGC-007/SRV/BULL(Release 8.5.3FP1|March 07, 2012) at 19/10/2012 12:41:08, Serialize by Router on MSGC-007/SRV/BULL(Release 8.5.3FP1|March 07, 2012) at 19/10/2012 12:41:09, Serialize complete at 19/10/2012 12:41:09
X-TNEFEvaluated: 1
Content-Type: multipart/alternative; boundary="------------030900000302070306050506"
X-Mailman-Approved-At: Fri, 19 Oct 2012 09:29:32 -0700
Cc: Stephen Kent <kent@bbn.com>, iesg-secretary@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, 19 Oct 2012 10:41:17 -0000

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

To the IESG,

I am making an appeal to the IESG from the decision of Steve Kent one of 
the co-chairs of the PKIX WG
to send back the document draft-ietf-pkix-rfc5280-clarifications-10.txt 
to the IESG.

This decision has not even been taken in agreement with the other PKIX 
co-chair Stefan Santesson, since he posted
a message on October 19 to the PKIX list saying:

    The current text requires me to reject a CRL as source of revocation
    information if ANY entry includes an unrecognised extension.
    So thinking as an implementer, I just wander how this works in practice.

    Consider I have a 100 MB CRL.
    I then have to go through each entry and determine if any of them have an
    unrecognised extension before I use it.

    Just going to the entry of interest is not enough, since another entry may
    have an unrecognised extension.

    Is this how implementations work today?

This illustrates once again that keeping the current text would be the 
worse of all the solutions.
*
**I am asking the IESG to send back the document (update to RFC 5280) to 
the WG.*

When the original last call was placed I sent the following argument:

    A discussion has just started yesterday on the PKIX mailing list
    about an "Errata in section 5.3 from RFC 5280".

    At this time it can clearly be seen that RFC 5280 is NOT compatible
    with X.509 for the processing of
    crlEntryExtensions, whereas RFC 5280 is supposed to be a *profile*
    of X.509.

    For that reason, I ask the IESG to suspend its decision until the
    issue about crlEntryExtensions is clarified
    one way or another, since this point now needs to be clarified and
    will impact a document whose goal is precisely
    to clarify RFC 5280.

My request has been accepted and the WG has worked in order to attempt 
to solve the issue.

Several people tried to propose text to fix the current text, while some 
others were providing arguments to say that the text was not "good enough"
but did not proposed an alternative text proposal.

The last exchanges, when attempting to correct the processing of CRL 
entry extensions in RFC 5280, are the following:

On October 5, Denis Pinkas (i.e. myself) made a new strawman proposal, 
using a text proposed by Steve Kent.

On October 9, 2012, Russ Housley replied to Denis Pinkas saying that he 
had arguments against this text.

On October 11, without leaving me the time to reply to Russ, Steve Kent 
asked Peter Yee to remove the Section 4 text from 5280bis and publish 
version -10.

In my opinion, Russ Housley has not spent sufficient time to read my 
proposal since his arguments did not take into consideration my proposed 
text.

Usually a two weeks interval is given by the chairs before making a 
decision. In this case, it has been *two days*, without any warning. I 
believe this is unfair.

The two co-chairs should have remembered to the WG participants 
(including Russ Housley as PKIX WG participant) how to address strawman 
proposals:
everyone is allowed to critize a strawman proposal, as long as he 
provides technical arguments for what he believes is incorrect, and also 
attempts to build
a new strawman proposal using as much as possible the previous one.

This is one of the explanations (but not the single one) why the PKIX WG 
is now unable to reach consensus. The co-chairs should act as facilitators.
They have been too often taking advantage of their "chair hat" while 
defending their own arguments or their own text.

If this appeal is rejected, the text from RFC 5280 will stay as it is, 
but it is incorrect.
Sharon Boeyen, the editor X.509, confirmed it was incorrect on the PKIX 
list on August 28, 2012.

If the document is sent back the WG, as requested, I believe it would be 
appropriate to ask to the PKIX co-chairs :
    (1) to manage the PKIX WG "more appropriately",
    (2) to remember to all the WG participants how to address strawman 
proposals, and
    (3) to avoid taking advantage of their "chair hat" while defending 
their own arguments or their own text.


I believe that the PKIX WG can agree on a "minimum text" shortly.
Having a polished text is even possible, but only if the WG participants 
are clearly instructed how to deal
with strawman proposals.


All of this is only in the interest of publishing RFCs with a correct 
content.

Denis Pinkas

=========================================================================

The facts (in reverse order):

3) On October 11, 2012, without any pre warning, Steve Kent, one of the 
co-chairs of the PKIX WG said :

"The PKIX list has not demonstrated consensus for the CRL entry 
extension text I suggested, or any other,
since Russ sent his message on this topic on 10/3, over a week ago.

  

Consistent with Russ's direction, I have asked Peter Yee to remove the 
Section 4 text from 5280bis and publish version -10.

  

I have begun preparation of the IESG report for the redacted version of 
the doc".

2) On October 9, 2012, Russ Housley replied to Denis Pinkas:

" do not support this alternate text.  If there is an unrecognized CRL 
Entry Extension, then the replying party cannot know
whether the entry applies to a particular certificate or not. 
  Certificates are identified by an issuer and serial number.
An unrecognized CRL Entry Extension can change the issuer portion of the 
tuple.

The relying party can always try an alternate CRL or and alternate 
protocol like OCSP to check out the certificate of interest.
This would be true for any type of CRL validation trouble.

I am unclear how local policy can be helpful here.  If there is an 
unrecognized CRL Entry Extension, the relying party knows
that it cannot use the entry.

If the relying party does not know the issuer associated with a 
particular CRL entry, then it does not know whether that entry
is associated with the certificate of interest or not.  Given this 
situation, I think that the appropriate action is not to treat the
certificate as revoked; instead, the CRL is providing no useful 
information to make such a decision".

1) On October 5, 2012, Denis replied to Russ:

You said:

" Steve put forward some alternate text, but it does not seem to have 
any more consensus than the text in the current I-D.
Can Steve's text be changed in a way that gets us to consensus? "

  

Here is a new proposal for changing Steve's text.

  

===========================================================================

  

    The CRL entry extensions defined by ISO/IEC, ITU-T, and ANSI X9

    for X.509 v2 CRLs provide methods for associating additional

    attributes with CRL entries [X.509] [X9.55].   The X.509 v2 CRL

    format also allows communities to define private CRL entry

    extensions to carry information unique to those communities.

    Each extension in a CRLentry may be designated as critical or

    non-critical.   A critical extension in the crlEntryExtensions

    field of an entry SHALL affect only the certificate identified

    in that entry, unless there is a related critical extension in

    the crlExtensions field that advertises a special treatment for

    it.

  

    If a CRL contains a critical CRL entry extension that the

    application cannot process, then the relying party SHOULD use,

    if possible, other sources of certificate revocation status

    (e.g. OCSP) to accurately the revocation status of the

    certificate identified in that CRLEntry.

    

    If the relying party is able to know (using a local policy)

    that the CRLEntry is associated with the CA that issued the CRL,

    then the relying party SHALL consider that the revocation status

    of the certificate is revoked.

  

    If the relying party is unable to know whether the CRLEntry

    is associated with the CA that issued the CRL, then the relying

    party SHOULD consider that the revocation status of the

    certificate is revoked.

  

    Note: In the last case, the relying party may treat a valid

          certificate as being revoked.   However, since most CAs are

          currently using large random certificate serial numbers,

          a collision between such numbers is rather unlikely.

          So it is more likely that the certificate serial number

          identified in the CRLentry relates to the right CA.

  

===========================================================================

  

The Note above could be transformed and placed in the security considerations section.

  

It is taking care of a situation that is likely to happen one out of a zillion of zillion cases.

  

It is one of the reasons why I have not kept the "dramatic" sentence from Steve's proposal:

  

"the relying party is faced with a difficult choice".

  

   

It seems that the PKIX WG is faced with a difficult choice.   I see three ways we could go regarding the update to Section 5.3 of RFC 5280.

  

(1) Stick with the text in RFC 5280.   At one point in time, there was consensus for it.   Ignoring a CRL with an unrecognized CRL Entry Extension
is not aligned with the most recent version of X.509, but it is a safe thing to do.

  

(2) Build consensus for the text in the current I-D.   We have been working toward that for several weeks, and we are not making progress.

  

(3) Build consensus around some alternate text.   Steve put forward some alternate text, but it does not seem to have any more consensus
than the text in the current I-D.   Can Steve's text be changed in a way that gets us to consensus?   So far, I have seen two major concerns raised that need to be resolved if this is the way forward.

  


Denis


> So that nobody is surprised:
>
> I've placed this draft on the 10/25 IESG telechat.  The -08 version 
> and the -10 version are technically identical.
> -08 went through IETF LC so I'm not planning on issuing another IETF 
> LC for -10.
>
> spt
>
> On 10/14/12 10:34 PM, internet-drafts@ietf.org wrote:
>>
>> A New Internet-Draft is available from the on-line Internet-Drafts 
>> directories.
>>   This draft is a work item of the Public-Key Infrastructure (X.509) 
>> Working Group of the IETF.
>>
>>     Title           : Updates to the Internet X.509 Public Key 
>> Infrastructure Certificate and Certificate Revocation List (CRL) Profile
>>     Author(s)       : Peter E. Yee
>>     Filename        : draft-ietf-pkix-rfc5280-clarifications-10.txt
>>     Pages           : 7
>>     Date            : 2012-10-14
>>
>> Abstract:
>>     This document updates RFC 5280, the Internet X.509 Public Key
>>     Infrastructure Certificate and Certificate Revocation List (CRL)
>>     Profile.  This document changes the set of acceptable encoding
>>     methods for the explicitText field of the user notice policy
>>     qualifier and clarifies the rules for converting internationalized
>>     domain name labels to ASCII.  This document also provides some
>>     clarifications on the use of self-signed certificates, trust 
>> anchors,
>>     and some updated security considerations.
>>
>>
>>
>> The IETF datatracker status page for this draft is:
>> https://datatracker.ietf.org/doc/draft-ietf-pkix-rfc5280-clarifications
>>
>> There's also a htmlized version available at:
>> http://tools.ietf.org/html/draft-ietf-pkix-rfc5280-clarifications-10
>>
>> A diff from the previous version is available at:
>> http://www.ietf.org/rfcdiff?url2=draft-ietf-pkix-rfc5280-clarifications-10 
>>
>>
>>
>> Internet-Drafts are also available by anonymous FTP at:
>> ftp://ftp.ietf.org/internet-drafts/
>>
>> _______________________________________________
>> pkix mailing list
>> pkix@ietf.org
>> https://www.ietf.org/mailman/listinfo/pkix
>>
> _______________________________________________
> pkix mailing list
> pkix@ietf.org
> https://www.ietf.org/mailman/listinfo/pkix


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

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <div class="moz-cite-prefix"><font size="-1" face="Arial">To the
        IESG,<br>
        <br>
        I am making an appeal to the IESG from the decision of Steve
        Kent </font><font size="-1" face="Arial"><font size="-1"
          face="Arial">one of the
          co-chairs of the PKIX WG<br>
        </font>to send back the document
        draft-ietf-pkix-rfc5280-clarifications-10.txt to the IESG.<br>
        <br>
        This decision has not even been taken in agreement with the
        other PKIX co-chair Stefan Santesson, since he posted <br>
        a message on October 19 to the PKIX list saying:</font><br>
      <blockquote>
        <pre wrap="">The current text requires me to reject a CRL as source of revocation
information if ANY entry includes an unrecognised extension.
So thinking as an implementer, I just wander how this works in practice.

Consider I have a 100 MB CRL.
I then have to go through each entry and determine if any of them have an
unrecognised extension before I use it.

Just going to the entry of interest is not enough, since another entry may
have an unrecognised extension.

Is this how implementations work today?
</pre>
      </blockquote>
      <font size="-1" face="Arial">This illustrates once again that
        keeping the current text would be the worse of all the
        solutions. <br>
        <b><br>
        </b></font><font size="-1" face="Arial"><font size="-1"
          face="Arial"><b>I am asking the IESG to send back the document
            (update to RFC 5280) to
            the WG.</b><br>
          <br>
        </font>When the original last call was placed I sent the
        following argument:<br>
      </font>
      <blockquote><font size="-1" face="Arial">A discussion has just
          started yesterday on the PKIX mailing list about an "Errata in
          section 5.3 from RFC 5280".<br>
          <br>
          At this time it can clearly be seen that RFC 5280 is NOT
          compatible with X.509 for the processing of <br>
          crlEntryExtensions, whereas RFC 5280 is supposed to be a
          *profile* of X.509.<br>
          <br>
          For that reason, I ask the IESG to suspend its decision until
          the issue about crlEntryExtensions is clarified <br>
          one way or another, since this point now needs to be clarified
          and will impact a document whose goal is precisely <br>
          to clarify RFC 5280.<br>
        </font></blockquote>
      <font face="Arial"><font size="-1">My request has been accepted
          and the WG has worked in order to attempt to solve the issue.<br>
          <br>
          Several people tried to propose text to fix the current text,
          while some others were providing arguments to say that the
          text was not "good enough"<br>
          but did not proposed an alternative text proposal. </font><br>
      </font>
      <meta http-equiv="Content-Type" content="text/html;
        charset=ISO-8859-1">
      <font size="-1" face="Arial"><o:p> <br>
        </o:p></font>
      <p class="MsoNormal"><font size="-1" face="Arial">The last
          exchanges, when attempting to correct the processing of CRL
          entry extensions in RFC 5280, are the following:<o:p></o:p></font></p>
      <p class="MsoNormal"><font size="-1" face="Arial"><o:p>&nbsp;</o:p></font></p>
      <p class="MsoNormal"><font size="-1" face="Arial">On October 5,
          Denis Pinkas (i.e. myself) made a new strawman proposal,
          using a text proposed by Steve Kent.<o:p></o:p></font></p>
      <p class="MsoNormal"><font size="-1" face="Arial"><o:p>&nbsp;</o:p></font></p>
      <p class="MsoNormal"><font size="-1" face="Arial">On October 9,
          2012, Russ Housley replied to Denis
          Pinkas saying that he had arguments against this text.<o:p></o:p></font></p>
      <p class="MsoNormal"><font size="-1" face="Arial"><o:p>&nbsp;</o:p></font></p>
      <p class="MsoNormal"><font size="-1" face="Arial">On October 11,
          without leaving me the time to reply to Russ, Steve Kent asked
          Peter Yee to remove the Section 4 text from 5280bis
          and publish version -10.<o:p></o:p></font></p>
      <p class="MsoNormal"><font size="-1" face="Arial"><o:p>&nbsp;</o:p></font></p>
      <p class="MsoNormal"><font size="-1" face="Arial">In my opinion,
          Russ Housley has not spent sufficient time to read my
          proposal since his arguments did not take into consideration
          my proposed text.<o:p></o:p></font></p>
      <p class="MsoNormal"><font size="-1" face="Arial"><o:p>&nbsp;</o:p></font></p>
      <p class="MsoNormal"><font size="-1" face="Arial">Usually a two
          weeks interval is given by the chairs before making a
          decision. In this case, it has been <b>two days</b>, without
          any warning. I believe
          this is unfair.<o:p></o:p></font></p>
      <p class="MsoNormal"><font size="-1" face="Arial"><o:p>&nbsp;</o:p></font></p>
      <p class="MsoNormal"><font size="-1" face="Arial">The two
          co-chairs should have remembered to the WG participants
          (including
          Russ Housley as PKIX WG participant) how to address strawman
          proposals:
          <br>
          everyone is allowed to critize a strawman proposal, as long as
          he provides
          technical arguments for what he believes is incorrect, and
          also attempts to
          build <br>
          a new strawman proposal using as much as possible the previous
          one.<o:p></o:p></font></p>
      <p class="MsoNormal"><font size="-1" face="Arial"><o:p>&nbsp;</o:p></font></p>
      <p class="MsoNormal"><font size="-1" face="Arial">This is one of
          the explanations (but not the single one) why the PKIX WG
          is now unable to reach consensus. The co-chairs should act as
          facilitators.
          <br>
          They have been too often taking advantage of their &#8220;chair hat&#8221;
          while defending
          their own arguments or their own text. <o:p></o:p></font></p>
      <p class="MsoNormal"><font size="-1" face="Arial"><o:p>&nbsp;</o:p></font></p>
      <p class="MsoNormal"><font size="-1" face="Arial">If this appeal
          is rejected, the text from RFC 5280 will stay as it is,
          but it is incorrect. <br>
          Sharon Boeyen, the editor X.509, confirmed it was incorrect on
          the PKIX
          list on August 28, 2012.<o:p></o:p></font></p>
      <p class="MsoNormal"><font size="-1" face="Arial"><o:p>&nbsp;</o:p></font></p>
      <p class="MsoNormal"><font size="-1" face="Arial">If the document
          is sent back the WG, as requested, I believe it would be
          appropriate
          to ask to the PKIX co-chairs : <br>
          &nbsp;&nbsp; (1) to manage the PKIX WG &#8220;more appropriately&#8221;, <br>
          &nbsp;&nbsp; (2)
          to remember to all the WG participants how to address strawman
          proposals, and <br>
          &nbsp;&nbsp; (3) to
          avoid taking advantage of their &#8220;chair hat&#8221; while defending
          their own arguments
          or their own text.<br>
        </font></p>
      <p class="MsoNormal"><br>
        <font size="-1" face="Arial">I believe that the PKIX WG can
          agree on a "minimum text" shortly.<br>
          Having a polished text is even possible, but only if the WG
          participants are clearly instructed how to deal <br>
          with strawman proposals.</font></p>
      <br>
      <p class="MsoNormal"><font size="-1" face="Arial">All of this is
          only in the interest of publishing RFCs with a correct
          content.</font><br>
        <font size="-1" face="Arial"><o:p></o:p></font></p>
      <p class="MsoNormal"><font size="-1" face="Arial"><o:p>&nbsp;</o:p></font></p>
      <p class="MsoNormal"><font size="-1" face="Arial">Denis Pinkas<o:p></o:p></font></p>
      <p class="MsoNormal"><font size="-1" face="Arial"><o:p>&nbsp;</o:p></font></p>
      <p class="MsoNormal"><font size="-1" face="Arial">=========================================================================<o:p></o:p></font></p>
      <p class="MsoNormal"><font size="-1" face="Arial">The facts (in
          reverse order):<o:p></o:p></font></p>
      <p class="MsoNormal"><font size="-1" face="Arial"><o:p>&nbsp;</o:p></font></p>
      <p class="MsoNormal"><font size="-1" face="Arial">3) On October
          11, 2012, without any pre warning,
          Steve Kent, one of the co-chairs of the PKIX WG said&nbsp;:<o:p></o:p></font></p>
      <p class="MsoNormal"><font size="-1" face="Arial"><o:p>&nbsp;</o:p></font></p>
      <p class="MsoNormal"><font size="-1" face="Arial">&#8220;The PKIX list
          has not demonstrated consensus for the CRL entry
          extension text I suggested, or any other, <br>
          since
          Russ sent his message on this topic on 10/3, over a week ago.<o:p></o:p></font></p>
      <pre><font size="-1" face="Arial"><span style="mso-ansi-language:EN-GB" lang="EN-GB"><o:p>&nbsp;</o:p></span></font></pre>
      <p class="MsoNormal"><font size="-1" face="Arial">Consistent with
          Russ's direction, I have asked Peter Yee to remove the
          Section 4 text from 5280bis and publish version
          -10.<o:p></o:p></font></p>
      <pre><font size="-1" face="Arial"><span style="mso-ansi-language:EN-GB" lang="EN-GB"><o:p>&nbsp;</o:p></span></font></pre>
      <p class="MsoNormal"><font size="-1" face="Arial">I have begun
          preparation of the IESG report for the redacted version of
          the doc&#8221;. <o:p></o:p></font></p>
      <p class="MsoNormal"><font size="-1" face="Arial"><o:p>&nbsp;</o:p></font></p>
      <p class="MsoNormal"><font size="-1" face="Arial"><o:p>&nbsp;</o:p></font></p>
      <p class="MsoNormal"><font size="-1" face="Arial">2) On October 9,
          2012, Russ Housley replied to Denis
          Pinkas:<o:p></o:p></font></p>
      <p class="MsoNormal"><font size="-1" face="Arial"><o:p>&nbsp;</o:p></font></p>
      <p class="MsoNormal"><font size="-1" face="Arial">&#8220; <span
            style="mso-spacerun:yes">&nbsp;</span>do not
          support this alternate text. &nbsp;If there is an unrecognized CRL
          Entry
          Extension, then the replying party cannot know <br>
          whether the entry applies to a
          particular certificate or not. &nbsp;Certificates are identified by
          an issuer
          and serial number.&nbsp; <br>
          An unrecognized CRL Entry Extension can change the
          issuer portion of the tuple.<o:p></o:p></font></p>
      <p class="MsoNormal"><font size="-1" face="Arial"><o:p>&nbsp;</o:p></font></p>
      <p class="MsoNormal"><font size="-1" face="Arial">The relying
          party can always try an alternate CRL or
          and alternate protocol like OCSP to check out the certificate
          of interest.&nbsp;
          <br>
          This would be true for any type of CRL validation trouble.<o:p></o:p></font></p>
      <p class="MsoNormal"><font size="-1" face="Arial"><o:p>&nbsp;</o:p></font></p>
      <p class="MsoNormal"><font size="-1" face="Arial">I am unclear how
          local policy can be helpful here.
          &nbsp;If there is an unrecognized CRL Entry Extension, the relying
          party knows
          <br>
          that it cannot use the entry.<o:p></o:p></font></p>
      <p class="MsoNormal"><font size="-1" face="Arial"><o:p>&nbsp;</o:p></font></p>
      <p class="MsoNormal"><font size="-1" face="Arial">If the relying
          party does not know the issuer
          associated with a particular CRL entry, then it does not know
          whether that
          entry <br>
          is associated with the certificate of interest or not. &nbsp;Given
          this
          situation, I think that the appropriate action is not to treat
          the <br>
          certificate
          as revoked; instead, the CRL is providing no useful
          information to make such a
          decision&#8221;.<o:p></o:p></font></p>
      <p class="MsoNormal"><font size="-1" face="Arial"><o:p>&nbsp;</o:p></font></p>
      <p class="MsoNormal"><font size="-1" face="Arial">1) On October 5,
          2012, Denis replied to Russ: <o:p></o:p></font></p>
      <p class="MsoNormal"><font size="-1" face="Arial"><o:p>&nbsp;</o:p></font></p>
      <p class="MsoNormal"><font size="-1" face="Arial">You said: <o:p></o:p></font></p>
      <p class="MsoNormal"><font size="-1" face="Arial"><o:p>&nbsp;</o:p></font></p>
      <p class="MsoNormal"><font size="-1" face="Arial">" Steve put
          forward some alternate text, but it
          does not seem to have any more consensus than the text in the
          current I-D.<span style="mso-spacerun:yes">&nbsp; </span><br>
          Can Steve's text be changed in a way that
          gets us to consensus? "<o:p></o:p></font></p>
      <pre><font size="-1" face="Arial"><span style="mso-ansi-language:EN-GB" lang="EN-GB"><o:p>&nbsp;</o:p></span></font></pre>
      <pre><font size="-1" face="Arial"><span style="mso-ansi-language:EN-GB" lang="EN-GB">Here is a new proposal for changing Steve's text.<o:p></o:p></span></font></pre>
      <pre><font size="-1" face="Arial"><span style="mso-ansi-language:EN-GB" lang="EN-GB"><o:p>&nbsp;</o:p></span></font></pre>
      <pre><font size="-1" face="Arial"><span style="mso-ansi-language:EN-GB" lang="EN-GB">===========================================================================<o:p></o:p></span></font></pre>
      <pre><font size="-1" face="Arial"><span style="mso-ansi-language:EN-GB" lang="EN-GB"><o:p>&nbsp;</o:p></span></font></pre>
      <pre><font size="-1" face="Arial"><span style="mso-ansi-language:EN-GB" lang="EN-GB"><span style="mso-spacerun:yes">&nbsp;&nbsp; </span>The CRL entry extensions defined by ISO/IEC, ITU-T, and ANSI X9<o:p></o:p></span></font></pre>
      <pre><font size="-1" face="Arial"><span style="mso-ansi-language:EN-GB" lang="EN-GB"><span style="mso-spacerun:yes">&nbsp;&nbsp; </span>for X.509 v2 CRLs provide methods for associating additional <o:p></o:p></span></font></pre>
      <pre><font size="-1" face="Arial"><span style="mso-ansi-language:EN-GB" lang="EN-GB"><span style="mso-spacerun:yes">&nbsp;&nbsp;&nbsp;</span>attributes with CRL entries [X.509] [X9.55].<span style="mso-spacerun:yes">&nbsp; </span>The X.509 v2 CRL <o:p></o:p></span></font></pre>
      <pre><font size="-1" face="Arial"><span style="mso-ansi-language:EN-GB" lang="EN-GB"><span style="mso-spacerun:yes">&nbsp;&nbsp;&nbsp;</span>format also allows communities to define private CRL entry <o:p></o:p></span></font></pre>
      <pre><font size="-1" face="Arial"><span style="mso-ansi-language:EN-GB" lang="EN-GB"><span style="mso-spacerun:yes">&nbsp;&nbsp;&nbsp;</span>extensions to carry information unique to those communities. <o:p></o:p></span></font></pre>
      <pre><font size="-1" face="Arial"><span style="mso-ansi-language:EN-GB" lang="EN-GB"><span style="mso-spacerun:yes">&nbsp;&nbsp;&nbsp;</span>Each extension in a CRLentry may be designated as critical or <o:p></o:p></span></font></pre>
      <pre><font size="-1" face="Arial"><span style="mso-ansi-language:EN-GB" lang="EN-GB"><span style="mso-spacerun:yes">&nbsp;&nbsp;&nbsp;</span>non-critical.<span style="mso-spacerun:yes">&nbsp; </span>A critical extension in the crlEntryExtensions <o:p></o:p></span></font></pre>
      <pre><font size="-1" face="Arial"><span style="mso-ansi-language:EN-GB" lang="EN-GB"><span style="mso-spacerun:yes">&nbsp;&nbsp;&nbsp;</span>field of an entry SHALL affect only the certificate identified <o:p></o:p></span></font></pre>
      <pre><font size="-1" face="Arial"><span style="mso-ansi-language:EN-GB" lang="EN-GB"><span style="mso-spacerun:yes">&nbsp;&nbsp;&nbsp;</span>in that entry, unless there is a related critical extension in <o:p></o:p></span></font></pre>
      <pre><font size="-1" face="Arial"><span style="mso-ansi-language:EN-GB" lang="EN-GB"><span style="mso-spacerun:yes">&nbsp;&nbsp;&nbsp;</span>the crlExtensions field that advertises a special treatment for <o:p></o:p></span></font></pre>
      <pre><font size="-1" face="Arial"><span style="mso-ansi-language:EN-GB" lang="EN-GB"><span style="mso-spacerun:yes">&nbsp;&nbsp;&nbsp;</span>it. <o:p></o:p></span></font></pre>
      <pre><font size="-1" face="Arial"><span style="mso-ansi-language:EN-GB" lang="EN-GB"><o:p>&nbsp;</o:p></span></font></pre>
      <pre><font size="-1" face="Arial"><span style="mso-ansi-language:EN-GB" lang="EN-GB"><span style="mso-spacerun:yes">&nbsp;&nbsp; </span>If a CRL contains a critical CRL entry extension that the <o:p></o:p></span></font></pre>
      <pre><font size="-1" face="Arial"><span style="mso-ansi-language:EN-GB" lang="EN-GB"><span style="mso-spacerun:yes">&nbsp;&nbsp;&nbsp;</span>application cannot process, then the relying party SHOULD use, <o:p></o:p></span></font></pre>
      <pre><font size="-1" face="Arial"><span style="mso-ansi-language:EN-GB" lang="EN-GB"><span style="mso-spacerun:yes">&nbsp;&nbsp;&nbsp;</span>if possible, other sources of certificate revocation status <o:p></o:p></span></font></pre>
      <pre><font size="-1" face="Arial"><span style="mso-ansi-language:EN-GB" lang="EN-GB"><span style="mso-spacerun:yes">&nbsp;&nbsp;&nbsp;</span>(e.g. OCSP) to accurately the revocation status of the <o:p></o:p></span></font></pre>
      <pre><font size="-1" face="Arial"><span style="mso-ansi-language:EN-GB" lang="EN-GB"><span style="mso-spacerun:yes">&nbsp;&nbsp;&nbsp;</span>certificate identified in that CRLEntry. <o:p></o:p></span></font></pre>
      <pre><font size="-1" face="Arial"><span style="mso-ansi-language:EN-GB" lang="EN-GB"><span style="mso-spacerun:yes">&nbsp;&nbsp;&nbsp;</span><o:p></o:p></span></font></pre>
      <pre><font size="-1" face="Arial"><span style="mso-ansi-language:EN-GB" lang="EN-GB"><span style="mso-spacerun:yes">&nbsp;&nbsp;&nbsp;</span>If the relying party is able to know (using a local policy) <o:p></o:p></span></font></pre>
      <pre><font size="-1" face="Arial"><span style="mso-ansi-language:EN-GB" lang="EN-GB"><span style="mso-spacerun:yes">&nbsp;&nbsp;&nbsp;</span>that the CRLEntry is associated with the CA that issued the CRL, <o:p></o:p></span></font></pre>
      <pre><font size="-1" face="Arial"><span style="mso-ansi-language:EN-GB" lang="EN-GB"><span style="mso-spacerun:yes">&nbsp;&nbsp;&nbsp;</span>then the relying party SHALL consider that the revocation status <o:p></o:p></span></font></pre>
      <pre><font size="-1" face="Arial"><span style="mso-ansi-language:EN-GB" lang="EN-GB"><span style="mso-spacerun:yes">&nbsp;&nbsp;&nbsp;</span>of the certificate is revoked. <o:p></o:p></span></font></pre>
      <pre><font size="-1" face="Arial"><span style="mso-ansi-language:EN-GB" lang="EN-GB"><o:p>&nbsp;</o:p></span></font></pre>
      <pre><font size="-1" face="Arial"><span style="mso-ansi-language:EN-GB" lang="EN-GB"><span style="mso-spacerun:yes">&nbsp;&nbsp; </span>If the relying party is unable to know whether the CRLEntry <o:p></o:p></span></font></pre>
      <pre><font size="-1" face="Arial"><span style="mso-ansi-language:EN-GB" lang="EN-GB"><span style="mso-spacerun:yes">&nbsp;&nbsp;&nbsp;</span>is associated with the CA that issued the CRL, then the relying <o:p></o:p></span></font></pre>
      <pre><font size="-1" face="Arial"><span style="mso-ansi-language:EN-GB" lang="EN-GB"><span style="mso-spacerun:yes">&nbsp;&nbsp;&nbsp;</span>party SHOULD consider that the revocation status of the <o:p></o:p></span></font></pre>
      <pre><font size="-1" face="Arial"><span style="mso-ansi-language:EN-GB" lang="EN-GB"><span style="mso-spacerun:yes">&nbsp;&nbsp;&nbsp;</span>certificate is revoked.<o:p></o:p></span></font></pre>
      <pre><font size="-1" face="Arial"><span style="mso-ansi-language:EN-GB" lang="EN-GB"><o:p>&nbsp;</o:p></span></font></pre>
      <pre><font size="-1" face="Arial"><span style="mso-ansi-language:EN-GB" lang="EN-GB"><span style="mso-spacerun:yes">&nbsp;&nbsp; </span>Note: In the last case, the relying party may treat a valid <o:p></o:p></span></font></pre>
      <pre><font size="-1" face="Arial"><span style="mso-ansi-language:EN-GB" lang="EN-GB"><span style="mso-spacerun:yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span>certificate as being revoked.<span style="mso-spacerun:yes">&nbsp; </span>However, since most CAs are <o:p></o:p></span></font></pre>
      <pre><font size="-1" face="Arial"><span style="mso-ansi-language:EN-GB" lang="EN-GB"><span style="mso-spacerun:yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span>currently using large random certificate serial numbers, <o:p></o:p></span></font></pre>
      <pre><font size="-1" face="Arial"><span style="mso-ansi-language:EN-GB" lang="EN-GB"><span style="mso-spacerun:yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span>a collision between such numbers is rather unlikely.<o:p></o:p></span></font></pre>
      <pre><font size="-1" face="Arial"><span style="mso-ansi-language:EN-GB" lang="EN-GB"><span style="mso-spacerun:yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span>So it is more likely that the certificate serial number <o:p></o:p></span></font></pre>
      <pre><font size="-1" face="Arial"><span style="mso-ansi-language:EN-GB" lang="EN-GB"><span style="mso-spacerun:yes">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</span>identified in the CRLentry relates to the right CA.<o:p></o:p></span></font></pre>
      <pre><font size="-1" face="Arial"><span style="mso-ansi-language:EN-GB" lang="EN-GB"><o:p>&nbsp;</o:p></span></font></pre>
      <pre><font size="-1" face="Arial"><span style="mso-ansi-language:EN-GB" lang="EN-GB">===========================================================================<o:p></o:p></span></font></pre>
      <pre><font size="-1" face="Arial"><span style="mso-ansi-language:EN-GB" lang="EN-GB"><o:p>&nbsp;</o:p></span></font></pre>
      <pre><font size="-1" face="Arial"><span style="mso-ansi-language:EN-GB" lang="EN-GB">The Note above could be transformed and placed in the security considerations section.<o:p></o:p></span></font></pre>
      <pre><font size="-1" face="Arial"><span style="mso-ansi-language:EN-GB" lang="EN-GB"><o:p>&nbsp;</o:p></span></font></pre>
      <pre><font size="-1" face="Arial"><span style="mso-ansi-language:EN-GB" lang="EN-GB">It is taking care of a situation that is likely to happen one out of a zillion of zillion cases.<o:p></o:p></span></font></pre>
      <pre><font size="-1" face="Arial"><span style="mso-ansi-language:EN-GB" lang="EN-GB"><o:p>&nbsp;</o:p></span></font></pre>
      <pre><font size="-1" face="Arial"><span style="mso-ansi-language:EN-GB" lang="EN-GB">It is one of the reasons why I have not kept the "dramatic" sentence from Steve's proposal: <o:p></o:p></span></font></pre>
      <pre><font size="-1" face="Arial"><span style="mso-ansi-language:EN-GB" lang="EN-GB"><o:p>&nbsp;</o:p></span></font></pre>
      <pre><font size="-1" face="Arial"><span style="mso-ansi-language:EN-GB" lang="EN-GB">"the relying party is faced with a difficult choice".<o:p></o:p></span></font></pre>
      <pre><font size="-1" face="Arial"><span style="mso-ansi-language:EN-GB" lang="EN-GB"><o:p>&nbsp;</o:p></span></font></pre>
      <pre><font size="-1" face="Arial"><span style="mso-ansi-language:EN-GB" lang="EN-GB"><span style="mso-spacerun:yes">&nbsp; </span><o:p></o:p></span></font></pre>
      <p class="MsoNormal"><font size="-1" face="Arial"><span
            style="mso-ansi-language:EN-GB" lang="EN-GB"><o:p>&nbsp;</o:p></span></font></p>
      <pre><font size="-1" face="Arial"><span style="mso-ansi-language:EN-GB" lang="EN-GB">It seems that the PKIX WG is faced with a difficult choice.<span style="mso-spacerun:yes">&nbsp; </span>I see three ways we could go regarding the update to Section 5.3 of RFC 5280.<o:p></o:p></span></font></pre>
      <pre><font size="-1" face="Arial"><span style="mso-ansi-language:EN-GB" lang="EN-GB"><o:p>&nbsp;</o:p></span></font></pre>
      <pre><font size="-1" face="Arial"><span style="mso-ansi-language:EN-GB" lang="EN-GB">(1) Stick with the text in RFC 5280.<span style="mso-spacerun:yes">&nbsp; </span>At one point in time, there was consensus for it.<span style="mso-spacerun:yes">&nbsp; </span>Ignoring a CRL with an unrecognized CRL Entry Extension 
is not aligned with the most recent version of X.509, but it is a safe thing to do.<o:p></o:p></span></font></pre>
      <pre><font size="-1" face="Arial"><span style="mso-ansi-language:EN-GB" lang="EN-GB"><o:p>&nbsp;</o:p></span></font></pre>
      <pre><font size="-1" face="Arial"><span style="mso-ansi-language:EN-GB" lang="EN-GB">(2) Build consensus for the text in the current I-D.<span style="mso-spacerun:yes">&nbsp; </span>We have been working toward that for several weeks, and we are not making progress.<o:p></o:p></span></font></pre>
      <pre><font size="-1" face="Arial"><span style="mso-ansi-language:EN-GB" lang="EN-GB"><o:p>&nbsp;</o:p></span></font></pre>
      <pre><font size="-1" face="Arial"><span style="mso-ansi-language:EN-GB" lang="EN-GB">(3) Build consensus around some alternate text.<span style="mso-spacerun:yes">&nbsp; </span>Steve put forward some alternate text, but it does not seem to have any more consensus 
than the text in the current I-D.<span style="mso-spacerun:yes">&nbsp; </span>Can Steve's text be changed in a way that gets us to consensus?<span style="mso-spacerun:yes">&nbsp; </span>So far, I have seen two major concerns raised that need to be resolved if this is the way forward.<o:p></o:p></span></font></pre>
      <pre><font size="-1" face="Arial"><span style="mso-ansi-language:EN-GB" lang="EN-GB"><o:p>&nbsp;</o:p></span></font></pre>
      <meta name="ProgId" content="Word.Document">
      <meta name="Generator" content="Microsoft Word 11">
      <meta name="Originator" content="Microsoft Word 11">
      <link rel="File-List"
href="file:///C:%5CDOCUME%7E1%5CPINKAS%5CLOCALS%7E1%5CTemp%5Cmsohtml1%5C01%5Cclip_filelist.xml">
      <!--[if gte mso 9]><xml>
 <w:WordDocument>
  <w:View>Normal</w:View>
  <w:Zoom>0</w:Zoom>
  <w:HyphenationZone>21</w:HyphenationZone>
  <w:PunctuationKerning/>
  <w:ValidateAgainstSchemas/>
  <w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>
  <w:IgnoreMixedContent>false</w:IgnoreMixedContent>
  <w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>
  <w:Compatibility>
   <w:BreakWrappedTables/>
   <w:SnapToGridInCell/>
   <w:WrapTextWithPunct/>
   <w:UseAsianBreakRules/>
   <w:DontGrowAutofit/>
  </w:Compatibility>
  <w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel>
 </w:WordDocument>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:LatentStyles DefLockedState="false" LatentStyleCount="156">
 </w:LatentStyles>
</xml><![endif]-->
      <style>
<!--
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-parent:"";
	margin:0cm;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
pre
	{margin:0cm;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:10.0pt;
	font-family:"Courier New";
	mso-fareast-font-family:"Times New Roman";}
tt
	{font-family:"Courier New";
	mso-ascii-font-family:"Courier New";
	mso-fareast-font-family:"Times New Roman";
	mso-hansi-font-family:"Courier New";
	mso-bidi-font-family:"Courier New";}
@page Section1
	{size:595.3pt 841.9pt;
	margin:53.85pt 70.9pt 59.55pt 70.9pt;
	mso-header-margin:35.45pt;
	mso-footer-margin:35.45pt;
	mso-paper-source:0;}
div.Section1
	{page:Section1;}
-->
</style><!--[if gte mso 10]>
<style>
 /* Style Definitions */
 table.MsoNormalTable
	{mso-style-name:"Tableau Normal";
	mso-tstyle-rowband-size:0;
	mso-tstyle-colband-size:0;
	mso-style-noshow:yes;
	mso-style-parent:"";
	mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
	mso-para-margin:0cm;
	mso-para-margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:10.0pt;
	font-family:"Times New Roman";
	mso-ansi-language:#0400;
	mso-fareast-language:#0400;
	mso-bidi-language:#0400;}
</style>
<![endif]--><font size="-1" face="Arial"><br>
        Denis<br>
        <br>
        <br>
      </font></div>
    <blockquote cite="mid:507DEDD4.5070409@ieca.com" type="cite"><font
        size="-1" face="Arial">So that nobody is surprised:
        <br>
        <br>
        I've placed this draft on the 10/25 IESG telechat.&nbsp; The -08
        version and the -10 version are technically identical.&nbsp; <br>
        -08 went through IETF LC so I'm not planning on issuing another
        IETF LC for -10.
      </font><font size="-1">
        <font face="Arial"><br>
          <br>
          spt
        </font>
        <font face="Arial"><br>
          <br>
          On 10/14/12 10:34 PM, <a class="moz-txt-link-abbreviated" href="mailto:internet-drafts@ietf.org">internet-drafts@ietf.org</a> wrote:
        </font>
        <font face="Arial"><br>
        </font></font>
      <blockquote type="cite">
        <font size="-1" face="Arial"><br>
          A New Internet-Draft is available from the on-line
          Internet-Drafts directories.
          <br>
          &nbsp; This draft is a work item of the Public-Key Infrastructure
          (X.509) Working Group of the IETF.
          <br>
          <br>
        </font><font size="-1">
          <font face="Arial">&nbsp;&nbsp;&nbsp;&nbsp;Title&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : Updates to the
            Internet X.509 Public Key Infrastructure Certificate and
            Certificate Revocation List (CRL) Profile
            <br>
            &nbsp;&nbsp;&nbsp;&nbsp;Author(s)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : Peter E. Yee
            <br>
            &nbsp;&nbsp;&nbsp;&nbsp;Filename&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; :
            draft-ietf-pkix-rfc5280-clarifications-10.txt
            <br>
            &nbsp;&nbsp;&nbsp;&nbsp;Pages&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : 7
            <br>
            &nbsp;&nbsp;&nbsp;&nbsp;Date&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : 2012-10-14
            <br>
            <br>
            Abstract:
          </font>
          <font face="Arial"><br>
            &nbsp;&nbsp;&nbsp; This document updates RFC 5280, the Internet X.509
            Public Key
            <br>
            &nbsp;&nbsp;&nbsp; Infrastructure Certificate and Certificate Revocation
            List (CRL)
            <br>
            &nbsp;&nbsp;&nbsp; Profile.&nbsp; This document changes the set of acceptable
            encoding
            <br>
            &nbsp;&nbsp;&nbsp; methods for the explicitText field of the user notice
            policy
            <br>
            &nbsp;&nbsp;&nbsp; qualifier and clarifies the rules for converting
            internationalized
            <br>
            &nbsp;&nbsp;&nbsp; domain name labels to ASCII.&nbsp; This document also
            provides some
            <br>
            &nbsp;&nbsp;&nbsp; clarifications on the use of self-signed certificates,
            trust anchors,
            <br>
            &nbsp;&nbsp;&nbsp; and some updated security considerations.
            <br>
            <br>
            <br>
            <br>
            The IETF datatracker status page for this draft is:
          </font>
          <font face="Arial"><br>
<a class="moz-txt-link-freetext" href="https://datatracker.ietf.org/doc/draft-ietf-pkix-rfc5280-clarifications">https://datatracker.ietf.org/doc/draft-ietf-pkix-rfc5280-clarifications</a>
            <br>
            <br>
            There's also a htmlized version available at:
          </font>
          <font face="Arial"><br>
<a class="moz-txt-link-freetext" href="http://tools.ietf.org/html/draft-ietf-pkix-rfc5280-clarifications-10">http://tools.ietf.org/html/draft-ietf-pkix-rfc5280-clarifications-10</a>
            <br>
            <br>
            A diff from the previous version is available at:
          </font>
          <font face="Arial"><br>
<a class="moz-txt-link-freetext" href="http://www.ietf.org/rfcdiff?url2=draft-ietf-pkix-rfc5280-clarifications-10">http://www.ietf.org/rfcdiff?url2=draft-ietf-pkix-rfc5280-clarifications-10</a>
            <br>
            <br>
            <br>
            Internet-Drafts are also available by anonymous FTP at:
          </font>
          <font face="Arial"><br>
            <a class="moz-txt-link-freetext" href="ftp://ftp.ietf.org/internet-drafts/">ftp://ftp.ietf.org/internet-drafts/</a>
            <br>
            <br>
            _______________________________________________
          </font>
          <font face="Arial"><br>
            pkix mailing list
            <br>
            <a class="moz-txt-link-abbreviated" href="mailto:pkix@ietf.org">pkix@ietf.org</a>
            <br>
            <a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/pkix">https://www.ietf.org/mailman/listinfo/pkix</a>
            <br>
            <br>
          </font></font>
      </blockquote>
      <font size="-1" face="Arial">_______________________________________________
        <br>
        pkix mailing list
        <br>
        <a class="moz-txt-link-abbreviated" href="mailto:pkix@ietf.org">pkix@ietf.org</a>
        <br>
        <a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/pkix">https://www.ietf.org/mailman/listinfo/pkix</a>
        <br>
      </font>
    </blockquote>
    <font face="Arial"><br>
    </font>
  </body>
</html>

--------------030900000302070306050506--


From listsebby@me.com  Fri Oct 19 11:46:37 2012
Return-Path: <listsebby@me.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C7F2621F8759 for <ietf@ietfa.amsl.com>; Fri, 19 Oct 2012 11:46:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.799
X-Spam-Level: 
X-Spam-Status: No, score=-2.799 tagged_above=-999 required=5 tests=[AWL=-1.500, BAYES_00=-2.599, MANGLED_OFF=2.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ehbwf8csXery for <ietf@ietfa.amsl.com>; Fri, 19 Oct 2012 11:46:33 -0700 (PDT)
Received: from nk11p04mm-asmtp008.mac.com (nk11p04mm-asmtpout008.mac.com [17.158.236.243]) by ietfa.amsl.com (Postfix) with ESMTP id 500A721F8778 for <ietf@ietf.org>; Fri, 19 Oct 2012 11:46:33 -0700 (PDT)
MIME-version: 1.0
Content-type: text/plain; charset=windows-1252
Received: from [192.168.1.5] (natbox.sabahattin-gucukoglu.com [213.123.192.30]) by nk11p04mm-asmtp008.mac.com (Oracle Communications Messaging Server 7u4-24.01(7.0.4.24.0) 64bit (built Jan 3 2012)) with ESMTPSA id <0MC50014CLHGJH10@nk11p04mm-asmtp008.mac.com> for ietf@ietf.org; Fri, 19 Oct 2012 18:46:31 +0000 (GMT)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.7.7855,1.0.431,0.0.0000 definitions=2012-10-19_04:2012-10-19, 2012-10-19, 1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 ipscore=0 suspectscore=0 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=6.0.2-1203120001 definitions=main-1210190218
Subject: Re: Format=flowed quoting (was "Re: IETF...the unconference of SDOs")
From: Sabahattin Gucukoglu <listsebby@me.com>
In-reply-to: <p06240600cca730fbf54c@[99.111.97.136]>
Date: Fri, 19 Oct 2012 19:46:28 +0100
Content-transfer-encoding: quoted-printable
Message-id: <FB2B1327-D139-4986-BC4A-C0F45D7C3865@me.com>
References: <94279462-0f48-41ec-933a-a7ac22ba204a@email.android.com> <p06240628cca279fdf657@[99.111.97.136]> <41CCF322-545D-49BD-AEC8-F7595AEE0222@me.com> <p06240600cca730fbf54c@[99.111.97.136]>
To: Randall Gellens <randy@qti.qualcomm.com>
X-Mailer: Apple Mail (2.1499)
Cc: Michael Richardson {quigon} <mcr@sandelman.ca>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Oct 2012 18:46:37 -0000

On 19 Oct 2012, at 17:45, Randall Gellens <randy@qti.qualcomm.com> =
wrote:
> At 11:42 AM +0100 10/19/12, Sabahattin Gucukoglu wrote:
>> Warning: this message was generated by Apple Mail.
>=20
> But not using Format=3DFlowed.

Precisely.

> On 16 Oct 2012, at 03:46, Randall Gellens <randy@qti.qualcomm.com> =
wrote:
>>> At 9:12 AM -0400 9/5/12, Michael Richardson {quigon} wrote:
>>>> Maybe I'm also concerned because many in the former "elite" have =
moved to Apple Mail, and it seems that it is bug
>>>> compatible with Outlook in it's assumption that format=3Dflowed is =
the default, an act which destroys email quoting, and therefore =
discussion.
>>>=20
>>> I just noticed this assertion, which is quite false.  Format=3Dflowed =
protects and preserved quoting.  It's the only way to avoid ludicrous =
and impossible to read quoting (which happens after quoted passages get =
line-wrapped at odd points).  Also, as far as I know, Exchange does not =
support format=3Dflowed at all.  My understanding is that it insists on =
HTML quoting, which is entirely different.
>>=20
>> You're right that this is the virtue of F/F, but that's not what =
Michael said.  Perhaps it was the context of the quoting, but the =
discussion refers to the fact that both LookOut and Apple Mail have (as =
you can see, by looking at this message) a nasty habit of *assuming* an =
F/F semantic by default.  In other words, they generate hugely long long =
long long long long long long long lines that only another equally =
broken client can interpret correctly, but dynamically reflowing those =
lines, by applying consistent quoting indicators to the lines of such =
reflowed lines, and so forth.  That, I believe, is a legitimate =
complaint, because it e
>=20
> This reflects a misunderstanding of Format=3DFlowed.  Properly =
generated F=3DF has lines of no more than 78 characters.  One of the =
primary goals of F=3DF is good interoperability between clients that =
support F=3DF and those that support traditional pure plain text email.  =
What you're describing is a symptom of HTML quoting (or a surprisingly =
poor F=3DF implementation):

Yes, absolutely.  We do not disagree.

Let's clear up the confusion.  I made two mistakes, firstly by calling =
this "F/F semantics" when what I mean is some sort of long-line-aware =
reflowing and quoting.  We'll have to find a name for it.  The other =
mistake was to call plain text plain text of any description, =
irrespective of the definition of text/plain.

So we are talking about three formats:
* text/plain, 78 characters wide
* format=3Dflowed, text/plain with soft breaks signalled by trailing =
whitespace, 78 characters
* text/paragraphs (or whatever), a completely different identity that =
violates the length limits

Apple Mail and Microsoft use this text/paragraphs.  It's not =
interoperable with text/plain (because it *isn't* text/plain, as you =
very correctly note) and therefore it gives everyone a really hard time. =
 Unless you've not dealt with plain text files from Windows or OS X, you =
may be sure that "Plain text" most certainly doesn't conform to RFC 822, =
either.

We should now all be on the same page, I think. :-)

> When generating Format=3DFlowed text, lines SHOULD be 78 characters or
>   shorter, including any trailing white space and also including any
>   space added as part of stuffing (see Section 4.4).  As suggested
>   values, any paragraph longer than 78 characters in total length =
could
>   be wrapped using lines of 72 or fewer characters.  While the =
specific
>   line length used is a matter of aesthetics and preference, longer
>   lines are more likely to require rewrapping and to encounter
>   difficulties with older mailers.  (It has been suggested that 66
>   character lines are the most readable.)
>=20
>   The restriction to 78 or fewer characters between CRLFs on the wire
>   is to conform to [MSG-FMT].
>=20
>=20
>> At least Apple has the decency to use quoted-printable encoding to =
protect the actual transmitted lines,
>=20
> Again, this shows a fundamental misunderstanding of F=3DF.  Properly =
generated F=3DF does not use quoted-printable unless otherwise needed:

Yes.  Apple Mail doesn't do this--it uses QP to keep the line lengths =
valid in transmission only.  Some mailers, or gateways, wouldn't do =
that, but would instead spew out long lines that compliant SMTP servers =
would helpfully corrupt, tail-drop, chop into pieces, etc (for lack of =
robustness or to protect themselves).

>> but it means nothing if competent MIME readers reconstitute the =
corruption at the other end, by reassembling long lines, and then =
failing to reflow them.  And it's worse yet if a news reader without =
MIME tries to quote the lines, complete with Q-P line terminators.  Or =
if a reply comes from somebody whose editor wraps the lines, but using =
soft line breaks which are never generated externally, resulting in =
whole paragraphs being quoted using a single quoting indicator.  And so =
on, and so on, and so on =8A
>=20
> All of these are part of the problem set that F=3DF was created to =
fix.  Proper F=3DF plays nice with pure plain text.

My first exposure to large numbers of affected people was on Usenet, =
when I sent mail from Apple Mail through a gateway.  Apparently, =
newsreaders fall into the categories of having no MIME at all, or having =
MIME but not reflowing text.  In any case, they were unhappy. :-(

>> I filed bug 7989556 (Mail uses quoted-printable indiscriminately) =
with Apple on 16 May 2010. It was marked as duplicate of 7547565 on 25 =
May 2010.  The system is closed; you can only see your own bug reports.  =
I therefore have no idea what's going on with that.  Meantime, I =
apologise for the inconvenience.  No, really. :-(
>=20
> I haven't looked into Apple's mail's generation of either F=3DF or =
plain text or HTML.  If it generates F=3DF with long lines and/or =
indiscriminate q-p, then those would in my view be bugs that should be =
fixed.  But I don't know if the symptoms described occur with Apple =
Mail's F=3DF or some other format.  To me, they sound like lack of F=3DF.

At one point--in Leopard (10.5), I think--they were using F=3DF.  It =
almost looks like the current behaviour is what's left of the F=3DF =
implementation, in that it renders and sends emails that can be flowed, =
though using text/paragraphs rather than F=3DF.

Cheers,
Sabahattin


From sm@elandsys.com  Fri Oct 19 13:06:17 2012
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3935421F842B for <ietf@ietfa.amsl.com>; Fri, 19 Oct 2012 13:06:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XunRLMcSxaft for <ietf@ietfa.amsl.com>; Fri, 19 Oct 2012 13:06:16 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 67D2C21F8200 for <ietf@ietf.org>; Fri, 19 Oct 2012 13:06:16 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.226.233.154]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id q9JK5pjL009248 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 19 Oct 2012 13:06:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1350677165; bh=oTABySVSYMaWdWW7V90CqwWgeLFIF8wZIL38jRdYyJ0=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=dCHOTjof8lmGpesqt4xU9JMO7y4eJklgzl43DXI1Ew6FyxfzmDer9s7RJygu+fkJ9 aohUHHwdt+Cs01P78oqkwWNP+J7K5h5KF6N3wocMZWA6ehtYkoRnBuNPJ6JHqArkfg 4fOPNe3bHzkqEZqDhyrlx1jXJOtwGgkeEYD46u/4=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1350677165; i=@elandsys.com; bh=oTABySVSYMaWdWW7V90CqwWgeLFIF8wZIL38jRdYyJ0=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=O3NkBtMu/HfmVu0I8VEr/qhBgwweZXDVghTVG82RYM70C4ZaRCHhW8x/ox04jUM3M GxJyt5MCmyUJbQbsdW3P1eIa1fOKczbQ/fpdTRenUtVpgbsp8P7foPZTWIz/yKZ3zT vlRhgMMD82aqBribZzDrERV4WZADk+RlBHP260v8=
Message-Id: <6.2.5.6.2.20121019123120.09fe1fb0@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 19 Oct 2012 12:57:37 -0700
To: ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Last Call: <draft-leiba-3777upd-eligibility-04.txt> (Update to RFC 3777 to Clarify Nominating Committee Eligibility of IETF Leadership) to Best Current Practice
In-Reply-To: <CAC4RtVA4xNndP=ok7DzoZJRz14Ox8q7yCh57wwcUoS6QGHpf1Q@mail.g mail.com>
References: <20120927150522.9680.50930.idtracker@ietfa.amsl.com> <8098D3F7-A030-49F0-ADBC-EE2F2F360D15@vigilsec.com> <CAC4RtVA4xNndP=ok7DzoZJRz14Ox8q7yCh57wwcUoS6QGHpf1Q@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: Adrian Farrel <adrian@olddog.co.uk>, Barry Leiba <barryleiba@computer.org>, Ted Hardie <ted.ietf@gmail.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Oct 2012 20:06:17 -0000

Hello,

Although the Last Call for draft-leiba-3777upd-eligibility-04 has not 
ended, I'll do a quick summary.  Russ Housley (as an individual) 
commented about updating one sentence about the recall of an IAOC 
member [1].  Barry recommended addressing this as part of a more 
comprehensive update [2].  Dave Crocker mentioned that such a change 
would alter the scope of the draft [3].  He also commented on "paid 
staff".  There was a comment from Ted Hardie [4] about that.  Adrian 
Farrel made two small editorial proposals [5] to which Barry agreed.

Please let me know if your comments have not been addressed.

Regards,
S. Moonesamy (as document shepherd)

1. http://www.ietf.org/mail-archive/web/ietf/current/msg75129.html
2. http://www.ietf.org/mail-archive/web/ietf/current/msg75138.html
3. http://www.ietf.org/mail-archive/web/ietf/current/msg75130.html
4. http://www.ietf.org/mail-archive/web/ietf/current/msg75135.html
5. http://www.ietf.org/mail-archive/web/ietf/current/msg75136.html


From adrian@olddog.co.uk  Sat Oct 20 12:57:14 2012
Return-Path: <adrian@olddog.co.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EE99A21F890B for <ietf@ietfa.amsl.com>; Sat, 20 Oct 2012 12:57:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id A09nNoBGCvNj for <ietf@ietfa.amsl.com>; Sat, 20 Oct 2012 12:57:14 -0700 (PDT)
Received: from asmtp3.iomartmail.com (asmtp3.iomartmail.com [62.128.201.159]) by ietfa.amsl.com (Postfix) with ESMTP id 2E78221F8904 for <ietf@ietf.org>; Sat, 20 Oct 2012 12:57:14 -0700 (PDT)
Received: from asmtp3.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id q9KJvCuq002513;  Sat, 20 Oct 2012 20:57:12 +0100
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id q9KJvAKk002495 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sat, 20 Oct 2012 20:57:11 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <jjaeggli@zynga.com>
References: <20121020174758.27335.19177.idtracker@ietfa.amsl.com>
In-Reply-To: <20121020174758.27335.19177.idtracker@ietfa.amsl.com>
Subject: RE: I-D Action: draft-jaeggli-interim-observations-02.txt
Date: Sat, 20 Oct 2012 20:57:12 +0100
Message-ID: <0b8201cdaefd$1996e210$4cc4a630$@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: AQJGaqi1/DM+Caq8hkHWfP6nGkP3G5bRIqWA
Content-Language: en-gb
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 20 Oct 2012 19:57:15 -0000

Thanks for the revision, Joel.

My greatest take-away is the phrase you suggest might be a tautology...

   Interim meetings probably are more
   successful when they appear necessary

In general, WGs feel they must meet at full IETF meetings, and they are
well-attended because everyone is there for the whole week often to do other
stuff.

In general, interims are only held when there is real need and desire to attend.
Thus, most WGs do not hold interims.

My concern with the relatively small LIM is that WGs feel they will "give it a
try" without having enough to discuss face to face. Not saying this happened
this time, but it seems like a WG might say "there's a LIM going on, so we might
as well meet" a bit like they do at a full IETF meeting, but without the
guaranteed attendance.

As you say, it is hard to draw a firm conclusion from just one experiment.

Thanks,
Adrian

> -----Original Message-----
> From: i-d-announce-bounces@ietf.org [mailto:i-d-announce-bounces@ietf.org]
> On Behalf Of internet-drafts@ietf.org
> Sent: 20 October 2012 18:48
> To: i-d-announce@ietf.org
> Subject: I-D Action: draft-jaeggli-interim-observations-02.txt
> 
> A New Internet-Draft is available from the on-line Internet-Drafts
directories.
> 
> 	Title           : Observations on the experience and nature of Large
Interim
> Meetings
> 	Author(s)       : Joel Jaeggli
>                           Jari Arkko
> 	Filename        : draft-jaeggli-interim-observations-02.txt
> 	Pages           : 9
> 	Date            : 2012-10-20
> 
> Abstract:
>    Planning, particpipation and conclusions from the experience of
>    participating in the IETF LIM activity on september 29th 2012.
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-jaeggli-interim-observations


From dhc@dcrocker.net  Sun Oct 21 09:31:44 2012
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 68E3621F88BD for <ietf@ietfa.amsl.com>; Sun, 21 Oct 2012 09:31:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rsOxpigmJbhc for <ietf@ietfa.amsl.com>; Sun, 21 Oct 2012 09:31:43 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id AF3AD21F860E for <ietf@ietf.org>; Sun, 21 Oct 2012 09:31:43 -0700 (PDT)
Received: from [192.168.11.199] (ip-64-134-97-182.public.wayport.net [64.134.97.182]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q9LGVfLl017119 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <ietf@ietf.org>; Sun, 21 Oct 2012 09:31:43 -0700
Message-ID: <50842367.3040108@dcrocker.net>
Date: Sun, 21 Oct 2012 12:31:35 -0400
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121010 Thunderbird/16.0.1
MIME-Version: 1.0
To: IETF Discussion <ietf@ietf.org>
Subject: In Memoriam IETF web page
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, 21 Oct 2012 09:31:43 -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, 21 Oct 2012 16:31:44 -0000

Folks,

A thread on the nanog list, about abha ahuja, reminds me of a suggestion 
I made casually to a few folk after the last IETF meeting:

      We should consider having a persistent IETF page in memory of 
people who were part of our community.

While the idea is simple, the comments I got back make clear that it 
needs to be pursued carefully.  That requires some formality.

There are two different lines of consideration. These are offered as a 
starting point for discussion:


1.   Who should be listed?

      A number of different models make sense, but the challenge is 
something that is workable. For example, it does not seem like the sort 
of thing that would be appropriate for a consensus call to the 
community, for each entry.  I think that means the rules should be 
entirely mechanical.

      Conceptually, the goal should be to include anyone who was "part 
of the IETF community".  I'll suggest that any of these would qualify:

      a. Held a formal position in the IETF (AD, WG Chair, IAOC/Trust,
         IAB, IRTF, Nomcom, ...are there others?)

      b. Held a position on an IETF committee (directorate,
         advisory, ...)

      c. Held a position on IETF staff (IAD, RFC Editor and, I think,
         this should include on-going contractors, including AMS and RFC
         document editors.

      d. RFC author


2.   What should be the form of the page?

      I suggest we keep it extremely simple:  an alphabetic listing by 
name, with a photo, if available, and a pointer to a page if they have 
one.  In some cases, the IETF might formulate its own page for a person, 
but that's distinct from this basic listing.


Thoughts?

d/

-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From housley@vigilsec.com  Sun Oct 21 09:36:50 2012
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3DD2421F8995 for <ietf@ietfa.amsl.com>; Sun, 21 Oct 2012 09:36:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.619
X-Spam-Level: 
X-Spam-Status: No, score=-102.619 tagged_above=-999 required=5 tests=[AWL=-0.020, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MhlLRZksgAgF for <ietf@ietfa.amsl.com>; Sun, 21 Oct 2012 09:36:49 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id 8D41A21F8993 for <ietf@ietf.org>; Sun, 21 Oct 2012 09:36:49 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 72FCF9A4003; Sun, 21 Oct 2012 12:36:54 -0400 (EDT)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([208.254.26.82]) by localhost (ronin.smetech.net [208.254.26.81]) (amavisd-new, port 10024) with ESMTP id GJhFZUWdj+Xa; Sun, 21 Oct 2012 12:36:42 -0400 (EDT)
Received: from [192.168.2.105] (pool-96-255-37-162.washdc.fios.verizon.net [96.255.37.162]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 5A30C9A4002; Sun, 21 Oct 2012 12:36:53 -0400 (EDT)
Subject: Re: In Memoriam IETF web page
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <50842367.3040108@dcrocker.net>
Date: Sun, 21 Oct 2012 12:36:46 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <61A98088-7151-43A1-95EE-85C327A3240C@vigilsec.com>
References: <50842367.3040108@dcrocker.net>
To: dcrocker@bbiw.net
X-Mailer: Apple Mail (2.1085)
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: Sun, 21 Oct 2012 16:36:50 -0000

I am very supportive of this idea.

Russ


On Oct 21, 2012, at 12:31 PM, Dave Crocker wrote:

> Folks,
>=20
> A thread on the nanog list, about abha ahuja, reminds me of a =
suggestion I made casually to a few folk after the last IETF meeting:
>=20
>     We should consider having a persistent IETF page in memory of =
people who were part of our community.
>=20
> While the idea is simple, the comments I got back make clear that it =
needs to be pursued carefully.  That requires some formality.
>=20
> There are two different lines of consideration. These are offered as a =
starting point for discussion:
>=20
>=20
> 1.   Who should be listed?
>=20
>     A number of different models make sense, but the challenge is =
something that is workable. For example, it does not seem like the sort =
of thing that would be appropriate for a consensus call to the =
community, for each entry.  I think that means the rules should be =
entirely mechanical.
>=20
>     Conceptually, the goal should be to include anyone who was "part =
of the IETF community".  I'll suggest that any of these would qualify:
>=20
>     a. Held a formal position in the IETF (AD, WG Chair, IAOC/Trust,
>        IAB, IRTF, Nomcom, ...are there others?)
>=20
>     b. Held a position on an IETF committee (directorate,
>        advisory, ...)
>=20
>     c. Held a position on IETF staff (IAD, RFC Editor and, I think,
>        this should include on-going contractors, including AMS and RFC
>        document editors.
>=20
>     d. RFC author
>=20
>=20
> 2.   What should be the form of the page?
>=20
>     I suggest we keep it extremely simple:  an alphabetic listing by =
name, with a photo, if available, and a pointer to a page if they have =
one.  In some cases, the IETF might formulate its own page for a person, =
but that's distinct from this basic listing.
>=20
>=20
> Thoughts?
>=20
> d/
>=20
> --=20
> Dave Crocker
> Brandenburg InternetWorking
> bbiw.net


From adrian@olddog.co.uk  Sun Oct 21 09:43:37 2012
Return-Path: <adrian@olddog.co.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B71EA21F87D9 for <ietf@ietfa.amsl.com>; Sun, 21 Oct 2012 09:43:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.887
X-Spam-Level: 
X-Spam-Status: No, score=-1.887 tagged_above=-999 required=5 tests=[AWL=0.112,  BAYES_00=-2.599, J_CHICKENPOX_23=0.6]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id am5WnB2SFRbh for <ietf@ietfa.amsl.com>; Sun, 21 Oct 2012 09:43:37 -0700 (PDT)
Received: from asmtp2.iomartmail.com (asmtp2.iomartmail.com [62.128.201.249]) by ietfa.amsl.com (Postfix) with ESMTP id C6B2E21F879B for <ietf@ietf.org>; Sun, 21 Oct 2012 09:43:36 -0700 (PDT)
Received: from asmtp2.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id q9LGhTlU001158;  Sun, 21 Oct 2012 17:43:29 +0100
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id q9LGhSxW001148 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sun, 21 Oct 2012 17:43:28 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <dcrocker@bbiw.net>, "'IETF Discussion'" <ietf@ietf.org>
References: <50842367.3040108@dcrocker.net>
In-Reply-To: <50842367.3040108@dcrocker.net>
Subject: RE: In Memoriam IETF web page
Date: Sun, 21 Oct 2012 17:43:28 +0100
Message-ID: <0c7601cdafab$32abca00$98035e00$@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: AQH5ANF8rMQcJFqOBUzUaET+9vGrSJdtU9jQ
Content-Language: en-gb
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 21 Oct 2012 16:43:37 -0000

Good idea, but suggest to go wider than your a-d and stick to:
> anyone who was "part
> of the IETF community".

In practice, that will mean, anyone who someone else thinks was a part of the
community.

It would not be seemly to squabble about whether someone had really played a
significant part in the IETF, and would be better to include anyone on request.
I think the reality is that no=one would make the request unless they felt that
the IETF had been a significant part of the deceased's life.

Cheers,
Adrian

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of Dave
> Crocker
> Sent: 21 October 2012 17:32
> To: IETF Discussion
> Subject: In Memoriam IETF web page
> 
> Folks,
> 
> A thread on the nanog list, about abha ahuja, reminds me of a suggestion
> I made casually to a few folk after the last IETF meeting:
> 
>       We should consider having a persistent IETF page in memory of
> people who were part of our community.
> 
> While the idea is simple, the comments I got back make clear that it
> needs to be pursued carefully.  That requires some formality.
> 
> There are two different lines of consideration. These are offered as a
> starting point for discussion:
> 
> 
> 1.   Who should be listed?
> 
>       A number of different models make sense, but the challenge is
> something that is workable. For example, it does not seem like the sort
> of thing that would be appropriate for a consensus call to the
> community, for each entry.  I think that means the rules should be
> entirely mechanical.
> 
>       Conceptually, the goal should be to include anyone who was "part
> of the IETF community".  I'll suggest that any of these would qualify:
> 
>       a. Held a formal position in the IETF (AD, WG Chair, IAOC/Trust,
>          IAB, IRTF, Nomcom, ...are there others?)
> 
>       b. Held a position on an IETF committee (directorate,
>          advisory, ...)
> 
>       c. Held a position on IETF staff (IAD, RFC Editor and, I think,
>          this should include on-going contractors, including AMS and RFC
>          document editors.
> 
>       d. RFC author
> 
> 
> 2.   What should be the form of the page?
> 
>       I suggest we keep it extremely simple:  an alphabetic listing by
> name, with a photo, if available, and a pointer to a page if they have
> one.  In some cases, the IETF might formulate its own page for a person,
> but that's distinct from this basic listing.
> 
> 
> Thoughts?
> 
> d/
> 
> --
>   Dave Crocker
>   Brandenburg InternetWorking
>   bbiw.net


From bensons@queuefull.net  Sun Oct 21 10:10:00 2012
Return-Path: <bensons@queuefull.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3779C21F86E1 for <ietf@ietfa.amsl.com>; Sun, 21 Oct 2012 10:10:00 -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, J_CHICKENPOX_23=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cu5CndL0G4mf for <ietf@ietfa.amsl.com>; Sun, 21 Oct 2012 10:09:59 -0700 (PDT)
Received: from mail-vc0-f172.google.com (mail-vc0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 507A121F8464 for <ietf@ietf.org>; Sun, 21 Oct 2012 10:09:59 -0700 (PDT)
Received: by mail-vc0-f172.google.com with SMTP id fl11so2371725vcb.31 for <ietf@ietf.org>; Sun, 21 Oct 2012 10:09:58 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding :x-gm-message-state; bh=qfMhPByMZIjBjh5bIVj1Hi+EvQ8TM4rZZN87uNn0H+k=; b=LF/XDYMbGuesk1JojpQQ/tS0AZLqNX/aZ8Qk5ulx4dlbEctRICEl2aNfv1yYctYQ0s m82Uo1fymIBvD9/inh8Pp728OHe+8/8CV0hh42iMI4qC5MClh1rW37ljPyiB1VuwF4eO ph5Y+OoymdL7hGD+aqf3pRZ/XdIJpHgpMWEkVA0w/4nsX7zFamo0nri6jpVa1gw0fCfv kODcQsGlTBESyjmd6WyzolcvsFRXMTLrpIi/d1rw6o3VwRjxMz0b2YCZWxSP1zlswkZt 8a5qwh7aLSINnJXJ5O6rJsxU/iKcgN3ClWZrr6U8UH5+qkxA5F7x1yX3D3laQGxejhfS Vn1g==
Received: by 10.52.29.233 with SMTP id n9mr8727191vdh.30.1350839398721; Sun, 21 Oct 2012 10:09:58 -0700 (PDT)
Received: from wasteland.local (westford-nat.juniper.net. [66.129.232.2]) by mx.google.com with ESMTPS id vl8sm7315595veb.9.2012.10.21.10.09.57 (version=SSLv3 cipher=OTHER); Sun, 21 Oct 2012 10:09:58 -0700 (PDT)
Message-ID: <50842C69.9080407@queuefull.net>
Date: Sun, 21 Oct 2012 12:10:01 -0500
From: Benson Schliesser <bensons@queuefull.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:16.0) Gecko/20121010 Thunderbird/16.0.1
MIME-Version: 1.0
To: adrian@olddog.co.uk, dcrocker@bbiw.net
Subject: Re: In Memoriam IETF web page
References: <50842367.3040108@dcrocker.net> <0c7601cdafab$32abca00$98035e00$@olddog.co.uk>
In-Reply-To: <0c7601cdafab$32abca00$98035e00$@olddog.co.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Gm-Message-State: ALoCoQm6tgwR95WikK9bjg68RNNciDvnb6KHq0tJbGbVwfGyDX/5E7aT68c4VVSSlBkC6lslBWoN
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: Sun, 21 Oct 2012 17:10:00 -0000

I feel a little bad saying this, because these individuals deserve 
recognition. But I rather think this memorial page is not a good idea.

If the IETF is around long enough, eventually all members of the 
community will die. (Unless medical science makes some amazing 
achievements, I suppose...) It's easy today to recognize a few people 
that made large contributions earlier in the IETF's history. But at some 
point the list will grow large, until it has lost its significance. And 
yet, at that point, it may be unseemly to stop the tradition, and even 
more unseemly to delete the existing memorial.

I don't want to be insensitive, and I'm sorry to point this out. But I 
think we're better off with heart-felt, personal memorials from living 
people that remember and care about the departed.

-Benson


On 10/21/12 11:43 AM, Adrian Farrel wrote:
> Good idea, but suggest to go wider than your a-d and stick to:
>> anyone who was "part
>> of the IETF community".
> In practice, that will mean, anyone who someone else thinks was a part of the
> community.
>
> It would not be seemly to squabble about whether someone had really played a
> significant part in the IETF, and would be better to include anyone on request.
> I think the reality is that no=one would make the request unless they felt that
> the IETF had been a significant part of the deceased's life.
>
> Cheers,
> Adrian
>
>> -----Original Message-----
>> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of Dave
>> Crocker
>> Sent: 21 October 2012 17:32
>> To: IETF Discussion
>> Subject: In Memoriam IETF web page
>>
>> Folks,
>>
>> A thread on the nanog list, about abha ahuja, reminds me of a suggestion
>> I made casually to a few folk after the last IETF meeting:
>>
>>        We should consider having a persistent IETF page in memory of
>> people who were part of our community.
>>
>> While the idea is simple, the comments I got back make clear that it
>> needs to be pursued carefully.  That requires some formality.
>>
>> There are two different lines of consideration. These are offered as a
>> starting point for discussion:
>>
>>
>> 1.   Who should be listed?
>>
>>        A number of different models make sense, but the challenge is
>> something that is workable. For example, it does not seem like the sort
>> of thing that would be appropriate for a consensus call to the
>> community, for each entry.  I think that means the rules should be
>> entirely mechanical.
>>
>>        Conceptually, the goal should be to include anyone who was "part
>> of the IETF community".  I'll suggest that any of these would qualify:
>>
>>        a. Held a formal position in the IETF (AD, WG Chair, IAOC/Trust,
>>           IAB, IRTF, Nomcom, ...are there others?)
>>
>>        b. Held a position on an IETF committee (directorate,
>>           advisory, ...)
>>
>>        c. Held a position on IETF staff (IAD, RFC Editor and, I think,
>>           this should include on-going contractors, including AMS and RFC
>>           document editors.
>>
>>        d. RFC author
>>
>>
>> 2.   What should be the form of the page?
>>
>>        I suggest we keep it extremely simple:  an alphabetic listing by
>> name, with a photo, if available, and a pointer to a page if they have
>> one.  In some cases, the IETF might formulate its own page for a person,
>> but that's distinct from this basic listing.
>>
>>
>> Thoughts?
>>
>> d/
>>
>> --
>>    Dave Crocker
>>    Brandenburg InternetWorking
>>    bbiw.net


From john-ietf@jck.com  Sun Oct 21 11:55:48 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 EB83A21F89D2 for <ietf@ietfa.amsl.com>; Sun, 21 Oct 2012 11:55:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.23
X-Spam-Level: 
X-Spam-Status: No, score=-102.23 tagged_above=-999 required=5 tests=[AWL=-0.231, BAYES_00=-2.599, J_CHICKENPOX_23=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KGf9x5yX4hcN for <ietf@ietfa.amsl.com>; Sun, 21 Oct 2012 11:55:48 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 7754021F8911 for <ietf@ietf.org>; Sun, 21 Oct 2012 11:55:48 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1TQ0ga-0006ej-KH; Sun, 21 Oct 2012 14:55:44 -0400
Date: Sun, 21 Oct 2012 14:55:40 -0400
From: John C Klensin <john-ietf@jck.com>
To: adrian@olddog.co.uk, 'IETF Discussion' <ietf@ietf.org>
Subject: RE: In Memoriam IETF web page
Message-ID: <E0D759CB97DC2AD27C86BA7D@JcK-HP8200.jck.com>
In-Reply-To: <0c7601cdafab$32abca00$98035e00$@olddog.co.uk>
References: <50842367.3040108@dcrocker.net> <0c7601cdafab$32abca00$98035e00$@olddog.co.uk>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 21 Oct 2012 18:55:49 -0000

--On Sunday, October 21, 2012 17:43 +0100 Adrian Farrel
<adrian@olddog.co.uk> wrote:

> In practice, that will mean, anyone who someone else thinks
> was a part of the community.
> 
> It would not be seemly to squabble about whether someone had
> really played a significant part in the IETF, and would be
> better to include anyone on request. I think the reality is
> that no=one would make the request unless they felt that the
> IETF had been a significant part of the deceased's life.

By itself, that would risk losing anyone who met one of Dave's
criteria but for "someone" didn't think to tell us.   So, while
I tend to agree with you, partially because there have been
people with significant impact on the IETF who don't meet any of
Dave's criteria, I think it maybe ought to be Dave's list plus
anyone for whom there is a request, rather than either-or.  I
note in particular that there are a number of people whom I
think had a significant impact on the IETF and on how we shaped
various protocols but who never attended a meeting, including,
e.g., a few late ITU-T Directors and ITU SGs and a few folks the
community often dismisses as loonies.

At the same time, I agree with Benson that such a list could
approach silliness and be impossible to stop.

   john


From dmm@1-4-5.net  Sun Oct 21 12:00:31 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 428CC21F8A12 for <ietf@ietfa.amsl.com>; Sun, 21 Oct 2012 12:00:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.677
X-Spam-Level: 
X-Spam-Status: No, score=-2.677 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, J_CHICKENPOX_23=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3XmtEeKM4-CO for <ietf@ietfa.amsl.com>; Sun, 21 Oct 2012 12:00:30 -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 803E021F89EB for <ietf@ietf.org>; Sun, 21 Oct 2012 12:00:30 -0700 (PDT)
Received: by mail-ob0-f172.google.com with SMTP id v19so2229123obq.31 for <ietf@ietf.org>; Sun, 21 Oct 2012 12:00:21 -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:x-gm-message-state; bh=plHBtjwfeqd/Shmcem3XrZfW1TUmoWX3HVyRnLLp5hw=; b=cl3yTb9MXifmj26J1NcpdnLiVXm9GR4DHRIoKM11eBiMUAFu/zFSQ0Silp8i3v37Sk z8dhxf7Vb3WbxeC1XGc/BwOrGe793xIazHGL6VYxHCQzGfoH1vHjBZu1f3lmQ1FzgmUH u0Ayc3IVnNFyzBOtl6dhHOUL2geKtIIb4CC412sVlfXfyE63dXZ8PJX/4eHMA/UaBAoU vyVY+oxaT0dOl58B7DqpTYP6b8iJeluIPYeGr3zEYhaoMFvrxTFZegWJARHEh+p6oJ4Y GsGgR+2VOUGrSKOiuXF18wA3OSMM7UK+vGK3cZiA/JC6qn14DFJAU5FTBUo8HHIvxqoR OAGw==
MIME-Version: 1.0
Received: by 10.182.177.100 with SMTP id cp4mr5374250obc.71.1350846021135; Sun, 21 Oct 2012 12:00:21 -0700 (PDT)
Received: by 10.76.130.44 with HTTP; Sun, 21 Oct 2012 12:00:21 -0700 (PDT)
X-Originating-IP: [208.46.205.10]
In-Reply-To: <50842C69.9080407@queuefull.net>
References: <50842367.3040108@dcrocker.net> <0c7601cdafab$32abca00$98035e00$@olddog.co.uk> <50842C69.9080407@queuefull.net>
Date: Sun, 21 Oct 2012 12:00:21 -0700
Message-ID: <CAHiKxWiN7v9bW0dQNrhOsuS8EPC2xUMnaJtwxhRntM6NT0fO+A@mail.gmail.com>
Subject: Re: In Memoriam IETF web page
From: David Meyer <dmm@1-4-5.net>
To: Benson Schliesser <bensons@queuefull.net>
Content-Type: text/plain; charset=ISO-8859-1
X-Gm-Message-State: ALoCoQnVbbgiP5nqbgXS7+QeC1Mp9j4tR2B5BvpHDmECCWdKkLaHVSXjT+GTSVoC6L7KKzU2Dm1x
Cc: adrian@olddog.co.uk, dcrocker@bbiw.net, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 21 Oct 2012 19:00:31 -0000

While I applaud the idea, I have to agree with Benson here. --dmm

On Sun, Oct 21, 2012 at 10:10 AM, Benson Schliesser
<bensons@queuefull.net> wrote:
> I feel a little bad saying this, because these individuals deserve
> recognition. But I rather think this memorial page is not a good idea.
>
> If the IETF is around long enough, eventually all members of the community
> will die. (Unless medical science makes some amazing achievements, I
> suppose...) It's easy today to recognize a few people that made large
> contributions earlier in the IETF's history. But at some point the list will
> grow large, until it has lost its significance. And yet, at that point, it
> may be unseemly to stop the tradition, and even more unseemly to delete the
> existing memorial.
>
> I don't want to be insensitive, and I'm sorry to point this out. But I think
> we're better off with heart-felt, personal memorials from living people that
> remember and care about the departed.
>
> -Benson
>
>
>
> On 10/21/12 11:43 AM, Adrian Farrel wrote:
>>
>> Good idea, but suggest to go wider than your a-d and stick to:
>>>
>>> anyone who was "part
>>> of the IETF community".
>>
>> In practice, that will mean, anyone who someone else thinks was a part of
>> the
>> community.
>>
>> It would not be seemly to squabble about whether someone had really played
>> a
>> significant part in the IETF, and would be better to include anyone on
>> request.
>> I think the reality is that no=one would make the request unless they felt
>> that
>> the IETF had been a significant part of the deceased's life.
>>
>> Cheers,
>> Adrian
>>
>>> -----Original Message-----
>>> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
>>> Dave
>>> Crocker
>>> Sent: 21 October 2012 17:32
>>> To: IETF Discussion
>>> Subject: In Memoriam IETF web page
>>>
>>> Folks,
>>>
>>> A thread on the nanog list, about abha ahuja, reminds me of a suggestion
>>> I made casually to a few folk after the last IETF meeting:
>>>
>>>        We should consider having a persistent IETF page in memory of
>>> people who were part of our community.
>>>
>>> While the idea is simple, the comments I got back make clear that it
>>> needs to be pursued carefully.  That requires some formality.
>>>
>>> There are two different lines of consideration. These are offered as a
>>> starting point for discussion:
>>>
>>>
>>> 1.   Who should be listed?
>>>
>>>        A number of different models make sense, but the challenge is
>>> something that is workable. For example, it does not seem like the sort
>>> of thing that would be appropriate for a consensus call to the
>>> community, for each entry.  I think that means the rules should be
>>> entirely mechanical.
>>>
>>>        Conceptually, the goal should be to include anyone who was "part
>>> of the IETF community".  I'll suggest that any of these would qualify:
>>>
>>>        a. Held a formal position in the IETF (AD, WG Chair, IAOC/Trust,
>>>           IAB, IRTF, Nomcom, ...are there others?)
>>>
>>>        b. Held a position on an IETF committee (directorate,
>>>           advisory, ...)
>>>
>>>        c. Held a position on IETF staff (IAD, RFC Editor and, I think,
>>>           this should include on-going contractors, including AMS and RFC
>>>           document editors.
>>>
>>>        d. RFC author
>>>
>>>
>>> 2.   What should be the form of the page?
>>>
>>>        I suggest we keep it extremely simple:  an alphabetic listing by
>>> name, with a photo, if available, and a pointer to a page if they have
>>> one.  In some cases, the IETF might formulate its own page for a person,
>>> but that's distinct from this basic listing.
>>>
>>>
>>> Thoughts?
>>>
>>> d/
>>>
>>> --
>>>    Dave Crocker
>>>    Brandenburg InternetWorking
>>>    bbiw.net
>
>

From randy@psg.com  Sun Oct 21 13:59:13 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 CEE6721F85B6 for <ietf@ietfa.amsl.com>; Sun, 21 Oct 2012 13:59:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.469
X-Spam-Level: 
X-Spam-Status: No, score=-2.469 tagged_above=-999 required=5 tests=[AWL=0.130,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MTlR8EdvzaO7 for <ietf@ietfa.amsl.com>; Sun, 21 Oct 2012 13:59:13 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 8175721F8695 for <ietf@ietf.org>; Sun, 21 Oct 2012 13:59:13 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=rair.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.80 (FreeBSD)) (envelope-from <randy@psg.com>) id 1TQ2c4-000DE3-5s; Sun, 21 Oct 2012 20:59:12 +0000
Date: Sun, 21 Oct 2012 15:59:11 -0500
Message-ID: <m2hapn35k0.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Russ Housley <housley@vigilsec.com>
Subject: Re: In Memoriam IETF web page
In-Reply-To: <61A98088-7151-43A1-95EE-85C327A3240C@vigilsec.com>
References: <50842367.3040108@dcrocker.net> <61A98088-7151-43A1-95EE-85C327A3240C@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.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 21 Oct 2012 20:59:13 -0000

i started the thread on nanog.  i am not sure abha or jon would want to
be on such a list.  remember them and honor and carry on their work,
don't memorialize them.

randy

From paul.hoffman@vpnc.org  Sun Oct 21 16:09:52 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 C62C821F8A16 for <ietf@ietfa.amsl.com>; Sun, 21 Oct 2012 16:09:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.597
X-Spam-Level: 
X-Spam-Status: No, score=-102.597 tagged_above=-999 required=5 tests=[AWL=0.002, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fQnjwp87zIQY for <ietf@ietfa.amsl.com>; Sun, 21 Oct 2012 16:09:52 -0700 (PDT)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id 5195D21F8A12 for <ietf@ietf.org>; Sun, 21 Oct 2012 16:09:52 -0700 (PDT)
Received: from [10.20.30.101] (50-1-50-97.dsl.dynamic.fusionbroadband.com [50.1.50.97]) (authenticated bits=0) by hoffman.proper.com (8.14.5/8.14.5) with ESMTP id q9LN9ktp078098 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <ietf@ietf.org>; Sun, 21 Oct 2012 16:09:47 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: In Memoriam IETF web page
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <m2hapn35k0.wl%randy@psg.com>
Date: Sun, 21 Oct 2012 16:09:46 -0700
Content-Transfer-Encoding: 7bit
Message-Id: <600EE061-F61A-4147-8747-6FBE82F146FD@vpnc.org>
References: <50842367.3040108@dcrocker.net> <61A98088-7151-43A1-95EE-85C327A3240C@vigilsec.com> <m2hapn35k0.wl%randy@psg.com>
To: IETF Discussion <ietf@ietf.org>
X-Mailer: Apple Mail (2.1499)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 21 Oct 2012 23:09:52 -0000

On Oct 21, 2012, at 1:59 PM, Randy Bush <randy@psg.com> wrote:

> i started the thread on nanog.  i am not sure abha or jon would want to
> be on such a list.  remember them and honor and carry on their work,
> don't memorialize them.

+1


From hartmans@mit.edu  Sun Oct 21 19:11:13 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 1D36421F8AAB for <ietf@ietfa.amsl.com>; Sun, 21 Oct 2012 19:11:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.063
X-Spam-Level: 
X-Spam-Status: No, score=-100.063 tagged_above=-999 required=5 tests=[AWL=2.536, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oBWRwJ6MjcRR for <ietf@ietfa.amsl.com>; Sun, 21 Oct 2012 19:11:12 -0700 (PDT)
Received: from mail.painless-security.com (mail.painless-security.com [23.30.188.241]) by ietfa.amsl.com (Postfix) with ESMTP id 985F421F8A9C for <ietf@ietf.org>; Sun, 21 Oct 2012 19:11:10 -0700 (PDT)
Received: from carter-zimmerman.suchdamage.org (c-98-217-126-210.hsd1.ma.comcast.net [98.217.126.210]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.painless-security.com (Postfix) with ESMTPS id 8107720115; Sun, 21 Oct 2012 22:10:49 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id C18634AD5; Sun, 21 Oct 2012 22:11:06 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: dcrocker@bbiw.net
Subject: Re: In Memoriam IETF web page
References: <50842367.3040108@dcrocker.net>
Date: Sun, 21 Oct 2012 22:11:06 -0400
In-Reply-To: <50842367.3040108@dcrocker.net> (Dave Crocker's message of "Sun,  21 Oct 2012 12:31:35 -0400")
Message-ID: <tslfw578ddx.fsf@mit.edu>
User-Agent: Gnus/5.110009 (No Gnus v0.9) Emacs/22.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Oct 2012 02:11:13 -0000

I'm supportive of ideas in this space.
I agree with Adrian that it would be far better to include someone that
some people don't recognize as influencing the community than to ever
get into an argument about excluding someone.
I am happy if others work out the details and trust to the community to
come up with something reasonable.

From turchanyi.geza@gmail.com  Sun Oct 21 23:28:20 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 9BCCD21F8B92 for <ietf@ietfa.amsl.com>; Sun, 21 Oct 2012 23:28:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id StZHOfKUi6aK for <ietf@ietfa.amsl.com>; Sun, 21 Oct 2012 23:28:20 -0700 (PDT)
Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id 34C5521F8B75 for <ietf@ietf.org>; Sun, 21 Oct 2012 23:28:20 -0700 (PDT)
Received: by mail-pb0-f44.google.com with SMTP id ro8so1753166pbb.31 for <ietf@ietf.org>; Sun, 21 Oct 2012 23:28:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=supGZodGSsfY89BU2xWAmnB25Rdl8hCKdsbvjzxlf+c=; b=Bd4cOzdKDrUs/kTFYT6s/7TaHeKycEdGtVG8KEKB3TTSY/VCAsOb4IAvn67hgdhbCJ pqT5SZeoft69lL3zHPQt4g6h9zj543M7nYR6vXAK6LUzf6HTQnAduXbWcQ7mjwVNR80f f/Tn2dMobNxldDUbPCGm7cIFp/K/QypWijhypujWJJtCwZHjchz2nwVLUHv7liQJrhbj Vjr+6b5D/8AbX/2Yt6Dhwcx2ztQfmPzbkVpIrjcjyCHtJfHzBXUeRU1izsklbJHsB2qh 46dVTj2uIaS5W2jHil4CLY22Zy3mO2WaH7DUV7nIpOW5RMxQMfvycCwjQ0pRrrFwRNXx k+Wg==
MIME-Version: 1.0
Received: by 10.66.80.133 with SMTP id r5mr23690182pax.24.1350887299906; Sun, 21 Oct 2012 23:28:19 -0700 (PDT)
Received: by 10.66.19.135 with HTTP; Sun, 21 Oct 2012 23:28:19 -0700 (PDT)
In-Reply-To: <m2hapn35k0.wl%randy@psg.com>
References: <50842367.3040108@dcrocker.net> <61A98088-7151-43A1-95EE-85C327A3240C@vigilsec.com> <m2hapn35k0.wl%randy@psg.com>
Date: Mon, 22 Oct 2012 08:28:19 +0200
Message-ID: <CAJfR-+OLgDve7T9-oULEKvQUHpRY_8gxj6gNtr1y0fxbTmyuBA@mail.gmail.com>
Subject: Re: In Memoriam IETF web page
From: Turchanyi Geza <turchanyi.geza@gmail.com>
To: Randy Bush <randy@psg.com>
Content-Type: multipart/alternative; boundary=f46d042ef671a47ad904cc9ff5a1
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Oct 2012 06:28:20 -0000

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

Randy,

On Sun, Oct 21, 2012 at 10:59 PM, Randy Bush <randy@psg.com> wrote:

> i started the thread on nanog.  i am not sure abha or jon would want to
> be on such a list.  remember them and honor and carry on their work,
> don't memorialize them.
>

I fully agree with you. However, unfortunately, a few years later some
people might not know that you meant Jon Postel, saying simple: Jon...

It is also a good question, who should write an "official" memorial page.
And, who should not.

 Any book about the heroes of the Internet would keep their memories. In
any language.
Mentioning just one conventional medium: book.



> randy
>

G=E9za

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

Randy,<br><br><div class=3D"gmail_quote">On Sun, Oct 21, 2012 at 10:59 PM, =
Randy Bush <span dir=3D"ltr">&lt;<a href=3D"mailto:randy@psg.com" target=3D=
"_blank">randy@psg.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_=
quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1=
ex">
i started the thread on nanog. =A0i am not sure abha or jon would want to<b=
r>
be on such a list. =A0remember them and honor and carry on their work,<br>
don&#39;t memorialize them.<br></blockquote><div><br>I fully agree with you=
. However, unfortunately, a few years later some people might not know that=
 you meant Jon Postel, saying simple: Jon...<br><br>It is also a good quest=
ion, who should write an &quot;official&quot; memorial page. And, who shoul=
d not.<br>
<br>=A0Any book about the heroes of the Internet would keep their memories.=
 In any language.<br>Mentioning just one conventional medium: book. <br><br=
><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bor=
der-left:1px #ccc solid;padding-left:1ex">

<span class=3D"HOEnZb"><font color=3D"#888888"><br>
randy<br>
</font></span></blockquote></div><br>G=E9za<br>

--f46d042ef671a47ad904cc9ff5a1--

From dhc@dcrocker.net  Mon Oct 22 04:35:37 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 44E3D21F8A10 for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 04:35:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8-3utaxYhpSn for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 04:35:36 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 9E58221F897D for <ietf@ietf.org>; Mon, 22 Oct 2012 04:35:36 -0700 (PDT)
Received: from [192.168.11.199] (ip-64-134-97-182.public.wayport.net [64.134.97.182]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q9MBZZe4001625 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <ietf@ietf.org>; Mon, 22 Oct 2012 04:35:36 -0700
Message-ID: <50852F80.5040605@dcrocker.net>
Date: Mon, 22 Oct 2012 07:35:28 -0400
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121010 Thunderbird/16.0.1
MIME-Version: 1.0
To: "'IETF Discussion'" <ietf@ietf.org>
Subject: Re: In Memoriam IETF web page
References: <50842367.3040108@dcrocker.net> <0c7601cdafab$32abca00$98035e00$@olddog.co.uk> <E0D759CB97DC2AD27C86BA7D@JcK-HP8200.jck.com>
In-Reply-To: <E0D759CB97DC2AD27C86BA7D@JcK-HP8200.jck.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Mon, 22 Oct 2012 04:35:36 -0700 (PDT)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Oct 2012 11:35:37 -0000

Folks,

Some follow-up to various postings.

We have long-established a pattern of taking a moment at IETF Plenaries 
to note a community loss.  My feeling is that something of this sort, 
which is worth doing in a plenary, is worth recording for longer term. 
Our world is increasingly ephemeral; this is one small way of improving 
our community memory.  I don't pretend to know what a potential listee 
might want, even for those I might know, or have known, well, but I'll 
note that most people do not turn down community recognition.  Jon 
didn't; Randy hasn't.

The real challenge is to formulate something both seemly in tone and 
workable for the long term.  Concern about the eventual size of the list 
is particularly apt, for a community that has sometimes been 
characterized as having the primary technical and operations task of 
worrying about scaling.  Indeed, scaling is part of the reason I 
suggested keeping the basic page so simple.  As for the list's 
eventually having thousands of names on it, I think that will be 
something to be proud of, not concerned about.

As for the selection criteria, it is certainly appealing to consider a 
more flexible and personal means of nominating folk.  The reason I 
suggested an entirely objective qualification mechanism is that the 
alternatives create some difficult, on-going challenges:  the process of 
nominating and approving will be quite easy for some/many/most, but not 
for all.  As an example, how will we feel about having the list contain 
the names of sockpuppets that have been active in the IETF?

Whatever criteria and process we choose, I suggest that they be simple 
and straightforward, avoiding the opportunity for debate about 
particular listings.

d/

-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From jnc@mercury.lcs.mit.edu  Mon Oct 22 06:01: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 8A7FE21F8B76 for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 06:01:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.545
X-Spam-Level: 
X-Spam-Status: No, score=-5.545 tagged_above=-999 required=5 tests=[AWL=-0.805, BAYES_20=-0.74, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DzOtlgFiLAbA for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 06:01: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 AC93121F8B79 for <ietf@ietf.org>; Mon, 22 Oct 2012 06:01:31 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id E5AF218C0B7; Mon, 22 Oct 2012 09:01:29 -0400 (EDT)
To: ietf@ietf.org
Subject: Re: In Memoriam IETF web page
Message-Id: <20121022130129.E5AF218C0B7@mercury.lcs.mit.edu>
Date: Mon, 22 Oct 2012 09:01:29 -0400 (EDT)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: jnc@mercury.lcs.mit.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Oct 2012 13:01:33 -0000

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

    > i am not sure abha or jon would want to be on such a list. remember
    > them and honor and carry on their work, don't memorialize them.

I hear you, but I am also mindful of human nature - and people often
(usually?) tend to be startlingly non-conversant with history they didn't
live through. In other words, if we don't do something to inform people of
people like Jon and Abha, people coming in now _won't_ remember them.

I myself am a perfect example of this. When I started, I had for a year (or
more, I don't recall exactly) an office two doors down from J.C.R. Licklider.
Alas, I never got to know him - because I had no idea who he was. (This, to
me, is akin to a young physicist having an office next door to Einstein, but
not knowing who he was. Startling, but it really happened.) The thing is that
nobody ever told me who he was, or what he had done, so as a result I had no
idea I might want to take time out of my focus on doing stuff in order to pay
attention to this person.

So I think some memorialization of significant people who are no longer with
us is warranted. Maybe an 'IETF Hall of Fame', to which each year we can add
significant contributors whom we've lost, or something like that? And the Tao
could point to it.

	Noel

From rpelletier@isoc.org  Mon Oct 22 06:27:00 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 3A22221F8549 for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 06:27:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.597
X-Spam-Level: 
X-Spam-Status: No, score=-103.597 tagged_above=-999 required=5 tests=[AWL=0.002, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UDe8iVjkdgWb for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 06:26:59 -0700 (PDT)
Received: from smtp187.iad.emailsrvr.com (smtp187.iad.emailsrvr.com [207.97.245.187]) by ietfa.amsl.com (Postfix) with ESMTP id 48F9821F8530 for <ietf@ietf.org>; Mon, 22 Oct 2012 06:26:59 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp58.relay.iad1a.emailsrvr.com (SMTP Server) with ESMTP id A4A16308A4C; Mon, 22 Oct 2012 09:26:58 -0400 (EDT)
X-Virus-Scanned: OK
Received: by smtp58.relay.iad1a.emailsrvr.com (Authenticated sender: rpelletier-AT-isoc.org) with ESMTPSA id 7F870308882;  Mon, 22 Oct 2012 09:26:58 -0400 (EDT)
Subject: Re: In Memoriam IETF web page
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: Pelletier Ray <rpelletier@isoc.org>
In-Reply-To: <m2hapn35k0.wl%randy@psg.com>
Date: Mon, 22 Oct 2012 09:26:58 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <12D99082-7020-42CF-BA94-A7D683587CBA@isoc.org>
References: <50842367.3040108@dcrocker.net> <61A98088-7151-43A1-95EE-85C327A3240C@vigilsec.com> <m2hapn35k0.wl%randy@psg.com>
To: Randy Bush <randy@psg.com>
X-Mailer: Apple Mail (2.1085)
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Oct 2012 13:27:00 -0000

On Oct 21, 2012, at 4:59 PM, Randy Bush wrote:

> i started the thread on nanog.  i am not sure abha or jon would want =
to
> be on such a list.  remember them and honor and carry on their work,
> don't memorialize them.

With all respect, it is not just about the person, it is about their =
work, its importance, the history of this Internet and providing role =
models to others.

Ray


>=20
> randy


From swb@internet2.edu  Mon Oct 22 06:36:58 2012
Return-Path: <swb@internet2.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B46EA21F8BBC for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 06:36:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WGG6ZFwgjX2z for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 06:36:58 -0700 (PDT)
Received: from int-proxy02.merit.edu (int-proxy02.merit.edu [207.75.116.231]) by ietfa.amsl.com (Postfix) with ESMTP id 0D55A21F8BC9 for <ietf@ietf.org>; Mon, 22 Oct 2012 06:36:58 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by int-proxy02.merit.edu (Postfix) with ESMTP id 89BE6120413; Mon, 22 Oct 2012 09:36:57 -0400 (EDT)
X-Virus-Scanned: amavisd-new at int-proxy02.merit.edu
Received: from int-proxy02.merit.edu ([127.0.0.1]) by localhost (int-proxy02.merit.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zgTUPvCsesbz; Mon, 22 Oct 2012 09:36:57 -0400 (EDT)
Received: from swbi2mbp.local (cpe-67-241-75-185.twcny.res.rr.com [67.241.75.185]) by int-proxy02.merit.edu (Postfix) with ESMTPSA id DFBF2120446; Mon, 22 Oct 2012 09:36:55 -0400 (EDT)
Message-ID: <50854BF5.5000409@internet2.edu>
Date: Mon, 22 Oct 2012 09:36:53 -0400
From: Scott Brim <swb@internet2.edu>
Organization: Internet2
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:16.0) Gecko/20121010 Thunderbird/16.0.1
MIME-Version: 1.0
To: Pelletier Ray <rpelletier@isoc.org>
Subject: Re: In Memoriam IETF web page
References: <50842367.3040108@dcrocker.net> <61A98088-7151-43A1-95EE-85C327A3240C@vigilsec.com> <m2hapn35k0.wl%randy@psg.com> <12D99082-7020-42CF-BA94-A7D683587CBA@isoc.org>
In-Reply-To: <12D99082-7020-42CF-BA94-A7D683587CBA@isoc.org>
X-Enigmail-Version: 1.4.5
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Oct 2012 13:36:58 -0000

If this memorial wiki page could be open to anyone who ever contributed
to any I* and for whom there was at least one person who wanted to
contribute the information, then fine.  If not, then it would be yet
another situation where there will be a line between the in-crowd and
the out-crowd.  There's plenty of implicit elitism and idol worship in
the IETF, and I wouldn't want to cultivate it more.

Scott

From ajs@anvilwalrusden.com  Mon Oct 22 07:42:42 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 E25CC21F8B8B for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 07:42:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.84
X-Spam-Level: 
X-Spam-Status: No, score=-0.84 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qxKA1hhri-x0 for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 07:42:42 -0700 (PDT)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id 75B4421F8B81 for <ietf@ietf.org>; Mon, 22 Oct 2012 07:42:42 -0700 (PDT)
Received: from mx1.yitter.info (dhcp-222-230.meetings.nanog.org [199.187.222.230]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id 2316E8A031 for <ietf@ietf.org>; Mon, 22 Oct 2012 14:42:40 +0000 (UTC)
Date: Mon, 22 Oct 2012 10:42:27 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: Re: In Memoriam IETF web page
Message-ID: <20121022144227.GB50381@mx1.yitter.info>
References: <50842367.3040108@dcrocker.net> <0c7601cdafab$32abca00$98035e00$@olddog.co.uk> <E0D759CB97DC2AD27C86BA7D@JcK-HP8200.jck.com> <50852F80.5040605@dcrocker.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <50852F80.5040605@dcrocker.net>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Oct 2012 14:42:43 -0000

On Mon, Oct 22, 2012 at 07:35:28AM -0400, Dave Crocker wrote:
> some/many/most, but not for all.  As an example, how will we feel
> about having the list contain the names of sockpuppets that have
> been active in the IETF?

This question nicely identifies why the proposal makes me so
uncomfortable, and why I don't think I can support it, however much I
think there are contributors worth remembering.  

The question assumes that there is an easy way to identify the "we" of
"how will we feel", not to mention an easy way to tell who is a
sockpuppet.  Each of us doubtless has perfectly useful and effective
ways of making such identifications, but I doubt they'll be the same
for everyone.  

Because of that, at the beginning it would probably be pretty easy to
decide who'd be on the list.  In a few years, however, there'll be a
case where there are hard feelings about inclusion or non-inclusion of
someone.  (Anyone who thinks we are going to make "purely objective"
criteria and then stick to them is just dreaming.  We can't even do
that when bits on the wire are involved.)  That will inevitably result
in a small bit of process, or an appeal route, or something, and we'll
be off on yet another attempt to write perfectly balanced procedures
to ensure The Right Result comes out.  Those will be more cycles that
are spent on process rather than getting work done.

Obviously, if someone wants to set up the network memorial pages
(unaffiliated with the IETF), I can't see anything wrong with it.  I
just don't think it's an IETF activity.  

Best,
A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

From paul.hoffman@vpnc.org  Mon Oct 22 07:43:15 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 D92C721F8BAF for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 07:43:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.597
X-Spam-Level: 
X-Spam-Status: No, score=-102.597 tagged_above=-999 required=5 tests=[AWL=0.002, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sCQxuoZjNo+4 for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 07:43:15 -0700 (PDT)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id 718CC21F8BBA for <ietf@ietf.org>; Mon, 22 Oct 2012 07:43:13 -0700 (PDT)
Received: from [10.20.30.101] (50-1-50-97.dsl.dynamic.fusionbroadband.com [50.1.50.97]) (authenticated bits=0) by hoffman.proper.com (8.14.5/8.14.5) with ESMTP id q9MEhB4I006409 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 22 Oct 2012 07:43:12 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: In Memoriam IETF web page
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <12D99082-7020-42CF-BA94-A7D683587CBA@isoc.org>
Date: Mon, 22 Oct 2012 07:43:12 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <83F2CC9B-60A2-4DA8-8217-642E2090D6B4@vpnc.org>
References: <50842367.3040108@dcrocker.net> <61A98088-7151-43A1-95EE-85C327A3240C@vigilsec.com> <m2hapn35k0.wl%randy@psg.com> <12D99082-7020-42CF-BA94-A7D683587CBA@isoc.org>
To: Pelletier Ray <rpelletier@isoc.org>
X-Mailer: Apple Mail (2.1499)
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Oct 2012 14:43:16 -0000

On Oct 22, 2012, at 6:26 AM, Pelletier Ray <rpelletier@isoc.org> wrote:

>=20
> On Oct 21, 2012, at 4:59 PM, Randy Bush wrote:
>=20
>> i started the thread on nanog.  i am not sure abha or jon would want =
to
>> be on such a list.  remember them and honor and carry on their work,
>> don't memorialize them.
>=20
> With all respect, it is not just about the person, it is about their =
work, its importance, the history of this Internet and providing role =
models to others.

And who gets to decide which "work" is worth putting in the memorial?

In the older case of Jon Postel, there are some things he did that =
pissed off some IETFers but made others quite happy. In at least one =
case, I believe that people representing both groups are still around =
and would want to "help" create the official IETF page for Jon.

In the recent case of RL "Bob" Morgan, most of what I would want to =
memorialize about his was his discussion manners and humor, which I =
think helped the IETF more than his technical contributions. I suspect a =
bunch of his friends would disagree with me and would want to emphasize =
his work in the many diverse areas.

The act of writing a history creates a story to be perpetuated. That's =
what Wikipedia and its interminable editing wars are for. Having Dave =
Crocker or Paul Hoffman or Randy Bush being the IETF Memorial Editor is =
simply not a good idea.

--Paul Hoffman=

From randy@psg.com  Mon Oct 22 07:50:24 2012
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2955F21F8976 for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 07:50:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.471
X-Spam-Level: 
X-Spam-Status: No, score=-2.471 tagged_above=-999 required=5 tests=[AWL=0.128,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IIszqHgLD-Sr for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 07:50:23 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id C8CAF21F85E2 for <ietf@ietf.org>; Mon, 22 Oct 2012 07:50:23 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=rair.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.80 (FreeBSD)) (envelope-from <randy@psg.com>) id 1TQJKf-000FtE-M2; Mon, 22 Oct 2012 14:50:21 +0000
Date: Mon, 22 Oct 2012 09:50:21 -0500
Message-ID: <m2hapmsgr6.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Paul Hoffman <paul.hoffman@vpnc.org>
Subject: Re: In Memoriam IETF web page
In-Reply-To: <83F2CC9B-60A2-4DA8-8217-642E2090D6B4@vpnc.org>
References: <50842367.3040108@dcrocker.net> <61A98088-7151-43A1-95EE-85C327A3240C@vigilsec.com> <m2hapn35k0.wl%randy@psg.com> <12D99082-7020-42CF-BA94-A7D683587CBA@isoc.org> <83F2CC9B-60A2-4DA8-8217-642E2090D6B4@vpnc.org>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Oct 2012 14:50:24 -0000

> Having Dave Crocker or Paul Hoffman or Randy Bush being the IETF
> Memorial Editor is simply not a good idea.

i do not want to be an editor.  and, when it is my turn, i do not want
to be memorialized.

we struggle to do a half-assed job at editing technology.  we are
amazingly unqualified to edit history.

randy

From hgs@cs.columbia.edu  Mon Oct 22 07:52:08 2012
Return-Path: <hgs@cs.columbia.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9749921F8976 for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 07:52:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EkMSksZqv2v7 for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 07:52:08 -0700 (PDT)
Received: from salak.cc.columbia.edu (salak.cc.columbia.edu [128.59.29.6]) by ietfa.amsl.com (Postfix) with ESMTP id 5C7EA21F85E2 for <ietf@ietf.org>; Mon, 22 Oct 2012 07:52:07 -0700 (PDT)
Received: from [172.20.27.119] ([208.23.64.30]) (user=hgs10 mech=PLAIN bits=0) by salak.cc.columbia.edu (8.14.4/8.14.3) with ESMTP id q9MEq4Er022717 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Mon, 22 Oct 2012 10:52:05 -0400 (EDT)
Subject: Re: In Memoriam IETF web page
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=us-ascii
From: Henning Schulzrinne <hgs@cs.columbia.edu>
In-Reply-To: <12D99082-7020-42CF-BA94-A7D683587CBA@isoc.org>
Date: Mon, 22 Oct 2012 10:52:07 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <A1029D11-E3D2-47DD-961A-CED1EB454DEF@cs.columbia.edu>
References: <50842367.3040108@dcrocker.net> <61A98088-7151-43A1-95EE-85C327A3240C@vigilsec.com> <m2hapn35k0.wl%randy@psg.com> <12D99082-7020-42CF-BA94-A7D683587CBA@isoc.org>
To: Pelletier Ray <rpelletier@isoc.org>
X-Mailer: Apple Mail (2.1283)
X-No-Spam-Score: Local
X-Scanned-By: MIMEDefang 2.68 on 128.59.29.6
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Oct 2012 14:52:08 -0000

It is quite common for technical societies (and, I assume, other =
professional associations) to note the passing of their members and =
contributors to their field. For many, the IETF is the closest thing =
they have to such a society and it is a key part of their professional =
and sometimes personal life.

We sometimes seem to worry too much about scaling problems that never =
actually occur; the discussion here seems to reflect one of them. I =
doubt that we'll be inundated with grieving relatives of one-time IETF =
attendees or IETF list subscribers who want their loved ones to be put =
on a web page.

If we want to keep this in the spirit of long-established (newspaper) =
traditions rather than a web page, we could use the IETF Journal for =
recording the passing of members of the community.

I also think that a longer list serves as a useful reminder that while =
we all are indebted to the pioneers, the Internet was built by a much =
larger number of people over the years, just like most human =
institutions.

As the first generation of contributors reaches zero on their =
time-to-live counter, this seems like the humane and professional thing =
to do, whatever precise form it takes.

Henning

On Oct 22, 2012, at 9:26 AM, Pelletier Ray wrote:

>=20
> On Oct 21, 2012, at 4:59 PM, Randy Bush wrote:
>=20
>> i started the thread on nanog.  i am not sure abha or jon would want =
to
>> be on such a list.  remember them and honor and carry on their work,
>> don't memorialize them.
>=20
> With all respect, it is not just about the person, it is about their =
work, its importance, the history of this Internet and providing role =
models to others.
>=20
> Ray
>=20
>=20
>>=20
>> randy
>=20
>=20


From housley@vigilsec.com  Mon Oct 22 08:02: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 E674121F8C2C for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 08:02:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.617
X-Spam-Level: 
X-Spam-Status: No, score=-102.617 tagged_above=-999 required=5 tests=[AWL=-0.018, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DI6OoTKWbLjg for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 08:02:39 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id 5697821F8C36 for <ietf@ietf.org>; Mon, 22 Oct 2012 08:02:36 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id E591A9A4003 for <ietf@ietf.org>; Mon, 22 Oct 2012 11:02:56 -0400 (EDT)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([208.254.26.82]) by localhost (ronin.smetech.net [208.254.26.81]) (amavisd-new, port 10024) with ESMTP id j17XTEBTzz6a for <ietf@ietf.org>; Mon, 22 Oct 2012 11:02:16 -0400 (EDT)
Received: from [192.168.2.100] (pool-96-255-37-162.washdc.fios.verizon.net [96.255.37.162]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 3D5429A4002 for <ietf@ietf.org>; Mon, 22 Oct 2012 11:02:56 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1085)
Subject: Re: In Memoriam IETF web page
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <12D99082-7020-42CF-BA94-A7D683587CBA@isoc.org>
Date: Mon, 22 Oct 2012 11:02:33 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <B1BAEDC3-F09C-48B2-BD8B-5DAAFADC0A49@vigilsec.com>
References: <50842367.3040108@dcrocker.net> <61A98088-7151-43A1-95EE-85C327A3240C@vigilsec.com> <m2hapn35k0.wl%randy@psg.com> <12D99082-7020-42CF-BA94-A7D683587CBA@isoc.org>
To: IETF <ietf@ietf.org>
X-Mailer: Apple Mail (2.1085)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Oct 2012 15:02:43 -0000

>> i started the thread on nanog.  i am not sure abha or jon would want =
to
>> be on such a list.  remember them and honor and carry on their work,
>> don't memorialize them.
>=20
> With all respect, it is not just about the person, it is about their =
work, its importance, the history of this Internet and providing role =
models to others.

This discussion has changed my mind.  I no longer support the creation =
of such a page.

A major factor in my changing my mind does not appear on this mail list, =
so I will share it.  In private I have received messages that can be =
summarized as: "If you make such a page, please do not put me on it."  =
These messages came from sources that clearly belong on such a page if =
it exists.

Russ


From stpeter@stpeter.im  Mon Oct 22 08:06:57 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 2B29F21F8C05 for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 08:06:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.613
X-Spam-Level: 
X-Spam-Status: No, score=-102.613 tagged_above=-999 required=5 tests=[AWL=-0.014, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id czLIMB9GQUdo for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 08:06:53 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id DA21A21F8C2E for <ietf@ietf.org>; Mon, 22 Oct 2012 08:06:52 -0700 (PDT)
Received: from [192.168.1.5] (unknown [71.237.13.154]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id BC4474010C; Mon, 22 Oct 2012 09:09:43 -0600 (MDT)
Message-ID: <50856118.5050203@stpeter.im>
Date: Mon, 22 Oct 2012 09:07:04 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:16.0) Gecko/20121010 Thunderbird/16.0.1
MIME-Version: 1.0
To: Russ Housley <housley@vigilsec.com>
Subject: Re: In Memoriam IETF web page
References: <50842367.3040108@dcrocker.net> <61A98088-7151-43A1-95EE-85C327A3240C@vigilsec.com> <m2hapn35k0.wl%randy@psg.com> <12D99082-7020-42CF-BA94-A7D683587CBA@isoc.org> <B1BAEDC3-F09C-48B2-BD8B-5DAAFADC0A49@vigilsec.com>
In-Reply-To: <B1BAEDC3-F09C-48B2-BD8B-5DAAFADC0A49@vigilsec.com>
X-Enigmail-Version: 1.4.5
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: Mon, 22 Oct 2012 15:06:57 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 10/22/12 9:02 AM, Russ Housley wrote:

> In private I have received messages that can be summarized as: "If
>  you make such a page, please do not put me on it."  These messages
>  came from sources that clearly belong on such a page if it
> exists.

Yeah, I certainly wouldn't want you to add people to such a page if
they're still sending you messages. Or does the Secretariat provide
seance services? ;-)

Peter

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


-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.18 (Darwin)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/

iEYEARECAAYFAlCFYRgACgkQNL8k5A2w/vwKigCdEj+5miwJlgFB7kT3IeEziHD/
jIIAnR4vQ39HJL+wBPRR0NaoWMZk+KGB
=CC9i
-----END PGP SIGNATURE-----

From randy@qti.qualcomm.com  Fri Oct 19 09:45:17 2012
Return-Path: <randy@qti.qualcomm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8EACF21F9057 for <ietf@ietfa.amsl.com>; Fri, 19 Oct 2012 09:45:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.299
X-Spam-Level: 
X-Spam-Status: No, score=-100.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MANGLED_OFF=2.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9zeNkmJCHCts for <ietf@ietfa.amsl.com>; Fri, 19 Oct 2012 09:45:16 -0700 (PDT)
Received: from sabertooth01.qualcomm.com (sabertooth01.qualcomm.com [65.197.215.72]) by ietfa.amsl.com (Postfix) with ESMTP id D13ED21F8F60 for <ietf@ietf.org>; Fri, 19 Oct 2012 09:45:15 -0700 (PDT)
X-IronPort-AV: E=McAfee;i="5400,1158,6870"; a="912881"
Received: from ironmsg03-l.qualcomm.com ([172.30.48.18]) by sabertooth01.qualcomm.com with ESMTP; 19 Oct 2012 09:31:51 -0700
X-IronPort-AV: E=Sophos;i="4.80,613,1344236400"; d="scan'208";a="350467002"
Received: from nasanexhc08.na.qualcomm.com ([172.30.39.7]) by Ironmsg03-L.qualcomm.com with ESMTP/TLS/RC4-SHA; 19 Oct 2012 09:45:15 -0700
Received: from [99.111.97.136] (172.30.39.5) by qcmail1.qualcomm.com (172.30.39.7) with Microsoft SMTP Server (TLS) id 14.2.318.1; Fri, 19 Oct 2012 09:45:14 -0700
Message-ID: <p06240600cca730fbf54c@[99.111.97.136]>
In-Reply-To: <41CCF322-545D-49BD-AEC8-F7595AEE0222@me.com>
References: <94279462-0f48-41ec-933a-a7ac22ba204a@email.android.com> <p06240628cca279fdf657@[99.111.97.136]> <41CCF322-545D-49BD-AEC8-F7595AEE0222@me.com>
X-Mailer: Eudora for Mac OS X
Date: Fri, 19 Oct 2012 09:45:12 -0700
To: Sabahattin Gucukoglu <listsebby@me.com>
From: Randall Gellens <randy@qti.qualcomm.com>
Subject: Re: Format=flowed quoting (was "Re: IETF...the unconference of SDOs")
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
Content-Transfer-Encoding: quoted-printable
X-Random-Sig-Tag: 1.0b28
X-Originating-IP: [172.30.39.5]
X-Mailman-Approved-At: Mon, 22 Oct 2012 08:14:18 -0700
Cc: Michael Richardson {quigon} <mcr@sandelman.ca>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Oct 2012 16:45:17 -0000

At 11:42 AM +0100 10/19/12, Sabahattin Gucukoglu wrote:

>  Warning: this message was generated by Apple Mail.

But not using Format=3DFlowed.


>  On 16 Oct 2012, at 03:46, Randall Gellens <randy@qti.qualcomm.com> wrote:
>
>>  At 9:12 AM -0400 9/5/12, Michael Richardson {quigon} wrote:
>>
>>>  Maybe I'm also concerned because many in the=20
>>> former "elite" have moved to Apple Mail, and=20
>>> it seems that it is bug
>>>  compatible with Outlook in it's assumption=20
>>> that format=3Dflowed is the default, an act=20
>>> which destroys email quoting, and therefore=20
>>> discussion.
>>
>>  I just noticed this assertion, which is quite=20
>> false.  Format=3Dflowed protects and preserved=20
>> quoting.  It's the only way to avoid ludicrous=20
>> and impossible to read quoting (which happens=20
>> after quoted passages get line-wrapped at odd=20
>> points).  Also, as far as I know, Exchange=20
>> does not support format=3Dflowed at all.  My=20
>> understanding is that it insists on HTML=20
>> quoting, which is entirely different.
>
>  You're right that this is the virtue of F/F,=20
> but that's not what Michael said.  Perhaps it=20
> was the context of the quoting, but the=20
> discussion refers to the fact that both LookOut=20
> and Apple Mail have (as you can see, by looking=20
> at this message) a nasty habit of *assuming* an=20
> F/F semantic by default.  In other words, they=20
> generate hugely long long long long long long=20
> long long long lines that only another equally=20
> broken client can interpret correctly, but=20
> dynamically reflowing those lines, by applying=20
> consistent quoting indicators to the lines of=20
> such reflowed lines, and so forth.  That, I=20
> believe, is a legitimate complaint, because it e

This reflects a misunderstanding of=20
=46ormat=3DFlowed.  Properly generated F=3DF has lines=20
of no more than 78 characters.  One of the=20
primary goals of F=3DF is good interoperability=20
between clients that support F=3DF and those that=20
support traditional pure plain text email.  What=20
you're describing is a symptom of HTML quoting=20
(or a surprisingly poor F=3DF implementation):

    When generating Format=3DFlowed text, lines SHOULD be 78 characters or
    shorter, including any trailing white space and also including any
    space added as part of stuffing (see Section 4.4).  As suggested
    values, any paragraph longer than 78 characters in total length could
    be wrapped using lines of 72 or fewer characters.  While the specific
    line length used is a matter of aesthetics and preference, longer
    lines are more likely to require rewrapping and to encounter
    difficulties with older mailers.  (It has been suggested that 66
    character lines are the most readable.)

    The restriction to 78 or fewer characters between CRLFs on the wire
    is to conform to [MSG-FMT].


>  At least Apple has the decency to use=20
> quoted-printable encoding to protect the actual=20
> transmitted lines,

Again, this shows a fundamental misunderstanding=20
of F=3DF.  Properly generated F=3DF does not use=20
quoted-printable unless otherwise needed:

    [Quoted-Printable] encoding SHOULD NOT be used with Format=3DFlowed
    unless absolutely necessary (for example, non-US-ASCII (8-bit)
    characters over a strictly 7-bit transport such as unextended
    [SMTP]).  In particular, a message SHOULD NOT be encoded in Quoted-
    Printable for the sole purpose of protecting the trailing space on
    flowed lines unless the body part is cryptographically signed or
    encrypted (see Section 4.6).


>  but it means nothing if competent MIME readers=20
> reconstitute the corruption at the other end,=20
> by reassembling long lines, and then failing to=20
> reflow them.  And it's worse yet if a news=20
> reader without MIME tries to quote the lines,=20
> complete with Q-P line terminators.  Or if a=20
> reply comes from somebody whose editor wraps=20
> the lines, but using soft line breaks which are=20
> never generated externally, resulting in whole=20
> paragraphs being quoted using a single quoting=20
> indicator.  And so on, and so on, and so on =8A

All of these are part of the problem set that F=3DF=20
was created to fix.  Proper F=3DF plays nice with=20
pure plain text.


>  I filed bug 7989556 (Mail uses quoted-printable=20
> indiscriminately) with Apple on 16 May 2010.=20
> It was marked as duplicate of 7547565 on 25 May=20
> 2010.  The system is closed; you can only see=20
> your own bug reports.  I therefore have no idea=20
> what's going on with that.  Meantime, I=20
> apologise for the inconvenience.  No, really.=20
> :-(

I haven't looked into Apple's mail's generation=20
of either F=3DF or plain text or HTML.  If it=20
generates F=3DF with long lines and/or=20
indiscriminate q-p, then those would in my view=20
be bugs that should be fixed.  But I don't know=20
if the symptoms described occur with Apple Mail's=20
=46=3DF or some other format.  To me, they sound like=20
lack of F=3DF.

-- 
Randall Gellens
Opinions are personal;    facts are suspect;    I speak for myself only
-------------- Randomly selected tag: ---------------
Perhaps the real reason why we have always been able to champion free
speech in this country is that we know perfectly well that hardly
anybody has got anything to say, and that no one will listen to anyone
that has.       -- Editorial, Daily Mail [British Paper, date unknown]

From kwiereng@cisco.com  Sun Oct 21 09:39:51 2012
Return-Path: <kwiereng@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 B21E321F85B3 for <ietf@ietfa.amsl.com>; Sun, 21 Oct 2012 09:39:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZXRMtmD2Dn6w for <ietf@ietfa.amsl.com>; Sun, 21 Oct 2012 09:39:51 -0700 (PDT)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) by ietfa.amsl.com (Postfix) with ESMTP id EFB2021F85B0 for <ietf@ietf.org>; Sun, 21 Oct 2012 09:39:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2006; q=dns/txt; s=iport; t=1350837591; x=1352047191; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=+Iq7JvdCz1bWCWt9DVYGAtBJly0Ss+5+LuQM50iqUJ4=; b=MDi0uO3mKeQMSRFqSQfYyefk5rNwNyjNTI6aDpJk6rhM2hCpPzy4ZO3t VVcvKdQmUX7FL4YHV2CwZljv+qgk6Gj+ZrmL34FD8F6ome2PtzPXGp7FT usdJDt7DU8NVr2owGKJAOJJ/zCcnlgp8myU3Q4++WeO5BbYgFwygK8WyN c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av4EAAYlhFCtJXG8/2dsb2JhbABEwRCBCIIgAQEBAwESASc/BQsCAQg2EDIlAgQOBRQOh1wGmyCfDotfhg9gA5VxgReNN4Frgm8
X-IronPort-AV: E=Sophos;i="4.80,626,1344211200"; d="scan'208";a="133854119"
Received: from rcdn-core2-1.cisco.com ([173.37.113.188]) by rcdn-iport-7.cisco.com with ESMTP; 21 Oct 2012 16:39:50 +0000
Received: from xhc-rcd-x06.cisco.com (xhc-rcd-x06.cisco.com [173.37.183.80]) by rcdn-core2-1.cisco.com (8.14.5/8.14.5) with ESMTP id q9LGdoCU007912 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sun, 21 Oct 2012 16:39:50 GMT
Received: from xmb-aln-x12.cisco.com ([169.254.7.49]) by xhc-rcd-x06.cisco.com ([173.37.183.80]) with mapi id 14.02.0318.001; Sun, 21 Oct 2012 11:39:50 -0500
From: "Klaas Wierenga (kwiereng)" <kwiereng@cisco.com>
To: "<dcrocker@bbiw.net>" <dcrocker@bbiw.net>
Subject: Re: In Memoriam IETF web page
Thread-Topic: In Memoriam IETF web page
Thread-Index: AQHNr6mbrZls30vBkUawfGhQ1c056pfD9gy6
Date: Sun, 21 Oct 2012 16:39:49 +0000
Message-ID: <637F44A1-49D0-4869-9912-52070E42EEAD@cisco.com>
References: <50842367.3040108@dcrocker.net>
In-Reply-To: <50842367.3040108@dcrocker.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-tm-as-product-ver: SMEX-10.2.0.1135-7.000.1014-19292.004
x-tm-as-result: No--45.013400-8.000000-31
x-tm-as-user-approved-sender: No
x-tm-as-user-blocked-sender: No
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Mon, 22 Oct 2012 08:14:18 -0700
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: Sun, 21 Oct 2012 16:39:51 -0000

Good plan!

Sent from my iPad

On 21 okt. 2012, at 18:32, "Dave Crocker" <dhc@dcrocker.net> wrote:

> Folks,
>=20
> A thread on the nanog list, about abha ahuja, reminds me of a suggestion =
I made casually to a few folk after the last IETF meeting:
>=20
>     We should consider having a persistent IETF page in memory of people =
who were part of our community.
>=20
> While the idea is simple, the comments I got back make clear that it need=
s to be pursued carefully.  That requires some formality.
>=20
> There are two different lines of consideration. These are offered as a st=
arting point for discussion:
>=20
>=20
> 1.   Who should be listed?
>=20
>     A number of different models make sense, but the challenge is somethi=
ng that is workable. For example, it does not seem like the sort of thing t=
hat would be appropriate for a consensus call to the community, for each en=
try.  I think that means the rules should be entirely mechanical.
>=20
>     Conceptually, the goal should be to include anyone who was "part of t=
he IETF community".  I'll suggest that any of these would qualify:
>=20
>     a. Held a formal position in the IETF (AD, WG Chair, IAOC/Trust,
>        IAB, IRTF, Nomcom, ...are there others?)
>=20
>     b. Held a position on an IETF committee (directorate,
>        advisory, ...)
>=20
>     c. Held a position on IETF staff (IAD, RFC Editor and, I think,
>        this should include on-going contractors, including AMS and RFC
>        document editors.
>=20
>     d. RFC author
>=20
>=20
> 2.   What should be the form of the page?
>=20
>     I suggest we keep it extremely simple:  an alphabetic listing by name=
, with a photo, if available, and a pointer to a page if they have one.  In=
 some cases, the IETF might formulate its own page for a person, but that's=
 distinct from this basic listing.
>=20
>=20
> Thoughts?
>=20
> d/
>=20
> --=20
> Dave Crocker
> Brandenburg InternetWorking
> bbiw.net

From peter@akayla.com  Sun Oct 21 14:39:33 2012
Return-Path: <peter@akayla.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F31A521F88FE; Sun, 21 Oct 2012 14:39:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.299
X-Spam-Level: 
X-Spam-Status: No, score=-0.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MANGLED_LIST=2.3]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aBZf2oN9T-vi; Sun, 21 Oct 2012 14:39:32 -0700 (PDT)
Received: from p3plsmtpa06-02.prod.phx3.secureserver.net (p3plsmtpa06-02.prod.phx3.secureserver.net [173.201.192.103]) by ietfa.amsl.com (Postfix) with ESMTP id 0CA9321F88F5; Sun, 21 Oct 2012 14:39:31 -0700 (PDT)
Received: from [192.168.6.4] ([64.134.68.84]) by p3plsmtpa06-02.prod.phx3.secureserver.net with  id DxfU1k0041p5FpL01xfV5A; Sun, 21 Oct 2012 14:39:30 -0700
User-Agent: Microsoft-MacOutlook/14.2.4.120824
Date: Sun, 21 Oct 2012 14:39:31 -0700
Subject: Gen-ART review of draft-ietf-nfsv4-federated-fs-protocol-13
From: Peter Yee <peter@akayla.com>
To: <draft-ietf-nfsv4-federated-fs-protocol.all@tools.ietf.org>
Message-ID: <CCA9B9A3.11A0%peter@akayla.com>
Thread-Topic: Gen-ART review of draft-ietf-nfsv4-federated-fs-protocol-13
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-Mailman-Approved-At: Mon, 22 Oct 2012 08:14:18 -0700
Cc: gen-art@ietf.org, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 21 Oct 2012 21:39:33 -0000

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>

Document: draft-ietf-nfsv4-federated-fs-protocol-13
Reviewer: Peter Yee
Review Date: Oct-19-2012
IETF LC End Date: Oct-22-2012
IESG Telechat date: TBD


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


This Standards Track document describes a protocol for maintaining a
Namespace Database for use with federated filesystem protocols.  The
document is well-written with good examples and little need to jump back
and forth in the text to understand it.

General: Are ranges (in attribute values) inclusive or exclusive?  They
appear to be inclusive, but it might be worth saying that somewhere, if
only once.

Section 2.7, NsdbName definition: expand NSDB to Namespace Database as
this is the first use of the term.

Section 2.8.1, 2nd sentence: "extention" -> "extension"

Section 2.8.3, 2nd paragraph, last sentence: in addition to checking for
added FSL records, shouldn't the fileserver also be checking for deleted
or migrated FSLs?  And why would the fileserver do this at the expiration
of the FSN TTL instead of waiting for the next access to the that FSN?
Otherwise the fileserver could be generating unnecessary traffic, although
there is a tradeoff to be made vs. performance.

Section 2.8.3, 3rd paragraph after bullet items, 1st sentence: "which" ->
"that".  (Yeah, I know, grammar police.)

Section 2.9, 3rd paragraph, 2nd sentence: "admininistrative" ->
"administrative"

Section 2.12, 2nd paragraph, last sentence: expand NCE (NSDB Container
Entry) as this is the first use of the term.

Section 3.2, item #5: "fs_location" -> "fs_locations"

Section 4.1, 1st paragraph, 3rd sentence: probably worth expanding "DSE"
to "DSA-specific entry" here.

Section 4.2.1.8, 1st paragraph, 2nd sentence: bracket "Section 2.8.1" in
"(see" and ")" for readability.

Section 4.2.2: "LDAP Objects" -> "LDAP Object Classes" seems appropriate.

Section 4.2.2.1, 2nd and 3rd sentences: replace "fedfsFsn" with
"fedfsNsdbContainerInfo"

Section 4.2.2.2, 5th paragraph: how is the prohibition on referencing
other attributes in the fedfsFsn object class supposed to work if this
document is the defining document for that object class?

Section 5.1.3.1, 1st paragraph after LDIF definition: a port number of
2049 is given.  Since this is already the default value, why not use a
different value?  Otherwise, there would be no practical need to include
that port number in the FSL creation request.

Section 5.1.3.1, 1st paragraph after LDIF definition: "up to date" ->
"up-to-date"

Section 5.1.3.2, 2nd paragraph: "a" -> "an"

Section 5.1.3.2, table entry for "fedfsNfsVarSub": "substituion" ->
"substitution"

Section 5.1.4, 1st paragraph, 1st sentence: "a Fileset location" -> "an
FSL"

Section 7.3, 2nd paragraph, "Specification" value: presumably this will be
changed to the RFC number when issued?

Section 8, 1st paragraph (definition of Administrator): "an" -> "a"

Section 8, 3rd paragraph (definition of Client): "filesystem access" ->
"file-access" for consistency of usage with the rest of the document.

Section 8, 5th paragraph (definition of Fileserver): rather than
discussing "a filesystem", should this be "one or more filesystems"?  Or
is a fileserver limited to exporting one filesystem?

Section 8, 8th paragraph (definition of Filesystem Access Protocol):
following up on the 3rd paragraph, should this be "File-access Protocol"
for consistency?

Section 8, 9th paragraph (definition of FSL), 2nd sentence: "fs_location"
-> "fs_locations".




From chuck.lever@oracle.com  Sun Oct 21 15:27:35 2012
Return-Path: <chuck.lever@oracle.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E5B7721F8C00; Sun, 21 Oct 2012 15:27:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.361
X-Spam-Level: 
X-Spam-Status: No, score=-9.361 tagged_above=-999 required=5 tests=[AWL=-1.063, BAYES_00=-2.599, MANGLED_LIST=2.3, RCVD_IN_DNSWL_HI=-8, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9oowAVDfqVp6; Sun, 21 Oct 2012 15:27:33 -0700 (PDT)
Received: from acsinet15.oracle.com (acsinet15.oracle.com [141.146.126.227]) by ietfa.amsl.com (Postfix) with ESMTP id 86D7321F8B7C; Sun, 21 Oct 2012 15:27:33 -0700 (PDT)
Received: from acsinet21.oracle.com (acsinet21.oracle.com [141.146.126.237]) by acsinet15.oracle.com (Sentrion-MTA-4.2.2/Sentrion-MTA-4.2.2) with ESMTP id q9LMRPew019467 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sun, 21 Oct 2012 22:27:26 GMT
Received: from acsmt357.oracle.com (acsmt357.oracle.com [141.146.40.157]) by acsinet21.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id q9LMRPrd009147 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 21 Oct 2012 22:27:25 GMT
Received: from abhmt104.oracle.com (abhmt104.oracle.com [141.146.116.56]) by acsmt357.oracle.com (8.12.11.20060308/8.12.11) with ESMTP id q9LMROTX032334; Sun, 21 Oct 2012 17:27:24 -0500
Received: from moret.1015granger.net (/99.26.161.222) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Sun, 21 Oct 2012 15:27:24 -0700
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: Gen-ART review of draft-ietf-nfsv4-federated-fs-protocol-13
From: Chuck Lever <chuck.lever@oracle.com>
In-Reply-To: <CCA9B9A3.11A0%peter@akayla.com>
Date: Sun, 21 Oct 2012 18:27:23 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <8E799E97-421F-4ECE-A1F0-CFCBE605C3E6@oracle.com>
References: <CCA9B9A3.11A0%peter@akayla.com>
To: Peter Yee <peter@akayla.com>
X-Mailer: Apple Mail (2.1499)
X-Source-IP: acsinet21.oracle.com [141.146.126.237]
X-Mailman-Approved-At: Mon, 22 Oct 2012 08:14:18 -0700
Cc: gen-art@ietf.org, "ietf@ietf.org" <ietf@ietf.org>, draft-ietf-nfsv4-federated-fs-protocol.all@tools.ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 21 Oct 2012 22:27:36 -0000

On Oct 21, 2012, at 5:39 PM, Peter Yee <peter@akayla.com> wrote:

> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>
>=20
> Document: draft-ietf-nfsv4-federated-fs-protocol-13
> Reviewer: Peter Yee
> Review Date: Oct-19-2012
> IETF LC End Date: Oct-22-2012
> IESG Telechat date: TBD
>=20
>=20
> Summary: This draft is basically ready for publication, but has nits =
that
> should be fixed before publication. [Ready with nits.]
>=20
>=20
> This Standards Track document describes a protocol for maintaining a
> Namespace Database for use with federated filesystem protocols.  The
> document is well-written with good examples and little need to jump =
back
> and forth in the text to understand it.
>=20
> General: Are ranges (in attribute values) inclusive or exclusive?  =
They
> appear to be inclusive, but it might be worth saying that somewhere, =
if
> only once.

Can you give me an example of a range that might need clarification?

I will address these comments and co-ordinate draft updates with our WG =
editor, Tom Haynes.

Thanks for your review. =20

> Section 2.7, NsdbName definition: expand NSDB to Namespace Database as
> this is the first use of the term.
>=20
> Section 2.8.1, 2nd sentence: "extention" -> "extension"
>=20
> Section 2.8.3, 2nd paragraph, last sentence: in addition to checking =
for
> added FSL records, shouldn't the fileserver also be checking for =
deleted
> or migrated FSLs?  And why would the fileserver do this at the =
expiration
> of the FSN TTL instead of waiting for the next access to the that FSN?
> Otherwise the fileserver could be generating unnecessary traffic, =
although
> there is a tradeoff to be made vs. performance.
>=20
> Section 2.8.3, 3rd paragraph after bullet items, 1st sentence: "which" =
->
> "that".  (Yeah, I know, grammar police.)
>=20
> Section 2.9, 3rd paragraph, 2nd sentence: "admininistrative" ->
> "administrative"
>=20
> Section 2.12, 2nd paragraph, last sentence: expand NCE (NSDB Container
> Entry) as this is the first use of the term.
>=20
> Section 3.2, item #5: "fs_location" -> "fs_locations"
>=20
> Section 4.1, 1st paragraph, 3rd sentence: probably worth expanding =
"DSE"
> to "DSA-specific entry" here.
>=20
> Section 4.2.1.8, 1st paragraph, 2nd sentence: bracket "Section 2.8.1" =
in
> "(see" and ")" for readability.
>=20
> Section 4.2.2: "LDAP Objects" -> "LDAP Object Classes" seems =
appropriate.
>=20
> Section 4.2.2.1, 2nd and 3rd sentences: replace "fedfsFsn" with
> "fedfsNsdbContainerInfo"
>=20
> Section 4.2.2.2, 5th paragraph: how is the prohibition on referencing
> other attributes in the fedfsFsn object class supposed to work if this
> document is the defining document for that object class?
>=20
> Section 5.1.3.1, 1st paragraph after LDIF definition: a port number of
> 2049 is given.  Since this is already the default value, why not use a
> different value?  Otherwise, there would be no practical need to =
include
> that port number in the FSL creation request.
>=20
> Section 5.1.3.1, 1st paragraph after LDIF definition: "up to date" ->
> "up-to-date"
>=20
> Section 5.1.3.2, 2nd paragraph: "a" -> "an"
>=20
> Section 5.1.3.2, table entry for "fedfsNfsVarSub": "substituion" ->
> "substitution"
>=20
> Section 5.1.4, 1st paragraph, 1st sentence: "a Fileset location" -> =
"an
> FSL"
>=20
> Section 7.3, 2nd paragraph, "Specification" value: presumably this =
will be
> changed to the RFC number when issued?
>=20
> Section 8, 1st paragraph (definition of Administrator): "an" -> "a"
>=20
> Section 8, 3rd paragraph (definition of Client): "filesystem access" =
->
> "file-access" for consistency of usage with the rest of the document.
>=20
> Section 8, 5th paragraph (definition of Fileserver): rather than
> discussing "a filesystem", should this be "one or more filesystems"?  =
Or
> is a fileserver limited to exporting one filesystem?
>=20
> Section 8, 8th paragraph (definition of Filesystem Access Protocol):
> following up on the 3rd paragraph, should this be "File-access =
Protocol"
> for consistency?
>=20
> Section 8, 9th paragraph (definition of FSL), 2nd sentence: =
"fs_location"
> -> "fs_locations".
>=20
>=20
>=20

--=20
Chuck Lever
chuck[dot]lever[at]oracle[dot]com





From peter@akayla.com  Sun Oct 21 20:35:44 2012
Return-Path: <peter@akayla.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4540421F8AB3 for <ietf@ietfa.amsl.com>; Sun, 21 Oct 2012 20:35:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.279
X-Spam-Level: 
X-Spam-Status: No, score=-0.279 tagged_above=-999 required=5 tests=[AWL=-0.020, BAYES_00=-2.599, MANGLED_LIST=2.3, MIME_BASE64_BLANKS=0.041]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id K2QyNcZUpLQe for <ietf@ietfa.amsl.com>; Sun, 21 Oct 2012 20:35:43 -0700 (PDT)
Received: from smtpauth05.prod.mesa1.secureserver.net (smtpauth05.prod.mesa1.secureserver.net [64.202.165.99]) by ietfa.amsl.com (Postfix) with SMTP id 723CD21F8AB0 for <ietf@ietf.org>; Sun, 21 Oct 2012 20:35:43 -0700 (PDT)
Received: (qmail 21731 invoked from network); 22 Oct 2012 03:35:42 -0000
Received: from unknown (64.134.68.84) by smtpauth05.prod.mesa1.secureserver.net (64.202.165.99) with ESMTP; 22 Oct 2012 03:35:40 -0000
User-Agent: Microsoft-MacOutlook/14.2.4.120824
Date: Sun, 21 Oct 2012 20:35:36 -0700
Subject: Re: Gen-ART review of draft-ietf-nfsv4-federated-fs-protocol-13
From: Peter Yee <peter@akayla.com>
To: Chuck Lever <chuck.lever@oracle.com>
Message-ID: <CCAA0CA5.11A5%peter@akayla.com>
Thread-Topic: Gen-ART review of draft-ietf-nfsv4-federated-fs-protocol-13
In-Reply-To: <8E799E97-421F-4ECE-A1F0-CFCBE605C3E6@oracle.com>
Mime-version: 1.0
Content-type: multipart/mixed; boundary="B_3433696546_3314490"
X-Mailman-Approved-At: Mon, 22 Oct 2012 08:14:18 -0700
Cc: gen-art@ietf.org, "ietf@ietf.org" <ietf@ietf.org>, draft-ietf-nfsv4-federated-fs-protocol.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, 22 Oct 2012 03:35:44 -0000

> This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--B_3433696546_3314490
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit

Chuck,
	Ranges include the 0,255 that appears commonly in the document in
attribute definitions along with one case of -2147483648,2147483647.

	Kind regards,
		-Peter

On 10/21/12 3:27 PM, "Chuck Lever" <chuck.lever@oracle.com> wrote:

>
>On Oct 21, 2012, at 5:39 PM, Peter Yee <peter@akayla.com> wrote:
>
>> I am the assigned Gen-ART reviewer for this draft. For background on
>> Gen-ART, please see the FAQ at
>> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>
>> 
>> Document: draft-ietf-nfsv4-federated-fs-protocol-13
>> Reviewer: Peter Yee
>> Review Date: Oct-19-2012
>> IETF LC End Date: Oct-22-2012
>> IESG Telechat date: TBD
>> 
>> 
>> Summary: This draft is basically ready for publication, but has nits
>>that
>> should be fixed before publication. [Ready with nits.]
>> 
>> 
>> This Standards Track document describes a protocol for maintaining a
>> Namespace Database for use with federated filesystem protocols.  The
>> document is well-written with good examples and little need to jump back
>> and forth in the text to understand it.
>> 
>> General: Are ranges (in attribute values) inclusive or exclusive?  They
>> appear to be inclusive, but it might be worth saying that somewhere, if
>> only once.
>
>Can you give me an example of a range that might need clarification?
>
>I will address these comments and co-ordinate draft updates with our WG
>editor, Tom Haynes.
>
>Thanks for your review.
>
>> Section 2.7, NsdbName definition: expand NSDB to Namespace Database as
>> this is the first use of the term.
>> 
>> Section 2.8.1, 2nd sentence: "extention" -> "extension"
>> 
>> Section 2.8.3, 2nd paragraph, last sentence: in addition to checking for
>> added FSL records, shouldn't the fileserver also be checking for deleted
>> or migrated FSLs?  And why would the fileserver do this at the
>>expiration
>> of the FSN TTL instead of waiting for the next access to the that FSN?
>> Otherwise the fileserver could be generating unnecessary traffic,
>>although
>> there is a tradeoff to be made vs. performance.
>> 
>> Section 2.8.3, 3rd paragraph after bullet items, 1st sentence: "which"
>>->
>> "that".  (Yeah, I know, grammar police.)
>> 
>> Section 2.9, 3rd paragraph, 2nd sentence: "admininistrative" ->
>> "administrative"
>> 
>> Section 2.12, 2nd paragraph, last sentence: expand NCE (NSDB Container
>> Entry) as this is the first use of the term.
>> 
>> Section 3.2, item #5: "fs_location" -> "fs_locations"
>> 
>> Section 4.1, 1st paragraph, 3rd sentence: probably worth expanding "DSE"
>> to "DSA-specific entry" here.
>> 
>> Section 4.2.1.8, 1st paragraph, 2nd sentence: bracket "Section 2.8.1" in
>> "(see" and ")" for readability.
>> 
>> Section 4.2.2: "LDAP Objects" -> "LDAP Object Classes" seems
>>appropriate.
>> 
>> Section 4.2.2.1, 2nd and 3rd sentences: replace "fedfsFsn" with
>> "fedfsNsdbContainerInfo"
>> 
>> Section 4.2.2.2, 5th paragraph: how is the prohibition on referencing
>> other attributes in the fedfsFsn object class supposed to work if this
>> document is the defining document for that object class?
>> 
>> Section 5.1.3.1, 1st paragraph after LDIF definition: a port number of
>> 2049 is given.  Since this is already the default value, why not use a
>> different value?  Otherwise, there would be no practical need to include
>> that port number in the FSL creation request.
>> 
>> Section 5.1.3.1, 1st paragraph after LDIF definition: "up to date" ->
>> "up-to-date"
>> 
>> Section 5.1.3.2, 2nd paragraph: "a" -> "an"
>> 
>> Section 5.1.3.2, table entry for "fedfsNfsVarSub": "substituion" ->
>> "substitution"
>> 
>> Section 5.1.4, 1st paragraph, 1st sentence: "a Fileset location" -> "an
>> FSL"
>> 
>> Section 7.3, 2nd paragraph, "Specification" value: presumably this will
>>be
>> changed to the RFC number when issued?
>> 
>> Section 8, 1st paragraph (definition of Administrator): "an" -> "a"
>> 
>> Section 8, 3rd paragraph (definition of Client): "filesystem access" ->
>> "file-access" for consistency of usage with the rest of the document.
>> 
>> Section 8, 5th paragraph (definition of Fileserver): rather than
>> discussing "a filesystem", should this be "one or more filesystems"?  Or
>> is a fileserver limited to exporting one filesystem?
>> 
>> Section 8, 8th paragraph (definition of Filesystem Access Protocol):
>> following up on the 3rd paragraph, should this be "File-access Protocol"
>> for consistency?
>> 
>> Section 8, 9th paragraph (definition of FSL), 2nd sentence:
>>"fs_location"
>> -> "fs_locations".
>> 
>> 
>> 
>
>-- 
>Chuck Lever
>chuck[dot]lever[at]oracle[dot]com
>
>
>
>
>


--B_3433696546_3314490
Content-type: application/xml; name="default[4].xml"
Content-disposition: attachment;
	filename="default[4].xml"
Content-transfer-encoding: base64


UEsDBBQABgAIAAAAIQCb6HBP/AAAABwCAAATAAAAW0NvbnRlbnRfVHlwZXNdLnhtbKyRy2rD
MBBF94X+g9C22HK6KKXYzqKPXR+L9AMGeWyL2CMhTULy9x07LpQSAoVuBNLMvffMqFwfxkHt
MSbnqdKrvNAKyfrGUVfpz81Ldq9VYqAGBk9Y6SMmva6vr8rNMWBSoqZU6Z45PBiTbI8jpNwH
JKm0Po7Aco2dCWC30KG5LYo7Yz0xEmc8eei6fMIWdgOr54M8n0hErtXjqW+KqjSEMDgLLKBm
qpqzuohDuiDcU/OLLlvIclHO5ql3Id0sCe+ymugaVB8Q+Q1G4TAsQ+LP8xVIRov5ZeYz0b5t
ncXG290o68hn48XsTwCr/4n+zjTz39ZfAAAA//8DAFBLAwQUAAYACAAAACEApdan58AAAAA2
AQAACwAAAF9yZWxzLy5yZWxzhI/PasMwDIfvhb2D0X1R0sMYJXYvpZBDL6N9AOEof2giG9sb
69tPxwYKuwiEpO/3qT3+rov54ZTnIBaaqgbD4kM/y2jhdj2/f4LJhaSnJQhbeHCGo3vbtV+8
UNGjPM0xG6VItjCVEg+I2U+8Uq5CZNHJENJKRds0YiR/p5FxX9cfmJ4Z4DZM0/UWUtc3YK6P
qMn/s8MwzJ5PwX+vLOVFBG43lExp5GKhqC/jU72QqGWq1B7Qtbj51v0BAAD//wMAUEsDBBQA
BgAIAAAAIQBreZYWgwAAAIoAAAAcAAAAdGhlbWUvdGhlbWUvdGhlbWVNYW5hZ2VyLnhtbAzM
TQrDIBBA4X2hd5DZN2O7KEVissuuu/YAQ5waQceg0p/b1+XjgzfO3xTVm0sNWSycBw2KZc0u
iLfwfCynG6jaSBzFLGzhxxXm6XgYybSNE99JyHNRfSPVkIWttd0g1rUr1SHvLN1euSRqPYtH
V+jT9yniResrJgoCOP0BAAD//wMAUEsDBBQABgAIAAAAIQAhWqKEIQcAANsdAAAWAAAAdGhl
bWUvdGhlbWUvdGhlbWUxLnhtbOxZT28bRRS/I/EdRnsvsRMnTaI6VezYDbRpo9gt6nG8O/ZO
M7uzmhkn8Q21RyQkREEcqMSNAwIqtRKX8mkCRVCkfgXezOyud+Jxk5QAFTSH1jv7e2/e+70/
82evXD1KGDogQlKeNoP6e7UAkTTkEU1HzeB2v3tpNUBS4TTCjKekGUyIDK5uvPvOFbyuYpIQ
BPKpXMfNIFYqW19YkCEMY/kez0gK74ZcJFjBoxgtRAIfgt6ELSzWaisLCaZpgFKcgNpbwyEN
CeprlcFGobzD4DFVUg+ETPS0auJIGGy0X9cIOZFtJtABZs0A5on4YZ8cqQAxLBW8aAY18xcs
bFxZwOu5EFNzZCtyXfOXy+UC0f6imVOMBuWk9W5j7fJWqd8AmJrFdTqddqde6jMAHIbgqbWl
qrPRXa23Cp0VkP05q7tdW641XHxF/9KMzWutVmt5LbfFKjUg+7Mxg1+trTQ2Fx28AVn88gy+
0dpst1ccvAFZ/MoMvnt5baXh4g0oZjTdn0HrgHa7ufYSMuRs2wtfBfhqLYdPUZANZXbpKYY8
VfNyLcH3uOgCQAMZVjRFapKRIQ4hi9uY0YGgegK8TnDljR0K5cyQngvJUNBMNYMPMgwVMdX3
8tl3L589Qcf3nx7f//H4wYPj+z9YRY7UNk5HVakX33z6x6OP0O9Pvn7x8HM/Xlbxv3z/8c8/
feYHQvlMzXn+xeNfnz5+/uUnv3370APfFHhQhfdpQiS6SQ7RHk/AMcOKazkZiPNJ9GNMqxKb
6UjiFOtZPPo7KnbQNyeYYQ+uRVwG7whoHz7gtfE9x+BeLMYqj7fj2fU4cYA7nLMWF14Wruu5
KjT3x+nIP7kYV3F7GB/45m7j1IlvZ5xB36Q+le2YOGbuMpwqPCIpUUi/4/uEePi6S6nD6w4N
BZd8qNBdilqYeinp04GTTVOhbZpAXCY+AyHeDjc7d1CLM5/XW+TARUJVYOYxvk+YQ+M1PFY4
8ans44RVCb+BVewzsjcRYRXXkQoiPSKMo05EpPTJ3BLgbyXo16F1+MO+wyaJixSK7vt03sCc
V5FbfL8d4yTzYXs0javY9+U+pChGu1z54DvcrRD9DHHA6dxw36HECffp3eA2HTkmTRNEvxkL
TyyvEe7kb2/ChpiYVgNN3enVCU1f1bgT6Nu54xfXuKFVPv/qkcfuN7VlbwIJvprZPtGo5+FO
tuc2FxF987vzFh6nuwQKYnaJetuc3zbn4D/fnOfV88W35GkXhgatt0x2o2223cncXfeQMtZT
E0ZuSLPxlrD2RF0Y1HLmxEnKU1gWw09dyTCBgxsJbGSQ4OpDquJejDPYtNcDrWQkc9UjiTIu
4bBohr26NR42/soeNZf1IcR2DonVDo/s8JIeLs4apRpj1cgcaIuJlrSCs062dDlXCr69zmR1
bdSZZ6sb00xTdGYrXdYUm0M5UF66BoMlm7CpQbAVApZX4Myvp4bDDmYk0rzbGBVhMVH4e0KU
e20diXFEbIic4QqbdRO7IoVm/NPu2Rw5H5sla0Da6UaYtJifP2ckuVAwJRkET1YTS6u1xVJ0
2AzWlheXAxTirBkM4ZgLP5MMgib1NhCzEdwVhUrYrD21Fk2RTj1e82dVHW4u5hSMU8aZkGoL
y9jG0LzKQ8VSPZO1f3G5oZPtYhzwNJOzWbG0Cinyr1kBoXZDS4ZDEqpqsCsjmjv7mHdCPlZE
9OLoEA3YWOxhCD9wqv2JqITbClPQ+gGu1jTb5pXbW/NOU73QMjg7jlkW47xb6quZouIs3PST
0gbzVDEPfPPabpw7vyu64i/KlWoa/89c0csBXB4sRToCIdzsCox0pTQDLlTMoQtlMQ27AtZ9
0zsgW+B6Fl4D+XC/bP4X5ED/b2vO6jBlDWdAtUdHSFBYTlQsCNmFtmSy7xRl9XzpsSpZrshk
VMVcmVmzB+SAsL7ugSu6BwcohlQ33SRvAwZ3Mv/c57yCBiO9R6nWm9PJyqXT1sA/vXGxxQxO
ndhL6Pwt+C9NLFf36epn5Y14sUZWHdEvprukRlEVzuK3tpZP9ZomnGUBrqy1tmPNeLy4XBgH
UZz1GAbL/UwGV0BI/wPrHxUhsx8r9ILa53vQWxF8e7D8IcjqS7qrQQbpBml/DWDfYwdtMmlV
ltp856NZKxbrC96olvOeIFtbdpZ4n5PschPlTufU4kWSnTPscG3H5lINkT1ZojA0LM4hJjDm
K1f1QxQf3INAb8GV/5jZT1MygydTB9muMNk14NEk/8mkXXBt1ukzjEaydI8MEY2OivNHyYQt
Ift5pNgiG7QW04lWCi75Dg2uYI7Xona1LIUXTxcuJczM0LJLYXOX5lMAH8fyxq2PdoC3TdZ6
rYurYIqlf4WyMxjvp8x78jkrZfag+MpAvQZl6ujVlOVMAXmziQefNwWGo1fP9F9YdGymm5Td
+BMAAP//AwBQSwMEFAAGAAgAAAAhAA3RkJ+2AAAAGwEAACcAAAB0aGVtZS90aGVtZS9fcmVs
cy90aGVtZU1hbmFnZXIueG1sLnJlbHOEj00KwjAUhPeCdwhvb9O6EJEm3YjQrdQDhOQ1DTY/
JFHs7Q2uLAguh2G+mWm7l53JE2My3jFoqhoIOumVcZrBbbjsjkBSFk6J2TtksGCCjm837RVn
kUsoTSYkUiguMZhyDidKk5zQilT5gK44o49W5CKjpkHIu9BI93V9oPGbAXzFJL1iEHvVABmW
UJr/s/04GolnLx8WXf5RQXPZhQUoosbM4CObqkwEylu6usTfAAAA//8DAFBLAQItABQABgAI
AAAAIQCb6HBP/AAAABwCAAATAAAAAAAAAAAAAAAAAAAAAABbQ29udGVudF9UeXBlc10ueG1s
UEsBAi0AFAAGAAgAAAAhAKXWp+fAAAAANgEAAAsAAAAAAAAAAAAAAAAALQEAAF9yZWxzLy5y
ZWxzUEsBAi0AFAAGAAgAAAAhAGt5lhaDAAAAigAAABwAAAAAAAAAAAAAAAAAFgIAAHRoZW1l
L3RoZW1lL3RoZW1lTWFuYWdlci54bWxQSwECLQAUAAYACAAAACEAIVqihCEHAADbHQAAFgAA
AAAAAAAAAAAAAADTAgAAdGhlbWUvdGhlbWUvdGhlbWUxLnhtbFBLAQItABQABgAIAAAAIQAN
0ZCftgAAABsBAAAnAAAAAAAAAAAAAAAAACgKAAB0aGVtZS90aGVtZS9fcmVscy90aGVtZU1h
bmFnZXIueG1sLnJlbHNQSwUGAAAAAAUABQBdAQAAIwsAAAAA
--B_3433696546_3314490--



From rwfranks@gmail.com  Mon Oct 22 05:07:00 2012
Return-Path: <rwfranks@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4076221F895C for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 05:07:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NV-bv7XBgdVB for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 05:06:59 -0700 (PDT)
Received: from mail-wi0-f178.google.com (mail-wi0-f178.google.com [209.85.212.178]) by ietfa.amsl.com (Postfix) with ESMTP id 5E36621F8906 for <ietf@ietf.org>; Mon, 22 Oct 2012 05:06:59 -0700 (PDT)
Received: by mail-wi0-f178.google.com with SMTP id hr7so1947811wib.13 for <ietf@ietf.org>; Mon, 22 Oct 2012 05:06:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=Uyqf+rKpCrjz5QsYO9m+ulp6jjRe9Q/uxi+vGQGgYOY=; b=UJkFZvEqqViNtxWlPYMPG8lQEecws/R2UvwkwPQLyy3XzoRfhANdSUUiLrQQZHHAKX THCz+g32dAC/DxYkwu2V2WhbjrZIEV78/NN2hroZzmu//jaj17OH1cFA58lBdMo/x6oq Gz0gbEfPB55evvyOZec1KPOYAxdh2oc6eNqggP2m5p5MbnV7dFGIiGZq7uBgxqT8eANe Y6hZgXh36uwIhvuWujDpZE9TQuDzK2jhpaVY9nukXJT+cMrI+io3FjAOMFUAmIK/HAl6 2ewSms3Fx5v+Zr9SQGqa0c54ZXyCdUmoIhh5Mw+IIcfwqqb64hTpwufZ27FDJQgUVnBF fcLw==
Received: by 10.180.8.41 with SMTP id o9mr20821947wia.3.1350907618392; Mon, 22 Oct 2012 05:06:58 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.194.41.65 with HTTP; Mon, 22 Oct 2012 05:06:38 -0700 (PDT)
In-Reply-To: <50842C69.9080407@queuefull.net>
References: <50842367.3040108@dcrocker.net> <0c7601cdafab$32abca00$98035e00$@olddog.co.uk> <50842C69.9080407@queuefull.net>
From: Dick Franks <rwfranks@gmail.com>
Date: Mon, 22 Oct 2012 13:06:38 +0100
Message-ID: <CAKW6Ri7vL5JEzEY3N5aXRBR0YW3KF5ABuJ=DLoJy5SYb2_fW1w@mail.gmail.com>
Subject: Re: In Memoriam IETF web page
To: Benson Schliesser <bensons@queuefull.net>
Content-Type: text/plain; charset=UTF-8
X-Mailman-Approved-At: Mon, 22 Oct 2012 08:14:18 -0700
Cc: adrian@olddog.co.uk, dcrocker@bbiw.net, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Oct 2012 12:07:00 -0000

+1

Better not to start a "tradition" which will become an intolerable
encumbrance even before we do!



On 21 October 2012 18:10, Benson Schliesser <bensons@queuefull.net> wrote:
> I feel a little bad saying this, because these individuals deserve
> recognition. But I rather think this memorial page is not a good idea.
>
> If the IETF is around long enough, eventually all members of the community
> will die. (Unless medical science makes some amazing achievements, I
> suppose...) It's easy today to recognize a few people that made large
> contributions earlier in the IETF's history. But at some point the list will
> grow large, until it has lost its significance. And yet, at that point, it
> may be unseemly to stop the tradition, and even more unseemly to delete the
> existing memorial.
>
> I don't want to be insensitive, and I'm sorry to point this out. But I think
> we're better off with heart-felt, personal memorials from living people that
> remember and care about the departed.
>
> -Benson

From dhc@dcrocker.net  Mon Oct 22 08:26:06 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 570F021F8CB6 for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 08:26:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eOVjAK-y4CAc for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 08:26:00 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 9ED2621F8CAE for <ietf@ietf.org>; Mon, 22 Oct 2012 08:25:58 -0700 (PDT)
Received: from [10.101.1.120] ([206.205.237.234]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q9MFPsw5005639 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <ietf@ietf.org>; Mon, 22 Oct 2012 08:25:55 -0700
Message-ID: <5085657B.3060908@dcrocker.net>
Date: Mon, 22 Oct 2012 11:25:47 -0400
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121010 Thunderbird/16.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: In Memoriam IETF web page
References: <50842367.3040108@dcrocker.net> <0c7601cdafab$32abca00$98035e00$@olddog.co.uk> <E0D759CB97DC2AD27C86BA7D@JcK-HP8200.jck.com> <50852F80.5040605@dcrocker.net> <20121022144227.GB50381@mx1.yitter.info>
In-Reply-To: <20121022144227.GB50381@mx1.yitter.info>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Mon, 22 Oct 2012 08:25:56 -0700 (PDT)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Oct 2012 15:26:06 -0000

>> some/many/most, but not for all.  As an example, how will we feel
>> about having the list contain the names of sockpuppets that have
>> been active in the IETF?
>
> This question nicely identifies why the proposal makes me so
> uncomfortable, and why I don't think I can support it, however much I
> think there are contributors worth remembering.
>
> The question assumes that there is an easy way to identify the "we" of
> "how will we feel", not to mention an easy way to tell who is a
> sockpuppet.  Each of us doubtless has perfectly useful and effective
> ways of making such identifications, but I doubt they'll be the same
> for everyone.


The proposal I posted offered specific roles and types of activity that 
would qualify.  It also asked some targeted questions.

The proposal is for a list of folk who have been active in the IETF. 
That's different from "relevant" to the IETF or active more generally in 
the Internet.

So far, the various notes expressing concerns have been quite generic, 
or have objected to details that weren't proposed.

It might be helpful to have some comments about the specifics that were 
offered.  For example, in what way are they inadequate?

d/
-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From brian.e.carpenter@gmail.com  Mon Oct 22 09:03:20 2012
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A273E21F8C68 for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 09:03:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.675
X-Spam-Level: 
X-Spam-Status: No, score=-101.675 tagged_above=-999 required=5 tests=[AWL=0.016, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lB4lPWGqLTTn for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 09:03:20 -0700 (PDT)
Received: from mail-bk0-f44.google.com (mail-bk0-f44.google.com [209.85.214.44]) by ietfa.amsl.com (Postfix) with ESMTP id 5DF6221F8C52 for <ietf@ietf.org>; Mon, 22 Oct 2012 09:03:19 -0700 (PDT)
Received: by mail-bk0-f44.google.com with SMTP id jc3so992770bkc.31 for <ietf@ietf.org>; Mon, 22 Oct 2012 09:03:18 -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=RKzxCWvYl9KhutImF9Uah1UOl+drmMi9d3Ia66tjzrY=; b=DX1KR15us5GI6SE0H2qZmqYa/BMpzvm3HajQwcoENB4UKTasJuxT0TdEM6dPykrC6k 6xoyQ6evo2ke7X06diNGM9OmQrfx5JL84O9+JcfvNG1gisZMKKQyFJgcCagSWcqZgBl5 WYfjlxy/c6UbJSA2yeOGMppB11H8uuVTGxpVLhPIlX5+sjcGGtdhubeaHoJ6YMTVsQyi JlQ65w8e3Be48Bovd6ix22xNE2Gy0LRU5Jab3USzKqnMPblXiyq+st4KAlnib6bi3dUA GK11Bmw8r8LYEReWKpLdpl6hTZP7+fniwo8dRZP3VY5loFrAnSmXwAD5QDwGU7HT/ejo 2gzw==
Received: by 10.204.150.141 with SMTP id y13mr2780533bkv.1.1350921798279; Mon, 22 Oct 2012 09:03:18 -0700 (PDT)
Received: from [192.168.1.64] (host-2-102-216-204.as13285.net. [2.102.216.204]) by mx.google.com with ESMTPS id r15sm4081605bkw.9.2012.10.22.09.03.13 (version=SSLv3 cipher=OTHER); Mon, 22 Oct 2012 09:03:14 -0700 (PDT)
Message-ID: <50856E3C.103@gmail.com>
Date: Mon, 22 Oct 2012 17:03:08 +0100
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Noah Mendelsohn <nrm@arcanedomain.com>
Subject: Re: [whatwg] New URL Standard from Anne van Kesteren on 2012-09-24 (public-whatwg-archive@w3.org from September 2012)
References: <50604C1A.7090901@gmx.de> <5060A964.5060001@stpeter.im>	<Pine.LNX.4.64.1210172354500.2478@ps20323.dreamhostps.com> <507F5A7E.6040206@arcanedomain.com>
In-Reply-To: <507F5A7E.6040206@arcanedomain.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Julian Reschke <julian.reschke@gmx.de>, mnot@mnot.net, URI <uri@w3.org>, Ian Hickson <ian@hixie.ch>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Oct 2012 16:03:20 -0000

Hi Noah,

On 18/10/2012 02:25, Noah Mendelsohn wrote:
> 
> 
> On 10/17/2012 7:57 PM, Ian Hickson wrote:
>> Yeah. Turns out we (the Web standards community) haven't been doing
>> such a
>> great job of making our specificatiosn match reality.:-(
> 
> Um, true... but it's also the case that the implementation community
> hasn't over the years been doing as much as might be best to make
> reality match the specifications. The new specs we're writing now would
> like have been a lot thinner and cleaner if they had.

However, I think the concern here is that if certain IETF specs need to be
updated to match the real world, that work needs to be done in the IETF.
It can't be done by reference in a W3C document; it has to be done by value
in an IETF document.

So it seems to me there is an open liaison question here and I'd like to hear
from the IETF/W3C liaison how this will be resolved.

Regards
    Brian

From ajs@anvilwalrusden.com  Mon Oct 22 09:11:01 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 8D1CC21F86D6 for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 09:11:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.84
X-Spam-Level: 
X-Spam-Status: No, score=-0.84 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PzE5LIw34e+p for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 09:11:01 -0700 (PDT)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id 040E621F887B for <ietf@ietf.org>; Mon, 22 Oct 2012 09:11:01 -0700 (PDT)
Received: from crankycanuck.ca (dhcp-222-230.meetings.nanog.org [199.187.222.230]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id 5BC4E8A031 for <ietf@ietf.org>; Mon, 22 Oct 2012 16:11:00 +0000 (UTC)
Date: Mon, 22 Oct 2012 12:10:56 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: Re: In Memoriam IETF web page
Message-ID: <20121022161055.GH50381@crankycanuck.ca>
References: <50842367.3040108@dcrocker.net> <0c7601cdafab$32abca00$98035e00$@olddog.co.uk> <E0D759CB97DC2AD27C86BA7D@JcK-HP8200.jck.com> <50852F80.5040605@dcrocker.net> <20121022144227.GB50381@mx1.yitter.info> <5085657B.3060908@dcrocker.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <5085657B.3060908@dcrocker.net>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Oct 2012 16:11:01 -0000

On Mon, Oct 22, 2012 at 11:25:47AM -0400, Dave Crocker wrote:
> The proposal I posted offered specific roles and types of activity
> that would qualify.  It also asked some targeted questions.

As I guess I suggested, I believe the idea that the objectivity is
going to last is just wishful thinking.  If I'm wrong about that, then
the list will not do the job we want of it.

You offered categories that would automatically qualify people.
Inevitably, there are going to be cases where some subset of the
community thought that a person who qualifies under those criteria was
notable primarily in the negative sense.  They weren't a contributor,
but rather did harm, either to the organization or to the protocol in
question (or both).  As soon as we run into such a case, there will be
a debate.  If not, the list will just be a list of the historical IETF
in-crowd (if I read him correctly, that's Scott Brim's objection).  A
cool kids list is hardly a fitting memorial to the people we are
trying to identify -- those giants on whose shoulders we stand.

I think it more likely that, in response to a controversial case,
we'll invent a new process to manage.  I think that's a threat to the
IETF, and it would be ironic if the list meant to lionize earlier
contributors managed to consume the very mechanism they used for
making their contributions.

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com


From hsantos@isdg.net  Mon Oct 22 10:08:52 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 0A85321F88F5 for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 10:08:52 -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=0.863, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uEteqBfqxxEh for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 10:08:50 -0700 (PDT)
Received: from winserver.com (ntbbs.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 99E9C21F88DC for <ietf@ietf.org>; Mon, 22 Oct 2012 10:08:50 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=299; t=1350925722; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=rsIUSj4QS01VBQtmUTDYARJWaJI=; b=t9kTmvezTHDUb8IzoWo3 RGKKL+2O3rRAUXJgabsxKkCUpeTs2KjnRU9mxjIibcQGnntcmE2TJxB7JSZzg/RC 8dXnazqYyqX4H+z/5Q5vvkfZjvsp3Irt2pxkNoyoOeTyTbH4xN4AM91O/zbXe33r bnrlL9koZk3Kfc/GRB84lOY=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Mon, 22 Oct 2012 13:08:42 -0400
Authentication-Results: dkim.winserver.com; dkim=pass header.d=beta.winserver.com header.s=tms1 header.i=beta.winserver.com;  adsp=pass policy=all author.d=isdg.net asl.d=beta.winserver.com;
Received: from beta.winserver.com ([208.247.131.23]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 2652493029.5415.1776; Mon, 22 Oct 2012 13:08:41 -0400
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=299; t=1350925426; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=S5301Wm fC3Gh7UBbeqN9X7jzXn8JOnKoFZ3JXXWseMU=; b=fj32YqQBmPmaZnqWQjgOz44 cpp2GWePy3TNb7TVVZNF4dk6zvuSgNBRR7/GcBcAEVCyicAYgbsEamt9j7O8kGDG g3EY7yr7GtpoKGkytKLPnJBNTddR53CZTG6XkvWaRbdus35GO0sPMbSaPmAls9Dr zgQcr+9Zt8ivjTfC3QRw=
Received: by beta.winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Mon, 22 Oct 2012 13:03:46 -0400
Received: from [192.168.1.101] ([99.3.147.93]) by beta.winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 3251257146.7.3356; Mon, 22 Oct 2012 13:03:45 -0400
Message-ID: <50857DB4.1080309@isdg.net>
Date: Mon, 22 Oct 2012 13:09:08 -0400
From: Hector Santos <hsantos@isdg.net>
Organization: Santronics Software, Inc.
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: Henning Schulzrinne <hgs@cs.columbia.edu>
Subject: Re: In Memoriam IETF web page
References: <50842367.3040108@dcrocker.net>	<61A98088-7151-43A1-95EE-85C327A3240C@vigilsec.com>	<m2hapn35k0.wl%randy@psg.com>	<12D99082-7020-42CF-BA94-A7D683587CBA@isoc.org> <A1029D11-E3D2-47DD-961A-CED1EB454DEF@cs.columbia.edu>
In-Reply-To: <A1029D11-E3D2-47DD-961A-CED1EB454DEF@cs.columbia.edu>
Content-Type: text/plain; charset=UTF-8; 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
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Oct 2012 17:08:52 -0000

Henning Schulzrinne wrote:
> If we want to keep this in the spirit of long-established 
> (newspaper) traditions rather than a web page, we could use the 
> IETF Journal for recording the passing of members of the community.

This seems reasonable and fitting for all qualifications.

-- 
HLS



From jnc@mercury.lcs.mit.edu  Mon Oct 22 10:14:20 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 93C7421F8466 for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 10:14:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.413
X-Spam-Level: 
X-Spam-Status: No, score=-6.413 tagged_above=-999 required=5 tests=[AWL=0.186,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HdHIcALs4Chj for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 10:14:16 -0700 (PDT)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id 4210121F84C4 for <ietf@ietf.org>; Mon, 22 Oct 2012 10:14:08 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 359B318C0B5; Mon, 22 Oct 2012 13:14:07 -0400 (EDT)
To: ietf@ietf.org
Subject: Re: In Memoriam IETF web page
Message-Id: <20121022171407.359B318C0B5@mercury.lcs.mit.edu>
Date: Mon, 22 Oct 2012 13:14:07 -0400 (EDT)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: jnc@mercury.lcs.mit.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Oct 2012 17:14:20 -0000

    > From: Scott Brim <swb@internet2.edu>

    > If this memorial wiki page could be open to anyone who ever contributed
    > to any I* and for whom there was at least one person who wanted to
    > contribute the information, then fine.

Then it turns into (effectively) a phone book - and I don't know too many
people who read phone books.

Not that I object to the creation of such a construct - far from it, I expect
that historians in decades to come would probably find it valuable and
interesting. I'm not sure too many others, would, though (at least, in its
entirety - for individual people they already know, they might find it good).

So it's not a replacement for a Hall of Fame, which people might read, or scan
through, in its entirety. (Steve Coya, for instance, I would like to see
memorialized in an IETF HoF. He did a great deal for us, but people who joined
recently will have no idea who he was.)

    > If not, then it would be yet another situation where there will be a
    > line between the in-crowd and the out-crowd.

Every award ever devised is, implicitly, a line between the 'betters' and the
'lessers'. So you're saying we should get rid of them all - the Nobels, the
EU's Sakharov Prize (for which I have a soft spot because the first one went
to one of my great heroes, Anatoly Marchenko), etc, etc?

(And no, I'm not ignoring the difficulties in picking honorees, in any
system. Maybe that difficulty makes it too much trouble to have an IETF HoF.
But that's a different point entirely from the ethical wholesomeness of having
honorees at all.)

	Noel

From swb@internet2.edu  Mon Oct 22 10:25:38 2012
Return-Path: <swb@internet2.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ADBC511E80E3 for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 10:25:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oQt8en2ciZm4 for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 10:25:35 -0700 (PDT)
Received: from int-proxy01.merit.edu (int-proxy01.merit.edu [207.75.116.230]) by ietfa.amsl.com (Postfix) with ESMTP id 3DA2F11E80BA for <ietf@ietf.org>; Mon, 22 Oct 2012 10:25:35 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by int-proxy01.merit.edu (Postfix) with ESMTP id B7539100047; Mon, 22 Oct 2012 13:25:34 -0400 (EDT)
X-Virus-Scanned: amavisd-new at int-proxy01.merit.edu
Received: from int-proxy01.merit.edu ([127.0.0.1]) by localhost (int-proxy01.merit.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H08U8UCdPv1p; Mon, 22 Oct 2012 13:25:33 -0400 (EDT)
Received: from swbi2mbp.local (cpe-67-241-75-185.twcny.res.rr.com [67.241.75.185]) by int-proxy01.merit.edu (Postfix) with ESMTPSA id 577DF100031; Mon, 22 Oct 2012 13:25:32 -0400 (EDT)
Message-ID: <50858186.3080804@internet2.edu>
Date: Mon, 22 Oct 2012 13:25:26 -0400
From: Scott Brim <swb@internet2.edu>
Organization: Internet2
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:16.0) Gecko/20121010 Thunderbird/16.0.1
MIME-Version: 1.0
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Subject: Re: In Memoriam IETF web page
References: <20121022171407.359B318C0B5@mercury.lcs.mit.edu>
In-Reply-To: <20121022171407.359B318C0B5@mercury.lcs.mit.edu>
X-Enigmail-Version: 1.4.5
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Oct 2012 17:25:38 -0000

Noel, in all of this you're assuming that being remembered on an IETF
wiki should be an exclusive award.

On 10/22/12 13:14, Noel Chiappa allegedly wrote:
>     > From: Scott Brim <swb@internet2.edu>
> 
>     > If this memorial wiki page could be open to anyone who ever contributed
>     > to any I* and for whom there was at least one person who wanted to
>     > contribute the information, then fine.
> 
> Then it turns into (effectively) a phone book - and I don't know too many
> people who read phone books.
> 
> Not that I object to the creation of such a construct - far from it, I expect
> that historians in decades to come would probably find it valuable and
> interesting. I'm not sure too many others, would, though (at least, in its
> entirety - for individual people they already know, they might find it good).
> 
> So it's not a replacement for a Hall of Fame, which people might read, or scan
> through, in its entirety. (Steve Coya, for instance, I would like to see
> memorialized in an IETF HoF. He did a great deal for us, but people who joined
> recently will have no idea who he was.)
> 
>     > If not, then it would be yet another situation where there will be a
>     > line between the in-crowd and the out-crowd.
> 
> Every award ever devised is, implicitly, a line between the 'betters' and the
> 'lessers'. So you're saying we should get rid of them all - the Nobels, the
> EU's Sakharov Prize (for which I have a soft spot because the first one went
> to one of my great heroes, Anatoly Marchenko), etc, etc?
> 
> (And no, I'm not ignoring the difficulties in picking honorees, in any
> system. Maybe that difficulty makes it too much trouble to have an IETF HoF.
> But that's a different point entirely from the ethical wholesomeness of having
> honorees at all.)
> 
> 	Noel
> 

From tytso@thunk.org  Mon Oct 22 10:48:03 2012
Return-Path: <tytso@thunk.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 1961911E80A4 for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 10:48:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.343
X-Spam-Level: 
X-Spam-Status: No, score=-1.343 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_MISMATCH_ORG=0.611, HOST_MISMATCH_COM=0.311, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dq0+PjBtlj3M for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 10:48:02 -0700 (PDT)
Received: from imap.thunk.org (li9-11.members.linode.com [67.18.176.11]) by ietfa.amsl.com (Postfix) with ESMTP id 493BC11E80E7 for <ietf@ietf.org>; Mon, 22 Oct 2012 10:48:01 -0700 (PDT)
Received: from root (helo=closure.thunk.org) by imap.thunk.org with local-esmtp (Exim 4.72) (envelope-from <tytso@thunk.org>) id 1TQM6S-0007U6-8Z; Mon, 22 Oct 2012 17:47:52 +0000
Received: by closure.thunk.org (Postfix, from userid 15806) id DC4C224030C; Mon, 22 Oct 2012 13:47:57 -0400 (EDT)
Date: Mon, 22 Oct 2012 13:47:57 -0400
From: Theodore Ts'o <tytso@mit.edu>
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Subject: Re: In Memoriam IETF web page
Message-ID: <20121022174757.GA9515@thunk.org>
References: <20121022171407.359B318C0B5@mercury.lcs.mit.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20121022171407.359B318C0B5@mercury.lcs.mit.edu>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Mail-From: tytso@thunk.org
X-SA-Exim-Scanned: No (on imap.thunk.org); SAEximRunCond expanded to 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: Mon, 22 Oct 2012 17:48:03 -0000

On Mon, Oct 22, 2012 at 01:14:07PM -0400, Noel Chiappa wrote:
>     > If this memorial wiki page could be open to anyone who ever contributed
>     > to any I* and for whom there was at least one person who wanted to
>     > contribute the information, then fine.
> 
> Then it turns into (effectively) a phone book - and I don't know too many
> people who read phone books.

Would you consider a war memorial a "phone book"?  Not that it's an
exact match, of course (or is it?  "The following people helped defend
the Internet against the scourge of OSI" :-), but that's also another
way of dealing with it.  Just make it a list, with the most recently
passed at the top of the list.

I suspect for those who think it's important, they would appreciate
the gesture, and for those who don't, well they probably won't bother
to look at the web page.  Just like I generally don't bother reading
all of the names listed at a war memorial, but I still support the
presence and existence of such memorials.  (And there *are* people who
go looking for the names of the fallen on such memorials.)

The bottom line for me is that if there are volunteers who feel
passionate about maintaining such a page, and if there is an opt out
for those really feel strongly about a few hundred bytes of HTML after
they pass away, does maintaining such a web page do significant harm?
And if it's important for some, why not do it?

Regards,

						- Ted

From acooper@cdt.org  Mon Oct 22 11:40:38 2012
Return-Path: <acooper@cdt.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 34A3B11E80FB for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 11:40:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.43
X-Spam-Level: 
X-Spam-Status: No, score=-102.43 tagged_above=-999 required=5 tests=[AWL=0.169, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hXNc5l9YN+F7 for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 11:40:37 -0700 (PDT)
Received: from mail.maclaboratory.net (mail.maclaboratory.net [209.190.215.232]) by ietfa.amsl.com (Postfix) with ESMTP id 1F32F11E80ED for <ietf@ietf.org>; Mon, 22 Oct 2012 11:40:37 -0700 (PDT)
X-Footer: Y2R0Lm9yZw==
Received: from localhost ([127.0.0.1]) by mail.maclaboratory.net (using TLSv1/SSLv3 with cipher AES128-SHA (128 bits)) for ietf@ietf.org; Mon, 22 Oct 2012 14:40:35 -0400
From: Alissa Cooper <acooper@cdt.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Mailing list for IETF women
Date: Mon, 22 Oct 2012 14:40:34 -0400
Message-Id: <0AC2765F-6BE7-450E-94BB-E8A99D9C0048@cdt.org>
To: IETF Discussion Mailing List <ietf@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1084)
X-Mailer: Apple Mail (2.1084)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Oct 2012 18:40:38 -0000

A group of folks have had discussions over the years about finding ways =
to encourage and support the participation of women in the IETF. For =
those who are interested, this is a reminder that a mailing list exists =
for IETF women: systers@ietf.org. Sign-up is at =
<https://www.ietf.org/mailman/listinfo/systers> -- thanks to Mirjam =
Kuehne and Margaret Wasserman for setting it up. There will likely be a =
systers lunch at IETF 85 in Atlanta; more details will be posted to =
systers@ietf.org.=


From jnc@mercury.lcs.mit.edu  Mon Oct 22 12:03:59 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 BDB331F0C67 for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 12:03:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.126
X-Spam-Level: 
X-Spam-Status: No, score=-6.126 tagged_above=-999 required=5 tests=[AWL=-0.127, BAYES_00=-2.599, J_CHICKENPOX_21=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id igi-kDei4ccQ for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 12:03:59 -0700 (PDT)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id 1AC9721F8788 for <ietf@ietf.org>; Mon, 22 Oct 2012 12:03:59 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 7F7BF18C0B7; Mon, 22 Oct 2012 15:03:58 -0400 (EDT)
To: ietf@ietf.org
Subject: Re: In Memoriam IETF web page
Message-Id: <20121022190358.7F7BF18C0B7@mercury.lcs.mit.edu>
Date: Mon, 22 Oct 2012 15:03:58 -0400 (EDT)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: jnc@mercury.lcs.mit.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Oct 2012 19:03:59 -0000

    >> Not that I object to the creation of such a construct - far from it
    >> ..
    >> So it's not a replacement for a Hall of Fame, which people might read,
    >> or scan through, in its entirety. 

    > From: Scott Brim <swb@internet2.edu>

    > you're assuming that being remembered on an IETF wiki should be an
    > exclusive award.

    > From: Theodore Ts'o <tytso@mit.edu>

    > Would you consider a war memorial a "phone book"? ... Just make it a
    > list, with the most recently passed at the top of the list.

You both seem to have completely missed the point of my message, so let me
re-state it more explicitly.

When I said "Not that I object to the creation of such a construct" (i.e.
Scott's suggested memorial wiki), I assumed that that made it perfectly clear
that I _wasn't_ against the concept of some sort of encompassing
listing/memorial.

So when I went on to say "it's not a replacement for a Hall of Fame", I
assumed that people would understand (given the above point) that I was
positing that i) such a HoF would _necessarily_ be a separate construct from a
memorial, and ii) that I saw the use/need for such a separate HoF.

I.e. (to be even more redundantly explicit) one could in theory have either
the memorial, the HoF, or both, or neither.

I make (and made) no statement about the memorial - as I said, 'I don't object
to such a construct'. More explicitly, if people want to do that, that's fine
with me. If they don't, that's fine with me too.


But I still feel a mild level of need for a IETF HoF to recognize, and keep
prominent (for new members) the memory of past IETFers whose contributions
are worthy of recognition, but who probably don't rise to the level needed
for more major honours (e.g. the ISOC Internet Hall of Fame).

Several have been named in this discussion.

	Noel

From julian.reschke@gmx.de  Mon Oct 22 12:09:32 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 6FA5721F8495 for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 12:09:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.487
X-Spam-Level: 
X-Spam-Status: No, score=-103.487 tagged_above=-999 required=5 tests=[AWL=-0.888, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oiPnONkgEZTv for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 12:09:32 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by ietfa.amsl.com (Postfix) with SMTP id 8825221F8480 for <ietf@ietf.org>; Mon, 22 Oct 2012 12:09:31 -0700 (PDT)
Received: (qmail invoked by alias); 22 Oct 2012 18:59:42 -0000
Received: from p5DD95D63.dip.t-dialin.net (EHLO [192.168.178.36]) [93.217.93.99] by mail.gmx.net (mp069) with SMTP; 22 Oct 2012 20:59:42 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1/2YHd0lWL2uJx/Rv8dsobGgm11W0tZmQji9bdAq6 XVhEYNoWsTUomY
Message-ID: <5085979D.8040104@gmx.de>
Date: Mon, 22 Oct 2012 20:59:41 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121010 Thunderbird/16.0.1
MIME-Version: 1.0
To: Ian Hickson <ian@hixie.ch>
Subject: Re: [whatwg] New URL Standard from Anne van Kesteren on 2012-09-24 (public-whatwg-archive@w3.org from September 2012)
References: <50604C1A.7090901@gmx.de> <5060A964.5060001@stpeter.im> <Pine.LNX.4.64.1210172354500.2478@ps20323.dreamhostps.com> <507F5A7E.6040206@arcanedomain.com> <50856E3C.103@gmail.com> <Pine.LNX.4.64.1210221753010.2471@ps20323.dreamhostps.com>
In-Reply-To: <Pine.LNX.4.64.1210221753010.2471@ps20323.dreamhostps.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: Noah Mendelsohn <nrm@arcanedomain.com>, mnot@mnot.net, URI <uri@w3.org>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Oct 2012 19:09:32 -0000

On 2012-10-22 19:55, Ian Hickson wrote:
> On Mon, 22 Oct 2012, Brian E Carpenter wrote:
>> On 18/10/2012 02:25, Noah Mendelsohn wrote:
>>> On 10/17/2012 7:57 PM, Ian Hickson wrote:
>>>> Yeah. Turns out we (the Web standards community) haven't been doing
>>>> such a great job of making our specificatiosn match reality.:-(
>>>
>>> Um, true... but it's also the case that the implementation community
>>> hasn't over the years been doing as much as might be best to make
>>> reality match the specifications. The new specs we're writing now
>>> would like have been a lot thinner and cleaner if they had.
>>
>> However, I think the concern here is that if certain IETF specs need to
>> be updated to match the real world, that work needs to be done in the
>> IETF.
>
> I couldn't agree more! We've been waiting for four years for the URI
> working group to get their act together and fix the URL mess. Nothing has
> happened. We lost patience and are now doing it ourselves.
> ...

Clarifying: there is no URI Working Group, and as far as I can tell, 
there is no consensus that there is a "mess" to fix related to URIs. 
There *is* indeed a *IRI* Working Group which planned to define things 
that occur in HTML links (including sanitizing whitespace and dealing 
with the problems with non-ASCII characters), and *that* WG indeed 
hasn't delivered yet.

Best regards, Julian

From dhc@dcrocker.net  Mon Oct 22 12:12:07 2012
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5942811E8097 for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 12:12:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1GzxAnOnYWyN for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 12:12:06 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 33D1011E808D for <ietf@ietf.org>; Mon, 22 Oct 2012 12:12:06 -0700 (PDT)
Received: from [10.101.1.120] ([206.205.237.234]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q9MJBscT009543 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 22 Oct 2012 12:11:55 -0700
Message-ID: <50859A72.3030105@dcrocker.net>
Date: Mon, 22 Oct 2012 15:11:46 -0400
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121010 Thunderbird/16.0.1
MIME-Version: 1.0
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Subject: IETF HOF vs. ISOC HOF
References: <20121022190358.7F7BF18C0B7@mercury.lcs.mit.edu>
In-Reply-To: <20121022190358.7F7BF18C0B7@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]); Mon, 22 Oct 2012 12:11:56 -0700 (PDT)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Oct 2012 19:12:07 -0000

On 10/22/2012 3:03 PM, Noel Chiappa wrote:
> But I still feel a mild level of need for a IETF HoF to recognize, and keep
> prominent (for new members) the memory of past IETFers whose contributions
> are worthy of recognition, but who probably don't rise to the level needed
> for more major honours (e.g. the ISOC Internet Hall of Fame).


Since ISOC recently initiated its own Hall of Fame effort, how would the 
IETF version be different and why?

d/

-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

From tytso@thunk.org  Mon Oct 22 12:45:48 2012
Return-Path: <tytso@thunk.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 D581121F84AB for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 12:45:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.343
X-Spam-Level: 
X-Spam-Status: No, score=-1.343 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_MISMATCH_ORG=0.611, HOST_MISMATCH_COM=0.311, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DlWf6mC6205p for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 12:45:48 -0700 (PDT)
Received: from imap.thunk.org (li9-11.members.linode.com [67.18.176.11]) by ietfa.amsl.com (Postfix) with ESMTP id 740E221F846C for <ietf@ietf.org>; Mon, 22 Oct 2012 12:45:47 -0700 (PDT)
Received: from root (helo=closure.thunk.org) by imap.thunk.org with local-esmtp (Exim 4.72) (envelope-from <tytso@thunk.org>) id 1TQNwR-0007XQ-GW; Mon, 22 Oct 2012 19:45:39 +0000
Received: by closure.thunk.org (Postfix, from userid 15806) id 15A3A2419CE; Mon, 22 Oct 2012 15:45:45 -0400 (EDT)
Date: Mon, 22 Oct 2012 15:45:45 -0400
From: Theodore Ts'o <tytso@mit.edu>
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Subject: Re: In Memoriam IETF web page
Message-ID: <20121022194545.GA11999@thunk.org>
References: <20121022190358.7F7BF18C0B7@mercury.lcs.mit.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20121022190358.7F7BF18C0B7@mercury.lcs.mit.edu>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Mail-From: tytso@thunk.org
X-SA-Exim-Scanned: No (on imap.thunk.org); SAEximRunCond expanded to 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: Mon, 22 Oct 2012 19:45:48 -0000

On Mon, Oct 22, 2012 at 03:03:58PM -0400, Noel Chiappa wrote:
> 
> But I still feel a mild level of need for a IETF HoF to recognize, and keep
> prominent (for new members) the memory of past IETFers whose contributions
> are worthy of recognition, but who probably don't rise to the level needed
> for more major honours (e.g. the ISOC Internet Hall of Fame).

Do we need to wait until someone who has made significant contribution
to have passed away before we recognize their contributions?  Many
other organizations give awards out to people while they are still
alive to receive the Usenix Flame Award, or the ACM Turing Award, or
whatever.

I wonder if we are conflating the concept of a memorial and a Hall of
Fame because many of the more deserving recipients that might deserve
recognition and would be awards that would have to be given
posthumously.

					- Ted

From steve@shinkuro.com  Mon Oct 22 13:25:05 2012
Return-Path: <steve@shinkuro.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7898B21F8949 for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 13:25:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.019
X-Spam-Level: 
X-Spam-Status: No, score=0.019 tagged_above=-999 required=5 tests=[BAYES_05=-1.11, HELO_EQ_DSL=1.129]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X2JPIIEJ1ZJj for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 13:25:05 -0700 (PDT)
Received: from execdsl.com (remote.shinkuro.com [50.56.68.178]) by ietfa.amsl.com (Postfix) with ESMTP id 05F0C21F8525 for <ietf@ietf.org>; Mon, 22 Oct 2012 13:25:04 -0700 (PDT)
Received: from [70.88.139.89] (account steve@shinkuro.com HELO [192.168.168.160]) by execdsl.com (CommuniGate Pro SMTP 5.1.16) with ESMTPSA id 20902648 for ietf@ietf.org; Mon, 22 Oct 2012 20:26:31 +0000
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: In Memoriam IETF web page -- a modest proposal
From: Steve Crocker <steve@shinkuro.com>
In-Reply-To: <20121022194545.GA11999@thunk.org>
Date: Mon, 22 Oct 2012 16:25:04 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <13E5830C-7323-4A7F-956A-2DD2CDB6D0AA@shinkuro.com>
References: <20121022190358.7F7BF18C0B7@mercury.lcs.mit.edu> <20121022194545.GA11999@thunk.org>
To: "ietf@ietf.org" <ietf@ietf.org>
X-Mailer: Apple Mail (2.1499)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Oct 2012 20:25:05 -0000

After watching the traffic on this, I'm thinking a memorial page is =
perhaps not the first place to focus attention.  Instead, write a =
memorial RFC for each person you think made a significant contribution =
to the IETF.  The RFC Editorial process will provide some vetting on =
quality.  Use Informational, Historic(!) or create a new class.

The memorial page can then list those who have memorial RFCs written for =
them.

Steve


From swb@internet2.edu  Mon Oct 22 13:34:22 2012
Return-Path: <swb@internet2.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 156AB21F8448 for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 13:34:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id T9Cyf4IkHMUE for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 13:34:21 -0700 (PDT)
Received: from int-proxy02.merit.edu (int-proxy02.merit.edu [207.75.116.231]) by ietfa.amsl.com (Postfix) with ESMTP id 9413921F8446 for <ietf@ietf.org>; Mon, 22 Oct 2012 13:34:21 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by int-proxy02.merit.edu (Postfix) with ESMTP id 4C0C5120448; Mon, 22 Oct 2012 16:34:21 -0400 (EDT)
X-Virus-Scanned: amavisd-new at int-proxy02.merit.edu
Received: from int-proxy02.merit.edu ([127.0.0.1]) by localhost (int-proxy02.merit.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XAYEZaGhqZq2; Mon, 22 Oct 2012 16:34:21 -0400 (EDT)
Received: from swbi2mbp.local (cpe-67-241-75-185.twcny.res.rr.com [67.241.75.185]) by int-proxy02.merit.edu (Postfix) with ESMTPSA id BD203120413; Mon, 22 Oct 2012 16:34:19 -0400 (EDT)
Message-ID: <5085ADC7.3020208@internet2.edu>
Date: Mon, 22 Oct 2012 16:34:15 -0400
From: Scott Brim <swb@internet2.edu>
Organization: Internet2
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:16.0) Gecko/20121010 Thunderbird/16.0.1
MIME-Version: 1.0
To: Steve Crocker <steve@shinkuro.com>
Subject: Re: In Memoriam IETF web page -- a modest proposal
References: <20121022190358.7F7BF18C0B7@mercury.lcs.mit.edu> <20121022194545.GA11999@thunk.org> <13E5830C-7323-4A7F-956A-2DD2CDB6D0AA@shinkuro.com>
In-Reply-To: <13E5830C-7323-4A7F-956A-2DD2CDB6D0AA@shinkuro.com>
X-Enigmail-Version: 1.4.5
Content-Type: text/plain; charset=ISO-8859-1
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, 22 Oct 2012 20:34:22 -0000

On 10/22/12 16:25, Steve Crocker allegedly wrote:
> After watching the traffic on this, I'm thinking a memorial page is perhaps not the first place to focus attention.  Instead, write a memorial RFC for each person you think made a significant contribution to the IETF.  The RFC Editorial process will provide some vetting on quality.  Use Informational, Historic(!) or create a new class.
> 
> The memorial page can then list those who have memorial RFCs written for them.
> 
> Steve

<like>

From stephen.farrell@cs.tcd.ie  Mon Oct 22 13:48:11 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 A87AB11E808D for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 13:48:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.479
X-Spam-Level: 
X-Spam-Status: No, score=-102.479 tagged_above=-999 required=5 tests=[AWL=0.120, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ue84ySEAE1YP for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 13:48:11 -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 35C121F041C for <ietf@ietf.org>; Mon, 22 Oct 2012 13:48:11 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hermes.scss.tcd.ie (Postfix) with ESMTP id 78D5710398A; Mon, 22 Oct 2012 21:48:10 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; h= content-transfer-encoding:content-type:in-reply-to:references :subject:mime-version:user-agent:from:date:message-id:received :received:x-virus-scanned; s=cs; t=1350938889; bh=FwWHlGDgggtEVq ctkYhWQRjhuxU110j28TQThiOqkHk=; b=uZoGQPNEmSev3TLCexWjpLAluvz4/C ztKX1aAC6rRdQANnfjXgHIH6jAPwuXoEUIVrd7SFT3s16SQdLyoyrQ/eKdAbwSGJ qzGux57dALq7QLAQkZ6q6LEN+DCIRUtTFRLXs/vH6x1Zcf5XjwZuZv1GOjH8T3ru ToNh78t0fbl0zA+026L223KVjYUxM/QkKUCIFG9FRRd/rgpmiuexW0P3fXteE157 Hyz0+QpGtZjNRze5Q3jm4EqqYhdEYlOMCmrl1JwD4MMnT+2A/vifwUJuNPu+wBbf BGb4AEH2J33w9zb1Zzw+QP2SdniKVFtS788o6D/dXuBF8KMaU2l11Xpw==
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 VywUDcmw5Lht; Mon, 22 Oct 2012 21:48:09 +0100 (IST)
Received: from [10.87.48.4] (unknown [86.45.58.1]) by smtp.scss.tcd.ie (Postfix) with ESMTPSA id A1841103988; Mon, 22 Oct 2012 21:48:09 +0100 (IST)
Message-ID: <5085B108.4030200@cs.tcd.ie>
Date: Mon, 22 Oct 2012 21:48:08 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20121017 Thunderbird/16.0.1
MIME-Version: 1.0
To: Henning Schulzrinne <hgs@cs.columbia.edu>
Subject: Re: In Memoriam IETF web page
References: <50842367.3040108@dcrocker.net> <61A98088-7151-43A1-95EE-85C327A3240C@vigilsec.com> <m2hapn35k0.wl%randy@psg.com> <12D99082-7020-42CF-BA94-A7D683587CBA@isoc.org> <A1029D11-E3D2-47DD-961A-CED1EB454DEF@cs.columbia.edu>
In-Reply-To: <A1029D11-E3D2-47DD-961A-CED1EB454DEF@cs.columbia.edu>
X-Enigmail-Version: 1.4.5
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Oct 2012 20:48:11 -0000

On 10/22/2012 03:52 PM, Henning Schulzrinne wrote:
> If we want to keep this in the spirit of long-established (newspaper) traditions rather than a web page, we could use the IETF Journal for recording the passing of members of the community.

This sounds like the best suggestion to me so far
if something is to be done. Second best would be
to do nothing.

S.

From lixia@cs.ucla.edu  Mon Oct 22 13:50:18 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 3CD5411E808D for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 13:50:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ji7MKGLzkFI3 for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 13:50:17 -0700 (PDT)
Received: from smtp.cs.ucla.edu (smtp.cs.ucla.edu [131.179.128.62]) by ietfa.amsl.com (Postfix) with ESMTP id B49A921F849D for <ietf@ietf.org>; Mon, 22 Oct 2012 13:50:17 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp.cs.ucla.edu (Postfix) with ESMTP id 2D050A60006; Mon, 22 Oct 2012 13:50:17 -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 KylXNQGtcKIf; Mon, 22 Oct 2012 13:50:16 -0700 (PDT)
Received: from dhcp-220-149.meetings.nanog.org (dhcp-220-149.meetings.nanog.org [199.187.220.149]) by smtp.cs.ucla.edu (Postfix) with ESMTPSA id B0560A60002; Mon, 22 Oct 2012 13:50:16 -0700 (PDT)
Subject: Re: In Memoriam IETF web page -- a modest proposal
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=us-ascii
From: Lixia Zhang <lixia@cs.ucla.edu>
In-Reply-To: <13E5830C-7323-4A7F-956A-2DD2CDB6D0AA@shinkuro.com>
Date: Mon, 22 Oct 2012 13:50:19 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <78E40B57-9C83-4CF8-8A26-71C391079DBD@cs.ucla.edu>
References: <20121022190358.7F7BF18C0B7@mercury.lcs.mit.edu> <20121022194545.GA11999@thunk.org> <13E5830C-7323-4A7F-956A-2DD2CDB6D0AA@shinkuro.com>
To: Steve Crocker <steve@shinkuro.com>
X-Mailer: Apple Mail (2.1283)
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Oct 2012 20:50:18 -0000

On Oct 22, 2012, at 1:25 PM, Steve Crocker wrote:

> After watching the traffic on this, I'm thinking a memorial page is =
perhaps not the first place to focus attention.  Instead, write a =
memorial RFC for each person you think made a significant contribution =
to the IETF.  The RFC Editorial process will provide some vetting on =
quality.  Use Informational, Historic(!) or create a new class.

like this idea, with a new category.

> The memorial page can then list those who have memorial RFCs written =
for them.

or we no longer need such a page, just an index to RFCs in this =
category.

Lixia

PS: Noel mentioned a few old names, like Licklider (maybe less than =
handful people on this list knew him), or Coya (unclear whether more =
people showing at Atlanta know the name, or the other way around) -- =
life moves forward fast, history fading away quickly, if we dont make an =
effort to put it in record.



From rwfranks@gmail.com  Mon Oct 22 14:47:57 2012
Return-Path: <rwfranks@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5BA1821F8504 for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 14:47:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.977
X-Spam-Level: 
X-Spam-Status: No, score=-102.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uBAsDhmw26ps for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 14:47:57 -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 AABC421F84C4 for <ietf@ietf.org>; Mon, 22 Oct 2012 14:47:56 -0700 (PDT)
Received: by mail-we0-f172.google.com with SMTP id u46so1952117wey.31 for <ietf@ietf.org>; Mon, 22 Oct 2012 14:47:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=es4Oq3cbH3uaAuWdG4JP7q97oDwkvKQip3p0OxAdGzU=; b=DhDTa5VupcZaFGbnx0L1URE44PXuGwsUm4PovgE48IgV/JMRWeOfvHa9j4Lu2n6X91 dlGanqfw7vbNEFRh2iXF8p+u69eFjNUd6TiKkIp1qbEs+xGyFV1lU8GyqT5IPjkcx6xd VFK5El21kXntw5fxluKnrWDLN9ICBtL8+rk9E/yyorKJsyQMgSENJyanIsBbvM+oc6D0 UpdZHkAIjj6RnqVUuoprKSiQTt6NNGTh1yZmvSOcn203X+JZtCLtDJSfWyMt1gLE8M+w Q/6EC2fbQ0VxZTby4eFcpojHk6SQyciMugWQhOL37uzHA8dO9yy5dAKhc28mGjzuz3ey Q3sw==
Received: by 10.180.8.41 with SMTP id o9mr24165780wia.3.1350942475675; Mon, 22 Oct 2012 14:47:55 -0700 (PDT)
MIME-Version: 1.0
Sender: rwfranks@gmail.com
Received: by 10.194.41.65 with HTTP; Mon, 22 Oct 2012 14:47:35 -0700 (PDT)
In-Reply-To: <13E5830C-7323-4A7F-956A-2DD2CDB6D0AA@shinkuro.com>
References: <20121022190358.7F7BF18C0B7@mercury.lcs.mit.edu> <20121022194545.GA11999@thunk.org> <13E5830C-7323-4A7F-956A-2DD2CDB6D0AA@shinkuro.com>
From: Dick Franks <rwfranks@acm.org>
Date: Mon, 22 Oct 2012 22:47:35 +0100
X-Google-Sender-Auth: lItWSE2eSWz41PsM9IQnlroLBEY
Message-ID: <CAKW6Ri7u+wrBgQTfHbT0pJxXrM4bW3toZjv7Ba9X8uYqndN0jQ@mail.gmail.com>
Subject: Re: In Memoriam IETF web page -- a modest proposal
To: Steve Crocker <steve@shinkuro.com>
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: Mon, 22 Oct 2012 21:47:57 -0000

On 22 October 2012 21:25, Steve Crocker <steve@shinkuro.com> wrote:
> After watching the traffic on this, I'm thinking a memorial page is perha=
ps not the first place to focus attention.  Instead, write a memorial RFC f=
or each person you think made a significant contribution to the IETF.  The =
RFC Editorial process will provide some vetting on quality.  Use Informatio=
nal, Historic(!) or create a new class.
>
> The memorial page can then list those who have memorial RFCs written for =
them.

OBITWG will need a charter, chair and mailing list.

From tbray@textuality.com  Mon Oct 22 15:11:40 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 02E9711E80EA for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 15:11:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.976
X-Spam-Level: 
X-Spam-Status: No, score=-2.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nr0u7FCfXn8u for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 15:11:39 -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 5D25F11E80E2 for <ietf@ietf.org>; Mon, 22 Oct 2012 15:11:39 -0700 (PDT)
Received: by mail-ob0-f172.google.com with SMTP id v19so3502454obq.31 for <ietf@ietf.org>; Mon, 22 Oct 2012 15:11:39 -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:x-gm-message-state; bh=hoxEWBClCdiJjME5SzedjPD+3ycSwNWfJljWNJQcBxE=; b=BIeRf6inyrjY7Xq1JaMAhvdMNNCtfBOiEc9cpEudnIK6btRsh742mEwLsoPUkzxcpV tBBFpvBg60mI9fiWa/9UaJJP/Evz2F9punti8DAhpKg8Ani3oP1XaW3emlo4l+WyVlYa fxPuxKGuk/pje8WjfDzZ2fITxjckEDtFa4K5zYsSunnc17n24XwaEbR8GKyYA/zcLGtZ zaEk8wKGCfDv1mjtqEds8IqZAksOCBU2evuWMnT5WchzrVSezrQe4T/gZV26LO76yAGc PbCRv/lY/1D0i0WBN2EPascD/qnLWqF27cf1b2zVXDNC/+LqIu3+c0fJF6fd9VU7Bv6N RlHw==
MIME-Version: 1.0
Received: by 10.182.146.46 with SMTP id sz14mr8201898obb.76.1350943898883; Mon, 22 Oct 2012 15:11:38 -0700 (PDT)
Received: by 10.76.87.136 with HTTP; Mon, 22 Oct 2012 15:11:38 -0700 (PDT)
X-Originating-IP: [2620:0:1000:5e03:8146:c08:57ba:8c50]
In-Reply-To: <Pine.LNX.4.64.1210222137530.2471@ps20323.dreamhostps.com>
References: <50604C1A.7090901@gmx.de> <5060A964.5060001@stpeter.im> <Pine.LNX.4.64.1210172354500.2478@ps20323.dreamhostps.com> <507F5A7E.6040206@arcanedomain.com> <50856E3C.103@gmail.com> <Pine.LNX.4.64.1210221753010.2471@ps20323.dreamhostps.com> <0DBC8A11-319C-4120-975E-7E40FD5818BF@gbiv.com> <Pine.LNX.4.64.1210222137530.2471@ps20323.dreamhostps.com>
Date: Mon, 22 Oct 2012 15:11:38 -0700
Message-ID: <CAHBU6isuainUDbAMPTjGJ3rQEE8Ru22ufMKDNDHWxbGLk4T8pg@mail.gmail.com>
Subject: Re: [whatwg] New URL Standard from Anne van Kesteren on 2012-09-24 (public-whatwg-archive@w3.org from September 2012)
From: Tim Bray <tbray@textuality.com>
To: Ian Hickson <ian@hixie.ch>
Content-Type: multipart/alternative; boundary=f46d0444e92b3454ff04ccad234f
X-Gm-Message-State: ALoCoQkqV5THtgUcgq5RS4uLS63rxYuYNcJUQlQjKW6vbkf6O+zCZB/cKIT8y49jsDJFSrFN7by5
Cc: IETF Discussion <ietf@ietf.org>, Julian Reschke <julian.reschke@gmx.de>, "Roy T. Fielding" <fielding@gbiv.com>, mnot@mnot.net, Noah Mendelsohn <nrm@arcanedomain.com>, URI <uri@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: Mon, 22 Oct 2012 22:11:40 -0000

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

On Mon, Oct 22, 2012 at 2:46 PM, Ian Hickson <ian@hixie.ch> wrote:

> On Mon, 22 Oct 2012, Roy T. Fielding wrote:
>>
>> What you are insisting on defining as a "URL" is the input to the
>> process of making a hypertext reference (the arbitrary string typed into
>> a dialog or placed inside an href/src attribute)
>
> Or placed on a command line to wget(1), or put in an RDFa triple store, or
> in transmitted in an HTTP Location: header, or...

It seems reasonable that someone should write rules for dealing with the
kinds of errors that are observed to occur in links as embedded in resource
representations AKA HTML pages.  It also seems reasonable that WHATWG, who
speak (if I understand correctly) for browser builders, can write those
rules.

The notion that curl, or an HTTP cache manager, or an XML namespace
processor, is going to be routing around errors, strikes me on the face of
it as being wrong.  One of the main uses I put curl to is making sure I
have the URL exactly right before I drop it into chat or whatever.   -T

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

On Mon, Oct 22, 2012 at 2:46 PM, Ian Hickson &lt;<a href=3D"mailto:ian@hixi=
e.ch">ian@hixie.ch</a>&gt; wrote:<br><br>&gt; On Mon, 22 Oct 2012, Roy T. F=
ielding wrote:<br>&gt;&gt;<br>&gt;&gt; What you are insisting on defining a=
s a &quot;URL&quot; is the input to the<br>
&gt;&gt; process of making a hypertext reference (the arbitrary string type=
d into<br>&gt;&gt; a dialog or placed inside an href/src attribute)<br>&gt;=
<br>&gt; Or placed on a command line to wget(1), or put in an RDFa triple s=
tore, or<br>
&gt; in transmitted in an HTTP Location: header, or...<br><br>It seems reas=
onable that someone should write rules for dealing with the kinds of errors=
 that are observed to occur in links as embedded in resource representation=
s AKA HTML pages. =A0It also seems reasonable that WHATWG, who speak (if I =
understand correctly) for browser builders, can write those rules.<br>
<br>The notion that curl, or an HTTP cache manager, or an XML namespace pro=
cessor, is going to be routing around errors, strikes me on the face of it =
as being wrong. =A0One of the main uses I put curl to is making sure I have=
 the URL exactly right before I drop it into chat or whatever.=A0=A0 -T<br>
<br><br>

--f46d0444e92b3454ff04ccad234f--

From julian.reschke@gmx.de  Mon Oct 22 15:12:14 2012
Return-Path: <julian.reschke@gmx.de>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A715D11E80DE for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 15:12:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.438
X-Spam-Level: 
X-Spam-Status: No, score=-103.438 tagged_above=-999 required=5 tests=[AWL=-0.839, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BgvEkmROyb2S for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 15:12:14 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by ietfa.amsl.com (Postfix) with SMTP id 8619B11E80BA for <ietf@ietf.org>; Mon, 22 Oct 2012 15:12:13 -0700 (PDT)
Received: (qmail invoked by alias); 22 Oct 2012 22:12:12 -0000
Received: from p5DD95D63.dip.t-dialin.net (EHLO [192.168.178.36]) [93.217.93.99] by mail.gmx.net (mp038) with SMTP; 23 Oct 2012 00:12:12 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1/eKegEy1De4aCYdzOPUs8Yrbl0sOjQHK6ib5xJ2W rsHWEs5QQzJiQp
Message-ID: <5085C4BA.2030505@gmx.de>
Date: Tue, 23 Oct 2012 00:12:10 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121010 Thunderbird/16.0.1
MIME-Version: 1.0
To: Ian Hickson <ian@hixie.ch>
Subject: Re: [whatwg] New URL Standard from Anne van Kesteren on 2012-09-24 (public-whatwg-archive@w3.org from September 2012)
References: <50604C1A.7090901@gmx.de> <5060A964.5060001@stpeter.im> <Pine.LNX.4.64.1210172354500.2478@ps20323.dreamhostps.com> <507F5A7E.6040206@arcanedomain.com> <50856E3C.103@gmail.com> <Pine.LNX.4.64.1210221753010.2471@ps20323.dreamhostps.com> <0DBC8A11-319C-4120-975E-7E40FD5818BF@gbiv.com> <Pine.LNX.4.64.1210222137530.2471@ps20323.dreamhostps.com>
In-Reply-To: <Pine.LNX.4.64.1210222137530.2471@ps20323.dreamhostps.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>, Noah Mendelsohn <nrm@arcanedomain.com>, "Roy T. Fielding" <fielding@gbiv.com>, URI <uri@w3.org>, mnot@mnot.net
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Oct 2012 22:12:14 -0000

On 2012-10-22 23:46, Ian Hickson wrote:
> On Mon, 22 Oct 2012, Julian Reschke wrote:
>>>
>>> I couldn't agree more! We've been waiting for four years for the URI
>>> working group to get their act together and fix the URL mess. Nothing
>>> has happened. We lost patience and are now doing it ourselves. ...
>>
>> Clarifying: there is no URI Working Group, and as far as I can tell,
>
> Whoever. The people complaining that it should be done at the IETF haven't
> done any work. That's the complaint. Until they do the work, complaining
> that we're doing it instead is going to fall on deaf ears and be met with
> the rolling of eyeballs.

This always was about venue, not people. If people want to "fix" or 
"augment" URIs/IRIs, they should come over to the IETF. That's where the 
specs live. The IETF is open to anyone, works async on mailing lists, 
and doesn't require any membership fees. I don't think there's any 
standards body that is *more* open to individuals.

But yes, you may have to convince a few people outside the WhatWG. 
That's a feature. It means more review from people outside the browser 
ecosystem.

>> there is no consensus that there is a "mess" to fix related to URIs.
>
> The specs don't define everything that implementations have to do to be
> interoperable. If the IETF doesn't think that's a problem, then that's
> fine, but then y'all shouldn't be surprised when people who _do_ think
> that's a problem try and fix it.

Yes, please fix *that*, but *just* that without messing with the basics 
without consensus/review.

So yes: if you feel you need to make \ to equivalent to /, that may be 
ok (as \ isn't valid anyway). But changing the reference resolution 
algorithm for valid URI/reference pairs is something entirely different. 
*If* it needs to be done, it needs to be done within the scope of the 
URI spec.

Best regards, Julian

From mnot@mnot.net  Mon Oct 22 15:14:42 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 065BA21F8972 for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 15:14:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.069
X-Spam-Level: 
X-Spam-Status: No, score=-104.069 tagged_above=-999 required=5 tests=[AWL=-1.470, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BugYT2+Z3lt0 for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 15:14:41 -0700 (PDT)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) by ietfa.amsl.com (Postfix) with ESMTP id 26C4321F894D for <ietf@ietf.org>; Mon, 22 Oct 2012 15:14:41 -0700 (PDT)
Received: from [192.168.1.72] (unknown [118.209.87.82]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 7651822E25C; Mon, 22 Oct 2012 18:14:28 -0400 (EDT)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: [whatwg] New URL Standard from Anne van Kesteren on 2012-09-24 (public-whatwg-archive@w3.org from September 2012)
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <CAHBU6isuainUDbAMPTjGJ3rQEE8Ru22ufMKDNDHWxbGLk4T8pg@mail.gmail.com>
Date: Tue, 23 Oct 2012 09:14:26 +1100
Content-Transfer-Encoding: quoted-printable
Message-Id: <3DC03673-7283-4D7C-8578-DEFAE047BE99@mnot.net>
References: <50604C1A.7090901@gmx.de> <5060A964.5060001@stpeter.im> <Pine.LNX.4.64.1210172354500.2478@ps20323.dreamhostps.com> <507F5A7E.6040206@arcanedomain.com> <50856E3C.103@gmail.com> <Pine.LNX.4.64.1210221753010.2471@ps20323.dreamhostps.com> <0DBC8A11-319C-4120-975E-7E40FD5818BF@gbiv.com> <Pine.LNX.4.64.1210222137530.2471@ps20323.dreamhostps.com> <CAHBU6isuainUDbAMPTjGJ3rQEE8Ru22ufMKDNDHWxbGLk4T8pg@mail.gmail.com>
To: Tim Bray <tbray@textuality.com>
X-Mailer: Apple Mail (2.1499)
Cc: IETF Discussion <ietf@ietf.org>, Julian Reschke <julian.reschke@gmx.de>, "Roy T. Fielding" <fielding@gbiv.com>, Noah Mendelsohn <nrm@arcanedomain.com>, URI <uri@w3.org>, Ian Hickson <ian@hixie.ch>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Oct 2012 22:14:42 -0000

On 23/10/2012, at 9:11 AM, Tim Bray <tbray@textuality.com> wrote:

> It seems reasonable that someone should write rules for dealing with =
the kinds of errors that are observed to occur in links as embedded in =
resource representations AKA HTML pages.  It also seems reasonable that =
WHATWG, who speak (if I understand correctly) for browser builders, can =
write those rules.

+1. The work seems obviously necessary, the confusion is around why this =
is being couched in terms of redefining URIs, rather than just defining =
it as "how you get to a URI (or an unrecoverable error) from an =
arbitrary string."

Cheers,

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




From turchanyi.geza@gmail.com  Mon Oct 22 15:35:22 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 40AAA11E80FD for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 15:35:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RsCekEH19cn2 for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 15:35:21 -0700 (PDT)
Received: from mail-da0-f44.google.com (mail-da0-f44.google.com [209.85.210.44]) by ietfa.amsl.com (Postfix) with ESMTP id 9EBE111E80F6 for <ietf@ietf.org>; Mon, 22 Oct 2012 15:35:20 -0700 (PDT)
Received: by mail-da0-f44.google.com with SMTP id h15so1586065dan.31 for <ietf@ietf.org>; Mon, 22 Oct 2012 15:35: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:date:message-id:subject:from:to :cc:content-type; bh=DmJlpGZiuxdzkb2hj7kZc8f0RqliusJCHEOdIIikLqo=; b=seXmMlw4H+xBwL/vnvzDcdNG2qeuGIbY1BEwZTS95SVFcDrmEWc6ncq2aZ7Yw37MrR Zjmzw9aK0OPKarXqsPCx8L5ef1SXFSM3l4YHgQ0aCrL7g6CxqRl37XiyUJ3maN2NsLOt r6SLLPiaVDL+ElYYn57ZSo5tJZQ15c7K/DKNi9WbMDReK9N4f3xni4eVeL0MWFY6+V2L fmePKzSOrMx5gL8ZNuJD8AKEP+iemSwPZa9ti87t7y/Wa6xFMn/QlIquPwKD/7IxOQBL Lg9i8Joy5GsYCojceaK5TuePYJDTITSa4w2bu/PMTd0GlRwPLecHMKfK2AngUHxFRYIP XDig==
MIME-Version: 1.0
Received: by 10.66.77.74 with SMTP id q10mr29504089paw.81.1350945303661; Mon, 22 Oct 2012 15:35:03 -0700 (PDT)
Received: by 10.66.19.135 with HTTP; Mon, 22 Oct 2012 15:35:03 -0700 (PDT)
In-Reply-To: <CAKW6Ri7u+wrBgQTfHbT0pJxXrM4bW3toZjv7Ba9X8uYqndN0jQ@mail.gmail.com>
References: <20121022190358.7F7BF18C0B7@mercury.lcs.mit.edu> <20121022194545.GA11999@thunk.org> <13E5830C-7323-4A7F-956A-2DD2CDB6D0AA@shinkuro.com> <CAKW6Ri7u+wrBgQTfHbT0pJxXrM4bW3toZjv7Ba9X8uYqndN0jQ@mail.gmail.com>
Date: Tue, 23 Oct 2012 00:35:03 +0200
Message-ID: <CAJfR-+M_DmQO4iTzxH=ZgnnTuZc5nJZu4b+f_19zCsM5MAM_fA@mail.gmail.com>
Subject: Re: In Memoriam IETF web page -- a modest proposal
From: Turchanyi Geza <turchanyi.geza@gmail.com>
To: Dick Franks <rwfranks@acm.org>
Content-Type: multipart/alternative; boundary=f46d042fdddeef8c2904ccad7611
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Oct 2012 22:35:22 -0000

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

Dick and Steve,


On Mon, Oct 22, 2012 at 11:47 PM, Dick Franks <rwfranks@acm.org> wrote:

> On 22 October 2012 21:25, Steve Crocker <steve@shinkuro.com> wrote:
> > After watching the traffic on this, I'm thinking a memorial page is
> perhaps not the first place to focus attention.  Instead, write a memoria=
l
> RFC for each person you think made a significant contribution to the IETF=
.
>  The RFC Editorial process will provide some vetting on quality.  Use
> Informational, Historic(!) or create a new class.
> >
> > The memorial page can then list those who have memorial RFCs written fo=
r
> them.
>
> OBITWG will need a charter, chair and mailing list.
>

I like Steve's idea, however, not exactly like the idea to set up a
permanent working group. Perhaps it would be better to form a "working
group" case by case, each "wg" focusing only on the merits of one
individual. However, I am not sure, that a wg would be a right form, anyhow=
,

I would prefer individual submissions, may be more than one
submission/person.

G=E9za
(author of a book about heros of networking in Hungary)

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

Dick and Steve,<br><br><br><div class=3D"gmail_quote">On Mon, Oct 22, 2012 =
at 11:47 PM, Dick Franks <span dir=3D"ltr">&lt;<a href=3D"mailto:rwfranks@a=
cm.org" target=3D"_blank">rwfranks@acm.org</a>&gt;</span> wrote:<br><blockq=
uote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc =
solid;padding-left:1ex">
<div class=3D"im">On 22 October 2012 21:25, Steve Crocker &lt;<a href=3D"ma=
ilto:steve@shinkuro.com">steve@shinkuro.com</a>&gt; wrote:<br>
&gt; After watching the traffic on this, I&#39;m thinking a memorial page i=
s perhaps not the first place to focus attention. =A0Instead, write a memor=
ial RFC for each person you think made a significant contribution to the IE=
TF. =A0The RFC Editorial process will provide some vetting on quality. =A0U=
se Informational, Historic(!) or create a new class.<br>

&gt;<br>
&gt; The memorial page can then list those who have memorial RFCs written f=
or them.<br>
<br>
</div>OBITWG will need a charter, chair and mailing list.<br></blockquote><=
div><br>I like Steve&#39;s idea, however, not exactly like the idea to set =
up a permanent working group. Perhaps it would be better to form a &quot;wo=
rking group&quot; case by case, each &quot;wg&quot; focusing only on the me=
rits of one individual. However, I am not sure, that a wg would be a right =
form, anyhow,<br>
<br>I would prefer individual submissions, may be more than one submission/=
person.<br><br>G=E9za<br>(author of a book about heros of networking in Hun=
gary) <br></div></div><br>

--f46d042fdddeef8c2904ccad7611--

From mnot@mnot.net  Mon Oct 22 15:40:06 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 7A35211E80EA for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 15:40:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.019
X-Spam-Level: 
X-Spam-Status: No, score=-104.019 tagged_above=-999 required=5 tests=[AWL=-1.420, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KWiXWAWNZC7e for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 15:40:05 -0700 (PDT)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) by ietfa.amsl.com (Postfix) with ESMTP id 5CFC911E80F7 for <ietf@ietf.org>; Mon, 22 Oct 2012 15:39:55 -0700 (PDT)
Received: from [192.168.1.72] (unknown [118.209.87.82]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id ABF8C22E25C; Mon, 22 Oct 2012 18:39:45 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: [whatwg] New URL Standard from Anne van Kesteren on 2012-09-24 (public-whatwg-archive@w3.org from September 2012)
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <Pine.LNX.4.64.1210222220510.2471@ps20323.dreamhostps.com>
Date: Tue, 23 Oct 2012 09:39:44 +1100
Content-Transfer-Encoding: quoted-printable
Message-Id: <16D9CBB2-45EF-418F-96ED-7A62CE399345@mnot.net>
References: <50604C1A.7090901@gmx.de> <5060A964.5060001@stpeter.im> <Pine.LNX.4.64.1210172354500.2478@ps20323.dreamhostps.com> <507F5A7E.6040206@arcanedomain.com> <50856E3C.103@gmail.com> <Pine.LNX.4.64.1210221753010.2471@ps20323.dreamhostps.com> <0DBC8A11-319C-4120-975E-7E40FD5818BF@gbiv.com> <Pine.LNX.4.64.1210222137530.2471@ps20323.dreamhostps.com> <5085C4BA.2030505@gmx.de> <Pine.LNX.4.64.1210222220510.2471@ps20323.dreamhostps.com>
To: Ian Hickson <ian@hixie.ch>
X-Mailer: Apple Mail (2.1499)
Cc: IETF Discussion <ietf@ietf.org>, Julian Reschke <julian.reschke@gmx.de>, "Roy T. Fielding" <fielding@gbiv.com>, Jan Algermissen <jan.algermissen@nordsc.com>, Noah Mendelsohn <nrm@arcanedomain.com>, URI <uri@w3.org>, Tim Bray <tbray@textuality.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Oct 2012 22:40:06 -0000

On 23/10/2012, at 9:35 AM, Ian Hickson <ian@hixie.ch> wrote:

> Consensus isn't a value I hold highly, but review of Anne's work is=20
> welcome.
>=20
> If the IETF community didn't want Anne to do this work, then the IETF=20=

> community should have done it. Having not done it, having not even=20
> understood that the problem exists, means the IETF has lost the=20
> credibility it needs to claim that this is in the IETF's domain.
>=20
> You don't get to claim authority over an area while at the same time=20=

> telling someone else "please fix that" for the hard work that comes =
with=20
> that area. The reality is, he who does the hard work, gets the =
authority.

All very interesting, but please address the point that's now been made =
repeatedly -- why is it necessary for you to redefine URIs, rather than =
doing as we suggest?

Regards,

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




From tbray@textuality.com  Mon Oct 22 16:17:34 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 2DA2E11E80FB for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 16:17:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.976
X-Spam-Level: 
X-Spam-Status: No, score=-2.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3s3hED+SpqRA for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 16:17:30 -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 00FBD11E80F4 for <ietf@ietf.org>; Mon, 22 Oct 2012 16:17:29 -0700 (PDT)
Received: by mail-ob0-f172.google.com with SMTP id v19so3553465obq.31 for <ietf@ietf.org>; Mon, 22 Oct 2012 16:17:29 -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:x-gm-message-state; bh=wN7gFXNILJCq1rrXHmx2TKbFkrCer5GkCYwh6ffms/I=; b=HbVwMdO299WLkVjsp0EuV2JQ1Is+RfWd6/XS/ZNbyLsfmtkLAWVvfIFRHfgUU+equU bO9xvsunVQua2ZFQF11BXBFAP8n1eVUJlAzZMWYKXShSXMGsGnk+XS5JSgzILEqgEd69 31fR+mJWPYngk5ImFgPrPVn++t+RHlY2yBctOymFb4foITgxhSZBdgEQNjNzPbjsf1fs yEpSmlnVcVnVDcQoNyhVIVsvDfNL9aV/kNJozoTgV7cp0d02iki7BbYqlhl0sdj+EL1B nAenoU0zV+dv131zLDWqG2jUTI6KViqUDfbDs7I4Zs5EpI249RPovTe7PDpQL80XtAJt ba1A==
MIME-Version: 1.0
Received: by 10.60.13.198 with SMTP id j6mr9488477oec.51.1350947849174; Mon, 22 Oct 2012 16:17:29 -0700 (PDT)
Received: by 10.76.87.136 with HTTP; Mon, 22 Oct 2012 16:17:29 -0700 (PDT)
X-Originating-IP: [2620:0:1000:5e03:8146:c08:57ba:8c50]
In-Reply-To: <Pine.LNX.4.64.1210222220510.2471@ps20323.dreamhostps.com>
References: <50604C1A.7090901@gmx.de> <5060A964.5060001@stpeter.im> <Pine.LNX.4.64.1210172354500.2478@ps20323.dreamhostps.com> <507F5A7E.6040206@arcanedomain.com> <50856E3C.103@gmail.com> <Pine.LNX.4.64.1210221753010.2471@ps20323.dreamhostps.com> <0DBC8A11-319C-4120-975E-7E40FD5818BF@gbiv.com> <Pine.LNX.4.64.1210222137530.2471@ps20323.dreamhostps.com> <5085C4BA.2030505@gmx.de> <Pine.LNX.4.64.1210222220510.2471@ps20323.dreamhostps.com>
Date: Mon, 22 Oct 2012 16:17:29 -0700
Message-ID: <CAHBU6is8LNZ7Rq-vwLuOm+8ThKB9c=QPwbUfQwDQD5bDPjtf7w@mail.gmail.com>
Subject: Re: [whatwg] New URL Standard from Anne van Kesteren on 2012-09-24 (public-whatwg-archive@w3.org from September 2012)
From: Tim Bray <tbray@textuality.com>
To: Ian Hickson <ian@hixie.ch>
Content-Type: multipart/alternative; boundary=e89a8ff253d2a8ff5b04ccae0e31
X-Gm-Message-State: ALoCoQkRKiK0FA3FTTffbWpNpcqzac78gzRxwup/AzdFidf1GY+Xsf9j6NRwsip/xeKACdKlWprn
Cc: IETF Discussion <ietf@ietf.org>, Julian Reschke <julian.reschke@gmx.de>, "Roy T. Fielding" <fielding@gbiv.com>, Jan Algermissen <jan.algermissen@nordsc.com>, mnot@mnot.net, Noah Mendelsohn <nrm@arcanedomain.com>, URI <uri@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: Mon, 22 Oct 2012 23:17:34 -0000

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

On Mon, Oct 22, 2012 at 3:35 PM, Ian Hickson <ian@hixie.ch> wrote:

> > The notion that curl, or an HTTP cache manager, or an XML namespace
> > processor, is going to be routing around errors, strikes me on the face
> > of it as being wrong.  One of the main uses I put curl to is making sur=
e
> > I have the URL exactly right before I drop it into chat or whatever.
>
>    $ wget 'http://example.com/a b'
>    --2012-10-23 00:27:43--  http://example.com/a%20b
>
>    # test.cgi returns a 301 with "Location: a b"
>    $ curl -L
> http://damowmow.com/playground/demos/url/in-http-headers/test.cgi
>    This file is:
> http://damowmow.com/playground/demos/url/in-http-headers/a%20b
>
> Software does this stuff already. We need to make sure it does it
> interoperably.
>

Hmm.  I went to tbray.org and made a file at '$ROOT_DIR/tmp/a b' - note the
space.

Then I did

curl -I 'http://www.tbray.org/tmp/a%20b'
curl -I 'http://www.tbray.org/tmp/a b'

Curl, quite properly, doesn=92t fuck with what I ask it, and revealed a ver=
y
interesting fact: That my Apache httpd returns 200 for both of these, but,
with, uh, interesting variations, amounting to what I think is quite
possibly a bug.  I also pasted the version with the space into the nearest
Web browser, and it quite properly auto-corrected to a%20b.

I think it=92s a bug that curl is claiming the 301 pointed at "a%20b" not "=
a
b".  Because suppose it had pointed at "a%20b" - I don=92t want middleware
lying to me.

It seems like a good idea to document the steps by which "a b" pasted in
becomes "a%20b" in the address bar. But I don=92t see the relevance outside
human-authored strings.  -T


>
>
> On Tue, 23 Oct 2012, Julian Reschke wrote:
> >
> > This always was about venue, not people. If people want to "fix" or
> > "augment" URIs/IRIs, they should come over to the IETF.
>
> I think the person doing the work has the prerogative to do it wherever h=
e
> or she wants to do it. Maybe the IETF should consider why Anne isn't doin=
g
> it in the IETF.
>
>
> > > The specs don't define everything that implementations have to do to
> > > be interoperable. If the IETF doesn't think that's a problem, then
> > > that's fine, but then y'all shouldn't be surprised when people who
> > > _do_ think that's a problem try and fix it.
> >
> > Yes, please fix *that*, but *just* that without messing with the basics
> > without consensus/review.
>
> Consensus isn't a value I hold highly, but review of Anne's work is
> welcome.
>
> If the IETF community didn't want Anne to do this work, then the IETF
> community should have done it. Having not done it, having not even
> understood that the problem exists, means the IETF has lost the
> credibility it needs to claim that this is in the IETF's domain.
>
> You don't get to claim authority over an area while at the same time
> telling someone else "please fix that" for the hard work that comes with
> that area. The reality is, he who does the hard work, gets the authority.
>
> --
> Ian Hickson               U+1047E                )\._.,--....,'``.    fL
> http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
> Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
>

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

On Mon, Oct 22, 2012 at 3:35 PM, Ian Hickson <span dir=3D"ltr">&lt;<a href=
=3D"mailto:ian@hixie.ch" target=3D"_blank">ian@hixie.ch</a>&gt;</span> wrot=
e:<br><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D=
"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
&gt; The notion that curl, or an HTTP cache manager, or an XML namespace<br=
><div class=3D"im">
&gt; processor, is going to be routing around errors, strikes me on the fac=
e<br>
&gt; of it as being wrong. =A0One of the main uses I put curl to is making =
sure<br>
&gt; I have the URL exactly right before I drop it into chat or whatever.<b=
r>
<br>
</div>=A0 =A0$ wget &#39;<a href=3D"http://example.com/a" target=3D"_blank"=
>http://example.com/a</a> b&#39;<br>
=A0 =A0--2012-10-23 00:27:43-- =A0<a href=3D"http://example.com/a%20b" targ=
et=3D"_blank">http://example.com/a%20b</a><br>
<br>
=A0 =A0# test.cgi returns a 301 with &quot;Location: a b&quot;<br>
=A0 =A0$ curl -L <a href=3D"http://damowmow.com/playground/demos/url/in-htt=
p-headers/test.cgi" target=3D"_blank">http://damowmow.com/playground/demos/=
url/in-http-headers/test.cgi</a><br>
=A0 =A0This file is: <a href=3D"http://damowmow.com/playground/demos/url/in=
-http-headers/a%20b" target=3D"_blank">http://damowmow.com/playground/demos=
/url/in-http-headers/a%20b</a><br>
<br>
Software does this stuff already. We need to make sure it does it<br>
interoperably.<br></blockquote><div><br>Hmm.=A0 I went to <a href=3D"http:/=
/tbray.org">tbray.org</a> and made a file at &#39;$ROOT_DIR/tmp/a b&#39; - =
note the space.<br><br>Then I did <br><br>curl -I &#39;<a href=3D"http://ww=
w.tbray.org/tmp/a%20b">http://www.tbray.org/tmp/a%20b</a>&#39;<br>
curl -I &#39;<a href=3D"http://www.tbray.org/tmp/a">http://www.tbray.org/tm=
p/a</a> b&#39;<br><br>Curl, quite properly, doesn=92t fuck with what I ask =
it, and revealed a very interesting fact: That my Apache httpd returns 200 =
for both of these, but, with, uh, interesting variations, amounting to what=
 I think is quite possibly a bug.=A0 I also pasted the version with the spa=
ce into the nearest Web browser, and it quite properly auto-corrected to a%=
20b.=A0 <br>
<br>I think it=92s a bug that curl is claiming the 301 pointed at &quot;a%2=
0b&quot; not &quot;a b&quot;.=A0 Because suppose it had pointed at &quot;a%=
20b&quot; - I don=92t want middleware lying to me.<br><br>It seems like a g=
ood idea to document the steps by which &quot;a b&quot; pasted in becomes &=
quot;a%20b&quot; in the address bar. But I don=92t see the relevance outsid=
e human-authored strings.=A0 -T<br>
=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;borde=
r-left:1px #ccc solid;padding-left:1ex">
<div class=3D"im"><br>
<br>
On Tue, 23 Oct 2012, Julian Reschke wrote:<br>
&gt;<br>
&gt; This always was about venue, not people. If people want to &quot;fix&q=
uot; or<br>
&gt; &quot;augment&quot; URIs/IRIs, they should come over to the IETF.<br>
<br>
</div>I think the person doing the work has the prerogative to do it wherev=
er he<br>
or she wants to do it. Maybe the IETF should consider why Anne isn&#39;t do=
ing<br>
it in the IETF.<br>
<div class=3D"im"><br>
<br>
&gt; &gt; The specs don&#39;t define everything that implementations have t=
o do to<br>
&gt; &gt; be interoperable. If the IETF doesn&#39;t think that&#39;s a prob=
lem, then<br>
&gt; &gt; that&#39;s fine, but then y&#39;all shouldn&#39;t be surprised wh=
en people who<br>
&gt; &gt; _do_ think that&#39;s a problem try and fix it.<br>
&gt;<br>
&gt; Yes, please fix *that*, but *just* that without messing with the basic=
s<br>
&gt; without consensus/review.<br>
<br>
</div>Consensus isn&#39;t a value I hold highly, but review of Anne&#39;s w=
ork is<br>
welcome.<br>
<br>
If the IETF community didn&#39;t want Anne to do this work, then the IETF<b=
r>
community should have done it. Having not done it, having not even<br>
understood that the problem exists, means the IETF has lost the<br>
credibility it needs to claim that this is in the IETF&#39;s domain.<br>
<br>
You don&#39;t get to claim authority over an area while at the same time<br=
>
telling someone else &quot;please fix that&quot; for the hard work that com=
es with<br>
that area. The reality is, he who does the hard work, gets the authority.<b=
r>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
--<br>
Ian Hickson =A0 =A0 =A0 =A0 =A0 =A0 =A0 U+1047E =A0 =A0 =A0 =A0 =A0 =A0 =A0=
 =A0)\._.,--....,&#39;``. =A0 =A0fL<br>
<a href=3D"http://ln.hixie.ch/" target=3D"_blank">http://ln.hixie.ch/</a> =
=A0 =A0 =A0 U+263A =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0/, =A0 _.. \ =A0 _\ =A0;`=
._ ,.<br>
Things that are impossible just take longer. =A0 `._.-(,_..&#39;--(,_..&#39=
;`-.;.&#39;<br>
</div></div></blockquote></div><br>

--e89a8ff253d2a8ff5b04ccae0e31--

From mnot@mnot.net  Mon Oct 22 16:33:06 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 7172021F890F for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 16:33:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.096
X-Spam-Level: 
X-Spam-Status: No, score=-104.096 tagged_above=-999 required=5 tests=[AWL=-1.497, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id M6dRNHfIKLf8 for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 16:33:05 -0700 (PDT)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) by ietfa.amsl.com (Postfix) with ESMTP id D1FBA21F88BE for <ietf@ietf.org>; Mon, 22 Oct 2012 16:33:05 -0700 (PDT)
Received: from [192.168.1.72] (unknown [118.209.87.82]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 1D8B422E1F4; Mon, 22 Oct 2012 19:32:53 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: [whatwg] New URL Standard from Anne van Kesteren on 2012-09-24 (public-whatwg-archive@w3.org from September 2012)
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <Pine.LNX.4.64.1210222320070.2471@ps20323.dreamhostps.com>
Date: Tue, 23 Oct 2012 10:32:54 +1100
Content-Transfer-Encoding: quoted-printable
Message-Id: <09DC68AA-2DAD-4CB1-9CA9-799AF12B7BE2@mnot.net>
References: <50604C1A.7090901@gmx.de> <5060A964.5060001@stpeter.im> <Pine.LNX.4.64.1210172354500.2478@ps20323.dreamhostps.com> <507F5A7E.6040206@arcanedomain.com> <50856E3C.103@gmail.com> <Pine.LNX.4.64.1210221753010.2471@ps20323.dreamhostps.com> <0DBC8A11-319C-4120-975E-7E40FD5818BF@gbiv.com> <Pine.LNX.4.64.1210222137530.2471@ps20323.dreamhostps.com> <5085C4BA.2030505@gmx.de> <Pine.LNX.4.64.1210222220510.2471@ps20323.dreamhostps.com> <CAHBU6is8LNZ7Rq-vwLuOm+8ThKB9c=QPwbUfQwDQD5bDPjtf7w@mail.gmail.com> <Pine.LNX.4.64.1210222320070.2471@ps20323.dreamhostps.com>
To: Ian Hickson <ian@hixie.ch>
X-Mailer: Apple Mail (2.1499)
Cc: IETF Discussion <ietf@ietf.org>, Julian Reschke <julian.reschke@gmx.de>, "Roy T. Fielding" <fielding@gbiv.com>, Jan Algermissen <jan.algermissen@nordsc.com>, Noah Mendelsohn <nrm@arcanedomain.com>, URI <uri@w3.org>, Tim Bray <tbray@textuality.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Oct 2012 23:33:06 -0000

On 23/10/2012, at 10:25 AM, Ian Hickson <ian@hixie.ch> wrote:
>=20
> What exactly do you suggest?=20
>=20
> Doing the work but at the IETF? See my reply to James.

Don't much care about the venue, as long as there's *some* coordination =
/ communication.

> Waiting for the IETF to do the work? We did, and timed out.

Understood, and unfortunate. Arguably, you waited longer than the =
timeout.

> Not doing the work? That doesn't lead to interop.

Absolutely - again, I don't see anyone suggesting that. Do I smell =
straw?

> Doing the work as a diff spec? That's what we did for a while, but it=20=

> doesn't work. Having to reference three specs (pre-parse, IRI, URI) =
just=20
> to parse and resolve a URL is not what leads to implementors having a =
good=20
> time and thus not what leads to interop.

Really? You're comfortable with the current weight and depth of the =
HTML5 spec, but balk at a pre-processing step for URIs? Seriously?

The underlying point that people seem to be making is that there's =
legitimate need for URIs to be a separate concept from "strings that =
will become URIs." By collapsing them into one thing, you're doing those =
folks a disservice. Browser implementers may not care, but it's pretty =
obvious that lots of other people do.

BTW, it doesn't have to be a separate spec, although it probably would =
benefit from being one. Browser implementers already have to reference =
TCP, IP, DNS, and likely tens to hundreds of other specs to get what =
they want done -- unless you have bigger plans?

Regards,


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




From mnot@mnot.net  Mon Oct 22 16:53:10 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 392AA11E813B for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 16:53:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.051
X-Spam-Level: 
X-Spam-Status: No, score=-104.051 tagged_above=-999 required=5 tests=[AWL=-1.452, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XyAzoWVrXzGv for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 16:53:09 -0700 (PDT)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) by ietfa.amsl.com (Postfix) with ESMTP id F3AD711E8131 for <ietf@ietf.org>; Mon, 22 Oct 2012 16:53:08 -0700 (PDT)
Received: from [192.168.1.72] (unknown [118.209.87.82]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 3721922E1F4; Mon, 22 Oct 2012 19:52:54 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: [whatwg] New URL Standard from Anne van Kesteren on 2012-09-24 (public-whatwg-archive@w3.org from September 2012)
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <Pine.LNX.4.64.1210222337520.2471@ps20323.dreamhostps.com>
Date: Tue, 23 Oct 2012 10:52:55 +1100
Content-Transfer-Encoding: quoted-printable
Message-Id: <D9485C0B-E3DA-4B51-9A25-9EAB018C1951@mnot.net>
References: <50604C1A.7090901@gmx.de> <5060A964.5060001@stpeter.im> <Pine.LNX.4.64.1210172354500.2478@ps20323.dreamhostps.com> <507F5A7E.6040206@arcanedomain.com> <50856E3C.103@gmail.com> <Pine.LNX.4.64.1210221753010.2471@ps20323.dreamhostps.com> <0DBC8A11-319C-4120-975E-7E40FD5818BF@gbiv.com> <Pine.LNX.4.64.1210222137530.2471@ps20323.dreamhostps.com> <5085C4BA.2030505@gmx.de> <Pine.LNX.4.64.1210222220510.2471@ps20323.dreamhostps.com> <CAHBU6is8LNZ7Rq-vwLuOm+8ThKB9c=QPwbUfQwDQD5bDPjtf7w@mail.gmail.com> <Pine.LNX.4.64.1210222320070.2471@ps20323.dreamhostps.com> <09DC68AA-2DAD-4CB1-9CA9-799AF12B7BE2@mnot.net> <Pine.LNX.4.64.1210222337520.2471@ps20323.dreamhostps.com>
To: Ian Hickson <ian@hixie.ch>
X-Mailer: Apple Mail (2.1499)
Cc: IETF Discussion <ietf@ietf.org>, Julian Reschke <julian.reschke@gmx.de>, "Roy T. Fielding" <fielding@gbiv.com>, Jan Algermissen <jan.algermissen@nordsc.com>, Noah Mendelsohn <nrm@arcanedomain.com>, URI <uri@w3.org>, Tim Bray <tbray@textuality.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Oct 2012 23:53:10 -0000

On 23/10/2012, at 10:40 AM, Ian Hickson <ian@hixie.ch> wrote:

> On Tue, 23 Oct 2012, Mark Nottingham wrote:
>>=20
>> Don't much care about the venue, as long as there's *some* =
coordination=20
>> / communication.
>=20
> Everyone is welcome to participate in the WHATWG list.

As they are on the IETF list. The difference is that the WHATWG is run =
by an unelected board of "members" - <http://www.whatwg.org/charter>.=20


> There's no reason to have three specs when one suffices.

OK.=20


> The underlying point that people seem to be making is that there's=20
>> legitimate need for URIs to be a separate concept from "strings that=20=

>> will become URIs."
>=20
> Anne's spec will define "valid URL", which addressed that need.

Why not define (or reuse) a separate term for the input stream, and =
leave "URL" alone?


> By collapsing them into one thing, you're doing those folks a=20
>> disservice.
>=20
> They are not collapsed into one thing.

OK, good.


>> Browser implementers may not care, but it's pretty obvious that lots =
of=20
>> other people do.
>=20
> Browser implementors aren't particularly special here.

No, but your arguments are often coloured by your perspective -- just as =
everyone else's are.=20


> BTW, it doesn't have to be a separate spec, although it probably would=20=

>> benefit from being one. Browser implementers already have to =
reference=20
>> TCP, IP, DNS, and likely tens to hundreds of other specs to get what=20=

>> they want done -- unless you have bigger plans?
>=20
> The difference is that the DNS implementor doesn't need to implement =
TCP,=20
> he uses TCP (and UDP) and builds on it. And so on. Whereas here we're=20=

> talking about one thing, URLs, being specified in one place vs three.


OK.

If I believed that Anne was willing to and capable of re-specifying =
RFC3986 in such a way that the definition, syntax and semantics of URLs =
(or whatever they ends up being called) doesn't change at all, I'd be =
less concerned.=20

However, that doesn't seem very likely, especially when he isn't =
engaging with the folks that wrote that spec (especially, Roy).=20

RFC3986 is referenced by a LOT of technologies, not just Web browsers, =
not just HTML. Replacing it unilaterally with input from the browser / =
HTML community from an implementer perspective is very likely to break =
most of them.

As such, they won't use your new spec, and we'll be living in a world =
where there will be two definitions of "URL" -- the IETF one and the =
WHATWG one (or perhaps the W3C one, I can never remember the =
relationship there).=20

That seems a pretty bad tradeoff for the benefits you're getting -- a =
slightly easier-to-read spec for browser implementers (a relatively tiny =
audience).

Regards,

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




From tbray@textuality.com  Mon Oct 22 17:15:45 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 DB7CF21F86D6 for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 17:15:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.976
X-Spam-Level: 
X-Spam-Status: No, score=-2.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CyE46x2s+Yu1 for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 17:15:44 -0700 (PDT)
Received: from mail-oa0-f44.google.com (mail-oa0-f44.google.com [209.85.219.44]) by ietfa.amsl.com (Postfix) with ESMTP id 51AE21F0429 for <ietf@ietf.org>; Mon, 22 Oct 2012 17:15:44 -0700 (PDT)
Received: by mail-oa0-f44.google.com with SMTP id n5so3632437oag.31 for <ietf@ietf.org>; Mon, 22 Oct 2012 17:15:41 -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:x-gm-message-state; bh=bXVKM7Ed9LgxNjSQOb/PrV8SOm8jj6/w/O878tIG63w=; b=Z5ZdE8WNFaxPqXAglnR1pOWDQz8zDsezFLfa6fnHAheeESBdSBsBfrIAsoVNvpEvLB a4yTKTOp5XpTJn8lI1UTBEXztOW5Z0SJz8sFz1mIb6WV3dtgas/+KYCWHMocKlfuATnE iUppE7Ld/TtxXbPNxSyfCSh7F2Mgah+Bpd7FBLuc6XE1tU1gVB7//Cs4D7bH2vAtthWw pgu3c4ho/g9NYClGJJGXozo+9rZID1bEEaw30KZWBFoTSvRWU0mvImkLs2/b8HJhhFzU FpOx0eOCbCcGkomBLPnHD0qsoH52wCpBK8VZSJvw4ag3MEIV7TR5YWzsOF9vOMj76Hz1 VJxw==
MIME-Version: 1.0
Received: by 10.60.32.210 with SMTP id l18mr9799222oei.79.1350951341864; Mon, 22 Oct 2012 17:15:41 -0700 (PDT)
Received: by 10.76.87.136 with HTTP; Mon, 22 Oct 2012 17:15:41 -0700 (PDT)
X-Originating-IP: [2620:0:1000:5e03:cc38:a077:8b09:36fb]
In-Reply-To: <Pine.LNX.4.64.1210222359080.2471@ps20323.dreamhostps.com>
References: <50604C1A.7090901@gmx.de> <5060A964.5060001@stpeter.im> <Pine.LNX.4.64.1210172354500.2478@ps20323.dreamhostps.com> <507F5A7E.6040206@arcanedomain.com> <50856E3C.103@gmail.com> <Pine.LNX.4.64.1210221753010.2471@ps20323.dreamhostps.com> <0DBC8A11-319C-4120-975E-7E40FD5818BF@gbiv.com> <Pine.LNX.4.64.1210222137530.2471@ps20323.dreamhostps.com> <5085C4BA.2030505@gmx.de> <Pine.LNX.4.64.1210222220510.2471@ps20323.dreamhostps.com> <CAHBU6is8LNZ7Rq-vwLuOm+8ThKB9c=QPwbUfQwDQD5bDPjtf7w@mail.gmail.com> <Pine.LNX.4.64.1210222320070.2471@ps20323.dreamhostps.com> <09DC68AA-2DAD-4CB1-9CA9-799AF12B7BE2@mnot.net> <Pine.LNX.4.64.1210222337520.2471@ps20323.dreamhostps.com> <D9485C0B-E3DA-4B51-9A25-9EAB018C1951@mnot.net> <Pine.LNX.4.64.1210222359080.2471@ps20323.dreamhostps.com>
Date: Mon, 22 Oct 2012 17:15:41 -0700
Message-ID: <CAHBU6iv29xAJvgVtcNVpYX=23tydt+mCOQegRiNLV=K8sCh-Cg@mail.gmail.com>
Subject: Re: [whatwg] New URL Standard from Anne van Kesteren on 2012-09-24 (public-whatwg-archive@w3.org from September 2012)
From: Tim Bray <tbray@textuality.com>
To: Ian Hickson <ian@hixie.ch>
Content-Type: multipart/alternative; boundary=e89a8f83a909d7362604ccaede38
X-Gm-Message-State: ALoCoQk9kjs4qI9H2tqHgrvQLuGs1xnyYeMhE7NT1C8J3JtLcGaCsDxAT55WchAqfrAT7uvPPQn/
Cc: IETF Discussion <ietf@ietf.org>, Julian Reschke <julian.reschke@gmx.de>, "Roy T. Fielding" <fielding@gbiv.com>, Jan Algermissen <jan.algermissen@nordsc.com>, URI <uri@w3.org>, Noah Mendelsohn <nrm@arcanedomain.com>, Mark Nottingham <mnot@mnot.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, 23 Oct 2012 00:15:46 -0000

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

One more data point... I work on Web software all the time and have for
many years; in recent years mostly at the REST (app-to-app HTTP
conversations) rather than browser-wrangling level.  I=92d have to say that
URI interoperability problems haven=92t come near getting into the list of
top-20 pain points.   So either my experience is wildly untypical, or maybe
it=92s a combination of being a little bit lucky, and that the pain which
exists is highly concentrated in the browser space.  -T

On Mon, Oct 22, 2012 at 5:05 PM, Ian Hickson <ian@hixie.ch> wrote:

> On Tue, 23 Oct 2012, Mark Nottingham wrote:
> > On 23/10/2012, at 10:40 AM, Ian Hickson <ian@hixie.ch> wrote:
> > > On Tue, 23 Oct 2012, Mark Nottingham wrote:
> > >>
> > >> Don't much care about the venue, as long as there's *some*
> > >> coordination / communication.
> > >
> > > Everyone is welcome to participate in the WHATWG list.
> >
> > As they are on the IETF list. The difference is that the WHATWG is run
> > by an unelected board of "members" - <http://www.whatwg.org/charter>.
>
> "Run" is a bit of a strong word. There's basically no non-public activity
> from the charter members.
>
>
> > > Anne's spec will define "valid URL", which addressed that need.
> >
> > Why not define (or reuse) a separate term for the input stream, and
> > leave "URL" alone?
>
> Because everyone calls these things URLs (except STD 66).
>
>
> > >> Browser implementers may not care, but it's pretty obvious that lots
> > >> of other people do.
> > >
> > > Browser implementors aren't particularly special here.
> >
> > No, but your arguments are often coloured by your perspective -- just a=
s
> > everyone else's are.
>
> Which arguments in particular are we talking about here? I've mostly been
> talking about curl, wget, GoogleBot, Perl libraries, etc.
>
>
> > If I believed that Anne was willing to and capable of re-specifying
> > RFC3986 in such a way that the definition, syntax and semantics of URLs
> > (or whatever they ends up being called) doesn't change at all, I'd be
> > less concerned.
> >
> > However, that doesn't seem very likely, especially when he isn't
> > engaging with the folks that wrote that spec (especially, Roy).
> >
> > RFC3986 is referenced by a LOT of technologies, not just Web browsers,
> > not just HTML. Replacing it unilaterally with input from the browser /
> > HTML community from an implementer perspective is very likely to break
> > most of them.
>
> I suspect it will break nothing, but I guess we'll find out.
>
> I don't really understand how it _could_ break anything, so long as the
> processing of IRI and URIs as defined by IETF is the same in the WHATWG
> spec, except where software already differs with the IETF specs.
>
> Do you have a concrete example I could study?
>
>
> > As such, they won't use your new spec, and we'll be living in a world
> > where there will be two definitions of "URL" -- the IETF one and the
> > WHATWG one [...].
> >
> > That seems a pretty bad tradeoff for the benefits you're getting -- a
> > slightly easier-to-read spec for browser implementers (a relatively tin=
y
> > audience).
>
> If you have any concrete concerns, please don't hesitate to e-mail the
> WHATWG list, showing the specific examples you're worried about. Browsers
> are but one of many implementation classes that are relevant.
>
> --
> Ian Hickson               U+1047E                )\._.,--....,'``.    fL
> http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
> Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
>

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

One more data point... I work on Web software all the time and have for man=
y years; in recent years mostly at the REST (app-to-app HTTP conversations)=
 rather than browser-wrangling level.=A0 I=92d have to say that URI interop=
erability problems haven=92t come near getting into the list of top-20 pain=
 points.=A0=A0 So either my experience is wildly untypical, or maybe it=92s=
 a combination of being a little bit lucky, and that the pain which exists =
is highly concentrated in the browser space.=A0 -T<br>
<br><div class=3D"gmail_quote">On Mon, Oct 22, 2012 at 5:05 PM, Ian Hickson=
 <span dir=3D"ltr">&lt;<a href=3D"mailto:ian@hixie.ch" target=3D"_blank">ia=
n@hixie.ch</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class=3D"im">On Tue, 23 Oct 2012, Mark Nottingham wrote:<br>
&gt; On 23/10/2012, at 10:40 AM, Ian Hickson &lt;<a href=3D"mailto:ian@hixi=
e.ch">ian@hixie.ch</a>&gt; wrote:<br>
&gt; &gt; On Tue, 23 Oct 2012, Mark Nottingham wrote:<br>
&gt; &gt;&gt;<br>
&gt; &gt;&gt; Don&#39;t much care about the venue, as long as there&#39;s *=
some*<br>
&gt; &gt;&gt; coordination / communication.<br>
&gt; &gt;<br>
&gt; &gt; Everyone is welcome to participate in the WHATWG list.<br>
&gt;<br>
&gt; As they are on the IETF list. The difference is that the WHATWG is run=
<br>
&gt; by an unelected board of &quot;members&quot; - &lt;<a href=3D"http://w=
ww.whatwg.org/charter" target=3D"_blank">http://www.whatwg.org/charter</a>&=
gt;.<br>
<br>
</div>&quot;Run&quot; is a bit of a strong word. There&#39;s basically no n=
on-public activity<br>
from the charter members.<br>
<div class=3D"im"><br>
<br>
&gt; &gt; Anne&#39;s spec will define &quot;valid URL&quot;, which addresse=
d that need.<br>
&gt;<br>
&gt; Why not define (or reuse) a separate term for the input stream, and<br=
>
&gt; leave &quot;URL&quot; alone?<br>
<br>
</div>Because everyone calls these things URLs (except STD 66).<br>
<div class=3D"im"><br>
<br>
&gt; &gt;&gt; Browser implementers may not care, but it&#39;s pretty obviou=
s that lots<br>
&gt; &gt;&gt; of other people do.<br>
&gt; &gt;<br>
&gt; &gt; Browser implementors aren&#39;t particularly special here.<br>
&gt;<br>
&gt; No, but your arguments are often coloured by your perspective -- just =
as<br>
&gt; everyone else&#39;s are.<br>
<br>
</div>Which arguments in particular are we talking about here? I&#39;ve mos=
tly been<br>
talking about curl, wget, GoogleBot, Perl libraries, etc.<br>
<div class=3D"im"><br>
<br>
&gt; If I believed that Anne was willing to and capable of re-specifying<br=
>
&gt; RFC3986 in such a way that the definition, syntax and semantics of URL=
s<br>
&gt; (or whatever they ends up being called) doesn&#39;t change at all, I&#=
39;d be<br>
&gt; less concerned.<br>
&gt;<br>
&gt; However, that doesn&#39;t seem very likely, especially when he isn&#39=
;t<br>
&gt; engaging with the folks that wrote that spec (especially, Roy).<br>
&gt;<br>
&gt; RFC3986 is referenced by a LOT of technologies, not just Web browsers,=
<br>
&gt; not just HTML. Replacing it unilaterally with input from the browser /=
<br>
&gt; HTML community from an implementer perspective is very likely to break=
<br>
&gt; most of them.<br>
<br>
</div>I suspect it will break nothing, but I guess we&#39;ll find out.<br>
<br>
I don&#39;t really understand how it _could_ break anything, so long as the=
<br>
processing of IRI and URIs as defined by IETF is the same in the WHATWG<br>
spec, except where software already differs with the IETF specs.<br>
<br>
Do you have a concrete example I could study?<br>
<div class=3D"im"><br>
<br>
&gt; As such, they won&#39;t use your new spec, and we&#39;ll be living in =
a world<br>
&gt; where there will be two definitions of &quot;URL&quot; -- the IETF one=
 and the<br>
</div>&gt; WHATWG one [...].<br>
<div class=3D"im">&gt;<br>
&gt; That seems a pretty bad tradeoff for the benefits you&#39;re getting -=
- a<br>
&gt; slightly easier-to-read spec for browser implementers (a relatively ti=
ny<br>
&gt; audience).<br>
<br>
</div>If you have any concrete concerns, please don&#39;t hesitate to e-mai=
l the<br>
WHATWG list, showing the specific examples you&#39;re worried about. Browse=
rs<br>
are but one of many implementation classes that are relevant.<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
--<br>
Ian Hickson =A0 =A0 =A0 =A0 =A0 =A0 =A0 U+1047E =A0 =A0 =A0 =A0 =A0 =A0 =A0=
 =A0)\._.,--....,&#39;``. =A0 =A0fL<br>
<a href=3D"http://ln.hixie.ch/" target=3D"_blank">http://ln.hixie.ch/</a> =
=A0 =A0 =A0 U+263A =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0/, =A0 _.. \ =A0 _\ =A0;`=
._ ,.<br>
Things that are impossible just take longer. =A0 `._.-(,_..&#39;--(,_..&#39=
;`-.;.&#39;<br>
</div></div></blockquote></div><br>

--e89a8f83a909d7362604ccaede38--

From lberger@labn.net  Mon Oct 22 17:40:58 2012
Return-Path: <lberger@labn.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E27441F0C49 for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 17:40:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.168
X-Spam-Level: 
X-Spam-Status: No, score=-101.168 tagged_above=-999 required=5 tests=[AWL=0.831, BAYES_00=-2.599, J_CHICKENPOX_14=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xUK1ITh4dAZj for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 17:40:58 -0700 (PDT)
Received: from oproxy12-pub.bluehost.com (oproxy12-pub.bluehost.com [50.87.16.10]) by ietfa.amsl.com (Postfix) with SMTP id 2F2321F0429 for <ietf@ietf.org>; Mon, 22 Oct 2012 17:40:58 -0700 (PDT)
Received: (qmail 12683 invoked by uid 0); 23 Oct 2012 00:40:34 -0000
Received: from unknown (HELO box313.bluehost.com) (69.89.31.113) by oproxy12.bluehost.com with SMTP; 23 Oct 2012 00:40:34 -0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=labn.net; s=default;  h=Content-Transfer-Encoding:Content-Type:In-Reply-To:References:Subject:CC:To:MIME-Version:From:Date:Message-ID; bh=Pt/+3ILc5XazMa21Ayvofm+brPTrfkXdzZLYUBatIP8=;  b=MAOZL+RXaCGIGKUWipIX2GO+zNUYOofrkxJ/s5tpxqFyc3hYAVmvriFC/SuOWyG/NEgiuUvS/UlTGc7CjFdLIUjR/mktUITmpbk1jVV3MuZQKHIhWOmgz+xnWk58TTOJ;
Received: from box313.bluehost.com ([69.89.31.113]:50891 helo=[127.0.0.1]) by box313.bluehost.com with esmtpa (Exim 4.76) (envelope-from <lberger@labn.net>) id 1TQSXq-00017u-BZ; Mon, 22 Oct 2012 18:40:34 -0600
Message-ID: <5085E77C.5020100@labn.net>
Date: Mon, 22 Oct 2012 20:40:28 -0400
From: Lou Berger <lberger@labn.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121010 Thunderbird/16.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Last Call: <draft-kumaki-murai-l3vpn-rsvp-te-06.txt> (Support for RSVP-TE in L3VPNs) to Experimental RFC
References: <20120905224357.14197.39927.idtracker@ietfa.amsl.com>
In-Reply-To: <20120905224357.14197.39927.idtracker@ietfa.amsl.com>
X-Enigmail-Version: 1.4.5
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Identified-User: {1038:box313.bluehost.com:labnmobi:labn.net} {sentby:smtp auth 69.89.31.113 authed with lberger@labn.net}
Cc: Adrian Farrel <afarrel@juniper.net>, draft-kumaki-murai-l3vpn-rsvp-te.all@tools.ietf.org, Dan King <daniel@olddog.co.uk>, Stewart Bryant <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, 23 Oct 2012 00:40:59 -0000

Hello,
	I made this comment privately during the LC period.  I don't mind
sharing it more widely:

> My high-order take away is that it seems to me that this draft runs
> counter to hierarchy-based solutions that can solve this problem just
> fine without any additional RSVP modifications. I therefore think
> this draft should be run through a WG that is willing to reconcile
> the approaches (and fully document their uses case supported by
> hierarchy). Failing that, I think the draft should have an IESG 
> applicability note added saying that this is experimental only and
> that standard hierarchy should be used to solve the problem in any 
> operational implementation/network.
> 
> As to the technical details, the next hop as identified by the Path 
> message in the VPN context, will have a route and associated label 
> within the VPN context. This VPN label can be added to the Path 
> message, just as it would be for any VPN IP packet, and additional 
> labels may be added for PE-PE transport. In implementations that 
> rewrite the IP header, the IP destination can be set to the next
> hop. The remote PE/next hop will receive the Path message with the
> VPN label which will identify the VPN context/VRF. This PE will then
> need to identify the packet as RSVP using either the router alert
> mechanism or based on the IP header destination address. So I see no
> reason for the modifications when the VAN-specific MPLS labels are
> used.
>
> Shout if you think I missed something.

Lou
On 9/5/2012 6:43 PM, The IESG wrote:
> 
> The IESG has received a request from an individual submitter to consider
> the following document:
> - 'Support for RSVP-TE in L3VPNs'
>   <draft-kumaki-murai-l3vpn-rsvp-te-06.txt> as Experimental RFC
> 
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2012-10-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
> 
> 
>    IP Virtual Private Networks (VPNs) provide connectivity between sites
>    across an IP/MPLS backbone. These VPNs can be operated using BGP/MPLS
>    and a single provider edge (PE) node may provide access to multiple
>    customer sites belonging to different VPNs.
> 
>    The VPNs may support a number of customer services including RSVP and
>    RSVP-TE traffic. This document describes how to support RSVP-TE
>    between customer sites when a single PE supports multiple VPNs.
> 
> 
> 
> 
> 
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-kumaki-murai-l3vpn-rsvp-te/
> 
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-kumaki-murai-l3vpn-rsvp-te/ballot/
> 
> 
> No IPR declarations have been submitted directly on this I-D.
> 
> Due to an error by the sponsoring Area Director, the Last Call on 
> this document (which completed on 3rd September) incorrectly 
> stated that this draft was intended that it be published as Informational.
> The correct intention (as stated in the draft itself) is that it  be 
> published as Experimental. 
> 
> This Last Call is to verify community consensus for publication of
> this draft as Experimental. 
> 
> 
> 
> 
> 
> 

From huitema@microsoft.com  Mon Oct 22 18:16:40 2012
Return-Path: <huitema@microsoft.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1918A1F0C51 for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 18:16:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GUgcKl7rAeFj for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 18:16:39 -0700 (PDT)
Received: from NA01-BL2-obe.outbound.protection.outlook.com (na01-bl2-obe.ptr.protection.outlook.com [65.55.169.32]) by ietfa.amsl.com (Postfix) with ESMTP id 649D01F0429 for <ietf@ietf.org>; Mon, 22 Oct 2012 18:16:39 -0700 (PDT)
Received: from BL2FFO11FD003.protection.gbl (10.173.161.201) by BL2FFO11HUB007.protection.gbl (10.173.160.227) with Microsoft SMTP Server (TLS) id 15.0.545.8; Tue, 23 Oct 2012 00:37:02 +0000
Received: from TK5EX14HUBC103.redmond.corp.microsoft.com (131.107.125.37) by BL2FFO11FD003.mail.protection.outlook.com (10.173.160.103) with Microsoft SMTP Server (TLS) id 15.0.545.8 via Frontend Transport; Tue, 23 Oct 2012 00:37:02 +0000
Received: from TK5EX14MBXC272.redmond.corp.microsoft.com ([169.254.2.52]) by TK5EX14HUBC103.redmond.corp.microsoft.com ([157.54.86.9]) with mapi id 14.02.0318.003; Tue, 23 Oct 2012 00:35:40 +0000
From: Christian Huitema <huitema@microsoft.com>
To: Steve Crocker <steve@shinkuro.com>, "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: In Memoriam IETF web page -- a modest proposal
Thread-Topic: In Memoriam IETF web page -- a modest proposal
Thread-Index: AQHNsJNrs72EPFAjcU6N8QBmHpWXm5fGCdD8
Date: Tue, 23 Oct 2012 00:35:38 +0000
Message-ID: <C91E67751B1EFF41B857DE2FE1F68ABA0BDF177F@tk5ex14mbxc272.redmond.corp.microsoft.com>
References: <20121022190358.7F7BF18C0B7@mercury.lcs.mit.edu> <20121022194545.GA11999@thunk.org>, <13E5830C-7323-4A7F-956A-2DD2CDB6D0AA@shinkuro.com>
In-Reply-To: <13E5830C-7323-4A7F-956A-2DD2CDB6D0AA@shinkuro.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.51.32]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Forefront-Antispam-Report: CIP:131.107.125.37; CTRY:US; IPV:CAL; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(377454001)(33656001)(53806001)(3846001)(47736001)(8716001)(20776001)(51856001)(5343655001)(50466001)(46102001)(2666001)(50986001)(47976001)(48376001)(1076001)(47776002)(16406001)(44976002)(31966008)(16696001)(42186003)(4396001)(4196001)(16826001)(49866001)(47446002)(74502001)(74662001)(316001)(3746001)(3556001); DIR:OUT; LANG:en; 
X-OriginatorOrg: microsoft.onmicrosoft.com
X-Forefront-PRVS: 0643BDA83C
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Oct 2012 01:16:40 -0000

Memorials are for the living. The dead typically have ceased to care.

I don't know what a simple listing will achieve. The "war monuments" that T=
ed mention sort of educate the living by reminding them of the massive sacr=
ifices that wars cause. Just listing a bunch of names will not help all tha=
t much. After all, most of these names are already listed in the RFC record=
.

A memorial RFC has more potential. A bit like what the catholic Church does=
 by publishing the "life of the saints." The results could be interesting.


________________________________________
From: ietf-bounces@ietf.org [ietf-bounces@ietf.org] on behalf of Steve Croc=
ker [steve@shinkuro.com]
Sent: Monday, October 22, 2012 1:25 PM
To: ietf@ietf.org
Subject: Re: In Memoriam IETF web page -- a modest proposal

After watching the traffic on this, I'm thinking a memorial page is perhaps=
 not the first place to focus attention.  Instead, write a memorial RFC for=
 each person you think made a significant contribution to the IETF.  The RF=
C Editorial process will provide some vetting on quality.  Use Informationa=
l, Historic(!) or create a new class.

The memorial page can then list those who have memorial RFCs written for th=
em.

Steve=

From randy@psg.com  Mon Oct 22 18:30:35 2012
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 57D451F0C71 for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 18:30:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.474
X-Spam-Level: 
X-Spam-Status: No, score=-2.474 tagged_above=-999 required=5 tests=[AWL=0.125,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9iHzRJn3bylG for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 18:30:35 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 0C3591F0C67 for <ietf@ietf.org>; Mon, 22 Oct 2012 18:30:35 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=rair.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.80 (FreeBSD)) (envelope-from <randy@psg.com>) id 1TQTKE-000IIi-0c for ietf@ietf.org; Tue, 23 Oct 2012 01:30:34 +0000
Date: Mon, 22 Oct 2012 20:30:34 -0500
Message-ID: <m2a9veq8jp.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: IETF Disgust <ietf@ietf.org>
Subject: Re: In Memoriam IETF web page -- a modest proposal
In-Reply-To: <C91E67751B1EFF41B857DE2FE1F68ABA0BDF177F@tk5ex14mbxc272.redmond.corp.microsoft.com>
References: <20121022190358.7F7BF18C0B7@mercury.lcs.mit.edu> <20121022194545.GA11999@thunk.org>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Oct 2012 01:30:35 -0000

a friend suggested privately an article in the ietf journal when someone
has died.  this seems a no-brainer.  and it is archived.

i will not indulge in the swamp of attempting to codify who writes it
and how.  if the ietf journal editor(s) can not be trusted, replace
them.  sheesh!

randy

From barryleiba.mailing.lists@gmail.com  Mon Oct 22 19:42:23 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 486411F0C8B for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 19:42:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.076
X-Spam-Level: 
X-Spam-Status: No, score=-103.076 tagged_above=-999 required=5 tests=[AWL=-0.100, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MORGvFD1Gf9U for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 19:42:22 -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 5D41E1F0C8A for <ietf@ietf.org>; Mon, 22 Oct 2012 19:42:22 -0700 (PDT)
Received: by mail-lb0-f172.google.com with SMTP id k13so67451lbo.31 for <ietf@ietf.org>; Mon, 22 Oct 2012 19:42:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=vxkZVoRqJxUurR6UteikReVd8IkVV5BQAhlhf5HxFCc=; b=w/G+SylJRYKN0VcyF1o5eYt4O1YKM82u5MZobgb2aZfhPNEUmOT2kRP/ScJv8e7xIw zP1xXZKDgeFxUysB+IThnmzDjDtV88ewFKTEDyrXIRyOiamxpsQScyDi11b2TS+oabls OXLOOH+UZsmg4cXUL6LxRvVaVNGZEn8BqPcUxWUCPRVqJAXGXAmf2RxTwt58ZDa/zd1i b7GFT73d276ZRb0fA73jkqxv76OIqM6syVk+UK7ye/AWoS8AYhuFCjPXEYVZqquROXIF eWHbWLBI4EEAwm1pIYedZMbMAV98xAzNW88TKZ+yJhZiSg1K3FtdkdJ82fZtRf+6BqPw 8tyg==
MIME-Version: 1.0
Received: by 10.112.38.228 with SMTP id j4mr4380907lbk.87.1350960141154; Mon, 22 Oct 2012 19:42:21 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.112.99.131 with HTTP; Mon, 22 Oct 2012 19:42:21 -0700 (PDT)
In-Reply-To: <20121022234941.28301.7687.idtracker@ietfa.amsl.com>
References: <20121022234941.28301.7687.idtracker@ietfa.amsl.com>
Date: Mon, 22 Oct 2012 22:42:21 -0400
X-Google-Sender-Auth: ldsq7HV7Lw44uFv5yXypX9Sts7c
Message-ID: <CAC4RtVAR+RrZ99akHrip_53QJ5=ocaPVn-sq9xLdAKfZPEMrkQ@mail.gmail.com>
Subject: Re: IAOC Request for community feedback
From: Barry Leiba <barryleiba@computer.org>
To: IETF discussion list <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=e0cb4efe2f1251ba7a04ccb0eb0e
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Oct 2012 02:42:23 -0000

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

> The IAOC is requesting feedback from the community whether it is
> reasonable to declare Marshall's IAOC position vacant.

Yes.

Barry

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

<font><span style=3D"line-height:normal;background-color:rgba(255,255,255,0=
)">&gt; The IAOC is requesting feedback from the community whether it is<br=
>&gt; reasonable to declare Marshall&#39;s IAOC position vacant.</span></fo=
nt><div>
<font><span style=3D"line-height:normal;background-color:rgba(255,255,255,0=
)"><br></span></font></div><div><font><span style=3D"line-height:normal;bac=
kground-color:rgba(255,255,255,0)">Yes.</span></font></div><div><font><span=
 style=3D"line-height:normal;background-color:rgba(255,255,255,0)"><br>
</span></font></div><div><font><span style=3D"line-height:normal;background=
-color:rgba(255,255,255,0)">Barry<span></span></span></font></div>

--e0cb4efe2f1251ba7a04ccb0eb0e--

From julian.reschke@gmx.de  Mon Oct 22 23:26: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 2C3A921F8923 for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 23:26:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.394
X-Spam-Level: 
X-Spam-Status: No, score=-103.394 tagged_above=-999 required=5 tests=[AWL=-0.795, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fgr-wcgKNbPn for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 23:26:58 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by ietfa.amsl.com (Postfix) with SMTP id 46AEF21F84C4 for <ietf@ietf.org>; Mon, 22 Oct 2012 23:26:58 -0700 (PDT)
Received: (qmail invoked by alias); 23 Oct 2012 06:26:56 -0000
Received: from p5DD95D63.dip.t-dialin.net (EHLO [192.168.178.36]) [93.217.93.99] by mail.gmx.net (mp038) with SMTP; 23 Oct 2012 08:26:56 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX197jbFoT3x71TtacqL6oeFIS/HQGbgeuG1WrAgLSC Go7uHuOGYyNpMi
Message-ID: <508638AF.4060307@gmx.de>
Date: Tue, 23 Oct 2012 08:26:55 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121010 Thunderbird/16.0.1
MIME-Version: 1.0
To: Ian Hickson <ian@hixie.ch>
Subject: Re: [whatwg] New URL Standard from Anne van Kesteren on 2012-09-24 (public-whatwg-archive@w3.org from September 2012)
References: <50604C1A.7090901@gmx.de> <5060A964.5060001@stpeter.im> <Pine.LNX.4.64.1210172354500.2478@ps20323.dreamhostps.com> <507F5A7E.6040206@arcanedomain.com> <50856E3C.103@gmail.com> <Pine.LNX.4.64.1210221753010.2471@ps20323.dreamhostps.com> <0DBC8A11-319C-4120-975E-7E40FD5818BF@gbiv.com> <Pine.LNX.4.64.1210222137530.2471@ps20323.dreamhostps.com> <5085C4BA.2030505@gmx.de> <Pine.LNX.4.64.1210222220510.2471@ps20323.dreamhostps.com> <CAHBU6is8LNZ7Rq-vwLuOm+8ThKB9c=QPwbUfQwDQD5bDPjtf7w@mail.gmail.com> <Pine.LNX.4.64.1210222320070.2471@ps20323.dreamhostps.com> <09DC68AA-2DAD-4CB1-9CA9-799AF12B7BE2@mnot.net> <Pine.LNX.4.64.1210222337520.2471@ps20323.dreamhostps.com> <D9485C0B-E3DA-4B51-9A25-9EAB018C1951@mnot.net> <Pine.LNX.4.64.1210222359080.2471@ps20323.dreamhostps.com>
In-Reply-To: <Pine.LNX.4.64.1210222359080.2471@ps20323.dreamhostps.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>, Noah Mendelsohn <nrm@arcanedomain.com>, "Roy T. Fielding" <fielding@gbiv.com>, Jan Algermissen <jan.algermissen@nordsc.com>, URI <uri@w3.org>, Mark Nottingham <mnot@mnot.net>, Tim Bray <tbray@textuality.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Oct 2012 06:26:59 -0000

On 2012-10-23 02:05, Ian Hickson wrote:
> ...
> I suspect it will break nothing, but I guess we'll find out.
>
> I don't really understand how it _could_ break anything, so long as the
> processing of IRI and URIs as defined by IETF is the same in the WHATWG
> spec, except where software already differs with the IETF specs.

Define "software". *All* software? How do you test that?

> Do you have a concrete example I could study?

Do you?

This brings me back to something I've been asking for many times: a 
*concrete* list of things that are "broken" in RFC 3986 (as opposed to 
be "undefined").

Best regards, Julian


From lars@netapp.com  Tue Oct 23 00:00:48 2012
Return-Path: <lars@netapp.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4721921F8AB5 for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 00:00:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.507
X-Spam-Level: 
X-Spam-Status: No, score=-10.507 tagged_above=-999 required=5 tests=[AWL=0.092, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dJerx2oEHYBD for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 00:00:47 -0700 (PDT)
Received: from mx2.netapp.com (mx2.netapp.com [216.240.18.37]) by ietfa.amsl.com (Postfix) with ESMTP id CB30F21F8923 for <ietf@ietf.org>; Tue, 23 Oct 2012 00:00:47 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.80,633,1344236400";  d="p7s'?scan'208";a="703167250"
Received: from smtp1.corp.netapp.com ([10.57.156.124]) by mx2-out.netapp.com with ESMTP; 23 Oct 2012 00:00:47 -0700
Received: from vmwexceht04-prd.hq.netapp.com (vmwexceht04-prd.hq.netapp.com [10.106.77.34]) by smtp1.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id q9N70lZ4022819; Tue, 23 Oct 2012 00:00:47 -0700 (PDT)
Received: from SACEXCMBX01-PRD.hq.netapp.com ([169.254.2.216]) by vmwexceht04-prd.hq.netapp.com ([10.106.77.34]) with mapi id 14.02.0318.001; Tue, 23 Oct 2012 00:00:47 -0700
From: "Eggert, Lars" <lars@netapp.com>
To: Barry Leiba <barryleiba@computer.org>
Subject: Re: IAOC Request for community feedback
Thread-Topic: IAOC Request for community feedback
Thread-Index: AQHNsK/yUK4KsMGdQ0mp4bZT2FEjw5fGpAWAgABIOwA=
Date: Tue, 23 Oct 2012 07:00:02 +0000
Message-ID: <D4D47BCFFE5A004F95D707546AC0D7E9185A2136@SACEXCMBX01-PRD.hq.netapp.com>
References: <20121022234941.28301.7687.idtracker@ietfa.amsl.com> <CAC4RtVAR+RrZ99akHrip_53QJ5=ocaPVn-sq9xLdAKfZPEMrkQ@mail.gmail.com>
In-Reply-To: <CAC4RtVAR+RrZ99akHrip_53QJ5=ocaPVn-sq9xLdAKfZPEMrkQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.104.60.115]
Content-Type: multipart/signed; boundary="Apple-Mail=_03AE124B-105D-4BF2-818C-7091B50B7ED2"; protocol="application/pkcs7-signature"; micalg=sha1
MIME-Version: 1.0
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Oct 2012 07:00:48 -0000

--Apple-Mail=_03AE124B-105D-4BF2-818C-7091B50B7ED2
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=iso-8859-1

On Oct 23, 2012, at 4:42, Barry Leiba <barryleiba@computer.org> wrote:
>> The IAOC is requesting feedback from the community whether it is
>> reasonable to declare Marshall's IAOC position vacant.
> 
> Yes.

+1

Lars
--Apple-Mail=_03AE124B-105D-4BF2-818C-7091B50B7ED2
Content-Disposition: attachment; filename="smime.p7s"
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIMQDCCBUow
ggQyoAMCAQICEFcfSRTG0jNknqb9LV9GuFkwDQYJKoZIhvcNAQEFBQAwgd0xCzAJBgNVBAYTAlVT
MRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29y
azE7MDkGA1UECxMyVGVybXMgb2YgdXNlIGF0IGh0dHBzOi8vd3d3LnZlcmlzaWduLmNvbS9ycGEg
KGMpMDkxHjAcBgNVBAsTFVBlcnNvbmEgTm90IFZhbGlkYXRlZDE3MDUGA1UEAxMuVmVyaVNpZ24g
Q2xhc3MgMSBJbmRpdmlkdWFsIFN1YnNjcmliZXIgQ0EgLSBHMzAeFw0xMTEyMTAwMDAwMDBaFw0x
MjEyMDkyMzU5NTlaMIIBDTEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlT
aWduIFRydXN0IE5ldHdvcmsxRjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9S
UEEgSW5jb3JwLiBieSBSZWYuLExJQUIuTFREKGMpOTgxHjAcBgNVBAsTFVBlcnNvbmEgTm90IFZh
bGlkYXRlZDEzMDEGA1UECxMqRGlnaXRhbCBJRCBDbGFzcyAxIC0gTmV0c2NhcGUgRnVsbCBTZXJ2
aWNlMRQwEgYDVQQDFAtMYXJzIEVnZ2VydDEeMBwGCSqGSIb3DQEJARYPbGFyc0BuZXRhcHAuY29t
MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAokrhJTcXt6J/VEpZOicLoguBlYTjXP9v
Ze4HuuhXnURUS8YouAfgaqA0zYbt5yd6fh4PBMdAaEWr5yJyHuFykXlrCumjUWSpLuqTS2A+pt4q
cZaAQk9iLDN/UVd3SpkUuvWbxXlqzG7/BSqa3VNObBzCmyh+V7aXxri+30CT//DSsNRC4VFy6sn6
dMgSaFenXLwe/FBwY0qTMfICT1PrrX6Sw1S8OfH9rykLlZXbmfkFExxQngp1DJH9xMHeODHGbCv/
ty5gdxMOrLe+vENxFEcy1YQWBZd1kNL4UObugF8A/jE/s+Oa3H1VFH8ghqZTdqGDysVxmtKHuNFx
6jIBSQIDAQABo4HSMIHPMAkGA1UdEwQCMAAwRAYDVR0gBD0wOzA5BgtghkgBhvhFAQcXATAqMCgG
CCsGAQUFBwIBFhxodHRwczovL3d3dy52ZXJpc2lnbi5jb20vcnBhMAsGA1UdDwQEAwIFoDAdBgNV
HSUEFjAUBggrBgEFBQcDBAYIKwYBBQUHAwIwUAYDVR0fBEkwRzBFoEOgQYY/aHR0cDovL2luZGMx
ZGlnaXRhbGlkLWczLWNybC52ZXJpc2lnbi5jb20vSW5kQzFEaWdpdGFsSUQtRzMuY3JsMA0GCSqG
SIb3DQEBBQUAA4IBAQBA7q6tR92qpd7xo7VBsrOfGCWzoxIVfTc7t0RhB/Oz/+c3lnhYnNScIuKN
JmyZvznmVxqB9BJ72+NkvmdB/hnILSBTRawL2tyLo9PkBtN0nRt4gS6wjpWnD8G83hlJLE7r25jk
7HkRev61dTIXsANFpJKF02C4XSoDfEzNV6MpuEvHvcgHCqMrlwWwfKc7+NoDnE8PBuRzwSXvlD5L
mswCY2iiOsd7ImNO4OzTCxETvKTDu92+FTIbRJJpYjVNv1UF7e3w9Kq65BkZJErUH19beUeQl0Wh
2BJQE6/15rQyCnP0iJ/Nmx2/kI6M0PWunEsI6FMs0MbosreaWGHlQmomMIIG7jCCBdagAwIBAgIQ
cRVmBUrkkSFN6bxE+azT3DANBgkqhkiG9w0BAQUFADCByjELMAkGA1UEBhMCVVMxFzAVBgNVBAoT
DlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTowOAYDVQQL
EzEoYykgMTk5OSBWZXJpU2lnbiwgSW5jLiAtIEZvciBhdXRob3JpemVkIHVzZSBvbmx5MUUwQwYD
VQQDEzxWZXJpU2lnbiBDbGFzcyAxIFB1YmxpYyBQcmltYXJ5IENlcnRpZmljYXRpb24gQXV0aG9y
aXR5IC0gRzMwHhcNMDkwNTAxMDAwMDAwWhcNMTkwNDMwMjM1OTU5WjCB3TELMAkGA1UEBhMCVVMx
FzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3Jr
MTswOQYDVQQLEzJUZXJtcyBvZiB1c2UgYXQgaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAo
YykwOTEeMBwGA1UECxMVUGVyc29uYSBOb3QgVmFsaWRhdGVkMTcwNQYDVQQDEy5WZXJpU2lnbiBD
bGFzcyAxIEluZGl2aWR1YWwgU3Vic2NyaWJlciBDQSAtIEczMIIBIjANBgkqhkiG9w0BAQEFAAOC
AQ8AMIIBCgKCAQEA7cRH3yooHXwGa7vXITLJbBOP6bGNQU4099oL42r6ZYggCxET6ZvgSU6Lb9UB
0F8NR5GKWkx0Pj/GkQm7TDSejW6hglFi92l2WJYHr54UGAdPWr2f0jGyVBlzRmoZQhHsEnMhjfXc
MM3l2VYKMcU2bSkUl70t2olHGYjYSwQ967Y8Zx50ABMN0Ibak2f4MwOuGjxraXj2wCyO4YM/d/mZ
//6fUlrCtIcK2GypR8FUKWVDPkrAlh/Brfd3r2yxBF6+wbaULZeQLSfSux7pg2qE9sSyriMGZSal
J1grByK0b6ZiSBp38tVQJ5op05b7KPW6JHZi44xZ6/tu1ULEvkHH9QIDAQABo4ICuTCCArUwNAYI
KwYBBQUHAQEEKDAmMCQGCCsGAQUFBzABhhhodHRwOi8vb2NzcC52ZXJpc2lnbi5jb20wEgYDVR0T
AQH/BAgwBgEB/wIBADBwBgNVHSAEaTBnMGUGC2CGSAGG+EUBBxcBMFYwKAYIKwYBBQUHAgEWHGh0
dHBzOi8vd3d3LnZlcmlzaWduLmNvbS9jcHMwKgYIKwYBBQUHAgIwHhocaHR0cHM6Ly93d3cudmVy
aXNpZ24uY29tL3JwYTA0BgNVHR8ELTArMCmgJ6AlhiNodHRwOi8vY3JsLnZlcmlzaWduLmNvbS9w
Y2ExLWczLmNybDAOBgNVHQ8BAf8EBAMCAQYwbgYIKwYBBQUHAQwEYjBgoV6gXDBaMFgwVhYJaW1h
Z2UvZ2lmMCEwHzAHBgUrDgMCGgQUS2u5KJYGDLvQUjibKaxLB4shBRgwJhYkaHR0cDovL2xvZ28u
dmVyaXNpZ24uY29tL3ZzbG9nbzEuZ2lmMC4GA1UdEQQnMCWkIzAhMR8wHQYDVQQDExZQcml2YXRl
TGFiZWw0LTIwNDgtMTE4MB0GA1UdDgQWBBR5R2EIQf04BKJL57XM9UP2SSsR+DCB8QYDVR0jBIHp
MIHmoYHQpIHNMIHKMQswCQYDVQQGEwJVUzEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNV
BAsTFlZlcmlTaWduIFRydXN0IE5ldHdvcmsxOjA4BgNVBAsTMShjKSAxOTk5IFZlcmlTaWduLCBJ
bmMuIC0gRm9yIGF1dGhvcml6ZWQgdXNlIG9ubHkxRTBDBgNVBAMTPFZlcmlTaWduIENsYXNzIDEg
UHVibGljIFByaW1hcnkgQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkgLSBHM4IRAItbdVaEVIULAM+v
OEjOsaQwDQYJKoZIhvcNAQEFBQADggEBADlNz0GZgbWpBbVSOOk5hIls5DSoWufYbAlMJBq6WaSH
O3Mh8ZOBz79oY1pn/jWFK6HDXaNKwjoZ3TDWzE3v8dKBl8pUWkO/N4t6jhmND0OojPKvYLMVirOV
nDzgnrMnmKQ1chfl/Cpdh9OKDcLRRSr4wPSsKpM61a4ScAjr+zvid+zoK2Q1ds262uDRyxTWcVib
vtU+fbbZ6CTFJGZMXZEfdrMXPn8NxiGJL7M3uKH/XLJtSd5lUkL7DojS7Uodv0vj+Mxy+kgOZY5J
yNb4mZg7t5Q+MXEGh/psWVMu198r7V9jAKwV7QO4VRaMxmgD5yKocwuxvKDaUljdCg5/wYIxggSL
MIIEhwIBATCB8jCB3TELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYD
VQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTswOQYDVQQLEzJUZXJtcyBvZiB1c2UgYXQgaHR0
cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAoYykwOTEeMBwGA1UECxMVUGVyc29uYSBOb3QgVmFs
aWRhdGVkMTcwNQYDVQQDEy5WZXJpU2lnbiBDbGFzcyAxIEluZGl2aWR1YWwgU3Vic2NyaWJlciBD
QSAtIEczAhBXH0kUxtIzZJ6m/S1fRrhZMAkGBSsOAwIaBQCgggJtMBgGCSqGSIb3DQEJAzELBgkq
hkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTEyMTAyMzA3MDA1M1owIwYJKoZIhvcNAQkEMRYEFFqr
UFyFcFKE/xcDgfkmsh2MflYSMIIBAwYJKwYBBAGCNxAEMYH1MIHyMIHdMQswCQYDVQQGEwJVUzEX
MBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5ldHdvcmsx
OzA5BgNVBAsTMlRlcm1zIG9mIHVzZSBhdCBodHRwczovL3d3dy52ZXJpc2lnbi5jb20vcnBhIChj
KTA5MR4wHAYDVQQLExVQZXJzb25hIE5vdCBWYWxpZGF0ZWQxNzA1BgNVBAMTLlZlcmlTaWduIENs
YXNzIDEgSW5kaXZpZHVhbCBTdWJzY3JpYmVyIENBIC0gRzMCEFcfSRTG0jNknqb9LV9GuFkwggEF
BgsqhkiG9w0BCRACCzGB9aCB8jCB3TELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJ
bmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMTswOQYDVQQLEzJUZXJtcyBvZiB1
c2UgYXQgaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYSAoYykwOTEeMBwGA1UECxMVUGVyc29u
YSBOb3QgVmFsaWRhdGVkMTcwNQYDVQQDEy5WZXJpU2lnbiBDbGFzcyAxIEluZGl2aWR1YWwgU3Vi
c2NyaWJlciBDQSAtIEczAhBXH0kUxtIzZJ6m/S1fRrhZMA0GCSqGSIb3DQEBAQUABIIBAG1OO05/
IKBzkeEx0P5egqI6oL3HehnPHQ+StvluqIT8KXYSdCCdhRtZns4u+1NFkya6gk09XwA0AVNyXJDt
Ebfz09FwDQDyeuY+m4PBXoP23UCz3vfAUUAgm7OJgAo2t8pRzbdXgAUjsE1gYaGwdTkGaMkVOeVb
zl4vZNCGx4lUD59CUE6b3+YQ9LzTFTVxMQxMyihm88E0uuLiD0ZFsuiYdWTGVlT+CV7Xnsm+maNH
fb/SQODYpwCqWfTCxDyuVrWBMEQIP/Cj1ifF2V4EEUvmemTvyMPEN5CEeJq+1YX7tzZ1O/IKj20J
SvhE/YlJXwQSn13Cy57C12h3hXlslhkAAAAAAAA=

--Apple-Mail=_03AE124B-105D-4BF2-818C-7091B50B7ED2--

From vesely@tana.it  Tue Oct 23 00:55:38 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 B0D9021F8673 for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 00:55:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.671
X-Spam-Level: 
X-Spam-Status: No, score=-4.671 tagged_above=-999 required=5 tests=[AWL=0.048,  BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Jo4xrEykjVlD for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 00:55:38 -0700 (PDT)
Received: from wmail.tana.it (wmail.tana.it [62.94.243.226]) by ietfa.amsl.com (Postfix) with ESMTP id E7E3221F85C3 for <ietf@ietf.org>; Tue, 23 Oct 2012 00:55:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=beta; t=1350978935; bh=ZCskGTkj3gEGw6WSh2naOj+VBuyCqHd1ICUhemHgnG8=; l=804; h=Date:From:To:References:In-Reply-To; b=WKxiAdIFIkQZUnEdseffAiFZMa2DvgiS/i0OmFuLIvkbQ/LvcqeeZZpyLCwd9wIhA 5HbCVHSA4v0mkU9yc65qvjRO/QxjboEOgv5AJK3Ci6ejTsA+fVObBzwVsaY/60q36c dn8EUYpIypEGzMeO5Bi/+wnrl62hE4Xn0NjXBHeI=
Received: from [172.25.197.158] (pcale.tana [172.25.197.158]) (AUTH: CRAM-MD5 uXDGrn@SYT0/k, TLS: TLS1.0, 256bits, RSA_AES_256_CBC_SHA1) by wmail.tana.it with ESMTPSA; Tue, 23 Oct 2012 09:55:35 +0200 id 00000000005DC033.0000000050864D77.00003D19
Message-ID: <50864D77.3070805@tana.it>
Date: Tue, 23 Oct 2012 09:55:35 +0200
From: Alessandro Vesely <vesely@tana.it>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:16.0) Gecko/20121010 Thunderbird/16.0.1
MIME-Version: 1.0
To: "ietf" <ietf@ietf.org>
Subject: Re: IAOC Request for community feedback
References: <20121022234941.28301.7687.idtracker@ietfa.amsl.com>
In-Reply-To: <20121022234941.28301.7687.idtracker@ietfa.amsl.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, 23 Oct 2012 07:55:38 -0000

On Tue 23/Oct/2012 01:49:41 +0200 The IAOC wrote:
> 
> We have tried to contact Marshall over this time period [...]
> 
> We think this process was not intended to be used when a sitting IAOC,
> IESG, or IAB member vacates his/her position. We believe that the
> intended use of this process was for determining whether a member
> should leave a position who is unwilling to leave and who has harmed
> the IETF. That is clearly not the case in this situation, to the
> contrary, we would have preferred Marshall to continue. It doesn't
> seem appropriate in this case, or when an member is unable to
> participate due to illness or death.

We seem to be missing a keepalive option, to be applicable to IETF
communities at large.  AFAIK, Linkedin and Facebook are not better in
this respect.


From ford@isoc.org  Tue Oct 23 02:38:28 2012
Return-Path: <ford@isoc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 169A321F8686 for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 02:38:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.024
X-Spam-Level: 
X-Spam-Status: No, score=-103.024 tagged_above=-999 required=5 tests=[AWL=0.241, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 06IGyoQcdd1P for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 02:38:27 -0700 (PDT)
Received: from smtp137.dfw.emailsrvr.com (smtp137.dfw.emailsrvr.com [67.192.241.137]) by ietfa.amsl.com (Postfix) with ESMTP id 6FECD21F867B for <ietf@ietf.org>; Tue, 23 Oct 2012 02:38:27 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp23.relay.dfw1a.emailsrvr.com (SMTP Server) with ESMTP id 040492F817D; Tue, 23 Oct 2012 05:38:27 -0400 (EDT)
X-Virus-Scanned: OK
Received: by smtp23.relay.dfw1a.emailsrvr.com (Authenticated sender: ford-AT-isoc.org) with ESMTPSA id 3BD2B2F8359;  Tue, 23 Oct 2012 05:38:26 -0400 (EDT)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: In Memoriam IETF web page
From: Matthew Ford <ford@isoc.org>
In-Reply-To: <5085B108.4030200@cs.tcd.ie>
Date: Tue, 23 Oct 2012 10:38:22 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <F408480F-3B11-48F0-9A20-E0985705A866@isoc.org>
References: <50842367.3040108@dcrocker.net> <61A98088-7151-43A1-95EE-85C327A3240C@vigilsec.com> <m2hapn35k0.wl%randy@psg.com> <12D99082-7020-42CF-BA94-A7D683587CBA@isoc.org> <A1029D11-E3D2-47DD-961A-CED1EB454DEF@cs.columbia.edu> <5085B108.4030200@cs.tcd.ie>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
X-Mailer: Apple Mail (2.1499)
Cc: Megan Kruse <kruse@isoc.org>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Oct 2012 09:38:28 -0000

On 22 Oct 2012, at 21:48, Stephen Farrell <stephen.farrell@cs.tcd.ie> =
wrote:

>=20
>=20
> On 10/22/2012 03:52 PM, Henning Schulzrinne wrote:
>> If we want to keep this in the spirit of long-established (newspaper) =
traditions rather than a web page, we could use the IETF Journal for =
recording the passing of members of the community.
>=20
> This sounds like the best suggestion to me so far
> if something is to be done. Second best would be
> to do nothing.
>=20

In the last issue, we briefly noted the passing of Bob Morgan in the =
online version =
(http://www.internetsociety.org/articles/implementing-identity-management-=
solutions) though it was too late for the print issue. In the latest =
issue we've posted a tribute to Wendy Rickard =
(http://www.internetsociety.org/articles/remembering-wendy-rickard) both =
online and in print.

I think the IETF Journal is a fine place to publish obituaries or =
memorials of IETF contributors to recognise their work and I'd encourage =
anyone moved to write such text to send it to ietfjournal@isoc.org.

Mat



From ynir@checkpoint.com  Tue Oct 23 03:55:57 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 252A021F86C1 for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 03:55:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.582
X-Spam-Level: 
X-Spam-Status: No, score=-10.582 tagged_above=-999 required=5 tests=[AWL=0.017, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ELaobS0r08uE for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 03:55:56 -0700 (PDT)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id B551A21F86BA for <ietf@ietf.org>; Tue, 23 Oct 2012 03:55:55 -0700 (PDT)
Received: from il-ex01.ad.checkpoint.com (il-ex01.ad.checkpoint.com [194.29.34.26]) by smtp.checkpoint.com (8.13.8/8.13.8) with ESMTP id q9NAtrbK009172 for <ietf@ietf.org>; Tue, 23 Oct 2012 12:55:54 +0200
X-CheckPoint: {508675B1-0-1B221DC2-2FFFF}
Received: from il-ex01.ad.checkpoint.com ([194.29.34.26]) by il-ex01.ad.checkpoint.com ([126.0.0.2]) with mapi; Tue, 23 Oct 2012 12:55:53 +0200
From: Yoav Nir <ynir@checkpoint.com>
To: IETF list <ietf@ietf.org>
Date: Tue, 23 Oct 2012 12:55:53 +0200
Subject: Re: IAOC Request for community feedback
Thread-Topic: IAOC Request for community feedback
Thread-Index: Ac2xDPh+tNOHz6FRTla4tDwD9RCISw==
Message-ID: <264769AC-3CC4-47CF-BD01-75C5131ADE0F@checkpoint.com>
References: <20121022234941.28301.7687.idtracker@ietfa.amsl.com> <CAC4RtVAR+RrZ99akHrip_53QJ5=ocaPVn-sq9xLdAKfZPEMrkQ@mail.gmail.com>
In-Reply-To: <CAC4RtVAR+RrZ99akHrip_53QJ5=ocaPVn-sq9xLdAKfZPEMrkQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Oct 2012 10:55:57 -0000

Since you have his postal address, has anyone notified the police?

> The IAOC is requesting feedback from the community concerning a
> vacancy that the IAOC feels is not adequately covered by existing IETF
> rules.
>=20
> Marshall Eubanks has been a active IETF participant for many years and
> a member of the IAOC since 2009. However, he recently stopped
> participating in the IAOC and Trust. The IAOC has made extensive
> efforts to contact Marshall about this, but has not received any
> response. Given the size of the IAOC, a missing member makes it much
> harder to get a quorum. The specifics of his absence include:
>=20
> - Missed the IAOC calls on 11 October 2012, 10 September 2012,
>    6 September 2012, 23 August 2012
>=20
> - No email received from Marshall since 1 August 2012 on the IAOC,
>    IETF Trust, and related private lists.
>=20
> Marshall is subscribed to the IAOC and IETF Trust lists and
> consequently should have received email discussing regular
> IAOC/Trust business including email on this topic.
>=20
> We have tried to contact Marshall over this time period using email 14
> times, telephone 6 times (leaving messages), SMS messages seven times,
> Linkedin messages once, Facebook messages once, and registered postal
> mail twice. We have not received any response from Marshall. It is
> also our understanding that Marshall has stopped participating in
> other IETF lists and stopped working on IDs he authored.
>=20
> On 6 September 2012 the IAOC appointed a replacement liaison to the
> IETF NomCom after learning from the NomCom chair that Marshall had not
> responded to emails from the NomCom chair.
>=20
> Based on all of this, the IAOC has concluded that Marshall's IAOC positio=
n
> is vacant.

Seems to be a solid conclusion.

Yoav



From adrian@olddog.co.uk  Tue Oct 23 04:40:17 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 4F87121F86CE for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 04:40:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.376
X-Spam-Level: 
X-Spam-Status: No, score=-2.376 tagged_above=-999 required=5 tests=[AWL=0.223,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Pj6M5XQAGerz for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 04:40:16 -0700 (PDT)
Received: from asmtp3.iomartmail.com (asmtp3.iomartmail.com [62.128.201.159]) by ietfa.amsl.com (Postfix) with ESMTP id 97D7E21F8644 for <ietf@ietf.org>; Tue, 23 Oct 2012 04:40:16 -0700 (PDT)
Received: from asmtp3.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id q9NBeFeR025587 for <ietf@ietf.org>; Tue, 23 Oct 2012 12:40:15 +0100
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id q9NBeCda025503 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <ietf@ietf.org>; Tue, 23 Oct 2012 12:40:14 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <ietf@ietf.org>
References: <20121022234941.28301.7687.idtracker@ietfa.amsl.com>
In-Reply-To: <20121022234941.28301.7687.idtracker@ietfa.amsl.com>
Subject: RE: IAOC Request for community feedback
Date: Tue, 23 Oct 2012 12:40:11 +0100
Message-ID: <0f6301cdb113$2aab5960$80020c20$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQHux+QtlrTbFLjMhqJjT8gO6gCowpeElJJw
Content-Language: en-gb
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Oct 2012 11:40:17 -0000

> The IAOC is requesting feedback from the community whether it is
> reasonable to declare Marshall's IAOC position vacant.

Yes, with regret. Marshall has done a lot of good stuff for us over the =
years, and I hope he is well and functioning.

However, Marshall filled a community-appointed post on the IAOC and it =
is important that the community is fully represented.

So please ask NomCom to fill the vacant position.

Adrian


From rumbiles@gmail.com  Tue Oct 23 05:28:48 2012
Return-Path: <rumbiles@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9F8FC21F86F4 for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 05:28:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id B4+RZ5nhRXX0 for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 05:28:48 -0700 (PDT)
Received: from mail-ie0-f172.google.com (mail-ie0-f172.google.com [209.85.223.172]) by ietfa.amsl.com (Postfix) with ESMTP id 0791E21F86F3 for <ietf@ietf.org>; Tue, 23 Oct 2012 05:28:47 -0700 (PDT)
Received: by mail-ie0-f172.google.com with SMTP id 9so6071337iec.31 for <ietf@ietf.org>; Tue, 23 Oct 2012 05:28:47 -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=/a8dqWCd5l+lctWGgveaf4OsQ6MbNj+8AaGvaoxjcWM=; b=dQZjnE5C7t0RNaOAJILuOn93zWWKKRIwa2aYpFsXzt9lrSaTPM9QI/0Ou4jhJQDyi1 sZj4TDH3HtiejMzRk4nAMe0PCH63ujF/mfWNlCdmimW7eDkachY/WFFuJueIinPxiA4I EejLrgB8Tww360sG2UbRHZoJS/+6/3UsxOSZ52NpQYudpcn9Furf0MSFYxvWFW2VXSim 9tWiW4atbZqVzvV7TpxS+/rs9oAQH31IJi61jaQ9WXK6d6po3Ps75VFfyxF3+t21lnb5 JEyI7KfTrT0xTyyP+MenLgYIQWOfgEWN9ZhjoynEH53Y3rmY/QUXWhKuuH3VT/yfbebF TU5g==
MIME-Version: 1.0
Received: by 10.50.154.227 with SMTP id vr3mr19731038igb.43.1350995327630; Tue, 23 Oct 2012 05:28:47 -0700 (PDT)
Received: by 10.64.148.47 with HTTP; Tue, 23 Oct 2012 05:28:47 -0700 (PDT)
In-Reply-To: <0f6301cdb113$2aab5960$80020c20$@olddog.co.uk>
References: <20121022234941.28301.7687.idtracker@ietfa.amsl.com> <0f6301cdb113$2aab5960$80020c20$@olddog.co.uk>
Date: Tue, 23 Oct 2012 14:28:47 +0200
Message-ID: <CAOnoajw+Xk+c6qRFa_cZDD3_Vx9F3VEMVCuXNH5jRZUjODvXrg@mail.gmail.com>
Subject: Re: IAOC Request for community feedback
From: Rumbidzayi Gadhula <rumbiles@gmail.com>
To: adrian@olddog.co.uk
Content-Type: multipart/alternative; boundary=14dae934085398be8e04ccb91ca5
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Oct 2012 12:28:48 -0000

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

He has done tremendous work for the IETF. It however appaears as though he
really is unreachable and it makes sense that the post be treated as vacant.

On another note though, it is important to find out what happened to him as
what you have written appears out of character for him (neglecting his
duties). Do you have information on any of his next of kin, friends, other
colleagues, neighbors who you can contact to verify if everything is well
with him, even while his post is now vacant?

On 23 October 2012 13:40, Adrian Farrel <adrian@olddog.co.uk> wrote:

> > The IAOC is requesting feedback from the community whether it is
> > reasonable to declare Marshall's IAOC position vacant.
>
> Yes, with regret. Marshall has done a lot of good stuff for us over the
> years, and I hope he is well and functioning.
>
> However, Marshall filled a community-appointed post on the IAOC and it is
> important that the community is fully represented.
>
> So please ask NomCom to fill the vacant position.
>
> Adrian
>
>

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

<br>He has done tremendous work for the IETF. It however appaears as though=
 he really is unreachable and it makes sense that the post be treated as va=
cant.<br><br>On another note though, it is important to find out what happe=
ned to him as what you have written appears out of character for him (negle=
cting his duties). Do you have information on any of his next of kin, frien=
ds, other colleagues, neighbors who you can contact to verify if everything=
 is well with him, even while his post is now vacant?<br>
<br><div class=3D"gmail_quote">On 23 October 2012 13:40, Adrian Farrel <spa=
n dir=3D"ltr">&lt;<a href=3D"mailto:adrian@olddog.co.uk" target=3D"_blank">=
adrian@olddog.co.uk</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quo=
te" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"=
>
<div class=3D"im">&gt; The IAOC is requesting feedback from the community w=
hether it is<br>
&gt; reasonable to declare Marshall&#39;s IAOC position vacant.<br>
<br>
</div>Yes, with regret. Marshall has done a lot of good stuff for us over t=
he years, and I hope he is well and functioning.<br>
<br>
However, Marshall filled a community-appointed post on the IAOC and it is i=
mportant that the community is fully represented.<br>
<br>
So please ask NomCom to fill the vacant position.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
Adrian<br>
<br>
</font></span></blockquote></div><br><br clear=3D"all"><br><br>

--14dae934085398be8e04ccb91ca5--

From rpelletier@isoc.org  Tue Oct 23 05:35:13 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 16D0921F86FF for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 05:35:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.596
X-Spam-Level: 
X-Spam-Status: No, score=-103.596 tagged_above=-999 required=5 tests=[AWL=0.002, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ucrpd90IjhrM for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 05:35:12 -0700 (PDT)
Received: from smtp157.iad.emailsrvr.com (smtp157.iad.emailsrvr.com [207.97.245.157]) by ietfa.amsl.com (Postfix) with ESMTP id 7380B21F86F6 for <ietf@ietf.org>; Tue, 23 Oct 2012 05:35:12 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp35.relay.iad1a.emailsrvr.com (SMTP Server) with ESMTP id 3C30A2C8666; Tue, 23 Oct 2012 01:34:38 -0400 (EDT)
X-Virus-Scanned: OK
Received: by smtp35.relay.iad1a.emailsrvr.com (Authenticated sender: rpelletier-AT-isoc.org) with ESMTPSA id 020882C8657;  Tue, 23 Oct 2012 01:34:37 -0400 (EDT)
Subject: Re: IAOC Request for community feedback
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: multipart/alternative; boundary=Apple-Mail-336--973643311
From: Pelletier Ray <rpelletier@isoc.org>
In-Reply-To: <CAOnoajw+Xk+c6qRFa_cZDD3_Vx9F3VEMVCuXNH5jRZUjODvXrg@mail.gmail.com>
Date: Tue, 23 Oct 2012 08:35:11 -0400
Message-Id: <82515288-B3D9-43AB-A863-528C019FA69C@isoc.org>
References: <20121022234941.28301.7687.idtracker@ietfa.amsl.com> <0f6301cdb113$2aab5960$80020c20$@olddog.co.uk> <CAOnoajw+Xk+c6qRFa_cZDD3_Vx9F3VEMVCuXNH5jRZUjODvXrg@mail.gmail.com>
To: Rumbidzayi Gadhula <rumbiles@gmail.com>
X-Mailer: Apple Mail (2.1085)
Cc: adrian@olddog.co.uk, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Oct 2012 12:35:13 -0000

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


On Oct 23, 2012, at 8:28 AM, Rumbidzayi Gadhula wrote:

>=20
> He has done tremendous work for the IETF. It however appaears as =
though he really is unreachable and it makes sense that the post be =
treated as vacant.
>=20
> On another note though, it is important to find out what happened to =
him as what you have written appears out of character for him =
(neglecting his duties). Do you have information on any of his next of =
kin, friends, other colleagues, neighbors who you can contact to verify =
if everything is well with him, even while his post is now vacant?

I have exchanged Facebook mail with a family member who said that =
Marshall was focused on other activities geared to securing employment =
opportunities.

Ray


>=20
> On 23 October 2012 13:40, Adrian Farrel <adrian@olddog.co.uk> wrote:
> > The IAOC is requesting feedback from the community whether it is
> > reasonable to declare Marshall's IAOC position vacant.
>=20
> Yes, with regret. Marshall has done a lot of good stuff for us over =
the years, and I hope he is well and functioning.
>=20
> However, Marshall filled a community-appointed post on the IAOC and it =
is important that the community is fully represented.
>=20
> So please ask NomCom to fill the vacant position.
>=20
> Adrian
>=20
>=20
>=20
>=20
>=20


--Apple-Mail-336--973643311
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><br><div><div>On Oct 23, 2012, at 8:28 AM, Rumbidzayi Gadhula =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><br>He has done tremendous work for the IETF. It however =
appaears as though he really is unreachable and it makes sense that the =
post be treated as vacant.<br><br>On another note though, it is =
important to find out what happened to him as what you have written =
appears out of character for him (neglecting his duties). Do you have =
information on any of his next of kin, friends, other colleagues, =
neighbors who you can contact to verify if everything is well with him, =
even while his post is now vacant?<br></blockquote><div><br></div><div>I =
have exchanged Facebook mail with a family member who said that Marshall =
was focused on other activities geared to securing employment =
opportunities.</div><div><br></div><div>Ray</div><div><br></div><br><block=
quote type=3D"cite">
<br><div class=3D"gmail_quote">On 23 October 2012 13:40, Adrian Farrel =
<span dir=3D"ltr">&lt;<a href=3D"mailto:adrian@olddog.co.uk" =
target=3D"_blank">adrian@olddog.co.uk</a>&gt;</span> =
wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class=3D"im">&gt; The IAOC is requesting feedback from the =
community whether it is<br>
&gt; reasonable to declare Marshall's IAOC position vacant.<br>
<br>
</div>Yes, with regret. Marshall has done a lot of good stuff for us =
over the years, and I hope he is well and functioning.<br>
<br>
However, Marshall filled a community-appointed post on the IAOC and it =
is important that the community is fully represented.<br>
<br>
So please ask NomCom to fill the vacant position.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
Adrian<br>
<br>
</font></span></blockquote></div><br><br clear=3D"all"><br><br>
</blockquote></div><br></body></html>=

--Apple-Mail-336--973643311--

From rumbiles@gmail.com  Tue Oct 23 05:50:02 2012
Return-Path: <rumbiles@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CB7EE21F84C7 for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 05:50:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FeKLA+hEZRaL for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 05:50:02 -0700 (PDT)
Received: from mail-ie0-f172.google.com (mail-ie0-f172.google.com [209.85.223.172]) by ietfa.amsl.com (Postfix) with ESMTP id 73F1721F86E8 for <ietf@ietf.org>; Tue, 23 Oct 2012 05:49:59 -0700 (PDT)
Received: by mail-ie0-f172.google.com with SMTP id 9so6106892iec.31 for <ietf@ietf.org>; Tue, 23 Oct 2012 05:49:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=rzn1SiU09j8p8jLHyJvySQL32FEQ17bFBxvQeN8DpNg=; b=xuBPvBaSQKGv+GsBY+SO3GfMUSD6B+QtUGMalFcbRKOjYGP3sZ9qBphPKAD6XQ1tmG 2HAk7qS00BGxUhWL+hjy88HQ/fqQy0J1Q7LLYXKolNhxOGPfBr0SW3Ae5NOrvQTONQcr SzOBHsmTkgT1pe/quONZcu1XW2zE8nDT5fz4UUbvABfmXXeeWkxEQvzI/ivhQUPLvMLi cNsOojRB0N3NIOXYm0Dau2+ptkD/zf5IjPlL6GuwGPUseaAW1DJtQsRKhY+65jonGeJe MU2c9sSlZACNqb0uY1kxDGAOlWrletciOVDG9BqU9u4mafct+tjdt5fBMJknkfls5DJ4 tfEw==
MIME-Version: 1.0
Received: by 10.50.149.163 with SMTP id ub3mr12545429igb.67.1350996599066; Tue, 23 Oct 2012 05:49:59 -0700 (PDT)
Received: by 10.64.148.47 with HTTP; Tue, 23 Oct 2012 05:49:59 -0700 (PDT)
In-Reply-To: <82515288-B3D9-43AB-A863-528C019FA69C@isoc.org>
References: <20121022234941.28301.7687.idtracker@ietfa.amsl.com> <0f6301cdb113$2aab5960$80020c20$@olddog.co.uk> <CAOnoajw+Xk+c6qRFa_cZDD3_Vx9F3VEMVCuXNH5jRZUjODvXrg@mail.gmail.com> <82515288-B3D9-43AB-A863-528C019FA69C@isoc.org>
Date: Tue, 23 Oct 2012 14:49:59 +0200
Message-ID: <CAOnoajzg59YeSEgm_fmxEgJ5+EcSMjtfVLUquix=281NzdP9jQ@mail.gmail.com>
Subject: Re: IAOC Request for community feedback
From: Rumbidzayi Gadhula <rumbiles@gmail.com>
To: Pelletier Ray <rpelletier@isoc.org>
Content-Type: multipart/alternative; boundary=e89a8f3ba31961503004ccb96851
Cc: adrian@olddog.co.uk, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Oct 2012 12:50:03 -0000

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

Thank you Pelletier

On 23 October 2012 14:35, Pelletier Ray <rpelletier@isoc.org> wrote:

>
> On Oct 23, 2012, at 8:28 AM, Rumbidzayi Gadhula wrote:
>
>
> He has done tremendous work for the IETF. It however appaears as though he
> really is unreachable and it makes sense that the post be treated as vacant.
>
> On another note though, it is important to find out what happened to him
> as what you have written appears out of character for him (neglecting his
> duties). Do you have information on any of his next of kin, friends, other
> colleagues, neighbors who you can contact to verify if everything is well
> with him, even while his post is now vacant?
>
>
> I have exchanged Facebook mail with a family member who said that Marshall
> was focused on other activities geared to securing employment opportunities.
>
> Ray
>
>
>
> On 23 October 2012 13:40, Adrian Farrel <adrian@olddog.co.uk> wrote:
>
>> > The IAOC is requesting feedback from the community whether it is
>> > reasonable to declare Marshall's IAOC position vacant.
>>
>> Yes, with regret. Marshall has done a lot of good stuff for us over the
>> years, and I hope he is well and functioning.
>>
>> However, Marshall filled a community-appointed post on the IAOC and it is
>> important that the community is fully represented.
>>
>> So please ask NomCom to fill the vacant position.
>>
>> Adrian
>>
>>
>
>
>
>
>


-- 
*Senior Systems Administrator
UZCHS- NECTAR
Ward C10, Parirenyatwa Hospital
Mazoe St, Avondale
Harare
Tel: +263772 148 889/890 x 320
Cell:0772588210*

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

Thank you Pelletier<br><br><div class=3D"gmail_quote">On 23 October 2012 14=
:35, Pelletier Ray <span dir=3D"ltr">&lt;<a href=3D"mailto:rpelletier@isoc.=
org" target=3D"_blank">rpelletier@isoc.org</a>&gt;</span> wrote:<br><blockq=
uote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc =
solid;padding-left:1ex">
<div style=3D"word-wrap:break-word"><br><div><div class=3D"im"><div>On Oct =
23, 2012, at 8:28 AM, Rumbidzayi Gadhula wrote:</div><br><blockquote type=
=3D"cite"><br>He has done tremendous work for the IETF. It however appaears=
 as though he really is unreachable and it makes sense that the post be tre=
ated as vacant.<br>
<br>On another note though, it is important to find out what happened to hi=
m as what you have written appears out of character for him (neglecting his=
 duties). Do you have information on any of his next of kin, friends, other=
 colleagues, neighbors who you can contact to verify if everything is well =
with him, even while his post is now vacant?<br>
</blockquote><div><br></div></div><div>I have exchanged Facebook mail with =
a family member who said that Marshall was focused on other activities gear=
ed to securing employment opportunities.</div><span class=3D"HOEnZb"><font =
color=3D"#888888"><div>
<br></div><div>Ray</div></font></span><div class=3D"im"><div><br></div><br>=
<blockquote type=3D"cite">
<br><div class=3D"gmail_quote">On 23 October 2012 13:40, Adrian Farrel <spa=
n dir=3D"ltr">&lt;<a href=3D"mailto:adrian@olddog.co.uk" target=3D"_blank">=
adrian@olddog.co.uk</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quo=
te" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"=
>

<div>&gt; The IAOC is requesting feedback from the community whether it is<=
br>
&gt; reasonable to declare Marshall&#39;s IAOC position vacant.<br>
<br>
</div>Yes, with regret. Marshall has done a lot of good stuff for us over t=
he years, and I hope he is well and functioning.<br>
<br>
However, Marshall filled a community-appointed post on the IAOC and it is i=
mportant that the community is fully represented.<br>
<br>
So please ask NomCom to fill the vacant position.<br>
<span><font color=3D"#888888"><br>
Adrian<br>
<br>
</font></span></blockquote></div><br><br clear=3D"all"><br><br>
</blockquote></div></div><br></div></blockquote></div><br><br clear=3D"all"=
><br>-- <br><i>Senior Systems Administrator<br>UZCHS- NECTAR<br>Ward C10, P=
arirenyatwa Hospital<br>Mazoe St, Avondale<br>Harare<br>Tel: +263<span styl=
e=3D"font-family:Arial" lang=3D"en-US">772 148 889/890 x 320<br>
Cell:0772588210</span></i><span lang=3D"en-ZW"></span>


<br>

--e89a8f3ba31961503004ccb96851--

From lberger@labn.net  Tue Oct 23 05:59:40 2012
Return-Path: <lberger@labn.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8CA5521F86B6 for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 05:59:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.014
X-Spam-Level: 
X-Spam-Status: No, score=-101.014 tagged_above=-999 required=5 tests=[AWL=0.651, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, J_CHICKENPOX_14=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VOwT+XpiZ7B9 for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 05:59:39 -0700 (PDT)
Received: from oproxy7-pub.bluehost.com (oproxy7-pub.bluehost.com [67.222.55.9]) by ietfa.amsl.com (Postfix) with SMTP id A255421F86AA for <ietf@ietf.org>; Tue, 23 Oct 2012 05:59:39 -0700 (PDT)
Received: (qmail 16841 invoked by uid 0); 23 Oct 2012 12:59:15 -0000
Received: from unknown (HELO box313.bluehost.com) (69.89.31.113) by oproxy7.bluehost.com with SMTP; 23 Oct 2012 12:59:15 -0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=labn.net; s=default;  h=Content-Transfer-Encoding:Content-Type:In-Reply-To:References:Subject:CC:To:MIME-Version:From:Date:Message-ID; bh=N9kiBjRIwHMqE+M2yc3hVQ9tpCU+0QZcOA/x2nkmd6U=;  b=kuOuWzU6GLzNYUSDn5IBkp2Dy/12Ltbd2WgpPbjVdgqGHtgLSTuwrIJWIhHEZeqedtvCJy23Df4CgsAem1NRo451Us+dunyAk1RDUpCAHZHYJXgW7aaLZcs7FqbLWqD1;
Received: from box313.bluehost.com ([69.89.31.113]:36657 helo=[127.0.0.1]) by box313.bluehost.com with esmtpa (Exim 4.76) (envelope-from <lberger@labn.net>) id 1TQe4h-0007eK-FM; Tue, 23 Oct 2012 06:59:15 -0600
Message-ID: <5086949E.4050305@labn.net>
Date: Tue, 23 Oct 2012 08:59:10 -0400
From: Lou Berger <lberger@labn.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121010 Thunderbird/16.0.1
MIME-Version: 1.0
To: Peng JIANG <pe-jiang@kddi.com>
Subject: Re: Last Call: <draft-kumaki-murai-l3vpn-rsvp-te-06.txt> (Supportfor RSVP-TE in L3VPNs) to Experimental RFC
References: <20120905224357.14197.39927.idtracker@ietfa.amsl.com> <5085E77C.5020100@labn.net> <201210231039.GAJ87540.KFBHtQOJ@kddi.com>
In-Reply-To: <201210231039.GAJ87540.KFBHtQOJ@kddi.com>
X-Enigmail-Version: 1.4.5
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Identified-User: {1038:box313.bluehost.com:labnmobi:labn.net} {sentby:smtp auth 69.89.31.113 authed with lberger@labn.net}
Cc: afarrel@juniper.net, stbryant@cisco.com, draft-kumaki-murai-l3vpn-rsvp-te.all@tools.ietf.org, ietf@ietf.org, daniel@olddog.co.uk
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Oct 2012 12:59:40 -0000

Peng,
	Thanks for the quick response!  Please see in line below.

On 10/22/2012 9:39 PM, Peng JIANG wrote:
> Hello Lou,
> 
>>> As to the technical details, the next hop as identified by the Path 
>>> message in the VPN context, will have a route and associated label 
>>> within the VPN context. This VPN label can be added to the Path 
>>> message, just as it would be for any VPN IP packet, and additional 
>>> labels may be added for PE-PE transport. In implementations that 
>>> rewrite the IP header, the IP destination can be set to the next
>>> hop. The remote PE/next hop will receive the Path message with the
>>> VPN label which will identify the VPN context/VRF. This PE will then
>>> need to identify the packet as RSVP using either the router alert
>>> mechanism or based on the IP header destination address. So I see no
>>> reason for the modifications when the VAN-specific MPLS labels are
>>> used.
>>>
>>> Shout if you think I missed something.
> 
> We think you are correct about the Path message.
> But Resv messages are different. The Resv messages are sent hop-
> by-hop. The destination is not the remote PE but the unicast 
> address of a previous RSVP hop when a PE send out a Resv message.
>
>  Therefor, there will be no VPN label and the remote PE will 
> have no method to identify the VPN context/VRF.
>

I'd expect it to be represented in the HOP object.

Lou

> In RFC 2205:
> 3.1.3 Path Messages
> A Path message travels from a sender to receiver(s) along the 
> same path(s) used by the data packets.  The IP source address of
>  a Path message must be an address of the sender it describes, 
> while the destination address must be the DestAddress for the 
> session.
> 3.1.4 Resv Messages
> Resv messages carry reservation requests hop-by-hop from 
> receivers to senders, along the reverse paths of data flows for 
> the session. The IP destination address of a Resv message is the
>  unicast address of a previous-hop node, obtained from the path 
> state. 
> 
>>> My high-order take away is that it seems to me that this draft runs
>>> counter to hierarchy-based solutions that can solve this problem just
>>> fine without any additional RSVP modifications. I therefore think
>>> this draft should be run through a WG that is willing to reconcile
>>> the approaches (and fully document their uses case supported by
>>> hierarchy). Failing that, I think the draft should have an IESG 
>>> applicability note added saying that this is experimental only and
>>> that standard hierarchy should be used to solve the problem in any 
>>> operational implementation/network.
> As I have explained, For Resv messages, hierarchy-based 
> solutions are not able to identify the VPN context/VRF at a 
> remote PE. 
> 
> Hope the above explaination will make sense to you.
> Please let us konw if you have any further comments.
> 
> Thanks.
> 
> 
> Best Regards,
> Peng JIANG
> KDDI
> 
> 
>>
>> Hello,
>> 	I made this comment privately during the LC period.  I don't mind
>> sharing it more widely:
>>
>>> My high-order take away is that it seems to me that this draft runs
>>> counter to hierarchy-based solutions that can solve this problem just
>>> fine without any additional RSVP modifications. I therefore think
>>> this draft should be run through a WG that is willing to reconcile
>>> the approaches (and fully document their uses case supported by
>>> hierarchy). Failing that, I think the draft should have an IESG 
>>> applicability note added saying that this is experimental only and
>>> that standard hierarchy should be used to solve the problem in any 
>>> operational implementation/network.
>>>
>>> As to the technical details, the next hop as identified by the Path 
>>> message in the VPN context, will have a route and associated label 
>>> within the VPN context. This VPN label can be added to the Path 
>>> message, just as it would be for any VPN IP packet, and additional 
>>> labels may be added for PE-PE transport. In implementations that 
>>> rewrite the IP header, the IP destination can be set to the next
>>> hop. The remote PE/next hop will receive the Path message with the
>>> VPN label which will identify the VPN context/VRF. This PE will then
>>> need to identify the packet as RSVP using either the router alert
>>> mechanism or based on the IP header destination address. So I see no
>>> reason for the modifications when the VAN-specific MPLS labels are
>>> used.
>>>
>>> Shout if you think I missed something.
>>
>> Lou
>> On 9/5/2012 6:43 PM, The IESG wrote:
>>>
>>> The IESG has received a request from an individual submitter to consider
>>> the following document:
>>> - 'Support for RSVP-TE in L3VPNs'
>>>   <draft-kumaki-murai-l3vpn-rsvp-te-06.txt> as Experimental RFC
>>>
>>> The IESG plans to make a decision in the next few weeks, and solicits
>>> final comments on this action. Please send substantive comments to the
>>> ietf@ietf.org mailing lists by 2012-10-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
>>>
>>>
>>>    IP Virtual Private Networks (VPNs) provide connectivity between sites
>>>    across an IP/MPLS backbone. These VPNs can be operated using BGP/MPLS
>>>    and a single provider edge (PE) node may provide access to multiple
>>>    customer sites belonging to different VPNs.
>>>
>>>    The VPNs may support a number of customer services including RSVP and
>>>    RSVP-TE traffic. This document describes how to support RSVP-TE
>>>    between customer sites when a single PE supports multiple VPNs.
>>>
>>>
>>>
>>>
>>>
>>> The file can be obtained via
>>> http://datatracker.ietf.org/doc/draft-kumaki-murai-l3vpn-rsvp-te/
>>>
>>> IESG discussion can be tracked via
>>> http://datatracker.ietf.org/doc/draft-kumaki-murai-l3vpn-rsvp-te/ballot/
>>>
>>>
>>> No IPR declarations have been submitted directly on this I-D.
>>>
>>> Due to an error by the sponsoring Area Director, the Last Call on 
>>> this document (which completed on 3rd September) incorrectly 
>>> stated that this draft was intended that it be published as Informational.
>>> The correct intention (as stated in the draft itself) is that it  be 
>>> published as Experimental. 
>>>
>>> This Last Call is to verify community consensus for publication of
>>> this draft as Experimental. 
>>>
>>>
>>>
>>>
>>>
>>>
>>
> 
> 
> 
> 

From lear@cisco.com  Tue Oct 23 06:32:10 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 0B4F221F870C for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 06:32:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.43
X-Spam-Level: 
X-Spam-Status: No, score=-110.43 tagged_above=-999 required=5 tests=[AWL=0.168, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OapRP+B4fT5o for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 06:32:09 -0700 (PDT)
Received: from ams-iport-4.cisco.com (ams-iport-4.cisco.com [144.254.224.147]) by ietfa.amsl.com (Postfix) with ESMTP id B513F21F8708 for <ietf@ietf.org>; Tue, 23 Oct 2012 06:32:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6126; q=dns/txt; s=iport; t=1350999128; x=1352208728; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to; bh=rbojmuXLikFV4s6zq951z5XaCBwo2mSM/n6ecJA/grA=; b=l0Wz4jGbofIC6XG22A6pDbOkCJtR7L9YaAcUrEwCRUIMkr/TmOCKeTA/ ug+g6j4SfXD0TeCwkcEdYLh4QpYIBzPKvGrh1grY4pKVUiJXoo5ZxRqiV c2hzfLpNa2C3NTiqoFnIfPQfW/oDEAs4fHVKCVZy5h4+dj2Exb/O44JHl o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AkcFAOOahlCQ/khR/2dsb2JhbABEDoYGhV+1coEIgh4BAQEEEgEQVQEQCw4KCRYLAgIJAwIBAgFFBg0BBwEBEAUJh2KcIo0hgjuQPItfhUyBEgOVcY5OgWuCMj8
X-IronPort-AV: E=Sophos;i="4.80,635,1344211200"; d="scan'208,217";a="9033582"
Received: from ams-core-1.cisco.com ([144.254.72.81]) by ams-iport-4.cisco.com with ESMTP; 23 Oct 2012 13:32:07 +0000
Received: from dhcp-10-55-83-129.cisco.com (dhcp-10-55-83-129.cisco.com [10.55.83.129]) by ams-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id q9NDW54R006160 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 23 Oct 2012 13:32:06 GMT
Message-ID: <50869C55.5010905@cisco.com>
Date: Tue, 23 Oct 2012 15:32:05 +0200
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:16.0) Gecko/20121010 Thunderbird/16.0.1
MIME-Version: 1.0
To: Henning Schulzrinne <hgs@cs.columbia.edu>
Subject: Re: In Memoriam IETF web page
References: <50842367.3040108@dcrocker.net> <61A98088-7151-43A1-95EE-85C327A3240C@vigilsec.com> <m2hapn35k0.wl%randy@psg.com> <12D99082-7020-42CF-BA94-A7D683587CBA@isoc.org> <A1029D11-E3D2-47DD-961A-CED1EB454DEF@cs.columbia.edu>
In-Reply-To: <A1029D11-E3D2-47DD-961A-CED1EB454DEF@cs.columbia.edu>
X-Enigmail-Version: 1.4.5
Content-Type: multipart/alternative; boundary="------------090809050909010603070902"
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, 23 Oct 2012 13:32:10 -0000

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

Henning,

I like what you are suggesting, but let me add two things:

  * The ITU does something interesting for notable individuals, which is
    that they offer a space on a web page to collect condolences.  Such
    a virtual book could be then presented to the family, to mark the
    important contributions an individual made.  Often times family
    members have no concept of just how important a person has been to
    their profession, nor how many friends that person REALLY had.
  * On the other side of the coin, I do wish we'd do a better job
    celebrating the achievements of those in our community who are ALIVE.

As Dave might say, these two points are not mutually exclusive.

Eliot

On 10/22/12 4:52 PM, Henning Schulzrinne wrote:
> It is quite common for technical societies (and, I assume, other professional associations) to note the passing of their members and contributors to their field. For many, the IETF is the closest thing they have to such a society and it is a key part of their professional and sometimes personal life.
>
> We sometimes seem to worry too much about scaling problems that never actually occur; the discussion here seems to reflect one of them. I doubt that we'll be inundated with grieving relatives of one-time IETF attendees or IETF list subscribers who want their loved ones to be put on a web page.
>
> If we want to keep this in the spirit of long-established (newspaper) traditions rather than a web page, we could use the IETF Journal for recording the passing of members of the community.
>
> I also think that a longer list serves as a useful reminder that while we all are indebted to the pioneers, the Internet was built by a much larger number of people over the years, just like most human institutions.
>
> As the first generation of contributors reaches zero on their time-to-live counter, this seems like the humane and professional thing to do, whatever precise form it takes.
>
> Henning
>
> On Oct 22, 2012, at 9:26 AM, Pelletier Ray wrote:
>
>> On Oct 21, 2012, at 4:59 PM, Randy Bush wrote:
>>
>>> i started the thread on nanog.  i am not sure abha or jon would want to
>>> be on such a list.  remember them and honor and carry on their work,
>>> don't memorialize them.
>> With all respect, it is not just about the person, it is about their work, its importance, the history of this Internet and providing role models to others.
>>
>> Ray
>>
>>
>>> randy
>>
>
>


--------------090809050909010603070902
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">
    Henning,<br>
    <br>
    I like what you are suggesting, but let me add two things:<br>
    <br>
    <ul>
      <li>The ITU does something interesting for notable individuals,
        which is that they offer a space on a web page to collect
        condolences.  Such a virtual book could be then presented to the
        family, to mark the important contributions an individual made. 
        Often times family members have no concept of just how important
        a person has been to their profession, nor how many friends that
        person REALLY had.</li>
      <li>On the other side of the coin, I do wish we'd do a better job
        celebrating the achievements of those in our community who are
        ALIVE.</li>
    </ul>
    <p>As Dave might say, these two points are not mutually exclusive.<br>
    </p>
    <p>Eliot<br>
    </p>
    <div class="moz-cite-prefix">On 10/22/12 4:52 PM, Henning
      Schulzrinne wrote:<br>
    </div>
    <blockquote
      cite="mid:A1029D11-E3D2-47DD-961A-CED1EB454DEF@cs.columbia.edu"
      type="cite">
      <pre wrap="">It is quite common for technical societies (and, I assume, other professional associations) to note the passing of their members and contributors to their field. For many, the IETF is the closest thing they have to such a society and it is a key part of their professional and sometimes personal life.

We sometimes seem to worry too much about scaling problems that never actually occur; the discussion here seems to reflect one of them. I doubt that we'll be inundated with grieving relatives of one-time IETF attendees or IETF list subscribers who want their loved ones to be put on a web page.

If we want to keep this in the spirit of long-established (newspaper) traditions rather than a web page, we could use the IETF Journal for recording the passing of members of the community.

I also think that a longer list serves as a useful reminder that while we all are indebted to the pioneers, the Internet was built by a much larger number of people over the years, just like most human institutions.

As the first generation of contributors reaches zero on their time-to-live counter, this seems like the humane and professional thing to do, whatever precise form it takes.

Henning

On Oct 22, 2012, at 9:26 AM, Pelletier Ray wrote:

</pre>
      <blockquote type="cite">
        <pre wrap="">
On Oct 21, 2012, at 4:59 PM, Randy Bush wrote:

</pre>
        <blockquote type="cite">
          <pre wrap="">i started the thread on nanog.  i am not sure abha or jon would want to
be on such a list.  remember them and honor and carry on their work,
don't memorialize them.
</pre>
        </blockquote>
        <pre wrap="">
With all respect, it is not just about the person, it is about their work, its importance, the history of this Internet and providing role models to others.

Ray


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

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


</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------090809050909010603070902--

From jari.arkko@piuha.net  Tue Oct 23 06:54:56 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 A6FD021F8646 for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 06:54:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.579
X-Spam-Level: 
X-Spam-Status: No, score=-102.579 tagged_above=-999 required=5 tests=[AWL=0.020, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qkyE9aVFFu+F for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 06:54:54 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by ietfa.amsl.com (Postfix) with ESMTP id EAB5421F85EA for <ietf@ietf.org>; Tue, 23 Oct 2012 06:54:53 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 861052CC56 for <ietf@ietf.org>; Tue, 23 Oct 2012 16:54:50 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id C_DDZCDe1hnO for <ietf@ietf.org>; Tue, 23 Oct 2012 16:54:49 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id EDEAE2CC2F for <ietf@ietf.org>; Tue, 23 Oct 2012 16:54:48 +0300 (EEST)
Message-ID: <5086A1A8.1040102@piuha.net>
Date: Tue, 23 Oct 2012 16:54:48 +0300
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20121011 Thunderbird/16.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: In Memoriam IETF web page
References: <50842367.3040108@dcrocker.net> <61A98088-7151-43A1-95EE-85C327A3240C@vigilsec.com> <m2hapn35k0.wl%randy@psg.com> <12D99082-7020-42CF-BA94-A7D683587CBA@isoc.org> <A1029D11-E3D2-47DD-961A-CED1EB454DEF@cs.columbia.edu> <50869C55.5010905@cisco.com>
In-Reply-To: <50869C55.5010905@cisco.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, 23 Oct 2012 13:54:56 -0000

I wish I had known Abha. I recently searched for information about her, as I was curious about her short AD career on some statistic that I looked up. She seemed like a very nice person based on the stories that I found.

But back to topic. I'm with Benson on this issue. And I also think that whoever we at the IETF think is "important" probably wrote enough important RFCs. At least for me, those RFCs far outweigh any "in memoriam" RFC that might be written for him or her. Those RFCs are the ones that I want to remember those persons from.

But I do like the idea of in memoriam articles in the IETF journal.

Jari


From jari.arkko@piuha.net  Tue Oct 23 07:01:38 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 A745A21F86BD for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 07:01:38 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CxP+Toxsv+Ku for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 07:01:38 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by ietfa.amsl.com (Postfix) with ESMTP id 0B6D221F86C1 for <ietf@ietf.org>; Tue, 23 Oct 2012 07:01:38 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id EB4E62CC56; Tue, 23 Oct 2012 17:01:30 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gjwea-Hvpcwg; Tue, 23 Oct 2012 17:01:29 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 23A4B2CC2F; Tue, 23 Oct 2012 17:01:29 +0300 (EEST)
Message-ID: <5086A338.8070101@piuha.net>
Date: Tue, 23 Oct 2012 17:01:28 +0300
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20121011 Thunderbird/16.0.1
MIME-Version: 1.0
To: Pelletier Ray <rpelletier@isoc.org>, "Eggert, Lars" <lars@netapp.com>
Subject: Re: IAOC Request for community feedback
References: <20121022234941.28301.7687.idtracker@ietfa.amsl.com> <0f6301cdb113$2aab5960$80020c20$@olddog.co.uk> <CAOnoajw+Xk+c6qRFa_cZDD3_Vx9F3VEMVCuXNH5jRZUjODvXrg@mail.gmail.com> <82515288-B3D9-43AB-A863-528C019FA69C@isoc.org>
In-Reply-To: <82515288-B3D9-43AB-A863-528C019FA69C@isoc.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Oct 2012 14:01:38 -0000

Lars Eggert wrote:

> On Oct 23, 2012, at 4:42, Barry Leiba<barryleiba@computer.org>  wrote:
>>> The IAOC is requesting feedback from the community whether it is
>>> reasonable to declare Marshall's IAOC position vacant.
>> Yes.
> +1

+1

Ray Pelletier wrote:

>  Marshall was focused on other activities

That's good to hear. I was worried about him when I read the mail from Bob. And yes, this can happen with people. Dayjobs or businesses or personal issues can sometimes cause this. Lets welcome him back to the IETF when he finishes his other business.

Jari


From stephen.farrell@cs.tcd.ie  Tue Oct 23 07:03:51 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 2905121F86DE for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 07:03:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9K0F1Eef0d92 for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 07:03:50 -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 757E721F8694 for <ietf@ietf.org>; Tue, 23 Oct 2012 07:03:50 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hermes.scss.tcd.ie (Postfix) with ESMTP id 892BF171479; Tue, 23 Oct 2012 15:03:49 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; h= content-transfer-encoding:content-type:in-reply-to:references :subject:mime-version:user-agent:from:date:message-id:received :received:x-virus-scanned; s=cs; t=1351001019; bh=HK6c56dF/Pv+44 NeRMm3kXOEK9ASJzwKHocX4lBRw34=; b=F/IIdxhFbnXZzkSu/20dUnR+RT14Tl NLLL0sGbYbEYcr+nurXVAlcB9/GSw+DAoOAqsIZux3WVgVLIVpdXxZzeQkrGhOuI YMEuk7NvY12euiMMzq657g522m+dMACDC+OJX26SYJUYeZEhLblaJrEe1PY2ndC6 O39ftqPUwzKVKWZIhbZkSi484fixjwF541LVsR4D/k60PnVV3xR/GjFnNGXmLt2s JJzvA07BscaTNA1N39V5vQm5ydD7zUx7vZ09vmdmyOUTAgn+vT8oZ4GvhQ6ERMRg u61Mi6D388H1jNTD1m7mqr61A3DL9HAUQf0SqizahKg2s4/nkQyYyFVw==
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 lK+Be+58Sjdq; Tue, 23 Oct 2012 15:03:39 +0100 (IST)
Received: from [IPv6:2001:770:10:203:a4de:b3a6:e192:7089] (unknown [IPv6:2001:770:10:203:a4de:b3a6:e192:7089]) by smtp.scss.tcd.ie (Postfix) with ESMTPSA id D6E96171473; Tue, 23 Oct 2012 15:03:34 +0100 (IST)
Message-ID: <5086A3B7.7060208@cs.tcd.ie>
Date: Tue, 23 Oct 2012 15:03:35 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20121017 Thunderbird/16.0.1
MIME-Version: 1.0
To: Jari Arkko <jari.arkko@piuha.net>
Subject: Re: IAOC Request for community feedback
References: <20121022234941.28301.7687.idtracker@ietfa.amsl.com> <0f6301cdb113$2aab5960$80020c20$@olddog.co.uk> <CAOnoajw+Xk+c6qRFa_cZDD3_Vx9F3VEMVCuXNH5jRZUjODvXrg@mail.gmail.com> <82515288-B3D9-43AB-A863-528C019FA69C@isoc.org> <5086A338.8070101@piuha.net>
In-Reply-To: <5086A338.8070101@piuha.net>
X-Enigmail-Version: 1.4.5
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Oct 2012 14:03:51 -0000

On 10/23/2012 03:01 PM, Jari Arkko wrote:
> Lars Eggert wrote:
> 
>> On Oct 23, 2012, at 4:42, Barry Leiba<barryleiba@computer.org>  wrote:
>>>> The IAOC is requesting feedback from the community whether it is
>>>> reasonable to declare Marshall's IAOC position vacant.
>>> Yes.
>> +1
> 
> +1

Ditto.

> 
> Ray Pelletier wrote:
> 
>>  Marshall was focused on other activities
> 
> That's good to hear. I was worried about him when I read the mail from
> Bob. And yes, this can happen with people. Dayjobs or businesses or
> personal issues can sometimes cause this. Lets welcome him back to the
> IETF when he finishes his other business.

Nicely said,
S.


> 
> Jari
> 
> 
> 

From ian@hixie.ch  Mon Oct 22 10:55:45 2012
Return-Path: <ian@hixie.ch>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 029BE21F8A71 for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 10:55:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xV3rSqyHO3b6 for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 10:55:43 -0700 (PDT)
Received: from homiemail-a52.g.dreamhost.com (caibbdcaaaaf.dreamhost.com [208.113.200.5]) by ietfa.amsl.com (Postfix) with ESMTP id A931A21F8A6E for <ietf@ietf.org>; Mon, 22 Oct 2012 10:55:43 -0700 (PDT)
Received: from homiemail-a52.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a52.g.dreamhost.com (Postfix) with ESMTP id 9D0576B826A; Mon, 22 Oct 2012 10:55:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=hixie.ch; h=date:from:to :cc:subject:in-reply-to:message-id:references:mime-version: content-type; s=hixie.ch; bh=UkcNbuyOvGdYfCUBQ65OxZRW5mA=; b=dz1 GvT4mFYDJ/1MHSMND7D/fmjnUUmTQtUCRGMFDKbmyssk7XV/bmAmn4OIy7J/J6yb ZLdR3ImmrkjFhHu2uIj5oqT/W4YCFIbB305Hr+Yev9+O5GbR7kZDT1ukwzJmVh54 2JANh7zD2Gty/uKK/7kDOepYIB2ZmxUJGYURnMio=
Received: from ps20323.dreamhostps.com (ps20323.dreamhost.com [69.163.222.251]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: internal@index.hixie.ch) by homiemail-a52.g.dreamhost.com (Postfix) with ESMTPSA id 4A6576B80B8;  Mon, 22 Oct 2012 10:55:45 -0700 (PDT)
Date: Mon, 22 Oct 2012 17:55:42 +0000 (UTC)
From: Ian Hickson <ian@hixie.ch>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: [whatwg] New URL Standard from Anne van Kesteren on 2012-09-24 (public-whatwg-archive@w3.org from September 2012)
In-Reply-To: <50856E3C.103@gmail.com>
Message-ID: <Pine.LNX.4.64.1210221753010.2471@ps20323.dreamhostps.com>
References: <50604C1A.7090901@gmx.de> <5060A964.5060001@stpeter.im> <Pine.LNX.4.64.1210172354500.2478@ps20323.dreamhostps.com> <507F5A7E.6040206@arcanedomain.com> <50856E3C.103@gmail.com>
Content-Language: en-GB-hixie
Content-Style-Type: text/css
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Mailman-Approved-At: Tue, 23 Oct 2012 09:13:03 -0700
Cc: Noah Mendelsohn <nrm@arcanedomain.com>, Julian Reschke <julian.reschke@gmx.de>, URI <uri@w3.org>, IETF Discussion <ietf@ietf.org>, mnot@mnot.net
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Oct 2012 17:55:45 -0000

On Mon, 22 Oct 2012, Brian E Carpenter wrote:
> On 18/10/2012 02:25, Noah Mendelsohn wrote:
> > On 10/17/2012 7:57 PM, Ian Hickson wrote:
> >> Yeah. Turns out we (the Web standards community) haven't been doing 
> >> such a great job of making our specificatiosn match reality.:-(
> > 
> > Um, true... but it's also the case that the implementation community 
> > hasn't over the years been doing as much as might be best to make 
> > reality match the specifications. The new specs we're writing now 
> > would like have been a lot thinner and cleaner if they had.
> 
> However, I think the concern here is that if certain IETF specs need to 
> be updated to match the real world, that work needs to be done in the 
> IETF.

I couldn't agree more! We've been waiting for four years for the URI 
working group to get their act together and fix the URL mess. Nothing has 
happened. We lost patience and are now doing it ourselves.

I'm sure Anne would love nothing more than to be able to work on something 
more interesting that this. But at the end of the day, someone has to do 
it, and y'all aren't doing it.

This should not come as a surprise to anyone, the IETF and W3C have been 
discussing this matter at last as far back as 2008.


> It can't be done by reference in a W3C document; it has to be done by 
> value in an IETF document.

Currently it's only being done in a WHATWG document.

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'

From nrm@arcanedomain.com  Mon Oct 22 11:29:46 2012
Return-Path: <nrm@arcanedomain.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 30F2D11E80A2 for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 11:29:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4wjhEyf1R8W3 for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 11:29:45 -0700 (PDT)
Received: from homiemail-a62.g.dreamhost.com (caiajhbdcbhh.dreamhost.com [208.97.132.177]) by ietfa.amsl.com (Postfix) with ESMTP id 71F9911E80EE for <ietf@ietf.org>; Mon, 22 Oct 2012 11:29:45 -0700 (PDT)
Received: from homiemail-a62.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a62.g.dreamhost.com (Postfix) with ESMTP id 348CA634075; Mon, 22 Oct 2012 11:29:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=arcanedomain.com; h= message-id:date:from:mime-version:to:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; s= arcanedomain.com; bh=wmb+i1f2My4odDBMWRN0W4WitHQ=; b=JKR+HFJVZqL DghIP9oq2eNxHUDUp3PaiLhwL5XgbPmowe7/Gobk3x/UMeu/It8gcDNMmeCzSI8u pBHueSb3r1aL7aKdySi5Ems0gs28ZW1J35WBDX5/m+2KjAEOciXAg19baLR3Jdo9 fdHhLGjeP9ZcmF/c0AB9Q6FC9kGvFqTc=
Received: from [192.168.1.70] (unknown [146.115.66.224]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: webmaster@arcanedomain.com) by homiemail-a62.g.dreamhost.com (Postfix) with ESMTPSA id 6353E63406F;  Mon, 22 Oct 2012 11:29:44 -0700 (PDT)
Message-ID: <5085909E.3040609@arcanedomain.com>
Date: Mon, 22 Oct 2012 14:29:50 -0400
From: Noah Mendelsohn <nrm@arcanedomain.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:16.0) Gecko/20121010 Thunderbird/16.0.1
MIME-Version: 1.0
To: Ian Hickson <ian@hixie.ch>
Subject: Re: [whatwg] New URL Standard from Anne van Kesteren on 2012-09-24 (public-whatwg-archive@w3.org from September 2012)
References: <50604C1A.7090901@gmx.de> <5060A964.5060001@stpeter.im> <Pine.LNX.4.64.1210172354500.2478@ps20323.dreamhostps.com> <507F5A7E.6040206@arcanedomain.com> <50856E3C.103@gmail.com> <Pine.LNX.4.64.1210221753010.2471@ps20323.dreamhostps.com>
In-Reply-To: <Pine.LNX.4.64.1210221753010.2471@ps20323.dreamhostps.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Tue, 23 Oct 2012 09:13:03 -0700
Cc: Julian Reschke <julian.reschke@gmx.de>, mnot@mnot.net, URI <uri@w3.org>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Oct 2012 18:29:46 -0000

On Mon, 22 Oct 2012, Brian E Carpenter wrote:
 > On 18/10/2012 02:25, Noah Mendelsohn wrote:
 >> On 10/17/2012 7:57 PM, Ian Hickson wrote:
 >>> Yeah. Turns out we (the Web standards community) haven't been doing
 >>> such a great job of making our specificatiosn match reality.:-(
 >>
 >> Um, true... but it's also the case that the implementation community
 >> hasn't over the years been doing as much as might be best to make
 >> reality match the specifications. The new specs we're writing now
 >> would like have been a lot thinner and cleaner if they had.
 >
 > However, I think the concern here is that if certain IETF specs need to
 > be updated to match the real world, that work needs to be done in the
 > IETF.

That's certainly an important concern, but it's not the one I had in mind 
when I made my comment.

Rather, while Ian is right that our new specifications must match today's 
"reality", we should also be sobered by the price we're paying for years of 
implementations that do things like sniffing. Yes, given that it's become 
widespread, documenting ways to do it interoperably and securely is good. 
I'm not convinced that implementing sniffing in widely-used user agents was 
the right choice way back when.

So, let's try harder than we have in the past to not introduce yet more 
such cruftiness, even if we do have to document what's there. Maybe we 
should have been a little more hesitant to do things like having both SVG 
and Canvas as ways of doing graphics. Perhaps that overlapping function is 
ultimately justified, but there's a long term cost. We're moving too far 
away from KISS IMO.

HTML5 is great work, but the spec is very, very thick. Keeping things as 
small and simple as we can moving forward is really what I had in mind.

Noah

From chuck.lever@oracle.com  Mon Oct 22 13:10:25 2012
Return-Path: <chuck.lever@oracle.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CE4C221F88EE; Mon, 22 Oct 2012 13:10:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.872
X-Spam-Level: 
X-Spam-Status: No, score=-8.872 tagged_above=-999 required=5 tests=[AWL=-0.574, BAYES_00=-2.599, MANGLED_LIST=2.3, RCVD_IN_DNSWL_HI=-8, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1Pav7CmHv+3I; Mon, 22 Oct 2012 13:10:25 -0700 (PDT)
Received: from rcsinet15.oracle.com (rcsinet15.oracle.com [148.87.113.117]) by ietfa.amsl.com (Postfix) with ESMTP id 0B3CE21F88EC; Mon, 22 Oct 2012 13:10:24 -0700 (PDT)
Received: from acsinet22.oracle.com (acsinet22.oracle.com [141.146.126.238]) by rcsinet15.oracle.com (Sentrion-MTA-4.2.2/Sentrion-MTA-4.2.2) with ESMTP id q9MKAHZx004216 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 22 Oct 2012 20:10:18 GMT
Received: from acsmt357.oracle.com (acsmt357.oracle.com [141.146.40.157]) by acsinet22.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id q9MKAHeL015793 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 22 Oct 2012 20:10:17 GMT
Received: from abhmt112.oracle.com (abhmt112.oracle.com [141.146.116.64]) by acsmt357.oracle.com (8.12.11.20060308/8.12.11) with ESMTP id q9MKAGMQ030301; Mon, 22 Oct 2012 15:10:16 -0500
Received: from moret.1015granger.net (/99.26.161.222) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Mon, 22 Oct 2012 13:10:16 -0700
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: Gen-ART review of draft-ietf-nfsv4-federated-fs-protocol-13
From: Chuck Lever <chuck.lever@oracle.com>
In-Reply-To: <CCAA0CA5.11A5%peter@akayla.com>
Date: Mon, 22 Oct 2012 16:10:16 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <F9C49DE0-5BB3-4714-96A7-96EA7DA94DF7@oracle.com>
References: <CCAA0CA5.11A5%peter@akayla.com>
To: Peter Yee <peter@akayla.com>
X-Mailer: Apple Mail (2.1499)
X-Source-IP: acsinet22.oracle.com [141.146.126.238]
X-Mailman-Approved-At: Tue, 23 Oct 2012 09:13:03 -0700
Cc: gen-art@ietf.org, "ietf@ietf.org" <ietf@ietf.org>, draft-ietf-nfsv4-federated-fs-protocol.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, 22 Oct 2012 20:10:25 -0000

On Oct 21, 2012, at 11:35 PM, Peter Yee <peter@akayla.com> wrote:

> Chuck,
> 	Ranges include the 0,255 that appears commonly in the document =
in
> attribute definitions along with one case of -2147483648,2147483647.

Hi Peter-

Upon further review, I see the document uses "interval notation" when =
defining ranges of allowed values in attributes.  The use of square =
brackets denotes inclusivity.  If you feel readers need more, or our use =
of this notation is inconsistent, I'm happy to add clarification.

> 	Kind regards,
> 		-Peter
>=20
> On 10/21/12 3:27 PM, "Chuck Lever" <chuck.lever@oracle.com> wrote:
>=20
>>=20
>> On Oct 21, 2012, at 5:39 PM, Peter Yee <peter@akayla.com> wrote:
>>=20
>>> I am the assigned Gen-ART reviewer for this draft. For background on
>>> Gen-ART, please see the FAQ at
>>> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>
>>>=20
>>> Document: draft-ietf-nfsv4-federated-fs-protocol-13
>>> Reviewer: Peter Yee
>>> Review Date: Oct-19-2012
>>> IETF LC End Date: Oct-22-2012
>>> IESG Telechat date: TBD
>>>=20
>>>=20
>>> Summary: This draft is basically ready for publication, but has nits
>>> that
>>> should be fixed before publication. [Ready with nits.]
>>>=20
>>>=20
>>> This Standards Track document describes a protocol for maintaining a
>>> Namespace Database for use with federated filesystem protocols.  The
>>> document is well-written with good examples and little need to jump =
back
>>> and forth in the text to understand it.
>>>=20
>>> General: Are ranges (in attribute values) inclusive or exclusive?  =
They
>>> appear to be inclusive, but it might be worth saying that somewhere, =
if
>>> only once.
>>=20
>> Can you give me an example of a range that might need clarification?
>>=20
>> I will address these comments and co-ordinate draft updates with our =
WG
>> editor, Tom Haynes.
>>=20
>> Thanks for your review.
>>=20
>>> Section 2.7, NsdbName definition: expand NSDB to Namespace Database =
as
>>> this is the first use of the term.
>>>=20
>>> Section 2.8.1, 2nd sentence: "extention" -> "extension"
>>>=20
>>> Section 2.8.3, 2nd paragraph, last sentence: in addition to checking =
for
>>> added FSL records, shouldn't the fileserver also be checking for =
deleted
>>> or migrated FSLs?  And why would the fileserver do this at the
>>> expiration
>>> of the FSN TTL instead of waiting for the next access to the that =
FSN?
>>> Otherwise the fileserver could be generating unnecessary traffic,
>>> although
>>> there is a tradeoff to be made vs. performance.
>>>=20
>>> Section 2.8.3, 3rd paragraph after bullet items, 1st sentence: =
"which"
>>> ->
>>> "that".  (Yeah, I know, grammar police.)
>>>=20
>>> Section 2.9, 3rd paragraph, 2nd sentence: "admininistrative" ->
>>> "administrative"
>>>=20
>>> Section 2.12, 2nd paragraph, last sentence: expand NCE (NSDB =
Container
>>> Entry) as this is the first use of the term.
>>>=20
>>> Section 3.2, item #5: "fs_location" -> "fs_locations"
>>>=20
>>> Section 4.1, 1st paragraph, 3rd sentence: probably worth expanding =
"DSE"
>>> to "DSA-specific entry" here.
>>>=20
>>> Section 4.2.1.8, 1st paragraph, 2nd sentence: bracket "Section =
2.8.1" in
>>> "(see" and ")" for readability.
>>>=20
>>> Section 4.2.2: "LDAP Objects" -> "LDAP Object Classes" seems
>>> appropriate.
>>>=20
>>> Section 4.2.2.1, 2nd and 3rd sentences: replace "fedfsFsn" with
>>> "fedfsNsdbContainerInfo"
>>>=20
>>> Section 4.2.2.2, 5th paragraph: how is the prohibition on =
referencing
>>> other attributes in the fedfsFsn object class supposed to work if =
this
>>> document is the defining document for that object class?
>>>=20
>>> Section 5.1.3.1, 1st paragraph after LDIF definition: a port number =
of
>>> 2049 is given.  Since this is already the default value, why not use =
a
>>> different value?  Otherwise, there would be no practical need to =
include
>>> that port number in the FSL creation request.
>>>=20
>>> Section 5.1.3.1, 1st paragraph after LDIF definition: "up to date" =
->
>>> "up-to-date"
>>>=20
>>> Section 5.1.3.2, 2nd paragraph: "a" -> "an"
>>>=20
>>> Section 5.1.3.2, table entry for "fedfsNfsVarSub": "substituion" ->
>>> "substitution"
>>>=20
>>> Section 5.1.4, 1st paragraph, 1st sentence: "a Fileset location" -> =
"an
>>> FSL"
>>>=20
>>> Section 7.3, 2nd paragraph, "Specification" value: presumably this =
will
>>> be
>>> changed to the RFC number when issued?
>>>=20
>>> Section 8, 1st paragraph (definition of Administrator): "an" -> "a"
>>>=20
>>> Section 8, 3rd paragraph (definition of Client): "filesystem access" =
->
>>> "file-access" for consistency of usage with the rest of the =
document.
>>>=20
>>> Section 8, 5th paragraph (definition of Fileserver): rather than
>>> discussing "a filesystem", should this be "one or more filesystems"? =
 Or
>>> is a fileserver limited to exporting one filesystem?
>>>=20
>>> Section 8, 8th paragraph (definition of Filesystem Access Protocol):
>>> following up on the 3rd paragraph, should this be "File-access =
Protocol"
>>> for consistency?
>>>=20
>>> Section 8, 9th paragraph (definition of FSL), 2nd sentence:
>>> "fs_location"
>>> -> "fs_locations".
>>>=20
>>>=20
>>>=20
>>=20
>> --=20
>> Chuck Lever
>> chuck[dot]lever[at]oracle[dot]com
>>=20
>>=20
>>=20
>>=20
>>=20
>=20
> <default[4].xml>

--=20
Chuck Lever
chuck[dot]lever[at]oracle[dot]com





From fielding@gbiv.com  Mon Oct 22 14:00:18 2012
Return-Path: <fielding@gbiv.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3BD441F0C69 for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 14:00:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[AWL=-4.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id x4-wS2E8CTP9 for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 14:00:17 -0700 (PDT)
Received: from homiemail-a90.g.dreamhost.com (caiajhbdcagg.dreamhost.com [208.97.132.66]) by ietfa.amsl.com (Postfix) with ESMTP id 732C41F0C5C for <ietf@ietf.org>; Mon, 22 Oct 2012 14:00:17 -0700 (PDT)
Received: from homiemail-a90.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a90.g.dreamhost.com (Postfix) with ESMTP id 19A9D2AC075; Mon, 22 Oct 2012 14:00:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=gbiv.com; h=subject :mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=gbiv.com; bh=TSyJ8wM86OG79GSuvxN+tTG3iVU=; b=rHgWN14ZZNaRbAEsdqiSaAK/S1MN /eJmWytCIDdWFJc5L6Sgm5dWaM3L2L9siRd8dl1W/Ov8A7Tx2uj4w6A+aDA0A2gn NsWM6+IQtR+QkDf2bWj+Lz2zIeJwSC9Q1UFO/asykcBYZ5gwQQVawm+STEhftNR+ iQqymoLdqgVmb3Y=
Received: from [192.168.1.84] (99-21-208-82.lightspeed.irvnca.sbcglobal.net [99.21.208.82]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: fielding@gbiv.com) by homiemail-a90.g.dreamhost.com (Postfix) with ESMTPSA id 823D92AC06A;  Mon, 22 Oct 2012 14:00:16 -0700 (PDT)
Subject: Re: [whatwg] New URL Standard from Anne van Kesteren on 2012-09-24 (public-whatwg-archive@w3.org from September 2012)
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=us-ascii
From: "Roy T. Fielding" <fielding@gbiv.com>
In-Reply-To: <Pine.LNX.4.64.1210221753010.2471@ps20323.dreamhostps.com>
Date: Mon, 22 Oct 2012 14:00:14 -0700
Content-Transfer-Encoding: 7bit
Message-Id: <0DBC8A11-319C-4120-975E-7E40FD5818BF@gbiv.com>
References: <50604C1A.7090901@gmx.de> <5060A964.5060001@stpeter.im> <Pine.LNX.4.64.1210172354500.2478@ps20323.dreamhostps.com> <507F5A7E.6040206@arcanedomain.com> <50856E3C.103@gmail.com> <Pine.LNX.4.64.1210221753010.2471@ps20323.dreamhostps.com>
To: Ian Hickson <ian@hixie.ch>
X-Mailer: Apple Mail (2.1283)
X-Mailman-Approved-At: Tue, 23 Oct 2012 09:13:03 -0700
Cc: IETF Discussion <ietf@ietf.org>, Noah Mendelsohn <nrm@arcanedomain.com>, mnot@mnot.net, Julian Reschke <julian.reschke@gmx.de>, URI <uri@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: Mon, 22 Oct 2012 21:00:18 -0000

On Oct 22, 2012, at 10:55 AM, Ian Hickson wrote:
> On Mon, 22 Oct 2012, Brian E Carpenter wrote:
>> On 18/10/2012 02:25, Noah Mendelsohn wrote:
>>> On 10/17/2012 7:57 PM, Ian Hickson wrote:
>>>> Yeah. Turns out we (the Web standards community) haven't been doing 
>>>> such a great job of making our specificatiosn match reality.:-(
>>> 
>>> Um, true... but it's also the case that the implementation community 
>>> hasn't over the years been doing as much as might be best to make 
>>> reality match the specifications. The new specs we're writing now 
>>> would like have been a lot thinner and cleaner if they had.
>> 
>> However, I think the concern here is that if certain IETF specs need to 
>> be updated to match the real world, that work needs to be done in the 
>> IETF.
> 
> I couldn't agree more! We've been waiting for four years for the URI 
> working group to get their act together and fix the URL mess. Nothing has 
> happened. We lost patience and are now doing it ourselves.

What you are insisting on defining as a "URL" is the input to the
process of making a hypertext reference (the arbitrary string typed
into a dialog or placed inside an href/src attribute), whereas the
IETF standards define the output of that process as a uniform
addressing syntax for use on the Internet by every application that
makes use of Web addresses.  Browsers implement both the input
processing and the output URI standards.  HTML must define the
input processing, either within the spec or by reference to a
new spec. The IETF defined the output standards for what goes
on the wire.

I would love to have a single standard for hypertext references.
However, they are not URLs, they are not implemented consistently
across HTML elements, and even within single elements they are
not implemented consistently across browsers.  It is a worthwhile
area to pursue further consistency, but only if you stop referring
to them as something they are not and never will be. "" is not a URL.

> I'm sure Anne would love nothing more than to be able to work on something 
> more interesting that this. But at the end of the day, someone has to do 
> it, and y'all aren't doing it.
> 
> This should not come as a surprise to anyone, the IETF and W3C have been 
> discussing this matter at last as far back as 2008.

Yes, we have been discussing it since 1994.  It would be nice
if you would take the advice already received and define
references in HTML, including the algorithms for converting them
into URI references (for DOM and network usage) and IRI
references (for display).

There is no need for any willful violations, since you aren't
even defining the same things.

....Roy


From ian@hixie.ch  Mon Oct 22 14:47:01 2012
Return-Path: <ian@hixie.ch>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8492D11E80E4 for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 14:47:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EBVei4KTZCZa for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 14:47:00 -0700 (PDT)
Received: from homiemail-a57.g.dreamhost.com (caibbdcaaaaf.dreamhost.com [208.113.200.5]) by ietfa.amsl.com (Postfix) with ESMTP id ABC141F042B for <ietf@ietf.org>; Mon, 22 Oct 2012 14:46:56 -0700 (PDT)
Received: from homiemail-a57.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a57.g.dreamhost.com (Postfix) with ESMTP id 0F793208073; Mon, 22 Oct 2012 14:46:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=hixie.ch; h=date:from:to :cc:subject:in-reply-to:message-id:references:mime-version: content-type; s=hixie.ch; bh=fSpWlUw2oz9502BQQIxlxr2Z34w=; b=acN yEZFH48HITssQv3fc/yUw2BZ4yv1D9cDz66ylwv9yD3livYeoT8rq9XyNe53Ac0A yt1JszMe4FPUaMKHdbHmsUtZrLIb66udBCqTWsYp9PcsCis8vxgegVa3sBGT7S96 j31s2Az17qsr0J/oOhJMF/cuEoOugTzivX1WllUk=
Received: from ps20323.dreamhostps.com (ps20323.dreamhost.com [69.163.222.251]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: internal@index.hixie.ch) by homiemail-a57.g.dreamhost.com (Postfix) with ESMTPSA id 0281F208070;  Mon, 22 Oct 2012 14:46:55 -0700 (PDT)
Date: Mon, 22 Oct 2012 21:46:56 +0000 (UTC)
From: Ian Hickson <ian@hixie.ch>
To: Julian Reschke <julian.reschke@gmx.de>,  "Roy T. Fielding" <fielding@gbiv.com>
Subject: Re: [whatwg] New URL Standard from Anne van Kesteren on 2012-09-24 (public-whatwg-archive@w3.org from September 2012)
In-Reply-To: <0DBC8A11-319C-4120-975E-7E40FD5818BF@gbiv.com>
Message-ID: <Pine.LNX.4.64.1210222137530.2471@ps20323.dreamhostps.com>
References: <50604C1A.7090901@gmx.de> <5060A964.5060001@stpeter.im> <Pine.LNX.4.64.1210172354500.2478@ps20323.dreamhostps.com> <507F5A7E.6040206@arcanedomain.com> <50856E3C.103@gmail.com> <Pine.LNX.4.64.1210221753010.2471@ps20323.dreamhostps.com> <0DBC8A11-319C-4120-975E-7E40FD5818BF@gbiv.com>
Content-Language: en-GB-hixie
Content-Style-Type: text/css
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Mailman-Approved-At: Tue, 23 Oct 2012 09:13:03 -0700
Cc: Noah Mendelsohn <nrm@arcanedomain.com>, mnot@mnot.net, URI <uri@w3.org>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Oct 2012 21:47:01 -0000

On Mon, 22 Oct 2012, Julian Reschke wrote:
> > 
> > I couldn't agree more! We've been waiting for four years for the URI 
> > working group to get their act together and fix the URL mess. Nothing 
> > has happened. We lost patience and are now doing it ourselves. ...
> 
> Clarifying: there is no URI Working Group, and as far as I can tell, 

Whoever. The people complaining that it should be done at the IETF haven't 
done any work. That's the complaint. Until they do the work, complaining 
that we're doing it instead is going to fall on deaf ears and be met with 
the rolling of eyeballs.


> there is no consensus that there is a "mess" to fix related to URIs.

The specs don't define everything that implementations have to do to be 
interoperable. If the IETF doesn't think that's a problem, then that's 
fine, but then y'all shouldn't be surprised when people who _do_ think 
that's a problem try and fix it.


On Mon, 22 Oct 2012, Roy T. Fielding wrote:
> 
> What you are insisting on defining as a "URL" is the input to the 
> process of making a hypertext reference (the arbitrary string typed into 
> a dialog or placed inside an href/src attribute)

Or placed on a command line to wget(1), or put in an RDFa triple store, or 
in transmitted in an HTTP Location: header, or...


> whereas the IETF standards define the output of that process as a 
> uniform addressing syntax for use on the Internet by every application 
> that makes use of Web addresses.

That's what Anne is specifying, because, despite your claims, STD 66 
doesn't actually define that. It only defines processing for valid 
strings, not invalid ones.


> Browsers implement both the input processing and the output URI 
> standards.  HTML must define the input processing, either within the 
> spec or by reference to a new spec.

This has nothing particularly to do with HTML, HTML is just one of many 
many contexts in which URLs are found.


> "" is not a URL.

Whether it's a valid URL or not is besides the point (it's like people 
claiming that invalid XML files aren't XML, a pointless argument). We 
still have to define the processing for such a string when software is to 
process it as a URL.


> > I'm sure Anne would love nothing more than to be able to work on 
> > something more interesting that this. But at the end of the day, 
> > someone has to do it, and y'all aren't doing it.
> > 
> > This should not come as a surprise to anyone, the IETF and W3C have 
> > been discussing this matter at last as far back as 2008.
> 
> Yes, we have been discussing it since 1994.

19 years of not fixing the problem, then. Shouldn't come as a surprise 
that someone has finally gotten around to doing it.


> It would be nice if you would take the advice already received and 
> define references in HTML, including the algorithms for converting them 
> into URI references (for DOM and network usage) and IRI references (for 
> display).

As far as HTML goes, my plan is to remove all references to STD 66 and 
rely entirely on Anne's work, so that there doesn't have to be any 
preprocessing nonsense. Then the STD 66 RFCs are entirely irrelevant.

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'

From jan.algermissen@nordsc.com  Mon Oct 22 15:05:23 2012
Return-Path: <jan.algermissen@nordsc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B02511E80D9 for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 15:05:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.76
X-Spam-Level: 
X-Spam-Status: No, score=-2.76 tagged_above=-999 required=5 tests=[AWL=-0.511,  BAYES_00=-2.599, HELO_EQ_DE=0.35]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yeUYT6rBa96J for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 15:05:22 -0700 (PDT)
Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.186]) by ietfa.amsl.com (Postfix) with ESMTP id 90B1F11E80A2 for <ietf@ietf.org>; Mon, 22 Oct 2012 15:05:22 -0700 (PDT)
Received: from [192.168.2.103] (p548FB0D3.dip.t-dialin.net [84.143.176.211]) by mrelayeu.kundenserver.de (node=mreu1) with ESMTP (Nemesis) id 0M9LFi-1Taul1340s-00C6Pl; Tue, 23 Oct 2012 00:04:45 +0200
Subject: Re: [whatwg] New URL Standard from Anne van Kesteren on 2012-09-24 (public-whatwg-archive@w3.org from September 2012)
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=us-ascii
From: Jan Algermissen <jan.algermissen@nordsc.com>
In-Reply-To: <Pine.LNX.4.64.1210222137530.2471@ps20323.dreamhostps.com>
Date: Tue, 23 Oct 2012 00:04:42 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <2FFEF121-A93A-4F64-8465-E05010C0E39B@nordsc.com>
References: <50604C1A.7090901@gmx.de> <5060A964.5060001@stpeter.im> <Pine.LNX.4.64.1210172354500.2478@ps20323.dreamhostps.com> <507F5A7E.6040206@arcanedomain.com> <50856E3C.103@gmail.com> <Pine.LNX.4.64.1210221753010.2471@ps20323.dreamhostps.com> <0DBC8A11-319C-4120-975E-7E40FD5818BF@gbiv.com> <Pine.LNX.4.64.1210222137530.2471@ps20323.dreamhostps.com>
To: Ian Hickson <ian@hixie.ch>
X-Mailer: Apple Mail (2.1283)
X-Provags-ID: V02:K0:5/lZ5vI8Io62/p2Yt/EB4bsZykkb5H5Emdq9UF1Qfu0 bDaxN+TNz0xHfrju5xE1OXgkzVFAW0E04Y9HIcXxt9yX/Fw3Qf Ay8OhHwJ1gk0BDVkqvdknvklETXQxDNdWWXkUKd3OcXlNcIp69 v9excL3HEs+gg7Bz3neMMce6TLLAbqNHzJn+/c+Puw5/aTIM2G 7eQJ1gFTmfxRbkAkwRoY02c+cM/h8tbrqPwFPoqSAJln7fRnWP 5Y/eJQ3Y39x2NE4dhpy9l/27KeUCfL+oEf+Q7/27fuddU8/c90 COA15aG2i9cNWZ1pXJ7knTqHY9u5ZGrB3MZ9GeqNGHgmddQji1 k3kxW4ItFJu3Yp1YIR7TEw7Eg6VbyR3iPTO9BS8zZ7LZjRRNj4 Vf9fe/iiBprWA==
X-Mailman-Approved-At: Tue, 23 Oct 2012 09:13:03 -0700
Cc: IETF Discussion <ietf@ietf.org>, Julian Reschke <julian.reschke@gmx.de>, "Roy T. Fielding" <fielding@gbiv.com>, mnot@mnot.net, Noah Mendelsohn <nrm@arcanedomain.com>, URI <uri@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: Mon, 22 Oct 2012 22:05:23 -0000

Ian,

On Oct 22, 2012, at 11:46 PM, Ian Hickson wrote:

>> "" is not a URL.
>=20
> Whether it's a valid URL=20

the question if not whether an empty string is a valid URI.

The point is that what you and Anne are addressing is parsing of URI =
*References* not URIs.

Roy, IIUC, meant that "" is a URI *reference* - it is not a valid or =
invalid URI.

This is why any references to fixing or aligning URI syntax with reality =
is besides the point and not neccessary. All that you (we) deal with is =
URI references and how to parse them to yield valid URIs.


Jan



From ian@hixie.ch  Mon Oct 22 15:35:23 2012
Return-Path: <ian@hixie.ch>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E65AF21F8504 for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 15:35:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dyVrVSbJs5VR for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 15:35:21 -0700 (PDT)
Received: from homiemail-a45.g.dreamhost.com (caibbdcaaaaf.dreamhost.com [208.113.200.5]) by ietfa.amsl.com (Postfix) with ESMTP id 305CB11E80F8 for <ietf@ietf.org>; Mon, 22 Oct 2012 15:35:20 -0700 (PDT)
Received: from homiemail-a45.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a45.g.dreamhost.com (Postfix) with ESMTP id 4533148096; Mon, 22 Oct 2012 15:35:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=hixie.ch; h=date:from:to :cc:subject:in-reply-to:message-id:references:mime-version: content-type; s=hixie.ch; bh=xCIOfL5NBydjDlRrhMsfrDdTxnc=; b=oQl M8iNKl3HchY8AK8lAFq4R132qm4qgjG5mp5yJqeOVJ46sEdkgi6NGwVa7gm5cnIl rDZSx7t5UMhjDLWwli2njcCDeq9Idrl/CUGp6D0ieqktxyF69ZMQGy/oNiUqS/I3 ilY0MmW9WRZJ0dHCSUvC8ZgXhcoAHQuyFLfNZpfs=
Received: from ps20323.dreamhostps.com (ps20323.dreamhost.com [69.163.222.251]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: internal@index.hixie.ch) by homiemail-a45.g.dreamhost.com (Postfix) with ESMTPSA id 34C4448073;  Mon, 22 Oct 2012 15:35:23 -0700 (PDT)
Date: Mon, 22 Oct 2012 22:35:16 +0000 (UTC)
From: Ian Hickson <ian@hixie.ch>
To: Jan Algermissen <jan.algermissen@nordsc.com>,  Tim Bray <tbray@textuality.com>, Julian Reschke <julian.reschke@gmx.de>
Subject: Re: [whatwg] New URL Standard from Anne van Kesteren on 2012-09-24 (public-whatwg-archive@w3.org from September 2012)
In-Reply-To: <5085C4BA.2030505@gmx.de>
Message-ID: <Pine.LNX.4.64.1210222220510.2471@ps20323.dreamhostps.com>
References: <50604C1A.7090901@gmx.de> <5060A964.5060001@stpeter.im> <Pine.LNX.4.64.1210172354500.2478@ps20323.dreamhostps.com> <507F5A7E.6040206@arcanedomain.com> <50856E3C.103@gmail.com> <Pine.LNX.4.64.1210221753010.2471@ps20323.dreamhostps.com> <0DBC8A11-319C-4120-975E-7E40FD5818BF@gbiv.com> <Pine.LNX.4.64.1210222137530.2471@ps20323.dreamhostps.com> <5085C4BA.2030505@gmx.de>
Content-Language: en-GB-hixie
Content-Style-Type: text/css
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Mailman-Approved-At: Tue, 23 Oct 2012 09:13:03 -0700
Cc: IETF Discussion <ietf@ietf.org>, Noah Mendelsohn <nrm@arcanedomain.com>, "Roy T. Fielding" <fielding@gbiv.com>, URI <uri@w3.org>, mnot@mnot.net
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Oct 2012 22:35:23 -0000

On Tue, 23 Oct 2012, Jan Algermissen wrote:
> 
> The point is that what you and Anne are addressing is parsing of URI 
> *References* not URIs.

Anne's spec defines how you get from any arbitrary string (plus a base 
URL) to a data structure with fields like scheme, hostname, port, path, 
etc. The input can be absolute, completely invalid, the empty string, 
whatever.


> This is why any references to fixing or aligning URI syntax with reality 
> is besides the point and not neccessary. All that you (we) deal with is 
> URI references and how to parse them to yield valid URIs.

That's certainly part of the required work, yes. It's not all of it.


On Mon, 22 Oct 2012, Tim Bray wrote:
> 
> The notion that curl, or an HTTP cache manager, or an XML namespace 
> processor, is going to be routing around errors, strikes me on the face 
> of it as being wrong.  One of the main uses I put curl to is making sure 
> I have the URL exactly right before I drop it into chat or whatever.  

   $ wget 'http://example.com/a b'
   --2012-10-23 00:27:43--  http://example.com/a%20b

   # test.cgi returns a 301 with "Location: a b"
   $ curl -L http://damowmow.com/playground/demos/url/in-http-headers/test.cgi
   This file is: http://damowmow.com/playground/demos/url/in-http-headers/a%20b

Software does this stuff already. We need to make sure it does it 
interoperably.


On Tue, 23 Oct 2012, Julian Reschke wrote:
> 
> This always was about venue, not people. If people want to "fix" or 
> "augment" URIs/IRIs, they should come over to the IETF.

I think the person doing the work has the prerogative to do it wherever he 
or she wants to do it. Maybe the IETF should consider why Anne isn't doing 
it in the IETF.


> > The specs don't define everything that implementations have to do to 
> > be interoperable. If the IETF doesn't think that's a problem, then 
> > that's fine, but then y'all shouldn't be surprised when people who 
> > _do_ think that's a problem try and fix it.
> 
> Yes, please fix *that*, but *just* that without messing with the basics 
> without consensus/review.

Consensus isn't a value I hold highly, but review of Anne's work is 
welcome.

If the IETF community didn't want Anne to do this work, then the IETF 
community should have done it. Having not done it, having not even 
understood that the problem exists, means the IETF has lost the 
credibility it needs to claim that this is in the IETF's domain.

You don't get to claim authority over an area while at the same time 
telling someone else "please fix that" for the hard work that comes with 
that area. The reality is, he who does the hard work, gets the authority.

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'

From jasnell@gmail.com  Mon Oct 22 15:51:32 2012
Return-Path: <jasnell@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2AF841F0C54 for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 15:51:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.633
X-Spam-Level: 
X-Spam-Status: No, score=-3.633 tagged_above=-999 required=5 tests=[AWL=-2.335, BAYES_00=-2.599, HTML_MESSAGE=0.001, MANGLED_DIET=2.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id epa5ZRurxg9m for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 15:51:31 -0700 (PDT)
Received: from mail-qc0-f172.google.com (mail-qc0-f172.google.com [209.85.216.172]) by ietfa.amsl.com (Postfix) with ESMTP id EA0931F0429 for <ietf@ietf.org>; Mon, 22 Oct 2012 15:51:27 -0700 (PDT)
Received: by mail-qc0-f172.google.com with SMTP id s14so2173290qcg.31 for <ietf@ietf.org>; Mon, 22 Oct 2012 15:51: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:from:date:message-id:subject:to :cc:content-type; bh=QZ/0/zZzP1umh8Lbkd7/nAYLU2Vgbww/QH+EKU5qtHA=; b=GTklUHHqJo7g2nvzxiAFm+uOfGI37waTwlAR5l6wLMnqQ78On/3u7IUMI/3mXmhxcm vpUZyLED7rWDctIivTTFbnjC2n3UyYi4tu4xmx/wi9ryABu73Kq7wxj2gSA9sAohJO6W xNZvOtXBXEVCkNjkWL95hvcUP9kqIdknrnRmjN1JqJ+APTEg9xqewT/ARQarDIkccPSZ inVR0w1RMupelYxYNRhUmTUFz03Z4cSeOmvbbKFf0Br5PamIm1PI48OoHfjmnIad5abA JPMINF4ijdHJXxu6oGuz1WWe5gOLlqrwuG6UjeN1Fk6DaabWXT6bPMxCEP4hfsJXGl5e HXyQ==
Received: by 10.49.103.162 with SMTP id fx2mr5929617qeb.1.1350946287437; Mon, 22 Oct 2012 15:51:27 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.49.81.230 with HTTP; Mon, 22 Oct 2012 15:51:06 -0700 (PDT)
In-Reply-To: <Pine.LNX.4.64.1210222220510.2471@ps20323.dreamhostps.com>
References: <50604C1A.7090901@gmx.de> <5060A964.5060001@stpeter.im> <Pine.LNX.4.64.1210172354500.2478@ps20323.dreamhostps.com> <507F5A7E.6040206@arcanedomain.com> <50856E3C.103@gmail.com> <Pine.LNX.4.64.1210221753010.2471@ps20323.dreamhostps.com> <0DBC8A11-319C-4120-975E-7E40FD5818BF@gbiv.com> <Pine.LNX.4.64.1210222137530.2471@ps20323.dreamhostps.com> <5085C4BA.2030505@gmx.de> <Pine.LNX.4.64.1210222220510.2471@ps20323.dreamhostps.com>
From: James M Snell <jasnell@gmail.com>
Date: Mon, 22 Oct 2012 15:51:06 -0700
Message-ID: <CABP7RbfgQrgduOzWaXcYieV3cw_=UoBaCC5e=XF+Y3PMEZoRMw@mail.gmail.com>
Subject: Re: [whatwg] New URL Standard from Anne van Kesteren on 2012-09-24 (public-whatwg-archive@w3.org from September 2012)
To: Ian Hickson <ian@hixie.ch>
Content-Type: multipart/alternative; boundary=047d7b2e79c892c7ce04ccadb1f5
X-Mailman-Approved-At: Tue, 23 Oct 2012 09:13:03 -0700
Cc: IETF Discussion <ietf@ietf.org>, Julian Reschke <julian.reschke@gmx.de>, "Roy T. Fielding" <fielding@gbiv.com>, Jan Algermissen <jan.algermissen@nordsc.com>, mnot@mnot.net, Noah Mendelsohn <nrm@arcanedomain.com>, URI <uri@w3.org>, Tim Bray <tbray@textuality.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Oct 2012 22:51:32 -0000

--047d7b2e79c892c7ce04ccadb1f5
Content-Type: text/plain; charset=UTF-8

On Mon, Oct 22, 2012 at 3:35 PM, Ian Hickson <ian@hixie.ch> wrote:

> On Tue, 23 Oct 2012, Jan Algermissen wrote:
> >
> > The point is that what you and Anne are addressing is parsing of URI
> > *References* not URIs.
>
> Anne's spec defines how you get from any arbitrary string (plus a base
> URL) to a data structure with fields like scheme, hostname, port, path,
> etc. The input can be absolute, completely invalid, the empty string,
> whatever.
>
>
Sounds useful but does not sound really like Anne's spec is "defining
URLs", however. Clarifying the language in your spec ought to resolve any
possible confusion.


>
> > This is why any references to fixing or aligning URI syntax with reality
> > is besides the point and not neccessary. All that you (we) deal with is
> > URI references and how to parse them to yield valid URIs.
>
> That's certainly part of the required work, yes. It's not all of it.
>
>
Is there a list of issues that you and Anne are working from for this? If
there indeed is a need to update the URI/IRI RFC's to address specific
problems I'm sure it wouldn't take much effort to draft up an I-D. I'd be
more than willing to help out with such an effort.


> [snip]
> I think the person doing the work has the prerogative to do it wherever he
> or she wants to do it. Maybe the IETF should consider why Anne isn't doing
> it in the IETF.
>
>
Indeed. Good question: Anne, is there are particular reason why you chose
not to pursue this work as an I-D? Let's get that particular issue resolved.

- James


>
> > > The specs don't define everything that implementations have to do to
> > > be interoperable. If the IETF doesn't think that's a problem, then
> > > that's fine, but then y'all shouldn't be surprised when people who
> > > _do_ think that's a problem try and fix it.
> >
> > Yes, please fix *that*, but *just* that without messing with the basics
> > without consensus/review.
>
> Consensus isn't a value I hold highly, but review of Anne's work is
> welcome.
>
> If the IETF community didn't want Anne to do this work, then the IETF
> community should have done it. Having not done it, having not even
> understood that the problem exists, means the IETF has lost the
> credibility it needs to claim that this is in the IETF's domain.
>
> You don't get to claim authority over an area while at the same time
> telling someone else "please fix that" for the hard work that comes with
> that area. The reality is, he who does the hard work, gets the authority.
>
> --
> Ian Hickson               U+1047E                )\._.,--....,'``.    fL
> http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
> Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
>
>

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

<font face=3D"courier new,monospace"><br></font><br><div class=3D"gmail_quo=
te">On Mon, Oct 22, 2012 at 3:35 PM, Ian Hickson <span dir=3D"ltr">&lt;<a h=
ref=3D"mailto:ian@hixie.ch" target=3D"_blank">ian@hixie.ch</a>&gt;</span> w=
rote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"im">On Tue, 23 Oct 2012, Jan A=
lgermissen wrote:<br>
&gt;<br>
&gt; The point is that what you and Anne are addressing is parsing of URI<b=
r>
&gt; *References* not URIs.<br>
<br>
</div>Anne&#39;s spec defines how you get from any arbitrary string (plus a=
 base<br>
URL) to a data structure with fields like scheme, hostname, port, path,<br>
etc. The input can be absolute, completely invalid, the empty string,<br>
whatever.<br>
<div class=3D"im"><br></div></blockquote><div><br></div><div>Sounds useful =
but does not sound really like Anne&#39;s spec is &quot;defining URLs&quot;=
, however. Clarifying the language in your spec ought to resolve any possib=
le confusion.=C2=A0</div>

<div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8=
ex;border-left:1px #ccc solid;padding-left:1ex"><div class=3D"im">
<br>
&gt; This is why any references to fixing or aligning URI syntax with reali=
ty<br>
&gt; is besides the point and not neccessary. All that you (we) deal with i=
s<br>
&gt; URI references and how to parse them to yield valid URIs.<br>
<br>
</div>That&#39;s certainly part of the required work, yes. It&#39;s not all=
 of it.<br>
<div class=3D"im"><br></div></blockquote><div><br></div><div>Is there a lis=
t of issues that you and Anne are working from for this? If there indeed is=
 a need to update the URI/IRI RFC&#39;s to address specific problems I&#39;=
m sure it wouldn&#39;t take much effort to draft up an I-D. I&#39;d be more=
 than willing to help out with such an effort.</div>

<div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8=
ex;border-left:1px #ccc solid;padding-left:1ex"><div class=3D"im">
[snip]
</div>I think the person doing the work has the prerogative to do it wherev=
er he<br>
or she wants to do it. Maybe the IETF should consider why Anne isn&#39;t do=
ing<br>
it in the IETF.<br>
<div class=3D"im"><br></div></blockquote><div><br></div><div>Indeed. Good q=
uestion: Anne, is there are particular reason why you chose not to pursue t=
his work as an I-D? Let&#39;s get that particular issue resolved.</div><div=
>

<br></div><div>- James</div><div>=C2=A0</div><blockquote class=3D"gmail_quo=
te" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"=
><div class=3D"im">
<br>
&gt; &gt; The specs don&#39;t define everything that implementations have t=
o do to<br>
&gt; &gt; be interoperable. If the IETF doesn&#39;t think that&#39;s a prob=
lem, then<br>
&gt; &gt; that&#39;s fine, but then y&#39;all shouldn&#39;t be surprised wh=
en people who<br>
&gt; &gt; _do_ think that&#39;s a problem try and fix it.<br>
&gt;<br>
&gt; Yes, please fix *that*, but *just* that without messing with the basic=
s<br>
&gt; without consensus/review.<br>
<br>
</div>Consensus isn&#39;t a value I hold highly, but review of Anne&#39;s w=
ork is<br>
welcome.<br>
<br>
If the IETF community didn&#39;t want Anne to do this work, then the IETF<b=
r>
community should have done it. Having not done it, having not even<br>
understood that the problem exists, means the IETF has lost the<br>
credibility it needs to claim that this is in the IETF&#39;s domain.<br>
<br>
You don&#39;t get to claim authority over an area while at the same time<br=
>
telling someone else &quot;please fix that&quot; for the hard work that com=
es with<br>
that area. The reality is, he who does the hard work, gets the authority.<b=
r>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
--<br>
Ian Hickson =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 U+1047E =C2=A0=
 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0)\._.,--....,&#39;``. =C2=
=A0 =C2=A0fL<br>
<a href=3D"http://ln.hixie.ch/" target=3D"_blank">http://ln.hixie.ch/</a> =
=C2=A0 =C2=A0 =C2=A0 U+263A =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0/, =C2=A0 _.. \ =C2=A0 _\ =C2=A0;`._ ,.<br>
Things that are impossible just take longer. =C2=A0 `._.-(,_..&#39;--(,_..&=
#39;`-.;.&#39;<br>
<br>
</div></div></blockquote></div><br>

--047d7b2e79c892c7ce04ccadb1f5--

From ian@hixie.ch  Mon Oct 22 16:16:26 2012
Return-Path: <ian@hixie.ch>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A6EEA11E80FB for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 16:16:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.449
X-Spam-Level: 
X-Spam-Status: No, score=-1.449 tagged_above=-999 required=5 tests=[AWL=-1.150, BAYES_00=-2.599, MANGLED_DIET=2.3]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3kVl9LpCzrO0 for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 16:16:26 -0700 (PDT)
Received: from homiemail-a93.g.dreamhost.com (caibbdcaaaaf.dreamhost.com [208.113.200.5]) by ietfa.amsl.com (Postfix) with ESMTP id 9C73A21F84C9 for <ietf@ietf.org>; Mon, 22 Oct 2012 16:16:20 -0700 (PDT)
Received: from homiemail-a93.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a93.g.dreamhost.com (Postfix) with ESMTP id 1E8508405B; Mon, 22 Oct 2012 16:15:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=hixie.ch; h=date:from:to :cc:subject:in-reply-to:message-id:references:mime-version: content-type; s=hixie.ch; bh=S1uOM6ImIqRIo/8bTWbw29BOI2E=; b=0fF vEpq+TyN4yD3spmlzBSZXTw2Hhyh3ptDJTazBdUpers0o0byeF0XotGmEnfUq3AO 3HGubZi9hKdPel0rSQ4znrua7nipXsj78BoPb2Ue/eI3sXQ+mKigKsvNz4wRgTng t5YGONqD6p34j0hm4SUtcMUxZ3wSF8MQMCPRBNX4=
Received: from ps20323.dreamhostps.com (ps20323.dreamhost.com [69.163.222.251]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: internal@index.hixie.ch) by homiemail-a93.g.dreamhost.com (Postfix) with ESMTPSA id DFD7584059;  Mon, 22 Oct 2012 16:15:19 -0700 (PDT)
Date: Mon, 22 Oct 2012 23:16:19 +0000 (UTC)
From: Ian Hickson <ian@hixie.ch>
To: James M Snell <jasnell@gmail.com>
Subject: Re: [whatwg] New URL Standard from Anne van Kesteren on 2012-09-24 (public-whatwg-archive@w3.org from September 2012)
In-Reply-To: <CABP7RbfgQrgduOzWaXcYieV3cw_=UoBaCC5e=XF+Y3PMEZoRMw@mail.gmail.com>
Message-ID: <Pine.LNX.4.64.1210222300490.2471@ps20323.dreamhostps.com>
References: <50604C1A.7090901@gmx.de> <5060A964.5060001@stpeter.im> <Pine.LNX.4.64.1210172354500.2478@ps20323.dreamhostps.com> <507F5A7E.6040206@arcanedomain.com> <50856E3C.103@gmail.com> <Pine.LNX.4.64.1210221753010.2471@ps20323.dreamhostps.com> <0DBC8A11-319C-4120-975E-7E40FD5818BF@gbiv.com> <Pine.LNX.4.64.1210222137530.2471@ps20323.dreamhostps.com> <5085C4BA.2030505@gmx.de> <Pine.LNX.4.64.1210222220510.2471@ps20323.dreamhostps.com> <CABP7RbfgQrgduOzWaXcYieV3cw_=UoBaCC5e=XF+Y3PMEZoRMw@mail.gmail.com>
Content-Language: en-GB-hixie
Content-Style-Type: text/css
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Mailman-Approved-At: Tue, 23 Oct 2012 09:13:03 -0700
Cc: IETF Discussion <ietf@ietf.org>, Julian Reschke <julian.reschke@gmx.de>, "Roy T. Fielding" <fielding@gbiv.com>, Jan Algermissen <jan.algermissen@nordsc.com>, mnot@mnot.net, Noah Mendelsohn <nrm@arcanedomain.com>, URI <uri@w3.org>, Tim Bray <tbray@textuality.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Oct 2012 23:16:26 -0000

On Mon, 22 Oct 2012, James M Snell wrote:
>
> Is there a list of issues that you and Anne are working from for this? 
> If there indeed is a need to update the URI/IRI RFC's to address 
> specific problems I'm sure it wouldn't take much effort to draft up an 
> I-D. I'd be more than willing to help out with such an effort.

See the spec. He's documented what needs to be done. The big one that he 
hasn't done yet is defining "valid URL" (the "Writing" section), which is 
the bulk of what STD 66 and the IRI RFC do.


> > Maybe the IETF should consider why Anne isn't doing it in the IETF.
>
> Indeed. Good question: Anne, is there are particular reason why you 
> chose not to pursue this work as an I-D? Let's get that particular issue 
> resolved.

(I don't think Anne is on any of the cc'ed mailing lists.)

I can't speak for Anne, but having experienced the IETF via the hybi work, 
my own opinion is that the main reason I wouldn't work with the IETF is 
that the community these days values consensus over technical value and 
running code, and the culture in the IETF doesn't value the kind of 
specification style that IMHO leads to better interop. For example, this 
very thraed -- we're having to argue to convince people that defining 
error handling is even a valuable thing to do. I have no interest in 
attempting to get anything done in an environment where that's the level 
at which the conversation starts.

Note that this isn't the only work recently that has gone from the IETF to 
the WHATWG. For example, the MIME Sniffing specification, which was 
originally in the HTML spec, was moved to the IETF by Adam Barth, who has 
done other work in the IETF successfully (e.g. Cookies). But in the end, 
Adam gave up on specifying MIME sniffing in the IETF and moved it out, and 
now it's found a home at the WHATWG:

   http://mimesniff.spec.whatwg.org/

The character encodings registry at IETF/IANA has also recently been, to 
some extent, suplanted by work at the WHATWG after failed attempts at 
getting the specs and registries at the IETF/IANA into better shape:

   http://encoding.spec.whatwg.org/

I spoke to Anne briefly and he pointed me to:

   http://wiki.whatwg.org/wiki/IETF

...which gives a very brief synopsis of why he's given up on the IETF.

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'

From mnot@mnot.net  Mon Oct 22 16:18:58 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 62B7511E8105 for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 16:18:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.12
X-Spam-Level: 
X-Spam-Status: No, score=-104.12 tagged_above=-999 required=5 tests=[AWL=-1.521, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yyqPhg8wWRIW for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 16:18:57 -0700 (PDT)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) by ietfa.amsl.com (Postfix) with ESMTP id 9175511E80F6 for <ietf@ietf.org>; Mon, 22 Oct 2012 16:18:57 -0700 (PDT)
Received: from [192.168.1.72] (unknown [118.209.87.82]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id CD62A22DD6D; Mon, 22 Oct 2012 19:18:47 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: [whatwg] New URL Standard from Anne van Kesteren on 2012-09-24 (public-whatwg-archive@w3.org from September 2012)
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <Pine.LNX.4.64.1210222300490.2471@ps20323.dreamhostps.com>
Date: Tue, 23 Oct 2012 10:18:47 +1100
Content-Transfer-Encoding: 7bit
Message-Id: <85CC064C-7592-4249-ACC9-7B55AAC0D7E7@mnot.net>
References: <50604C1A.7090901@gmx.de> <5060A964.5060001@stpeter.im> <Pine.LNX.4.64.1210172354500.2478@ps20323.dreamhostps.com> <507F5A7E.6040206@arcanedomain.com> <50856E3C.103@gmail.com> <Pine.LNX.4.64.1210221753010.2471@ps20323.dreamhostps.com> <0DBC8A11-319C-4120-975E-7E40FD5818BF@gbiv.com> <Pine.LNX.4.64.1210222137530.2471@ps20323.dreamhostps.com> <5085C4BA.2030505@gmx.de> <Pine.LNX.4.64.1210222220510.2471@ps20323.dreamhostps.com> <CABP7RbfgQrgduOzWaXcYieV3cw_=UoBaCC5e=XF+Y3PMEZoRMw@mail.gmail.com> <Pine.LNX.4.64.1210222300490.2471@ps20323.dreamhostps.com>
To: Ian Hickson <ian@hixie.ch>
X-Mailer: Apple Mail (2.1499)
X-Mailman-Approved-At: Tue, 23 Oct 2012 09:13:03 -0700
Cc: IETF Discussion <ietf@ietf.org>, Julian Reschke <julian.reschke@gmx.de>, "Roy T. Fielding" <fielding@gbiv.com>, Jan Algermissen <jan.algermissen@nordsc.com>, Noah Mendelsohn <nrm@arcanedomain.com>, URI <uri@w3.org>, James M Snell <jasnell@gmail.com>, Tim Bray <tbray@textuality.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Oct 2012 23:18:58 -0000

On 23/10/2012, at 10:16 AM, Ian Hickson <ian@hixie.ch> wrote:

> I can't speak for Anne, but having experienced the IETF via the hybi work, 
> my own opinion is that the main reason I wouldn't work with the IETF is 
> that the community these days values consensus over technical value and 
> running code, and the culture in the IETF doesn't value the kind of 
> specification style that IMHO leads to better interop. For example, this 
> very thraed -- we're having to argue to convince people that defining 
> error handling is even a valuable thing to do.

Wait - who's making that argument? References, please.

> I have no interest in 
> attempting to get anything done in an environment where that's the level 
> at which the conversation starts.


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




From ian@hixie.ch  Mon Oct 22 16:25:46 2012
Return-Path: <ian@hixie.ch>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C54631F0C5C for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 16:25:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.407
X-Spam-Level: 
X-Spam-Status: No, score=-2.407 tagged_above=-999 required=5 tests=[AWL=0.192,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LIoUSC6itaM3 for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 16:25:46 -0700 (PDT)
Received: from homiemail-a80.g.dreamhost.com (caibbdcaaaaf.dreamhost.com [208.113.200.5]) by ietfa.amsl.com (Postfix) with ESMTP id 04D8D1F0C54 for <ietf@ietf.org>; Mon, 22 Oct 2012 16:25:46 -0700 (PDT)
Received: from homiemail-a80.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a80.g.dreamhost.com (Postfix) with ESMTP id 7AA4037A06F; Mon, 22 Oct 2012 16:25:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=hixie.ch; h=date:from:to :cc:subject:in-reply-to:message-id:references:mime-version: content-type; s=hixie.ch; bh=q3vKAFMbO3sNB58gYSoGH0+AWlY=; b=D6R qizRxqQ8836F1m9jC28CviQEZ3+O188KCI/GO4sp82UpmPv6GJ0oO7hrLDeo4OBn 8/7sJzT9uL7AjZAhGCA+I9gYgOEX4x2bwZFnAZYK7pweAMeufN1ZQK3UijgPfal0 GMvYpbbTi6SNRqSOyxtBCM2riQcbO/t1406pFaYc=
Received: from ps20323.dreamhostps.com (ps20323.dreamhost.com [69.163.222.251]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: internal@index.hixie.ch) by homiemail-a80.g.dreamhost.com (Postfix) with ESMTPSA id 4B64937A06B;  Mon, 22 Oct 2012 16:25:45 -0700 (PDT)
Date: Mon, 22 Oct 2012 23:25:45 +0000 (UTC)
From: Ian Hickson <ian@hixie.ch>
To: Mark Nottingham <mnot@mnot.net>, Tim Bray <tbray@textuality.com>
Subject: Re: [whatwg] New URL Standard from Anne van Kesteren on 2012-09-24 (public-whatwg-archive@w3.org from September 2012)
In-Reply-To: <CAHBU6is8LNZ7Rq-vwLuOm+8ThKB9c=QPwbUfQwDQD5bDPjtf7w@mail.gmail.com>
Message-ID: <Pine.LNX.4.64.1210222320070.2471@ps20323.dreamhostps.com>
References: <50604C1A.7090901@gmx.de> <5060A964.5060001@stpeter.im> <Pine.LNX.4.64.1210172354500.2478@ps20323.dreamhostps.com> <507F5A7E.6040206@arcanedomain.com> <50856E3C.103@gmail.com> <Pine.LNX.4.64.1210221753010.2471@ps20323.dreamhostps.com> <0DBC8A11-319C-4120-975E-7E40FD5818BF@gbiv.com> <Pine.LNX.4.64.1210222137530.2471@ps20323.dreamhostps.com> <5085C4BA.2030505@gmx.de> <Pine.LNX.4.64.1210222220510.2471@ps20323.dreamhostps.com> <CAHBU6is8LNZ7Rq-vwLuOm+8ThKB9c=QPwbUfQwDQD5bDPjtf7w@mail.gmail.com>
Content-Language: en-GB-hixie
Content-Style-Type: text/css
MIME-Version: 1.0
Content-Type: MULTIPART/MIXED; BOUNDARY="-1555694626-2073023172-1350948345=:2471"
X-Mailman-Approved-At: Tue, 23 Oct 2012 09:13:03 -0700
Cc: IETF Discussion <ietf@ietf.org>, Julian Reschke <julian.reschke@gmx.de>, "Roy T. Fielding" <fielding@gbiv.com>, Jan Algermissen <jan.algermissen@nordsc.com>, Noah Mendelsohn <nrm@arcanedomain.com>, URI <uri@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: Mon, 22 Oct 2012 23:25:46 -0000

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

---1555694626-2073023172-1350948345=:2471
Content-Type: TEXT/PLAIN; charset=UTF-8
Content-Transfer-Encoding: QUOTED-PRINTABLE

On Tue, 23 Oct 2012, Mark Nottingham wrote:
> On 23/10/2012, at 9:35 AM, Ian Hickson <ian@hixie.ch> wrote:
> >=20
> > Consensus isn't a value I hold highly, but review of Anne's work is=20
> > welcome.
> >=20
> > If the IETF community didn't want Anne to do this work, then the IETF=
=20
> > community should have done it. Having not done it, having not even=20
> > understood that the problem exists, means the IETF has lost the=20
> > credibility it needs to claim that this is in the IETF's domain.
> >=20
> > You don't get to claim authority over an area while at the same time=20
> > telling someone else "please fix that" for the hard work that comes=20
> > with that area. The reality is, he who does the hard work, gets the=20
> > authority.
>=20
> All very interesting, but please address the point that's now been made=
=20
> repeatedly -- why is it necessary for you to redefine URIs, rather than=
=20
> doing as we suggest?

What exactly do you suggest?=20

Doing the work but at the IETF? See my reply to James.

Waiting for the IETF to do the work? We did, and timed out.

Not doing the work? That doesn't lead to interop.

Doing the work as a diff spec? That's what we did for a while, but it=20
doesn't work. Having to reference three specs (pre-parse, IRI, URI) just=20
to parse and resolve a URL is not what leads to implementors having a good=
=20
time and thus not what leads to interop.

What else do you suggest?


On Mon, 22 Oct 2012, Tim Bray wrote:
> >
> >    $ wget 'http://example.com/a b'
> >    --2012-10-23 00:27:43--  http://example.com/a%20b
> >
> >    # test.cgi returns a 301 with "Location: a b"
> >    $ curl -L http://damowmow.com/playground/demos/url/in-http-headers/t=
est.cgi
> >    This file is: http://damowmow.com/playground/demos/url/in-http-heade=
rs/a%20b
>=20
> Hmm.  I went to tbray.org and made a file at '$ROOT_DIR/tmp/a b' - note=
=20
> the space.
>=20
> Then I did
>=20
> curl -I 'http://www.tbray.org/tmp/a%20b'
> curl -I 'http://www.tbray.org/tmp/a b'
>=20
> Curl, quite properly, doesn't fuck with what I ask it

Instead it makes an invalid HTTP request. Your offensive language=20
notwithstanding, that means wget and curl don't interoperate. This is bad.=
=20
This is what we want to fix.


> and revealed a very interesting fact: That my Apache httpd returns 200=20
> for both of these, but, with, uh, interesting variations, amounting to=20
> what I think is quite possibly a bug.

How could it be a bug, since there's no spec that says how to handle a URL=
=20
with spaces in it?


> I also pasted the version with the space into the nearest Web browser,=20
> and it quite properly auto-corrected to a%20b.

Quite properly according to whom? There's no spec that defines this.


> I think it=92s a bug that curl is claiming the 301 pointed at "a%20b" not=
=20
> "a b".

You're wrong, but only because the de facto standard of "most software=20
does it that way" says so. No IETF spec does. That's the problem.


> Because suppose it had pointed at "a%20b" - I don=92t want middleware=20
> lying to me.

What you want isn't really the issue. Compatibility with deployed code is=
=20
the issue.


> It seems like a good idea to document the steps by which "a b" pasted in=
=20
> becomes "a%20b" in the address bar. But I don=92t see the relevance=20
> outside human-authored strings.

All the strings in question are human-authored.

--=20
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
---1555694626-2073023172-1350948345=:2471--

From ian@hixie.ch  Mon Oct 22 16:31:51 2012
Return-Path: <ian@hixie.ch>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7423511E80F7 for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 16:31:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.435
X-Spam-Level: 
X-Spam-Status: No, score=-2.435 tagged_above=-999 required=5 tests=[AWL=0.164,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wodjJ81c6ZMK for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 16:31:50 -0700 (PDT)
Received: from homiemail-a80.g.dreamhost.com (caibbdcaaaaf.dreamhost.com [208.113.200.5]) by ietfa.amsl.com (Postfix) with ESMTP id 2F63C11E810A for <ietf@ietf.org>; Mon, 22 Oct 2012 16:31:49 -0700 (PDT)
Received: from homiemail-a80.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a80.g.dreamhost.com (Postfix) with ESMTP id 3FFC437A06F; Mon, 22 Oct 2012 16:31:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=hixie.ch; h=date:from:to :cc:subject:in-reply-to:message-id:references:mime-version: content-type; s=hixie.ch; bh=KaR9VD4gXZYMMRg6pKCk+EbP8Ts=; b=bK1 42peu/dlqTk3N+SFGtYPx8R5s4sNr8OCef/duUommo7f+C3Et+e1azCFKvKEr5Vd FCW/WMFy5aPGxAXfWwFIAMiByDsRCpofWCSBa8a5ydCypslyVKGr07fJVdip75Yq TH8nSrLTSlcYPE7o61KcL/QgMUAvdSaJcvUaLmU4=
Received: from ps20323.dreamhostps.com (ps20323.dreamhost.com [69.163.222.251]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: internal@index.hixie.ch) by homiemail-a80.g.dreamhost.com (Postfix) with ESMTPSA id 08D6C37A06B;  Mon, 22 Oct 2012 16:31:45 -0700 (PDT)
Date: Mon, 22 Oct 2012 23:31:44 +0000 (UTC)
From: Ian Hickson <ian@hixie.ch>
To: Mark Nottingham <mnot@mnot.net>
Subject: Re: [whatwg] New URL Standard from Anne van Kesteren on 2012-09-24 (public-whatwg-archive@w3.org from September 2012)
In-Reply-To: <85CC064C-7592-4249-ACC9-7B55AAC0D7E7@mnot.net>
Message-ID: <Pine.LNX.4.64.1210222325540.2471@ps20323.dreamhostps.com>
References: <50604C1A.7090901@gmx.de> <5060A964.5060001@stpeter.im> <Pine.LNX.4.64.1210172354500.2478@ps20323.dreamhostps.com> <507F5A7E.6040206@arcanedomain.com> <50856E3C.103@gmail.com> <Pine.LNX.4.64.1210221753010.2471@ps20323.dreamhostps.com> <0DBC8A11-319C-4120-975E-7E40FD5818BF@gbiv.com> <Pine.LNX.4.64.1210222137530.2471@ps20323.dreamhostps.com> <5085C4BA.2030505@gmx.de> <Pine.LNX.4.64.1210222220510.2471@ps20323.dreamhostps.com> <CABP7RbfgQrgduOzWaXcYieV3cw_=UoBaCC5e=XF+Y3PMEZoRMw@mail.gmail.com> <Pine.LNX.4.64.1210222300490.2471@ps20323.dreamhostps.com> <85CC064C-7592-4249-ACC9-7B55AAC0D7E7@mnot.net>
Content-Language: en-GB-hixie
Content-Style-Type: text/css
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Mailman-Approved-At: Tue, 23 Oct 2012 09:13:03 -0700
Cc: IETF Discussion <ietf@ietf.org>, Julian Reschke <julian.reschke@gmx.de>, "Roy T. Fielding" <fielding@gbiv.com>, Jan Algermissen <jan.algermissen@nordsc.com>, Noah Mendelsohn <nrm@arcanedomain.com>, URI <uri@w3.org>, James M Snell <jasnell@gmail.com>, Tim Bray <tbray@textuality.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Oct 2012 23:31:51 -0000

On Tue, 23 Oct 2012, Mark Nottingham wrote:
> On 23/10/2012, at 10:16 AM, Ian Hickson <ian@hixie.ch> wrote:
> > 
> > I can't speak for Anne, but having experienced the IETF via the hybi 
> > work, my own opinion is that the main reason I wouldn't work with the 
> > IETF is that the community these days values consensus over technical 
> > value and running code, and the culture in the IETF doesn't value the 
> > kind of specification style that IMHO leads to better interop. For 
> > example, this very thraed -- we're having to argue to convince people 
> > that defining error handling is even a valuable thing to do.
> 
> Wait - who's making that argument?

Me.


> References, please.

This very thread is evidence enough, but see also the complete disinterest 
in fixing the URL specs, or the reaction abarth got from MIME sniffing, or 
the disaster that was hybi, or this complete disinterest in fixing the 
problem with encodings:

   http://mail.apps.ietf.org/ietf/charsets/threads.html#01830
   http://mail.apps.ietf.org/ietf/charsets/threads.html#02027
   http://mail.apps.ietf.org/ietf/charsets/threads.html#02034

...or the way IANA registrations for MIME types get handled, or HTTP bis' 
reaction to browser feedback, or the way process is put ahead of progress 
(there's no way to fix an RFC once it's published, even errata are often 
rejected), or the lack of any testing culture...

I understand that you disagree that most of those were a problem. But the 
original question was "why don't you work at IETF", and that's the answer. 
It may be that you conclude that it's a good thing, therefore, that I and 
others don't work at the IETF, but in that case you shouldn't complain 
when we go and do stuff outside the IETF.

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'

From ian@hixie.ch  Mon Oct 22 16:40:53 2012
Return-Path: <ian@hixie.ch>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7193811E80F4 for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 16:40:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.455
X-Spam-Level: 
X-Spam-Status: No, score=-2.455 tagged_above=-999 required=5 tests=[AWL=0.144,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CC0UGvw+rPNf for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 16:40:52 -0700 (PDT)
Received: from homiemail-a59.g.dreamhost.com (caibbdcaaaaf.dreamhost.com [208.113.200.5]) by ietfa.amsl.com (Postfix) with ESMTP id 8873F11E80E8 for <ietf@ietf.org>; Mon, 22 Oct 2012 16:40:52 -0700 (PDT)
Received: from homiemail-a59.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a59.g.dreamhost.com (Postfix) with ESMTP id D8A3A56406C; Mon, 22 Oct 2012 16:40:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=hixie.ch; h=date:from:to :cc:subject:in-reply-to:message-id:references:mime-version: content-type; s=hixie.ch; bh=aXE2/rU9xpov8idwvXtJzr3qs9M=; b=1pg pR4axhC5ktohbTI9SOmXMMUbWAHOz1xjG+qtKe2hFWfxxJ5BuFJQZjVry6TN5AV9 VoR9ShBrmkESJGwA99cF/zXyXiQMW+d/eG2cHIxrqrSp8rcFjI5H329wTkpV13tz 4TRhVrfn9oKxvWBFh8gWc2XK9xPBJBxRuEGraphQ=
Received: from ps20323.dreamhostps.com (ps20323.dreamhost.com [69.163.222.251]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: internal@index.hixie.ch) by homiemail-a59.g.dreamhost.com (Postfix) with ESMTPSA id C6ACA564061;  Mon, 22 Oct 2012 16:40:55 -0700 (PDT)
Date: Mon, 22 Oct 2012 23:40:51 +0000 (UTC)
From: Ian Hickson <ian@hixie.ch>
To: Mark Nottingham <mnot@mnot.net>
Subject: Re: [whatwg] New URL Standard from Anne van Kesteren on 2012-09-24 (public-whatwg-archive@w3.org from September 2012)
In-Reply-To: <09DC68AA-2DAD-4CB1-9CA9-799AF12B7BE2@mnot.net>
Message-ID: <Pine.LNX.4.64.1210222337520.2471@ps20323.dreamhostps.com>
References: <50604C1A.7090901@gmx.de> <5060A964.5060001@stpeter.im> <Pine.LNX.4.64.1210172354500.2478@ps20323.dreamhostps.com> <507F5A7E.6040206@arcanedomain.com> <50856E3C.103@gmail.com> <Pine.LNX.4.64.1210221753010.2471@ps20323.dreamhostps.com> <0DBC8A11-319C-4120-975E-7E40FD5818BF@gbiv.com> <Pine.LNX.4.64.1210222137530.2471@ps20323.dreamhostps.com> <5085C4BA.2030505@gmx.de> <Pine.LNX.4.64.1210222220510.2471@ps20323.dreamhostps.com> <CAHBU6is8LNZ7Rq-vwLuOm+8ThKB9c=QPwbUfQwDQD5bDPjtf7w@mail.gmail.com> <Pine.LNX.4.64.1210222320070.2471@ps20323.dreamhostps.com> <09DC68AA-2DAD-4CB1-9CA9-799AF12B7BE2@mnot.net>
Content-Language: en-GB-hixie
Content-Style-Type: text/css
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Mailman-Approved-At: Tue, 23 Oct 2012 09:13:03 -0700
Cc: IETF Discussion <ietf@ietf.org>, Julian Reschke <julian.reschke@gmx.de>, "Roy T. Fielding" <fielding@gbiv.com>, Jan Algermissen <jan.algermissen@nordsc.com>, Noah Mendelsohn <nrm@arcanedomain.com>, URI <uri@w3.org>, Tim Bray <tbray@textuality.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Oct 2012 23:40:53 -0000

On Tue, 23 Oct 2012, Mark Nottingham wrote:
> 
> Don't much care about the venue, as long as there's *some* coordination 
> / communication.

Everyone is welcome to participate in the WHATWG list.


> > Doing the work as a diff spec? That's what we did for a while, but it 
> > doesn't work. Having to reference three specs (pre-parse, IRI, URI) 
> > just to parse and resolve a URL is not what leads to implementors 
> > having a good time and thus not what leads to interop.
> 
> Really? You're comfortable with the current weight and depth of the 
> HTML5 spec, but balk at a pre-processing step for URIs? Seriously?

Good lord, no. Who's comfortable with the HTML spec's size?

Unfortunately, the size of the HTML spec is dictated by the complexity of 
the platform it is describing.

There's no reason to have three specs when one suffices.


> The underlying point that people seem to be making is that there's 
> legitimate need for URIs to be a separate concept from "strings that 
> will become URIs."

Anne's spec will define "valid URL", which addressed that need.


> By collapsing them into one thing, you're doing those folks a 
> disservice.

They are not collapsed into one thing.


> Browser implementers may not care, but it's pretty obvious that lots of 
> other people do.

Browser implementors aren't particularly special here.


> BTW, it doesn't have to be a separate spec, although it probably would 
> benefit from being one. Browser implementers already have to reference 
> TCP, IP, DNS, and likely tens to hundreds of other specs to get what 
> they want done -- unless you have bigger plans?

The difference is that the DNS implementor doesn't need to implement TCP, 
he uses TCP (and UDP) and builds on it. And so on. Whereas here we're 
talking about one thing, URLs, being specified in one place vs three.

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'

From mnot@mnot.net  Mon Oct 22 16:42:30 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 300D111E8107 for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 16:42:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.073
X-Spam-Level: 
X-Spam-Status: No, score=-104.073 tagged_above=-999 required=5 tests=[AWL=-1.474, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jQboad3GlsJZ for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 16:42:28 -0700 (PDT)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) by ietfa.amsl.com (Postfix) with ESMTP id A208511E80E8 for <ietf@ietf.org>; Mon, 22 Oct 2012 16:42:28 -0700 (PDT)
Received: from [192.168.1.72] (unknown [118.209.87.82]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 1B21822E253; Mon, 22 Oct 2012 19:42:17 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: [whatwg] New URL Standard from Anne van Kesteren on 2012-09-24 (public-whatwg-archive@w3.org from September 2012)
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <Pine.LNX.4.64.1210222325540.2471@ps20323.dreamhostps.com>
Date: Tue, 23 Oct 2012 10:42:18 +1100
Content-Transfer-Encoding: quoted-printable
Message-Id: <5DF21D1C-3A60-4E68-9BBF-16B5B69CFF5D@mnot.net>
References: <50604C1A.7090901@gmx.de> <5060A964.5060001@stpeter.im> <Pine.LNX.4.64.1210172354500.2478@ps20323.dreamhostps.com> <507F5A7E.6040206@arcanedomain.com> <50856E3C.103@gmail.com> <Pine.LNX.4.64.1210221753010.2471@ps20323.dreamhostps.com> <0DBC8A11-319C-4120-975E-7E40FD5818BF@gbiv.com> <Pine.LNX.4.64.1210222137530.2471@ps20323.dreamhostps.com> <5085C4BA.2030505@gmx.de> <Pine.LNX.4.64.1210222220510.2471@ps20323.dreamhostps.com> <CABP7RbfgQrgduOzWaXcYieV3cw_=UoBaCC5e=XF+Y3PMEZoRMw@mail.gmail.com> <Pine.LNX.4.64.1210222300490.2471@ps20323.dreamhostps.com> <85CC064C-7592-4249-ACC9-7B55AAC0D7E7@mnot.net> <Pine.LNX.4.64.1210222325540.2471@ps20323.dreamhostps.com>
To: Ian Hickson <ian@hixie.ch>
X-Mailer: Apple Mail (2.1499)
X-Mailman-Approved-At: Tue, 23 Oct 2012 09:13:03 -0700
Cc: IETF Discussion <ietf@ietf.org>, Julian Reschke <julian.reschke@gmx.de>, "Roy T. Fielding" <fielding@gbiv.com>, Jan Algermissen <jan.algermissen@nordsc.com>, Noah Mendelsohn <nrm@arcanedomain.com>, URI <uri@w3.org>, James M Snell <jasnell@gmail.com>, Tim Bray <tbray@textuality.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Oct 2012 23:42:30 -0000

On 23/10/2012, at 10:31 AM, Ian Hickson <ian@hixie.ch> wrote:

> On Tue, 23 Oct 2012, Mark Nottingham wrote:
>> On 23/10/2012, at 10:16 AM, Ian Hickson <ian@hixie.ch> wrote:
>>>=20
>>> I can't speak for Anne, but having experienced the IETF via the hybi=20=

>>> work, my own opinion is that the main reason I wouldn't work with =
the=20
>>> IETF is that the community these days values consensus over =
technical=20
>>> value and running code, and the culture in the IETF doesn't value =
the=20
>>> kind of specification style that IMHO leads to better interop. For=20=

>>> example, this very thraed -- we're having to argue to convince =
people=20
>>> that defining error handling is even a valuable thing to do.
>>=20
>> Wait - who's making that argument?
>=20
> Me.

So, you're saying that you can't work in this environment (*fans self*) =
because of the arguments you're making?

OK.


>> References, please.
>=20
> This very thread is evidence enough, but see also the complete =
disinterest=20
> in fixing the URL specs

Also? I thought that was what we were talking about...

> or the reaction abarth got from MIME sniffing

AIUI Adam walked away from it because two people expressed individual =
concerns about it. Had he stuck with it, I'm personally convinced it =
would have gotten through pretty easily.

> or=20
> the disaster that was hybi

I personally think websockets was a bad idea from the start, so I'll =
refrain from further comment.

> or this complete disinterest in fixing the=20
> problem with encodings:
>=20
>   http://mail.apps.ietf.org/ietf/charsets/threads.html#01830
>   http://mail.apps.ietf.org/ietf/charsets/threads.html#02027
>   http://mail.apps.ietf.org/ietf/charsets/threads.html#02034

No comment, would have to look into it.

> ...or the way IANA registrations for MIME types get handled

... the process for which was recently revised, based partially on those =
experiences.

> or HTTP bis' reaction to browser feedback

As far as I know, we addressed all of that feedback to the satisfaction =
of those who brought it. If you believe otherwise, we're currently in =
WGLC.

> or the way process is put ahead of progress=20
> (there's no way to fix an RFC once it's published, even errata are =
often=20
> rejected), or the lack of any testing culture...
>=20
> I understand that you disagree that most of those were a problem.

Oh, no, I agree that there are some pretty serious problems here.=20

> But the=20
> original question was "why don't you work at IETF", and that's the =
answer.=20
> It may be that you conclude that it's a good thing, therefore, that I =
and=20
> others don't work at the IETF, but in that case you shouldn't complain=20=

> when we go and do stuff outside the IETF.


Again, I'm not stuffed about the venue, and you can do what you like. =
However, when the *W3C* does things that interact with IETF =
technologies, we coordinate to make sure that there aren't overlaps, =
conflicts, etc.=20

Regards,


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




From ian@hixie.ch  Mon Oct 22 16:59:03 2012
Return-Path: <ian@hixie.ch>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F08FA21F86D6 for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 16:59:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.471
X-Spam-Level: 
X-Spam-Status: No, score=-2.471 tagged_above=-999 required=5 tests=[AWL=0.128,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0o3DG7+zCS9N for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 16:59:03 -0700 (PDT)
Received: from homiemail-a93.g.dreamhost.com (caibbdcaaaaf.dreamhost.com [208.113.200.5]) by ietfa.amsl.com (Postfix) with ESMTP id 5195E21F8906 for <ietf@ietf.org>; Mon, 22 Oct 2012 16:59:01 -0700 (PDT)
Received: from homiemail-a93.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a93.g.dreamhost.com (Postfix) with ESMTP id 270E284065; Mon, 22 Oct 2012 16:58:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=hixie.ch; h=date:from:to :cc:subject:in-reply-to:message-id:references:mime-version: content-type; s=hixie.ch; bh=ip3HJ9gnnjHzPLWVQ5X763nTM8U=; b=uor J/HfrGJitRd76iaVU/iXV5rdwBmbgTViARXNUxT6EsgCf150/2shGK627x0KXHG/ c4ofAiX+suFJTgD8HDmrqsVwGwPRZMptOOi1Rq/Cf2wR2P0eNh5uwR0SWrjfSINA 1uxVSMTVosMW606s03VBDx+w1JGyeJmccCcYRQIw=
Received: from ps20323.dreamhostps.com (ps20323.dreamhost.com [69.163.222.251]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: internal@index.hixie.ch) by homiemail-a93.g.dreamhost.com (Postfix) with ESMTPSA id CC5DE8405B;  Mon, 22 Oct 2012 16:58:00 -0700 (PDT)
Date: Mon, 22 Oct 2012 23:59:00 +0000 (UTC)
From: Ian Hickson <ian@hixie.ch>
To: Mark Nottingham <mnot@mnot.net>
Subject: Re: [whatwg] New URL Standard from Anne van Kesteren on 2012-09-24 (public-whatwg-archive@w3.org from September 2012)
In-Reply-To: <5DF21D1C-3A60-4E68-9BBF-16B5B69CFF5D@mnot.net>
Message-ID: <Pine.LNX.4.64.1210222346590.2471@ps20323.dreamhostps.com>
References: <50604C1A.7090901@gmx.de> <5060A964.5060001@stpeter.im> <Pine.LNX.4.64.1210172354500.2478@ps20323.dreamhostps.com> <507F5A7E.6040206@arcanedomain.com> <50856E3C.103@gmail.com> <Pine.LNX.4.64.1210221753010.2471@ps20323.dreamhostps.com> <0DBC8A11-319C-4120-975E-7E40FD5818BF@gbiv.com> <Pine.LNX.4.64.1210222137530.2471@ps20323.dreamhostps.com> <5085C4BA.2030505@gmx.de> <Pine.LNX.4.64.1210222220510.2471@ps20323.dreamhostps.com> <CABP7RbfgQrgduOzWaXcYieV3cw_=UoBaCC5e=XF+Y3PMEZoRMw@mail.gmail.com> <Pine.LNX.4.64.1210222300490.2471@ps20323.dreamhostps.com> <85CC064C-7592-4249-ACC9-7B55AAC0D7E7@mnot.net> <Pine.LNX.4.64.1210222325540.2471@ps20323.dreamhostps.com> <5DF21D1C-3A60-4E68-9BBF-16B5B69CFF5D@mnot.net>
Content-Language: en-GB-hixie
Content-Style-Type: text/css
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Mailman-Approved-At: Tue, 23 Oct 2012 09:13:03 -0700
Cc: IETF Discussion <ietf@ietf.org>, Julian Reschke <julian.reschke@gmx.de>, "Roy T. Fielding" <fielding@gbiv.com>, Jan Algermissen <jan.algermissen@nordsc.com>, Noah Mendelsohn <nrm@arcanedomain.com>, URI <uri@w3.org>, James M Snell <jasnell@gmail.com>, Tim Bray <tbray@textuality.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Oct 2012 23:59:04 -0000

On Tue, 23 Oct 2012, Mark Nottingham wrote:
> 
> So, you're saying that you can't work in this environment (*fans self*) 
> because of the arguments you're making?

I'm saying this is why I don't want to work here, yes.


> >> References, please.
> > 
> > This very thread is evidence enough, but see also the complete 
> > disinterest in fixing the URL specs
> 
> Also? I thought that was what we were talking about...

The disinterest spans many years. This thread demonstrates not so much the 
disinterest so much as the lack of understanding that there's a problem to 
fix, which is a bit of a different issue, though equally frustrating and 
equally discouraging.


> > or the reaction abarth got from MIME sniffing
> 
> AIUI Adam walked away from it because two people expressed individual 
> concerns about it. Had he stuck with it, I'm personally convinced it 
> would have gotten through pretty easily.

The question here is "why do people walk away from the IETF or not 
participate in the IETF". Adam walked away. It doesn't matter whether he 
would have been able to get his stuff done if he'd stayed -- the fact is 
he walked away, so if you're looking for reasons why people walked away, 
it's a relevant data point.

Imagine you're trying to sell me a car, and I think the car is ugly, so I 
don't buy it. Then you're trying to figure out why people like me don't 
buy the car, and you ask me, and I say it's ugly. It doesn't matter if you 
think it's the prettiest thing in the world; if your goal is to sell me 
the car, then I can't think it's ugly.

Now if your goal _isn't_ to sell me that car, then that's fine.


> > or the disaster that was hybi
> 
> I personally think websockets was a bad idea from the start, so I'll 
> refrain from further comment.

Whether WebSockets is a good idea or not is besides the point. The point 
is that the hybi group was not a pleasant experience for me. If I were to 
be in a position to do Web Sockets again, I would decline the opportunity 
to do it through the IETF. Doing it through the IETF made the work take a 
year longer than it would have, made the protocol less secure (the WG 
removed a number of defense-in-depth features), and made the spec a mess 
(it's a mishmash of different editing styles). Plus, the group _still_ 
hasn't done multiplexing, which some of the vendors said was a prereq to 
implementation, something which, prior to the IETF getting involved, was 
only 3 to 6 months out on the roadmap.


> > ...or the way IANA registrations for MIME types get handled
> 
> ... the process for which was recently revised, based partially on those 
> experiences.

If it was revised more than about 2 weeks ago, the problems aren't solved, 
based on what I've seen in the past 2 weeks.


> > or HTTP bis' reaction to browser feedback
> 
> As far as I know, we addressed all of that feedback to the satisfaction 
> of those who brought it. If you believe otherwise, we're currently in 
> WGLC.

There's a number of people who raised feedback who gave up trying to get 
it addressed, but I haven't been following this closely enough to tell you 
what those are, because I gave up too.


> > But the original question was "why don't you work at IETF", and that's 
> > the answer. It may be that you conclude that it's a good thing, 
> > therefore, that I and others don't work at the IETF, but in that case 
> > you shouldn't complain when we go and do stuff outside the IETF.
> 
> Again, I'm not stuffed about the venue, and you can do what you like. 
> However, when the *W3C* does things that interact with IETF 
> technologies, we coordinate to make sure that there aren't overlaps, 
> conflicts, etc.

Yeah, well, I've mostly given up on the W3C, too. :-)

Anyway, this URL work isn't happening at the W3C.

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'

From ian@hixie.ch  Mon Oct 22 17:05:11 2012
Return-Path: <ian@hixie.ch>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0CDA11F0C5C for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 17:05:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.484
X-Spam-Level: 
X-Spam-Status: No, score=-2.484 tagged_above=-999 required=5 tests=[AWL=0.115,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0QRYnvd2vKNi for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 17:05:10 -0700 (PDT)
Received: from homiemail-a82.g.dreamhost.com (caibbdcaaaaf.dreamhost.com [208.113.200.5]) by ietfa.amsl.com (Postfix) with ESMTP id 460AC1F0429 for <ietf@ietf.org>; Mon, 22 Oct 2012 17:05:10 -0700 (PDT)
Received: from homiemail-a82.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a82.g.dreamhost.com (Postfix) with ESMTP id A97DD28207B; Mon, 22 Oct 2012 17:05:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=hixie.ch; h=date:from:to :cc:subject:in-reply-to:message-id:references:mime-version: content-type; s=hixie.ch; bh=xzlwGPdaQEvXLmecGBSmGeAYXdc=; b=nls ysUUXr1+zu+mNtkjmoaABlyU16RsdD76QKTvT/BSTnD2FH4M2P5ke8dfHDJWeDpb zNJhjemzUGTs4FhW43UgXYJA3MgJK5ftYhNErTYQUEjeLKJRq6O5ZDvihpBcIxF/ 14G73znIbHHgVjAjf/OJ3z5zJkj+Sju2xjxN9TiQ=
Received: from ps20323.dreamhostps.com (ps20323.dreamhost.com [69.163.222.251]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: internal@index.hixie.ch) by homiemail-a82.g.dreamhost.com (Postfix) with ESMTPSA id 9A953282074;  Mon, 22 Oct 2012 17:05:14 -0700 (PDT)
Date: Tue, 23 Oct 2012 00:05:09 +0000 (UTC)
From: Ian Hickson <ian@hixie.ch>
To: Mark Nottingham <mnot@mnot.net>
Subject: Re: [whatwg] New URL Standard from Anne van Kesteren on 2012-09-24 (public-whatwg-archive@w3.org from September 2012)
In-Reply-To: <D9485C0B-E3DA-4B51-9A25-9EAB018C1951@mnot.net>
Message-ID: <Pine.LNX.4.64.1210222359080.2471@ps20323.dreamhostps.com>
References: <50604C1A.7090901@gmx.de> <5060A964.5060001@stpeter.im> <Pine.LNX.4.64.1210172354500.2478@ps20323.dreamhostps.com> <507F5A7E.6040206@arcanedomain.com> <50856E3C.103@gmail.com> <Pine.LNX.4.64.1210221753010.2471@ps20323.dreamhostps.com> <0DBC8A11-319C-4120-975E-7E40FD5818BF@gbiv.com> <Pine.LNX.4.64.1210222137530.2471@ps20323.dreamhostps.com> <5085C4BA.2030505@gmx.de> <Pine.LNX.4.64.1210222220510.2471@ps20323.dreamhostps.com> <CAHBU6is8LNZ7Rq-vwLuOm+8ThKB9c=QPwbUfQwDQD5bDPjtf7w@mail.gmail.com> <Pine.LNX.4.64.1210222320070.2471@ps20323.dreamhostps.com> <09DC68AA-2DAD-4CB1-9CA9-799AF12B7BE2@mnot.net> <Pine.LNX.4.64.1210222337520.2471@ps20323.dreamhostps.com> <D9485C0B-E3DA-4B51-9A25-9EAB018C1951@mnot.net>
Content-Language: en-GB-hixie
Content-Style-Type: text/css
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Mailman-Approved-At: Tue, 23 Oct 2012 09:13:03 -0700
Cc: IETF Discussion <ietf@ietf.org>, Julian Reschke <julian.reschke@gmx.de>, "Roy T. Fielding" <fielding@gbiv.com>, Jan Algermissen <jan.algermissen@nordsc.com>, Noah Mendelsohn <nrm@arcanedomain.com>, URI <uri@w3.org>, Tim Bray <tbray@textuality.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Oct 2012 00:05:11 -0000

On Tue, 23 Oct 2012, Mark Nottingham wrote:
> On 23/10/2012, at 10:40 AM, Ian Hickson <ian@hixie.ch> wrote:
> > On Tue, 23 Oct 2012, Mark Nottingham wrote:
> >> 
> >> Don't much care about the venue, as long as there's *some* 
> >> coordination / communication.
> > 
> > Everyone is welcome to participate in the WHATWG list.
> 
> As they are on the IETF list. The difference is that the WHATWG is run 
> by an unelected board of "members" - <http://www.whatwg.org/charter>.

"Run" is a bit of a strong word. There's basically no non-public activity 
from the charter members.


> > Anne's spec will define "valid URL", which addressed that need.
> 
> Why not define (or reuse) a separate term for the input stream, and 
> leave "URL" alone?

Because everyone calls these things URLs (except STD 66).


> >> Browser implementers may not care, but it's pretty obvious that lots 
> >> of other people do.
> > 
> > Browser implementors aren't particularly special here.
> 
> No, but your arguments are often coloured by your perspective -- just as 
> everyone else's are.

Which arguments in particular are we talking about here? I've mostly been 
talking about curl, wget, GoogleBot, Perl libraries, etc.


> If I believed that Anne was willing to and capable of re-specifying 
> RFC3986 in such a way that the definition, syntax and semantics of URLs 
> (or whatever they ends up being called) doesn't change at all, I'd be 
> less concerned.
> 
> However, that doesn't seem very likely, especially when he isn't 
> engaging with the folks that wrote that spec (especially, Roy).
> 
> RFC3986 is referenced by a LOT of technologies, not just Web browsers, 
> not just HTML. Replacing it unilaterally with input from the browser / 
> HTML community from an implementer perspective is very likely to break 
> most of them.

I suspect it will break nothing, but I guess we'll find out.

I don't really understand how it _could_ break anything, so long as the 
processing of IRI and URIs as defined by IETF is the same in the WHATWG 
spec, except where software already differs with the IETF specs.

Do you have a concrete example I could study?


> As such, they won't use your new spec, and we'll be living in a world 
> where there will be two definitions of "URL" -- the IETF one and the 
> WHATWG one [...].
> 
> That seems a pretty bad tradeoff for the benefits you're getting -- a 
> slightly easier-to-read spec for browser implementers (a relatively tiny 
> audience).

If you have any concrete concerns, please don't hesitate to e-mail the 
WHATWG list, showing the specific examples you're worried about. Browsers 
are but one of many implementation classes that are relevant.

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'

From mca@amundsen.com  Mon Oct 22 17:33:14 2012
Return-Path: <mca@amundsen.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 000471F0C49 for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 17:33:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.379
X-Spam-Level: 
X-Spam-Status: No, score=-0.379 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, FORGED_YAHOO_RCVD=2.297, HTML_MESSAGE=0.001, J_CHICKENPOX_38=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pJWFvtn2P6NZ for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 17:33:12 -0700 (PDT)
Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id 99EF51F0429 for <ietf@ietf.org>; Mon, 22 Oct 2012 17:33:12 -0700 (PDT)
Received: by mail-vb0-f44.google.com with SMTP id fc26so4005408vbb.31 for <ietf@ietf.org>; Mon, 22 Oct 2012 17:33:11 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type :x-gm-message-state; bh=Fmf+3zTslB/hiqB2nteJGIPSiOdO689Uc+GtKoTErlE=; b=Mgp6HbuA7/AOpepNFOzzULal2vAynoYyMU27sInfgRaxM+wrubQ78Wuzd+LcJfDDd5 VENToSrxMkX38odx9zuPSjY8pVn8CJw8ukiOUq+unuiPsVZ5B8tEf63yBEz8dNTaWvXt +TOHE5JSSqP+5F7Aisf0dkafh2lZm7VVfZHp7xQxo8b9NiO2qWTCZ0WJ1otnazwcuFvb IGkX6pkX29O6wHuylBYxma8h/fcMQhx0LWvuKzrLrBjJaY+mxweO1QpNOPrm72xCTqgx t2b1REY3fSDMxFXStsRlYR8FcVi4eF6Z94WaKqQ3schUoWY6h2d9ohciDONTC59VVOhB BICQ==
Received: by 10.52.93.238 with SMTP id cx14mr14301659vdb.42.1350952391441; Mon, 22 Oct 2012 17:33:11 -0700 (PDT)
MIME-Version: 1.0
Sender: mca@amundsen.com
Received: by 10.58.187.228 with HTTP; Mon, 22 Oct 2012 17:32:51 -0700 (PDT)
In-Reply-To: <CAHBU6iv29xAJvgVtcNVpYX=23tydt+mCOQegRiNLV=K8sCh-Cg@mail.gmail.com>
References: <50604C1A.7090901@gmx.de> <5060A964.5060001@stpeter.im> <Pine.LNX.4.64.1210172354500.2478@ps20323.dreamhostps.com> <507F5A7E.6040206@arcanedomain.com> <50856E3C.103@gmail.com> <Pine.LNX.4.64.1210221753010.2471@ps20323.dreamhostps.com> <0DBC8A11-319C-4120-975E-7E40FD5818BF@gbiv.com> <Pine.LNX.4.64.1210222137530.2471@ps20323.dreamhostps.com> <5085C4BA.2030505@gmx.de> <Pine.LNX.4.64.1210222220510.2471@ps20323.dreamhostps.com> <CAHBU6is8LNZ7Rq-vwLuOm+8ThKB9c=QPwbUfQwDQD5bDPjtf7w@mail.gmail.com> <Pine.LNX.4.64.1210222320070.2471@ps20323.dreamhostps.com> <09DC68AA-2DAD-4CB1-9CA9-799AF12B7BE2@mnot.net> <Pine.LNX.4.64.1210222337520.2471@ps20323.dreamhostps.com> <D9485C0B-E3DA-4B51-9A25-9EAB018C1951@mnot.net> <Pine.LNX.4.64.1210222359080.2471@ps20323.dreamhostps.com> <CAHBU6iv29xAJvgVtcNVpYX=23tydt+mCOQegRiNLV=K8sCh-Cg@mail.gmail.com>
From: mike amundsen <mamund@yahoo.com>
Date: Mon, 22 Oct 2012 20:32:51 -0400
X-Google-Sender-Auth: Ev1YBH3uKkdJFLFDOyVNLxCCQzA
Message-ID: <CAPW_8m6r38A+OB40FKqJ7LwEk3iUUZb=ZQsc2wvBR1h_KV7o0g@mail.gmail.com>
Subject: Re: [whatwg] New URL Standard from Anne van Kesteren on 2012-09-24 (public-whatwg-archive@w3.org from September 2012)
To: Tim Bray <tbray@textuality.com>
Content-Type: multipart/alternative; boundary=20cf3071d090667ed004ccaf1df1
X-Gm-Message-State: ALoCoQmVyAfJavL//e8IsqNYrcW/3siU0IcCzLxcKbcgzXnrwUetLR/8NCtWgiR1tauRAKIzUkHH
X-Mailman-Approved-At: Tue, 23 Oct 2012 09:13:03 -0700
Cc: IETF Discussion <ietf@ietf.org>, Julian Reschke <julian.reschke@gmx.de>, "Roy T. Fielding" <fielding@gbiv.com>, Jan Algermissen <jan.algermissen@nordsc.com>, URI <uri@w3.org>, Noah Mendelsohn <nrm@arcanedomain.com>, Mark Nottingham <mnot@mnot.net>, Ian Hickson <ian@hixie.ch>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Oct 2012 00:33:14 -0000

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

<snip>
I=92d have to say that URI interoperability problems haven=92t come near
getting into the list of top-20 pain points.
</snip>
I can't recall the last time i experienced "URI interoperability problems"
across various user agents/implementations on the public Internet. My
problems w/ browser implementations is another thing.

In this particular case (URIs), I applaud Anne's attempt to fix the broken
way browsers handle these strings within their own executable code (i.e
"browsers (apart from Chrome) do not unescape URL escapes."[1]).

However, I find the announcement that he plans to change the names of
things along the way (i.e. "And yes, the plan is to do away with IRI/URI
and just call them all URLs"[1]) a waste of time.

Fixing the code can happen regardless of naming. Do that and do it now.

Thanks.

[1] http://annevankesteren.nl/2012/09/url-equivalence


mca+1.859.757.1449
skype: mca.amundsen
http://amundsen.com/blog/
http://twitter.com/mamund
https://github.com/mamund
http://www.linkedin.com/in/mikeamundsen


On Mon, Oct 22, 2012 at 8:15 PM, Tim Bray <tbray@textuality.com> wrote:

> One more data point... I work on Web software all the time and have for
> many years; in recent years mostly at the REST (app-to-app HTTP
> conversations) rather than browser-wrangling level.  I=92d have to say th=
at
> URI interoperability problems haven=92t come near getting into the list o=
f
> top-20 pain points.   So either my experience is wildly untypical, or may=
be
> it=92s a combination of being a little bit lucky, and that the pain which
> exists is highly concentrated in the browser space.  -T
>
> On Mon, Oct 22, 2012 at 5:05 PM, Ian Hickson <ian@hixie.ch> wrote:
>
>> On Tue, 23 Oct 2012, Mark Nottingham wrote:
>> > On 23/10/2012, at 10:40 AM, Ian Hickson <ian@hixie.ch> wrote:
>> > > On Tue, 23 Oct 2012, Mark Nottingham wrote:
>> > >>
>> > >> Don't much care about the venue, as long as there's *some*
>> > >> coordination / communication.
>> > >
>> > > Everyone is welcome to participate in the WHATWG list.
>> >
>> > As they are on the IETF list. The difference is that the WHATWG is run
>> > by an unelected board of "members" - <http://www.whatwg.org/charter>.
>>
>> "Run" is a bit of a strong word. There's basically no non-public activit=
y
>> from the charter members.
>>
>>
>> > > Anne's spec will define "valid URL", which addressed that need.
>> >
>> > Why not define (or reuse) a separate term for the input stream, and
>> > leave "URL" alone?
>>
>> Because everyone calls these things URLs (except STD 66).
>>
>>
>> > >> Browser implementers may not care, but it's pretty obvious that lot=
s
>> > >> of other people do.
>> > >
>> > > Browser implementors aren't particularly special here.
>> >
>> > No, but your arguments are often coloured by your perspective -- just =
as
>> > everyone else's are.
>>
>> Which arguments in particular are we talking about here? I've mostly bee=
n
>> talking about curl, wget, GoogleBot, Perl libraries, etc.
>>
>>
>> > If I believed that Anne was willing to and capable of re-specifying
>> > RFC3986 in such a way that the definition, syntax and semantics of URL=
s
>> > (or whatever they ends up being called) doesn't change at all, I'd be
>> > less concerned.
>> >
>> > However, that doesn't seem very likely, especially when he isn't
>> > engaging with the folks that wrote that spec (especially, Roy).
>> >
>> > RFC3986 is referenced by a LOT of technologies, not just Web browsers,
>> > not just HTML. Replacing it unilaterally with input from the browser /
>> > HTML community from an implementer perspective is very likely to break
>> > most of them.
>>
>> I suspect it will break nothing, but I guess we'll find out.
>>
>> I don't really understand how it _could_ break anything, so long as the
>> processing of IRI and URIs as defined by IETF is the same in the WHATWG
>> spec, except where software already differs with the IETF specs.
>>
>> Do you have a concrete example I could study?
>>
>>
>> > As such, they won't use your new spec, and we'll be living in a world
>> > where there will be two definitions of "URL" -- the IETF one and the
>> > WHATWG one [...].
>> >
>> > That seems a pretty bad tradeoff for the benefits you're getting -- a
>> > slightly easier-to-read spec for browser implementers (a relatively ti=
ny
>> > audience).
>>
>> If you have any concrete concerns, please don't hesitate to e-mail the
>> WHATWG list, showing the specific examples you're worried about. Browser=
s
>> are but one of many implementation classes that are relevant.
>>
>>
>> --
>> Ian Hickson               U+1047E                )\._.,--....,'``.    fL
>> http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
>> Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
>>
>
>

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

&lt;snip&gt;<div>I=92d have to say that URI interoperability problems haven=
=92t come near getting into the list of top-20 pain points.=A0</div><div>&l=
t;/snip&gt;</div><div>I can&#39;t recall the last time i experienced &quot;=
URI interoperability problems&quot; across various user agents/implementati=
ons on the public Internet. My problems w/ browser implementations is anoth=
er thing.</div>

<div><br></div><div>In this particular case (URIs), I applaud Anne&#39;s at=
tempt to fix the broken way browsers handle these strings within their own =
executable code (i.e &quot;browsers (apart from Chrome) do not unescape URL=
 escapes.&quot;[1]).</div>

<div><br></div><div>However, I find the=A0announcement=A0that he plans to c=
hange the names of things along the way (i.e. &quot;And yes, the plan is to=
 do away with IRI/URI and just call them all URLs&quot;[1]) a waste of time=
.</div>

<div><br></div><div>Fixing the code can happen regardless of naming. Do tha=
t and do it now.</div><div><br></div><div>Thanks.</div><div><br></div><div>=
[1]=A0<a href=3D"http://annevankesteren.nl/2012/09/url-equivalence">http://=
annevankesteren.nl/2012/09/url-equivalence</a></div>

<div><br></div><div><br clear=3D"all">mca+1.859.757.1449<br>skype: mca.amun=
dsen<br><a href=3D"http://amundsen.com/blog/" target=3D"_blank">http://amun=
dsen.com/blog/</a><br><a href=3D"http://twitter.com/mamund" target=3D"_blan=
k">http://twitter.com/mamund</a><br>

<a href=3D"https://github.com/mamund" target=3D"_blank">https://github.com/=
mamund</a><br><a href=3D"http://www.linkedin.com/in/mikeamundsen" target=3D=
"_blank">http://www.linkedin.com/in/mikeamundsen</a><br>
<br><br><div class=3D"gmail_quote">On Mon, Oct 22, 2012 at 8:15 PM, Tim Bra=
y <span dir=3D"ltr">&lt;<a href=3D"mailto:tbray@textuality.com" target=3D"_=
blank">tbray@textuality.com</a>&gt;</span> wrote:<br><blockquote class=3D"g=
mail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-l=
eft:1ex">

One more data point... I work on Web software all the time and have for man=
y years; in recent years mostly at the REST (app-to-app HTTP conversations)=
 rather than browser-wrangling level.=A0 I=92d have to say that URI interop=
erability problems haven=92t come near getting into the list of top-20 pain=
 points.=A0=A0 So either my experience is wildly untypical, or maybe it=92s=
 a combination of being a little bit lucky, and that the pain which exists =
is highly concentrated in the browser space.=A0 -T<br>


<br><div class=3D"gmail_quote"><div class=3D"im">On Mon, Oct 22, 2012 at 5:=
05 PM, Ian Hickson <span dir=3D"ltr">&lt;<a href=3D"mailto:ian@hixie.ch" ta=
rget=3D"_blank">ian@hixie.ch</a>&gt;</span> wrote:<br></div><blockquote cla=
ss=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;pa=
dding-left:1ex">


<div><div class=3D"im">On Tue, 23 Oct 2012, Mark Nottingham wrote:<br></div=
><div class=3D"im">
&gt; On 23/10/2012, at 10:40 AM, Ian Hickson &lt;<a href=3D"mailto:ian@hixi=
e.ch" target=3D"_blank">ian@hixie.ch</a>&gt; wrote:<br>
&gt; &gt; On Tue, 23 Oct 2012, Mark Nottingham wrote:<br>
&gt; &gt;&gt;<br></div><div class=3D"im">
&gt; &gt;&gt; Don&#39;t much care about the venue, as long as there&#39;s *=
some*<br>
&gt; &gt;&gt; coordination / communication.<br>
&gt; &gt;<br></div>
&gt; &gt; Everyone is welcome to participate in the WHATWG list.<br>
&gt;<br>
&gt; As they are on the IETF list. The difference is that the WHATWG is run=
<br>
&gt; by an unelected board of &quot;members&quot; - &lt;<a href=3D"http://w=
ww.whatwg.org/charter" target=3D"_blank">http://www.whatwg.org/charter</a>&=
gt;.<br>
<br>
</div>&quot;Run&quot; is a bit of a strong word. There&#39;s basically no n=
on-public activity<br>
from the charter members.<br>
<div><br>
<br>
&gt; &gt; Anne&#39;s spec will define &quot;valid URL&quot;, which addresse=
d that need.<br>
&gt;<br>
&gt; Why not define (or reuse) a separate term for the input stream, and<br=
>
&gt; leave &quot;URL&quot; alone?<br>
<br>
</div>Because everyone calls these things URLs (except STD 66).<br>
<div><div class=3D"im"><br>
<br>
&gt; &gt;&gt; Browser implementers may not care, but it&#39;s pretty obviou=
s that lots<br>
&gt; &gt;&gt; of other people do.<br>
&gt; &gt;<br></div>
&gt; &gt; Browser implementors aren&#39;t particularly special here.<br>
&gt;<br>
&gt; No, but your arguments are often coloured by your perspective -- just =
as<br>
&gt; everyone else&#39;s are.<br>
<br>
</div>Which arguments in particular are we talking about here? I&#39;ve mos=
tly been<br>
talking about curl, wget, GoogleBot, Perl libraries, etc.<br>
<div><br>
<br>
&gt; If I believed that Anne was willing to and capable of re-specifying<br=
>
&gt; RFC3986 in such a way that the definition, syntax and semantics of URL=
s<br>
&gt; (or whatever they ends up being called) doesn&#39;t change at all, I&#=
39;d be<br>
&gt; less concerned.<br>
&gt;<br>
&gt; However, that doesn&#39;t seem very likely, especially when he isn&#39=
;t<br>
&gt; engaging with the folks that wrote that spec (especially, Roy).<br>
&gt;<br>
&gt; RFC3986 is referenced by a LOT of technologies, not just Web browsers,=
<br>
&gt; not just HTML. Replacing it unilaterally with input from the browser /=
<br>
&gt; HTML community from an implementer perspective is very likely to break=
<br>
&gt; most of them.<br>
<br>
</div>I suspect it will break nothing, but I guess we&#39;ll find out.<br>
<br>
I don&#39;t really understand how it _could_ break anything, so long as the=
<br>
processing of IRI and URIs as defined by IETF is the same in the WHATWG<br>
spec, except where software already differs with the IETF specs.<br>
<br>
Do you have a concrete example I could study?<br>
<div><br>
<br>
&gt; As such, they won&#39;t use your new spec, and we&#39;ll be living in =
a world<br>
&gt; where there will be two definitions of &quot;URL&quot; -- the IETF one=
 and the<br>
</div>&gt; WHATWG one [...].<br>
<div>&gt;<br>
&gt; That seems a pretty bad tradeoff for the benefits you&#39;re getting -=
- a<br>
&gt; slightly easier-to-read spec for browser implementers (a relatively ti=
ny<br>
&gt; audience).<br>
<br>
</div>If you have any concrete concerns, please don&#39;t hesitate to e-mai=
l the<br>
WHATWG list, showing the specific examples you&#39;re worried about. Browse=
rs<br>
are but one of many implementation classes that are relevant.<div class=3D"=
im"><br>
<div><div><br>
--<br>
Ian Hickson =A0 =A0 =A0 =A0 =A0 =A0 =A0 U+1047E =A0 =A0 =A0 =A0 =A0 =A0 =A0=
 =A0)\._.,--....,&#39;``. =A0 =A0fL<br>
<a href=3D"http://ln.hixie.ch/" target=3D"_blank">http://ln.hixie.ch/</a> =
=A0 =A0 =A0 U+263A =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0/, =A0 _.. \ =A0 _\ =A0;`=
._ ,.<br>
Things that are impossible just take longer. =A0 `._.-(,_..&#39;--(,_..&#39=
;`-.;.&#39;<br>
</div></div></div></blockquote></div><br>
</blockquote></div><br></div>

--20cf3071d090667ed004ccaf1df1--

From ian@hixie.ch  Mon Oct 22 18:02:03 2012
Return-Path: <ian@hixie.ch>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A14901F0C5F for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 18:02:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.494
X-Spam-Level: 
X-Spam-Status: No, score=-2.494 tagged_above=-999 required=5 tests=[AWL=0.105,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NO70kTPta1r8 for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 18:02:03 -0700 (PDT)
Received: from homiemail-a45.g.dreamhost.com (caibbdcaaaaf.dreamhost.com [208.113.200.5]) by ietfa.amsl.com (Postfix) with ESMTP id 032C21F0C51 for <ietf@ietf.org>; Mon, 22 Oct 2012 18:02:03 -0700 (PDT)
Received: from homiemail-a45.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a45.g.dreamhost.com (Postfix) with ESMTP id 160E84806C; Mon, 22 Oct 2012 18:02:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=hixie.ch; h=date:from:to :cc:subject:in-reply-to:message-id:references:mime-version: content-type; s=hixie.ch; bh=toGxC/aadf99DjkdRm+NMFMOoO0=; b=gq1 e6cHItxcZTikfZUvuLEi3JA2ZTJSnRiNvUkLaBX163wldVkCMIrJh4L/gqjzYzng ij0H4WI2tv6ycMSM5kaU1jqdUgjbb9xpKkJdYc1VoD/iGReObcW1xSyi0z2xp9Pz rWLvyF8Ui3APoQEOccDdZ8CYfuWmg+djxhMilUic=
Received: from ps20323.dreamhostps.com (ps20323.dreamhost.com [69.163.222.251]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: internal@index.hixie.ch) by homiemail-a45.g.dreamhost.com (Postfix) with ESMTPSA id F3AB24802D;  Mon, 22 Oct 2012 18:02:08 -0700 (PDT)
Date: Tue, 23 Oct 2012 01:02:02 +0000 (UTC)
From: Ian Hickson <ian@hixie.ch>
To: Tim Bray <tbray@textuality.com>
Subject: Re: [whatwg] New URL Standard from Anne van Kesteren on 2012-09-24 (public-whatwg-archive@w3.org from September 2012)
In-Reply-To: <CAHBU6iv29xAJvgVtcNVpYX=23tydt+mCOQegRiNLV=K8sCh-Cg@mail.gmail.com>
Message-ID: <Pine.LNX.4.64.1210230055550.2471@ps20323.dreamhostps.com>
References: <50604C1A.7090901@gmx.de> <5060A964.5060001@stpeter.im> <Pine.LNX.4.64.1210172354500.2478@ps20323.dreamhostps.com> <507F5A7E.6040206@arcanedomain.com> <50856E3C.103@gmail.com> <Pine.LNX.4.64.1210221753010.2471@ps20323.dreamhostps.com> <0DBC8A11-319C-4120-975E-7E40FD5818BF@gbiv.com> <Pine.LNX.4.64.1210222137530.2471@ps20323.dreamhostps.com> <5085C4BA.2030505@gmx.de> <Pine.LNX.4.64.1210222220510.2471@ps20323.dreamhostps.com> <CAHBU6is8LNZ7Rq-vwLuOm+8ThKB9c=QPwbUfQwDQD5bDPjtf7w@mail.gmail.com> <Pine.LNX.4.64.1210222320070.2471@ps20323.dreamhostps.com> <09DC68AA-2DAD-4CB1-9CA9-799AF12B7BE2@mnot.net> <Pine.LNX.4.64.1210222337520.2471@ps20323.dreamhostps.com> <D9485C0B-E3DA-4B51-9A25-9EAB018C1951@mnot.net> <Pine.LNX.4.64.1210222359080.2471@ps20323.dreamhostps.com> <CAHBU6iv29xAJvgVtcNVpYX=23tydt+mCOQegRiNLV=K8sCh-Cg@mail.gmail.com>
Content-Language: en-GB-hixie
Content-Style-Type: text/css
MIME-Version: 1.0
Content-Type: MULTIPART/MIXED; BOUNDARY="-1555694626-39812219-1350954122=:2471"
X-Mailman-Approved-At: Tue, 23 Oct 2012 09:13:03 -0700
Cc: IETF Discussion <ietf@ietf.org>, Julian Reschke <julian.reschke@gmx.de>, "Roy T. Fielding" <fielding@gbiv.com>, Jan Algermissen <jan.algermissen@nordsc.com>, URI <uri@w3.org>, Noah Mendelsohn <nrm@arcanedomain.com>, Mark Nottingham <mnot@mnot.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, 23 Oct 2012 01:02:03 -0000

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

---1555694626-39812219-1350954122=:2471
Content-Type: TEXT/PLAIN; charset=UTF-8
Content-Transfer-Encoding: QUOTED-PRINTABLE

On Mon, 22 Oct 2012, Tim Bray wrote:
>
> One more data point... I work on Web software all the time and have for=
=20
> many years; in recent years mostly at the REST (app-to-app HTTP=20
> conversations) rather than browser-wrangling level.  I=92d have to say=20
> that URI interoperability problems haven=92t come near getting into the=
=20
> list of top-20 pain points.  So either my experience is wildly=20
> untypical, or maybe it=92s a combination of being a little bit lucky, and=
=20
> that the pain which exists is highly concentrated in the browser space. =
=20

The importance of error handling goes up dramatically as the number of=20
participants in a space increases. When one is writing private software=20
where you write the server and the client, one is unlikely to run into any=
=20
problems that one would attribute to the specs. When one is writing=20
software with a few hundred participants, these kinds of errors occur, but=
=20
it's trivial to deal with them by telling the offending people to follow=20
the spec. When one is dealing with trillions of items, it becomes=20
impossible to fix the problems, and error-handling becomes necessary.

The Web is a classic example of the latter, so browser vendors and authors=
=20
of software that interacts with the Web, e.g. Web search engine software=20
(GoogleBot), Web mirroring software (wget), etc, often run into it.

--=20
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
---1555694626-39812219-1350954122=:2471--

From peter@akayla.com  Mon Oct 22 18:24:06 2012
Return-Path: <peter@akayla.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E107321F88EE; Mon, 22 Oct 2012 18:24:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.097
X-Spam-Level: *
X-Spam-Status: No, score=1.097 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MANGLED_LIST=2.3, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tbnLWoVmY6-0; Mon, 22 Oct 2012 18:24:04 -0700 (PDT)
Received: from m1plsmtpa01-04.prod.mesa1.secureserver.net (m1plsmtpa01-04.prod.mesa1.secureserver.net [64.202.165.6]) by ietfa.amsl.com (Postfix) with ESMTP id 5DB2521F841E; Mon, 22 Oct 2012 18:24:03 -0700 (PDT)
Received: from [10.1.168.230] ([198.228.207.143]) by m1plsmtpa01-04.prod.mesa1.secureserver.net with  id ERQ01k00436ACtS01RQ1yU; Mon, 22 Oct 2012 18:24:02 -0700
References: <CCAA0CA5.11A5%peter@akayla.com> <F9C49DE0-5BB3-4714-96A7-96EA7DA94DF7@oracle.com>
Mime-Version: 1.0 (1.0)
In-Reply-To: <F9C49DE0-5BB3-4714-96A7-96EA7DA94DF7@oracle.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-Id: <1ACD4B0A-FA94-46BE-8343-2B3D6A6ACCDB@akayla.com>
X-Mailer: iPhone Mail (10A405)
From: Peter Yee <peter@akayla.com>
Subject: Re: Gen-ART review of draft-ietf-nfsv4-federated-fs-protocol-13
Date: Mon, 22 Oct 2012 21:24:00 -0400
To: Chuck Lever <chuck.lever@oracle.com>
X-Mailman-Approved-At: Tue, 23 Oct 2012 09:13:03 -0700
Cc: "<gen-art@ietf.org>" <gen-art@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "<draft-ietf-nfsv4-federated-fs-protocol.all@tools.ietf.org>" <draft-ietf-nfsv4-federated-fs-protocol.all@tools.ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Oct 2012 01:24:06 -0000

Chuck,

I'll cheerfully settle for the status quo. Please ignore that comment.=20

Thanks.=20

                                -Peter


On Oct 22, 2012, at 4:10 PM, Chuck Lever <chuck.lever@oracle.com> wrote:

>=20
> On Oct 21, 2012, at 11:35 PM, Peter Yee <peter@akayla.com> wrote:
>=20
>> Chuck,
>>    Ranges include the 0,255 that appears commonly in the document in
>> attribute definitions along with one case of -2147483648,2147483647.
>=20
> Hi Peter-
>=20
> Upon further review, I see the document uses "interval notation" when defi=
ning ranges of allowed values in attributes.  The use of square brackets den=
otes inclusivity.  If you feel readers need more, or our use of this notatio=
n is inconsistent, I'm happy to add clarification.
>=20
>>    Kind regards,
>>        -Peter
>>=20
>> On 10/21/12 3:27 PM, "Chuck Lever" <chuck.lever@oracle.com> wrote:
>>=20
>>>=20
>>> On Oct 21, 2012, at 5:39 PM, Peter Yee <peter@akayla.com> wrote:
>>>=20
>>>> I am the assigned Gen-ART reviewer for this draft. For background on
>>>> Gen-ART, please see the FAQ at
>>>> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>
>>>>=20
>>>> Document: draft-ietf-nfsv4-federated-fs-protocol-13
>>>> Reviewer: Peter Yee
>>>> Review Date: Oct-19-2012
>>>> IETF LC End Date: Oct-22-2012
>>>> IESG Telechat date: TBD
>>>>=20
>>>>=20
>>>> Summary: This draft is basically ready for publication, but has nits
>>>> that
>>>> should be fixed before publication. [Ready with nits.]
>>>>=20
>>>>=20
>>>> This Standards Track document describes a protocol for maintaining a
>>>> Namespace Database for use with federated filesystem protocols.  The
>>>> document is well-written with good examples and little need to jump bac=
k
>>>> and forth in the text to understand it.
>>>>=20
>>>> General: Are ranges (in attribute values) inclusive or exclusive?  They=

>>>> appear to be inclusive, but it might be worth saying that somewhere, if=

>>>> only once.
>>>=20
>>> Can you give me an example of a range that might need clarification?
>>>=20
>>> I will address these comments and co-ordinate draft updates with our WG
>>> editor, Tom Haynes.
>>>=20
>>> Thanks for your review.
>>>=20
>>>> Section 2.7, NsdbName definition: expand NSDB to Namespace Database as
>>>> this is the first use of the term.
>>>>=20
>>>> Section 2.8.1, 2nd sentence: "extention" -> "extension"
>>>>=20
>>>> Section 2.8.3, 2nd paragraph, last sentence: in addition to checking fo=
r
>>>> added FSL records, shouldn't the fileserver also be checking for delete=
d
>>>> or migrated FSLs?  And why would the fileserver do this at the
>>>> expiration
>>>> of the FSN TTL instead of waiting for the next access to the that FSN?
>>>> Otherwise the fileserver could be generating unnecessary traffic,
>>>> although
>>>> there is a tradeoff to be made vs. performance.
>>>>=20
>>>> Section 2.8.3, 3rd paragraph after bullet items, 1st sentence: "which"
>>>> ->
>>>> "that".  (Yeah, I know, grammar police.)
>>>>=20
>>>> Section 2.9, 3rd paragraph, 2nd sentence: "admininistrative" ->
>>>> "administrative"
>>>>=20
>>>> Section 2.12, 2nd paragraph, last sentence: expand NCE (NSDB Container
>>>> Entry) as this is the first use of the term.
>>>>=20
>>>> Section 3.2, item #5: "fs_location" -> "fs_locations"
>>>>=20
>>>> Section 4.1, 1st paragraph, 3rd sentence: probably worth expanding "DSE=
"
>>>> to "DSA-specific entry" here.
>>>>=20
>>>> Section 4.2.1.8, 1st paragraph, 2nd sentence: bracket "Section 2.8.1" i=
n
>>>> "(see" and ")" for readability.
>>>>=20
>>>> Section 4.2.2: "LDAP Objects" -> "LDAP Object Classes" seems
>>>> appropriate.
>>>>=20
>>>> Section 4.2.2.1, 2nd and 3rd sentences: replace "fedfsFsn" with
>>>> "fedfsNsdbContainerInfo"
>>>>=20
>>>> Section 4.2.2.2, 5th paragraph: how is the prohibition on referencing
>>>> other attributes in the fedfsFsn object class supposed to work if this
>>>> document is the defining document for that object class?
>>>>=20
>>>> Section 5.1.3.1, 1st paragraph after LDIF definition: a port number of
>>>> 2049 is given.  Since this is already the default value, why not use a
>>>> different value?  Otherwise, there would be no practical need to includ=
e
>>>> that port number in the FSL creation request.
>>>>=20
>>>> Section 5.1.3.1, 1st paragraph after LDIF definition: "up to date" ->
>>>> "up-to-date"
>>>>=20
>>>> Section 5.1.3.2, 2nd paragraph: "a" -> "an"
>>>>=20
>>>> Section 5.1.3.2, table entry for "fedfsNfsVarSub": "substituion" ->
>>>> "substitution"
>>>>=20
>>>> Section 5.1.4, 1st paragraph, 1st sentence: "a Fileset location" -> "an=

>>>> FSL"
>>>>=20
>>>> Section 7.3, 2nd paragraph, "Specification" value: presumably this will=

>>>> be
>>>> changed to the RFC number when issued?
>>>>=20
>>>> Section 8, 1st paragraph (definition of Administrator): "an" -> "a"
>>>>=20
>>>> Section 8, 3rd paragraph (definition of Client): "filesystem access" ->=

>>>> "file-access" for consistency of usage with the rest of the document.
>>>>=20
>>>> Section 8, 5th paragraph (definition of Fileserver): rather than
>>>> discussing "a filesystem", should this be "one or more filesystems"?  O=
r
>>>> is a fileserver limited to exporting one filesystem?
>>>>=20
>>>> Section 8, 8th paragraph (definition of Filesystem Access Protocol):
>>>> following up on the 3rd paragraph, should this be "File-access Protocol=
"
>>>> for consistency?
>>>>=20
>>>> Section 8, 9th paragraph (definition of FSL), 2nd sentence:
>>>> "fs_location"
>>>> -> "fs_locations".
>>>=20
>>> --=20
>>> Chuck Lever
>>> chuck[dot]lever[at]oracle[dot]com
>>=20
>> <default[4].xml>
>=20
> --=20
> Chuck Lever
> chuck[dot]lever[at]oracle[dot]com
>=20
>=20
>=20
>=20
>=20

From pe-jiang@kddi.com  Mon Oct 22 18:39:29 2012
Return-Path: <pe-jiang@kddi.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5F0FE1F0C67 for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 18:39:29 -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, J_CHICKENPOX_14=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0YZCiJ4jOFHT for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 18:39:28 -0700 (PDT)
Received: from UTMC1102.kddi.com (athena.kddi.com [210.141.112.39]) by ietfa.amsl.com (Postfix) with ESMTP id 276701F0429 for <ietf@ietf.org>; Mon, 22 Oct 2012 18:39:27 -0700 (PDT)
Received: from UTMC1131 (unknown [10.5.16.192]) by UTMC1102.kddi.com (Postfix) with SMTP id 1BBF61E17; Tue, 23 Oct 2012 10:39:26 +0900 (JST)
Received: from UTMC1123.kddi.com (localhost [127.0.0.1]) by localhost.kddi.com (Postfix) with ESMTP id A47751C45; Tue, 23 Oct 2012 10:39:18 +0900 (JST)
Received: from UTMC1114.kddi.com (unknown [10.5.16.17]) by UTMC1123.kddi.com (Postfix) with ESMTP id 846EB1BD2; Tue, 23 Oct 2012 10:39:18 +0900 (JST)
Received: from KDDI-0806PC0671 ([10.200.129.117] [10.200.129.117]) by post-ims.kddi.com with ESMTPA; Tue, 23 Oct 2012 10:39:18 +0900
To: lberger@labn.net, ietf@ietf.org
Subject: Re: Last Call: <draft-kumaki-murai-l3vpn-rsvp-te-06.txt> (Supportfor RSVP-TE in L3VPNs) to Experimental RFC
From: Peng JIANG <pe-jiang@kddi.com>
References: <20120905224357.14197.39927.idtracker@ietfa.amsl.com> <5085E77C.5020100@labn.net>
In-Reply-To: <5085E77C.5020100@labn.net>
Message-Id: <201210231039.GAJ87540.KFBHtQOJ@kddi.com>
X-Mailer: Winbiff [Version 2.51 PL3]
X-Accept-Language: ja,en,zh
Date: Tue, 23 Oct 2012 10:39:18 +0900
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-WAuditID: 1210231039180000125691
X-Mailman-Approved-At: Tue, 23 Oct 2012 09:13:03 -0700
Cc: afarrel@juniper.net, draft-kumaki-murai-l3vpn-rsvp-te.all@tools.ietf.org, daniel@olddog.co.uk, 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, 23 Oct 2012 01:39:29 -0000

Hello Lou,

> > As to the technical details, the next hop as identified by the Path 
> > message in the VPN context, will have a route and associated label 
> > within the VPN context. This VPN label can be added to the Path 
> > message, just as it would be for any VPN IP packet, and additional 
> > labels may be added for PE-PE transport. In implementations that 
> > rewrite the IP header, the IP destination can be set to the next
> > hop. The remote PE/next hop will receive the Path message with the
> > VPN label which will identify the VPN context/VRF. This PE will then
> > need to identify the packet as RSVP using either the router alert
> > mechanism or based on the IP header destination address. So I see no
> > reason for the modifications when the VAN-specific MPLS labels are
> > used.
> >
> > Shout if you think I missed something.

We think you are correct about the Path message.
But Resv messages are different. The Resv messages are sent hop-
by-hop. The destination is not the remote PE but the unicast 
address of a previous RSVP hop when a PE send out a Resv message.
 Therefor, there will be no VPN label and the remote PE will 
have no method to identify the VPN context/VRF.

In RFC 2205:
3.1.3 Path Messages
A Path message travels from a sender to receiver(s) along the 
same path(s) used by the data packets.  The IP source address of
 a Path message must be an address of the sender it describes, 
while the destination address must be the DestAddress for the 
session.
3.1.4 Resv Messages
Resv messages carry reservation requests hop-by-hop from 
receivers to senders, along the reverse paths of data flows for 
the session. The IP destination address of a Resv message is the
 unicast address of a previous-hop node, obtained from the path 
state. 

> > My high-order take away is that it seems to me that this draft runs
> > counter to hierarchy-based solutions that can solve this problem just
> > fine without any additional RSVP modifications. I therefore think
> > this draft should be run through a WG that is willing to reconcile
> > the approaches (and fully document their uses case supported by
> > hierarchy). Failing that, I think the draft should have an IESG 
> > applicability note added saying that this is experimental only and
> > that standard hierarchy should be used to solve the problem in any 
> > operational implementation/network.
As I have explained, For Resv messages, hierarchy-based 
solutions are not able to identify the VPN context/VRF at a 
remote PE. 

Hope the above explaination will make sense to you.
Please let us konw if you have any further comments.

Thanks.


Best Regards,
Peng JIANG
KDDI


> 
> Hello,
> 	I made this comment privately during the LC period.  I don't mind
> sharing it more widely:
> 
> > My high-order take away is that it seems to me that this draft runs
> > counter to hierarchy-based solutions that can solve this problem just
> > fine without any additional RSVP modifications. I therefore think
> > this draft should be run through a WG that is willing to reconcile
> > the approaches (and fully document their uses case supported by
> > hierarchy). Failing that, I think the draft should have an IESG 
> > applicability note added saying that this is experimental only and
> > that standard hierarchy should be used to solve the problem in any 
> > operational implementation/network.
> > 
> > As to the technical details, the next hop as identified by the Path 
> > message in the VPN context, will have a route and associated label 
> > within the VPN context. This VPN label can be added to the Path 
> > message, just as it would be for any VPN IP packet, and additional 
> > labels may be added for PE-PE transport. In implementations that 
> > rewrite the IP header, the IP destination can be set to the next
> > hop. The remote PE/next hop will receive the Path message with the
> > VPN label which will identify the VPN context/VRF. This PE will then
> > need to identify the packet as RSVP using either the router alert
> > mechanism or based on the IP header destination address. So I see no
> > reason for the modifications when the VAN-specific MPLS labels are
> > used.
> >
> > Shout if you think I missed something.
> 
> Lou
> On 9/5/2012 6:43 PM, The IESG wrote:
> > 
> > The IESG has received a request from an individual submitter to consider
> > the following document:
> > - 'Support for RSVP-TE in L3VPNs'
> >   <draft-kumaki-murai-l3vpn-rsvp-te-06.txt> as Experimental RFC
> > 
> > The IESG plans to make a decision in the next few weeks, and solicits
> > final comments on this action. Please send substantive comments to the
> > ietf@ietf.org mailing lists by 2012-10-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
> > 
> > 
> >    IP Virtual Private Networks (VPNs) provide connectivity between sites
> >    across an IP/MPLS backbone. These VPNs can be operated using BGP/MPLS
> >    and a single provider edge (PE) node may provide access to multiple
> >    customer sites belonging to different VPNs.
> > 
> >    The VPNs may support a number of customer services including RSVP and
> >    RSVP-TE traffic. This document describes how to support RSVP-TE
> >    between customer sites when a single PE supports multiple VPNs.
> > 
> > 
> > 
> > 
> > 
> > The file can be obtained via
> > http://datatracker.ietf.org/doc/draft-kumaki-murai-l3vpn-rsvp-te/
> > 
> > IESG discussion can be tracked via
> > http://datatracker.ietf.org/doc/draft-kumaki-murai-l3vpn-rsvp-te/ballot/
> > 
> > 
> > No IPR declarations have been submitted directly on this I-D.
> > 
> > Due to an error by the sponsoring Area Director, the Last Call on 
> > this document (which completed on 3rd September) incorrectly 
> > stated that this draft was intended that it be published as Informational.
> > The correct intention (as stated in the draft itself) is that it  be 
> > published as Experimental. 
> > 
> > This Last Call is to verify community consensus for publication of
> > this draft as Experimental. 
> > 
> > 
> > 
> > 
> > 
> > 
> 

From mccap@petoni.org  Mon Oct 22 18:42:29 2012
Return-Path: <mccap@petoni.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 DBA8A1F0C8A for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 18:42:29 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id V75Tqg1pIYa4 for <ietf@ietfa.amsl.com>; Mon, 22 Oct 2012 18:42:27 -0700 (PDT)
Received: from mail-gg0-f172.google.com (mail-gg0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id 592811F0C72 for <ietf@ietf.org>; Mon, 22 Oct 2012 18:42:13 -0700 (PDT)
Received: by mail-gg0-f172.google.com with SMTP id i4so660106ggn.31 for <ietf@ietf.org>; Mon, 22 Oct 2012 18:42:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=petoni.org; s=google; h=mime-version:x-originating-ip:date:message-id:subject:from:to :content-type; bh=CjPBLpHlp+0PZ9ogVy8VYvtKWS+/qb8JsLJG5YxGIxo=; b=D4UMlS7mKhrLuTaeaOWOPKAtukubkINP29akuJc1Y3TLoB5kYRH2FkCbgUQSaO8VGg Sqc/pXAGzqBcWY02SMG4OghyKUV0b8GzMF8doW82mrVDLwzIGpdlhcD8ot5anVx9A75y Rx6mWdKhnNhSxPe2y1DO7BqFzxBlUeX3WtJJg=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:date:message-id:subject:from:to :content-type:x-gm-message-state; bh=CjPBLpHlp+0PZ9ogVy8VYvtKWS+/qb8JsLJG5YxGIxo=; b=pa7z8m3lDvOILFnMXCc2NZKUNHOdKKVTnUsjA3O0h/1Ag3GNCCYRtGMr5sB56fpvkg ZCrMCwuWtrWmsJOK8BBWJzzj385/DMtrpR93Rg8g6QWWBOOgd0ar6e21EXw3bf1+owX5 TZmY4qZMdMIyZQ7GxGiV4CGGOcgsllaew86rHuq0taVUwwIQBrp7F+bwoHIvbnS2B6RS xAE05E5VVjdQ71BMIv4oaOYzm+yJvjdJpq6RcAg0HAT4Ar6j0fLzo7M7TQwhB0sI/A6O J2tHj/kr/b1mFuWsvFBf3pejm2+0hokSz+z3wcyf3XXNMNFwG3J0I995fHm4qnmKLJYz AHaQ==
MIME-Version: 1.0
Received: by 10.236.86.73 with SMTP id v49mr10326282yhe.31.1350956532874; Mon, 22 Oct 2012 18:42:12 -0700 (PDT)
Received: by 10.101.117.7 with HTTP; Mon, 22 Oct 2012 18:42:12 -0700 (PDT)
X-Originating-IP: [68.45.157.93]
Date: Mon, 22 Oct 2012 21:42:12 -0400
Message-ID: <CACvMsLHpd7hqx0A8JzLst_o05cdMRpGcQtgPoMC=kD6xh6u4Tw@mail.gmail.com>
Subject: Gen-ART LC Review of draft-ietf-storm-iser-12
From: Pete McCann <mccap@petoni.org>
To: gen-art@ietf.org, ietf@ietf.org, draft-ietf-storm-iser.all@tools.ietf.org
Content-Type: text/plain; charset=ISO-8859-1
X-Gm-Message-State: ALoCoQlUIP/GhXk8NNic2L/FHa6Roj0ylCf2IskN/8EQpirb/4LCFPngHfwfkkWWx2AD/kh/oECV
X-Mailman-Approved-At: Tue, 23 Oct 2012 09:13:03 -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: Tue, 23 Oct 2012 01:42:30 -0000

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at

<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

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

Document:  draft-ietf-storm-iser-12
Reviewer:  Peter McCann
Review Date:  2012-10-22
IETF LC End Date:  2012-10-22
IESG Telechat date: unknown

Summary: Ready

Major issues: None

Minor issues: None

Nits/editorial comments:

page 38:
   iSERHelloREquired
SHOULD BE:
   iSERHelloRequired

From GK-lists@ninebynine.org  Tue Oct 23 01:39:23 2012
Return-Path: <GK-lists@ninebynine.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 A7D3621F8461 for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 01:39:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3DNM3ijtcXyF for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 01:39:23 -0700 (PDT)
Received: from relay3.mail.ox.ac.uk (relay3.mail.ox.ac.uk [163.1.2.165]) by ietfa.amsl.com (Postfix) with ESMTP id 0B26921F845D for <ietf@ietf.org>; Tue, 23 Oct 2012 01:39:16 -0700 (PDT)
Received: from smtp2.mail.ox.ac.uk ([163.1.2.205]) by relay3.mail.ox.ac.uk with esmtp (Exim 4.75) (envelope-from <GK-lists@ninebynine.org>) id 1TQa0z-0004pY-AC; Tue, 23 Oct 2012 09:39:09 +0100
Received: from gklyne.plus.com ([80.229.154.156] helo=Eskarina.local) by smtp2.mail.ox.ac.uk with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <GK-lists@ninebynine.org>) id 1TQa0y-0000IW-7H; Tue, 23 Oct 2012 09:39:08 +0100
Message-ID: <508655F2.2060800@ninebynine.org>
Date: Tue, 23 Oct 2012 09:31:46 +0100
From: Graham Klyne <GK-lists@ninebynine.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.5; rv:15.0) Gecko/20120907 Thunderbird/15.0.1
MIME-Version: 1.0
To: Ian Hickson <ian@hixie.ch>
Subject: Re: [whatwg] New URL Standard from Anne van Kesteren on 2012-09-24 (public-whatwg-archive@w3.org from September 2012)
References: <50604C1A.7090901@gmx.de> <5060A964.5060001@stpeter.im> <Pine.LNX.4.64.1210172354500.2478@ps20323.dreamhostps.com> <507F5A7E.6040206@arcanedomain.com> <50856E3C.103@gmail.com> <Pine.LNX.4.64.1210221753010.2471@ps20323.dreamhostps.com> <0DBC8A11-319C-4120-975E-7E40FD5818BF@gbiv.com> <Pine.LNX.4.64.1210222137530.2471@ps20323.dreamhostps.com> <5085C4BA.2030505@gmx.de> <Pine.LNX.4.64.1210222220510.2471@ps20323.dreamhostps.com>
In-Reply-To: <Pine.LNX.4.64.1210222220510.2471@ps20323.dreamhostps.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Oxford-Username: zool0635
X-Mailman-Approved-At: Tue, 23 Oct 2012 09:13:03 -0700
Cc: IETF Discussion <ietf@ietf.org>, Julian Reschke <julian.reschke@gmx.de>, "Roy T. Fielding" <fielding@gbiv.com>, Jan Algermissen <jan.algermissen@nordsc.com>, mnot@mnot.net, Noah Mendelsohn <nrm@arcanedomain.com>, URI <uri@w3.org>, Tim Bray <tbray@textuality.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Oct 2012 08:39:23 -0000

On 22/10/2012 23:35, Ian Hickson wrote:
> Consensus isn't a value I hold highly,

!

#g
--


From cowan@ccil.org  Tue Oct 23 06:23:19 2012
Return-Path: <cowan@ccil.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 91A0921F8718 for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 06:23:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DMe6Cv+4dhkl for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 06:23:17 -0700 (PDT)
Received: from earth.ccil.org (earth.ccil.org [192.190.237.11]) by ietfa.amsl.com (Postfix) with ESMTP id 9E17621F849B for <ietf@ietf.org>; Tue, 23 Oct 2012 06:23:15 -0700 (PDT)
Received: from cowan by earth.ccil.org with local (Exim 4.72) (envelope-from <cowan@ccil.org>) id 1TQeRi-0006cd-3W; Tue, 23 Oct 2012 09:23:02 -0400
Date: Tue, 23 Oct 2012 09:23:02 -0400
From: John Cowan <cowan@mercury.ccil.org>
To: Graham Klyne <GK-lists@ninebynine.org>
Subject: Re: [whatwg] New URL Standard from Anne van Kesteren on 2012-09-24 (public-whatwg-archive@w3.org from September 2012)
Message-ID: <20121023132301.GC7895@mercury.ccil.org>
References: <5060A964.5060001@stpeter.im> <Pine.LNX.4.64.1210172354500.2478@ps20323.dreamhostps.com> <507F5A7E.6040206@arcanedomain.com> <50856E3C.103@gmail.com> <Pine.LNX.4.64.1210221753010.2471@ps20323.dreamhostps.com> <0DBC8A11-319C-4120-975E-7E40FD5818BF@gbiv.com> <Pine.LNX.4.64.1210222137530.2471@ps20323.dreamhostps.com> <5085C4BA.2030505@gmx.de> <Pine.LNX.4.64.1210222220510.2471@ps20323.dreamhostps.com> <508655F2.2060800@ninebynine.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <508655F2.2060800@ninebynine.org>
User-Agent: Mutt/1.5.20 (2009-06-14)
Sender: John Cowan <cowan@ccil.org>
X-Mailman-Approved-At: Tue, 23 Oct 2012 09:12:56 -0700
Cc: IETF Discussion <ietf@ietf.org>, Julian Reschke <julian.reschke@gmx.de>, "Roy T. Fielding" <fielding@gbiv.com>, Jan Algermissen <jan.algermissen@nordsc.com>, mnot@mnot.net, Noah Mendelsohn <nrm@arcanedomain.com>, URI <uri@w3.org>, Tim Bray <tbray@textuality.com>, Ian Hickson <ian@hixie.ch>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Oct 2012 13:23:19 -0000

Graham Klyne scripsit:

> On 22/10/2012 23:35, Ian Hickson wrote:
> >Consensus isn't a value I hold highly,
> 
> !

Just call him Frank Sinatra.

-- 
John Cowan   cowan@ccil.org    http://ccil.org/~cowan
I am he that buries his friends alive and drowns them and draws them
alive again from the water. I came from the end of a bag, but no bag
went over me.  I am the friend of bears and the guest of eagles. I am
Ringwinner and Luckwearer; and I am Barrel-rider.  --Bilbo to Smaug

From julian.reschke@gmx.de  Tue Oct 23 06:27:08 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 BD47021F849C for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 06:27:08 -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.628, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q8BPjfNkKXvc for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 06:27:07 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by ietfa.amsl.com (Postfix) with SMTP id 73ED221F84B1 for <ietf@ietf.org>; Tue, 23 Oct 2012 06:27:07 -0700 (PDT)
Received: (qmail invoked by alias); 23 Oct 2012 13:27:05 -0000
Received: from mail.greenbytes.de (EHLO [192.168.1.140]) [217.91.35.233] by mail.gmx.net (mp020) with SMTP; 23 Oct 2012 15:27:05 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX18ma8l03Pcms/p9yKvtPBrUsNJXmQDDLlcvSsmsF6 35/qKrpMJmOs8e
Message-ID: <50869B24.2070109@gmx.de>
Date: Tue, 23 Oct 2012 15:27:00 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121010 Thunderbird/16.0.1
MIME-Version: 1.0
To: Ian Hickson <ian@hixie.ch>
Subject: websockets in the IETF, was: [whatwg] New URL Standard from Anne van Kesteren on 2012-09-24 (public-whatwg-archive@w3.org from September 2012)
References: <50604C1A.7090901@gmx.de> <5060A964.5060001@stpeter.im> <Pine.LNX.4.64.1210172354500.2478@ps20323.dreamhostps.com> <507F5A7E.6040206@arcanedomain.com> <50856E3C.103@gmail.com> <Pine.LNX.4.64.1210221753010.2471@ps20323.dreamhostps.com> <0DBC8A11-319C-4120-975E-7E40FD5818BF@gbiv.com> <Pine.LNX.4.64.1210222137530.2471@ps20323.dreamhostps.com> <5085C4BA.2030505@gmx.de> <Pine.LNX.4.64.1210222220510.2471@ps20323.dreamhostps.com> <CABP7RbfgQrgduOzWaXcYieV3cw_=UoBaCC5e=XF+Y3PMEZoRMw@mail.gmail.com> <Pine.LNX.4.64.1210222300490.2471@ps20323.dreamhostps.com> <85CC064C-7592-4249-ACC9-7B55AAC0D7E7@mnot.net> <Pine.LNX.4.64.1210222325540.2471@ps20323.dreamhostps.com> <5DF21D1C-3A60-4E68-9BBF-16B5B69CFF5D@mnot.net> <Pine.LNX.4.64.1210222346590.2471@ps20323.dreamhostps.com>
In-Reply-To: <Pine.LNX.4.64.1210222346590.2471@ps20323.dreamhostps.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
X-Mailman-Approved-At: Tue, 23 Oct 2012 09:13:03 -0700
Cc: IETF Discussion <ietf@ietf.org>, Noah Mendelsohn <nrm@arcanedomain.com>, "Roy T. Fielding" <fielding@gbiv.com>, Jan Algermissen <jan.algermissen@nordsc.com>, URI <uri@w3.org>, Mark Nottingham <mnot@mnot.net>, James M Snell <jasnell@gmail.com>, Tim Bray <tbray@textuality.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Oct 2012 13:27:08 -0000

On 2012-10-23 01:59, Ian Hickson wrote:
> ...
> Whether WebSockets is a good idea or not is besides the point. The point
> is that the hybi group was not a pleasant experience for me. If I were to
> be in a position to do Web Sockets again, I would decline the opportunity
> to do it through the IETF. Doing it through the IETF made the work take a
> year longer than it would have, made the protocol less secure (the WG
> removed a number of defense-in-depth features), and made the spec a mess
 > ...

And, as far as I can tell, fixed a security problem in the original 
design (which caused some UA implementers to actually disable what they 
were shipping at that time): <http://w2spconf.com/2011/papers/websocket.pdf>

> (it's a mishmash of different editing styles). Plus, the group _still_
> hasn't done multiplexing, which some of the vendors said was a prereq to
> implementation, something which, prior to the IETF getting involved, was
> only 3 to 6 months out on the roadmap.
> ...

Indeed, but then wasn't it you arguing *against* having it in the base 
spec? (see 
<http://www.ietf.org/mail-archive/web/hybi/current/msg00239.html>)


Best regards, Julian



From ted.ietf@gmail.com  Tue Oct 23 09:45:01 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 638C71F0C60 for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 09:44:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.527
X-Spam-Level: 
X-Spam-Status: No, score=-3.527 tagged_above=-999 required=5 tests=[AWL=0.072,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nDTpRmbUHoV4 for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 09:44:55 -0700 (PDT)
Received: from mail-vc0-f172.google.com (mail-vc0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 066441F0C51 for <ietf@ietf.org>; Tue, 23 Oct 2012 09:44:54 -0700 (PDT)
Received: by mail-vc0-f172.google.com with SMTP id fl11so4864574vcb.31 for <ietf@ietf.org>; Tue, 23 Oct 2012 09:44:54 -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=LL0cf4FQFtEG6RK66ROzFQ7eVl14TqSeo8E6KgzNOyI=; b=ZxAGvZHIBXRZsrCamPdPf/0BIq+GmPKijx7EuR6+BUQg3ABOBoReeD6GDUM0Lh5r4l IwymRIwxVUoeEa1cuuZwKFOJVfqAimlWykTJTdcoJ59cjDRQeu3tDiAANDydp7EiFeZK e9hP3p75hZPCT3mo9u0zfk+j3CTC8PDsOpldpHP6EFGEiBMLYjW6KnmbY4jqbxN+VyMk tY+bWTt4puBPcGvStKkZt/26MWcIrkIG0+88b4a38WETz6XEeYj9qhrmclfHyYrYg4rF qy3gWifAvQdjm39b6GY598VE+cJ1ffWRQxAY8C2AlKWBpzArcjMe9i8qPPvqCLojdG25 Fe4w==
MIME-Version: 1.0
Received: by 10.52.90.212 with SMTP id by20mr18075786vdb.118.1351010693827; Tue, 23 Oct 2012 09:44:53 -0700 (PDT)
Received: by 10.58.245.39 with HTTP; Tue, 23 Oct 2012 09:44:53 -0700 (PDT)
In-Reply-To: <Pine.LNX.4.64.1210222137530.2471@ps20323.dreamhostps.com>
References: <50604C1A.7090901@gmx.de> <5060A964.5060001@stpeter.im> <Pine.LNX.4.64.1210172354500.2478@ps20323.dreamhostps.com> <507F5A7E.6040206@arcanedomain.com> <50856E3C.103@gmail.com> <Pine.LNX.4.64.1210221753010.2471@ps20323.dreamhostps.com> <0DBC8A11-319C-4120-975E-7E40FD5818BF@gbiv.com> <Pine.LNX.4.64.1210222137530.2471@ps20323.dreamhostps.com>
Date: Tue, 23 Oct 2012 09:44:53 -0700
Message-ID: <CA+9kkMDpEZCvcG1DJd=O1qPNV+=+GTBeN+CGndUe51Xym_A9sg@mail.gmail.com>
Subject: Re: [whatwg] New URL Standard from Anne van Kesteren on 2012-09-24 (public-whatwg-archive@w3.org from September 2012)
From: Ted Hardie <ted.ietf@gmail.com>
To: Ian Hickson <ian@hixie.ch>
Content-Type: text/plain; charset=ISO-8859-1
Cc: IETF Discussion <ietf@ietf.org>, Julian Reschke <julian.reschke@gmx.de>, "Roy T. Fielding" <fielding@gbiv.com>, URI <uri@w3.org>, Noah Mendelsohn <nrm@arcanedomain.com>, mnot@mnot.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, 23 Oct 2012 16:45:01 -0000

On Mon, Oct 22, 2012 at 2:46 PM, Ian Hickson <ian@hixie.ch> wrote:
> On Mon, 22 Oct 2012, Julian Reschke wrote:
>> >
>> > I couldn't agree more! We've been waiting for four years for the URI
>> > working group to get their act together and fix the URL mess. Nothing
>> > has happened. We lost patience and are now doing it ourselves. ...
>>
>> Clarifying: there is no URI Working Group, and as far as I can tell,
>
> Whoever. The people complaining that it should be done at the IETF haven't
> done any work. That's the complaint. Until they do the work,

Handing things off to the IETF and saying "please go do this work" has
a very low success rate, because that's not how the IETF works.  The
IETF works by bringing together folks interested in solving a
particular problem and putting them in a larger context; that context
can help those working on a point solution see other aspects of their
problem space.  It also provides a set of processes which can be
useful for decision making when the trade-offs may involve different
folks' oxes being gored.

In this case, the concern is that defining what you are doing as a
revision of the URL standard outside the IETF will:

* lose that larger context
* use a process which has a bias toward browser viewpoints, which
raises concerns about trade-offs outside that space
* generate a fork, either directly or in the creation of two
communities which understand URL to be either a subset of URI in the
STD 66 sense or the "input string to web identifier" sense that Anne's
work uses.

It's tedious when people say "you should come here and do the work",
and I apologize that I'm about to say it.  But for work which
redefines IETF standards, the IETF is really the place to do it, and
preserving that context is important to making sure that the
communities of use retain a single standard.  I share your frustration
with the pace of work on related topics, but I urge you to put energy
into the process rather than simply appropriating the term.

If you choose not call what you're doing a "URL" but by some other
term ("fleen" is my favorite), then the issue does not arise; at most,
someone needs to later define how a fleen and URL relate, but that's
much less likely to cause confusion.

My two cents, as an individual as always,

Ted

From mstjohns@comcast.net  Tue Oct 23 10:20:14 2012
Return-Path: <mstjohns@comcast.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C93D611E80D1 for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 10:20:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.135
X-Spam-Level: 
X-Spam-Status: No, score=-100.135 tagged_above=-999 required=5 tests=[AWL=0.302, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id O2g6XexdMAlN for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 10:20:13 -0700 (PDT)
Received: from qmta04.westchester.pa.mail.comcast.net (qmta04.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:40]) by ietfa.amsl.com (Postfix) with ESMTP id 918DC11E8099 for <ietf@ietf.org>; Tue, 23 Oct 2012 10:20:13 -0700 (PDT)
Received: from omta16.westchester.pa.mail.comcast.net ([76.96.62.88]) by qmta04.westchester.pa.mail.comcast.net with comcast id EbUm1k0041uE5Es54hLJA9; Tue, 23 Oct 2012 17:20:18 +0000
Received: from Mike-T530.comcast.net ([68.83.222.237]) by omta16.westchester.pa.mail.comcast.net with comcast id EhLU1k00b57vnMg3chLWLm; Tue, 23 Oct 2012 17:20:30 +0000
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Tue, 23 Oct 2012 13:16:05 -0400
To: The IAOC <bob.hinden@gmail.com>,ietf@ietf.org
From: Michael StJohns <mstjohns@comcast.net>
Subject: Re: IAOC Request for community feedback
In-Reply-To: <20121022234941.28301.7687.idtracker@ietfa.amsl.com>
References: <20121022234941.28301.7687.idtracker@ietfa.amsl.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Message-Id: <20121023172013.918DC11E8099@ietfa.amsl.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Oct 2012 17:20:15 -0000

Wait just one minute.....


Marshal has neither resigned nor died (both of which would vacate the position).  He apparently *has* abrogated his responsibilities.

I'm not sure why the IAOC thinks that the recall procedure shouldn't be followed.

Get a petition signed.  Run a 1 week call for volunteers. Do the  recall committee selection prior to the IETF, present your case to the recall committee at the IETF and stand back and let them do the work.

I appreciate the pain of having a member go AWOL, but I see no basis for declaring the position vacant based on current practice.

I would consider that your email constitutes evidence that the IAOC has asked for a recall petition to be circulated.  I would consider that the list of grievances you've posted constitutes sufficient grounds for the petition.  

I would estimate that you have sufficient support for the petition to be confirmed, but I don't see anything so critical that would suggest that the recall process need not be followed.

I'm willing to sign on to the petition.  I'm willing to volunteer for the recall committee.

Mike




At 07:49 PM 10/22/2012, The IAOC wrote:
>The IAOC is requesting feedback from the community concerning a
>vacancy that the IAOC feels is not adequately covered by existing IETF
>rules.
>
>Marshall Eubanks has been a active IETF participant for many years and
>a member of the IAOC since 2009. However, he recently stopped
>participating in the IAOC and Trust. The IAOC has made extensive
>efforts to contact Marshall about this, but has not received any
>response. Given the size of the IAOC, a missing member makes it much
>harder to get a quorum. The specifics of his absence include:
>
>- Missed the IAOC calls on 11 October 2012, 10 September 2012,
>   6 September 2012, 23 August 2012
>
>- No email received from Marshall since 1 August 2012 on the IAOC,
>   IETF Trust, and related private lists.
>
>Marshall is subscribed to the IAOC and IETF Trust lists and
>consequently should have received email discussing regular
>IAOC/Trust business including email on this topic.
>
>We have tried to contact Marshall over this time period using email 14
>times, telephone 6 times (leaving messages), SMS messages seven times,
>Linkedin messages once, Facebook messages once, and registered postal
>mail twice. We have not received any response from Marshall. It is
>also our understanding that Marshall has stopped participating in
>other IETF lists and stopped working on IDs he authored.
>
>On 6 September 2012 the IAOC appointed a replacement liaison to the
>IETF NomCom after learning from the NomCom chair that Marshall had not
>responded to emails from the NomCom chair.
>
>Based on all of this, the IAOC has concluded that Marshall's IAOC position
>is vacant.
>
>The IAOC has reviewed BCP101 and concludes it does not handle this
>case very well. BCP101 says that if "an IAOC member abrogates his or
>her duties" the recall process in BCP10/RFC3777 may be used. The
>specific text is:
>
>   IAOC members are subject to recall in the event that an IAOC member
>   abrogates his or her duties or acts against the best interests of the
>   IETF community. Any appointed IAOC member, including any appointed
>   by the IAB, IESG, or ISOC Board of Trustees, may be recalled using
>   the recall procedure defined in RFC 3777 [RFC3777]. IAOC members are
>   not, however, subject to recall by the bodies that appointed them.
>
>   If a vacancy occurs among the appointed members, this is filled by
>   the appointing body for that position according to its procedures.
>
>The conditions for determining that a vacancy exist are not well-defined.
>
>BCP10/RFC3777 (Section 7) defines a process where a recall petition is
>signed by 20 NomCom qualified IETFers, the petition is sent to the
>ISOC President, the ISOC President appoints a recall committee chair,
>the chair follows normal NomCom procedures to select 20 committee
>members (this includes a public call for volunteers, max of two per
>organization, random selection of volunteers, etc.), recall committee
>investigates, recall committee votes and requires a 3/4 majority to
>pass the recall.
>
>We think this process was not intended to be used when a sitting IAOC,
>IESG, or IAB member vacates his/her position. We believe that the
>intended use of this process was for determining whether a member
>should leave a position who is unwilling to leave and who has harmed
>the IETF. That is clearly not the case in this situation, to the
>contrary, we would have preferred Marshall to continue. It doesn't
>seem appropriate in this case, or when an member is unable to
>participate due to illness or death.
>
>The IAOC believes that it is reasonable to declare Marshall's IAOC
>position vacant and, therefore, to ask NomCom to fill his position for
>the remainder of his term (~15 months.)
>
>The IAOC is requesting feedback from the community whether it is
>reasonable to declare Marshall's IAOC position vacant. Responses are
>solicited by no later than 5 November 2012. If there is not community
>support for this approach, the IAOC will pursue the BCP10/RFC3777
>recall petition path because having a missing member for 15 months
>significantly effects the operation of the IAOC and IETF Trust.
>
>Please send your comments to <ietf@ietf.org>.
>
>The IAOC and IETF chairs will review the community feedback and make a
>determination if there is support for declaring the position vacant.
>
>I would add that we all feel very badly for Marshall given his many
>years of service to the IETF. We really don't understand why he is not
>responding and are concerned about it. Unfortunately, we don't know
>what else to do given his lack of response to our many attempts to
>contact him.
>
>Bob Hinden
>IAOC Chair
>
>p.s. A draft is in progress that proposes an update to
>BCP10/RFC3777 similar to what we propose here to handle how cases of
>vacancy be handled. The issue applies to the IAB, IESG, and the IAOC.
>An announcement will be sent when that is available.



From jnc@mercury.lcs.mit.edu  Tue Oct 23 11:42:35 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 8B5DA11E80DC for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 11:42:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.418
X-Spam-Level: 
X-Spam-Status: No, score=-6.418 tagged_above=-999 required=5 tests=[AWL=0.181,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WYX1ofEelK+W for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 11:42:34 -0700 (PDT)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id 2319A11E80A4 for <ietf@ietf.org>; Tue, 23 Oct 2012 11:42:33 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 9FCA418C0A4; Tue, 23 Oct 2012 14:42:29 -0400 (EDT)
To: ietf@ietf.org
Subject: Re: IAOC Request for community feedback
Message-Id: <20121023184229.9FCA418C0A4@mercury.lcs.mit.edu>
Date: Tue, 23 Oct 2012 14:42:29 -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: Tue, 23 Oct 2012 18:42:35 -0000

    > From: Michael StJohns <mstjohns@comcast.net>

    >> The IAOC is requesting feedback from the community concerning a
    >> vacancy that the IAOC feels is not adequately covered by existing IETF
    >> rules.

    > I'm not sure why the IAOC thinks that the recall procedure shouldn't be
    > followed.

Because it's a fairly lengthy, complex, and effort-consuming, process to use
in this kind of case - rather like using a pile-driver to crack a nut?

I hear you, and understand the concern about ignoring established procedures,
but at the same time, calling for a hum from the IETF community is sufficient
to get the _entire procedure_ changed, a far more consequential act, so
asking for a hum to temporarily bypass them seems to me to be acting in the
general spirit.

And of course we do need to update our procedures so that if this ever
happens again, we don't face the choice of rolling out the pile-driver, or
proceeding in an ad hoc way, but that's a separate point.

	Noel

From sm@resistor.net  Tue Oct 23 11:44: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 6DFE11F0CA1 for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 11:44:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.588
X-Spam-Level: 
X-Spam-Status: No, score=-102.588 tagged_above=-999 required=5 tests=[AWL=0.011, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RiFBxGC-w7L7 for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 11:44:08 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id CDEE21F042A for <ietf@ietf.org>; Tue, 23 Oct 2012 11:44:08 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id q9NIi1NH024195; Tue, 23 Oct 2012 11:44:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1351017845; bh=rmkrTyrpIOJ29NdCH/4fggBfA/Bpz4sND/vgSIpwHEc=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=pX8GTR2c8qLOyxkkw42fjIrf8XlWEha5W3zOn4gKwt8eixfH8/LS6M1Y5Eqy8Ph+e 2xVhPBOWMK9MqNFvgu3+oQz93Y7VTU2OEiWKa331fXR2wwLy2W5AfSCfuKQTjbBaQ1 N8czRu3Po94D2YtHhS9iftvYC1k3lXFI0Z5AIuao=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1351017845; i=@resistor.net; bh=rmkrTyrpIOJ29NdCH/4fggBfA/Bpz4sND/vgSIpwHEc=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=ztexwvvRXsiLnEFjIqMS1wHK9i2UgegRjgWQoRHXRb7QME2XclTUKyGvLUuS69R+V nTVKEDoMU6F1/S8AFISFyjRY1S1P+mIHuDZ04D74Ou+LMwcWQl2XfHfP3rM2t0vDPu MmQ2Hm62qBXm8A7XK+gl7hbdQEFg50M0Utw4S/Us=
Message-Id: <6.2.5.6.2.20121023105638.09612698@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 23 Oct 2012 11:40:24 -0700
To: The IAOC <bob.hinden@gmail.com>
From: SM <sm@resistor.net>
Subject: Re: IAOC Request for community feedback
In-Reply-To: <20121022234941.28301.7687.idtracker@ietfa.amsl.com>
References: <20121022234941.28301.7687.idtracker@ietfa.amsl.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Oct 2012 18:44:09 -0000

At 16:49 22-10-2012, The IAOC wrote:
>The IAOC has reviewed BCP101 and concludes it does not handle this
>case very well. BCP101 says that if "an IAOC member abrogates his or
>her duties" the recall process in BCP10/RFC3777 may be used. The
>specific text is:
>
>    IAOC members are subject to recall in the event that an IAOC member
>    abrogates his or her duties or acts against the best interests of the
>    IETF community. Any appointed IAOC member, including any appointed
>    by the IAB, IESG, or ISOC Board of Trustees, may be recalled using
>    the recall procedure defined in RFC 3777 [RFC3777]. IAOC members are
>    not, however, subject to recall by the bodies that appointed them.
>
>    If a vacancy occurs among the appointed members, this is filled by
>    the appointing body for that position according to its procedures.
>
>The conditions for determining that a vacancy exist are not well-defined.

The above also affects the IETF Trust as the person is the 
Chair.  The mid-term vacancy rules take effect when a sitting member 
is recalled from the open position.  In other words the recall 
procedure can be used to determine the vacancy.  The person was 
appointed by the community represented by NomCom.  It would be 
problematic for the IAOC and IETF chairs to declare the position vacant.

Regards,
-sm



From ogud@ogud.com  Tue Oct 23 11:55:29 2012
Return-Path: <ogud@ogud.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 74D9A1F042A for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 11:55:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.541
X-Spam-Level: 
X-Spam-Status: No, score=-104.541 tagged_above=-999 required=5 tests=[AWL=1.058, BAYES_00=-2.599, GB_I_LETTER=-2, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UU3xA8Ki7OtY for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 11:55:28 -0700 (PDT)
Received: from smtp177.iad.emailsrvr.com (smtp177.iad.emailsrvr.com [207.97.245.177]) by ietfa.amsl.com (Postfix) with ESMTP id 872121F0C59 for <ietf@ietf.org>; Tue, 23 Oct 2012 11:55:28 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp57.relay.iad1a.emailsrvr.com (SMTP Server) with ESMTP id 3B152F9081 for <ietf@ietf.org>; Tue, 23 Oct 2012 14:55:21 -0400 (EDT)
X-Virus-Scanned: OK
Received: by smtp57.relay.iad1a.emailsrvr.com (Authenticated sender: ogud-AT-ogud.com) with ESMTPSA id BBC50F9083 for <ietf@ietf.org>; Tue, 23 Oct 2012 14:55:18 -0400 (EDT)
Message-ID: <5086E815.7060600@ogud.com>
Date: Tue, 23 Oct 2012 14:55:17 -0400
From: Olafur Gudmundsson <ogud@ogud.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121010 Thunderbird/16.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: IAOC Request for community feedback
References: <20121022234941.28301.7687.idtracker@ietfa.amsl.com> <20121023172013.918DC11E8099@ietfa.amsl.com>
In-Reply-To: <20121023172013.918DC11E8099@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
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Oct 2012 18:55:29 -0000

On 23/10/2012 13:16, Michael StJohns wrote:
> Wait just one minute.....
>
>
> Marshal has neither resigned nor died (both of which would vacate the
> position).  He apparently *has* abrogated his responsibilities.
>

In even stronger terms: if a person after many years of involvement and
understanding of the rules, does not take the 5 minutes to write
a letter saying 'I resign from the IOAC', I wonder what triggered that
behavior.

> I'm willing to sign on to the petition.  I'm willing to volunteer for
> the recall committee.
>

Same here.

	Olafur


From mstjohns@comcast.net  Tue Oct 23 12:03:53 2012
Return-Path: <mstjohns@comcast.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E8AA511E80D9 for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 12:03:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.196
X-Spam-Level: 
X-Spam-Status: No, score=-101.196 tagged_above=-999 required=5 tests=[AWL=1.241, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, GB_I_LETTER=-2, HELO_MISMATCH_NET=0.611, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id s7NLVt7GwcbM for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 12:03:53 -0700 (PDT)
Received: from qmta05.westchester.pa.mail.comcast.net (qmta05.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:48]) by ietfa.amsl.com (Postfix) with ESMTP id 48C9F11E80A3 for <ietf@ietf.org>; Tue, 23 Oct 2012 12:03:53 -0700 (PDT)
Received: from omta06.westchester.pa.mail.comcast.net ([76.96.62.51]) by qmta05.westchester.pa.mail.comcast.net with comcast id EcUe1k00516LCl055j3wUG; Tue, 23 Oct 2012 19:03:56 +0000
Received: from Mike-T530.comcast.net ([68.83.222.237]) by omta06.westchester.pa.mail.comcast.net with comcast id Ej3Q1k00b57vnMg3Sj3RYL; Tue, 23 Oct 2012 19:03:25 +0000
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Tue, 23 Oct 2012 15:03:52 -0400
To: jnc@mercury.lcs.mit.edu (Noel Chiappa),ietf@ietf.org
From: Michael StJohns <mstjohns@comcast.net>
Subject: Re: IAOC Request for community feedback
In-Reply-To: <20121023184229.9FCA418C0A4@mercury.lcs.mit.edu>
References: <20121023184229.9FCA418C0A4@mercury.lcs.mit.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Message-Id: <20121023190353.48C9F11E80A3@ietfa.amsl.com>
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: Tue, 23 Oct 2012 19:03:54 -0000

Umm.. no.

When would you consider the office vacant?  Missing one meeting, missing two?  Not calling in for a week, a month, two months?  Etc.  I'm currently in jury duty - and sequestered for a major murder trial?  I'm in the service and on a classified assignment for three months?  Trapped in a hospital for 6 weeks for traction?  On a spiritual retreat that ends when you achieve oneness with the tao of the IETF?  In rehab for 30-90 days for drug or gambling addiction?

We have a process.  The IAOC has made its case.  Let's let the IETF follow its process and do the official thing to declare the office vacant.  After all, its already (only?) been two months.  Another month or less shouldn't hurt that much.

And for that matter, if the recall process is broken for this, it's broken for everything.  So we should use this opportunity to figure out if it's broken, and if it is, figure out how to fix it for everything.  (Seriously, I can think of a couple of AD's that I would have attempted to remove,  if all that were needed were a hum on the list!!!)

As part of this process, the recall committee should send a registered letter notifying Marshall of the recall petition, and requesting Marshall's views on the matter. It may not get any response which is a good datum in and of itself.

Later, Mike


At 02:42 PM 10/23/2012, Noel Chiappa wrote:
>    > From: Michael StJohns <mstjohns@comcast.net>
>
>    >> The IAOC is requesting feedback from the community concerning a
>    >> vacancy that the IAOC feels is not adequately covered by existing IETF
>    >> rules.
>
>    > I'm not sure why the IAOC thinks that the recall procedure shouldn't be
>    > followed.
>
>Because it's a fairly lengthy, complex, and effort-consuming, process to use
>in this kind of case - rather like using a pile-driver to crack a nut?
>
>I hear you, and understand the concern about ignoring established procedures,
>but at the same time, calling for a hum from the IETF community is sufficient
>to get the _entire procedure_ changed, a far more consequential act, so
>asking for a hum to temporarily bypass them seems to me to be acting in the
>general spirit.
>
>And of course we do need to update our procedures so that if this ever
>happens again, we don't face the choice of rolling out the pile-driver, or
>proceeding in an ad hoc way, but that's a separate point.
>
>        Noel



From dougb@dougbarton.us  Tue Oct 23 12:04:31 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 C062321F865E for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 12:04:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.135
X-Spam-Level: 
X-Spam-Status: No, score=-3.135 tagged_above=-999 required=5 tests=[AWL=0.464,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ke6kESH6PS1r for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 12:04:31 -0700 (PDT)
Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by ietfa.amsl.com (Postfix) with ESMTP id 0874921F864A for <ietf@ietf.org>; Tue, 23 Oct 2012 12:04:30 -0700 (PDT)
Received: (qmail 10746 invoked by uid 399); 23 Oct 2012 19:04:13 -0000
Received: from unknown (HELO ?192.168.0.102?) (dougb@dougbarton.us@12.207.105.210) by mail2.fluidhosting.com with ESMTPAM; 23 Oct 2012 19:04:13 -0000
X-Originating-IP: 12.207.105.210
X-Sender: dougb@dougbarton.us
Message-ID: <5086EA38.6020806@dougbarton.us>
Date: Tue, 23 Oct 2012 12:04:24 -0700
From: Doug Barton <dougb@dougbarton.us>
Organization: http://SupersetSolutions.com/
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121010 Thunderbird/16.0.1
MIME-Version: 1.0
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Subject: Re: IAOC Request for community feedback
References: <20121023184229.9FCA418C0A4@mercury.lcs.mit.edu>
In-Reply-To: <20121023184229.9FCA418C0A4@mercury.lcs.mit.edu>
X-Enigmail-Version: 1.4.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: Tue, 23 Oct 2012 19:04:31 -0000

On 10/23/2012 11:42 AM, Noel Chiappa wrote:
>     > From: Michael StJohns <mstjohns@comcast.net>
> 
>     >> The IAOC is requesting feedback from the community concerning a
>     >> vacancy that the IAOC feels is not adequately covered by existing IETF
>     >> rules.
> 
>     > I'm not sure why the IAOC thinks that the recall procedure shouldn't be
>     > followed.
> 
> Because it's a fairly lengthy, complex, and effort-consuming, process to use
> in this kind of case - rather like using a pile-driver to crack a nut?

The procedures are what they are, and the recall procedure provides a
reasonable safeguard against abuse. By not following them you set a
dangerous precedent.

> I hear you, and understand the concern about ignoring established procedures,
> but at the same time, calling for a hum from the IETF community is sufficient
> to get the _entire procedure_ changed, a far more consequential act, so
> asking for a hum to temporarily bypass them seems to me to be acting in the
> general spirit.

I here you, and understand your desire for expedience. But at the same
time, the larger community has already expressed their will in
establishing the procedure we have. It is neither safe, nor appropriate,
to assume that the subset of people humming about this issue overlaps
sufficiently with the subset that hummed about establishing the
procedure to justify this decision.

There is also the risk of how abrogating our own procedures makes us
look to those observing us from the outside.

> And of course we do need to update our procedures so that if this ever
> happens again, we don't face the choice of rolling out the pile-driver, or
> proceeding in an ad hoc way, but that's a separate point.

No, it's a very cogent point, and one that should be pursued by
interested parties who wish to modify the procedure for the next instance.

To put this another way, if you think it is easy to get the hums you
need to abrogate the procedure, it should be just as easy to accomplish
the recall process. And actually doing it will greatly inform those who
wish to improve the procedure for the future.

Doug


From jnc@mercury.lcs.mit.edu  Tue Oct 23 12:06:07 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 1ADC011E80ED for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 12:06:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.129
X-Spam-Level: 
X-Spam-Status: No, score=-6.129 tagged_above=-999 required=5 tests=[AWL=-0.130, BAYES_00=-2.599, J_CHICKENPOX_21=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xqnZIATG2Y0h for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 12:06:06 -0700 (PDT)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id 5386A11E80A4 for <ietf@ietf.org>; Tue, 23 Oct 2012 12:06:06 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id BA48A18C0A4; Tue, 23 Oct 2012 15:06:03 -0400 (EDT)
To: ietf@ietf.org
Subject: Re: IETF HOF vs. ISOC HOF
Message-Id: <20121023190603.BA48A18C0A4@mercury.lcs.mit.edu>
Date: Tue, 23 Oct 2012 15:06:03 -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: Tue, 23 Oct 2012 19:06:07 -0000

{Apologies for the bunched reply - I was offline for a bit, now trying to
catch up without inundating the list.}

    > From: Theodore Ts'o <tytso@mit.edu>

    > Do we need to wait until someone who has made significant contribution
    > to have passed away before we recognize their contributions?
    > ...
    > I wonder if we are conflating the concept of a memorial and a Hall of
    > Fame

This is an excellent point. I guess I just fell into assuming that the IETF
HoF would be for people who have passed away because that was how the whole
discussion started, and I didn't question that initial assumption. But you're
quite right that it would be nice to recognize people while they are still
around to appreciate it.

(I've always been bummed that Van Gogh only sold like 3 paintings while he
was still alive, and so probably never appreciated how good his work was, and
how much it would mean to other people.)


    > From: Dave Crocker <dhc@dcrocker.net>

    > Since ISOC recently initiated its own Hall of Fame effort, how would
    > the IETF version be different and why?

Umm, hard to put into words, but basically the IETF one would be i) for
people who had done things for the IETF (e.g. Steve Coya), or people whom we
felt were important, but whose contributions (and affect on the world as a
whole) didn't rise to the level of the ISOC one (e.g. Abha).


    > From: Lixia Zhang <lixia@cs.ucla.edu>

    > life moves forward fast, history fading away quickly, if we dont make
    > an effort to put it in record.

Exactly.


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

    > a friend suggested privately an article in the ietf journal when
    > someone has died. ... and it is archived.
    > i will not indulge in the swamp of attempting to codify who writes it
    > and how. if the ietf journal editor(s) can not be trusted, replace
    > them.

Agree with both of these (although _very_ significant figures, e.g. Jon,
might merit a full-blown RFC, as Jon did - RFC-2468).

One tweak I would request, though; if someone could set up a web page which is
linked to all the various memorical articles, and put a link to that somewhere
close to the top of the IETF web site, so it would be easy to find/notice,
that would be really useful - short of that, one would have to grub around to
find them all.


    > From: Jari Arkko <jari.arkko@piuha.net>

    > I also think that whoever we at the IETF think is "important" probably
    > wrote enough important RFCs.

Not necessarily. Not everyone important in the IETF writes RFCs...

	Noel

From tobias.gondrom@gondrom.org  Tue Oct 23 12:15:52 2012
Return-Path: <tobias.gondrom@gondrom.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5F61B11E80E9 for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 12:15:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -97.362
X-Spam-Level: 
X-Spam-Status: No, score=-97.362 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_HELO_EQ_D_D_D_D=1.597, FH_HOST_EQ_D_D_D_D=0.765, FM_DDDD_TIMES_2=1.999, GB_I_LETTER=-2, HELO_DYNAMIC_IPADDR=2.426, HELO_EQ_DE=0.35, RDNS_DYNAMIC=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r9NK7sY32j93 for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 12:15:51 -0700 (PDT)
Received: from lvps176-28-13-69.dedicated.hosteurope.de (lvps176-28-13-69.dedicated.hosteurope.de [176.28.13.69]) by ietfa.amsl.com (Postfix) with ESMTP id 0B5BF11E80D9 for <ietf@ietf.org>; Tue, 23 Oct 2012 12:15:50 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1;  q=dns; c=nofws; s=default; d=gondrom.org; b=SiP8I6AHQ1kmLIoeYaWyERAgLVnpcC0op4AexZhwI4R1PwJdG4SfkW5VAoMal6+00uDYOgRte5QA+qRbT3aU9GGAmSd6f6YtO37qv5u2DZtCHJ0L/FBeQFVB70Nr8R5R; h=Received:Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding;
Received: (qmail 26560 invoked from network); 23 Oct 2012 21:15:48 +0200
Received: from unknown (HELO ?10.71.45.180?) (207.238.37.130) by lvps176-28-13-69.dedicated.hosteurope.de with ESMTPSA (DHE-RSA-AES256-SHA encrypted, authenticated); 23 Oct 2012 21:15:48 +0200
Message-ID: <5086ECE2.9010206@gondrom.org>
Date: Tue, 23 Oct 2012 14:15:46 -0500
From: Tobias Gondrom <tobias.gondrom@gondrom.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20121011 Thunderbird/16.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: IAOC Request for community feedback
References: <20121022234941.28301.7687.idtracker@ietfa.amsl.com> <20121023172013.918DC11E8099@ietfa.amsl.com> <5086E815.7060600@ogud.com>
In-Reply-To: <5086E815.7060600@ogud.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Oct 2012 19:15:52 -0000

I would support the call to use our defined recall procedures, even if 
it takes a few weeks longer.
And not unnecessarily set a precedent. If you feel the rules are not 
suitable, than we should think about adjusting them. And be careful, it 
may take "only" a hum to change a procedure, but the discussions 
preceding that hum for a constructive change of such can take quite a 
bit longer. ;-)

However, I would hope and recommend that we could follow the 
communication channel Ray established with a family member of Marshall. 
And maybe we can get a 3 minute time piece from him (or someone 
authorised to speak on his behalf). If he would resign due to the fact 
that he has no time at the moment and for the foreseeable future, 
everything would be settled without trouble.

Best regards, Tobias



On 23/10/12 13:55, Olafur Gudmundsson wrote:
> On 23/10/2012 13:16, Michael StJohns wrote:
>> Wait just one minute.....
>>
>>
>> Marshal has neither resigned nor died (both of which would vacate the
>> position).  He apparently *has* abrogated his responsibilities.
>>
>
> In even stronger terms: if a person after many years of involvement and
> understanding of the rules, does not take the 5 minutes to write
> a letter saying 'I resign from the IOAC', I wonder what triggered that
> behavior.
>
>> I'm willing to sign on to the petition. I'm willing to volunteer for
>> the recall committee.
>>
>
> Same here.
>
>     Olafur
>


From jnc@mercury.lcs.mit.edu  Tue Oct 23 12:21:36 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 71C4611E80FF for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 12:21:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.421
X-Spam-Level: 
X-Spam-Status: No, score=-6.421 tagged_above=-999 required=5 tests=[AWL=0.178,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lQ29+GFBj+wY for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 12:21:36 -0700 (PDT)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id B647611E80FE for <ietf@ietf.org>; Tue, 23 Oct 2012 12:21:35 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 203AC18C0A4; Tue, 23 Oct 2012 15:21:35 -0400 (EDT)
To: ietf@ietf.org
Subject: Re: IAOC Request for community feedback
Message-Id: <20121023192135.203AC18C0A4@mercury.lcs.mit.edu>
Date: Tue, 23 Oct 2012 15:21: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: Tue, 23 Oct 2012 19:21:36 -0000

    > From: Michael StJohns <mstjohns@comcast.net>

    > When would you consider the office vacant?

The complete data on what attempts had been made to communicate with him were
given to us all, so we can all form our own individual opinion as to whether
sufficient conditions had been met.

    > I'm currently in jury duty - and sequestered for a major murder trial?
    > ... Trapped in a hospital for 6 weeks for traction?

In all of these cases one presumably wouldn't vanish without a word of
explanation. It's that, as much as the non-performance, that's an issue.

You know as well as I do that in a normal company, if an employee stopped
showing up for work with no notice, no communication about the situation,
and that went on for months, the person would find themselves terminated.


    > From: Doug Barton <dougb@dougbarton.us>

    > It is neither safe, nor appropriate, to assume that the subset of
    > people humming about this issue overlaps sufficiently with the subset
    > that hummed about establishing the procedure to justify this decision.

What, we can't change a procedure unless the set of people who previously
OK'd it now agree to change it? I don't think so. A hum is a hum is a hum.

	Noel

From dougb@dougbarton.us  Tue Oct 23 12:27:02 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 830291F0C91 for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 12:27:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.228
X-Spam-Level: 
X-Spam-Status: No, score=-3.228 tagged_above=-999 required=5 tests=[AWL=0.371,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CWpHwE+wjX46 for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 12:27:02 -0700 (PDT)
Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by ietfa.amsl.com (Postfix) with ESMTP id CD05B1F042A for <ietf@ietf.org>; Tue, 23 Oct 2012 12:27:01 -0700 (PDT)
Received: (qmail 10580 invoked by uid 399); 23 Oct 2012 19:26:47 -0000
Received: from unknown (HELO ?192.168.0.102?) (dougb@dougbarton.us@12.207.105.210) by mail2.fluidhosting.com with ESMTPAM; 23 Oct 2012 19:26:47 -0000
X-Originating-IP: 12.207.105.210
X-Sender: dougb@dougbarton.us
Message-ID: <5086EF82.9060900@dougbarton.us>
Date: Tue, 23 Oct 2012 12:26:58 -0700
From: Doug Barton <dougb@dougbarton.us>
Organization: http://SupersetSolutions.com/
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121010 Thunderbird/16.0.1
MIME-Version: 1.0
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Subject: Re: IAOC Request for community feedback
References: <20121023192135.203AC18C0A4@mercury.lcs.mit.edu>
In-Reply-To: <20121023192135.203AC18C0A4@mercury.lcs.mit.edu>
X-Enigmail-Version: 1.4.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: Tue, 23 Oct 2012 19:27:02 -0000

On 10/23/2012 12:21 PM, Noel Chiappa wrote:
>     > From: Doug Barton <dougb@dougbarton.us>
> 
>     > It is neither safe, nor appropriate, to assume that the subset of
>     > people humming about this issue overlaps sufficiently with the subset
>     > that hummed about establishing the procedure to justify this decision.
> 
> What, we can't change a procedure unless the set of people who previously
> OK'd it now agree to change it? I don't think so. A hum is a hum is a hum.

You're not proposing a change in procedure. You're proposing to ignore
one. Those are entirely different things.

You've also snipped out the entire portion of my message where I talked
about actually changing the procedure, and why that may actually be a
good thing. I can't tell if you're deliberately trying to confuse the
issue by arguing against a straw-man that I did not actually propose, or
if you just didn't understand what I wrote previously. If the latter I
apologize, and would be happy to clarify if necessary.

Doug

From david.kessens@nsn.com  Tue Oct 23 13:08:28 2012
Return-Path: <david.kessens@nsn.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C996911E810D for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 13:08:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.501
X-Spam-Level: 
X-Spam-Status: No, score=-6.501 tagged_above=-999 required=5 tests=[AWL=0.098,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SodugyyX2oQs for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 13:08:28 -0700 (PDT)
Received: from demumfd002.nsn-inter.net (demumfd002.nsn-inter.net [93.183.12.31]) by ietfa.amsl.com (Postfix) with ESMTP id 0DABB11E810B for <ietf@ietf.org>; Tue, 23 Oct 2012 13:08:27 -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 q9NK8MSH017084 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 23 Oct 2012 22:08:22 +0200
Received: from P ([10.138.52.238]) by demuprx016.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id q9NK8H3g002428; Tue, 23 Oct 2012 22:08:18 +0200
Received: from P (localhost.localdomain [127.0.0.1]) by P (8.14.5/8.14.5) with ESMTP id q9NK8GHq002045; Tue, 23 Oct 2012 13:08:16 -0700
Received: (from david@localhost) by P (8.14.5/8.14.5/Submit) id q9NK8DCt002036; Tue, 23 Oct 2012 13:08:13 -0700
Date: Tue, 23 Oct 2012 13:07:13 -0700
From: David Kessens <david.kessens@nsn.com>
To: Doug Barton <dougb@dougbarton.us>
Subject: Re: IAOC Request for community feedback
Message-ID: <20121023200713.GC1861@nsn.com>
References: <20121023192135.203AC18C0A4@mercury.lcs.mit.edu> <5086EF82.9060900@dougbarton.us>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <5086EF82.9060900@dougbarton.us>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-purgate-type: clean
X-purgate-Ad: Categorized by eleven eXpurgate (R) http://www.eleven.de
X-purgate: clean
X-purgate: This mail is considered clean (visit http://www.eleven.de for further information)
X-purgate-size: 655
X-purgate-ID: 151667::1351022902-00006DFC-F1FB343A/0-0/0-0
Cc: Noel Chiappa <jnc@mercury.lcs.mit.edu>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Oct 2012 20:08:28 -0000

Doug,

On Tue, Oct 23, 2012 at 12:26:58PM -0700, Doug Barton wrote:
> 
> You're not proposing a change in procedure. You're proposing to ignore
> one. 

No procedure is ignored.

BCP 101 does not define the rules for declaring a position vacant. In
absense of such rules, the IAOC decided to consult with the community
whether the community agrees that the position is now vacant.

Another avenue, which is also mentioned in the BCP, that could have been
followed is the recall procedure. However, the IAOC felt that it was not
really intended for a situation where somebody apparently has vacated their
position.

David Kessens
---

From dougb@dougbarton.us  Tue Oct 23 13:20:06 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 DC96E1F0424 for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 13:20:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.29
X-Spam-Level: 
X-Spam-Status: No, score=-3.29 tagged_above=-999 required=5 tests=[AWL=0.310,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NHC7p5PSqZqi for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 13:20:06 -0700 (PDT)
Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by ietfa.amsl.com (Postfix) with ESMTP id 284181F0C93 for <ietf@ietf.org>; Tue, 23 Oct 2012 13:20:06 -0700 (PDT)
Received: (qmail 25111 invoked by uid 399); 23 Oct 2012 20:19:47 -0000
Received: from unknown (HELO ?192.168.0.100?) (dougb@dougbarton.us@12.207.105.210) by mail2.fluidhosting.com with ESMTPAM; 23 Oct 2012 20:19:47 -0000
X-Originating-IP: 12.207.105.210
X-Sender: dougb@dougbarton.us
Message-ID: <5086FBCE.2070503@dougbarton.us>
Date: Tue, 23 Oct 2012 13:19:26 -0700
From: Doug Barton <dougb@dougbarton.us>
Organization: http://SupersetSolutions.com/
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20121011 Thunderbird/16.0.1
MIME-Version: 1.0
To: David Kessens <david.kessens@nsn.com>
Subject: Re: IAOC Request for community feedback
References: <20121023192135.203AC18C0A4@mercury.lcs.mit.edu> <5086EF82.9060900@dougbarton.us> <20121023200713.GC1861@nsn.com>
In-Reply-To: <20121023200713.GC1861@nsn.com>
X-Enigmail-Version: 1.4.5
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: Noel Chiappa <jnc@mercury.lcs.mit.edu>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Oct 2012 20:20:07 -0000

On 10/23/2012 01:07 PM, David Kessens wrote:
> 
> Doug,
> 
> On Tue, Oct 23, 2012 at 12:26:58PM -0700, Doug Barton wrote:
>>
>> You're not proposing a change in procedure. You're proposing to ignore
>> one. 
> 
> No procedure is ignored.

That is a matter of interpretation.

> BCP 101 does not define the rules for declaring a position vacant. In
> absense of such rules, the IAOC decided to consult with the community
> whether the community agrees that the position is now vacant.

While I applaud the IAOC for not acting unilaterally on their beliefs,
what the community (at least parts of it) are saying is that their
belief that the situation is ambiguous is incorrect.

Or, put another way, no; I do not agree that the position is currently
vacant.

> Another avenue, which is also mentioned in the BCP, that could have been
> followed is the recall procedure. However, the IAOC felt that it was not
> really intended for a situation where somebody apparently has vacated their
> position.

It's the "apparently" that is troublesome. With due respect to Marshall
(since I don't know his circumstances) he seems to have become derelict
in his duty, therefore the recall procedure should be initiated. To do
otherwise would be setting a very bad precedent.

You asked for feedback, you have now received a non-trivial number of
responses saying that arbitrarily declaring the position vacant is not
an appropriate action. You have also received volunteers for the recall
process. Rather than spending more time on trying to justify declaring
the position vacant, why not get started on that recall?

Doug


From barryleiba.mailing.lists@gmail.com  Tue Oct 23 14:03: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 88C9111E80A3 for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 14:03:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.103
X-Spam-Level: 
X-Spam-Status: No, score=-104.103 tagged_above=-999 required=5 tests=[AWL=0.873, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, GB_I_LETTER=-2, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dechzXSzH+1m for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 14:03:33 -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 A366611E80FC for <ietf@ietf.org>; Tue, 23 Oct 2012 14:03:32 -0700 (PDT)
Received: by mail-lb0-f172.google.com with SMTP id k13so728198lbo.31 for <ietf@ietf.org>; Tue, 23 Oct 2012 14:03:31 -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=1oj809j4zAJD0mydaxi6IoxNCo/3GBUiMEER9iZNL6A=; b=YzD1kp0//sU0APVJLHVMP/oZYvTFSe8l6O20kqw4DSp2y/1ZzAPvXm3E8XSTshyF/X TLY8jrkae8DBvKnwC3A4JZ6V1EhaWqAwFC+O+bxapld3tJyThQW2RGzeZQQwzsuKwQKQ zUmq+asxcAkyxfQsQp9J7eg3vtL8R0QOJ7tsSeET/NJpH8VXNGs+h+gMVIC4AHzlrhn1 fPlYQBEiyemOXvBzognHMhrq3Bp1BtZiToIAexHKcyrY/442XRahXwgV+Ck8fqxx/CRW Wxl89EXAFYhibvT3QU7Ggbrs5aSQcwLT/OypfqUi4PD/4cmvJ9NfomJX2GwFlUw7n01t ob2Q==
MIME-Version: 1.0
Received: by 10.152.108.197 with SMTP id hm5mr12565338lab.45.1351026211636; Tue, 23 Oct 2012 14:03:31 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.112.99.131 with HTTP; Tue, 23 Oct 2012 14:03:31 -0700 (PDT)
In-Reply-To: <20121023190353.48C9F11E80A3@ietfa.amsl.com>
References: <20121023184229.9FCA418C0A4@mercury.lcs.mit.edu> <20121023190353.48C9F11E80A3@ietfa.amsl.com>
Date: Tue, 23 Oct 2012 17:03:31 -0400
X-Google-Sender-Auth: fnH4GR0dbT_mG4aVH4TWbRlOk-g
Message-ID: <CAC4RtVBfgsb+Fdts3YXYn1FMpt-HUZTBsQjcYqfxt2tYDJTnkA@mail.gmail.com>
Subject: Re: IAOC Request for community feedback
From: Barry Leiba <barryleiba@computer.org>
To: Michael StJohns <mstjohns@comcast.net>
Content-Type: multipart/alternative; boundary=bcaec54fbd3a6d46ee04ccc04dc2
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, 23 Oct 2012 21:03:33 -0000

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

Mike has convinced me that we should be following the recall process.  So I
will change my initial "Yes," to a "No; we have to follow the process we've
set up.  Do a recall."

Barry

On Tuesday, October 23, 2012, Michael StJohns wrote:

> Umm.. no.
>
> When would you consider the office vacant?  Missing one meeting, missing
> two?  Not calling in for a week, a month, two months?  Etc.  I'm currently
> in jury duty - and sequestered for a major murder trial?  I'm in the
> service and on a classified assignment for three months?  Trapped in a
> hospital for 6 weeks for traction?  On a spiritual retreat that ends when
> you achieve oneness with the tao of the IETF?  In rehab for 30-90 days for
> drug or gambling addiction?
>
> We have a process.  The IAOC has made its case.  Let's let the IETF follow
> its process and do the official thing to declare the office vacant.  After
> all, its already (only?) been two months.  Another month or less shouldn't
> hurt that much.
>
> And for that matter, if the recall process is broken for this, it's broken
> for everything.  So we should use this opportunity to figure out if it's
> broken, and if it is, figure out how to fix it for everything.  (Seriously,
> I can think of a couple of AD's that I would have attempted to remove,  if
> all that were needed were a hum on the list!!!)
>
> As part of this process, the recall committee should send a registered
> letter notifying Marshall of the recall petition, and requesting Marshall's
> views on the matter. It may not get any response which is a good datum in
> and of itself.
>
> Later, Mike
>

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

Mike has convinced me that we should be following the recall process. =A0So=
 I will change my initial &quot;Yes,&quot; to a &quot;No; we have to follow=
 the process we&#39;ve set up. =A0Do a recall.&quot;<div><br></div><div>Bar=
ry<span></span><br>
<br>On Tuesday, October 23, 2012, Michael StJohns  wrote:<br><blockquote cl=
ass=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;p=
adding-left:1ex">Umm.. no.<br>
<br>
When would you consider the office vacant? =A0Missing one meeting, missing =
two? =A0Not calling in for a week, a month, two months? =A0Etc. =A0I&#39;m =
currently in jury duty - and sequestered for a major murder trial? =A0I&#39=
;m in the service and on a classified assignment for three months? =A0Trapp=
ed in a hospital for 6 weeks for traction? =A0On a spiritual retreat that e=
nds when you achieve oneness with the tao of the IETF? =A0In rehab for 30-9=
0 days for drug or gambling addiction?<br>

<br>
We have a process. =A0The IAOC has made its case. =A0Let&#39;s let the IETF=
 follow its process and do the official thing to declare the office vacant.=
 =A0After all, its already (only?) been two months. =A0Another month or les=
s shouldn&#39;t hurt that much.<br>

<br>
And for that matter, if the recall process is broken for this, it&#39;s bro=
ken for everything. =A0So we should use this opportunity to figure out if i=
t&#39;s broken, and if it is, figure out how to fix it for everything. =A0(=
Seriously, I can think of a couple of AD&#39;s that I would have attempted =
to remove, =A0if all that were needed were a hum on the list!!!)<br>

<br>
As part of this process, the recall committee should send a registered lett=
er notifying Marshall of the recall petition, and requesting Marshall&#39;s=
 views on the matter. It may not get any response which is a good datum in =
and of itself.<br>

<br>
Later, Mike<br>
</blockquote></div>

--bcaec54fbd3a6d46ee04ccc04dc2--

From jnc@mercury.lcs.mit.edu  Tue Oct 23 14:11:32 2012
Return-Path: <jnc@mercury.lcs.mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E0B1211E80DC for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 14:11:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.431
X-Spam-Level: 
X-Spam-Status: No, score=-6.431 tagged_above=-999 required=5 tests=[AWL=0.168,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CRXlfP8HWdSq for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 14:11:32 -0700 (PDT)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id 4156D11E80BF for <ietf@ietf.org>; Tue, 23 Oct 2012 14:11:31 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 773D018C0A0; Tue, 23 Oct 2012 17:11:28 -0400 (EDT)
To: ietf@ietf.org
Subject: Re: IAOC Request for community feedback
Message-Id: <20121023211128.773D018C0A0@mercury.lcs.mit.edu>
Date: Tue, 23 Oct 2012 17:11:28 -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: Tue, 23 Oct 2012 21:11:33 -0000

    > From: Doug Barton <dougb@dougbarton.us>

    > You've also snipped out the entire portion of my message where I talked
    > about actually changing the procedure

I happened to see one point I wanted to say something about (the 'hum group'
thingy), that's all.


And now that I've thought about this whole thing a bit more, I think Mike may
have put his finger on the key point: just what is enough to consider the
office vacant? His list of scenarios points out (implicitly) that we're
probably going to have a very hard time codifying that, without wasting
endless hours discussing and word-smithing.

That being the case, probably the much easier, simpler and better formal
procedure to set up, for use in these rare cases, is to put the facts of the
particular case before the community, and let them decide if the actions in
the particular case count as 'leaving the office vacant'.

Which is, by an odd coincidence, just what's been done here.


    > you have now received a non-trivial number of responses saying that
    > arbitrarily declaring the position vacant is not an appropriate action.

And considerably more saying it is.

Look, using the full-blown recall process here is really disproportionate.
That complex, lengthy process is appropriate for places where one is unhappy
with what an office-holder is doing. It's a wholly different situation when
someone's has effectively resigned by going incommunicado for months.

I would like to point out that the United States Government is also happy to
use very different mechanisms for the two cases: for removal of an
officeholder over what they have done, the lengthy, complex, impeachment and
trial process is specified. For someone who's just plain incapacitated, a
much simpler process (a simple majority of the Cabinet) can act.


    > From: Tobias Gondrom <tobias.gondrom@gondrom.org>

    > And maybe we can get a 3 minute time piece from him (or someone
    > authorised to speak on his behalf). If he would resign due to the fact
    > that he has no time at the moment and for the foreseeable future,
    > everything would be settled without trouble.

Now, that's by some distance the best suggestion I've heard yet.

Can Ray (or whomever) contact that person they are in touch with, and pass in
a message asking him if he wouldn't mind just formally quitting, so we don't
have to waste inordinate amounts of time and energy either i) doing the
recall thing, or ii) debating whether we need to do the full-blown recall or
not?

	Noel

From john@jlc.net  Tue Oct 23 14:32:52 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 1C14811E80DC for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 14:32:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.449
X-Spam-Level: 
X-Spam-Status: No, score=-106.449 tagged_above=-999 required=5 tests=[AWL=0.150, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DFQRS+PSn00i for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 14:32:51 -0700 (PDT)
Received: from mailhost.jlc.net (mailhost.jlc.net [199.201.159.4]) by ietfa.amsl.com (Postfix) with ESMTP id 8E47E11E80D9 for <ietf@ietf.org>; Tue, 23 Oct 2012 14:32:51 -0700 (PDT)
Received: by mailhost.jlc.net (Postfix, from userid 104) id 8B42233C23; Tue, 23 Oct 2012 17:32:51 -0400 (EDT)
Date: Tue, 23 Oct 2012 17:32:51 -0400
From: John Leslie <john@jlc.net>
To: Doug Barton <dougb@dougbarton.us>
Subject: Re: IAOC Request for community feedback
Message-ID: <20121023213251.GF27557@verdi>
References: <20121023192135.203AC18C0A4@mercury.lcs.mit.edu> <5086EF82.9060900@dougbarton.us> <20121023200713.GC1861@nsn.com> <5086FBCE.2070503@dougbarton.us>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <5086FBCE.2070503@dougbarton.us>
User-Agent: Mutt/1.4.1i
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Oct 2012 21:32:52 -0000

Doug Barton <dougb@dougbarton.us> wrote:
> 
> You asked for feedback, you have now received a non-trivial number of
> responses saying that arbitrarily declaring the position vacant is not
> an appropriate action. You have also received volunteers for the recall
> process. Rather than spending more time on trying to justify declaring
> the position vacant, why not get started on that recall?

   I strongly urge folks who think as Doug does to _read_ RFC 3777.

   Note that the recall process can only start with 20 "members of the
IETF community, who are qualified to be voting members of a nominating
committee" petitioning to the Internet Society President.

   If that happens, the recall process will start; if not, it won't.

   If the process starts, the Secretariat must go through the process
for selecting a nominating committee (separate from "the" nominating
committee) excluding the petitioners above. Presumably liaisons also
need to be selected. This process won't be "quick".

   BCP 101, IMHO, does allow for a vacancy to "occur" by other means
than recall, though it certainly doesn't try to specify these. Perhaps
it needs to be updated to cover vacancy by abandonment...

   I can but suggest that the nominating committee be asked to select
a replacement _promptly_ while we see whether a recall is started
and discuss the proper update to BCP 101. If that replacement is
selected before the issue is "resolved", the person could participate
"informally" without vote until there is some resolution.

   Myself, I don't expect to petition or volunteer to serve on a
recall committee. The recall process isn't intended to be "practical",
IMHO, and seems intended only to prod the subject of recall to resign.
In other organizations, I have lived through longish periods of
uncertainty about the exact status of an individual, and I no longer
find it scary.

--
John Leslie <john@jlc.net>

From bob.hinden@gmail.com  Tue Oct 23 14:33:25 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 676B911E80F3 for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 14:33:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.597
X-Spam-Level: 
X-Spam-Status: No, score=-103.597 tagged_above=-999 required=5 tests=[AWL=0.002, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1h96KF+TxhyY for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 14:33:24 -0700 (PDT)
Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id ACFDF11E80D9 for <ietf@ietf.org>; Tue, 23 Oct 2012 14:33:24 -0700 (PDT)
Received: by mail-pb0-f44.google.com with SMTP id ro8so740380pbb.31 for <ietf@ietf.org>; Tue, 23 Oct 2012 14:33:24 -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=SICseEC1100babJpG5oHAViO31gbl4mqqXPuJiwWATI=; b=bSHatyhzmTiowNxVkOnKJ5JUoviWr01UbvOugf1xOeuHlUSjVJMLxCIb13hrUFf0N5 J+RNYV7sBRhQk7MzbHcWYeoC6cimX/AjNZfq9sY0hwNtMYrdZCAPipRcmgnJ2wOD/yhD jqB3qxzCpeyxpux7L3+2Y7no9PDhwzoG1Iic35VA7AOWZklk3SC2FcOe6knZE6CgJOQr nDKOa9UCMVyBDmbmKhYwUJ1Y9xmyIOc74GmusLuto5+TeNqLmb8wvSnQTWKBdY8APrms IO+RY603WL8TpIt0Qd62lB+XmcEvVKsqzIPHlPRmYk9qzi0OsJlQJdu0QMSQxR/YcSgg ldfA==
Received: by 10.68.115.75 with SMTP id jm11mr43876045pbb.28.1351028004499; Tue, 23 Oct 2012 14:33:24 -0700 (PDT)
Received: from [172.16.224.219] ([209.97.127.34]) by mx.google.com with ESMTPS id yi9sm8269538pbc.39.2012.10.23.14.33.22 (version=SSLv3 cipher=OTHER); Tue, 23 Oct 2012 14:33:23 -0700 (PDT)
Subject: Re: IAOC Request for community feedback
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=us-ascii
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <20121023211128.773D018C0A0@mercury.lcs.mit.edu>
Date: Tue, 23 Oct 2012 14:33:21 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <1FB012B6-672D-47DD-92A5-81084E833136@gmail.com>
References: <20121023211128.773D018C0A0@mercury.lcs.mit.edu>
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
X-Mailer: Apple Mail (2.1283)
Cc: Bob Hinden <bob.hinden@gmail.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Oct 2012 21:33:25 -0000

Noel,

>=20
>> From: Tobias Gondrom <tobias.gondrom@gondrom.org>
>=20
>> And maybe we can get a 3 minute time piece from him (or someone
>> authorised to speak on his behalf). If he would resign due to the =
fact
>> that he has no time at the moment and for the foreseeable future,
>> everything would be settled without trouble.
>=20
> Now, that's by some distance the best suggestion I've heard yet.
>=20
> Can Ray (or whomever) contact that person they are in touch with, and =
pass in
> a message asking him if he wouldn't mind just formally quitting, so we =
don't
> have to waste inordinate amounts of time and energy either i) doing =
the
> recall thing, or ii) debating whether we need to do the full-blown =
recall or
> not?

We have been trying to do that for the past month.  No one we have =
talked to has been able to talk to him.  For example, Marshall was =
active in Lift Port (http://liftport.com) where Marshall is listed as =
their CTO.  I contacted them and they have not been able to reach him.

Bob


From paul.hoffman@vpnc.org  Tue Oct 23 14:55:43 2012
Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A93C91F0C96 for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 14:55:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bWSjKZ39nniC for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 14:55:42 -0700 (PDT)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id 9D0E51F0C92 for <ietf@ietf.org>; Tue, 23 Oct 2012 14:55:37 -0700 (PDT)
Received: from [165.227.249.210] (sn81.proper.com [75.101.18.81]) (authenticated bits=0) by hoffman.proper.com (8.14.5/8.14.5) with ESMTP id q9NLtUs0069896 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 23 Oct 2012 14:55:32 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: IAOC Request for community feedback
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <20121023172013.918DC11E8099@ietfa.amsl.com>
Date: Tue, 23 Oct 2012 14:55:31 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <C1A50EDF-60C0-41EC-9F2D-15EAE495B352@vpnc.org>
References: <20121022234941.28301.7687.idtracker@ietfa.amsl.com> <20121023172013.918DC11E8099@ietfa.amsl.com>
To: Michael StJohns <mstjohns@comcast.net>
X-Mailer: Apple Mail (2.1499)
Cc: The IAOC <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: Tue, 23 Oct 2012 21:55:43 -0000

On Oct 23, 2012, at 10:16 AM, Michael StJohns <mstjohns@comcast.net> =
wrote:

> Wait just one minute.....
>=20
>=20
> Marshal has neither resigned nor died (both of which would vacate the =
position). =20

I don't see anything in BCP 10 that says those are the only to ways to =
vacate a position. Those two are obvious possibilities, but "went away =
and actively refused to respond to queries" seems like a reasonable one =
as well.

> He apparently *has* abrogated his responsibilities.
>=20
> I'm not sure why the IAOC thinks that the recall procedure shouldn't =
be followed.

Isn't it obvious? Given a choice of the two procedures, and given that =
Nomcom is already choosing an IAOC member, declaring the seat vacant is =
way easier.

> Get a petition signed.  Run a 1 week call for volunteers. Do the  =
recall committee selection prior to the IETF, present your case to the =
recall committee at the IETF and stand back and let them do the work.
>=20
> I appreciate the pain of having a member go AWOL, but I see no basis =
for declaring the position vacant based on current practice.

Ummmm, what current practice are you referring to? Has something like =
this happened in the past decade or two?

> I would consider that your email constitutes evidence that the IAOC =
has asked for a recall petition to be circulated.  I would consider that =
the list of grievances you've posted constitutes sufficient grounds for =
the petition. =20

That's an interesting reading, given that what the email says is "we =
consider the seat vacant".

> I would estimate that you have sufficient support for the petition to =
be confirmed, but I don't see anything so critical that would suggest =
that the recall process need not be followed.
>=20
> I'm willing to sign on to the petition.  I'm willing to volunteer for =
the recall committee.

I'm willing to let the IAOC define the seat vacant, because it clearly =
is, and there is no specific definition of "vacant" that disagrees with =
the logical conclusion.

--Paul Hoffman=

From ted.ietf@gmail.com  Tue Oct 23 15:02:29 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 5DCB21F0C96 for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 15:02:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.466
X-Spam-Level: 
X-Spam-Status: No, score=-3.466 tagged_above=-999 required=5 tests=[AWL=0.003,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, SARE_RMML_Stock10=0.13]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lfl1SLcanyfW for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 15:02:28 -0700 (PDT)
Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id AC1BA1F0C92 for <ietf@ietf.org>; Tue, 23 Oct 2012 15:02:28 -0700 (PDT)
Received: by mail-vb0-f44.google.com with SMTP id fc26so5285518vbb.31 for <ietf@ietf.org>; Tue, 23 Oct 2012 15:02: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; bh=yHXluHJ4DZuAXq1ZHGfrC1huES5YKGc73dGWzjgC/lU=; b=PHe4/+kcWfkb53YEosCzuA8mijTDLSHei20HgpOlOVwO7hIwKOnre2U7s11oZ/o4EG 80CZs3nfQHG7pJp54lE/xbHmnQr5pJdvOX387TZsaAFvEg2ws4A1OWs9Xs7M7eHPNw0q 16d7YfAbgITuftKFYdMJJCHURCUa+PQHzshsS5I5CYAaNrRM0COhWZQLlx/J0hZsf4DQ 3DqCCpxPL0AdDKGM25+ZcPMy26Bzg0xIXG4Eh4F2DHPvqFi0u1NhAiIpj8ZHCDG7fn9z 1sG0KwS2595AbuM+tGGTaDuj9iky6mGCV/OwLqCEnksBUCWFyKd7+IKoxLq5aom4Wtwa Dthw==
MIME-Version: 1.0
Received: by 10.220.220.7 with SMTP id hw7mr4682544vcb.17.1351029747844; Tue, 23 Oct 2012 15:02:27 -0700 (PDT)
Received: by 10.58.245.39 with HTTP; Tue, 23 Oct 2012 15:02:27 -0700 (PDT)
In-Reply-To: <Pine.LNX.4.64.1210232115210.2471@ps20323.dreamhostps.com>
References: <50604C1A.7090901@gmx.de> <5060A964.5060001@stpeter.im> <Pine.LNX.4.64.1210172354500.2478@ps20323.dreamhostps.com> <507F5A7E.6040206@arcanedomain.com> <50856E3C.103@gmail.com> <Pine.LNX.4.64.1210221753010.2471@ps20323.dreamhostps.com> <0DBC8A11-319C-4120-975E-7E40FD5818BF@gbiv.com> <Pine.LNX.4.64.1210222137530.2471@ps20323.dreamhostps.com> <CA+9kkMDpEZCvcG1DJd=O1qPNV+=+GTBeN+CGndUe51Xym_A9sg@mail.gmail.com> <Pine.LNX.4.64.1210232115210.2471@ps20323.dreamhostps.com>
Date: Tue, 23 Oct 2012 15:02:27 -0700
Message-ID: <CA+9kkMBg=hxz=yRYfYA5Hkwp-4ODFBnpK_qctCMB_oEHLPP49g@mail.gmail.com>
Subject: Re: [whatwg] New URL Standard from Anne van Kesteren on 2012-09-24 (public-whatwg-archive@w3.org from September 2012)
From: Ted Hardie <ted.ietf@gmail.com>
To: Ian Hickson <ian@hixie.ch>
Content-Type: text/plain; charset=ISO-8859-1
Cc: URI <uri@w3.org>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Oct 2012 22:02:29 -0000

On Tue, Oct 23, 2012 at 2:34 PM, Ian Hickson <ian@hixie.ch> wrote:
>> If you choose not call what you're doing a "URL" but by some other
>> term ("fleen" is my favorite), then the issue does not arise
>
> Since the IETF doesn't call it a URL anyway, I don't see the problem with
> terminology.
>

Please see RFC 3986, Section 1.1.3, which says:

   "A URI can be further classified as a locator, a name, or both.  The
   term "Uniform Resource Locator" (URL) refers to the subset of URIs
   that, in addition to identifying a resource, provide a means of
   locating the resource by describing its primary access mechanism
   (e.g., its network "location").  The term "Uniform Resource Name"
   (URN) has been used historically to refer to both URIs under the
   "urn" scheme [RFC2141], which are required to remain globally unique
   and persistent even when the resource ceases to exist or becomes
   unavailable, and to any other URI with the properties of a name."

While the document does recommend the use of the more generic term
"URI" it defines URL clearly and in a way that is significantly
different from that used in Anne's document and which you have
described as the aim of your work.

Note also that Anne's document contains this text:

"Align RFC 3986 and RFC 3987 with contemporary implementations and
obsolete them in the process."

Unless you get buy-in from the community that produced RFC 3986 and
RFC 3987, the production of this document *will* result in a fork, and
that is damaging to the Internet.  I urge you to pick a different term
(several far more useful ones than fleen have been suggested) and
avoid this needless conflict.  The WhatWG choosing to redefine IETF
standards is not contributing to a better web; it's simply making it
less clear for those outside the small cabal of standards workers what
they should do when faced with a URL.  Un-marked context shifts are
likely, and likely to be bad.  Avoiding them by picking a new term is
both easy and appropriate.

My personal opinion, as always,

regards,

Ted Hardie

From henk.uijterwaal@gmail.com  Tue Oct 23 15:05:40 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 339011F0C9A for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 15:05:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.555
X-Spam-Level: 
X-Spam-Status: No, score=-3.555 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, DATE_IN_PAST_03_06=0.044, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gOl7ebB2CrLu for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 15:05:39 -0700 (PDT)
Received: from mail-ea0-f172.google.com (mail-ea0-f172.google.com [209.85.215.172]) by ietfa.amsl.com (Postfix) with ESMTP id A10761F0424 for <ietf@ietf.org>; Tue, 23 Oct 2012 15:05:38 -0700 (PDT)
Received: by mail-ea0-f172.google.com with SMTP id k13so1538196eaa.31 for <ietf@ietf.org>; Tue, 23 Oct 2012 15:05:37 -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=XfM4rBDYgVsdPfiyRWqJxXrRtm966vdKbYtb+ASqpBo=; b=SLz4i6Gv+avm8q386YaorvATLPmsp0G4zcR7YtV6Hv16xQD6V316MBrysXOtToai7w rAXwKiVu0VIzG2NJYJgwLRuQ4YD1UzR/VsEAbcv8+Fg56muw+bBY0pugWOPKicTD9VNM 0ZMy5NfmJtWsHDs71OAcoGuZiasVFsLJ69Ah7It6ODDd5XZxkz6wR8eTdTMDTrmEwZV1 /J5/td4dc1MqEBzw2dgMINYdBVoxgr81GddJOqGh8kXaSIncsiAiO3LW34CB7b0xywAY 6ATczI9vVhw/+ZgHRtE/1AkRZ8nqoFTSJQx5NoJXLe84nMwPvn2EJzzOYSQqPWcBmamd U/cg==
Received: by 10.14.173.67 with SMTP id u43mr18959070eel.27.1351029937802; Tue, 23 Oct 2012 15:05:37 -0700 (PDT)
Received: from geir.local (thuis.uijterwaal.nl. [82.95.178.49]) by mx.google.com with ESMTPS id t7sm22980789eel.14.2012.10.23.15.05.35 (version=SSLv3 cipher=OTHER); Tue, 23 Oct 2012 15:05:36 -0700 (PDT)
Message-ID: <5086C15B.10404@gmail.com>
Date: Tue, 23 Oct 2012 18:10:03 +0200
From: Henk Uijterwaal <henk.uijterwaal@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:16.0) Gecko/20121010 Thunderbird/16.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: IAOC Request for community feedback
References: <20121022234941.28301.7687.idtracker@ietfa.amsl.com> <0f6301cdb113$2aab5960$80020c20$@olddog.co.uk> <CAOnoajw+Xk+c6qRFa_cZDD3_Vx9F3VEMVCuXNH5jRZUjODvXrg@mail.gmail.com> <82515288-B3D9-43AB-A863-528C019FA69C@isoc.org> <5086A338.8070101@piuha.net> <5086A3B7.7060208@cs.tcd.ie>
In-Reply-To: <5086A3B7.7060208@cs.tcd.ie>
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: Tue, 23 Oct 2012 22:05:40 -0000

>>>>> The IAOC is requesting feedback from the community whether it is
>>>>> reasonable to declare Marshall's IAOC position vacant.
>>>> Yes.
>>> +1

I agree.


>> Ray Pelletier wrote:
>>
>>>  Marshall was focused on other activities
>>
>> That's good to hear. I was worried about him when I read the mail from
>> Bob. And yes, this can happen with people. Dayjobs or businesses or
>> personal issues can sometimes cause this. Lets welcome him back to the
>> IETF when he finishes his other business.

Good to hear that he is (at least) still alive.

Henk



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

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

From ben@nostrum.com  Tue Oct 23 15:06:14 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 CBDA01F0424; Tue, 23 Oct 2012 15:06:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.59
X-Spam-Level: 
X-Spam-Status: No, score=-102.59 tagged_above=-999 required=5 tests=[AWL=0.010, BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 05MVDloJu4zb; Tue, 23 Oct 2012 15:06:14 -0700 (PDT)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id BFDD81F0C9C; Tue, 23 Oct 2012 15:06:13 -0700 (PDT)
Received: from [10.0.1.12] (cpe-76-187-92-156.tx.res.rr.com [76.187.92.156]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id q9NM6CPt051092 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 23 Oct 2012 17:06:13 -0500 (CDT) (envelope-from ben@nostrum.com)
From: Ben Campbell <ben@nostrum.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Subject: Gen-ART LC Review of draft-leiba-extended-doc-shepherd-00
Date: Tue, 23 Oct 2012 17:06:15 -0500
Message-Id: <5D777775-C4B8-4AEF-A445-D38EF47B0AD1@nostrum.com>
To: draft-leiba-extended-doc-shepherd-all@tools.ietf.org
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
X-Mailer: Apple Mail (2.1499)
Received-SPF: pass (nostrum.com: 76.187.92.156 is authenticated by a trusted mechanism)
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, "ietf@ietf.org List" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Oct 2012 22:06:15 -0000

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at

<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

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

Document:  draft-leiba-extended-doc-shepherd-00

Reviewer: Ben Campbell
Review Date: 2012-10-23
IETF LC End Date: 2012-10-23

Summary: I'm not sure what to make of this draft. I think the opinions =
herein are worth capturing, but have mixed feelings about it belong in =
an informational RFC.

Major issues:

-- Process: I share some of the concerns that have been mentioned by =
others, namely that I'm not sure whether an individual opinion paper =
should be published as an informational RFC. OTOH, I'm not sure that it =
shouldn't. The operative words here are "I'm not sure." The opinions =
contained in the document are interesting, and likely of use to the =
community. I just wonder if another publication form might not be more =
appropriate.

-- Content: It's hard to disagree with most of the activities in =
general, but it seems to me that much of the pre pubreq processes here =
are just things that Chairs should be doing anyway. I guess it doesn't =
hurt to call all of that "shepherding", but I don't think it's the same =
thing as "having a shepherd" in the PROTO sense.  I see the potential =
value of having continuity of responsibility throughout the entire =
process, but I also see value in the flexibility of deferring the =
shepherd selection until time for the proto writeup. (I recognize that =
you don't necessarily expect the same person to shepherd all phases--but =
if I read correctly you also seem to indicate a preference that they do =
so.)

Minor issues:

-- section 1, 4th paragraph: "It adds to what=92s in RFC 4858, intending =
to extend it, not replace it."

Do you intend this to formally update 4858? It doesn't seem like it from =
the rest of the text, but one might infer otherwise from this sentence.

-- section 4, 2nd paragraph: "... What it all boils down to is setting =
up one person who takes responsibility for following the progress of a =
document from Call for Adoption through Publication ..."

The text offers examples of changing the responsible person during the =
process, but also mentions the advantages of continuity. If continuity =
is the real goal, then are the examples that show the role changing over =
the life of the draft are counterproductive?


Nits/editorial comments:

None.=

From ben@nostrum.com  Tue Oct 23 15:07:48 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 1FC6B1F0C96; Tue, 23 Oct 2012 15:07:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.59
X-Spam-Level: 
X-Spam-Status: No, score=-102.59 tagged_above=-999 required=5 tests=[AWL=0.010, BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2NxH8WFEovrg; Tue, 23 Oct 2012 15:07:48 -0700 (PDT)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 753821F0424; Tue, 23 Oct 2012 15:07:45 -0700 (PDT)
Received: from [10.0.1.12] (cpe-76-187-92-156.tx.res.rr.com [76.187.92.156]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id q9NM7heR051231 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 23 Oct 2012 17:07:43 -0500 (CDT) (envelope-from ben@nostrum.com)
From: Ben Campbell <ben@nostrum.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Subject: Gen-ART LC Review of draft-leiba-extended-doc-shepherd-00
Date: Tue, 23 Oct 2012 17:07:45 -0500
Message-Id: <8414B0C3-C97E-4A1A-8F21-6387E85C8D84@nostrum.com>
To: draft-leiba-extended-doc-shepherd.all@tools.ietf.org
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
X-Mailer: Apple Mail (2.1499)
Received-SPF: pass (nostrum.com: 76.187.92.156 is authenticated by a trusted mechanism)
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, "ietf@ietf.org List" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Oct 2012 22:07:48 -0000

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at

<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

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

Document:  draft-leiba-extended-doc-shepherd-00

Reviewer: Ben Campbell
Review Date: 2012-10-23
IETF LC End Date: 2012-10-23

Summary: I'm not sure what to make of this draft. I think the opinions =
herein are worth capturing, but have mixed feelings about it belong in =
an informational RFC.

Major issues:

-- Process: I share some of the concerns that have been mentioned by =
others, namely that I'm not sure whether an individual opinion paper =
should be published as an informational RFC. OTOH, I'm not sure that it =
shouldn't. The operative words here are "I'm not sure." The opinions =
contained in the document are interesting, and likely of use to the =
community. I just wonder if another publication form might not be more =
appropriate.

-- Content: It's hard to disagree with most of the activities in =
general, but it seems to me that much of the pre pubreq processes here =
are just things that Chairs should be doing anyway. I guess it doesn't =
hurt to call all of that "shepherding", but I don't think it's the same =
thing as "having a shepherd" in the PROTO sense.  I see the potential =
value of having continuity of responsibility throughout the entire =
process, but I also see value in the flexibility of deferring the =
shepherd selection until time for the proto writeup. (I recognize that =
you don't necessarily expect the same person to shepherd all phases--but =
if I read correctly you also seem to indicate a preference that they do =
so.)

Minor issues:

-- section 1, 4th paragraph: "It adds to what=92s in RFC 4858, intending =
to extend it, not replace it."

Do you intend this to formally update 4858? It doesn't seem like it from =
the rest of the text, but one might infer otherwise from this sentence.

-- section 4, 2nd paragraph: "... What it all boils down to is setting =
up one person who takes responsibility for following the progress of a =
document from Call for Adoption through Publication ..."

The text offers examples of changing the responsible person during the =
process, but also mentions the advantages of continuity. If continuity =
is the real goal, then are the examples that show the role changing over =
the life of the draft are counterproductive?


Nits/editorial comments:

None.=

From hallam@gmail.com  Tue Oct 23 15:11:15 2012
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1CBD01F0C92; Tue, 23 Oct 2012 15:11:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.887
X-Spam-Level: 
X-Spam-Status: No, score=-3.887 tagged_above=-999 required=5 tests=[AWL=-0.289, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H6i4jRolwCm8; Tue, 23 Oct 2012 15:11:14 -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 2810A21F8470; Tue, 23 Oct 2012 15:11:14 -0700 (PDT)
Received: by mail-ob0-f172.google.com with SMTP id v19so4749782obq.31 for <multiple recipients>; Tue, 23 Oct 2012 15:11: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=teF6+M7MQmH8nqvXlOW5WLkpAt291DxwbdwKzC55trI=; b=OKqwTUE3VJ0sWPGGyLCPWKq5gu/1jsyjgb0y9VAbjFhHVMs3WLq/E68kbkq1Yfpouk bXZQHGACWPc2BauhuvW+y+swdtU19r+Pt4uuifPE3Sl2j9qpxycDl9ijTraCr9x9RMXf 7gQiQC7zZn8RLVWUFM3ipSQZT/Kht2nh2V/JjUmNuXzVS7s7793uwbsEMNSLfCKn6t0g Z5iyTycNSd5qKnaO3vqgu7VwhRKGW4WOOdPtZCGO4Qi0T9cpg6xGIy8XfoUs3xz6Qhgt siNkBSHu7bt5Ga/Hhb8I/NC8oIJArLq+sO5cG4LmNwKpJdpiJFD3yeKNqnPCWU2pRe+L Bs5A==
MIME-Version: 1.0
Received: by 10.60.31.135 with SMTP id a7mr12047642oei.26.1351030273774; Tue, 23 Oct 2012 15:11:13 -0700 (PDT)
Received: by 10.76.27.103 with HTTP; Tue, 23 Oct 2012 15:11:13 -0700 (PDT)
Date: Tue, 23 Oct 2012 18:11:13 -0400
Message-ID: <CAMm+Lwj75TJ3OttfMOqZ=dkMQZFe1PAZTXG=+KoGwp6M87TG9g@mail.gmail.com>
Subject: draft-ietf-softwire-stateless-4v6-motivation-04
From: Phillip Hallam-Baker <hallam@gmail.com>
To: secdir@ietf.org, IETF Discussion Mailing List <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=e89a8fb1f59a8c942f04ccc13f08
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Oct 2012 22:11:15 -0000

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

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

The draft is a discussion of the reasons why a stateless solution to
mapping IPv4 addresses to IPv6 is desirable. As such the security
considerations are probably best dealt with in the manner that the document
addresses them, pointing out that a stateless approach has the advantage of
not having state.

While the draft might have been a little easier to follow if it was a
little more concrete, for example how is the statelessness to be achieved
and what are the costs of this approach (which must presumably exist or
else why use a statefull mapping), this will have to be addressed in any
implementation draft.


-- 
Website: http://hallambaker.com/

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

<span style=3D"color:rgb(34,34,34);font-family:arial,sans-serif;font-size:1=
2.800000190734863px;background-color:rgb(255,255,255)">I have reviewed this=
 document as part of the security directorate&#39;s ongoing effort to revie=
w all IETF documents being processed by the IESG. =A0These comments were wr=
itten primarily for the benefit of the security area directors. =A0Document=
 editors and WG chairs should treat these comments just like any other last=
 call comments.</span><br style=3D"color:rgb(34,34,34);font-family:arial,sa=
ns-serif;font-size:12.800000190734863px;background-color:rgb(255,255,255)">
<div><br></div><div>The draft is a discussion of the reasons why a stateles=
s solution to mapping IPv4 addresses to IPv6 is desirable. As such the secu=
rity considerations are probably best dealt with in the manner that the doc=
ument addresses them, pointing out that a stateless approach has the advant=
age of not having state.</div>
<div><br></div><div>While the draft might have been a little easier to foll=
ow if it was a little more concrete, for example how is the statelessness t=
o be achieved and what are the costs of this approach (which must presumabl=
y exist or else why use a statefull mapping), this will have to be addresse=
d in any implementation draft.</div>
<div><br></div><div><br></div>-- <br>Website: <a href=3D"http://hallambaker=
.com/">http://hallambaker.com/</a><br><br>

--e89a8fb1f59a8c942f04ccc13f08--

From mstjohns@comcast.net  Tue Oct 23 15:57:05 2012
Return-Path: <mstjohns@comcast.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EC78B1F0C96 for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 15:57:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.403
X-Spam-Level: 
X-Spam-Status: No, score=-100.403 tagged_above=-999 required=5 tests=[AWL=0.034, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JYKsKl+xtmva for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 15:57:05 -0700 (PDT)
Received: from qmta03.westchester.pa.mail.comcast.net (qmta03.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:32]) by ietfa.amsl.com (Postfix) with ESMTP id 2F9CC1F0C3A for <ietf@ietf.org>; Tue, 23 Oct 2012 15:57:04 -0700 (PDT)
Received: from omta11.westchester.pa.mail.comcast.net ([76.96.62.36]) by qmta03.westchester.pa.mail.comcast.net with comcast id EdVp1k00R0mv7h053mx9Gu; Tue, 23 Oct 2012 22:57:09 +0000
Received: from Mike-T530.comcast.net ([68.83.222.237]) by omta11.westchester.pa.mail.comcast.net with comcast id Emwr1k00557vnMg3XmwrBr; Tue, 23 Oct 2012 22:56:52 +0000
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Tue, 23 Oct 2012 18:57:04 -0400
To: Paul Hoffman <paul.hoffman@vpnc.org>
From: Michael StJohns <mstjohns@comcast.net>
Subject: Re: IAOC Request for community feedback
In-Reply-To: <C1A50EDF-60C0-41EC-9F2D-15EAE495B352@vpnc.org>
References: <20121022234941.28301.7687.idtracker@ietfa.amsl.com> <20121023172013.918DC11E8099@ietfa.amsl.com> <C1A50EDF-60C0-41EC-9F2D-15EAE495B352@vpnc.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Message-Id: <20121023225705.2F9CC1F0C3A@ietfa.amsl.com>
Cc: The IAOC <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: Tue, 23 Oct 2012 22:57:06 -0000

At 05:55 PM 10/23/2012, Paul Hoffman wrote:
>On Oct 23, 2012, at 10:16 AM, Michael StJohns <mstjohns@comcast.net> wrote:
>
>> Wait just one minute.....
>> 
>> 
>> Marshal has neither resigned nor died (both of which would vacate the position).  
>
>I don't see anything in BCP 10 that says those are the only to ways to vacate a position. Those two are obvious possibilities, but "went away and actively refused to respond to queries" seems like a reasonable one as well.

Death is an objective evaluation.  Resigned is an objective evaluation.  "went away" is a subjective evaluation.  "refused to respond to queries" - irrelevant unless you know why, and then it's a subjective evaluation.

The recall committee gets to decide subjective questions.  AFAIK that's why it's specified in this document.  There is no other way specified in BCP101 for the position to become vacant.


>> He apparently *has* abrogated his responsibilities.
>> 
>> I'm not sure why the IAOC thinks that the recall procedure shouldn't be followed.
>
>Isn't it obvious? Given a choice of the two procedures, and given that Nomcom is already choosing an IAOC member, declaring the seat vacant is way easier.

It would be easier to declare that we're not going to put the choice to the Nomcom and just have Russ pick the next member.  But that's not what's written down.


>> Get a petition signed.  Run a 1 week call for volunteers. Do the  recall committee selection prior to the IETF, present your case to the recall committee at the IETF and stand back and let them do the work.
>> 
>> I appreciate the pain of having a member go AWOL, but I see no basis for declaring the position vacant based on current practice.
>
>Ummmm, what current practice are you referring to? Has something like this happened in the past decade or two?

Exactly - we have no precedent, and I for one do not want to establish one.  

During my time as Nomcom chair a while back - we had a member that checked out on the IESG.  We never contemplated declaring the position vacant, instead the Nomcom asked the chair at the time to suggest that the member resign.  Fortunately, he was able to respond and we got the resignation.  But had he not responded, I would have fought any attempt to replace him without first doing due process.




>> I would consider that your email constitutes evidence that the IAOC has asked for a recall petition to be circulated.  I would consider that the list of grievances you've posted constitutes sufficient grounds for the petition.  
>
>That's an interesting reading, given that what the email says is "we consider the seat vacant".

No, the facts of the email are that he hasn't responded or attended. That's the evidence.  The "we consider the seat vacant" is a verdict by a group of people not yet empowered to enforce that verdict.




>> I would estimate that you have sufficient support for the petition to be confirmed, but I don't see anything so critical that would suggest that the recall process need not be followed.
>> 
>> I'm willing to sign on to the petition.  I'm willing to volunteer for the recall committee.
>
>I'm willing to let the IAOC define the seat vacant, because it clearly is, and there is no specific definition of "vacant" that disagrees with the logical conclusion.

If Marshall showed up at the IETF in Atlanta, explaining that he had been absent for personal reasons now resolved, would you still feel the same way?

I'm not willing to allow the IAOC to define the seat vacant, because it is not one of the powers delegated to them jointly or severally. 


>--Paul Hoffman



From bob.hinden@gmail.com  Tue Oct 23 16:26:13 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 9380311E80E3 for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 16:26:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.595
X-Spam-Level: 
X-Spam-Status: No, score=-103.595 tagged_above=-999 required=5 tests=[AWL=0.004, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SqznKTALDPYk for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 16:26:01 -0700 (PDT)
Received: from mail-pa0-f44.google.com (mail-pa0-f44.google.com [209.85.220.44]) by ietfa.amsl.com (Postfix) with ESMTP id C85DD11E80A4 for <ietf@ietf.org>; Tue, 23 Oct 2012 16:26:00 -0700 (PDT)
Received: by mail-pa0-f44.google.com with SMTP id fb11so3098802pad.31 for <ietf@ietf.org>; Tue, 23 Oct 2012 16:26:00 -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=ryTxvXQE9RZGczB3S8KeR7wAflqV+GQBLG5314z/G2k=; b=E8CV9xxod26gcTv0PNsRM9VMnTQ6NSS7Vt6Y7XhavjjWHVVVFwNlH3Ln1TdemEbjqk pln7WhisQ+S1awiITw1hQLaoYoDxC+mqEBBXYZbZpiF/T3dT8VrXTLcOIoJHb/Eo7ECe AxJy0nclDubOXSjmHCUQ7Lt6wghn5hROMPS+6vhZY+bFUdsyfi72KxNOdUIjL3sM2KgJ rKJcs7R26vC2UyaHmXYYsY0wFU07ZCKKoVTcFUWjTyXUC8+CWjLjWHzNxQEBsCGxha8d WOkFLwHw2TDKn15/kxGWp05NvcZW/VWlbpoWFUZmIc6ceEkTUjIj9nwCGngWViHWB1Ow VyjQ==
Received: by 10.68.125.229 with SMTP id mt5mr44537086pbb.51.1351034760513; Tue, 23 Oct 2012 16:26:00 -0700 (PDT)
Received: from [172.16.224.219] ([209.97.127.34]) by mx.google.com with ESMTPS id lb3sm8393296pbc.73.2012.10.23.16.25.50 (version=SSLv3 cipher=OTHER); Tue, 23 Oct 2012 16:25:58 -0700 (PDT)
Subject: Re: IAOC Request for community feedback
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=us-ascii
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <1FB012B6-672D-47DD-92A5-81084E833136@gmail.com>
Date: Tue, 23 Oct 2012 16:25:49 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <F7DE7677-5ADA-4FEF-B383-DF91535FB291@gmail.com>
References: <20121023211128.773D018C0A0@mercury.lcs.mit.edu> <1FB012B6-672D-47DD-92A5-81084E833136@gmail.com>
To: ietf@ietf.org
X-Mailer: Apple Mail (2.1283)
Cc: Bob Hinden <bob.hinden@gmail.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Oct 2012 23:26:13 -0000

Responding to some of the discussion, I would like to raise a few =
points.

I don't see how the IAOC has bypassed any rules.  We are asking the =
community if it is OK to declare Marshall's position vacant.  Bypassing =
the rules would be true if the IAOC had gone ahead unilaterally and =
asked the NomCom to fill the reminder of Marshall's term.  The community =
consensus will determine the answer to the query. =20

We think the current procedures were not meant for this case and are not =
clear on the situation when to declare a position vacant.

BCP101 says:

  Any appointed IAOC member, including any appointed
  by the IAB, IESG, or ISOC Board of Trustees, may be recalled using
  the recall procedure defined in RFC 3777.

The use of "may" usually means do this unless there is good reason to do =
otherwise.  I think that is the case in this situation.

The IAOC has operational responsibilities.  Having one voting member not =
attending many meetings makes it harder obtaining a consensus.  Without =
a consensus the IAOC can not approve contracts, RFPs, etc. =20

Lastly, and I think most important, the IAOC proposed this approach =
because we think it would cause the least amount of embarrassment to =
Marshall.  Marshall has been active in the IETF for many years and has =
made many important contributions.  We proposed this course of action in =
respect to Marshall.  We think it's better to not subject him to the =
formal RFC3777 recall process.  Having his position declared vacant is =
milder than having him be formally recalled.

Bob



From joelja@bogus.com  Tue Oct 23 16:47:54 2012
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 74B811F0CBD for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 16:47:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.399
X-Spam-Level: 
X-Spam-Status: No, score=-102.399 tagged_above=-999 required=5 tests=[AWL=0.200, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8Lj7GOwlljuf for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 16:47:53 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id CF8A41F0CB7 for <ietf@ietf.org>; Tue, 23 Oct 2012 16:47:53 -0700 (PDT)
Received: from joels-MacBook-Air.local (host-64-47-153-50.masergy.com [64.47.153.50]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id q9NNln2b042047 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Tue, 23 Oct 2012 23:47:50 GMT (envelope-from joelja@bogus.com)
Message-ID: <50872CA5.70500@bogus.com>
Date: Tue, 23 Oct 2012 16:47:49 -0700
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: Bob Hinden <bob.hinden@gmail.com>
Subject: Re: IAOC Request for community feedback
References: <20121023211128.773D018C0A0@mercury.lcs.mit.edu> <1FB012B6-672D-47DD-92A5-81084E833136@gmail.com> <F7DE7677-5ADA-4FEF-B383-DF91535FB291@gmail.com>
In-Reply-To: <F7DE7677-5ADA-4FEF-B383-DF91535FB291@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Tue, 23 Oct 2012 23:47:50 +0000 (UTC)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Oct 2012 23:47:54 -0000

On 10/23/12 4:25 PM, Bob Hinden wrote:
> Responding to some of the discussion, I would like to raise a few points.
>
> I don't see how the IAOC has bypassed any rules.  We are asking the community if it is OK to declare Marshall's position vacant.  Bypassing the rules would be true if the IAOC had gone ahead unilaterally and asked the NomCom to fill the reminder of Marshall's term.  The community consensus will determine the answer to the query.
>
> We think the current procedures were not meant for this case and are not clear on the situation when to declare a position vacant.
>
> BCP101 says:
>
>    Any appointed IAOC member, including any appointed
>    by the IAB, IESG, or ISOC Board of Trustees, may be recalled using
>    the recall procedure defined in RFC 3777.
>
> The use of "may" usually means do this unless there is good reason to do otherwise.  I think that is the case in this situation.
>
> The IAOC has operational responsibilities.  Having one voting member not attending many meetings makes it harder obtaining a consensus.  Without a consensus the IAOC can not approve contracts, RFPs, etc.
>
> Lastly, and I think most important, the IAOC proposed this approach because we think it would cause the least amount of embarrassment to Marshall.  Marshall has been active in the IETF for many years and has made many important contributions.  We proposed this course of action in respect to Marshall.  We think it's better to not subject him to the formal RFC3777 recall process.  Having his position declared vacant is milder than having him be formally recalled.
The result
> Bob
>
>
>


From joelja@bogus.com  Tue Oct 23 16:52:25 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 40A8E11E8111 for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 16:52:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.414
X-Spam-Level: 
X-Spam-Status: No, score=-102.414 tagged_above=-999 required=5 tests=[AWL=0.185, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OvydbpG1UF0I for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 16:52:23 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 9913511E810B for <ietf@ietf.org>; Tue, 23 Oct 2012 16:52:22 -0700 (PDT)
Received: from joels-MacBook-Air.local (host-64-47-153-50.masergy.com [64.47.153.50]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id q9NNqJw9042099 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Tue, 23 Oct 2012 23:52:19 GMT (envelope-from joelja@bogus.com)
Message-ID: <50872DB3.9090608@bogus.com>
Date: Tue, 23 Oct 2012 16:52:19 -0700
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: Bob Hinden <bob.hinden@gmail.com>
Subject: Re: IAOC Request for community feedback
References: <20121023211128.773D018C0A0@mercury.lcs.mit.edu> <1FB012B6-672D-47DD-92A5-81084E833136@gmail.com> <F7DE7677-5ADA-4FEF-B383-DF91535FB291@gmail.com>
In-Reply-To: <F7DE7677-5ADA-4FEF-B383-DF91535FB291@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Tue, 23 Oct 2012 23:52:19 +0000 (UTC)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Oct 2012 23:52:26 -0000

On 10/23/12 4:25 PM, Bob Hinden wrote:
> Responding to some of the discussion, I would like to raise a few points.
>
> I don't see how the IAOC has bypassed any rules.  We are asking the community if it is OK to declare Marshall's position vacant.  Bypassing the rules would be true if the IAOC had gone ahead unilaterally and asked the NomCom to fill the reminder of Marshall's term.  The community consensus will determine the answer to the query.
>
> We think the current procedures were not meant for this case and are not clear on the situation when to declare a position vacant.
>
> BCP101 says:
>
>    Any appointed IAOC member, including any appointed
>    by the IAB, IESG, or ISOC Board of Trustees, may be recalled using
>    the recall procedure defined in RFC 3777.
>
> The use of "may" usually means do this unless there is good reason to do otherwise.  I think that is the case in this situation.
>
> The IAOC has operational responsibilities.  Having one voting member not attending many meetings makes it harder obtaining a consensus.  Without a consensus the IAOC can not approve contracts, RFPs, etc.
>
> Lastly, and I think most important, the IAOC proposed this approach because we think it would cause the least amount of embarrassment to Marshall.  Marshall has been active in the IETF for many years and has made many important contributions.  We proposed this course of action in respect to Marshall.  We think it's better to not subject him to the formal RFC3777 recall process.  Having his position declared vacant is milder than having him be formally recalled.
The result of a 3777 process is theoretically not subject to appeal. 
which has a certainly finality on completion that I don't think this 
proposal has. I don't think the proposal is bad, but I don't think it is 
a generically appropriate approach.
> Bob
>
>
>


From ted.ietf@gmail.com  Tue Oct 23 17:10:21 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 B4A4A11E8112 for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 17:10:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.531
X-Spam-Level: 
X-Spam-Status: No, score=-3.531 tagged_above=-999 required=5 tests=[AWL=0.068,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I7VuoklFAApv for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 17:10:21 -0700 (PDT)
Received: from mail-vc0-f172.google.com (mail-vc0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 833CE11E810E for <ietf@ietf.org>; Tue, 23 Oct 2012 17:10:20 -0700 (PDT)
Received: by mail-vc0-f172.google.com with SMTP id fl11so5341980vcb.31 for <ietf@ietf.org>; Tue, 23 Oct 2012 17:10: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=JKpy25S4Yb/AU2nX7lH22T4hBram4zTAscnl9pbWJ/8=; b=rq9/AGxmG2zRnM4sxUTewNr+98RHSQdE21onpvC+gtIwVYXIKGo6wW/2HcATPuiLDL GnAft71OfyjngEe15/laowlL5He2lpby7h+aTgowLfNgO0DMN9KzeSBozgVGoZaU5uZq HMtXjTIzvawXVlHOUJJeg8kWi1u1RboWRsWJV0ch4311DNVfUsq+jxuzWm5JkDJQMJW8 vN33BSO5Pk7ER5Sp6ni0Eocdrw7CaXrGfrMbKeg+vku9w0kwgP+vcNIwNFgVB8YPxcwr 1rLFG/Dzhr2u6uci6QsIoZIDvlJMqe1D7wOgFqloO6t2p72MK5A1G+A8jbKH36VGQk34 UA0Q==
MIME-Version: 1.0
Received: by 10.59.13.135 with SMTP id ey7mr7707804ved.37.1351037419767; Tue, 23 Oct 2012 17:10:19 -0700 (PDT)
Received: by 10.58.245.39 with HTTP; Tue, 23 Oct 2012 17:10:19 -0700 (PDT)
In-Reply-To: <Pine.LNX.4.64.1210232348110.2471@ps20323.dreamhostps.com>
References: <50604C1A.7090901@gmx.de> <5060A964.5060001@stpeter.im> <Pine.LNX.4.64.1210172354500.2478@ps20323.dreamhostps.com> <507F5A7E.6040206@arcanedomain.com> <50856E3C.103@gmail.com> <Pine.LNX.4.64.1210221753010.2471@ps20323.dreamhostps.com> <0DBC8A11-319C-4120-975E-7E40FD5818BF@gbiv.com> <Pine.LNX.4.64.1210222137530.2471@ps20323.dreamhostps.com> <CA+9kkMDpEZCvcG1DJd=O1qPNV+=+GTBeN+CGndUe51Xym_A9sg@mail.gmail.com> <Pine.LNX.4.64.1210232115210.2471@ps20323.dreamhostps.com> <15E1D98B-8883-4936-81A9-174E1323683C@nordsc.com> <CAGKvQ5ZV6_GMVgjEezhR-oKqSikxR7GYgacMitbfczmNh725mw@mail.gmail.com> <Pine.LNX.4.64.1210232348110.2471@ps20323.dreamhostps.com>
Date: Tue, 23 Oct 2012 17:10:19 -0700
Message-ID: <CA+9kkMDN6+WGkvVC94iiSjB2O+ijGDiweqPfagm6ZTBdLz12_Q@mail.gmail.com>
Subject: Re: [whatwg] New URL Standard from Anne van Kesteren on 2012-09-24 (public-whatwg-archive@w3.org from September 2012)
From: Ted Hardie <ted.ietf@gmail.com>
To: Ian Hickson <ian@hixie.ch>
Content-Type: text/plain; charset=ISO-8859-1
Cc: Christophe Lauret <clauret@weborganic.com>, Jan Algermissen <jan.algermissen@nordsc.com>, URI <uri@w3.org>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Oct 2012 00:10:21 -0000

On Tue, Oct 23, 2012 at 4:51 PM, Ian Hickson <ian@hixie.ch> wrote:
> Having multiple specs means an implementor has to refer to multiple specs
> to implement one algorithm, which is not a way to get interoperability.
> Bugs creep in much faster when implementors have to switch between specs
> just in the implementation of one algorithm.
>

First, do you have data that supports this assertion?

Second, multiple folks in this conversation have asserted that the
right way to approach this is to have *two* algorithms.  The first is
"method to get from string to URI"  and the second is "Process URI".
It is not obvious that those need to be in the same document, any more
than the processing of DNS names needs to be described in the same
document of URLs whose schemes include DNS names.

(In case it is not obvious, it is the string-which-may-become-a-URI
that I have referred to as a "fleen" in previous notes).

It also seems far more likely to me that bugs will creep in from
re-defining a known algorithm (the "process URI" bit from the pair
above) than from the separation of that from a different operation.
If the results of the rewording would be different operations the, as
I have noted before, you really should use different terms and admit
to the fork.

My personal opinion, as has been noted,

regards,

Ted Hardie

From sm@resistor.net  Tue Oct 23 17:19:05 2012
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C364211E811D for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 17:19:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.588
X-Spam-Level: 
X-Spam-Status: No, score=-102.588 tagged_above=-999 required=5 tests=[AWL=0.011, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F0taIU7B5mQE for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 17:19:05 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2B3FE11E8118 for <ietf@ietf.org>; Tue, 23 Oct 2012 17:19:05 -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 q9O0IwJK002470; Tue, 23 Oct 2012 17:19:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1351037942; bh=7gv3cUdRk4aNZVDXtQoviC1ZwQqsIZoHUhg5QOzPj04=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=zucT5FEQboRhZXBk0d3TlKy/aTa4clQ1K0A3oR3ny1cT2XKySJ2w4ZW5iR+9fE9fY +DpuYieKC8sFi6moBaTdpmm0aPUZ92UaO7tDxBaWaBWN3VK7ds/WPUth0K9ei3mcxP WWVDo1nKnP8tBuKEnpkjDCKymXzfnXKclTuPC2HM=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1351037942; i=@resistor.net; bh=7gv3cUdRk4aNZVDXtQoviC1ZwQqsIZoHUhg5QOzPj04=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=1YrHfe7PWQzpzMIfOzqrp7usvUMirrdKX/oijFALWsODguW8OC+pZBRAoQgT6bG7M KhHobrdPH7aHeWHPZ5itD7XM3BfNJz3p8o5zwB4/ovsmliFsRwudl9UwkqgWvYOybV owtbfQ7nTo9Sz7CvK2ePOUtlmXHZNo5IPegd+bM8=
Message-Id: <6.2.5.6.2.20121023165657.09513cd8@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 23 Oct 2012 17:17:46 -0700
To: ietf@ietf.org
From: SM <sm@resistor.net>
Subject: Re: IAOC Request for community feedback
In-Reply-To: <F7DE7677-5ADA-4FEF-B383-DF91535FB291@gmail.com>
References: <20121023211128.773D018C0A0@mercury.lcs.mit.edu> <1FB012B6-672D-47DD-92A5-81084E833136@gmail.com> <F7DE7677-5ADA-4FEF-B383-DF91535FB291@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: Bob Hinden <bob.hinden@gmail.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Oct 2012 00:19:05 -0000

At 16:25 23-10-2012, Bob Hinden wrote:
>The IAOC has operational responsibilities.  Having one voting member 
>not attending many meetings makes it harder obtaining a 
>consensus.  Without a consensus the IAOC can not approve contracts, RFPs, etc.

According to the IAOC procedures:

   "A quorum for a meeting of the IAOC shall be a majority of the IAOC then in
    office.  All decisions of the members must be approved by majority vote of
    the members then in office."

>formal RFC3777 recall process.  Having his position declared vacant 
>is milder than having him be formally recalled.

Having a recall committee decide about the matter instead of the IETF 
Community discussion is milder as the details would not be subject to 
public scrutiny.  The following (edited) question [1] is relevant:

   If the person showed up at the IETF in Atlanta, explaining that he had
   been absent for personal reasons now resolved, what would be the
   course of action?

There are a few "bugs" in RFC 3777.  It might be better not to 
discuss about that now.

Regards,
-sm

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


From dougb@dougbarton.us  Tue Oct 23 17:47:51 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 350A011E8141 for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 17:47:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.334
X-Spam-Level: 
X-Spam-Status: No, score=-3.334 tagged_above=-999 required=5 tests=[AWL=0.265,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id w9ushOO8KA5g for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 17:47:50 -0700 (PDT)
Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by ietfa.amsl.com (Postfix) with ESMTP id 7FA3F11E813D for <ietf@ietf.org>; Tue, 23 Oct 2012 17:47:50 -0700 (PDT)
Received: (qmail 4659 invoked by uid 399); 24 Oct 2012 00:47:36 -0000
Received: from unknown (HELO ?192.168.0.102?) (dougb@dougbarton.us@12.207.105.210) by mail2.fluidhosting.com with ESMTPAM; 24 Oct 2012 00:47:36 -0000
X-Originating-IP: 12.207.105.210
X-Sender: dougb@dougbarton.us
Message-ID: <50873AB4.1000905@dougbarton.us>
Date: Tue, 23 Oct 2012 17:47:48 -0700
From: Doug Barton <dougb@dougbarton.us>
Organization: http://SupersetSolutions.com/
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121010 Thunderbird/16.0.1
MIME-Version: 1.0
To: John Leslie <john@jlc.net>
Subject: Re: IAOC Request for community feedback
References: <20121023192135.203AC18C0A4@mercury.lcs.mit.edu> <5086EF82.9060900@dougbarton.us> <20121023200713.GC1861@nsn.com> <5086FBCE.2070503@dougbarton.us> <20121023213251.GF27557@verdi>
In-Reply-To: <20121023213251.GF27557@verdi>
X-Enigmail-Version: 1.4.5
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: 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: Wed, 24 Oct 2012 00:47:51 -0000

First in regards to Bob's post a bit ago, I personally am not asserting
that the IAOC has broken any rules. I was sincere in my applause for
their requesting feedback on this question; in spite of the fact that I
disagree with their premise.

On 10/23/2012 2:32 PM, John Leslie wrote:
> Doug Barton <dougb@dougbarton.us> wrote:
>>
>> You asked for feedback, you have now received a non-trivial number of
>> responses saying that arbitrarily declaring the position vacant is not
>> an appropriate action. You have also received volunteers for the recall
>> process. Rather than spending more time on trying to justify declaring
>> the position vacant, why not get started on that recall?
> 
>    I strongly urge folks who think as Doug does to _read_ RFC 3777.

I watched the castle being built, I've no desire to live in it. :) I did
do a quick review of it just now, and at the risk of repeating myself I
think anyone who is interested in revamping it would be putting their
efforts to excellent use.

>    Note that the recall process can only start with 20 "members of the
> IETF community, who are qualified to be voting members of a nominating
> committee" petitioning to the Internet Society President.
> 
>    If that happens, the recall process will start; if not, it won't.

How very tautological of you. :)

[snip]

>    Myself, I don't expect to petition or volunteer to serve on a
> recall committee. The recall process isn't intended to be "practical",
> IMHO, and seems intended only to prod the subject of recall to resign.
> In other organizations, I have lived through longish periods of
> uncertainty about the exact status of an individual, and I no longer
> find it scary.

I tend to agree, which is one of the reasons I think the procedure
should be followed as written.

Doug

From ajs@anvilwalrusden.com  Tue Oct 23 20:47:40 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 5C9691F0C7E for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 20:47:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.84
X-Spam-Level: 
X-Spam-Status: No, score=-0.84 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VSwzihSCxSVQ for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 20:47:40 -0700 (PDT)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id E66261F0C5F for <ietf@ietf.org>; Tue, 23 Oct 2012 20:47:39 -0700 (PDT)
Received: from crankycanuck.ca (unknown [38.107.218.2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id AAB728A031 for <ietf@ietf.org>; Wed, 24 Oct 2012 03:47:38 +0000 (UTC)
Date: Tue, 23 Oct 2012 23:47:37 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: Just so I'm clear (was: IAOC Request for community feedback)
Message-ID: <20121024034736.GC52558@crankycanuck.ca>
References: <20121023192135.203AC18C0A4@mercury.lcs.mit.edu> <5086EF82.9060900@dougbarton.us> <20121023200713.GC1861@nsn.com> <5086FBCE.2070503@dougbarton.us> <20121023213251.GF27557@verdi> <50873AB4.1000905@dougbarton.us>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <50873AB4.1000905@dougbarton.us>
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, 24 Oct 2012 03:47:40 -0000

On Tue, Oct 23, 2012 at 05:47:48PM -0700, Doug Barton wrote:
> 
> On 10/23/2012 2:32 PM, John Leslie wrote:

> > In other organizations, I have lived through longish periods of
> > uncertainty about the exact status of an individual, and I no longer
> > find it scary.
> 
> I tend to agree, which is one of the reasons I think the procedure
> should be followed as written.

Let me get this straight: for the sake of procedures that are clearly
designed to be hard to use, and on the dubious principle that some
"precedent" is going to be set with respect to doing something that we
have never done before and hope never to do again (because we're going
to clarify the procedures right now), and in the face of an impending
decision by an already-sitting nomcom that is already doing all this
work, we're going to cleave to using the heavyweight procedure instead
of allowing judgement to carry the day?

I just want to be clear about this, since I'm busy running around the
NANOG meeting attempting to encourage operators to devote more of the
time they don't have to IETF activities.  I want to be sure I'm
correct in illustrating to them how we have all the bureaucratic
agility of the ITU-T or ICANN and all the legal and political
sophistication of the Occupy Wall Street committees.

Best,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com


From dougb@dougbarton.us  Tue Oct 23 21:23:33 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 ECAD811E8164 for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 21:23:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.367
X-Spam-Level: 
X-Spam-Status: No, score=-3.367 tagged_above=-999 required=5 tests=[AWL=0.232,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1DOoZMLWkAJm for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 21:23:33 -0700 (PDT)
Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by ietfa.amsl.com (Postfix) with ESMTP id 11ED411E8161 for <ietf@ietf.org>; Tue, 23 Oct 2012 21:23:32 -0700 (PDT)
Received: (qmail 30801 invoked by uid 399); 24 Oct 2012 04:23:13 -0000
Received: from unknown (HELO ?192.168.0.102?) (dougb@dougbarton.us@12.207.105.210) by mail2.fluidhosting.com with ESMTPAM; 24 Oct 2012 04:23:13 -0000
X-Originating-IP: 12.207.105.210
X-Sender: dougb@dougbarton.us
Message-ID: <50876D39.20502@dougbarton.us>
Date: Tue, 23 Oct 2012 21:23:21 -0700
From: Doug Barton <dougb@dougbarton.us>
Organization: http://SupersetSolutions.com/
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121010 Thunderbird/16.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Just so I'm clear
References: <20121023192135.203AC18C0A4@mercury.lcs.mit.edu> <5086EF82.9060900@dougbarton.us> <20121023200713.GC1861@nsn.com> <5086FBCE.2070503@dougbarton.us> <20121023213251.GF27557@verdi> <50873AB4.1000905@dougbarton.us> <20121024034736.GC52558@crankycanuck.ca>
In-Reply-To: <20121024034736.GC52558@crankycanuck.ca>
X-Enigmail-Version: 1.4.5
OpenPGP: id=1A1ABC84
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, 24 Oct 2012 04:23:34 -0000

On 10/23/2012 8:47 PM, Andrew Sullivan wrote:

> Let me get this straight: for the sake of procedures that are clearly
> designed to be hard to use,

While I think that 3777 probably errs on the side of too hard to use,
recalling someone from one of these positions _should_ be hard to do,
and should not be undertaken lightly.

> and on the dubious principle that some
> "precedent" is going to be set with respect to doing something that we
> have never done before and hope never to do again

Thus, the definition of a precedent.

> (because we're going to clarify the procedures right now),

One hopes, but there are no guarantees in life.

> and in the face of an impending
> decision by an already-sitting nomcom that is already doing all this
> work,

That's one of the reasons that the documented procedure is more
palatable (barely).

> we're going to cleave to using the heavyweight procedure instead
> of allowing judgement to carry the day?

The problem with that "judgement" that you'd like to use here is that it
may be all fine and good in this case, but what about next time?

> I just want to be clear about this, since I'm busy running around the
> NANOG meeting attempting to encourage operators to devote more of the
> time they don't have to IETF activities.  I want to be sure I'm
> correct in illustrating to them how we have all the bureaucratic
> agility of the ITU-T or ICANN and all the legal and political
> sophistication of the Occupy Wall Street committees.

With respect, you haven't spent much time with either the ITU or ICANN
if you think that 3777 is rigidly bureaucratic by their standards.

This is one of those situations where we have to take our medicine.

Doug

From lear@cisco.com  Tue Oct 23 21:52:03 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 F29FC21F8C0D for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 21:51:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.437
X-Spam-Level: 
X-Spam-Status: No, score=-110.437 tagged_above=-999 required=5 tests=[AWL=0.162, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id biMLv4hK19Sz for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 21:51:53 -0700 (PDT)
Received: from ams-iport-4.cisco.com (ams-iport-4.cisco.com [144.254.224.147]) by ietfa.amsl.com (Postfix) with ESMTP id E491D21F8C0C for <ietf@ietf.org>; Tue, 23 Oct 2012 21:51:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=777; q=dns/txt; s=iport; t=1351054312; x=1352263912; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=SzgfuRSwmjZo15up2o1usiIWOvf1eHadf15+HRMGO2k=; b=JpMC+1vh1NVdpzFAh3tVaW2/fL5I0M7jpxTBXZmMISkUC3myJyv7+jf1 mYiDDftCXUA5u9ZOSH8WjjE2cwJSLROOTg7XFupPzI93mNwrv8oMP9Xxy UWs4mncGlh6fFklO+Qp+4p1blMmpj5BoEQJbBK1/YDkXKVU6PhH9jdnk+ c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAHdyh1CQ/khL/2dsb2JhbABEhhS7cYEIgh4BAQEEEgEQVhALGAICBSECAg8CRgYNAQcBAR6HYpsFjSGSWoEgkBmBEgOVc45OgWuCcQ
X-IronPort-AV: E=Sophos;i="4.80,638,1344211200";  d="scan'208";a="9051332"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by ams-iport-4.cisco.com with ESMTP; 24 Oct 2012 04:51:51 +0000
Received: from dhcp-10-55-83-243.cisco.com (dhcp-10-55-83-243.cisco.com [10.55.83.243]) by ams-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id q9O4powU001260 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 24 Oct 2012 04:51:50 GMT
Message-ID: <508773E7.10203@cisco.com>
Date: Wed, 24 Oct 2012 06:51:51 +0200
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:16.0) Gecko/20121010 Thunderbird/16.0.1
MIME-Version: 1.0
To: Doug Barton <dougb@dougbarton.us>
Subject: Re: Just so I'm clear
References: <20121023192135.203AC18C0A4@mercury.lcs.mit.edu> <5086EF82.9060900@dougbarton.us> <20121023200713.GC1861@nsn.com> <5086FBCE.2070503@dougbarton.us> <20121023213251.GF27557@verdi> <50873AB4.1000905@dougbarton.us> <20121024034736.GC52558@crankycanuck.ca> <50876D39.20502@dougbarton.us>
In-Reply-To: <50876D39.20502@dougbarton.us>
X-Enigmail-Version: 1.4.5
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, 24 Oct 2012 04:52:06 -0000

On 10/24/12 6:23 AM, Doug Barton wrote:
> With respect, you haven't spent much time with either the ITU or ICANN
> if you think that 3777 is rigidly bureaucratic by their standards.
> This is one of those situations where we have to take our medicine. Doug 

There are actually very few ITU rules, and very many guidelines.  The
latter are the exact opposite of rigid, but subject to overturning by
Member States at any time.  I had thought that we were roughly the same
in that regard, so as to avoid a perversity.  We've had any number of
debates on this list about not creating process without a reason. 
Fine.  The price for that is that you have to deal with these sorts of
circumstances as and when they arise, using rough consensus as your guide.

Eliot


From dougb@dougbarton.us  Tue Oct 23 22:01: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 495D321F8C2A for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 22:01:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.393
X-Spam-Level: 
X-Spam-Status: No, score=-3.393 tagged_above=-999 required=5 tests=[AWL=0.206,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Rf2XFYEqihsD for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 22:01:55 -0700 (PDT)
Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by ietfa.amsl.com (Postfix) with ESMTP id 942ED21F8C18 for <ietf@ietf.org>; Tue, 23 Oct 2012 22:01:55 -0700 (PDT)
Received: (qmail 13382 invoked by uid 399); 24 Oct 2012 05:01:27 -0000
Received: from unknown (HELO ?192.168.0.102?) (dougb@dougbarton.us@12.207.105.210) by mail2.fluidhosting.com with ESMTPAM; 24 Oct 2012 05:01:27 -0000
X-Originating-IP: 12.207.105.210
X-Sender: dougb@dougbarton.us
Message-ID: <50877633.1000402@dougbarton.us>
Date: Tue, 23 Oct 2012 22:01:39 -0700
From: Doug Barton <dougb@dougbarton.us>
Organization: http://SupersetSolutions.com/
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121010 Thunderbird/16.0.1
MIME-Version: 1.0
To: Eliot Lear <lear@cisco.com>
Subject: Re: Just so I'm clear
References: <20121023192135.203AC18C0A4@mercury.lcs.mit.edu> <5086EF82.9060900@dougbarton.us> <20121023200713.GC1861@nsn.com> <5086FBCE.2070503@dougbarton.us> <20121023213251.GF27557@verdi> <50873AB4.1000905@dougbarton.us> <20121024034736.GC52558@crankycanuck.ca> <50876D39.20502@dougbarton.us> <508773E7.10203@cisco.com>
In-Reply-To: <508773E7.10203@cisco.com>
X-Enigmail-Version: 1.4.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: Wed, 24 Oct 2012 05:01:56 -0000

On 10/23/2012 9:51 PM, Eliot Lear wrote:
> 
> On 10/24/12 6:23 AM, Doug Barton wrote:
>> With respect, you haven't spent much time with either the ITU or ICANN
>> if you think that 3777 is rigidly bureaucratic by their standards.
>> This is one of those situations where we have to take our medicine. Doug 
> 
> There are actually very few ITU rules, and very many guidelines.  The
> latter are the exact opposite of rigid, but subject to overturning by
> Member States at any time.  I had thought that we were roughly the same
> in that regard, so as to avoid a perversity.  We've had any number of
> debates on this list about not creating process without a reason. 
> Fine.  The price for that is that you have to deal with these sorts of
> circumstances as and when they arise, using rough consensus as your guide.

I've repeated myself many times now, so you're going to get the last word.

I get what you're saying, but this is one of those times where (arguably
for the better) we've created a difficult procedure that should be
infrequently exercised. We should follow the procedure because it _is_
the procedure. And then use the opportunity to improve it.

Changing, or even overturning a procedure is quite a different thing
from ignoring one altogether.

Doug


From melinda.shore@gmail.com  Tue Oct 23 22:04:14 2012
Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1D4B721F8C48 for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 22:04:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tLmf2vWCJZLz for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 22:04:13 -0700 (PDT)
Received: from mail-da0-f44.google.com (mail-da0-f44.google.com [209.85.210.44]) by ietfa.amsl.com (Postfix) with ESMTP id 1EF6F21F8C39 for <ietf@ietf.org>; Tue, 23 Oct 2012 22:04:13 -0700 (PDT)
Received: by mail-da0-f44.google.com with SMTP id h15so75047dan.31 for <ietf@ietf.org>; Tue, 23 Oct 2012 22:04:12 -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=e2zq02Hx4FPVsIZU1aD1+hklwlH7ROL3EzZ2FzM/1wM=; b=huqtTKq/spD3Y16vjgzbfZivHlFp6N7AZBQxpgBGyGmsLEBfR96rdYlpLxvwC6Cy24 43TkwISh8i1ubDnFs5/mEMUHpLFjwEkOGCXYlYK8ctt8+k3brOqLWNt8Hnoen120LRGG puIInmbP0ONFwIkQwvVry8ka0pvbqh4MVWR72slhks8drLhTjgCdVsBAXEh80AFtvtMb RvokVl4/ZKwR9Iyg7XYEcjns8kAGa+Kn48wyhxrnJTsuEmlvO60sbZ3y+KLwLwpqddK5 abSAeIvRXpaaolkEZDbSAFdBfkdU7pDwN1HbrJDPc+3Tv5z+HSxLDpIm9Dv7plxx9RF3 3qdQ==
Received: by 10.68.200.227 with SMTP id jv3mr46415407pbc.162.1351055052819; Tue, 23 Oct 2012 22:04:12 -0700 (PDT)
Received: from spandex.local (216-67-49-109-rb1.fai.dsl.dynamic.acsalaska.net. [216.67.49.109]) by mx.google.com with ESMTPS id k6sm5049574paz.8.2012.10.23.22.04.11 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 23 Oct 2012 22:04:12 -0700 (PDT)
Message-ID: <508776CA.7070208@gmail.com>
Date: Tue, 23 Oct 2012 21:04:10 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:16.0) Gecko/20121010 Thunderbird/16.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Just so I'm clear
References: <20121023192135.203AC18C0A4@mercury.lcs.mit.edu> <5086EF82.9060900@dougbarton.us> <20121023200713.GC1861@nsn.com> <5086FBCE.2070503@dougbarton.us> <20121023213251.GF27557@verdi> <50873AB4.1000905@dougbarton.us> <20121024034736.GC52558@crankycanuck.ca> <50876D39.20502@dougbarton.us> <508773E7.10203@cisco.com>
In-Reply-To: <508773E7.10203@cisco.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Oct 2012 05:04:14 -0000

On 10/23/12 8:51 PM, Eliot Lear wrote:
> There are actually very few ITU rules, and very many guidelines.  The
> latter are the exact opposite of rigid, but subject to overturning by
> Member States at any time.  I had thought that we were roughly the same
> in that regard, so as to avoid a perversity.  We've had any number of
> debates on this list about not creating process without a reason. 
> Fine.  The price for that is that you have to deal with these sorts of
> circumstances as and when they arise, using rough consensus as your guide.

I was away from the IETF for several years and was surprised by the
degree of ossification I found when I returned.  I would very much
like to see us find some way to restore some agility.  That said,
consensus-y processes scale poorly in cases where there's substantial
disagreement.  On the other hand, what I've seen so far in this
discussion is two roughly sorted groups of responses:  1) "yes," and
2) "I am not comfortable with this process."  There doesn't seem to
be anybody saying "No" on the merits of the question, but concern
that saying "yes" will violate some processes we've put in place.

I am curious to know whether or not there are people who feel that
Marshall shouldn't be considered to have quit IAOC.  If there's
nobody who feels that way I'm personally great with going ahead
without a recall.  If we've got basic agreement that Marshall
needs to be replaced it seems to me that we're good to go ahead and
do so.  If we don't have agreement, then it's time to go through the
process.

Melinda


From jnc@mercury.lcs.mit.edu  Tue Oct 23 22:09:01 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 9FB8721F8C8E for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 22:09:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.44
X-Spam-Level: 
X-Spam-Status: No, score=-6.44 tagged_above=-999 required=5 tests=[AWL=0.159,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hhBBMQr1mqB5 for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 22:09:00 -0700 (PDT)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id 8BA8521F8C91 for <ietf@ietf.org>; Tue, 23 Oct 2012 22:09:00 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 5B23918C0A6; Wed, 24 Oct 2012 01:08:59 -0400 (EDT)
To: ietf@ietf.org
Subject: Re: Just so I'm clear
Message-Id: <20121024050859.5B23918C0A6@mercury.lcs.mit.edu>
Date: Wed, 24 Oct 2012 01:08:59 -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, 24 Oct 2012 05:09:01 -0000

    > From: Doug Barton <dougb@dougbarton.us>

    > recalling someone from one of these positions _should_ be hard to do,
    > and should not be undertaken lightly.

No disagreement there - but we're not trying to recall him because of actions
he took, things he said, etc, etc.

Like I said, I think the US's federal constitution is a useful model here: it
has a very onerous process (impeachment and trial) with a high final bar
(2/3) for actions taken in response to what someone did/said, but a wholly
different, simpler and easier process (majority of Cabinet) for sidelining
someone because of incapacity.

And I doubt anyone here is seriously going to argue that Marshall is not
fulfulling his role...


    > From: Melinda Shore <melinda.shore@gmail.com>

    > I am curious to know whether or not there are people who feel that
    > Marshall shouldn't be considered to have quit IAOC. If there's nobody
    > who feels that way I'm personally great with going ahead without a
    > recall.

Exactly.

	Noel

From mstjohns@comcast.net  Tue Oct 23 22:23:56 2012
Return-Path: <mstjohns@comcast.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D02CE21F8D16 for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 22:23:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.709
X-Spam-Level: 
X-Spam-Status: No, score=-99.709 tagged_above=-999 required=5 tests=[AWL=-0.668, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, MIME_QP_LONG_LINE=1.396, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EBeuGY6RX+Ci for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 22:23:56 -0700 (PDT)
Received: from qmta01.emeryville.ca.mail.comcast.net (qmta01.emeryville.ca.mail.comcast.net [IPv6:2001:558:fe2d:43:76:96:30:16]) by ietfa.amsl.com (Postfix) with ESMTP id C309421F8D15 for <ietf@ietf.org>; Tue, 23 Oct 2012 22:23:55 -0700 (PDT)
Received: from omta18.emeryville.ca.mail.comcast.net ([76.96.30.74]) by qmta01.emeryville.ca.mail.comcast.net with comcast id EtMG1k0051bwxycA1tPvSA; Wed, 24 Oct 2012 05:23:55 +0000
Received: from [192.168.1.102] ([68.83.222.237]) by omta18.emeryville.ca.mail.comcast.net with comcast id EtPt1k00E57vnMg8etPuuv; Wed, 24 Oct 2012 05:23:55 +0000
References: <20121024050859.5B23918C0A6@mercury.lcs.mit.edu>
In-Reply-To: <20121024050859.5B23918C0A6@mercury.lcs.mit.edu>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=us-ascii
Message-Id: <3823F8B2-8A7A-4528-B8CE-49A1F867968D@comcast.net>
X-Mailer: iPad Mail (9B206)
From: Michael StJohns <mstjohns@comcast.net>
Subject: Re: Just so I'm clear
Date: Wed, 24 Oct 2012 01:23:55 -0400
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Cc: "ietf@ietf.org" <ietf@ietf.org>, "jnc@mercury.lcs.mit.edu" <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, 24 Oct 2012 05:23:56 -0000

Yes but -=20

The process you refer to deals with "temporary" incapacity where the office h=
older might not want to go away for a while.   And even then there's a proce=
ss and a defined group of people who run that process.  (cf 25th amendment).=
 =20

I agree with you that removing him would be the simplest approach, but I can=
 see possible situations where NOT following the process could lead us into l=
egal trouble. =20

Consider: =20
1) Marshall sues because we've removed him and it caused him to lose an inco=
me opportunity.
2) Someone who does business with the IETF sues because he didn't like the o=
utcome of a contracting action, and argues that the new and improved IAOC (m=
inus marshall, plus a replacement) wasn't legitimate and didn't have the sta=
nding to sign a new contract.
3) someone sues the replacement for an action taken in conjunction with the I=
AOC and the insurance company denies liability coverage because the replacem=
ent wasn't legitimately appointed.

If we follow the documented procedures, those arguments lack foundation. =20=


I've made my points.  The IAOC will do what it will do. =20

Sent from my iPad

On Oct 24, 2012, at 1:08, jnc@mercury.lcs.mit.edu (Noel Chiappa) wrote:

>> From: Doug Barton <dougb@dougbarton.us>
>=20
>> recalling someone from one of these positions _should_ be hard to do,
>> and should not be undertaken lightly.
>=20
> No disagreement there - but we're not trying to recall him because of acti=
ons
> he took, things he said, etc, etc.
>=20
> Like I said, I think the US's federal constitution is a useful model here:=
 it
> has a very onerous process (impeachment and trial) with a high final bar
> (2/3) for actions taken in response to what someone did/said, but a wholly=

> different, simpler and easier process (majority of Cabinet) for sidelining=

> someone because of incapacity.
>=20
> And I doubt anyone here is seriously going to argue that Marshall is not
> fulfulling his role...
>=20
>=20
>> From: Melinda Shore <melinda.shore@gmail.com>
>=20
>> I am curious to know whether or not there are people who feel that
>> Marshall shouldn't be considered to have quit IAOC. If there's nobody
>> who feels that way I'm personally great with going ahead without a
>> recall.
>=20
> Exactly.
>=20
>    Noel

From rdroms.ietf@gmail.com  Tue Oct 23 23:06:40 2012
Return-Path: <rdroms.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 01B7E21F8D8C for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 23:06:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zhGegkYVeKBQ for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 23:06:39 -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 D2E6221F8D88 for <ietf@ietf.org>; Tue, 23 Oct 2012 23:06:38 -0700 (PDT)
Received: by mail-wi0-f178.google.com with SMTP id hr7so104557wib.13 for <ietf@ietf.org>; Tue, 23 Oct 2012 23:06:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to:x-mailer; bh=oZfvQVACqgORgnmUF2dGm7/mnERVRisfUw3lwFXYcS4=; b=cXkDwhykOhdCDF8xoNegEpXNMuzG6vhJzKfInnWNyq9HLQivrRvXe0pdHjr0zOF6nm fxyQ8urPOe47o7VDeZkaNrW8TCi1ij1GwXWMJhH6G2oM6Uh8/HtCfxrpQSHyJZscXuek dH7rvTxSntVRd70LOlcyKcmeoBfSm7M84UA6Mk2Tmsnfo2jifLqTr0jA7iEkSbiCsJkn Bp+xqhhSpxmOsQB3qlj7iQIU+4lX6KG2cOtLEudM+wSzhy3+eKQP703lmlEvxaXBoT1H 7OrJ/8cHTPWlrMmdpramJhDukCE8kF/NjT2Cwhcd7Ewn10Ed1G5WFimHxJylDppwajfp BplQ==
Received: by 10.216.217.38 with SMTP id h38mr7859819wep.82.1351058789787; Tue, 23 Oct 2012 23:06:29 -0700 (PDT)
Received: from [192.168.1.139] (62.83.159.26.dyn.user.ono.com. [62.83.159.26]) by mx.google.com with ESMTPS id cn6sm2988888wib.9.2012.10.23.23.06.21 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 23 Oct 2012 23:06:28 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1283)
Subject: Re: Just so I'm clear
From: Ralph Droms <rdroms.ietf@gmail.com>
In-Reply-To: <3823F8B2-8A7A-4528-B8CE-49A1F867968D@comcast.net>
Date: Wed, 24 Oct 2012 08:06:18 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <14D6B8A6-4F79-4AED-A89A-58CF3A6BE803@gmail.com>
References: <20121024050859.5B23918C0A6@mercury.lcs.mit.edu> <3823F8B2-8A7A-4528-B8CE-49A1F867968D@comcast.net>
To: IETF discussion list <ietf@ietf.org>
X-Mailer: Apple Mail (2.1283)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Oct 2012 06:06:40 -0000

I'm convinced the IAOC needs to be restored to full membership and I'm =
not convinced we need to bypass our existing recall process.  I would =
prefer that we exercise that process, but will accede to whatever =
process is judged to have consensus.

- Ralph


From bortzmeyer@nic.fr  Tue Oct 23 23:58:03 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 7575221F8D85 for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 23:58:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.999
X-Spam-Level: 
X-Spam-Status: No, score=-101.999 tagged_above=-999 required=5 tests=[AWL=0.250, BAYES_00=-2.599, HELO_EQ_FR=0.35, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SXnqH-z0pDQD for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 23:58:00 -0700 (PDT)
Received: from mx4.nic.fr (mx4.nic.fr [192.134.4.12]) by ietfa.amsl.com (Postfix) with ESMTP id CC4AC21F8D80 for <ietf@ietf.org>; Tue, 23 Oct 2012 23:57:59 -0700 (PDT)
Received: from mx4.nic.fr (localhost [127.0.0.1]) by mx4.nic.fr (Postfix) with SMTP id 649422804F1; Wed, 24 Oct 2012 08:57:28 +0200 (CEST)
Received: from relay2.nic.fr (relay2.nic.fr [192.134.4.163]) by mx4.nic.fr (Postfix) with ESMTP id 5FDEF2804B3; Wed, 24 Oct 2012 08:57:28 +0200 (CEST)
Received: from bortzmeyer.nic.fr (batilda.nic.fr [IPv6:2001:67c:2219:8::6:69]) by relay2.nic.fr (Postfix) with ESMTP id 54E13B38004; Wed, 24 Oct 2012 08:57:28 +0200 (CEST)
Date: Wed, 24 Oct 2012 08:57:28 +0200
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: iab@iab.org
Subject: Re: REMINDER: Call for Comment on 'Affirmation of the Modern Paradigm for 	Standards'
Message-ID: <20121024065728.GA32267@nic.fr>
References: <018e01cda7ba$036c0960$0a441c20$@iab.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <018e01cda7ba$036c0960$0a441c20$@iab.org>
X-Operating-System: Debian GNU/Linux wheezy/sid
X-Kernel: Linux 3.2.0-3-686-pae i686
Organization: NIC France
X-URL: http://www.nic.fr/
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Oct 2012 06:58:03 -0000

On Thu, Oct 11, 2012 at 07:09:22AM -0700,
 IAB Chair <iab-chair@iab.org> wrote 
 a message of 155 lines which said:

> This is an IETF-wide Call for Comment on 'Affirmation of the Modern
> Paradigm for Standards'.

What's the point of this Call for Comment? Was there any chance that
the text could be modified (after all, it would require agreement of
all organisations).

The way ticket #193 was closed without any explanation seems to
indicate that, no, there never was any chance for a change:

http://trac.tools.ietf.org/group/iab/trac/ticket/193

From brian.e.carpenter@gmail.com  Wed Oct 24 00:16:45 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 513BB21F8D0E for <ietf@ietfa.amsl.com>; Wed, 24 Oct 2012 00:16:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.691
X-Spam-Level: 
X-Spam-Status: No, score=-101.691 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7FikZ3DN4DYI for <ietf@ietfa.amsl.com>; Wed, 24 Oct 2012 00:16:44 -0700 (PDT)
Received: from mail-ea0-f172.google.com (mail-ea0-f172.google.com [209.85.215.172]) by ietfa.amsl.com (Postfix) with ESMTP id 94DD721F8D0C for <ietf@ietf.org>; Wed, 24 Oct 2012 00:16:44 -0700 (PDT)
Received: by mail-ea0-f172.google.com with SMTP id k13so56424eaa.31 for <ietf@ietf.org>; Wed, 24 Oct 2012 00:16:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=iaSko/l8DLm0kJM/NNIhMzrQfQqIDTyQLAlstv2JVZc=; b=u+of06TfhT1gtm2//25XiMJQr5miwEucc3SbZfnvH9+2fyGabvco8WlgyeJiYSh8m2 ul53jH+VPAL9asgxyL32y4oaBKbog8CRvatK2jc/rZVq53FrRLER9Q46ggrkMBZXUgsq RKAmuKTyi49LC4mCNUNo8l5wtDnx747p1H9PVrxG5pJMAp1+MHf0kg466eqgeUxZ6FSg DvlpVJBWmibUxJqjhldPgDz8qG3z+4upaGabJbqUbHj7TKPu7/oo9lEFqdPBM++zdtH8 /w3LyA9kFu2VhN4vc2HgMD1muiu28KyVuVv9kG4qOb1VpznB2K5RbeuKL32g4vSjUnFd s2RQ==
Received: by 10.14.215.69 with SMTP id d45mr20095165eep.16.1351063003694; Wed, 24 Oct 2012 00:16:43 -0700 (PDT)
Received: from [192.168.1.65] (host-2-101-189-188.as13285.net. [2.101.189.188]) by mx.google.com with ESMTPS id r45sm24250920eem.6.2012.10.24.00.16.41 (version=SSLv3 cipher=OTHER); Wed, 24 Oct 2012 00:16:42 -0700 (PDT)
Message-ID: <508795D7.1050102@gmail.com>
Date: Wed, 24 Oct 2012 08:16:39 +0100
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: David Kessens <david.kessens@nsn.com>
Subject: Re: IAOC Request for community feedback
References: <20121023192135.203AC18C0A4@mercury.lcs.mit.edu>	<5086EF82.9060900@dougbarton.us> <20121023200713.GC1861@nsn.com>
In-Reply-To: <20121023200713.GC1861@nsn.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org, Noel Chiappa <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, 24 Oct 2012 07:16:45 -0000

On 23/10/2012 21:07, David Kessens wrote:
> Doug,
> 
> On Tue, Oct 23, 2012 at 12:26:58PM -0700, Doug Barton wrote:
>> You're not proposing a change in procedure. You're proposing to ignore
>> one. 
> 
> No procedure is ignored.
> 
> BCP 101 does not define the rules for declaring a position vacant. In
> absense of such rules, the IAOC decided to consult with the community
> whether the community agrees that the position is now vacant.

Exactly. To my mind, a member who ceases to participate, and fails to
reply to messages indicating that the seat is about to be declared
vacant, has created a vacancy. I think the IAOC is behaving appropriately.

> Another avenue, which is also mentioned in the BCP, that could have been
> followed is the recall procedure. However, the IAOC felt that it was not
> really intended for a situation where somebody apparently has vacated their
> position.

Agreed. It could be used for that, but I don't see it as required.
We aren't dealing with alleged misbehaviour.

    Brian Carpenter

From bortzmeyer@nic.fr  Wed Oct 24 03:09:19 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 EFE4121F893E; Wed, 24 Oct 2012 03:09:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.041
X-Spam-Level: 
X-Spam-Status: No, score=-102.041 tagged_above=-999 required=5 tests=[AWL=0.208, BAYES_00=-2.599, HELO_EQ_FR=0.35, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NFQQMrz-elK5; Wed, 24 Oct 2012 03:09:19 -0700 (PDT)
Received: from mx4.nic.fr (mx4.nic.fr [192.134.4.12]) by ietfa.amsl.com (Postfix) with ESMTP id 48A5421F8672; Wed, 24 Oct 2012 03:09:19 -0700 (PDT)
Received: from mx4.nic.fr (localhost [127.0.0.1]) by mx4.nic.fr (Postfix) with SMTP id 007E22804B3; Wed, 24 Oct 2012 12:08:48 +0200 (CEST)
Received: from relay2.nic.fr (relay2.nic.fr [192.134.4.163]) by mx4.nic.fr (Postfix) with ESMTP id E41A728050D; Wed, 24 Oct 2012 12:08:47 +0200 (CEST)
Received: from bortzmeyer.nic.fr (batilda.nic.fr [IPv6:2001:67c:2219:8::6:69]) by relay2.nic.fr (Postfix) with ESMTP id EBD89B380A2; Wed, 24 Oct 2012 12:07:44 +0200 (CEST)
Date: Wed, 24 Oct 2012 12:07:44 +0200
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: IESG Secretary <iesg-secretary@ietf.org>
Subject: Re: WG Action: Conclusion of Address Resolution for Massive numbers of 	hosts in the Data center (armd)
Message-ID: <20121024100744.GA15377@nic.fr>
References: <20121023183252.7359.72200.idtracker@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20121023183252.7359.72200.idtracker@ietfa.amsl.com>
X-Operating-System: Debian GNU/Linux wheezy/sid
X-Kernel: Linux 3.2.0-3-686-pae i686
Organization: NIC France
X-URL: http://www.nic.fr/
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: ldunbar@huawei.com, ietf@ietf.org, armd@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Oct 2012 10:09:20 -0000

On Tue, Oct 23, 2012 at 11:32:52AM -0700,
 IESG Secretary <iesg-secretary@ietf.org> wrote 
 a message of 7 lines which said:

> The Address Resolution for Massive numbers of hosts in the Data
> center (armd) working group in the Operations and Management Area
> has concluded.

Its charter is far from completed and I do not find in the archives of
the mailing list of the WG an explanation. Two lines of text to
explain what happened?

From jari.arkko@piuha.net  Wed Oct 24 03:36:37 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 E5B4A21F8BB4 for <ietf@ietfa.amsl.com>; Wed, 24 Oct 2012 03:36:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.584
X-Spam-Level: 
X-Spam-Status: No, score=-102.584 tagged_above=-999 required=5 tests=[AWL=0.015, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id loZqomFhcaim for <ietf@ietfa.amsl.com>; Wed, 24 Oct 2012 03:36:37 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by ietfa.amsl.com (Postfix) with ESMTP id 46FB321F8BB2 for <ietf@ietf.org>; Wed, 24 Oct 2012 03:36:37 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 7AF9B2CF37; Wed, 24 Oct 2012 13:36:35 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id P3ZFUVKZnhOB; Wed, 24 Oct 2012 13:36:35 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 0B4102CC2F; Wed, 24 Oct 2012 13:36:35 +0300 (EEST)
Message-ID: <5087C4B2.1060109@piuha.net>
Date: Wed, 24 Oct 2012 13:36:34 +0300
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20121011 Thunderbird/16.0.1
MIME-Version: 1.0
To: Ted Hardie <ted.ietf@gmail.com>, Ian Hickson <ian@hixie.ch>
Subject: Re: [whatwg] New URL Standard from Anne van Kesteren on 2012-09-24 (public-whatwg-archive@w3.org from September 2012)
References: <50604C1A.7090901@gmx.de> <5060A964.5060001@stpeter.im> <Pine.LNX.4.64.1210172354500.2478@ps20323.dreamhostps.com> <507F5A7E.6040206@arcanedomain.com> <50856E3C.103@gmail.com> <Pine.LNX.4.64.1210221753010.2471@ps20323.dreamhostps.com> <0DBC8A11-319C-4120-975E-7E40FD5818BF@gbiv.com> <Pine.LNX.4.64.1210222137530.2471@ps20323.dreamhostps.com> <CA+9kkMDpEZCvcG1DJd=O1qPNV+=+GTBeN+CGndUe51Xym_A9sg@mail.gmail.com> <Pine.LNX.4.64.1210232115210.2471@ps20323.dreamhostps.com> <CA+9kkMBg=hxz=yRYfYA5Hkwp-4ODFBnpK_qctCMB_oEHLPP49g@mail.gmail.com>
In-Reply-To: <CA+9kkMBg=hxz=yRYfYA5Hkwp-4ODFBnpK_qctCMB_oEHLPP49g@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: URI <uri@w3.org>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Oct 2012 10:36:38 -0000

Ted, Ian,

> Un-marked context shifts are
> likely, and likely to be bad.  Avoiding them by picking a new term is
> both easy and appropriate.

FWIW, I agree with Ted's advice above.

>
> My personal opinion, as always,
>

Mine too.

Jari


From brian.e.carpenter@gmail.com  Wed Oct 24 03:39:53 2012
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BA38E21F8948 for <ietf@ietfa.amsl.com>; Wed, 24 Oct 2012 03:39:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.691
X-Spam-Level: 
X-Spam-Status: No, score=-101.691 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BXYnz9+pW3-u for <ietf@ietfa.amsl.com>; Wed, 24 Oct 2012 03:39:53 -0700 (PDT)
Received: from mail-bk0-f44.google.com (mail-bk0-f44.google.com [209.85.214.44]) by ietfa.amsl.com (Postfix) with ESMTP id 1691121F893B for <ietf@ietf.org>; Wed, 24 Oct 2012 03:39:52 -0700 (PDT)
Received: by mail-bk0-f44.google.com with SMTP id jc3so148839bkc.31 for <ietf@ietf.org>; Wed, 24 Oct 2012 03:39:52 -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=Pk3ryE1M/fYAuunVK1M3CTxaLayfPz8tBijtbzs0Th4=; b=yUnblBF7Q+eqhvMI3YrS34+Fo2x1SyastetO2/gVydlxVs/X2UwOcZBhNHY+0lM3Ma /WGNgAVoFAqSu9tE++jpVTxd4URsKK3OChIxh8NbpUH6gIfWiJFzIC/Y6a8cMqwP5SJ6 /iKwC/vYdRgPcRzasinAUTkkV5/g6BMCjIciMTeY7r5OQaM3n8pgyKxNf0TUAdc6E0fI zuo8xGLHYP9HWqMNIVMm1XXqMQTs3ZqsoAddXC6YmeOTTCBgmbmVJxnOIPqISAEMnG0h jpTQUtItYaxILJyIkmNh6vpVzTvGmBOjt5eeCluwsC0h2XeeJ4SC1Gt5IOodBmTx0K8Y ZmJw==
Received: by 10.204.131.75 with SMTP id w11mr4739018bks.111.1351075192197; Wed, 24 Oct 2012 03:39:52 -0700 (PDT)
Received: from [192.168.1.65] (host-2-101-189-188.as13285.net. [2.101.189.188]) by mx.google.com with ESMTPS id v14sm7642166bkv.10.2012.10.24.03.39.50 (version=SSLv3 cipher=OTHER); Wed, 24 Oct 2012 03:39:51 -0700 (PDT)
Message-ID: <5087C57A.80607@gmail.com>
Date: Wed, 24 Oct 2012 11:39:54 +0100
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Mark Nottingham <mnot@mnot.net>
Subject: Re: [whatwg] New URL Standard from Anne van Kesteren on 2012-09-24 (public-whatwg-archive@w3.org from September 2012)
References: <50604C1A.7090901@gmx.de> <5060A964.5060001@stpeter.im> <Pine.LNX.4.64.1210172354500.2478@ps20323.dreamhostps.com> <507F5A7E.6040206@arcanedomain.com> <50856E3C.103@gmail.com> <Pine.LNX.4.64.1210221753010.2471@ps20323.dreamhostps.com> <0DBC8A11-319C-4120-975E-7E40FD5818BF@gbiv.com> <Pine.LNX.4.64.1210222137530.2471@ps20323.dreamhostps.com> <5085C4BA.2030505@gmx.de> <Pine.LNX.4.64.1210222220510.2471@ps20323.dreamhostps.com> <CAHBU6is8LNZ7Rq-vwLuOm+8ThKB9c=QPwbUfQwDQD5bDPjtf7w@mail.gmail.com> <Pine.LNX.4.64.1210222320070.2471@ps20323.dreamhostps.com> <09DC68AA-2DAD-4CB1-9CA9-799AF12B7BE2@mnot.net>
In-Reply-To: <09DC68AA-2DAD-4CB1-9CA9-799AF12B7BE2@mnot.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: IETF Discussion <ietf@ietf.org>, Julian Reschke <julian.reschke@gmx.de>, "Roy T. Fielding" <fielding@gbiv.com>, Jan Algermissen <jan.algermissen@nordsc.com>, Noah Mendelsohn <nrm@arcanedomain.com>, URI <uri@w3.org>, Tim Bray <tbray@textuality.com>, Ian Hickson <ian@hixie.ch>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Oct 2012 10:39:53 -0000

On 23/10/2012 00:32, Mark Nottingham wrote:
...
> The underlying point that people seem to be making is that there's legitimate need for URIs to be a separate concept from "strings that will become URIs." By collapsing them into one thing, you're doing those folks a disservice. Browser implementers may not care, but it's pretty obvious that lots of other people do.

Thanks for bringing this point out. It was explained to me in 1993 by TBL and
Robert Cailliau that URLs (the only term used then, I think) should never
be typed in by a user, and preferably never even seen by a user. It's because
that doctrine was abandoned a year or so later that we have this problem
today. I think there would be value in a document making this clear, as
a framework for clearly separating the specification of what is allowable
as a URI on the wire from what is acceptable as a user input string (UIS?).

UIS to URI conversion may well end up as a heuristic algorithm.

Regards

     Brian

From stephen.farrell@cs.tcd.ie  Wed Oct 24 05:18:48 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 C2E6021F887E for <ietf@ietfa.amsl.com>; Wed, 24 Oct 2012 05:18:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.266
X-Spam-Level: 
X-Spam-Status: No, score=-103.266 tagged_above=-999 required=5 tests=[AWL=-0.667, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XVaP221LRexV for <ietf@ietfa.amsl.com>; Wed, 24 Oct 2012 05:18:47 -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 2DE8A21F886D for <ietf@ietf.org>; Wed, 24 Oct 2012 05:18:47 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hermes.scss.tcd.ie (Postfix) with ESMTP id E6EAC171479; Wed, 24 Oct 2012 13:18:44 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; h= content-transfer-encoding:content-type:in-reply-to:references :subject:mime-version:user-agent:from:date:message-id:received :received:x-virus-scanned; s=cs; t=1351081123; bh=4Y4k79dyuTu8Y9 Bx1h33NlisDnPR9Tdtuj73vG/Jfu0=; b=lSaEAtVH+1uyCRLVxmwESoACveGf1C l2sICGRIpeLPnt4VfvX2fEcgmcZb6fXH6r+IKn1Tq4XrPjwGsZF8rQNwnNkOrLyV z/m39OQljBMZjj4PG3OlzMpuHmjEzc9gpSH2ZaoY9CLipOCsuP8Fkkq6d6KNvUDb bssy0AJqqxfo8Z7q5xXR5q5nwW5GAxKeeCUzCD4lykMqcf2Zn4plN2CtRHANDTqx EoyNakPuS88Q0YEbL7Zf1t9Bjc4wO+Fcj8ylDknaiISZHm10RMQ71AEA3tdMAOha HOoLD6TCnwLLn8wQ9vbg8BXFA6KM1d2XCgIin93iaFNIa/xGA9XEv4rg==
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 UzoZLql+CEU4; Wed, 24 Oct 2012 13:18:43 +0100 (IST)
Received: from [IPv6:2001:770:10:203:93a:7c18:9b35:51a7] (unknown [IPv6:2001:770:10:203:93a:7c18:9b35:51a7]) by smtp.scss.tcd.ie (Postfix) with ESMTPSA id 6B04C171478; Wed, 24 Oct 2012 13:18:41 +0100 (IST)
Message-ID: <5087DCA1.505@cs.tcd.ie>
Date: Wed, 24 Oct 2012 13:18:41 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20121017 Thunderbird/16.0.1
MIME-Version: 1.0
To: Jari Arkko <jari.arkko@piuha.net>
Subject: Re: [whatwg] New URL Standard from Anne van Kesteren on 2012-09-24 (public-whatwg-archive@w3.org from September 2012)
References: <50604C1A.7090901@gmx.de> <5060A964.5060001@stpeter.im> <Pine.LNX.4.64.1210172354500.2478@ps20323.dreamhostps.com> <507F5A7E.6040206@arcanedomain.com> <50856E3C.103@gmail.com> <Pine.LNX.4.64.1210221753010.2471@ps20323.dreamhostps.com> <0DBC8A11-319C-4120-975E-7E40FD5818BF@gbiv.com> <Pine.LNX.4.64.1210222137530.2471@ps20323.dreamhostps.com> <CA+9kkMDpEZCvcG1DJd=O1qPNV+=+GTBeN+CGndUe51Xym_A9sg@mail.gmail.com> <Pine.LNX.4.64.1210232115210.2471@ps20323.dreamhostps.com> <CA+9kkMBg=hxz=yRYfYA5Hkwp-4ODFBnpK_qctCMB_oEHLPP49g@mail.gmail.com> <5087C4B2.1060109@piuha.net>
In-Reply-To: <5087C4B2.1060109@piuha.net>
X-Enigmail-Version: 1.4.5
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: Ted Hardie <ted.ietf@gmail.com>, Ian Hickson <ian@hixie.ch>, URI <uri@w3.org>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Oct 2012 12:18:48 -0000

On 10/24/2012 11:36 AM, Jari Arkko wrote:
> Ted, Ian,
> 
>> Un-marked context shifts are
>> likely, and likely to be bad.  Avoiding them by picking a new term is
>> both easy and appropriate.
> 
> FWIW, I agree with Ted's advice above.

Further to that, some guy's fine tool [1] says that
RFC 3986 is referenced by 193 other RFCs. Google
scholar says that RFC 3986 has 2090 citations. [2]
While that's nowhere near the full story, it is
nonetheless significant.

Buggering about with a spec like that whilst only
considering a limited context seems hugely dumb to
me, no matter how good a case you seem to have for
changing bits and pieces of it. So far, I've not seen
the argument for changing 3986, but there do seem
to be good arguments for additional things such as
error-handling specific to the browser context.

I honestly don't get the argument for forking,
and I agree with Ted that that's what's at issue
and would be stupid. I don't know that inventing a
new term is that good an approach either really,
it'd seem better to me to try specify the additional
stuff needed in the whatwg context and then see if
there's any change to 3986 needed and if so, then
propose those changes as an update to the RFC,
following the IETF process. That is not what I
see happening now and I do see an apparent intent
to create the stupid fork that Ted identified.

Getting an update to 3986 through the IETF process
will I'm sure be a huge PITA for whoever does
propose it, since there are so many other dependent
specs. But that's life, and its quite do-able, if
done by someone who's able to handle that kind of
work.

S.

[1] http://www.arkko.com/tools/allstats/citations-rfc3986.html
[2]
http://scholar.google.com/scholar?cites=6121683772362091274&as_sdt=2005&sciodt=0,5&hl=en


> 
>>
>> My personal opinion, as always,
>>
> 
> Mine too.
> 
> Jari
> 
> 
> 

From edj.etc@gmail.com  Wed Oct 24 05:18:58 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 A90B821F8B89; Wed, 24 Oct 2012 05:18:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.846
X-Spam-Level: 
X-Spam-Status: No, score=-103.846 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, GB_I_LETTER=-2, MIME_BASE64_TEXT=1.753, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rwPEl4MTVaUn; Wed, 24 Oct 2012 05:18:57 -0700 (PDT)
Received: from mail-ie0-f172.google.com (mail-ie0-f172.google.com [209.85.223.172]) by ietfa.amsl.com (Postfix) with ESMTP id 8CD4321F8B8A; Wed, 24 Oct 2012 05:18:56 -0700 (PDT)
Received: by mail-ie0-f172.google.com with SMTP id 9so637974iec.31 for <multiple recipients>; Wed, 24 Oct 2012 05:18:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-rim-org-msg-ref-id:message-id:content-transfer-encoding:reply-to :x-priority:references:in-reply-to:sensitivity:importance:subject:to :from:date:content-type:mime-version; bh=Ty5Cbfk/632B5mPS3TytsmDxgLjQBlktd0eXA4tVCSM=; b=mJGvtn+oA2ZofTZ5iChzBTcJoLd+gFEyerwEKgsgR7hzGUA3nG8J4M6zZeGi0d+cHQ R3BbUVug2YMkT9gG9xZaK/2aHZCQ36dC+tKlTCYgctQSLFabs9EDhARrwMKLTwDVSWuX 3JuhBqs6VI6R5AHogr3TqnZwTAhFjxaccozsfPet/aYtpXN3Jb1Z1L+y50Wb5+ynNVP3 wqzlIT0FuvYNOH/b8qO6wxn71HngqiJLKv2/wKINk54vt1qtxt1PfauA+Up2kgwG2cwE 5BAfhTB9cAyf2Zt37K4mxdWa2ZKOKVgb5aUAEaXyTF09B+50Ye9y3FYJVb/ek3E8u9Oy bIUQ==
Received: by 10.50.77.136 with SMTP id s8mr1678996igw.74.1351081136040; Wed, 24 Oct 2012 05:18:56 -0700 (PDT)
Received: from 172.29.195.188 (bda-74-82-80-72.bis6.us.blackberry.com. [74.82.80.72]) by mx.google.com with ESMTPS id ez8sm1835693igb.17.2012.10.24.05.18.54 (version=SSLv3 cipher=OTHER); Wed, 24 Oct 2012 05:18:55 -0700 (PDT)
X-rim-org-msg-ref-id: 794893936
Message-ID: <794893936-1351081133-cardhu_decombobulator_blackberry.rim.net-1553919746-@b2.c2.bise6.blackberry>
Content-Transfer-Encoding: base64
X-Priority: Normal
References: <20121023211128.773D018C0A0@mercury.lcs.mit.edu> <1FB012B6-672D-47DD-92A5-81084E833136@gmail.com> <F7DE7677-5ADA-4FEF-B383-DF91535FB291@gmail.com>
In-Reply-To: <F7DE7677-5ADA-4FEF-B383-DF91535FB291@gmail.com>
Sensitivity: Normal
Importance: Normal
Subject: Re: IAOC Request for community feedback
To: "Bob Hinden" <bob.hinden@gmail.com>,ietf-bounces@ietf.org,ietf@ietf.org
From: edj.etc@gmail.com
Date: Wed, 24 Oct 2012 12:18:50 +0000
Content-Type: text/plain
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: edj.etc@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, 24 Oct 2012 12:18:58 -0000

Qm9iIHdyb3RlOg0KDQo+IEhhdmluZyBoaXMgcG9zaXRpb24gZGVjbGFyZWQgdmFjYW50IC4uLg0K
DQpIb3cgbG9uZyBoYXMgaXQgYmVlbiBzaW5jZSB0aGUgbGFzdCB0aW1lIGhlIGF0dGVuZGVkIGFu
IElBT0Mgb3IgSUVURiBtZWV0aW5nLCBvciByZXNwb25kZWQgdG8gYW4gZS1tYWlsIGFkZHJlc3Nl
ZCBkaXJlY3RseSB0byBoaW0/DQoNCldlIGhhdmUgcHJvY2Vzc2VzIHRoYXQgaW52b2x2ZSB0aW1l
cnMgKHZpei4gSS1EcyBleHBpcmUgYWZ0ZXIgNiBtb250aHMpLCBhbmQgc28gSSBhbSB0aGlua2lu
ZyB3ZSBzaG91bGQgZGlzY3VzcyBob3cgbG9uZyBhbiBJQU9DIG1lbWJlciBtYXkgYmUgTUlBIGJl
Zm9yZSBoaXMvaGVyIHNlYXQgaXMgZGVjbGFyZWQgdmFjYW50IG9yICBhdCByaXNrIG9mIHJlY2Fs
bCBiZWNhdXNlIG9mIGJlaW5nIE1JQS4NCg0KSSBhbHNvIGhhdmUgb25lIG1vcmUgcXVlc3Rpb24u
ICBIYXZlIG90aGVyIG1vZGVzIG9mIGNvbW11bmljYXRpb24gYmVlbiBhdHRlbXB0ZWQ/ICBGb3Ig
ZXhhbXBsZTogcmVnaXN0ZXJlZCBsZXR0ZXJzICh2aWEgc25haWwtbWFpbCkgb3IgcGhvbmUgY2Fs
bHM/DQoNClJlZ2FyZHMsDQoNCkVkICBKLiANCiANCg0KLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0t
LS0NCkZyb206IEJvYiBIaW5kZW4gPGJvYi5oaW5kZW5AZ21haWwuY29tPg0KU2VuZGVyOiBpZXRm
LWJvdW5jZXNAaWV0Zi5vcmcNCkRhdGU6IFR1ZSwgMjMgT2N0IDIwMTIgMTY6MjU6NDkgDQpUbzog
PGlldGZAaWV0Zi5vcmc+DQpDYzogQm9iIEhpbmRlbjxib2IuaGluZGVuQGdtYWlsLmNvbT4NClN1
YmplY3Q6IFJlOiBJQU9DIFJlcXVlc3QgZm9yIGNvbW11bml0eSBmZWVkYmFjaw0KDQpSZXNwb25k
aW5nIHRvIHNvbWUgb2YgdGhlIGRpc2N1c3Npb24sIEkgd291bGQgbGlrZSB0byByYWlzZSBhIGZl
dyBwb2ludHMuDQoNCkkgZG9uJ3Qgc2VlIGhvdyB0aGUgSUFPQyBoYXMgYnlwYXNzZWQgYW55IHJ1
bGVzLiAgV2UgYXJlIGFza2luZyB0aGUgY29tbXVuaXR5IGlmIGl0IGlzIE9LIHRvIGRlY2xhcmUg
TWFyc2hhbGwncyBwb3NpdGlvbiB2YWNhbnQuICBCeXBhc3NpbmcgdGhlIHJ1bGVzIHdvdWxkIGJl
IHRydWUgaWYgdGhlIElBT0MgaGFkIGdvbmUgYWhlYWQgdW5pbGF0ZXJhbGx5IGFuZCBhc2tlZCB0
aGUgTm9tQ29tIHRvIGZpbGwgdGhlIHJlbWluZGVyIG9mIE1hcnNoYWxsJ3MgdGVybS4gIFRoZSBj
b21tdW5pdHkgY29uc2Vuc3VzIHdpbGwgZGV0ZXJtaW5lIHRoZSBhbnN3ZXIgdG8gdGhlIHF1ZXJ5
LiAgDQoNCldlIHRoaW5rIHRoZSBjdXJyZW50IHByb2NlZHVyZXMgd2VyZSBub3QgbWVhbnQgZm9y
IHRoaXMgY2FzZSBhbmQgYXJlIG5vdCBjbGVhciBvbiB0aGUgc2l0dWF0aW9uIHdoZW4gdG8gZGVj
bGFyZSBhIHBvc2l0aW9uIHZhY2FudC4NCg0KQkNQMTAxIHNheXM6DQoNCiAgQW55IGFwcG9pbnRl
ZCBJQU9DIG1lbWJlciwgaW5jbHVkaW5nIGFueSBhcHBvaW50ZWQNCiAgYnkgdGhlIElBQiwgSUVT
Rywgb3IgSVNPQyBCb2FyZCBvZiBUcnVzdGVlcywgbWF5IGJlIHJlY2FsbGVkIHVzaW5nDQogIHRo
ZSByZWNhbGwgcHJvY2VkdXJlIGRlZmluZWQgaW4gUkZDIDM3NzcuDQoNClRoZSB1c2Ugb2YgIm1h
eSIgdXN1YWxseSBtZWFucyBkbyB0aGlzIHVubGVzcyB0aGVyZSBpcyBnb29kIHJlYXNvbiB0byBk
byBvdGhlcndpc2UuICBJIHRoaW5rIHRoYXQgaXMgdGhlIGNhc2UgaW4gdGhpcyBzaXR1YXRpb24u
DQoNClRoZSBJQU9DIGhhcyBvcGVyYXRpb25hbCByZXNwb25zaWJpbGl0aWVzLiAgSGF2aW5nIG9u
ZSB2b3RpbmcgbWVtYmVyIG5vdCBhdHRlbmRpbmcgbWFueSBtZWV0aW5ncyBtYWtlcyBpdCBoYXJk
ZXIgb2J0YWluaW5nIGEgY29uc2Vuc3VzLiAgV2l0aG91dCBhIGNvbnNlbnN1cyB0aGUgSUFPQyBj
YW4gbm90IGFwcHJvdmUgY29udHJhY3RzLCBSRlBzLCBldGMuICANCg0KTGFzdGx5LCBhbmQgSSB0
aGluayBtb3N0IGltcG9ydGFudCwgdGhlIElBT0MgcHJvcG9zZWQgdGhpcyBhcHByb2FjaCBiZWNh
dXNlIHdlIHRoaW5rIGl0IHdvdWxkIGNhdXNlIHRoZSBsZWFzdCBhbW91bnQgb2YgZW1iYXJyYXNz
bWVudCB0byBNYXJzaGFsbC4gIE1hcnNoYWxsIGhhcyBiZWVuIGFjdGl2ZSBpbiB0aGUgSUVURiBm
b3IgbWFueSB5ZWFycyBhbmQgaGFzIG1hZGUgbWFueSBpbXBvcnRhbnQgY29udHJpYnV0aW9ucy4g
IFdlIHByb3Bvc2VkIHRoaXMgY291cnNlIG9mIGFjdGlvbiBpbiByZXNwZWN0IHRvIE1hcnNoYWxs
LiAgV2UgdGhpbmsgaXQncyBiZXR0ZXIgdG8gbm90IHN1YmplY3QgaGltIHRvIHRoZSBmb3JtYWwg
UkZDMzc3NyByZWNhbGwgcHJvY2Vzcy4gIEhhdmluZyBoaXMgcG9zaXRpb24gZGVjbGFyZWQgdmFj
YW50IGlzIG1pbGRlciB0aGFuIGhhdmluZyBoaW0gYmUgZm9ybWFsbHkgcmVjYWxsZWQuDQoNCkJv
Yg0KDQoNCg==


From housley@vigilsec.com  Wed Oct 24 06:18:47 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 7A77621F8B6C for <ietf@ietfa.amsl.com>; Wed, 24 Oct 2012 06:18:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.493
X-Spam-Level: 
X-Spam-Status: No, score=-102.493 tagged_above=-999 required=5 tests=[AWL=0.106, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gTDWrrVTODJ7 for <ietf@ietfa.amsl.com>; Wed, 24 Oct 2012 06:18:46 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id D1B6E21F8B71 for <ietf@ietf.org>; Wed, 24 Oct 2012 06:18:46 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id 7479E9A4001; Wed, 24 Oct 2012 09:18:43 -0400 (EDT)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([208.254.26.82]) by localhost (ronin.smetech.net [208.254.26.81]) (amavisd-new, port 10024) with ESMTP id 3nfnrC4niRR5; Wed, 24 Oct 2012 09:18:36 -0400 (EDT)
Received: from [192.168.2.100] (pool-96-255-37-162.washdc.fios.verizon.net [96.255.37.162]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id C1E799A4005; Wed, 24 Oct 2012 09:18:41 -0400 (EDT)
Subject: Re: REMINDER: Call for Comment on 'Affirmation of the Modern Paradigm for Standards'
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <20121024065728.GA32267@nic.fr>
Date: Wed, 24 Oct 2012 09:18:38 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <16992A95-66EF-42E9-9170-A24FC008BECA@vigilsec.com>
References: <018e01cda7ba$036c0960$0a441c20$@iab.org> <20121024065728.GA32267@nic.fr>
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>
X-Mailer: Apple Mail (2.1085)
Cc: iab@iab.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Oct 2012 13:18:47 -0000

Stephane:

> On Thu, Oct 11, 2012 at 07:09:22AM -0700,
> IAB Chair <iab-chair@iab.org> wrote=20
> a message of 155 lines which said:
>=20
>> This is an IETF-wide Call for Comment on 'Affirmation of the Modern
>> Paradigm for Standards'.
>=20
> What's the point of this Call for Comment? Was there any chance that
> the text could be modified (after all, it would require agreement of
> all organisations).
>=20
> The way ticket #193 was closed without any explanation seems to
> indicate that, no, there never was any chance for a change:
>=20
> http://trac.tools.ietf.org/group/iab/trac/ticket/193


The ticket is about this document:
http://www.ietf.org/id/draft-iab-modern-paradigm-01.txt

The document captures the affirmation that took place on 29 August 2012. =
 The document needs to contain the words that were affirmed.  Any =
changes are a future activity, not associated with this document.

Russ


From bortzmeyer@nic.fr  Wed Oct 24 06:24:38 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 95F4121F882E for <ietf@ietfa.amsl.com>; Wed, 24 Oct 2012 06:24:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.071
X-Spam-Level: 
X-Spam-Status: No, score=-102.071 tagged_above=-999 required=5 tests=[AWL=0.179, BAYES_00=-2.599, HELO_EQ_FR=0.35, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oWs8W0zer8NR for <ietf@ietfa.amsl.com>; Wed, 24 Oct 2012 06:24:38 -0700 (PDT)
Received: from mx4.nic.fr (mx4.nic.fr [192.134.4.12]) by ietfa.amsl.com (Postfix) with ESMTP id 1B3D121F882D for <ietf@ietf.org>; Wed, 24 Oct 2012 06:24:38 -0700 (PDT)
Received: from mx4.nic.fr (localhost [127.0.0.1]) by mx4.nic.fr (Postfix) with SMTP id 6C0302801A1; Wed, 24 Oct 2012 15:24:05 +0200 (CEST)
Received: from relay2.nic.fr (relay2.nic.fr [192.134.4.163]) by mx4.nic.fr (Postfix) with ESMTP id 66F9F280127; Wed, 24 Oct 2012 15:24:05 +0200 (CEST)
Received: from bortzmeyer.nic.fr (batilda.nic.fr [IPv6:2001:67c:2219:8::6:69]) by relay2.nic.fr (Postfix) with ESMTP id 5B5E3B38004; Wed, 24 Oct 2012 15:23:35 +0200 (CEST)
Date: Wed, 24 Oct 2012 15:23:35 +0200
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: Russ Housley <housley@vigilsec.com>
Subject: Re: REMINDER: Call for Comment on 'Affirmation of the Modern Paradigm for 	Standards'
Message-ID: <20121024132335.GA25725@nic.fr>
References: <018e01cda7ba$036c0960$0a441c20$@iab.org> <20121024065728.GA32267@nic.fr> <16992A95-66EF-42E9-9170-A24FC008BECA@vigilsec.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <16992A95-66EF-42E9-9170-A24FC008BECA@vigilsec.com>
X-Operating-System: Debian GNU/Linux wheezy/sid
X-Kernel: Linux 3.2.0-3-686-pae i686
Organization: NIC France
X-URL: http://www.nic.fr/
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: iab@iab.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Oct 2012 13:24:38 -0000

On Wed, Oct 24, 2012 at 09:18:38AM -0400,
 Russ Housley <housley@vigilsec.com> wrote 
 a message of 27 lines which said:

> The document captures the affirmation that took place on 29 August
> 2012.  The document needs to contain the words that were affirmed.
> Any changes are a future activity, not associated with this
> document.

Precisely my point: why a Call for Comments if the document can no
longer be modified?


From daedulus@btconnect.com  Wed Oct 24 06:28:51 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 6C19D21F8B88 for <ietf@ietfa.amsl.com>; Wed, 24 Oct 2012 06:28:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.67
X-Spam-Level: 
X-Spam-Status: No, score=-4.67 tagged_above=-999 required=5 tests=[AWL=-1.071,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wriZhx2+EL0d for <ietf@ietfa.amsl.com>; Wed, 24 Oct 2012 06:28:50 -0700 (PDT)
Received: from db3outboundpool.messaging.microsoft.com (db3ehsobe006.messaging.microsoft.com [213.199.154.144]) by ietfa.amsl.com (Postfix) with ESMTP id 0901821F8B7E for <ietf@ietf.org>; Wed, 24 Oct 2012 06:28:49 -0700 (PDT)
Received: from mail69-db3-R.bigfish.com (10.3.81.228) by DB3EHSOBE008.bigfish.com (10.3.84.28) with Microsoft SMTP Server id 14.1.225.23; Wed, 24 Oct 2012 13:28:49 +0000
Received: from mail69-db3 (localhost [127.0.0.1])	by mail69-db3-R.bigfish.com (Postfix) with ESMTP id D978380369; Wed, 24 Oct 2012 13:28:48 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.253.197; KIP:(null); UIP:(null); IPV:NLI; H:DBXPRD0710HT002.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -24
X-BigFish: PS-24(zz98dI9371I542M1432Izz1202h1d1ah1d2ahzz1033IL8275bh8275dhz2dh2a8h5a9h668h839hd24hf0ah1177h1179h1288h12a5h12a9h12bdh137ah139eh13b6h1441h1504h1537h304l1155h)
Received: from mail69-db3 (localhost.localdomain [127.0.0.1]) by mail69-db3 (MessageSwitch) id 1351085327824526_30919; Wed, 24 Oct 2012 13:28:47 +0000 (UTC)
Received: from DB3EHSMHS002.bigfish.com (unknown [10.3.81.244])	by mail69-db3.bigfish.com (Postfix) with ESMTP id C55F53600A1; Wed, 24 Oct 2012 13:28:47 +0000 (UTC)
Received: from DBXPRD0710HT002.eurprd07.prod.outlook.com (157.56.253.197) by DB3EHSMHS002.bigfish.com (10.3.87.102) with Microsoft SMTP Server (TLS) id 14.1.225.23; Wed, 24 Oct 2012 13:28:47 +0000
Received: from AMSPRD0610HT005.eurprd06.prod.outlook.com (157.56.248.85) by pod51017.outlook.com (10.255.79.165) with Microsoft SMTP Server (TLS) id 14.16.224.5; Wed, 24 Oct 2012 13:28:45 +0000
Message-ID: <021c01cdb1eb$71282660$4001a8c0@gateway.2wire.net>
From: t.p. <daedulus@btconnect.com>
To: Russ Housley <housley@vigilsec.com>
References: <4FD845AB.9020505@gmail.com> <D903BF63-043C-400A-90AF-DF962B246540@vigilsec.com>
Subject: Re: Change in I-D announcement format
Date: Wed, 24 Oct 2012 14:28:16 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [157.56.248.85]
X-OriginatorOrg: btconnect.com
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Oct 2012 13:28:51 -0000

And now there seems to be another unannounced change, in that in
addition to the usual announcement format e-mails, there may also be, or
may not be, the appearance seems random, of

Subject: New Version Notification -

e-mails.  This may or may not be an improvement, depending on how long
it takes me to work out what is happening and whether or not I then like
my conclusion.  And whether or not what I rely on is still available.

Tom Petch

----- Original Message -----
From: "Russ Housley" <housley@vigilsec.com>
To: "Brian E Carpenter" <brian.e.carpenter@gmail.com>
Cc: "IETF discussion list" <ietf@ietf.org>
Sent: Wednesday, June 13, 2012 2:06 PM
Subject: Re: Change in I-D announcement format


Brian:

There was no announcement that this change was about to be deployed;
however, there was a long discussion of the change.  It started with a
request for the HTML version of the I-D instead of the plain text
version.  At the end of the discussion the decision was to use the
Datatracker URL as it allows anyone to get the plaintext or a diff with
just one more click.

Russ


On Jun 13, 2012, at 3:47 AM, Brian E Carpenter wrote:

> Did I miss an announcement of the change in format of
> I-D announcement messages?
>
> There's no longer a URL for the standard .txt format. That's
> mildly annoying for me (extra time and extra mouse clicks)
> and must be a nuisance for anyone who processes these messages
> automatically.
>
> At least, I would have expected a warning message about the change.
>
> --
> Regards
>   Brian Carpenter
>
>




From ggm@algebras.org  Wed Oct 24 06:31:35 2012
Return-Path: <ggm@algebras.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 59BF621F8B3E for <ietf@ietfa.amsl.com>; Wed, 24 Oct 2012 06:31:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gucyECTuu0fo for <ietf@ietfa.amsl.com>; Wed, 24 Oct 2012 06:31:34 -0700 (PDT)
Received: from mail-ea0-f172.google.com (mail-ea0-f172.google.com [209.85.215.172]) by ietfa.amsl.com (Postfix) with ESMTP id 2646621F88EB for <ietf@ietf.org>; Wed, 24 Oct 2012 06:31:33 -0700 (PDT)
Received: by mail-ea0-f172.google.com with SMTP id k13so194726eaa.31 for <ietf@ietf.org>; Wed, 24 Oct 2012 06:31:33 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=content-type:mime-version:subject:from:x-priority:in-reply-to:date :content-transfer-encoding:message-id:references:to:x-mailer :x-gm-message-state; bh=JX4l48MEMZtJOTNjXhbE7/WrmhMr3HZXxBkFVSN88kk=; b=WjQGdDDJJZrFATYkGVZ1jUAwswiTBZt/6XvAhMrKrTMThOXKIIF9dTEKkXpz/Wlb3Q lfi7hsU9yhOTIRn/+eGPOi0A/4nOM/qG7zdAWx35uTfNZR6QCr4ik/hdth4CEjQYIkTn ASxe51YBMv4JFI6o9yd9Vfrq6u8qXb91dAi137rQETTmrDXecf1GHM1I7LwC1PSJn7UX IRYPke90dYYnjSd/RsIOWsVALJFGUFQTQfQpKo+Zla9tnZZ5n0SkPpT/uscvBZ34+GSD QjZqaXqquSGg7bMAQd+SdJ7ZKW513hmywBWMVCtHup8g1g6+627SDAp9rdR5zY8mADak oSRA==
Received: by 10.14.178.195 with SMTP id f43mr21735979eem.44.1351085493012; Wed, 24 Oct 2012 06:31:33 -0700 (PDT)
Received: from [10.116.113.126] (net-rtvisitors.oecd.org. [78.41.129.5]) by mx.google.com with ESMTPS id r45sm25758508eem.6.2012.10.24.06.31.31 (version=SSLv3 cipher=OTHER); Wed, 24 Oct 2012 06:31:32 -0700 (PDT)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: Change in I-D announcement format
From: George Michaelson <ggm@algebras.org>
X-Priority: 3
In-Reply-To: <021c01cdb1eb$71282660$4001a8c0@gateway.2wire.net>
Date: Wed, 24 Oct 2012 15:31:30 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <108DFF15-F558-4872-A7F4-AD21192F2C0D@algebras.org>
References: <4FD845AB.9020505@gmail.com> <D903BF63-043C-400A-90AF-DF962B246540@vigilsec.com> <021c01cdb1eb$71282660$4001a8c0@gateway.2wire.net>
To: IETF discussion list <ietf@ietf.org>
X-Mailer: Apple Mail (2.1499)
X-Gm-Message-State: ALoCoQlRRWzh7fWxR1koedzi3F/7aOg2kfrkj3dIP5STL0doeq2eXV8JUOMgCKv/RG8J5fxlfTFA
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Oct 2012 13:31:35 -0000

put bluntly, we all know the mail tools we're using to process these =
mails, and the mails could be a damn sight more tractable for tools than =
they are.

ever tried sorting drafts by subject line?

that old draft-random-group-something-KEYWORD-version is really suckful =
for something as basic as .. sorting.

gonna change that religion? I don't think so.

-G

PS can all the emacs users please not pile on with 'works for me =
(smirk)))))" responses, I know you LISPoids have this dealt with. Some =
of us lost enough braincells to use GUI, and the GUI really don't like =
IETF Draft subjectlines. They mask almost all the useful bits, and =
expose almost all the useless bits.=

From dwm@xpasc.com  Wed Oct 24 06:46:35 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 B258421F8941 for <ietf@ietfa.amsl.com>; Wed, 24 Oct 2012 06:46:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.953
X-Spam-Level: 
X-Spam-Status: No, score=-1.953 tagged_above=-999 required=5 tests=[AWL=-0.646, BAYES_00=-2.599, MISSING_HEADERS=1.292]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IX0hPzArGd1A for <ietf@ietfa.amsl.com>; Wed, 24 Oct 2012 06:46:35 -0700 (PDT)
Received: from c2w3p-2.abacamail.com (c2w3p-2.abacamail.com [209.133.53.32]) by ietfa.amsl.com (Postfix) with ESMTP id 5003521F893F for <ietf@ietf.org>; Wed, 24 Oct 2012 06:46:35 -0700 (PDT)
Received: from xpasc.com (unknown [68.164.244.188]) by c2w3p-2.abacamail.com (Postfix) with ESMTP id C8C233FBAE for <ietf@ietf.org>; Wed, 24 Oct 2012 13:46:34 +0000 (UTC)
Received: from egate.xpasc.com (egate.xpasc.com [10.1.2.49]) by xpasc.com (8.13.8/8.13.8) with ESMTP id q9ODkYkQ004593 for <ietf@ietf.org>; Wed, 24 Oct 2012 06:46:34 -0700
Date: Wed, 24 Oct 2012 06:46:34 -0700 (PDT)
From: David Morris <dwm@xpasc.com>
cc: ietf@ietf.org
Subject: Re: IAOC Request for community feedback
In-Reply-To: <508795D7.1050102@gmail.com>
Message-ID: <alpine.LRH.2.01.1210240634310.32353@egate.xpasc.com>
References: <20121023192135.203AC18C0A4@mercury.lcs.mit.edu> <5086EF82.9060900@dougbarton.us> <20121023200713.GC1861@nsn.com> <508795D7.1050102@gmail.com>
User-Agent: Alpine 2.01 (LRH 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Milter-Version: master.1+13-gbab1945
X-AV-Type: clean
X-AV-Accuracy: exact
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: ietf@ietf.org
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Oct 2012 13:46:35 -0000

On Wed, 24 Oct 2012, Brian E Carpenter wrote:
 
> Agreed. It could be used for that, but I don't see it as required.
> We aren't dealing with alleged misbehaviour.

Where I come from failure to fulfill the duties of the position is
misbehaviour. I think it would be serious lack of respect for Marshall
to not follow the only documented procedure for removing someone
from a position. After all, he has spent many years contributing
to the IETF, including the definition of the removal procedure.

FWIW, in some sense, this is a good first test case for the
procedure in that I don't sense an inclination by anyone to
oppose the outcome of removal. At the minimum, there should
probably be a simpler procedure for removal in a case like
this where responsibilities have be abandoned. But we don't
have that alternative now, so I think we must follow what
we have already defined.

We might also want to consider a documented procedure
like the 25th ammendment for temporary removal.

David Morris 

From suresh.krishnan@ericsson.com  Wed Oct 24 08:15:14 2012
Return-Path: <suresh.krishnan@ericsson.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0F97F21F88CC for <ietf@ietfa.amsl.com>; Wed, 24 Oct 2012 08:15:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level: 
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1XUXtkGyQeqQ for <ietf@ietfa.amsl.com>; Wed, 24 Oct 2012 08:15:13 -0700 (PDT)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.9]) by ietfa.amsl.com (Postfix) with ESMTP id 2042E21F8A34 for <ietf@ietf.org>; Wed, 24 Oct 2012 08:15:13 -0700 (PDT)
Received: from eusaamw0707.eamcs.ericsson.se ([147.117.20.32]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id q9OFHfcF013220; Wed, 24 Oct 2012 10:18:12 -0500
Received: from [142.133.112.74] (147.117.20.214) by smtps-am.internal.ericsson.com (147.117.20.32) with Microsoft SMTP Server (TLS) id 8.3.279.1; Wed, 24 Oct 2012 11:15:05 -0400
Message-ID: <508805F9.1000606@ericsson.com>
Date: Wed, 24 Oct 2012 11:15:05 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20121011 Thunderbird/16.0.1
MIME-Version: 1.0
To: "t.p." <daedulus@btconnect.com>
Subject: Re: Change in I-D announcement format
References: <4FD845AB.9020505@gmail.com> <D903BF63-043C-400A-90AF-DF962B246540@vigilsec.com> <021c01cdb1eb$71282660$4001a8c0@gateway.2wire.net>
In-Reply-To: <021c01cdb1eb$71282660$4001a8c0@gateway.2wire.net>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Oct 2012 15:15:14 -0000

Hi Tom,

On 10/24/2012 09:28 AM, t.p. wrote:
> And now there seems to be another unannounced change, in that in
> addition to the usual announcement format e-mails, there may also be, or
> may not be, the appearance seems random, of

Not so random. I noticed that the "New Version Notification" mails are 
sent to you if you are

a) A co-author/editor of a newly submitted draft
b) A wg chair for a newly submitted version of a WG document
c) Other situations that do not apply to me :-)

Thanks
Suresh

>
> Subject: New Version Notification -
>
> e-mails.  This may or may not be an improvement, depending on how long
> it takes me to work out what is happening and whether or not I then like
> my conclusion.  And whether or not what I rely on is still available.
>
> Tom Petch


From ian@hixie.ch  Tue Oct 23 14:12:18 2012
Return-Path: <ian@hixie.ch>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E7DA211E80BF for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 14:12:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.503
X-Spam-Level: 
X-Spam-Status: No, score=-2.503 tagged_above=-999 required=5 tests=[AWL=0.096,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DYcJhAQuHLgw for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 14:12:18 -0700 (PDT)
Received: from homiemail-a94.g.dreamhost.com (caibbdcaaaaf.dreamhost.com [208.113.200.5]) by ietfa.amsl.com (Postfix) with ESMTP id 2A48811E80F3 for <ietf@ietf.org>; Tue, 23 Oct 2012 14:12:18 -0700 (PDT)
Received: from homiemail-a94.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a94.g.dreamhost.com (Postfix) with ESMTP id E706F38A071; Tue, 23 Oct 2012 14:12:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=hixie.ch; h=date:from:to :cc:subject:in-reply-to:message-id:references:mime-version: content-type; s=hixie.ch; bh=0NsrLlROcFEkBWfYklg0KGHfyDk=; b=I2g rGMCvv2iiUiszIuKa/bmjpddBTxCgpqie5bnrR+4qX3artdwSltsAllVCLdz8O8m mjWghHZVj2wbydqGBle5e664RHW71hsBFNvn9CoiS8FsQQ9UOkTtrywsZ+VInOiu UCLhz8BGn9XiT+KYs+4ZVxrhwqBNYPCxkJMzJL2A=
Received: from ps20323.dreamhostps.com (ps20323.dreamhost.com [69.163.222.251]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: internal@index.hixie.ch) by homiemail-a94.g.dreamhost.com (Postfix) with ESMTPSA id B1D8938A058;  Tue, 23 Oct 2012 14:12:17 -0700 (PDT)
Date: Tue, 23 Oct 2012 21:12:17 +0000 (UTC)
From: Ian Hickson <ian@hixie.ch>
To: Julian Reschke <julian.reschke@gmx.de>
Subject: Re: websockets in the IETF, was: [whatwg] New URL Standard from Anne van Kesteren on 2012-09-24 (public-whatwg-archive@w3.org from September 2012)
In-Reply-To: <50869B24.2070109@gmx.de>
Message-ID: <Pine.LNX.4.64.1210232104200.2471@ps20323.dreamhostps.com>
References: <50604C1A.7090901@gmx.de> <5060A964.5060001@stpeter.im> <Pine.LNX.4.64.1210172354500.2478@ps20323.dreamhostps.com> <507F5A7E.6040206@arcanedomain.com> <50856E3C.103@gmail.com> <Pine.LNX.4.64.1210221753010.2471@ps20323.dreamhostps.com> <0DBC8A11-319C-4120-975E-7E40FD5818BF@gbiv.com> <Pine.LNX.4.64.1210222137530.2471@ps20323.dreamhostps.com> <5085C4BA.2030505@gmx.de> <Pine.LNX.4.64.1210222220510.2471@ps20323.dreamhostps.com> <CABP7RbfgQrgduOzWaXcYieV3cw_=UoBaCC5e=XF+Y3PMEZoRMw@mail.gmail.com> <Pine.LNX.4.64.1210222300490.2471@ps20323.dreamhostps.com> <85CC064C-7592-4249-ACC9-7B55AAC0D7E7@mnot.net> <Pine.LNX.4.64.1210222325540.2471@ps20323.dreamhostps.com> <5DF21D1C-3A60-4E68-9BBF-16B5B69CFF5D@mnot.net> <Pine.LNX.4.64.1210222346590.2471@ps20323.dreamhostps.com> <50869B24.2070109@gmx.de>
Content-Language: en-GB-hixie
Content-Style-Type: text/css
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Mailman-Approved-At: Wed, 24 Oct 2012 08:37:09 -0700
Cc: IETF Discussion <ietf@ietf.org>, Noah Mendelsohn <nrm@arcanedomain.com>, "Roy T. Fielding" <fielding@gbiv.com>, Jan Algermissen <jan.algermissen@nordsc.com>, URI <uri@w3.org>, Mark Nottingham <mnot@mnot.net>, James M Snell <jasnell@gmail.com>, Tim Bray <tbray@textuality.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Oct 2012 21:12:19 -0000

On Tue, 23 Oct 2012, Julian Reschke wrote:
> On 2012-10-23 01:59, Ian Hickson wrote:
> > ...
> > Whether WebSockets is a good idea or not is besides the point. The point
> > is that the hybi group was not a pleasant experience for me. If I were to
> > be in a position to do Web Sockets again, I would decline the opportunity
> > to do it through the IETF. Doing it through the IETF made the work take a
> > year longer than it would have, made the protocol less secure (the WG
> > removed a number of defense-in-depth features), and made the spec a mess
> > ...
> 
> And, as far as I can tell, fixed a security problem in the original 
> design (which caused some UA implementers to actually disable what they 
> were shipping at that time): 
> <http://w2spconf.com/2011/papers/websocket.pdf>

The security issue in question was already fixed in the draft by the time 
that paper came out.


> > (it's a mishmash of different editing styles). Plus, the group _still_ 
> > hasn't done multiplexing, which some of the vendors said was a prereq 
> > to implementation, something which, prior to the IETF getting 
> > involved, was only 3 to 6 months out on the roadmap. ...
> 
> Indeed, but then wasn't it you arguing *against* having it in the base 
> spec? (see <http://www.ietf.org/mail-archive/web/hybi/current/msg00239.html>)

I was arguing against having it in the first version, which I had planned 
for Q3 2009 IIRC, and was planning on defining it as an extension protocol 
in early 2010 (I even had a strawman ready). The hybi group argued and 
argued and argued and argued and then decided to not have it in the first 
version, which they ended up doing in Q4 2011, and still haven't done the 
extension. So yeah, I stand by my point above.

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'

From jasnell@gmail.com  Tue Oct 23 14:32:15 2012
Return-Path: <jasnell@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8871E11E8102 for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 14:32:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.802
X-Spam-Level: 
X-Spam-Status: No, score=-4.802 tagged_above=-999 required=5 tests=[AWL=-1.204, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lpXkePU39cFD for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 14:32:14 -0700 (PDT)
Received: from mail-qa0-f51.google.com (mail-qa0-f51.google.com [209.85.216.51]) by ietfa.amsl.com (Postfix) with ESMTP id 819EA11E80DC for <ietf@ietf.org>; Tue, 23 Oct 2012 14:32:14 -0700 (PDT)
Received: by mail-qa0-f51.google.com with SMTP id j40so609366qab.10 for <ietf@ietf.org>; Tue, 23 Oct 2012 14:32:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=1FBcYdIIflAHBm959E87HZfLs/3mygOo8Os1iGtEFOE=; b=C7PMNCHHR6P34KZZwKoigZhDZcHPwt1Y1fLPRyHgFLTYtZba/IZD43zazkaiw6oytS Rs0ANlR9N11PECUCYmujaJB6CCuDq3W4jc4GKFH36fTltWQFjG1xCql9y4poeh82CkeD 8CQ2W5aXTEQFDYNDe1oWxdKfyszKPbe5pIiv9kyuOmR1OtTVSuLI/vciHG0tbwL6Tjn0 w8/da3AuNtPRmru55vxZ+08POB6OVfo56Ta5t56nGvKJNFlFJjQkzcYYXCx4BdrTDfKS mQaRAROevT7tK+zR5vVpfuKjuHd6GeTPB6E8bjojUg3AI9kcv73j0gAbxLH8a4HOAJIm Xc8A==
MIME-Version: 1.0
Received: by 10.224.220.146 with SMTP id hy18mr6304582qab.5.1351027933902; Tue, 23 Oct 2012 14:32:13 -0700 (PDT)
Received: by 10.49.81.230 with HTTP; Tue, 23 Oct 2012 14:32:13 -0700 (PDT)
Received: by 10.49.81.230 with HTTP; Tue, 23 Oct 2012 14:32:13 -0700 (PDT)
In-Reply-To: <Pine.LNX.4.64.1210232104200.2471@ps20323.dreamhostps.com>
References: <50604C1A.7090901@gmx.de> <5060A964.5060001@stpeter.im> <Pine.LNX.4.64.1210172354500.2478@ps20323.dreamhostps.com> <507F5A7E.6040206@arcanedomain.com> <50856E3C.103@gmail.com> <Pine.LNX.4.64.1210221753010.2471@ps20323.dreamhostps.com> <0DBC8A11-319C-4120-975E-7E40FD5818BF@gbiv.com> <Pine.LNX.4.64.1210222137530.2471@ps20323.dreamhostps.com> <5085C4BA.2030505@gmx.de> <Pine.LNX.4.64.1210222220510.2471@ps20323.dreamhostps.com> <CABP7RbfgQrgduOzWaXcYieV3cw_=UoBaCC5e=XF+Y3PMEZoRMw@mail.gmail.com> <Pine.LNX.4.64.1210222300490.2471@ps20323.dreamhostps.com> <85CC064C-7592-4249-ACC9-7B55AAC0D7E7@mnot.net> <Pine.LNX.4.64.1210222325540.2471@ps20323.dreamhostps.com> <5DF21D1C-3A60-4E68-9BBF-16B5B69CFF5D@mnot.net> <Pine.LNX.4.64.1210222346590.2471@ps20323.dreamhostps.com> <50869B24.2070109@gmx.de> <Pine.LNX.4.64.1210232104200.2471@ps20323.dreamhostps.com>
Date: Tue, 23 Oct 2012 14:32:13 -0700
Message-ID: <CABP7Rbfk_oT_oXERcYYXfb+=aztWdvNgkfeEdvhKtBBnJbqH5g@mail.gmail.com>
Subject: Re: websockets in the IETF, was: [whatwg] New URL Standard from Anne van Kesteren on 2012-09-24 (public-whatwg-archive@w3.org from September 2012)
From: James M Snell <jasnell@gmail.com>
To: Ian Hickson <ian@hixie.ch>
Content-Type: multipart/alternative; boundary=20cf3074b6e014f77b04ccc0b442
X-Mailman-Approved-At: Wed, 24 Oct 2012 08:37:10 -0700
Cc: IETF Discussion <ietf@ietf.org>, Noah Mendelsohn <nrm@arcanedomain.com>, "Roy T. Fielding" <fielding@gbiv.com>, Jan Algermissen <jan.algermissen@nordsc.com>, Mark Nottingham <mnot@mnot.net>, Julian Reschke <julian.reschke@gmx.de>, URI <uri@w3.org>, Tim Bray <tbray@textuality.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Oct 2012 21:32:15 -0000

--20cf3074b6e014f77b04ccc0b442
Content-Type: text/plain; charset=UTF-8

It should be quite clear to everyone that the horse is quite dead at this
point. Any further beating is entirely unnecessary. So let's wrap it up
with this: the whatwg's spec language around urls has the potential to
cause confusion among implementers, so please consider reworking that
language to avoid such confusion. Period, end of story.
 On Oct 23, 2012 2:12 PM, "Ian Hickson" <ian@hixie.ch> wrote:

> On Tue, 23 Oct 2012, Julian Reschke wrote:
> > On 2012-10-23 01:59, Ian Hickson wrote:
> > > ...
> > > Whether WebSockets is a good idea or not is besides the point. The
> point
> > > is that the hybi group was not a pleasant experience for me. If I were
> to
> > > be in a position to do Web Sockets again, I would decline the
> opportunity
> > > to do it through the IETF. Doing it through the IETF made the work
> take a
> > > year longer than it would have, made the protocol less secure (the WG
> > > removed a number of defense-in-depth features), and made the spec a
> mess
> > > ...
> >
> > And, as far as I can tell, fixed a security problem in the original
> > design (which caused some UA implementers to actually disable what they
> > were shipping at that time):
> > <http://w2spconf.com/2011/papers/websocket.pdf>
>
> The security issue in question was already fixed in the draft by the time
> that paper came out.
>
>
> > > (it's a mishmash of different editing styles). Plus, the group _still_
> > > hasn't done multiplexing, which some of the vendors said was a prereq
> > > to implementation, something which, prior to the IETF getting
> > > involved, was only 3 to 6 months out on the roadmap. ...
> >
> > Indeed, but then wasn't it you arguing *against* having it in the base
> > spec? (see <
> http://www.ietf.org/mail-archive/web/hybi/current/msg00239.html>)
>
> I was arguing against having it in the first version, which I had planned
> for Q3 2009 IIRC, and was planning on defining it as an extension protocol
> in early 2010 (I even had a strawman ready). The hybi group argued and
> argued and argued and argued and then decided to not have it in the first
> version, which they ended up doing in Q4 2011, and still haven't done the
> extension. So yeah, I stand by my point above.
>
> --
> Ian Hickson               U+1047E                )\._.,--....,'``.    fL
> http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
> Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
>

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

<p>It should be quite clear to everyone that the horse is quite dead at thi=
s point. Any further beating is entirely unnecessary. So let&#39;s wrap it =
up with this: the whatwg&#39;s spec language around urls has the potential =
to cause confusion among implementers, so please consider reworking that la=
nguage to avoid such confusion. Period, end of story. <br>

</p>
<div class=3D"gmail_quote">On Oct 23, 2012 2:12 PM, &quot;Ian Hickson&quot;=
 &lt;<a href=3D"mailto:ian@hixie.ch">ian@hixie.ch</a>&gt; wrote:<br type=3D=
"attribution"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex">
On Tue, 23 Oct 2012, Julian Reschke wrote:<br>
&gt; On 2012-10-23 01:59, Ian Hickson wrote:<br>
&gt; &gt; ...<br>
&gt; &gt; Whether WebSockets is a good idea or not is besides the point. Th=
e point<br>
&gt; &gt; is that the hybi group was not a pleasant experience for me. If I=
 were to<br>
&gt; &gt; be in a position to do Web Sockets again, I would decline the opp=
ortunity<br>
&gt; &gt; to do it through the IETF. Doing it through the IETF made the wor=
k take a<br>
&gt; &gt; year longer than it would have, made the protocol less secure (th=
e WG<br>
&gt; &gt; removed a number of defense-in-depth features), and made the spec=
 a mess<br>
&gt; &gt; ...<br>
&gt;<br>
&gt; And, as far as I can tell, fixed a security problem in the original<br=
>
&gt; design (which caused some UA implementers to actually disable what the=
y<br>
&gt; were shipping at that time):<br>
&gt; &lt;<a href=3D"http://w2spconf.com/2011/papers/websocket.pdf" target=
=3D"_blank">http://w2spconf.com/2011/papers/websocket.pdf</a>&gt;<br>
<br>
The security issue in question was already fixed in the draft by the time<b=
r>
that paper came out.<br>
<br>
<br>
&gt; &gt; (it&#39;s a mishmash of different editing styles). Plus, the grou=
p _still_<br>
&gt; &gt; hasn&#39;t done multiplexing, which some of the vendors said was =
a prereq<br>
&gt; &gt; to implementation, something which, prior to the IETF getting<br>
&gt; &gt; involved, was only 3 to 6 months out on the roadmap. ...<br>
&gt;<br>
&gt; Indeed, but then wasn&#39;t it you arguing *against* having it in the =
base<br>
&gt; spec? (see &lt;<a href=3D"http://www.ietf.org/mail-archive/web/hybi/cu=
rrent/msg00239.html" target=3D"_blank">http://www.ietf.org/mail-archive/web=
/hybi/current/msg00239.html</a>&gt;)<br>
<br>
I was arguing against having it in the first version, which I had planned<b=
r>
for Q3 2009 IIRC, and was planning on defining it as an extension protocol<=
br>
in early 2010 (I even had a strawman ready). The hybi group argued and<br>
argued and argued and argued and then decided to not have it in the first<b=
r>
version, which they ended up doing in Q4 2011, and still haven&#39;t done t=
he<br>
extension. So yeah, I stand by my point above.<br>
<br>
--<br>
Ian Hickson =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 U+1047E =C2=A0=
 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0)\._.,--....,&#39;``. =C2=
=A0 =C2=A0fL<br>
<a href=3D"http://ln.hixie.ch/" target=3D"_blank">http://ln.hixie.ch/</a> =
=C2=A0 =C2=A0 =C2=A0 U+263A =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0/, =C2=A0 _.. \ =C2=A0 _\ =C2=A0;`._ ,.<br>
Things that are impossible just take longer. =C2=A0 `._.-(,_..&#39;--(,_..&=
#39;`-.;.&#39;<br>
</blockquote></div>

--20cf3074b6e014f77b04ccc0b442--

From ian@hixie.ch  Tue Oct 23 14:34:06 2012
Return-Path: <ian@hixie.ch>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D2E7211E8105 for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 14:34:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.511
X-Spam-Level: 
X-Spam-Status: No, score=-2.511 tagged_above=-999 required=5 tests=[AWL=0.088,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bqHWCuQ10yAj for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 14:34:06 -0700 (PDT)
Received: from homiemail-a48.g.dreamhost.com (caibbdcaaaaf.dreamhost.com [208.113.200.5]) by ietfa.amsl.com (Postfix) with ESMTP id 3262711E80DC for <ietf@ietf.org>; Tue, 23 Oct 2012 14:34:05 -0700 (PDT)
Received: from homiemail-a48.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a48.g.dreamhost.com (Postfix) with ESMTP id 7300D4F805C; Tue, 23 Oct 2012 14:34:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=hixie.ch; h=date:from:to :cc:subject:in-reply-to:message-id:references:mime-version: content-type; s=hixie.ch; bh=v4sa8N0BWBJLG7PgP/DFLj85cIo=; b=SbN lCyCvsty6V1LcPx+VopidOoHdtMLObFMeHIEt6UTAhau3qU0T9YdWea7rQbxGThV 3cB7AjQ6smXxbrvMWNpsikXmG8oR5096w2E0gzg7IKX0sgw6IsKdi5tdq1MbUOn8 hgAsGRe7XxIJfo4Egft7oji3XS1Zd418dgAItNLo=
Received: from ps20323.dreamhostps.com (ps20323.dreamhost.com [69.163.222.251]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: internal@index.hixie.ch) by homiemail-a48.g.dreamhost.com (Postfix) with ESMTPSA id 6AEAD4F8057;  Tue, 23 Oct 2012 14:34:05 -0700 (PDT)
Date: Tue, 23 Oct 2012 21:34:05 +0000 (UTC)
From: Ian Hickson <ian@hixie.ch>
To: Ted Hardie <ted.ietf@gmail.com>
Subject: Re: [whatwg] New URL Standard from Anne van Kesteren on 2012-09-24 (public-whatwg-archive@w3.org from September 2012)
In-Reply-To: <CA+9kkMDpEZCvcG1DJd=O1qPNV+=+GTBeN+CGndUe51Xym_A9sg@mail.gmail.com>
Message-ID: <Pine.LNX.4.64.1210232115210.2471@ps20323.dreamhostps.com>
References: <50604C1A.7090901@gmx.de> <5060A964.5060001@stpeter.im> <Pine.LNX.4.64.1210172354500.2478@ps20323.dreamhostps.com> <507F5A7E.6040206@arcanedomain.com> <50856E3C.103@gmail.com> <Pine.LNX.4.64.1210221753010.2471@ps20323.dreamhostps.com> <0DBC8A11-319C-4120-975E-7E40FD5818BF@gbiv.com> <Pine.LNX.4.64.1210222137530.2471@ps20323.dreamhostps.com> <CA+9kkMDpEZCvcG1DJd=O1qPNV+=+GTBeN+CGndUe51Xym_A9sg@mail.gmail.com>
Content-Language: en-GB-hixie
Content-Style-Type: text/css
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Mailman-Approved-At: Wed, 24 Oct 2012 08:37:10 -0700
Cc: URI <uri@w3.org>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Oct 2012 21:34:06 -0000

On Tue, 23 Oct 2012, Ted Hardie wrote:
> On Mon, Oct 22, 2012 at 2:46 PM, Ian Hickson <ian@hixie.ch> wrote:
> > On Mon, 22 Oct 2012, Julian Reschke wrote:
> >> >
> >> > I couldn't agree more! We've been waiting for four years for the 
> >> > URI working group to get their act together and fix the URL mess. 
> >> > Nothing has happened. We lost patience and are now doing it 
> >> > ourselves. ...
> >>
> >> Clarifying: there is no URI Working Group, and as far as I can tell,
> >
> > Whoever. The people complaining that it should be done at the IETF 
> > haven't done any work. That's the complaint. Until they do the work,
> 
> Handing things off to the IETF and saying "please go do this work" has a 
> very low success rate, because that's not how the IETF works.

Ok, but "we disagree with you, do it differently" is not how it works 
either.


> The IETF works by bringing together folks interested in solving a 
> particular problem and putting them in a larger context

The problem here is that the bulk of the people here don't seem interested 
in solving this particular problem. In fact, many don't seem to even think 
that there is a problem to solve.


> In this case, the concern is that defining what you are doing as a 
> revision of the URL standard outside the IETF will:
> 
> * lose that larger context

By which I presume you mean "you'll miss good feedback".

My experience with the Web Sockets work at the IETF is that we got way 
better feedback (in terms of technical usefulness, relevance, and style) 
when it was at the WHATWG than when it was at the IETF. All the good 
feedback we got at the IETF was from people who were already participating 
in the WHATWG.

So I'm not sure that this is a given.


> * use a process which has a bias toward browser viewpoints, which raises 
> concerns about trade-offs outside that space

Working at the IETF results in the opposite concern, of course.

You're all welcome to participate in the WHATWG.


> * generate a fork, either directly or in the creation of two communities 
> which understand URL to be either a subset of URI in the STD 66 sense or 
> the "input string to web identifier" sense that Anne's work uses.

If Anne does a good job, then STD 66 can just be updated to contain Anne's 
work, and then there's no fork to worry about. If Anne does a poor job, 
then people will ignore it, and there's still no fork to worry about. The 
only way there could be a problem is if Anne does a good job, so people 
pay attention to it, but the IETF for political reasons refuses to 
acknowledge it. That's up to the IETF.


> It's tedious when people say "you should come here and do the work", and 
> I apologize that I'm about to say it.  But for work which redefines IETF 
> standards, the IETF is really the place to do it, and preserving that 
> context is important to making sure that the communities of use retain a 
> single standard.  I share your frustration with the pace of work on 
> related topics, but I urge you to put energy into the process rather 
> than simply appropriating the term.

The problem is that we have lost hope that the IETF is somewhere where 
this work could even take place. There's too much stop energy (just look 
at this thread -- Tim just said we were all wasting our time and should 
all shut up!).

But suppose we did try. Let's in fact try: Hi guys, we need to fix STD 66 
because it doesn't define error handling. Also it seems to be about time 
to merge IRIs and URIs together since implementing IRIs on top of URIs 
leads to a confusing implementation experience. We can call the result 
just "URLs" since that's what the majority of people call these things. 
Anne has a proposal for how to do it:

   http://url.spec.whatwg.org/

Does anyone object to us updating STD 66 to using this once it's ready? 
How do we go about it?


> If you choose not call what you're doing a "URL" but by some other
> term ("fleen" is my favorite), then the issue does not arise

Since the IETF doesn't call it a URL anyway, I don't see the problem with 
terminology.

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'

From stpeter@stpeter.im  Tue Oct 23 14:36:55 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 B90E111E80DC for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 14:36:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id E6HmiDrxYx11 for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 14:36:55 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 5279211E80D9 for <ietf@ietf.org>; Tue, 23 Oct 2012 14:36:55 -0700 (PDT)
Received: from [172.16.0.126] (unknown [199.223.125.116]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 581D7400FA; Tue, 23 Oct 2012 15:39:52 -0600 (MDT)
Message-ID: <50870DF4.4080906@stpeter.im>
Date: Tue, 23 Oct 2012 14:36:52 -0700
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:16.0) Gecko/20121010 Thunderbird/16.0.1
MIME-Version: 1.0
To: James M Snell <jasnell@gmail.com>
Subject: Re: websockets in the IETF, was: [whatwg] New URL Standard from Anne van Kesteren on 2012-09-24 (public-whatwg-archive@w3.org from September 2012)
References: <50604C1A.7090901@gmx.de> <5060A964.5060001@stpeter.im> <Pine.LNX.4.64.1210172354500.2478@ps20323.dreamhostps.com> <507F5A7E.6040206@arcanedomain.com> <50856E3C.103@gmail.com> <Pine.LNX.4.64.1210221753010.2471@ps20323.dreamhostps.com> <0DBC8A11-319C-4120-975E-7E40FD5818BF@gbiv.com> <Pine.LNX.4.64.1210222137530.2471@ps20323.dreamhostps.com> <5085C4BA.2030505@gmx.de> <Pine.LNX.4.64.1210222220510.2471@ps20323.dreamhostps.com> <CABP7RbfgQrgduOzWaXcYieV3cw_=UoBaCC5e=XF+Y3PMEZoRMw@mail.gmail.com> <Pine.LNX.4.64.1210222300490.2471@ps20323.dreamhostps.com> <85CC064C-7592-4249-ACC9-7B55AAC0D7E7@mnot.net> <Pine.LNX.4.64.1210222325540.2471@ps20323.dreamhostps.com> <5DF21D1C-3A60-4E68-9BBF-16B5B69CFF5D@mnot.net> <Pine.LNX.4.64.1210222346590.2471@ps20323.dreamhostps.com> <50869B24.2070109@gmx.de> <Pine.LNX.4.64.1210232104200.2471@ps20323.dreamhostps.com> <CABP7Rbfk_oT_oXERcYYXfb+=aztWdvNgkfeEdvhKtBBnJbqH5g@mail.gmail.com>
In-Reply-To: <CABP7Rbfk_oT_oXERcYYXfb+=aztWdvNgkfeEdvhKtBBnJbqH5g@mail.gmail.com>
X-Enigmail-Version: 1.4.5
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Wed, 24 Oct 2012 08:37:10 -0700
Cc: IETF Discussion <ietf@ietf.org>, Noah Mendelsohn <nrm@arcanedomain.com>, "Roy T. Fielding" <fielding@gbiv.com>, Jan Algermissen <jan.algermissen@nordsc.com>, Mark Nottingham <mnot@mnot.net>, Julian Reschke <julian.reschke@gmx.de>, URI <uri@w3.org>, Tim Bray <tbray@textuality.com>, Ian Hickson <ian@hixie.ch>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Oct 2012 21:36:55 -0000

+1

On 10/23/12 2:32 PM, James M Snell wrote:
> It should be quite clear to everyone that the horse is quite dead at
> this point. Any further beating is entirely unnecessary. So let's wrap
> it up with this: the whatwg's spec language around urls has the
> potential to cause confusion among implementers, so please consider
> reworking that language to avoid such confusion. Period, end of story.


From jan.algermissen@nordsc.com  Tue Oct 23 14:51:20 2012
Return-Path: <jan.algermissen@nordsc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2B6441F0C92 for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 14:51:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.696
X-Spam-Level: 
X-Spam-Status: No, score=-2.696 tagged_above=-999 required=5 tests=[AWL=-0.447, BAYES_00=-2.599, HELO_EQ_DE=0.35]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lQ70OIeaadLs for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 14:51:19 -0700 (PDT)
Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.17.9]) by ietfa.amsl.com (Postfix) with ESMTP id 4BCA911E8099 for <ietf@ietf.org>; Tue, 23 Oct 2012 14:51:17 -0700 (PDT)
Received: from [192.168.2.103] (p548FAD1A.dip.t-dialin.net [84.143.173.26]) by mrelayeu.kundenserver.de (node=mrbap2) with ESMTP (Nemesis) id 0M1hZS-1TB30t32mw-00t0Bd; Tue, 23 Oct 2012 23:51:13 +0200
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: [whatwg] New URL Standard from Anne van Kesteren on 2012-09-24 (public-whatwg-archive@w3.org from September 2012)
From: Jan Algermissen <jan.algermissen@nordsc.com>
In-Reply-To: <Pine.LNX.4.64.1210232115210.2471@ps20323.dreamhostps.com>
Date: Tue, 23 Oct 2012 23:51:12 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <15E1D98B-8883-4936-81A9-174E1323683C@nordsc.com>
References: <50604C1A.7090901@gmx.de> <5060A964.5060001@stpeter.im> <Pine.LNX.4.64.1210172354500.2478@ps20323.dreamhostps.com> <507F5A7E.6040206@arcanedomain.com> <50856E3C.103@gmail.com> <Pine.LNX.4.64.1210221753010.2471@ps20323.dreamhostps.com> <0DBC8A11-319C-4120-975E-7E40FD5818BF@gbiv.com> <Pine.LNX.4.64.1210222137530.2471@ps20323.dreamhostps.com> <CA+9kkMDpEZCvcG1DJd=O1qPNV+=+GTBeN+CGndUe51Xym_A9sg@mail.gmail.com> <Pine.LNX.4.64.1210232115210.2471@ps20323.dreamhostps.com>
To: Ian Hickson <ian@hixie.ch>
X-Mailer: Apple Mail (2.1499)
X-Provags-ID: V02:K0:NdNMEzg6mgjjTyfrdaUe5ShWHZrmf4OS6+JQ62xs2hI jomLOrRMmX4eO8fSm2YfWDgQUtjlOxwa7K5ity4maUS+Vc4tC0 a6ZVZ21GlmwJVn2OxrH9iC5hGbV5TnsJJaLkxgEDpz/ucvuVpM gUjxkpjR5EWsvLonfpLLoGa8xiq6gVYAJRzfj/DdcdgX7o/bo8 SDUXF2cKxi0lbQ2w0DP6zB2s/+tGSJBxYAdMZKbeR8HFPTA47f HsM3pKueouH2vonRW/PAaub9ly1Xhv2bRbNslz5jvaCgNF7R1s w7slGc8AHPDCTR4Rt9JKBgW3MWM3geaOvOwvJe7YUcWXdjcbOy LV9PKoh4yrXz+DyGAoMqNFaZWu0DDKGYsipGW+FHCefIAUPRTs HjStGpLc//jBw==
X-Mailman-Approved-At: Wed, 24 Oct 2012 08:37:10 -0700
Cc: Ted Hardie <ted.ietf@gmail.com>, URI <uri@w3.org>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Oct 2012 21:51:20 -0000

On Oct 23, 2012, at 11:34 PM, Ian Hickson <ian@hixie.ch> wrote:

>  Let's in fact try: Hi guys, we need to fix STD 66=20
> because it doesn't define error handling.=20

Help me, I am just not getting it:

Why do you insist on 'fixing STD 66'?

What is the reason you are not willing to reframe the problem to 'fixing =
how we get from the provided string -the input to the reference =
construction process- to a STD-66-valid result'?

To me this is really what you are aiming at and dropping the 'fix the =
URI spec' language would get everyone on board immediately in my =
perception.


Jan


From ian@hixie.ch  Tue Oct 23 15:43:24 2012
Return-Path: <ian@hixie.ch>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 37E661F0C95 for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 15:43:24 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Zkxr7+3BVenY for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 15:43:23 -0700 (PDT)
Received: from homiemail-a47.g.dreamhost.com (caibbdcaaaaf.dreamhost.com [208.113.200.5]) by ietfa.amsl.com (Postfix) with ESMTP id 725E81F0C3A for <ietf@ietf.org>; Tue, 23 Oct 2012 15:43:23 -0700 (PDT)
Received: from homiemail-a47.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a47.g.dreamhost.com (Postfix) with ESMTP id 8958B28406E; Tue, 23 Oct 2012 15:43:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=hixie.ch; h=date:from:to :cc:subject:in-reply-to:message-id:references:mime-version: content-type; s=hixie.ch; bh=KFoahIh+HE7Xu3u7HFWOAQD5iDc=; b=1yD MtIzZDtS2N9r+AXZj3IDFyEBYYfzgFdaiNz+USv5xia39BL/T2dJkfoO9nX+fqWh oRvgqONy8MsKXuZRElHQ+P3FYRNrjia+3qULvYRMWUEg/TVI+tyWXT7vvAtMnn5l CayNEnz0JL3y7i56f1NBNx0as4ttRMKUUQXxRsyI=
Received: from ps20323.dreamhostps.com (ps20323.dreamhost.com [69.163.222.251]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: internal@index.hixie.ch) by homiemail-a47.g.dreamhost.com (Postfix) with ESMTPSA id 6A58B28405C;  Tue, 23 Oct 2012 15:43:23 -0700 (PDT)
Date: Tue, 23 Oct 2012 22:43:22 +0000 (UTC)
From: Ian Hickson <ian@hixie.ch>
To: Jan Algermissen <jan.algermissen@nordsc.com>
Subject: Re: [whatwg] New URL Standard from Anne van Kesteren on 2012-09-24 (public-whatwg-archive@w3.org from September 2012)
In-Reply-To: <15E1D98B-8883-4936-81A9-174E1323683C@nordsc.com>
Message-ID: <Pine.LNX.4.64.1210232234590.2471@ps20323.dreamhostps.com>
References: <50604C1A.7090901@gmx.de> <5060A964.5060001@stpeter.im> <Pine.LNX.4.64.1210172354500.2478@ps20323.dreamhostps.com> <507F5A7E.6040206@arcanedomain.com> <50856E3C.103@gmail.com> <Pine.LNX.4.64.1210221753010.2471@ps20323.dreamhostps.com> <0DBC8A11-319C-4120-975E-7E40FD5818BF@gbiv.com> <Pine.LNX.4.64.1210222137530.2471@ps20323.dreamhostps.com> <CA+9kkMDpEZCvcG1DJd=O1qPNV+=+GTBeN+CGndUe51Xym_A9sg@mail.gmail.com> <Pine.LNX.4.64.1210232115210.2471@ps20323.dreamhostps.com> <15E1D98B-8883-4936-81A9-174E1323683C@nordsc.com>
Content-Language: en-GB-hixie
Content-Style-Type: text/css
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Mailman-Approved-At: Wed, 24 Oct 2012 08:37:10 -0700
Cc: Ted Hardie <ted.ietf@gmail.com>, URI <uri@w3.org>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Oct 2012 22:43:24 -0000

On Tue, 23 Oct 2012, Jan Algermissen wrote:
> On Oct 23, 2012, at 11:34 PM, Ian Hickson <ian@hixie.ch> wrote:
> >
> > Let's in fact try: Hi guys, we need to fix STD 66 because it doesn't 
> > define error handling.
> 
> Help me, I am just not getting it:
> 
> Why do you insist on 'fixing STD 66'?
> 
> What is the reason you are not willing to reframe the problem to 'fixing 
> how we get from the provided string -the input to the reference 
> construction process- to a STD-66-valid result'?

Because that's not a good way to write specs. Implementors shouldn't have 
to read three separate specs to implement one algorithm. The definition 
for Base64 isn't spread into tree separate RFCs. You don't put the HTML 
parser in a different spec than the HTML elements.

A spec for this kind of thing should define the following:

 - The conformance requirements for authors so that they can use the 
   technology in a manner that avoids likely pitfalls

 - A processing model for each relevant implementation conformance class 
   (software) that defines how you take the input and use it

In the case of these string, that means, to a first approximation:

 - A definition of what the valid syntax of these strings is.

 - A definition of how you get from one of these strings, whether valid or 
   not, to the information you need to process it, in particular, for 
   e.g. strings that reference specific files:
    - the scheme (what protocol you're going to be using)
    - the hostname and port of the remote host
    - the path and query string to pass to that host
    - the fragment identifier

So there should just be one spec, not three (IRIs, URIs, and the error 
handling).

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'

From ian@hixie.ch  Tue Oct 23 15:47:56 2012
Return-Path: <ian@hixie.ch>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B37421F0C96 for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 15:47:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.462
X-Spam-Level: 
X-Spam-Status: No, score=-2.462 tagged_above=-999 required=5 tests=[AWL=0.007,  BAYES_00=-2.599, SARE_RMML_Stock10=0.13]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id APvvgvu-QLWT for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 15:47:56 -0700 (PDT)
Received: from homiemail-a83.g.dreamhost.com (caibbdcaaaaf.dreamhost.com [208.113.200.5]) by ietfa.amsl.com (Postfix) with ESMTP id 2889B1F0C3A for <ietf@ietf.org>; Tue, 23 Oct 2012 15:47:56 -0700 (PDT)
Received: from homiemail-a83.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a83.g.dreamhost.com (Postfix) with ESMTP id A43A65E073; Tue, 23 Oct 2012 15:47:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=hixie.ch; h=date:from:to :cc:subject:in-reply-to:message-id:references:mime-version: content-type; s=hixie.ch; bh=ij2/HRQihS5pslefik/FSAMt2/8=; b=ndo lf9xZkCD3pejcFIWAvmcIhsodrCb+fg+tJHj4iH8//FJDNYsBguqko0ZYk0Dp2Or Db2LZtVy5asEz4aM6kvODnm4X7NVcjDpOm2SWgBsx0KH3TfDFQ+BcVtWeERvuCyN DpsxiwHWWfVAAM/dkL/OdlC3rfSWBWfYhdkmgvxk=
Received: from ps20323.dreamhostps.com (ps20323.dreamhost.com [69.163.222.251]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: internal@index.hixie.ch) by homiemail-a83.g.dreamhost.com (Postfix) with ESMTPSA id 97C8D5E063;  Tue, 23 Oct 2012 15:47:55 -0700 (PDT)
Date: Tue, 23 Oct 2012 22:47:55 +0000 (UTC)
From: Ian Hickson <ian@hixie.ch>
To: Ted Hardie <ted.ietf@gmail.com>
Subject: Re: [whatwg] New URL Standard from Anne van Kesteren on 2012-09-24 (public-whatwg-archive@w3.org from September 2012)
In-Reply-To: <CA+9kkMBg=hxz=yRYfYA5Hkwp-4ODFBnpK_qctCMB_oEHLPP49g@mail.gmail.com>
Message-ID: <Pine.LNX.4.64.1210232243510.2471@ps20323.dreamhostps.com>
References: <50604C1A.7090901@gmx.de> <5060A964.5060001@stpeter.im> <Pine.LNX.4.64.1210172354500.2478@ps20323.dreamhostps.com> <507F5A7E.6040206@arcanedomain.com> <50856E3C.103@gmail.com> <Pine.LNX.4.64.1210221753010.2471@ps20323.dreamhostps.com> <0DBC8A11-319C-4120-975E-7E40FD5818BF@gbiv.com> <Pine.LNX.4.64.1210222137530.2471@ps20323.dreamhostps.com> <CA+9kkMDpEZCvcG1DJd=O1qPNV+=+GTBeN+CGndUe51Xym_A9sg@mail.gmail.com> <Pine.LNX.4.64.1210232115210.2471@ps20323.dreamhostps.com> <CA+9kkMBg=hxz=yRYfYA5Hkwp-4ODFBnpK_qctCMB_oEHLPP49g@mail.gmail.com>
Content-Language: en-GB-hixie
Content-Style-Type: text/css
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Mailman-Approved-At: Wed, 24 Oct 2012 08:37:10 -0700
Cc: URI <uri@w3.org>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Oct 2012 22:47:56 -0000

On Tue, 23 Oct 2012, Ted Hardie wrote:
> 
> Unless you get buy-in from the community that produced RFC 3986 and RFC 
> 3987, the production of this document *will* result in a fork, and that 
> is damaging to the Internet.

I'm trying to work with y'all to see how we can update these specs instead 
of having to do it elsewhere.


> I urge you to pick a different term (several far more useful ones than 
> fleen have been suggested) and avoid this needless conflict.

What term we use isn't going to have any effect on whether it harms the 
Internet. If curl decides it should use WHATWGRLs or whatever and wget 
decides it should use IRIs or whatever, and the specs aren't compatible, 
then wget and curl won't interoperate.

Then again, they already don't interoperate -- that's the problem we're 
trying to fix -- so maybe the fork won't harm the Internet any more than 
STD 66 already is. Might even help matters, if curl and wget both decide 
to follow the WHATWGRLs spec (or whatever), instead of STD 66, and as a 
result start interoperating.

$ curl 'http://example.com/a b' # fetches "/a b" from example.com
$ wget 'http://example.com/a b' # fetches "/a%20b" from example.com

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'

From jan.algermissen@nordsc.com  Tue Oct 23 15:52:45 2012
Return-Path: <jan.algermissen@nordsc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A0FBE1F0C95 for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 15:52:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.646
X-Spam-Level: 
X-Spam-Status: No, score=-2.646 tagged_above=-999 required=5 tests=[AWL=-0.397, BAYES_00=-2.599, HELO_EQ_DE=0.35]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TMoPCV7IMNJP for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 15:52:44 -0700 (PDT)
Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.17.8]) by ietfa.amsl.com (Postfix) with ESMTP id 52AC21F0C3A for <ietf@ietf.org>; Tue, 23 Oct 2012 15:52:44 -0700 (PDT)
Received: from [192.168.2.103] (p548FAD1A.dip.t-dialin.net [84.143.173.26]) by mrelayeu.kundenserver.de (node=mreu2) with ESMTP (Nemesis) id 0MIAjy-1TRKVC3okw-004OYd; Wed, 24 Oct 2012 00:52:41 +0200
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: [whatwg] New URL Standard from Anne van Kesteren on 2012-09-24 (public-whatwg-archive@w3.org from September 2012)
From: Jan Algermissen <jan.algermissen@nordsc.com>
In-Reply-To: <Pine.LNX.4.64.1210232234590.2471@ps20323.dreamhostps.com>
Date: Wed, 24 Oct 2012 00:52:40 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <8CC5FA04-2F61-408F-AED5-792E086E9BA0@nordsc.com>
References: <50604C1A.7090901@gmx.de> <5060A964.5060001@stpeter.im> <Pine.LNX.4.64.1210172354500.2478@ps20323.dreamhostps.com> <507F5A7E.6040206@arcanedomain.com> <50856E3C.103@gmail.com> <Pine.LNX.4.64.1210221753010.2471@ps20323.dreamhostps.com> <0DBC8A11-319C-4120-975E-7E40FD5818BF@gbiv.com> <Pine.LNX.4.64.1210222137530.2471@ps20323.dreamhostps.com> <CA+9kkMDpEZCvcG1DJd=O1qPNV+=+GTBeN+CGndUe51Xym_A9sg@mail.gmail.com> <Pine.LNX.4.64.1210232115210.2471@ps20323.dreamhostps.com> <15E1D98B-8883-4936-81A9-174E1323683C@nordsc.com> <Pine.LNX.4.64.1210232234590.2471@ps20323.dreamhostps.com>
To: Ian Hickson <ian@hixie.ch>
X-Mailer: Apple Mail (2.1499)
X-Provags-ID: V02:K0:SUm83kQs02Oxz12SR6kBrY48ScbXHt78CvBPgL2E8DB Vl7nyzkZNgwekNA5F0/U2u/E5U5veNmDVT8xi0xncrQgAEYxPo D50hpntDmPEU3YJdTNzhyDLLc8oGwH1T//kbjm0JzJXTn2dsPx LTlYxj0PSEW1eUQB6wKDE3AXm62/yqX43+GNdqJBn8vua+CEuh dXYx4ESjJla2hO4Ez57IWrU+Lvy7Jpoahm18EmfgtoYbvJ7OTY Sh4qVMkd0khU/NggdZ57q7JgclzTslzIkrXflq4BGgUpPqn6t+ LweJxZn/yJkiYwXaaI107CyTY1VP+VUEcf2/5s9PCWOSwF9Kg+ dHF4nCGhBZPiWSbc0CNVb9Cfng7s5Vg2KWlwuPYRNCJTuNQFrw 3SjBrWJSLbrrw==
X-Mailman-Approved-At: Wed, 24 Oct 2012 08:37:10 -0700
Cc: Ted Hardie <ted.ietf@gmail.com>, URI <uri@w3.org>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Oct 2012 22:52:45 -0000

On Oct 24, 2012, at 12:43 AM, Ian Hickson <ian@hixie.ch> wrote:

> On Tue, 23 Oct 2012, Jan Algermissen wrote:
>> On Oct 23, 2012, at 11:34 PM, Ian Hickson <ian@hixie.ch> wrote:
>>>=20
>>> Let's in fact try: Hi guys, we need to fix STD 66 because it doesn't=20=

>>> define error handling.
>>=20
>> Help me, I am just not getting it:
>>=20
>> Why do you insist on 'fixing STD 66'?
>>=20
>> What is the reason you are not willing to reframe the problem to =
'fixing=20
>> how we get from the provided string -the input to the reference=20
>> construction process- to a STD-66-valid result'?
>=20
> Because that's not a good way to write specs. Implementors shouldn't =
have=20
> to read three separate specs to implement one algorithm. The =
definition=20
> for Base64 isn't spread into tree separate RFCs. You don't put the =
HTML=20
> parser in a different spec than the HTML elements.
>=20
> A spec for this kind of thing should define the following:

Then, how about going from 'fixing STD 66' to

'augmenting STD 66 with how we get from the provided string -the input =
to the reference construction process- to a valid URI'?


(Personally, I do not see any problems with having one spec defining the =
valid output and one spec defining how to get from input to valid =
output. But that is a discussion that can be easily separated from the =
current one.)

What matters is that nothing of the existing URI spec *changes*.

Can you agree on that?

Jan


>=20
> - The conformance requirements for authors so that they can use the=20
>   technology in a manner that avoids likely pitfalls
>=20
> - A processing model for each relevant implementation conformance =
class=20
>   (software) that defines how you take the input and use it
>=20
> In the case of these string, that means, to a first approximation:
>=20
> - A definition of what the valid syntax of these strings is.
>=20
> - A definition of how you get from one of these strings, whether valid =
or=20
>   not, to the information you need to process it, in particular, for=20=

>   e.g. strings that reference specific files:
>    - the scheme (what protocol you're going to be using)
>    - the hostname and port of the remote host
>    - the path and query string to pass to that host
>    - the fragment identifier
>=20
> So there should just be one spec, not three (IRIs, URIs, and the error=20=

> handling).
>=20
> --=20
> Ian Hickson               U+1047E                )\._.,--....,'``.    =
fL
> http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ =
,.
> Things that are impossible just take longer.   =
`._.-(,_..'--(,_..'`-.;.'


From clauret@weborganic.com  Tue Oct 23 16:09:56 2012
Return-Path: <clauret@weborganic.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7A85F1F0CAB for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 16:09:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.976
X-Spam-Level: 
X-Spam-Status: No, score=-2.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 02TJldIcQX3d for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 16:09:55 -0700 (PDT)
Received: from mail-ie0-f172.google.com (mail-ie0-f172.google.com [209.85.223.172]) by ietfa.amsl.com (Postfix) with ESMTP id B86F91F0C3A for <ietf@ietf.org>; Tue, 23 Oct 2012 16:09:55 -0700 (PDT)
Received: by mail-ie0-f172.google.com with SMTP id 9so7154664iec.31 for <ietf@ietf.org>; Tue, 23 Oct 2012 16:09:55 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=aTNLWy+nAYQhy0bjWNyUDByka+Xh/UiDAfKhGeYsZ8E=; b=TikIVzvLssZ+BMZ9Jz2PjOBcetyFd0o7xJ60005yvZ/OInT0vjukwPM3wJvaWGaCKs FnEml+gZ0pScTsSlIt8uFFfs1sxCpJIsViP4IllvPmV8iGaZt2mvSF2UAOJBRdp2Jxsc NND/StKVMjRIsfTygZYDFpfJAIqoRflTLoBkZlDtdP9q3VYlgpfUtWAPxrCEVgcYLNAS QfueCFIjUcA7mZYRy+ycOZSh0Gi+KB2lhS37HNZVNY6alQ96NCGVE3eUqq/OZ9Ay1mI9 aLsAjWcOaenpfmOkpHr+Zs4+kvWlpXj1Mf5FH10K2V+C2GRIVT4F70Mt92AQvhzZadI5 mx6Q==
MIME-Version: 1.0
Received: by 10.50.151.210 with SMTP id us18mr809278igb.1.1351033795247; Tue, 23 Oct 2012 16:09:55 -0700 (PDT)
Received: by 10.64.38.66 with HTTP; Tue, 23 Oct 2012 16:09:54 -0700 (PDT)
In-Reply-To: <15E1D98B-8883-4936-81A9-174E1323683C@nordsc.com>
References: <50604C1A.7090901@gmx.de> <5060A964.5060001@stpeter.im> <Pine.LNX.4.64.1210172354500.2478@ps20323.dreamhostps.com> <507F5A7E.6040206@arcanedomain.com> <50856E3C.103@gmail.com> <Pine.LNX.4.64.1210221753010.2471@ps20323.dreamhostps.com> <0DBC8A11-319C-4120-975E-7E40FD5818BF@gbiv.com> <Pine.LNX.4.64.1210222137530.2471@ps20323.dreamhostps.com> <CA+9kkMDpEZCvcG1DJd=O1qPNV+=+GTBeN+CGndUe51Xym_A9sg@mail.gmail.com> <Pine.LNX.4.64.1210232115210.2471@ps20323.dreamhostps.com> <15E1D98B-8883-4936-81A9-174E1323683C@nordsc.com>
Date: Wed, 24 Oct 2012 10:09:54 +1100
Message-ID: <CAGKvQ5ZV6_GMVgjEezhR-oKqSikxR7GYgacMitbfczmNh725mw@mail.gmail.com>
Subject: Re: [whatwg] New URL Standard from Anne van Kesteren on 2012-09-24 (public-whatwg-archive@w3.org from September 2012)
From: Christophe Lauret <clauret@weborganic.com>
To: Jan Algermissen <jan.algermissen@nordsc.com>
Content-Type: multipart/alternative; boundary=e89a8f3b9e9971ff6f04ccc21148
X-Gm-Message-State: ALoCoQljSBPTUPAzmU+KbmUb1sROO5lqxC5Bm+FlNBFUsy6IxG2Xa/0E8tLHFYnD2b9r/72GLkpW
X-Mailman-Approved-At: Wed, 24 Oct 2012 08:37:10 -0700
Cc: Ted Hardie <ted.ietf@gmail.com>, Ian Hickson <ian@hixie.ch>, URI <uri@w3.org>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Oct 2012 23:13:41 -0000

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

Jan wrote:

Help me, I am just not getting it:
> Why do you insist on 'fixing STD 66'?
> What is the reason you are not willing to reframe the problem to 'fixing
> how we get from the provided string -the input to the reference
> construction process- to a STD-66-valid result'?
> To me this is really what you are aiming at and dropping the 'fix the URI
> spec' language would get everyone on board immediately in my perception.


I completely agree - I don't understand the insistence on "fixing" STD 66.

As a Web developer who's had to write code multiple times to handle URIs in
very different contexts, I actually *like* the constraints in STD 66, there
are many instances where it is simpler to assume that the error handling
has been done prior and simply reject an invalid URI. By reducing the space
of valid addresses around rigid rules to match more closely the set of
addressable resources, it reduces my scope of work.

I understand that it isn't practical in some contexts (e.g. browsers) where
it is inevitable that strings that are not considered valid URI references
will crop up and it is desirable for everyone to deal with these in a
consistent manner. So, I applaud Anne and Ian for wanting to standardize
the error handling and tackling this problem head on.
But why not do it as a separate spec?

Increasing the space of valid addresses, when the set of addressable
resources is not actually increasing only means more complex parsing rules.
I accept that it is a requirement in some contexts, but it is
also completely unnecessary in others where coding against STD 66 is just
fine if not more desirable.

Personally, I don't have any qualms in calling that larger set of addresses
"URLs" if it is what most people use, and leave STD 66 and URIs are as they
are.

Christophe-

(I've used 'address' as a short for a "string which should ultimately
resolve as a valid STD 66 result")

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

<div>Jan wrote:</div><div><br></div><blockquote class=3D"gmail_quote" style=
=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(20=
4,204,204);border-left-style:solid;padding-left:1ex">Help me, I am just not=
 getting it:<br>
Why do you insist on &#39;fixing STD 66&#39;?<br>What is the reason you are=
 not willing to reframe the problem to &#39;fixing how we get from the prov=
ided string -the input to the reference construction process- to a STD-66-v=
alid result&#39;?<br>
To me this is really what you are aiming at and dropping the &#39;fix the U=
RI spec&#39; language would get everyone on board immediately in my percept=
ion.</blockquote><div><br></div><div>I completely agree -=A0I don&#39;t und=
erstand the insistence on &quot;fixing&quot; STD 66.</div>
<div><div><br></div><div>As a Web developer who&#39;s had to write code mul=
tiple times to handle URIs in very different contexts, I=A0actually *like* =
the constraints in STD 66, there are many instances where it is simpler to =
assume that the error handling has been done prior and simply reject an inv=
alid URI. By reducing the space of valid addresses around rigid rules to ma=
tch more closely the set of addressable resources, it reduces my scope of w=
ork.</div>
<div><br></div><div>I understand that it isn&#39;t practical in some contex=
ts (e.g. browsers) where it is inevitable that strings that are not conside=
red valid URI references will crop up and it is desirable for everyone to d=
eal with these in a consistent manner.=A0So, I=A0applaud=A0Anne and Ian for=
=A0wanting to standardize the error handling and=A0tackling this problem he=
ad on.</div>
<div>But why not do it as a separate spec?</div><div><br></div><div>Increas=
ing the space of valid addresses, when=A0the=A0set of addressable resources=
 is not actually increasing only means more complex parsing rules.</div><di=
v>
I accept that it is=A0a requirement=A0in some contexts, but it is also=A0co=
mpletely=A0unnecessary in others where coding against STD 66 is just fine i=
f not more desirable.</div><div><br></div><div>Personally, I don&#39;t have=
 any qualms in calling that larger set of addresses &quot;URLs&quot; if it =
is what most people use, and leave STD 66 and URIs are as they are.</div>
<div><br></div><div>Christophe-</div></div><br><div>(I&#39;ve used &#39;add=
ress&#39; as a short for a &quot;string which should ultimately resolve as =
a valid STD 66 result&quot;)</div><div><br></div>

--e89a8f3b9e9971ff6f04ccc21148--

From ian@hixie.ch  Tue Oct 23 16:47:55 2012
Return-Path: <ian@hixie.ch>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 95B231F0CBD for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 16:47:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.532
X-Spam-Level: 
X-Spam-Status: No, score=-2.532 tagged_above=-999 required=5 tests=[AWL=0.068,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id A0bl+4RHaIK6 for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 16:47:54 -0700 (PDT)
Received: from homiemail-a47.g.dreamhost.com (caibbdcaaaaf.dreamhost.com [208.113.200.5]) by ietfa.amsl.com (Postfix) with ESMTP id B46921F0CB7 for <ietf@ietf.org>; Tue, 23 Oct 2012 16:47:54 -0700 (PDT)
Received: from homiemail-a47.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a47.g.dreamhost.com (Postfix) with ESMTP id 4708F28405B; Tue, 23 Oct 2012 16:47:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=hixie.ch; h=date:from:to :cc:subject:in-reply-to:message-id:references:mime-version: content-type; s=hixie.ch; bh=5/dXRyfZP79/ZyddN5lqheksCbQ=; b=2V6 5FRMA5AHG7f7JlMYAm4MVx/4c5gvS6cGuB2NYYfypABT4hd9XdRROac+NIVvb11O Z1Qrj2xfnGiVdqDs/ePkKBxl7sl5XH4oyww23Z1ofWcnVPX29ZWR3qzN95zD/13Y CfxNI47FaFj8+HZWsDDtZq4ZL+9QlD/2kQZ+EbXE=
Received: from ps20323.dreamhostps.com (ps20323.dreamhost.com [69.163.222.251]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: internal@index.hixie.ch) by homiemail-a47.g.dreamhost.com (Postfix) with ESMTPSA id 3DE41284058;  Tue, 23 Oct 2012 16:47:55 -0700 (PDT)
Date: Tue, 23 Oct 2012 23:47:54 +0000 (UTC)
From: Ian Hickson <ian@hixie.ch>
To: Jan Algermissen <jan.algermissen@nordsc.com>
Subject: Re: [whatwg] New URL Standard from Anne van Kesteren on 2012-09-24 (public-whatwg-archive@w3.org from September 2012)
In-Reply-To: <8CC5FA04-2F61-408F-AED5-792E086E9BA0@nordsc.com>
Message-ID: <Pine.LNX.4.64.1210232347280.2471@ps20323.dreamhostps.com>
References: <50604C1A.7090901@gmx.de> <5060A964.5060001@stpeter.im> <Pine.LNX.4.64.1210172354500.2478@ps20323.dreamhostps.com> <507F5A7E.6040206@arcanedomain.com> <50856E3C.103@gmail.com> <Pine.LNX.4.64.1210221753010.2471@ps20323.dreamhostps.com> <0DBC8A11-319C-4120-975E-7E40FD5818BF@gbiv.com> <Pine.LNX.4.64.1210222137530.2471@ps20323.dreamhostps.com> <CA+9kkMDpEZCvcG1DJd=O1qPNV+=+GTBeN+CGndUe51Xym_A9sg@mail.gmail.com> <Pine.LNX.4.64.1210232115210.2471@ps20323.dreamhostps.com> <15E1D98B-8883-4936-81A9-174E1323683C@nordsc.com> <Pine.LNX.4.64.1210232234590.2471@ps20323.dreamhostps.com> <8CC5FA04-2F61-408F-AED5-792E086E9BA0@nordsc.com>
Content-Language: en-GB-hixie
Content-Style-Type: text/css
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Mailman-Approved-At: Wed, 24 Oct 2012 08:37:10 -0700
Cc: Ted Hardie <ted.ietf@gmail.com>, URI <uri@w3.org>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Oct 2012 23:47:55 -0000

On Wed, 24 Oct 2012, Jan Algermissen wrote:
> 
> What matters is that nothing of the existing URI spec *changes*.
> 
> Can you agree on that?

Do you mean the actual text, or the normative meaning of the text?

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'

From ian@hixie.ch  Tue Oct 23 16:51:13 2012
Return-Path: <ian@hixie.ch>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8D6C511E810B for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 16:51:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.535
X-Spam-Level: 
X-Spam-Status: No, score=-2.535 tagged_above=-999 required=5 tests=[AWL=0.064,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mHODVX5Mg0UO for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 16:51:12 -0700 (PDT)
Received: from homiemail-a94.g.dreamhost.com (caibbdcaaaaf.dreamhost.com [208.113.200.5]) by ietfa.amsl.com (Postfix) with ESMTP id 4CCDA11E80FE for <ietf@ietf.org>; Tue, 23 Oct 2012 16:51:10 -0700 (PDT)
Received: from homiemail-a94.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a94.g.dreamhost.com (Postfix) with ESMTP id 23A1838A06F; Tue, 23 Oct 2012 16:51:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=hixie.ch; h=date:from:to :cc:subject:in-reply-to:message-id:references:mime-version: content-type; s=hixie.ch; bh=d4f8KxGspATkP2rbxqss3qZU3ds=; b=nFF AeW37abDJNo3WgrWliwTmxx+dWV5oNgS9OBE5M5llWfZRj0Iud17E4JCHW5YthxZ 0J7sjGPi/ZmoxYR7GUNKWQrvJwTUbKpoCwfKXZfMKU4qiee9DZPROL9AU4R2Xn+5 ACLJlWeckJr8dmP8cDhdchy9f6pfst9inPOMIul0=
Received: from ps20323.dreamhostps.com (ps20323.dreamhost.com [69.163.222.251]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: internal@index.hixie.ch) by homiemail-a94.g.dreamhost.com (Postfix) with ESMTPSA id 036B438A059;  Tue, 23 Oct 2012 16:51:09 -0700 (PDT)
Date: Tue, 23 Oct 2012 23:51:09 +0000 (UTC)
From: Ian Hickson <ian@hixie.ch>
To: Christophe Lauret <clauret@weborganic.com>
Subject: Re: [whatwg] New URL Standard from Anne van Kesteren on 2012-09-24 (public-whatwg-archive@w3.org from September 2012)
In-Reply-To: <CAGKvQ5ZV6_GMVgjEezhR-oKqSikxR7GYgacMitbfczmNh725mw@mail.gmail.com>
Message-ID: <Pine.LNX.4.64.1210232348110.2471@ps20323.dreamhostps.com>
References: <50604C1A.7090901@gmx.de> <5060A964.5060001@stpeter.im> <Pine.LNX.4.64.1210172354500.2478@ps20323.dreamhostps.com> <507F5A7E.6040206@arcanedomain.com> <50856E3C.103@gmail.com> <Pine.LNX.4.64.1210221753010.2471@ps20323.dreamhostps.com> <0DBC8A11-319C-4120-975E-7E40FD5818BF@gbiv.com> <Pine.LNX.4.64.1210222137530.2471@ps20323.dreamhostps.com> <CA+9kkMDpEZCvcG1DJd=O1qPNV+=+GTBeN+CGndUe51Xym_A9sg@mail.gmail.com> <Pine.LNX.4.64.1210232115210.2471@ps20323.dreamhostps.com> <15E1D98B-8883-4936-81A9-174E1323683C@nordsc.com> <CAGKvQ5ZV6_GMVgjEezhR-oKqSikxR7GYgacMitbfczmNh725mw@mail.gmail.com>
Content-Language: en-GB-hixie
Content-Style-Type: text/css
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Mailman-Approved-At: Wed, 24 Oct 2012 08:37:10 -0700
Cc: Ted Hardie <ted.ietf@gmail.com>, Jan Algermissen <jan.algermissen@nordsc.com>, URI <uri@w3.org>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Oct 2012 23:51:13 -0000

On Wed, 24 Oct 2012, Christophe Lauret wrote:
> 
> As a Web developer who's had to write code multiple times to handle URIs 
> in very different contexts, I actually *like* the constraints in STD 66, 
> there are many instances where it is simpler to assume that the error 
> handling has been done prior and simply reject an invalid URI.

I think we can agree that the error handling should be, at the option of 
the software developer, either to handle the input as defined by the 
spec's algorithms, or to abort and not handle the input at all.


> But why not do it as a separate spec?

Having multiple specs means an implementor has to refer to multiple specs 
to implement one algorithm, which is not a way to get interoperability. 
Bugs creep in much faster when implementors have to switch between specs 
just in the implementation of one algorithm.


> Increasing the space of valid addresses, when the set of addressable
> resources is not actually increasing only means more complex parsing rules.

I'm not saying we should increase the space of valid addresses. The de 
facto parsing rules are already complicated by de facto requirements for 
handling errors, so defining those doesn't increase complexity either 
(especially if such behaviour is left as optional, as discussed above.)

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'

From ian@hixie.ch  Tue Oct 23 18:16:33 2012
Return-Path: <ian@hixie.ch>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9309511E814B for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 18:16:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.538
X-Spam-Level: 
X-Spam-Status: No, score=-2.538 tagged_above=-999 required=5 tests=[AWL=0.061,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id h2Akvb4LX2jR for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 18:16:32 -0700 (PDT)
Received: from homiemail-a44.g.dreamhost.com (caibbdcaaaaf.dreamhost.com [208.113.200.5]) by ietfa.amsl.com (Postfix) with ESMTP id 99F9111E8149 for <ietf@ietf.org>; Tue, 23 Oct 2012 18:16:32 -0700 (PDT)
Received: from homiemail-a44.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a44.g.dreamhost.com (Postfix) with ESMTP id 6AE0E11805C; Tue, 23 Oct 2012 18:16:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=hixie.ch; h=date:from:to :cc:subject:in-reply-to:message-id:references:mime-version: content-type; s=hixie.ch; bh=exs+VddM/nrWAle9Bar8YFpxcnI=; b=O7h 5VDtSgKo7RWbHATaf3gEKLYTXfvjsS+KXU6mxHueTBBsN8Tz6oAC2iTBqkKLhPox PLkmT2LKPQB5pKSZA5ZyZm7Q6x4Qm230bvpvbduNP6TulC6S04xkXPyFSC3HdPIo xKv9k2B4VnAs9JByfbv8KZ6Zs3/9rjT8P5qwZTbE=
Received: from ps20323.dreamhostps.com (ps20323.dreamhost.com [69.163.222.251]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: internal@index.hixie.ch) by homiemail-a44.g.dreamhost.com (Postfix) with ESMTPSA id 57ECF118057;  Tue, 23 Oct 2012 18:16:34 -0700 (PDT)
Date: Wed, 24 Oct 2012 01:16:31 +0000 (UTC)
From: Ian Hickson <ian@hixie.ch>
To: Ted Hardie <ted.ietf@gmail.com>
Subject: Re: [whatwg] New URL Standard from Anne van Kesteren on 2012-09-24 (public-whatwg-archive@w3.org from September 2012)
In-Reply-To: <CA+9kkMDN6+WGkvVC94iiSjB2O+ijGDiweqPfagm6ZTBdLz12_Q@mail.gmail.com>
Message-ID: <Pine.LNX.4.64.1210240110240.2471@ps20323.dreamhostps.com>
References: <50604C1A.7090901@gmx.de> <5060A964.5060001@stpeter.im> <Pine.LNX.4.64.1210172354500.2478@ps20323.dreamhostps.com> <507F5A7E.6040206@arcanedomain.com> <50856E3C.103@gmail.com> <Pine.LNX.4.64.1210221753010.2471@ps20323.dreamhostps.com> <0DBC8A11-319C-4120-975E-7E40FD5818BF@gbiv.com> <Pine.LNX.4.64.1210222137530.2471@ps20323.dreamhostps.com> <CA+9kkMDpEZCvcG1DJd=O1qPNV+=+GTBeN+CGndUe51Xym_A9sg@mail.gmail.com> <Pine.LNX.4.64.1210232115210.2471@ps20323.dreamhostps.com> <15E1D98B-8883-4936-81A9-174E1323683C@nordsc.com> <CAGKvQ5ZV6_GMVgjEezhR-oKqSikxR7GYgacMitbfczmNh725mw@mail.gmail.com> <Pine.LNX.4.64.1210232348110.2471@ps20323.dreamhostps.com> <CA+9kkMDN6+WGkvVC94iiSjB2O+ijGDiweqPfagm6ZTBdLz12_Q@mail.gmail.com>
Content-Language: en-GB-hixie
Content-Style-Type: text/css
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Mailman-Approved-At: Wed, 24 Oct 2012 08:37:10 -0700
Cc: Christophe Lauret <clauret@weborganic.com>, Jan Algermissen <jan.algermissen@nordsc.com>, URI <uri@w3.org>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Oct 2012 01:16:33 -0000

On Tue, 23 Oct 2012, Ted Hardie wrote:
> On Tue, Oct 23, 2012 at 4:51 PM, Ian Hickson <ian@hixie.ch> wrote:
> > Having multiple specs means an implementor has to refer to multiple 
> > specs to implement one algorithm, which is not a way to get 
> > interoperability. Bugs creep in much faster when implementors have to 
> > switch between specs just in the implementation of one algorithm.
> 
> First, do you have data that supports this assertion?

No.


> Second, multiple folks in this conversation have asserted that the right 
> way to approach this is to have *two* algorithms. The first is "method 
> to get from string to URI"  and the second is "Process URI".

That would be inefficient, so isn't likely to be a solid implementation 
strategy in many environments. I don't see any reason to do it this way.


> It also seems far more likely to me that bugs will creep in from 
> re-defining a known algorithm (the "process URI" bit from the pair 
> above) than from the separation of that from a different operation.

That's what regression tests and review are for. Obviously if we rewrote 
the algorithms and introduced bugs and just left them as is, we'd be 
pretty awfully incompetent. Nobody is suggesting that the work will be 
done before we have reached a point where the new spec is as good or 
better than the existing specs.


> If the results of the rewording would be different operations then, as I 
> have noted before, you really should use different terms and admit to 
> the fork.

There's no desire to make the new spec incompatible with existing 
software. That would not be a useful spec.

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'

From James.H.Manger@team.telstra.com  Tue Oct 23 18:59:11 2012
Return-Path: <James.H.Manger@team.telstra.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 18C0011E8146 for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 18:59:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.929
X-Spam-Level: 
X-Spam-Status: No, score=-0.929 tagged_above=-999 required=5 tests=[AWL=-0.028, BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327, RELAY_IS_203=0.994]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4K1GnNmhx6P1 for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 18:59:10 -0700 (PDT)
Received: from ipxcno.tcif.telstra.com.au (ipxcno.tcif.telstra.com.au [203.35.82.208]) by ietfa.amsl.com (Postfix) with ESMTP id 3042C11E80E9 for <ietf@ietf.org>; Tue, 23 Oct 2012 18:59:09 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.80,638,1344175200"; d="scan'208";a="98037678"
Received: from unknown (HELO ipccni.tcif.telstra.com.au) ([10.97.216.208]) by ipocni.tcif.telstra.com.au with ESMTP; 24 Oct 2012 12:59:08 +1100
X-IronPort-AV: E=McAfee;i="5400,1158,6874"; a="96043639"
Received: from wsmsg3705.srv.dir.telstra.com ([172.49.40.203]) by ipccni.tcif.telstra.com.au with ESMTP; 24 Oct 2012 12:59:08 +1100
Received: from WSMSG3153V.srv.dir.telstra.com ([172.49.40.159]) by WSMSG3705.srv.dir.telstra.com ([172.49.40.203]) with mapi; Wed, 24 Oct 2012 12:59:07 +1100
From: "Manger, James H" <James.H.Manger@team.telstra.com>
To: Ian Hickson <ian@hixie.ch>, Christophe Lauret <clauret@weborganic.com>
Date: Wed, 24 Oct 2012 12:59:05 +1100
Subject: RE: [whatwg] New URL Standard from Anne van Kesteren on 2012-09-24 (public-whatwg-archive@w3.org from September 2012)
Thread-Topic: [whatwg] New URL Standard from Anne van Kesteren on 2012-09-24 (public-whatwg-archive@w3.org from September 2012)
Thread-Index: Ac2xeWY/aSNY/ig4Q1OIdv9rcNd7qgADHwyA
Message-ID: <255B9BB34FB7D647A506DC292726F6E114FE01A829@WSMSG3153V.srv.dir.telstra.com>
References: <50604C1A.7090901@gmx.de> <5060A964.5060001@stpeter.im> <Pine.LNX.4.64.1210172354500.2478@ps20323.dreamhostps.com> <507F5A7E.6040206@arcanedomain.com> <50856E3C.103@gmail.com> <Pine.LNX.4.64.1210221753010.2471@ps20323.dreamhostps.com> <0DBC8A11-319C-4120-975E-7E40FD5818BF@gbiv.com> <Pine.LNX.4.64.1210222137530.2471@ps20323.dreamhostps.com> <CA+9kkMDpEZCvcG1DJd=O1qPNV+=+GTBeN+CGndUe51Xym_A9sg@mail.gmail.com> <Pine.LNX.4.64.1210232115210.2471@ps20323.dreamhostps.com> <15E1D98B-8883-4936-81A9-174E1323683C@nordsc.com> <CAGKvQ5ZV6_GMVgjEezhR-oKqSikxR7GYgacMitbfczmNh725mw@mail.gmail.com> <Pine.LNX.4.64.1210232348110.2471@ps20323.dreamhostps.com>
In-Reply-To: <Pine.LNX.4.64.1210232348110.2471@ps20323.dreamhostps.com>
Accept-Language: en-US, en-AU
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-AU
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Mailman-Approved-At: Wed, 24 Oct 2012 08:37:10 -0700
Cc: Anne van Kesteren <annevk@annevk.nl>, Ted Hardie <ted.ietf@gmail.com>, Jan Algermissen <jan.algermissen@nordsc.com>, URI <uri@w3.org>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Oct 2012 01:59:11 -0000

PiBGcm9tOiBJYW4gSGlja3NvbiBbbWFpbHRvOmlhbkBoaXhpZS5jaF0NCj4gSSB0aGluayB3ZSBj
YW4gYWdyZWUgdGhhdCB0aGUgZXJyb3IgaGFuZGxpbmcgc2hvdWxkIGJlLCBhdCB0aGUgb3B0aW9u
DQo+IG9mIHRoZSBzb2Z0d2FyZSBkZXZlbG9wZXIsIGVpdGhlciB0byBoYW5kbGUgdGhlIGlucHV0
IGFzIGRlZmluZWQgYnkgdGhlDQo+IHNwZWMncyBhbGdvcml0aG1zLCBvciB0byBhYm9ydCBhbmQg
bm90IGhhbmRsZSB0aGUgaW5wdXQgYXQgYWxsLg0KDQpDdXJyZW50bHksIEkgZG9uJ3QgdGhpbmsg
dXJsLnNwZWMud2hhdHdnLm9yZyBkaXN0aW5ndWlzaGVzIGJldHdlZW4gc3RyaW5ncyB0aGF0IGFy
ZQ0KdmFsaWQgVVJMcyBhbmQgc3RyaW5ncyB0aGF0IGNhbiBiZSBpbnRlcnByZXRlZCBhcyBVUkxz
IGJ5IGFwcGx5aW5nIGl0cyBzdGFuZGFyZGlzZWQgZXJyb3IgaGFuZGxpbmcuIENvbnNlcXVlbnRs
eSwgZXJyb3IgaGFuZGxpbmcgY2Fubm90IGJlIGF0IHRoZSBvcHRpb24gb2YgdGhlIHNvZnR3YXJl
IGRldmVsb3BlciBhcyB5b3UgY2Fubm90IHRlbGwgd2hpY2ggYml0cyBhcmUgZXJyb3IgaGFuZGxp
bmcuDQoNClRoaXMgbWlnaHQgYmUgd2h5IHNvbWUgYXJlIHVuaGFwcHkgd2l0aCB1cmwuc3BlYy53
aGF0d2cub3JnLg0KDQp1cmwuc3BlYy53aGF0d2cub3JnIGRvZXMgaGF2ZSBzZXBhcmF0ZSAiV3Jp
dGluZyIgYW5kICJQYXJzaW5nIiBzZWN0aW9ucy4gUGVyaGFwcyB0aGUgaW1wbGljaXQgaWRlYSBp
cyB0aGF0IGFueSBvdXRwdXQgb2YgdGhlICJXcml0aW5nIiBzZWN0aW9uIGlzIGEgdmFsaWQgVVJM
ICh0aGF0IGFsbCBVUkwtcHJvY2Vzc2luZyBzb2Z0d2FyZSBzaG91bGQgaGFuZGxlKS4gVGhlICJQ
YXJzaW5nIiBzZWN0aW9uIGFjY2VwdHMgbW9yZSBzdHJpbmdzIHRoYW4gY2FuIGJlIGNyZWF0ZWQg
YnkgdGhlICJXcml0aW5nIiBzZWN0aW9uLiBUaGUgZGlmZmVyZW5jZSBpcyB0aGUgZXJyb3IgaGFu
ZGxpbmcuIEl0J3MgT0sgZm9yIGEgc29mdHdhcmUgZGV2ZWxvcGVyIG5vdCB0byBwYXJzZSB0aGlz
IGRpZmZlcmVuY2UgaWYgaXQgbWFrZXMgaXRzIHBhcnNlciBzaW1wbGVyLCBzYWZlciwgb3IgdGhh
dCBpcyB0aGUgd2F5IGl0cyBwYXJzZXIgd29ya3MgdG9kYXkuDQoNCg0KLS0NCkphbWVzIE1hbmdl
cg0KDQo=

From pe-jiang@kddi.com  Tue Oct 23 19:57:49 2012
Return-Path: <pe-jiang@kddi.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 135B31F0C5F for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 19:57:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.954
X-Spam-Level: *
X-Spam-Status: No, score=1.954 tagged_above=-999 required=5 tests=[AWL=-5.403,  BAYES_00=-2.599, FB_EMAIL_HIER=10.357, J_CHICKENPOX_14=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wz3ZIFFpDxTH for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 19:57:48 -0700 (PDT)
Received: from UTMC1102.kddi.com (athena.kddi.com [210.141.112.39]) by ietfa.amsl.com (Postfix) with ESMTP id 23CCB1F0C6E for <ietf@ietf.org>; Tue, 23 Oct 2012 19:57:47 -0700 (PDT)
Received: from UTMC1132 (unknown [10.5.16.195]) by UTMC1102.kddi.com (Postfix) with SMTP id 433822BC2; Wed, 24 Oct 2012 11:57:46 +0900 (JST)
Received: from UTMC1122.kddi.com (localhost [127.0.0.1]) by localhost.kddi.com (Postfix) with ESMTP id 034F81467; Wed, 24 Oct 2012 11:57:44 +0900 (JST)
Received: from UTMC1116.kddi.com (unknown [10.5.16.25]) by UTMC1122.kddi.com (Postfix) with ESMTP id D807916DC; Wed, 24 Oct 2012 11:57:43 +0900 (JST)
Received: from KDDI-0806PC0671 ([10.200.129.117] [10.200.129.117]) by post-ims.kddi.com with ESMTPA; Wed, 24 Oct 2012 11:57:43 +0900
To: lberger@labn.net
Subject: Re: Last Call: <draft-kumaki-murai-l3vpn-rsvp-te-06.txt> (SupportforRSVP-TE in L3VPNs) to Experimental RFC
From: Peng JIANG <pe-jiang@kddi.com>
References: <20120905224357.14197.39927.idtracker@ietfa.amsl.com> <5085E77C.5020100@labn.net> <201210231039.GAJ87540.KFBHtQOJ@kddi.com> <5086949E.4050305@labn.net>
In-Reply-To: <5086949E.4050305@labn.net>
Message-Id: <201210241157.HAF69250.QHBtKFJO@kddi.com>
X-Mailer: Winbiff [Version 2.51 PL3]
X-Accept-Language: ja,en,zh
Date: Wed, 24 Oct 2012 11:57:43 +0900
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-WAuditID: 1210241157440000200778
X-Mailman-Approved-At: Wed, 24 Oct 2012 08:37:10 -0700
Cc: afarrel@juniper.net, stbryant@cisco.com, draft-kumaki-murai-l3vpn-rsvp-te.all@tools.ietf.org, ietf@ietf.org, daniel@olddog.co.uk
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Oct 2012 02:57:49 -0000

Hello Lou,

> > 
> > We think you are correct about the Path message.
> > But Resv messages are different. The Resv messages are sent hop-
> > by-hop. The destination is not the remote PE but the unicast 
> > address of a previous RSVP hop when a PE send out a Resv message.
> >
> >  Therefor, there will be no VPN label and the remote PE will 
> > have no method to identify the VPN context/VRF.
> >
> 
> I'd expect it to be represented in the HOP object.

Sorry for misleading.

Scenario 1: (Our main scenario)
RSVP-TE control messages are used to create LSP between CE and 
CE including PE-to-PE(multi hops) part.

We do not see PE-to-PE part as one hop.

Our Path and Resv messages, both of them do not have VPN labels 
because we want to reserve network resources hop-by-hop between 
PEs.

Scenario 2:
View PE-to-PE as one hop and adds VPN labels to both Path and 
Resv messages. In this case, as in your email hierarchy-based 
solutions is also effective.


But our main target is Scenario 1.
We think it is necessary to also reserve network resources 
between PEs.

Best Regards,
Peng JIANG
KDDI





> Peng,
> 	Thanks for the quick response!  Please see in line below.
> 
> On 10/22/2012 9:39 PM, Peng JIANG wrote:
> > Hello Lou,
> > 
> >>> As to the technical details, the next hop as identified by the Path 
> >>> message in the VPN context, will have a route and associated label 
> >>> within the VPN context. This VPN label can be added to the Path 
> >>> message, just as it would be for any VPN IP packet, and additional 
> >>> labels may be added for PE-PE transport. In implementations that 
> >>> rewrite the IP header, the IP destination can be set to the next
> >>> hop. The remote PE/next hop will receive the Path message with the
> >>> VPN label which will identify the VPN context/VRF. This PE will then
> >>> need to identify the packet as RSVP using either the router alert
> >>> mechanism or based on the IP header destination address. So I see no
> >>> reason for the modifications when the VAN-specific MPLS labels are
> >>> used.
> >>>
> >>> Shout if you think I missed something.
> > 
> > We think you are correct about the Path message.
> > But Resv messages are different. The Resv messages are sent hop-
> > by-hop. The destination is not the remote PE but the unicast 
> > address of a previous RSVP hop when a PE send out a Resv message.
> >
> >  Therefor, there will be no VPN label and the remote PE will 
> > have no method to identify the VPN context/VRF.
> >
> 
> I'd expect it to be represented in the HOP object.
> 
> Lou
> 
> > In RFC 2205:
> > 3.1.3 Path Messages
> > A Path message travels from a sender to receiver(s) along the 
> > same path(s) used by the data packets.  The IP source address of
> >  a Path message must be an address of the sender it describes, 
> > while the destination address must be the DestAddress for the 
> > session.
> > 3.1.4 Resv Messages
> > Resv messages carry reservation requests hop-by-hop from 
> > receivers to senders, along the reverse paths of data flows for 
> > the session. The IP destination address of a Resv message is the
> >  unicast address of a previous-hop node, obtained from the path 
> > state. 
> > 
> >>> My high-order take away is that it seems to me that this draft runs
> >>> counter to hierarchy-based solutions that can solve this problem just
> >>> fine without any additional RSVP modifications. I therefore think
> >>> this draft should be run through a WG that is willing to reconcile
> >>> the approaches (and fully document their uses case supported by
> >>> hierarchy). Failing that, I think the draft should have an IESG 
> >>> applicability note added saying that this is experimental only and
> >>> that standard hierarchy should be used to solve the problem in any 
> >>> operational implementation/network.
> > As I have explained, For Resv messages, hierarchy-based 
> > solutions are not able to identify the VPN context/VRF at a 
> > remote PE. 
> > 
> > Hope the above explaination will make sense to you.
> > Please let us konw if you have any further comments.
> > 
> > Thanks.
> > 
> > 
> > Best Regards,
> > Peng JIANG
> > KDDI
> > 
> > 
> >>
> >> Hello,
> >> 	I made this comment privately during the LC period.  I don't mind
> >> sharing it more widely:
> >>
> >>> My high-order take away is that it seems to me that this draft runs
> >>> counter to hierarchy-based solutions that can solve this problem just
> >>> fine without any additional RSVP modifications. I therefore think
> >>> this draft should be run through a WG that is willing to reconcile
> >>> the approaches (and fully document their uses case supported by
> >>> hierarchy). Failing that, I think the draft should have an IESG 
> >>> applicability note added saying that this is experimental only and
> >>> that standard hierarchy should be used to solve the problem in any 
> >>> operational implementation/network.
> >>>
> >>> As to the technical details, the next hop as identified by the Path 
> >>> message in the VPN context, will have a route and associated label 
> >>> within the VPN context. This VPN label can be added to the Path 
> >>> message, just as it would be for any VPN IP packet, and additional 
> >>> labels may be added for PE-PE transport. In implementations that 
> >>> rewrite the IP header, the IP destination can be set to the next
> >>> hop. The remote PE/next hop will receive the Path message with the
> >>> VPN label which will identify the VPN context/VRF. This PE will then
> >>> need to identify the packet as RSVP using either the router alert
> >>> mechanism or based on the IP header destination address. So I see no
> >>> reason for the modifications when the VAN-specific MPLS labels are
> >>> used.
> >>>
> >>> Shout if you think I missed something.
> >>
> >> Lou
> >> On 9/5/2012 6:43 PM, The IESG wrote:
> >>>
> >>> The IESG has received a request from an individual submitter to consider
> >>> the following document:
> >>> - 'Support for RSVP-TE in L3VPNs'
> >>>   <draft-kumaki-murai-l3vpn-rsvp-te-06.txt> as Experimental RFC
> >>>
> >>> The IESG plans to make a decision in the next few weeks, and solicits
> >>> final comments on this action. Please send substantive comments to the
> >>> ietf@ietf.org mailing lists by 2012-10-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
> >>>
> >>>
> >>>    IP Virtual Private Networks (VPNs) provide connectivity between sites
> >>>    across an IP/MPLS backbone. These VPNs can be operated using BGP/MPLS
> >>>    and a single provider edge (PE) node may provide access to multiple
> >>>    customer sites belonging to different VPNs.
> >>>
> >>>    The VPNs may support a number of customer services including RSVP and
> >>>    RSVP-TE traffic. This document describes how to support RSVP-TE
> >>>    between customer sites when a single PE supports multiple VPNs.
> >>>
> >>>
> >>>
> >>>
> >>>
> >>> The file can be obtained via
> >>> http://datatracker.ietf.org/doc/draft-kumaki-murai-l3vpn-rsvp-te/
> >>>
> >>> IESG discussion can be tracked via
> >>> http://datatracker.ietf.org/doc/draft-kumaki-murai-l3vpn-rsvp-te/ballot/
> >>>
> >>>
> >>> No IPR declarations have been submitted directly on this I-D.
> >>>
> >>> Due to an error by the sponsoring Area Director, the Last Call on 
> >>> this document (which completed on 3rd September) incorrectly 
> >>> stated that this draft was intended that it be published as 
Informational.
> >>> The correct intention (as stated in the draft itself) is that it  be 
> >>> published as Experimental. 
> >>>
> >>> This Last Call is to verify community consensus for publication of
> >>> this draft as Experimental. 
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>
> > 
> > 
> > 
> > 
> 

From ajs@crankycanuck.ca  Tue Oct 23 20:36:43 2012
Return-Path: <ajs@crankycanuck.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 8D7F611E8129 for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 20:36:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.84
X-Spam-Level: 
X-Spam-Status: No, score=-0.84 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OzLOVQCzVlyt for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 20:36:43 -0700 (PDT)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id E120F11E8115 for <ietf@ietf.org>; Tue, 23 Oct 2012 20:36:42 -0700 (PDT)
Received: from crankycanuck.ca (unknown [38.107.218.2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id 31FD28A031 for <ietf@ietf.org>; Wed, 24 Oct 2012 03:36:39 +0000 (UTC)
Date: Tue, 23 Oct 2012 23:36:35 -0400
From: Andrew Sullivan <ajs@crankycanuck.ca>
To: ietf@ietf.org
Subject: Just so I'm clear (was: IAOC Request for community feedback)
Message-ID: <20121024033635.GA52558@crankycanuck.ca>
References: <20121023192135.203AC18C0A4@mercury.lcs.mit.edu> <5086EF82.9060900@dougbarton.us> <20121023200713.GC1861@nsn.com> <5086FBCE.2070503@dougbarton.us> <20121023213251.GF27557@verdi> <50873AB4.1000905@dougbarton.us>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <50873AB4.1000905@dougbarton.us>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-Mailman-Approved-At: Wed, 24 Oct 2012 08:37:10 -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, 24 Oct 2012 03:36:43 -0000

On Tue, Oct 23, 2012 at 05:47:48PM -0700, Doug Barton wrote:
> 
> On 10/23/2012 2:32 PM, John Leslie wrote:

> > In other organizations, I have lived through longish periods of
> > uncertainty about the exact status of an individual, and I no longer
> > find it scary.
> 
> I tend to agree, which is one of the reasons I think the procedure
> should be followed as written.

Let me get this straight: for the sake of procedures that are clearly
designed to be hard to use, and on the dubious principle that some
"precedent" is going to be set with respect to doing something that we
have never done before and hope never to do again (because we're going
to clarify the procedures right now), and in the face of an impending
decision by an already-sitting nomcom that is already doing all this
work, we're going to cleave to using the heavyweight procedure instead
of allowing judgement to carry the day?

I just want to be clear about this, since I'm busy running around the
NANOG meeting attempting to encourage operators to devote more of the
time they don't have to IETF activities.  I want to be sure I'm
correct in illustrating to them how we have all the bureaucratic
agility of the ITU-T or ICANN and all the legal and political
sophistication of the Occupy Wall Street committees.

Best,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com


From kosmo.zb@gmail.com  Tue Oct 23 20:49:55 2012
Return-Path: <kosmo.zb@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0F0F511E810B for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 20:49: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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JlnbPXoDqvWv for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 20:49:54 -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 DFC7711E80D3 for <ietf@ietf.org>; Tue, 23 Oct 2012 20:49:53 -0700 (PDT)
Received: by mail-lb0-f172.google.com with SMTP id k13so887287lbo.31 for <ietf@ietf.org>; Tue, 23 Oct 2012 20:49:52 -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=PKZPtJ8b5c+W0ciT+NzeCmOU0mJLa0R9Cg7hPp5XQQI=; b=KAB4WJTybRwgIbEI1QJnH1Q0lTKNHWFP5XCsCWqQuCNBtYEQQ/+LYxDfgbhRdIDWOU XLp2melfob8wCeoK/wWmEQ96/Zu41ypcXIkwuS5y2axqWI63EnQz5348UPx7DXF5pykc 0DS4xmD5RAZg/NNiaTvAiYhZWtKyglUV56wuYI/VdTkIa901O9sv3YNKKJ6kBta+snn+ mbNVo/ch5buInh6TDpbv/l5gU42NtPVkLrVZtO9t+nELAB0ThkGYZzkbBqNAuFZD9OMT VPNBXFC/XlGRuqLvQnpIF4pAmhc0O1xCsjb0AxVOfZHPYp9uRZn8wed/8eFE2QocoJ/T SmNw==
MIME-Version: 1.0
Received: by 10.152.105.173 with SMTP id gn13mr13151743lab.41.1351050592846; Tue, 23 Oct 2012 20:49:52 -0700 (PDT)
Received: by 10.112.36.227 with HTTP; Tue, 23 Oct 2012 20:49:52 -0700 (PDT)
In-Reply-To: <Pine.LNX.4.64.1210232348110.2471@ps20323.dreamhostps.com>
References: <50604C1A.7090901@gmx.de> <5060A964.5060001@stpeter.im> <Pine.LNX.4.64.1210172354500.2478@ps20323.dreamhostps.com> <507F5A7E.6040206@arcanedomain.com> <50856E3C.103@gmail.com> <Pine.LNX.4.64.1210221753010.2471@ps20323.dreamhostps.com> <0DBC8A11-319C-4120-975E-7E40FD5818BF@gbiv.com> <Pine.LNX.4.64.1210222137530.2471@ps20323.dreamhostps.com> <CA+9kkMDpEZCvcG1DJd=O1qPNV+=+GTBeN+CGndUe51Xym_A9sg@mail.gmail.com> <Pine.LNX.4.64.1210232115210.2471@ps20323.dreamhostps.com> <15E1D98B-8883-4936-81A9-174E1323683C@nordsc.com> <CAGKvQ5ZV6_GMVgjEezhR-oKqSikxR7GYgacMitbfczmNh725mw@mail.gmail.com> <Pine.LNX.4.64.1210232348110.2471@ps20323.dreamhostps.com>
Date: Tue, 23 Oct 2012 20:49:52 -0700
Message-ID: <CAAWM5Tz3NdprjqwgyoVoV9qUuiwXb2gTQ49u4a4ePGfjyusDkw@mail.gmail.com>
Subject: Re: [whatwg] New URL Standard from Anne van Kesteren on 2012-09-24 (public-whatwg-archive@w3.org from September 2012)
From: David Sheets <kosmo.zb@gmail.com>
To: Ian Hickson <ian@hixie.ch>
Content-Type: text/plain; charset=ISO-8859-1
X-Mailman-Approved-At: Wed, 24 Oct 2012 08:37:10 -0700
Cc: Christophe Lauret <clauret@weborganic.com>, Jan Algermissen <jan.algermissen@nordsc.com>, Ted Hardie <ted.ietf@gmail.com>, URI <uri@w3.org>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Oct 2012 03:49:55 -0000

On Tue, Oct 23, 2012 at 4:51 PM, Ian Hickson <ian@hixie.ch> wrote:
> On Wed, 24 Oct 2012, Christophe Lauret wrote:
>>
>> As a Web developer who's had to write code multiple times to handle URIs
>> in very different contexts, I actually *like* the constraints in STD 66,
>> there are many instances where it is simpler to assume that the error
>> handling has been done prior and simply reject an invalid URI.
>
> I think we can agree that the error handling should be, at the option of
> the software developer, either to handle the input as defined by the
> spec's algorithms, or to abort and not handle the input at all.

Yes, input is handled according to the specs' algorithmS.

>> But why not do it as a separate spec?
>
> Having multiple specs means an implementor has to refer to multiple specs
> to implement one algorithm, which is not a way to get interoperability.
> Bugs creep in much faster when implementors have to switch between specs
> just in the implementation of one algorithm.

One algorithm? There seem to be several functions...

- URI reference parsing (parse : scheme -> string -> raw uri_ref)
- URI reference normalization (normalize : raw uri_ref -> normal uri_ref)
- absolute URI predicate (absp : normal uri_ref -> absolute uri_ref option)
- URI resolution (resolve : absolute uri_ref -> _ uri_ref -> absolute uri_ref)

Of course, some of these may be composed in any given implementation.
In the case of a/@href and img/@src, it appears to be something like
(one_algorithm = (resolve base_uri) . normalize . parse (scheme
base_uri)) is in use.

A good way to get interop is to thoroughly define each function and
supply implementors with test cases for each processing stage
(one_algorithm's test cases define some tests for parse, normalize,
and resolve as well).

Some systems use more than the simple function composition of web browsers...

>> Increasing the space of valid addresses, when the set of addressable
>> resources is not actually increasing only means more complex parsing rules.
>
> I'm not saying we should increase the space of valid addresses.

Anne's current draft increases the space of valid addresses. This
isn't obvious as Anne's draft lacks a grammar and URI component
alphabets. You support Anne's draft and its philosophy, therefore you
are saying the space of valid addresses should be expanded.

Here is an example of a grammar extension that STD 66 disallows but
WHATWGRL allows:
<http://www.rfc-editor.org/errata_search.php?rfc=3986&eid=3330>

> The de facto parsing rules are already complicated by de facto requirements for
> handling errors, so defining those doesn't increase complexity either
> (especially if such behaviour is left as optional, as discussed above.)

*parse* is separate from *normalize* is separate from checking if a
reference is absolute (*absp*) is separate from *resolve*.

Why don't we have a discussion about the functions and types involved
in URI processing?

Why don't we discuss expanding allowable alphabets and production rules?

David

From cowan@ccil.org  Tue Oct 23 21:00:01 2012
Return-Path: <cowan@ccil.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 56AA911E810B for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 21:00:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3dusHrr-TAeJ for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 21:00:00 -0700 (PDT)
Received: from earth.ccil.org (earth.ccil.org [192.190.237.11]) by ietfa.amsl.com (Postfix) with ESMTP id ABD9511E80D3 for <ietf@ietf.org>; Tue, 23 Oct 2012 20:59:59 -0700 (PDT)
Received: from cowan by earth.ccil.org with local (Exim 4.72) (envelope-from <cowan@ccil.org>) id 1TQs8J-0007Fx-2b; Tue, 23 Oct 2012 23:59:55 -0400
Date: Tue, 23 Oct 2012 23:59:55 -0400
From: John Cowan <cowan@mercury.ccil.org>
To: David Sheets <kosmo.zb@gmail.com>
Subject: Re: [whatwg] New URL Standard from Anne van Kesteren on 2012-09-24 (public-whatwg-archive@w3.org from September 2012)
Message-ID: <20121024035954.GA27268@mercury.ccil.org>
References: <50856E3C.103@gmail.com> <Pine.LNX.4.64.1210221753010.2471@ps20323.dreamhostps.com> <0DBC8A11-319C-4120-975E-7E40FD5818BF@gbiv.com> <Pine.LNX.4.64.1210222137530.2471@ps20323.dreamhostps.com> <CA+9kkMDpEZCvcG1DJd=O1qPNV+=+GTBeN+CGndUe51Xym_A9sg@mail.gmail.com> <Pine.LNX.4.64.1210232115210.2471@ps20323.dreamhostps.com> <15E1D98B-8883-4936-81A9-174E1323683C@nordsc.com> <CAGKvQ5ZV6_GMVgjEezhR-oKqSikxR7GYgacMitbfczmNh725mw@mail.gmail.com> <Pine.LNX.4.64.1210232348110.2471@ps20323.dreamhostps.com> <CAAWM5Tz3NdprjqwgyoVoV9qUuiwXb2gTQ49u4a4ePGfjyusDkw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAAWM5Tz3NdprjqwgyoVoV9qUuiwXb2gTQ49u4a4ePGfjyusDkw@mail.gmail.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Sender: John Cowan <cowan@ccil.org>
X-Mailman-Approved-At: Wed, 24 Oct 2012 08:37:09 -0700
Cc: Ted Hardie <ted.ietf@gmail.com>, IETF Discussion <ietf@ietf.org>, Christophe Lauret <clauret@weborganic.com>, Jan Algermissen <jan.algermissen@nordsc.com>, URI <uri@w3.org>, Ian Hickson <ian@hixie.ch>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Oct 2012 04:00:01 -0000

David Sheets scripsit:

> Anne's current draft increases the space of valid addresses. This
> isn't obvious as Anne's draft lacks a grammar and URI component
> alphabets. You support Anne's draft and its philosophy, therefore you
> are saying the space of valid addresses should be expanded.

Before confusion is worse confounded, Anne's draft does not extend the space
of valid addresses, but rather provides processing for both valid and
invalid addresses.  As such, it extends the space of what may be called
processable or usable addresses.

-- 
"The serene chaos that is Courage, and the phenomenon   cowan@ccil.org
of Unopened Consciousness have been known to the        John Cowan
Great World eons longer than Extaboulism."
"Why is that?" the woman inquired.
"Because I just made that word up", the Master said wisely.
        --Kehlog Albran, The Profit             http://www.ccil.org/~cowan

From kosmo.zb@gmail.com  Tue Oct 23 21:20:19 2012
Return-Path: <kosmo.zb@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BDA3211E8115 for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 21:20:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X-JEiTRx57Aa for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 21:20:19 -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 96A9F11E810B for <ietf@ietf.org>; Tue, 23 Oct 2012 21:20:18 -0700 (PDT)
Received: by mail-lb0-f172.google.com with SMTP id k13so897719lbo.31 for <ietf@ietf.org>; Tue, 23 Oct 2012 21:20:17 -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=WsuK149O6Zb84nb1VVHYVTz/tVVnYryCZ0Dos0FXEsk=; b=Y+hQstkchLxahdcf/8FS4b0B1B1VCrOU9BwmkqUnDvCVJ2rF+NyenOtJ+jMGAfvJ2L YBWRmT6UnfNr35s4ZkTEY3SzQSoQlKXY1AWT2YUU+bKuj9LKfj5v+CCF9AantgJ9sVzK jxZvjQCgdvqrW0HVIlBo2rlYxSn/ZSokaiwKlG2bLKwcW82Wg4gMN0Senl7q7vDZTvLb 3uCfTFsiv8GLXUAMupGTdLnCU4KBsYQND0/1a6opTMqFkBNC4EIJrXKvafKISucZRrRY NH3nVCtxvxpHDWj7lNxbZq+tKcdUUHyJr1rFlq2aih40pLS3VOnjJlKf2U/+rXkw6xlV DLQA==
MIME-Version: 1.0
Received: by 10.152.105.173 with SMTP id gn13mr13204547lab.41.1351052417548; Tue, 23 Oct 2012 21:20:17 -0700 (PDT)
Received: by 10.112.36.227 with HTTP; Tue, 23 Oct 2012 21:20:17 -0700 (PDT)
In-Reply-To: <20121024035954.GA27268@mercury.ccil.org>
References: <50856E3C.103@gmail.com> <Pine.LNX.4.64.1210221753010.2471@ps20323.dreamhostps.com> <0DBC8A11-319C-4120-975E-7E40FD5818BF@gbiv.com> <Pine.LNX.4.64.1210222137530.2471@ps20323.dreamhostps.com> <CA+9kkMDpEZCvcG1DJd=O1qPNV+=+GTBeN+CGndUe51Xym_A9sg@mail.gmail.com> <Pine.LNX.4.64.1210232115210.2471@ps20323.dreamhostps.com> <15E1D98B-8883-4936-81A9-174E1323683C@nordsc.com> <CAGKvQ5ZV6_GMVgjEezhR-oKqSikxR7GYgacMitbfczmNh725mw@mail.gmail.com> <Pine.LNX.4.64.1210232348110.2471@ps20323.dreamhostps.com> <CAAWM5Tz3NdprjqwgyoVoV9qUuiwXb2gTQ49u4a4ePGfjyusDkw@mail.gmail.com> <20121024035954.GA27268@mercury.ccil.org>
Date: Tue, 23 Oct 2012 21:20:17 -0700
Message-ID: <CAAWM5TypLoCA5EmLkb=n5ic8GDyAVmKXs=CcAYn66rb2quPeQg@mail.gmail.com>
Subject: Re: [whatwg] New URL Standard from Anne van Kesteren on 2012-09-24 (public-whatwg-archive@w3.org from September 2012)
From: David Sheets <kosmo.zb@gmail.com>
To: John Cowan <cowan@mercury.ccil.org>
Content-Type: text/plain; charset=ISO-8859-1
X-Mailman-Approved-At: Wed, 24 Oct 2012 08:37:10 -0700
Cc: Ted Hardie <ted.ietf@gmail.com>, IETF Discussion <ietf@ietf.org>, Christophe Lauret <clauret@weborganic.com>, Jan Algermissen <jan.algermissen@nordsc.com>, URI <uri@w3.org>, Ian Hickson <ian@hixie.ch>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Oct 2012 04:20:19 -0000

On Tue, Oct 23, 2012 at 8:59 PM, John Cowan <cowan@mercury.ccil.org> wrote:
> David Sheets scripsit:
>
>> Anne's current draft increases the space of valid addresses. This
>> isn't obvious as Anne's draft lacks a grammar and URI component
>> alphabets. You support Anne's draft and its philosophy, therefore you
>> are saying the space of valid addresses should be expanded.
>
> Before confusion is worse confounded, Anne's draft does not extend the space
> of valid addresses, but rather provides processing for both valid and
> invalid addresses.  As such, it extends the space of what may be called
> processable or usable addresses.

In the version of the spec that I am reading
<http://url.spec.whatwg.org/>, I see definition of an "invalid flag"
<http://url.spec.whatwg.org/#invalid-flag> and a "valid attribute"
<http://url.spec.whatwg.org/#dom-url-valid>.

It would appear that <##> is a valid WHATWGRL but an invalid URI reference.

Under WHATWGRL processing (and as is found in extant browsers), <##>
is handled as it is literally written and not through coercion to a
"valid" address from a "usable" address.

Given these facts, I don't understand how Anne's spec doesn't extend
the space of valid addresses. If the spec says that input is output
without modification and that input is outside of the STD 66 space,
doesn't that expand the space of valid addresses?

WHATWGRLs with "[" and "]" in path, query, and fragment are allowed as well.

David

From ian@hixie.ch  Tue Oct 23 22:05:51 2012
Return-Path: <ian@hixie.ch>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E7B4521F8C66 for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 22:05:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.541
X-Spam-Level: 
X-Spam-Status: No, score=-2.541 tagged_above=-999 required=5 tests=[AWL=0.058,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fiUNt3pAxj8G for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 22:05:50 -0700 (PDT)
Received: from homiemail-a83.g.dreamhost.com (caibbdcaaaaf.dreamhost.com [208.113.200.5]) by ietfa.amsl.com (Postfix) with ESMTP id B1EBD21F8C65 for <ietf@ietf.org>; Tue, 23 Oct 2012 22:05:45 -0700 (PDT)
Received: from homiemail-a83.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a83.g.dreamhost.com (Postfix) with ESMTP id 4EED75E06A; Tue, 23 Oct 2012 22:05:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=hixie.ch; h=date:from:to :cc:subject:in-reply-to:message-id:references:mime-version: content-type; s=hixie.ch; bh=3nA2Vv9poxRq5GY5pv8ycFfFKNI=; b=ymb arrihSE8Eeg08aJJ4Nx5BOCXFPuXK5iUVRqSV+u8E/SVRSTwiPwWWRQuFGREWtBF pk+vDISjTBfUna4GvUPTKG/1xYYi4MSstxGabXwo5ORaZXIzBV3hL1cDzcupBxLY PQF1baqrtAkAs/QFPWdY/i+d2e1X6ti2wdu0SBM0=
Received: from ps20323.dreamhostps.com (ps20323.dreamhost.com [69.163.222.251]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: internal@index.hixie.ch) by homiemail-a83.g.dreamhost.com (Postfix) with ESMTPSA id 17C955E063;  Tue, 23 Oct 2012 22:05:45 -0700 (PDT)
Date: Wed, 24 Oct 2012 05:05:44 +0000 (UTC)
From: Ian Hickson <ian@hixie.ch>
To: "Manger, James H" <James.H.Manger@team.telstra.com>,  David Sheets <kosmo.zb@gmail.com>
Subject: RE: [whatwg] New URL Standard from Anne van Kesteren on 2012-09-24 (public-whatwg-archive@w3.org from September 2012)
In-Reply-To: <CAAWM5Tz3NdprjqwgyoVoV9qUuiwXb2gTQ49u4a4ePGfjyusDkw@mail.gmail.com>
Message-ID: <Pine.LNX.4.64.1210240451150.2471@ps20323.dreamhostps.com>
References: <50604C1A.7090901@gmx.de> <5060A964.5060001@stpeter.im> <Pine.LNX.4.64.1210172354500.2478@ps20323.dreamhostps.com> <507F5A7E.6040206@arcanedomain.com> <50856E3C.103@gmail.com> <Pine.LNX.4.64.1210221753010.2471@ps20323.dreamhostps.com> <0DBC8A11-319C-4120-975E-7E40FD5818BF@gbiv.com> <Pine.LNX.4.64.1210222137530.2471@ps20323.dreamhostps.com> <CA+9kkMDpEZCvcG1DJd=O1qPNV+=+GTBeN+CGndUe51Xym_A9sg@mail.gmail.com> <Pine.LNX.4.64.1210232115210.2471@ps20323.dreamhostps.com> <15E1D98B-8883-4936-81A9-174E1323683C@nordsc.com> <CAGKvQ5ZV6_GMVgjEezhR-oKqSikxR7GYgacMitbfczmNh725mw@mail.gmail.com> <Pine.LNX.4.64.1210232348110.2471@ps20323.dreamhostps.com> <CAAWM5Tz3NdprjqwgyoVoV9qUuiwXb2gTQ49u4a4ePGfjyusDkw@mail.gmail.com>
Content-Language: en-GB-hixie
Content-Style-Type: text/css
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Mailman-Approved-At: Wed, 24 Oct 2012 08:37:10 -0700
Cc: Ted Hardie <ted.ietf@gmail.com>, IETF Discussion <ietf@ietf.org>, Christophe Lauret <clauret@weborganic.com>, Jan Algermissen <jan.algermissen@nordsc.com>, URI <uri@w3.org>, Anne van Kesteren <annevk@annevk.nl>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Oct 2012 05:05:51 -0000

On Wed, 24 Oct 2012, Manger, James H wrote:
> 
> Currently, I don't think url.spec.whatwg.org distinguishes between 
> strings that are valid URLs and strings that can be interpreted as URLs 
> by applying its standardised error handling. Consequently, error 
> handling cannot be at the option of the software developer as you cannot 
> tell which bits are error handling.

Well first, the whole point of discussions like this is to work out what 
the specs _should_ say; if the specs were perfect then there wouldn't be 
any need for discussion.

But second, I believe it's already Anne's intention to add to the parsing 
algorithm the ability to abort whenever the URL isn't conforming, he just 
hasn't done that yet because he hasn't specced what's conforming in the 
first place.


On Tue, 23 Oct 2012, David Sheets wrote:
> 
> One algorithm? There seem to be several functions...
> 
> - URI reference parsing (parse : scheme -> string -> raw uri_ref)
> - URI reference normalization (normalize : raw uri_ref -> normal uri_ref)
> - absolute URI predicate (absp : normal uri_ref -> absolute uri_ref option)
> - URI resolution (resolve : absolute uri_ref -> _ uri_ref -> absolute uri_ref)

I don't understand what your four algorithms are supposed to be.

There's just one algorithm as far as I can tell -- it takes as input an 
arbitrary string and a base URL object, and returns a normalised absolute 
URL object, where a "URL object" is a conceptual construct consisting of 
the components scheme, userinfo, host, port, path, query, and 
fragment, which can be serialised together into a string form.

(I guess you could count the serialiser as a second algorithm, in which 
case there's two.)


> Anne's current draft increases the space of valid addresses.

No, Anne hasn't finished defining conformance yet. (He just started 
today.)

You may be getting confused by the "invalid flag", which doesn't mean the 
input is non-conforming, but means that the input is uninterpretable.


> > The de facto parsing rules are already complicated by de facto 
> > requirements for handling errors, so defining those doesn't increase 
> > complexity either (especially if such behaviour is left as optional, 
> > as discussed above.)
> 
> *parse* is separate from *normalize* is separate from checking if a 
> reference is absolute (*absp*) is separate from *resolve*.

No, it doesn't have to be. That's actually a more complicated way of 
looking at it than necessary, IMHO.


> Why don't we have a discussion about the functions and types involved in 
> URI processing?
>
> Why don't we discuss expanding allowable alphabets and production rules?

Personally I think this kind of open-ended approach is not a good way to 
write specs. Better is to put forward concrete use cases, technical data, 
etc, and let the spec editor take all that into account and turn it into a 
standard. Arguing about what precise alphabets are allowed and whether to 
spec something using prose or production rules is just bikeshedding.

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'

From James.H.Manger@team.telstra.com  Tue Oct 23 23:41:22 2012
Return-Path: <James.H.Manger@team.telstra.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1583621F8D28 for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 23:41:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.928
X-Spam-Level: 
X-Spam-Status: No, score=-0.928 tagged_above=-999 required=5 tests=[AWL=-0.027, BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327, RELAY_IS_203=0.994]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9-SKMCSF13bU for <ietf@ietfa.amsl.com>; Tue, 23 Oct 2012 23:41:21 -0700 (PDT)
Received: from ipxbvo.tcif.telstra.com.au (ipxbvo.tcif.telstra.com.au [203.35.135.204]) by ietfa.amsl.com (Postfix) with ESMTP id D26D021F8D17 for <ietf@ietf.org>; Tue, 23 Oct 2012 23:41:20 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.80,639,1344175200"; d="scan'208";a="99840902"
Received: from unknown (HELO ipcavi.tcif.telstra.com.au) ([10.97.217.200]) by ipobvi.tcif.telstra.com.au with ESMTP; 24 Oct 2012 17:41:18 +1100
X-IronPort-AV: E=McAfee;i="5400,1158,6874"; a="139545093"
Received: from wsmsg3755.srv.dir.telstra.com ([172.49.40.196]) by ipcavi.tcif.telstra.com.au with ESMTP; 24 Oct 2012 17:41:17 +1100
Received: from WSMSG3153V.srv.dir.telstra.com ([172.49.40.159]) by WSMSG3755.srv.dir.telstra.com ([172.49.40.196]) with mapi; Wed, 24 Oct 2012 17:41:17 +1100
From: "Manger, James H" <James.H.Manger@team.telstra.com>
To: Ian Hickson <ian@hixie.ch>, David Sheets <kosmo.zb@gmail.com>
Date: Wed, 24 Oct 2012 17:41:16 +1100
Subject: RE: [whatwg] New URL Standard from Anne van Kesteren on 2012-09-24 (public-whatwg-archive@w3.org from September 2012)
Thread-Topic: [whatwg] New URL Standard from Anne van Kesteren on 2012-09-24 (public-whatwg-archive@w3.org from September 2012)
Thread-Index: Ac2xpTwYvMOy7vTuSDmxHNM3EVsdUwAAYabg
Message-ID: <255B9BB34FB7D647A506DC292726F6E114FE0A3DE8@WSMSG3153V.srv.dir.telstra.com>
References: <50604C1A.7090901@gmx.de> <5060A964.5060001@stpeter.im> <Pine.LNX.4.64.1210172354500.2478@ps20323.dreamhostps.com> <507F5A7E.6040206@arcanedomain.com> <50856E3C.103@gmail.com> <Pine.LNX.4.64.1210221753010.2471@ps20323.dreamhostps.com> <0DBC8A11-319C-4120-975E-7E40FD5818BF@gbiv.com> <Pine.LNX.4.64.1210222137530.2471@ps20323.dreamhostps.com> <CA+9kkMDpEZCvcG1DJd=O1qPNV+=+GTBeN+CGndUe51Xym_A9sg@mail.gmail.com> <Pine.LNX.4.64.1210232115210.2471@ps20323.dreamhostps.com> <15E1D98B-8883-4936-81A9-174E1323683C@nordsc.com> <CAGKvQ5ZV6_GMVgjEezhR-oKqSikxR7GYgacMitbfczmNh725mw@mail.gmail.com> <Pine.LNX.4.64.1210232348110.2471@ps20323.dreamhostps.com> <CAAWM5Tz3NdprjqwgyoVoV9qUuiwXb2gTQ49u4a4ePGfjyusDkw@mail.gmail.com> <Pine.LNX.4.64.1210240451150.2471@ps20323.dreamhostps.com>
In-Reply-To: <Pine.LNX.4.64.1210240451150.2471@ps20323.dreamhostps.com>
Accept-Language: en-US, en-AU
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-AU
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Mailman-Approved-At: Wed, 24 Oct 2012 08:37:10 -0700
Cc: Ted Hardie <ted.ietf@gmail.com>, IETF Discussion <ietf@ietf.org>, Christophe Lauret <clauret@weborganic.com>, Jan Algermissen <jan.algermissen@nordsc.com>, URI <uri@w3.org>, Anne van Kesteren <annevk@annevk.nl>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Oct 2012 06:41:22 -0000

PiBPbiBXZWQsIDI0IE9jdCAyMDEyLCBNYW5nZXIsIEphbWVzIEggd3JvdGU6DQo+ID4NCj4gPiBD
dXJyZW50bHksIEkgZG9uJ3QgdGhpbmsgdXJsLnNwZWMud2hhdHdnLm9yZyBkaXN0aW5ndWlzaGVz
IGJldHdlZW4NCj4gPiBzdHJpbmdzIHRoYXQgYXJlIHZhbGlkIFVSTHMgYW5kIHN0cmluZ3MgdGhh
dCBjYW4gYmUgaW50ZXJwcmV0ZWQgYXMNCj4gPiBVUkxzIGJ5IGFwcGx5aW5nIGl0cyBzdGFuZGFy
ZGlzZWQgZXJyb3IgaGFuZGxpbmcuIENvbnNlcXVlbnRseSwgZXJyb3INCj4gPiBoYW5kbGluZyBj
YW5ub3QgYmUgYXQgdGhlIG9wdGlvbiBvZiB0aGUgc29mdHdhcmUgZGV2ZWxvcGVyIGFzIHlvdQ0K
PiA+IGNhbm5vdCB0ZWxsIHdoaWNoIGJpdHMgYXJlIGVycm9yIGhhbmRsaW5nLg0KDQo+IFdlbGwg
Zmlyc3QsIHRoZSB3aG9sZSBwb2ludCBvZiBkaXNjdXNzaW9ucyBsaWtlIHRoaXMgaXMgdG8gd29y
ayBvdXQNCj4gd2hhdCB0aGUgc3BlY3MgX3Nob3VsZF8gc2F5OyBpZiB0aGUgc3BlY3Mgd2VyZSBw
ZXJmZWN0IHRoZW4gdGhlcmUNCj4gd291bGRuJ3QgYmUgYW55IG5lZWQgZm9yIGRpc2N1c3Npb24u
DQo+IA0KPiBCdXQgc2Vjb25kLCBJIGJlbGlldmUgaXQncyBhbHJlYWR5IEFubmUncyBpbnRlbnRp
b24gdG8gYWRkIHRvIHRoZQ0KPiBwYXJzaW5nIGFsZ29yaXRobSB0aGUgYWJpbGl0eSB0byBhYm9y
dCB3aGVuZXZlciB0aGUgVVJMIGlzbid0DQo+IGNvbmZvcm1pbmcsIGhlIGp1c3QgaGFzbid0IGRv
bmUgdGhhdCB5ZXQgYmVjYXVzZSBoZSBoYXNuJ3Qgc3BlY2NlZA0KPiB3aGF0J3MgY29uZm9ybWlu
ZyBpbiB0aGUgZmlyc3QgcGxhY2UuDQoNClRoYXQgaXMgZ29vZCB0byBoZWFyLiBUaGVyZSBpcyBu
byBoaW50IGFib3V0IHRoaXMgaW4gdGhlIGN1cnJlbnQgdGV4dC9vdXRsaW5lLiBUaGVyZSBpcyBh
biAiaW52YWxpZCIgZmxhZyBpbiB0aGUgY3VycmVudCB0ZXh0IC0tIGJ1dCB0aGF0IGlzIGZvciBz
dHJpbmdzIHRoYXQgYXJlIHNvIGJyb2tlbiBubyBlcnJvciBoYW5kbGluZyBjYW4gcmVzdXJyZWN0
IGEgVVJMLiBUaGVyZSBpcyBubyBtZW50aW9uIG9mIGEgc2VwYXJhdGUgImNvbmZvcm1pbmciIGZs
YWcsIGV2ZW4gaWYgdGhlIHJ1bGVzIGZvciB3aGVuIHRvIHNldCBpdCBhcmUgeWV0IHRvIGJlIGZp
eGVkICh0aG91Z2ggaXQgc2hvdWxkIGhhdmUgYmVlbiBlYXN5IHRvIHNheSBjb25mb3JtaW5nPWNv
bmZvcm1pbmctYXMtcGVyLXJmYzM5ODcvMzk4NyBpZiB0aGF0IHdhcyB0aGUgaW50ZW50aW9uKS4N
Cg0KQXNzdW1pbmcgdGhpcyBpcyBBbm5lJ3MgaW50ZW50aW9uLCB0aGVuIDEgc3BlYyBmb3IgVVJJ
L0lSSS9lcnJvci1oYW5kbGluZyB3b3VsZCBiZSBoZWxwZnVsLiBJJ20gbm90IHN1cmUgdGhhdCBw
YXJzaW5nIHJ1bGVzIHdpdGggY29uZm9ybWluZy9ub24tY29uZm9ybWluZyBicmFuY2hlcyB3b3Vs
ZCBiZSBwcmV0dHksIGJ1dCBwZXJoYXBzIHRoaXMgaXNuJ3QgbmVjZXNzYXJ5IGlmIHdoYXQgYSBj
b25mb3JtaW5nIFVSTCBpcyBpcyBjbGVhciBmcm9tIG90aGVyIHBhcnRzIG9mIHRoZSBzcGVjLg0K
DQotLQ0KSmFtZXMgTWFuZ2VyDQoNCg==

From annevankesteren@gmail.com  Wed Oct 24 01:14:39 2012
Return-Path: <annevankesteren@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DEE8921F889A for <ietf@ietfa.amsl.com>; Wed, 24 Oct 2012 01:14:29 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OYB2z+x2M5yx for <ietf@ietfa.amsl.com>; Wed, 24 Oct 2012 01:14:28 -0700 (PDT)
Received: from mail-wg0-f44.google.com (mail-wg0-f44.google.com [74.125.82.44]) by ietfa.amsl.com (Postfix) with ESMTP id 7B9F121F880B for <ietf@ietf.org>; Wed, 24 Oct 2012 01:14:27 -0700 (PDT)
Received: by mail-wg0-f44.google.com with SMTP id dr13so132076wgb.13 for <ietf@ietf.org>; Wed, 24 Oct 2012 01:14:25 -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=pbuyi/ochG37amaR8kNydcWl+eafwaMNPbNmc/3lT/A=; b=S6lEg/DsVm+etgV1BJ05eyIdf2FzahPdOer9yoUQGOHBFkVEDbj//jnRs1eCSTO/W8 zxbL/kZnNl87PiJCMKG5zDcbtAVUwfijn6Cdyx48esVjm7wKVaK9J1vMuukdAqsRFTZ4 +4LBf2Lvzj700MDHRDdDjJigj5MJulvSKwyLwN4TLQfJ00jFNImqV5w2uSUovmmAEu5B xv58AHGP3nN/fxSWnCo1JYEh6Sa4XjUuDbZdY66zBUOUMeSteKauW7ahizlQvTse1PmM A9jaax9tNqITQS9LEnx7+297n9KxQ3Yf+UWY+/ESkv2/CGqwCyyfTLV1ncQRHETvBPSy XOZQ==
MIME-Version: 1.0
Received: by 10.180.84.202 with SMTP id b10mr3959020wiz.13.1351066465259; Wed, 24 Oct 2012 01:14:25 -0700 (PDT)
Sender: annevankesteren@gmail.com
Received: by 10.223.145.195 with HTTP; Wed, 24 Oct 2012 01:14:25 -0700 (PDT)
In-Reply-To: <255B9BB34FB7D647A506DC292726F6E114FE0A3DE8@WSMSG3153V.srv.dir.telstra.com>
References: <50604C1A.7090901@gmx.de> <5060A964.5060001@stpeter.im> <Pine.LNX.4.64.1210172354500.2478@ps20323.dreamhostps.com> <507F5A7E.6040206@arcanedomain.com> <50856E3C.103@gmail.com> <Pine.LNX.4.64.1210221753010.2471@ps20323.dreamhostps.com> <0DBC8A11-319C-4120-975E-7E40FD5818BF@gbiv.com> <Pine.LNX.4.64.1210222137530.2471@ps20323.dreamhostps.com> <CA+9kkMDpEZCvcG1DJd=O1qPNV+=+GTBeN+CGndUe51Xym_A9sg@mail.gmail.com> <Pine.LNX.4.64.1210232115210.2471@ps20323.dreamhostps.com> <15E1D98B-8883-4936-81A9-174E1323683C@nordsc.com> <CAGKvQ5ZV6_GMVgjEezhR-oKqSikxR7GYgacMitbfczmNh725mw@mail.gmail.com> <Pine.LNX.4.64.1210232348110.2471@ps20323.dreamhostps.com> <CAAWM5Tz3NdprjqwgyoVoV9qUuiwXb2gTQ49u4a4ePGfjyusDkw@mail.gmail.com> <Pine.LNX.4.64.1210240451150.2471@ps20323.dreamhostps.com> <255B9BB34FB7D647A506DC292726F6E114FE0A3DE8@WSMSG3153V.srv.dir.telstra.com>
Date: Wed, 24 Oct 2012 10:14:25 +0200
X-Google-Sender-Auth: _1W0xeGZcj0d-Y8dHOgOk9Tpohc
Message-ID: <CADnb78ggmdj6AtZNA14j+-j2WMvkv_juOkV5JZMGmkNjn3P+tw@mail.gmail.com>
Subject: Re: [whatwg] New URL Standard from Anne van Kesteren on 2012-09-24 (public-whatwg-archive@w3.org from September 2012)
From: Anne van Kesteren <annevk@annevk.nl>
To: "Manger, James H" <James.H.Manger@team.telstra.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Wed, 24 Oct 2012 08:37:10 -0700
Cc: Ted Hardie <ted.ietf@gmail.com>, IETF Discussion <ietf@ietf.org>, Christophe Lauret <clauret@weborganic.com>, Jan Algermissen <jan.algermissen@nordsc.com>, URI <uri@w3.org>, David Sheets <kosmo.zb@gmail.com>, Ian Hickson <ian@hixie.ch>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Oct 2012 08:16:21 -0000

On Wed, Oct 24, 2012 at 8:41 AM, Manger, James H
<James.H.Manger@team.telstra.com> wrote:
> That is good to hear. There is no hint about this in the current text/out=
line. There is an "invalid" flag in the current text -- but that is for str=
ings that are so broken no error handling can resurrect a URL. There is no =
mention of a separate "conforming" flag, even if the rules for when to set =
it are yet to be fixed (though it should have been easy to say conforming=
=3Dconforming-as-per-rfc3987/3987 if that was the intention).

Thanks for pointing that out. I renamed it to "fatal error flag" and
added an issue about the ability to halt on the first (non-fatal)
error. Ian is right that it's not defined yet because conformance is
not defined. And yes, as you say I've yet to figure out if branches in
the parser section is easy enough to do. If it is I think it's
worthwhile because it makes implementing a conformance checker (or
strict parser) much more straightforward.


--=20
http://annevankesteren.nl/

From jan.algermissen@nordsc.com  Wed Oct 24 04:05:01 2012
Return-Path: <jan.algermissen@nordsc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9A27521F8869 for <ietf@ietfa.amsl.com>; Wed, 24 Oct 2012 04:05:01 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Tthl4LbcPRfB for <ietf@ietfa.amsl.com>; Wed, 24 Oct 2012 04:04:59 -0700 (PDT)
Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.17.8]) by ietfa.amsl.com (Postfix) with ESMTP id 3530121F886A for <ietf@ietf.org>; Wed, 24 Oct 2012 04:04:59 -0700 (PDT)
Received: from [10.90.128.69] ([87.253.171.220]) by mrelayeu.kundenserver.de (node=mreu3) with ESMTP (Nemesis) id 0LfcCc-1T6XAT3AuQ-00pJsP; Wed, 24 Oct 2012 13:04:23 +0200
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: [whatwg] New URL Standard from Anne van Kesteren on 2012-09-24 (public-whatwg-archive@w3.org from September 2012)
From: Jan Algermissen <jan.algermissen@nordsc.com>
In-Reply-To: <Pine.LNX.4.64.1210232347280.2471@ps20323.dreamhostps.com>
Date: Wed, 24 Oct 2012 13:04:25 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <85621CE2-4ACD-499F-AFBF-AE7BA18F3666@nordsc.com>
References: <50604C1A.7090901@gmx.de> <5060A964.5060001@stpeter.im> <Pine.LNX.4.64.1210172354500.2478@ps20323.dreamhostps.com> <507F5A7E.6040206@arcanedomain.com> <50856E3C.103@gmail.com> <Pine.LNX.4.64.1210221753010.2471@ps20323.dreamhostps.com> <0DBC8A11-319C-4120-975E-7E40FD5818BF@gbiv.com> <Pine.LNX.4.64.1210222137530.2471@ps20323.dreamhostps.com> <CA+9kkMDpEZCvcG1DJd=O1qPNV+=+GTBeN+CGndUe51Xym_A9sg@mail.gmail.com> <Pine.LNX.4.64.1210232115210.2471@ps20323.dreamhostps.com> <15E1D98B-8883-4936-81A9-174E1323683C@nordsc.com> <Pine.LNX.4.64.1210232234590.2471@ps20323.dreamhostps.com> <8CC5FA04-2F61-408F-AED5-792E086E9BA0@nordsc.com> <Pine.LNX.4.64.1210232347280.2471@ps20323.dreamhostps.com>
To: Ian Hickson <ian@hixie.ch>
X-Mailer: Apple Mail (2.1499)
X-Provags-ID: V02:K0:BSqQwnGFEWoY3QL90e4vZvFw++WYE3GwEEpvMSA/MSt Wq1XUb1UGon0C0DOkUsNUKj29hUN/RNGM1w56r4vvPrVidXV3Q CYHR/VT0B07AuIW2j0C1CVVJ4aNLPPXYAv9oRkaeYrsd2Xd7lk ch063BTwtkjpQsngXdhuonQ5cdZWU2x3ZaNHcr9C++dvDumnC7 OKX0AnHLn5gCe0DmjCGpFpMIQmsbpJ6tXAJKejZFBkN8uNRSM+ 5GExJhXLV6kNCUfNexwwSQjmUtAuVZhbGfFxyFOgqUuwhGJ7Am 7G4y6kW5ntPmaR6mVIN0rhGwZx6DkvKEQIYI5s6pA+tX7kiHUP enYo7QZeXk2wH+ijM+jWe/jfwY3HpMrI9ld5p76fF9HQiOdhgu xn6bag/zthrHg==
X-Mailman-Approved-At: Wed, 24 Oct 2012 08:37:10 -0700
Cc: Ted Hardie <ted.ietf@gmail.com>, Jan Algermissen <jan.algermissen@nordsc.com>, URI <uri@w3.org>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Oct 2012 11:05:01 -0000

On Oct 24, 2012, at 1:47 AM, Ian Hickson <ian@hixie.ch> wrote:

> On Wed, 24 Oct 2012, Jan Algermissen wrote:
>>=20
>> What matters is that nothing of the existing URI spec *changes*.
>>=20
>> Can you agree on that?
>=20
> Do you mean the actual text, or the normative meaning of the text?

I ideally mean the actual text, but it might be that there is some =
overlap in the construction algorithms - I am not expert enough there to =
judge that.

The point really was to make it very clear that *additional* stuff is =
going to be said and that existing implementations that follow the URI =
spec strictly remain conforming.

Jan


>=20
> --=20
> Ian Hickson               U+1047E                )\._.,--....,'``.    =
fL
> http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ =
,.
> Things that are impossible just take longer.   =
`._.-(,_..'--(,_..'`-.;.'
>=20


From john-ietf@jck.com  Wed Oct 24 04:38:58 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 D1B4D21F8B94 for <ietf@ietfa.amsl.com>; Wed, 24 Oct 2012 04:38:58 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iSSs5MyAlfTL for <ietf@ietfa.amsl.com>; Wed, 24 Oct 2012 04:38:58 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 4B05D21F8B93 for <ietf@ietf.org>; Wed, 24 Oct 2012 04:38:58 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1TQzIM-000CP6-2b; Wed, 24 Oct 2012 07:38:46 -0400
Date: Wed, 24 Oct 2012 07:38:41 -0400
From: John C Klensin <john-ietf@jck.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Mark Nottingham <mnot@mnot.net>
Subject: Re: [whatwg] New URL Standard from Anne van Kesteren on 2012-09-24	(public-whatwg-archive@w3.org from September 2012)
Message-ID: <67FF7890FC3B18EF24B48C89@JcK-HP8200.jck.com>
In-Reply-To: <5087C57A.80607@gmail.com>
References: <50604C1A.7090901@gmx.de> <5060A964.5060001@stpeter.im> <Pine.LNX.4.64.1210172354500.2478@ps20323.dreamhostps.com> <507F5A7E.6040206@arcanedomain.com> <50856E3C.103@gmail.com> <Pine.LNX.4.64.1210221753010.2471@ps20323.dreamhostps.com> <0DBC8A11-319C-4120-975E-7E40FD5818BF@gbiv.com> <Pine.LNX.4.64.1210222137530.2471@ps20323.dreamhostps.com> <5085C4BA.2030505@gmx.de> <Pine.LNX.4.64.1210222220510.2471@ps20323.dreamhostps.com> <CAHBU6is8LNZ7Rq-vwLuOm+8ThKB9c=QPwbUfQwDQD5bDPjtf7w@mail.gmail.com> <Pine.LNX.4.64.1210222320070.2471@ps20323.dreamhostps.com> <09DC68AA-2DAD-4CB1-9CA9-799AF12B7BE2@mnot.net> <5087C57A.80607@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-Mailman-Approved-At: Wed, 24 Oct 2012 08:37:10 -0700
Cc: IETF Discussion <ietf@ietf.org>, Julian Reschke <julian.reschke@gmx.de>, "Roy T. Fielding" <fielding@gbiv.com>, Jan Algermissen <jan.algermissen@nordsc.com>, Noah Mendelsohn <nrm@arcanedomain.com>, URI <uri@w3.org>, Tim Bray <tbray@textuality.com>, Ian Hickson <ian@hixie.ch>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Oct 2012 11:38:59 -0000

--On Wednesday, October 24, 2012 11:39 +0100 Brian E Carpenter
<brian.e.carpenter@gmail.com> wrote:

> 
> On 23/10/2012 00:32, Mark Nottingham wrote:
> ...
>> The underlying point that people seem to be making is that
>> there's legitimate need for URIs to be a separate concept
>> from "strings that will become URIs." By collapsing them into
>> one thing, you're doing those folks a disservice. Browser
>> implementers may not care, but it's pretty obvious that lots
>> of other people do.
> 
> Thanks for bringing this point out. It was explained to me in
> 1993 by TBL and Robert Cailliau that URLs (the only term used
> then, I think) should never be typed in by a user, and
> preferably never even seen by a user. It's because that
> doctrine was abandoned a year or so later that we have this
> problem today. I think there would be value in a document
> making this clear, as a framework for clearly separating the
> specification of what is allowable as a URI on the wire from
> what is acceptable as a user input string (UIS?).
> 
> UIS to URI conversion may well end up as a heuristic algorithm.

Very useful perspective, IMO.

Seen that way, IRIs might then be considered a different flavor
of UIS.  Less heuristic than some, but not a flavor of URI.

best,
   john


From margaretw42@gmail.com  Wed Oct 24 05:49:26 2012
Return-Path: <margaretw42@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0A9E321F86C9 for <ietf@ietfa.amsl.com>; Wed, 24 Oct 2012 05:49: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=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 77RRtzAqjbL8 for <ietf@ietfa.amsl.com>; Wed, 24 Oct 2012 05:49:25 -0700 (PDT)
Received: from mail-vc0-f172.google.com (mail-vc0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 577A221F86C4 for <ietf@ietf.org>; Wed, 24 Oct 2012 05:49:25 -0700 (PDT)
Received: by mail-vc0-f172.google.com with SMTP id fl11so526646vcb.31 for <ietf@ietf.org>; Wed, 24 Oct 2012 05:49:24 -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=JXHUr5zfNY9VQXYHejv67CThlLm+n4OO4oBQEriZlU0=; b=FG/Eh5rmiDvF4Apu5a181LtNueLNhQ+3muHwV36HMx5YjRYytDkcz3oqeO14EmWKiW gfmEGhyRvhBSVsTKTw9ffvj9CFpeQiP9CDMPolJAqKNzjQKo2SUQ7Q33Jbq2vrwq9GY4 YvLFTPYKbLyqIpr4KgtE+5FpK0z7P9SJnov+0MnL+n1lIkHBQmqFPOatiVdx5oob9Fld LeQJQkXIBkDyUt0leSwGUTakSQ+iWVoFWkhzTCru4k+/ZobigFSybwa81dRfQAylICws h3yJRgMS2KZPjfekcoJ5tGh7+1qu5cEYmpXr/tP3ndQuefVo8Fi4vTiWU6NSQ8WqUa3H c1qw==
Received: by 10.220.157.15 with SMTP id z15mr25527390vcw.38.1351082964773; Wed, 24 Oct 2012 05:49:24 -0700 (PDT)
Received: from lilac-too.home (pool-71-184-79-25.bstnma.fios.verizon.net. [71.184.79.25]) by mx.google.com with ESMTPS id t12sm16052246vdi.18.2012.10.24.05.49.09 (version=SSLv3 cipher=OTHER); Wed, 24 Oct 2012 05:49:16 -0700 (PDT)
Subject: Re: Just so I'm clear
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Margaret Wasserman <margaretw42@gmail.com>
In-Reply-To: <50877633.1000402@dougbarton.us>
Date: Wed, 24 Oct 2012 08:49:09 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <EA9BEA2E-EE96-4E80-B719-652BBD620A79@lilacglade.org>
References: <20121023192135.203AC18C0A4@mercury.lcs.mit.edu> <5086EF82.9060900@dougbarton.us> <20121023200713.GC1861@nsn.com> <5086FBCE.2070503@dougbarton.us> <20121023213251.GF27557@verdi> <50873AB4.1000905@dougbarton.us> <20121024034736.GC52558@crankycanuck.ca> <50876D39.20502@dougbarton.us> <508773E7.10203@cisco.com> <50877633.1000402@dougbarton.us>
To: Doug Barton <dougb@dougbarton.us>
X-Mailer: Apple Mail (2.1084)
X-Mailman-Approved-At: Wed, 24 Oct 2012 08:37:10 -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: Wed, 24 Oct 2012 12:49:26 -0000

On Oct 24, 2012, at 1:01 AM, Doug Barton wrote:
> I get what you're saying, but this is one of those times where =
(arguably
> for the better) we've created a difficult procedure that should be
> infrequently exercised. We should follow the procedure because it _is_
> the procedure. And then use the opportunity to improve it.

The existence of the recall procedure does not imply that there isn't =
any other way for a seat to become vacant.  For example, a seat can =
become vacant when an I* member resigns or dies, and there is no need =
for a recall in those cases. =20

I think it is reasonable for the IAOC to set it's own (reasonable, =
consistent) bar for deciding that a sitting member has vacated his/her =
seat through lack of attendance and lack of response.  No recall should =
be needed in that case to replace the missing member, any more than if =
the person had explicitly resigned.  The IAOC sent a long list of things =
that they have done to contact Marshall, and he has not responded.  It =
seems impossible that he has not received any of those contacts, so his =
lack of response is indicative, IMO, that he has indeed vacated his =
seat.

I share the hope of the IAOC and others that Marshall is okay, and that =
he will return to the IETF when he can.  I appreciate his contributions =
throughout the years, and I would be happy to see him return to continue =
making those contributions.  For now, though, he has vacated his IAOC =
seat and should be replaced.

Margaret





From bob.hinden@gmail.com  Wed Oct 24 08:37:35 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 294CF21F8C1A for <ietf@ietfa.amsl.com>; Wed, 24 Oct 2012 08:37:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.596
X-Spam-Level: 
X-Spam-Status: No, score=-103.596 tagged_above=-999 required=5 tests=[AWL=0.003, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wzvJ6xp00ac9 for <ietf@ietfa.amsl.com>; Wed, 24 Oct 2012 08:37:34 -0700 (PDT)
Received: from mail-bk0-f44.google.com (mail-bk0-f44.google.com [209.85.214.44]) by ietfa.amsl.com (Postfix) with ESMTP id E78FF21F8C10 for <ietf@ietf.org>; Wed, 24 Oct 2012 08:37:33 -0700 (PDT)
Received: by mail-bk0-f44.google.com with SMTP id jc3so310781bkc.31 for <ietf@ietf.org>; Wed, 24 Oct 2012 08:37:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=gBKEx8x12ARv5UsIVSCrf/cyc66GyCmQZsb51z6JhuQ=; b=FkR+jnA6Z8FYklzc8OEe0oaUpVGLSFFEX08JVBj6Z6YO7R84opqWMwEt0HpuPRxT2o 5YY4MVae33MzeuxScFy7fMjB8Eg8SIflX34Z9d+BCSAMnB+NsKCi2Kbm6kMiuccFc612 sCcW6sOqEmuj1VXK4xKceRKVndLiYCLEjq9VCY6CQ6wW7IqvOUhLgXikf/8AJfqV0xr8 CcDEMrFrWHId2nI9yebnaGJu+u4+BUBoA2PHd8B/uXnILuFo4dpWnhK+hNFU3ako7wO8 HlnfbvPn/wSNBenCIeWJVgQNovRJjuLcz0ar6A49fkeDiZ8QosplarmF4nBf6NwtJWBU Ko7w==
Received: by 10.204.129.213 with SMTP id p21mr4906962bks.115.1351093052599; Wed, 24 Oct 2012 08:37:32 -0700 (PDT)
Received: from ?IPv6:2601:9:4080:10:25b4:6ba3:3bdc:c25e? ([2601:9:4080:10:25b4:6ba3:3bdc:c25e]) by mx.google.com with ESMTPS id x13sm8612555bkv.16.2012.10.24.08.37.28 (version=SSLv3 cipher=OTHER); Wed, 24 Oct 2012 08:37:32 -0700 (PDT)
Subject: Re: IAOC Request for community feedback
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=us-ascii
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <F7DE7677-5ADA-4FEF-B383-DF91535FB291@gmail.com>
Date: Wed, 24 Oct 2012 08:37:23 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <B2DB1626-83E1-461E-89DB-E26176BD65C0@gmail.com>
References: <20121023211128.773D018C0A0@mercury.lcs.mit.edu> <1FB012B6-672D-47DD-92A5-81084E833136@gmail.com> <F7DE7677-5ADA-4FEF-B383-DF91535FB291@gmail.com>
To: ietf@ietf.org
X-Mailer: Apple Mail (2.1283)
Cc: Bob Hinden <bob.hinden@gmail.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Oct 2012 15:37:35 -0000

Since a few people are asking questions that were answered in the =
original email, here is a link to the mail that was sent to =
ietf-announce on October 22, 2012:

   =
https://www.ietf.org/ibin/c5i?mid=3D6&rid=3D49&gid=3D0&k1=3D934&k2=3D11277=
&tid=3D1351092666

I thought this would be helpful since it was only sent to ietf-announce, =
not to the IETF list.

Bob



From alh-ietf@tndh.net  Wed Oct 24 08:41:30 2012
Return-Path: <alh-ietf@tndh.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 897EF21F8C03 for <ietf@ietfa.amsl.com>; Wed, 24 Oct 2012 08:41:30 -0700 (PDT)
X-Quarantine-ID: <q2puMqHdOZ-M>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Improper folded header field made up entirely of whitespace (char 20 hex): X-Spam-Report: ...that system for details.\n \n Content previ[...]
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q2puMqHdOZ-M for <ietf@ietfa.amsl.com>; Wed, 24 Oct 2012 08:41:30 -0700 (PDT)
Received: from express.tndh.net (express.tndh.net [IPv6:2001:470:e930:1240:20d:56ff:fe04:4c0a]) by ietfa.amsl.com (Postfix) with ESMTP id EA25D21F8C06 for <ietf@ietf.org>; Wed, 24 Oct 2012 08:41:29 -0700 (PDT)
Received: from [172.20.144.31] (helo=eaglet) by express.tndh.net with esmtp (Exim 4.72 (FreeBSD)) (envelope-from <alh-ietf@tndh.net>) id 1TR359-000LED-WD for ietf@ietf.org; Wed, 24 Oct 2012 08:41:29 -0700
From: "Tony Hain" <alh-ietf@tndh.net>
To: <ietf@ietf.org>
References: <20121023192135.203AC18C0A4@mercury.lcs.mit.edu>	<5086EF82.9060900@dougbarton.us>	<20121023200713.GC1861@nsn.com> <508795D7.1050102@gmail.com> <alpine.LRH.2.01.1210240634310.32353@egate.xpasc.com>
In-Reply-To: <alpine.LRH.2.01.1210240634310.32353@egate.xpasc.com>
Subject: RE: IAOC Request for community feedback
Date: Wed, 24 Oct 2012 08:41:24 -0700
Message-ID: <015001cdb1fe$05dcac10$11960430$@tndh.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Content-Language: en-us
Thread-Index: AQHh8wyhXJPu+L+ckiGZSgshdBMy0gH3avBPAb9jkuIBbFxFLgM3Crajl10/0hA=
X-SA-Exim-Connect-IP: 172.20.144.31
X-SA-Exim-Mail-From: alh-ietf@tndh.net
X-SA-Exim-Scanned: No (on express.tndh.net); SAEximRunCond expanded to 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: Wed, 24 Oct 2012 15:41:30 -0000

> David Morris wrote:
> 
> On Wed, 24 Oct 2012, Brian E Carpenter wrote:
> 
> > Agreed. It could be used for that, but I don't see it as required.
> > We aren't dealing with alleged misbehaviour.
> 
> Where I come from failure to fulfill the duties of the position is
misbehaviour.

My thoughts exactly. 

To a first order the 'urgency' implied by those arguing to bypass the recall
process suggests masking another failure. 
In other words: failure to act on your part does not create a crisis on my
part ...

If the delay to run the recall process is creating a problem for the IAOC,
the petition for recall should have started earlier in parallel with ongoing
contact attempts. If contact occurred, the petition could have been
abandoned. On the other hand, since there is time to waste arguing to bypass
the recall process, there must not be any real urgency. 

While I can understand wanting to follow the simplest process, the expedient
thing to do is follow the established process no matter how long that takes,
because in the end you will end up there and will only have wasted time
trying to work around it.

As StJohns pointed out, there are repercussions outside the cozy den of the
old-boys&girls club here. Has anyone asked council for their take on his
points? If not, that should happen before anything else. 

Tony





From cabo@tzi.org  Wed Oct 24 08:53:23 2012
Return-Path: <cabo@tzi.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 21F3B21F8CA6 for <ietf@ietfa.amsl.com>; Wed, 24 Oct 2012 08:53:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.223
X-Spam-Level: 
X-Spam-Status: No, score=-106.223 tagged_above=-999 required=5 tests=[AWL=0.026, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id faSYbm9vWTUm for <ietf@ietfa.amsl.com>; Wed, 24 Oct 2012 08:53:22 -0700 (PDT)
Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) by ietfa.amsl.com (Postfix) with ESMTP id 2A45521F84D7 for <ietf@ietf.org>; Wed, 24 Oct 2012 08:53:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.3/8.14.3) with ESMTP id q9OFrAnW007856; Wed, 24 Oct 2012 17:53:10 +0200 (CEST)
Received: from [192.168.217.117] (p5489481E.dip.t-dialin.net [84.137.72.30]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 666D2B7F; Wed, 24 Oct 2012 17:53:09 +0200 (CEST)
Subject: Re: [whatwg] New URL Standard from Anne van Kesteren on 2012-09-24 (public-whatwg-archive@w3.org from September 2012)
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Content-Type: text/plain; charset=iso-8859-1
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <CAAWM5TypLoCA5EmLkb=n5ic8GDyAVmKXs=CcAYn66rb2quPeQg@mail.gmail.com>
Date: Wed, 24 Oct 2012 17:53:07 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <47BB91F7-5CC0-4A3F-ABBF-4A80A844ECA5@tzi.org>
References: <50856E3C.103@gmail.com> <Pine.LNX.4.64.1210221753010.2471@ps20323.dreamhostps.com> <0DBC8A11-319C-4120-975E-7E40FD5818BF@gbiv.com> <Pine.LNX.4.64.1210222137530.2471@ps20323.dreamhostps.com> <CA+9kkMDpEZCvcG1DJd=O1qPNV+=+GTBeN+CGndUe51Xym_A9sg@mail.gmail.com> <Pine.LNX.4.64.1210232115210.2471@ps20323.dreamhostps.com> <15E1D98B-8883-4936-81A9-174E1323683C@nordsc.com> <CAGKvQ5ZV6_GMVgjEezhR-oKqSikxR7GYgacMitbfczmNh725mw@mail.gmail.com> <Pine.LNX.4.64.1210232348110.2471@ps20323.dreamhostps.com> <CAAWM5Tz3NdprjqwgyoVoV9qUuiwXb2gTQ49u4a4ePGfjyusDkw@mail.gmail.com> <20121024035954.GA27268@mercury.ccil.org> <CAAWM5TypLoCA5EmLkb=n5ic8GDyAVmKXs=CcAYn66rb2quPeQg@mail.gmail.com>
To: David Sheets <kosmo.zb@gmail.com>
X-Mailer: Apple Mail (2.1499)
Cc: Ted Hardie <ted.ietf@gmail.com>, John Cowan <cowan@mercury.ccil.org>, IETF Discussion <ietf@ietf.org>, Christophe Lauret <clauret@weborganic.com>, Jan Algermissen <jan.algermissen@nordsc.com>, URI <uri@w3.org>, Ian Hickson <ian@hixie.ch>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Oct 2012 15:53:23 -0000

On Oct 24, 2012, at 06:20, David Sheets <kosmo.zb@gmail.com> wrote:

> WHATWGRL

Hey, call them EARLs.  Error-tolerant web-Address Repairing Labels or =
whatever.
(Just not URLs, that term is already taken in the Web.)

Gr=FC=DFe, Carsten


From bob.hinden@gmail.com  Wed Oct 24 09:14:15 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 3F70B21F88DD for <ietf@ietfa.amsl.com>; Wed, 24 Oct 2012 09:14:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.596
X-Spam-Level: 
X-Spam-Status: No, score=-103.596 tagged_above=-999 required=5 tests=[AWL=0.003, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Sl84r6qfysSl for <ietf@ietfa.amsl.com>; Wed, 24 Oct 2012 09:14:14 -0700 (PDT)
Received: from mail-bk0-f44.google.com (mail-bk0-f44.google.com [209.85.214.44]) by ietfa.amsl.com (Postfix) with ESMTP id 3E57321F86F4 for <ietf@ietf.org>; Wed, 24 Oct 2012 09:14:14 -0700 (PDT)
Received: by mail-bk0-f44.google.com with SMTP id jc3so330174bkc.31 for <ietf@ietf.org>; Wed, 24 Oct 2012 09:14:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:content-type:content-transfer-encoding:subject:date:message-id :cc:to:mime-version:x-mailer; bh=9wTn23GDwTdULEU4cSdeyxEsLKlez1EbMoELXyYhRsE=; b=iZyuM+N2dv5WTx7XXbaGUgX/A0qOIZSgImpHBuhyRDSy+hQ7Nr7rUqu4dta1z7XdtV bYSL/74NEnOdYEExy9UjfNS52xiJ5eCYLikqr7LWUZIvj8Cmmi52mboFrZpyOdkr6wA6 xiPn435xJ447yGVBiTkxrDsfdt2JE7lT88Z9xGYF7k3nFkRpjwUv5yUMQkIGWbaL9uns gdSbYFEXzIdj5vGb//uS+V6VEQZ6okdtVThl7B8Boqows3qh2uU2Rx9Azj6D4I9gGzp9 Ld+l7kQrLh6RCA9oymkGlmKlyhKOiy4u61MoPS28/WSBSpxaoEzQdVXO3VrPOdWRPYPW QUrg==
Received: by 10.204.12.205 with SMTP id y13mr5174278bky.46.1351095253374; Wed, 24 Oct 2012 09:14:13 -0700 (PDT)
Received: from ?IPv6:2601:9:4080:10:25b4:6ba3:3bdc:c25e? ([2601:9:4080:10:25b4:6ba3:3bdc:c25e]) by mx.google.com with ESMTPS id v14sm8636037bkv.10.2012.10.24.09.14.10 (version=SSLv3 cipher=OTHER); Wed, 24 Oct 2012 09:14:11 -0700 (PDT)
From: Bob Hinden <bob.hinden@gmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: [RFC 3777 Update for Vacancies]
Date: Wed, 24 Oct 2012 09:14:10 -0700
Message-Id: <D90D92A7-0906-4620-93A0-D116D15A10FA@gmail.com>
To: ietf@ietf.org
Mime-Version: 1.0 (Apple Message framework v1283)
X-Mailer: Apple Mail (2.1283)
Cc: Bob Hinden <bob.hinden@gmail.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Oct 2012 16:14:15 -0000

The draft that proposes changes to the RFC3777/BCP10 to deal with =
vacancies is now available.

  http://tools.ietf.org/html/draft-ietf-genarea-bcp10upd-00

Bob

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

From: Internet-Drafts@ietf.org=20
To: i-d-announce@ietf.org=20
Reply-to: Internet-Drafts@ietf.org=20
Subject: I-D ACTION:draft-ietf-genarea-bcp10upd-00.txt=20
X-C5I-RSN: 1/0/935/46939/50333=20
=20
A new Internet-Draft is available from the on-line Internet-Drafts =
directories.=20
=20
Title : RFC 3777 Update for Vacancies=20
Author(s) : D. Crocker, et al=20
Filename : draft-ietf-genarea-bcp10upd=20
Pages : 4 =20
Date : Oct. 24, 2012 =20
=20
BCP 10 (RFC 3777) specifies IETF processes for selection,=20
confirmation and recall of appointees to IETF positions. It also=20
refers to the mechanism of resignation as part of a sequence that=20
moves a sitting member to a new IETF position. However it does not=20
more generally deal with vacancies created by resignation, death or=20
uncontested, sustained absence from participation. This update to=20
BCP 10 specifies procedures for handling vacancies.=20
=20
A URL for this Internet-Draft is:=20
http://www.ietf.org/internet-drafts/draft-ietf-genarea-bcp10upd-00.txt=20=

=20
Internet-Drafts are also available by anonymous FTP at:=20
ftp://ftp.ietf.org/internet-drafts/=20
=20=

From melinda.shore@gmail.com  Wed Oct 24 09:59:28 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 8BEE121F86CB for <ietf@ietfa.amsl.com>; Wed, 24 Oct 2012 09:59:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TFgQ5fuIYqzk for <ietf@ietfa.amsl.com>; Wed, 24 Oct 2012 09:59:28 -0700 (PDT)
Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id 202EC21F86BC for <ietf@ietf.org>; Wed, 24 Oct 2012 09:59:28 -0700 (PDT)
Received: by mail-pb0-f44.google.com with SMTP id ro8so1350685pbb.31 for <ietf@ietf.org>; Wed, 24 Oct 2012 09:59:27 -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=JyymWqffVqpR9t14RQ3trFaOZqB3buK3UWmwUbZOi2k=; b=DZQi4KqJB8xmftbd/x7a3O9QNv0HApkaiNSITRXP6ebw8qO9rpJoL4yC7/WHJkoQ3I CER+egc7bYF2C5emYzsZXJlzyFwnJmcaiunrpSS6TIkDetr39JHBh6d+2jO0f+VFL+UF ACNOJlv/f/DmHeL2ZudH+OfOR9WxPLRy3/ipB8+2z6tLRbcrKF3zBtbHRhqFVzJCeBNe YBaUvmeoVxckGd1WMKhnxMkZZSjWURsYMpeGgGCEN+98i6YTBUyS2wIyClfpPWdnhgAf 7hiNuj5FHEOHKhDoj8diMWVFmll1w7qBWJWjyV+FIxcL+jKMMjIKxoW1MEprMyRLputU XtqQ==
Received: by 10.68.129.72 with SMTP id nu8mr51457554pbb.29.1351097967713; Wed, 24 Oct 2012 09:59:27 -0700 (PDT)
Received: from spandex.local (216-67-49-109-rb1.fai.dsl.dynamic.acsalaska.net. [216.67.49.109]) by mx.google.com with ESMTPS id n7sm9753944pav.26.2012.10.24.09.59.26 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 24 Oct 2012 09:59:26 -0700 (PDT)
Message-ID: <50881E6C.7090105@gmail.com>
Date: Wed, 24 Oct 2012 08:59:24 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:16.0) Gecko/20121010 Thunderbird/16.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: [whatwg] New URL Standard from Anne van Kesteren on 2012-09-24 (public-whatwg-archive@w3.org from September 2012)
References: <50604C1A.7090901@gmx.de> <5060A964.5060001@stpeter.im> <Pine.LNX.4.64.1210172354500.2478@ps20323.dreamhostps.com> <507F5A7E.6040206@arcanedomain.com> <50856E3C.103@gmail.com> <Pine.LNX.4.64.1210221753010.2471@ps20323.dreamhostps.com> <0DBC8A11-319C-4120-975E-7E40FD5818BF@gbiv.com> <Pine.LNX.4.64.1210222137530.2471@ps20323.dreamhostps.com> <CA+9kkMDpEZCvcG1DJd=O1qPNV+=+GTBeN+CGndUe51Xym_A9sg@mail.gmail.com> <Pine.LNX.4.64.1210232115210.2471@ps20323.dreamhostps.com> <15E1D98B-8883-4936-81A9-174E1323683C@nordsc.com> <Pine.LNX.4.64.1210232234590.2471@ps20323.dreamhostps.com> <8CC5FA04-2F61-408F-AED5-792E086E9BA0@nordsc.com>
In-Reply-To: <8CC5FA04-2F61-408F-AED5-792E086E9BA0@nordsc.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Oct 2012 16:59:28 -0000

On 10/23/12 2:52 PM, Jan Algermissen wrote:
> Then, how about going from 'fixing STD 66' to
> 
> 'augmenting STD 66 with how we get from the provided string -the
> input to the reference construction process- to a valid URI'?

[ ... ]

> What matters is that nothing of the existing URI spec *changes*.

W00t!  Uh, that is to say, +1.

Melinda


From johnl@iecc.com  Wed Oct 24 11:44: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 D9DE821F84ED for <ietf@ietfa.amsl.com>; Wed, 24 Oct 2012 11:44:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -111.751
X-Spam-Level: 
X-Spam-Status: No, score=-111.751 tagged_above=-999 required=5 tests=[AWL=0.448, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BTSHaaf5KMgL for <ietf@ietfa.amsl.com>; Wed, 24 Oct 2012 11:44:04 -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 EA8B321F8472 for <ietf@ietf.org>; Wed, 24 Oct 2012 11:44:03 -0700 (PDT)
Received: (qmail 28105 invoked from network); 24 Oct 2012 18:44:03 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 24 Oct 2012 18:44:03 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=508836f2.xn--i8sz2z.k1208; i=johnl@user.iecc.com; bh=7WuGgCqMsMK7hvIVXtoj/C0XCNZuVpd8VXI82f3FRAA=; b=vH8c/ABF68AFTdsx0WtdW0v1+whjHhq7wboW/0nlInDFdSKav1ByumLLTEUIsfUei0vELIFaakDd+M/+2S18g0Ep7KWrRUOHdCw5qky5/24CWHOTDauOT0maAnQZIvbcOTVXjuIDlDcJM0Q2KsNf1wW5+SKAl9S4IDPcPLjxTQM=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=508836f2.xn--i8sz2z.k1208; olt=johnl@user.iecc.com; bh=7WuGgCqMsMK7hvIVXtoj/C0XCNZuVpd8VXI82f3FRAA=; b=Y0azCaHjIMc6+iZzQR96Eu4ZWc+S43JE6es2oC85XyQVjJNiyoENtOEn5+h8JW/vV4fOWqOT+8lv+zAhuSYjfgnflk750Eco3u9pEHfIBlghkTulvZV3HxAz1NeL6N6kSg4vX8VGb+0qYkVk6m2ap3d+eDhkFvGhTRtk2JMru9U=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 24 Oct 2012 18:43:39 -0000
Message-ID: <20121024184339.3638.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: don't overthink, was Just so I'm clear
In-Reply-To: <3823F8B2-8A7A-4528-B8CE-49A1F867968D@comcast.net>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Oct 2012 18:44:05 -0000

>I agree with you that removing him would be the simplest approach, but I
>can see possible situations where NOT following the process could lead
>us into legal trouble.  

Anyone can sue in the US for any reason, but this is silly.

The IAOC made extensive attempts to contact him in many ways, with
zero response.  No court I know would find it unreasonable to assume
that he's no longer interested.

I certainly hope that this sort of situation does not recur, but it
seems perfectly reasonable in view of the facts to let the IAOC
proceed as though he's resigned.

R's,
John

From dwm@xpasc.com  Wed Oct 24 12:20:30 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 7204421F86EB for <ietf@ietfa.amsl.com>; Wed, 24 Oct 2012 12:20:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.824
X-Spam-Level: 
X-Spam-Status: No, score=-1.824 tagged_above=-999 required=5 tests=[AWL=-0.517, BAYES_00=-2.599, MISSING_HEADERS=1.292]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S1rzf2EQIUuD for <ietf@ietfa.amsl.com>; Wed, 24 Oct 2012 12:20:29 -0700 (PDT)
Received: from c2w3p-2.abacamail.com (c2w3p-2.abacamail.com [209.133.53.32]) by ietfa.amsl.com (Postfix) with ESMTP id C062921F88CA for <ietf@ietf.org>; Wed, 24 Oct 2012 12:20:28 -0700 (PDT)
Received: from xpasc.com (unknown [68.164.244.188]) by c2w3p-2.abacamail.com (Postfix) with ESMTP id 1F9A73F537 for <ietf@ietf.org>; Wed, 24 Oct 2012 19:20:28 +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 q9OJKRgs008672 for <ietf@ietf.org>; Wed, 24 Oct 2012 12:20:27 -0700
Date: Wed, 24 Oct 2012 12:20:27 -0700 (PDT)
From: David Morris <dwm@xpasc.com>
cc: ietf@ietf.org
Subject: Re: don't overthink, was Just so I'm clear
In-Reply-To: <20121024184339.3638.qmail@joyce.lan>
Message-ID: <alpine.LRH.2.01.1210241214280.6521@egate.xpasc.com>
References: <20121024184339.3638.qmail@joyce.lan>
User-Agent: Alpine 2.01 (LRH 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Milter-Version: master.1+13-gbab1945
X-AV-Type: clean
X-AV-Accuracy: exact
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: ietf@ietf.org
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Oct 2012 19:20:30 -0000

On Wed, 24 Oct 2012, John Levine wrote:

> >I agree with you that removing him would be the simplest approach, but I
> >can see possible situations where NOT following the process could lead
> >us into legal trouble.  
> 
> Anyone can sue in the US for any reason, but this is silly.
> 
> The IAOC made extensive attempts to contact him in many ways, with
> zero response.  No court I know would find it unreasonable to assume
> that he's no longer interested.

The legal issue raised by a previous reply that resonates with me is
that someone unsatisfied with a business decision by the adjusted
IAOC membership could sue based on documented process not being
followed to appoint the membership.

> I certainly hope that this sort of situation does not recur, but it
> seems perfectly reasonable in view of the facts to let the IAOC
> proceed as though he's resigned.

Yeah, except establishing new process and applying it retroactively
could be an issue. A new removal process could be defined and accepted
by the IETF's normal process, but the clock would have to start with
approval of the new process.

From dougb@dougbarton.us  Wed Oct 24 12:34:31 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 B921721F8645 for <ietf@ietfa.amsl.com>; Wed, 24 Oct 2012 12:34:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.413
X-Spam-Level: 
X-Spam-Status: No, score=-3.413 tagged_above=-999 required=5 tests=[AWL=0.186,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pzSRU3owXdhK for <ietf@ietfa.amsl.com>; Wed, 24 Oct 2012 12:34:31 -0700 (PDT)
Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by ietfa.amsl.com (Postfix) with ESMTP id 171BB21F85A2 for <ietf@ietf.org>; Wed, 24 Oct 2012 12:34:30 -0700 (PDT)
Received: (qmail 20948 invoked by uid 399); 24 Oct 2012 19:34:15 -0000
Received: from unknown (HELO ?192.168.0.102?) (dougb@dougbarton.us@12.207.105.210) by mail2.fluidhosting.com with ESMTPAM; 24 Oct 2012 19:34:15 -0000
X-Originating-IP: 12.207.105.210
X-Sender: dougb@dougbarton.us
Message-ID: <508842C2.4020203@dougbarton.us>
Date: Wed, 24 Oct 2012 12:34:26 -0700
From: Doug Barton <dougb@dougbarton.us>
Organization: http://SupersetSolutions.com/
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121010 Thunderbird/16.0.1
MIME-Version: 1.0
To: Margaret Wasserman <margaretw42@gmail.com>
Subject: Re: Just so I'm clear
References: <20121023192135.203AC18C0A4@mercury.lcs.mit.edu> <5086EF82.9060900@dougbarton.us> <20121023200713.GC1861@nsn.com> <5086FBCE.2070503@dougbarton.us> <20121023213251.GF27557@verdi> <50873AB4.1000905@dougbarton.us> <20121024034736.GC52558@crankycanuck.ca> <50876D39.20502@dougbarton.us> <508773E7.10203@cisco.com> <50877633.1000402@dougbarton.us> <EA9BEA2E-EE96-4E80-B719-652BBD620A79@lilacglade.org>
In-Reply-To: <EA9BEA2E-EE96-4E80-B719-652BBD620A79@lilacglade.org>
X-Enigmail-Version: 1.4.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: Wed, 24 Oct 2012 19:34:31 -0000

On 10/24/2012 5:49 AM, Margaret Wasserman wrote:
> 
> On Oct 24, 2012, at 1:01 AM, Doug Barton wrote:
>> I get what you're saying, but this is one of those times where
>> (arguably for the better) we've created a difficult procedure that
>> should be infrequently exercised. We should follow the procedure
>> because it _is_ the procedure. And then use the opportunity to
>> improve it.
> 
> The existence of the recall procedure does not imply that there isn't
> any other way for a seat to become vacant.  For example, a seat can
> become vacant when an I* member resigns or dies, and there is no need
> for a recall in those cases.

The 2 examples you gave are (as someone else pointed out)
incontrovertibly objective criteria, as is the explicit mention of the
use of the recall procedure in BCP 101. Nothing in the text suggests an
unfettered right of creating new definitions of "vacant."

For Melinda's benefit, in _addition_ to the process issue I am also not
in agreement with declaring the position vacant in this manner.

Doug

From barryleiba.mailing.lists@gmail.com  Wed Oct 24 13:22:09 2012
Return-Path: <barryleiba.mailing.lists@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DE17D21F8ACD for <ietf@ietfa.amsl.com>; Wed, 24 Oct 2012 13:22:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.098
X-Spam-Level: 
X-Spam-Status: No, score=-103.098 tagged_above=-999 required=5 tests=[AWL=-0.122, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VLeVp3XPM4U9 for <ietf@ietfa.amsl.com>; Wed, 24 Oct 2012 13:22:09 -0700 (PDT)
Received: from mail-ea0-f172.google.com (mail-ea0-f172.google.com [209.85.215.172]) by ietfa.amsl.com (Postfix) with ESMTP id 2F14F21F8A89 for <ietf@ietf.org>; Wed, 24 Oct 2012 13:22:09 -0700 (PDT)
Received: by mail-ea0-f172.google.com with SMTP id k13so348747eaa.31 for <ietf@ietf.org>; Wed, 24 Oct 2012 13:22: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=ZYV8fpwWgLTlvSdoFhA9QCkpApQmB5D3f943L3macaY=; b=jCHXbjXq/VolGlAUybsCpwQGyjqkMR8xg2J2dQ+8JY13aGIAX1WompeZ76uh1eJdQP 8FEsQrTV1nXkL7YzjzbzxeeAQNeGpePmEc2/UxfJ3WZ19cZumsqqdo9GDuhCXM4EbLTD tddKv4ydSqe6vUrBniip1V/IGIis8Xs4iWexQZ97v0hHlLz0+BUmAuvRPmbSCG1pbkWw 2o/G9D0PKxy7rFY1h28gBONxOa4qM0Mr2jO2O1F9Q96sl2C9dMG/oUioH4vjgDSal6Qf Ta8SuC9XNMH42+SxVQKDNs65IG63XbkhmnV5fB+Ie7zIogp6tISXowgwj6S59lzNv0w5 4g8Q==
MIME-Version: 1.0
Received: by 10.14.0.68 with SMTP id 44mr23625792eea.1.1351110128256; Wed, 24 Oct 2012 13:22:08 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.14.98.71 with HTTP; Wed, 24 Oct 2012 13:22:08 -0700 (PDT)
In-Reply-To: <D90D92A7-0906-4620-93A0-D116D15A10FA@gmail.com>
References: <D90D92A7-0906-4620-93A0-D116D15A10FA@gmail.com>
Date: Wed, 24 Oct 2012 16:22:08 -0400
X-Google-Sender-Auth: _zEnpTi36y-19KCaYLx2x94DQ_M
Message-ID: <CAC4RtVCE_ocLmv1Q4DtGn8GYHRs1byatrXpTjHLX5wueg=jx_g@mail.gmail.com>
Subject: Re: [RFC 3777 Update for Vacancies]
From: Barry Leiba <barryleiba@computer.org>
To: Bob Hinden <bob.hinden@gmail.com>
Content-Type: multipart/alternative; boundary=047d7b6228223f45a704ccd3d75e
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, 24 Oct 2012 20:22:10 -0000

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

>
> The draft that proposes changes to the RFC3777/BCP10 to deal with
> vacancies is now available.
>
>   http://tools.ietf.org/html/draft-ietf-genarea-bcp10upd-00
>
>
Two comments:

1 (nit):
   For vacancies due to death or resignation, no further action is
   required, to declare the seat vacant.

Remove the second comma.

2:
   For vacancies due to uncontested, sustained absence, the IETF body
   making that determination will issue an Extended Last Call to the
   community.

Where is "Extended Last Call" defined?  There should be a citation thither,
or a definition here.

I think this is a fine proposal, and I support it and hope the community
will show consensus for it.

Barry

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

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">The draft that proposes changes to the RFC37=
77/BCP10 to deal with vacancies is now available.<br>
<br>
=A0 <a href=3D"http://tools.ietf.org/html/draft-ietf-genarea-bcp10upd-00" t=
arget=3D"_blank">http://tools.ietf.org/html/draft-ietf-genarea-bcp10upd-00<=
/a><br><br></blockquote><div><br></div><div>Two comments:</div><div><br></d=
iv>
<div>1 (nit):</div><div>=A0 =A0For vacancies due to death or resignation, n=
o further action is</div><div>=A0 =A0required, to declare the seat vacant.<=
/div><div><br></div><div>Remove the second comma.</div><div><br></div><div>=
2:</div>
<div>=A0 =A0For vacancies due to uncontested, sustained absence, the IETF b=
ody</div><div>=A0 =A0making that determination will issue an Extended Last =
Call to the</div><div dir=3D"ltr">=A0 =A0community.</div><div dir=3D"ltr"><=
br></div><div dir=3D"ltr">
Where is &quot;<font><span style=3D"line-height:normal;background-color:rgb=
a(255,255,255,0)">Extended Last Call&quot; defined? =A0There should be a ci=
tation thither, or a definition here.</span></font></div><div dir=3D"ltr"><=
font><span style=3D"line-height:normal;background-color:rgba(255,255,255,0)=
"><br>
</span></font></div><div dir=3D"ltr"><font><span style=3D"line-height:norma=
l;background-color:rgba(255,255,255,0)">I think this is a fine proposal, an=
d I support it and hope the community will show consensus for it.</span></f=
ont></div>
<div dir=3D"ltr"><font><span style=3D"line-height:normal;background-color:r=
gba(255,255,255,0)"><br></span></font></div><div dir=3D"ltr"><font><span st=
yle=3D"line-height:normal;background-color:rgba(255,255,255,0)">Barry<span>=
</span></span></font></div>

--047d7b6228223f45a704ccd3d75e--

From sob@harvard.edu  Wed Oct 24 13:25:27 2012
Return-Path: <sob@harvard.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BCF2421F8A6B for <ietf@ietfa.amsl.com>; Wed, 24 Oct 2012 13:25:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.449
X-Spam-Level: 
X-Spam-Status: No, score=-103.449 tagged_above=-999 required=5 tests=[AWL=0.150, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OmMjV9Svle99 for <ietf@ietfa.amsl.com>; Wed, 24 Oct 2012 13:25:27 -0700 (PDT)
Received: from ackroyd.harvard.edu (ackroyd.harvard.edu [128.103.208.29]) by ietfa.amsl.com (Postfix) with ESMTP id D5E5B21F8A49 for <ietf@ietf.org>; Wed, 24 Oct 2012 13:25:12 -0700 (PDT)
Received: from exchange.university.harvard.edu (entwedge0000000.university.harvard.edu [10.35.2.151]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ackroyd.harvard.edu (Postfix) with ESMTP id 67A7AE8CB5; Wed, 24 Oct 2012 16:25:07 -0400 (EDT)
Received: from ENTWHUBT0000005.university.harvard.edu (10.32.208.51) by ENTWEDGE0000000.university.harvard.edu (10.35.2.151) with Microsoft SMTP Server (TLS) id 14.1.355.2; Wed, 24 Oct 2012 16:24:36 -0400
Received: from ENTWEXMB0000008.university.harvard.edu ([169.254.1.87]) by ENTWHUBT0000005.university.harvard.edu ([10.32.208.51]) with mapi id 14.01.0355.002; Wed, 24 Oct 2012 16:25:04 -0400
From: "Bradner, Scott" <sob@harvard.edu>
To: Barry Leiba <barryleiba@computer.org>
Subject: Re: [RFC 3777 Update for Vacancies]
Thread-Topic: [RFC 3777 Update for Vacancies]
Thread-Index: AQHNsgKf7I9KSYfz7UyfmlaB/6ys/JfJKYQAgAAA0QA=
Date: Wed, 24 Oct 2012 20:25:03 +0000
Message-ID: <CF2C098E-9928-4951-8EE8-154D8D894BC0@harvard.edu>
References: <D90D92A7-0906-4620-93A0-D116D15A10FA@gmail.com> <CAC4RtVCE_ocLmv1Q4DtGn8GYHRs1byatrXpTjHLX5wueg=jx_g@mail.gmail.com>
In-Reply-To: <CAC4RtVCE_ocLmv1Q4DtGn8GYHRs1byatrXpTjHLX5wueg=jx_g@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [136.248.127.173]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <D4CC2C6D60520D4F81F637E640485162@Exchange.university.harvard.edu>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Bob Hinden <bob.hinden@gmail.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Oct 2012 20:25:27 -0000

On Oct 24, 2012, at 4:22 PM, Barry Leiba <barryleiba@computer.org>
 wrote:

>=20
> 2:
>    For vacancies due to uncontested, sustained absence, the IETF body
>    making that determination will issue an Extended Last Call to the
>    community.
>=20
> Where is "Extended Last Call" defined?  There should be a citation thithe=
r, or a definition here.

RFC 2026 section 9.1

   The proposed variance must detail the problem perceived, explain the
   precise provision of this document which is causing the need for a
   variance, and the results of the IESG's considerations including
   consideration of points (a) through (d) in the previous paragraph.
   The proposed variance shall be issued as an Internet Draft.  The IESG
   shall then issue an extended Last-Call, of no less than 4 weeks, to
   allow for community comment upon the proposal.


From barryleiba.mailing.lists@gmail.com  Wed Oct 24 13:27: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 6330B21F8B83 for <ietf@ietfa.amsl.com>; Wed, 24 Oct 2012 13:27:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.098
X-Spam-Level: 
X-Spam-Status: No, score=-103.098 tagged_above=-999 required=5 tests=[AWL=-0.122, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mqqxmlyfgscS for <ietf@ietfa.amsl.com>; Wed, 24 Oct 2012 13:27:18 -0700 (PDT)
Received: from mail-ea0-f172.google.com (mail-ea0-f172.google.com [209.85.215.172]) by ietfa.amsl.com (Postfix) with ESMTP id A85AD21F8ACD for <ietf@ietf.org>; Wed, 24 Oct 2012 13:27:17 -0700 (PDT)
Received: by mail-ea0-f172.google.com with SMTP id k13so350223eaa.31 for <ietf@ietf.org>; Wed, 24 Oct 2012 13:27:16 -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=+sh6iZ64Do5Rvp5/4iPJUcUjeCtKvNwWDMvv5+f27Hk=; b=KSZMPRvnHs73QuQmkXeo9WIja7uw0kNNvjWClxph7eplNWMPIBT1j3LDDzlkLegc+g zfAozqEEluYGlDhVoXexrJnUyoN7ze5Ts3UWA4UoRh08PvV5fQWx3/S9BoP5tNsB6B+w YYzUFmwrOLg+WzTY3TKICelqJRu7QnDJ8zLQDlky/a9XKy8cU7qFm3QF6pFhGjQZVXaj Gyn5z89sYVczO14wIdd4kN8JW1sLXEZEw38koGCWNLfTJ5vLBwj5C+E0MXY/i2/kytxM 2pyHj237fyM0/X9wEjzEciDeat+Kl3JfXfHanjm2N3K50qjKcSWzKU2c0pf4QQ3WSlpG 3FBA==
MIME-Version: 1.0
Received: by 10.14.203.3 with SMTP id e3mr9914862eeo.35.1351110436695; Wed, 24 Oct 2012 13:27:16 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.14.98.71 with HTTP; Wed, 24 Oct 2012 13:27:16 -0700 (PDT)
In-Reply-To: <CF2C098E-9928-4951-8EE8-154D8D894BC0@harvard.edu>
References: <D90D92A7-0906-4620-93A0-D116D15A10FA@gmail.com> <CAC4RtVCE_ocLmv1Q4DtGn8GYHRs1byatrXpTjHLX5wueg=jx_g@mail.gmail.com> <CF2C098E-9928-4951-8EE8-154D8D894BC0@harvard.edu>
Date: Wed, 24 Oct 2012 16:27:16 -0400
X-Google-Sender-Auth: U5QHf7aN5ZdTIgF9hwQ-2G7tgUw
Message-ID: <CAC4RtVDmC3Anb-ywbCizYux2MjDn=T0=Z8pWSXyjC5RZqU_Upg@mail.gmail.com>
Subject: Re: [RFC 3777 Update for Vacancies]
From: Barry Leiba <barryleiba@computer.org>
To: "Bradner, Scott" <sob@harvard.edu>
Content-Type: multipart/alternative; boundary=047d7b343b2aa1ae4c04ccd3e9dd
Cc: Barry Leiba <barryleiba@computer.org>, Bob Hinden <bob.hinden@gmail.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Oct 2012 20:27:18 -0000

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

>
> > Where is "Extended Last Call" defined?  There should be a citation
> thither, or a definition here.
>
> RFC 2026 section 9.1
>
>    The proposed variance must detail the problem perceived, explain the
>    precise provision of this document which is causing the need for a
>    variance, and the results of the IESG's considerations including
>    consideration of points (a) through (d) in the previous paragraph.
>    The proposed variance shall be issued as an Internet Draft.  The IESG
>    shall then issue an extended Last-Call, of no less than 4 weeks, to
>    allow for community comment upon the proposal.
>

Indeed.  And (1) "Extended Last Call" <> "extended Last-Call" and (2)
there's no citation to 2026.

b

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

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">&gt; Where is &quot;Extended Last Call&quot;=
 defined? =A0There should be a citation thither, or a definition here.<br>
<br>
RFC 2026 section 9.1<br>
<br>
=A0 =A0The proposed variance must detail the problem perceived, explain the=
<br>
=A0 =A0precise provision of this document which is causing the need for a<b=
r>
=A0 =A0variance, and the results of the IESG&#39;s considerations including=
<br>
=A0 =A0consideration of points (a) through (d) in the previous paragraph.<b=
r>
=A0 =A0The proposed variance shall be issued as an Internet Draft. =A0The I=
ESG<br>
=A0 =A0shall then issue an extended Last-Call, of no less than 4 weeks, to<=
br>
=A0 =A0allow for community comment upon the proposal.<br>
</blockquote><div><br></div><div>Indeed. =A0And (1) &quot;Extended Last Cal=
l&quot; &lt;&gt; &quot;extended Last-Call&quot; and (2) there&#39;s no cita=
tion to 2026.</div><div><br></div><div>b=A0<span></span></div>

--047d7b343b2aa1ae4c04ccd3e9dd--

From dwm@xpasc.com  Wed Oct 24 13:45:57 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 9F5D021F8869 for <ietf@ietfa.amsl.com>; Wed, 24 Oct 2012 13:45:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.384
X-Spam-Level: 
X-Spam-Status: No, score=-2.384 tagged_above=-999 required=5 tests=[AWL=0.215,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ViEk2cUZCSOL for <ietf@ietfa.amsl.com>; Wed, 24 Oct 2012 13:45:57 -0700 (PDT)
Received: from c2w3p-2.abacamail.com (c2w3p-2.abacamail.com [209.133.53.32]) by ietfa.amsl.com (Postfix) with ESMTP id 06EED21F883A for <ietf@ietf.org>; Wed, 24 Oct 2012 13:45:56 -0700 (PDT)
Received: from xpasc.com (unknown [68.164.244.188]) by c2w3p-2.abacamail.com (Postfix) with ESMTP id 74BD93F519; Wed, 24 Oct 2012 20:45:55 +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 q9OKjrfF010138; Wed, 24 Oct 2012 13:45:53 -0700
Date: Wed, 24 Oct 2012 13:45:53 -0700 (PDT)
From: David Morris <dwm@xpasc.com>
To: Bob Hinden <bob.hinden@gmail.com>
Subject: Re: [RFC 3777 Update for Vacancies]
In-Reply-To: <D90D92A7-0906-4620-93A0-D116D15A10FA@gmail.com>
Message-ID: <alpine.LRH.2.01.1210241335320.6521@egate.xpasc.com>
References: <D90D92A7-0906-4620-93A0-D116D15A10FA@gmail.com>
User-Agent: Alpine 2.01 (LRH 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Milter-Version: master.1+13-gbab1945
X-AV-Type: clean
X-AV-Accuracy: exact
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Oct 2012 20:45:57 -0000

I see several issues .... 

a) To my reading RFC 3777 only deals with IAB and IESG membership
b) Neither this draft nor 3777 defines 'IETF body' 
c) Consindering that someone would be a member until removed, and
   assuming IAOC is meant to be considered an IETF body, 2/3 of
   members approving could be sticky at some point if 2/3 of
   the members aren't available to vote.
d) We need a better definition of 'sustained' absence ... e.g., 
   a minimum period of time, number of regularily scheduled
   'meetings' missed, no response to queries.
e) "Multiple different queries" ... needs more precision as it
   is satisfied as stated by 2 emails sent at the same time to
   the same destination. This section may require an adjustment
   to the sort of contact information required for each position
   covered by this process.

Dave Morris

On Wed, 24 Oct 2012, Bob Hinden wrote:

> The draft that proposes changes to the RFC3777/BCP10 to deal with vacancies is now available.
> 
>   http://tools.ietf.org/html/draft-ietf-genarea-bcp10upd-00
> 
> Bob
> 
> --------------------
> 
> From: Internet-Drafts@ietf.org 
> To: i-d-announce@ietf.org 
> Reply-to: Internet-Drafts@ietf.org 
> Subject: I-D ACTION:draft-ietf-genarea-bcp10upd-00.txt 
> X-C5I-RSN: 1/0/935/46939/50333 
>  
> A new Internet-Draft is available from the on-line Internet-Drafts directories. 
>  
> Title : RFC 3777 Update for Vacancies 
> Author(s) : D. Crocker, et al 
> Filename : draft-ietf-genarea-bcp10upd 
> Pages : 4  
> Date : Oct. 24, 2012  
>  
> BCP 10 (RFC 3777) specifies IETF processes for selection, 
> confirmation and recall of appointees to IETF positions. It also 
> refers to the mechanism of resignation as part of a sequence that 
> moves a sitting member to a new IETF position. However it does not 
> more generally deal with vacancies created by resignation, death or 
> uncontested, sustained absence from participation. This update to 
> BCP 10 specifies procedures for handling vacancies. 
>  
> A URL for this Internet-Draft is: 
> http://www.ietf.org/internet-drafts/draft-ietf-genarea-bcp10upd-00.txt 
>  
> Internet-Drafts are also available by anonymous FTP at: 
> ftp://ftp.ietf.org/internet-drafts/ 
>  
> 

From johnl@iecc.com  Wed Oct 24 13:50:46 2012
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 162EA21F8A2D for <ietf@ietfa.amsl.com>; Wed, 24 Oct 2012 13:50:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -111.758
X-Spam-Level: 
X-Spam-Status: No, score=-111.758 tagged_above=-999 required=5 tests=[AWL=0.441, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FiIPsXufT7-0 for <ietf@ietfa.amsl.com>; Wed, 24 Oct 2012 13:50:42 -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 DD52B21F86C9 for <ietf@ietf.org>; Wed, 24 Oct 2012 13:50:41 -0700 (PDT)
Received: (qmail 57133 invoked from network); 24 Oct 2012 20:50:37 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 24 Oct 2012 20:50:37 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=5088549d.xn--btvx9d.k1208; i=johnl@user.iecc.com; bh=z7sEBVvrb1NZJunnovzcnZNwJFt3CzA53KpW2n9ZS1g=; b=fix94hmyC7nh9S6RctIish22dha9pCt1qTdcotiySdgUqhFt62I2g2fn4tRdspV3F1LL+KJGGGpfyjANLMwc61g0rPaGgPacjvFbdQLLxtqkofFq6iHdgWLy8J34GhKNpMIYHc5teC6jfMWYnWoVD4ybeJ1sFEyuQSm63+/7oCo=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=5088549d.xn--btvx9d.k1208; olt=johnl@user.iecc.com; bh=z7sEBVvrb1NZJunnovzcnZNwJFt3CzA53KpW2n9ZS1g=; b=ZiHSes11N3xP8iDWZUw/6QwR80Ypfvp6XbYPv8hd5q1cmyVc0PWTKytgx8tSghWuao6Z8sqfy/STLsi96FS4Plr3AK1/SEERMAyEJcH3Egv1N2QwAXK/yzjztzYh7/eKVXSPWfZenk6+JGuUTQ3jLLdruftdxzQO/mtAu7PA1po=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 24 Oct 2012 20:50:15 -0000
Message-ID: <20121024205015.6775.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: don't overthink, was Just so I'm clear
In-Reply-To: <alpine.LRH.2.01.1210241214280.6521@egate.xpasc.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Oct 2012 20:50:46 -0000

>The legal issue raised by a previous reply that resonates with me is
>that someone unsatisfied with a business decision by the adjusted
>IAOC membership could sue based on documented process not being
>followed to appoint the membership.

Are you aware of any case law that suggests that any U.S. court would
be interested in interpreting or enforcing the nitpicky details of the
IETF's governance, or that there is any reason to believe that there
are third party beneficiaries to the IAOC's operating rules?

R's,
John

PS: Perhaps we can all stop playing Junior Lawyer now.


From barryleiba.mailing.lists@gmail.com  Wed Oct 24 14:05:20 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 75A0A21F88D4 for <ietf@ietfa.amsl.com>; Wed, 24 Oct 2012 14:05:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.096
X-Spam-Level: 
X-Spam-Status: No, score=-103.096 tagged_above=-999 required=5 tests=[AWL=-0.120, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Fd4acbu+TuZ7 for <ietf@ietfa.amsl.com>; Wed, 24 Oct 2012 14:05:19 -0700 (PDT)
Received: from mail-la0-f44.google.com (mail-la0-f44.google.com [209.85.215.44]) by ietfa.amsl.com (Postfix) with ESMTP id 57B7721F8858 for <ietf@ietf.org>; Wed, 24 Oct 2012 14:05:19 -0700 (PDT)
Received: by mail-la0-f44.google.com with SMTP id b11so672632lam.31 for <ietf@ietf.org>; Wed, 24 Oct 2012 14:05:13 -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=AE9znNqYoBszvJdSc9F4oXgIjpr5QtuEKUnHDQcxSZU=; b=QADiEQh9dMPlNwh1Lpa779Q1VLpoVpVxlxXQvydb6RWKXbvg1GhrCyVYvF6MhAfK97 ABEWaHgfJ1AzAb9ojs97dwCOfodRW1Rkd7vhBFZFet+O/+FIYkrvjVP6TvafVNkRlQqg vzBUGDj9K70JEIEZDEWMkXV9HPycoN13howKb9MoikG5DLWk/Sjz6EO18eUy2H/T9MpI yN9xLBmYJrOp2tIT0cKKxn7dUMUwDPeCfa3kr9ejA/5dgs1YUT8rlTKnHT/33Q/njWBC f/20ZW2JXhq7Z8HShZp1kAjLHGrqDWtZWF4yJM8S++IxvryXFBALFckvD42xQc9lDqYx vqUw==
MIME-Version: 1.0
Received: by 10.112.87.167 with SMTP id az7mr7078413lbb.47.1351112712940; Wed, 24 Oct 2012 14:05:12 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.112.99.131 with HTTP; Wed, 24 Oct 2012 14:05:12 -0700 (PDT)
In-Reply-To: <alpine.LRH.2.01.1210241335320.6521@egate.xpasc.com>
References: <D90D92A7-0906-4620-93A0-D116D15A10FA@gmail.com> <alpine.LRH.2.01.1210241335320.6521@egate.xpasc.com>
Date: Wed, 24 Oct 2012 17:05:12 -0400
X-Google-Sender-Auth: fZIHz_pamZ7ONbsRvtOnkX3ywDQ
Message-ID: <CAC4RtVDfb=B0bC=+eH8KVnPcwkxEihuEsRAUYSGgxnjU1VQbyQ@mail.gmail.com>
Subject: Re: [RFC 3777 Update for Vacancies]
From: Barry Leiba <barryleiba@computer.org>
To: David Morris <dwm@xpasc.com>
Content-Type: multipart/alternative; boundary=f46d0401f96d4e6c1104ccd47129
Cc: Bob Hinden <bob.hinden@gmail.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Oct 2012 21:05:20 -0000

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

>
> a) To my reading RFC 3777 only deals with IAB and IESG membership


RFC 4071 (BCP 101) specifies use of the 3777 recall process for the IAOC.


> b) Neither this draft nor 3777 defines 'IETF body'


Simply making Section 3.1 say 'the IAB, IESG, or IAOC ("an IETF body")'
will take care of that.


> c) Consindering that someone would be a member until removed, and
>    assuming IAOC is meant to be considered an IETF body, 2/3 of
>    members approving could be sticky at some point if 2/3 of
>    the members aren't available to vote.


I presume you mean, "if there aren't 2/3 of the members available to vote."
 Yes, well, true.  But then there's always the recall process to fall back
on.


> d) We need a better definition of 'sustained' absence ... e.g.,
>    a minimum period of time, number of regularily scheduled
>    'meetings' missed, no response to queries.
> e) "Multiple different queries" ... needs more precision as it
>    is satisfied as stated by 2 emails sent at the same time to
>    the same destination. This section may require an adjustment
>    to the sort of contact information required for each position
>    covered by this process.
>

Both of these are handled by giving the IETF body some judgment,
counterbalanced by the ability to contest it.  If the judgment is
uncontested, we're fine.  If it is contested, then we go back to the recall
process.  I think that's a fine approach, and would NOT like to overspecify
this.

Barry

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

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">a) To my reading RFC 3777 only deals with IA=
B and IESG membership</blockquote><div><br></div><div>RFC 4071 (BCP 101) sp=
ecifies use of the 3777 recall process for the IAOC.</div>
<div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex">
b) Neither this draft nor 3777 defines &#39;IETF body&#39;</blockquote><div=
><br></div><div>Simply making Section 3.1 say &#39;the IAB, IESG, or IAOC (=
&quot;an IETF body&quot;)&#39; will take care of that.</div><div>=A0</div>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
c) Consindering that someone would be a member until removed, and<br>
=A0 =A0assuming IAOC is meant to be considered an IETF body, 2/3 of<br>
=A0 =A0members approving could be sticky at some point if 2/3 of<br>
=A0 =A0the members aren&#39;t available to vote.</blockquote><div><br></div=
><div>I presume you mean, &quot;if there aren&#39;t 2/3 of the members avai=
lable to vote.&quot; =A0Yes, well, true. =A0But then there&#39;s always the=
 recall process to fall back on.</div>
<div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex">
d) We need a better definition of &#39;sustained&#39; absence ... e.g.,<br>
=A0 =A0a minimum period of time, number of regularily scheduled<br>
=A0 =A0&#39;meetings&#39; missed, no response to queries.<br>
e) &quot;Multiple different queries&quot; ... needs more precision as it<br=
>
=A0 =A0is satisfied as stated by 2 emails sent at the same time to<br>
=A0 =A0the same destination. This section may require an adjustment<br>
=A0 =A0to the sort of contact information required for each position<br>
=A0 =A0covered by this process.<br>
</blockquote><div><br></div><div>Both of these are handled by giving the IE=
TF body some judgment, counterbalanced by the ability to contest it. =A0If =
the judgment is uncontested, we&#39;re fine. =A0If it is contested, then we=
 go back to the recall process. =A0I think that&#39;s a fine approach, and =
would NOT like to overspecify this.<span></span></div>
<div><br></div><div>Barry</div>

--f46d0401f96d4e6c1104ccd47129--

From dwm@xpasc.com  Wed Oct 24 14:05:43 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 6D98421F8A62 for <ietf@ietfa.amsl.com>; Wed, 24 Oct 2012 14:05:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.768
X-Spam-Level: 
X-Spam-Status: No, score=-1.768 tagged_above=-999 required=5 tests=[AWL=-0.461, BAYES_00=-2.599, MISSING_HEADERS=1.292]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tDJZhNq7Nng3 for <ietf@ietfa.amsl.com>; Wed, 24 Oct 2012 14:05:43 -0700 (PDT)
Received: from c2w3p-2.abacamail.com (c2w3p-2.abacamail.com [209.133.53.32]) by ietfa.amsl.com (Postfix) with ESMTP id F2AA121F8A2A for <ietf@ietf.org>; Wed, 24 Oct 2012 14:05:42 -0700 (PDT)
Received: from xpasc.com (unknown [68.164.244.188]) by c2w3p-2.abacamail.com (Postfix) with ESMTP id AFF8C3FBB2 for <ietf@ietf.org>; Wed, 24 Oct 2012 21:05:42 +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 q9OL5g9u010455 for <ietf@ietf.org>; Wed, 24 Oct 2012 14:05:42 -0700
Date: Wed, 24 Oct 2012 14:05:42 -0700 (PDT)
From: David Morris <dwm@xpasc.com>
cc: ietf@ietf.org
Subject: Re: don't overthink, was Just so I'm clear
In-Reply-To: <20121024205015.6775.qmail@joyce.lan>
Message-ID: <alpine.LRH.2.01.1210241402030.6521@egate.xpasc.com>
References: <20121024205015.6775.qmail@joyce.lan>
User-Agent: Alpine 2.01 (LRH 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Milter-Version: master.1+13-gbab1945
X-AV-Type: clean
X-AV-Accuracy: exact
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: ietf@ietf.org
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Oct 2012 21:05:43 -0000

On Wed, 24 Oct 2012, John Levine wrote:

> >The legal issue raised by a previous reply that resonates with me is
> >that someone unsatisfied with a business decision by the adjusted
> >IAOC membership could sue based on documented process not being
> >followed to appoint the membership.
> 
> Are you aware of any case law that suggests that any U.S. court would
> be interested in interpreting or enforcing the nitpicky details of the
> IETF's governance, or that there is any reason to believe that there
> are third party beneficiaries to the IAOC's operating rules?

As I understand the situation, the IAOC is responsible for administrative
decisions such as contracting for venues, issuing RFPs, etc. That 
means that there are third parties who will be impacted by IAOC
decisions.

> 
> PS: Perhaps we can all stop playing Junior Lawyer now.

As soon as we have been assured that the plan and questions raised
have been reviewed and judged by the real IETF lawyers to not be
a concern

From mrex@sap.com  Wed Oct 24 14:41:30 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 42A4B21F88B9 for <ietf@ietfa.amsl.com>; Wed, 24 Oct 2012 14:41:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.21
X-Spam-Level: 
X-Spam-Status: No, score=-10.21 tagged_above=-999 required=5 tests=[AWL=0.039,  BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NAKIXP5n6rU7 for <ietf@ietfa.amsl.com>; Wed, 24 Oct 2012 14:41:29 -0700 (PDT)
Received: from smtpde02.sap-ag.de (smtpde02.sap-ag.de [155.56.68.140]) by ietfa.amsl.com (Postfix) with ESMTP id 58C7621F86B8 for <ietf@ietf.org>; Wed, 24 Oct 2012 14:41:29 -0700 (PDT)
Received: from mail.sap.corp by smtpde02.sap-ag.de (26) with ESMTP id q9OLfMgR009261 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for <ietf@ietf.org>; Wed, 24 Oct 2012 23:41:27 +0200 (MEST)
Subject: Re: don't overthink, was Just so I'm clear
In-Reply-To: <alpine.LRH.2.01.1210241214280.6521@egate.xpasc.com>
To: ietf@ietf.org
Date: Wed, 24 Oct 2012 23:41:22 +0200 (CEST)
X-Mailer: ELM [version 2.4ME+ PL125 (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="US-ASCII"
Message-Id: <20121024214122.7ED0F1A2F3@ld9781.wdf.sap.corp>
From: mrex@sap.com (Martin Rex)
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: Wed, 24 Oct 2012 21:41:30 -0000

David Morris wrote:
> 
> John Levine wrote:
> >
> > >I agree with you that removing him would be the simplest approach, but I
> > >can see possible situations where NOT following the process could lead
> > >us into legal trouble.  
> > 
> > Anyone can sue in the US for any reason, but this is silly.
> > 
> > The IAOC made extensive attempts to contact him in many ways, with
> > zero response.  No court I know would find it unreasonable to assume
> > that he's no longer interested.
> 
> The legal issue raised by a previous reply that resonates with me is
> that someone unsatisfied with a business decision by the adjusted
> IAOC membership could sue based on documented process not being
> followed to appoint the membership.
> 
> > I certainly hope that this sort of situation does not recur, but it
> > seems perfectly reasonable in view of the facts to let the IAOC
> > proceed as though he's resigned.
> 
> Yeah, except establishing new process and applying it retroactively
> could be an issue. A new removal process could be defined and accepted
> by the IETF's normal process, but the clock would have to start with
> approval of the new process.


I believe you're blowing the (in)significance of "someone unsatisfied
with a business decision" out of proportion.


But actually, discussing the recall procedure _now_ looks like barking up
the _wrong_ tree to me.

The IAOC says it is currently understaffed to do its work.  So what
the IAOC needs quickly is another (at least temporary) _active_ membership.

Whether or not Marshall remains an (inactive) member of the IAOC 
may be academically interesting, and a topic of discussion to
augment the procedures for the future, but appears less relevant
for the IAOC in trying to get its work done.
 

Doing an extended last call to augment the IAOC membership by one
addidional _active_ seat up to the end of Marshalls term should
be possible as an ad-hoc interim measure to address a specific
current resource shortage.  Adjusting the procedures is a secondary
issue.


-Martin


From ian@hixie.ch  Wed Oct 24 10:02:18 2012
Return-Path: <ian@hixie.ch>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 46AF721F86CA for <ietf@ietfa.amsl.com>; Wed, 24 Oct 2012 10:02:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.544
X-Spam-Level: 
X-Spam-Status: No, score=-2.544 tagged_above=-999 required=5 tests=[AWL=0.055,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kQlQWcL3t7Kk for <ietf@ietfa.amsl.com>; Wed, 24 Oct 2012 10:02:17 -0700 (PDT)
Received: from homiemail-a80.g.dreamhost.com (caibbdcaaaaf.dreamhost.com [208.113.200.5]) by ietfa.amsl.com (Postfix) with ESMTP id 7356421F86D8 for <ietf@ietf.org>; Wed, 24 Oct 2012 10:02:17 -0700 (PDT)
Received: from homiemail-a80.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a80.g.dreamhost.com (Postfix) with ESMTP id 30F1A37A089; Wed, 24 Oct 2012 10:02:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=hixie.ch; h=date:from:to :cc:subject:in-reply-to:message-id:references:mime-version: content-type; s=hixie.ch; bh=T9tBSMO96K6AauEH5TBdnQZYyQA=; b=Tps emH2uL2h5udcuH6qkV9eUcP58fPo2ojkFR6jFCJWVJqqGrMhiSYcmBlCRvhGdwRX LUej1EEIh+ers2PW5RTkQGnM90Kby4Pn7W95Y6cDFGclhc+AI/RObqqMS5RuQFx8 1V00jOS0CSs6lvh2Kp12HWpddUFo1rMoYifjQv7A=
Received: from ps20323.dreamhostps.com (ps20323.dreamhost.com [69.163.222.251]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: internal@index.hixie.ch) by homiemail-a80.g.dreamhost.com (Postfix) with ESMTPSA id 1EC2037A085;  Wed, 24 Oct 2012 10:02:17 -0700 (PDT)
Date: Wed, 24 Oct 2012 17:02:16 +0000 (UTC)
From: Ian Hickson <ian@hixie.ch>
To: Jan Algermissen <jan.algermissen@nordsc.com>
Subject: Re: [whatwg] New URL Standard from Anne van Kesteren on 2012-09-24 (public-whatwg-archive@w3.org from September 2012)
In-Reply-To: <85621CE2-4ACD-499F-AFBF-AE7BA18F3666@nordsc.com>
Message-ID: <Pine.LNX.4.64.1210241642080.2471@ps20323.dreamhostps.com>
References: <50604C1A.7090901@gmx.de> <5060A964.5060001@stpeter.im> <Pine.LNX.4.64.1210172354500.2478@ps20323.dreamhostps.com> <507F5A7E.6040206@arcanedomain.com> <50856E3C.103@gmail.com> <Pine.LNX.4.64.1210221753010.2471@ps20323.dreamhostps.com> <0DBC8A11-319C-4120-975E-7E40FD5818BF@gbiv.com> <Pine.LNX.4.64.1210222137530.2471@ps20323.dreamhostps.com> <CA+9kkMDpEZCvcG1DJd=O1qPNV+=+GTBeN+CGndUe51Xym_A9sg@mail.gmail.com> <Pine.LNX.4.64.1210232115210.2471@ps20323.dreamhostps.com> <15E1D98B-8883-4936-81A9-174E1323683C@nordsc.com> <Pine.LNX.4.64.1210232234590.2471@ps20323.dreamhostps.com> <8CC5FA04-2F61-408F-AED5-792E086E9BA0@nordsc.com> <Pine.LNX.4.64.1210232347280.2471@ps20323.dreamhostps.com> <85621CE2-4ACD-499F-AFBF-AE7BA18F3666@nordsc.com>
Content-Language: en-GB-hixie
Content-Style-Type: text/css
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Mailman-Approved-At: Wed, 24 Oct 2012 14:49:03 -0700
Cc: Ted Hardie <ted.ietf@gmail.com>, URI <uri@w3.org>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Oct 2012 17:02:18 -0000

On Wed, 24 Oct 2012, Jan Algermissen wrote:
> On Oct 24, 2012, at 1:47 AM, Ian Hickson <ian@hixie.ch> wrote:
> > On Wed, 24 Oct 2012, Jan Algermissen wrote:
> >> 
> >> What matters is that nothing of the existing URI spec *changes*.
> >> 
> >> Can you agree on that?
> > 
> > Do you mean the actual text, or the normative meaning of the text?
> 
> I ideally mean the actual text, but it might be that there is some 
> overlap in the construction algorithms - I am not expert enough there to 
> judge that.

Well I definitely don't think we should constrain a spec editor to being 
forced to use text he didn't even write, that seems like a very poor way 
to write a spec. Especially given that here the text is already spread 
across two specs (URI and IRI).

I think it makes sense to be conservative and say that URL synatx 
conformance requirements should probably not change from what the IRI spec 
says today unless there's a really compelling reason, though.


> The point really was to make it very clear that *additional* stuff is 
> going to be said and that existing implementations that follow the URI 
> spec strictly remain conforming.

Well unless there's a very good reason (e.g. following the current specs 
involves a security vulnerability or something like that) then I'd think 
that was a reasonably strong technical requirement, sure. But that's 
independent of how the spec is written. It's trivial to write a spec that 
uses existing text while making all existing implementations 
non-conforming, for example (just add a line that says "implementations 
MUST NOT do what the following section says" or something...).

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'

From fielding@gbiv.com  Wed Oct 24 12:11:04 2012
Return-Path: <fielding@gbiv.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9D8BC21F887E for <ietf@ietfa.amsl.com>; Wed, 24 Oct 2012 12:11:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.235
X-Spam-Level: 
X-Spam-Status: No, score=-106.235 tagged_above=-999 required=5 tests=[AWL=-3.636, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vaQ3XGFGL6Sx for <ietf@ietfa.amsl.com>; Wed, 24 Oct 2012 12:11:03 -0700 (PDT)
Received: from homiemail-a24.g.dreamhost.com (caiajhbdcbef.dreamhost.com [208.97.132.145]) by ietfa.amsl.com (Postfix) with ESMTP id 9A45F21F8755 for <ietf@ietf.org>; Wed, 24 Oct 2012 12:11:03 -0700 (PDT)
Received: from homiemail-a24.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a24.g.dreamhost.com (Postfix) with ESMTP id 84E2A2C806D; Wed, 24 Oct 2012 12:11:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=gbiv.com; h=subject :mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=gbiv.com; bh=vGp4eUrybmjKKRHnUjE5bMc9NqI=; b=W/f8KmfgXMX+xsaroaOKJ2c7+kFh nux1/ZHanse39Scogac1onbrbAtWtm3hCYhK3uSbHDlywJVOmB2wq+UjiGDinBpb JTvyk/5IKLx+v+zC/u65NzYHdIiqidNgIMkMVEGROG7Ikg4gIPshl5TSNZ3UO8ov Pdo8wS8lLNlDFHY=
Received: from [192.168.1.84] (99-21-208-82.lightspeed.irvnca.sbcglobal.net [99.21.208.82]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: fielding@gbiv.com) by homiemail-a24.g.dreamhost.com (Postfix) with ESMTPSA id CD7502C8057;  Wed, 24 Oct 2012 12:10:59 -0700 (PDT)
Subject: Re: [whatwg] New URL Standard from Anne van Kesteren on 2012-09-24 (public-whatwg-archive@w3.org from September 2012)
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=us-ascii
From: "Roy T. Fielding" <fielding@gbiv.com>
In-Reply-To: <5087C57A.80607@gmail.com>
Date: Wed, 24 Oct 2012 12:10:59 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <097534B5-8135-4A20-8275-934A5547ACDB@gbiv.com>
References: <50604C1A.7090901@gmx.de> <5060A964.5060001@stpeter.im> <Pine.LNX.4.64.1210172354500.2478@ps20323.dreamhostps.com> <507F5A7E.6040206@arcanedomain.com> <50856E3C.103@gmail.com> <Pine.LNX.4.64.1210221753010.2471@ps20323.dreamhostps.com> <0DBC8A11-319C-4120-975E-7E40FD5818BF@gbiv.com> <Pine.LNX.4.64.1210222137530.2471@ps20323.dreamhostps.com> <5085C4BA.2030505@gmx.de> <Pine.LNX.4.64.1210222220510.2471@ps20323.dreamhostps.com> <CAHBU6is8LNZ7Rq-vwLuOm+8ThKB9c=QPwbUfQwDQD5bDPjtf7w@mail.gmail.com> <Pine.LNX.4.64.1210222320070.2471@ps20323.dreamhostps.com> <09DC68AA-2DAD-4CB1-9CA9-799AF12B7BE2@mnot.net> <5087C57A.80607@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1283)
X-Mailman-Approved-At: Wed, 24 Oct 2012 14:49:03 -0700
Cc: IETF Discussion <ietf@ietf.org>, Julian Reschke <julian.reschke@gmx.de>, Jan Algermissen <jan.algermissen@nordsc.com>, URI <uri@w3.org>, Noah Mendelsohn <nrm@arcanedomain.com>, Mark Nottingham <mnot@mnot.net>, Tim Bray <tbray@textuality.com>, Ian Hickson <ian@hixie.ch>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Oct 2012 19:11:04 -0000

On Oct 24, 2012, at 3:39 AM, Brian E Carpenter wrote:
> On 23/10/2012 00:32, Mark Nottingham wrote:
> ...
>> The underlying point that people seem to be making is that there's =
legitimate need for URIs to be a separate concept from "strings that =
will become URIs." By collapsing them into one thing, you're doing those =
folks a disservice. Browser implementers may not care, but it's pretty =
obvious that lots of other people do.
>=20
> Thanks for bringing this point out. It was explained to me in 1993 by =
TBL and
> Robert Cailliau that URLs (the only term used then, I think)

As a historical footnote, the term URL was created by the same
BOF that created the Uniform Resource Identifiers working group
at the IETF meeting in July 1992.

The early Web protocol specs had used the term "network address".

The term "Document Identifiers" came from Brewster Kahle and was
later used in a call for proposals by the Coalition for Networked
Information's Architectures & Standards Working Group, which in
turn led to TimBL propose Web addresses as Universal Document
Identifiers for a BOF at IETF 24 (Cambridge, MA).  Somewhere
in that BOF discussion, the URI working group was proposed and
TimBL's proposal was renamed Uniform Resource Locators
to distinguish it from other ideas for URNs
[see IETF 24 proceedings, p.184, and the following link].

 ftp://ftp.ietf.org/ietf/92jul/udi-minutes-92jul.txt

TimBL had originally specified that addresses in HREF could be
provided in full or partial form.  The IETF removed the partial
form, leading to all sorts of bad decisions regarding syntax,
and so I revived it in 1994 as Relative URLs [RFC1808].  That
spec is the only one that came close to defining what Anne
is trying to do here -- a single parsing standard for
potentially relative references.=20

It is easy to claim that the merging of syntax specs that
created RFC2396 lost some value when the parsing standard was
replaced by a non-normative appendix.  However, it was discussed
extensively at the time, including with the browser developers,
and there was simply nothing common enough to make standard.
The best I could do for 2396 and 3986 was to include a
regular expression that accepts all strings and parses them
into the component parts.

I have absolutely no problem with writing a proposed standard
for parsing references, particularly if browser developers are
willing to adhere to one.  However, it is not a redefinition of
URLs, nor does it make sense for error-correcting transformations
(like pct-encoding embedded spaces) to be "the standard" for
parsing when there are plenty of applications that string
parse references for the sake of generating invalid test cases
(e.g., the example attributed to curl).

It is not non-interoperable behavior to parse input data
differently depending on the context in which it is entered.
What matters is that the context be properly documented to
indicate what pre/post-processing is applied, just as we
expect a browser's combined search/location dialog bars to
be documented as not merely URL-entry forms (or be banned
due to the privacy leakage of incremental search results).

....Roy=

From dwm@xpasc.com  Wed Oct 24 16:16:58 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 C4DCC1F0C49 for <ietf@ietfa.amsl.com>; Wed, 24 Oct 2012 16:16:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.711
X-Spam-Level: 
X-Spam-Status: No, score=-1.711 tagged_above=-999 required=5 tests=[AWL=-0.404, BAYES_00=-2.599, MISSING_HEADERS=1.292]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WxWEt4M442X8 for <ietf@ietfa.amsl.com>; Wed, 24 Oct 2012 16:16:58 -0700 (PDT)
Received: from c2w3p-2.abacamail.com (c2w3p-2.abacamail.com [209.133.53.32]) by ietfa.amsl.com (Postfix) with ESMTP id 628071F0419 for <ietf@ietf.org>; Wed, 24 Oct 2012 16:16:58 -0700 (PDT)
Received: from xpasc.com (unknown [68.164.244.188]) by c2w3p-2.abacamail.com (Postfix) with ESMTP id EA36D3FA8A; Wed, 24 Oct 2012 23:16:57 +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 q9ONGvlL011408; Wed, 24 Oct 2012 16:16:57 -0700
Date: Wed, 24 Oct 2012 16:16:57 -0700 (PDT)
From: David Morris <dwm@xpasc.com>
Subject: Re: [whatwg] New URL Standard from Anne van Kesteren on 2012-09-24 (public-whatwg-archive@w3.org from September 2012)
In-Reply-To: <Pine.LNX.4.64.1210232348110.2471@ps20323.dreamhostps.com>
Message-ID: <alpine.LRH.2.01.1210241611060.6521@egate.xpasc.com>
References: <50604C1A.7090901@gmx.de> <5060A964.5060001@stpeter.im> <Pine.LNX.4.64.1210172354500.2478@ps20323.dreamhostps.com> <507F5A7E.6040206@arcanedomain.com> <50856E3C.103@gmail.com> <Pine.LNX.4.64.1210221753010.2471@ps20323.dreamhostps.com> <0DBC8A11-319C-4120-975E-7E40FD5818BF@gbiv.com> <Pine.LNX.4.64.1210222137530.2471@ps20323.dreamhostps.com> <CA+9kkMDpEZCvcG1DJd=O1qPNV+=+GTBeN+CGndUe51Xym_A9sg@mail.gmail.com> <Pine.LNX.4.64.1210232115210.2471@ps20323.dreamhostps.com> <15E1D98B-8883-4936-81A9-174E1323683C@nordsc.com> <CAGKvQ5ZV6_GMVgjEezhR-oKqSikxR7GYgacMitbfczmNh725mw@mail.gmail.com> <Pine.LNX.4.64.1210232348110.2471@ps20323.dreamhostps.com>
User-Agent: Alpine 2.01 (LRH 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Milter-Version: master.1+13-gbab1945
X-AV-Type: clean
X-AV-Accuracy: exact
Cc: URI <uri@w3.org>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: uri@w3.org, ietf@ietf.org
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Oct 2012 23:16:58 -0000

On Tue, 23 Oct 2012, Ian Hickson wrote:

> Having multiple specs means an implementor has to refer to multiple specs 
> to implement one algorithm, which is not a way to get interoperability. 
> Bugs creep in much faster when implementors have to switch between specs 
> just in the implementation of one algorithm.

That is true to the extent that all developers have the same objective but 
we've already established that there at least two case:
a) Products which can assume correct URI (STD 66) syntax and reject errors
b) Products which need to handle human mangled input

By writing merging (a) and (b)->(a) you make life more difficult and hence
error prone for (a). I would suggest that the developers of (b) will be
better served by a clear specification of (a) w/o the (b)->(a) concerns
because that will improve their ability to validate URIs generated by
their logic as well as have meaningful discussions with folks who
assume (a).


From mrex@sap.com  Wed Oct 24 16:25: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 7B04D1F0C6E for <ietf@ietfa.amsl.com>; Wed, 24 Oct 2012 16:25:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.212
X-Spam-Level: 
X-Spam-Status: No, score=-10.212 tagged_above=-999 required=5 tests=[AWL=0.037, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a+o9rvbZ4xiG for <ietf@ietfa.amsl.com>; Wed, 24 Oct 2012 16:25:55 -0700 (PDT)
Received: from smtpde02.sap-ag.de (smtpde02.sap-ag.de [155.56.68.140]) by ietfa.amsl.com (Postfix) with ESMTP id 773581F0419 for <ietf@ietf.org>; Wed, 24 Oct 2012 16:25:55 -0700 (PDT)
Received: from mail.sap.corp by smtpde02.sap-ag.de (26) with ESMTP id q9ONPpXk019074 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 25 Oct 2012 01:25:51 +0200 (MEST)
Subject: Re: Just so I'm clear
In-Reply-To: <50876D39.20502@dougbarton.us>
To: Doug Barton <dougb@dougbarton.us>
Date: Thu, 25 Oct 2012 01:25:50 +0200 (CEST)
X-Mailer: ELM [version 2.4ME+ PL125 (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="ISO-8859-1"
Message-Id: <20121024232550.C14861A2F3@ld9781.wdf.sap.corp>
From: mrex@sap.com (Martin Rex)
X-SAP: out
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: mrex@sap.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Oct 2012 23:25:56 -0000

Doug Barton wrote:
>
> Andrew Sullivan wrote:
>>=20
>> Let me get this straight: for the sake of procedures that are clearly
>> designed to be hard to use,
>=20
> While I think that 3777 probably errs on the side of too hard to use,
> recalling someone from one of these positions _should_ be hard to do,
> and should not be undertaken lightly.

There is a good reason why procedures for recalling someone from
a position in a decision-making body with elected members is much
harder than electing the person into that body.

Sometimes, members are elected by only a small majority over competitors,
and they even may have been "weak supporting" votes, and those may even
be known to each member.  Now it happens that those decision bodies
have to occasionally make contentious or unpopular, but necessary
and hopefully rational and mostly unbiased decisions,

What you want to avoid is those members with "weak" votes to worry
about mainly pleasing one or a few very specific "voters" during
those decisions, that could otherwise have them recalled by just
those persons not voting for them again in the recall procedure.


On a different issue:  The "legal" procedure if someone does not
perform his agreed duties and falls into total inactivity would
be (German legalese "(Ver)s=E4umnisurteil"), which Wikipedia maps to
this english term:

   http://en.wikipedia.org/wiki/Default_judgment


-Martin

From marka@isc.org  Wed Oct 24 16:43:30 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 3A4381F0C70 for <ietf@ietfa.amsl.com>; Wed, 24 Oct 2012 16:43:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.342
X-Spam-Level: 
X-Spam-Status: No, score=-2.342 tagged_above=-999 required=5 tests=[AWL=0.257,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2s+QxHMWjv5P for <ietf@ietfa.amsl.com>; Wed, 24 Oct 2012 16:43:29 -0700 (PDT)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) by ietfa.amsl.com (Postfix) with ESMTP id A09BE1F0C61 for <ietf@ietf.org>; Wed, 24 Oct 2012 16:43:29 -0700 (PDT)
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mail.isc.org", Issuer "RapidSSL CA" (not verified)) by mx.pao1.isc.org (Postfix) with ESMTPS id 49227C9664; Wed, 24 Oct 2012 23:43:23 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (c211-30-172-21.carlnfd1.nsw.optusnet.com.au [211.30.172.21]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by bikeshed.isc.org (Postfix) with ESMTPSA id 1117B216C3B; Wed, 24 Oct 2012 23:43:23 +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 111F52A3997A; Thu, 25 Oct 2012 10:43:20 +1100 (EST)
To: Margaret Wasserman <margaretw42@gmail.com>
From: Mark Andrews <marka@isc.org>
References: <20121023192135.203AC18C0A4@mercury.lcs.mit.edu> <5086EF82.9060900@dougbarton.us> <20121023200713.GC1861@nsn.com> <5086FBCE.2070503@dougbarton.us> <20121023213251.GF27557@verdi> <50873AB4.1000905@dougbarton.us> <20121024034736.GC52558@crankycanuck.ca> <50876D39.20502@dougbarton.us> <508773E7.10203@cisco.com> <50877633.1000402@dougbarton.us> <EA9BEA2E-EE96-4E80-B719-652BBD620A79@lilacglade.org>
Subject: Re: Just so I'm clear
In-reply-to: Your message of "Wed, 24 Oct 2012 08:49:09 EDT." <EA9BEA2E-EE96-4E80-B719-652BBD620A79@lilacglade.org>
Date: Thu, 25 Oct 2012 10:43:20 +1100
Message-Id: <20121024234320.111F52A3997A@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, 24 Oct 2012 23:43:30 -0000

In message <EA9BEA2E-EE96-4E80-B719-652BBD620A79@lilacglade.org>, Margaret Wass
erman writes:
> 
> On Oct 24, 2012, at 1:01 AM, Doug Barton wrote:
> > I get what you're saying, but this is one of those times where (arguably
> > for the better) we've created a difficult procedure that should be
> > infrequently exercised. We should follow the procedure because it _is_
> > the procedure. And then use the opportunity to improve it.
> 
> The existence of the recall procedure does not imply that there isn't any 
> other way for a seat to become vacant.  For example, a seat can become 
> vacant when an I* member resigns or dies, and there is no need for a 
> recall in those cases.  
> 
> I think it is reasonable for the IAOC to set it's own (reasonable, 
> consistent) bar for deciding that a sitting member has vacated his/her 
> seat through lack of attendance and lack of response.  No recall should 
> be needed in that case to replace the missing member, any more than if 
> the person had explicitly resigned.  The IAOC sent a long list of things 
> that they have done to contact Marshall, and he has not responded.  It 
> seems impossible that he has not received any of those contacts, so his 
> lack of response is indicative, IMO, that he has indeed vacated his seat.

But we don't have rules that say, "failure to attend for X period,
without permission, will result in the position being declared
vacant".  I we did this would be simple.  I don't think we have
any choice from a proceedural point of view other than to start
recall proceedings.

> I share the hope of the IAOC and others that Marshall is okay, and that 
> he will return to the IETF when he can.  I appreciate his contributions 
> throughout the years, and I would be happy to see him return to continue 
> making those contributions.  For now, though, he has vacated his IAOC 
> seat and should be replaced.
> 
> Margaret

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

From mcr@sandelman.ca  Wed Oct 24 17:21:16 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 A57D421F8EA4 for <ietf@ietfa.amsl.com>; Wed, 24 Oct 2012 17:21:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.96
X-Spam-Level: 
X-Spam-Status: No, score=-0.96 tagged_above=-999 required=5 tests=[AWL=-1.306,  BAYES_00=-2.599, HOST_MISMATCH_NET=0.311, IP_NOT_FRIENDLY=0.334, MANGLED_OFF=2.3]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rr8Lj1Qh0Guw for <ietf@ietfa.amsl.com>; Wed, 24 Oct 2012 17:21:16 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [67.23.6.41]) by ietfa.amsl.com (Postfix) with ESMTP id 4198821F8E86 for <ietf@ietf.org>; Wed, 24 Oct 2012 17:21:16 -0700 (PDT)
Received: from sandelman.ca (unknown [75.98.19.132]) by relay.sandelman.ca (Postfix) with ESMTPS id 7FE5C81AE; Wed, 24 Oct 2012 20:13:38 -0400 (EDT)
Received: from sandelman.ca (quigon.sandelman.ca [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id D24E6CA0BC; Wed, 24 Oct 2012 20:21:16 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Randall Gellens <randy@qti.qualcomm.com>
Subject: Re: Format=flowed quoting (was "Re: IETF...the unconference of SDOs") In-reply-to: <p06240600cca730fbf54c@[99.111.97.136]>
References: <94279462-0f48-41ec-933a-a7ac22ba204a@email.android.com> <p06240628cca279fdf657@[99.111.97.136]> <41CCF322-545D-49BD-AEC8-F7595AEE0222@me.com> <p06240600cca730fbf54c@[99.111.97.136]>
Comments: In-reply-to Randall Gellens <randy@qti.qualcomm.com> message dated "Fri, 19 Oct 2012 09:45:12 -0700."
X-Mailer: MH-E 8.3; nmh 1.3; XEmacs 21.4 (patch 22)
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Wed, 24 Oct 2012 20:21:16 -0400
Message-ID: <1826.1351124476@sandelman.ca>
Sender: mcr@sandelman.ca
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Oct 2012 00:21:16 -0000

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


Randall Gellens <randy@qti.qualcomm.com> wrote:
    >> Warning: this message was generated by Apple Mail.

    RG> But not using Format=3DFlowed.

    RG> This reflects a misunderstanding of Format=3DFlowed.  Properly
    RG> generated F=3DF has lines of no more than 78 characters.  One of
    RG> the primary goals of F=3DF is good interoperability between
    RG> clients that support F=3DF and those that support traditional pure
    RG> plain text email.  What you're describing is a symptom of HTML
    RG> quoting (or a surprisingly poor F=3DF implementation):

so, really, what you are saying is that my complaint is not about a poor
F=3DF implementation, but in fact, not even being attempted.  It's just a
really poor text/plain part generated to go along with an (often absent)
text/html part, combined with a forced "upgrade" from text/plain to
text/html on the display side.

That's why they aren't marking, or paying attention to format=3D, because
they didn't even know about it.

=2D-=20
Michael Richardson
=2Don the road-



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

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

iQEcBAABAgAGBQJQiIX8AAoJEKD0KQ7Gj3P2pXIH/1grm1o2M0FyttMkz/XhC+LD
vidnRbGPr8fq1IyPTksa9VKAw6U299fTImOK2kN503aOTfNuJGp1hqii6uTSCNJw
nIokJYAa/8vklaQf70jvabwrVrpYagxgM7Mh/HQ8GAEkpCY8Y87gSkrjOrVoSSxz
4bndEC5E7in0tWdCLi9K/Ex/IBTrvAE81fuCAs68YRfcNTLXQjKJAPzmjJ2MNwB+
OULN4zjU9WIFCwdytRuVsYiSg4BbRLb1783A3PtvGcxkcafWbfYS2sv2QKDX1gF3
7Kvq1PZxrbAeokqxn0hnNYW7aDfd+ptpVv/t2ir0wtn0rMQY9fjkkVQodcmEC0w=
=SmuY
-----END PGP SIGNATURE-----
--=-=-=--

From mcr@sandelman.ca  Wed Oct 24 17:25:55 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 3B0661F0C7E for <ietf@ietfa.amsl.com>; Wed, 24 Oct 2012 17:25:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.023
X-Spam-Level: 
X-Spam-Status: No, score=-2.023 tagged_above=-999 required=5 tests=[AWL=-0.069, BAYES_00=-2.599, HOST_MISMATCH_NET=0.311, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ydBqOKuKXBUC for <ietf@ietfa.amsl.com>; Wed, 24 Oct 2012 17:25:54 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [67.23.6.41]) by ietfa.amsl.com (Postfix) with ESMTP id D40231F0C71 for <ietf@ietf.org>; Wed, 24 Oct 2012 17:25:54 -0700 (PDT)
Received: from sandelman.ca (unknown [75.98.19.132]) by relay.sandelman.ca (Postfix) with ESMTPS id A6FD381AE; Wed, 24 Oct 2012 20:18:19 -0400 (EDT)
Received: from sandelman.ca (quigon.sandelman.ca [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 92250CA0BC; Wed, 24 Oct 2012 20:25:54 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Sabahattin Gucukoglu <listsebby@me.com>
Subject: Re: Format=flowed quoting (was "Re: IETF...the unconference of SDOs")
In-reply-to: <FB2B1327-D139-4986-BC4A-C0F45D7C3865@me.com>
References: <94279462-0f48-41ec-933a-a7ac22ba204a@email.android.com> <p06240628cca279fdf657@[99.111.97.136]> <41CCF322-545D-49BD-AEC8-F7595AEE0222@me.com> <p06240600cca730fbf54c@[99.111.97.136]> <FB2B1327-D139-4986-BC4A-C0F45D7C3865@me.com>
Comments: In-reply-to Sabahattin Gucukoglu <listsebby@me.com> message dated "Fri, 19 Oct 2012 19:46:28 +0100."
X-Mailer: MH-E 8.3; nmh 1.3; XEmacs 21.4 (patch 22)
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Wed, 24 Oct 2012 20:25:54 -0400
Message-ID: <2380.1351124754@sandelman.ca>
Sender: mcr@sandelman.ca
Cc: Randall Gellens <randy@qti.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, 25 Oct 2012 00:25:55 -0000

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


Sabahattin Gucukoglu <listsebby@me.com> wrote:
SG> Let's clear up the confusion.  I made two mistakes, firstly by
SG> calling this "F/F semantics" when what I mean is some sort of
SG> long-line-aware reflowing and quoting.  We'll have to find a name
SG> for it.  The other mistake was to call plain text plain text of any
SG> description, irrespective of the definition of text/plain.=20=20

    SG> So we are talking about three formats:
    SG> * text/plain, 78 characters wide
    SG> * format=3Dflowed, text/plain with soft breaks signalled by trailin=
g whitespace, 78 characters
    SG> * text/paragraphs (or whatever), a completely different identity th=
at violates the length limits

    SG> Apple Mail and Microsoft use this text/paragraphs.  It's not

Do you think it would be worth writing a specification for text/paragraphs?

Heuristically, it's not that hard to identify, and a small patch for
mailman would at least mark email as being in that format, so that at
least, IETF lists could have email that complies to some standard.

(Whether or not we then drop email that doesn't have a text/plain part
is a second conversation)

=2D-=20
Michael Richardson
=2Don the road-



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

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

iQEcBAABAgAGBQJQiIcSAAoJEKD0KQ7Gj3P2XuIIALqK5THR4VZ9tNn89aTPggsg
ODLKtfP+B++z7hMsvhlqJaGPDNzESswjKkM6OHHL/gb+SWnBcn4r0sXYdz1c0oEp
FluQq+aahcvwZAgj1TVD+tE2arH/kWplvSZd7wWZuoM/hXE5+Sz4C/Atpe6MrQP3
mzGATtTzPvt24N1NOBqQpiga4pCqOuNktOiVAviCE0qAT6dVc+f58hE3ZQeWoZQ0
BtTt6pQzVPveMGsMsN/hbGRvXdv+GJ6gq/v/a/FFCtXpa14JoaAqo3sa/jom3klJ
Pby+DtuzVUXfgHSAP/SfZet3UngAAFg266lNmmZ3nU/O/ubmYrzUD3sZ1OLh6Oc=
=yLZM
-----END PGP SIGNATURE-----
--=-=-=--

From johnl@iecc.com  Wed Oct 24 20:00:17 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 1925821F866E for <ietf@ietfa.amsl.com>; Wed, 24 Oct 2012 20:00:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -111.771
X-Spam-Level: 
X-Spam-Status: No, score=-111.771 tagged_above=-999 required=5 tests=[AWL=0.428, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tPYgJFaTEk+3 for <ietf@ietfa.amsl.com>; Wed, 24 Oct 2012 20:00:16 -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 A813311E80AE for <ietf@ietf.org>; Wed, 24 Oct 2012 20:00:15 -0700 (PDT)
Received: (qmail 25771 invoked from network); 25 Oct 2012 03:00:13 -0000
Received: from leila.iecc.com (64.57.183.34) by mail1.iecc.com with QMQP; 25 Oct 2012 03:00:13 -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=5088ab3d.xn--yuvv84g.k1210; i=johnl@user.iecc.com; bh=r/RclvJIQFIEnjXvZWKAEU1wOFwxDzrc5BNGRuA0Vk8=; b=Da71ndsCVCwcVu9Hlms0TWGnwQ/TivnGCmz0dgxftT7nQfBn/OpGbEd3O2iqsJ5Pj8rhAMpIEkPDIld1Z56iwn8EN2rdxX9TgCxdFNmgXlZ7MnzKycA6PLFRorg2Jjt1HWuz5F8yZK35aZlBENt1BDgvg1qypsFr9ZFSZF0jaV0=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:vbr-info; s=5088ab3d.xn--yuvv84g.k1210; olt=johnl@user.iecc.com; bh=r/RclvJIQFIEnjXvZWKAEU1wOFwxDzrc5BNGRuA0Vk8=; b=GZd1E+LyeZHSKg7lJb3ajdBrecTxlr5tibA1WU1GKEX08RGHXuDRN84A/7rofkqCer4s9prtVjlcqz50+4+ZFVWRZb4Rs91pnamS5y4PrggWnzWpiJD3AIIwma/40fZWzBg8O+IVGeTuLEs0eh/k5b4qKfpLEp0tNy6keRnDmjA=
VBR-Info: md=iecc.com; mc=all; mv=dwl.spamhaus.org
Date: 25 Oct 2012 02:59:51 -0000
Message-ID: <20121025025951.3245.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: rules for the sake of rules, was Just so I'm clear
In-Reply-To: <20121024234320.111F52A3997A@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: Thu, 25 Oct 2012 03:00:17 -0000

>But we don't have rules that say, "failure to attend for X period,
>without permission, will result in the position being declared
>vacant".  I we did this would be simple.  I don't think we have
>any choice from a proceedural point of view other than to start
>recall proceedings.

Having reread RFC 4071, I don't see a rule that says that the death of
a member will result in the position being declared vacant, either.
Nor are there any rules that say what documentation would be required
to establish that someone had died.

At some point we have to allow a sliver of common sense to intervene
so people can do reasonable things to solve problems.

R's,
John

From kosmo.zb@gmail.com  Wed Oct 24 20:37:31 2012
Return-Path: <kosmo.zb@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 955DD1F0C4A for <ietf@ietfa.amsl.com>; Wed, 24 Oct 2012 20:37:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WZh0vxOsqQdM for <ietf@ietfa.amsl.com>; Wed, 24 Oct 2012 20:37:30 -0700 (PDT)
Received: from mail-oa0-f44.google.com (mail-oa0-f44.google.com [209.85.219.44]) by ietfa.amsl.com (Postfix) with ESMTP id 061C91F0C6A for <ietf@ietf.org>; Wed, 24 Oct 2012 20:37:29 -0700 (PDT)
Received: by mail-oa0-f44.google.com with SMTP id n5so1311823oag.31 for <ietf@ietf.org>; Wed, 24 Oct 2012 20:37:28 -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=SPPy4ES9LUn+157VP35193JShq2zjpp/VAg4SsCHij8=; b=EdMLUItd1gom/yBsTUwyic8tzHXG44iZVeMUmwDBr0bflku7ikmW7Pmqly5ujs+Xes eCBu4DxfHfGaVpjIkMdTO2Azj//Ez9TAXwCglD4vHTUJjEMkAzCcNk+t5HkU9CzUkjBT x+6WFl+Z7SJkfE5sB4L0NpoES3Ykq4DgP6O5cGiRO/FMQqwXyeXp6aXFVcLK+GPoxoWC YzZBZMthTruySfZZS2Q1q0DLWwzLdIm9FIkti6R1jq3250ypHXtPnNizRLpLr3Zi1JtF lb9J5pYWcZgkcAWlHAXdHkZZvxRivxxrlC8V+h5JtgirnNKV1Jr+xKIVzyuX0iGMXQ0J RkoA==
MIME-Version: 1.0
Received: by 10.60.14.165 with SMTP id q5mr16159174oec.28.1351136248850; Wed, 24 Oct 2012 20:37:28 -0700 (PDT)
Received: by 10.76.13.132 with HTTP; Wed, 24 Oct 2012 20:37:28 -0700 (PDT)
In-Reply-To: <Pine.LNX.4.64.1210240451150.2471@ps20323.dreamhostps.com>
References: <50604C1A.7090901@gmx.de> <5060A964.5060001@stpeter.im> <Pine.LNX.4.64.1210172354500.2478@ps20323.dreamhostps.com> <507F5A7E.6040206@arcanedomain.com> <50856E3C.103@gmail.com> <Pine.LNX.4.64.1210221753010.2471@ps20323.dreamhostps.com> <0DBC8A11-319C-4120-975E-7E40FD5818BF@gbiv.com> <Pine.LNX.4.64.1210222137530.2471@ps20323.dreamhostps.com> <CA+9kkMDpEZCvcG1DJd=O1qPNV+=+GTBeN+CGndUe51Xym_A9sg@mail.gmail.com> <Pine.LNX.4.64.1210232115210.2471@ps20323.dreamhostps.com> <15E1D98B-8883-4936-81A9-174E1323683C@nordsc.com> <CAGKvQ5ZV6_GMVgjEezhR-oKqSikxR7GYgacMitbfczmNh725mw@mail.gmail.com> <Pine.LNX.4.64.1210232348110.2471@ps20323.dreamhostps.com> <CAAWM5Tz3NdprjqwgyoVoV9qUuiwXb2gTQ49u4a4ePGfjyusDkw@mail.gmail.com> <Pine.LNX.4.64.1210240451150.2471@ps20323.dreamhostps.com>
Date: Wed, 24 Oct 2012 20:37:28 -0700
Message-ID: <CAAWM5TzjsxOWB4pL3XaWAa5zDdsZb=1-jOZ2JM9L9hbPtd7azA@mail.gmail.com>
Subject: Re: [whatwg] New URL Standard from Anne van Kesteren on 2012-09-24 (public-whatwg-archive@w3.org from September 2012)
From: David Sheets <kosmo.zb@gmail.com>
To: Ian Hickson <ian@hixie.ch>
Content-Type: text/plain; charset=ISO-8859-1
X-Mailman-Approved-At: Wed, 24 Oct 2012 20:37:57 -0700
Cc: Ted Hardie <ted.ietf@gmail.com>, IETF Discussion <ietf@ietf.org>, Christophe Lauret <clauret@weborganic.com>, Jan Algermissen <jan.algermissen@nordsc.com>, URI <uri@w3.org>, Anne van Kesteren <annevk@annevk.nl>, "Manger, James H" <James.H.Manger@team.telstra.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, 25 Oct 2012 03:37:31 -0000

On Tue, Oct 23, 2012 at 10:05 PM, Ian Hickson <ian@hixie.ch> wrote:
> On Wed, 24 Oct 2012, Manger, James H wrote:
>>
>> Currently, I don't think url.spec.whatwg.org distinguishes between
>> strings that are valid URLs and strings that can be interpreted as URLs
>> by applying its standardised error handling. Consequently, error
>> handling cannot be at the option of the software developer as you cannot
>> tell which bits are error handling.
>
> Well first, the whole point of discussions like this is to work out what
> the specs _should_ say; if the specs were perfect then there wouldn't be
> any need for discussion.

Good! Let's have a discussion about what the spec should say.

> On Tue, 23 Oct 2012, David Sheets wrote:
>>
>> One algorithm? There seem to be several functions...
>>
>> - URI reference parsing (parse : scheme -> string -> raw uri_ref)
>> - URI reference normalization (normalize : raw uri_ref -> normal uri_ref)
>> - absolute URI predicate (absp : normal uri_ref -> absolute uri_ref option)
>> - URI resolution (resolve : absolute uri_ref -> _ uri_ref -> absolute uri_ref)
>
> I don't understand what your four algorithms are supposed to be.

Ian, these are common descriptors (and function signatures).

Here are (longer) prose descriptions for those unfamiliar with
standard functional notation:

*parse* is a function which takes the contextual scheme and a string
to be parsed and produces a structure of unnormalized reference
components.
*normalize* is a function which takes a structure of unnormalized
reference components and produces a structure of normalized reference
components (lower-casing scheme, lower-casing host for some schemes,
collapsing default ports, coercing invalid codepoints, etc).
*absp* is a function which takes a structure of normalized reference
components and potentially produces a structure of normalized
reference components which is guaranteed to be absolute (or nothing:
in JS, this roughly corresponds to nullable).
*resolve* is a function which takes a URI structure and a reference
component structure and produces a URI structure corresponding to the
reference resolution of the second argument against the first (base)
argument.

See my original message for how these compose into your one_algorithm.

> There's just one algorithm as far as I can tell -- it takes as input an
> arbitrary string and a base URL object, and returns a normalised absolute
> URL object, where a "URL object" is a conceptual construct consisting of
> the components scheme, userinfo, host, port, path, query, and
> fragment, which can be serialised together into a string form.

How is the arbitrary string deconstructed? How is the result
normalized? What constitutes an absolute reference? How does a
reference resolve against a base URI?

>> Anne's current draft increases the space of valid addresses.
>
> No, Anne hasn't finished defining conformance yet. (He just started
> today.)

This is a political dodge to delay the inevitable discussion of
address space expansion.

>From what I have read of WHATWG's intentions and discussed with you
and others, you are codifying current browser behavior for
'interoperability'. Current browsers happily consume and emit URIs
that are invalid per STD 66.

<http://url.spec.whatwg.org/#writing> presently says:
"A fragment is "#", followed by any URL unit that is not one of
U+0009, U+000A, and U+000D."
This is larger than STD 66's space of valid addresses.

>> > The de facto parsing rules are already complicated by de facto
>> > requirements for handling errors, so defining those doesn't increase
>> > complexity either (especially if such behaviour is left as optional,
>> > as discussed above.)
>>
>> *parse* is separate from *normalize* is separate from checking if a
>> reference is absolute (*absp*) is separate from *resolve*.
>
> No, it doesn't have to be. That's actually a more complicated way of
> looking at it than necessary, IMHO.

Why use several simple, flexible sharp tools when you could use a
single complicated, monolithic blunt tool?

Why do you insist on producing a single, brittle, opaque function when
you could produce several simply-defined functions that actually model
the data type transformations?

Vendors are, of course, always free to implement an optimized
composition for their specific use cases.

>> Why don't we have a discussion about the functions and types involved in
>> URI processing?
>>
>> Why don't we discuss expanding allowable alphabets and production rules?
>
> Personally I think this kind of open-ended approach is not a good way to
> write specs.

The specs already exist and use these formalisms successfully. Why do
you think discussions about the model of the problem-space are
'open-ended'? Why are you trying to stop a potentially productive
discussion?

> Better is to put forward concrete use cases, technical data,
> etc, and let the spec editor take all that into account and turn it into a
> standard.

Is <https://github.com/dsheets/ocaml-uri/blob/master/lib/uri.ml#L108>
correct or should safe_chars_for_fragment include '#'?

Whatever 'standard' you produce will require me to exert significant
effort on your One Giant Algorithm to factor it into its proper
components and reconcile it with competing standards for my users. I
have applications that use each of the above functions separately.

> Arguing about what precise alphabets are allowed and whether to
> spec something using prose or production rules is just bikeshedding.

I can only conclude that you understand neither the value of precision
nor the meaning of "bikeshedding".

You are not constructing anything remotely comparable to a nuclear reactor.

I am expressing a genuine desire to discuss the actual technical
content of the relevant specifications in the most precise and concise
way possible.

I am losing confidence in your technical leadership.

Sincerely,

David Sheets

From ynir@checkpoint.com  Wed Oct 24 23:15:49 2012
Return-Path: <ynir@checkpoint.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E49EC21E8037 for <ietf@ietfa.amsl.com>; Wed, 24 Oct 2012 23:15:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.585
X-Spam-Level: 
X-Spam-Status: No, score=-10.585 tagged_above=-999 required=5 tests=[AWL=0.014, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KOvhp6p-w4pw for <ietf@ietfa.amsl.com>; Wed, 24 Oct 2012 23:15:48 -0700 (PDT)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id E698E21F8830 for <ietf@ietf.org>; Wed, 24 Oct 2012 23:15:47 -0700 (PDT)
Received: from il-ex01.ad.checkpoint.com (il-ex01.ad.checkpoint.com [194.29.34.26]) by smtp.checkpoint.com (8.13.8/8.13.8) with ESMTP id q9P6Ffmo022463; Thu, 25 Oct 2012 08:15:41 +0200
X-CheckPoint: {5088D6EF-5-1B221DC2-2FFFF}
Received: from il-ex01.ad.checkpoint.com ([194.29.34.26]) by il-ex01.ad.checkpoint.com ([126.0.0.2]) with mapi; Thu, 25 Oct 2012 08:15:40 +0200
From: Yoav Nir <ynir@checkpoint.com>
To: "mrex@sap.com" <mrex@sap.com>
Date: Thu, 25 Oct 2012 08:15:39 +0200
Subject: Re: Just so I'm clear
Thread-Topic: Just so I'm clear
Thread-Index: Ac2yeCgew6YBBiiZSPiqe5dlEDbBpw==
Message-ID: <50AF7BF6-75E5-4F07-91A5-D80145A3F96B@checkpoint.com>
References: <20121024232550.C14861A2F3@ld9781.wdf.sap.corp>
In-Reply-To: <20121024232550.C14861A2F3@ld9781.wdf.sap.corp>
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, 25 Oct 2012 06:15:49 -0000

On Oct 25, 2012, at 1:25 AM, Martin Rex wrote:

> Doug Barton wrote:
>>=20
>> Andrew Sullivan wrote:
>>>=20
>>> Let me get this straight: for the sake of procedures that are clearly
>>> designed to be hard to use,
>>=20
>> While I think that 3777 probably errs on the side of too hard to use,
>> recalling someone from one of these positions _should_ be hard to do,
>> and should not be undertaken lightly.
>=20
> There is a good reason why procedures for recalling someone from
> a position in a decision-making body with elected members is much
> harder than electing the person into that body.
>=20
> Sometimes, members are elected by only a small majority over competitors,
> and they even may have been "weak supporting" votes, and those may even
> be known to each member.  Now it happens that those decision bodies
> have to occasionally make contentious or unpopular, but necessary
> and hopefully rational and mostly unbiased decisions,
>=20
> What you want to avoid is those members with "weak" votes to worry
> about mainly pleasing one or a few very specific "voters" during
> those decisions, that could otherwise have them recalled by just
> those persons not voting for them again in the recall procedure.

All correct, except that the IAOC (and IAB, IESG) are not elected. Just as =
some companies have staffing committees which make the decision on who to h=
ire and who to promote, the IETF has the NomCom. While they have the power =
to appoint people to vacant positions, they don't have firing power, and ha=
ve no bigger say in a recall process than you or me.

There is a good reason to make it hard to unseat a president or prime minis=
ter. There is a good reason to make it hard to unseat an IAOC member if the=
 claim is made that they're trying to get rid of him because he's voting ag=
ainst the decisions favored by Russ or Bob. This is not the case here. He h=
as simply chosen a particularly strange way to resign.

If president Obama chose to hide in the presidential bedroom and not answer=
 the phone, Mr. Biden would be sworn in within hours, not three months.

Yoav


From brian.e.carpenter@gmail.com  Thu Oct 25 00:22:29 2012
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 18F1F21F9084 for <ietf@ietfa.amsl.com>; Thu, 25 Oct 2012 00:22:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.696
X-Spam-Level: 
X-Spam-Status: No, score=-101.696 tagged_above=-999 required=5 tests=[AWL=-0.005, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vkI-ks5X6C-t for <ietf@ietfa.amsl.com>; Thu, 25 Oct 2012 00:22:28 -0700 (PDT)
Received: from mail-ea0-f172.google.com (mail-ea0-f172.google.com [209.85.215.172]) by ietfa.amsl.com (Postfix) with ESMTP id 675A521F9082 for <ietf@ietf.org>; Thu, 25 Oct 2012 00:22:26 -0700 (PDT)
Received: by mail-ea0-f172.google.com with SMTP id k13so463840eaa.31 for <ietf@ietf.org>; Thu, 25 Oct 2012 00:22:25 -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=ZIWYBQHqt1Af6/nY9t9kIKkdXCt5SMxsqrBMZu88vPU=; b=k+0wMCXZOUtCjP4LyV5vpbZh3mnSdOQt6Iv9KntCX00VZYsRcUhf06H0iB5gcc5H+5 Yt4B/Q5cKzOzm6qEiCQ9XopqXafJyY2gdsj/GPjKMT//55apKHy4UEoRnWAw+uRbEp/s 3TxzwV1BkUQ3SohOPd71b+sRtcjVH6bZDfp6y8Y29uulsfjm4NBayLBa+RqrTeNga7M6 PTqCFKBmZb6ZlnEUrd4P9II/jv8furnz+C+wbRnKiL6guAOlybsIwyBVz7WhktJzigsF IUPVrnqIfG9+wbUYkhsQeSBzTo8gAk1sdXi8E8K1iHnB4p04CFU9qHVZwwEwLKxaJsEn hSzQ==
Received: by 10.14.214.2 with SMTP id b2mr25169288eep.32.1351149745666; Thu, 25 Oct 2012 00:22:25 -0700 (PDT)
Received: from [192.168.1.65] (host-2-102-218-61.as13285.net. [2.102.218.61]) by mx.google.com with ESMTPS id o47sm29132127eem.11.2012.10.25.00.22.24 (version=SSLv3 cipher=OTHER); Thu, 25 Oct 2012 00:22:24 -0700 (PDT)
Message-ID: <5088E8B6.5060004@gmail.com>
Date: Thu, 25 Oct 2012 08:22:30 +0100
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Barry Leiba <barryleiba@computer.org>
Subject: Re: [RFC 3777 Update for Vacancies]
References: <D90D92A7-0906-4620-93A0-D116D15A10FA@gmail.com> <CAC4RtVCE_ocLmv1Q4DtGn8GYHRs1byatrXpTjHLX5wueg=jx_g@mail.gmail.com>
In-Reply-To: <CAC4RtVCE_ocLmv1Q4DtGn8GYHRs1byatrXpTjHLX5wueg=jx_g@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Bob Hinden <bob.hinden@gmail.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Oct 2012 07:22:29 -0000

On 24/10/2012 21:22, Barry Leiba wrote:
>> The draft that proposes changes to the RFC3777/BCP10 to deal with
>> vacancies is now available.
>>
>>   http://tools.ietf.org/html/draft-ietf-genarea-bcp10upd-00
...
> I think this is a fine proposal, and I support it and hope the community
> will show consensus for it.

+1.

However, I suggest that "For a contested, sustained absence,..." is
a little unclear. I suggest

   If the member concerned contests the determination that they have
   vacated the position, the existing Member Recall process, as specified
   in Section 7 of [RFC3777], is required.

(This contest could occur during the Last Call.)

     Brian

From brian.e.carpenter@gmail.com  Thu Oct 25 00:46: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 BA7C721F892D for <ietf@ietfa.amsl.com>; Thu, 25 Oct 2012 00:46:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.696
X-Spam-Level: 
X-Spam-Status: No, score=-101.696 tagged_above=-999 required=5 tests=[AWL=-0.005, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Dpzwu0mMeAwH for <ietf@ietfa.amsl.com>; Thu, 25 Oct 2012 00:46:31 -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 B85AC21F892C for <ietf@ietf.org>; Thu, 25 Oct 2012 00:46:30 -0700 (PDT)
Received: by mail-ee0-f44.google.com with SMTP id d4so555510eek.31 for <ietf@ietf.org>; Thu, 25 Oct 2012 00:46: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=SkY2GvP60E6lIJzcBC3b/JG+4vX5yqNa4PUnzf8q2CI=; b=iT8V9Jn2nkRXjEW1RF+h6HQx9Of+dU9nZA5rvhs+vewpKs/VKE/y8n5WxIQre2VViS tjxY1Yo5rVCrFzmrI77fAcM34nX1kwlXEezwVGRFq+gWlPvzci2rXEeVAiKS+nb7OoZc NVcCy1dNsjIwHrwCGjjPlf/vAnK6OjxPAxtKnHbXmF/1YEzv3HEoEvcYSKJ0GSjOSe0M 7JUGZk+uKNJ0Yht88MsduGehPpCYEcmFTQGHr1PLnFamikwkWJkfQj1+rBjkWNnqwdpN aEnNrK0Pazc8aPWyEb0Z/xFKzqNk7VEvozSrpOVqcIgKqQk+PrnnlhDbugqZZB+VxUZq 9cJw==
Received: by 10.14.184.1 with SMTP id r1mr25050824eem.4.1351151189807; Thu, 25 Oct 2012 00:46:29 -0700 (PDT)
Received: from [192.168.1.65] (host-2-102-218-61.as13285.net. [2.102.218.61]) by mx.google.com with ESMTPS id i1sm29219887eeo.8.2012.10.25.00.46.27 (version=SSLv3 cipher=OTHER); Thu, 25 Oct 2012 00:46:28 -0700 (PDT)
Message-ID: <5088EE5A.4090103@gmail.com>
Date: Thu, 25 Oct 2012 08:46:34 +0100
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Doug Barton <dougb@dougbarton.us>
Subject: Re: Just so I'm clear
References: <20121023192135.203AC18C0A4@mercury.lcs.mit.edu>	<5086EF82.9060900@dougbarton.us> <20121023200713.GC1861@nsn.com>	<5086FBCE.2070503@dougbarton.us> <20121023213251.GF27557@verdi>	<50873AB4.1000905@dougbarton.us>	<20121024034736.GC52558@crankycanuck.ca>	<50876D39.20502@dougbarton.us> <508773E7.10203@cisco.com>	<50877633.1000402@dougbarton.us>	<EA9BEA2E-EE96-4E80-B719-652BBD620A79@lilacglade.org> <508842C2.4020203@dougbarton.us>
In-Reply-To: <508842C2.4020203@dougbarton.us>
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, 25 Oct 2012 07:46:31 -0000

On 24/10/2012 20:34, Doug Barton wrote:
...
> ... Nothing in the text suggests an
> unfettered right of creating new definitions of "vacant."

You mean, new compared to the first definition in Merriam-Webster.com?

1: not occupied by an incumbent, possessor, or officer <a vacant office> <vacant thrones>

Objectively and factually, that seems to be the case. The IAOC is actually
going an extra mile rather than simply informing NomCom that the seat
has become vacant.

    Brian



From Tina.Tsou.Zouting@huawei.com  Wed Oct 24 22:04:42 2012
Return-Path: <Tina.Tsou.Zouting@huawei.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5553A21F88FA for <ietf@ietfa.amsl.com>; Wed, 24 Oct 2012 22:04:42 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Sij5aTPoH65I for <ietf@ietfa.amsl.com>; Wed, 24 Oct 2012 22:04:41 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id F058D21F8830 for <ietf@ietf.org>; Wed, 24 Oct 2012 22:04:40 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id AKX65038; Thu, 25 Oct 2012 05:04:36 +0000 (GMT)
Received: from LHREML406-HUB.china.huawei.com (10.201.5.243) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 25 Oct 2012 06:03:01 +0100
Received: from DFWEML404-HUB.china.huawei.com (10.193.5.203) by lhreml406-hub.china.huawei.com (10.201.5.243) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 25 Oct 2012 06:03:12 +0100
Received: from DFWEML513-MBS.china.huawei.com ([169.254.4.153]) by dfweml404-hub.china.huawei.com ([10.193.5.203]) with mapi id 14.01.0323.003; Wed, 24 Oct 2012 22:03:09 -0700
From: Tina TSOU <Tina.Tsou.Zouting@huawei.com>
To: The IAOC <bob.hinden@gmail.com>
Subject: Re: IAOC Request for community feedback
Thread-Topic: IAOC Request for community feedback
Thread-Index: AQHNsK/2oJWynEHbaU2ZkVwkmohmA5fJkHWA
Date: Thu, 25 Oct 2012 05:03:09 +0000
Message-ID: <0E6823FE-31CA-426D-BA3E-E0A2C3674215@huawei.com>
References: <20121022234941.28301.7687.idtracker@ietfa.amsl.com>
In-Reply-To: <20121022234941.28301.7687.idtracker@ietfa.amsl.com>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="us-ascii"
Content-ID: <12BDBA69E35FCA43ACD059EFE9DFFB1F@huawei.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mailman-Approved-At: Thu, 25 Oct 2012 02:10:34 -0700
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Oct 2012 05:04:42 -0000

Dear Bob,
It is reasonable to declare Marshall's IAOC position vacant.
As far as I know, his wife had medical issue this year.


Thank you,
Tina

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

> The IAOC is requesting feedback from the community concerning a
> vacancy that the IAOC feels is not adequately covered by existing IETF
> rules.
>=20
> Marshall Eubanks has been a active IETF participant for many years and
> a member of the IAOC since 2009. However, he recently stopped
> participating in the IAOC and Trust. The IAOC has made extensive
> efforts to contact Marshall about this, but has not received any
> response. Given the size of the IAOC, a missing member makes it much
> harder to get a quorum. The specifics of his absence include:
>=20
> - Missed the IAOC calls on 11 October 2012, 10 September 2012,
>   6 September 2012, 23 August 2012
>=20
> - No email received from Marshall since 1 August 2012 on the IAOC,
>   IETF Trust, and related private lists.
>=20
> Marshall is subscribed to the IAOC and IETF Trust lists and
> consequently should have received email discussing regular
> IAOC/Trust business including email on this topic.
>=20
> We have tried to contact Marshall over this time period using email 14
> times, telephone 6 times (leaving messages), SMS messages seven times,
> Linkedin messages once, Facebook messages once, and registered postal
> mail twice. We have not received any response from Marshall. It is
> also our understanding that Marshall has stopped participating in
> other IETF lists and stopped working on IDs he authored.
>=20
> On 6 September 2012 the IAOC appointed a replacement liaison to the
> IETF NomCom after learning from the NomCom chair that Marshall had not
> responded to emails from the NomCom chair.
>=20
> Based on all of this, the IAOC has concluded that Marshall's IAOC positio=
n
> is vacant.
>=20
> The IAOC has reviewed BCP101 and concludes it does not handle this
> case very well. BCP101 says that if "an IAOC member abrogates his or
> her duties" the recall process in BCP10/RFC3777 may be used. The
> specific text is:
>=20
>   IAOC members are subject to recall in the event that an IAOC member
>   abrogates his or her duties or acts against the best interests of the
>   IETF community. Any appointed IAOC member, including any appointed
>   by the IAB, IESG, or ISOC Board of Trustees, may be recalled using
>   the recall procedure defined in RFC 3777 [RFC3777]. IAOC members are
>   not, however, subject to recall by the bodies that appointed them.
>=20
>   If a vacancy occurs among the appointed members, this is filled by
>   the appointing body for that position according to its procedures.
>=20
> The conditions for determining that a vacancy exist are not well-defined.
>=20
> BCP10/RFC3777 (Section 7) defines a process where a recall petition is
> signed by 20 NomCom qualified IETFers, the petition is sent to the
> ISOC President, the ISOC President appoints a recall committee chair,
> the chair follows normal NomCom procedures to select 20 committee
> members (this includes a public call for volunteers, max of two per
> organization, random selection of volunteers, etc.), recall committee
> investigates, recall committee votes and requires a 3/4 majority to
> pass the recall.
>=20
> We think this process was not intended to be used when a sitting IAOC,
> IESG, or IAB member vacates his/her position. We believe that the
> intended use of this process was for determining whether a member
> should leave a position who is unwilling to leave and who has harmed
> the IETF. That is clearly not the case in this situation, to the
> contrary, we would have preferred Marshall to continue. It doesn't
> seem appropriate in this case, or when an member is unable to
> participate due to illness or death.
>=20
> The IAOC believes that it is reasonable to declare Marshall's IAOC
> position vacant and, therefore, to ask NomCom to fill his position for
> the remainder of his term (~15 months.)
>=20
> The IAOC is requesting feedback from the community whether it is
> reasonable to declare Marshall's IAOC position vacant. Responses are
> solicited by no later than 5 November 2012. If there is not community
> support for this approach, the IAOC will pursue the BCP10/RFC3777
> recall petition path because having a missing member for 15 months
> significantly effects the operation of the IAOC and IETF Trust.
>=20
> Please send your comments to <ietf@ietf.org>.
>=20
> The IAOC and IETF chairs will review the community feedback and make a
> determination if there is support for declaring the position vacant.
>=20
> I would add that we all feel very badly for Marshall given his many
> years of service to the IETF. We really don't understand why he is not
> responding and are concerned about it. Unfortunately, we don't know
> what else to do given his lack of response to our many attempts to
> contact him.
>=20
> Bob Hinden
> IAOC Chair
>=20
> p.s. A draft is in progress that proposes an update to
> BCP10/RFC3777 similar to what we propose here to handle how cases of
> vacancy be handled. The issue applies to the IAB, IESG, and the IAOC.
> An announcement will be sent when that is available.

From jnc@mercury.lcs.mit.edu  Thu Oct 25 05:53:58 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 066E321F89FC for <ietf@ietfa.amsl.com>; Thu, 25 Oct 2012 05:53:58 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id k78QmO4xWkwK for <ietf@ietfa.amsl.com>; Thu, 25 Oct 2012 05:53:57 -0700 (PDT)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id 4F14821F86E1 for <ietf@ietf.org>; Thu, 25 Oct 2012 05:53:57 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 285D818C0A0; Thu, 25 Oct 2012 08:53:51 -0400 (EDT)
To: ietf@ietf.org
Subject: Re: don't overthink, was Just so I'm clear
Message-Id: <20121025125351.285D818C0A0@mercury.lcs.mit.edu>
Date: Thu, 25 Oct 2012 08:53:51 -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, 25 Oct 2012 12:53:58 -0000

    > From: David Morris <dwm@xpasc.com>

    > someone unsatisfied with a business decision by the adjusted IAOC
    > membership could sue based on documented process not being followed to
    > appoint the membership.

Nothing can stop someone from filing a suit, no matter what you do (even if
you do follow procedure). But try looking at it this way.


We're all agreed that the IETF in plenary mode (i.e. all of us) can change
any/all policy/procedures, right?

So, view the original call from the IAOC as a request to the IETF, in formal
plenary mode, to make the following policy/procedure changes/etc:

- To declare that, due to an oversight on our part at the time of drafting,
our existing policy/procedure does not handle certain cases, so we are
_temporarily_ (see below) setting up an ad hoc procedure to handle those
cases;

- That said temporary ad hoc procedure is to have the IETF in plenary mode
decide/declare that positions are vacant due to the withdrawal of the holder.

The call also make the following procedural request:

- That, following that temporary ad hoc procedure, in the particular case in
the original call, the holder be declared to have vacated, due to his long
lack of communication, despite _extensive_ attempts to contact him.

So if people all hum to OK all that, it has _just as much legitimacy_ as
_any other policy/procedure set into place by the IETF in plenary mode_.


And of course we all recognize that we need to write down non-ad hoc
policy/procedure to handle such cases, an effort which has already started.


    > From: "John Levine" <johnl@taugh.com>

    > Having reread RFC 4071, I don't see a rule that says that the death of
    > a member will result in the position being declared vacant, either. Nor
    > are there any rules that say what documentation would be required to
    > establish that someone had died.

    > At some point we have to allow a sliver of common sense to intervene so
    > people can do reasonable things to solve problems.

Exactly.

I'm really boggled at the amount of time and energy which has been wasted
arguing about this point. Don't we have better things to spend our time on?

It's pretty clear he's checked out, and needs to be replaced. We ought to
focus on the most economical way to achieve that purely bureacratic action.

	Noel

From barryleiba.mailing.lists@gmail.com  Thu Oct 25 06:20:25 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 64E2821F8A33 for <ietf@ietfa.amsl.com>; Thu, 25 Oct 2012 06:20:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.09
X-Spam-Level: 
X-Spam-Status: No, score=-103.09 tagged_above=-999 required=5 tests=[AWL=-0.114, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ShkIe3PWIT5e for <ietf@ietfa.amsl.com>; Thu, 25 Oct 2012 06:20:24 -0700 (PDT)
Received: from mail-la0-f44.google.com (mail-la0-f44.google.com [209.85.215.44]) by ietfa.amsl.com (Postfix) with ESMTP id 88ADC21F8789 for <ietf@ietf.org>; Thu, 25 Oct 2012 06:20:24 -0700 (PDT)
Received: by mail-la0-f44.google.com with SMTP id b11so1656313lam.31 for <ietf@ietf.org>; Thu, 25 Oct 2012 06:20:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=QsCwHSX+JaPMyPnUHII4FK45FuxKXNyEdrYMFDwJD6g=; b=yZuUOkNOtqBNOT+BODPB/6pNnjk4AopvO4yRCQKAcOMuURE2GvSMEBLAt6TcY1s6ic zwFzibX+GIhD6thUQL3QIWAnOLqKuP7GETxoe9YKskM08NgKexBpSTKYKwmZMCsYrOFb XjDYuaW9g4Ark2um64jPmBXJtW7SH1yETv5/56t1pbcXZ+GdBXHfOX0nBvvStczFc37X 9YTMkdijLWE+CHBcqBOuUIRL44UL0Qf5iuEIlQ9GjaSy5RGfxWdKbhCXgjUz0syZ829v 5BsLl4Ih3fETr1Up7PKD/HZMpeX5/OS2Zff0W74zR09053cLl3j2JD8zEFx696mDZZqs ZaGw==
MIME-Version: 1.0
Received: by 10.112.87.167 with SMTP id az7mr7965965lbb.47.1351171223455; Thu, 25 Oct 2012 06:20:23 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.112.99.131 with HTTP; Thu, 25 Oct 2012 06:20:23 -0700 (PDT)
In-Reply-To: <20121025125351.285D818C0A0@mercury.lcs.mit.edu>
References: <20121025125351.285D818C0A0@mercury.lcs.mit.edu>
Date: Thu, 25 Oct 2012 09:20:23 -0400
X-Google-Sender-Auth: 7KaRDd-UmrHZL47cp9Gkt6eE9jE
Message-ID: <CAC4RtVAhAsLxkaOOFvW5BnSSxYzbR_bfppgSGtm_ocvO0oqycA@mail.gmail.com>
Subject: Re: don't overthink, was Just so I'm clear
From: Barry Leiba <barryleiba@computer.org>
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Content-Type: multipart/alternative; boundary=f46d0401f96dce0a4104cce210e5
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, 25 Oct 2012 13:20:25 -0000

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

>
> We're all agreed that the IETF in plenary mode (i.e. all of us) can change
> any/all policy/procedures, right?

...

> So if people all hum to OK all that, it has _just as much legitimacy_ as
> _any other policy/procedure set into place by the IETF in plenary mode_.
>

Alas, that's not how we do things.  We have a process, and we need to
follow it.  Anything else does NOT have legitimacy.

I suggest that

- the authors of  draft-ietf-genarea-bcp10upd post an -01 version TODAY,
incorporating comments received so far.

- Russ, as Gen AD, immediately issue a formal (4 week) last call on that
version.

- The document be put on he 29 November IESG telechat for approval.

If we do that, unless something odd happens we will have this process
update formally approved BY OUR PROCESS in five weeks.

Barry

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

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">We&#39;re all agreed that the IETF in plenar=
y mode (i.e. all of us) can change<br>
any/all policy/procedures, right?</blockquote><div>...=A0</div><blockquote =
class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid=
;padding-left:1ex">So if people all hum to OK all that, it has _just as muc=
h legitimacy_ as<br>

_any other policy/procedure set into place by the IETF in plenary mode_.<br=
>
</blockquote><div><br></div><div>Alas, that&#39;s not how we do things. =A0=
We have a process, and we need to follow it. =A0Anything else does NOT have=
 legitimacy.</div><div><br></div><div dir=3D"ltr">I suggest that</div><div =
dir=3D"ltr">
<br></div><div dir=3D"ltr">- the authors of =A0<span style=3D"font-family:H=
elvetica;font-size:15px;white-space:nowrap">draft-ietf-genarea-bcp10upd pos=
t an -01 version TODAY, incorporating comments received so far.<span></span=
></span></div>
<div dir=3D"ltr"><span style=3D"font-family:Helvetica;font-size:15px;white-=
space:nowrap"><br></span></div><div dir=3D"ltr"><span style=3D"font-family:=
Helvetica;font-size:15px;white-space:nowrap">- Russ, as Gen AD, immediately=
 issue a formal (4 week) last call on that version.</span></div>
<div dir=3D"ltr"><span style=3D"font-family:Helvetica;font-size:15px;white-=
space:nowrap"><br></span></div><div dir=3D"ltr"><span style=3D"font-family:=
Helvetica;font-size:15px;white-space:nowrap">- The document be put on he 29=
 November IESG telechat for approval.</span></div>
<div dir=3D"ltr"><span style=3D"font-family:Helvetica;font-size:15px;white-=
space:nowrap"><br></span></div><div dir=3D"ltr"><font face=3D"Helvetica"><s=
pan style=3D"font-size:15px;white-space:nowrap">If we do that, unless somet=
hing odd happens we will have this process update formally approved BY OUR =
PROCESS in five weeks.</span></font></div>
<div dir=3D"ltr"><font face=3D"Helvetica"><span style=3D"font-size:15px;whi=
te-space:nowrap"><br></span></font></div><div dir=3D"ltr"><font face=3D"Hel=
vetica"><span style=3D"font-size:15px;white-space:nowrap">Barry</span></fon=
t></div>
<div dir=3D"ltr"><font face=3D"Helvetica"><span style=3D"font-size:15px;whi=
te-space:nowrap"><br></span></font></div>

--f46d0401f96dce0a4104cce210e5--

From barryleiba.mailing.lists@gmail.com  Thu Oct 25 06:23:40 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 9C62A21F8A55 for <ietf@ietfa.amsl.com>; Thu, 25 Oct 2012 06:23:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.089
X-Spam-Level: 
X-Spam-Status: No, score=-103.089 tagged_above=-999 required=5 tests=[AWL=-0.113, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PyoFUCBWdHbn for <ietf@ietfa.amsl.com>; Thu, 25 Oct 2012 06:23:40 -0700 (PDT)
Received: from mail-la0-f44.google.com (mail-la0-f44.google.com [209.85.215.44]) by ietfa.amsl.com (Postfix) with ESMTP id 11CC321F8A50 for <ietf@ietf.org>; Thu, 25 Oct 2012 06:23:38 -0700 (PDT)
Received: by mail-la0-f44.google.com with SMTP id b11so1661038lam.31 for <ietf@ietf.org>; Thu, 25 Oct 2012 06:23:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=6Uhj82+qCTozsKDx8XSDXhTa2CaqZUpBhnhg7ZpyhnM=; b=Ipx2GoOFUkexEg0m/8Jj5TXZdh5+nd/kSNfaKoIG/kD0ucAqPQQGWmgko4UeQFsFjx hTzdqCwWTlOi6tFFW9DXLB/mo/I29jID6YxFmUcQCybX5dNKbSsIMGfNqR7LCF9DNSor CUw/0mWGjlPXIihK8FtVZnspWsUkqNljKX4HWitnmIeBD4yCAysS99Nyj7SL25mRPfLj BuhiCn9BX/cMhrNWZuUV73CL9BeAu8laJzDugqlmRb49dd5XilDm/QuSV4WkXSRUh2g6 QMmh7KIhWRIrdf5cC/gbMibMmM/iYWxtn5SIAgF1FOTpjMn2VRTNVHyqqXSwPY5O8qFJ zwHw==
MIME-Version: 1.0
Received: by 10.112.103.7 with SMTP id fs7mr7729396lbb.25.1351171417141; Thu, 25 Oct 2012 06:23:37 -0700 (PDT)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.112.99.131 with HTTP; Thu, 25 Oct 2012 06:23:37 -0700 (PDT)
In-Reply-To: <D90D92A7-0906-4620-93A0-D116D15A10FA@gmail.com>
References: <D90D92A7-0906-4620-93A0-D116D15A10FA@gmail.com>
Date: Thu, 25 Oct 2012 09:23:37 -0400
X-Google-Sender-Auth: VRruWojrWz3vzG8FKw195buCsPI
Message-ID: <CAC4RtVAj5MV3uZN02b0DECes+MZaA6681D46aN5z5XaMDnoWAg@mail.gmail.com>
Subject: Re: [RFC 3777 Update for Vacancies]
From: Barry Leiba <barryleiba@computer.org>
To: Bob Hinden <bob.hinden@gmail.com>
Content-Type: multipart/alternative; boundary=f46d0401fea559729904cce21c31
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, 25 Oct 2012 13:23:40 -0000

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

Bob, Russ... repeating here what I said in the other thread, I suggest
that...

- the authors of  draft-ietf-genarea-bcp10upd post an -01 version TODAY,
incorporating comments received so far,

- Russ, as Gen AD, immediately issue a formal (4 week) last call on that
version, and

- the document be put on he 29 November IESG telechat for approval.

If we do that, unless something odd happens we will have this process
update formally approved BY OUR PROCESS in five weeks.

Let's please not delay.

Barry

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

Bob, Russ... repeating here what I said in the other thread, I suggest that=
...<div><br></div><div><div dir=3D"ltr"><font><span style=3D"line-height:no=
rmal;background-color:rgba(255,255,255,0)">- the authors of =A0draft-ietf-g=
enarea-bcp10upd post an -01 version TODAY, incorporating comments received =
so far,</span></font></div>
<div dir=3D"ltr"><font><span style=3D"line-height:normal;background-color:r=
gba(255,255,255,0)"><br></span></font></div><div dir=3D"ltr"><font><span st=
yle=3D"line-height:normal;background-color:rgba(255,255,255,0)">- Russ, as =
Gen AD, immediately issue a formal (4 week) last call on that version, and<=
/span></font></div>
<div dir=3D"ltr"><font><span style=3D"line-height:normal;background-color:r=
gba(255,255,255,0)"><br></span></font></div><div dir=3D"ltr"><font><span st=
yle=3D"line-height:normal;background-color:rgba(255,255,255,0)">- the docum=
ent be put on he 29 November IESG telechat for approval.</span></font></div=
>
<div dir=3D"ltr"><font><span style=3D"line-height:normal;background-color:r=
gba(255,255,255,0)"><br></span></font></div><div dir=3D"ltr"><font style=3D=
"line-height:normal;background-color:rgba(255,255,255,0)">If we do that, un=
less something odd happens we will have this process update formally approv=
ed BY OUR PROCESS in five weeks.</font></div>
</div><div dir=3D"ltr"><font style=3D"line-height:normal;background-color:r=
gba(255,255,255,0)"><br></font></div><div dir=3D"ltr"><font style=3D"line-h=
eight:normal;background-color:rgba(255,255,255,0)">Let&#39;s please not del=
ay.<span></span></font></div>
<div dir=3D"ltr"><font style=3D"line-height:normal;background-color:rgba(25=
5,255,255,0)"><br></font></div><div dir=3D"ltr"><font style=3D"line-height:=
normal;background-color:rgba(255,255,255,0)">Barry</font></div>

--f46d0401fea559729904cce21c31--

From jnc@mercury.lcs.mit.edu  Thu Oct 25 06:28:40 2012
Return-Path: <jnc@mercury.lcs.mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6473621F87A2 for <ietf@ietfa.amsl.com>; Thu, 25 Oct 2012 06:28:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.455
X-Spam-Level: 
X-Spam-Status: No, score=-6.455 tagged_above=-999 required=5 tests=[AWL=0.144,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lE4XAZdCG2YJ for <ietf@ietfa.amsl.com>; Thu, 25 Oct 2012 06:28:39 -0700 (PDT)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id DC8EA21F892C for <ietf@ietf.org>; Thu, 25 Oct 2012 06:28:39 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 1D88118C0A0; Thu, 25 Oct 2012 09:28:39 -0400 (EDT)
To: ietf@ietf.org
Subject: Re: don't overthink, was Just so I'm clear
Message-Id: <20121025132839.1D88118C0A0@mercury.lcs.mit.edu>
Date: Thu, 25 Oct 2012 09:28:39 -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, 25 Oct 2012 13:28:40 -0000

    > From: Barry Leiba <barryleiba@computer.org>

    >> We're all agreed that the IETF in plenary mode (i.e. all of us) can
    >> change any/all policy/procedures, right?

    > Alas, that's not how we do things. 

Wrong. That's exactly how we do things. Any piece of electronic paper you
point to to argue otherwise was adopted in exactly that manner.

	Noel

From adrian@olddog.co.uk  Thu Oct 25 07:37:43 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 6DB3021F89E0 for <ietf@ietfa.amsl.com>; Thu, 25 Oct 2012 07:37:43 -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.082,  BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id soKVhYKw-0gM for <ietf@ietfa.amsl.com>; Thu, 25 Oct 2012 07:37:42 -0700 (PDT)
Received: from asmtp5.iomartmail.com (asmtp5.iomartmail.com [62.128.201.176]) by ietfa.amsl.com (Postfix) with ESMTP id 0442321F89DF for <ietf@ietf.org>; Thu, 25 Oct 2012 07:37:41 -0700 (PDT)
Received: from asmtp5.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id q9PEbXYA007235;  Thu, 25 Oct 2012 15:37:33 +0100
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id q9PEbWLf007207 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 25 Oct 2012 15:37:32 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Barry Leiba'" <barryleiba@computer.org>
References: <20121025125351.285D818C0A0@mercury.lcs.mit.edu> <CAC4RtVAhAsLxkaOOFvW5BnSSxYzbR_bfppgSGtm_ocvO0oqycA@mail.gmail.com>
In-Reply-To: <CAC4RtVAhAsLxkaOOFvW5BnSSxYzbR_bfppgSGtm_ocvO0oqycA@mail.gmail.com>
Subject: RE: don't overthink, was Just so I'm clear
Date: Thu, 25 Oct 2012 15:37:29 +0100
Message-ID: <14b501cdb2be$43301f50$c9905df0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_14B6_01CDB2C6.A509E410"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQJm/12SxATP88AG50E/SnxaWoM8YQHpv+JflogvO9A=
Content-Language: en-gb
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Oct 2012 14:37:43 -0000

This is a multipart message in MIME format.

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

Barry,
 
If you believe that a change to process is necessary to make a ruling on
absentee-ism, then you will also (on reflection) believe that process changes
cannot be made retro-active.
 
So, rushing this through (I do not mean to be pejorative in my use of "rushing")
will not actually help the current situation.
 
Cheers,
Adrian
 
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of Barry
Leiba
Sent: 25 October 2012 14:20
To: Noel Chiappa
Cc: ietf@ietf.org
Subject: Re: don't overthink, was Just so I'm clear
 
We're all agreed that the IETF in plenary mode (i.e. all of us) can change
any/all policy/procedures, right?
... 
So if people all hum to OK all that, it has _just as much legitimacy_ as
_any other policy/procedure set into place by the IETF in plenary mode_.
 
Alas, that's not how we do things.  We have a process, and we need to follow it.
Anything else does NOT have legitimacy.
 
I suggest that
 
- the authors of  draft-ietf-genarea-bcp10upd post an -01 version TODAY,
incorporating comments received so far.
 
- Russ, as Gen AD, immediately issue a formal (4 week) last call on that
version.
 
- The document be put on he 29 November IESG telechat for approval.
 
If we do that, unless something odd happens we will have this process update
formally approved BY OUR PROCESS in five weeks.
 
Barry
 

------=_NextPart_000_14B6_01CDB2C6.A509E410
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=3DProgId content=3DWord.Document><meta =
name=3DGenerator content=3D"Microsoft Word 14"><meta name=3DOriginator =
content=3D"Microsoft Word 14"><link rel=3DFile-List =
href=3D"cid:filelist.xml@01CDB2C6.A31259D0"><!--[if gte mso 9]><xml>
<o:OfficeDocumentSettings>
<o:AllowPNG/>
</o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
<w:WordDocument>
<w:SpellingState>Clean</w:SpellingState>
<w:TrackMoves/>
<w:TrackFormatting/>
<w:EnvelopeVis/>
<w:ValidateAgainstSchemas/>
<w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>
<w:IgnoreMixedContent>false</w:IgnoreMixedContent>
<w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>
<w:DoNotPromoteQF/>
<w:LidThemeOther>EN-GB</w:LidThemeOther>
<w:LidThemeAsian>X-NONE</w:LidThemeAsian>
<w:LidThemeComplexScript>X-NONE</w:LidThemeComplexScript>
<w:Compatibility>
<w:DoNotExpandShiftReturn/>
<w:BreakWrappedTables/>
<w:SnapToGridInCell/>
<w:WrapTextWithPunct/>
<w:UseAsianBreakRules/>
<w:DontGrowAutofit/>
<w:SplitPgBreakAndParaMark/>
<w:EnableOpenTypeKerning/>
<w:DontFlipMirrorIndents/>
<w:OverrideTableStyleHps/>
</w:Compatibility>
<m:mathPr>
<m:mathFont m:val=3D"Cambria Math"/>
<m:brkBin m:val=3D"before"/>
<m:brkBinSub m:val=3D"&#45;-"/>
<m:smallFrac m:val=3D"off"/>
<m:dispDef/>
<m:lMargin m:val=3D"0"/>
<m:rMargin m:val=3D"0"/>
<m:defJc m:val=3D"centerGroup"/>
<m:wrapIndent m:val=3D"1440"/>
<m:intLim m:val=3D"subSup"/>
<m:naryLim m:val=3D"undOvr"/>
</m:mathPr></w:WordDocument>
</xml><![endif]--><!--[if gte mso 9]><xml>
<w:LatentStyles DefLockedState=3D"false" DefUnhideWhenUsed=3D"true" =
DefSemiHidden=3D"true" DefQFormat=3D"false" DefPriority=3D"99" =
LatentStyleCount=3D"267">
<w:LsdException Locked=3D"false" Priority=3D"0" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Normal"/>
<w:LsdException Locked=3D"false" Priority=3D"9" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"heading 1"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 2"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 3"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 4"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 5"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 6"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 7"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 8"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" =
Name=3D"heading 9"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 1"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 2"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 3"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 4"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 5"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 6"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 7"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 8"/>
<w:LsdException Locked=3D"false" Priority=3D"39" Name=3D"toc 9"/>
<w:LsdException Locked=3D"false" Priority=3D"35" QFormat=3D"true" =
Name=3D"caption"/>
<w:LsdException Locked=3D"false" Priority=3D"10" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Title"/>
<w:LsdException Locked=3D"false" Priority=3D"1" Name=3D"Default =
Paragraph Font"/>
<w:LsdException Locked=3D"false" Priority=3D"11" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtitle"/>
<w:LsdException Locked=3D"false" Priority=3D"22" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Strong"/>
<w:LsdException Locked=3D"false" Priority=3D"20" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Emphasis"/>
<w:LsdException Locked=3D"false" Priority=3D"59" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Table Grid"/>
<w:LsdException Locked=3D"false" UnhideWhenUsed=3D"false" =
Name=3D"Placeholder Text"/>
<w:LsdException Locked=3D"false" Priority=3D"1" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"No Spacing"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 1"/>
<w:LsdException Locked=3D"false" UnhideWhenUsed=3D"false" =
Name=3D"Revision"/>
<w:LsdException Locked=3D"false" Priority=3D"34" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"List Paragraph"/>
<w:LsdException Locked=3D"false" Priority=3D"29" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Quote"/>
<w:LsdException Locked=3D"false" Priority=3D"30" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Quote"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"60" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Shading Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"61" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light List Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"62" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Light Grid Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"63" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 1 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"64" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Shading 2 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"65" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 1 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"66" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium List 2 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"67" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 1 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"68" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 2 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"69" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Medium Grid 3 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"70" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Dark List Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"71" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Shading Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"72" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful List Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"73" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" Name=3D"Colorful Grid Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"19" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtle Emphasis"/>
<w:LsdException Locked=3D"false" Priority=3D"21" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Emphasis"/>
<w:LsdException Locked=3D"false" Priority=3D"31" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Subtle Reference"/>
<w:LsdException Locked=3D"false" Priority=3D"32" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Intense Reference"/>
<w:LsdException Locked=3D"false" Priority=3D"33" SemiHidden=3D"false" =
UnhideWhenUsed=3D"false" QFormat=3D"true" Name=3D"Book Title"/>
<w:LsdException Locked=3D"false" Priority=3D"37" Name=3D"Bibliography"/>
<w:LsdException Locked=3D"false" Priority=3D"39" QFormat=3D"true" =
Name=3D"TOC Heading"/>
</w:LatentStyles>
</xml><![endif]--><style><!--
/* Font Definitions */
@font-face
	{font-family:Helvetica;
	panose-1:2 11 6 4 2 2 2 2 2 4;
	mso-font-charset:0;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:-536859905 -1073711037 9 0 511 0;}
@font-face
	{font-family:Helvetica;
	panose-1:2 11 6 4 2 2 2 2 2 4;
	mso-font-charset:0;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:-536859905 -1073711037 9 0 511 0;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;
	mso-font-charset:0;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:-520092929 1073786111 9 0 415 0;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;
	mso-font-charset:0;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:-520081665 -1073717157 41 0 66047 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-unhide:no;
	mso-style-qformat:yes;
	mso-style-parent:"";
	margin:0cm;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";
	mso-fareast-font-family:Calibri;}
a:link, span.MsoHyperlink
	{mso-style-noshow:yes;
	mso-style-priority:99;
	color:blue;
	text-decoration:underline;
	text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-noshow:yes;
	mso-style-priority:99;
	color:purple;
	text-decoration:underline;
	text-underline:single;}
span.EmailStyle17
	{mso-style-type:personal-reply;
	mso-style-noshow:yes;
	mso-style-unhide:no;
	mso-ansi-font-size:11.0pt;
	mso-bidi-font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-ascii-font-family:Calibri;
	mso-fareast-font-family:Calibri;
	mso-hansi-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";
	color:#1F497D;}
span.SpellE
	{mso-style-name:"";
	mso-spl-e:yes;}
.MsoChpDefault
	{mso-style-type:export-only;
	mso-default-props:yes;
	font-family:"Calibri","sans-serif";
	mso-ascii-font-family:Calibri;
	mso-fareast-font-family:Calibri;
	mso-hansi-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";
	mso-fareast-language:EN-US;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;
	mso-header-margin:36.0pt;
	mso-footer-margin:36.0pt;
	mso-paper-source:0;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 10]><style>/* Style Definitions */
table.MsoNormalTable
	{mso-style-name:"Table Normal";
	mso-tstyle-rowband-size:0;
	mso-tstyle-colband-size:0;
	mso-style-noshow:yes;
	mso-style-priority:99;
	mso-style-parent:"";
	mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
	mso-para-margin:0cm;
	mso-para-margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-ascii-font-family:Calibri;
	mso-hansi-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";
	mso-fareast-language:EN-US;}
</style><![endif]--><!--[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-GB link=3Dblue =
vlink=3Dpurple style=3D'tab-interval:36.0pt'><div =
class=3DWordSection1><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'>Barry,<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'>If you believe that a change =
to process is necessary to make a ruling on absentee-ism, then you will =
also (on reflection) believe that process changes cannot be made =
retro-active.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'>So, rushing this through (I do =
not mean to be pejorative in my use of &quot;rushing&quot;) will not =
actually help the current situation.<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New =
Roman";color:#1F497D'>Cheers,<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New Roman";color:#1F497D'>Adrian<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";mso-bidi-fon=
t-family:"Times New =
Roman";color:#1F497D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt'><div><div style=3D'border:none;border-top:solid #B5C4DF =
1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=3DMsoNormal><b><span =
lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";mso-fareast-f=
ont-family:"Times New =
Roman";mso-ansi-language:EN-US'>From:</span></b><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";mso-fareast-f=
ont-family:"Times New Roman";mso-ansi-language:EN-US'> =
ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] <b>On Behalf Of =
</b>Barry Leiba<br><b>Sent:</b> 25 October 2012 14:20<br><b>To:</b> Noel =
Chiappa<br><b>Cc:</b> ietf@ietf.org<br><b>Subject:</b> Re: don't =
overthink, was Just so I'm clear<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><blockquote =
style=3D'border:none;border-left:solid #CCCCCC =
1.0pt;mso-border-left-alt:solid #CCCCCC .75pt;padding:0cm 0cm 0cm =
6.0pt;margin-left:4.8pt;margin-right:0cm'><p class=3DMsoNormal>We're all =
agreed that the IETF in plenary mode (i.e. all of us) can =
change<br>any/all policy/procedures, =
right?<o:p></o:p></p></blockquote><div><p =
class=3DMsoNormal>...&nbsp;<o:p></o:p></p></div><blockquote =
style=3D'border:none;border-left:solid #CCCCCC =
1.0pt;mso-border-left-alt:solid #CCCCCC .75pt;padding:0cm 0cm 0cm =
6.0pt;margin-left:4.8pt;margin-right:0cm'><p class=3DMsoNormal>So if =
people all hum to OK all that, it has _just as much legitimacy_ =
as<br>_any other policy/procedure set into place by the IETF in plenary =
mode_.<o:p></o:p></p></blockquote><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>Alas, that's not how we do things. &nbsp;We have a =
process, and we need to follow it. &nbsp;Anything else does NOT have =
legitimacy.<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>I =
suggest that<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>- =
the authors of &nbsp;<span =
style=3D'font-size:11.5pt;font-family:"Helvetica","sans-serif"'>draft-iet=
f-genarea-bcp10upd post an -01 version TODAY, incorporating comments =
received so far.</span><o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal><span =
style=3D'font-size:11.5pt;font-family:"Helvetica","sans-serif"'>- Russ, =
as Gen AD, immediately issue a formal (4 week) last call on that =
version.</span><o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal><span =
style=3D'font-size:11.5pt;font-family:"Helvetica","sans-serif"'>- The =
document be put on he 29 November IESG telechat for =
approval.</span><o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal><span =
style=3D'font-size:11.5pt;font-family:"Helvetica","sans-serif"'>If we do =
that, unless something odd happens we will have this process update =
formally approved BY OUR PROCESS in five =
weeks.</span><o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal><span =
style=3D'font-size:11.5pt;font-family:"Helvetica","sans-serif"'>Barry</sp=
an><o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></div></div></body></html>
------=_NextPart_000_14B6_01CDB2C6.A509E410--


From john-ietf@jck.com  Thu Oct 25 08:03:48 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 7046B21F8F9E for <ietf@ietfa.amsl.com>; Thu, 25 Oct 2012 08:03:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.529
X-Spam-Level: 
X-Spam-Status: No, score=-103.529 tagged_above=-999 required=5 tests=[AWL=1.070, BAYES_00=-2.599, GB_I_LETTER=-2, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4Bwahy5Npx6X for <ietf@ietfa.amsl.com>; Thu, 25 Oct 2012 08:03:37 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id B73EA21F8F9A for <ietf@ietf.org>; Thu, 25 Oct 2012 08:03:37 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1TROy3-000EeE-9h; Thu, 25 Oct 2012 11:03:31 -0400
Date: Thu, 25 Oct 2012 11:03:26 -0400
From: John C Klensin <john-ietf@jck.com>
To: Barry Leiba <barryleiba@computer.org>, Bob Hinden <bob.hinden@gmail.com>
Subject: Hasty procedural changes (was: Re: [RFC 3777 Update for Vacancies])
Message-ID: <58AF646D478492278E715428@JcK-HP8200.jck.com>
In-Reply-To: <CAC4RtVAj5MV3uZN02b0DECes+MZaA6681D46aN5z5XaMDnoWAg@mail.gmail.com>
References: <D90D92A7-0906-4620-93A0-D116D15A10FA@gmail.com> <CAC4RtVAj5MV3uZN02b0DECes+MZaA6681D46aN5z5XaMDnoWAg@mail.gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Oct 2012 15:03:48 -0000

--On Thapparently-strongly-held ursday, October 25, 2012 09:23
-0400 Barry Leiba <barryleiba@computer.org> wrote:

> Bob, Russ... repeating here what I said in the other thread, I
> suggest that...
> 
> - the authors of  draft-ietf-genarea-bcp10upd post an -01
> version TODAY, incorporating comments received so far,
> 
> - Russ, as Gen AD, immediately issue a formal (4 week) last
> call on that version, and
> 
> - the document be put on he 29 November IESG telechat for
> approval.
> 
> If we do that, unless something odd happens we will have this
> process update formally approved BY OUR PROCESS in five weeks.
> 
> Let's please not delay.

Barry,

I really, strongly, object to this way of proceeding.   Making
fundamental procedural changes in haste and in the middle of a
perceived crisis is never a good idea for any organization.  My
experience leads me to believe that IETF is even less good at it
than average, but, even if your experience differs, it still
isn't a good idea.  Doing it right now is particularly bad
because, despite the many postings on the list, a significant
fraction of the community is (and should be) focused on
preparation for the technical work of the IETF meeting or on
clearing up other work so that they can attend, not on
discussion of a procedural change that appeared in a late-posted
draft.   A four-week Last Call offers some protection against
that but maybe not enough (I note that the IESG has often
required longer-than-minimum Last Call periods when the Last
Call spans IETF meetings and/or major holidays).

In addition, making a procedural change to deal, effectively
retroactively, with a problem that is already in progress simply
has a bad, ex post facto, odor about it, an odor I believe we
should not ignore.

Let's deal with the matter at hand and the associated perceived
emergency and then, after the dust has settled, go back and
review procedures.  If you want a more pragmatic argument than
the "bad idea to rush through a procedure change" one above,
consider that your desired fast schedule could be entirely
derailed by _one_ member of the community waiting until the IESG
votes and then lodging an appeal whose substance is that, if the
IESG can change procedures in this way to change the rules as
applied to a particular situation, especially one related to a
personnel matter, that predated the change, it makes fairness
impossible.  

While I disagree with most of them, I've seen enough comments on
the list to the effect that, if recall is the only option we
have, we need to use it -- comments based on principles that are
apparently strongly-held by those making them-- to believe that
such an appeal is not entirely unplausible**.  (And my apologies
if I'm giving anyone ideas they didn't have already.)

So let's solve the present problem using good sense and the
tools at hand.  

>From my personal point of view, either of the following would be
rational, consistent with good sense, and just about as fast as
your proposal:

(i) If the IAOC is unanimously (obviously less Marshall)
convinced that everything plausibly possible has been done to
try to get a response from Marshall and that that there is no
reasonable possibility that he is unaware of the situation, then
a conclusion that he has resigned by his silence would seem to
be in order.  Personally, I'd like to see that in a resolution
in which the steps taken are reviewed, the unanimity is
recorded, and the resignation is noted.  I'd prefer to see that
resignation noted as "presumably for personal reasons" as well,
rather than "deeming the position vacant" because I would prefer
that we not hint at anger at Marshall in the record.  But, if
those distinctions are too subtle for the IAOC. so be it.

(ii) The IESG could use its implied authority to interpret RFC
2026 (an authority it has at least implicitly applied many times
in the past).  It could interpret the 2026 variance procedure as
applying to all bodies to which 2026 applies, whether they were
created earlier enough to be enumerated in 2026 or not.  (FWIW,
I personally believe that interpretation would be correct
relative to the intentions 16 years ago.)  That procedure could
then be used to treat the current situation as a resignation
without creating any unfortunate precedents.

While either of those approaches could be appealed as well, it
would be far harder to create a plausible claim of unfairness
in/to the community.  Indeed, it might be that only Marshall or
someone plausibly acting on his behalf, could reasonably appeal
and, if that were to occur, the real problem of non-response
would presumably disappear. 

I think other approaches are plausible too.  I hope we can avoid
the recall procedure, not because it would take a long time but
because it involves a level of condemnation of Marshall that I
believe that, in the light of past contributions, we should
bypass if possible.   Given the number of years we have gone
without ever exercising the recall procedure, I'd rather reserve
"first person ever recalled" for someone who has misbehaved in
some rather nasty way and I'm not convinced that Marshall
qualifies.  But even it would be better than trying to make a
significant and permanent procedural change on a "let's see if
we can do it before the end of November and then retroactively
apply it to this problem" basis.

best,
   john

** I've used "plausible", "rational", and their synonyms several
times in this note to stress the principle that the IETF should
continue to favor good sense and consensus over rigid rules and
their more rigid consideration.  If we cannot continue to do
that, I believe we are lost because our procedures are not
nearly good enough (or updated carefully enough every time
something changes) to sustain a rigid adherence to the letter of
the rules and nothing else.


From annevankesteren@gmail.com  Thu Oct 25 06:54:47 2012
Return-Path: <annevankesteren@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4F28321F89BB for <ietf@ietfa.amsl.com>; Thu, 25 Oct 2012 06:54:46 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rc+ZeAWPifv0 for <ietf@ietfa.amsl.com>; Thu, 25 Oct 2012 06:54:45 -0700 (PDT)
Received: from mail-wi0-f170.google.com (mail-wi0-f170.google.com [209.85.212.170]) by ietfa.amsl.com (Postfix) with ESMTP id 0C38021F896B for <ietf@ietf.org>; Thu, 25 Oct 2012 06:54:44 -0700 (PDT)
Received: by mail-wi0-f170.google.com with SMTP id hm2so5310876wib.1 for <ietf@ietf.org>; Thu, 25 Oct 2012 06:54:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=HmF4RNLGlcNtxBzibQRIwfKv47h9cWbZGU2aX5S0F9A=; b=IEOd6d+ERxYvg+cz1UFOE6safQScvqew84bV2w3vjQXKl/+yh9gKKd7EvDn3A8RwxL VRsoe9Af6hgHyixRUofc6bEk2V02cRE4echToYW32UaKUyl7wzFzRB9zRqpoFZ1xBtgd EKmhjWt+f5L2x5ZD4wB1npla+TztzFKNcRorLa2Z4hUxKlWkEYktOXKdHPqRwazzrZA4 bv9TTeVFhc+/NSpotVkcNd+3x602/+0yyAtGdcC4f143ry30ICi5tZROnB3p21AeE1c3 Vz13I1+KQTfuSe9iICjZrK5mUedLQmkjWDj32Pe4fvdrjxVwHJUN10r1n9ljG6naM7H0 kibA==
MIME-Version: 1.0
Received: by 10.180.75.161 with SMTP id d1mr14025657wiw.19.1351173283906; Thu, 25 Oct 2012 06:54:43 -0700 (PDT)
Sender: annevankesteren@gmail.com
Received: by 10.223.145.195 with HTTP; Thu, 25 Oct 2012 06:54:43 -0700 (PDT)
In-Reply-To: <CAAWM5TzjsxOWB4pL3XaWAa5zDdsZb=1-jOZ2JM9L9hbPtd7azA@mail.gmail.com>
References: <50604C1A.7090901@gmx.de> <5060A964.5060001@stpeter.im> <Pine.LNX.4.64.1210172354500.2478@ps20323.dreamhostps.com> <507F5A7E.6040206@arcanedomain.com> <50856E3C.103@gmail.com> <Pine.LNX.4.64.1210221753010.2471@ps20323.dreamhostps.com> <0DBC8A11-319C-4120-975E-7E40FD5818BF@gbiv.com> <Pine.LNX.4.64.1210222137530.2471@ps20323.dreamhostps.com> <CA+9kkMDpEZCvcG1DJd=O1qPNV+=+GTBeN+CGndUe51Xym_A9sg@mail.gmail.com> <Pine.LNX.4.64.1210232115210.2471@ps20323.dreamhostps.com> <15E1D98B-8883-4936-81A9-174E1323683C@nordsc.com> <CAGKvQ5ZV6_GMVgjEezhR-oKqSikxR7GYgacMitbfczmNh725mw@mail.gmail.com> <Pine.LNX.4.64.1210232348110.2471@ps20323.dreamhostps.com> <CAAWM5Tz3NdprjqwgyoVoV9qUuiwXb2gTQ49u4a4ePGfjyusDkw@mail.gmail.com> <Pine.LNX.4.64.1210240451150.2471@ps20323.dreamhostps.com> <CAAWM5TzjsxOWB4pL3XaWAa5zDdsZb=1-jOZ2JM9L9hbPtd7azA@mail.gmail.com>
Date: Thu, 25 Oct 2012 15:54:43 +0200
X-Google-Sender-Auth: NHcYPtUlCJd75vV_2zCG2xl2Xt8
Message-ID: <CADnb78ikWsuWyx-QCvvHkvUs0N0FQChBybdVQyJpkxQKrYcC4A@mail.gmail.com>
Subject: Re: [whatwg] New URL Standard from Anne van Kesteren on 2012-09-24 (public-whatwg-archive@w3.org from September 2012)
From: Anne van Kesteren <annevk@annevk.nl>
To: David Sheets <kosmo.zb@gmail.com>
Content-Type: text/plain; charset=UTF-8
X-Mailman-Approved-At: Thu, 25 Oct 2012 08:05:16 -0700
Cc: Ted Hardie <ted.ietf@gmail.com>, IETF Discussion <ietf@ietf.org>, Ian Hickson <ian@hixie.ch>, Christophe Lauret <clauret@weborganic.com>, Jan Algermissen <jan.algermissen@nordsc.com>, URI <uri@w3.org>, "Manger, James H" <James.H.Manger@team.telstra.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, 25 Oct 2012 13:54:47 -0000

On Thu, Oct 25, 2012 at 5:37 AM, David Sheets <kosmo.zb@gmail.com> wrote:
> On Tue, Oct 23, 2012 at 10:05 PM, Ian Hickson <ian@hixie.ch> wrote:
>> No, Anne hasn't finished defining conformance yet. (He just started
>> today.)
>
> This is a political dodge to delay the inevitable discussion of
> address space expansion.
>
> From what I have read of WHATWG's intentions and discussed with you
> and others, you are codifying current browser behavior for
> 'interoperability'. Current browsers happily consume and emit URIs
> that are invalid per STD 66.

Correct, that does not mean valid input is similarly relaxed. That is
also not the case for HTML for example. Literally anything produces a
tree of sorts, but far from all input is considered valid.


> <http://url.spec.whatwg.org/#writing> presently says:
> "A fragment is "#", followed by any URL unit that is not one of
> U+0009, U+000A, and U+000D."
> This is larger than STD 66's space of valid addresses.

I aligned it with IRI now, apart from private Unicode ranges. Not
really sure why we should ban them in one place and not in another.


We discussed how to write the algorithms on the WHATWG list before and
again I challenge you to write out your approach and convince the
world it's better. I'm not interested in doing that work for you.


-- 
http://annevankesteren.nl/

From alh-ietf@tndh.net  Thu Oct 25 08:08:16 2012
Return-Path: <alh-ietf@tndh.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DCEC021F90D8 for <ietf@ietfa.amsl.com>; Thu, 25 Oct 2012 08:08:16 -0700 (PDT)
X-Quarantine-ID: <yIdT01+IPvsq>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Improper folded header field made up entirely of whitespace (char 20 hex): X-Spam-Report: ...that system for details.\n \n Content previ[...]
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yIdT01+IPvsq for <ietf@ietfa.amsl.com>; Thu, 25 Oct 2012 08:08:16 -0700 (PDT)
Received: from express.tndh.net (express.tndh.net [IPv6:2001:470:e930:1240:20d:56ff:fe04:4c0a]) by ietfa.amsl.com (Postfix) with ESMTP id 351D521F9037 for <ietf@ietf.org>; Thu, 25 Oct 2012 08:08:16 -0700 (PDT)
Received: from [172.20.144.31] (helo=eaglet) by express.tndh.net with esmtp (Exim 4.72 (FreeBSD)) (envelope-from <alh-ietf@tndh.net>) id 1TRP2V-000EDL-2V; Thu, 25 Oct 2012 08:08:12 -0700
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'Brian E Carpenter'" <brian.e.carpenter@gmail.com>, "'Doug Barton'" <dougb@dougbarton.us>
References: <20121023192135.203AC18C0A4@mercury.lcs.mit.edu>	<5086EF82.9060900@dougbarton.us>	<20121023200713.GC1861@nsn.com>	<5086FBCE.2070503@dougbarton.us>	<20121023213251.GF27557@verdi>	<50873AB4.1000905@dougbarton.us>	<20121024034736.GC52558@crankycanuck.ca>	<50876D39.20502@dougbarton.us>	<508773E7.10203@cisco.com>	<50877633.1000402@dougbarton.us>	<EA9BEA2E-EE96-4E80-B719-652BBD620A79@lilacglade.org>	<508842C2.4020203@dougbarton.us> <5088EE5A.4090103@gmail.com>
In-Reply-To: <5088EE5A.4090103@gmail.com>
Subject: RE: Just so I'm clear
Date: Thu, 25 Oct 2012 08:08:07 -0700
Message-ID: <01ef01cdb2c2$8a062330$9e126990$@tndh.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Content-Language: en-us
Thread-Index: AQHh8wyhXJPu+L+ckiGZSgshdBMy0gH3avBPAb9jkuICgS4F6AI9qB72AUIb6loCmWavzgMFwvI0AiIqCvUCZdM2MgHlnrYNAhldDa4CU3itJpbQE+jQ
X-SA-Exim-Connect-IP: 172.20.144.31
X-SA-Exim-Mail-From: alh-ietf@tndh.net
X-SA-Exim-Scanned: No (on express.tndh.net); SAEximRunCond expanded to 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: Thu, 25 Oct 2012 15:08:17 -0000

Has anyone bothered to ask counsel for an opinion about the issues =
StJohns raised?

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf =
Of
> Brian E Carpenter
> Sent: Thursday, October 25, 2012 12:47 AM
> To: Doug Barton
> Cc: ietf@ietf.org
> Subject: Re: Just so I'm clear
>=20
> On 24/10/2012 20:34, Doug Barton wrote:
> ...
> > ... Nothing in the text suggests an
> > unfettered right of creating new definitions of "vacant."
>=20
> You mean, new compared to the first definition in Merriam-Webster.com?
>=20
> 1: not occupied by an incumbent, possessor, or officer <a vacant =
office>
> <vacant thrones>
>=20
> Objectively and factually, that seems to be the case. The IAOC is =
actually
> going an extra mile rather than simply informing NomCom that the seat =
has
> become vacant.
>=20
>     Brian



From john@jlc.net  Thu Oct 25 08:24:06 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 9A36921F8462 for <ietf@ietfa.amsl.com>; Thu, 25 Oct 2012 08:24:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.432
X-Spam-Level: 
X-Spam-Status: No, score=-106.432 tagged_above=-999 required=5 tests=[AWL=0.167, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 00FpVYdoi7Rn for <ietf@ietfa.amsl.com>; Thu, 25 Oct 2012 08:24:06 -0700 (PDT)
Received: from mailhost.jlc.net (mailhost.jlc.net [199.201.159.4]) by ietfa.amsl.com (Postfix) with ESMTP id 0EE3F21F8449 for <ietf@ietf.org>; Thu, 25 Oct 2012 08:24:06 -0700 (PDT)
Received: by mailhost.jlc.net (Postfix, from userid 104) id B350333C2B; Thu, 25 Oct 2012 11:24:05 -0400 (EDT)
Date: Thu, 25 Oct 2012 11:24:05 -0400
From: John Leslie <john@jlc.net>
To: John C Klensin <john-ietf@jck.com>
Subject: Re: Hasty procedural changes (was: Re: [RFC 3777 Update for Vacancies])
Message-ID: <20121025152405.GP27557@verdi>
References: <D90D92A7-0906-4620-93A0-D116D15A10FA@gmail.com> <CAC4RtVAj5MV3uZN02b0DECes+MZaA6681D46aN5z5XaMDnoWAg@mail.gmail.com> <58AF646D478492278E715428@JcK-HP8200.jck.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <58AF646D478492278E715428@JcK-HP8200.jck.com>
User-Agent: Mutt/1.4.1i
Cc: Barry Leiba <barryleiba@computer.org>, Bob Hinden <bob.hinden@gmail.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Oct 2012 15:24:06 -0000

John C Klensin <john-ietf@jck.com> wrote:
> --On Thapparently-strongly-held ursday, October 25, 2012 09:23
> -0400 Barry Leiba <barryleiba@computer.org> wrote:
>... 
>> If we do that, unless something odd happens we will have this
>> process update formally approved BY OUR PROCESS in five weeks.
>> 
>> Let's please not delay.
> 
> I really, strongly, object to this way of proceeding. Making
> fundamental procedural changes in haste and in the middle of a
> perceived crisis is never a good idea for any organization.

   I don't agree this is a "fundamental" procedural change. Barry
would like to start a four-week last call on a procedure change
to which I haven't heard any objection -- just a lot of discussion
on whether it's needed and whether it might apply to the current
situation.

   IMHO it's needed, precisely because of the current disagreement
on this list.

   Also IMHO, it doesn't apply to the current situation. This will
either have resolved itself in five weeks or it won't. If 20 folks
petition for recall, recall procedure will be followed. If this
issue dies down with folks consenting to the NomCom filling the
vacancy, it will be filled.

   If, OTOH, in five weeks it hasn't died down, we could _start_
another four-week LastCall on whether there is a vacancy, based
on five more weeks of inactivity than we already have.

   If, during the next four weeks, further suggestions are made to
the process to be used going forward, they can be incorporated
before it's adopted.

   For myself, I'm willing to let this fester longer if it is indeed
the consensus of the IETF to let it fester. But I find Barry's
proposal entirely reasonable. (And I have to stop here, to be set up
for scribing today's IESG telechat.)

--
John Leslie <john@jlc.net>

From sm@resistor.net  Thu Oct 25 08:24:18 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 422AD21F88A9 for <ietf@ietfa.amsl.com>; Thu, 25 Oct 2012 08:24:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.588
X-Spam-Level: 
X-Spam-Status: No, score=-102.588 tagged_above=-999 required=5 tests=[AWL=0.011, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vv4sUW0JXSwk for <ietf@ietfa.amsl.com>; Thu, 25 Oct 2012 08:24:17 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 9FB3421F88D8 for <ietf@ietf.org>; Thu, 25 Oct 2012 08:24:16 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id q9PFOAIA002169; Thu, 25 Oct 2012 08:24:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1351178655; bh=bkMQd6VMZxqj7V0t+CQuhohm3rfB1sJ564pDxmP2Di4=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=JyYa4ikiTlvK5NxgIMWC56Fjl9piAwu47ulDYjf5NrJWxGjGqpn4aja3QT1eg/doE zAnqgpIwsp5iQCgDbAr18nNOyeFdMEU/r68TLfLXw5swFp3xqXy0156ir+bmhxKleO wMO5+V53Yr/FDhCLB2gSNLRO0yU1sjO5+edxhM9M=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1351178655; i=@resistor.net; bh=bkMQd6VMZxqj7V0t+CQuhohm3rfB1sJ564pDxmP2Di4=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=0TENGEMT88Tj4hZRcbF+T7BZwGMl/+ngX8McSqAO/DE5ucYpvF7Ne/VuJcySvSrZN fcJIqEzr8Mkz3Towbwthn5W1e77ZDdUFYR/k96yChPP3xPbiCYg7vIkyCfnOaSMvp8 k68O4XLLid3RqrWIJLnwDswHLlNAMhuNUJSwmu3M=
Message-Id: <6.2.5.6.2.20121025073426.09c18a38@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 25 Oct 2012 08:22:03 -0700
To: jnc@mercury.lcs.mit.edu (Noel Chiappa)
From: SM <sm@resistor.net>
Subject: Re: don't overthink, was Just so I'm clear
In-Reply-To: <20121025125351.285D818C0A0@mercury.lcs.mit.edu>
References: <20121025125351.285D818C0A0@mercury.lcs.mit.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Oct 2012 15:24:18 -0000

Hi Noel,
At 05:53 25-10-2012, Noel Chiappa wrote:
>We're all agreed that the IETF in plenary mode (i.e. all of us) can change
>any/all policy/procedures, right?

It's going to be controversial.

>So, view the original call from the IAOC as a request to the IETF, in formal
>plenary mode, to make the following policy/procedure changes/etc:
>
>- To declare that, due to an oversight on our part at the time of drafting,
>our existing policy/procedure does not handle certain cases, so we are
>_temporarily_ (see below) setting up an ad hoc procedure to handle those
>cases;
>
>- That said temporary ad hoc procedure is to have the IETF in plenary mode
>decide/declare that positions are vacant due to the withdrawal of the holder.

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

>The call also make the following procedural request:
>
>- That, following that temporary ad hoc procedure, in the particular case in
>the original call, the holder be declared to have vacated, due to his long
>lack of communication, despite _extensive_ attempts to contact him.
>
>So if people all hum to OK all that, it has _just as much legitimacy_ as
>_any other policy/procedure set into place by the IETF in plenary mode_.

Julian Reschke mentioned the following [1] on an unrelated thread:

   "The IETF is open to anyone, works async on mailing lists, and doesn't
    require any membership fees. I don't think there's any standards body
    that is *more* open to individuals."

I would add the word "fair" to the above.

>It's pretty clear he's checked out, and needs to be replaced. We ought to
>focus on the most economical way to achieve that purely bureacratic action.

Yes.  The problem with fairness is that it can be an overhead.  Its 
advantage is a sense of legitimacy which is more than a piece of 
paper, electronic or otherwise, can do.

Regards,
-sm

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


From john-ietf@jck.com  Thu Oct 25 09:22:30 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 79B4F21F88CF for <ietf@ietfa.amsl.com>; Thu, 25 Oct 2012 09:22:30 -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.056, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ppt05R3uS0zA for <ietf@ietfa.amsl.com>; Thu, 25 Oct 2012 09:22:24 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 91BDF21F878B for <ietf@ietf.org>; Thu, 25 Oct 2012 09:22:24 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1TRQCK-000Ek5-3I; Thu, 25 Oct 2012 12:22:20 -0400
Date: Thu, 25 Oct 2012 12:22:15 -0400
From: John C Klensin <john-ietf@jck.com>
To: John Leslie <john@jlc.net>
Subject: Re: Hasty procedural changes (was: Re: [RFC 3777 Update for Vacancies])
Message-ID: <8E2BDA6663427575A089372E@JcK-HP8200.jck.com>
In-Reply-To: <20121025152405.GP27557@verdi>
References: <D90D92A7-0906-4620-93A0-D116D15A10FA@gmail.com> <CAC4RtVAj5MV3uZN02b0DECes+MZaA6681D46aN5z5XaMDnoWAg@mail.gmail.com> <58AF646D478492278E715428@JcK-HP8200.jck.com> <20121025152405.GP27557@verdi>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: Barry Leiba <barryleiba@computer.org>, Bob Hinden <bob.hinden@gmail.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Oct 2012 16:22:30 -0000

--On Thursday, October 25, 2012 11:24 -0400 John Leslie
<john@jlc.net> wrote:

>...
>> I really, strongly, object to this way of proceeding. Making
>> fundamental procedural changes in haste and in the middle of a
>> perceived crisis is never a good idea for any organization.
> 
>    I don't agree this is a "fundamental" procedural change.
> Barry would like to start a four-week last call on a procedure
> change to which I haven't heard any objection -- just a lot of
> discussion on whether it's needed and whether it might apply
> to the current situation.

John,

I'm not going to debate this and will now go back to
intermittent lurking because I've got too much other work to do
right now if I'm going to get to IETF.  However: 

-- The community has had significant experience with procedural
changes having unexpected consequences or side effects that then
have to be corrected or worked around.  I suggest that
experience implies that _any_ change to basic procedures should
be treated as fundamental and considered on that basis until the
community is satisfied that it actually covers the cases it is
intended to cover and nothing else.

-- While you may interpret "haven't heard any objection" as
agreement, I suggest that, for a late-posted draft at this time
of year, it could as easily be "silence from people whose
priorities haven't allowed sufficient opportunity to study the
proposal and comment".

best,
   john





From cabo@tzi.org  Thu Oct 25 09:57:16 2012
Return-Path: <cabo@tzi.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C267621F8920 for <ietf@ietfa.amsl.com>; Thu, 25 Oct 2012 09:57:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.225
X-Spam-Level: 
X-Spam-Status: No, score=-106.225 tagged_above=-999 required=5 tests=[AWL=0.024, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id je1cTyNnXNXA for <ietf@ietfa.amsl.com>; Thu, 25 Oct 2012 09:57:16 -0700 (PDT)
Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) by ietfa.amsl.com (Postfix) with ESMTP id F39FC21F851E for <ietf@ietf.org>; Thu, 25 Oct 2012 09:57:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.3/8.14.3) with ESMTP id q9PGv2rE003653; Thu, 25 Oct 2012 18:57:02 +0200 (CEST)
Received: from [192.168.217.105] (p54892C1E.dip.t-dialin.net [84.137.44.30]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id AC3921FB; Thu, 25 Oct 2012 18:57:01 +0200 (CEST)
Subject: Re: don't overthink, was Just so I'm clear
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Content-Type: text/plain; charset=iso-8859-1
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <14b501cdb2be$43301f50$c9905df0$@olddog.co.uk>
Date: Thu, 25 Oct 2012 18:57:00 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <9DE2CA28-1D75-4BF4-8B4C-9B0449B0D9BE@tzi.org>
References: <20121025125351.285D818C0A0@mercury.lcs.mit.edu> <CAC4RtVAhAsLxkaOOFvW5BnSSxYzbR_bfppgSGtm_ocvO0oqycA@mail.gmail.com> <14b501cdb2be$43301f50$c9905df0$@olddog.co.uk>
To: adrian@olddog.co.uk
X-Mailer: Apple Mail (2.1499)
Cc: 'Barry Leiba' <barryleiba@computer.org>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Oct 2012 16:57:16 -0000

On Oct 25, 2012, at 16:37, "Adrian Farrel" <adrian@olddog.co.uk> wrote:

> retro-active

I don't get how that is relevant.
This is for the case the seat is still vacant when the new process comes =
into force.

I'm still amazed at the number of messages the resolution of this issue =
has generated.
There is complete consensus on the needed outcome, so finding a =
procedure should mostly be a matter of consulting counsel.
(All that while showing our respect for the individual caught up in this =
situation, I should add. =20
Not one of mailing list discussions' strongest points.  And that's why =
I'm going to shut up again, now.)

Gr=FC=DFe, Carsten


From grmocg@gmail.com  Thu Oct 25 10:45:50 2012
Return-Path: <grmocg@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2E72221F889E for <ietf@ietfa.amsl.com>; Thu, 25 Oct 2012 10:45:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.105
X-Spam-Level: 
X-Spam-Status: No, score=-7.105 tagged_above=-999 required=5 tests=[AWL=-3.507, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5SgFlCXaZlRR for <ietf@ietfa.amsl.com>; Thu, 25 Oct 2012 10:45:49 -0700 (PDT)
Received: from mail-la0-f44.google.com (mail-la0-f44.google.com [209.85.215.44]) by ietfa.amsl.com (Postfix) with ESMTP id BA04E21F888D for <ietf@ietf.org>; Thu, 25 Oct 2012 10:45:48 -0700 (PDT)
Received: by mail-la0-f44.google.com with SMTP id b11so1974853lam.31 for <ietf@ietf.org>; Thu, 25 Oct 2012 10:45:47 -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=hg2lHCReEa5/yZKL7di74y0Lf2hijv2Xr63fPSkgPnw=; b=OPhksayqgTQ4FoRoyvIbxGWcnOLhczvKvMaFf05mS7wHr6nb9WYaYuM27Oi0DnAIlO v3g96WKCdk+BrRDR3dbOBR1w5YRcj6ZfOQaSX/0FzebgqyZYMHH6DhV7/H6iHfD6orb3 IP0y1o73b5et2cAMI0HErmdw+6LDOxtOMWbfRc6BLwIJMGtKjmcsz+XVLJt3ttD00TRU J55MVd7E3+pZo7oh+XWPgWaduGDJQUHbKthv/PyIAe8JITGsjFzM7WKjv1ek5sRNA+Xx qmOXkSmLqngKYlgujQ5fyyDQ0YIw+kvxcRecp4pCcBRek1xBMkhvURcUssemGPIjgLvr 67zg==
MIME-Version: 1.0
Received: by 10.112.30.65 with SMTP id q1mr7435436lbh.83.1351187147700; Thu, 25 Oct 2012 10:45:47 -0700 (PDT)
Received: by 10.114.39.113 with HTTP; Thu, 25 Oct 2012 10:45:47 -0700 (PDT)
Received: by 10.114.39.113 with HTTP; Thu, 25 Oct 2012 10:45:47 -0700 (PDT)
In-Reply-To: <Pine.LNX.4.64.1210232348110.2471@ps20323.dreamhostps.com>
References: <50604C1A.7090901@gmx.de> <5060A964.5060001@stpeter.im> <Pine.LNX.4.64.1210172354500.2478@ps20323.dreamhostps.com> <507F5A7E.6040206@arcanedomain.com> <50856E3C.103@gmail.com> <Pine.LNX.4.64.1210221753010.2471@ps20323.dreamhostps.com> <0DBC8A11-319C-4120-975E-7E40FD5818BF@gbiv.com> <Pine.LNX.4.64.1210222137530.2471@ps20323.dreamhostps.com> <CA+9kkMDpEZCvcG1DJd=O1qPNV+=+GTBeN+CGndUe51Xym_A9sg@mail.gmail.com> <Pine.LNX.4.64.1210232115210.2471@ps20323.dreamhostps.com> <15E1D98B-8883-4936-81A9-174E1323683C@nordsc.com> <CAGKvQ5ZV6_GMVgjEezhR-oKqSikxR7GYgacMitbfczmNh725mw@mail.gmail.com> <Pine.LNX.4.64.1210232348110.2471@ps20323.dreamhostps.com>
Date: Thu, 25 Oct 2012 10:45:47 -0700
Message-ID: <CAP+FsNdkYyZ0DMJ2jz+Yh6uSSGSV=BH5hfspsdXcXEzDpc83DA@mail.gmail.com>
Subject: Re: [whatwg] New URL Standard from Anne van Kesteren on 2012-09-24 (public-whatwg-archive@w3.org from September 2012)
From: Roberto Peon <grmocg@gmail.com>
To: Ian Hickson <ian@hixie.ch>
Content-Type: multipart/alternative; boundary=bcaec55401c4f6b96304cce5c5e1
Cc: URI <uri@w3.org>, Jan Algermissen <jan.algermissen@nordsc.com>, Christophe Lauret <clauret@weborganic.com>, Ted Hardie <ted.ietf@gmail.com>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Oct 2012 17:45:50 -0000

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

There are obviously orthogonal problems here.
If we were doing this as code, these would be separate functions and most
everyone would agree that it would make both testing and understanding
easier.

Why is it different with specs? The hardest part of specs is choosing which
one is right. The second hardest part is dealing with ambiguity (and the
larger the function, the more difficult figuring out intention, at least
IMHO)

-=R
On Oct 24, 2012 8:44 AM, "Ian Hickson" <ian@hixie.ch> wrote:

> On Wed, 24 Oct 2012, Christophe Lauret wrote:
> >
> > As a Web developer who's had to write code multiple times to handle URIs
> > in very different contexts, I actually *like* the constraints in STD 66,
> > there are many instances where it is simpler to assume that the error
> > handling has been done prior and simply reject an invalid URI.
>
> I think we can agree that the error handling should be, at the option of
> the software developer, either to handle the input as defined by the
> spec's algorithms, or to abort and not handle the input at all.
>
>
> > But why not do it as a separate spec?
>
> Having multiple specs means an implementor has to refer to multiple specs
> to implement one algorithm, which is not a way to get interoperability.
> Bugs creep in much faster when implementors have to switch between specs
> just in the implementation of one algorithm.
>
>
> > Increasing the space of valid addresses, when the set of addressable
> > resources is not actually increasing only means more complex parsing
> rules.
>
> I'm not saying we should increase the space of valid addresses. The de
> facto parsing rules are already complicated by de facto requirements for
> handling errors, so defining those doesn't increase complexity either
> (especially if such behaviour is left as optional, as discussed above.)
>
> --
> Ian Hickson               U+1047E                )\._.,--....,'``.    fL
> http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
> Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
>

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

<p dir=3D"ltr"></p>
<p dir=3D"ltr">There are obviously orthogonal problems here.<br>
If we were doing this as code, these would be separate functions and most e=
veryone would agree that it would make both testing and understanding easie=
r.</p>
<p dir=3D"ltr">Why is it different with specs? The hardest part of specs is=
 choosing which one is right. The second hardest part is dealing with ambig=
uity (and the larger the function, the more difficult figuring out intentio=
n, at least IMHO)</p>

<p dir=3D"ltr">-=3DR</p>
<div class=3D"gmail_quote">On Oct 24, 2012 8:44 AM, &quot;Ian Hickson&quot;=
 &lt;<a href=3D"mailto:ian@hixie.ch">ian@hixie.ch</a>&gt; wrote:<br type=3D=
"attribution"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex">
On Wed, 24 Oct 2012, Christophe Lauret wrote:<br>
&gt;<br>
&gt; As a Web developer who&#39;s had to write code multiple times to handl=
e URIs<br>
&gt; in very different contexts, I actually *like* the constraints in STD 6=
6,<br>
&gt; there are many instances where it is simpler to assume that the error<=
br>
&gt; handling has been done prior and simply reject an invalid URI.<br>
<br>
I think we can agree that the error handling should be, at the option of<br=
>
the software developer, either to handle the input as defined by the<br>
spec&#39;s algorithms, or to abort and not handle the input at all.<br>
<br>
<br>
&gt; But why not do it as a separate spec?<br>
<br>
Having multiple specs means an implementor has to refer to multiple specs<b=
r>
to implement one algorithm, which is not a way to get interoperability.<br>
Bugs creep in much faster when implementors have to switch between specs<br=
>
just in the implementation of one algorithm.<br>
<br>
<br>
&gt; Increasing the space of valid addresses, when the set of addressable<b=
r>
&gt; resources is not actually increasing only means more complex parsing r=
ules.<br>
<br>
I&#39;m not saying we should increase the space of valid addresses. The de<=
br>
facto parsing rules are already complicated by de facto requirements for<br=
>
handling errors, so defining those doesn&#39;t increase complexity either<b=
r>
(especially if such behaviour is left as optional, as discussed above.)<br>
<br>
--<br>
Ian Hickson =A0 =A0 =A0 =A0 =A0 =A0 =A0 U+1047E =A0 =A0 =A0 =A0 =A0 =A0 =A0=
 =A0)\._.,--....,&#39;``. =A0 =A0fL<br>
<a href=3D"http://ln.hixie.ch/" target=3D"_blank">http://ln.hixie.ch/</a> =
=A0 =A0 =A0 U+263A =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0/, =A0 _.. \ =A0 _\ =A0;`=
._ ,.<br>
Things that are impossible just take longer. =A0 `._.-(,_..&#39;--(,_..&#39=
;`-.;.&#39;<br>
</blockquote></div>

--bcaec55401c4f6b96304cce5c5e1--

From iesg-secretary@ietf.org  Thu Oct 25 11:34:42 2012
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0FE0121F885F; Thu, 25 Oct 2012 11:34:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.54
X-Spam-Level: 
X-Spam-Status: No, score=-102.54 tagged_above=-999 required=5 tests=[AWL=0.059, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4Glb3NKYPDAZ; Thu, 25 Oct 2012 11:34:41 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6CEF621F85BB; Thu, 25 Oct 2012 11:34:41 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: IESG Secretary <iesg-secretary@ietf.org>
To: IETF Announcement List <ietf-announce@ietf.org>
Subject: IESG Statement on Ethertypes
X-Test-IDTracker: no
X-IETF-IDTracker: 4.34
Message-ID: <20121025183441.32156.10765.idtracker@ietfa.amsl.com>
Date: Thu, 25 Oct 2012 11:34:41 -0700
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Oct 2012 18:34:42 -0000

The IEEE Registration Authority (IEEE RA) assigns Ethertypes with
oversight from the IEEE Registration Authority Committee (IEEE RAC).
(See http://standards.ieee.org/develop/regauth/ethertype/.)  Some IETF
protocol specification make use of Ethertypes.  All Ethertype requests
are subject to review by a consultant to the IEEE RA followed by
IEEE RAC confirmation. =


Since Ethertypes are a fairly scarce resource, the IEEE RAC has let us
know that they will not assign a new Ethertype to a new IETF protocol
specification until the IESG has approved the protocol specification for
publication as an RFC.  In exceptional cases, the IEEE RA is willing to
consider "early allocation" of an Ethertype for an IETF protocol that is
still under development as long as the request comes from and has been
vetted by the IESG.

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

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


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

From dougb@dougbarton.us  Thu Oct 25 11:41:04 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 1303521F87E1 for <ietf@ietfa.amsl.com>; Thu, 25 Oct 2012 11:41:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.43
X-Spam-Level: 
X-Spam-Status: No, score=-3.43 tagged_above=-999 required=5 tests=[AWL=0.169,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1RqC+3IetHOL for <ietf@ietfa.amsl.com>; Thu, 25 Oct 2012 11:41:03 -0700 (PDT)
Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by ietfa.amsl.com (Postfix) with ESMTP id 9D4B221F87BD for <ietf@ietf.org>; Thu, 25 Oct 2012 11:41:02 -0700 (PDT)
Received: (qmail 18376 invoked by uid 399); 25 Oct 2012 18:40:46 -0000
Received: from unknown (HELO ?192.168.0.102?) (dougb@dougbarton.us@12.207.105.210) by mail2.fluidhosting.com with ESMTPAM; 25 Oct 2012 18:40:46 -0000
X-Originating-IP: 12.207.105.210
X-Sender: dougb@dougbarton.us
Message-ID: <508987B9.2040207@dougbarton.us>
Date: Thu, 25 Oct 2012 11:40:57 -0700
From: Doug Barton <dougb@dougbarton.us>
Organization: http://SupersetSolutions.com/
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121010 Thunderbird/16.0.1
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Just so I'm clear
References: <20121023192135.203AC18C0A4@mercury.lcs.mit.edu>	<5086EF82.9060900@dougbarton.us> <20121023200713.GC1861@nsn.com>	<5086FBCE.2070503@dougbarton.us> <20121023213251.GF27557@verdi>	<50873AB4.1000905@dougbarton.us>	<20121024034736.GC52558@crankycanuck.ca>	<50876D39.20502@dougbarton.us> <508773E7.10203@cisco.com>	<50877633.1000402@dougbarton.us>	<EA9BEA2E-EE96-4E80-B719-652BBD620A79@lilacglade.org> <508842C2.4020203@dougbarton.us> <5088EE5A.4090103@gmail.com>
In-Reply-To: <5088EE5A.4090103@gmail.com>
X-Enigmail-Version: 1.4.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: Thu, 25 Oct 2012 18:41:04 -0000

On 10/25/2012 12:46 AM, Brian E Carpenter wrote:
> On 24/10/2012 20:34, Doug Barton wrote:
> ...
>> ... Nothing in the text suggests an
>> unfettered right of creating new definitions of "vacant."
> 
> You mean, new compared to the first definition in Merriam-Webster.com?
> 
> 1: not occupied by an incumbent, possessor, or officer <a vacant office> <vacant thrones>

C'mon Brian, not helpful. We're talking about the BCP 101 "definition of
vacant" which unfortunately is not nearly so precise. If there were no
mention of 3777 in the text then there would appear to be more leeway in
declaring a position vacant.

> Objectively and factually, that seems to be the case.

I get that this is what you believe to be true, however what some of us
are saying is that we don't agree. Given that the only choices are
"vacant, or recall;" and given that the vacant state of the seat isn't
100% clear, at this time recall is the only option.

Doug

From iesg-secretary@ietf.org  Thu Oct 25 11:47:21 2012
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7CC9621F887C; Thu, 25 Oct 2012 11:47:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.54
X-Spam-Level: 
X-Spam-Status: No, score=-102.54 tagged_above=-999 required=5 tests=[AWL=0.059, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8wKb8X35t4ar; Thu, 25 Oct 2012 11:47:20 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E005C21F8830; Thu, 25 Oct 2012 11:47:20 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: IESG Secretary <iesg-secretary@ietf.org>
To: IETF Announcement List <ietf-announce@ietf.org>
Subject: IESG Statement on Removal of an Internet-Draft from the IETF Web Site
X-Test-IDTracker: no
X-IETF-IDTracker: 4.34
Message-ID: <20121025184720.8144.21627.idtracker@ietfa.amsl.com>
Date: Thu, 25 Oct 2012 11:47:20 -0700
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Oct 2012 18:47:21 -0000

Internet-Drafts (I-Ds) are working documents of the IETF.  RFC 2026,
BCP 9, describes the purpose of I-Ds, and it also provides some policies
that govern the I-D Repository.  RFC 2026 says:

   During the development of a specification, draft versions of the
   document are made available for informal review and comment by
   placing them in the IETF's "Internet-Drafts" directory, which is
   replicated on a number of Internet hosts.  This makes an evolving
   working document readily available to a wide audience, facilitating
   the process of review and revision.

   An Internet-Draft that is published as an RFC, or that has remained
   unchanged in the Internet-Drafts directory for more than six months
   without being recommended by the IESG for publication as an RFC, is
   simply removed from the Internet-Drafts directory.  At any time, an
   Internet-Draft may be replaced by a more recent version of the same
   specification, restarting the six-month timeout period.

   An Internet-Draft is NOT a means of "publishing" a specification;
   specifications are published through the RFC mechanism described in
   the previous section.  Internet-Drafts have no formal status, and are
   subject to change or removal at any time.

I-Ds provide important historical records for the open and transparent
operation of the IETF.  It should be noted that individuals and groups,
including the IAB and IRTF Research Groups, have chosen to distribute
working documents as I-Ds.

I-Ds are stored in two places on the IETF web site.  First, current I-Ds
are stored in the I-D Repository.  Second, current and past I-Ds are
stored in a Public I-D Archive.

The policies associated with I-D Repository are discussed in RFC 2026,
and this IESG statement offers no additional policies regarding the
I-D Repository.

As RFC 2026 says, the entries in the I-D Repository are subject to
change or removal at any time; however, I-Ds generally remain in the
Public I-D Archive to support easy comparison with previous versions.
This availability facilitates review, comment, and revision.

An I-D will only be removed from the Public I-D Archive under unusual
circumstances with consensus of the IESG.  If you are aware of abuse or
misuse that warrants removal of an I-D from the Public I-D Archive,
please write to iesg@ietf.org and explain the situation.  At its
discretion, the IESG may consult counsel or the IETF community before
taking any action on such requests.  If circumstances permit, a removed
I-D will be replaced with a tombstone file that describes the reason that
the I-D was removed from the Public I-D Archive.

When an I-D is removed from the Public I-D Archive, a copy will be kept
in a location accessible by the IETF Secretariat.  This private location
is described in RFC 2026 as follows:

  ... Internet-Drafts that
  have been removed (for any reason) from the Internet-Drafts
  directories shall be archived by the IETF Secretariat for the sole
  purpose of preserving an historical record of Internet standards
  activity and thus are not retrievable except in special
  circumstances.
  =

The IESG, IAB, IAOC, or the Internet Society Board of Trustees can
request the IETF Secretariat to search this private location in
support of responses to appeals, responses to subpoenas, or other
handling of legal matters.  The IETF Secretariat is expected to make
the results of searches of the private location available as needed to
appropriately respond to such matters.

From dougb@dougbarton.us  Thu Oct 25 11:52:50 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 F116321F8662 for <ietf@ietfa.amsl.com>; Thu, 25 Oct 2012 11:52:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.444
X-Spam-Level: 
X-Spam-Status: No, score=-3.444 tagged_above=-999 required=5 tests=[AWL=0.155,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IYzopXQrNr4d for <ietf@ietfa.amsl.com>; Thu, 25 Oct 2012 11:52:50 -0700 (PDT)
Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by ietfa.amsl.com (Postfix) with ESMTP id 4219621F863F for <ietf@ietf.org>; Thu, 25 Oct 2012 11:52:50 -0700 (PDT)
Received: (qmail 31472 invoked by uid 399); 25 Oct 2012 18:52:35 -0000
Received: from unknown (HELO ?192.168.0.102?) (dougb@dougbarton.us@12.207.105.210) by mail2.fluidhosting.com with ESMTPAM; 25 Oct 2012 18:52:35 -0000
X-Originating-IP: 12.207.105.210
X-Sender: dougb@dougbarton.us
Message-ID: <50898A7E.7050906@dougbarton.us>
Date: Thu, 25 Oct 2012 11:52:46 -0700
From: Doug Barton <dougb@dougbarton.us>
Organization: http://SupersetSolutions.com/
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121010 Thunderbird/16.0.1
MIME-Version: 1.0
To: Carsten Bormann <cabo@tzi.org>
Subject: Re: don't overthink, was Just so I'm clear
References: <20121025125351.285D818C0A0@mercury.lcs.mit.edu> <CAC4RtVAhAsLxkaOOFvW5BnSSxYzbR_bfppgSGtm_ocvO0oqycA@mail.gmail.com> <14b501cdb2be$43301f50$c9905df0$@olddog.co.uk> <9DE2CA28-1D75-4BF4-8B4C-9B0449B0D9BE@tzi.org>
In-Reply-To: <9DE2CA28-1D75-4BF4-8B4C-9B0449B0D9BE@tzi.org>
X-Enigmail-Version: 1.4.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: Thu, 25 Oct 2012 18:52:51 -0000

On 10/25/2012 9:57 AM, Carsten Bormann wrote:
> On Oct 25, 2012, at 16:37, "Adrian Farrel" <adrian@olddog.co.uk> wrote:
> 
>> > retro-active
> I don't get how that is relevant.
> This is for the case the seat is still vacant when the new process comes into force.

When Marshall was appointed the rules we have now were in place. To
change the rules now, and then apply them to this situation is by
definition retroactive.

Doug

From jnc@mercury.lcs.mit.edu  Thu Oct 25 11:57:31 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 3039721F873A for <ietf@ietfa.amsl.com>; Thu, 25 Oct 2012 11:57:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.473
X-Spam-Level: 
X-Spam-Status: No, score=-6.473 tagged_above=-999 required=5 tests=[AWL=0.126,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fT+JfN0VQr9q for <ietf@ietfa.amsl.com>; Thu, 25 Oct 2012 11:57:29 -0700 (PDT)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id 6ED1221F87BD for <ietf@ietf.org>; Thu, 25 Oct 2012 11:57:27 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 9CACF18C0A0; Thu, 25 Oct 2012 14:57:24 -0400 (EDT)
To: ietf@ietf.org
Subject: Re: don't overthink, was Just so I'm clear
Message-Id: <20121025185724.9CACF18C0A0@mercury.lcs.mit.edu>
Date: Thu, 25 Oct 2012 14:57:24 -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, 25 Oct 2012 18:57:31 -0000

    > From: Doug Barton <dougb@dougbarton.us>

    > When Marshall was appointed the rules we have now were in place. 
    > To change the rules now, and then apply them to this situation is by
    > definition retroactive.

By that logic, _any_ change to any rule involving, say, the IESG (repeat for
all other I* bodies) - e.g. changing its powers, etc - can't come into play
until between 1 and 2 years have passed, so that all existing seated members
will have been replaced/reseated.

Otherwise you'll be changing the powers/etc that they had when they were
seated - i.e. retroactive changes to their powers/etc.

	Noel

From melinda.shore@gmail.com  Thu Oct 25 12:01:54 2012
Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9989521F8961 for <ietf@ietfa.amsl.com>; Thu, 25 Oct 2012 12:01:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cFmE4vnjDcz0 for <ietf@ietfa.amsl.com>; Thu, 25 Oct 2012 12:01:54 -0700 (PDT)
Received: from mail-pa0-f44.google.com (mail-pa0-f44.google.com [209.85.220.44]) by ietfa.amsl.com (Postfix) with ESMTP id D1EE821F896D for <ietf@ietf.org>; Thu, 25 Oct 2012 12:01:49 -0700 (PDT)
Received: by mail-pa0-f44.google.com with SMTP id fb11so1376334pad.31 for <ietf@ietf.org>; Thu, 25 Oct 2012 12:01:49 -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=NCx8qCqk+GtJmvBcZd+QwGNEHMj8bobiYD/HweEVUeU=; b=xv88foradjLPluSnDP+wj+3xBqjKWb0JHUJ6P0OTLmho332NORu9yfpOfiLAjR7Q34 F4P3RNltaDy0x0AnIhTVEiBJ90HLA/BxNdtMkJo/kVEJxfYU1xRAclyY8UvQs+O17c4b B2hXoefF6QiBbknegbR90/I/12hs41xu1p2jPtEksZreLhOKdnJ/AW5gHgbGWLOFHeNO 9VDw3Cy/GnbgkDONL9bHV0SuYJKy9bE+AhsdmR57BStNPznkVQYC1/TS2dCBO0ubQKMv RLAznOUOtHrapwLSxSg1jHA9leiyCCuW2NBY6wa5sNOYjnEBpfNHjgHpZtRJ5YK+mGWD SjMA==
Received: by 10.68.247.39 with SMTP id yb7mr17239663pbc.15.1351191709603; Thu, 25 Oct 2012 12:01:49 -0700 (PDT)
Received: from spandex.local (216-67-49-109-rb1.fai.dsl.dynamic.acsalaska.net. [216.67.49.109]) by mx.google.com with ESMTPS id un16sm11607373pbc.47.2012.10.25.12.01.47 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 25 Oct 2012 12:01:48 -0700 (PDT)
Message-ID: <50898C9A.5010408@gmail.com>
Date: Thu, 25 Oct 2012 11:01:46 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:16.0) Gecko/20121010 Thunderbird/16.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: don't overthink, was Just so I'm clear
References: <20121025185724.9CACF18C0A0@mercury.lcs.mit.edu>
In-Reply-To: <20121025185724.9CACF18C0A0@mercury.lcs.mit.edu>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Oct 2012 19:01:54 -0000

On 10/25/12 10:57 AM, Noel Chiappa wrote:
> Otherwise you'll be changing the powers/etc that they had when they were
> seated - i.e. retroactive changes to their powers/etc.

I'm not seeing any movement in the discussion - it's probably time to
talk with an attorney.

Melinda



From cabo@tzi.org  Thu Oct 25 12:05:16 2012
Return-Path: <cabo@tzi.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 93B1621F869F for <ietf@ietfa.amsl.com>; Thu, 25 Oct 2012 12:05:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.226
X-Spam-Level: 
X-Spam-Status: No, score=-106.226 tagged_above=-999 required=5 tests=[AWL=0.023, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Zc7T6zDa4Kz2 for <ietf@ietfa.amsl.com>; Thu, 25 Oct 2012 12:05:15 -0700 (PDT)
Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) by ietfa.amsl.com (Postfix) with ESMTP id A770421F868C for <ietf@ietf.org>; Thu, 25 Oct 2012 12:05:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.3/8.14.3) with ESMTP id q9PJ54kv004629; Thu, 25 Oct 2012 21:05:04 +0200 (CEST)
Received: from [192.168.217.105] (p54892C1E.dip.t-dialin.net [84.137.44.30]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 2C71E29C; Thu, 25 Oct 2012 21:05:04 +0200 (CEST)
Subject: Re: don't overthink, was Just so I'm clear
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Content-Type: text/plain; charset=iso-8859-1
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <50898A7E.7050906@dougbarton.us>
Date: Thu, 25 Oct 2012 21:05:02 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <D8E173AE-2C40-497D-9566-933C7DE642ED@tzi.org>
References: <20121025125351.285D818C0A0@mercury.lcs.mit.edu> <CAC4RtVAhAsLxkaOOFvW5BnSSxYzbR_bfppgSGtm_ocvO0oqycA@mail.gmail.com> <14b501cdb2be$43301f50$c9905df0$@olddog.co.uk> <9DE2CA28-1D75-4BF4-8B4C-9B0449B0D9BE@tzi.org> <50898A7E.7050906@dougbarton.us>
To: Doug Barton <dougb@dougbarton.us>
X-Mailer: Apple Mail (2.1499)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Oct 2012 19:05:16 -0000

On Oct 25, 2012, at 20:52, Doug Barton <dougb@dougbarton.us> wrote:

> On 10/25/2012 9:57 AM, Carsten Bormann wrote:
>> On Oct 25, 2012, at 16:37, "Adrian Farrel" <adrian@olddog.co.uk> =
wrote:
>>=20
>>>> retro-active
>> I don't get how that is relevant.
>> This is for the case the seat is still vacant when the new process =
comes into force.
>=20
> When Marshall was appointed the rules we have now were in place. To
> change the rules now, and then apply them to this situation is by
> definition retroactive.

There is some confusion in this argument:
We are not doing penal code here, where such a definition would indeed =
apply.
 =20
We are trying to keep the IAOC functioning.

If the IAOC is still impaired at the time the new process comes into =
force,=20
there is nothing retroactive about acting on the situation then and =
there.

Gr=FC=DFe, Carsten


From rbonica@juniper.net  Thu Oct 25 12:12:45 2012
Return-Path: <rbonica@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 B740721F8960; Thu, 25 Oct 2012 12:12:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.449
X-Spam-Level: 
X-Spam-Status: No, score=-104.449 tagged_above=-999 required=5 tests=[AWL=-0.982, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, UNRESOLVED_TEMPLATE=3.132, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2JmqCfl0nXi7; Thu, 25 Oct 2012 12:12:45 -0700 (PDT)
Received: from exprod7og112.obsmtp.com (exprod7og112.obsmtp.com [64.18.2.177]) by ietfa.amsl.com (Postfix) with ESMTP id E50D521F88F9; Thu, 25 Oct 2012 12:12:44 -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 DSNKUImPKbxcvv2z4gA5LGW1jdjdRCzi8q44@postini.com; Thu, 25 Oct 2012 12:12:45 PDT
Received: from P-CLDFE01-HQ.jnpr.net (172.24.192.59) by P-EMHUB01-HQ.jnpr.net (172.24.192.35) with Microsoft SMTP Server (TLS) id 8.3.213.0; Thu, 25 Oct 2012 12:11:47 -0700
Received: from o365mail.juniper.net (207.17.137.224) by o365mail.juniper.net (172.24.192.59) with Microsoft SMTP Server id 14.1.355.2; Thu, 25 Oct 2012 12:11:47 -0700
Received: from db3outboundpool.messaging.microsoft.com (213.199.154.143) by o365mail.juniper.net (207.17.137.224) with Microsoft SMTP Server (TLS) id 14.1.355.2; Thu, 25 Oct 2012 12:17:59 -0700
Received: from mail17-db3-R.bigfish.com (10.3.81.244) by DB3EHSOBE010.bigfish.com (10.3.84.30) with Microsoft SMTP Server id 14.1.225.23; Thu, 25 Oct 2012 19:11:45 +0000
Received: from mail17-db3 (localhost [127.0.0.1])	by mail17-db3-R.bigfish.com (Postfix) with ESMTP id A5AC52201D8; Thu, 25 Oct 2012 19:11:44 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.245.197; KIP:(null); UIP:(null); (null); H:CH1PRD0511HT002.namprd05.prod.outlook.com; R:internal; EFV:INT
X-SpamScore: -24
X-BigFish: PS-24(z5b2kz9371I542M1432Izz1202h1d1ah1d2ahzz1033IL17326ah8275dhz2dh2a8h668h839h944hd25hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh1155h)
Received: from mail17-db3 (localhost.localdomain [127.0.0.1]) by mail17-db3 (MessageSwitch) id 1351192300423298_26121; Thu, 25 Oct 2012 19:11:40 +0000 (UTC)
Received: from DB3EHSMHS014.bigfish.com (unknown [10.3.81.254])	by mail17-db3.bigfish.com (Postfix) with ESMTP id 5F103340067; Thu, 25 Oct 2012 19:11:40 +0000 (UTC)
Received: from CH1PRD0511HT002.namprd05.prod.outlook.com (157.56.245.197) by DB3EHSMHS014.bigfish.com (10.3.87.114) with Microsoft SMTP Server (TLS) id 14.1.225.23; Thu, 25 Oct 2012 19:11:38 +0000
Received: from CH1PRD0511MB418.namprd05.prod.outlook.com ([169.254.9.10]) by CH1PRD0511HT002.namprd05.prod.outlook.com ([10.255.159.37]) with mapi id 14.16.0224.004; Thu, 25 Oct 2012 19:11:15 +0000
From: Ronald Bonica <rbonica@juniper.net>
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>, IESG Secretary <iesg-secretary@ietf.org>
Subject: RE: WG Action: Conclusion of Address Resolution for Massive numbers of 	hosts in the Data center (armd)
Thread-Topic: WG Action: Conclusion of Address Resolution for Massive numbers	of 	hosts in the Data center (armd)
Thread-Index: AQHNsc+2UXvvFPDuQ0GplIXY/fYhh5fKYJeg
Date: Thu, 25 Oct 2012 19:11:15 +0000
Message-ID: <2CF4CB03E2AA464BA0982EC92A02CE2502C225@CH1PRD0511MB418.namprd05.prod.outlook.com>
References: <20121023183252.7359.72200.idtracker@ietfa.amsl.com> <20121024100744.GA15377@nic.fr>
In-Reply-To: <20121024100744.GA15377@nic.fr>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [66.129.232.2]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
X-FOPE-CONNECTOR: Id%12219$Dn%NIC.FR$RO%2$TLS%5$FQDN%onpremiseedge-1018244.customer.frontbridge.com$TlsDn%o365mail.juniper.net
X-FOPE-CONNECTOR: Id%12219$Dn%IETF.ORG$RO%2$TLS%5$FQDN%onpremiseedge-1018244.customer.frontbridge.com$TlsDn%o365mail.juniper.net
X-FOPE-CONNECTOR: Id%12219$Dn%HUAWEI.COM$RO%2$TLS%5$FQDN%onpremiseedge-1018244.customer.frontbridge.com$TlsDn%o365mail.juniper.net
Cc: "ldunbar@huawei.com" <ldunbar@huawei.com>, "ietf@ietf.org" <ietf@ietf.org>, "armd@ietf.org" <armd@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Oct 2012 19:12:45 -0000

Hello Stephane,

My apologies. The shutdown message should have included a pointer to the fo=
llowing email, which was posted on the ARMD mailing list by Benson Schliess=
er on June 22:

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

                            Ron

> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
> Stephane Bortzmeyer
> Sent: Wednesday, October 24, 2012 6:08 AM
> To: IESG Secretary
> Cc: ldunbar@huawei.com; ietf@ietf.org; armd@ietf.org
> Subject: Re: WG Action: Conclusion of Address Resolution for Massive
> numbers of hosts in the Data center (armd)
>=20
> On Tue, Oct 23, 2012 at 11:32:52AM -0700,  IESG Secretary <iesg-
> secretary@ietf.org> wrote  a message of 7 lines which said:
>=20
> > The Address Resolution for Massive numbers of hosts in the Data
> center
> > (armd) working group in the Operations and Management Area has
> > concluded.
>=20
> Its charter is far from completed and I do not find in the archives of
> the mailing list of the WG an explanation. Two lines of text to explain
> what happened?



From dougb@dougbarton.us  Thu Oct 25 12:13:32 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 B27C421F88F9 for <ietf@ietfa.amsl.com>; Thu, 25 Oct 2012 12:13:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.456
X-Spam-Level: 
X-Spam-Status: No, score=-3.456 tagged_above=-999 required=5 tests=[AWL=0.143,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iHnrgR9tZ1ew for <ietf@ietfa.amsl.com>; Thu, 25 Oct 2012 12:13:32 -0700 (PDT)
Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by ietfa.amsl.com (Postfix) with ESMTP id D01F021F84EE for <ietf@ietf.org>; Thu, 25 Oct 2012 12:13:31 -0700 (PDT)
Received: (qmail 28305 invoked by uid 399); 25 Oct 2012 19:13:17 -0000
Received: from unknown (HELO ?192.168.0.102?) (dougb@dougbarton.us@12.207.105.210) by mail2.fluidhosting.com with ESMTPAM; 25 Oct 2012 19:13:17 -0000
X-Originating-IP: 12.207.105.210
X-Sender: dougb@dougbarton.us
Message-ID: <50898F58.4030605@dougbarton.us>
Date: Thu, 25 Oct 2012 12:13:28 -0700
From: Doug Barton <dougb@dougbarton.us>
Organization: http://SupersetSolutions.com/
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121010 Thunderbird/16.0.1
MIME-Version: 1.0
To: Carsten Bormann <cabo@tzi.org>
Subject: Re: don't overthink, was Just so I'm clear
References: <20121025125351.285D818C0A0@mercury.lcs.mit.edu> <CAC4RtVAhAsLxkaOOFvW5BnSSxYzbR_bfppgSGtm_ocvO0oqycA@mail.gmail.com> <14b501cdb2be$43301f50$c9905df0$@olddog.co.uk> <9DE2CA28-1D75-4BF4-8B4C-9B0449B0D9BE@tzi.org> <50898A7E.7050906@dougbarton.us> <D8E173AE-2C40-497D-9566-933C7DE642ED@tzi.org>
In-Reply-To: <D8E173AE-2C40-497D-9566-933C7DE642ED@tzi.org>
X-Enigmail-Version: 1.4.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: Thu, 25 Oct 2012 19:13:32 -0000

On 10/25/2012 12:05 PM, Carsten Bormann wrote:
> On Oct 25, 2012, at 20:52, Doug Barton <dougb@dougbarton.us> wrote:
> 
>> On 10/25/2012 9:57 AM, Carsten Bormann wrote:
>>> On Oct 25, 2012, at 16:37, "Adrian Farrel" <adrian@olddog.co.uk> wrote:
>>>
>>>>> retro-active
>>> I don't get how that is relevant.
>>> This is for the case the seat is still vacant when the new process comes into force.
>>
>> When Marshall was appointed the rules we have now were in place. To
>> change the rules now, and then apply them to this situation is by
>> definition retroactive.
> 
> There is some confusion in this argument:
> We are not doing penal code here, where such a definition would indeed apply.
>   
> We are trying to keep the IAOC functioning.
> 
> If the IAOC is still impaired at the time the new process comes into force, 
> there is nothing retroactive about acting on the situation then and there.

First, I disagree with your belief that what you propose would not be
retroactive. Second, it's worth pointing out that if the IAOC put an
equal amount of effort into the recall procedure, the problem would be
just as solved, without danger of repercussion.

Doug

From dougb@dougbarton.us  Thu Oct 25 12:20:09 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 9FCCE21F86CB for <ietf@ietfa.amsl.com>; Thu, 25 Oct 2012 12:20:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.466
X-Spam-Level: 
X-Spam-Status: No, score=-3.466 tagged_above=-999 required=5 tests=[AWL=0.133,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zQrXCi8e7mlm for <ietf@ietfa.amsl.com>; Thu, 25 Oct 2012 12:20:09 -0700 (PDT)
Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by ietfa.amsl.com (Postfix) with ESMTP id E0E6A21F86B9 for <ietf@ietf.org>; Thu, 25 Oct 2012 12:20:08 -0700 (PDT)
Received: (qmail 30855 invoked by uid 399); 25 Oct 2012 19:19:53 -0000
Received: from unknown (HELO ?192.168.0.102?) (dougb@dougbarton.us@12.207.105.210) by mail2.fluidhosting.com with ESMTPAM; 25 Oct 2012 19:19:53 -0000
X-Originating-IP: 12.207.105.210
X-Sender: dougb@dougbarton.us
Message-ID: <508990E4.9040809@dougbarton.us>
Date: Thu, 25 Oct 2012 12:20:04 -0700
From: Doug Barton <dougb@dougbarton.us>
Organization: http://SupersetSolutions.com/
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121010 Thunderbird/16.0.1
MIME-Version: 1.0
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Subject: Re: don't overthink, was Just so I'm clear
References: <20121025185724.9CACF18C0A0@mercury.lcs.mit.edu>
In-Reply-To: <20121025185724.9CACF18C0A0@mercury.lcs.mit.edu>
X-Enigmail-Version: 1.4.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: Thu, 25 Oct 2012 19:20:10 -0000

On 10/25/2012 11:57 AM, Noel Chiappa wrote:
>> From: Doug Barton <dougb@dougbarton.us>
> 
>> When Marshall was appointed the rules we have now were in place. To
>> change the rules now, and then apply them to this situation is by 
>> definition retroactive.
> 
> By that logic, _any_ change to any rule involving, say, the IESG
> (repeat for all other I* bodies) - e.g. changing its powers, etc -
> can't come into play until between 1 and 2 years have passed, so that
> all existing seated members will have been replaced/reseated.
> 
> Otherwise you'll be changing the powers/etc that they had when they
> were seated - i.e. retroactive changes to their powers/etc.

I can see why you would conclude that, but generally your interpretation
would be wrong. The idea here is that applying _punitive_ action (such
as removal from a position) retroactively is not "fair," and therefore
shouldn't be done.

If your hypothetical changes involved granting more powers/benefits/etc.
to a sitting board, it's doubtful that any of them would disagree. :)

If your hypothetical change _removed_ things from a sitting board, some
of them may not like it ("This was not the job I signed up for") and
then they have the option to resign.

Doug

From melinda.shore@gmail.com  Thu Oct 25 12:21:22 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 562F021F86CB for <ietf@ietfa.amsl.com>; Thu, 25 Oct 2012 12:21:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OPQoD792GvZa for <ietf@ietfa.amsl.com>; Thu, 25 Oct 2012 12:21:21 -0700 (PDT)
Received: from mail-da0-f44.google.com (mail-da0-f44.google.com [209.85.210.44]) by ietfa.amsl.com (Postfix) with ESMTP id B55DF21F86B9 for <ietf@ietf.org>; Thu, 25 Oct 2012 12:21:21 -0700 (PDT)
Received: by mail-da0-f44.google.com with SMTP id h15so926183dan.31 for <ietf@ietf.org>; Thu, 25 Oct 2012 12:21: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=iiS/kkzy0t4APC1mk3oNcdlGZWcENuZPDmfMNGh4r9Q=; b=V71zlE8SSz5KefOiUzksDpeXVTrbmsw0eZELlSNEGIE9xLtlKzXkbYyRGQqLopgmFI Px/UFj9xU83e4tcGfIRqG6ZPJtvhH2Sf6PQZDZA3KPCK5D2ZszAibvMUheG59vcs/1nl dE54znXuHmS8Iz9Zl1L5KbVQxtKAxq10P1g3VZl//Fqz3PnsyhKfoz2ITQowsQ/uH5JV T/f7OZow95hLDOv2fgWifuLHGbcVqU12+4BlwCjvyErv+oxWDn1BR2Gx9GRVlquay70L ZxeHru7l4to9nt6hI+cReEBI9jdBmGaGj4Ggx0MPHdN12swgTHO9vrpiO8n+kGA/KnVo wjqQ==
Received: by 10.66.88.4 with SMTP id bc4mr55588706pab.42.1351192881491; Thu, 25 Oct 2012 12:21:21 -0700 (PDT)
Received: from spandex.local (216-67-49-109-rb1.fai.dsl.dynamic.acsalaska.net. [216.67.49.109]) by mx.google.com with ESMTPS id oi2sm11625153pbb.62.2012.10.25.12.21.20 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 25 Oct 2012 12:21:20 -0700 (PDT)
Message-ID: <5089912E.3080200@gmail.com>
Date: Thu, 25 Oct 2012 11:21:18 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:16.0) Gecko/20121010 Thunderbird/16.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: don't overthink, was Just so I'm clear
References: <20121025125351.285D818C0A0@mercury.lcs.mit.edu> <CAC4RtVAhAsLxkaOOFvW5BnSSxYzbR_bfppgSGtm_ocvO0oqycA@mail.gmail.com> <14b501cdb2be$43301f50$c9905df0$@olddog.co.uk> <9DE2CA28-1D75-4BF4-8B4C-9B0449B0D9BE@tzi.org> <50898A7E.7050906@dougbarton.us> <D8E173AE-2C40-497D-9566-933C7DE642ED@tzi.org> <50898F58.4030605@dougbarton.us>
In-Reply-To: <50898F58.4030605@dougbarton.us>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Oct 2012 19:21:22 -0000

On 10/25/12 11:13 AM, Doug Barton wrote:
> First, I disagree with your belief that what you propose would not be
> retroactive. Second, it's worth pointing out that if the IAOC put an
> equal amount of effort into the recall procedure, the problem would be
> just as solved, without danger of repercussion.

In the interest of progress, what do you think *should* be done?
Yesterday you said that you were not in agreement with declaring
the position vacant in this manner.  Is it that you think that
Marshall should not be removed at all, that you think Marshall
should not be considered as having resigned, that you think ... ?
How do you think this should be resolved?

Melinda


From dougb@dougbarton.us  Thu Oct 25 12:28:59 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 CEF4821F87CB for <ietf@ietfa.amsl.com>; Thu, 25 Oct 2012 12:28:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.475
X-Spam-Level: 
X-Spam-Status: No, score=-3.475 tagged_above=-999 required=5 tests=[AWL=0.124,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9mmIc-be-R62 for <ietf@ietfa.amsl.com>; Thu, 25 Oct 2012 12:28:59 -0700 (PDT)
Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by ietfa.amsl.com (Postfix) with ESMTP id 2DE1821F8594 for <ietf@ietf.org>; Thu, 25 Oct 2012 12:28:59 -0700 (PDT)
Received: (qmail 10709 invoked by uid 399); 25 Oct 2012 19:28:44 -0000
Received: from unknown (HELO ?192.168.0.102?) (dougb@dougbarton.us@12.207.105.210) by mail2.fluidhosting.com with ESMTPAM; 25 Oct 2012 19:28:44 -0000
X-Originating-IP: 12.207.105.210
X-Sender: dougb@dougbarton.us
Message-ID: <508992F7.9080700@dougbarton.us>
Date: Thu, 25 Oct 2012 12:28:55 -0700
From: Doug Barton <dougb@dougbarton.us>
Organization: http://SupersetSolutions.com/
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121010 Thunderbird/16.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: don't overthink, was Just so I'm clear
References: <20121025125351.285D818C0A0@mercury.lcs.mit.edu> <CAC4RtVAhAsLxkaOOFvW5BnSSxYzbR_bfppgSGtm_ocvO0oqycA@mail.gmail.com> <14b501cdb2be$43301f50$c9905df0$@olddog.co.uk> <9DE2CA28-1D75-4BF4-8B4C-9B0449B0D9BE@tzi.org> <50898A7E.7050906@dougbarton.us> <D8E173AE-2C40-497D-9566-933C7DE642ED@tzi.org> <50898F58.4030605@dougbarton.us> <5089912E.3080200@gmail.com>
In-Reply-To: <5089912E.3080200@gmail.com>
X-Enigmail-Version: 1.4.5
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Oct 2012 19:28:59 -0000

On 10/25/2012 12:21 PM, Melinda Shore wrote:
> On 10/25/12 11:13 AM, Doug Barton wrote:
>> First, I disagree with your belief that what you propose would not be
>> retroactive. Second, it's worth pointing out that if the IAOC put an
>> equal amount of effort into the recall procedure, the problem would be
>> just as solved, without danger of repercussion.
> 
> In the interest of progress, what do you think *should* be done?
> Yesterday you said that you were not in agreement with declaring
> the position vacant in this manner.  Is it that you think that
> Marshall should not be removed at all, that you think Marshall
> should not be considered as having resigned, that you think ... ?
> How do you think this should be resolved?

I've said it many times already. Start the recall.


From cabo@tzi.org  Thu Oct 25 12:34:20 2012
Return-Path: <cabo@tzi.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 992DD21F85E6 for <ietf@ietfa.amsl.com>; Thu, 25 Oct 2012 12:34:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.227
X-Spam-Level: 
X-Spam-Status: No, score=-106.227 tagged_above=-999 required=5 tests=[AWL=0.022, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Fba9NP17XbIk for <ietf@ietfa.amsl.com>; Thu, 25 Oct 2012 12:34:20 -0700 (PDT)
Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) by ietfa.amsl.com (Postfix) with ESMTP id D2A3B21F85CF for <ietf@ietf.org>; Thu, 25 Oct 2012 12:34:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.3/8.14.3) with ESMTP id q9PJYAPG017935; Thu, 25 Oct 2012 21:34:10 +0200 (CEST)
Received: from [192.168.217.105] (p54892C1E.dip.t-dialin.net [84.137.44.30]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 5D7922BF; Thu, 25 Oct 2012 21:34:10 +0200 (CEST)
Subject: Re: don't overthink, was Just so I'm clear
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Content-Type: text/plain; charset=iso-8859-1
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <508990E4.9040809@dougbarton.us>
Date: Thu, 25 Oct 2012 21:34:09 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <4AC7D071-E72E-4520-8763-381A81FF6AA5@tzi.org>
References: <20121025185724.9CACF18C0A0@mercury.lcs.mit.edu> <508990E4.9040809@dougbarton.us>
To: Doug Barton <dougb@dougbarton.us>
X-Mailer: Apple Mail (2.1499)
Cc: "ietf@ietf.org Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Oct 2012 19:34:20 -0000

On Oct 25, 2012, at 21:20, Doug Barton <dougb@dougbarton.us> wrote:

> _punitive_

Again, you are confused.
This action is not about punishing an individual, and I would be =
violently opposed to it if it were.

This is my last message on this. =20
I'm repulsed by the idea of discussing this under this premise.

Gr=FC=DFe, Carsten


From ajs@anvilwalrusden.com  Thu Oct 25 12:52:55 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 968FD21F8757 for <ietf@ietfa.amsl.com>; Thu, 25 Oct 2012 12:52:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.84
X-Spam-Level: 
X-Spam-Status: No, score=-0.84 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pDMPcg5g2EpQ for <ietf@ietfa.amsl.com>; Thu, 25 Oct 2012 12:52:54 -0700 (PDT)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id BBE0821F873A for <ietf@ietf.org>; Thu, 25 Oct 2012 12:52:50 -0700 (PDT)
Received: from mx1.yitter.info (dhcp-222-230.meetings.nanog.org [199.187.222.230]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id C7AE38A031 for <ietf@ietf.org>; Thu, 25 Oct 2012 19:52:49 +0000 (UTC)
Date: Thu, 25 Oct 2012 15:52:51 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: Exceptional cases (was: don't overthink)
Message-ID: <20121025195057.GA55999@mx1.yitter.info>
References: <20121025185724.9CACF18C0A0@mercury.lcs.mit.edu> <508990E4.9040809@dougbarton.us>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <508990E4.9040809@dougbarton.us>
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, 25 Oct 2012 19:52:55 -0000

On Thu, Oct 25, 2012 at 12:20:04PM -0700, Doug Barton wrote:
> would be wrong. The idea here is that applying _punitive_ action (such
> as removal from a position) retroactively is not "fair," 

Oh, for heaven's sake.  This is nothing to do with punishment.  This
is a straightforward administrative problem.  Turning this into an
opportunity to exercise a heavyweight and in fact punitive process
would be an injustice.  If the IETF has wound itself into such
bureaucratic knots that we can't just make an exceptional decision in
exceptional circumstances, we are in much worse trouble than I
thought.

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

From tglassey@earthlink.net  Thu Oct 25 13:07:21 2012
Return-Path: <tglassey@earthlink.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1FB9821F8816; Thu, 25 Oct 2012 13:07:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.685
X-Spam-Level: 
X-Spam-Status: No, score=-2.685 tagged_above=-999 required=5 tests=[AWL=-0.086, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zgJhnpHymfrL; Thu, 25 Oct 2012 13:07:20 -0700 (PDT)
Received: from elasmtp-galgo.atl.sa.earthlink.net (elasmtp-galgo.atl.sa.earthlink.net [209.86.89.61]) by ietfa.amsl.com (Postfix) with ESMTP id 06B1E21F87BD; Thu, 25 Oct 2012 13:07:20 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=q77E4cBOv6BP/dGbAcPG8xwrb8R4Uc7EPnW8Cxf+Eh/9ESGWDa6sAGc7vyGf1P8y; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [67.180.133.21] (helo=[192.168.15.2]) by elasmtp-galgo.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from <tglassey@earthlink.net>) id 1TRTi3-0001Og-C4; Thu, 25 Oct 2012 16:07:19 -0400
Message-ID: <50899BF5.3050703@earthlink.net>
Date: Thu, 25 Oct 2012 13:07:17 -0700
From: tglassey <tglassey@earthlink.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: ietf@ietf.org, IETF Chair <chair@ietf.org>,  Jorge Contreras <contreraslegal@att.net>
Subject: Doesn't the legal standard for maintaining documents also control this? - Re: IESG Statement on Removal of an Internet-Draft from the IETF Web Site -
References: <20121025184720.8144.21627.idtracker@ietfa.amsl.com>
In-Reply-To: <20121025184720.8144.21627.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 01b7a7e171bdf5911aa676d7e74259b7b3291a7d08dfec797d181e872fe2b4e933c6a0ba6fd7253c350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 67.180.133.21
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Oct 2012 20:07:21 -0000

On 10/25/2012 11:47 AM, IESG Secretary wrote:
> Internet-Drafts (I-Ds) are working documents of the IETF.  RFC 2026,
> BCP 9, describes the purpose of I-Ds, and it also provides some policies
> that govern the I-D Repository.  RFC 2026 says:
>
>     During the development of a specification, draft versions of the
>     document are made available for informal review and comment by
>     placing them in the IETF's "Internet-Drafts" directory, which is
>     replicated on a number of Internet hosts.
OK - we acknowledge that we replicate this for wide distribution... why? 
what specifically is the goal in that? If the goal is to say "This is 
deployed across a large number of sites to enable wide-community 
exposure to in-process works" then perhaps we should revise the BCP's to 
include that idea as well.
>   This makes an evolving
>     working document readily available to a wide audience, facilitating
>     the process of review and revision.
I.e. its supposed to be a snapshot, a signpost along the path so to 
speak...
>
>     An Internet-Draft that is published as an RFC, or that has remained
>     unchanged in the Internet-Drafts directory for more than six months
>     without being recommended by the IESG for publication as an RFC, is
>     simply removed from the Internet-Drafts directory.

An interesting question is how this affects the people hosting images of 
the IETF media and what their legal obligations under CFAA and 
associated legal precedents is. Hosting the IETF file-store could be 
very financially dangerous for publication partners in that they dont 
get the IETF research exemption and are at risk for litigation no matter 
what the "hey the world is flat because we said so" idea which has 
existed so long here.

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

    At any time, an
    Internet-Draft may be replaced by a more recent version of the same
    specification, restarting the six-month timeout period.

Which then raises the issue of whether an I-D provides any 'right to implement the proposed IP it defines' because if it does in any form then it or the trust must address 'rights collisions' or 'rights expiry' and what that means to Relying Parties (as part of the Relying Party License blob) attached to everything IETF.

    An Internet-Draft is NOT a means of "publishing" a specification;

Yeah right - an I-D is exactly a means of publishing a specification, just not one which is a IETF Standard... The problem is the improper use of the Term SPECIFICATION to imply "approved IETF Standard" instead of just a technical discourse on how some protocol works.

    specifications are published through the RFC mechanism described in
    the previous section.  Internet-Drafts have no formal status, and are
    subject to change or removal at any time.

Again - All IETF IP seems to be published with an eternal-use license so all documents must be maintained forever under that mindset it would seem...

    I-Ds provide important historical records for the open and transparent
    operation of the IETF.

Yes very important point and one which ties the issues of the mandatory term of availability to the archival period...

    It should be noted that individuals and groups,
    including the IAB and IRTF Research Groups, have chosen to distribute
    working documents as I-Ds.

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

Yes but what happens to the legal assignment for the licensing of the IP 
in the I-D for its uses as described therein? Does it persist? Is it 
superseded and if so what are the responsibilities in the relying 
parties to deal with that?
>
> I-Ds are stored in two places on the IETF web site.  First, current I-Ds
> are stored in the I-D Repository.  Second, current and past I-Ds are
> stored in a Public I-D Archive.
>
> The policies associated with I-D Repository are discussed in RFC 2026,
> and this IESG statement offers no additional policies regarding the
> I-D Repository.
That is the problem RFC2026 and BCP78/79 fail (and intentionally too) to 
address this issue to try and make an argument that the IETF is not 
accountable for these processes because it has no membership - one of 
those famous fictions the IETF was based on... wink nod...

So the real issue is now - in today's world where the sponsor is 
accountable - what does all this mean?

>
> As RFC 2026 says, the entries in the I-D Repository are subject to
> change or removal at any time; however, I-Ds generally remain in the
> Public I-D Archive to support easy comparison with previous versions.
> This availability facilitates review, comment, and revision.
>
> An I-D will only be removed from the Public I-D Archive under unusual
> circumstances with consensus of the IESG.  If you are aware of abuse or
> misuse that warrants removal of an I-D from the Public I-D Archive,
> please write to iesg@ietf.org and explain the situation.  At its
> discretion, the IESG may consult counsel or the IETF community before
> taking any action on such requests.  If circumstances permit, a removed
> I-D will be replaced with a tombstone file that describes the reason that
> the I-D was removed from the Public I-D Archive.
>
> When an I-D is removed from the Public I-D Archive, a copy will be kept
> in a location accessible by the IETF Secretariat.  This private location
> is described in RFC 2026 as follows:
>
>    ... Internet-Drafts that
>    have been removed (for any reason) from the Internet-Drafts
>    directories shall be archived by the IETF Secretariat for the sole
>    purpose of preserving an historical record of Internet standards
>    activity and thus are not retrievable except in special
>    circumstances.
Again - more smoke and mirrors - please simply answer the question as to 
what happens to the legal contract for the use and reprinting of that IP 
per RFC2026 and all of the subsequent RFC's on the matter?
>    
> The IESG, IAB, IAOC, or the Internet Society Board of Trustees can
> request the IETF Secretariat to search this private location in
> support of responses to appeals, responses to subpoenas, or other
> handling of legal matters.

Minimum Storage Period is Seven Years by US Law... sorry... =
=====================================================
OK, in all other areas for every other tax exempt entity there is a 
minimum archive requirement for storage of documents. Since much of the 
IETF's operations are supported by effort which is tied to either tax 
exempt entities or those using the IETF participation as part of 
employee development, it would seem that this same minimum legal 
mandatory retention period of seven years  would apply to any 
workproduct done as part of that process.

Since both ISOC and the parties making those contributions do so under 
this banner its just simple logic that QED the IETF Standards Process 
was impinged by any legal organization requirements for retention of 
documents tied to the charter of that org.

Jorge - since many people use the IETF as part of their tax status 
clearly this is true right? Since the IETF itself is claiming Tax Exempt 
Status all of its operations under the ISOC would also seem to be tied 
for seven years as well... and so many not be an issue which is subject 
to negotiation here.
> The IETF Secretariat is expected to make
> the results of searches of the private location available as needed to
> appropriately respond to such matters.
>


-- 
Regards TSG
"Ex-Cruce-Leo"

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


From dougb@dougbarton.us  Thu Oct 25 13:10:28 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 1942D21F84EA for <ietf@ietfa.amsl.com>; Thu, 25 Oct 2012 13:10:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.483
X-Spam-Level: 
X-Spam-Status: No, score=-3.483 tagged_above=-999 required=5 tests=[AWL=0.116,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MUSi4IpohCtw for <ietf@ietfa.amsl.com>; Thu, 25 Oct 2012 13:10:23 -0700 (PDT)
Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by ietfa.amsl.com (Postfix) with ESMTP id 7895021F88BD for <ietf@ietf.org>; Thu, 25 Oct 2012 13:10:23 -0700 (PDT)
Received: (qmail 31627 invoked by uid 399); 25 Oct 2012 20:09:55 -0000
Received: from unknown (HELO ?192.168.0.102?) (dougb@dougbarton.us@12.207.105.210) by mail2.fluidhosting.com with ESMTPAM; 25 Oct 2012 20:09:55 -0000
X-Originating-IP: 12.207.105.210
X-Sender: dougb@dougbarton.us
Message-ID: <50899C9D.5060108@dougbarton.us>
Date: Thu, 25 Oct 2012 13:10:05 -0700
From: Doug Barton <dougb@dougbarton.us>
Organization: http://SupersetSolutions.com/
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121010 Thunderbird/16.0.1
MIME-Version: 1.0
To: Carsten Bormann <cabo@tzi.org>
Subject: Re: don't overthink, was Just so I'm clear
References: <20121025185724.9CACF18C0A0@mercury.lcs.mit.edu> <508990E4.9040809@dougbarton.us> <4AC7D071-E72E-4520-8763-381A81FF6AA5@tzi.org>
In-Reply-To: <4AC7D071-E72E-4520-8763-381A81FF6AA5@tzi.org>
X-Enigmail-Version: 1.4.5
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "ietf@ietf.org Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Oct 2012 20:10:29 -0000

On 10/25/2012 12:34 PM, Carsten Bormann wrote:
> On Oct 25, 2012, at 21:20, Doug Barton <dougb@dougbarton.us> wrote:
> 
>> _punitive_
> 
> Again, you are confused. This action is not about punishing an
> individual, and I would be violently opposed to it if it were.

Removal from office _is_ considered a punitive action, by any commonly
accepted definition in any context having to do with boards, committees,
etc. But "punitive" is different from "punishment." It's a subtle
distinction, but an important one.

I am not suggesting that Marshall should be punished, and I do not with
my remarks to be construed that way.

From sm@resistor.net  Thu Oct 25 13:13: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 4967F21F88CD for <ietf@ietfa.amsl.com>; Thu, 25 Oct 2012 13:13:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.589
X-Spam-Level: 
X-Spam-Status: No, score=-102.589 tagged_above=-999 required=5 tests=[AWL=0.010, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EFsMjgPwcGqY for <ietf@ietfa.amsl.com>; Thu, 25 Oct 2012 13:13:30 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2733121F88CA for <ietf@ietf.org>; Thu, 25 Oct 2012 13:13:29 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id q9PKDKwR017616; Thu, 25 Oct 2012 13:13:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1351196006; bh=CWUeeJOQXQ5GC8wJ/KjnRMXMqkOEWAkXsvqAbgkL9e4=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=JXNYxo59NqRnXHzEQyDe5qU6xuPeIeKNQSeL8Hr7p0iY2/ieCJwisGzMRWrcIgGs/ 7YSmw0a3DBwhFnZEX4Dd8XBTRb1AUOJ6S8vSFAcdsBFp2X9ay9BO/IpMvdGLNXfMfH qcBL+Xkh3E4mDPpIigjOH3PLwL2Y9hZs68evLm3g=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1351196006; i=@resistor.net; bh=CWUeeJOQXQ5GC8wJ/KjnRMXMqkOEWAkXsvqAbgkL9e4=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=mbVWlGT7Cy3xfKtMEvVyMJPpNQ5oDQkjDDqofltS/LovEM0nZiaSTylEO6i+EpGIt YrEJyldSTViR5peadoXjlsAldANZeTF7If2nQ/sQB3e+bkI2CCzXvWPALoJxVxqIxn 0+IQeQr54/BKV8cnONif2larQn8WByEIPdOqUyWc=
Message-Id: <6.2.5.6.2.20121025122654.0a1e79e8@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 25 Oct 2012 13:11:31 -0700
To: John C Klensin <john-ietf@jck.com>
From: SM <sm@resistor.net>
Subject: Re: Hasty procedural changes (was: Re: [RFC 3777 Update for Vacancies])
In-Reply-To: <58AF646D478492278E715428@JcK-HP8200.jck.com>
References: <D90D92A7-0906-4620-93A0-D116D15A10FA@gmail.com> <CAC4RtVAj5MV3uZN02b0DECes+MZaA6681D46aN5z5XaMDnoWAg@mail.gmail.com> <58AF646D478492278E715428@JcK-HP8200.jck.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: Bob Hinden <bob.hinden@gmail.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Oct 2012 20:13:35 -0000

Hi John,
At 08:03 25-10-2012, John C Klensin wrote:
>(ii) The IESG could use its implied authority to interpret RFC
>2026 (an authority it has at least implicitly applied many times
>in the past).  It could interpret the 2026 variance procedure as
>applying to all bodies to which 2026 applies, whether they were
>created earlier enough to be enumerated in 2026 or not.  (FWIW,
>I personally believe that interpretation would be correct
>relative to the intentions 16 years ago.)  That procedure could
>then be used to treat the current situation as a resignation
>without creating any unfortunate precedents.

Yes.

RFC 4333 could also be used:

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

Please note that a member recall requires a signed petition by at 
least 20 people.  It does not require the approval of the IAOC or the 
IESG.  As such, nobody is stopping anyone from doing that.

Regards,
-sm 


From alh-ietf@tndh.net  Thu Oct 25 13:19:33 2012
Return-Path: <alh-ietf@tndh.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4133B21F8531 for <ietf@ietfa.amsl.com>; Thu, 25 Oct 2012 13:19:33 -0700 (PDT)
X-Quarantine-ID: <cpCE94QrsJgL>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Improper folded header field made up entirely of whitespace (char 20 hex): X-Spam-Report: ...that system for details.\n \n Content previ[...]
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cpCE94QrsJgL for <ietf@ietfa.amsl.com>; Thu, 25 Oct 2012 13:19:32 -0700 (PDT)
Received: from express.tndh.net (express.tndh.net [IPv6:2001:470:e930:1240:20d:56ff:fe04:4c0a]) by ietfa.amsl.com (Postfix) with ESMTP id 8945D21F84DF for <ietf@ietf.org>; Thu, 25 Oct 2012 13:19:32 -0700 (PDT)
Received: from [172.20.144.31] (helo=eaglet) by express.tndh.net with esmtp (Exim 4.72 (FreeBSD)) (envelope-from <alh-ietf@tndh.net>) id 1TRTtl-000IPP-Um; Thu, 25 Oct 2012 13:19:31 -0700
From: "Tony Hain" <alh-ietf@tndh.net>
To: "'Andrew Sullivan'" <ajs@anvilwalrusden.com>, <ietf@ietf.org>
References: <20121025185724.9CACF18C0A0@mercury.lcs.mit.edu>	<508990E4.9040809@dougbarton.us> <20121025195057.GA55999@mx1.yitter.info>
In-Reply-To: <20121025195057.GA55999@mx1.yitter.info>
Subject: RE: Exceptional cases (was: don't overthink)
Date: Thu, 25 Oct 2012 13:19:26 -0700
Message-ID: <001301cdb2ee$0780e220$1682a660$@tndh.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQJTDK6t1rDy6kcDW38/cj1FgQKf2wGezyPkAgjbZx2WooIgEA==
Content-Language: en-us
X-SA-Exim-Connect-IP: 172.20.144.31
X-SA-Exim-Mail-From: alh-ietf@tndh.net
X-SA-Exim-Scanned: No (on express.tndh.net); SAEximRunCond expanded to 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: Thu, 25 Oct 2012 20:19:33 -0000

Andrew Sullivan wrote:
> 
> On Thu, Oct 25, 2012 at 12:20:04PM -0700, Doug Barton wrote:
> > would be wrong. The idea here is that applying _punitive_ action (such
> > as removal from a position) retroactively is not "fair,"
> 
> Oh, for heaven's sake.  This is nothing to do with punishment.  This is a
> straightforward administrative problem.  Turning this into an opportunity
to
> exercise a heavyweight and in fact punitive process would be an injustice.
If
> the IETF has wound itself into such bureaucratic knots that we can't just
> make an exceptional decision in exceptional circumstances, we are in much
> worse trouble than I thought.

Clearly the IAOC is inadequately staffed if one person missing for an
extended period is inhibiting their activities. Beyond that, in this
specific case, someone needs to ask counsel about the issues StJohns raised.
Logic and common sense have no utility in the legal system, so making
arguments in favor of a logical outcome are simply a waste of time. 

We have already wasted 2 days of the procedurally defined recall, so if it
is so urgent that the position gets filled, that should have already
started. Clearly this is not urgent because people would rather argue about
why the defined process is too much of a burden, and won't take the simple
step of asking counsel for an opinion on concrete legal concerns. 

Since observed behavior shows this is not urgent, then take the next 6 weeks
to define a new process, then another 6 weeks to demonstrate vacancy after
the new process is defined, then another 6 weeks to find and vet the
replacement.  If you really want it done faster than that, start the defined
recall now and stop arguing why it is overkill. 

Tony



From jnc@mercury.lcs.mit.edu  Thu Oct 25 13:26:34 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 F1F7321F881E for <ietf@ietfa.amsl.com>; Thu, 25 Oct 2012 13:26:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.483
X-Spam-Level: 
X-Spam-Status: No, score=-6.483 tagged_above=-999 required=5 tests=[AWL=0.116,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iuGOLiAlEz8q for <ietf@ietfa.amsl.com>; Thu, 25 Oct 2012 13:26:28 -0700 (PDT)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id D0D7221F879C for <ietf@ietf.org>; Thu, 25 Oct 2012 13:26:28 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 52CD118C0B3; Thu, 25 Oct 2012 16:26:28 -0400 (EDT)
To: ietf@ietf.org
Subject: Re: don't overthink, was Just so I'm clear
Message-Id: <20121025202628.52CD118C0B3@mercury.lcs.mit.edu>
Date: Thu, 25 Oct 2012 16:26:28 -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, 25 Oct 2012 20:26:34 -0000

    > From: Doug Barton <dougb@dougbarton.us>

    > Removal from office _is_ considered a punitive action

Sorry all, but my bogometer just blew out.

He isn't being turfed out of his post (in a high-level sense); he quit.

He simply wasn't polite or thoughtful enough to do so formally, instead of by
just going catatonic on us.

It's very rude to do that. If he's going to bail, he ought to have the decency
to summon the strength needed to say 'I quit'. That's not a long or involved
communication, and unless he's completely catatonic, to the point of being
institutionalized, he should be able to manage that, at least.

I know whereof I speak, having been through some bad meltdowns myself, so
much as I have great _personal_ sympathy for him (knowing what he must be
going through to act like this), _institutionally_, I don't.

Anyway, in view of that failure on his part, I would recommend that he never,
ever, be considered for _any_ post in the I*, ever again. People who can do
that sort of thing shouldn't be trusted with any responsibility ever again.

And now, yes, I _am_ being punitive.

Because I'm ticked off at the amount of time/energy being wasted in this
incredible stupidity, and the ridiculous, petty-fogging amateur legalisms
which are being thrown around like the chicken-feed they are. This probably
means that he's paying the price for other people's actions, but since when
did life come with a 'fair' guarantee tag?

	Noel

From dougb@dougbarton.us  Thu Oct 25 13:44:08 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 5D5EE21F848F for <ietf@ietfa.amsl.com>; Thu, 25 Oct 2012 13:44:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.49
X-Spam-Level: 
X-Spam-Status: No, score=-3.49 tagged_above=-999 required=5 tests=[AWL=0.109,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id if6ELphxDaJe for <ietf@ietfa.amsl.com>; Thu, 25 Oct 2012 13:44:07 -0700 (PDT)
Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by ietfa.amsl.com (Postfix) with ESMTP id 9FB3221F8862 for <ietf@ietf.org>; Thu, 25 Oct 2012 13:44:07 -0700 (PDT)
Received: (qmail 388 invoked by uid 399); 25 Oct 2012 20:43:52 -0000
Received: from unknown (HELO ?192.168.0.102?) (dougb@dougbarton.us@12.207.105.210) by mail2.fluidhosting.com with ESMTPAM; 25 Oct 2012 20:43:52 -0000
X-Originating-IP: 12.207.105.210
X-Sender: dougb@dougbarton.us
Message-ID: <5089A493.6050106@dougbarton.us>
Date: Thu, 25 Oct 2012 13:44:03 -0700
From: Doug Barton <dougb@dougbarton.us>
Organization: http://SupersetSolutions.com/
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121010 Thunderbird/16.0.1
MIME-Version: 1.0
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Subject: Re: don't overthink, was Just so I'm clear
References: <20121025202628.52CD118C0B3@mercury.lcs.mit.edu>
In-Reply-To: <20121025202628.52CD118C0B3@mercury.lcs.mit.edu>
X-Enigmail-Version: 1.4.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: Thu, 25 Oct 2012 20:44:08 -0000

On 10/25/2012 1:26 PM, Noel Chiappa wrote:
>> From: Doug Barton <dougb@dougbarton.us>
> 
>> Removal from office _is_ considered a punitive action

Noel, you have a very bad habit of replying to snippets out of context.
Personally I don't appreciate it, as the snippet above could lead
someone to believe that what I said above means something very different
than what it actually meant in the context of my post.

Trimming quotes in responses is reasonable (I've done it in this one),
and arguably not practiced often (or well) enough. Taking the most
inflammatory bits out of context is neither useful nor appropriate.

> Sorry all, but my bogometer just blew out.
> 
> He isn't being turfed out of his post (in a high-level sense); he
> quit.

Yes, I fully understand that that is your argument. Some of us disagree.
Vive le difference. :)

> He simply wasn't polite or thoughtful enough to do so formally,
> instead of by just going catatonic on us.

Without any personal knowledge of his circumstances, I'm not prepared to
judge him.

> Because I'm ticked off at the amount of time/energy being wasted in
> this incredible stupidity, and the ridiculous, petty-fogging amateur
> legalisms which are being thrown around like the chicken-feed they
> are. 

This kind of ad hominem attack has no place in the IETF. You are
perfectly free to disagree with me, but that doesn't give you the right
to cast aspersions regarding the quality of, or motives behind my
contribution.

In fact, the _only_ reason I have spent so much time on this is that I
think it's an incredibly important question. Are we going to be an
organization that follows its own procedures, or are we going to treat
every written word as a guideline, which can be freely interpreted as
the occasion dictates?

Taking the latter course may be expedient, but IMO it has far-reaching
implications that will do far more harm to the organization than good.

Doug

From mstjohns@comcast.net  Thu Oct 25 13:49:16 2012
Return-Path: <mstjohns@comcast.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 00F3721F84BB for <ietf@ietfa.amsl.com>; Thu, 25 Oct 2012 13:49:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.324
X-Spam-Level: 
X-Spam-Status: No, score=-100.324 tagged_above=-999 required=5 tests=[AWL=0.113, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qsrJLkp5j0iJ for <ietf@ietfa.amsl.com>; Thu, 25 Oct 2012 13:49:15 -0700 (PDT)
Received: from qmta02.westchester.pa.mail.comcast.net (qmta02.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:24]) by ietfa.amsl.com (Postfix) with ESMTP id 6C09621F8491 for <ietf@ietf.org>; Thu, 25 Oct 2012 13:49:15 -0700 (PDT)
Received: from omta24.westchester.pa.mail.comcast.net ([76.96.62.76]) by qmta02.westchester.pa.mail.comcast.net with comcast id FN1A1k0041ei1Bg51YpKqc; Thu, 25 Oct 2012 20:49:19 +0000
Received: from Mike-T530.comcast.net ([68.83.212.126]) by omta24.westchester.pa.mail.comcast.net with comcast id FYpC1k01L2kB7pQ3kYpDNw; Thu, 25 Oct 2012 20:49:13 +0000
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Thu, 25 Oct 2012 16:49:15 -0400
To: jnc@mercury.lcs.mit.edu (Noel Chiappa),ietf@ietf.org
From: Michael StJohns <mstjohns@comcast.net>
Subject: Re: don't overthink, was Just so I'm clear
In-Reply-To: <20121025125351.285D818C0A0@mercury.lcs.mit.edu>
References: <20121025125351.285D818C0A0@mercury.lcs.mit.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Message-Id: <20121025204915.6C09621F8491@ietfa.amsl.com>
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, 25 Oct 2012 20:49:16 -0000

At 08:53 AM 10/25/2012, Noel Chiappa wrote:
>We're all agreed that the IETF in plenary mode (i.e. all of us) can change
>any/all policy/procedures, right?

Actually, that's my point here.

Once upon a time, we did everything by group hum.  Then we became a standards body with formal procedures and gave up the power to change any/all policy/procedures by just wishing they were changed.

As I see it, with respect to this "problem" -

The IAOC has no power to declare the position vacant.  They know this, and that's why they sent a note to the list asking for "permission".

But - the IETF may do one of two things:
   1) It may change the procedure/policy by using the existing defined procedures and policies and THEN follow the new procedure policy. 
or
   2) It may initiate the recall procedures.

AFAIK the IETF "plenary" does not have the powers you suggest it has.

Mike



From mstjohns@comcast.net  Thu Oct 25 13:56:12 2012
Return-Path: <mstjohns@comcast.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4F2E121F8595 for <ietf@ietfa.amsl.com>; Thu, 25 Oct 2012 13:56:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.336
X-Spam-Level: 
X-Spam-Status: No, score=-100.336 tagged_above=-999 required=5 tests=[AWL=0.101, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4KrQyZTQ4FJe for <ietf@ietfa.amsl.com>; Thu, 25 Oct 2012 13:56:11 -0700 (PDT)
Received: from qmta03.westchester.pa.mail.comcast.net (qmta03.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:32]) by ietfa.amsl.com (Postfix) with ESMTP id 587DD21F8592 for <ietf@ietf.org>; Thu, 25 Oct 2012 13:56:11 -0700 (PDT)
Received: from omta03.westchester.pa.mail.comcast.net ([76.96.62.27]) by qmta03.westchester.pa.mail.comcast.net with comcast id FY221k00o0bG4ec53YwFiB; Thu, 25 Oct 2012 20:56:15 +0000
Received: from Mike-T530.comcast.net ([68.83.212.126]) by omta03.westchester.pa.mail.comcast.net with comcast id FYvx1k00B2kB7pQ3PYvxtx; Thu, 25 Oct 2012 20:55:58 +0000
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Thu, 25 Oct 2012 16:56:11 -0400
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Doug Barton <dougb@dougbarton.us>
From: Michael StJohns <mstjohns@comcast.net>
Subject: Re: Just so I'm clear
In-Reply-To: <5088EE5A.4090103@gmail.com>
References: <20121023192135.203AC18C0A4@mercury.lcs.mit.edu> <5086EF82.9060900@dougbarton.us> <20121023200713.GC1861@nsn.com> <5086FBCE.2070503@dougbarton.us> <20121023213251.GF27557@verdi> <50873AB4.1000905@dougbarton.us> <20121024034736.GC52558@crankycanuck.ca> <50876D39.20502@dougbarton.us> <508773E7.10203@cisco.com> <50877633.1000402@dougbarton.us> <EA9BEA2E-EE96-4E80-B719-652BBD620A79@lilacglade.org> <508842C2.4020203@dougbarton.us> <5088EE5A.4090103@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Message-Id: <20121025205611.587DD21F8592@ietfa.amsl.com>
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Oct 2012 20:56:12 -0000

At 03:46 AM 10/25/2012, Brian E Carpenter wrote:
>On 24/10/2012 20:34, Doug Barton wrote:
>...
>> ... Nothing in the text suggests an
>> unfettered right of creating new definitions of "vacant."
>
>You mean, new compared to the first definition in Merriam-Webster.com?
>
>1: not occupied by an incumbent, possessor, or officer <a vacant office> <vacant thrones>
>
>Objectively and factually, that seems to be the case. 

The objective facts of the case are that Marshall is non-responsive and has not attended some number of meetings and teleconferences. Period.

To put a very specific point on this - in the real world, people get shot, or are other wise hurt and end up in coma's and are otherwise unable to fulfill the responsibilities of their office, and unless and until they resign from office or are removed by defined procedures, they remain the incumbent.

I can list at least a few examples from American politics if you desire.  In the academic world, a tenured named position does not become vacant when the incumbent goes on sabatical.  If there are administrative responsibilities associated with the position, generally the organization has defined procedures to deal with the absence.  



>The IAOC is actually
>going an extra mile rather than simply informing NomCom that the seat
>has become vacant.
>
>    Brian



From melinda.shore@gmail.com  Thu Oct 25 14:08:51 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 EB2C421F86B0 for <ietf@ietfa.amsl.com>; Thu, 25 Oct 2012 14:08:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9CiEwaDCFQI0 for <ietf@ietfa.amsl.com>; Thu, 25 Oct 2012 14:08:51 -0700 (PDT)
Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id 77DBC21F86A9 for <ietf@ietf.org>; Thu, 25 Oct 2012 14:08:51 -0700 (PDT)
Received: by mail-pb0-f44.google.com with SMTP id ro8so2279417pbb.31 for <ietf@ietf.org>; Thu, 25 Oct 2012 14:08:51 -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=++NX1nSA8+pAaRnruiZARe45rWQ6V0rQg9eC3Hvjpjo=; b=AF+Bro2kPfo8YWr/5Jc17pko0laISOuvymbhlJPEqQliUpMTrWIJ6HuqGj0JF707Vy JGSKN2lBgxkd43E3REAxmhMk0ZHec+3k55y3OpLbBA6JJaDCvebjZBdWu266Kx4B0x7M xtaL9JcelKxHkw7JG8sPHM41EULq4DlH665HjMvZEMr1cirDxohqLe5qBQ+3xz/54d+b c5hgB91AfpihUhXm868E9hzPr/K6Tz7ccIIcWQlwa/rhEXXRvzleJWqNbrFCQPSb+9g2 KQdlF5pWqYF9H4b5I3GEsN97Dz8I5zd+QrTTNSJfrIjNQ1K/xbXPeI/ALYFFiW5xURJs iSYA==
Received: by 10.68.223.37 with SMTP id qr5mr63585332pbc.101.1351199331199; Thu, 25 Oct 2012 14:08:51 -0700 (PDT)
Received: from spandex.local (216-67-49-109-rb1.fai.dsl.dynamic.acsalaska.net. [216.67.49.109]) by mx.google.com with ESMTPS id mn5sm11753965pbc.12.2012.10.25.14.08.49 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 25 Oct 2012 14:08:50 -0700 (PDT)
Message-ID: <5089AA60.3060405@gmail.com>
Date: Thu, 25 Oct 2012 13:08:48 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:16.0) Gecko/20121010 Thunderbird/16.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Just so I'm clear
References: <20121023192135.203AC18C0A4@mercury.lcs.mit.edu> <5086EF82.9060900@dougbarton.us> <20121023200713.GC1861@nsn.com> <5086FBCE.2070503@dougbarton.us> <20121023213251.GF27557@verdi> <50873AB4.1000905@dougbarton.us> <20121024034736.GC52558@crankycanuck.ca> <50876D39.20502@dougbarton.us> <508773E7.10203@cisco.com> <50877633.1000402@dougbarton.us> <EA9BEA2E-EE96-4E80-B719-652BBD620A79@lilacglade.org> <508842C2.4020203@dougbarton.us> <5088EE5A.4090103@gmail.com> <20121025205611.587DD21F8592@ietfa.amsl.com>
In-Reply-To: <20121025205611.587DD21F8592@ietfa.amsl.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Oct 2012 21:08:52 -0000

On 10/25/12 12:56 PM, Michael StJohns wrote:
> To put a very specific point on this - in the real world, people get
> shot, or are other wise hurt and end up in coma's and are otherwise
> unable to fulfill the responsibilities of their office, and unless
> and until they resign from office or are removed by defined
> procedures, they remain the incumbent.
> 
> I can list at least a few examples from American politics if you
> desire.  In the academic world, a tenured named position does not
> become vacant when the incumbent goes on sabatical.  If there are
> administrative responsibilities associated with the position,
> generally the organization has defined procedures to deal with the
> absence.

I don't think that these are in any way analogous, since in each
case that you mentioned the individual who left was either incapacitated
or had pre-arranged an absence.  If someone simply disappeared from
work without notice or comment I expect it would be handled rather
differently.

It's not at all clear to me that a recall actually is required, but
it seems to me that in the interest of getting this resolved one
should be started.  Soon.  Now, if possible.

Melinda


From mstjohns@comcast.net  Thu Oct 25 14:27:11 2012
Return-Path: <mstjohns@comcast.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0B54D21F869B for <ietf@ietfa.amsl.com>; Thu, 25 Oct 2012 14:27:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.347
X-Spam-Level: 
X-Spam-Status: No, score=-100.347 tagged_above=-999 required=5 tests=[AWL=0.090, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xdS14p-Z-UzK for <ietf@ietfa.amsl.com>; Thu, 25 Oct 2012 14:27:10 -0700 (PDT)
Received: from qmta13.westchester.pa.mail.comcast.net (qmta13.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:44:76:96:59:243]) by ietfa.amsl.com (Postfix) with ESMTP id 83BCF21F85C0 for <ietf@ietf.org>; Thu, 25 Oct 2012 14:27:10 -0700 (PDT)
Received: from omta20.westchester.pa.mail.comcast.net ([76.96.62.71]) by qmta13.westchester.pa.mail.comcast.net with comcast id FQTB1k0061YDfWL5DZTENm; Thu, 25 Oct 2012 21:27:14 +0000
Received: from Mike-T530.comcast.net ([68.83.212.126]) by omta20.westchester.pa.mail.comcast.net with comcast id FZSJ1k00E2kB7pQ3gZSKxn; Thu, 25 Oct 2012 21:26:19 +0000
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Thu, 25 Oct 2012 17:27:10 -0400
To: Melinda Shore <melinda.shore@gmail.com>,ietf@ietf.org
From: Michael StJohns <mstjohns@comcast.net>
Subject: Re: Just so I'm clear
In-Reply-To: <5089AA60.3060405@gmail.com>
References: <20121023192135.203AC18C0A4@mercury.lcs.mit.edu> <5086EF82.9060900@dougbarton.us> <20121023200713.GC1861@nsn.com> <5086FBCE.2070503@dougbarton.us> <20121023213251.GF27557@verdi> <50873AB4.1000905@dougbarton.us> <20121024034736.GC52558@crankycanuck.ca> <50876D39.20502@dougbarton.us> <508773E7.10203@cisco.com> <50877633.1000402@dougbarton.us> <EA9BEA2E-EE96-4E80-B719-652BBD620A79@lilacglade.org> <508842C2.4020203@dougbarton.us> <5088EE5A.4090103@gmail.com> <20121025205611.587DD21F8592@ietfa.amsl.com> <5089AA60.3060405@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Message-Id: <20121025212710.83BCF21F85C0@ietfa.amsl.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Oct 2012 21:27:11 -0000

At 05:08 PM 10/25/2012, Melinda Shore wrote:
>don't think that these are in any way analogous, since in each
>case that you mentioned the individual who left was either incapacitated
>or had pre-arranged an absence.  If someone simply disappeared from
>work without notice or comment I expect it would be handled rather
>differently.

Professor A does not return from Sabbatical at the time he had previously indicated.  He is not reachable.

Congresswoman B goes into 90 day rehab suddenly.  Her staff says only that she's unavailable.  At the end of 90 days, she extends for another month.

I can go on.

We know that Marshall is unresponsive for a while and that is the ONLY fact we have.  We suspect (from the 2nd party Facebook conversation) that we know why.  But the truth may be (and probably is) somewhat different.


Later, Mike




From iad@ietf.org  Thu Oct 25 15:04:44 2012
Return-Path: <iad@ietf.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 56B4621F8578; Thu, 25 Oct 2012 15:04: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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mxY2vr1lsSGw; Thu, 25 Oct 2012 15:04:43 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E9A7A21F8562; Thu, 25 Oct 2012 15:04:43 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: IETF Administrative Director <iad@ietf.org>
To: IETF Announcement List <ietf-announce@ietf.org>
Subject: Draft Network Services RFP for Community Comment
X-Test-IDTracker: no
X-IETF-IDTracker: 4.34
Message-ID: <20121025220443.5845.46565.idtracker@ietfa.amsl.com>
Date: Thu, 25 Oct 2012 15:04:43 -0700
Cc: iaoc@ietf.org, iab@iab.org, ietf@ietf.org, wgchairs@ietf.org, iesg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Oct 2012 22:04:44 -0000

The IAOC is seeking community input on a proposed Network Services Request =
for Proposal.  The =

successful bidder(s) will have the opportunity to compete for delivering ne=
twork services at IETF meetings.

The IAOC has decided that it wants to issue a Network Services RFP during t=
he current one-year extension =

that VeriLan is working under to see whether it can identify other qualifie=
d providers, provide for a =

backup for VeriLan, and maybe introduce some competition and competitive pr=
ices for these services.

The RFP is located here under the Community Review section:
<http://iaoc.ietf.org/rfpsrfis.html>

Comments to the Tools Management Committee at tmc@ietf-bids.org provided by=
 5:00 PM EST 6 =

November 2012 will be considered.

Proposed RFP Schedule

0.  Community review October 26 - November 6, 2012
1.  IAOC approves RFP for publication November 7, 2012
2. RFP Issued by email:  November 8, 2012.
3. Proposal submitted by email due no later than 5 PM EST
4. Proposal Review Period:  December 11 - 21, 2012.
5. Notification of selection:  January 3, 2013
6. Contract Negotiation and Agreement:  January 7 - 21, 2013.
7. Contract Accepted:  February 7, 2013.
8. Contract Commencement: March 1, 2013.

We appreciate your insight.  Thanks

Ray Pelletier
IETF Administrative Director





From sob@sobco.com  Thu Oct 25 15:08:27 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 E1E7F21F85E7 for <ietf@ietfa.amsl.com>; Thu, 25 Oct 2012 15:08:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.495
X-Spam-Level: 
X-Spam-Status: No, score=-0.495 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7iQnwC76tBND for <ietf@ietfa.amsl.com>; Thu, 25 Oct 2012 15:08:27 -0700 (PDT)
Received: from sobco.sobco.com (unknown [136.248.127.164]) by ietfa.amsl.com (Postfix) with ESMTP id 60C0E21F8589 for <ietf@ietf.org>; Thu, 25 Oct 2012 15:08:27 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by sobco.sobco.com (Postfix) with ESMTP id 616EC2B99EB; Thu, 25 Oct 2012 18:08:26 -0400 (EDT)
X-Virus-Scanned: amavisd-new at sobco.com
Received: from sobco.sobco.com ([127.0.0.1]) by localhost (sobco.sobco.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bVhBPXpLWsEr; Thu, 25 Oct 2012 18:08:25 -0400 (EDT)
Received: from dhcp-223-244.meetings.nanog.org (dhcp-223-244.meetings.nanog.org [199.187.223.244]) by sobco.sobco.com (Postfix) with ESMTPSA id 400CE2B99DC; Thu, 25 Oct 2012 18:08:25 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: Hasty procedural changes (was: Re: [RFC 3777 Update for Vacancies])
From: Scott O Bradner <sob@sobco.com>
In-Reply-To: <58AF646D478492278E715428@JcK-HP8200.jck.com>
Date: Thu, 25 Oct 2012 18:08:23 -0400
Content-Transfer-Encoding: 7bit
Message-Id: <A1EED41B-6D7F-4E2F-AB24-AFA6BF9D9808@sobco.com>
References: <D90D92A7-0906-4620-93A0-D116D15A10FA@gmail.com> <CAC4RtVAj5MV3uZN02b0DECes+MZaA6681D46aN5z5XaMDnoWAg@mail.gmail.com> <58AF646D478492278E715428@JcK-HP8200.jck.com>
To: John C Klensin <john-ietf@jck.com>
X-Mailer: Apple Mail (2.1499)
Cc: Barry Leiba <barryleiba@computer.org>, Bob Hinden <bob.hinden@gmail.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Oct 2012 22:08:28 -0000

On Oct 25, 2012, at 11:03 AM, John C Klensin <john-ietf@jck.com> wrote:
> (ii) The IESG could use its implied authority to interpret RFC
> 2026 (an authority it has at least implicitly applied many times
> in the past).  It could interpret the 2026 variance procedure as
> applying to all bodies to which 2026 applies, whether they were
> created earlier enough to be enumerated in 2026 or not.  (FWIW,
> I personally believe that interpretation would be correct
> relative to the intentions 16 years ago.)  That procedure could
> then be used to treat the current situation as a resignation
> without creating any unfortunate precedents.

for some additional context about the variance procedure - it originally 
came from RFC 1871

Scott


From iad@ietf.org  Thu Oct 25 15:38:59 2012
Return-Path: <iad@ietf.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 59A0421F887A; Thu, 25 Oct 2012 15:38:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id B9Vd75y6SdQI; Thu, 25 Oct 2012 15:38:58 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ED3D321F8727; Thu, 25 Oct 2012 15:38:58 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: IETF Administrative Director <iad@ietf.org>
To: IETF Announcement List <ietf-announce@ietf.org>
Subject: IETF Trust Chair -- 25 Oct 2012
X-Test-IDTracker: no
X-IETF-IDTracker: 4.34
Message-ID: <20121025223858.8296.34327.idtracker@ietfa.amsl.com>
Date: Thu, 25 Oct 2012 15:38:58 -0700
Cc: iaoc@ietf.org, iab@iab.org, 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, 25 Oct 2012 22:38:59 -0000

The Trustees of the IETF Trust took two actions today:
1.  Removed the current IETF Trust Chair
2.  Elected a new IETF Trust Chair

The Trustees passed the following resolution removing Marshal Eubanks as Tr=
ust Chair:

RESOLUTION
After consideration of the lack of participation by the Trust Chair in Trus=
t matters for a =

period in excess of two months, and the failure of the Chair to respond to =
repeated =

attempts to contact him, the Trustees hereby remove Marshall Eubanks as the=
 IETF =

Trust Chair effective 25 October at 10:15 AM EDT.

The resolution passed with seven of the nine votes, with two absentees, whi=
ch included
Marshall.  =


The Trustees took this action pursuant to the authority in the Trust Admini=
strative =

Procedures (adopted 4-17-08) <http://trustee.ietf.org/docs/Trust_Procedures=
_2008.pdf>, which states:

	The Chair serves at the pleasure of the Trustees and may be removed from t=
hat
	position at any time by the Trustees.

Notice of the Trust meeting and its Agenda that specifically included Trust=
 Chair =

Removal Vote was sent to all Trustees  on October 12, 2012.

Following this action the Trustees elected Ole Jacobsen as the Chair of the=
 IETF Trust =

for the remainder of the term of Marshall Eubanks, that is, until March 13,=
 2013.  =

We appreciate Ole's volunteering for this position.

The Trustees thank Marshall for his contribution to the Trust as a Trustee =
and as an
 active, effective Chair from March 2009 through August 4, 2012.  His contr=
ibution =

will be missed.

Ray Pelletier
Trustee


From listsebby@me.com  Thu Oct 25 15:50:07 2012
Return-Path: <listsebby@me.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E4D4121F869F for <ietf@ietfa.amsl.com>; Thu, 25 Oct 2012 15:50:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.199
X-Spam-Level: 
X-Spam-Status: No, score=-3.199 tagged_above=-999 required=5 tests=[AWL=0.400,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7Ss+7dcqQge2 for <ietf@ietfa.amsl.com>; Thu, 25 Oct 2012 15:50:07 -0700 (PDT)
Received: from nk11p04mm-asmtp007.mac.com (nk11p04mm-asmtpout007.mac.com [17.158.236.242]) by ietfa.amsl.com (Postfix) with ESMTP id 47E0721F867C for <ietf@ietf.org>; Thu, 25 Oct 2012 15:50:07 -0700 (PDT)
MIME-version: 1.0
Content-type: text/plain; charset=windows-1252
Received: from [192.168.1.5] (natbox.sabahattin-gucukoglu.com [213.123.192.30]) by nk11p04mm-asmtp007.mac.com (Oracle Communications Messaging Server 7u4-24.01(7.0.4.24.0) 64bit (built Jan 3 2012)) with ESMTPSA id <0MCH00MCB0RE7K20@nk11p04mm-asmtp007.mac.com> for ietf@ietf.org; Thu, 25 Oct 2012 22:50:07 +0000 (GMT)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.7.7855,1.0.431,0.0.0000 definitions=2012-10-25_04:2012-10-25, 2012-10-25, 1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 ipscore=0 suspectscore=0 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=6.0.2-1203120001 definitions=main-1210250304
Subject: Re: the usual mail stuff, was IETF...the unconference of SDOs
From: Sabahattin Gucukoglu <listsebby@me.com>
In-reply-to: <20120909192557.33735.qmail@joyce.lan>
Date: Thu, 25 Oct 2012 23:50:02 +0100
Content-transfer-encoding: quoted-printable
Message-id: <C0F92EF7-8923-45E6-AB2E-FAEB40A6DFC9@me.com>
References: <20120909192557.33735.qmail@joyce.lan>
To: John Levine <johnl@taugh.com>
X-Mailer: Apple Mail (2.1499)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Oct 2012 22:50:08 -0000

Wo!  There's a whole section of the conversation that ended up in =
"Untidy" that shouldn't've.

On 9 Sep 2012, at 20:25, John Levine <johnl@taugh.com> wrote:
> I have to say that I'm baffled at the perverse pride that people seem
> to take in being so technically backward that they're unable to handle
> the mail that 99% of the world uses today.  While not being a fan of
> overdecorated HTML and endless font changes, and strongly preferring a
> mail program that lets me keep my fingers on the keyboard, I can deal
> with it.  (I use Alpine, keep meaning to take another look at mutt.)

This sort of modernist attitude only really works while you're not =
recovering mail from mbox files using less.  Or, in general, while you =
need to do as little work as possible to redisplay or process a message. =
 Not to say you're point isn't essentially valid--we must, of course, be =
aware of the current trends--but popularity doesn't mean correct for the =
group of people genuinely preferring low-overhead or "Technically =
backward" MUAs, pagers, scripts, etc.  Those people got there first and =
have a pretty good leverage for screaming at other people who got there =
later, and failed to regard those others not like themselves by =
flagrantly ignoring standards which would have guaranteed =
interoperability had they not done so, particularly when the primary =
motivation for doing so is ease of implementation with a fundamentally =
different UI paradigm.

Keep using alpine.  Move to mutt and you'll get pretty plus-signs in the =
left column of wrapped mail--that is, unless mutt has also worked around =
this type of breakage (doubtful, they're a pretty puritanical bunch :-) =
).  But mutt has maildir+ support where alpine doesn't without a load of =
controversial patching, and so while I'm using alpine now it's only =
because I go through Dovecot as intermediary or use external IMAP =
servers.  (Yes, free email providers accessed through IMAP/SMTP in =
textmode as opposed to /usr/sbin/sendmail are cool when they come from =
Apple.  They're =85 all shiny. :-) )

> For the large majority of mail that is written in paragraphs rather
> than tables, line wrapping is a useful feature, regardless of the
> character set, particularly for those of us who sometimes read our
> mail on a tablet or phone while changing planes.  For mail that is a
> table and stuff has to line up in columns, use HTML tables. That's
> what they're for.
>=20
And Format=3DFlowed takes care of the first requirement.  =
Multipart/alternative takes care of the latter (when inventive =
multi-line columns will not suffice) (and they don't, with small-screen =
devices).

> PS: Yes, this is top posted.  You can deal with that, too.

This message bottom-posted for your reading convenience, as opposed to =
my laziness.  It'll render beautifully in alpine, I'm sure. :-)

Cheers,
Sabahattin


From hartmans@mit.edu  Thu Oct 25 15:51:51 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 065A021F8727 for <ietf@ietfa.amsl.com>; Thu, 25 Oct 2012 15:51:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.454
X-Spam-Level: 
X-Spam-Status: No, score=-100.454 tagged_above=-999 required=5 tests=[AWL=2.145, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id au-m7BLLrXyT for <ietf@ietfa.amsl.com>; Thu, 25 Oct 2012 15:51:50 -0700 (PDT)
Received: from mail.painless-security.com (mail.painless-security.com [23.30.188.241]) by ietfa.amsl.com (Postfix) with ESMTP id A53E521F86D6 for <ietf@ietf.org>; Thu, 25 Oct 2012 15:51:42 -0700 (PDT)
Received: from carter-zimmerman.suchdamage.org (c-98-217-126-210.hsd1.ma.comcast.net [98.217.126.210]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.painless-security.com (Postfix) with ESMTPS id E5A792003E; Thu, 25 Oct 2012 18:51:12 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id EA8B4412A; Thu, 25 Oct 2012 18:51:39 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: Michael StJohns <mstjohns@comcast.net>
Subject: Re: don't overthink, was Just so I'm clear
References: <20121025125351.285D818C0A0@mercury.lcs.mit.edu> <20121025204915.6C09621F8491@ietfa.amsl.com>
Date: Thu, 25 Oct 2012 18:51:39 -0400
In-Reply-To: <20121025204915.6C09621F8491@ietfa.amsl.com> (Michael StJohns's message of "Thu, 25 Oct 2012 16:49:15 -0400")
Message-ID: <tslhapi5fno.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: Noel Chiappa <jnc@mercury.lcs.mit.edu>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Oct 2012 22:51:51 -0000

>>>>> "Michael" == Michael StJohns <mstjohns@comcast.net> writes:

    Michael> At 08:53 AM 10/25/2012, Noel Chiappa wrote:
    >> We're all agreed that the IETF in plenary mode (i.e. all of us)
    >> can change any/all policy/procedures, right?

    Michael> Actually, that's my point here.

    Michael> Once upon a time, we did everything by group hum.  Then we
    Michael> became a standards body with formal procedures and gave up
    Michael> the power to change any/all policy/procedures by just
    Michael> wishing they were changed.

I started to say yes to the above statement but then ran across so many
problems that I'm going to say...
No, it's quite obvious to me the IETf in plenary mode doesn't have this
power.
Foundational procedures are created by approving a BCP.
The IETf in plenary mode can reach consensus to do that but:

1) publication of an RFC on the IETF stream requires the consensus of
the IESG. Presumably if there's a strong consensus in the IETF and a
lack of consensus on the IESG, we're set up for a constitutional crisis
or a run of the recall procedure real quick.

2) IETF process documents require approval by the ISOC BOT.

3) There is a variance procedure. I've always been puzzled by it because
it seems to require exactly the same things as approving a new procedure
plus extra work.

4) I do not believe that the IETF in plenary has the ability  to choose
to ignore its procedures or to take an action that rightfully ought to
require a BCP without such a BCP.

5) We as individuals can always form IETF' and start going there instead
of IETF if we don't like the IETF. There's a bit of a high bar in
convincing ISOC,  sponsors, the ITU and others that they too want to
attend IETF' meetings and get rid of this IETF thing.


From dwm@xpasc.com  Thu Oct 25 16:00:40 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 9EA3521F86C8 for <ietf@ietfa.amsl.com>; Thu, 25 Oct 2012 16:00:40 -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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fKAC0yy8h7tY for <ietf@ietfa.amsl.com>; Thu, 25 Oct 2012 16:00:40 -0700 (PDT)
Received: from c2w3p-2.abacamail.com (c2w3p-2.abacamail.com [209.133.53.32]) by ietfa.amsl.com (Postfix) with ESMTP id 2EB5D21F8594 for <ietf@ietf.org>; Thu, 25 Oct 2012 16:00:40 -0700 (PDT)
Received: from xpasc.com (unknown [68.164.244.188]) by c2w3p-2.abacamail.com (Postfix) with ESMTP id 8A14C3FA70 for <ietf@ietf.org>; Thu, 25 Oct 2012 23:00:39 +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 q9PN0d0G022062 for <ietf@ietf.org>; Thu, 25 Oct 2012 16:00:39 -0700
Date: Thu, 25 Oct 2012 16:00:39 -0700 (PDT)
From: David Morris <dwm@xpasc.com>
To: ietf@ietf.org
Subject: Re: IETF Trust Chair -- 25 Oct 2012
In-Reply-To: <20121025223858.8296.34327.idtracker@ietfa.amsl.com>
Message-ID: <alpine.LRH.2.01.1210251559300.21823@egate.xpasc.com>
References: <20121025223858.8296.34327.idtracker@ietfa.amsl.com>
User-Agent: Alpine 2.01 (LRH 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Milter-Version: master.1+13-gbab1945
X-AV-Type: clean
X-AV-Accuracy: exact
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: ietf@ietf.org
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Oct 2012 23:00:40 -0000

Does the resolve the issue, or only move Marshall from the role of Trust 
Chair to Trustee?

On Thu, 25 Oct 2012, IETF Administrative Director wrote:

> The Trustees of the IETF Trust took two actions today:
> 1.  Removed the current IETF Trust Chair
> 2.  Elected a new IETF Trust Chair
> 
> The Trustees passed the following resolution removing Marshal Eubanks as Trust Chair:
> 
> RESOLUTION
> After consideration of the lack of participation by the Trust Chair in Trust matters for a 
> period in excess of two months, and the failure of the Chair to respond to repeated 
> attempts to contact him, the Trustees hereby remove Marshall Eubanks as the IETF 
> Trust Chair effective 25 October at 10:15 AM EDT.
> 
> The resolution passed with seven of the nine votes, with two absentees, which included
> Marshall.  
> 
> The Trustees took this action pursuant to the authority in the Trust Administrative 
> Procedures (adopted 4-17-08) <http://trustee.ietf.org/docs/Trust_Procedures_2008.pdf>, which states:
> 
> 	The Chair serves at the pleasure of the Trustees and may be removed from that
> 	position at any time by the Trustees.
> 
> Notice of the Trust meeting and its Agenda that specifically included Trust Chair 
> Removal Vote was sent to all Trustees  on October 12, 2012.
> 
> Following this action the Trustees elected Ole Jacobsen as the Chair of the IETF Trust 
> for the remainder of the term of Marshall Eubanks, that is, until March 13, 2013.  
> We appreciate Ole's volunteering for this position.
> 
> The Trustees thank Marshall for his contribution to the Trust as a Trustee and as an
>  active, effective Chair from March 2009 through August 4, 2012.  His contribution 
> will be missed.
> 
> Ray Pelletier
> Trustee
> 
> 

From rpelletier@isoc.org  Thu Oct 25 16:02:56 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 4512721F86DB for <ietf@ietfa.amsl.com>; Thu, 25 Oct 2012 16:02:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.154
X-Spam-Level: 
X-Spam-Status: No, score=-102.154 tagged_above=-999 required=5 tests=[AWL=0.049, BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vCIFhHiDT481 for <ietf@ietfa.amsl.com>; Thu, 25 Oct 2012 16:02:55 -0700 (PDT)
Received: from smtp142.ord.emailsrvr.com (smtp142.ord.emailsrvr.com [173.203.6.142]) by ietfa.amsl.com (Postfix) with ESMTP id 87B9221F8594 for <ietf@ietf.org>; Thu, 25 Oct 2012 16:02:55 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp26.relay.ord1a.emailsrvr.com (SMTP Server) with ESMTP id 0E3401C0032 for <ietf@ietf.org>; Thu, 25 Oct 2012 19:02:55 -0400 (EDT)
X-Virus-Scanned: OK
Received: by smtp26.relay.ord1a.emailsrvr.com (Authenticated sender: rpelletier-AT-isoc.org) with ESMTPSA id AFBAC1C002E for <ietf@ietf.org>; Thu, 25 Oct 2012 19:02:54 -0400 (EDT)
References: <20121025223858.8296.34327.idtracker@ietfa.amsl.com> <alpine.LRH.2.01.1210251559300.21823@egate.xpasc.com>
Mime-Version: 1.0 (1.0)
In-Reply-To: <alpine.LRH.2.01.1210251559300.21823@egate.xpasc.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-Id: <F8E6D0C0-3D7F-4310-8A99-E1B69584EE1D@isoc.org>
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-Mailer: iPhone Mail (10A403)
From: Pelletier Ray <rpelletier@isoc.org>
Subject: Re: IETF Trust Chair -- 25 Oct 2012
Date: Thu, 25 Oct 2012 19:02:50 -0400
To: "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, 25 Oct 2012 23:02:56 -0000

On Oct 25, 2012, at 7:00 PM, David Morris <dwm@xpasc.com> wrote:

>=20
> Does the resolve the issue, or only move Marshall from the role of Trust=20=

> Chair to Trustee?

The latter. Marshall is still a Trustee.=20

Ray


>=20
> On Thu, 25 Oct 2012, IETF Administrative Director wrote:
>=20
>> The Trustees of the IETF Trust took two actions today:
>> 1.  Removed the current IETF Trust Chair
>> 2.  Elected a new IETF Trust Chair
>>=20
>> The Trustees passed the following resolution removing Marshal Eubanks as T=
rust Chair:
>>=20
>> RESOLUTION
>> After consideration of the lack of participation by the Trust Chair in Tr=
ust matters for a=20
>> period in excess of two months, and the failure of the Chair to respond t=
o repeated=20
>> attempts to contact him, the Trustees hereby remove Marshall Eubanks as t=
he IETF=20
>> Trust Chair effective 25 October at 10:15 AM EDT.
>>=20
>> The resolution passed with seven of the nine votes, with two absentees, w=
hich included
>> Marshall. =20
>>=20
>> The Trustees took this action pursuant to the authority in the Trust Admi=
nistrative=20
>> Procedures (adopted 4-17-08) <http://trustee.ietf.org/docs/Trust_Procedur=
es_2008.pdf>, which states:
>>=20
>>    The Chair serves at the pleasure of the Trustees and may be removed fr=
om that
>>    position at any time by the Trustees.
>>=20
>> Notice of the Trust meeting and its Agenda that specifically included Tru=
st Chair=20
>> Removal Vote was sent to all Trustees  on October 12, 2012.
>>=20
>> Following this action the Trustees elected Ole Jacobsen as the Chair of t=
he IETF Trust=20
>> for the remainder of the term of Marshall Eubanks, that is, until March 1=
3, 2013. =20
>> We appreciate Ole's volunteering for this position.
>>=20
>> The Trustees thank Marshall for his contribution to the Trust as a Truste=
e and as an
>> active, effective Chair from March 2009 through August 4, 2012.  His cont=
ribution=20
>> will be missed.
>>=20
>> Ray Pelletier
>> Trustee
>>=20
>>=20

From listsebby@me.com  Thu Oct 25 16:43:32 2012
Return-Path: <listsebby@me.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4BB0421F8869 for <ietf@ietfa.amsl.com>; Thu, 25 Oct 2012 16:43:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.832
X-Spam-Level: 
X-Spam-Status: No, score=-4.832 tagged_above=-999 required=5 tests=[AWL=1.767,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZBSlBGX7W3hZ for <ietf@ietfa.amsl.com>; Thu, 25 Oct 2012 16:43:31 -0700 (PDT)
Received: from nk11p04mm-asmtp001.mac.com (nk11p04mm-asmtpout001.mac.com [17.158.236.236]) by ietfa.amsl.com (Postfix) with ESMTP id 4909921F8893 for <ietf@ietf.org>; Thu, 25 Oct 2012 16:43:31 -0700 (PDT)
MIME-version: 1.0
Content-type: text/plain; charset=windows-1252
Received: from [192.168.1.5] (natbox.sabahattin-gucukoglu.com [213.123.192.30]) by nk11p04mm-asmtp001.mac.com (Oracle Communications Messaging Server 7u4-24.01(7.0.4.24.0) 64bit (built Jan 3 2012)) with ESMTPSA id <0MCH00MOX38GI970@nk11p04mm-asmtp001.mac.com> for ietf@ietf.org; Thu, 25 Oct 2012 23:43:30 +0000 (GMT)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.7.7855,1.0.431,0.0.0000 definitions=2012-10-25_05:2012-10-25, 2012-10-25, 1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 ipscore=0 suspectscore=0 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=6.0.2-1203120001 definitions=main-1210250322
Subject: Re: Format=flowed quoting (was "Re: IETF...the unconference of SDOs")
From: Sabahattin Gucukoglu <listsebby@me.com>
In-reply-to: <2380.1351124754@sandelman.ca>
Date: Fri, 26 Oct 2012 00:43:27 +0100
Content-transfer-encoding: quoted-printable
Message-id: <0AAED330-3C9E-4071-9780-A278DAA89E8A@me.com>
References: <94279462-0f48-41ec-933a-a7ac22ba204a@email.android.com> <p06240628cca279fdf657@[99.111.97.136]> <41CCF322-545D-49BD-AEC8-F7595AEE0222@me.com> <p06240600cca730fbf54c@[99.111.97.136]> <FB2B1327-D139-4986-BC4A-C0F45D7C3865@me.com> <2380.1351124754@sandelman.ca>
To: Michael Richardson <mcr+ietf@sandelman.ca>
X-Mailer: Apple Mail (2.1499)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Oct 2012 23:43:32 -0000

On 25 Oct 2012, at 01:25, Michael Richardson <mcr+ietf@sandelman.ca> =
wrote:
> Sabahattin Gucukoglu <listsebby@me.com> wrote:
>    SG> * text/paragraphs (or whatever), a completely different =
identity that violates the length limits
>=20
>    SG> Apple Mail and Microsoft use this text/paragraphs.
>=20
> Do you think it would be worth writing a specification for =
text/paragraphs?

Only if we can get a whole bunch of defective code reading and writing =
it.  There might be a case for that, given the laziness they've =
demonstrated in simply abusing text/plain, but it's also just possible =
that they might, just might implement format=3Dflowed instead.  But it's =
unlikely. :-(

> Heuristically, it's not that hard to identify, and a small patch for
> mailman would at least mark email as being in that format, so that at
> least, IETF lists could have email that complies to some standard.

It would be easier and simpler and probably more participant-friendly =
(though not, see below, quite as good for changing the running code :-) =
) to perform imperfect conversions from text/paragraphs to text/plain; =
format=3Dflowed.  All we've got to do is identify any line longer than =
80 characters and, assuming that it runs to the end of a paragraph at =
all times, add a forced soft line break encoded using F=3DF's stuffing =
rules.  Any line terminated before it's too long is assumed to be a =
manually inserted hard line break.

Now that I come to think of it, now is the time to see if the Tcl MIME =
parser will help me out writing a quick and dirty proxy server for my =
own machine =85

> (Whether or not we then drop email that doesn't have a text/plain part
> is a second conversation)

You want to punish Apple and/or Microsoft?  That's how to do it. :-)

Cheers,
Sabahattin


From tytso@thunk.org  Thu Oct 25 18:21:56 2012
Return-Path: <tytso@thunk.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 DEA3221F85F0 for <ietf@ietfa.amsl.com>; Thu, 25 Oct 2012 18:21:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.343
X-Spam-Level: 
X-Spam-Status: No, score=-1.343 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_MISMATCH_ORG=0.611, HOST_MISMATCH_COM=0.311, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uEyuEeW2GJ6z for <ietf@ietfa.amsl.com>; Thu, 25 Oct 2012 18:21:56 -0700 (PDT)
Received: from imap.thunk.org (li9-11.members.linode.com [67.18.176.11]) by ietfa.amsl.com (Postfix) with ESMTP id 5ED6E21F85C2 for <ietf@ietf.org>; Thu, 25 Oct 2012 18:21:55 -0700 (PDT)
Received: from root (helo=closure.thunk.org) by imap.thunk.org with local-esmtp (Exim 4.72) (envelope-from <tytso@thunk.org>) id 1TRYcM-0004gl-Ri; Fri, 26 Oct 2012 01:21:46 +0000
Received: by closure.thunk.org (Postfix, from userid 15806) id ADED4245F9E; Thu, 25 Oct 2012 21:21:52 -0400 (EDT)
Date: Thu, 25 Oct 2012 21:21:52 -0400
From: Theodore Ts'o <tytso@mit.edu>
To: Tony Hain <alh-ietf@tndh.net>
Subject: Re: Exceptional cases (was: don't overthink)
Message-ID: <20121026012152.GA12095@thunk.org>
References: <20121025185724.9CACF18C0A0@mercury.lcs.mit.edu> <508990E4.9040809@dougbarton.us> <20121025195057.GA55999@mx1.yitter.info> <001301cdb2ee$0780e220$1682a660$@tndh.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <001301cdb2ee$0780e220$1682a660$@tndh.net>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Mail-From: tytso@thunk.org
X-SA-Exim-Scanned: No (on imap.thunk.org); SAEximRunCond expanded to 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, 26 Oct 2012 01:21:57 -0000

On Thu, Oct 25, 2012 at 01:19:26PM -0700, Tony Hain wrote:
> 
> Clearly the IAOC is inadequately staffed if one person missing for an
> extended period is inhibiting their activities.....

This is the part which really confuses me.  Why is this such an urgent
matter?

The stated reason in the IAOC request for community feedback was
difficulty in getting a quorum:

    "Given the size of the IAOC, a missing member makes it much
     harder to get a quorum."

I was trying to figure out what the quorum requirements were, so I
checked out RFC 4071.  There I found:

   The IAOC decides the details about its decision-making rules,
   including its rules for quorum, conflict of interest, and breaking of
   ties.  These rules shall be made public.

I am not sure these are latest rules, but [1] states:

    "A quorum for a meeting of the IAOC shall be a majority of the
     IAOC then in office. All decisions of the members must be
     approved by majority vote of the members then in office."

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

So that means the quorum requirement is 5 people --- out of the 9
IAOC members.  OK, so if Marshall has been AWOL, there must be at
least four other people who are also not showing up if quorom is not
being achieved, which would seem to indicate a problem that extends
beyond just that of a single person.

The other potential problem is that the decision making process seems
to currently require a majority of the IAOC members, and not a
majority of the IAOC members who are attending a meeting.  This means
that if only five IAOC members attend an IAOC meeting, all five would
have to act unaminously to make a decision.

Still, I'm curious why the absence of one person is so great that
people want to make emergency rule changes and why people are treating
this as some kind of constitutional crisis.  Is there part of the
story which I am missing?

Regards,

						- Ted

P.S.  And if the IAOC is empowered to change its quorum and decision
making rules, is there some reason why they can't unanimously (if
there are only five people who are paying attention and attending
meetings) chose to set quorom to be say 3 or 4 people, and perhaps
only require a majority of the IAOC members in attendance?

This is something that appears could be done without having to make
any variances to existing procedure, or to make any emergency rule
changes.


From rbarnes@bbn.com  Thu Oct 25 18:22:41 2012
Return-Path: <rbarnes@bbn.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5895421F8672 for <ietf@ietfa.amsl.com>; Thu, 25 Oct 2012 18:22:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.552
X-Spam-Level: 
X-Spam-Status: No, score=-106.552 tagged_above=-999 required=5 tests=[AWL=0.047, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vsBPxFMCTbCT for <ietf@ietfa.amsl.com>; Thu, 25 Oct 2012 18:22:40 -0700 (PDT)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.0.80]) by ietfa.amsl.com (Postfix) with ESMTP id 5EAB821F8588 for <ietf@ietf.org>; Thu, 25 Oct 2012 18:22:40 -0700 (PDT)
Received: from [128.89.255.5] (port=50804) by smtp.bbn.com with esmtps (TLSv1:AES128-SHA:128) (Exim 4.77 (FreeBSD)) (envelope-from <rbarnes@bbn.com>) id 1TRYdD-0002il-9H; Thu, 25 Oct 2012 21:22:39 -0400
Subject: Re: Exceptional cases (was: don't overthink)
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=us-ascii
From: Richard Barnes <rbarnes@bbn.com>
In-Reply-To: <20121025195057.GA55999@mx1.yitter.info>
Date: Thu, 25 Oct 2012 21:22:38 -0400
Content-Transfer-Encoding: 7bit
Message-Id: <552D37D2-9211-4432-B1CF-330CF0F3FAFB@bbn.com>
References: <20121025185724.9CACF18C0A0@mercury.lcs.mit.edu> <508990E4.9040809@dougbarton.us> <20121025195057.GA55999@mx1.yitter.info>
To: Andrew Sullivan <ajs@anvilwalrusden.com>
X-Mailer: Apple Mail (2.1283)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Oct 2012 01:22:41 -0000

>> would be wrong. The idea here is that applying _punitive_ action (such
>> as removal from a position) retroactively is not "fair," 
> 
> Oh, for heaven's sake.  This is nothing to do with punishment.  This
> is a straightforward administrative problem.  Turning this into an
> opportunity to exercise a heavyweight and in fact punitive process
> would be an injustice.  If the IETF has wound itself into such
> bureaucratic knots that we can't just make an exceptional decision in
> exceptional circumstances, we are in much worse trouble than I
> thought.
> 
> A

+1

+(much more than 1, actually)


From narten@us.ibm.com  Thu Oct 25 21:53:10 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 B577221F8493 for <ietf@ietfa.amsl.com>; Thu, 25 Oct 2012 21:53:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.435
X-Spam-Level: 
X-Spam-Status: No, score=-110.435 tagged_above=-999 required=5 tests=[AWL=0.164, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WqSxKsAtOI47 for <ietf@ietfa.amsl.com>; Thu, 25 Oct 2012 21:53:09 -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 C3FF821F85F4 for <ietf@ietf.org>; Thu, 25 Oct 2012 21:53:09 -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, 25 Oct 2012 22:53:08 -0600
Received: from d03dlp03.boulder.ibm.com (9.17.202.179) by e34.co.us.ibm.com (192.168.1.134) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Thu, 25 Oct 2012 22:53:07 -0600
Received: from d03relay03.boulder.ibm.com (d03relay03.boulder.ibm.com [9.17.195.228]) by d03dlp03.boulder.ibm.com (Postfix) with ESMTP id 9C8DD19D803C for <ietf@ietf.org>; Thu, 25 Oct 2012 22:53:06 -0600 (MDT)
Received: from d03av06.boulder.ibm.com (d03av06.boulder.ibm.com [9.17.195.245]) by d03relay03.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id q9Q4r6Ro229844 for <ietf@ietf.org>; Thu, 25 Oct 2012 22:53:06 -0600
Received: from d03av06.boulder.ibm.com (loopback [127.0.0.1]) by d03av06.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id q9Q4smU8003151 for <ietf@ietf.org>; Thu, 25 Oct 2012 22:54:48 -0600
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.44.115.148]) by d03av06.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id q9Q4slws003128 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Thu, 25 Oct 2012 22:54:48 -0600
Received: from rotala.raleigh.ibm.com (localhost.localdomain [127.0.0.1]) by rotala.raleigh.ibm.com (8.14.5/8.12.5) with ESMTP id q9Q4r4GM019854 for <ietf@ietf.org>; Fri, 26 Oct 2012 00:53:04 -0400
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.5/8.14.5/Submit) id q9Q4r4gJ019812 for ietf@ietf.org; Fri, 26 Oct 2012 00:53:04 -0400
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201210260453.q9Q4r4gJ019812@rotala.raleigh.ibm.com>
Date: Fri, 26 Oct 2012 00:53:04 -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: 12102604-2876-0000-0000-0000015FFF67
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Oct 2012 04:53:10 -0000

Total of 253 messages in the last 7 days.
 
script run at: Fri Oct 26 00:53:04 EDT 2012
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
  7.51% |   19 |  8.44% |   159158 | ian@hixie.ch
  5.93% |   15 |  4.78% |    90220 | dougb@dougbarton.us
  4.74% |   12 |  3.50% |    66074 | jnc@mercury.lcs.mit.edu
  2.77% |    7 |  3.00% |    56606 | barryleiba@computer.org
  2.77% |    7 |  2.73% |    51552 | mstjohns@comcast.net
  2.37% |    6 |  2.25% |    42372 | mnot@mnot.net
  1.58% |    4 |  2.82% |    53162 | adrian@olddog.co.uk
  2.37% |    6 |  2.02% |    38032 | melinda.shore@gmail.com
  2.37% |    6 |  1.92% |    36298 | dwm@xpasc.com
  1.98% |    5 |  1.75% |    33089 | brian.e.carpenter@gmail.com
  1.58% |    4 |  1.86% |    35090 | listsebby@me.com
  1.19% |    3 |  2.00% |    37803 | tbray@textuality.com
  1.58% |    4 |  1.55% |    29152 | john-ietf@jck.com
  0.40% |    1 |  2.70% |    50895 | denis.pinkas@bull.net
  1.58% |    4 |  1.45% |    27421 | jan.algermissen@nordsc.com
  1.58% |    4 |  1.42% |    26717 | julian.reschke@gmx.de
  1.58% |    4 |  1.40% |    26492 | sm@resistor.net
  1.58% |    4 |  1.38% |    26027 | bob.hinden@gmail.com
  1.19% |    3 |  1.72% |    32457 | peter@akayla.com
  1.58% |    4 |  1.30% |    24477 | dhc@dcrocker.net
  1.58% |    4 |  1.24% |    23444 | cabo@tzi.org
  1.58% |    4 |  1.24% |    23306 | ajs@anvilwalrusden.com
  1.19% |    3 |  1.51% |    28520 | kosmo.zb@gmail.com
  1.19% |    3 |  1.21% |    22840 | ted.ietf@gmail.com
  1.19% |    3 |  1.10% |    20700 | stephen.farrell@cs.tcd.ie
  1.19% |    3 |  1.09% |    20492 | rpelletier@isoc.org
  1.19% |    3 |  1.02% |    19250 | alh-ietf@tndh.net
  1.19% |    3 |  1.00% |    18875 | tytso@mit.edu
  1.19% |    3 |  1.00% |    18783 | housley@vigilsec.com
  0.79% |    2 |  1.37% |    25773 | jasnell@gmail.com
  1.19% |    3 |  0.95% |    17844 | johnl@taugh.com
  1.19% |    3 |  0.94% |    17821 | paul.hoffman@vpnc.org
  1.19% |    3 |  0.94% |    17732 | swb@internet2.edu
  1.19% |    3 |  0.90% |    16979 | jari.arkko@piuha.net
  0.79% |    2 |  1.29% |    24258 | pe-jiang@kddi.com
  1.19% |    3 |  0.85% |    16052 | bortzmeyer@nic.fr
  1.19% |    3 |  0.76% |    14351 | randy@psg.com
  0.79% |    2 |  1.10% |    20805 | lberger@labn.net
  0.79% |    2 |  1.07% |    20201 | chuck.lever@oracle.com
  0.79% |    2 |  0.96% |    18035 | lear@cisco.com
  0.79% |    2 |  0.94% |    17824 | fielding@gbiv.com
  0.79% |    2 |  0.93% |    17555 | rumbiles@gmail.com
  0.79% |    2 |  0.82% |    15513 | turchanyi.geza@gmail.com
  0.79% |    2 |  0.81% |    15311 | annevk@annevk.nl
  0.79% |    2 |  0.81% |    15234 | james.h.manger@team.telstra.com
  0.79% |    2 |  0.76% |    14297 | ben@nostrum.com
  0.79% |    2 |  0.73% |    13857 | ynir@checkpoint.com
  0.79% |    2 |  0.70% |    13253 | mcr+ietf@sandelman.ca
  0.79% |    2 |  0.70% |    13251 | joelja@bogus.com
  0.79% |    2 |  0.69% |    13050 | iesg-secretary@ietf.org
  0.79% |    2 |  0.67% |    12595 | john@jlc.net
  0.79% |    2 |  0.65% |    12352 | mrex@sap.com
  0.79% |    2 |  0.62% |    11743 | cowan@mercury.ccil.org
  0.79% |    2 |  0.62% |    11711 | stpeter@stpeter.im
  0.79% |    2 |  0.62% |    11675 | hartmans-ietf@mit.edu
  0.79% |    2 |  0.59% |    11179 | iad@ietf.org
  0.40% |    1 |  0.99% |    18607 | mamund@yahoo.com
  0.40% |    1 |  0.67% |    12620 | tglassey@earthlink.net
  0.40% |    1 |  0.62% |    11734 | lars@netapp.com
  0.40% |    1 |  0.59% |    11043 | grmocg@gmail.com
  0.40% |    1 |  0.56% |    10613 | tina.tsou.zouting@huawei.com
  0.40% |    1 |  0.56% |    10605 | clauret@weborganic.com
  0.40% |    1 |  0.56% |    10501 | randy@qti.qualcomm.com
  0.40% |    1 |  0.49% |     9188 | dmm@1-4-5.net
  0.40% |    1 |  0.48% |     9084 | bensons@queuefull.net
  0.40% |    1 |  0.45% |     8524 | rbonica@juniper.net
  0.40% |    1 |  0.44% |     8330 | narten@us.ibm.com
  0.40% |    1 |  0.43% |     8051 | edj.etc@gmail.com
  0.40% |    1 |  0.41% |     7665 | kwiereng@cisco.com
  0.40% |    1 |  0.40% |     7561 | hallam@gmail.com
  0.40% |    1 |  0.39% |     7409 | nrm@arcanedomain.com
  0.40% |    1 |  0.39% |     7381 | daedulus@btconnect.com
  0.40% |    1 |  0.38% |     7257 | marka@isc.org
  0.40% |    1 |  0.38% |     7222 | margaretw42@gmail.com
  0.40% |    1 |  0.38% |     7085 | huitema@microsoft.com
  0.40% |    1 |  0.35% |     6584 | sm+ietf@elandsys.com
  0.40% |    1 |  0.35% |     6581 | henk.uijterwaal@gmail.com
  0.40% |    1 |  0.35% |     6546 | tobias.gondrom@gondrom.org
  0.40% |    1 |  0.34% |     6481 | hgs@cs.columbia.edu
  0.40% |    1 |  0.34% |     6346 | ggm@algebras.org
  0.40% |    1 |  0.34% |     6345 | hsantos@isdg.net
  0.40% |    1 |  0.34% |     6344 | sob@harvard.edu
  0.40% |    1 |  0.33% |     6245 | rwfranks@gmail.com
  0.40% |    1 |  0.32% |     6097 | mccap@petoni.org
  0.40% |    1 |  0.32% |     6067 | ford@isoc.org
  0.40% |    1 |  0.32% |     6065 | rwfranks@acm.org
  0.40% |    1 |  0.32% |     6000 | lixia@cs.ucla.edu
  0.40% |    1 |  0.32% |     5987 | ajs@crankycanuck.ca
  0.40% |    1 |  0.31% |     5851 | sob@sobco.com
  0.40% |    1 |  0.31% |     5818 | david.kessens@nsn.com
  0.40% |    1 |  0.30% |     5732 | rdroms.ietf@gmail.com
  0.40% |    1 |  0.30% |     5665 | vesely@tana.it
  0.40% |    1 |  0.30% |     5661 | gk-lists@ninebynine.org
  0.40% |    1 |  0.29% |     5545 | suresh.krishnan@ericsson.com
  0.40% |    1 |  0.28% |     5309 | ogud@ogud.com
  0.40% |    1 |  0.27% |     5165 | rbarnes@bbn.com
  0.40% |    1 |  0.27% |     5001 | steve@shinkuro.com
  0.40% |    1 |  0.26% |     4903 | acooper@cdt.org
--------+------+--------+----------+------------------------
100.00% |  253 |100.00% |  1886373 | Total


From brian.e.carpenter@gmail.com  Fri Oct 26 00:11:10 2012
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8564021F86B1 for <ietf@ietfa.amsl.com>; Fri, 26 Oct 2012 00:11:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.693
X-Spam-Level: 
X-Spam-Status: No, score=-101.693 tagged_above=-999 required=5 tests=[AWL=-0.002, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2aaQhrfMwz+S for <ietf@ietfa.amsl.com>; Fri, 26 Oct 2012 00:11:10 -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 D768E21F8662 for <ietf@ietf.org>; Fri, 26 Oct 2012 00:11:09 -0700 (PDT)
Received: by mail-ee0-f44.google.com with SMTP id d4so1023416eek.31 for <ietf@ietf.org>; Fri, 26 Oct 2012 00:11:09 -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=+AE6YwjmUtsZJsRDyrWUgdYCCkkR/GUVghSKd9MnkJw=; b=w8sCQLnZ0y4Kda8UtupbVM1/aGN6YxFWDy/g7WFtufeTUKwsvxe12uMl/PZcNLM2Ig seV005wKXwGL3IxIOwUJaDsNXlaHgv/WGnnYyA1Okhx2OiEgyNWwLvTzOjxzZmPKUnXv EYhTRDMlLsEZHWWZkyzy/Mks7zZ1YqbUk7In19rXJXLtdwc/66L7uKjdVh2qtOx2n4gM rocQOIPrainw+5G74DVbZz6XWAuMCbxtZD1GZLPUdWRZG26BsML/lYo8f7U+v/je0+hx ffUhHhQKZbP91Jwuu9nIj2mLZG8Drzk68TbNm4NqZ9nEyu/cvpTQtwiGVGurxYoniHK0 UAfA==
Received: by 10.14.215.69 with SMTP id d45mr29821340eep.16.1351235469098; Fri, 26 Oct 2012 00:11:09 -0700 (PDT)
Received: from [192.168.1.65] (host-2-102-216-184.as13285.net. [2.102.216.184]) by mx.google.com with ESMTPS id g47sm970421eeo.6.2012.10.26.00.11.07 (version=SSLv3 cipher=OTHER); Fri, 26 Oct 2012 00:11:07 -0700 (PDT)
Message-ID: <508A3794.3070303@gmail.com>
Date: Fri, 26 Oct 2012 08:11:16 +0100
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Richard Barnes <rbarnes@bbn.com>
Subject: Re: Exceptional cases
References: <20121025185724.9CACF18C0A0@mercury.lcs.mit.edu>	<508990E4.9040809@dougbarton.us>	<20121025195057.GA55999@mx1.yitter.info> <552D37D2-9211-4432-B1CF-330CF0F3FAFB@bbn.com>
In-Reply-To: <552D37D2-9211-4432-B1CF-330CF0F3FAFB@bbn.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: Fri, 26 Oct 2012 07:11:10 -0000

On 26/10/2012 02:22, Richard Barnes wrote:
>>> would be wrong. The idea here is that applying _punitive_ action (such
>>> as removal from a position) retroactively is not "fair," 
>> Oh, for heaven's sake.  This is nothing to do with punishment.  This
>> is a straightforward administrative problem.  Turning this into an
>> opportunity to exercise a heavyweight and in fact punitive process
>> would be an injustice.  If the IETF has wound itself into such
>> bureaucratic knots that we can't just make an exceptional decision in
>> exceptional circumstances, we are in much worse trouble than I
>> thought.
>>
>> A
> 
> +1
> 
> +(much more than 1, actually)

What he said. Common sense should prevail. We can fix *this* tiny gap in
our procedures in due course, but we will need to apply common sense again
the next time we find a tiny gap.

    Brian

From brian.e.carpenter@gmail.com  Fri Oct 26 00:19:56 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 6DD3221F844C for <ietf@ietfa.amsl.com>; Fri, 26 Oct 2012 00:19:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.693
X-Spam-Level: 
X-Spam-Status: No, score=-101.693 tagged_above=-999 required=5 tests=[AWL=-0.002, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iFYST3bhllGz for <ietf@ietfa.amsl.com>; Fri, 26 Oct 2012 00:19:55 -0700 (PDT)
Received: from mail-ea0-f172.google.com (mail-ea0-f172.google.com [209.85.215.172]) by ietfa.amsl.com (Postfix) with ESMTP id 76EA321F8608 for <ietf@ietf.org>; Fri, 26 Oct 2012 00:19:54 -0700 (PDT)
Received: by mail-ea0-f172.google.com with SMTP id k13so845047eaa.31 for <ietf@ietf.org>; Fri, 26 Oct 2012 00:19:53 -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=naFJMgvnLOYS941Ba652AyLBmwXNiTHTHkD0oJSPsIY=; b=FF5YpqTL0hj/i6tDzyQkYy5J0Jn9TLmwSHYaGEjlHw2PmzuPr0d/q8bJHsO1wZPUoi /tUtWhQ/WnwXRZwrFkGlZahJnxpYnBGj+0+wIkPrnZ8zU9ek8AQNwDI5EVxrK0scryIa jXelXSlpKiBy90PXkaO1zq6/zgANGR/BsyCgqaYG7awk/augkpbeA84PC0yCwohQLCnm 0awh9ZgDImsfNnbSjMX+GELauae9y+GxRUDaDRl0RBIeElh0OpQ3/U9ad9wHGQs2P+l7 2PmuUsVH72xBu24QVyJJQH+3db5M30IZf/CDXyiO8tvCApCosxcQq7Tpwt9Up8JWnRbF tNAg==
Received: by 10.14.179.6 with SMTP id g6mr29765956eem.46.1351235993522; Fri, 26 Oct 2012 00:19:53 -0700 (PDT)
Received: from [192.168.1.65] (host-2-102-216-184.as13285.net. [2.102.216.184]) by mx.google.com with ESMTPS id d44sm999312eeo.10.2012.10.26.00.19.51 (version=SSLv3 cipher=OTHER); Fri, 26 Oct 2012 00:19:52 -0700 (PDT)
Message-ID: <508A39A0.3090602@gmail.com>
Date: Fri, 26 Oct 2012 08:20:00 +0100
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Doug Barton <dougb@dougbarton.us>
Subject: Re: Just so I'm clear
References: <20121023192135.203AC18C0A4@mercury.lcs.mit.edu>	<5086EF82.9060900@dougbarton.us> <20121023200713.GC1861@nsn.com>	<5086FBCE.2070503@dougbarton.us> <20121023213251.GF27557@verdi>	<50873AB4.1000905@dougbarton.us>	<20121024034736.GC52558@crankycanuck.ca>	<50876D39.20502@dougbarton.us> <508773E7.10203@cisco.com>	<50877633.1000402@dougbarton.us>	<EA9BEA2E-EE96-4E80-B719-652BBD620A79@lilacglade.org> <508842C2.4020203@dougbarton.us> <5088EE5A.4090103@gmail.com> <508987B9.2040207@dougbarton.us>
In-Reply-To: <508987B9.2040207@dougbarton.us>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Oct 2012 07:19:56 -0000

On 25/10/2012 19:40, Doug Barton wrote:
> On 10/25/2012 12:46 AM, Brian E Carpenter wrote:
>> On 24/10/2012 20:34, Doug Barton wrote:
>> ...
>>> ... Nothing in the text suggests an
>>> unfettered right of creating new definitions of "vacant."
>> You mean, new compared to the first definition in Merriam-Webster.com?
>>
>> 1: not occupied by an incumbent, possessor, or officer <a vacant office> <vacant thrones>
> 
> C'mon Brian, not helpful. We're talking about the BCP 101 "definition of
> vacant" which unfortunately is not nearly so precise. If there were no
> mention of 3777 in the text then there would appear to be more leeway in
> declaring a position vacant.

There is no definition of "vacant" or "vacancy" in RFC 3777 (except for the
special case of a mid-term vacancy caused by the appointment of the member
to another IETF position). Therefore it seems reasonable to resort
to the dictionary.

> 
>> Objectively and factually, that seems to be the case.
> 
> I get that this is what you believe to be true, however what some of us
> are saying is that we don't agree. 

Actually I haven't seen that. I've seen people assert that our process
doesn't document the case of a non-responsive absentee member, but I
haven't seen anyone deny that we have an empty seat.

  Brian

From jari.arkko@piuha.net  Fri Oct 26 00:29:48 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 6A10821F842D for <ietf@ietfa.amsl.com>; Fri, 26 Oct 2012 00:29:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.588
X-Spam-Level: 
X-Spam-Status: No, score=-102.588 tagged_above=-999 required=5 tests=[AWL=0.011, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WrcfkOIo6M2D for <ietf@ietfa.amsl.com>; Fri, 26 Oct 2012 00:29:47 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by ietfa.amsl.com (Postfix) with ESMTP id A8F8621F841A for <ietf@ietf.org>; Fri, 26 Oct 2012 00:29:47 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id C06D92D7F7; Fri, 26 Oct 2012 10:29:42 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3n7KNhaDo92j; Fri, 26 Oct 2012 10:29:42 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id 218F22CC56; Fri, 26 Oct 2012 10:29:42 +0300 (EEST)
Message-ID: <508A3BE5.5070406@piuha.net>
Date: Fri, 26 Oct 2012 10:29:41 +0300
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20121011 Thunderbird/16.0.1
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Exceptional cases
References: <20121025185724.9CACF18C0A0@mercury.lcs.mit.edu>	<508990E4.9040809@dougbarton.us>	<20121025195057.GA55999@mx1.yitter.info> <552D37D2-9211-4432-B1CF-330CF0F3FAFB@bbn.com> <508A3794.3070303@gmail.com>
In-Reply-To: <508A3794.3070303@gmail.com>
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, 26 Oct 2012 07:29:48 -0000

Brian, Richard, others,

>>> Oh, for heaven's sake.  This is nothing to do with punishment.  This
>>> is a straightforward administrative problem.  Turning this into an
>>> opportunity to exercise a heavyweight and in fact punitive process
>>> would be an injustice.  If the IETF has wound itself into such
>>> bureaucratic knots that we can't just make an exceptional decision in
>>> exceptional circumstances, we are in much worse trouble than I
>>> thought.
>>>
>>> A
>> +1
>>
>> +(much more than 1, actually)
> What he said. Common sense should prevail. We can fix *this* tiny gap in
> our procedures in due course, but we will need to apply common sense again
> the next time we find a tiny gap.
>

For what it is worth, I agree with this as well.

Jari


From bortzmeyer@nic.fr  Fri Oct 26 00:39:45 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 D788C21F8471; Fri, 26 Oct 2012 00:39:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.11
X-Spam-Level: 
X-Spam-Status: No, score=-102.11 tagged_above=-999 required=5 tests=[AWL=0.139, BAYES_00=-2.599, HELO_EQ_FR=0.35, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id s3B5655eslOe; Fri, 26 Oct 2012 00:39:45 -0700 (PDT)
Received: from mx4.nic.fr (mx4.nic.fr [192.134.4.12]) by ietfa.amsl.com (Postfix) with ESMTP id 55E7D21F8460; Fri, 26 Oct 2012 00:39:45 -0700 (PDT)
Received: from mx4.nic.fr (localhost [127.0.0.1]) by mx4.nic.fr (Postfix) with SMTP id B9A9E2805C0; Fri, 26 Oct 2012 09:39:10 +0200 (CEST)
Received: from relay1.nic.fr (relay1.nic.fr [192.134.4.162]) by mx4.nic.fr (Postfix) with ESMTP id B49682802FA; Fri, 26 Oct 2012 09:39:10 +0200 (CEST)
Received: from bortzmeyer.nic.fr (batilda.nic.fr [IPv6:2001:67c:2219:8::6:69]) by relay1.nic.fr (Postfix) with ESMTP id A8E574C007F; Fri, 26 Oct 2012 09:38:40 +0200 (CEST)
Date: Fri, 26 Oct 2012 09:38:40 +0200
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: IESG Secretary <iesg-secretary@ietf.org>
Subject: Stable URL of IESG statements (Was: IESG Statement on Ethertypes
Message-ID: <20121026073840.GA18964@nic.fr>
References: <20121025183441.32156.10765.idtracker@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20121025183441.32156.10765.idtracker@ietfa.amsl.com>
X-Operating-System: Debian GNU/Linux wheezy/sid
X-Kernel: Linux 3.2.0-3-686-pae i686
Organization: NIC France
X-URL: http://www.nic.fr/
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Oct 2012 07:39:46 -0000

On Thu, Oct 25, 2012 at 11:34:41AM -0700,
 IESG Secretary <iesg-secretary@ietf.org> wrote 
 a message of 28 lines which said:

> The IEEE Registration Authority (IEEE RA) assigns Ethertypes 

I suggest it would be a good idea to have the stable URL of the
statement <http://www.ietf.org/iesg/statement/ethertypes.html> *in*
the announcement. Sometimes, people read the mail announcement after
some forwarding and may want to check the authoritative source.


From sm@resistor.net  Fri Oct 26 02:43:29 2012
Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DF2CE21F8500 for <ietf@ietfa.amsl.com>; Fri, 26 Oct 2012 02:43:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.289
X-Spam-Level: 
X-Spam-Status: No, score=-102.289 tagged_above=-999 required=5 tests=[AWL=-0.290, BAYES_00=-2.599, J_CHICKENPOX_21=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kU23RZXZwo53 for <ietf@ietfa.amsl.com>; Fri, 26 Oct 2012 02:43:29 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2885421F84CA for <ietf@ietf.org>; Fri, 26 Oct 2012 02:43:28 -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 q9Q9hGli026788; Fri, 26 Oct 2012 02:43:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1351244603; bh=tj2jN0ONnhzY1CbQtCzXhnIxw75yK9doH24ZyvNokKQ=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=mtW8LOJsP5NTUGwTRcZvn3SSJ398l6xV/sVcZT2hkuheEGz73tGbdbzvTOLBl0dr0 JJ806Bma+Z+hDAiIUcwPjwfjTFy+h1fNWXmNiNwwlgJeBwzU0t+qAwF1a+7cHb0/O4 ZPTsuirpadSVyT1Zlf+6fCphKich2h5XFtz5FkVA=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1351244603; i=@resistor.net; bh=tj2jN0ONnhzY1CbQtCzXhnIxw75yK9doH24ZyvNokKQ=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=vUODSJjvcCNKCfl6/yHfsBSUwu9qNQJb3A9gDK5qjs27x7j+rkn5+N74GMvjUPN6V svrXzqLTv73w3a67ka+0f9lEAeJZNTXluAvxezixtiUvkE/yKpR0tdw/LBFoGOjzGD T/lUqyzRmK0sBC7iYXzMUekRCT4XPICcUIsfsqMM=
Message-Id: <6.2.5.6.2.20121025232216.094f24e8@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 26 Oct 2012 02:35:30 -0700
To: ietf@ietf.org
From: SM <sm@resistor.net>
Subject: Re: don't overthink, was Just so I'm clear
In-Reply-To: <tslhapi5fno.fsf@mit.edu>
References: <20121025125351.285D818C0A0@mercury.lcs.mit.edu> <20121025204915.6C09621F8491@ietfa.amsl.com> <tslhapi5fno.fsf@mit.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: Theodore Ts'o <tytso@mit.edu>, Sam Hartman <hartmans-ietf@mit.edu>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Oct 2012 09:43:30 -0000

At 15:51 25-10-2012, Sam Hartman wrote:
>2) IETF process documents require approval by the ISOC BOT.

Not really.  The ISOC Board of Trustees is not in the loop when it 
comes to IETF document approval.

>3) There is a variance procedure. I've always been puzzled by it because
>it seems to require exactly the same things as approving a new procedure
>plus extra work.

It's generally a bad idea to make rules to address a specific case or 
to craft rules to favor or take action against one party.  A variance 
procedure is useful for unforeseen procedural issues.  Without it a 
system ends up being rigid.  The problem with variance is generally 
the "collateral and precedential effects of granting a variance".

At 00:11 26-10-2012, Brian E Carpenter wrote:
>What he said. Common sense should prevail. We can fix *this* tiny gap in
>our procedures in due course, but we will need to apply common sense again
>the next time we find a tiny gap.

Common sense is rarely used as a justification as there isn't IETF 
Consensus on the meaning of "common sense".  I edited the text posted 
by the IAOC Chair [1]:

   The IAOC believes that it is reasonable to fill his position for the
   remainder of his term as the IAOC has been unable to communicate with him
   since 1 August 2012.

It's going to be difficult to argue that it is not reasonable to fill 
the position.  Now, if someone argues that it is unreasonable, you 
can try to show that the person is being unreasonable or you can 
accept the opinion.  The latter is somewhat related to the notion of 
consensus.  The former raises questions about the presumption of good faith.

At 18:21 25-10-2012, Theodore Ts'o wrote:
>Still, I'm curious why the absence of one person is so great that
>people want to make emergency rule changes and why people are treating
>this as some kind of constitutional crisis.  Is there part of the
>story which I am missing?

It's an awkward situation.  "The IAOC proposed this approach because 
we think it would cause the least amount of embarrassment" [2].

At 13:44 25-10-2012, Doug Barton wrote:
>Without any personal knowledge of his circumstances, I'm not prepared to
>judge him.

Yes.

At 11:40 25-10-2012, Doug Barton wrote:
>are saying is that we don't agree. Given that the only choices are
>"vacant, or recall;" and given that the vacant state of the seat isn't
>100% clear, at this time recall is the only option.

One generally takes a three-way hum [3].

Regards,
-sm

1. http://www.ietf.org/mail-archive/web/ietf-announce/current/msg10812.html
2. http://www.ietf.org/mail-archive/web/ietf/current/msg75414.html
3. http://www.ietf.org/mail-archive/web/ietf/current/msg75523.html


From rwfranks@gmail.com  Thu Oct 25 19:15:39 2012
Return-Path: <rwfranks@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B49EE21F88CE for <ietf@ietfa.amsl.com>; Thu, 25 Oct 2012 19:15:39 -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, J_CHICKENPOX_21=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Jc1Yk3kh6yMi for <ietf@ietfa.amsl.com>; Thu, 25 Oct 2012 19:15: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 4529E21F88CB for <ietf@ietf.org>; Thu, 25 Oct 2012 19:15:37 -0700 (PDT)
Received: by mail-wi0-f178.google.com with SMTP id hr7so113067wib.13 for <ietf@ietf.org>; Thu, 25 Oct 2012 19:15:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=pMkBWZel9actIlTEewoug8wP1oE+JAOqLGir4wO0H/s=; b=fgW1WMP6NL9RZaL3JeNRwKets/rbHOmKW/jwy/XKBCDAwcdZHJa9t4FbZ33tbrbCuf CQwg/o4YM6IE7SMcVdA7Z2YI48369lsKArs/Mphg0YbH6CNzNdCjbfmVoH0JvSqe8/Gt 7nYkHK4yTp6Q+49MaYMBtnIRFth4Vc2krOsZyzl3qlzcMByOGZeipF9OqB5G87WWxEH9 h73R1fJf0ppz5Nik2J5DNnolnjginBpduGP25Wz5oK3S38v3MSelVeVyAcEzEULiqHS2 jF13g//HJyGhwAU0eRQpR7B7bUAb5Qbs71cUs05bLq/AxqHCQ0eG+ENewjlKRcleY/ky YbJw==
Received: by 10.180.85.99 with SMTP id g3mr1674624wiz.5.1351217736166; Thu, 25 Oct 2012 19:15:36 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.194.41.65 with HTTP; Thu, 25 Oct 2012 19:15:16 -0700 (PDT)
In-Reply-To: <20121026012152.GA12095@thunk.org>
References: <20121025185724.9CACF18C0A0@mercury.lcs.mit.edu> <508990E4.9040809@dougbarton.us> <20121025195057.GA55999@mx1.yitter.info> <001301cdb2ee$0780e220$1682a660$@tndh.net> <20121026012152.GA12095@thunk.org>
From: Dick Franks <rwfranks@gmail.com>
Date: Fri, 26 Oct 2012 03:15:16 +0100
Message-ID: <CAKW6Ri7TwZrmahaOoCUQZJJW-Z22sqAMZzc84EUm45B0nyNwRw@mail.gmail.com>
Subject: Re: Exceptional cases (was: don't overthink)
To: "Theodore Ts'o" <tytso@mit.edu>
Content-Type: text/plain; charset=UTF-8
X-Mailman-Approved-At: Fri, 26 Oct 2012 03:46:39 -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, 26 Oct 2012 02:15:39 -0000

and IAOC is unable to change its own quorum requirement because . . .
it can't achieve the necessary quorum!!

Now that _is_ a serious administrative oversight.

--


On 26 October 2012 02:21, Theodore Ts'o <tytso@mit.edu> wrote:
> On Thu, Oct 25, 2012 at 01:19:26PM -0700, Tony Hain wrote:
>>
>> Clearly the IAOC is inadequately staffed if one person missing for an
>> extended period is inhibiting their activities.....
>
> This is the part which really confuses me.  Why is this such an urgent
> matter?
>
> The stated reason in the IAOC request for community feedback was
> difficulty in getting a quorum:
>
>     "Given the size of the IAOC, a missing member makes it much
>      harder to get a quorum."
>
> I was trying to figure out what the quorum requirements were, so I
> checked out RFC 4071.  There I found:
>
>    The IAOC decides the details about its decision-making rules,
>    including its rules for quorum, conflict of interest, and breaking of
>    ties.  These rules shall be made public.
>
> I am not sure these are latest rules, but [1] states:
>
>     "A quorum for a meeting of the IAOC shall be a majority of the
>      IAOC then in office. All decisions of the members must be
>      approved by majority vote of the members then in office."
>
> [1]  http://iaoc.ietf.org/docs/IAOC-Administrative-Procedures-9-16-2010.pdf
>
> So that means the quorum requirement is 5 people --- out of the 9
> IAOC members.  OK, so if Marshall has been AWOL, there must be at
> least four other people who are also not showing up if quorom is not
> being achieved, which would seem to indicate a problem that extends
> beyond just that of a single person.
>
> The other potential problem is that the decision making process seems
> to currently require a majority of the IAOC members, and not a
> majority of the IAOC members who are attending a meeting.  This means
> that if only five IAOC members attend an IAOC meeting, all five would
> have to act unaminously to make a decision.
>
> Still, I'm curious why the absence of one person is so great that
> people want to make emergency rule changes and why people are treating
> this as some kind of constitutional crisis.  Is there part of the
> story which I am missing?
>
> Regards,
>
>                                                 - Ted
>
> P.S.  And if the IAOC is empowered to change its quorum and decision
> making rules, is there some reason why they can't unanimously (if
> there are only five people who are paying attention and attending
> meetings) chose to set quorom to be say 3 or 4 people, and perhaps
> only require a majority of the IAOC members in attendance?
>
> This is something that appears could be done without having to make
> any variances to existing procedure, or to make any emergency rule
> changes.
>

From hartmans@mit.edu  Fri Oct 26 04:20:51 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 8211421F84AF for <ietf@ietfa.amsl.com>; Fri, 26 Oct 2012 04:20:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.502
X-Spam-Level: 
X-Spam-Status: No, score=-100.502 tagged_above=-999 required=5 tests=[AWL=2.097, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rBmdBrwzDbJV for <ietf@ietfa.amsl.com>; Fri, 26 Oct 2012 04:20:50 -0700 (PDT)
Received: from mail.painless-security.com (mail.painless-security.com [23.30.188.241]) by ietfa.amsl.com (Postfix) with ESMTP id 7272021F84AD for <ietf@ietf.org>; Fri, 26 Oct 2012 04:20:50 -0700 (PDT)
Received: from carter-zimmerman.suchdamage.org (c-98-217-126-210.hsd1.ma.comcast.net [98.217.126.210]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.painless-security.com (Postfix) with ESMTPS id 760B520178; Fri, 26 Oct 2012 07:20:19 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id AD739412A; Fri, 26 Oct 2012 07:20:46 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: SM <sm@resistor.net>
Subject: ISOC BOT and Process BCPs
References: <20121025125351.285D818C0A0@mercury.lcs.mit.edu> <20121025204915.6C09621F8491@ietfa.amsl.com> <tslhapi5fno.fsf@mit.edu> <6.2.5.6.2.20121025232216.094f24e8@resistor.net>
Date: Fri, 26 Oct 2012 07:20:46 -0400
In-Reply-To: <6.2.5.6.2.20121025232216.094f24e8@resistor.net> (sm@resistor.net's message of "Fri, 26 Oct 2012 02:35:30 -0700")
Message-ID: <tsly5it32ep.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: Theodore Ts'o <tytso@mit.edu>, Sam Hartman <hartmans-ietf@mit.edu>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Oct 2012 11:20:51 -0000

>>>>> "SM" == SM  <sm@resistor.net> writes:


So, I'm puzzled by this.  my claim was that ISOC needed to approve
process related BCPs.  If you take a look at RFC 2031, it supports that
claim.  However, I'd kind of expect the other half of this to be in RFC
2026.  I certainly recall us sending things like BCP 101 before the ISOC
BOT. I also think we sent a couple of other documents there because they
were process documents.
However this is clearly more complex than I thought it was.

Scott, or anyone else with more history, can you tell us a story about
how this works?

From margaretw42@gmail.com  Fri Oct 26 04:37:00 2012
Return-Path: <margaretw42@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DDC8D21F84D4 for <ietf@ietfa.amsl.com>; Fri, 26 Oct 2012 04:37:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wajgrcXKepcs for <ietf@ietfa.amsl.com>; Fri, 26 Oct 2012 04:37:00 -0700 (PDT)
Received: from mail-qa0-f51.google.com (mail-qa0-f51.google.com [209.85.216.51]) by ietfa.amsl.com (Postfix) with ESMTP id 5112C21F8545 for <ietf@ietf.org>; Fri, 26 Oct 2012 04:37:00 -0700 (PDT)
Received: by mail-qa0-f51.google.com with SMTP id j40so188304qab.10 for <ietf@ietf.org>; Fri, 26 Oct 2012 04:36:59 -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=93qHaI5Zls6gUhHfH5Tob7cz1oki25roHW9ASDRPuj0=; b=iUWh48++hr3vtBzJmcKo2dUqcfXtlxDERjDkWV/ulwxJjsAOJi3Pi5tc7OugiTKV+N 0aP/11ixiu3sRpt/3bUrE79uNHB4BpXIE/yeoeegD/FcqPANOI8+ELLuGflK5u9EMCwI bTaV4Ddu+0En1s5FANYZHLv6X1R39jlR7xtKTTR3colUUAFij6Hic0diqozfleEz1/OC IttCOALd43mcduHUGTsqyjLKMSfp5r3lKqswPKKaXJ7OaAkc+EI51oub+s9uMVGoT6Pd t0Mr0vh6R7UPrU/6eoCqnEk6VPewbdFSPjnde8YhXwYYOnoYuUxYzGFImEhXWdVol0bf AAyg==
Received: by 10.49.2.74 with SMTP id 10mr2789170qes.10.1351251419674; Fri, 26 Oct 2012 04:36:59 -0700 (PDT)
Received: from lilac-too.home (pool-71-184-79-25.bstnma.fios.verizon.net. [71.184.79.25]) by mx.google.com with ESMTPS id ig20sm885252qab.19.2012.10.26.04.36.49 (version=SSLv3 cipher=OTHER); Fri, 26 Oct 2012 04:36:56 -0700 (PDT)
Subject: Re: Exceptional cases
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Margaret Wasserman <margaretw42@gmail.com>
In-Reply-To: <508A3794.3070303@gmail.com>
Date: Fri, 26 Oct 2012 07:36:52 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <8882ADBD-D068-486B-BCE6-BDEF3ABF925C@lilacglade.org>
References: <20121025185724.9CACF18C0A0@mercury.lcs.mit.edu>	<508990E4.9040809@dougbarton.us>	<20121025195057.GA55999@mx1.yitter.info> <552D37D2-9211-4432-B1CF-330CF0F3FAFB@bbn.com> <508A3794.3070303@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1084)
X-Mailman-Approved-At: Fri, 26 Oct 2012 04:49:12 -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, 26 Oct 2012 11:37:01 -0000

On Oct 26, 2012, at 3:11 AM, Brian E Carpenter wrote:

> On 26/10/2012 02:22, Richard Barnes wrote:
>>>> would be wrong. The idea here is that applying _punitive_ action =
(such
>>>> as removal from a position) retroactively is not "fair,"=20
>>> Oh, for heaven's sake.  This is nothing to do with punishment.  This
>>> is a straightforward administrative problem.  Turning this into an
>>> opportunity to exercise a heavyweight and in fact punitive process
>>> would be an injustice.  If the IETF has wound itself into such
>>> bureaucratic knots that we can't just make an exceptional decision =
in
>>> exceptional circumstances, we are in much worse trouble than I
>>> thought.
>>>=20
>>> A
>>=20
>> +1
>>=20
>> +(much more than 1, actually)
>=20
> What he said. Common sense should prevail. We can fix *this* tiny gap =
in
> our procedures in due course, but we will need to apply common sense =
again
> the next time we find a tiny gap.

I also agree. =20

The existence of an inappropriate tool (the recall process) should not =
prevent us from doing the right thing here.

Margaret



From lear@cisco.com  Fri Oct 26 05:16:06 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 E049B21F852A for <ietf@ietfa.amsl.com>; Fri, 26 Oct 2012 05:16:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.45
X-Spam-Level: 
X-Spam-Status: No, score=-110.45 tagged_above=-999 required=5 tests=[AWL=0.149, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oAjCLDTSMXBy for <ietf@ietfa.amsl.com>; Fri, 26 Oct 2012 05:16:05 -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 3797C21F8513 for <ietf@ietf.org>; Fri, 26 Oct 2012 05:16:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=843; q=dns/txt; s=iport; t=1351253765; x=1352463365; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=2Kyst2tMRHBmMoPn4s2uZP+1koF6HolpbBGpesO0hII=; b=BVI0TDr1RBSXznzvnEXR6SZNeoJ0Vu/coJPx1v9D0zdAdgxRLq9IAErS m4lkATJ/BUiXS1G0G1ZE5vT7TLuGAEsplAFCRbd9PDV0nfkVXg1l0VQmu CKuWtSVVW4u0aKDg4uanKMMK3bYLU04JYKOM9RZ8krDuiRRrpjBjpMImf U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAFAHV+ilCQ/khN/2dsb2JhbABEhhe8IIEIgh4BAQEEEgEQVQEQCw4KAgIFFgsCAgkDAgECAUUGDQEHAQEeh2KdEY0okmWBIJAjgRMDlXaOUoFrgnE
X-IronPort-AV: E=Sophos;i="4.80,654,1344211200"; d="scan'208";a="77776746"
Received: from ams-core-4.cisco.com ([144.254.72.77]) by ams-iport-2.cisco.com with ESMTP; 26 Oct 2012 12:16:03 +0000
Received: from dhcp-10-55-94-238.cisco.com (dhcp-10-55-94-238.cisco.com [10.55.94.238]) by ams-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id q9QCG2lR008297 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 26 Oct 2012 12:16:03 GMT
Message-ID: <508A7F02.5080905@cisco.com>
Date: Fri, 26 Oct 2012 14:16:02 +0200
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:16.0) Gecko/20121010 Thunderbird/16.0.1
MIME-Version: 1.0
To: Andrew Sullivan <ajs@anvilwalrusden.com>
Subject: Re: Exceptional cases
References: <20121025185724.9CACF18C0A0@mercury.lcs.mit.edu> <508990E4.9040809@dougbarton.us> <20121025195057.GA55999@mx1.yitter.info>
In-Reply-To: <20121025195057.GA55999@mx1.yitter.info>
X-Enigmail-Version: 1.4.5
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Oct 2012 12:16:07 -0000

Andrew,

On 10/25/12 9:52 PM, Andrew Sullivan wrote:
> Oh, for heaven's sake. This is nothing to do with punishment. This is
> a straightforward administrative problem. Turning this into an
> opportunity to exercise a heavyweight and in fact punitive process
> would be an injustice. If the IETF has wound itself into such
> bureaucratic knots that we can't just make an exceptional decision in
> exceptional circumstances, we are in much worse trouble than I thought. A 

And as of yet nobody has challenged the need to remove Marshall.  We've
just gone off the deep end on process.  Yes, let's close the process
problem as Brian said in due course.  Let's also not rush through the
changes for all the reasons that John Klensin wrote, plus another: I
don't like the proposed approach, but that's for another message.

Eliot



From julian.reschke@gmx.de  Fri Oct 26 05:21:34 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 5D18421F8513 for <ietf@ietfa.amsl.com>; Fri, 26 Oct 2012 05:21:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.675
X-Spam-Level: 
X-Spam-Status: No, score=-103.675 tagged_above=-999 required=5 tests=[AWL=-1.076, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y-7CyoXHY0YI for <ietf@ietfa.amsl.com>; Fri, 26 Oct 2012 05:21:33 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by ietfa.amsl.com (Postfix) with SMTP id EA99D21F84ED for <ietf@ietf.org>; Fri, 26 Oct 2012 05:21:32 -0700 (PDT)
Received: (qmail invoked by alias); 26 Oct 2012 12:21:31 -0000
Received: from mail.greenbytes.de (EHLO [192.168.1.140]) [217.91.35.233] by mail.gmx.net (mp037) with SMTP; 26 Oct 2012 14:21:31 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1/GNx0x5vDGc6NxE31WxHawcrzJcIibElBqP8Ru/W qMYeV/MGG+gmhY
Message-ID: <508A8048.4010007@gmx.de>
Date: Fri, 26 Oct 2012 14:21:28 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121010 Thunderbird/16.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Last Call: <draft-snell-http-prefer-14.txt> (Prefer Header for HTTP) to Proposed Standard
References: <20120914184457.16683.33382.idtracker@ietfa.amsl.com> <6.2.5.6.2.20120914153648.09f87700@resistor.net> <506EF8FA.1030100@gmx.de>
In-Reply-To: <506EF8FA.1030100@gmx.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: SM <sm@resistor.net>, James M Snell <jasnell@gmail.com>, HTTP Working Group <ietf-http-wg@w3.org>, Barry Leiba <barryleiba@computer.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Oct 2012 12:21:34 -0000

On 2012-10-05 17:12, Julian Reschke wrote:
> Hi James,
>
> see below for my (mostly editorial) feedback:

I note that there was no reply to this mail, and at least one problem is 
still present in the latest draft...:

> 2.2.  Examples
>
>     The following examples illustrate the use of various preferences
>     defined by this specification, as well as undefined extensions for
>     strictly illustrative purposes:
>
>     1.  Return a "202 Accepted" response for asynchronous processing if
>     the response cannot be processed within 10 seconds.  An undefined
>     "priority" preference is also specified:
>
>       Prefer: return-asynch, wait=10;
>       Prefer: priority=5;
>
> Shouldn't that be:
>
>       Prefer: return-asynch; wait=10
>       Prefer: priority=5
>
> ???

Best regards, Julian


From lear@cisco.com  Fri Oct 26 05:23:20 2012
Return-Path: <lear@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E3C0B21F8513 for <ietf@ietfa.amsl.com>; Fri, 26 Oct 2012 05:23:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.452
X-Spam-Level: 
X-Spam-Status: No, score=-110.452 tagged_above=-999 required=5 tests=[AWL=0.146, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oabN565QgfqV for <ietf@ietfa.amsl.com>; Fri, 26 Oct 2012 05:23:20 -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 96DBE21F8421 for <ietf@ietf.org>; Fri, 26 Oct 2012 05:23:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4870; q=dns/txt; s=iport; t=1351254199; x=1352463799; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to; bh=JbaX+WBwjHx+RYj0fHSJzxCQFi5k8FsVV5q+Ayelnlc=; b=V8fS4ZdhMqnXdmtxERSmmi5jit68/oL62uC60xSZl9wJp5JAxuSytA3w XDLvkUf6ApS2pNy3/Xs0X5QA09m5E6rXWlEAKJKdfbn4R4M2Zbh8vRY/K o38NKplT4OqXtTeksCYWkRn6p9D8eZqmsP2PeVvINdDYfGsP8JX4J9if4 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvUFAKF/ilCQ/khM/2dsb2JhbABEhheFX7ZBgQiCGgQBAQEEEgEQVQEQCwQRAgEJFgsCAgkDAgECATQJCAYNAQUCAQEFCw6FJweCGBwLnQuNKJJlhhqECIFGhVuBEwOVdoEXjTuBa4Jx
X-IronPort-AV: E=Sophos;i="4.80,654,1344211200"; d="scan'208,217";a="77776895"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-2.cisco.com with ESMTP; 26 Oct 2012 12:23:18 +0000
Received: from dhcp-10-55-94-238.cisco.com (dhcp-10-55-94-238.cisco.com [10.55.94.238]) by ams-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id q9QCNHu6019547 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 26 Oct 2012 12:23:18 GMT
Message-ID: <508A80B5.4020702@cisco.com>
Date: Fri, 26 Oct 2012 14:23:17 +0200
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:16.0) Gecko/20121010 Thunderbird/16.0.1
MIME-Version: 1.0
To: Bob Hinden <bob.hinden@gmail.com>
Subject: Re: [RFC 3777 Update for Vacancies]
References: <D90D92A7-0906-4620-93A0-D116D15A10FA@gmail.com>
In-Reply-To: <D90D92A7-0906-4620-93A0-D116D15A10FA@gmail.com>
X-Enigmail-Version: 1.4.5
Content-Type: multipart/alternative; boundary="------------050606020802010000070608"
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Oct 2012 12:23:21 -0000

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

Bob,

I've read through the draft, and would prefer a different approach. 
Since we already have a recall procedure for contested removals, this
draft should focus itself on uncontested removals, and really just
*absense*.  How do you test if something is uncontested?  Easy enough:
ask the IETF community.  If a single person objects, let's call that
"contested" and go with the other procedure.

Eliot

On 10/24/12 6:14 PM, Bob Hinden wrote:
> The draft that proposes changes to the RFC3777/BCP10 to deal with vacancies is now available.
>
>   http://tools.ietf.org/html/draft-ietf-genarea-bcp10upd-00
>
> Bob
>
> --------------------
>
> From: Internet-Drafts@ietf.org 
> To: i-d-announce@ietf.org 
> Reply-to: Internet-Drafts@ietf.org 
> Subject: I-D ACTION:draft-ietf-genarea-bcp10upd-00.txt 
> X-C5I-RSN: 1/0/935/46939/50333 
>  
> A new Internet-Draft is available from the on-line Internet-Drafts directories. 
>  
> Title : RFC 3777 Update for Vacancies 
> Author(s) : D. Crocker, et al 
> Filename : draft-ietf-genarea-bcp10upd 
> Pages : 4  
> Date : Oct. 24, 2012  
>  
> BCP 10 (RFC 3777) specifies IETF processes for selection, 
> confirmation and recall of appointees to IETF positions. It also 
> refers to the mechanism of resignation as part of a sequence that 
> moves a sitting member to a new IETF position. However it does not 
> more generally deal with vacancies created by resignation, death or 
> uncontested, sustained absence from participation. This update to 
> BCP 10 specifies procedures for handling vacancies. 
>  
> A URL for this Internet-Draft is: 
> http://www.ietf.org/internet-drafts/draft-ietf-genarea-bcp10upd-00.txt 
>  
> Internet-Drafts are also available by anonymous FTP at: 
> ftp://ftp.ietf.org/internet-drafts/ 
>  
>


--------------050606020802010000070608
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">
    Bob,<br>
    <br>
    I've read through the draft, and would prefer a different approach. 
    Since we already have a recall procedure for contested removals,
    this draft should focus itself on uncontested removals, and really
    just <b>absense</b>.  How do you test if something is uncontested? 
    Easy enough: ask the IETF community.  If a single person objects,
    let's call that "contested" and go with the other procedure.<br>
    <br>
    Eliot<br>
    <br>
    <div class="moz-cite-prefix">On 10/24/12 6:14 PM, Bob Hinden wrote:<br>
    </div>
    <blockquote
      cite="mid:D90D92A7-0906-4620-93A0-D116D15A10FA@gmail.com"
      type="cite">
      <pre wrap="">The draft that proposes changes to the RFC3777/BCP10 to deal with vacancies is now available.

  <a class="moz-txt-link-freetext" href="http://tools.ietf.org/html/draft-ietf-genarea-bcp10upd-00">http://tools.ietf.org/html/draft-ietf-genarea-bcp10upd-00</a>

Bob

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

From: <a class="moz-txt-link-abbreviated" href="mailto:Internet-Drafts@ietf.org">Internet-Drafts@ietf.org</a> 
To: <a class="moz-txt-link-abbreviated" href="mailto:i-d-announce@ietf.org">i-d-announce@ietf.org</a> 
Reply-to: <a class="moz-txt-link-abbreviated" href="mailto:Internet-Drafts@ietf.org">Internet-Drafts@ietf.org</a> 
Subject: I-D ACTION:draft-ietf-genarea-bcp10upd-00.txt 
X-C5I-RSN: 1/0/935/46939/50333 
 
A new Internet-Draft is available from the on-line Internet-Drafts directories. 
 
Title : RFC 3777 Update for Vacancies 
Author(s) : D. Crocker, et al 
Filename : draft-ietf-genarea-bcp10upd 
Pages : 4  
Date : Oct. 24, 2012  
 
BCP 10 (RFC 3777) specifies IETF processes for selection, 
confirmation and recall of appointees to IETF positions. It also 
refers to the mechanism of resignation as part of a sequence that 
moves a sitting member to a new IETF position. However it does not 
more generally deal with vacancies created by resignation, death or 
uncontested, sustained absence from participation. This update to 
BCP 10 specifies procedures for handling vacancies. 
 
A URL for this Internet-Draft is: 
<a class="moz-txt-link-freetext" href="http://www.ietf.org/internet-drafts/draft-ietf-genarea-bcp10upd-00.txt">http://www.ietf.org/internet-drafts/draft-ietf-genarea-bcp10upd-00.txt</a> 
 
Internet-Drafts are also available by anonymous FTP at: 
<a class="moz-txt-link-freetext" href="ftp://ftp.ietf.org/internet-drafts/">ftp://ftp.ietf.org/internet-drafts/</a> 
 

</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------050606020802010000070608--

From brian.e.carpenter@gmail.com  Fri Oct 26 05:24:57 2012
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D956121F855A for <ietf@ietfa.amsl.com>; Fri, 26 Oct 2012 05:24:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.693
X-Spam-Level: 
X-Spam-Status: No, score=-101.693 tagged_above=-999 required=5 tests=[AWL=-0.002, BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BP-Fdih3243C for <ietf@ietfa.amsl.com>; Fri, 26 Oct 2012 05:24:57 -0700 (PDT)
Received: from mail-wg0-f44.google.com (mail-wg0-f44.google.com [74.125.82.44]) by ietfa.amsl.com (Postfix) with ESMTP id 3802B21F84ED for <ietf@ietf.org>; Fri, 26 Oct 2012 05:24:57 -0700 (PDT)
Received: by mail-wg0-f44.google.com with SMTP id dr13so1477651wgb.13 for <ietf@ietf.org>; Fri, 26 Oct 2012 05:24:56 -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=3t/+SpeBqzl6DnWiQWlodvwl7J0n9uUag9J1i0FiXyI=; b=dyTOWMohBrPlnz1Pet2QLhaF6bP1u1gzf/UZqq4ylLCIzz5BbVrDhpxzE7EWULqMLJ 3wYqNMjKj8FE06b4sFXAbcyUy/2cUNCE6XntbFqWVT8bjcRDZFu1P4fdFRMfU1gBOVZJ mGB0yZTPFz5/+zkpaUPFUBrIewy19f1R8+80cbrz7P2dFZTc+bn2FAZ2JHnpFGLiQmCT Xcp/brnGNOfeN4yiy0TGIVnyzIhcwRtC8TQvIV9521ci0S/KcU52oGwMSq+/ncO2rOfw fVkv41qJHVJlK9lVsfKl8/cSr0X1C0vPKYT7m4OVzXbC7kBZRQ2REAqUlOF8OtIuqXJN kC4Q==
Received: by 10.216.211.19 with SMTP id v19mr13669237weo.91.1351254296347; Fri, 26 Oct 2012 05:24:56 -0700 (PDT)
Received: from [192.168.1.65] (host-2-102-216-184.as13285.net. [2.102.216.184]) by mx.google.com with ESMTPS id dm2sm893080wib.4.2012.10.26.05.24.54 (version=SSLv3 cipher=OTHER); Fri, 26 Oct 2012 05:24:55 -0700 (PDT)
Message-ID: <508A8120.9010407@gmail.com>
Date: Fri, 26 Oct 2012 13:25:04 +0100
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Sam Hartman <hartmans-ietf@mit.edu>
Subject: Re: ISOC BOT and Process BCPs
References: <20121025125351.285D818C0A0@mercury.lcs.mit.edu>	<20121025204915.6C09621F8491@ietfa.amsl.com> <tslhapi5fno.fsf@mit.edu>	<6.2.5.6.2.20121025232216.094f24e8@resistor.net> <tsly5it32ep.fsf_-_@mit.edu>
In-Reply-To: <tsly5it32ep.fsf_-_@mit.edu>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: SM <sm@resistor.net>, Theodore Ts'o <tytso@mit.edu>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Oct 2012 12:24:58 -0000

Hi Sam,

> So, I'm puzzled by this.  my claim was that ISOC needed to approve
> process related BCPs.  If you take a look at RFC 2031, it supports that
> claim.  However, I'd kind of expect the other half of this to be in RFC
> 2026.  I certainly recall us sending things like BCP 101 before the ISOC
> BOT. I also think we sent a couple of other documents there because they
> were process documents.
> However this is clearly more complex than I thought it was.
> 
> Scott, or anyone else with more history, can you tell us a story about
> how this works?

My recollection from a few years ago is that we put various new process BCPs
in front of the ISOC Board and they minuted that they took note of them.
They were specifically not asked to approve them.

It's quite possible that this has been overlooked in some cases. Somebody
would have to grep the ISOC Board minutes to be sure.

   Brian




From mstjohns@comcast.net  Fri Oct 26 07:29:31 2012
Return-Path: <mstjohns@comcast.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 832A821F8662 for <ietf@ietfa.amsl.com>; Fri, 26 Oct 2012 07:29:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.355
X-Spam-Level: 
X-Spam-Status: No, score=-100.355 tagged_above=-999 required=5 tests=[AWL=0.082, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DzQUfRIVPgrr for <ietf@ietfa.amsl.com>; Fri, 26 Oct 2012 07:29:31 -0700 (PDT)
Received: from qmta03.westchester.pa.mail.comcast.net (qmta03.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:32]) by ietfa.amsl.com (Postfix) with ESMTP id B34B021F84D3 for <ietf@ietf.org>; Fri, 26 Oct 2012 07:29:30 -0700 (PDT)
Received: from omta05.westchester.pa.mail.comcast.net ([76.96.62.43]) by qmta03.westchester.pa.mail.comcast.net with comcast id Fm561k0070vyq2s53qVbyn; Fri, 26 Oct 2012 14:29:35 +0000
Received: from Mike-T530.comcast.net ([68.83.212.126]) by omta05.westchester.pa.mail.comcast.net with comcast id FqVw1k01B2kB7pQ3RqVxx9; Fri, 26 Oct 2012 14:29:57 +0000
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Fri, 26 Oct 2012 10:29:30 -0400
To: Bob Hinden <bob.hinden@gmail.com>,ietf@ietf.org
From: Michael StJohns <mstjohns@comcast.net>
Subject: Re: [RFC 3777 Update for Vacancies]
In-Reply-To: <D90D92A7-0906-4620-93A0-D116D15A10FA@gmail.com>
References: <D90D92A7-0906-4620-93A0-D116D15A10FA@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Message-Id: <20121026142930.B34B021F84D3@ietfa.amsl.com>
Cc: Bob Hinden <bob.hinden@gmail.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Oct 2012 14:29:31 -0000

I've read the draft.  I think its the wrong approach, mainly because its focusing on the current problem rather than a new mechanism.

In general, I know of 5 ways an elected or appointed position may become vacant:  resignation, death, incapacity, recall or expulsion.

We currently have mechanisms in place for 3 of the 5.  I'm not sure at this point how to deal with incapacity, and I think it can actually be handled (except possibly for the IETF chair) under recall or expulsion or resignation.  (There's also removal for appointees where the appointing entity has removal rights).

I'm using "expulsion" here the way its used in the US political system - a legislative body may choose to expel one of its members for various reasons.  I propose that we define such a mechanism for the IETF bodies.


See below. 

And I'm not proposing that this be adopted in a hurry to fix the current problem.  

Mike




_____________________________________________________
Expulsion - General:

Members may be expelled from the bodies to which they belong by votes of other members of those bodies.  The expelling bodies need not give or have any public reason for the expulsion, but should consider the impact on the standards process prior to proceeding with the expulsion.


Expulsion - the IETF chair:

The IETF chair is not subject to expulsion.  In the event the IETF chair is not available, and at the request of 2/3 of the remaining voting members of the IESG, the ISOC President shall appoint a temporary replacement with the advice and consent of the IAB who shall serve until the end of the IETF chair's term whenever the IETF chair is unavailable.  The recommendation is that a former IETF or IAB chair be appointed if available.  The replacement serves at the pleasure of the ISOC president and may be replaced if, in the sole judgement of the ISOC president, replacement is required.

Expulsion of liaison members:

If 2/3 of the voting members (minus the liaison member in question if that member is a voting member) concur, the liaison member is expelled and the appointing organization shall appoint a replacement.  A member not subject to removal by their appointing body is not considered a liaison member for the purposes of this section.

Expulsion of all other members.

If 2/3 of the voting members (minus the member in question, if that member is a voting member) concur notice shall be sent to the appropriate IETF mailing lists.  The notice shall be repeated three times with a two week interval between each notice.  The notice shall indicate the intent to expel the member and shall request the member show cause to the confirming body as to why the expulsion should not occur.

One week after the last notice, the appropriate confirming body (e.g. IAB for IESG, IESG for IAOC, etc), shall consider the expulsion request and any response given by the member.  If 2/3 of the voting members of the confirming body concur, the member shall be removed and the position be considered vacant.




At 12:14 PM 10/24/2012, Bob Hinden wrote:
>The draft that proposes changes to the RFC3777/BCP10 to deal with vacancies is now available.
>
>  http://tools.ietf.org/html/draft-ietf-genarea-bcp10upd-00
>
>Bob
>
>--------------------
>
>From: Internet-Drafts@ietf.org 
>To: i-d-announce@ietf.org 
>Reply-to: Internet-Drafts@ietf.org 
>Subject: I-D ACTION:draft-ietf-genarea-bcp10upd-00.txt 
>X-C5I-RSN: 1/0/935/46939/50333 
> 
>A new Internet-Draft is available from the on-line Internet-Drafts directories. 
> 
>Title : RFC 3777 Update for Vacancies 
>Author(s) : D. Crocker, et al 
>Filename : draft-ietf-genarea-bcp10upd 
>Pages : 4  
>Date : Oct. 24, 2012  
> 
>BCP 10 (RFC 3777) specifies IETF processes for selection, 
>confirmation and recall of appointees to IETF positions. It also 
>refers to the mechanism of resignation as part of a sequence that 
>moves a sitting member to a new IETF position. However it does not 
>more generally deal with vacancies created by resignation, death or 
>uncontested, sustained absence from participation. This update to 
>BCP 10 specifies procedures for handling vacancies. 
> 
>A URL for this Internet-Draft is: 
>http://www.ietf.org/internet-drafts/draft-ietf-genarea-bcp10upd-00.txt 
> 
>Internet-Drafts are also available by anonymous FTP at: 
>ftp://ftp.ietf.org/internet-drafts/ 
> 



From lear@cisco.com  Fri Oct 26 08:02:45 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 0FCFB21F8644 for <ietf@ietfa.amsl.com>; Fri, 26 Oct 2012 08:02:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.455
X-Spam-Level: 
X-Spam-Status: No, score=-110.455 tagged_above=-999 required=5 tests=[AWL=0.144, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Vkzz9rLo6-1a for <ietf@ietfa.amsl.com>; Fri, 26 Oct 2012 08:02:44 -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 3CB9021F8232 for <ietf@ietf.org>; Fri, 26 Oct 2012 08:02:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=316; q=dns/txt; s=iport; t=1351263764; x=1352473364; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=iceja+vZTbSUSyWBUXVSyUq6nSNBmvD5wI7Sw/lojR8=; b=FrQOjLsJBtNQ4ENvCE4kOcr1itshuL2yH5pAO03g2/R65spKw1MzDIuz wFS/kWO5P+CwYJvgqi2AhycDcDMg7WFDTOnKHDhZL3IkCsKDOZdzImz0W nsoB3funEs28s8UiOBr7SGUW/bevYJcnL6IlbMEFX328cb9WkyKRycFnS M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAFAJ6lilCQ/khL/2dsb2JhbABEhhi8J4EIgh4BAQEEEgEQVQEQCxgCAgUWCwICCQMCAQIBRQYNAQcBAR6HZJ0tjSySboEghH6EDYchgRMDlXOOU4FrgnE
X-IronPort-AV: E=Sophos;i="4.80,654,1344211200"; d="scan'208";a="145869774"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by ams-iport-1.cisco.com with ESMTP; 26 Oct 2012 15:02:42 +0000
Received: from dhcp-10-55-94-238.cisco.com (dhcp-10-55-94-238.cisco.com [10.55.94.238]) by ams-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id q9QF2f3l011604 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 26 Oct 2012 15:02:42 GMT
Message-ID: <508AA611.7030206@cisco.com>
Date: Fri, 26 Oct 2012 17:02:41 +0200
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:16.0) Gecko/20121010 Thunderbird/16.0.1
MIME-Version: 1.0
To: Michael StJohns <mstjohns@comcast.net>
Subject: Re: [RFC 3777 Update for Vacancies]
References: <D90D92A7-0906-4620-93A0-D116D15A10FA@gmail.com> <20121026142930.B34B021F84D3@ietfa.amsl.com>
In-Reply-To: <20121026142930.B34B021F84D3@ietfa.amsl.com>
X-Enigmail-Version: 1.4.5
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Bob Hinden <bob.hinden@gmail.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Oct 2012 15:02:45 -0000

On 10/26/12 4:29 PM, Michael StJohns wrote:
> I'm using "expulsion" here the way its used in the US political system - a legislative body may choose to expel one of its members for various reasons.  I propose that we define such a mechanism for the IETF bodies.
>

Why should bodies have this right?

Eliot

From mstjohns@comcast.net  Fri Oct 26 08:11:52 2012
Return-Path: <mstjohns@comcast.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DEA7121F8678 for <ietf@ietfa.amsl.com>; Fri, 26 Oct 2012 08:11:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.362
X-Spam-Level: 
X-Spam-Status: No, score=-100.362 tagged_above=-999 required=5 tests=[AWL=0.075, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nUdBVMoGZu-l for <ietf@ietfa.amsl.com>; Fri, 26 Oct 2012 08:11:52 -0700 (PDT)
Received: from qmta09.westchester.pa.mail.comcast.net (qmta09.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:96]) by ietfa.amsl.com (Postfix) with ESMTP id 4F5AF21F862D for <ietf@ietf.org>; Fri, 26 Oct 2012 08:11:52 -0700 (PDT)
Received: from omta08.westchester.pa.mail.comcast.net ([76.96.62.12]) by qmta09.westchester.pa.mail.comcast.net with comcast id FnMw1k0030Fqzac59rBwyT; Fri, 26 Oct 2012 15:11:56 +0000
Received: from Mike-T530.comcast.net ([68.83.212.126]) by omta08.westchester.pa.mail.comcast.net with comcast id FrBf1k00d2kB7pQ3UrBfnq; Fri, 26 Oct 2012 15:11:40 +0000
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Fri, 26 Oct 2012 11:11:52 -0400
To: Eliot Lear <lear@cisco.com>
From: Michael StJohns <mstjohns@comcast.net>
Subject: Re: [RFC 3777 Update for Vacancies]
In-Reply-To: <508AA611.7030206@cisco.com>
References: <D90D92A7-0906-4620-93A0-D116D15A10FA@gmail.com> <20121026142930.B34B021F84D3@ietfa.amsl.com> <508AA611.7030206@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Message-Id: <20121026151152.4F5AF21F862D@ietfa.amsl.com>
Cc: Bob Hinden <bob.hinden@gmail.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Oct 2012 15:11:53 -0000

At 11:02 AM 10/26/2012, Eliot Lear wrote:

>On 10/26/12 4:29 PM, Michael StJohns wrote:
>> I'm using "expulsion" here the way its used in the US political system - a legislative body may choose to expel one of its members for various reasons.  I propose that we define such a mechanism for the IETF bodies.
>>
>
>Why should bodies have this right?


I'm not saying they should - but that seems to be what Bob et al are asking for.  Doing it this way means you don't have to reach to questions of what constitutes an "absence" or "abandonment" - subjective judgements.

If someone pisses his fellow members off sufficiently that they can't work with him/her for whatever reason you have this.

And it's still subject to veto by the confirming body, so the expulsion reasons will have to be pretty egregious to get through two votes of 2/3. 

Mike



>Eliot



From acooper@cdt.org  Fri Oct 26 08:35:11 2012
Return-Path: <acooper@cdt.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CC55C21F856D for <ietf@ietfa.amsl.com>; Fri, 26 Oct 2012 08:35:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.339
X-Spam-Level: 
X-Spam-Status: No, score=-101.339 tagged_above=-999 required=5 tests=[AWL=-0.959, BAYES_00=-2.599, TVD_SPACE_RATIO=2.219, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vZ7cbfCNmUHv for <ietf@ietfa.amsl.com>; Fri, 26 Oct 2012 08:35:11 -0700 (PDT)
Received: from mail.maclaboratory.net (mail.maclaboratory.net [209.190.215.232]) by ietfa.amsl.com (Postfix) with ESMTP id 3AD3621F856B for <ietf@ietf.org>; Fri, 26 Oct 2012 08:35:11 -0700 (PDT)
X-Footer: Y2R0Lm9yZw==
Received: from localhost ([127.0.0.1]) by mail.maclaboratory.net (using TLSv1/SSLv3 with cipher AES128-SHA (128 bits)) for ietf@ietf.org; Fri, 26 Oct 2012 11:35:08 -0400
From: Alissa Cooper <acooper@cdt.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: draft-iab-filtering-considerations
Date: Fri, 26 Oct 2012 11:35:06 -0400
Message-Id: <0D4D95FE-8A8E-46C4-9F84-93FEF4B263D9@cdt.org>
To: IETF Discussion Mailing List <ietf@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1084)
X-Mailer: Apple Mail (2.1084)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Oct 2012 15:35:11 -0000

The IAB is working on a document about "Technical Considerations for =
Internet Service Filtering," =
<http://tools.ietf.org/html/draft-iab-filtering-considerations-01>. =
Feedback and discussion are welcome on the architecture-discuss list, =
<https://www.ietf.org/mailman/listinfo/architecture-discuss>.=


From john-ietf@jck.com  Fri Oct 26 08:39:58 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 1AC5A21F861E for <ietf@ietfa.amsl.com>; Fri, 26 Oct 2012 08:39:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.544
X-Spam-Level: 
X-Spam-Status: No, score=-102.544 tagged_above=-999 required=5 tests=[AWL=0.055, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EbrNkbEWwOXe for <ietf@ietfa.amsl.com>; Fri, 26 Oct 2012 08:39:57 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 253B721F8615 for <ietf@ietf.org>; Fri, 26 Oct 2012 08:39:57 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1TRm0n-000Gos-P9; Fri, 26 Oct 2012 11:39:53 -0400
Date: Fri, 26 Oct 2012 11:39:48 -0400
From: John C Klensin <john-ietf@jck.com>
To: Michael StJohns <mstjohns@comcast.net>, Eliot Lear <lear@cisco.com>
Subject: Re: [RFC 3777 Update for Vacancies]
Message-ID: <B5A61583C347AB7D9F752B11@JcK-HP8200.jck.com>
In-Reply-To: <20121026151152.4F5AF21F862D@ietfa.amsl.com>
References: <D90D92A7-0906-4620-93A0-D116D15A10FA@gmail.com> <20121026142930.B34B021F84D3@ietfa.amsl.com> <508AA611.7030206@cisco.com> <20121026151152.4F5AF21F862D@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: Bob Hinden <bob.hinden@gmail.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Oct 2012 15:39:58 -0000

--On Friday, October 26, 2012 11:11 -0400 Michael StJohns
<mstjohns@comcast.net> wrote:

>...
>> On 10/26/12 4:29 PM, Michael StJohns wrote:
>>> I'm using "expulsion" here the way its used in the US
>>> political system - a legislative body may choose to expel
>>> one of its members for various reasons.  I propose that we
>>> define such a mechanism for the IETF bodies.
>>> 
>> 
>> Why should bodies have this right?

> I'm not saying they should - but that seems to be what Bob et
> al are asking for.  Doing it this way means you don't have to
> reach to questions of what constitutes an "absence" or
> "abandonment" - subjective judgements.
> 
> If someone pisses his fellow members off sufficiently that
> they can't work with him/her for whatever reason you have this.
> 
> And it's still subject to veto by the confirming body, so the
> expulsion reasons will have to be pretty egregious to get
> through two votes of 2/3. 

Mike,

This is exactly the sort of path I don't want to go down, at
least without a lot of consideration of its possible
implications.  Remember that the community has refused to even
let IAB or IAOC members sign/endorse a recall petition against
one of their own number and that process provides far better
checks against abuses or personality problems than any "expel
member" plan, even with a requirement for confirming body
signoff.

It is possible for someone to be in a tiny minority (perhaps of
one) in those bodies, thoroughly irritate everyone else about
positions, and still be acting in the best interests of the
community, maybe even reflecting community consensus.  Having
watched a number of IABs from the inside, I wouldn't count on
them, and much less on the ISOC BoT, to say "no" to an internal
membership management request from the IESG or IAB respectively.
There have been exceptional years, but the general instinct in
matters that are really internal to how the other body functions
is to defer to that body on the grounds that they know what they
need.

In principle, I have no problem with setting up a list of
repeated/ long-term non-feasance, non-appearance, or
non-responsiveness conditions that are treated as equivalent to
a more formal resignation unless the body of which that person
is a member votes to waive the rule (i.e., not accept the
resignation).    I actually think that would be completely
reasonable and that we probably should have established such
principles years ago even though I'd expect a lot of quibbling
about setting the thresholds for "repeated/ long-term".

But I believe we should not design things around this particular
case or create the perception that we are doing so by changing
processes while the case is still open.  Indeed, I think
fairness dictates that people should know about such rules and
their implications at the time they accept nomination for a
position -- it becomes part of what they are signing up for --
rather than applying such a rule to today's incumbents.

best,
   john




From spencer@wonderhamster.org  Fri Oct 26 09:00:25 2012
Return-Path: <spencer@wonderhamster.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A21C221F8641 for <ietf@ietfa.amsl.com>; Fri, 26 Oct 2012 09:00:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.611
X-Spam-Level: 
X-Spam-Status: No, score=-102.611 tagged_above=-999 required=5 tests=[AWL=-0.012, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SGHirfqjHCSZ for <ietf@ietfa.amsl.com>; Fri, 26 Oct 2012 09:00:24 -0700 (PDT)
Received: from mout.perfora.net (mout.perfora.net [74.208.4.195]) by ietfa.amsl.com (Postfix) with ESMTP id 0C0FD21F8634 for <ietf@ietf.org>; Fri, 26 Oct 2012 09:00:24 -0700 (PDT)
Received: from [192.168.1.79] (99-108-174-213.lightspeed.rcsntx.sbcglobal.net [99.108.174.213]) by mrelay.perfora.net (node=mrus2) with ESMTP (Nemesis) id 0LqQWn-1Sx6DI2Ioz-00dbB2; Fri, 26 Oct 2012 12:00:13 -0400
Message-ID: <508AB382.6050106@wonderhamster.org>
Date: Fri, 26 Oct 2012 11:00:02 -0500
From: Spencer Dawkins <spencer@wonderhamster.org>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:16.0) Gecko/20121010 Thunderbird/16.0.1
MIME-Version: 1.0
To: Jari Arkko <jari.arkko@piuha.net>
Subject: Re: I-D Action: draft-jaeggli-interim-observations-00.txt
References: <042001cdab1d$df26b6b0$9d742410$@olddog.co.uk> <507D7A8C.1090201@piuha.net>
In-Reply-To: <507D7A8C.1090201@piuha.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Provags-ID: V02:K0:68wUOCCCkP2fMaCeo3Z0CqcaG2TWJ6mvPLj+RynuoSH wrG7DnSF5nylhIW+BVqIvT08z7UWKSmnW35pCpHSBhpBtYc9je MOf7ffFOqfNT5X8BbsiUa+6MJcrEpl5BFV+2+CdXlGGxRX7eWO biUkBSlvpgyJp1Ic+q7XWX1vZwuDDYdm31IJ3z1kJZkHb5ZaYA rzkaEM2PtaDHymW2s7nr/7fgQkDga6cTaZGa5IzQlA6GPEceIB hWaSdz17BDGeT8oLl197smfJXPTA9qumRxXP1DVt+GOS8FlwxX 3MGcl49ZhslSB8Xf+dDep46BjCrmmwjePdKOXmjbueEVTftPOI iFb6OE0h9OxqrIJWkQC0D1iHgpq6EOOp7xy1uC8nO
Cc: jjaeggli@zynga.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, 26 Oct 2012 16:00:25 -0000

Thank you, Joel, for putting pen to paper (pixels to glass?) on this, 
and thank you, Jari, Randy, and Warren for sharing your thoughts.

As was pointed out, we've had conversations about LIMs previously. It 
might be worth asking Ray to provide a paragraph or two on history and 
the motivations when some of the previous LIMs were discussed.

My memory of the proposed 2009 Malta LIM (supplemented by Teh Google) 
was that the working groups planning to meet weren't just from one area 
of interest (something like four RAI groups, plus SOFTWIRES and BEHAVE). 
I don't know if that helps or hurts - at a minimum, RIPE/foonog may not 
be the draw for RAI that it was for the groups that met this time.

FWIW, http://trac.tools.ietf.org/2009/jan-large-interim/ says 60 
potential attendees didn't qualify as a large interim :-)

Spencer

From joelja@bogus.com  Fri Oct 26 09:16:04 2012
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CC0EF21F8633 for <ietf@ietfa.amsl.com>; Fri, 26 Oct 2012 09:16:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.428
X-Spam-Level: 
X-Spam-Status: No, score=-102.428 tagged_above=-999 required=5 tests=[AWL=0.171, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PtrN5yV8coTA for <ietf@ietfa.amsl.com>; Fri, 26 Oct 2012 09:16:04 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 3B7F421F8629 for <ietf@ietf.org>; Fri, 26 Oct 2012 09:16:04 -0700 (PDT)
Received: from joels-MacBook-Air.local (host-64-47-153-50.masergy.com [64.47.153.50]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id q9QGG3tV082017 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Fri, 26 Oct 2012 16:16:03 GMT (envelope-from joelja@bogus.com)
Message-ID: <508AB73D.401@bogus.com>
Date: Fri, 26 Oct 2012 09:15:57 -0700
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: Spencer Dawkins <spencer@wonderhamster.org>
Subject: Re: I-D Action: draft-jaeggli-interim-observations-00.txt
References: <042001cdab1d$df26b6b0$9d742410$@olddog.co.uk> <507D7A8C.1090201@piuha.net> <508AB382.6050106@wonderhamster.org>
In-Reply-To: <508AB382.6050106@wonderhamster.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Fri, 26 Oct 2012 16:16:03 +0000 (UTC)
Cc: jjaeggli@zynga.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, 26 Oct 2012 16:16:04 -0000

On 10/26/12 9:00 AM, Spencer Dawkins wrote:
> Thank you, Joel, for putting pen to paper (pixels to glass?) on this, 
> and thank you, Jari, Randy, and Warren for sharing your thoughts.
>
> As was pointed out, we've had conversations about LIMs previously. It 
> might be worth asking Ray to provide a paragraph or two on history and 
> the motivations when some of the previous LIMs were discussed.
>
> My memory of the proposed 2009 Malta LIM (supplemented by Teh Google) 
> was that the working groups planning to meet weren't just from one 
> area of interest (something like four RAI groups, plus SOFTWIRES and 
> BEHAVE). I don't know if that helps or hurts - at a minimum, 
> RIPE/foonog may not be the draw for RAI that it was for the groups 
> that met this time.
yeah I didn't have enough useful data on the proposed meeting in malta 
to really commit it to the initial draft.

for one I had the dates wrong in my notes.

> FWIW, http://trac.tools.ietf.org/2009/jan-large-interim/ says 60 
> potential attendees didn't qualify as a large interim :-)
that is useful.
> Spencer
>


From mstjohns@comcast.net  Fri Oct 26 09:25:04 2012
Return-Path: <mstjohns@comcast.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9FF1C21F8559 for <ietf@ietfa.amsl.com>; Fri, 26 Oct 2012 09:25:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.367
X-Spam-Level: 
X-Spam-Status: No, score=-100.367 tagged_above=-999 required=5 tests=[AWL=0.070, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YNjRz0f+vs6J for <ietf@ietfa.amsl.com>; Fri, 26 Oct 2012 09:25:04 -0700 (PDT)
Received: from qmta02.westchester.pa.mail.comcast.net (qmta02.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:24]) by ietfa.amsl.com (Postfix) with ESMTP id 1CF8E21F852A for <ietf@ietf.org>; Fri, 26 Oct 2012 09:25:03 -0700 (PDT)
Received: from omta06.westchester.pa.mail.comcast.net ([76.96.62.51]) by qmta02.westchester.pa.mail.comcast.net with comcast id FmiH1k00416LCl051sR8Rk; Fri, 26 Oct 2012 16:25:08 +0000
Received: from Mike-T530.comcast.net ([68.83.212.126]) by omta06.westchester.pa.mail.comcast.net with comcast id FsQb1k00M2kB7pQ3SsQbqG; Fri, 26 Oct 2012 16:24:36 +0000
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Fri, 26 Oct 2012 12:25:05 -0400
To: John C Klensin <john-ietf@jck.com>,Eliot Lear <lear@cisco.com>
From: Michael StJohns <mstjohns@comcast.net>
Subject: Re: [RFC 3777 Update for Vacancies]
In-Reply-To: <B5A61583C347AB7D9F752B11@JcK-HP8200.jck.com>
References: <D90D92A7-0906-4620-93A0-D116D15A10FA@gmail.com> <20121026142930.B34B021F84D3@ietfa.amsl.com> <508AA611.7030206@cisco.com> <20121026151152.4F5AF21F862D@ietfa.amsl.com> <B5A61583C347AB7D9F752B11@JcK-HP8200.jck.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Message-Id: <20121026162504.1CF8E21F852A@ietfa.amsl.com>
Cc: Bob Hinden <bob.hinden@gmail.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Oct 2012 16:25:04 -0000

At 11:39 AM 10/26/2012, John C Klensin wrote:
>In principle, I have no problem with setting up a list of
>repeated/ long-term non-feasance, non-appearance, or
>non-responsiveness conditions that are treated as equivalent to
>a more formal resignation unless the body of which that person
>is a member votes to waive the rule (i.e., not accept the
>resignation).    I actually think that would be completely
>reasonable and that we probably should have established such
>principles years ago even though I'd expect a lot of quibbling
>about setting the thresholds for "repeated/ long-term".


This is exactly what I'd like to avoid.  No matter how we set the conditions, someone will argue - successfully - that the conditions are not met.  (For example, I attend one out of every 3 meetings for exactly 5 minutes - I obviously haven't abandoned the position, but I really have abrogated my responsibilities).  Etc etc etc etc etc... 

Or something will come up that the conditions just never anticipated (the current example springs to mind).


Let the bodies decide if the member is doing their job.  If 2/3 of them think no and they can convince 2/3 of the confirming body, then its time for him to go.  This handles pretty much any "emergency" condition I can think of and does it in only a little more than a month.  And note, that unlike a recall, there is no bar to being re-appointed by the Nomcom in the following term.

The recall process remains for the body of the IETF to be able to affect a removal with some amount of formalism.

I'm pretty much going to object to any condition based model that anyone proposes, because we're really bad at a) figuring out the complete list of all possible conditions that could ever happen, b) writing conditions that can be objectively evaluated, and c) figuring out how to decide when specific conditions are met (because of the lack of objective criteria).  In addition, people have been carping on the mailing list about how we need to be flexible - and condition lists by their very nature are not flexible.







From dougb@dougbarton.us  Fri Oct 26 10:02:12 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 537E921F864D for <ietf@ietfa.amsl.com>; Fri, 26 Oct 2012 10:02:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.496
X-Spam-Level: 
X-Spam-Status: No, score=-3.496 tagged_above=-999 required=5 tests=[AWL=0.103,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id skKm1xeom8kI for <ietf@ietfa.amsl.com>; Fri, 26 Oct 2012 10:02:11 -0700 (PDT)
Received: from mail2.fluidhosting.com (mx22.fluidhosting.com [204.14.89.5]) by ietfa.amsl.com (Postfix) with ESMTP id 5F90021F8611 for <ietf@ietf.org>; Fri, 26 Oct 2012 10:02:10 -0700 (PDT)
Received: (qmail 18375 invoked by uid 399); 26 Oct 2012 17:01:54 -0000
Received: from unknown (HELO ?192.168.0.102?) (dougb@dougbarton.us@12.207.105.210) by mail2.fluidhosting.com with ESMTPAM; 26 Oct 2012 17:01:54 -0000
X-Originating-IP: 12.207.105.210
X-Sender: dougb@dougbarton.us
Message-ID: <508AC20C.2030609@dougbarton.us>
Date: Fri, 26 Oct 2012 10:02:04 -0700
From: Doug Barton <dougb@dougbarton.us>
Organization: http://SupersetSolutions.com/
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121010 Thunderbird/16.0.1
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Just so I'm clear
References: <20121023192135.203AC18C0A4@mercury.lcs.mit.edu>	<5086EF82.9060900@dougbarton.us> <20121023200713.GC1861@nsn.com>	<5086FBCE.2070503@dougbarton.us> <20121023213251.GF27557@verdi>	<50873AB4.1000905@dougbarton.us>	<20121024034736.GC52558@crankycanuck.ca>	<50876D39.20502@dougbarton.us> <508773E7.10203@cisco.com>	<50877633.1000402@dougbarton.us>	<EA9BEA2E-EE96-4E80-B719-652BBD620A79@lilacglade.org> <508842C2.4020203@dougbarton.us> <5088EE5A.4090103@gmail.com> <508987B9.2040207@dougbarton.us> <508A39A0.3090602@gmail.com>
In-Reply-To: <508A39A0.3090602@gmail.com>
X-Enigmail-Version: 1.4.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, 26 Oct 2012 17:02:12 -0000

On 10/26/2012 12:20 AM, Brian E Carpenter wrote:
> On 25/10/2012 19:40, Doug Barton wrote:
>> On 10/25/2012 12:46 AM, Brian E Carpenter wrote:
>>> On 24/10/2012 20:34, Doug Barton wrote: ...
>>>> ... Nothing in the text suggests an unfettered right of
>>>> creating new definitions of "vacant."
>>> You mean, new compared to the first definition in
>>> Merriam-Webster.com?
>>> 
>>> 1: not occupied by an incumbent, possessor, or officer <a vacant
>>> office> <vacant thrones>
>> 
>> C'mon Brian, not helpful. We're talking about the BCP 101
>> "definition of vacant" which unfortunately is not nearly so
>> precise. If there were no mention of 3777 in the text then there
>> would appear to be more leeway in declaring a position vacant.
> 
> There is no definition of "vacant" or "vacancy" in RFC 3777 (except
> for the special case of a mid-term vacancy caused by the appointment
> of the member to another IETF position). Therefore it seems
> reasonable to resort to the dictionary.

Except that, unfortunately, it isn't (reasonable). The equivalent
situation is something akin to a corporation's bylaws. Given that there
are 2 procedures actually defined in BCP 101 (vacant, and recall) it is
not Ok to simply make up a new procedure.

With all due respect to Marshall, he has clearly abrogated his duty, and
is subject to recall. While the argument of "not communicative ==
vacant" is attractive for its expedience, the document not only does not
say that, it has specific language that defines what to do in the case
that a member is not doing their job, "abrogates his or her duties ->
recall."

>>> Objectively and factually, that seems to be the case.
>> 
>> I get that this is what you believe to be true, however what some
>> of us are saying is that we don't agree.
> 
> Actually I haven't seen that. I've seen people assert that our
> process doesn't document the case of a non-responsive absentee
> member, but I haven't seen anyone deny that we have an empty seat.

Several of us have said it several times now.

All that said, I agree with the previous poster who pointed out that
nothing new has been said on this thread for a while now, and it's high
time we got the opinion of competent legal counsel. If we have a strong
legal opinion that declaring the position vacant by fiat is an
acceptable course of action, I will drop my objection.

Doug

From rja.lists@gmail.com  Fri Oct 26 10:15:44 2012
Return-Path: <rja.lists@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 178EE21F863C for <ietf@ietfa.amsl.com>; Fri, 26 Oct 2012 10:15:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.196
X-Spam-Level: 
X-Spam-Status: No, score=-3.196 tagged_above=-999 required=5 tests=[AWL=-0.197, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id x6BfhvbKeYn4 for <ietf@ietfa.amsl.com>; Fri, 26 Oct 2012 10:15:43 -0700 (PDT)
Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id 573F421F8634 for <ietf@ietf.org>; Fri, 26 Oct 2012 10:15:43 -0700 (PDT)
Received: by mail-vb0-f44.google.com with SMTP id fc26so3602850vbb.31 for <ietf@ietf.org>; Fri, 26 Oct 2012 10:15:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to:x-mailer; bh=KTzuJ3keLhEyGohw/K9xabkkjQXRZiCrQt9KMeo6JfM=; b=livuazgISVbTVtCkmP5AagR2HiIgPkWD/QNClS5qKQtqmOoia/8P729mchepdz5k/R xvuIufULKKUdlJd6pyYppy2hAc4vhcHAluFZ1UShjskDqiirVy8wzhhBmZrIOKtlbLgR 3clhLsMODQionVMqqQUSVwzzWcyL8QuvoSTS2Dj+XPYWBIviIO4azTR5ioDxMkipNaZM GraiEu1f8Y4jKuRpQMoFkCnyW7jEpcXhsCeHJZ6e1Ytku0yMS9J0U8jfVoMvd7UD/FMk WmCeMh5njH+eOqiNfflylUa1JzAJFuTIhPPXzYvuSq1WrOWmpqY27sM/Vftob/j9Y01s aN2Q==
Received: by 10.220.221.203 with SMTP id id11mr19894191vcb.42.1351271742810; Fri, 26 Oct 2012 10:15:42 -0700 (PDT)
Received: from [10.30.20.14] (pool-74-110-100-136.nrflva.fios.verizon.net. [74.110.100.136]) by mx.google.com with ESMTPS id o13sm1097848vde.21.2012.10.26.10.15.41 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 26 Oct 2012 10:15:42 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1283)
Subject: Re: Last Call: <draft-ietf-v6ops-ra-guard-implementation-04.txt> (Implementation Advice for IPv6 Router Advertisement Guard (RA-Guard)) to Best Current Practice
From: RJ Atkinson <rja.lists@gmail.com>
In-Reply-To: <20121026160427.30056.5891.idtracker@ietfa.amsl.com>
Date: Fri, 26 Oct 2012 13:15:40 -0400
Content-Transfer-Encoding: 7bit
Message-Id: <2164CBA8-3B59-4A83-A170-B68D118B44FC@gmail.com>
References: <20121026160427.30056.5891.idtracker@ietfa.amsl.com>
To: ietf@ietf.org
X-Mailer: Apple Mail (2.1283)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Oct 2012 17:15:44 -0000

On 26  Oct 2012, at 12:04 , The IESG wrote:
> The IESG has received a request from the IPv6 Operations WG (v6ops)
> to consider the following document:
> - 'Implementation Advice for IPv6 Router Advertisement Guard (RA-Guard)'
>  <draft-ietf-v6ops-ra-guard-implementation-04.txt>
> as Best Current Practice
> 
> The IESG plans to make a decision in the next few weeks,
> and solicits final comments on this action. 



Starting IETF Last Call seems premature for this document.
(Perhaps there was some slip of the keyboard somewhere ??)


1) Conflicts with active work items of the IPv6 WG

This I-D has the effect of over-riding parts of the 
standards-track IPv6 specifications (e.g. by making 
currently valid/legal (if unusual) IPv6 packets illegal 
and instructing RA-Guard implementations to drop such
currently valid/legal IPv6 packets).

My understanding is that the 2 proposals to update the 
IPv6 specifications (directly related to this document) 
are current work items of the IETF 6MAN WG, but (as near 
as I can tell) those documents have not even begun 
WG Last Call within the IPv6 WG.



2) Previously agreed document edits are not present
   in the document version referenced by the IESG
   announcement.

Prior discussion with the document author, both on the
v6ops mailing list (e.g. various notes in June 2012, e.g.,
<http://www.ietf.org/mail-archive/web/v6ops/current/msg13258.html>) 
and also off-list, indicated that he had agreed to move the 
relevant IPv6 protocol update documents from "Informative" 
references to "Normative" references, specifically the 
draft-ietf-6man-* versions of these 2 references of the 
IESG cited document:

   [I-D.gont-6man-oversized-header-chain]
              Gont, F. and V. Manral, "Security and Interoperability
              Implications of Oversized IPv6 Header Chains",
              draft-gont-6man-oversized-header-chain-01 (work in
              progress), April 2012.

   [I-D.gont-6man-nd-extension-headers]
              Gont, F., "Security Implications of the Use of IPv6
              Extension Headers with IPv6 Neighbor Discovery",
              draft-gont-6man-nd-extension-headers-02 (work in
              progress), January 2012.



3) Email from document author indicates this document
   will be updated soon.

Separately, overnight private email from the author (received 
by me prior to my receipt of this IESG announcement) indicates 
that an update to draft-ietf-v6ops-ra-guard-implementation is
imminent.  The pending update apparently resolves issue (2)
above.


So it seems to me that this document is not yet ready for
IETF Last Call.  Instead, it seems to me that the pending I-D 
update needs to occur, a (hopefully quick) review of that 
revision within IETF v6ops WG then needs to occur, and (ideally 
in parallel) IETF 6MAN WG review (and ideally approval) of the 
proposed changes to the IPv6 specifications needs to occur.


LAST)

In the (one hopes unlikely) event that the 6MAN WG is NOT
comfortable with the 2 directly-related proposed IPv6 
specification updates, then this document ought not be 
published on the IETF standards-track, on grounds that 
it specifies packet dropping behaviour inconsistent with 
the extant IPv6 specifications.


Yours,

Ran Atkinson


From john-ietf@jck.com  Fri Oct 26 10:16:24 2012
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4CA0B21F8669 for <ietf@ietfa.amsl.com>; Fri, 26 Oct 2012 10:16:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.544
X-Spam-Level: 
X-Spam-Status: No, score=-102.544 tagged_above=-999 required=5 tests=[AWL=0.055, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SoD+3JRsNtSH for <ietf@ietfa.amsl.com>; Fri, 26 Oct 2012 10:16:23 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id AAA1B21F865C for <ietf@ietf.org>; Fri, 26 Oct 2012 10:16:23 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1TRnW8-000GvM-Fq; Fri, 26 Oct 2012 13:16:20 -0400
Date: Fri, 26 Oct 2012 13:16:15 -0400
From: John C Klensin <john-ietf@jck.com>
To: Michael StJohns <mstjohns@comcast.net>, Eliot Lear <lear@cisco.com>
Subject: Re: [RFC 3777 Update for Vacancies]
Message-ID: <9A363D0FB7ED2D777C76867F@JcK-HP8200.jck.com>
References: <D90D92A7-0906-4620-93A0-D116D15A10FA@gmail.com> <20121026142930.B34B021F84D3@ietfa.amsl.com> <508AA611.7030206@cisco.com> <20121026151152.4F5AF21F862D@ietfa.amsl.com> <B5A61583C347AB7D9F752B11@JcK-HP8200.jck.com> 
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc: Bob Hinden <bob.hinden@gmail.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Oct 2012 17:16:24 -0000

--On Friday, October 26, 2012 12:25 -0400 Michael StJohns
<mstjohns@comcast.net> wrote:

>...
> I'm pretty much going to object to any condition based model
> that anyone proposes, because we're really bad at a) figuring
> out the complete list of all possible conditions that could
> ever happen, b) writing conditions that can be objectively
> evaluated, and c) figuring out how to decide when specific
> conditions are met (because of the lack of objective
> criteria).  In addition, people have been carping on the
> mailing list about how we need to be flexible - and condition
> lists by their very nature are not flexible.

Mike,
Oddly, while I disagree with your conclusion, I agree with the
above.  The difference is that I don't expect an "if X, then you
resigned" condition-based model to work very well in the edge
cases and where someone was trying to game the system.  It can't
work well for the edge cases for all the reasons you list,
especially because we are lousy at anticipating all possible
cases and writing rules to match.

More specifically, I'm ok with a procedure that works well when
someone just disappears and stops performing -- a problem that I
think has arisen around three times in the last 20 years.  I'm
also ok with the fact that such a procedure probably would not
have worked for one of them and that it would fail any time an
incumbent chose to fight expulsion, whether by stunts like "one
out of every 3 meetings for exactly 5 minutes" or by nit-picking
the rules.

My only interest is to help these who, for one reason or other,
have already slunk away into the night or otherwise disappeared
make a graceful and efficient exit.    That is an entirely
different case from someone who is not performing  but who
actively wants to hold onto the job.

For the latter cases --if someone is intentionally gaming the
system or resisting expulsion or resignation in other ways-- I
think the recall procedure, and all of the public unpleasantness
and condemnation that go with it, is exactly right and that
nothing new is needed (although see below).  It doesn't let a
body determine its own membership (if we don't want IESG or IAB
members, even retiring ones, voting on the Nomcom because we are
afraid of self-perpetuating bodies, we certainly shouldn't let
them second-guess Nomcom decisions by ejecting members without
any review external to the I* leadership).

If someone is non-performing and being a jerk about it (and
maybe just consistently being a jerk), I think it would be
reasonable to let a supermajority of the relevant body initiate
(and fast track the beginning of) a recall, but I note that the
community has rejected less drastic ideas in the past.

  best,
   john




From rbonica@juniper.net  Fri Oct 26 11:03:01 2012
Return-Path: <rbonica@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 504FF21F860B for <ietf@ietfa.amsl.com>; Fri, 26 Oct 2012 11:03:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.055
X-Spam-Level: 
X-Spam-Status: No, score=-104.055 tagged_above=-999 required=5 tests=[AWL=-1.188, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_MED=-4, UNRESOLVED_TEMPLATE=3.132, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eERZMWIUmSqd for <ietf@ietfa.amsl.com>; Fri, 26 Oct 2012 11:03:00 -0700 (PDT)
Received: from exprod7og125.obsmtp.com (exprod7og125.obsmtp.com [64.18.2.28]) by ietfa.amsl.com (Postfix) with ESMTP id 6B0B121F860A for <ietf@ietf.org>; Fri, 26 Oct 2012 11:03:00 -0700 (PDT)
Received: from P-EMHUB03-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob125.postini.com ([64.18.6.12]) with SMTP ID DSNKUIrQVN0vzvIK0ffW4X40ttyLGWZ/WBAD@postini.com; Fri, 26 Oct 2012 11:03:00 PDT
Received: from P-CLDFE01-HQ.jnpr.net (172.24.192.59) by P-EMHUB03-HQ.jnpr.net (172.24.192.37) with Microsoft SMTP Server (TLS) id 8.3.213.0; Fri, 26 Oct 2012 11:01:14 -0700
Received: from o365mail.juniper.net (207.17.137.224) by o365mail.juniper.net (172.24.192.59) with Microsoft SMTP Server id 14.1.355.2; Fri, 26 Oct 2012 11:01:13 -0700
Received: from am1outboundpool.messaging.microsoft.com (213.199.154.209) by o365mail.juniper.net (207.17.137.224) with Microsoft SMTP Server (TLS) id 14.1.355.2; Fri, 26 Oct 2012 11:07:25 -0700
Received: from mail2-am1-R.bigfish.com (10.3.201.251) by AM1EHSOBE001.bigfish.com (10.3.204.21) with Microsoft SMTP Server id 14.1.225.23; Fri, 26 Oct 2012 18:01:12 +0000
Received: from mail2-am1 (localhost [127.0.0.1])	by mail2-am1-R.bigfish.com (Postfix) with ESMTP id 4302D1A033D	for <ietf@ietf.org.FOPE.CONNECTOR.OVERRIDE>; Fri, 26 Oct 2012 18:01:12 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.245.197; KIP:(null); UIP:(null); (null); H:CH1PRD0511HT003.namprd05.prod.outlook.com; R:internal; EFV:INT
X-SpamScore: -28
X-BigFish: PS-28(zz98dI9371I542M1432Izz1202h1d1ah1d2ahzz1033IL17326ah8275dhz2dh2a8h668h839h944hd25hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh1155h)
Received: from mail2-am1 (localhost.localdomain [127.0.0.1]) by mail2-am1 (MessageSwitch) id 135127447057960_30105; Fri, 26 Oct 2012 18:01:10 +0000 (UTC)
Received: from AM1EHSMHS001.bigfish.com (unknown [10.3.201.249])	by mail2-am1.bigfish.com (Postfix) with ESMTP id F006320098; Fri, 26 Oct 2012 18:01:09 +0000 (UTC)
Received: from CH1PRD0511HT003.namprd05.prod.outlook.com (157.56.245.197) by AM1EHSMHS001.bigfish.com (10.3.207.101) with Microsoft SMTP Server (TLS) id 14.1.225.23; Fri, 26 Oct 2012 18:01:08 +0000
Received: from CH1PRD0511MB418.namprd05.prod.outlook.com ([169.254.9.10]) by CH1PRD0511HT003.namprd05.prod.outlook.com ([10.255.159.38]) with mapi id 14.16.0224.004; Fri, 26 Oct 2012 18:01:06 +0000
From: Ronald Bonica <rbonica@juniper.net>
To: RJ Atkinson <rja.lists@gmail.com>, "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: Last Call: <draft-ietf-v6ops-ra-guard-implementation-04.txt> (Implementation Advice for IPv6 Router Advertisement Guard	(RA-Guard)) to Best Current Practice
Thread-Topic: Last Call: <draft-ietf-v6ops-ra-guard-implementation-04.txt> (Implementation Advice for IPv6 Router Advertisement Guard	(RA-Guard)) to Best Current Practice
Thread-Index: AQHNs52QeYy07NCzAkmVq2uozIsKKJfL32tA
Date: Fri, 26 Oct 2012 18:01:05 +0000
Message-ID: <2CF4CB03E2AA464BA0982EC92A02CE2502DAF8@CH1PRD0511MB418.namprd05.prod.outlook.com>
References: <20121026160427.30056.5891.idtracker@ietfa.amsl.com> <2164CBA8-3B59-4A83-A170-B68D118B44FC@gmail.com>
In-Reply-To: <2164CBA8-3B59-4A83-A170-B68D118B44FC@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [66.129.232.2]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
X-FOPE-CONNECTOR: Id%12219$Dn%GMAIL.COM$RO%2$TLS%5$FQDN%onpremiseedge-1018244.customer.frontbridge.com$TlsDn%o365mail.juniper.net
X-FOPE-CONNECTOR: Id%12219$Dn%IETF.ORG$RO%2$TLS%5$FQDN%onpremiseedge-1018244.customer.frontbridge.com$TlsDn%o365mail.juniper.net
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Oct 2012 18:03:01 -0000

Ran,

I agree that the references to I-D.gont-6man-oversized-header-chain and gon=
t-6man-nd-extension-headers should both be NORMATIVE, and not INFORMATIVE. =
Sorry for having missed this.

If Fernando were to post an updated version that makes this change, would i=
t address all of your issues? If Fernando did this, it should address 6man'=
s concerns because even if draft-ietf-v6ops-ra-guard-implementation were ap=
proved, it couldn't be published until the other two drafts are also approv=
ed.

                                          Ron


> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
> RJ Atkinson
> Sent: Friday, October 26, 2012 1:16 PM
> To: ietf@ietf.org
> Subject: Re: Last Call: <draft-ietf-v6ops-ra-guard-implementation-
> 04.txt> (Implementation Advice for IPv6 Router Advertisement Guard (RA-
> Guard)) to Best Current Practice
>=20
>=20
> On 26  Oct 2012, at 12:04 , The IESG wrote:
> > The IESG has received a request from the IPv6 Operations WG (v6ops)
> to
> > consider the following document:
> > - 'Implementation Advice for IPv6 Router Advertisement Guard (RA-
> Guard)'
> >  <draft-ietf-v6ops-ra-guard-implementation-04.txt>
> > as Best Current Practice
> >
> > The IESG plans to make a decision in the next few weeks, and solicits
> > final comments on this action.
>=20
>=20
>=20
> Starting IETF Last Call seems premature for this document.
> (Perhaps there was some slip of the keyboard somewhere ??)
>=20
>=20
> 1) Conflicts with active work items of the IPv6 WG
>=20
> This I-D has the effect of over-riding parts of the standards-track
> IPv6 specifications (e.g. by making currently valid/legal (if unusual)
> IPv6 packets illegal and instructing RA-Guard implementations to drop
> such currently valid/legal IPv6 packets).
>=20
> My understanding is that the 2 proposals to update the
> IPv6 specifications (directly related to this document) are current
> work items of the IETF 6MAN WG, but (as near as I can tell) those
> documents have not even begun WG Last Call within the IPv6 WG.
>=20
>=20
>=20
> 2) Previously agreed document edits are not present
>    in the document version referenced by the IESG
>    announcement.
>=20
> Prior discussion with the document author, both on the v6ops mailing
> list (e.g. various notes in June 2012, e.g.,
> <http://www.ietf.org/mail-archive/web/v6ops/current/msg13258.html>)
> and also off-list, indicated that he had agreed to move the relevant
> IPv6 protocol update documents from "Informative"
> references to "Normative" references, specifically the
> draft-ietf-6man-* versions of these 2 references of the IESG cited
> document:
>=20
>    [I-D.gont-6man-oversized-header-chain]
>               Gont, F. and V. Manral, "Security and Interoperability
>               Implications of Oversized IPv6 Header Chains",
>               draft-gont-6man-oversized-header-chain-01 (work in
>               progress), April 2012.
>=20
>    [I-D.gont-6man-nd-extension-headers]
>               Gont, F., "Security Implications of the Use of IPv6
>               Extension Headers with IPv6 Neighbor Discovery",
>               draft-gont-6man-nd-extension-headers-02 (work in
>               progress), January 2012.
>=20
>=20
>=20
> 3) Email from document author indicates this document
>    will be updated soon.
>=20
> Separately, overnight private email from the author (received by me
> prior to my receipt of this IESG announcement) indicates that an update
> to draft-ietf-v6ops-ra-guard-implementation is imminent.  The pending
> update apparently resolves issue (2) above.
>=20
>=20
> So it seems to me that this document is not yet ready for IETF Last
> Call.  Instead, it seems to me that the pending I-D update needs to
> occur, a (hopefully quick) review of that revision within IETF v6ops WG
> then needs to occur, and (ideally in parallel) IETF 6MAN WG review (and
> ideally approval) of the proposed changes to the IPv6 specifications
> needs to occur.
>=20
>=20
> LAST)
>=20
> In the (one hopes unlikely) event that the 6MAN WG is NOT comfortable
> with the 2 directly-related proposed IPv6 specification updates, then
> this document ought not be published on the IETF standards-track, on
> grounds that it specifies packet dropping behaviour inconsistent with
> the extant IPv6 specifications.
>=20
>=20
> Yours,
>=20
> Ran Atkinson
>=20



From rja.lists@gmail.com  Fri Oct 26 11:34:31 2012
Return-Path: <rja.lists@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B8EB921F85C0 for <ietf@ietfa.amsl.com>; Fri, 26 Oct 2012 11:34:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.193
X-Spam-Level: 
X-Spam-Status: No, score=-3.193 tagged_above=-999 required=5 tests=[AWL=-0.194, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YMt7MNpfkJp5 for <ietf@ietfa.amsl.com>; Fri, 26 Oct 2012 11:34:31 -0700 (PDT)
Received: from mail-vc0-f172.google.com (mail-vc0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 003C821F85B8 for <ietf@ietf.org>; Fri, 26 Oct 2012 11:34:30 -0700 (PDT)
Received: by mail-vc0-f172.google.com with SMTP id fl11so3606262vcb.31 for <ietf@ietf.org>; Fri, 26 Oct 2012 11:34:30 -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=bRPhUSJJ/YGGJfPkkxHjBKrOt5pX19Yoq+gU4fZW38c=; b=0hE6Jic6Z7wdRheHGMF3qzXsvdBcfoUWAwt0td/OBb2g5YtiyCZ5uDQSlqwioQie+T IdgsX0aJnW6piBKVCSZpCTbg76lP0wUugyDFHNTLMerYjl17LQPjddLiOS7xizaF2L1z a1bVOvmf1KB+U2kV2mNPWiblrLg1ARoHJnlpxaD1No/6lwHeulY8kM9Qeci28lnRJw5M +BeqUY5JGIOj3eUxxsuKX7asCR0XKpGCxnr/+T44ET2ufzaij5EAKm72bOokaBdG5+Bd tA4OrBB/nIS3DYKkQ7PKzus3npzovnjzBU3Uq7D4vZesN3NUA+noawdFIzUmCWKiu6Br q7cg==
Received: by 10.52.76.40 with SMTP id h8mr31084112vdw.123.1351276470448; Fri, 26 Oct 2012 11:34:30 -0700 (PDT)
Received: from [10.30.20.14] (pool-74-110-100-136.nrflva.fios.verizon.net. [74.110.100.136]) by mx.google.com with ESMTPS id zx18sm1098835veb.3.2012.10.26.11.34.29 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 26 Oct 2012 11:34:29 -0700 (PDT)
Subject: Re: Last Call: <draft-ietf-v6ops-ra-guard-implementation-04.txt> (Implementation Advice for IPv6 Router Advertisement Guard	(RA-Guard)) to Best Current Practice
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=us-ascii
From: RJ Atkinson <rja.lists@gmail.com>
In-Reply-To: <2CF4CB03E2AA464BA0982EC92A02CE2502DAF8@CH1PRD0511MB418.namprd05.prod.outlook.com>
Date: Fri, 26 Oct 2012 14:34:28 -0400
Content-Transfer-Encoding: 7bit
Message-Id: <0C27784D-05DC-4ABE-BFAA-8301551D4714@gmail.com>
References: <20121026160427.30056.5891.idtracker@ietfa.amsl.com> <2164CBA8-3B59-4A83-A170-B68D118B44FC@gmail.com> <2CF4CB03E2AA464BA0982EC92A02CE2502DAF8@CH1PRD0511MB418.namprd05.prod.outlook.com>
To: Ronald Bonica <rbonica@juniper.net>
X-Mailer: Apple Mail (2.1283)
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, 26 Oct 2012 18:34:31 -0000

On 26  Oct 2012, at 14:01 , Ronald Bonica wrote:
> I agree that the references to I-D.gont-6man-oversized-header-chain
> and gont-6man-nd-extension-headers should both be NORMATIVE,
> and not INFORMATIVE. Sorry for having missed this.

Thank you.


> If Fernando were to post an updated version that makes this change,
> would it address all of your issues?



The full set of edits previously agreed are summarised
in this note to the v6ops WG list:
  <http://www.ietf.org/mail-archive/web/v6ops/current/msg13258.html>


At least this other note from Fernando to the v6ops list 
also seems relevant:
  <http://www.ietf.org/mail-archive/web/v6ops/current/msg13257.html>


Several of the previously-agreed edits are not present in the 
I-D referenced in today's IETF Last Call.  The delta isn't huge,
but there are other agreed edits -- beyond just how the two related
draft-6man-* I-Ds are cited.
  

I might be confused, but I understand that Fernando 
has an updated RA-Guard I-D "ready to post".

> If Fernando did this, it should address 6man's concerns,
> because even if draft-ietf-v6ops-ra-guard-implementation
> were approved, it couldn't be published until the other
> two drafts are also approved.

Fair enough.


Thanks very much.

Ran


From warren@kumari.net  Fri Oct 26 14:00:20 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 0D35021F85C6 for <ietf@ietfa.amsl.com>; Fri, 26 Oct 2012 14:00:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.25
X-Spam-Level: 
X-Spam-Status: No, score=-102.25 tagged_above=-999 required=5 tests=[AWL=0.349, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gWIIxM7juW6T for <ietf@ietfa.amsl.com>; Fri, 26 Oct 2012 14:00:19 -0700 (PDT)
Received: from vimes.kumari.net (smtp1.kumari.net [204.194.22.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2A31F21F85C1 for <ietf@ietf.org>; Fri, 26 Oct 2012 14:00:18 -0700 (PDT)
Received: from [192.168.1.142] (unknown [66.84.81.102]) by vimes.kumari.net (Postfix) with ESMTPSA id DE5B11B40038; Fri, 26 Oct 2012 17:00:17 -0400 (EDT)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: [IETF] Exceptional cases
From: Warren Kumari <warren@kumari.net>
In-Reply-To: <508A7F02.5080905@cisco.com>
Date: Fri, 26 Oct 2012 17:00:17 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <B4023F7B-4658-45CB-80DD-E3467DCF411E@kumari.net>
References: <20121025185724.9CACF18C0A0@mercury.lcs.mit.edu> <508990E4.9040809@dougbarton.us> <20121025195057.GA55999@mx1.yitter.info> <508A7F02.5080905@cisco.com>
To: Eliot Lear <lear@cisco.com>
X-Mailer: Apple Mail (2.1499)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Oct 2012 21:00:20 -0000

On Oct 26, 2012, at 8:16 AM, Eliot Lear <lear@cisco.com> wrote:

> Andrew,
>=20
> On 10/25/12 9:52 PM, Andrew Sullivan wrote:
>> Oh, for heaven's sake. This is nothing to do with punishment. This is
>> a straightforward administrative problem. Turning this into an
>> opportunity to exercise a heavyweight and in fact punitive process
>> would be an injustice. If the IETF has wound itself into such
>> bureaucratic knots that we can't just make an exceptional decision in
>> exceptional circumstances, we are in much worse trouble than I =
thought. A=20
>=20
> And as of yet nobody has challenged the need to remove Marshall.  =
We've
> just gone off the deep end on process. =20

What?! You are trying to say that the IETF ratholed on process? Never=85

=
http://www.cafepress.com/mf/33235226/ietf-process-organic-cotton-tee_tshir=
t

W


> Yes, let's close the process
> problem as Brian said in due course.  Let's also not rush through the
> changes for all the reasons that John Klensin wrote, plus another: I
> don't like the proposed approach, but that's for another message.
>=20
> Eliot
>=20
>=20

--
"When it comes to glittering objects, wizards have all the taste and =
self-control of a deranged magpie."
-- Terry Pratchett





From dwm@xpasc.com  Sat Oct 27 21:28:36 2012
Return-Path: <dwm@xpasc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 06B7621F8686 for <ietf@ietfa.amsl.com>; Sat, 27 Oct 2012 21:28:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.307
X-Spam-Level: 
X-Spam-Status: No, score=-1.307 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MISSING_HEADERS=1.292]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GdkepFAR6IQG for <ietf@ietfa.amsl.com>; Sat, 27 Oct 2012 21:28:35 -0700 (PDT)
Received: from c2w3p-2.abacamail.com (c2w3p-2.abacamail.com [209.133.53.32]) by ietfa.amsl.com (Postfix) with ESMTP id A588521F8685 for <ietf@ietf.org>; Sat, 27 Oct 2012 21:28:35 -0700 (PDT)
Received: from xpasc.com (unknown [68.164.244.188]) by c2w3p-2.abacamail.com (Postfix) with ESMTP id 036923FC16 for <ietf@ietf.org>; Sun, 28 Oct 2012 04:28:35 +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 q9S4SYBu013563 for <ietf@ietf.org>; Sat, 27 Oct 2012 21:28:34 -0700
Date: Sat, 27 Oct 2012 21:28:34 -0700 (PDT)
From: David Morris <dwm@xpasc.com>
cc: ietf@ietf.org
Subject: Re: Just so I'm clear
In-Reply-To: <508A39A0.3090602@gmail.com>
Message-ID: <alpine.LRH.2.01.1210272123530.13487@egate.xpasc.com>
References: <20121023192135.203AC18C0A4@mercury.lcs.mit.edu> <5086EF82.9060900@dougbarton.us> <20121023200713.GC1861@nsn.com> <5086FBCE.2070503@dougbarton.us> <20121023213251.GF27557@verdi> <50873AB4.1000905@dougbarton.us> <20121024034736.GC52558@crankycanuck.ca> <50876D39.20502@dougbarton.us> <508773E7.10203@cisco.com> <50877633.1000402@dougbarton.us> <EA9BEA2E-EE96-4E80-B719-652BBD620A79@lilacglade.org> <508842C2.4020203@dougbarton.us> <5088EE5A.4090103@gmail.com> <508987B9.2040207@dougbarton.us> <508A39A0.3090602@gmail.com>
User-Agent: Alpine 2.01 (LRH 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Milter-Version: master.1+13-gbab1945
X-AV-Type: clean
X-AV-Accuracy: exact
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: ietf@ietf.org
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 28 Oct 2012 04:28:36 -0000

On Fri, 26 Oct 2012, Brian E Carpenter wrote:

> Actually I haven't seen that. I've seen people assert that our process
> doesn't document the case of a non-responsive absentee member, but I
> haven't seen anyone deny that we have an empty seat.

I don't believe the seat is vacant or empty. Without some form of
rule or process documented, it isn't vacant. For unknown reasons
(we've had two different 3rd party reports, neither of which makes
sense given the individual's prior commitment to the IETF community,
we have a clear case of failure to fulfill the obligations assumed when
the position was accepted.

That isn't a defacto vacancy.

From sob@sobco.com  Sun Oct 28 04:35:31 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 461F721F86F3 for <ietf@ietfa.amsl.com>; Sun, 28 Oct 2012 04:35:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.364
X-Spam-Level: *
X-Spam-Status: No, score=1.364 tagged_above=-999 required=5 tests=[BAYES_20=-0.74, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UbLhq141+l4q for <ietf@ietfa.amsl.com>; Sun, 28 Oct 2012 04:35:29 -0700 (PDT)
Received: from sobco.sobco.com (unknown [136.248.127.164]) by ietfa.amsl.com (Postfix) with ESMTP id 43F4621F86D5 for <ietf@ietf.org>; Sun, 28 Oct 2012 04:35:29 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by sobco.sobco.com (Postfix) with ESMTP id 4C2282DF623; Sun, 28 Oct 2012 07:35:27 -0400 (EDT)
X-Virus-Scanned: amavisd-new at sobco.com
Received: from sobco.sobco.com ([127.0.0.1]) by localhost (sobco.sobco.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hIaEaO8DP0WS; Sun, 28 Oct 2012 07:35:25 -0400 (EDT)
Received: from golem.sobco.com (golem.sobco.com [136.248.127.162]) by sobco.sobco.com (Postfix) with ESMTPSA id D69172DF615; Sun, 28 Oct 2012 07:35:25 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: ISOC BOT and Process BCPs
From: Scott O Bradner <sob@sobco.com>
In-Reply-To: <tsly5it32ep.fsf_-_@mit.edu>
Date: Sun, 28 Oct 2012 07:35:25 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <98FC5245-04DD-4B0E-AB8A-F03858417829@sobco.com>
References: <20121025125351.285D818C0A0@mercury.lcs.mit.edu> <20121025204915.6C09621F8491@ietfa.amsl.com> <tslhapi5fno.fsf@mit.edu> <6.2.5.6.2.20121025232216.094f24e8@resistor.net> <tsly5it32ep.fsf_-_@mit.edu>
To: Sam Hartman <hartmans-ietf@mit.edu>
X-Mailer: Apple Mail (2.1499)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 28 Oct 2012 11:35:31 -0000

Sam -
	The ISOC BoT has generally (with some slip-ups) accepted IETF =
process documents as=20
describing the IETF process - this has been seen as a good idea for the =
insurance coverage

there is no requirement in the IETF process that such RFCs be approved =
by the ISOC board=20
nor that they are accepted as describing IETF process before the RFCs =
become active=20

see, for example, Resolution 2006-36=20
=
http://www.internetsociety.org/who-we-are/board-trustees/list-resolutions

Scott

On Oct 26, 2012, at 7:20 AM, Sam Hartman <hartmans-ietf@mit.edu> wrote:

>>>>>> "SM" =3D=3D SM  <sm@resistor.net> writes:
>=20
>=20
> So, I'm puzzled by this.  my claim was that ISOC needed to approve
> process related BCPs.  If you take a look at RFC 2031, it supports =
that
> claim.  However, I'd kind of expect the other half of this to be in =
RFC
> 2026.  I certainly recall us sending things like BCP 101 before the =
ISOC
> BOT. I also think we sent a couple of other documents there because =
they
> were process documents.
> However this is clearly more complex than I thought it was.
>=20
> Scott, or anyone else with more history, can you tell us a story about
> how this works?


From ted.ietf@gmail.com  Sun Oct 28 10:24:40 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 C3CEA21F8640 for <ietf@ietfa.amsl.com>; Sun, 28 Oct 2012 10:24:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4SUaR98KqREU for <ietf@ietfa.amsl.com>; Sun, 28 Oct 2012 10:24:40 -0700 (PDT)
Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id 09C8721F8630 for <ietf@ietf.org>; Sun, 28 Oct 2012 10:24:39 -0700 (PDT)
Received: by mail-vb0-f44.google.com with SMTP id fc26so4940003vbb.31 for <ietf@ietf.org>; Sun, 28 Oct 2012 10:24:39 -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=k0afvaWIb4nI34AOWkeBJhaLTRA7vQpWHsIc/cLkkd0=; b=PY1zeuY2gENpHwQRu6wJywItwp+qTq7e/LFqt2fuXOoItlM5CbyTPHMwQhOdMC0IIx 02HI7hxip7Y7wltaouquyYK+LZB2Iaa+ypRjYZO/15DbR2VLV1BR8SDK94kbIuwyE0uT Xqq6sBisqaDSpUodgVIs7DqYBep03T7K5u6eHxb3lPWzwFDXl/e+2gM+XzhqESenBlkp yl8sBc5IgWhxpTZllgpl1q+fs1oyWiDwLo8jURoZuoDuUnJtCj0BfkUEQWU00iACUVoF OLTDpgxzxPVM2AiHDWO4aq0bHL8yShz9kcuMy9lm9wnlNSoercXnWuRU/L7nopRJmdeU 1/+A==
MIME-Version: 1.0
Received: by 10.52.99.103 with SMTP id ep7mr15794357vdb.17.1351445079377; Sun, 28 Oct 2012 10:24:39 -0700 (PDT)
Received: by 10.58.164.35 with HTTP; Sun, 28 Oct 2012 10:24:39 -0700 (PDT)
In-Reply-To: <98FC5245-04DD-4B0E-AB8A-F03858417829@sobco.com>
References: <20121025125351.285D818C0A0@mercury.lcs.mit.edu> <20121025204915.6C09621F8491@ietfa.amsl.com> <tslhapi5fno.fsf@mit.edu> <6.2.5.6.2.20121025232216.094f24e8@resistor.net> <tsly5it32ep.fsf_-_@mit.edu> <98FC5245-04DD-4B0E-AB8A-F03858417829@sobco.com>
Date: Sun, 28 Oct 2012 10:24:39 -0700
Message-ID: <CA+9kkMBGKb0siEwBA9UoX6JskjXZwN3V_=OiXvzwwBWNyDaNfQ@mail.gmail.com>
Subject: Re: ISOC BOT and Process BCPs
From: Ted Hardie <ted.ietf@gmail.com>
To: Scott O Bradner <sob@sobco.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: Sam Hartman <hartmans-ietf@mit.edu>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 28 Oct 2012 17:24:40 -0000

On Sun, Oct 28, 2012 at 4:35 AM, Scott O Bradner <sob@sobco.com> wrote:
> Sam -
>         The ISOC BoT has generally (with some slip-ups) accepted IETF process documents as
> describing the IETF process - this has been seen as a good idea for the insurance coverage
>
> there is no requirement in the IETF process that such RFCs be approved by the ISOC board
> nor that they are accepted as describing IETF process before the RFCs become active
>
> see, for example, Resolution 2006-36
> http://www.internetsociety.org/who-we-are/board-trustees/list-resolutions
>

The other piece to this is in RFC 2026, in the section on appeals:

   Further recourse is available only in cases in which the procedures
   themselves (i.e., the procedures described in this document) are
   claimed to be inadequate or insufficient to the protection of the
   rights of all parties in a fair and open Internet Standards Process.
   Claims on this basis may be made to the Internet Society Board of
   Trustees.

By sending process documents to the ISOC Board on adoption, the IETF
avoids the late surprise possibility that they will later be found to
be "inadequate or insufficient".  That doesn't eliminate the right of
appeal (someone filing one may raise and issue that the Board didn't
consider), but it does mean that there is some context when appeals
occur.

It may not be strictly required, in other words, but it is a good idea.

My two cents,

Ted Hardie

> Scott
>
> On Oct 26, 2012, at 7:20 AM, Sam Hartman <hartmans-ietf@mit.edu> wrote:
>
>>>>>>> "SM" == SM  <sm@resistor.net> writes:
>>
>>
>> So, I'm puzzled by this.  my claim was that ISOC needed to approve
>> process related BCPs.  If you take a look at RFC 2031, it supports that
>> claim.  However, I'd kind of expect the other half of this to be in RFC
>> 2026.  I certainly recall us sending things like BCP 101 before the ISOC
>> BOT. I also think we sent a couple of other documents there because they
>> were process documents.
>> However this is clearly more complex than I thought it was.
>>
>> Scott, or anyone else with more history, can you tell us a story about
>> how this works?
>

From eburger-l@standardstrack.com  Sun Oct 28 10:31:16 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 E27EC21F84FC for <ietf@ietfa.amsl.com>; Sun, 28 Oct 2012 10:31:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.001
X-Spam-Level: 
X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[BAYES_50=0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 35qgK5i7xSqn for <ietf@ietfa.amsl.com>; Sun, 28 Oct 2012 10:31:16 -0700 (PDT)
Received: from biz104.inmotionhosting.com (biz104.inmotionhosting.com [173.247.254.120]) by ietfa.amsl.com (Postfix) with ESMTP id 2635F21F84F8 for <ietf@ietf.org>; Sun, 28 Oct 2012 10:31:16 -0700 (PDT)
Received: from ip68-100-199-8.dc.dc.cox.net ([68.100.199.8]:56203 helo=[192.168.15.175]) by biz104.inmotionhosting.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.77) (envelope-from <eburger-l@standardstrack.com>) id 1TSWha-0008M6-Fa for ietf@ietf.org; Sun, 28 Oct 2012 10:31:11 -0700
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1085)
Subject: Re: [RFC 3777 Update for Vacancies]
From: Eric Burger <eburger-l@standardstrack.com>
In-Reply-To: <9A363D0FB7ED2D777C76867F@JcK-HP8200.jck.com>
Date: Sun, 28 Oct 2012 13:31:18 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <13622014-D180-4737-A698-219C1832F1E1@standardstrack.com>
References: <D90D92A7-0906-4620-93A0-D116D15A10FA@gmail.com> <20121026142930.B34B021F84D3@ietfa.amsl.com> <508AA611.7030206@cisco.com> <20121026151152.4F5AF21F862D@ietfa.amsl.com> <B5A61583C347AB7D9F752B11@JcK-HP8200.jck.com> <9A363D0FB7ED2D777C76867F@JcK-HP8200.jck.com>
To: IETF list <ietf@ietf.org>
X-Mailer: Apple Mail (2.1085)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - biz104.inmotionhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - standardstrack.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 28 Oct 2012 17:31:17 -0000

Echoing John here, he very succinctly explains why setting out clear =
lines of what does or does not constitute abandonment invites abuse.

If someone is acting against the interests of the IETF, we have lots of =
ways of dealing with it.

If someone falls off the face of the Earth, and repeated attempts to =
contact them using legally recognized methods of notice fails, and more =
importantly they have a positive track record that spans over a decade, =
we can use our existing nomcom tools to replace their nomcom-appointed =
duties. I would offer that a person in such a position with such =
demonstrated dedication would not want us to do otherwise.

On Oct 26, 2012, at 1:16 PM, John C Klensin wrote:

>=20
>=20
> --On Friday, October 26, 2012 12:25 -0400 Michael StJohns
> <mstjohns@comcast.net> wrote:
>=20
>> ...
>> I'm pretty much going to object to any condition based model
>> that anyone proposes, because we're really bad at a) figuring
>> out the complete list of all possible conditions that could
>> ever happen, b) writing conditions that can be objectively
>> evaluated, and c) figuring out how to decide when specific
>> conditions are met (because of the lack of objective
>> criteria).  In addition, people have been carping on the
>> mailing list about how we need to be flexible - and condition
>> lists by their very nature are not flexible.
>=20
> Mike,
> Oddly, while I disagree with your conclusion, I agree with the
> above.  The difference is that I don't expect an "if X, then you
> resigned" condition-based model to work very well in the edge
> cases and where someone was trying to game the system.  It can't
> work well for the edge cases for all the reasons you list,
> especially because we are lousy at anticipating all possible
> cases and writing rules to match.
>=20
> More specifically, I'm ok with a procedure that works well when
> someone just disappears and stops performing -- a problem that I
> think has arisen around three times in the last 20 years.  I'm
> also ok with the fact that such a procedure probably would not
> have worked for one of them and that it would fail any time an
> incumbent chose to fight expulsion, whether by stunts like "one
> out of every 3 meetings for exactly 5 minutes" or by nit-picking
> the rules.
>=20
> My only interest is to help these who, for one reason or other,
> have already slunk away into the night or otherwise disappeared
> make a graceful and efficient exit.    That is an entirely
> different case from someone who is not performing  but who
> actively wants to hold onto the job.
>=20
> For the latter cases --if someone is intentionally gaming the
> system or resisting expulsion or resignation in other ways-- I
> think the recall procedure, and all of the public unpleasantness
> and condemnation that go with it, is exactly right and that
> nothing new is needed (although see below).  It doesn't let a
> body determine its own membership (if we don't want IESG or IAB
> members, even retiring ones, voting on the Nomcom because we are
> afraid of self-perpetuating bodies, we certainly shouldn't let
> them second-guess Nomcom decisions by ejecting members without
> any review external to the I* leadership).
>=20
> If someone is non-performing and being a jerk about it (and
> maybe just consistently being a jerk), I think it would be
> reasonable to let a supermajority of the relevant body initiate
> (and fast track the beginning of) a recall, but I note that the
> community has rejected less drastic ideas in the past.
>=20
>  best,
>   john
>=20
>=20
>=20


From randy@psg.com  Sun Oct 28 18:05:41 2012
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7C42421F85BA for <ietf@ietfa.amsl.com>; Sun, 28 Oct 2012 18:05:41 -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_05=-1.11]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wckLCT99Z+KC for <ietf@ietfa.amsl.com>; Sun, 28 Oct 2012 18:05:41 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by ietfa.amsl.com (Postfix) with ESMTP id 3196D21F84A9 for <ietf@ietf.org>; Sun, 28 Oct 2012 18:05:41 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=rair.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.80 (FreeBSD)) (envelope-from <randy@psg.com>) id 1TSdnP-000Ms8-9K for ietf@ietf.org; Mon, 29 Oct 2012 01:05:39 +0000
Date: Mon, 29 Oct 2012 10:05:38 +0900
Message-ID: <m2y5iq140t.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: IETF Disgust <ietf@ietf.org>
Subject: itojun
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Oct 2012 01:05:41 -0000

five years ago, sigh.  october is not a good month.

randy

From lear@cisco.com  Mon Oct 29 06:07:01 2012
Return-Path: <lear@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4422A21F866D for <ietf@ietfa.amsl.com>; Mon, 29 Oct 2012 06:07:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.598
X-Spam-Level: 
X-Spam-Status: No, score=-110.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J6h4MBTf5K0O for <ietf@ietfa.amsl.com>; Mon, 29 Oct 2012 06:07:00 -0700 (PDT)
Received: from ams-iport-4.cisco.com (ams-iport-4.cisco.com [144.254.224.147]) by ietfa.amsl.com (Postfix) with ESMTP id 270C021F855C for <ietf@ietf.org>; Mon, 29 Oct 2012 06:07:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4255; q=dns/txt; s=iport; t=1351516020; x=1352725620; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to; bh=IKdV1ZZhNFfhYA5So665u51dh7N54vJzSw021fHcN0E=; b=fEKrMOf/kz44cZHz4BIjxWy8ByMnT+c4BH43X+AggHzNJnw4jz6NIDoE btSRmprjG0wOPityrbbUfYNIy5IMJ4yO7LNvI0UjG47n7xYXBXk5/O7ay /BqKOBzLla3oMDpJ+Zv+VxWQ9lUhuPt2VEU0p8oITz6LL+8VIwTdPi+gg 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgcGABl/jlCQ/khR/2dsb2JhbABEhhiFX7ZrgQiCHwEBBAEBAQ8BEFUBEAsEChMWCwICCQMCAQIBRQUBDQEHAQEQDodknDyNLJIphh+EEIFhhS+BEwOVdI5XgWuCcA
X-IronPort-AV: E=Sophos;i="4.80,672,1344211200"; d="scan'208,217";a="9185071"
Received: from ams-core-1.cisco.com ([144.254.72.81]) by ams-iport-4.cisco.com with ESMTP; 29 Oct 2012 13:06:59 +0000
Received: from dhcp-10-55-92-4.cisco.com (dhcp-10-55-92-4.cisco.com [10.55.92.4]) by ams-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id q9TD6wJ6011996 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 29 Oct 2012 13:06:58 GMT
Message-ID: <508E7F72.4010606@cisco.com>
Date: Mon, 29 Oct 2012 14:06:58 +0100
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:16.0) Gecko/20121010 Thunderbird/16.0.1
MIME-Version: 1.0
To: Eric Burger <eburger-l@standardstrack.com>
Subject: Re: [RFC 3777 Update for Vacancies]
References: <D90D92A7-0906-4620-93A0-D116D15A10FA@gmail.com> <20121026142930.B34B021F84D3@ietfa.amsl.com> <508AA611.7030206@cisco.com> <20121026151152.4F5AF21F862D@ietfa.amsl.com> <B5A61583C347AB7D9F752B11@JcK-HP8200.jck.com> <9A363D0FB7ED2D777C76867F@JcK-HP8200.jck.com> <13622014-D180-4737-A698-219C1832F1E1@standardstrack.com>
In-Reply-To: <13622014-D180-4737-A698-219C1832F1E1@standardstrack.com>
X-Enigmail-Version: 1.4.5
Content-Type: multipart/alternative; boundary="------------060907000205060906030803"
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: Mon, 29 Oct 2012 13:07:01 -0000

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

Bob, everyone,

As I've mentioned, I'd prefer an alternative to what the authors have
written.  Call this the "let's program ourselves out of a paper bag"
option, when we all agree.  This may be a rule we would wish to
generalize.  Here is the basis for what I propose:

 1. We have existing procedures to resolve contested removals – the
    recall process.
 2. "Uncontested" essentially means that we as a community are in
    unanimous agreement that the position is vacant.  That means that by
    definition, any "no" votes from a body means it's contested.
 3. The least amount of power should be delegated to our bodies as is
    necessary for the organization's smooth operation.
 4. Procedural arguments on the IETF list are tiresome, when we all
    agree on the right outcome ;-)

With that in mind, I've attempted to reduce changes to a more simplified
form, as follows:

In draft-ietf-genarea-bcp10upd-00.txt, Section 3.3, 2nd and 3rd paragraphs,

OLD:

   For vacancies due to uncontested, sustained absence, the IETF body
   making that determination will issue an Extended Last Call to the
   community.  The Last Call will explain the basis for declaring the
   position vacant and include a summary of efforts to contact the
   member to resolve the issue.

   The results of the Last Call are assessed by the IETF body, with a
   two-thirds vote of the body.


NEW:

    When an IETF body unanimously believes that a position on that
    body has been vacated, they may request confirmation of this by
    the community through an Extended Last Call with their reasoning.
    Should no objections be received during that period, the position is
    said to be vacant.


Eliot



--------------060907000205060906030803
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">
    Bob, everyone,<br>
    <br>
    As I've mentioned, I'd prefer an alternative to what the authors
    have written.  Call this the "let's program ourselves out of a paper
    bag" option, when we all agree.  This may be a rule we would wish to
    generalize.  Here is the basis for what I propose:<br>
    <ol>
      <li>We have existing procedures to resolve contested removals –
        the recall process.</li>
      <li>"Uncontested" essentially means that we as a community are in
        unanimous agreement that the position is vacant.  That means
        that by definition, any "no" votes from a body means it's
        contested.</li>
      <li>The least amount of power should be delegated to our bodies as
        is necessary for the organization's smooth operation.</li>
      <li>Procedural arguments on the IETF list are tiresome, when we
        all agree on the right outcome ;-)<br>
      </li>
    </ol>
    With that in mind, I've attempted to reduce changes to a more
    simplified form, as follows:<br>
    <br>
    In draft-ietf-genarea-bcp10upd-00.txt, Section 3.3, 2nd and 3rd
    paragraphs,<br>
    <br>
    OLD:<br>
    <pre>   For vacancies due to uncontested, sustained absence, the IETF body
   making that determination will issue an Extended Last Call to the
   community.  The Last Call will explain the basis for declaring the
   position vacant and include a summary of efforts to contact the
   member to resolve the issue.</pre>
    <pre>
   The results of the Last Call are assessed by the IETF body, with a
   two-thirds vote of the body.</pre>
    <br>
    NEW:<br>
    <pre wrap="">    When an IETF body unanimously believes that a position on that
    body has been vacated, they may request confirmation of this by
    the community through an Extended Last Call with their reasoning.
    Should no objections be received during that period, the position is
    said to be vacant.


Eliot
</pre>
    <br>
  </body>
</html>

--------------060907000205060906030803--

From john-ietf@jck.com  Mon Oct 29 06:58:57 2012
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1E6ED21F8665 for <ietf@ietfa.amsl.com>; Mon, 29 Oct 2012 06:58:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.855
X-Spam-Level: 
X-Spam-Status: No, score=-101.855 tagged_above=-999 required=5 tests=[AWL=0.745, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q1nV6pRhb1mF for <ietf@ietfa.amsl.com>; Mon, 29 Oct 2012 06:58:56 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 2F47A21F8660 for <ietf@ietf.org>; Mon, 29 Oct 2012 06:58:56 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1TSprh-0001BH-OY; Mon, 29 Oct 2012 09:58:53 -0400
Date: Mon, 29 Oct 2012 09:58:48 -0400
From: John C Klensin <john-ietf@jck.com>
To: Eliot Lear <lear@cisco.com>, Eric Burger <eburger-l@standardstrack.com>
Subject: Re: [RFC 3777 Update for Vacancies]
Message-ID: <EB7C203201A34EBCA9500A84@JcK-HP8200.jck.com>
In-Reply-To: <508E7F72.4010606@cisco.com>
References: <D90D92A7-0906-4620-93A0-D116D15A10FA@gmail.com> <20121026142930.B34B021F84D3@ietfa.amsl.com> <508AA611.7030206@cisco.com> <20121026151152.4F5AF21F862D@ietfa.amsl.com> <B5A61583C347AB7D9F752B11@JcK-HP8200.jck.com> <9A363D0FB7ED2D777C76867F@JcK-HP8200.jck.com> <13622014-D180-4737-A698-219C1832F1E1@standardstrack.com> <508E7F72.4010606@cisco.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
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: Mon, 29 Oct 2012 13:58:57 -0000

--On Monday, October 29, 2012 14:06 +0100 Eliot Lear
<lear@cisco.com> wrote:

> Bob, everyone,
>=20
> As I've mentioned, I'd prefer an alternative to what the
> authors have written.  Call this the "let's program ourselves
> out of a paper bag" option, when we all agree.  This may be a
> rule we would wish to generalize.  Here is the basis for what
> I propose:
>=20
>  1. We have existing procedures to resolve contested removals
> =E2=80=93 the     recall process.
>  2. "Uncontested" essentially means that we as a community are
> in     unanimous agreement that the position is vacant.  That
> means that by     definition, any "no" votes from a body means
> it's contested.  3. The least amount of power should be
> delegated to our bodies as is     necessary for the
> organization's smooth operation.  4. Procedural arguments on
> the IETF list are tiresome, when we all     agree on the right
> outcome ;-)
>=20
> With that in mind, I've attempted to reduce changes to a more
> simplified form, as follows:
>...
> NEW:
>=20
>     When an IETF body unanimously believes that a position on
> that     body has been vacated, they may request confirmation
> of this by     the community through an Extended Last Call
> with their reasoning.     Should no objections be received
> during that period, the position is     said to be vacant.

Eliot,

I generally like the general direction in which you are headed.
On other other hand, your specific proposal creates an
opportunity for a single individual, perhaps even one who
follows the mailing list but who is not an active participant in
the IETF or who just doesn't like the procedure, to disrupt
things and throw us back on recalls.   Given the number of
occasionally-grumpy people in the extended community, that does
not seem wise.

Quick thought and strawman suggestion: how about we take your
general model, but instead of using the absence of any
objections as the "not vacant, requires recall" trigger, perhaps
we could borrow a little bit from the recall model.  For
example, we might say that deciding that the procedure doesn't
apply when the body thinks the position is vacant requires a
petition endorsed by some number of people.  The "20" of the
recall procedure seems a bit high to me, but you get the general
idea.  One person claiming the position isn't really vacant
could be just a grump; ten or twenty probably indicates that
something odd is going on and a more heavyweight procedure is
required.

   john


From d3e3e3@gmail.com  Mon Oct 29 07:01:18 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 CD64E21F866D for <ietf@ietfa.amsl.com>; Mon, 29 Oct 2012 07:01:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xPAF5x9-Dx3S for <ietf@ietfa.amsl.com>; Mon, 29 Oct 2012 07:01:18 -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 6427821F8660 for <ietf@ietf.org>; Mon, 29 Oct 2012 07:01:12 -0700 (PDT)
Received: by mail-ob0-f172.google.com with SMTP id v19so5196879obq.31 for <ietf@ietf.org>; Mon, 29 Oct 2012 07:01: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:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=9l2ZfYKodDLDjbO8wOk8ffzFI0IIVJ3xxzlql/aKxeg=; b=ZnQddNmemQXO0kjX2kVBUjNHg6s7Oz7yVYqM9E0rydNaZdCmUZ9DLZURAbxce2YCZ2 bWsIiPRyNbOipj08ASfsOKoqdJdX80vSG+AzjmvPV6U67sZ0qfYZI3z+fmV/3DcLLiwN XZEQq42Az7Znxv/io4YhJ32V7xJ+7D11fjI83aB6UjpwzehKag7bCq9umC5UqIPRIrRi d1Kyxy3MfTO4pawTTTwHLYOj8X70Fh/3M71SUUV2cv5DV+N7zr1erm/hjnTcJUbmcbJF fSQx+cNRCm/u/NDp7kC0dFNX6UpXTri7nQxolLKERZFFO1roA3XWkXCQudVJ2r1bEPgu eY0g==
Received: by 10.60.22.161 with SMTP id e1mr25609929oef.93.1351519272049; Mon, 29 Oct 2012 07:01:12 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.60.41.36 with HTTP; Mon, 29 Oct 2012 07:00:51 -0700 (PDT)
In-Reply-To: <EB7C203201A34EBCA9500A84@JcK-HP8200.jck.com>
References: <D90D92A7-0906-4620-93A0-D116D15A10FA@gmail.com> <20121026142930.B34B021F84D3@ietfa.amsl.com> <508AA611.7030206@cisco.com> <20121026151152.4F5AF21F862D@ietfa.amsl.com> <B5A61583C347AB7D9F752B11@JcK-HP8200.jck.com> <9A363D0FB7ED2D777C76867F@JcK-HP8200.jck.com> <13622014-D180-4737-A698-219C1832F1E1@standardstrack.com> <508E7F72.4010606@cisco.com> <EB7C203201A34EBCA9500A84@JcK-HP8200.jck.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Mon, 29 Oct 2012 10:00:51 -0400
Message-ID: <CAF4+nEE8KOph091zmLBRQOsktExMvKoigDPWs0uu1jufkcFUng@mail.gmail.com>
Subject: Re: [RFC 3777 Update for Vacancies]
To: Eliot Lear <lear@cisco.com>, John C Klensin <john-ietf@jck.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
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: Mon, 29 Oct 2012 14:01:18 -0000

On Mon, Oct 29, 2012 at 9:58 AM, John C Klensin <john-ietf@jck.com> wrote:
>
>
> --On Monday, October 29, 2012 14:06 +0100 Eliot Lear
> <lear@cisco.com> wrote:
>
>> Bob, everyone,
>>
>> As I've mentioned, I'd prefer an alternative to what the
>> authors have written.  Call this the "let's program ourselves
>> out of a paper bag" option, when we all agree.  This may be a
>> rule we would wish to generalize.  Here is the basis for what
>> I propose:
>>
>>  1. We have existing procedures to resolve contested removals
>> =96 the     recall process.
>>  2. "Uncontested" essentially means that we as a community are
>> in     unanimous agreement that the position is vacant.  That
>> means that by     definition, any "no" votes from a body means
>> it's contested.  3. The least amount of power should be
>> delegated to our bodies as is     necessary for the
>> organization's smooth operation.  4. Procedural arguments on
>> the IETF list are tiresome, when we all     agree on the right
>> outcome ;-)
>>
>> With that in mind, I've attempted to reduce changes to a more
>> simplified form, as follows:
>>...
>> NEW:
>>
>>     When an IETF body unanimously believes that a position on
>> that     body has been vacated, they may request confirmation
>> of this by     the community through an Extended Last Call
>> with their reasoning.     Should no objections be received
>> during that period, the position is     said to be vacant.
>
> Eliot,
>
> I generally like the general direction in which you are headed.
> On other other hand, your specific proposal creates an
> opportunity for a single individual, perhaps even one who
> follows the mailing list but who is not an active participant in
> the IETF or who just doesn't like the procedure, to disrupt
> things and throw us back on recalls.   Given the number of
> occasionally-grumpy people in the extended community, that does
> not seem wise.

+1

Thanks,
Donald
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 155 Beaver Street, Milford, MA 01757 USA
 d3e3e3@gmail.com


> Quick thought and strawman suggestion: how about we take your
> general model, but instead of using the absence of any
> objections as the "not vacant, requires recall" trigger, perhaps
> we could borrow a little bit from the recall model.  For
> example, we might say that deciding that the procedure doesn't
> apply when the body thinks the position is vacant requires a
> petition endorsed by some number of people.  The "20" of the
> recall procedure seems a bit high to me, but you get the general
> idea.  One person claiming the position isn't really vacant
> could be just a grump; ten or twenty probably indicates that
> something odd is going on and a more heavyweight procedure is
> required.
>
>    john
>

From eburger-l@standardstrack.com  Mon Oct 29 07:01:35 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 D1E7421F86E1 for <ietf@ietfa.amsl.com>; Mon, 29 Oct 2012 07:01:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.299
X-Spam-Level: 
X-Spam-Status: No, score=-1.299 tagged_above=-999 required=5 tests=[AWL=1.300,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0TE5mEg9yc4K for <ietf@ietfa.amsl.com>; Mon, 29 Oct 2012 07:01:35 -0700 (PDT)
Received: from biz104.inmotionhosting.com (biz104.inmotionhosting.com [173.247.254.120]) by ietfa.amsl.com (Postfix) with ESMTP id 4604821F86DB for <ietf@ietf.org>; Mon, 29 Oct 2012 07:01:35 -0700 (PDT)
Received: from ip68-100-199-8.dc.dc.cox.net ([68.100.199.8]:49314 helo=[192.168.15.175]) by biz104.inmotionhosting.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.77) (envelope-from <eburger-l@standardstrack.com>) id 1TSpuE-0003sM-F3 for ietf@ietf.org; Mon, 29 Oct 2012 07:01:32 -0700
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Apple Message framework v1085)
Subject: Re: [RFC 3777 Update for Vacancies]
From: Eric Burger <eburger-l@standardstrack.com>
In-Reply-To: <EB7C203201A34EBCA9500A84@JcK-HP8200.jck.com>
Date: Mon, 29 Oct 2012 10:01:29 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <C9FA0E62-D17B-4EDA-A399-3B3643027D5E@standardstrack.com>
References: <D90D92A7-0906-4620-93A0-D116D15A10FA@gmail.com> <20121026142930.B34B021F84D3@ietfa.amsl.com> <508AA611.7030206@cisco.com> <20121026151152.4F5AF21F862D@ietfa.amsl.com> <B5A61583C347AB7D9F752B11@JcK-HP8200.jck.com> <9A363D0FB7ED2D777C76867F@JcK-HP8200.jck.com> <13622014-D180-4737-A698-219C1832F1E1@standardstrack.com> <508E7F72.4010606@cisco.com> <EB7C203201A34EBCA9500A84@JcK-HP8200.jck.com>
To: IETF list <ietf@ietf.org>
X-Mailer: Apple Mail (2.1085)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - biz104.inmotionhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - standardstrack.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Oct 2012 14:01:35 -0000

Sounds reasonable to me.


On Oct 29, 2012, at 9:58 AM, John C Klensin wrote:

>=20
>=20
> --On Monday, October 29, 2012 14:06 +0100 Eliot Lear
> <lear@cisco.com> wrote:
>=20
>> Bob, everyone,
>>=20
>> As I've mentioned, I'd prefer an alternative to what the
>> authors have written.  Call this the "let's program ourselves
>> out of a paper bag" option, when we all agree.  This may be a
>> rule we would wish to generalize.  Here is the basis for what
>> I propose:
>>=20
>> 1. We have existing procedures to resolve contested removals
>> =96 the     recall process.
>> 2. "Uncontested" essentially means that we as a community are
>> in     unanimous agreement that the position is vacant.  That
>> means that by     definition, any "no" votes from a body means
>> it's contested.  3. The least amount of power should be
>> delegated to our bodies as is     necessary for the
>> organization's smooth operation.  4. Procedural arguments on
>> the IETF list are tiresome, when we all     agree on the right
>> outcome ;-)
>>=20
>> With that in mind, I've attempted to reduce changes to a more
>> simplified form, as follows:
>> ...
>> NEW:
>>=20
>>    When an IETF body unanimously believes that a position on
>> that     body has been vacated, they may request confirmation
>> of this by     the community through an Extended Last Call
>> with their reasoning.     Should no objections be received
>> during that period, the position is     said to be vacant.
>=20
> Eliot,
>=20
> I generally like the general direction in which you are headed.
> On other other hand, your specific proposal creates an
> opportunity for a single individual, perhaps even one who
> follows the mailing list but who is not an active participant in
> the IETF or who just doesn't like the procedure, to disrupt
> things and throw us back on recalls.   Given the number of
> occasionally-grumpy people in the extended community, that does
> not seem wise.
>=20
> Quick thought and strawman suggestion: how about we take your
> general model, but instead of using the absence of any
> objections as the "not vacant, requires recall" trigger, perhaps
> we could borrow a little bit from the recall model.  For
> example, we might say that deciding that the procedure doesn't
> apply when the body thinks the position is vacant requires a
> petition endorsed by some number of people.  The "20" of the
> recall procedure seems a bit high to me, but you get the general
> idea.  One person claiming the position isn't really vacant
> could be just a grump; ten or twenty probably indicates that
> something odd is going on and a more heavyweight procedure is
> required.
>=20
>   john
>=20


From rbonica@juniper.net  Mon Oct 29 07:22:46 2012
Return-Path: <rbonica@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 91DD821F84E1 for <ietf@ietfa.amsl.com>; Mon, 29 Oct 2012 07:22:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.722
X-Spam-Level: 
X-Spam-Status: No, score=-102.722 tagged_above=-999 required=5 tests=[AWL=0.745, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, UNRESOLVED_TEMPLATE=3.132, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Bl3VAIiqp5lr for <ietf@ietfa.amsl.com>; Mon, 29 Oct 2012 07:22:46 -0700 (PDT)
Received: from exprod7og119.obsmtp.com (exprod7og119.obsmtp.com [64.18.2.16]) by ietfa.amsl.com (Postfix) with ESMTP id 8F22821F84EC for <ietf@ietf.org>; Mon, 29 Oct 2012 07:22:45 -0700 (PDT)
Received: from P-EMHUB03-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob119.postini.com ([64.18.6.12]) with SMTP ID DSNKUI6RNSTllovu7iVN2nCHzVp0Mjr4Q7Ho@postini.com; Mon, 29 Oct 2012 07:22:45 PDT
Received: from P-CLDFE02-HQ.jnpr.net (172.24.192.60) by P-EMHUB03-HQ.jnpr.net (172.24.192.37) with Microsoft SMTP Server (TLS) id 8.3.213.0; Mon, 29 Oct 2012 07:12:45 -0700
Received: from o365mail.juniper.net (207.17.137.224) by o365mail.juniper.net (172.24.192.60) with Microsoft SMTP Server id 14.1.355.2; Mon, 29 Oct 2012 07:12:45 -0700
Received: from co1outboundpool.messaging.microsoft.com (216.32.180.188) by o365mail.juniper.net (207.17.137.224) with Microsoft SMTP Server (TLS) id 14.1.355.2; Mon, 29 Oct 2012 07:18:54 -0700
Received: from mail66-co1-R.bigfish.com (10.243.78.246) by CO1EHSOBE015.bigfish.com (10.243.66.78) with Microsoft SMTP Server id 14.1.225.23; Mon, 29 Oct 2012 14:12:44 +0000
Received: from mail66-co1 (localhost [127.0.0.1])	by mail66-co1-R.bigfish.com (Postfix) with ESMTP id 98093680090	for <ietf@ietf.org.FOPE.CONNECTOR.OVERRIDE>; Mon, 29 Oct 2012 14:12:44 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.237.149; KIP:(null); UIP:(null); (null); H:BY2PRD0511HT002.namprd05.prod.outlook.com; R:internal; EFV:INT
X-SpamScore: -6
X-BigFish: PS-6(zz542M1432Izz1202h1d1ah1d2ahzzz2dh2a8h668h839h944hd25hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh1155h)
Received: from mail66-co1 (localhost.localdomain [127.0.0.1]) by mail66-co1 (MessageSwitch) id 1351519962576434_1974; Mon, 29 Oct 2012 14:12:42 +0000 (UTC)
Received: from CO1EHSMHS025.bigfish.com (unknown [10.243.78.231])	by mail66-co1.bigfish.com (Postfix) with ESMTP id 8B05FA0005A; Mon, 29 Oct 2012 14:12:42 +0000 (UTC)
Received: from BY2PRD0511HT002.namprd05.prod.outlook.com (157.56.237.149) by CO1EHSMHS025.bigfish.com (10.243.66.35) with Microsoft SMTP Server (TLS) id 14.1.225.23; Mon, 29 Oct 2012 14:12:41 +0000
Received: from BY2PRD0511MB417.namprd05.prod.outlook.com ([169.254.12.23]) by BY2PRD0511HT002.namprd05.prod.outlook.com ([10.255.129.37]) with mapi id 14.16.0233.002; Mon, 29 Oct 2012 14:12:37 +0000
From: Ronald Bonica <rbonica@juniper.net>
To: RJ Atkinson <rja.lists@gmail.com>
Subject: RE: Last Call: <draft-ietf-v6ops-ra-guard-implementation-04.txt> (Implementation Advice for IPv6 Router Advertisement Guard	(RA-Guard)) to Best Current Practice
Thread-Topic: Last Call: <draft-ietf-v6ops-ra-guard-implementation-04.txt> (Implementation Advice for IPv6 Router Advertisement Guard	(RA-Guard)) to Best Current Practice
Thread-Index: AQHNs6iP2hKi74KDcUKO1sESHWR3wZfQVzWg
Date: Mon, 29 Oct 2012 14:12:37 +0000
Message-ID: <2CF4CB03E2AA464BA0982EC92A02CE25034133@BY2PRD0511MB417.namprd05.prod.outlook.com>
References: <20121026160427.30056.5891.idtracker@ietfa.amsl.com> <2164CBA8-3B59-4A83-A170-B68D118B44FC@gmail.com> <2CF4CB03E2AA464BA0982EC92A02CE2502DAF8@CH1PRD0511MB418.namprd05.prod.outlook.com> <0C27784D-05DC-4ABE-BFAA-8301551D4714@gmail.com>
In-Reply-To: <0C27784D-05DC-4ABE-BFAA-8301551D4714@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [66.129.232.2]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
X-FOPE-CONNECTOR: Id%12219$Dn%GMAIL.COM$RO%2$TLS%5$FQDN%onpremiseedge-1018244.customer.frontbridge.com$TlsDn%o365mail.juniper.net
X-FOPE-CONNECTOR: Id%12219$Dn%IETF.ORG$RO%2$TLS%5$FQDN%onpremiseedge-1018244.customer.frontbridge.com$TlsDn%o365mail.juniper.net
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Oct 2012 14:22:46 -0000

Ran,

Yes, he does. In fact, I thought that it had already been posted when I iss=
ued the last call, but forgot about the draft cutoff.

So, I have asked the secretariat to post the updated version.

                                 Ron


> -----Original Message-----
> From: RJ Atkinson [mailto:rja.lists@gmail.com]
>=20
> I might be confused, but I understand that Fernando
> has an updated RA-Guard I-D "ready to post".
>=20



From john-ietf@jck.com  Mon Oct 29 07:39:26 2012
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EE08B21F85C6 for <ietf@ietfa.amsl.com>; Mon, 29 Oct 2012 07:39:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.351
X-Spam-Level: 
X-Spam-Status: No, score=-102.351 tagged_above=-999 required=5 tests=[AWL=0.248, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eGnsT6UhEvZI for <ietf@ietfa.amsl.com>; Mon, 29 Oct 2012 07:39:26 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 70EEC21F85B6 for <ietf@ietf.org>; Mon, 29 Oct 2012 07:39:26 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1TSqUv-0001E1-SQ; Mon, 29 Oct 2012 10:39:25 -0400
Date: Mon, 29 Oct 2012 10:39:20 -0400
From: John C Klensin <john-ietf@jck.com>
To: Eric Burger <eburger-l@standardstrack.com>, IETF list <ietf@ietf.org>
Subject: Re: [RFC 3777 Update for Vacancies]
Message-ID: <957D18C44076BA88E73669E7@JcK-HP8200.jck.com>
In-Reply-To: <13622014-D180-4737-A698-219C1832F1E1@standardstrack.com>
References: <D90D92A7-0906-4620-93A0-D116D15A10FA@gmail.com> <20121026142930.B34B021F84D3@ietfa.amsl.com> <508AA611.7030206@cisco.com> <20121026151152.4F5AF21F862D@ietfa.amsl.com> <B5A61583C347AB7D9F752B11@JcK-HP8200.jck.com> <9A363D0FB7ED2D777C76867F@JcK-HP8200.jck.com> <13622014-D180-4737-A698-219C1832F1E1@standardstrack.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: Mon, 29 Oct 2012 14:39:27 -0000

--On Sunday, October 28, 2012 13:31 -0400 Eric Burger
<eburger-l@standardstrack.com> wrote:

> If someone falls off the face of the Earth, and repeated
> attempts to contact them using legally recognized methods of
> notice fails, and more importantly they have a positive track
> record that spans over a decade, we can use our existing
> nomcom tools to replace their nomcom-appointed duties. I would
> offer that a person in such a position with such demonstrated
> dedication would not want us to do otherwise.

IMO, Eric's last sentence above is exactly the essence of why I
think a lightweight (and different-from-recall) procedure is
needed.  Suppose we have a long-standing positive contributor,
or even someone who took a high-responsibility position in good
faith but then discovered that he or she was seriously in over
their head.  That person responds to conditions beyond our
control (and maybe beyond theirs) by disappearing and not
responding to attempts to get them to clarify things.  Whatever
is causing those symptoms, we probably do both the community and
the person involved a favor by replacing them and moving forward
without making a huge fuss about it.   There have to be
safeguards, but there don't need to be formal accusations of
malfeasance.

Coming back to the note from which Eric quoted, none of the
above has anything to do with someone who is consistently
behaving like a jerk -- whether by participation or
non-participation (including active attempts to resist vacancy
claims when they aren't doing anything).  For those situations,
the determination of whether a sufficient level of jerk-like
behavior has been achieved to justify expulsion needs to be made
by the community, not by irritated fellow members of the
affected body.  Our presumption is that recall is a perfectly
adequate mechanism for that purpose.  If it isn't, we should fix
it, but it has nothing to do with the case described above.

   best,
   john


From edj.etc@gmail.com  Mon Oct 29 14:18:04 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 D0F5021F85C6; Mon, 29 Oct 2012 14:18:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.846
X-Spam-Level: 
X-Spam-Status: No, score=-101.846 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_BASE64_TEXT=1.753, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4P9RLDVW+fvc; Mon, 29 Oct 2012 14:18:04 -0700 (PDT)
Received: from mail-ia0-f172.google.com (mail-ia0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id 2950321F8516; Mon, 29 Oct 2012 14:18:04 -0700 (PDT)
Received: by mail-ia0-f172.google.com with SMTP id x24so2627535iak.31 for <multiple recipients>; Mon, 29 Oct 2012 14:18:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-rim-org-msg-ref-id:message-id:content-transfer-encoding:reply-to :x-priority:references:in-reply-to:sensitivity:importance:subject:to :cc:from:date:content-type:mime-version; bh=3D6ykucRIQvPMNx5ZiX45pctoE2UiYaKrs+XcraN9Kg=; b=bL/e8YIfj0Q51W1WOD7SW2myMyfVY5iewbRmVXJcNmNKPfKw1h052ET9J8dYjO0c9/ yPikvUM4k4LtGMfxccElYcgCUDcvz2JVnT/OWHhesyDzhuCq6tAU0MxraCf1P2y3ThZ3 6hL3hxDsFfn48EmCyav8yh8rhovibwuiRDs1guNHICrpN0yCVBPXFFBBu9r4KmhrEOuo 7kkwruXsOq/zOrAB0SF6vuyZUSHKxkKAYyOajwVW0P3Ia26HZGkPHoEm616XaucKRcXQ eLEZOK5WbgOXowHK2rTMjxWDhKXY/qD8ufkB3DLZcBWrh/MbDVZOsf7e2lwxhBjXJri9 mT0g==
Received: by 10.50.15.194 with SMTP id z2mr10723727igc.30.1351545483755; Mon, 29 Oct 2012 14:18:03 -0700 (PDT)
Received: from 172.29.195.188 (bda-74-82-80-72.bis6.us.blackberry.com. [74.82.80.72]) by mx.google.com with ESMTPS id hg2sm6452261igc.3.2012.10.29.14.18.02 (version=SSLv3 cipher=OTHER); Mon, 29 Oct 2012 14:18:03 -0700 (PDT)
X-rim-org-msg-ref-id: 1761739935
Message-ID: <1761739935-1351545481-cardhu_decombobulator_blackberry.rim.net-893299132-@b2.c2.bise6.blackberry>
Content-Transfer-Encoding: base64
X-Priority: Normal
References: <D90D92A7-0906-4620-93A0-D116D15A10FA@gmail.com> <20121026142930.B34B021F84D3@ietfa.amsl.com> <508AA611.7030206@cisco.com> <20121026151152.4F5AF21F862D@ietfa.amsl.com> <B5A61583C347AB7D9F752B11@JcK-HP8200.jck.com> <9A363D0FB7ED2D777C76867F@JcK-HP8200.jck.com> <13622014-D180-4737-A698-219C1832F1E1@standardstrack.com> <508E7F72.4010606@cisco.com> <EB7C203201A34EBCA9500A84@JcK-HP8200.jck.com> <CAF4+nEE8KOph091zmLBRQOsktExMvKoigDPWs0uu1jufkcFUng@mail.gmail.com>
In-Reply-To: <CAF4+nEE8KOph091zmLBRQOsktExMvKoigDPWs0uu1jufkcFUng@mail.gmail.com>
Sensitivity: Normal
Importance: Normal
Subject: Re: [RFC 3777 Update for Vacancies]
To: "Donald Eastlake" <d3e3e3@gmail.com>, ietf-bounces@ietf.org, "Eliot Lear" <lear@cisco.com>, "John C Klensin" <john-ietf@jck.com>
From: edj.etc@gmail.com
Date: Mon, 29 Oct 2012 21:18:00 +0000
Content-Type: text/plain; charset="Windows-1252"
MIME-Version: 1.0
Cc: IETF list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: edj.etc@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: Mon, 29 Oct 2012 21:18:05 -0000

KzENCiANClJlZ2FyZHMsDQogDQpFZCAgSi4NCiANCi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0t
DQpGcm9tOiBEb25hbGQgRWFzdGxha2UgPGQzZTNlM0BnbWFpbC5jb20+DQpTZW5kZXI6IGlldGYt
Ym91bmNlc0BpZXRmLm9yZw0KRGF0ZTogTW9uLCAyOSBPY3QgMjAxMiAxMDowMDo1MSANClRvOiBF
bGlvdCBMZWFyPGxlYXJAY2lzY28uY29tPjsgSm9obiBDIEtsZW5zaW48am9obi1pZXRmQGpjay5j
b20+DQpDYzogSUVURiBsaXN0PGlldGZAaWV0Zi5vcmc+DQpTdWJqZWN0OiBSZTogW1JGQyAzNzc3
IFVwZGF0ZSBmb3IgVmFjYW5jaWVzXQ0KDQpPbiBNb24sIE9jdCAyOSwgMjAxMiBhdCA5OjU4IEFN
LCBKb2huIEMgS2xlbnNpbiA8am9obi1pZXRmQGpjay5jb20+IHdyb3RlOg0KPg0KPg0KPiAtLU9u
IE1vbmRheSwgT2N0b2JlciAyOSwgMjAxMiAxNDowNiArMDEwMCBFbGlvdCBMZWFyDQo+IDxsZWFy
QGNpc2NvLmNvbT4gd3JvdGU6DQo+DQo+PiBCb2IsIGV2ZXJ5b25lLA0KPj4NCj4+IEFzIEkndmUg
bWVudGlvbmVkLCBJJ2QgcHJlZmVyIGFuIGFsdGVybmF0aXZlIHRvIHdoYXQgdGhlDQo+PiBhdXRo
b3JzIGhhdmUgd3JpdHRlbi4gIENhbGwgdGhpcyB0aGUgImxldCdzIHByb2dyYW0gb3Vyc2VsdmVz
DQo+PiBvdXQgb2YgYSBwYXBlciBiYWciIG9wdGlvbiwgd2hlbiB3ZSBhbGwgYWdyZWUuICBUaGlz
IG1heSBiZSBhDQo+PiBydWxlIHdlIHdvdWxkIHdpc2ggdG8gZ2VuZXJhbGl6ZS4gIEhlcmUgaXMg
dGhlIGJhc2lzIGZvciB3aGF0DQo+PiBJIHByb3Bvc2U6DQo+Pg0KPj4gIDEuIFdlIGhhdmUgZXhp
c3RpbmcgcHJvY2VkdXJlcyB0byByZXNvbHZlIGNvbnRlc3RlZCByZW1vdmFscw0KPj4gliB0aGUg
ICAgIHJlY2FsbCBwcm9jZXNzLg0KPj4gIDIuICJVbmNvbnRlc3RlZCIgZXNzZW50aWFsbHkgbWVh
bnMgdGhhdCB3ZSBhcyBhIGNvbW11bml0eSBhcmUNCj4+IGluICAgICB1bmFuaW1vdXMgYWdyZWVt
ZW50IHRoYXQgdGhlIHBvc2l0aW9uIGlzIHZhY2FudC4gIFRoYXQNCj4+IG1lYW5zIHRoYXQgYnkg
ICAgIGRlZmluaXRpb24sIGFueSAibm8iIHZvdGVzIGZyb20gYSBib2R5IG1lYW5zDQo+PiBpdCdz
IGNvbnRlc3RlZC4gIDMuIFRoZSBsZWFzdCBhbW91bnQgb2YgcG93ZXIgc2hvdWxkIGJlDQo+PiBk
ZWxlZ2F0ZWQgdG8gb3VyIGJvZGllcyBhcyBpcyAgICAgbmVjZXNzYXJ5IGZvciB0aGUNCj4+IG9y
Z2FuaXphdGlvbidzIHNtb290aCBvcGVyYXRpb24uICA0LiBQcm9jZWR1cmFsIGFyZ3VtZW50cyBv
bg0KPj4gdGhlIElFVEYgbGlzdCBhcmUgdGlyZXNvbWUsIHdoZW4gd2UgYWxsICAgICBhZ3JlZSBv
biB0aGUgcmlnaHQNCj4+IG91dGNvbWUgOy0pDQo+Pg0KPj4gV2l0aCB0aGF0IGluIG1pbmQsIEkn
dmUgYXR0ZW1wdGVkIHRvIHJlZHVjZSBjaGFuZ2VzIHRvIGEgbW9yZQ0KPj4gc2ltcGxpZmllZCBm
b3JtLCBhcyBmb2xsb3dzOg0KPj4uLi4NCj4+IE5FVzoNCj4+DQo+PiAgICAgV2hlbiBhbiBJRVRG
IGJvZHkgdW5hbmltb3VzbHkgYmVsaWV2ZXMgdGhhdCBhIHBvc2l0aW9uIG9uDQo+PiB0aGF0ICAg
ICBib2R5IGhhcyBiZWVuIHZhY2F0ZWQsIHRoZXkgbWF5IHJlcXVlc3QgY29uZmlybWF0aW9uDQo+
PiBvZiB0aGlzIGJ5ICAgICB0aGUgY29tbXVuaXR5IHRocm91Z2ggYW4gRXh0ZW5kZWQgTGFzdCBD
YWxsDQo+PiB3aXRoIHRoZWlyIHJlYXNvbmluZy4gICAgIFNob3VsZCBubyBvYmplY3Rpb25zIGJl
IHJlY2VpdmVkDQo+PiBkdXJpbmcgdGhhdCBwZXJpb2QsIHRoZSBwb3NpdGlvbiBpcyAgICAgc2Fp
ZCB0byBiZSB2YWNhbnQuDQo+DQo+IEVsaW90LA0KPg0KPiBJIGdlbmVyYWxseSBsaWtlIHRoZSBn
ZW5lcmFsIGRpcmVjdGlvbiBpbiB3aGljaCB5b3UgYXJlIGhlYWRlZC4NCj4gT24gb3RoZXIgb3Ro
ZXIgaGFuZCwgeW91ciBzcGVjaWZpYyBwcm9wb3NhbCBjcmVhdGVzIGFuDQo+IG9wcG9ydHVuaXR5
IGZvciBhIHNpbmdsZSBpbmRpdmlkdWFsLCBwZXJoYXBzIGV2ZW4gb25lIHdobw0KPiBmb2xsb3dz
IHRoZSBtYWlsaW5nIGxpc3QgYnV0IHdobyBpcyBub3QgYW4gYWN0aXZlIHBhcnRpY2lwYW50IGlu
DQo+IHRoZSBJRVRGIG9yIHdobyBqdXN0IGRvZXNuJ3QgbGlrZSB0aGUgcHJvY2VkdXJlLCB0byBk
aXNydXB0DQo+IHRoaW5ncyBhbmQgdGhyb3cgdXMgYmFjayBvbiByZWNhbGxzLiAgIEdpdmVuIHRo
ZSBudW1iZXIgb2YNCj4gb2NjYXNpb25hbGx5LWdydW1weSBwZW9wbGUgaW4gdGhlIGV4dGVuZGVk
IGNvbW11bml0eSwgdGhhdCBkb2VzDQo+IG5vdCBzZWVtIHdpc2UuDQoNCisxDQoNClRoYW5rcywN
CkRvbmFsZA0KPT09PT09PT09PT09PT09PT09PT09PT09PT09PT0NCiBEb25hbGQgRS4gRWFzdGxh
a2UgM3JkICAgKzEtNTA4LTMzMy0yMjcwIChjZWxsKQ0KIDE1NSBCZWF2ZXIgU3RyZWV0LCBNaWxm
b3JkLCBNQSAwMTc1NyBVU0ENCiBkM2UzZTNAZ21haWwuY29tDQoNCg0KPiBRdWljayB0aG91Z2h0
IGFuZCBzdHJhd21hbiBzdWdnZXN0aW9uOiBob3cgYWJvdXQgd2UgdGFrZSB5b3VyDQo+IGdlbmVy
YWwgbW9kZWwsIGJ1dCBpbnN0ZWFkIG9mIHVzaW5nIHRoZSBhYnNlbmNlIG9mIGFueQ0KPiBvYmpl
Y3Rpb25zIGFzIHRoZSAibm90IHZhY2FudCwgcmVxdWlyZXMgcmVjYWxsIiB0cmlnZ2VyLCBwZXJo
YXBzDQo+IHdlIGNvdWxkIGJvcnJvdyBhIGxpdHRsZSBiaXQgZnJvbSB0aGUgcmVjYWxsIG1vZGVs
LiAgRm9yDQo+IGV4YW1wbGUsIHdlIG1pZ2h0IHNheSB0aGF0IGRlY2lkaW5nIHRoYXQgdGhlIHBy
b2NlZHVyZSBkb2Vzbid0DQo+IGFwcGx5IHdoZW4gdGhlIGJvZHkgdGhpbmtzIHRoZSBwb3NpdGlv
biBpcyB2YWNhbnQgcmVxdWlyZXMgYQ0KPiBwZXRpdGlvbiBlbmRvcnNlZCBieSBzb21lIG51bWJl
ciBvZiBwZW9wbGUuICBUaGUgIjIwIiBvZiB0aGUNCj4gcmVjYWxsIHByb2NlZHVyZSBzZWVtcyBh
IGJpdCBoaWdoIHRvIG1lLCBidXQgeW91IGdldCB0aGUgZ2VuZXJhbA0KPiBpZGVhLiAgT25lIHBl
cnNvbiBjbGFpbWluZyB0aGUgcG9zaXRpb24gaXNuJ3QgcmVhbGx5IHZhY2FudA0KPiBjb3VsZCBi
ZSBqdXN0IGEgZ3J1bXA7IHRlbiBvciB0d2VudHkgcHJvYmFibHkgaW5kaWNhdGVzIHRoYXQNCj4g
c29tZXRoaW5nIG9kZCBpcyBnb2luZyBvbiBhbmQgYSBtb3JlIGhlYXZ5d2VpZ2h0IHByb2NlZHVy
ZSBpcw0KPiByZXF1aXJlZC4NCj4NCj4gICAgam9obg0KPg0K


From tglassey@earthlink.net  Mon Oct 29 15:17:54 2012
Return-Path: <tglassey@earthlink.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1599A21F8507 for <ietf@ietfa.amsl.com>; Mon, 29 Oct 2012 15:17:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.001
X-Spam-Level: 
X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[BAYES_50=0.001]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DzzPVncVx1ik for <ietf@ietfa.amsl.com>; Mon, 29 Oct 2012 15:17:53 -0700 (PDT)
Received: from elasmtp-spurfowl.atl.sa.earthlink.net (elasmtp-spurfowl.atl.sa.earthlink.net [209.86.89.66]) by ietfa.amsl.com (Postfix) with ESMTP id 3132F21F84FB for <ietf@ietf.org>; Mon, 29 Oct 2012 15:17:53 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=mM6EYm4Xoe9vJcY1sqgAiLGx4x88n2THcGzODE5cjYzfTL1JqUHY6/LUOzi3eVC7; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [67.180.133.21] (helo=[192.168.15.2]) by elasmtp-spurfowl.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from <tglassey@earthlink.net>) id 1TSxea-000593-IG for ietf@ietf.org; Mon, 29 Oct 2012 18:17:52 -0400
Message-ID: <508F0091.8010502@earthlink.net>
Date: Mon, 29 Oct 2012 15:17:53 -0700
From: tglassey <tglassey@earthlink.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: ietf <ietf@ietf.org>
Subject: New Copyright directives from Librarian of Congress specific to use,  exemptions and rights therein...
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 01b7a7e171bdf5911aa676d7e74259b7b3291a7d08dfec79a7a8881c73c7588210b869adea37ad70350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 67.180.133.21
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Oct 2012 22:17:54 -0000

The game has changed a tad and now there is a three year cap on the 
exemption for use which clearly will possibly impact the BCP78 and BCP79 
use statements.

https://www.federalregister.gov/articles/2012/10/26/2012-26308/exemption-to-prohibition-on-circumvention-of-copyright-protection-systems-for-access-control#h-23

https://www.federalregister.gov/articles/2012/10/26/2012-26308/exemption-to-prohibition-on-circumvention-of-copyright-protection-systems-for-access-control#h-20

-- 
Regards TSG
"Ex-Cruce-Leo"

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


From bertietf@bwijnen.net  Wed Oct 31 01:40:36 2012
Return-Path: <bertietf@bwijnen.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 289D921F873C for <ietf@ietfa.amsl.com>; Wed, 31 Oct 2012 01:40:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wFcYzpVNvwBH for <ietf@ietfa.amsl.com>; Wed, 31 Oct 2012 01:40:35 -0700 (PDT)
Received: from postgirl.ripe.net (postgirl.ipv6.ripe.net [IPv6:2001:67c:2e8:11::c100:1342]) by ietfa.amsl.com (Postfix) with ESMTP id 21E9221F8742 for <ietf@ietf.org>; Wed, 31 Oct 2012 01:40:35 -0700 (PDT)
Received: from dodo.ripe.net ([193.0.23.4]) by postgirl.ripe.net with esmtps (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from <bertietf@bwijnen.net>) id 1TTTqh-00087c-7S for ietf@ietf.org; Wed, 31 Oct 2012 09:40:32 +0100
Received: from dog.ripe.net ([193.0.1.217] helo=BWMACBOOK.local) by dodo.ripe.net with esmtp (Exim 4.72) (envelope-from <bertietf@bwijnen.net>) id 1TTTqg-0005jq-U0 for ietf@ietf.org; Wed, 31 Oct 2012 09:40:31 +0100
Message-ID: <5090E3FE.805@bwijnen.net>
Date: Wed, 31 Oct 2012 09:40:30 +0100
From: "Bert Wijnen (IETF)" <bertietf@bwijnen.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: RIPE NCC ATLAS Measurements around Sandy
References: <5090E321.8070601@ripe.net>
In-Reply-To: <5090E321.8070601@ripe.net>
X-Forwarded-Message-Id: <5090E321.8070601@ripe.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Anti-Virus: Kaspersky Anti-Virus for Linux Mail Server 5.6.48/RELEASE, bases: 20120425 #7816575, check: 20121031 clean
X-RIPE-Spam-Level: --
X-RIPE-Spam-Report: Spam Total Points:   -2.9 points pts rule name              description ---- ---------------------- ------------------------------------ -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP -1.9 BAYES_00               BODY: Bayes spam probability is 0 to 1% [score: 0.0000]
X-RIPE-Signature: 86ab03e524994f79ca2c75a176445dd499ae00e8560b40282050de0f407cc473
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Oct 2012 08:40:36 -0000

In case people are interested.

Some of you might be interested to know that we have
tried to see any impacts of Sandy via our ATLAS measurements.

Latest update of the graphs:
http://albatross.ripe.net/demo-area/sandy-2012/

Article that explains the graphs
https://labs.ripe.net/Members/emileaben/ripe-atlas-superstorm-sandy

Bert



From ford@isoc.org  Wed Oct 31 07:04:36 2012
Return-Path: <ford@isoc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 20EB521F87FC for <ietf@ietfa.amsl.com>; Wed, 31 Oct 2012 07:04:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.265
X-Spam-Level: 
X-Spam-Status: No, score=-103.265 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TPkmM4BEmsmW for <ietf@ietfa.amsl.com>; Wed, 31 Oct 2012 07:04:35 -0700 (PDT)
Received: from smtp147.dfw.emailsrvr.com (smtp147.dfw.emailsrvr.com [67.192.241.147]) by ietfa.amsl.com (Postfix) with ESMTP id 882DF21F84D6 for <ietf@ietf.org>; Wed, 31 Oct 2012 07:04:35 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp4.relay.dfw1a.emailsrvr.com (SMTP Server) with ESMTP id 09C1C3A04D3 for <ietf@ietf.org>; Wed, 31 Oct 2012 10:04:35 -0400 (EDT)
X-Virus-Scanned: OK
Received: by smtp4.relay.dfw1a.emailsrvr.com (Authenticated sender: ford-AT-isoc.org) with ESMTPSA id 469C03A0120 for <ietf@ietf.org>; Wed, 31 Oct 2012 10:04:34 -0400 (EDT)
From: Matthew Ford <ford@isoc.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: IETF Journal - latest issue now available
Message-Id: <CDBD0FE7-1710-4AAB-A1C7-BD744796CF1F@isoc.org>
Date: Wed, 31 Oct 2012 14:03:52 +0000
To: "ietf@ietf.org Discussion" <ietf@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
X-Mailer: Apple Mail (2.1499)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Oct 2012 14:04:36 -0000

Hi,

The latest issue of the IETF Journal (Volume 8, Issue 2) is available =
online:

	http://internetsociety.org/ietfjournal

Among others it contains articles on the impact of World IPv6 Launch, =
using JSON in IETF protocols, software-defined networking, and moving =
toward a censorship-free Internet.

In addition you will find summary reports of the IETF 84 meeting held in =
Vancouver, regular columns submitted by the IETF, the IAB and the IRTF =
chairs, summaries of the plenary sessions, and articles on the =
fellowships to IETF.

You can read this publication online or download the full issue in PDF =
format. You can also keep up to date with the latest issue by =
subscribing to the IETF Journal as an email edition or have it delivered =
to your postal address in hardcopy.

Many thanks to all our contributors. Please send any comments or =
suggestions for future issues to ietfjournal@isoc.org.

Kind Regards,

Mat Ford
Managing Editor
IETF Journal
http://internetsociety.org/ietfjournal=

From ogud@ogud.com  Wed Oct 31 14:22:01 2012
Return-Path: <ogud@ogud.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 56E3921F877F for <ietf@ietfa.amsl.com>; Wed, 31 Oct 2012 14:22:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.843
X-Spam-Level: 
X-Spam-Status: No, score=-104.843 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, GB_I_LETTER=-2, J_CHICKENPOX_42=0.6, RCVD_IN_DNSWL_LOW=-1, SUBJECT_FUZZY_TION=0.156, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9Kne4sTKBEJd for <ietf@ietfa.amsl.com>; Wed, 31 Oct 2012 14:22:00 -0700 (PDT)
Received: from smtp157.iad.emailsrvr.com (smtp157.iad.emailsrvr.com [207.97.245.157]) by ietfa.amsl.com (Postfix) with ESMTP id CC81221F876D for <ietf@ietf.org>; Wed, 31 Oct 2012 14:22:00 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp45.relay.iad1a.emailsrvr.com (SMTP Server) with ESMTP id 0AFC59086F; Wed, 31 Oct 2012 17:21:57 -0400 (EDT)
X-Virus-Scanned: OK
Received: by smtp45.relay.iad1a.emailsrvr.com (Authenticated sender: ogud-AT-ogud.com) with ESMTPSA id 023C4901A1;  Wed, 31 Oct 2012 17:21:55 -0400 (EDT)
Message-ID: <50919671.6000605@ogud.com>
Date: Wed, 31 Oct 2012 17:21:53 -0400
From: Olafur Gudmundsson <ogud@ogud.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121010 Thunderbird/16.0.1
MIME-Version: 1.0
To: 'IETF-Discussion list' <ietf@ietf.org>
Subject: Recall petition for Mr. Marshall Eubanks
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: ogud@ogud.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Oct 2012 21:22:01 -0000

Fellow IETF'rs
below is a recall petition that I plan on submitting soon if there is 
enough support.

If you agree with this petition please either comment on this posting, 
or send me email of support noting if you are NomCom eligible (I'm 
arbitrarily limiting the submitted signers of the petition to people 
that have demonstrated recent IETF attendance and participation)

The reason I'm starting this recall petition is that I think no other 
way will vacate the positions that Marchall holds before the end of the 
year, I have purposely held of starting this process in the hope that 
Marshall on his own resigned but that has not happened even after he has 
been publicly exposed for over a week.

I'm disappointed that a person that took on a responsibility that he his 
not able/willing to fulfill anymore, has not had the courtesy to take a 
few minutes to draft and send a letter of resignation or an explanation.

Olafur

-------- Recall Petition ------------

Lynn St. Amour ISOC president,

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

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

   I as an IETF member in good standing (having attended over 50 
meetings since 1987, including 9 of the last 10 meetings), regrettably 
request that you start the recall procedure. Below are listed statements 
of support for this recall petition from  more than 20 other NomCom 
eligible IETF participants.


Thanks

       Olafur Gudmundsson

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


From melinda.shore@gmail.com  Wed Oct 31 18:15:18 2012
Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 407B221F889C for <ietf@ietfa.amsl.com>; Wed, 31 Oct 2012 18:15:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.471
X-Spam-Level: 
X-Spam-Status: No, score=-3.471 tagged_above=-999 required=5 tests=[AWL=-0.628, BAYES_00=-2.599, J_CHICKENPOX_42=0.6, RCVD_IN_DNSWL_LOW=-1, SUBJECT_FUZZY_TION=0.156]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hDqfRD5uFI7J for <ietf@ietfa.amsl.com>; Wed, 31 Oct 2012 18:15:16 -0700 (PDT)
Received: from mail-da0-f44.google.com (mail-da0-f44.google.com [209.85.210.44]) by ietfa.amsl.com (Postfix) with ESMTP id 76C6B21F8889 for <ietf@ietf.org>; Wed, 31 Oct 2012 18:15:16 -0700 (PDT)
Received: by mail-da0-f44.google.com with SMTP id h15so900288dan.31 for <ietf@ietf.org>; Wed, 31 Oct 2012 18:15:16 -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=7Hld+pgGf8VxvX6+dw9h4oqqkvICb+o3kfLu1JOTEA4=; b=O0AOvxqOBfBPPpuuVkKHEuGwkIaSKZWgO7qBK8r8coOvlhvZTkJwfdfhnaJ/6ehlew QcLvsbKHgJ0s9daUqbN+NopaO9FokRSpgIxFDnLTs1YxprQYsqTZtsQ60McR2iWglEkA +OU7pOGdMDtRSQKIgrWEsntKfI++53fJFXG5AFYwN35vfHYlODt8qMUbzBjd7jf80gi1 pznn4f/N+Bqi7eEtL2bDJU4so/yxnTiIpakWmV05KYHAFk7gl3bMfcCznQDSysN9oTRN RmGTQjjGMLkyqItJTPQfmFP41aaYJrFsIg9qb/5S9ce49rVL+zWcrdN9WNTr1BV4GzPx XW9A==
Received: by 10.68.115.75 with SMTP id jm11mr117242112pbb.28.1351732515976; Wed, 31 Oct 2012 18:15:15 -0700 (PDT)
Received: from spandex.local (216-67-49-109-rb1.fai.dsl.dynamic.acsalaska.net. [216.67.49.109]) by mx.google.com with ESMTPS id g10sm3034457pav.9.2012.10.31.18.15.14 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 31 Oct 2012 18:15:15 -0700 (PDT)
Message-ID: <5091CD21.3010504@gmail.com>
Date: Wed, 31 Oct 2012 17:15:13 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:16.0) Gecko/20121010 Thunderbird/16.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Recall petition for Mr. Marshall Eubanks
References: <50919671.6000605@ogud.com>
In-Reply-To: <50919671.6000605@ogud.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Nov 2012 01:15:18 -0000

On 10/31/12 1:21 PM, Olafur Gudmundsson wrote:
> Fellow IETF'rs
> below is a recall petition that I plan on submitting soon if there is
> enough support.

I regret having to do it this way, but since it seems to be necessary
and there is no agreed-upon alternative, I support this.

Melinda



From warren@kumari.net  Wed Oct 31 18:22:19 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 37A0B21F869C for <ietf@ietfa.amsl.com>; Wed, 31 Oct 2012 18:22:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.447
X-Spam-Level: 
X-Spam-Status: No, score=-100.447 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_42=0.6, MIME_QP_LONG_LINE=1.396, SUBJECT_FUZZY_TION=0.156, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FC8nVCItGNga for <ietf@ietfa.amsl.com>; Wed, 31 Oct 2012 18:22:18 -0700 (PDT)
Received: from vimes.kumari.net (smtp1.kumari.net [204.194.22.1]) by ietfa.amsl.com (Postfix) with ESMTP id B370621F8650 for <ietf@ietf.org>; Wed, 31 Oct 2012 18:22:18 -0700 (PDT)
Received: from [10.71.6.206] (unknown [216.138.103.10]) by vimes.kumari.net (Postfix) with ESMTPSA id BA4C01B400EE; Wed, 31 Oct 2012 21:22:16 -0400 (EDT)
References: <50919671.6000605@ogud.com> <5091CD21.3010504@gmail.com>
In-Reply-To: <5091CD21.3010504@gmail.com>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=us-ascii
Message-Id: <1158F458-8810-4CD2-B874-3DE1A1B8B0B5@kumari.net>
X-Mailer: iPhone Mail (10A405)
From: Warren Kumari <warren@kumari.net>
Subject: Re: [IETF] Re: Recall petition for Mr. Marshall Eubanks
Date: Wed, 31 Oct 2012 21:22:15 -0400
To: Melinda Shore <melinda.shore@gmail.com>
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Nov 2012 01:22:19 -0000

Warren Kumari
------
Please excuse typing, etc -- This was sent from a device with a tiny keyboar=
d.

On Oct 31, 2012, at 9:15 PM, Melinda Shore <melinda.shore@gmail.com> wrote:

> On 10/31/12 1:21 PM, Olafur Gudmundsson wrote:
>> Fellow IETF'rs
>> below is a recall petition that I plan on submitting soon if there is
>> enough support.
>=20
> I regret having to do it this way,

+1

> but since it seems to be necessary
> and there is no agreed-upon alternative, I support this.
>=20

As do I.

:-(

W

> Melinda
>=20
>=20
